HP Advanced Services zl Module with Microsoft® Windows Server® 2008 R2 Installation and Getting Started Guide

5-11

Troubleshooting

Restore a Module Reported as Failed

In normal operation, the module’s Services Management Agent (SMA) com-

municates with the HP zl switch in which it is installed. The SMA allows you

to access a CLI for the module as well as for the module’s Services OS. It also

enables the module and switch LEDs to report on the module’s status. Finally,

the SMA is required for the software system integrity and licensing verifica-

tion.

If the SMA communications between the module and the switch fail, you will

notice that these functions fail. The module will be reported as faulting, and

you will not be able to access it.

There are two primary reasons for this problem to occur:

 Someone has disabled the module’s internal interface 2.

If the interface has been disabled from the server side, the module should

automatically recover from this problem by reenabling the interface after

30 seconds. However, if the interface has been disabled from the switch

side, you must enabled it manually.

 The module’s WinPcap application, which it uses for the management

connection, is not functioning correctly. This can occur when someone

does not follow the correct procedure for installing (or uninstalling) an

application that uses WinPcap (such as Wireshark).

Result:

A = Interface 1 is up and functioning normally

B = Interface 2 is up and functioning normally

C = Interface 1 is down and unavailable

D = Interface 2 is down and unavailable. The SMA and the module CLI are still available.

E = The CLI is down for less than 30 seconds. Then the SMA brings interface 2 back up (if Hyper-V is in use,

the SMA brings the physical interface 2 back up).

F = The SMA brings the virtual interface 2 back up.

G = You must enable the virtual interface manually.