You can monitor your NSX-T Data Center environment using vRealize Operations Manager.

Table 1. Alerts in the Management Pack for NSX-T
Alert Description Recommendation
NSX-T Management service has failed Triggered when the management service on the NSX-T Data Center host is not running. Please log in to the NSX-T Manager and restart the failed management service.
Logical Switch's admin state is not UP Triggered when the admin state is disabled on the logical switch. Please log in to NSX-T and enable the admin state if it is intended so.
Edge Node Controller/Manager Connectivity is not UP Triggered when the edge node connectivity status is down in NSX-T Data Center. Please check the Edge node connection status with Controller Cluster and Manager Cluster and fix the broken connection.
Edge Host node is in Failed/Error state Triggered when the host node in NSX-T Data Center is in error or failed state due to one of the following reasons:
  • Edge configuration error
  • Installation failure
  • Uninstallation failure
  • Upgrade failure
  • Virtual Machine deployment failure
  • Virtual Machine power off failure
  • Virtual Machine power on failure
  • Virtual Machine undeployment failure
Edge host node is in failed/error state, please check the host node state and fix the issue.
BFD service is disabled Triggered when the BFD service is not enabled on the logical router. BFD Service for a TIER0 router is not enabled even though neighbors are configured. Please enable the BFD service if required.
NAT rule not configured Triggered when the NAT rule on the logical router is not configured. Please log in to the NSX-T Manager and add the NAT rules for the Logical Router.
Static Route not configured Triggered when the static route on the logical router is not configured. Please log in to the NSX-T Manager and add the static routes for the Logical Router if required.
Route Advertisement service is disabled Triggered when the route advertisement service is not enabled on the logical router. Route Advertisement service for a TIER1 router is not enabled even though route advertisements are configured, please log in to NSX-T Manager and enable the service.
Route Redistribution service is disabled Triggered when the route redistribution service is not enabled on the logical router. Route Redistribution service for a TIER0 router is not enabled even though route redistribution rules are configured, please log in to NSX-T Manager and enable the service.
ECMP service is disabled for Logical Router Triggered when the ECMP service is not enabled on the logical router. BGP ECMP service for a TIER0 router is not enabled even though neighbors are configured, please log in to NSX-T Manager and enable the service.
Controller Node Connectivity is broken Triggered when the controller node connection status is down in NSX-T Data Center Please log in to NSX-T Manager and check the connectivity of the controller node with Management Node and Controller cluster and resolve the disconnected state.
Less than 3 controller nodes are deployed Triggered when the NSX-T Data Center server has less than three controller nodes. Deploy at least 3 controller nodes in the cluster.
Controller Cluster Status is not stable Triggered when all the controller nodes are down in NSX-T Data Center. Please check the status of controller cluster.
Management Status is not stable Triggered when the status of any node on the management cluster is down. Please check the status of management cluster.
File System usage is more than 85 percent Triggered when the guest file systems usage of the Controller Virtual Machine is more than 85 percent. File system usage is more than 85, please check and clean the File System to make more space.
File System usage is more than 75 percent Triggered when the guest file systems usage of the Controller Virtual Machine is more than 75 percent. File system usage is more than 75, please check and clean the File System to make more space.
File System usage is higher than 70 percent Triggered when the guest file systems usage of the Controller Virtual Machine is more than 70 percent. File system usage is more than 70, please check and clean the File System to make more space.
Edge Cluster Status is down Triggered when edge cluster status is down. Please check the edge cluster status and if required follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Logical Switch State has failed Triggered when the state of logical switch has failed. Please check the logical switch state and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Load Balancer Service operational status down Triggered when the operational status of load balancer service is down. Please check the operational status of load balancer service and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Load balancer service operational status error Triggered when the operational status of load balancer service contains error. Please check the operational status of load balancer service and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Load Balancer virtual server operational state down Triggered when the operational state of load balancer virtual server is down. Please check the operational state of load balancer virtual server and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Load Balancer virtual server operational state detached Triggered when the operational state of load balancer virtual server is detached. Please check the operational state of load balancer virtual server and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Edge node configuration state has failed Triggered when the configuration state of edge node has failed. Please check the configuration state of the edge node and if necessary follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
Management service monitor runtime state has failed Triggered when the monitor runtime state of the management service stops running. Please log in to the NSX-T Manager VA and restart the failed management service.
Management cluster's management status is not stable Triggered when the management status of a management cluster is not stable. Please check the status of management cluster.
Less than 3 manager nodes are deployed Triggered when the NSX-T server has less than three manager nodes deployed. Deploy at least 3 manager nodes in the cluster.
Manager node connectivity is broken Triggered when the manager connection status of manager node is down. Please log in to NSX-T Manager and check the manager connectivity of manager node and follow standard troubleshooting steps recommended by NSX-T documentation and VMware documentation.
File System usage of manager node is more than 85 percent Triggered when the guest file systems usage of the manager node is more than 85 percent. File system usage is more than 85, please check and clean the File System to make more space.
File System usage of manager node is more than 75 percent Triggered when the guest file systems usage of the manager node is more than 75 percent. File system usage is more than 75, please check and clean the File System to make more space.
File System usage of manager node is more than 70 percent Triggered when the guest file systems usage of the manager node is more than 70 percent. File system usage is more than 70, please check and clean the File System to make more space.