EasyManuals Logo

HP ProLiant Gen9 User Manual

HP ProLiant Gen9
410 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #225 background imageLoading...
Page #225 background image
HP Virtual Connect errors 225
Description: The Fibre Channel module in this interconnect bay is incompatible with the VCM domain.
Possible causes:
• The module is running outdated FW. It might be running either an older or newer version than Virtual
Connect manager expects.
• The module is not compatible with a module running in an adjacent bay in either double-dense or
single-dense mode.
• The module is not compatible with another module in the same bay group for multi-enclosure or
double-dense mode.
Action: Replace the module with a module type that is compatible with the bay group of the VC domain. In
the case of an incorrect FW revision, update the module to the correct FW revision.
4019 - FC Module State is NO_COMM
Severity: MAJOR
Description: The Virtual Connect Manager is unable to communicate with the FC module.
Possible causes:
• The VC-FC module is rebooting after a FW panic and is not responding to VCM commands.
• The VC-FC module is not responding to ISMIC commands due to a FW defect.
• The VC-FC module fails to start the DHCP client due to a FW defect and therefore does not respond to
commands from VCM to provide the switch configuration, including the FW revision number.
• The VC-FC module never obtains an IP address through DHCP and therefore does not respond to VCM
commands.
• The VC-FC module never sends a COMM_OK OA event after a FW reboot due to a FW defect or
hardware problem.
Action: Make sure that the DHCP server is running and correctly assigning addresses. In case of a transient
error, power cycle the module to see if communication is restored. A support dump of the VC-FC module
needs to be analyzed to determine the basic cause of the problem. The module might need to be replaced.
Server events (5000-5999)
5009 - Server OA fault event
Severity: MAJOR
Description: The Virtual Connect Manager has received a Blade Fault event from the OA.
Possible cause: The server hardware has failed.
Actions:
• Verify the communication between VC and the Onboard Administrator for the affected server is
operational.
• Verify the server is in a good state.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the HP ProLiant Gen9 and is the answer not in the manual?

HP ProLiant Gen9 Specifications

General IconGeneral
Product LineProLiant
GenerationGen9
ChipsetIntel C610 series
Expansion SlotsPCIe 3.0
StorageSATA, SAS, SSD
Network1GbE, 10GbE
ManagementHP iLO (Integrated Lights-Out)
Power SupplyFlexible slot, hot-plug power supplies
Form FactorRack, Tower, Blade
ProcessorIntel Xeon E5-2600 v3/v4 series
RAIDHP Smart Array controllers

Related product manuals