HP Virtual Connect errors 231
Possible cause 2: Unable to communicate with the module through management interfaces.
Action: Reseat, reboot, or replace the module with one of the same type.
Possible cause 3: If a module reset occurred recently, it might be in this state for a period of time until VCM
can properly communicate with it. If this is the case, then waiting for a few minutes will usually clear the state.
Action: Wait for up to 5 minutes to see if the module recovers from this state.
Possible cause 4: Module reset occurred, but module never recovered from this state because VCM did not
receive an event notification from the OA. This can be caused by a problem with the OA firmware, or a
problem with the module.
Action: Reseat, reboot, or replace module with one of the same type.
Enet uplinkset events (17000-17999)
17012 - Enet uplinkset state FAILED
Severity: CRITICAL
Description: The VC Enet network lost uplink connectivity in the uplink set due to lack of configured ports,
all configured ports are in a bad state, or a bad or incompatible transceiver was inserted.
Possible cause: All the uplink ports in the shared uplink set associated with the network are unlinked or all
uplink ports in a shared uplink set associated with a shared network have been disabled.
Actions:
• Connect the uplink ports.
• Enable the uplink ports in a shared uplink set associated with a shared network.
17014 - Enet uplinkset state is DISABLED
Severity: MAJOR
Description: All ports in the Ethernet uplink port set are administratively disabled.
Possible cause: The speedtype of the ports in the uplink port set might be set to disabled.
Action: Check the speedtype of the ports in the uplink port set and set it to auto-negotiation, or any
appropriate value.
To Next Page
Loading...
Need help?
General
