topic 6513 WISM Problem in Wireless

6513 WISM Problem

aous.salloum — Sun, 04 Jul 2021 03:55:21 GMT

hello dears , I have 6513 which have wism and sup 720 , for some reason the access points keeps on going up and down

the port channels created automatically but i cannot see any configuration inside it as shown below , is that normal ?

I tried to edit the interfaces and add the trunk configuration but it cannot be modified .

CORE-SWITCH2#sh run int port-channel 417

Building configuration...

Current configuration : 5 bytes

end

CORE-SWITCH2#sh run int port-channel 418

Building configuration...

Current configuration : 5 bytes

CORE-SWITCH2#sh run int gigabitEthernet 9/1

Building configuration...

Current configuration : 5 bytes

end

the Wism status is showing up but the APs Number regestered keeps on going up and down .

the version running on the sup 720 is 12.2(33)SXI5 and the wism is installed in slot 9

any ideas

many thanks

6513 WISM Problem

Stephen Rodriguez — Thu, 13 Oct 2011 16:04:36 GMT

That is the correct behavior, depending on the IOS running on the Sup.

12.2.SXF5 is where Cisco first started using the "auto commands" to configure the WiSM vs configuring the port-channels manually.

I believe it was around SXF9/11 that it became only the "auto commands", and around this time, once the auto commands were used, access to configure the port-channels directly was depricated.

Now, in the logs on the Sup, are you seeing any messages regarding slot 9? If you do a show wism stat, are they up? Can you session in from the Sup, and reach via the mgmt interface?

If so, more than likely it's not a "WiSM" problem

What errors are showing on the switch ports the AP's are connected to? If you do a show msglog on the WLC, do you see a lot of messages about the AP? Can you run debugs against an AP to see if you can gather the messages to see why the AP might be falling off the WLC?

HTH,

Steve

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

Please remember to rate helpful posts or to mark the question as answered so that it can be found later.

6513 WISM Problem

aous.salloum — Sat, 15 Oct 2011 21:13:28 GMT

Hello Steve , thanks allot for your reply and consideration

if I do show wism state its showing as up

CORE-SWITCH2#sh wism status

Service Vlan : 76, Service IP Subnet : 6.6.6.1/255.255.255.0

WLAN

Slot Controller Service IP Management IP SW Version Status

----+-----------+----------------+----------------+-----------+---------------

9 1 6.6.6.4 172.16.40.13 6.0.196.0 Oper-Up

9 2 6.6.6.3 172.16.40.14 6.0.196.0 Oper-Up

and yes i can session in from the Sup I will run some debug tomorrow , capture the logs and past it here .

my question was its ok that the ether channel was created automatically

but if i put show run interface portchannel 418

or show run int gig 9/1

I should not see ? switchport

switchport trunk encapsulation dot1q

switchport trunk native vlan 40

or it will show as blank configuration ?

is it any problem that am using SXI not SXF ? or its ok ?

Re: 6513 WISM Problem

Stephen Rodriguez — Sun, 16 Oct 2011 14:07:40 GMT

what you are seeing is normal and expected. SXI is fine as well for the Sup code.

Sent from Cisco Technical Support iPad App

Re: 6513 WISM Problem

George Stefanick — Sun, 16 Oct 2011 14:13:10 GMT

Its funny you mention this... After "SXH", AUTOLAG is required and you will not see the WISM interfaces in the show run. But you will see them in the show interfaces and eitherchannel.

This threw me from a loop as well...

6513 WISM Problem

aous.salloum — Tue, 18 Oct 2011 15:32:14 GMT

Guys , 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

Note : If I try to ping from my laptop connected to the Access Points Vlans to the controllers I have 58 % Lost but if I try to ping a server in the controllers vlans its pinging fine so its not routing issue

your reply and feed back is highly appreciated

many thanks

thanks