Onboard Administrator Is Unresponsive; X9000 Rpc Call To Host Failed; Degrade Server Blade/Power Pic; Lun Status Is Failed - HP IBRIX X9720 System Administrator Manual

bonding for additional bandwidth. However, mode 6 bonding is more sensitive to issues in the s
network topology, and has been seen to cause storms of ARP traffic when deployed.

Onboard Administrator is unresponsive

On systems with a flat network, excessive broadcast traffic can cause the OA to be unresponsive.
Note the following:
The OA should be connected to a network with a low level of broadcast traffic. Failure to
follow this guideline can first manifest as timeout errors during installation, can later manifest
as false alerts from monitoring, and in the worst case, can cause the OA to hang.
In rare cases, the OA can become hung when it is overwhelmed by broadcast traffic. This
condition manifests in various errors from monitoring, installation, and IBRIX failover. To recover
proper functionality, manually reseat the OA module or power cycle the C7000. To diagnose
this issue, check the OA's syslog for messages such as the following:
Feb 1 16:41:56 Kernel: Network packet flooding detected. Disabling
network interface for 2 seconds

X9000 RPC call to host failed

In /var/log/messages on a file serving node, you may see messages such as:
ibr_process_status(): Err: RPC call to host=wodao6 failed, error=-651,
func=IDE_FSYNC_prepacked
If you see these messages persistently, contact HP Services as soon as possible. The messages
could indicate possible data loss and can cause I/O errors for applications that access X9000
file systems.

Degrade server blade/Power PIC

After a server blade or motherboard replacement, Insight Manager display on the blade chassis
may show an error message indicating that the power PIC module has outdated or incompatible
firmware. If this occurs, you can update the PIC firmware as follows:
1. Log on to the server.
2. Start hp-ilo:
# service hp-ilo start
3. Flash the power PIC:
# /opt/hp/mxso/firmware/power_pic_scexe
4. Reboot the server.

LUN status is failed

A LUN status of failed indicates that the logical drive has failed. This is usually the result of failure
of three or more disk drives. This can also happen if you remove the wrong disk drive when
replacing a failed disk drive.
If this situation occurs, take the following steps:
1. Carefully record any recent disk removal or reinsertion actions. Make sure you track the array,
box, and bay numbers and know which disk drive was removed or inserted.
2. On X9720 systems, immediately run the following command:
# exds_escalate
This gathers log information that is useful in diagnosing whether the data can be recovered.
Generally, if the failure is due to real disk failures, the data cannot be recovered. However,
if the failure is due to an inadvertent removal of a working disk drive, it may be possible to
restore the LUN to operation.
Troubleshooting specific issues 153