what should I have done ?
Here is a situation were I cut myself out trying to change IP address .. I need to know what I should do the next time so that I can avoid this from happening.
purpose of the project was to change ip address in a remote 1702 route.
Working status:
---------------
cisco 7206
----------
serial 1/1/1:0
ip address 10.10.1.61 255.255.255.252
ip route *.*.*.60 255.255.255.252 serial 1/1/1:0
Remote end 1702 router:
------------------------
Serial0
ip address 10.10.1.62 255.255.255.252
Fastethernet0
ip address *.*.*.61 255.255.255.252
ip route 0.0.0.0 0.0.0.0 10.10.1.61
**************************
In the above situation , I wanted to change IP block to *.*.*.114 . I also wanted to change the private IP on the serial
so that I can be consistent..
So this is what I did.
CISCO 7206:
-----------
I added an ip route
ip route *.*.*.112 255.255.255.252 serial 1/1/1:0
Then on CISCO 1702 (remote end)
I changed the IP for Fastethernet to
ip address *.*.*.113 255.255.255.252 and finally it looked like this
CISCO 7206:
-----------
serial 1/1/1:0
ip address 10.10.1.61 255.255.255.252
ip address 10.10.1.113 255.255.255.252 secondary <=== added secondary on the serial
ip route *.*.*.112 255.255.255.252 serial 1/1/1:0 <== added the correct ip route for that block
CISCO 1702:
-----------
Serial0
ip address 10.10.1.62 255.255.255.252
ip address 10.10.1.114 255.255.255.252 secondary
Fastethernet0
ip address *.*.*.113 255.255.255.252
ip route 0.0.0.0 0.0.0.0 10.10.1.61
ip route 0.0.0.0 0.0.0.0 10.10.1.113 <===== added this so that I can get back to it from 7206
Even at this point , I was good..... Now I went inside the CISCO 1702 using the public IP and had to remove the serial interface primary IP and make secondary as primary.. I removed the secondary , I was good. I removed the primary , I got cut off.. What should I have done ??
purpose of the project was to change ip address in a remote 1702 route.
Working status:
---------------
cisco 7206
----------
serial 1/1/1:0
ip address 10.10.1.61 255.255.255.252
ip route *.*.*.60 255.255.255.252 serial 1/1/1:0
Remote end 1702 router:
------------------------
Serial0
ip address 10.10.1.62 255.255.255.252
Fastethernet0
ip address *.*.*.61 255.255.255.252
ip route 0.0.0.0 0.0.0.0 10.10.1.61
**************************
In the above situation , I wanted to change IP block to *.*.*.114 . I also wanted to change the private IP on the serial
so that I can be consistent..
So this is what I did.
CISCO 7206:
-----------
I added an ip route
ip route *.*.*.112 255.255.255.252 serial 1/1/1:0
Then on CISCO 1702 (remote end)
I changed the IP for Fastethernet to
ip address *.*.*.113 255.255.255.252 and finally it looked like this
CISCO 7206:
-----------
serial 1/1/1:0
ip address 10.10.1.61 255.255.255.252
ip address 10.10.1.113 255.255.255.252 secondary <=== added secondary on the serial
ip route *.*.*.112 255.255.255.252 serial 1/1/1:0 <== added the correct ip route for that block
CISCO 1702:
-----------
Serial0
ip address 10.10.1.62 255.255.255.252
ip address 10.10.1.114 255.255.255.252 secondary
Fastethernet0
ip address *.*.*.113 255.255.255.252
ip route 0.0.0.0 0.0.0.0 10.10.1.61
ip route 0.0.0.0 0.0.0.0 10.10.1.113 <===== added this so that I can get back to it from 7206
Even at this point , I was good..... Now I went inside the CISCO 1702 using the public IP and had to remove the serial interface primary IP and make secondary as primary.. I removed the secondary , I was good. I removed the primary , I got cut off.. What should I have done ??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So I guess the problem was that to start with in my 1702 , I had
ip route 0.0.0.0 0.0.0.0 10.10.1.61
Was that the issue then ?
ip route 0.0.0.0 0.0.0.0 10.10.1.61
Was that the issue then ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>So I guess the problem was that to start with in my 1702 , I had
>ip route 0.0.0.0 0.0.0.0 10.10.1.61
>Was that the issue then ?
Yep. It should either be changed to the interface, or add another route to the new .113, then go back and delete the one to .61
>ip route 0.0.0.0 0.0.0.0 10.10.1.61
>Was that the issue then ?
Yep. It should either be changed to the interface, or add another route to the new .113, then go back and delete the one to .61
ASKER
This is what happened..
I had only 1 ip route to start with in 1702 and it was
ip route 0.0.0.0 0.0.0.0 10.10.1.61
Then I assumed adding a secondary route would help some , so i added this
ip route 0.0.0.0 0.0.0.0 10.10.1.113 <-=== I had already added serial interface in 7206 for 10.10.1.113..
I didnot realise that I could have done all these without even adding a secondary ip address to any of the interface as Lrmoore had mentioned.. But knowing how to add secondary IP address would come handy sometimes.
>>So you removed both the secondary AND the primary IP address ? This would mean that the interface had NO IP address ??
Exactly what happened. Now it looks that i made a silly mistake but when I was doing this , I had good concentration on what i was doing. We had a linux machine at the customer end which was connected to the 1702.. I did the change on the linux first (went well) , then changed the IP address of the fastethernet (that went well) but screwed at the serial..
Oh well.. another learning experience..
I had only 1 ip route to start with in 1702 and it was
ip route 0.0.0.0 0.0.0.0 10.10.1.61
Then I assumed adding a secondary route would help some , so i added this
ip route 0.0.0.0 0.0.0.0 10.10.1.113 <-=== I had already added serial interface in 7206 for 10.10.1.113..
I didnot realise that I could have done all these without even adding a secondary ip address to any of the interface as Lrmoore had mentioned.. But knowing how to add secondary IP address would come handy sometimes.
>>So you removed both the secondary AND the primary IP address ? This would mean that the interface had NO IP address ??
Exactly what happened. Now it looks that i made a silly mistake but when I was doing this , I had good concentration on what i was doing. We had a linux machine at the customer end which was connected to the 1702.. I did the change on the linux first (went well) , then changed the IP address of the fastethernet (that went well) but screwed at the serial..
Oh well.. another learning experience..
ASKER
>> It should either be changed to the interface, or add another route to the new .113, then go back and delete the one to .61
As i said , I did have 2 routes...Hmm. puzzling now..
As i said , I did have 2 routes...Hmm. puzzling now..
ASKER
The reload option that td_miles suggested is a very smart suggestion
ASKER