APs not Join WiSM - Page 3

cdiaz · ‎08-26-2011

Hello, I am Claudio

I have problems with register the APs in the module WiSM, the AP join statistics is null.

The IPs from APs are local DHCP in the module.

The softtware version in the WiSM is 7.0.116. The APs are 1140. The IOS version on the Cat6500 is 12.2.33SXI4a.

Some of you had a similar problem.

Thanks, best regards

cdiaz · ‎09-01-2011

David,

Thanks for you help but the option 43 is not the problem, becouse I replaced the module WiSM for a apliance 4402 and the APs joined succsessfully.

URA_NUNOA_SW_6500_CLH#show wism status

Service Vlan : 209, Service IP Subnet : 172.20.1.177/255.255.255.248
      WLAN
Slot Controller Service IP       Management IP    SW Version Status
----+-----------+----------------+----------------+-----------+---------------
2     1           172.20.1.178     172.20.1.148     7.0.116.0   Oper-Up
2     2           172.20.1.179     172.23.24.252    7.0.116.0   Oper-Up

URA_NUNOA_SW_6500_CLH#show etherchannel load-balance
EtherChannel Load-Balancing Configuration:
src-dst-ip vlan included
mpls label-ip

EtherChannel Load-Balancing Addresses Used Per-Protocol:
Non-IP: Source XOR Destination MAC address
IPv4: Source XOR Destination IP address
IPv6: Source XOR Destination IP address
MPLS: Label or IP
URA_NUNOA_SW_6500_CLH#

URA_NUNOA_SW_6500_CLH#show etherchannel summary
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator

        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port

w - waiting to be aggregated
Number of channel-groups in use: 3
Number of aggregators: 3

Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
305    Po305(SU)        -        Gi1/1(P)       Gi1/2(P)       Gi1/3(P)
                                 Gi1/4(P)       Gi1/5(P)       Gi1/6(P)
403    Po403(SU)        -        Gi2/1(P)       Gi2/2(P)       Gi2/3(P)
                                 Gi2/4(P)
404    Po404(SU)        -        Gi2/5(P)       Gi2/6(P)       Gi2/7(P)
                                 Gi2/8(P)

URA_NUNOA_SW_6500_CLH#

weterry · ‎09-01-2011

Are you saying that there are 0 APs able to register to either WLC in the WiSM? But you can still manage the WLC?

I'm just throwing this out there, based on things I remember from the past, but I'm not sure if its relevant:

I wonder if load-balancing is at fault here?

EtherChannel Load-Balancing Configuration:

src-dst-ip vlan included

I remeber awhile ago we had a problem when the switch did "src-dst-ip enhanced". And the solution to that was later ios allowed a "src-dst-ip eclude vlan" command..... So the fact that yours is saying vlan included makes me think its like the "enhanced".

If your IOS runnning-config is showing you the interfaces for your WLC, you could try to shut down all but one port and see if everything suddenly starts working, but I'm thinking your IOS might hide all those ports. Perhaps disabling the port from the WLC itself will have the same effect?

Either way, the idea is still if you have the same problem with a single interface connected (or you can try to change load-balancing to be the "exclude vlan" option, if thats possible).

daviwatk · ‎09-01-2011

Thats fine. Your original post stated you are offering DHCP internal to the module, but you also have a DHCP pool defined elsewhere with option 43?

My suggestion was that you do not offer DHCP at the module. I'm really not sure from what you described whether it is internal or external to the module at this point. If that pool is external to the module you "should" be fine as you are offering two addresses in option 43, per your hex code: 172.20.1.148 and 172.20.1.150.

Have you performed a debug from the AP to verify it is receiving the Option 43 information correctly?

#debug dhcp detail

You will be able to see what address the AP gets from Option 43. At that point, the AP should be sending a unicast join to those addreses UDP 12223. Did you confirm you are permitting traffic for 12223? Can you ping the mgmt interface of either WLC on the WiSM from the AP?

CORRECTION EDIT: I have specified LWAPP UDP ports. This should be CAPWAP UDP ports: 5246 and 5247. Regardless, we would need to see what the AP console output looks like and verify communication from AP to WLC MGMT.

aous.salloum · ‎10-18-2011

Dears ,

we have also problem with the WISM in 6513 the Number of Access Points is going up and down on the controllers

and if i try to ping the WISM from the access points vlan am getting so many requests time out

In the core switch we are tagging the native Vlan as you can see below

CORE-SWITCH2#sh run | i tag

vlan dot1q tag native

and we don't have the command wism module 9 controller 1 native-vlan X because the native vlan is tagged

could this be the reason ? that its mandatory that the native VLAN is not tagged for the Cisco WISM configuration