I have 2 6509 switches configured with VSS.As per advised my managment I have to enable SSH but it is not available existing IOS which is "s72033-ipbase-z.122-33.SXI3.bin". SSH available in "s72033-ipbasek9-mz.122-33.SXI10".
upgrade the IOS with VSS configured switches.
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?
If I have two stackable switches were only one stackable switch has two uplinks one uplink goes to one core 6509 switch and the other uplink goes to the other 6509 core switch can a Layer 3 etherchannel be used if each uplink go to a different core switch, by the way hsrp is running between both switches and also can you give an example how data will be routed from the stackable switch through the ethernetchannel to one of the core switch accross the WAN to another core switch?
View 1 Replies View RelatedTonight we were performing an IOS upgrade on our 6509 VSS to 122-33.SXI6. Both 6509's have dual Supervisor cards installed. Initially we had problems with switch 2 slot 5 supervisor returning to rommon however switch 2 slot 6 supervisor loaded correctly. After manually setting the boot var in rommon, switch 2 slot 5 supervisor reloaded correctly.
After all supervisor's were online we noticed when looking at " show switch virtual redundancy" that sw 1 & 2 slot 6 supervisors were running the correct IOS version but sw 1 & 2 slot 5 were running different IOS versions, however when looking at the show version we are running on the upgraded IOS??? See output below...
Why the active supervisor has loaded the incorrect IOS the VSS is running on the upgraded IOS? I have verified the IOS was copied correctly to each supervisor bootdisk, I see no issues.
My Switch Id = 1 Peer Switch Id = 2 Last switchover reason = none Configured Redundancy Mode = sso Operating Redundancy Mode = sso
Switch 1 Slot 5 Processor Information :----------------------------------------------- Current Software state = ACTIVE Uptime in current state = 3 hours, 38 minutes Image Version = Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(33)SXI9, RELEASE SOFTWARE (fc2)Technical Support:
[code].....
Will I be OK doing a eFSU Upgrade from s72033-ipservicesk9_wan-mz.122-33.SXI2a to s72033-ipservicesk9_wan-mz.122-33.SXJ1?
I only have a single supervisor in each chassis.
Should I be ok with just following the eFSU upgrade instructions in the below?
[URL]
I am going to upgrade the IOS image on 6509-E SUP 2T from 15.1 to s2t54-adventerprisek9-mz.SPA.150-1.SY3.bin switch and i would like to know whether i would need to upgrade the boot loader image as well.
View 4 Replies View RelatedI have a 6509 switch with SSO Redundancy (STANDBY HOT) with IOS ver 12.2(17d)SXB11, RELEASE SOFTWARE (fc1) (c6k222-jk9sv-mz.122-17d.SXB11.bin). I need to upgrade the IOS on this switch.I have 512MB Memory on the switch and 40144896 bytes free on Disk0.which IOS is the latest version to upgrade and also give me some hints for IOS upgrade on this switch?
View 7 Replies View RelatedI would like to find out how to upgrade SUP engine 32 via USB port as I've never did IOS upgrade on a SUP engine via USB before
View 5 Replies View RelatedWe 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 am planning on upgrading my 6509s to use VSS within the next few weeks. I have checked all of the hardware and software prerequisites, and we are good to go from that perspective.I do have more of a procedural question- my switches are already configured and in production, VLANs, HSRP (3 IP addresses per VLAN- 1 per switch plus virtual IP), etc. Does the VSS upgrade take all of this into account and rewrite the configuration correctly, or should I plan on redoing the entire config for the switches after the upgrade?
View 6 Replies View RelatedWe 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 am going to upgarde SUP2 to SUP32 on my 6509 by next week. right now I have 2 SUPs on the 6509 in redundant mode.
View 5 Replies View Relatedwe 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 ROM MON version 12.2(17r)S2 and I am trying to determine if I need to chnage this to 12.2(17r)SX7. It does not appear I need to with the upgrade to 12.2(33)SXI10. Is this correct?
View 1 Replies View RelatedI need to upgrade 2xsup2 module to 2xsup32 on my cisco 6509. I just found out that I can not have the CISCO WS-X6500-SFM(Cisco Switch Fabric Module switch) with Sup32 and I have to remove 2 xCISCO WS-X6500-SFM2 modules from the switch.I am using this switch as a access switch and most of the ports are 100Mbps.
let me know if the upgrade would be safe or not as far as the bandwidth?
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 have 2 6509 chasis with one SUP720-3B in each and current IOS is s72033-ipservicesk9_wan-mz.122-18.SXF4 and 2 FWSM with version is 3.3.1 I need to upgrade FWSM system software to 4.1, after checking FWSM 4.1 release notes, I thought of upgrading IOS to latest version to 12.2(33)SXJ.I got new 2 CF of 512MB and downloaded the new IOS on them and need to upgrade 6509 IOS first to meet the requirement for FWSM upgrade.
View 1 Replies View RelatedI am planning to upgrade the current core switch(3750) to 6509 series switch. Since we have a production network running we have to plan for an online core switch upgrade.
View 7 Replies View RelatedI've upgraded a 6509 switches wich are running in VSS, from IOS 12.2 (33)SHI1 to 12.2 (33)SHI5. After that I'm facing the folowing log messages periodically. [code] I know that this is a diagnostic result from TestUnusedPortLoopback feature. But this interface is disabled (shutdown).
View 5 Replies View RelatedI want to setup HSRP between three 6509 switches with a single virtual ip for all the three switches.
know if its possible and share any site or config.
I have 1x Cisco 6509 with Sup2 and MSFC2 and it is running on IOS (c6k222-jk9sv-mz.122-17d.SXB11). I have following policy map :
Policy Map VOIP
Class IP PHONE
priority percent 75
and the following command on each interface: service-policy output VOIP those configuration are working fine on SUP2 with MSFC2 but last week I tried to upgrade the SUP2 to SUP32 on the switch and upgrade the IOS to the latest version (s3223-adventerprisek9-mz.122-33.SXJ4) but when I try to put service-policy output VOIP on each physical interface I am getting the following error:
"Priority command is not supported in output direction for this interface" and when I try to add service-policy output VOIP on a V LAN interface I am getting following error:
MQC features are not supported in output direction for this interface. Will I need to change something after upgrading to SUP32..
we are using cisco 6509 series switches as core switches. and Cisco 4510,4507 series switches as edge switches. all the vlans are created at core switches and propogating to edge switches through VTP. we are using OSPF as routing protocol at core switch for internal routing. till now we are using 4510,4507 switches as layer 2 switches. Since, 4510 & 4507 switches are hign end swithces i want use them as layer 3 switches instead of layer 2.if i change these switches from layer 2 to layer 3 does it make any impact on our network or better to keep them as layer 2 switches.if i change these switches to layer 3 is there any advantage i will have.
View 3 Replies View RelatedOn our backbone (Cisco 6509) we have the following config.
spanning-tree mode rapid-pvst
spanning-tree extend system-id
spanning-tree vlan 1-200 priority 24576
1. is rapid-pvst the best spanning tree protocol to use? on some switches we have pvst (not rapid)
2. do all switches in the LAN need to use the same protocol?
3. does line 3 :priority 24576 mean that someone set tis switch as root manually? how can one further enforce the backbone as root (so noone adds a old switch with lower root id)
In the next couple weekends I'm planning to add 2 CISCO UCS 6248UP Interconnects to 6509 Core Switches via 10G links.
Is there any impact anticipated? It's a production environment and no loss of up-time is acceptable.
I am trying to understand what load balancing method is used on a port channel on a Nexus switch . I have a server connected by a VPC to two Nexus switches. The nexus switches are only acting as layer 2 switches. I have a 6509 connected via a upstream link that does all of the routing for my VLANS. If have a server connected to the Nexus switches and it talks to a server on my 6509 what load balancing happens on the Nexus going across VPC 27 which is a layer 2 trunk going up to my 6509. Is it done on layer 2 or layer 3 flows?
My Nexus shows the default load balancing configurations
Port Channel Load-Balancing Configuration:System: source-dest-ip
Port Channel Load-Balancing Addresses Used Per-Protocol:Non-IP: source-dest-macIP: source-dest-ip source-dest-mac
Is it possible to use two different load balancing methods at each end of a port-channel between two switches?
We have a Cisco 6509 at one end of the port-channel and a Cisco blade switch 3020 at the other end. Right now, we are using "src-dst-ip" at both end of the port-channel. We would like to change this. That is, we would like the #3020 switch to use "src-dst-ip" while the 6509 switch should use the "src-dst-port".
Why we want to do this, the reason is that we have FWSMs on the 6509. I've read that by configuring "src-dst-port" on the 6509, one can get a better performance of traffic going through the FWSM. However, the issue is that the 3020 switch does not support "src-dst-port".
We are currently designing Layer 3 to the edge EIGRP solution for our customers. The network is a hybrid of collapsed core (Core to access) as well as a three layer design (Core/Distro/Access) for connectivity to the Data Centre, Internet, Wireless Blocks etc.The core of the network contains two 6509-E switches interconnected on a Layer 3 Port channel (no VSS). Access Layer switches (3750-X series running Stackwiseplus protocol) connect to the core switches over p2p routed links and Distribution layer switches (3750X stackwiseplus) provide connectivity to the Data centre, Internet, wireless blocks etc.
The access and distribution switch stacks(Cisco 3750-X) are set up with two or three member switches with uplinks multihomed to the primary and secondary core switch with each uplink included in EIGRP. In each of the stacks, one of the switches controls the operation of the stack, which will be the stack master.As the Cisco Stackwise architecture is not SSO-capable but NSF aware, all Layer 3 fuctions must be re-established during a master switch outage. To minimize control plane impact and improve Layer3 convergence, uplinks should be diverse and originate from the member switches instead of the Master switches in the respective stack. This is as per Cisco recommended design solution.The above solution can be setup if there are more than two switches in the stack. i.e. uplinks are configured on the backup member switch modules.
1.But what about stack with two switches..Which switch should be set up as the Master for a two member stack with uplinks to the core primary and secondary from each switch(Master and Backup)
2. For Layer 3 routing, does the routing takes precedene over switch failures? Say for eg. In a two member stack, the master switch with uplink to primary fails, does EIGRP provide a fast convergence to route traffic via backup secondary and does not wait for the control plane on the switch stack to converge? All the access to core links will be set up for ECMP.
I had a sw/reset on my 6509 switch. The info in the crashinfo file pointed me to bug CSCso89550.
The workaround for this issue is to disable the gold diagnostics tool.
connecting a 5548 pair to our core 6509s. Just want to be sure we don't introduce any issues into the network.The 6509's are connected and perform all the routing. Essentially, we're moving away from a 3750 stack in the data center and the 5548s are the replacement. We'd want to limit the vlans to the specific server network vlans. Our current setup is a port channel between the 3750 and each of the 2 6509s for redundancy. I'd like to use the same functionality when we connect the 5548's but I'm looking for what the config should look like to ensure no spanning tree loops are introduced and that it is configured optimally.
View 1 Replies View RelatedHow i can view the capacity throughput (backplane) of core switches (6509)? How i know much is in use?
View 2 Replies View RelatedI am trying to do ios upgrade on 5 stacked 3750 switches. All the switches have different model number, so i am wondering which image file i should download. As far as i understand all the stacked switches should have the same IOS, i may be wrong. The switches have the following model numbers and SW images;
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
1 28 WS-C3750G-24PS 12.2(35)SE5 C3750-IPSERVICESK9-M
* 2 28 WS-C3750G-24PS 12.2(35)SE5 C3750-IPSERVICESK9-M
3 52 WS-C3750G-48PS 12.2(35)SE5 C3750-IPSERVICESK9-M
4 30 WS-C3750E-24PD 12.2(35)SE5 C3750E-UNIVERSAL-M
5 30 WS-C3750E-24PD 12.2(35)SE5 C3750E-UNIVERSAL-M
which image file i should use as they all have different model numbers and Cisco provides different image files for each model.
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]