RE: WAN's secondary ip

From: Joe (groupstudy@comcast.net)
Date: Mon Dec 30 2002 - 22:51:56 GMT-3


This is great example of where the command 'reload' with a timer on it
would come into use to minimize error and down-time. First schedule the
reload, then change the address. When you try to reconnect you either
get in or you don't, 50/50 chance of it being done right or wrong. If
you don't get in, the timer counts down and reboots into the old config.
If you do get in, cancel the reboot and write mem and pop open a
'beverage'.

Joe

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Tim Fletcher
Sent: Monday, December 30, 2002 11:38 AM
To: Tom Young; ccielab@groupstudy.com
Subject: Re: WAN's secondary ip

Tom,

I don't think a secondary address will help, but there's no reason why
you
can't change the primary remote address, I've done it many times. It
does
create a short outage, usually less than a minute.

Before you do this, you should go through your configs carefully to make

sure changing the address is not going to break anything else. For
example
if you are running a routing protocol and the new addresses are not
configured as part of that protocol, your routing will break.

1. Telnet to the both the local and remote routers.
2. Do an "reload in 10" on the remote router. (just in case)
3. Change the IP address on your remote router. The instant you hit the
Enter key your telnet session will die, but that's ok.
4. Change the IP address on your local router.
5. Telnet to the new remote address (you may want to telnet from the
session on your local router to eliminate any dependency on routing
issues). 6. If the telnet is successful, do a "reload cancel". If not,
change the
local routers address back and wait for the remote router to reload with

the old address.

If you're careful, you shouldn't have a problem, but you should always
consider the risk if things don't go right.

-Tim Fletcher

At 02:12 PM 12/27/2002 +0900, Tom Young wrote:
>Hi, group
>
> I will change the ip of leased line from host, and
>nobody in the remote office. So, I have to change the
>remote router's wan ip from host but don't let the line
>cut. I want to set the new ip as secondary ip in remote router's wan
>port, and change the host 's wan ip, then delete the remote router's
>old wan ip. Is it ok?
> I know I could assign the secondary ip in a etherport , but the bri

>port, I don't know.
>
>
>Thanks alot
>
>__________________________________________________
>Do You Yahoo!?
>Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
>.
.



This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:55 GMT-3