Cisco Switching/Routing :: 6500 Redundant Supervisor Port Channel?
Oct 30, 2011
I have a Cisco 6500 series switch with VS-C6509E-S720-10G ,I have two redundant supervisors between two chassis on the LAN with no add-on line cards ?
I need to know if I can use the redundant supervisor 10 Gb uplinks to form a layer-2 Port channel between the two 6500 switches as i do not want to use want to keep the port idle additionally I need more bandwidth between the two switches for my server farm?
We bought Cisco sup engine WS-SUP32-GE-3B for 6500 switches 2 nos for redundancy. I have connected 6 systems on each sup engine ports. How to clarify whether both sup engine will forward the data while one is Master and other is standby?
I have a pair of 6500's setup with VSS and there is currently only one link between then. However one end of the link is on Po10 and the other end is on Po25. If I move the Po25 over to Po10, will things break? It seems to be working fine now. I'm about to add a second link and I'm concerned about the current configuration. It makes more sense to me to have both ends of the same link on the same port-channel ID. I've seen documentation which states otherwise however.
interface Port-channel10 no switchport no ip address
I have 2 cisco 6500 in a VSS configuration , All of my Lan access switches are Stack switches and every Stack is connected to the VSS in a Port-channel so basically this is a loop free environment with no blocked ports .As a best practice I left STP in the Background (mstp)which enhanced cisco features to STP should I configure on the Aggregator (6500-VSS) and on the Access switches ?
Because of my topology I dont see the need in configuring most features like Uplink Fast and Backbone Fast but I have configured Loop Guard in addition to UDLD on the 6500 Aggregation Switches (on the port-channels).On the access ports I have configured portfast , bpduguard and guard root (seems a little pointless to configure the two...)
1.should I Leave UDLD on and get rid of LoopGuard and configure Guard root instead ? since LoopGuard cannot be configured with Guard Root.
2.should I configure GuardRoot on access ports if I already have BpduGuard on them ?
3.Is there anything I need to configure on the physicall interface or is everything configured on the port-channel since STP reguards port- channel as a single interface ?
I need adding a vlan to the trunks bundled in port channel. I know how to add v lans to a port channel with Cisco IOS but with CAT OS.
I have 2 ports bundled to form ether channel in switch which is running CAT OS. There are already few v lans allowed in the trunk of each interface. now I need to add one more v lan.
For Example:- v lan 135 needs to be added in addition to the existing v lans.
clear trunk1/2 1-112,115,117-134,136-4094 set trunk 1/2 on dot1q 113-114,116,135
and similarly on the 2nd interface
so if I add vlan135 to the trunk one after another will it cause any service disruption?
and i see output "show interface Po4A" up up on switch-1, "show interface Po4B" up up on switch-2
5.- In the show running-config not appear configured Po4A and Po4B. it only show on outputs
6.- Po4A and Po4 was not configured on neither switches, my question is why appear Po4A and Po4B on switch-1 and switch-2 respectively? and why Po4 appear in down down.
7.- I solved this issue by shutdown and not shutdown to the interfaces on both routers, currently all is OK.
Configured Layer 3 portchannel from 6500VSS enabled switch to two different 6500 standalone switch. Configured first ip on VSS switch, second ip on standalone switch1 and third IP on standalone switch2. My question is
1. Will the portchannel be up? 2. If port channel is up, will I able to ping the connected IP's.
I would like to add a redundant supervisor to my core 6509. Is this tricky to do? I know they have to be running the same IOS. I am worried if I put the new supervisor in it will write over the exsisting running config.
we have 2 Supervisor IV modules in our 4507, i want to upgrade the IOS as its still on 12.2 and i am going to upgrade it to the latest.
my first question is, if i update the IOS on the bootflash will it replicate to the secondarybootflash?
secondly, can i force a reboot of the secondary supervisor, then the primary after the secondary is up? i'm just trying to minimise downtime and get a plan going.
is there a difference in 12 vs 15 that would impact my current config that i should be aware of?
There is a Cisco Catalyst 6513 in my office. Recently we decided to setup redundant Supervisor Engine 720-3B. When we did it, its became STANDBY COLD, and then it reloads. IOS is equal on both supervisors. It must be STANDBY HOT (SSO) redundancy. There is a configuration and show ver and show module outputs, and log of my actions.
The SuperVisor engine in slot 1 of a Catalyst 6513 needed to be replaced because a hardware defect. The SuperVisor engine in slot 2 is active and running CatOS 8.5. The new SuperVisor engine for slot 1 came with CatOS 6.3 and was not syncronized auromatically after insertion. When the customer enter the command "Show boot" he get the output:
AG-A6513-51> (enable) sh boot BOOT variable = bootflash:cat6000-sup2k8.8-5-5.bin,1;bootflash:cat6000-sup2k8.7-6-2.bin,1;
I know in the past on earlier models of the supervisors that you couldn't use all eight uplink ports(4 on each supervisor) simultaneously when you have two supervisors on the chassis. Is this the same case for the 10Gb uplinks on the supervisor 7-E on the 4500 chassis? I tried doing my research but couldn't find an answer.
I have a doubt about upgrading Memory in Redundant Supervisor Modules Nexus 7K18, i read the Cisco Nexus 7000 Series Hardware Installation and Reference Guide, and the process for upgrading the memory in redundant supervisors do not says that i can have a lose of service, but it also says that both supervisor modules must have the same amount of memory for redundancy to work;If the switch has two supervisor modules, both must have the same amount of memory. If you upgrade the standby supervisor module to 8 GB of memory, you must then switch the active supervisor to standby and upgrade the new standby supervisor to 8 GB of memory.
We've been mocking up a test lab to test VSS on two 6500's. Each 6500 has one sup720 and a 6708-10ge blade and we've established the two 10ge links between the two chassis; the first from the each chassis' sup and the second from each 6708.My question is, what happens when the supervisor fails on one of the chassis?
I sort of messed up and upgraded the IOS on one supervisor on a 6500 without doing the second, saved and reloaded. How to I get the 2nd one working again? When I issued a show module the "normal" Active sup shows active and the standby shows as Supervisor.
I know that the 6500 with a Sup 720 reserves power for a redundant 720. If there is no plan to install that redundant Sup, is there a means of releasing that reserved power? I know that one approach would be to insert a card into that slot to cut the reserve down, but I need to reclaim all of that power.
1. We now have SupA & SupB in the chassis, due to some mistake we have same IOS version but different feature set on them, although we configured redundancy mode sso, in the "show redundancy" we see Operating Redundancy Mode = rpr due to Software mismat, we now need to fix them as same feature set image, if I use "copy sup-bootdisk0:/xxxx slavesup-bootdisk0:/xxx", then write memory, does this cause any service/network interuption?
Available system uptime = 1 year, 1 week, 4 days, 9 hours, 21 minutes Switchovers system experienced = 2 Standby failures = 0 Last switchover reason = active unit removed
[code]....
2. We did a failover test with this status, found that if we triggered supervisor failover, all modules will reload thus the services if interupped. How about after we make the Operating Redundancy Mode as sso, will this behaviour shows again? Or a stateful failover will happens, then modules no need reload?
3. We are using OSPF as our L3 routing protocol, after reference to the configuration, nsf should be enabled, we want to ask in the OSPF-domain nsf should be configured in all OSPF-enabled router or only 6500 which have dual-sup?
4. We also found that the interfaces(3 * Gig & 2 * TenG) in Standby supervisor cannot be use even enabled & configured, is it because we are running rpr mode now or will be the same even change to sso? Before customer have some older supervisor in 6500 non-e chassis, and they can use the standby supervisor interfaces as traffic forwarding, they use rpr-plus mode before, how about in sso mode?
I have a question. I have a 6500 with two supervosrs and they both have CATOS. One of them failed and I need to replace. As long as the hardware is the same does the CATOS have to be indentical or can this be different.
I have 2 6504's running HSRP as my core. They are each etherchannel'd to my Datacenter switch (3750 Stack) -- see image below.The problem i a having is with the etherchannel status:
Core1 PO11 status w (waiting) Core2 PO11 status P(bundled)
DC11 PO48 status P -- but only to Core2 - the interfaces to Core1 are suspended. (See attached configuration documents) None of the devices have any information in the logs. I run this same configuration in my central location, but we are running Nexus 7000's. With the 6500's, do I need to split the port channels on the 3750 to allow them to negotiate the etherchannel? If I split the portchannels, are there any concerns? Should I expect to see the etherchannel status as P (Bundled) or H (Hot-Standby)?
I'm trying to configure a egress netflow in a 6500 (VSS) with VS-S720-10G supervisor. I foud some old posts and understood that netflow wasn't supported on 6500 but i found a new document and it seems that netflow is supported in Supervisor Engine 2T:[URL] Does the netflow still not supported in VS-S720-10G? It's weird because the command is supported:
#sh run int vlan 4 Building configuration... Current configuration : 353 bytes ! interface Vlan4 ip address X.X.X.X 255.255.0.0
"How to display the EOBC error counters in the Catalyst 6500 series switches and a definition of the EOBC interface" document here on support forum stays that The Ethernet Out of Band Channel (EOBC) is a half duplex channel that services many functions, which include the Simple Network Management Protocol (SNMP) and the packets that are destined for the switch.
Previously i were thinking that EoBC used only for SCP and SLP protocol. In addition i found other article (but not on cisco site, heh) where stays that The Results bus is a control plane, while the C (EoBC) bus is more of an "admin plane", thus you will never see data packets (such as CDP, SNMP, etc.) going over the R or C bus.
So there is a big contradiction between those two statements. How to prove one of those and if first one right, what meaned under the packets that are destined for the switch in it? SCP and SLP or other traffic as well?
How the port numbering would be on Sup 7-E and Sup 7L-E? I mean, on Sup-6E and Sup-6LE, if I used a twin-gig converter, I used ports gi3/3,gi3/4,gi3/5 and Gi3/6 [If the sup is in 3rd Slot]. I know there are now 4 ports on the Sup 7 which can either be used as Gig ports or TenGig ports. So, how will the port numbering change ?
We have one cisco core switch 6500 series which was configured portchannel on several gig interfaces. This port is used as a trunk to enable communication between VLANs. The VLANs is where several high-end servers/hosts reside.After we disable / unbind the portchannel, the port turns amber. The following is what we did on the interface
1-no switchport command
2- make the port as access mode #switchport mode access
3- shut and no shut
4- clear arp
5- clear mac
what else can we do on that particular interface. It is just on that particular interface, the rest are ok.
we have cisco 6500 series switch and configured port channel on both switches with 2 gig interfaces on both switches.
When we enable the port channel mode to as desirable to the interfaces on both side and applied the port channel to physical interfaces switch will go down and if we remove on any one side switch will come up. we have enabled globally the following commands. [code]
On the supervisor card of a cisco 6500 series, according to the following link, [URL] it only has 2 uplink ports on the card. Would I be correct in assuming that I only have those to ports that I can configure IP addresses on?
The cisco that is being devlivere is coming with a 48 port switch and 24 port fibre switch. Could I change any of those ports into a router port and configure IP addresses on those?
The supervisor card is a ws-sup-720-3b the 48 port switch is a ws-x6748-ge-tx the 24 port fibre switch is ws-x6724-sfp
I have 3750 core/distribution switches with routing enabled in two offices connected with copper link and L3 port channel interfaces. NewOffice#2 has moved about 5 miles farther away from office#1 and I have to deploy new core/distribution switch connect it to old core#2 via F.O and move all access switches with it. Old core will stay in old #2 offices as a bridge between office#1 and new office#2 Office#1core<->copper (Ethernet) <->oldoffice#2core<->f.o. <->new office#2core How I should configure port channels ports on oldoffice#2 core to act as bridge between office#1 core/dist and newoffice#2 core/dist without changing anything else (ip, etc) on whole network
I have 2 Cisco 6509 switches linked together via single Fibre as a trunk.I want to change this to a port channel where I will add another 3 fibre ports to the port channel but what order do I do this to minimise any disruption.
1-Configure PortChannel and add the 3 new ports, this will bring up the Port Channel but what effect will this have on traffic currently going over the single Trunk link? Will spanning tree go mad, how will switches react?
2-Convert existing Trunk link to Portchannel then add in new ports to PortChannel, I guess in doing this there will be a small hit on traffic as it changes to a port channel.