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. And see here for current known issues.

Wism Module Controller 2 not detect IP Address

Hi, im badrul..i got one problem regarding the wism module controller. as we know in wism module have 2 controller, controller 1 and controller 2. i try to configure that wism module. but only controller 1 can used. for controller 2, it not detect the IP address that assign by DHCP. i try direct console on console port 2 on wism module, but it not detect console also. so i need help from who expert on this matter to soft my problem.

11 REPLIES

Re: Wism Module Controller 2 not detect IP Address

Badrul,

Please issue the following commands on your 6500 CLI and post the output in a reply. Where you see , replace with the module/slot number where you have installed your wism.

show module


show wism status

show wism mod  cont 1 status

show wism mod  cont 2 status


Justin

Wism Module Controller 2 not detect IP Address

Thanks Justin on your respond

here the commands :

sh module

Mod Ports Card Type                              Model              Serial No.

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

  1   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1329U59V

  3    6  Firewall Module                        WS-SVC-FWM-1       SAD1311014S

  4    8  Intrusion Detection System             WS-SVC-IDSM-2      SAD124101TB

  7    2  Supervisor Engine 720 (Active)         WS-SUP720-3B       SAL1326T4VZ

  9   10  WiSM WLAN Service Module               WS-SVC-WISM-1-K9   SAD132500BX

10    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL15108PHU

11    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL1329U9DC

12    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL1416FNEH

13    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL1517CGRF

Mod MAC addresses                       Hw    Fw           Sw           Status

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

  1  0026.0b5b.46b4 to 0026.0b5b.46cb   4.1   12.2(18r)S1  12.2(33)SXH5 Ok

  3  0021.a082.b420 to 0021.a082.b427   4.5   7.2(1)       4.0(4)       Ok

  4  0021.d869.d4e0 to 0021.d869.d4e7   6.4   7.2(1)       5.0(2)       Ok

  7  0024.1499.51d8 to 0024.1499.51db   5.9   8.5(3)       12.2(33)SXH5 Ok

  9  0024.9774.2344 to 0024.9774.2353   2.3   12.2(14r)S5  12.2(33)SXH5 Ok

10  c89c.1d2f.5a78 to c89c.1d2f.5a7f   2.3   12.2(18r)S1  12.2(33)SXH5 Ok

11  0026.0b5b.4694 to 0026.0b5b.4697   2.9   12.2(14r)S5  12.2(33)SXH5 Ok

12  8843.e11b.4eb0 to 8843.e11b.4eb3   3.1   12.2(14r)S5  12.2(33)SXH5 Ok

13  e05f.b974.e7d0 to e05f.b974.e7d7   2.3   12.2(18r)S1  12.2(33)SXH5 Ok

Mod  Sub-Module                  Model              Serial       Hw     Status

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

  1  Centralized Forwarding Card WS-F6700-CFC       SAL1329U27Q  4.1    Ok

  4  IDS 2 accelerator board     WS-SVC-IDSUPG      CFBG8260009  2.5    Ok

  7  Policy Feature Card 3       WS-F6K-PFC3B       SAL1326SS36  2.5    Ok

  7  MSFC3 Daughterboard         WS-SUP720          SAL1326T1EZ  4.0    Ok

  9  Centralized Forwarding Card WS-SVC-WISM-1-K9-D SAD1324048G  2.1    Ok

10  Distributed Forwarding Card WS-F6700-DFC3C     SAL1516C139  1.4    Ok

11  Centralized Forwarding Card WS-F6700-CFC       SAL1327TF1L  4.1    Ok

12  Centralized Forwarding Card WS-F6700-CFC       SAL1414EZAX  4.1    Ok

13  Distributed Forwarding Card WS-F6700-DFC3C     SAL1517CHK1  1.4    Ok

Mod  Online Diag Status

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

  1  Pass

  3  Pass

  4  Pass

  7  Pass

  9  Pass

10  Pass

11  Pass

12  Pass

13  Pass

show wism status

Service Vlan : 900, Service IP Subnet : 20.20.10.254/255.255.255.0

      WLAN

Slot  Controller  Service IP       Management IP    SW Version  Status

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

9     1           20.20.10.1          172.28.40.11         5.2.178.0      Oper-Up

9     2           0.0.0.0                0.0.0.0                                     Service Port Up

show wism module 9 controller 1 status

WiSM Controller 1 in Slot 9 configured with auto-lag

Operational Status of the Controller : Oper-Up

Service VLAN                         : 900

Service Port                            : 9

Service Port Mac Address        : 0025.84a9.a062

Service IP Address                  : 20.20.10.1

Management IP Address          : 172.28.40.11

Software Version                      : 5.2.178.0

Port Channel Number               : 417

Allowed-vlan list                       : 8,15,19,31,40-41,44,50-51,200,208,212,800,900

