Cisco Switching/Routing :: Supervisor 7-E / 7L-E Port Numbering
Jan 30, 2013
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 ?
Concerning the WS-X4640-CSFP-E module, I was surprised to realize when I got it that the ports are numbered 1-80 rather than 1-40. Then I saw it is actually an 80 port blade when you use half-SFP's. But we have full SFP's, so how does it do the numbering? If I use all full-SFP modules, do the even-numbered ports just go unconfigured?
Assume I had Catalyst 3560X/3750X with 24 ports. The partnumber is WS-C3560X-24P-LI would like to how is the numbering defined if the switches have a C3KX-NM-10G installed with 4 SFP-GE-L.
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?
I was wondering if a interface numbering scheme is available for the 4900M. Configuration includes 1 x 8Port 10G and 1 x 20Port 1G modules. would like to understand How the slots are addressedInterface AddressingTwinGig interface addressing
We are planning for the first installation of 4500 switches containing these supervisor modules. I'm trying to determine the interface numbering convention for ports on the supervisors. Our existing 4500E all have SUP6 modules with twin-gig converters - so I am familiar with the numbering conventions used on those supervisors. How does this change with the software based selection command "hw-module uplink select" used in SUP7?
When configuring QoS on 3750s/3560s, we're mapping packets to particular interface output queues with commands such as: [code] The command to see what's actually being enqueued, dropped, etc. is: [code]
Note that these queues are numbered 0 - 3, and not 1 - 4. We've been assuming that the first queue number in the "mls qos" (i.e., 1) command maps to the first queue (i.e., 0) in the "show mls qos" command.
we've had an issue with our network, we have 2 6509 connected with redundancy, which are connected with 2 x 4900 Switches, from which are connected to a ESX Chassis for visualization, the thing is that the ESX stopped working, and the 4900 switches, and the main core were suffering from overload, they hang on it very well, in order to stop the overload, one of the links to the ESX Chassis were disconnected from one of the 4900 switches. The CPU usage from the 4900 and the core(6509) went down below 40%, and then they started to migrate the virtual servers from the chassis to another 2 chassis that were added right after. They were actually working well, but suddenly the 6509 changed to the other supervisor after everything was OK. We were wondering what could have been the cause of this, maybe the virtual servers migrations, maybe the overload from the ESX ? We also had a few question, is there any need to reload the cores every few months as a planned task ? Because the cores have been up for more than 1 year. And also is there any kind of of tool to monitor the CPU status, or the status overall from the cores or the switches ?
i have a standalone SUP720, no traffic is passing through it. only one port connected for remote telnet, its kind of backup device.today i checked its log, and there are some wiered message.is it a software bug or my SUP has gone bad? [code]
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 have a 4510R-E chassis which currently has a single supervisor 5 installed.
We are now looking at upgrading the supervisor to a Sup6. Now the question is this, can I install the Sup6 into the redundant cpu slot and then perform a failover to get the new switch working without any noticable downtime.
I'm not sure what having a Sup V and a Sup 6 in at the same time will do to the backplane.
Otherwise I have to take the switch down and then install the card and software manually.
We have a scenario with 2 chassis, both with 2 supervisor Engine 2T, we try to make a configuration of VSS with the chassis and would link to know if is possible have 2 supervisor on chassis one and 2 supervisors on chassis 2 with VSS?
Router#sho switch virtual redundancy My Switch Id = 1 Peer Switch Id = 2 Last switchover reason = active unit removed Configured Redundancy Mode = sso Operating Redundancy Mode = sso
[code]....
would like to use the second supervisors for obteind the local redundancy en chassis 1 and 2, this is possible?
the actually version on four supervisors is: s2t54-ipservicesk9-mz.SPA.150-1.SY3.bin
I'm having a trouble with a 4510R+E switch. The WS-X45-SUP7-E supervisors are constantly rebooting, and we can see a 'critical software exception reload' reason. We have checked the logs
______ uptime is 5 weeks, 1 day, 19 hours, 3 minutes Uptime for this control processor is 37 minutes System returned to ROM by reload
[Code]....
What can we do to solve this incident?. Everything was working fine, and suddently the problem arose.
I am trying to understand the implicit limit to the priority queue. I know you can define an explicit policer but if you don't I can't find out what the rate limit really is.
I'm working on deploying a new 4510R+E for our organization. This is my first experience with a modular switch. I'm trying to enable SSO, however in the redundancy configuration mode, the sso command is not available. Is SSO only available with certain software images / licensing levels? [code]
We are trying to upgrade the IOS on one of our 6509 switches. We have two 720 10GE supervisors running in SSO. Our procedure is reload the standby supervisor with the new IOS. We understand that you can only use one console connection when in RPR mode so we rely on the active supervisor giving us information that the standby unit is up and running.
The problem we have is that when we do a "show Module" on the switch the online diagnostics for the standby supervisor comes back us unknown. [code] We believe the active supervisor can see the standby supervisor because when we save the configuration we get a message saying that the config is sync'd with the standby router. We have a TAC case raised to investigate. We are upgrading from 12.2(33) SXI1 to 12.2(33) SXJ3
I have a Sup32 that I suspect has faulty NVRAM (e.g., I am unable to "wr mem" on the device - it states resource is busy but no other active connections exist). Prior to replacing the supervisor engine I'd like to take a crack at formatting NVRAM to see if it resolves the issue. This supervisor does not have a CF card installed, thus no Disk0:. Within the CLI, I am presented two options with the "format" command - bootflash: and sup-bootflash:. Bootflash: does not have any data on it, however, sup-bootflash: contains my IOS image. I believe that both of these locations are simply directories within NVRAM.
I have configured the VSS in two cisco 6509-E series with only one supervisor engine, but if i configured with two supervisor engine. it is going to common mode. One supervisor engine is 3c and 3cxl.
I have an older 4006 with a Supervisor II+. We now need OSPF support, which the Sup II+ does not provide. I have access to a Supervisor III (WS-X4014), which will provide OSPF support. Question is, are there any gotchas to shutting down the switch, replacing Supervisor Engines and then powering up? What about the flash card? On my current system, it appears that I am only using bootflash: , which is where the IOS resides (see below). Since my startup config is in nvram and my IOS is in bootflash, what's the purpose of the flash card in slot0: ? and where does NVRAM and bootflash actually live on a 4006 ( on the Supervisor Engine?)
sh bootvar BOOT variable = bootflash:cat4500-ipbase-mz.122-31.SGA11.bin,1;,1; CONFIG_FILE variable does not exist BOOTLDR variable does not exist
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 are planning to upgrade the IOS on our two 6509E supervisors in the next few weeks. We currently run IOS 12.2(33) SXI1 and are upgrading to 12.2(33) SXJ3. At the moment the two supervisors are in SSO mode and after reading many articles it says that when the images are different on the two supervisors they are in RPR mode. When you then reload the active supervisor it will reboot all the line cards.
1. Is above correct? Will my line card reload?
2. We also have a FWSM installed, When/If the line cards are rebooted does the FWSM also reboot?
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 "inherited" a Catalyst 4506 with IOS version 12.2(20)EWA1 and Supervisor IV already installed. We recently purchased a second Supervisor IV and I am looking to install this second supervisor for redundancy. Is there anything special with installing a second supervisor or so I just physically install the new supervisor and the IOS will automatically set everything up?
We will install a new Supervisor Engine in our Nexus 7010.One Supervisor Engine is already installed an 1Year old.So the Problem is that both Supervisor Engines may have different NX-OS version.Could this lead to a problem?Does the installed Supervisor Engine "udate" the newer Supervisor engine?
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?
We recently wanted to swap our existing WS-SUP720-base with a WS-SUP720-3B in a 6513 chassis.Had the existing configuration config saved in a txt file and replaced the supervisor. Booting went fine and we pasted in the original config. There was one failure message about unnsupported command but didnt take further notice."boot system flash sup-bootflash:" was probaly the line that the 720-3B didnt support.After wr mem and reload it went in continious loop and rebooting due to inncorrect boot device. Had to put back the old supervisor and have now the 720-3B in a 6504 chassis. Tried some commands in rommon, but are not getting any further.