Cisco WAN :: VS Based 720 Supervisor As Minimum To Support Full BGP On Catalyst 6509-E
Nov 18, 2011
I'm currently in the process of evaluating potential equipment options for a Core Router/Switch that will be running BGP with several Tier 1 ISP's, the table download from each ISP will be full (300,000+ Routes). I was looking at a 6509-E with dual SUP720-3BXL supervisors but after reading the below link I'm a little concerned by the maximum routes table: [URL]
Do I have to go to the VS based 720 supervisor as a minimum to support full BGP on a 6509-E? Does any experience of the above switch + supervisor combination under a full BGP table, how well does it work? I'm looking at long term using this as a consolidated core (i.e. a VRF for the Global Internet routing table + a VRF for internal data center traffic, plus maybe some more shared VRF's).
Would I be better keeping a Core switch by itself and just buying edge routers to run BGP?
we have Supervisor Engine 720 10GE (VS-S720-10G) in slot 5 on Catalyst 6509-E. Slot 6 is free. We need to replace VS-S720-10G. Is it possible the following scenario
1. we will insert new VS-S720-10G into the slot 6 2. then we will remove the faulty VS-S720-10G from the slot 5
Will everything work without interuptions. Is any document where I can find step-by-step procedure how to replace VS-S720-10G ?
We have 2 catalyst 3560g-48-PoE protected by a 1000Va 800Watt tripp-lite and I was cheking to see if that is really sufficient. Looking at the charts from Cisco suppport I would think I should have more, but have not had any issues with a few power outages
I am looking to install 2 1552I outdoor AP's. I can't find what the minimum code version is on the WISM controller that supports this AP.I am running 7.0.98.0 on the WISM. Where can I find this information?
We have a 6509-e (WS-C6509-E V04) with (4) (WS-X6148-GE-TX) 48 port modules and a supervisor 32 (WS-SUP32-GE-3B).We purchased a supervisor 720 (WS-SUP720-3B) and (2) (WS-6708-10G-3C) 8 port fiber modules and (1) WS-X6748-GE-TX)48 port module to add to the switch. My question is what is the best way to swap out the supervisor module? Can the SUP720 be added as a standby module so that the config can be transferred? Probably a long shot. Is there anything in this swap that I should be concerned with? The other three modules should be pretty straight forward.
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
A small compatibility question regarding 6500 series:
The document: [URL]
, but Dynamic Configuration Tool sais that:
"Two or more selected items are incompatible. Selected or default-included item [WS-SVC-FWM-1-K9] is incompatible with: [VS-S2T-10G]. Please change one or more items."
I am looking at getting a Cisco 4003 and get a Supervisor that can support IOS. Something like this url...I can't figure out if the the 4003 can take an IOS supported Supervisor engine. The Cisco documentation is lacking since it is EOL.
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 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?
I have a strange issue with 4500 E chassis loaded with SUP 7L-E which always remains in ORANGE LED status, also the uplink ports interface is down and the line protocol is down but when i execute the command sh int gig1/5 it show me the media type sfp but there is no red laser light seen in the sfp transiever,The below command is configured for the uplink gig port on the SUP engine.hw-module uplink select gigabitethernet?
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]
Problem I have encountered when upgrading a Cisco 6509 chassis with a new supervisor card from Sup2 to Sup 720b. The 6509 loads and then crashes completely, and when rebooted reloads into rommon.The same upgrade was performed on a similar switch with no apparent problems.
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.
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?
Does a new Cisco Catalyst 4500 series supervisor 7L-E model WS-X45-SUP7L-E is backward compatible with a Cisco Catalyst 4500 series chassis model 4507R? I've checked on Cisco website for that Supervisor and it shows only new chassis models WS-C4507R+E and R-E, but what about old type of chassis? We need to upgrade that Supervisor as it's out of line, but we don't really want to buy a new chassis as well as it's going to be very pricy.
I have two Catalyst 3560 series switches with a 100Mb Ethernet microwave link and a 250Mb Ethernet microwave link between them. Can the switches be set up to make full use of the added bandwidth (350 Mb).
switch catalyst 4500 with ios cat4500e-universal.SPA.03.02.00.XO.150-2.XO.bin. I need to configure modules 3 and 4 of supervision, the problem is that I need the 4-port module 3 are active but only the first turn on both the module 3 and the first port on the module 4. [code]
I have two Catalyst 6506 in VSS mode with VS-S720-10G running 12.2(33)SXI1 IP SERVICES.I have two firewalls that communicate on to the other through a dedicated VLAN created on Catalyst 6506.
One firewall is able to ping the other one on this dedicated VLAN but if I send multicast traffic from firewall-1 I didn't receive it on firewall-2.I found a bug related to multicast issues on Cisco WS-C6509-E with VS-S720-10G. The bug ID is CSCtc59038.
My Company use Core Sw 4507R-Sup 7L-E with Enterprise Services License. I has upgraded to use iOS cat4500e-universal.SPA.03.03.01.SG.151-1.SG1.bin
When I use match protocol in class-map, there are only about 10 protocols, and not have those ones I need. I intend to expand the list of protocols to do some Policy-map by loading PDLM. But 4507 is no longer support NBAR. So do we have another way to set Catalyst 4507R with Sup 7L-E recongnize more protocols in match protocol command?
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;