Request to review my process for upgrading 6509's from Sup1a's to Sup2's...

Unanswered Question

(I had to enter this in three posts, so bare with me)


I have TWO 6509's I'm upgrading from redundant Sup1a-2ge's to redundant Sup2's.


Fortunately I have a spare 6509 to build and prep the current configuration on the new Sup's.


I believe I've covered all the bases but thought I'd throw it out to the pro's to see if there's anything else I should be aware of. I'd appreciate any further input.


I've list a "show module" output and my process in a nutshell below.


Thanks in advance for reviewing my process and for any other information you might have.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

SWITCH1#sho mod

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 2 Cat 6k sup 1 Enhanced QoS (Active) WS-X6K-SUP1A-2GE SAD040200B0

2 2 Cat 6k sup 1 Enhanced QoS (Standby) WS-X6K-SUP1A-2GE SAD0430020W

3 8 8 port 1000mb ethernet WS-X6408-GBIC SAD03352733

4 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD03466100

5 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD04160DYZ

6 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD040706BV

7 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAD082701B5

9 8 8 port 1000mb ethernet WS-X6408-GBIC SAD03407071


Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

1 0030.b634.7858 to 0030.b634.7859 3.1 5.3(1) 12.1(27b)E1 Ok

2 00d0.d33b.ba10 to 00d0.d33b.ba11 3.2 5.3(1) 12.1(27b)E1 Ok

3 0030.80af.42bc to 0030.80af.42c3 2.3 4.2(0.24)VAI 8.5(0.23)COS Ok

4 0030.b633.9ce8 to 0030.b633.9d17 1.1 4.2(0.24)VAI 8.5(0.23)COS Ok

5 00b0.8e81.d264 to 00b0.8e81.d293 1.2 5.1(1)CSX 8.5(0.23)COS Ok

6 0030.19c6.c3e0 to 0030.19c6.c40f 1.1 4.2(0.24)VAI 8.5(0.23)COS Ok

7 0001.c9dc.c76e to 0001.c9dc.c79d 6.1 7.2(1) 8.5(0.23)COS Ok

9 0030.9629.e7e4 to 0030.9629.e7eb 2.3 4.2(0.24)VAI 8.5(0.23)COS Ok


Mod Sub-Module Model Serial Hw Status

--- --------------------------- --------------- --------------- ------- -------

1 Policy Feature Card WS-F6K-PFC SAD04010C6C 1.0 Ok

1 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04010CBK 1.4 Ok

2 Policy Feature Card WS-F6K-PFC SAD042810D3 1.1 Ok

2 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04280H1S 1.4 Ok


SWITCH2#sho mod

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 2 Cat 6k sup 1 Enhanced QoS (Active) WS-X6K-SUP1A-2GE SAD04320FF2

2 2 Cat 6k sup 1 Enhanced QoS (Standby) WS-X6K-SUP1A-2GE SAD04500C1H

3 8 8 port 1000mb ethernet WS-X6408-GBIC SAD041308ML

4 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD04110A8W

5 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD03235340

6 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD04160EM5

7 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAD082001HS

9 8 8 port 1000mb ethernet WS-X6408-GBIC SAD03362037


Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

1 00d0.c0d2.0b00 to 00d0.c0d2.0b01 3.2 5.3(1) 12.1(27b)E1 Ok

2 0001.972d.00c4 to 0001.972d.00c5 7.0 5.3(1) 12.1(27b)E1 Ok

3 0030.b637.1d6c to 0030.b637.1d73 2.4 5.1(1)CSX 8.5(0.23)COS Ok

4 00d0.d3a0.7320 to 00d0.d3a0.734f 1.2 5.1(1)CSX 8.5(0.23)COS Ok

5 0050.f0ae.3824 to 0050.f0ae.3853 1.1 4.2(0.24)VAI 8.5(0.23)COS Ok

6 0001.9713.5af0 to 0001.9713.5b1f 1.2 5.1(1)CSX 8.5(0.23)COS Ok

7 0011.2056.d6fe to 0011.2056.d72d 6.0 7.2(1) 8.5(0.23)COS Ok

9 00d0.d39c.eb24 to 00d0.d39c.eb2b 2.3 4.2(0.24)VAI 8.5(0.23)COS Ok


Mod Sub-Module Model Serial Hw Status

--- --------------------------- --------------- --------------- ------- -------

1 Policy Feature Card WS-F6K-PFC SAD04290S68 1.1 Ok

1 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04320K67 1.4 Ok

2 Policy Feature Card WS-F6K-PFC SAD050102DH 1.1 Ok

2 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04281CBN 1.4 Ok

SWITCH2#sho mod

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

1 2 Cat 6k sup 1 Enhanced QoS (Active) WS-X6K-SUP1A-2GE SAD04320FF2

2 2 Cat 6k sup 1 Enhanced QoS (Standby) WS-X6K-SUP1A-2GE SAD04500C1H

3 8 8 port 1000mb ethernet WS-X6408-GBIC SAD041308ML

4 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD04110A8W

5 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD03235340

6 48 48 port 10/100 mb RJ-45 ethernet WS-X6248-RJ-45 SAD04160EM5

7 48 48 port 10/100/1000mb EtherModule WS-X6148-GE-TX SAD082001HS

9 8 8 port 1000mb ethernet WS-X6408-GBIC SAD03362037


Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

1 00d0.c0d2.0b00 to 00d0.c0d2.0b01 3.2 5.3(1) 12.1(27b)E1 Ok

2 0001.972d.00c4 to 0001.972d.00c5 7.0 5.3(1) 12.1(27b)E1 Ok

3 0030.b637.1d6c to 0030.b637.1d73 2.4 5.1(1)CSX 8.5(0.23)COS Ok

