cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
629
Views
0
Helpful
6
Replies

WISM Slot2 is not reachable via management ip

Martin H
Level 1
Level 1

Hello everybody,

WISM 1 Slot 2 is not reachable via its management ip address.

Only via service ip reachable.

(WiSM-slot28-2) >show logging
*nim_t: Jul 06 07:47:23.087: %SIM-3-PORT_UP: sim.c:9982 Physical port 4is up!.
*nim_t: Jul 06 07:47:23.084: %SIM-3-PORT_UP: sim.c:9982 Physical port 3 is up!.
*nim_t: Jul 06 07:47:23.082: %SIM-3-PORT_UP: sim.c:9982 Physical port 2 is up!.
*nim_t: Jul 06 07:47:23.079: %SIM-3-PORT_UP: sim.c:9982 Physical port 1 is up!.
*sshpmMainTask: Jul 06 07:47:22.955: %SSHPM-3-IN_WCP_CONFIGURED: sshpmrules.c:2199 Inbound WCP rule already configured
*fp_main_task: Jul 06 07:47:22.858: %CNFGR-3-INV_COMP_ID: cnfgr.c:2221 Invalid Component Id : Unrecognized (77) in cfgConfiguratorInit.
*fp_main_task: Jul 06 07:47:22.769: %LOG-3-Q_IND: rrmCfg.c:1501 RRM LOG: Airewave Director: Configuration has been sanitized -- save configuration to commit
*fp_main_task: Jul 06 07:47:22.562: %RRM-3-RRM_LOGMSG: rrmCfg.c:1501 RRM LOG: Airewave Director: Configuration has been sanitized -- save configuration to commit
*fp_main_task: Jul 06 07:47:16.797: %MM-3-MEMBER_ADD_FAILED: mm_dir.c:926 Could not add Mobility Member. Reason: IP already assigned, Member-Count:1,MAC: 00:00:00:00:00:00, IP: 0.0.0.0
*fp_main_task: Jul 06 07:47:16.588: %DTL-3-DSNET_CONF_FAILED: dtl_ds.c:424 Unable to set symmetric mobility tunneling to disabled on Distribution Service interface.
*fp_main_task: Jul 06 07:47:01.575: %CNFGR-3-INV_COMP_ID: cnfgr.c:2221 Invalid Component Id : Unrecognized (36) in cfgConfiguratorInit.
*mfpKeyRefreshTask: Jul 06 07:47:01.574: %SSHPM-3-NOT_INIT: bsnrandom.c:636 Random context not initialized

NW-SW0-1#show wism status
Service Vlan : 323, Service IP Subnet : 10.243.123.1/255.255.255.240
WLAN
Slot Controller Service IP Management IP SW Version Status
----+-----------+----------------+----------------+-----------+---------------
28 1 10.243.123.7 10.243.48.11 7.0.240.0 Oper-Up
28 2 10.243.123.8 10.243.48.12 7.0.240.0 Oper-Up
41 1 10.243.123.9 10.243.48.13 7.0.240.0 Oper-Up
41 2 10.243.123.10 10.243.48.14 7.0.240.0 Oper-Up

Reboot done, same problem.

Any ideas?

Thanks a lot & Best Reagrds

Martin

1 Accepted Solution

Accepted Solutions

 What does your switch port configuration look like up to the box. 

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

View solution in original post

6 Replies 6

Leo Laohoo
Hall of Fame
Hall of Fame

What happens if you try to get in using the Service Port:  session slot <X> processor 1

 What does your switch port configuration look like up to the box. 

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

Hi George,

I dont think, the Problem is the Port Konfiguration-  but I can check.

Management is untagged at all WISMs.

There are 4 WISM Slots and 3 of them work well.

Interessting thing:

The first "problem" was -> Accesss Points have connection problem with this wism slot.

Then reboot this slot via GUI Management IP. After, the management IP is no longer available.

Thanks and Best Regards,

Martin

Ports was in suspended mode

You good now?

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

Hi Leo,

when I try to connect to Service Port - it works.

BR, Martin

Review Cisco Networking for a $25 gift card