Alert Message in
Alert Message in
VxFlex OS GUI
REST
Unable to connect
NODE_FAILED_TO_CO
to monitoring agent
NNECT_TO_ESX
(ESX)
Unable to connect
NODE_FAILED_TO_CO
to monitoring agent
NNECT_TO_HOST
(host)
Unable to connect
NODE_FAILED_TO_CO
to monitoring agent
NNECT_TO_VCENTER
(VCenter)
Node serial number
NODE_SERIAL_NUMBE
has changed
R_CHANGE
Table 34 VxFlex OS Alerts in SNMP, VxFlex OS GUI, REST, and ESRS (continued)
Alert
Message in
SNMP Trap
Node.Node.FAI
LED_TO_CON
NECT_TO_ESX
Node.Node.FAI
LED_TO_CON
NECT_TO_HO
ST
Node.Node.FAI
LED_TO_CON
NECT_TOVCE
NTER
Node.Node.SE
RIAL_NUMBER
_CHANGE
Alert Code
Severity
(for ESRS)
SIO07.05.000
5 (Critical)
0007
SIO07.05.000
5 (Critical)
0007
SIO07.05.000
5 (Critical)
0008
SIO07.05.000
3 (Error)
0009
Dell EMC VxFlex Ready Node AMS User Guide
SNMP Trap Support
Recommended Action
vCenter and try to open the
SSH or the console to it.
Then check the message
log for errors.
The ESX IP address or User
credentials do not respond
to AMS queries. Check the
ESX state in vCenter and
try to open the SSH or the
console (via BMC http) to
it. Then check the
messages log for errors.
The ESX IP address or User
credentials do not respond
to AMS queries. Check the
ESX state in vCenter and
try to open the SSH or the
console (via BMC http) to
it. Then check the
messages log for errors.
Ensure that the vCenter
configuration is correct,
and ensure that the node's
Mgmt port is routable to
the vCenter IP address
The S/N of the
Motherboard does not
match the IP address of the
ESX. Either the SATADOM
was moved to a new server
or the motherboard was
replaced. It is also possible
that a new server that has
the same IP addresses and
the same user and
password, but was not
installed using the AMS
flow, exists in the network.
EMC does not support such
field replacement cases.
Such cases should be
solved by replacing nodes
using EMC-recommended
procedures. For more
information, contact
Customer Support.
309