Aruba & ProVision-based
1752644 Members
5883 Online
108788 Solutions
New Discussion юеВ

J9051A is "booted" but not "running".

 
Russ-HLC
Occasional Visitor

J9051A is "booted" but not "running".

We have a J9051A wireless module in our Procurve 5406zl chassis.

Followinga reboot on Monday, we have no wireless, but card appears to be running :-

LRC-GF-CORE1# show wireless-services e

Status and Counters - Wireless Services Module E Status

HP Wireless Services ZL Module J9051A

Versions : A.01.05
Current status : booted
Uplink MAC address : 001c2e-e3d79e

For more information, use the show commands in wireless-services context.

Commands such as 

LRC-GF-CORE1# show wireless-services e

Status and Counters - Wireless Services Module E Status

HP Wireless Services ZL Module J9051A

Versions : A.01.05
Current status : booted
Uplink MAC address : 001c2e-e3d79e

For more information, use the show commands in wireless-services context

This suggests the wireless config is ok.

 

Any idea how we can get the module to a "running" state ?

Russ.

 

2 REPLIES 2
parnassus
Honored Contributor

Re: J9051A is "booted" but not "running".

Interesting, since the module sends messages to the zl switch's Event Log [*]...what you see in switch's Event Log (use the show logging command)?

Did you tested a reload (via CLI) or an orderly shutdown (via the Shutdown Module recessed push button for more than 2 seconds) of your HP Wireless Edge Services zl Module (J9051A) module?

Which software version is currently running (use the show flash, show version and show modules commands) your HP ProCurve 5406 zl Switch?

[*] Messages related to J9051A should show up in the form of:

<severity code> <date stamp> <time stamp> <number> wsm <slot-id>: message
<severity code> <date stamp> <time stamp> <number> HPESP: message

Where message is the specific message logged.


I'm not an HPE Employee
Kudos and Accepted Solution banner
Russ-HLC
Occasional Visitor

Re: J9051A is "booted" but not "running".

We have managed to bring it back to life, but it had lost its config. We are now working again.

To get it working we :-

Removed J9051A from Core Switch.

Rebooted Core Switch

Inserted J9051A back into Core Switch.

 

( Restarting with the J9051A installed was not enough )