vince
asked on
Switch Migration
Hello Team,
We have a migration project as below.I’m thinking should we do a rip & replace or run the 3750 and 6509 parallel till migration is over,if that is a viable option.Most of the existing configs will be copied to 6509.
Existing WS-C3750X-48 stacked core switch to be migrated to 6509-V-E with 2x WS-X6848-TX-2T and WS-X6816-10G-2T.
Various 2960’S and 3850 are trunked to the existing 3750X-48.
1)Existing 3750 has pvst and new 6509 has rapid-pvst.Will it be ok to use rapid-pvst.Will there be any issues with the existing switches on the network.We don’t have access to other access switches and assume they running pvst.
2)Existing 3750 is configured as VTP Primary Server.How do we configure the 6509 VTP, so that existing VLAN’s get transferred to the 6509.There are about 100 SVI/VLAN.Do we need to re-create the SVI’s on 6509.
3)Concerned if we connect the 6509 to existing environment the revision numbers may change and we lose the vlan database on entire network.
We have a migration project as below.I’m thinking should we do a rip & replace or run the 3750 and 6509 parallel till migration is over,if that is a viable option.Most of the existing configs will be copied to 6509.
Existing WS-C3750X-48 stacked core switch to be migrated to 6509-V-E with 2x WS-X6848-TX-2T and WS-X6816-10G-2T.
Various 2960’S and 3850 are trunked to the existing 3750X-48.
1)Existing 3750 has pvst and new 6509 has rapid-pvst.Will it be ok to use rapid-pvst.Will there be any issues with the existing switches on the network.We don’t have access to other access switches and assume they running pvst.
2)Existing 3750 is configured as VTP Primary Server.How do we configure the 6509 VTP, so that existing VLAN’s get transferred to the 6509.There are about 100 SVI/VLAN.Do we need to re-create the SVI’s on 6509.
3)Concerned if we connect the 6509 to existing environment the revision numbers may change and we lose the vlan database on entire network.
ASKER
Thanks Jovic.
After seeing your response,surely will do a rip/replace as IP/SVI will be re-used.Will re-create all SVI's on 6k.
Should we connect the 6k as a trunk to 3750 as VTP client or transparent.At least the VLAN's will be transferred to 6k that way.
Once we take 3750 offline and plug the trunks from other access/distribution switches to 6509,should it all work fine.Meaning as we don't have access to other switches,will make 6k pvst.
Do you think it is mandatory to access all other switches and see the vtp status and stp on them.
After seeing your response,surely will do a rip/replace as IP/SVI will be re-used.Will re-create all SVI's on 6k.
Should we connect the 6k as a trunk to 3750 as VTP client or transparent.At least the VLAN's will be transferred to 6k that way.
Once we take 3750 offline and plug the trunks from other access/distribution switches to 6509,should it all work fine.Meaning as we don't have access to other switches,will make 6k pvst.
Do you think it is mandatory to access all other switches and see the vtp status and stp on them.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks alot Mate.What is (be careful to assign proper Root bridge priority).I want my 6k to be the root bridge for all VLAN's/entire network.
How should I configure this please.
How should I configure this please.
Switch that suppose to be primary root bridge
spanning-tree vlan 1-4094 priority 4096
Switch that suppose to be secondary root bridge
spanning-tree vlan 1-4094 priority 8192
or any other values that you find convenient typically in is multiplier of number 4096 :)
You can find Best practices for Catalyst 6500 in Cisco article, but be careful what you will implement ... since it need to match to configurations on old devices....
Good luck.
spanning-tree vlan 1-4094 priority 4096
Switch that suppose to be secondary root bridge
spanning-tree vlan 1-4094 priority 8192
or any other values that you find convenient typically in is multiplier of number 4096 :)
You can find Best practices for Catalyst 6500 in Cisco article, but be careful what you will implement ... since it need to match to configurations on old devices....
Good luck.
ASKER
Thanks Mate,
Because I have only 1x 6k Core switch on the network ,I assume that I only have to do:
spanning-tree vlan 1-4094 priority 4096
Because I have only 1x 6k Core switch on the network ,I assume that I only have to do:
spanning-tree vlan 1-4094 priority 4096
ASKER
I have noticed that a Blade Server Chassis switch is trunked to 3750.It is in VTP client Mode.Revision number on the Blade Chassis Switch is same as Core Switch.Also noticed that the root bridge for some VLAN’s is the Blade Chassis Switch and for some VLAN’s is the 3750 Core Switch.So it seems I don’t make the 6k root bridge for my network.What do you suggest?
That depends on network design, but I am not familiar with design of that network.
My guess is that blade switch is second core device and being root bridge for some VLANs is done for load balancing of traffic.
If you are not familiar with design of that network - copy 1 to 1 as much as you can.
Example:
If VTP client mode is configured, configure VTP client mode on new device.
If 3750 is root bridge for VLANs 1, 2, 5 and HSRP active instances are on that device for the same VLANs - make the same on new device.
Maybe design should be improved, but that depends on your knowledge of current design, your ability to change current design and ... are you paid to redesign that network or you are paid to replace device. Also if you need to do network redesign I guess you would need to have access to other network devices there.
My guess is that blade switch is second core device and being root bridge for some VLANs is done for load balancing of traffic.
If you are not familiar with design of that network - copy 1 to 1 as much as you can.
Example:
If VTP client mode is configured, configure VTP client mode on new device.
If 3750 is root bridge for VLANs 1, 2, 5 and HSRP active instances are on that device for the same VLANs - make the same on new device.
Maybe design should be improved, but that depends on your knowledge of current design, your ability to change current design and ... are you paid to redesign that network or you are paid to replace device. Also if you need to do network redesign I guess you would need to have access to other network devices there.
1) it's OK, configure all devices to use Rapid-PVST. Rapid-PVST is backward compatible with PVST, but suggest there to use rapid on all devices that support it for faster convergence.
2 ) You can connect 6k switches to one of current VTP servers and 6k switches to learn vlans including revision number. Than promote 6k to be VTP server.
This is design dependent, but if 6k are replacing those 3750s most likely you do.
3) described in 2), however you can also create different VTP domain on 6k and make it VTP primary server, create all VLANs and then change VTP domain on all downstream switches. During VTP domain change on old devices revision on old devices will be changed to 0 (but have in mind that vlan.dat can get corrupted and you may need to delete it from flash to be able to have valid vlan database).... But if you don't have access to those switches as suggested in 1) - use approach 2).