Cisco Switching/Routing :: 4500 Chassis - How To Use VSS With 6500
Aug 22, 2012
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?
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.
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.
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?
I encountered a problem migrating configuration from Cisco 4500 with IOS 12.2(53)SG4 to Cisco 6500-VSS with IOS 12.2(33)SXI7.
With 4500, we had 2 servers with JBoss running multicast to build up the cluster. They used 239.X.X.X multicast IP. There was no need to configure "ip igmp snooping vlan XX static XXXX.XXXX.XXXX interface X" neither static arp entry.
When we migrated to 6500 in VSS, we had to do:
mac-address-table static XXXX.XXXX.XXXX vlan XX interface X disable-snooping
With this command, the JBoss cluster worked well. The question is, ¿Is there any difference regarding IGMP in 4500 versus 6500?
can I plug power supply from 4500 to 6500? more specifically we have power supply PWR-C45-1300ACV. And we need to place some power supply to 6500, which has only one active module. So 1300 should be enough for it. But we dont know if they are physically compatible, if it is possible to plug. I didnt find this power supply to be officially?
Currently have a pair of 6509 chassis setup with VSS. Only have the Sup and two line cards in each chassis. Would like to replace with a new pair of 6504E chassis. Is it possible to fail one chassis at a time and migrate to the new 6504E?
I have PAT set up successfully on 6506 chassis - My outside address range is 78.24.112.114 255.255.255.240.Relevant parts of the config below: [code] This works fine but of course is only using the one IP address 78.24.112.114.how I can utilize the other outside addresses available or is this not really necessary? I've browsed through loads of Cisco docs.
why is not possible to put a WS-X4712-SFP+E - module into an R-E chassis?The module has the same connection to backplane as the WS-X4748-UPOE+E and this one works in a R-E chassis.I know the restriction of Cisco that the 4712 is only supported in 4503-E, 4506-E,4507+E and 4510+E, but why?Are there hardware-restrictions, is the backplane different?
Configuring a 4507R classic chassis with redundant Sup 6L-E? TAC told me the Supervisor 6LE was only supported on the 4507R+E or 4507R-E chassis but I have found in Cisco documentation several places that indicate that the Sup 6LE is supported in the classic chassis.
We have a backup sup 720 which has a 2 gigabit ethernet though port channel, to another chassis. Suddenly UDLD detected an error and got into err disable, then this err disable didn't let the interface set to DOWN, and created a switch loop, then our Supervisor reloaded. I'd like to know what could have caused this reload. In my opinion could have a been the switch loop, but also I've been checking from the output interpreter the show tech and might have been a bug, the only one that could match in IOS version 12.2(33)SXH, is this one: url...
We're going to disable err-disable next time I guess and recover the link manually, apart from that what could have made the sup for crash and reload?
Can any share some useful links on how this works and how to configure it? Do you still need to configure FHRP or does configuring redundancy take care of active/standby relationship between the ASR's?
I have an alert from monitoring system about: “ fan for this system is not in the NORMAL state”. In the switch I found that the problem is with fex 3, see below:
Nexus5020# sh env fex 3 fan Fan Fex: 3: ------------------------------------------------------ Fan Model Hw Status ------------------------------------------------------ Chassis N2K-C2148-FAN -- failure PS-1 N2K-PAC-200W -- OK PS-2 N2K-PAC-200W -- OK
Technician said: fans appear to be operational, BUT the only thing that appears abnormal is STAT light is amber (not sure what it means).
Also, if I compare the temperature from module 3 with module 2 (which doesn’t have an alert) is almost the same, this is why I think the fan is working fine, since module 3 is not hotter that module 2.
I have 4x 3110x switches in a Bladecenter H chassis and the stack cables are connected so that they are in a circle (IE, SW1 connects to SW2, SW2 connects to SW3, SW3 to SW4 and SW4 to SW1). Each of the switches physical 10GE port is trunked to a 6509. If I pull a 3110x switch out, does this network connectivity? Theoretically it should not?
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 have multiple 6509 vss switch. and i notice when the standby chassis reboot I didn't get any snmp trap, but I got when the active one reboot. my question is is there any mib out there for detecting and got a trap when standby reboot?
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?
Any have experience on triggered failover on VSS deployment with 1 VS-720-10G-3C in each chassis? I tried using "redundancy force-switchover" but after that the 20G VSL is flapping up & down and cannot be up normally, we got 1 FWSM in each chassis, any configuration need to fit in this kind deployment? BTW, if I shutdown the power source of VSS active chassis, both FWSM & VSS can failover normally.
I'm seeing several error messages like these in the logs of my Nexus 5548UP switches.
2012 Apr 24 16:39:41.470 SSV_5K_SW2 %LLDP-5-SERVER_ADDED: Server with Chassis ID aaaa.bbbb.cccc Port ID mgmt0 management address X.X.X.X discovered on local port mgmt0 in vlan 0 with enabled capability Bridge
2012 May 2 05:05:00.627 COR_CCO-NX-5548-UP_01 %LLDP-5-SERVER_REMOVED: Server with Chassis ID aaaa.bbbb.cccd Port ID aaaa.bbbb.cccc on local port Eth1/1 has been removed
2012 May 2 05:06:40.328 COR_CCO-NX-5548-UP_01 %LLDP-5-SERVER_ADDED: Server with Chassis ID aaaa.bbbb.cccd Port ID aaaa/bbbb.cccc management address NIL discovered on local port Eth1/1 in vlan 0 with enabled capability None
I will say that these 5548s are serving as the distribution layer for a UCS chassis (2x 6120 FIs) but didn't know what kind of visibility the Nexus would have into that - the chassis keyword is what's alluding to this in my mind, and I'm seeing these messages whenever interfaces that connect downstream to the fabric interconnects are brought up or down.
We currently have a WS-C6506 chassis with a line-card WS-X6408A-GBIC. Currently we need to replace the chassis by a Ws-6504-E and also the line-card. My question is: What must buy line-card and meets the same specifications of WS-X6408A-GBIC?.
Currently I have a Cat4506 chassis with a Sup II+ engine and one WS-X4232-RJ-XX linecard with the WS-U4504-FX-MT daughtercard to provide uplinks to four Cat2955 switches. I chose the Cat2955 because the switches are in an industrial facility and they fit the envrionment very well. Each of them has a multimode fiber uplink.
The issue I have now is that I need to add at least 4 more Cat2955 switches to the topology and find that the x4232 is EOL. I can always find a used one somewhere, but is there another currently shipping linecard that will do the trick? I see there is WS-X4248-FE-SFP with the 100BaseX interfaces, but don't really need 48 ports, just 8.
Is there another linecard that can downswitch a 1000BASE-X port to 100Base-X, or can I use a 100Base-X SPF in a switch like the WS-X4448-GB-SFP?
What are my options, aside from buying another X4232?
We are looking forward to install a Cisco 6513 with IDSM-2 in each chassis in a VSS mode. Any experience with the configuration of the 6513 ? Also, lets assume I installed one active IDSM in each chassis with identical configuration... what happens when one of them fails ?
I have a 3750-48P when plugged in has fans that spin up, but no lights on the front of the chassis. Does this mean the power supply is bad? If its bad, why do the fans power up? Also, i am not receiving any data through the console.
