Cisco Switching/Routing :: 6500 - Upgrade From SUP720 To SUP2T With New Chassis?
Apr 28, 2013
We recently purchased 2 Cisco 6500 series switches (with Sup 2T). These switches will be replacing our old 2 6500 series switches (with Sup 720).
We have 70 vlans and 90+ closet switches (2900) connecting the core switches We have 2 WLC connected to the core switch. We also have a 1 x 1 connection to a VSS switch which in turn connects to our Server Co-Location data center utilizing IPSec & GRE tunnel to connect to our Server Co-Location data center.
Our routing protocol is EIGRP. Our VTP domain at Server Co-Location is separate from our location “A” campus. I was wondering what is the best way to migrate our Core switches at location “A” campus.
The requirement is we would like to replace these switches with minimum downtime.
We've just invested in a pair of Sup2Ts to upgrade a Sup720 6509 chassis but I'm unsure exactly how the management port(s), aka the Connectivity Management Processor (CMP), should be configured (and patched) in a dual supervisor system?Is each CMP an independent entity or is the management interface configuration (IP address, gateway, etc) replicated between supervisors?If it's the latter then do both management ports need to be physically connected at the same time?
I support an active VSS cluster using 2 x 6509E chassis with single Supervisor 3C modules in each chassis. I want to replace these with Supervisor 2T modules. All my service modules and line cards are supported with the Sup2Ts (I will also be implementing 6908 modules). Is there a document on the Cisco site for this? I haven't found one though I can find plenty that describe how to do a software upgrade.
(Note, I have a 3rd (non VSS) 6509E chassis that is also part of this core network and that will maintain VTP/V LAN's etc).
I am trying to upgrade Sup2T from 15.0 to 15.1 (same feature sets). I have the new image in bootflash and have changed the boot system statement to boot from the new image and the config register is 0x2102. However, everytime it reboots it loads the old image. [code]
I have a heck of a time finding this kind of information on the cisco site...Is the WS-SUP720-BASE line card a fully supported module in the 6509-E chassis?
Cisco 6500 with 2T supervisor engine with following software Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.0(1)SY1, RELEASE SOFTWARE (fc4)
The problem is that, I am not able to configure Multilayer Switching (MLS) (mls rp ip) in the global config command. Although the "mls" is visible on the config menu. but when I say "mls ?", the router prompt "unrecognize command"
Not sure if SUP 2T support MLS or it come with different name.
I am migrating services from SUP720-3B to VS-SUP2T-10G= and moving to a VSS configuration between a pair of Cat6506 distribution layer switches. I need to enable QoS on these switches, primarily to trust dscp and also to prioritise voice traffic. The autoqos feature works for some ports but does not work on port-channel interfaces and port-channel member interfaces. How can I apply the qos settings for these interfaces in line with what auto qos would normally provide. My line cards are as follows:
Civic_6506VSS#sho mod Mod Ports Card Type Model Serial No. --- ----- -------------------------------------- ------------------ ----------- 1 4 CEF720 4 port 10-Gigabit Ethernet WS-X6704-10GE
I have problem with the standby supervisor in 6500 vss and need to replace the supervisor. I have follow how-to on the cisco web site url...
But when i boot the new standby sup720 it comes active and both supervisors is rebooting. I wonder if i can do the replacement without rebooting both active and standy supervisor.
We are preparing to install a new switching Infrastructure at one of our sites. We have decided that we want to have two separate chassis as a core. My original idea was to purchase 2 - 4500 chassis and install 10Gb and 1GB line cards in each and use STP and HSRP to load balance between the two cores.
We had also contacted a vendor for thier recommendations and they came back with 2 6500 Chassis running VSS. I reviewed what VSS was as I had never heard of it and it looks to me basically to be real close to the same thing as Stacking. I didn't really want to have stacked Cores because I would like to have the flexibility to be able to take one core out and update the software or image, reboot, and such without effecting anything on the network. I can do that with the non-VSS approach but it looks like that would be more of a problem with VSS.
My question is, how to use VSS with the 6500's? How to take one of the VSS pairs off line and not effect normal network operations?
if it is possible to recover a Cat 6500 that has no code on bootflash from ROMMON, and is it mandatory to have a compact flash card to do the recovery ? or can one use xmodem or TFTP ?
I will be installing a secondary SUP720 in a 6509-E and will be upgrading the IOS on the existing SUP which is on 122-18.SXF6. I've read that this release has passed End of Critical Maintenance earlier this you. I thinking of upgrading the IOS to 12.2.33-SXJ1(ED) or 12.2.33-SXI8(ED) (possible more stable), but i'm not sure if i need any step upgrades from the current version. The SUP meets the required hardware specs and I will also be upgrading the ROMMON to 12.2(17r)SX7 first.
I have alot of experience upgrading IOS on routers and switches, but i just need to now if there are any gotchas that i need to know for the upgrade on the SUP.
The other issue is i don't believe the current IOS has been installed, are there any issue running on an IOS not installed. Patching is not available since the system is not running from an installed image. To install please use the "install file" command.
I have 2x v10000 Websense Security Gateways that are connected to 2x 6500 SUP720. When I turn on cluster management function between Websense appliance, they speak to each other only if they are connected in the same 6500. When they are connected one in every 6500 cluster management does not work. They are connected on the same physical vlan. Do I need multicast to be configured in the 6500 switches?
migration of an existing Sup720 configuration to a new Sup2T. At present we have a Sup2T chassis in the lab running 15.0(1)SY1 and a production Sup720 chassis running 12.2(33)SXI5.I've taken a copy of the production startup-config, renamed it to 'startup-config-BGFL_6509_MBAS-020712' and copied it to the bootdisk (and slave bootdisk) of the new Sup2Ts.I've then added the command 'boot config bootdisk:startup-config-BGFL_6509_MBAS-020712' in an attempt to boot from that config and have the Sup2T migrate it to the new config standards (particularly from a QoS perspective as mentioned here :[URL]
I came across this Multichassis EtherChannel Features when read about information from Cisco Smart Business Architecture.After checking further, knowing that Cataly stwitch 6500 supports this feature.provide information that beside Catalyst 6500, is there any other model of Catalyst switch can support this feature?
we have some pairs of 6509-VSS, which partially have old (no more officially supported) 6509-Chassis.All linecards in the VSS are the same (Sup 720-10GE-3C, 67XX).
We now bought some new 6509-E-Chassis and want to change the old chassis by the new ones in a ISSU manner, that means:
1. putting the partner, which chassis changes, in redundancy mode, switch it off, exchange chassis (old "Catalyst 6509", new "Catalyst 6509-E")
2. inserting the line-cards exactly in the same slots and connecting all cables
3. switch on the new chassis, witing to come up in VSS
I'm not sure of having to set the switch number for VSS (is that in the Sup?; configuration? or part of the chassis-memory?)
I've looked up cisco for some hints, but don't found anything.
I currently have a couple of 6509 chassis (router/switches) with the following hardware blades:
x3 48 ports x1 NAM x2 Sup720 Running 12.2(18)SXF3
I am keeping the four Sup720 modules and have purchased new versions of the others blades including two new 6509-E chassis?Can I take my stand-by Sup720 out of the production machine and insert it into the new chassis?
I currently have a couple of 6509 chassis (router/switches) with the following hardware blades:
x3 48 ports x1 NAM x2 Sup720
Running 12.2(18)SXF3.I am keeping the four Sup720 modules and have purchased new versions of the others blades including two new 6509-E chassis. Can I take my stand-by Sup720 out of the production machine and insert it into the new chassis?
we have a customer who needs to perform upgrade on their Core 6500 Switch IOS from version 12.2(17d)SXB11a to 15.1SY.Is this a supported upgrade path and can it be done directly?
Today we have 2 VSS, and are about to buy another two 6500 chassies to bulid a new VSS. Our currens chassies have supervisor 720, and the new one will probably have SUP2T
We have a network design that allowes us to run on a single chassie per VSS if we have hardware failure. This means that in a really worst case scenario we need to move around hardware to have 3 system up and running (that would mean multiple failures on all systems... so really really worst case scenario )
So here is my first question. Can I run a VSS with different supervisors in the chassies? Second question: If I want to upgrade a VSS from SUP720 to SUP2T, cna I run 2 supervisors per chassie (quad supervisor VSS) where one supervisor is SUP720 and one is SUP2T?
Doing a bug scrub on our dual core, dual Sup 720 6500s tonight. We are going from s72033-advipservicesk9_wan-mz.122-33.SXI4a.bin to SXI9. I want to get a second set of eyes on my script since I have not done this for about 1 1/2 years. Following this doc:[URL]
My task is to upgrade a couple of 6500 series switches, 6513 with SUP720/MSFC3 (WS-SUP720) and Policy Feature Card 3 (WS-F6K-PFC3B) installed. How to upgrade those switches if in SSO redundancy mode with two SUPs installed?
I understand that it is good to connect to the MSFC3 via console and upgrade this first, is this correct?
I also have to upgrade some 6509 but I only can test it on one 6509-E, how to get everything up to date. [code]
Have a new 6509-E router with 2 sup2T blades. However it came with IPbase and we need to put Ipservices on it. I have copied ipservices IOS to bootdisk and slavebootdisk.
However I cannot get get to the boot command to point to bootdisk. It only allows me to point to flash:
)#boot system flash ? WORD System image filename <cr>
Yet I don't seem to have an option to copy this new IOS to flash. How do I get to copy it to flash:
Here is the original show boot command:
sh boot BOOT variable = bootflash:s2t54-ipbasek9_npe-mz.SPA.150-1.SY1.bin,1; CONFIG_FILE variable =
I have a 6509 witch a sup vs-Sup2T, and I´m very confuse for to configure QoS. is diferent in the old supervisor..What is the command similar to map cos to DSCP.. look
This is a configuration in a sw 4507
qos map dscp 56 to tx-queue 1 qos map cos 1 to dscp 10 qos map cos 2 to dscp 18 qos map cos 3 to dscp 26 qos map cos 4 to dscp 34 qos map cos 5 to dscp 46 qos
In 6509 with sup2T and version 15.0.SY2 Im no sure.. I see two command
Are there any best practices for preventative maintenance on Catalyst Chassis switches. Looking to build a PMI schedule for a customer. Or is there evidence not to perform it at all. Things like re-seating line cards, cleaning fan exhausts, etc.
Is there any challenge to upgrade core switch 6500 series from Nexus 7009 which runs NxOS, because i have 3750X series switches connected at distribution and access layer in my network topology??
Is there any challenge if we place NxOS in core and IOS in distribution and Access layer??? how we are able to match sh run config in existing 6500 switch to Nexus 7009 NXOS?
We are planning to implement the 6509-E with two Sup 2Ts and a few 48 ports switches. We also want to make this the router for our network and replace the 7206VRX.
