Re: [c-nsp] Renumbering serial interfaces
Another option is to have a loopback address on the far end device with a static route on the near end device pointing at the exit interface (not the next-hop IP). That way you can telnet to the loopback address and overwrite the interface address without breaking your telnet session. Reload in 5 as a precaution, of course. Robert Robert Smales Technical Engineer CableWireless Worldwide www.cw.com -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net]on Behalf Of Johan Grip Sent: 18 February 2010 15:21 To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Renumbering serial interfaces On Thu, 18 Feb 2010 14:22:26 +0100, Steve Bertrand st...@ibctech.ca wrote: On 2010.02.18 03:22, Brian Turnbow wrote: Besides the reload in xx that several have mentioned you can also put secondary Ips on the link Nad then cancel the primary. I.e. interface ATM0/0.32 point-to-point Ip add 2.2.2.2 255.255.255.252 secondary Telnet/ssh to this address using source address 2.2.2.1 Then no ip add 1.1.1.1 255.255.255.252 The 2.2.2.2 address becomes the priamry and you should not loose the management session. Does this work differently on a serial interface? On an fa int: route-server1(config)#int lo75 route-server1(config-if)#ip address 208.70.109.155 255.255.255.255 route-server1(config-if)#ip address 208.70.109.156 255.255.255.255 sec route-server1(config-if)#no ip address 208.70.109.155 255.255.255.255 Must delete secondary before deleting primary Steve This is how I usually do it. --- Router#sh run int fa0/0 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/0 ip address 2.2.2.2 255.255.255.0 secondary ip address 1.1.1.1 255.255.255.0 duplex auto speed auto end Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#int fa0/0 Router(config-if)#ip add 2.2.2.2 255.255.255.0 Router(config-if)#^Z Router# Router#sh run int fa0/0 Building configuration... Current configuration : 92 bytes ! interface FastEthernet0/0 ip address 2.2.2.2 255.255.255.0 duplex auto speed auto end Router# --- //Johan ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ This e-mail has been scanned for viruses by the Cable Wireless e-mail security system - powered by MessageLabs. For more information on a proactive managed e-mail security service, visit http://www.cwworldwide.com/managed-exchange The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named above as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender (whose contact details are above) immediately by reply e-mail and delete the message and any attachments without retaining any copies. Cable and Wireless plc Registered in England and Wales.Company Number 238525 Registered office: 3rd Floor, 26 Red Lion Square, London WC1R 4HQ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Isn't configuration rollback supposed to bypass the reload in 5 issue? -- Tassos Gert Doering wrote on 17/02/2010 22:30: Always remember to put in reload in 5 before you do anything that might lock you out, and reload cancel afterwards... gert ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Besides the reload in xx that several have mentioned you can also put secondary Ips on the link Nad then cancel the primary. I.e. interface ATM0/0.32 point-to-point Ip add 2.2.2.2 255.255.255.252 secondary Telnet/ssh to this address using source address 2.2.2.1 Then no ip add 1.1.1.1 255.255.255.252 The 2.2.2.2 address becomes the priamry and you should not loose the management session. Don't forget to cancell the reload Brian -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of james edwards Sent: mercoledì 17 febbraio 2010 19.20 To: cisco-nsp@puck.nether.net Subject: [c-nsp] Renumbering serial interfaces I have a bunch of T-1 (ATM) interfaces that I need to renumber. I have always done this with 2 people, one on each end. Is it possible for one person to do this, from one end ? If I am on the near side, I log into the far sides serial IP and do this: LALMR_2620(config)#interface ATM0/0.32 point-to-point LALMR_2620(config-subif)#ip address 1.1.1.1 255.255.255.252 LALMR_2620(config-subif)#^Z -- James H. Edwards Senior Network Systems Administrator Judicial Information Division jedwa...@nmcourts.gov ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
I have a bunch of T-1 (ATM) interfaces that I need to renumber. I have always done this with 2 people, one on each end. Is it possible for one person to do this, from one end ? If I am on the near side, I log into the far sides serial IP and do this: You could setup ipv6 between the two routers and ssh/telnet over that while you are changing the ipv4 settings. Craig. ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Sorry the last line should be ip address 208.70.109.156 255.255.255.255 Making the secondary primary, and removing the primary. I remember doing it with no ip address x.x.x.x but I just tried and it gives me the same error. Too much lunch I think. Brian -Original Message- From: Steve Bertrand [mailto:st...@ibctech.ca] Sent: giovedì 18 febbraio 2010 14.22 To: Brian Turnbow Cc: james edwards; cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Renumbering serial interfaces On 2010.02.18 03:22, Brian Turnbow wrote: Besides the reload in xx that several have mentioned you can also put secondary Ips on the link Nad then cancel the primary. I.e. interface ATM0/0.32 point-to-point Ip add 2.2.2.2 255.255.255.252 secondary Telnet/ssh to this address using source address 2.2.2.1 Then no ip add 1.1.1.1 255.255.255.252 The 2.2.2.2 address becomes the priamry and you should not loose the management session. Does this work differently on a serial interface? On an fa int: route-server1(config)#int lo75 route-server1(config-if)#ip address 208.70.109.155 255.255.255.255 route-server1(config-if)#ip address 208.70.109.156 255.255.255.255 sec route-server1(config-if)#no ip address 208.70.109.155 255.255.255.255 Must delete secondary before deleting primary Steve ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
On Thu, 18 Feb 2010 14:22:26 +0100, Steve Bertrand st...@ibctech.ca wrote: On 2010.02.18 03:22, Brian Turnbow wrote: Besides the reload in xx that several have mentioned you can also put secondary Ips on the link Nad then cancel the primary. I.e. interface ATM0/0.32 point-to-point Ip add 2.2.2.2 255.255.255.252 secondary Telnet/ssh to this address using source address 2.2.2.1 Then no ip add 1.1.1.1 255.255.255.252 The 2.2.2.2 address becomes the priamry and you should not loose the management session. Does this work differently on a serial interface? On an fa int: route-server1(config)#int lo75 route-server1(config-if)#ip address 208.70.109.155 255.255.255.255 route-server1(config-if)#ip address 208.70.109.156 255.255.255.255 sec route-server1(config-if)#no ip address 208.70.109.155 255.255.255.255 Must delete secondary before deleting primary Steve This is how I usually do it. --- Router#sh run int fa0/0 Building configuration... Current configuration : 136 bytes ! interface FastEthernet0/0 ip address 2.2.2.2 255.255.255.0 secondary ip address 1.1.1.1 255.255.255.0 duplex auto speed auto end Router#conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#int fa0/0 Router(config-if)#ip add 2.2.2.2 255.255.255.0 Router(config-if)#^Z Router# Router#sh run int fa0/0 Building configuration... Current configuration : 92 bytes ! interface FastEthernet0/0 ip address 2.2.2.2 255.255.255.0 duplex auto speed auto end Router# --- //Johan ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Hi, On Thu, Feb 18, 2010 at 08:58:56AM -0500, Steve Bertrand wrote: I suppose that considering that this is a PtP link, the OP could apply an IPv6 address to each end, verify reachability, and temporarily remove all v4 addresses and still maintain a connection until the work is complete :) Haha, cool approach. (But given that this is Cisco and ATM, chances are that IPv6 will not work in this specific combination of IOS + ATM setup + ATM hardware...) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgp9bVH3Y21M9.pgp Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Test this ahead of time with a lab box if you can ;) What I've done in this scenarios is to build the snippets of config I need to apply and put them into a plain text file. Then do a copy tftp://blahblah/filename running-config which merges the changes. Before I do the copy I do a reload in 15 in case it fails so that I know I can get back into the box in 15 minutes YMMV... Please test this though as I haven't done it in a while but did work for my needs at the time... Paul -Original Message- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of james edwards Sent: Wednesday, February 17, 2010 1:20 PM To: cisco-nsp@puck.nether.net Subject: [c-nsp] Renumbering serial interfaces I have a bunch of T-1 (ATM) interfaces that I need to renumber. I have always done this with 2 people, one on each end. Is it possible for one person to do this, from one end ? If I am on the near side, I log into the far sides serial IP and do this: LALMR_2620(config)#interface ATM0/0.32 point-to-point LALMR_2620(config-subif)#ip address 1.1.1.1 255.255.255.252 LALMR_2620(config-subif)#^Z -- James H. Edwards Senior Network Systems Administrator Judicial Information Division jedwa...@nmcourts.gov ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
You can renumber serial links with one person. Standard disclaimer of paying attention to detail, being careful, etc. If you can tolerate a few minutes downtime worst-case (which, I'm making the assumption this is being done in a window that can), you can also use the 'reload in x' command, where x = minutes. If you botch it and cannot get back in, the device will reload with the saved startup configuration (ie: not with your most current changes). You can roll back the near side and be back up. If all changes are successful, don't forget to reload cancel and write your changes. Obviously there are some other things you probably need to consider like routing protocol adjacencies, or static default routes... so telnet/ssh'ing in from a directly connected interface may be necessary depending on the setup. The only time something like this is a bit more tricky is when multiple changes are required (encapsulation, etc.) HTH, -Ryan On Wed, Feb 17, 2010 at 1:19 PM, james edwards lists.james.edwa...@gmail.com wrote: I have a bunch of T-1 (ATM) interfaces that I need to renumber. I have always done this with 2 people, one on each end. Is it possible for one person to do this, from one end ? If I am on the near side, I log into the far sides serial IP and do this: LALMR_2620(config)#interface ATM0/0.32 point-to-point LALMR_2620(config-subif)#ip address 1.1.1.1 255.255.255.252 LALMR_2620(config-subif)#^Z -- James H. Edwards Senior Network Systems Administrator Judicial Information Division jedwa...@nmcourts.gov ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: [c-nsp] Renumbering serial interfaces
Hi, On Wed, Feb 17, 2010 at 11:19:31AM -0700, james edwards wrote: I have a bunch of T-1 (ATM) interfaces that I need to renumber. I have always done this with 2 people, one on each end. Is it possible for one person to do this, from one end ? If I am on the near side, I log into the far sides serial IP and do this: LALMR_2620(config)#interface ATM0/0.32 point-to-point LALMR_2620(config-subif)#ip address 1.1.1.1 255.255.255.252 LALMR_2620(config-subif)#^Z Should work. (At that point, the connection will lock up, and then you need to connect to the new address and continue) Always remember to put in reload in 5 before you do anything that might lock you out, and reload cancel afterwards... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany g...@greenie.muc.de fax: +49-89-35655025g...@net.informatik.tu-muenchen.de pgpGmYeZeGU3S.pgp Description: PGP signature ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