Native VLAN ID                        : 900

WCP Keep Alive Missed           : 0

show wism module 9 controller 2 status

WiSM Controller 2 in Slot 9 configured with auto-lag

Operational Status of the Controller : Service Port Up

Service VLAN                          : 900

Service Port                             : 10

Service Port Mac Address         : 0025.84ba.08a2

Service IP Address                   : 0.0.0.0

Management IP Address           : 0.0.0.0

Software Version                       :

Port Channel Number                : 418

Allowed-vlan list                        : 8,15,19,31,40-41,50-51,200,208,212,800,900

Native VLAN ID                         : 900

WCP Keep Alive Missed            : 0

TQ again Justin...

Re: Wism Module Controller 2 not detect IP Address

Muhamad,

Thanks for posting your output.

Here are some quick observations:

  • I saw a similar issue once before, including getting no response from the console port on controller 2 and I think it may have something to do with the auto-configuration of the wism controllers and possibly the 5.2 revision of code. I didn't troubleshoot long enough to figure it out, but I was able to fix the issue, so I'll outline the procedure for you below. Hopefully it will help you.

  • I noticed that you have VLAN 900 on your wism portchannels, and because 900 is also your service VLAN, you do not (and should not) put it on the portchannels. Only the service ports need to be on VLAN 900. Also in this vein, you do not need to declare 900 as your native vlan on the controllers, and if your controller management interfaces are going to be in one of VLANs 8,15,19,31,40-41,44,50-51,200,208,212, or 800, then you do not need any native VLAN declared. You only need the native VLAN if you are going to leave your management VLAN ID tag at 0 (default).

  • Finally, and this is likely unrelated to your problem, but you are missing VLAN 44 on the controller 2 wism portchannel. If you want the same VLANs allowed on both wism controllers then be sure to correct the missing VLAN:

show wism module 9 controller 1 status

...

Allowed-vlan list                       : 8,15,19,31,40-41,44,50-51,200,208,212,800,900

show wism module 9 controller 2 status

...

Allowed-vlan list                        : 8,15,19,31,40-41,50-51,200,208,212,800,900

  • NOTE: You cannot have the controller management interface IPs and the service-port IPs in the same subnets.

OK, to try to recover from the unreachable wism controller 2 issue, try these steps:

1. Connect a console cable to the console port on wism controller 2 and start your console application

2. Separately, ssh/telnet to your 6500 (or on a console on another machine) and issue the command hw-module module 9 reset

... This will initiate a soft reload of the entire wism module

3. On your console, watch for your wism controller 2 to boot. When you see the the autoconfigure prompts, choose to exit autoconfiguration.

4. You should now be able to run through a basic setup wizard. Set the Service-Port config to DHCP (this should be the default).

5. When prompted to save and reboot, choose YES and this time around, you should see the controller come up and you will hopefully see that the service-port gets an IP

If you never see the wism controller 2 boot, then you may have a failed controller, so the next step may need to be a call into TAC.

Justin

Wism Module Controller 2 not detect IP Address

thank you justin...

because willing help me to solve my problem and sharing  your knowledge and skills. however, i'm not use yet your way to  troubleshoot actually, because, after you give me the way to  troubleshoot this matter, i try tu put console cable on console  port controller 2, and then it display a basic setup. so, i'm just put the info that needed. and then service port  interface was got the IP Address. and controller 2 can be used now.

thanks again justin..

Wism Module Controller 2 not detect IP Address

Muhamad,

I'm glad to hear that your wism is alive.

When you get a chance, can you mark this question as answered for the benefit of future searchers?

Thanks!

Justin

New Member

Wism Module Controller 2 not detect IP Address

Justin,

Thanks for the good info. your explanation fixed my problem!

Re: Wism Module Controller 2 not detect IP Address

hope anyone can help me again..

ok, i already install wism controller 1 and controller 2 and all connection is up. i want to move a AP in controller 1 to controller 2, i already set that AP use controller 2 as primary controler , and then i reset the AP. the problem is, the AP cannot move to controller 2 and in the same time its not in controller 1 also.

so, what the problem actually and how to solve this promlem?.

TQ

Re: Wism Module Controller 2 not detect IP Address

When you use the high availability, you need to make sure you use the controller name and ip address. Did you double check they are correct ?

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

Re: Wism Module Controller 2 not detect IP Address

thanks george...i did double check, i try again with another AP, move to controller 2 with set high availability, the problem still the same...

Re: Wism Module Controller 2 not detect IP Address

Is controller 1 and controller 2 in the same mobility group ? Is there an ACL anywhere that might prevent them AP moves?

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

Re: Wism Module Controller 2 not detect IP Address

Yes..already set in the same mobility group...but still cannot move...

2700
Views
10
Helpful
11
Replies
CreatePlease login to create content