Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Unable to access WISM2 Management interface from particulart slot in a 6509 e chassis

I have recently installed 2 WiSM2 controllers into 2 6509e Chassis in a VSS configuration. The first WiSM2 in the first chassis came up fine little to no issue. The second however did not...I followed the same procedure as the first and I can session into the controller service interface but I can not access the controller via GUI or telnet nor can I ping it's management interface. If I place the controller into a different slot in the chassis it works fine. So I opened a case with TAC after some testing they determined that it may be the chassis. After replacing the chassis the problem still remains with the same exact slot. Now, they want to replace the controller which doesn't make sense since it works fine in another slots. I know the simple answer would be just leave it in the slot that works dummy...but it is bugging the heck out me to figure out why the one particular does not work. Can anyone help???

12 REPLIES

Re: Unable to access WISM2 Management interface from particulart

Are you putting the wism in the sup slot by chance? Also what code is on the sup ?

Shave you seen this document ?

http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a0080b7c904.shtml

Sent from Cisco Technical Support iPad App

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: Unable to access WISM2 Management interface from particulart

No, the slot in question is slot 4, it works fine in slot 8 and slot 6 (even though it is not a recommended slot). The 6509 has a Supervisor Engine 720 10GE  running version 12.2(33)SXJ2 and the controller is running version 7.0.116.0

Yes, I've seen this document it is the one I used to configure the first WISM2 Controller.

Bronze

Re: Unable to access WISM2 Management interface from particulart

If you have time to put it back in slot 4, post the following information from the 6509.  I believe you need the switch designation for these first few commands.

Module detected properly?

#show switch '%' hw module

Is WiSM in Oper-Up status, with an IP?

#show switch '%' wism status

What port-channel is created for these WLCs?

#show switch '%' wism module 4 controller 1 status

#show switch '%' wism module 4 controller 2 status

Is the port-channel passing traffic and all ports bundled properly?

#show etherchannel summary

Is your load-balance set to 'src-dst-ip'?

#show etherchannel load-balance

You could try re-issuing your wism allowed/native vlan statements.  Sometimes removing and re-creating these can restore connectivity.

#show run | section include wism

What status is the WiSM in?  Do the service ports get an IP address (assuming assigned via DHCP)?

Service-port, port-channel vlans up/up?

#show ip int brief

#show run (service-port vlan)

New Member

Re: Unable to access WISM2 Management interface from particulart

Module detected properly? Yes...

WHCORE1#sho module switch 1

Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 48 CEF720 48 port 1000mb SFP WS-X6748-SFP SAL13474QBP
2 10 WiSM WLAN Service Module WS-SVC-WISM-1-K9 SAD120309UK
3 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL13463UFR
4 4 WiSM 2 WLAN Service Module WS-SVC-WISM2-K9 SAL1540RSC7
5 5 Supervisor Engine 720 10GE (Hot) VS-S720-10G SAL13474884
7 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL13463T0H
9 48 CEF720 48 port 10/100/1000mb Ethernet WS-X6748-GE-TX SAL13463Q2P

Mod MAC addresses Hw Fw Sw Status
--- ---------------------------------- ------ ------------ ------------ -------
1 0023.ebb8.a5bc to 0023.ebb8.a5eb 2.3 12.2(18r)S1 12.2(33)SXJ2 Ok
2 001e.beb0.49c8 to 001e.beb0.49d7 2.2 12.2(14r)S5 12.2(33)SXJ2 Ok
3 0026.995f.9520 to 0026.995f.954f 3.4 12.2(18r)S1 12.2(33)SXJ2 Ok
4 e05f.b994.98b8 to e05f.b994.98c7 1.0 12.2(18r)S1 12.2(33)SXJ2 Ok
5 0023.33ab.de78 to 0023.33ab.de7f 3.1 8.5(3) 12.2(33)SXJ2 Ok
7 0026.9987.7b28 to 0026.9987.7b57 3.4 12.2(18r)S1 12.2(33)SXJ2 Ok
9 0026.995f.7b10 to 0026.995f.7b3f 3.4 12.2(18r)S1 12.2(33)SXJ2 Ok

Is WiSM in Oper-Up status, with an IP? Yes

WHCORE1#sho wism switch 1 module 4 controller 1 status

