Cisco Wireless :: 6509-E / WiSM Controller Unreachable From WCS
Jan 26, 2013
I am getting an alarm on WCS where a one controller is down, unreachable from WCS, while the other one is reachable on the same WiSM module. Upon investigation, Status of controller is shown as "Oper-Up" for all controllers on Supervisory engine. Hardware platform is Cisco 6509-E.
WLAN
Slot Controller Service IP Management IP SW Version Status
----+-----------+----------------+----------------+-----------+---------------
2 1 192.167.10.11 172.19.47.65 6.0.196.0 Oper-Up
2 2 192.167.10.12 172.19.47.66 6.0.196.0 Oper-Up
However, I can not ping the managment interface of the down controller while the other controller management interface is pingable. All these interfaces are in the same VLAN.
ping 172.19.47.65
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.19.47.65, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Problem is fixed when I reboot the problematic Controller. However, this problem re-appears after some time. I am not able to figure out why controller is not able to ping its default-gateway which is an SVI interface on Supervisory card on the same chassis, and showing status UP/UP. Is it a software bug or backplane fault or any other reason ?
We have a WISM in a 6509. The 6509 lost power (the UPS failed) and upon reboot the WISM isn't allowing AP's to connect. The WISM is blade 4. Upon consoling in, I get this error message for all 8 ports: 42w6d: %EC-SP-5-CANNOT_BUNDLE2: Gi4/1 is not compatible with Po407 and will be suspended (trunk mode of Gi4/1 is dynamic, Po407 is trunk)
I have been having some issues trying to stand up an older WiSM that has been incorrectly configured by my predecesssor and has a bad Mgt IP so I am unable to telnet or SSH into it, nor can I console or session into it.
What I would like to do is to change the Mgt address for the WiSM controllers (1 and 2) by way of the Sup (not sure that is possible) because as it stands they are set to 169.254.1.1 and are unreachable even when directly consoled into them.
Core-A#sh wism status
Service Vlan : 52, Service IP Subnet : 10.104.52.2/255.255.255.0 WLAN Slot Controller Service IP Management IP SW Version Status ------------------------------------------------------------------------------------------------------- 3 1 10.104.52.3 169.254.1.1 4.0.217.0 Oper-Up 3 2 10.104.52.4 169.254.1.1 4.0.217.0 Oper-Up
Core-B#sh wism status
Service Vlan : 52, Service IP Subnet : 10.104.52.1/255.255.255.0 WLAN Slot Controller Service IP Management IP SW Version Status ------------------------------------------------------------------------------------------------------- 3 1 10.104.52.50 10.104.30.254 7.0.116.0 Oper-Up 3 2 10.104.52.51 10.104.30.250 7.0.116.0 Oper-Up
I hope to get this WiSM setup on Core A and get it configured like I have my Core B and then run them in a dual failover design with load balancing between the two.
although cisco sw advisor said that the best IOS for my hardware 6509 Sup720 IOS: (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF16 suits the WiSM; And I tested it already with WiSM version 5.0 but when I've upgraded the WiSM to version 6.0 the service interface from the switch side says:
B5_Noc2_CS1(config)#int gig 4/9 % This interface cannot be modified
as the customer refuse to upgrade the switch IOS & He wants to use the latest ED WiSM sw 6.0;
I have issue to access one of the wism on 6509 switch however other wism is ok both wism on switch are up and functional how to enable remote access on wism.
I have one instance of WCS 7.0.172.0 (on a Linux host) and a fleet of WiSMs that I'm upgrading from 7.0.98.0 to 7.0.116.0. Every time I run thru the upgrade process from within WCS (scheduled to run overnight, off peak hours) all of the controllers that were upgraded then show as "unreachable". Grepping thru wcs-0-0.log shows messages that the controllers are unreachable via SNMP but running an "snmpget" from the command line to any of the affected controllers works just fine. The only way I've found to remedy this is to stop and restart the WCS service. Considering how long that takes with my deployment...I'd rather not do that every time .
I will upgrade my Wireless Controller Firmware 7.2.103.0 But I dont know WCS will support manager new controller firmware 7.2.103.0 ?is need NCS to manager? or WCS can be manager new controller firmware 7.2.103.0 all feature?
Now My hw is
Csico 6509 Sup 720 3b 12(33)SXJ My Controller is WiSM2 WiSM2 is 7.0.116.0 WCS is 7.0.172.0
I am using WiSM in 6509, this WiSM has two controller with the same management IP subnet, I tired to upload the configuration to the TFTP server, but tried many times, one of the controller working well, but the other one always cannot reach the TFTP server, here is the debugger log for both controller
Failed one: (KGV-WiSM-1) >debug transfer all a enable (KGV-WiSM-1) >*TransferTask: Nov 10 16:26:08.735: RESULT_STRING: TFTP Config transfer starting. *TransferTask: Nov 10 16:26:08.735: RESULT_CODE:1 *TransferTask: Nov 10 16:26:32.018: Locking tftp semaphore, pHost=172.16.102.107 pFilename=/KGV.aes *TransferTask: Nov 10 16:26:32.018: Semaphore locked, now unlocking, pHost=172.16.102.107 pFilename=/KGV.aes
[code].....
why the controller can't upload the file, I can ping both controller and both controllers can ping to the TFTP server.
I dont think my cards are faulty (4 cards in 2 6500 switches),I connect directly to my WISM cards, boot them (insert them), I see it turning on, enabling services, and as soon as the "username:" prompt apears, the Status led turns off and I lose console. [code]
We have Cisco WiSM modules on our 6500 switch. I tried to register a 1142 access point to the WiSM. Is there any difference in the way an AP registers and appears on the WiSM as compared to the Wireless Lan controller?
I could see the AP get an ip from dhcp pool ( configured on the switch ) and Ap was visible on the cdp neighbor of switch.
However, i could not locate the new AP on the WiSM module. Do i need to add MAC address to the WiSM as same as WLC.
I have a facility, where all the access points almost 250 of them are connected to two WisM's (One in each core switch ) . They are running in 6.0.199 firmware . These two WisM's are managed by WCS , which is running 6.0.188.
As i need to add more access points and to make fully redundant , 5500 controller was ordered and it has with firmware 7.0 installed. Couple of queries related with it .
1. Can 5500 be added in the WLC group, so that existing Access Points can be configured to use primary controller as 5500 and secondary / tertiary controller as WISM ?
2. Will 5500 be able to be detected by WCS , as the version of 5500 is 7.0 and WCS version is 6.0.188 ?
3. As WCS was already deployed and live, is it possible to upgrade, if the client has support contract like SUSA ?
WiSM WLAN Service Module WS-SVC-WISM-1-K9 in 6509e running VSS IOs s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin having trouble to get the IP from service-vlan DHCP.The pertinent config is as follows.
! vlan 300 name WiSM_Service_Vlan !interface Vlan300 description *** WiSM Service-Vlan ip address 192.168.200.1 255.255.255.0
[code]....
The service IP is supposed to have been populated with an address from the dhcp pool. I am also unable to connect to it by doing a session switch 1 slot 4 processor 1. I get the following upon attempting to do so:
HO2NET0001##session switch 1 slot 4 proc 1
The default escape character is Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 0.0.0.0 ...
I'm trying to configure an snmp notification reciever on WCS 7.0, so that critical alarms get reported to our central console. Following the configuration guide I was able to add the reciever as northbound, but after adding it I get an alarm saying that it is unreachable by WCS so all alarm notification will be suspended. I have tested snmp and ping connectivity between the WCS box and the notification reciever and it works ok, is there some other traffic that I might be missing?. I've seen some packets going from the WCS box to TCP port 7 on the reciever, which as far as I know is the echo service, is that what WCS uses to test connectivity?
I have a WiSM installed in WS-6504E, vesion 6.0.182. It can't function normally after upgrading to version7.0.220.When it was unstable, I found three strange condition 1. A lot of log looks like this*osapiReaper: Mar 10 14:53:39.282: %OSAPI-3-FILE_OPEN_FAILED: osapi_file.c:370 Failed to open the file : /proc/1059/stat.(erno 24)*osapiReaper: Mar 10 14:53:39.282: %OSAPI-3-TASK_GETTIME_FAILED: osapi_task.c:3431 Failed to retrieve statistics (/proc/<pid>/stats) for task 'fmcHsTask'2. Internal Temperature was showed "sensor failed"3. CPU User load is Zero?
The Samsung SCH-i569 Wi-Fi can't work at the LAP1131G with WiSM. It can associate to AP and get the ip address but about one minutes ago it had deauthentication and the phone's Wi-Fi status will show scanning. The phone can work at the Autonoumous mode or other 3rd party Fat AP.
Setting up a multi floor WLAN using a 6500 WISM Controller. Each floor has an AP group with the floor WAPs assigned. Each floor has a VLAN and the WLC has an interface configured. Each floor has a WLAN configured with the same SSID and the only change is the interface on the WLAN per floor.DHCP is remote on AD servers and each floor as a scope configured.Each floor works fine - we can get connected and get assigned to correct IP address. The issue we had with this setup was moving between floors. When we move up a floor the client loses connection to the inital floor (coverage - as expected). if we disconnect and reconnect it connects to the new floor SSID and gets an IP from DHCP.When looking into this - I then created an interface group and added all the floor interfaces into the group. I then applied the interface group to each floor WLAN and did soem testing - it worked as expected. I could now move between floors.The issue with this is though. When I was testing I already had an IP address assigned from DHCP - before I changed to interface groups. The issue is that the intial DHCP assignment no longer works and we cant connect to the WLAN anymore,
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?
I have a customer buys 12 x WISM and build up a mobility, when I add the final WLC to mobility, it prompts that there mobility group has reached the max of mobility member, but the total member is 23, according the configuration guide, it should be allow to 24 member, do I hit some bug? My using version is 7.0.98.0.
The problem is WiSM module not coming in OPER-UP status , it’s in Started-Keepalive status.I did run debug wism events on cat6509 and seeing below logs:
[code]...
It’s receiving garp request from controller and assign ip to controller but then keepalive time expired and it’s put the controller in started-keeplaive status.
I have 2 brand new systems, a desktop running Windows 7 Pro connected with a had line, and a laptop running Windows 7 Home Premium connected wirelessly. Both can access the router, both can access the internet, both can be pinged from the router. However, they absolutely cannot see each other on the network. If I try to ping by name, the addresses don't resolve. If I try to ping by IP, I get either no reply or the "destination host unreachable."I've disabled firewall completely on both. I've double, triple, quadruple checked all sharing settings (network discovery is enabled on both, sharing enabled everywhere, etc. etc.). I've tried disabling all other network adapters on the laptop, no difference. I've tried all of the online tips about repairing winsock.
I have used this WRT54gl for several years and it's performed flawlessly both wireless and wired. Recently I've extended the reach of my home network by adding a second WRT54g cabled to the network. I also added another PC in a nearby home with a wireless dongle attachment to the network. In setting all this up I've just noticed that the 'Traceroute' and 'Ping' functions in the original WRT54gl do not work. That is, when in the Administration, Diagnostics window and select either function I get a 'Network is unreachable' message instead of the ping/traceroute information.
All other functions on the network seem to work fine, ie..., I can ping the router from anywhere. Both wireless and ethernet connections work fine through it. The newer WRT54G addition to the lan is setup identical and the ping/ trace router work fine with it.Both routers have DHCP disabled. My modem handles it.
Once in a while, I lose Internet connection and at the same time cannot reach my Siemens Speetstream 4100b DSL modem's setup page 192.168.0.1 ; it happened again this morning (from both wired and wirelessy connected computers). When I go to the router's setup page 192.168.1.1 , it would usually in that situation show that the router has not acquired the Internet IP Address; I power-recycle (a few times) both modem and router and eventually the router reports that it has acquired the Internet IP Address, but there is still no Internet, and the DSL modem's setup page 192.168.0.1 is unreacheable.The situation usually self-resolves only in an hour or so after the time the router has acquired the Internet IP Address: Internet starts working, and the DSL modem's setup page 192.168.0.1 becomes reacheable.
I have different types of network clients connecting to both bands of router (5 ghz and 2.4 ghz), and both bands set to WPA2 only. Everything has been set up and working for the past year with no problems.
Suddenly this morning, none of the 2.4 ghz clients can connect and get authenticated. When I attempt to ping them from a Windows 7 desktop connected by a LAN cable, I get Destination Host Unreachable.
The 5 ghz clients are fine and have had no problems. I tested this with the New iPad connected to the 5 ghz band.
Rebooted the E3000 router and the Comcast cable modem, then installed the newest firmware on the E3000 using the web access portal at 192.168.1.1, and still not working.
Changed the WPA2 Personal security mode for the 2.4 ghz band to WPA2 Personal/WPA Mixed Mode, and now all the clients are connected and authenticated and working OK, albeit slower.
What happened? And how can I fix this so I can change the security mode for the 2.4 ghz band back to WPA2 Personal?
P.S. The types of clients that connect to the 2.4 ghz band are 2 Windows 7 desktops, a Windows 7 laptop, and 5 Cisco Wireless N Internet Home Monitoring Cameras. The camera feeds have slowed down considerably using this Mixed mode.
I've tried everything that has been posted so far except for opening up the router itself which I will refuse to do.- Getting = Host Unreachable 192.168.1.20 (I am using 192.168.1.1 as the gateway)- No ping whatsoever even when turning on the router over and over.
