Host- ICN IPMI Path

1 Diagnostic Links

Diagnostics >> System Function >> Recon >> VRE Communication Diagnostics

Diagnostics >> Hardware Location >> System Cabinet >> Recon >> VRE Communication Diagnostics

2 Purpose

The purpose of this diagnostic is to verify the IPMI remote communication link from the host to the ICNs. The IPMI interface is used for remote management of the ICNs. This diagnostic uses the VRE configuration file /w/config/vre.cfg that specifies the IP numbers or the ICNs IPMI Ethernet interface.

3 Components Tested

Host eth 1 port, cable, and gigabit switch port
ICNs Ethernet port, LAN card, and IPMI card
ICN IPMI Ethernet cable and gigabit switch port

4 Requirements

The ICNs are turned on and has a network connection from the IPMI Ethernet port to the host.

5 Block Diagrams

6 Test Sequence

Select the Host-ICN IPMI Ethernet Diagnostic from the VRE Communication Diagnostics screen.
Click Run.

note:
Once you click Run, do not click anywhere else in the Common Service Desktop until the test is complete. If you need to abort the test prior to its completion, you must click Stop.
Ensure that the ICN passes the diagnostic by reviewing the status in the Test Results table.

7 Expected Results

This diagnostic can result in a pass or fail. If the diagnostic has failed, please review the error log and corresponding extended error messages for subsequent actions. Additional responses to the diagnostic's results are outlined in Table 1.

Table 1. Diagnostic Results
Result	Description	GE Field Action
Passed	The ICN passed the diagnostic.	No further action required.
Failed	The ICN failed the diagnostic.	Verify the failed ICN has power (it does not need to be running on the OS). note: The ICN is identified by its MAC address label on the back of the ICN. Verify the host to ICN network connectivity for the IPMI Ethernet port furthest left on the back of the ICN. Check to see if the tiny green LED (very indistinct) is lit for the IPMI port. Try swapping either the ICN IPMI to the switch cable, or moving it to a different switch port. Try swapping the host eth 1 port to the switch cable, or moving it to a different port. note: If the host eth 1 port or cable is bad, there will be several diagnostic failures as the entire CAM subnet will be offline.