Cisco Wireless :: WiSM2 Version 7.4 Cannot Work On Same Subnet
Jan 8, 2013
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.
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?
The pppoe on IOS (15 version) does not work (when using 12.4 version- everything is OK)I have tried it with c880data-universalk9-mz.151-1.T.bin, c880 data-universalk9-mz.150-1.M3.bin, c880data-universalk9-mz.150-1.M2.bin - DOES NOT WORK.But it DOES WORK with c880data-universalk9-mz.124-24.T4.bin.The configuration interface FastEthernet4 no ip address duplex auto speed auto pppoe enable pppoe-client dial-pool-number 1 service-name "xxx" interface Dialer0 ip address negotiated ip mtu 1452 encapsulation ppp dialer pool 1 dialer-group 1 no cdp enable ppp authentication chap callin ppp chap hostname xxx ppp chap password 7 xxx.
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.
problem with a Belkin Wifi Router: it's a G+ wireless router
Model:F5d9231-4 Version 2 OS- XP Service pack 2
i've tried resetting to factory settings and power cycling my modem and router but nothing.. the issue is that my Wifi icon on the router does NOT show and i went in to the setttings for it and tried resetting everything and nothing works. it works fine hardwired but my Wireless does NOT work..
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 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?
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 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'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.
I've installed our previous WISMs and other WISM2s previously and never had a problem.
6500 running SXJ2. WISM2 running 7.3.101.0 (which is what the rest of our WISM2s are on)
Insert WISM and go through initial setup. Run a show wism status on the 6500, and show sysinfo on the WISM. All looks good. Service port and management vlans are up. From the 6500 I can ping the service port IP, but not the management IP. From the WISM I can't ping the managment default gw but I can the service port. Unable to get anything back from the GUI..not surprising as not even ping works.
Now, as I said I've done it this way many times before...in fact I'm following my documentation from the last successful implementation and even adding in Cisco docs.
how to safely remove the WiSM2 from the Catalyst 6500 series switch? According to the documentation "Catalyst 6500 Series Wireless Services Module 2 Installation and Verification Note":
To remove the WiSM2, perform these steps:
Step1 Shut down the module by one of these methods: In privileged mode from the router prompt, enter the hw-mod module mod shutdown command. NoteIf you enter this command to shut down the module, you must enter the following commands in global configuration mode to restart (power down, and then power up) the module: Router# no power enable module modRouter# power enable module mod If the module does not respond to any commands, press the SHUTDOWN button located on the front panel of the module.
Step2 Verify that the WiSM2 shuts down. Do not remove the module from the switch until the POWER LEDis off.
But, in the case of Step1 (1st methods) I do not see a option "shutdown" in the command "hw-mod module 3"...
All I prompted to enter is: c6500#hw-module module 3 ?
boot Specify boot options for the module through Power Management Bus control register
reset Reset specified component
simulate Simulate options for the module Is it hidden options?
IOS version of c6500 is 12.2(33)SXJ1
In the case of Step2 (2nd methods) there is not any button on the front panel of the module?
And yet, it is better to remove the module configuration manually or use the command module clear-config prior to removing the module?
it is normal for the WISM2 time to be resetted to default of 1 Jan 2000 after rebooting the 6506E if no NTP is configured?I had to configure it back to the correct time. If not, the APs will not come up.Also, does the ap or wlc keep track of the ap group the ap is provisioned to?
I am trying to remove a line in a particular access-list configured in a FWSM module using this command "no access-list <acl> line 19 x x x x" but it doesn't work. See below:
FWSM/xxx03(config)# no access-list ? configure mode commands/options: alert-interval Specify the alert interval for generating syslog message 106001 which alerts that the system has reached a deny
[code]...
How can I remove a line from the access-list without clearing the entire access-list?
McAffee scan of acs 1113 appliance running the 4.2 build 124 patch 12 version reports that a medium vulnerability exists because the system has SSH version 1. Any way to specify only version 2 or turn off SSH?
We have just installed lms 4.2 and are having problems collecting config and inventory from ws-svc-wism2-k9. The response from TAC was that this is not supported. And it also says this in [URL]
Is this really the case ? Will there be released packeges to support this. It would be really useful if this was supported in lms4.2.
I know the WiSM 2 is like the 5500 WLC regarding the fact that you do not need to configure an ap-manager interface for CAPWAP packets because by default the managment interface acts like an ap-manager interface.
Any major advantages or disadvantages by letting the default action occur?
Just loaded the 7.2.103.0 software onto the brand new WiSM2. Going throught the options and have found that under the global parameters for 802.11a/n, 802.11b/g/n radios is now the "Maximum Allowed Clients" option. The allowed setting is from 1 - 200 clients.
Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
Doesn't seems to make sense... I have the 500 AP license on this WiSM2... I know this option used to be an optional setting under a WLAN in previous releases.
What I am trying to do is I have one switch with say a 10.1.9.1 sub-net I need to have one of the ports to be trucked with two vlans one for DSL and the other for a local connection with the sub-net of 10.1.5.1 both of the sub-nets are configured in the core as 9 and 5 so I have port 0 set up as a trunk and it is set up as ge-0/0/0.0 vlan_5, vlan_192 on the 10.1.9.1 subnet switch. The DSL is working but the local is not pulling a 10.1.5.1 IP and has no connectivity. Everything looks as if it is configured correctly but still the DSl is working but not the Local connection.
Is there any chance the Wireless Repeater mode work with WPA2-AES ?If not, which model of AP should I buy to connect it with my wap54g as Wireless Repeater?
We are looking to upgrade our WiSMs to version 7.0.230.0, but the Cisco compatibility matrix suggests we need to upgrade WCS to the same version (it is currently on 7.0.172.0). My question is can we upgrade the WiSMs and do the WCS at a later date with no issues or do we need to do them at the same time to keep visibility of everything?
The reason I ask is that some of my clients use lobby ambassador for some of their users and they will need wireless access on the day we are due to upgrade WCS (the WiSMs are due to be upgraded and rebooted earlier that morning.
I have a cisco 877w and ive setup two ssids on it each with different vlans (I intend to use the zone based firewall to lock down the guest zone later)
Ive made a quick diagram of my network its a single server with 2 NIC's one for the internal lan and another for the external network (direct connection to the router) The server hosts 3 virtualized servers with the ecternal nic only shared with the tmg 2010 server.
So my problem is that when I connect to the 10.0.1.1 network as 10.0.1.2 I can only ping the internal network however the internal network is incapable of responding (pinging back) giving destination host unreachable. I know I need some kind of routing but im not sure where to apply it on the TMG server with the next hop as 10.0.0.10 or on the router.
The guest wifi is intended to bypass the network firewall and not allow access to the internal network. I've enabled ip routing on the cisco router and attached the config below.