4 00d0.d3a0.7320 to 00d0.d3a0.734f 1.2 5.1(1)CSX 8.5(0.23)COS Ok

5 0050.f0ae.3824 to 0050.f0ae.3853 1.1 4.2(0.24)VAI 8.5(0.23)COS Ok

6 0001.9713.5af0 to 0001.9713.5b1f 1.2 5.1(1)CSX 8.5(0.23)COS Ok

7 0011.2056.d6fe to 0011.2056.d72d 6.0 7.2(1) 8.5(0.23)COS Ok

9 00d0.d39c.eb24 to 00d0.d39c.eb2b 2.3 4.2(0.24)VAI 8.5(0.23)COS Ok


Mod Sub-Module Model Serial Hw Status

--- --------------------------- --------------- --------------- ------- -------

1 Policy Feature Card WS-F6K-PFC SAD04290S68 1.1 Ok

1 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04320K67 1.4 Ok

2 Policy Feature Card WS-F6K-PFC SAD050102DH 1.1 Ok

2 MSFC Cat6k daughterboard WS-F6K-MSFC SAD04281CBN 1.4 Ok

This is my preperation process so far (please make any further corrections/comments):


1. Found and loaded acceptable IOS.


2. Put IOS in the sup-bootflash and slavesup-bootflash of both switches, as well as booting it from a flash/disk location.


3. Matched VTP settings on new Sup's to match current Sup's.


4. Created current/matching/correct Vlan database in global configuration on both

Sup's/switches.


5. Entered current configs line by line into spare switch with new processor cards. Resolved all conflicts/messages.


6. Manually "no shutdown" appropriate interfaces since all were in shutdown by default.


7. Connected to a few ports tested some routing across ports and saw interfaces, vlan, and spanning-tree come up for the active ports and vlans I was testing.


8. Tested Redundancy Plus failover feature.


9. Set time, date, timezone.


10. Wrote memory and backed up new running-config and vlan.dat files.


11. Gathered legacy information from current switches for interface status, speed/duplex settings, VTP, show version, etc, etc...so if anything doesn't work I can reference on the fly.

glen.grant Fri, 01/30/2009 - 08:51
User Badges:
  • Purple, 4500 points or more

If you are running client/server for vtp then if the current version level on the network is higher than what you have on your new sup then the vlan database will get overwritten . If you are all transparent mode then it isn't a issue.

Thank you for taking the time to look at it.


Both routers are configured in VTP server mode so each one can up date the other. And, there are no other devices participating in VTP on the network, just these two.


Correct me if I'm wrong but if I bring one switch up, and then the other switch, and one did overwrite the other I shouldn't have an issue as long as they have the same contents, right? As in one might overwrite the other but with the same data.



ibrunello Fri, 01/30/2009 - 09:55
User Badges:

The issue is with VTP config revision.

You can tell by running "show vtp status" in IOS-integrated (cannot recall CatOS command).

Latest revision always overwrites former one.

Same revision: no overwrite at all.

To ensure VTP works as expected:

1) bring up first switch, in server mode, and check everything is alright (that is, all VLAN config is as expected).

2) shut down all trunk ports to second switch.

(this prevent exchanging VTP info, unless you have other switches connected to both nodes: in this case shut down EVERY TRUNK port)

3) start second switch.

4) set second switch to transparent (this reset revision on the second to "0")

5) bring up trunk ports.

6) set second switch to VTP mode server: as long as vtp domain and password are the same, you can be sure that the FIRST COPIES OVER TO SECOND, and not the reverse.


hope this may help.


Ivan

Thanks for the information so far.


I double checked the VTP status' on the SUPs and see that switch 2 is at a higher revision number.


Since both SUPs have the same VLAN DB, does it matter which over writes the other?


Also...


Is it true that I can change the VTP domain NAME on the second switch/set of SUPs and then set it back to what it was and that will reset the VTP Configuration Revision number?


I just want to verify that the VLAN DB will stay the same after changing the name, as I don't want to mess with this configuration again if I don't have to.

ibrunello Fri, 01/30/2009 - 11:40
User Badges:

If switch 2 has an higher revision, and they're still connected, something is wrong.

in a working VTP environment, revision should be the same across all VTP domain.


If you disconnected them, or change something (e.g. domain name or password), then there should not be a problem.

use switch 2 as the master, and make the vtp transparent/master on switch 1.


Not quite sure changing domain resets revision.

I'd perform such test on the third, offline chassis.


Cisco suggested way of resetting revision is setting to VTP transparent mode and then back to VTP server mode.


ibrunello Fri, 01/30/2009 - 11:33
User Badges:

As long as they're the same, it doesn't matter.

Please note that even if you create them the same, every time you perform a change in vlan structure (e.g. adding or removing vlan), the vlan.dat is automatically updated.


That is why, although you're sure vlan.dat is the same, I always prefer to consider one as the master.


The sequence outlined ensures that one vlan.dat (the latter), is somehow "demoted" and considered older, and thus overwritten.


Hope this cleared a bit more.

I know performing this kind of operations on such beasts is somehow scaring, expecially when they carry a lot of services.

Thanks for the clarification!


They are the same since I used the same "script" or command list to create them. The only thing that's different between the two switches are the interfaces assigned to the VLANs.


I'm going to try the Domain Name change. It seems the revision number will set back to 0 and also DB will stay the same between name changes.

Just as follow up...


I was able to rename the VTP domain on switch2 then rename it back to what I wanted. This set the Config Revision back to 0 and the Vlan.dat stayed intact without nothing changing/resetting.


So now when the two switches peer up switch1 we be the "master revision" during the process/changes.


Thanks for the help guys!

Actions

This Discussion