WiSM Controller 1 in Slot 20 configured with auto-lag

Operational Status of the Controller : Oper-Up
Service VLAN : 192
Service Port : 3
Service Port Mac Address : 0007.7d0a.da61
Service IP Address : 192.168.192.14
Management IP Address : 172.18.50.14
Software Version : 7.0.116.0
Port Channel Number : 695
Allowed-vlan list : 50-56,192,917-919,922
Native VLAN ID : 1
WCP Keep Alive Missed : 0

What port-channel is created for these WLCs? 695

Is the port-channel passing traffic and all ports bundled properly? Yes

WHCORE1#sho etherchannel summary | incl 695

695 Po695(SU) - Te1/4/1(P)

Is your load-balance set to 'src-dst-ip'? Yes

You could try re-issuing your wism allowed/native vlan statements. Sometimes removing and re-creating these can restore connectivity. Tried that still did not work...

WHCORE1#sho run | section include wism

wism service-vlan 192

wism switch 1 module 2 controller 1 allowed-vlan 50-56,192,917-919,922

wism switch 1 module 2 controller 2 allowed-vlan 50-56,192,917-919,922

wism switch 1 module 4 controller 1 allowed-vlan 50-56,192,917-919,922

wism switch 2 module 2 controller 1 allowed-vlan 50-56,192,917-919,922

wism switch 2 module 2 controller 2 allowed-vlan 50-56,192,917-919,922

wism switch 2 module 4 controller 1 allowed-vlan 50-56,192,917-919,922

What status is the WiSM in? Oper-Up

Do the service ports get an IP address (assuming assigned via DHCP)? Service Port has a static IP Address .. I can session into the service port from the chassis.

Service-port, port-channel vlans up/up? Yes

Re: Unable to access WISM2 Management interface from particulart

Can you post the show interface summary from the WiSM in slot 4? 

Management IP Address : 172.18.50.14  this shows it is VLAN 1, is this correct?  IF it is, your allowed vlan list doesn't allow VLAN 1.

Steve

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

Unable to access WISM2 Management interface from particulart slo

(WiSM-slot20-1) >show interface summ

Interface Name                   Port Vlan Id  IP Address      Type    Ap Mgr Guest
-------------------------------- ---- -------- --------------- ------- ------ -----
management                       LAG  50       172.18.50.14    Static  Yes    No
service-port                     N/A  N/A      192.168.192.14  Static  No     No
virtual                          N/A  N/A      1.1.1.1         Static  No     No
whicorp                          LAG  919      172.30.62.14    Dynamic No     No
whidevices                       LAG  917      172.30.15.14    Dynamic No     No
whivoip                          LAG  918      172.30.46.14    Dynamic No     No

New Member

Re: Unable to access WISM2 Management interface from particulart

When I show my interface summary, my mgmt interface is untagged. If I add a native VLAN to my interface I lose connectivity. I would check your other WiSM and see if it's untagged as well.

Re: Unable to access WISM2 Management interface from particulart

Ok, misread that earlier, the PortChannel is native to VLAN 1...

that all looks ok.  You're taggin on the WLC side and not the switch, so we don't have to worry about dropping our own tag.

If this works in another slot, and TAC already RMA'd the chassis, I would next see if a different Sup module would make it work.

Do you have a spare Sup that you can put in slot 5?  Or if you have redundant Sup try to force it to fail over to the redundant one first.

Steve.

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

Unable to access WISM2 Management interface from particulart slo

Yes we have redundant Sup...and have tried failling it over which didn't help either.

Re: Unable to access WISM2 Management interface from particulart

Do you have a spare Sup that you could put in and test?

Steve

Sent from Cisco Technical Support iPad App

HTH, Steve ------------------------------------------------------------------------------------------------ Please remember to rate useful posts, and mark questions as answered
New Member

Unable to access WISM2 Management interface from particulart slo

No we don't we only 2 Sup mods ACTIVE and STANDBY.

New Member

Unable to access WISM2 Management interface from particulart slo

Since everything seems to be isolated to this one slot is it possible that the slot is holding any type of settings other than what is seen from sho run | section include wism? Is it possible view a slot configuration?

1035
Views
0
Helpful
12
Replies