Enet Module State No_Comm; Enet Module Ip Is - HP ProLiant Gen9 Troubleshooting Manual

Hide thumbs Also See for ProLiant Gen9:
Table of Contents

Advertisement

3023 - Enet Module state NO_COMM

Severity: MAJOR
Description: The VC management application has detected a problem with the communication to the VC-Enet
module.
Possible causes:
Configuration of IP addresses/network topology is preventing communication between the primary
VC-Enet module and the identified VC-Enet module.
An unexpected error has occurred while sending a configuration update to the module or while
requesting status information from the module. This error may be due to TCP/IP communications
interruption/timeout or due to a software generated failure.
The primary VC-Enet module is unable to exchange network packets with the indicated module. This
inability can occur if the Onboard Administrator has configured the internal switch that connects the
I/O modules inappropriately.
Action:
Verify that the network configuration (IP address, topology, etc.) is correct. If the module is in a remote
enclosure (not located in the same enclosure as the primary VC-Enet module), reset or reboot the Active
Onboard Administrator in the remote enclosure.
Verify that the OA Enclosure Bay IP Addressing (EBIPA) is either disabled or is providing the correct
information to each module.

3031 - Enet Module IP is 0.0.0.0

Severity: MAJOR
Description: The OA is reporting that an Ethernet module does not have an IP address. The module will be
marked as NO-COMM.
Possible causes:
The external DHCP server did not provide the module with an IP address.
There is a networking issue with the DHCP server.
There is an IO Module or Onboard Administrator hardware or software issue.
Action:
Verify the OA is set up to provide a specific IP address.
Verify an external DHCP server is available on the management network.
3101 - Port is disabled as network loop is detected
Severity: MAJOR
Description: Because a network loop was detected on an Ethernet port, it has been disabled to avoid further
service degradation.
Possible cause 1: More than one active uplink port or uplink Link Aggregation Group (LAG) from an uplink
set has been assigned to the same network from the Virtual Connect domain to the external Ethernet switching
environment, causing a network loop.
HP Virtual Connect errors 223

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents