My company has been contracted to upgrade the 2 WiSM1 modules on a 6509 for a customer. The hardware isn't changing but the software is being upgraded to WiSM2. The cutsomer has HUNDREDS of AP's and dozens of VLANs and subnets (large municipality and school district).
Cisco SE's have been pushing the customer to purchase the WCS 7 software (they've been managing these Controllers independantly) stating there is no mechanism to upgrade WiSM1 configs to WiSM2. I am vaguely familiar with the cisco controllers but have little WiSM experience. So i feel like i'm working without a net here.
So,
1) Any way to migrate from 1 to 2 without the WCS and without having to reinvent the wheel?
2) How does the WCS make this transition easier? What does it do to the WiSM1 configs to make them WiSM2 compatable?
I am about to migrate WISM1 to WISM2, The image of WISM1 is 6.0.199.4 and the image of WISM2 is 7.2.111.3.
Do i need to upgrade WISM1 to 7.2.111.3 before i export the configuration and import it into WISM2? Or can i just export the configuration from WISM1 on 6.0.199.4 and import directly to WISM2 which is on 7.1.111.3?
We have some new WISM2 running 7.0.116.0, but now we need to upgrade their license to suport 1000 APs. So I am looking at upgrading the software to 7.2.110.0. We are running WCS at the moment and got NCS with the new WISM2, so going to 7.3 and buying Prime Infrastructure is not an option at the moment, thus we are going for 7.2.
The thing is I can't seem to find much info about this upgrade. Is 7.0->7.2 a smooth upgrade? Do we need to do any configuration changes to the WISM2 or LAP1242? We are running H-REAP, will the change to FlexConnect be affected? I can't seem to find anything regarding requirements for 6500/SUP for running WISM2 7.2, do I need a certain software for that?
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?
I am getting many radio resets on 1252AG access point on Wism1. The warning in WLC shows as : AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:c4:71:fe:5c:xxxx Cause=Reset on transmit completion. Status:NA cause = reset on transmit completion.I have fixed RRM to freeze and still same result.
We are trying to test ios upgrade for Cisco 6509 switch with issu (in service software upgrade). We were able to upgrade the ios but there is one issue in issue 6509's supviseengine720 gigabit port lost the connection during the upgrade process.
boot system flash bootflash:s72033-jk9o3sv-mz.122-17a.SX3.bin boot bootldr sup-bootflash:s72033-psv-mz.122-17a.SX1.bin
I downloaded s72033-mp001-pz.122-33.SXH5
I read the documentation on Upgrading Software Images on Catalyst 6000/6500 Series SwitchesURL
I was wondering do I copy the s72033-mp001-pz.122-33.SXH5 to the sup-bootflash and bootflash? In the example it also uses disk0: but I get a <No device available>. Also keep in mind we're upgrading the application and maintanence partitions also. So this is a big upgrade and I've never done this before.
I guess the 2 things I want to know is:
1) Can I copy the s72033-mp001-pz.122-33.SXH5 to both the sup-bootflash and the bootflash? Can I run it just copying it to the sup-bootflash? 2) It was my understanding that I only needed one image file for the upgrade but the documentation says I need "a. the main software image b. the bootloader image" Do I need another file? I'm a little confused. I did notice the files had different names and sizes and so do the ones on my current Sup 720.
And we are doing this tomorrow and I just happened to be reviewing the documentation one more time and somehow missed this.
Have a new 6509-E router with 2 sup2T blades. However it came with IPbase and we need to put Ipservices on it. I have copied ipservices IOS to bootdisk and slavebootdisk.
However I cannot get get to the boot command to point to bootdisk. It only allows me to point to flash:
)#boot system flash ? WORD System image filename <cr>
Yet I don't seem to have an option to copy this new IOS to flash. How do I get to copy it to flash:
Here is the original show boot command:
sh boot BOOT variable = bootflash:s2t54-ipbasek9_npe-mz.SPA.150-1.SY1.bin,1; CONFIG_FILE variable =
I have a question regarding WISM2 DP and licensing.
Suppose i have a WISM2 with 7.0, 500AP license today and i activate WISM2-DP by upgrading to 7.2,Do i get 500 AP capacity for free (total 1000AP) or do i get 250APs on each WISM2-blade ?
If i get 500APs for free, why is Cisco selling an expensive licensed 1000 AP WISM2 ? I better buy a single-plane 500AP-WISM2 and upgrade it myself then...50% profit.
Is this the same for a WISM2-300 (supporting 300 APs) ?When i activate WISM2-DP here, do i get an extra 300 AP or an extra 500 APs ? Or 150AP on each blade ?
I having an issue with WCS and the new code 7.4 on my WiSM2 blade. When I try to refresh configuration from/to controller it fails. I just upgraded from 7.01 and it worked before the upgrade.
Is this not supported?
I am able to change configuration from WCS to the WiSM2 and it works fine just cant copy config.
I need to upgrade IOS on my 6509 MSFC2. Below is the software version I have on the Sup2 and msfc2. The reason I need to upgrade the msfc2 IOS is that I need to implement ip sla/object tracking and it is not supported by the current version of IOS on msfc2. How do I select the new IOS that I should upgrade the msfc2, in order to achieve object tracking...I see a long list of IOS in the software download section of 6509 msfc2, but not sure which one to choose..
I just need to upgrade existing FWSM of 6509.FWSM Firewall Version 2.3(1)is it possible to upgrade to the version of 4.X .If not to which version is safe?And also I need to steps of doing FWSM upgrade.
Tonight 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:
I have just been setting up a WISM2 in a test lab and for some reason the Supervisor is not creating a port channel on my 6500 as suggested in the WISM2 Deployment Guide. WISM2 is installed in an appropriate slot (according to same doco) and have attempted reset to factory defaults, removing and power cycling several times.
I have installed WiSM2 with ver 7.4 and Bonjour works great with instruction provided, But…… 2 problems. I cant get it to work on the same subnet. (odd since the whole problem was not able to work across subnets), More important the new Code function / password function on the airplay wont work. I get the code on the projector, but the ipad never pop up the login box it just errors out.
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.
I 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?
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".
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 wireless network running with Controller WISM2 and I also have a NCS.I want to know if there is any way to look of individual log of CAPWAP and LAPWAP Access Points. It is better if I can see it through NCS.
I have a situation where a customer doesn't have the required power units installed in their 6500 for me to provision a WiSM2.They use a VSS pair with a single Sup720 in each. They have no intention of adding a second Sup to each chassis.
I need to justify why they can't use slot 6 (which has power reserved) if I am to get them to upgrade the PSU's. The documentation I've found says it is supported but not recommended.
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?
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 will be installing a secondary SUP720 in a 6509-E and will be upgrading the IOS on the existing SUP which is on 122-18.SXF6. I've read that this release has passed End of Critical Maintenance earlier this you. I thinking of upgrading the IOS to 12.2.33-SXJ1(ED) or 12.2.33-SXI8(ED) (possible more stable), but i'm not sure if i need any step upgrades from the current version. The SUP meets the required hardware specs and I will also be upgrading the ROMMON to 12.2(17r)SX7 first.
I have alot of experience upgrading IOS on routers and switches, but i just need to now if there are any gotchas that i need to know for the upgrade on the SUP.
The other issue is i don't believe the current IOS has been installed, are there any issue running on an IOS not installed. Patching is not available since the system is not running from an installed image. To install please use the "install file" command.
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 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?
I 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've just reset our WISM2 in the test lab back to factory default as I needed to reconfigure the 6500 and the WISM2 itself. Bearing in mind I had it working before.I've just renamed and re-addressed some of the vlans so things flow better and make it easier to add more WISM2s in the future.Now I've run through the initial configuration and it's rebooted ok and show WISM status is showing Oper-Up and there's a port channel 407 been created as I would expect. However, I am unable to get to the management interface via GUI or SSH. In fact from the 6500 I can't even ping the management interface (but I can the service port).The Vlans have been changed in the 6500 config so it knows the native-vlan and service vlan etc and all the vlans are up/up.
