WISM not connecting after reboot

[Dave Culver]

          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 am fairly new to WISMS and my other 2 team members are out sick. Any suggestions?              

[Scott Fella]

You should check the connection on the chassis. Seems like maybe the configuration got lost. Check the trunk/port channel on the chassis for that WiSM.

Sent from Cisco Technical Support iPhone App

[Dave Culver]

Scott,

     Thank you for responding so quickly.

     I pulled this from "show run-config"

Port Summary

           STP   Admin   Physical   Physical   Link   Link    Mcast     

Pr  Type   Stat   Mode     Mode      Status   Status  Trap   Appliance   POE 

-- ------- ---- ------- ---------- ---------- ------ ------- --------- -------

1  Normal  Forw Enable  Auto       1000 Full  Up     Enable  Enable     N/A    

2  Normal  Forw Enable  Auto       1000 Full  Up     Enable  Enable     N/A    

3  Normal  Forw Enable  Auto       1000 Full  Up     Enable  Enable     N/A    

4  Normal  Forw Enable  Auto       1000 Full  Up     Enable  Enable     N/A

        I pulled this from " show wism module 4 controller 1 status"

WiSM Controller 1 in Slot 4 configured with auto-lag

Operational Status of the Controller : Oper-Up

         Is this the information you are asking for?

[Leo Laohoo]

This is a known "bug" between the chassis' IOS and the WiSM1/WiSM2 firmware.

Do a search for the 6500 configuration that goes with the line like "sh run | b wism module X controller Y native-vlan".

Remove this line (with a "no wism module X native-vlan N")  and add it back.  Your WiSM should reconnect. 

[Shao-Yu Chen]

I work with Dave and we are able to login to WISM via GUI now. The problem that we are having now is that LWAPs are not showing on WISM. I have checked WISM and LWAPs are on the same vlan. The only thing I noticed the run config on module X is empty, and it is the same way as on the other WISM at the other school. Any suggestions?

[Leo Laohoo]

 The only thing I noticed the run config on module X is empty

You mean you can't find the line that specifies what are the allowed-vlans?

If this is the case, then the only way is to manually put it back in.

And I haven't seen this behaviour since the Cat 6500 IOS SXI days.  What IOS is your chassis running?

[George Stefanick]

Can you post the entire running config.

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Shao-Yu Chen]

Running-config from the 6509 chassis,

ip dhcp pool WISM-Service-Ports

   network 192.168.0.0 255.255.255.248

   default-router 192.168.0.1

wism service-vlan 192

wism module 4 controller 1 allowed-vlan 150,174,190,196,198

wism module 4 controller 2 allowed-vlan 150,174,190,196,198

wism module 4 controller 1 native-vlan 196

wism module 4 controller 2 native-vlan 196

wism module 4 controller 1 qos-trust dscp

wism module 4 controller 2 qos-trust dscp

show run from the 4510 where LWAP is connected to,

interface GigabitEthernet2/48
description - LWAP -
switchport access vlan 196
switchport mode access
spanning-tree portfast
end

[George Stefanick]

Can you console into the ap, reboot, collect all the output and post.

Config in the wism looks good ..

Sent from Cisco Technical Support iPhone App

[Shao-Yu Chen]

One thing I find it strange, why there is no Option 43 on the WISM,

ip dhcp pool LWAP

   network 10.x.196.0 255.255.255.0

   default-router 10.x.196.1

   domain-name osceola.k12.fl.us

   dns-server 10.y.z.12 10.y.z.13

But, I do see our WLCs using Option 43 for ip dhcp pool.

How do those LWAPs know which WISM to connect to? Does it help if I add Option 43 into run-config for the WISMs?

[George Stefanick]

If the APs are on the same vlan as the management vlan (196) they should broadcast and find the WLC. Option 43 is used if the APs are on a different subnet. This is why I was curious to see the AP output.

Specific to option 43. You put option 43 on the DHCP server that is sending the DHCP address to the AP. This allows the AP to find the controller. But again, if you are on the same vlan, option 43 isnt needed.



__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Shao-Yu Chen]

Found out DHCP pool was full from core switch. By removing the ip dhcp pool LWAP and put those lines back in. We have all the LWAPs joined with WISM. Finally case cloased.

[George Stefanick]

Excellent!

__________________________________________________________________________________________
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
__________________________________________________________________________________________
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

[Leo Laohoo]

wism module 4 controller 1 native-vlan 196 
wism module 4 controller 2 native-vlan 196

Delete these two lines and re-add them.