Alert definitions are combinations of symptoms and recommendations that identify problem areas in your environment and generate alerts on which you can act. You can import all NSX alerts into VMware Aria Operations, allowing the users to manage and monitor these alerts from a single location. This integration between NSX and VMware Aria Operations improves overall visibility and simplifies operations, making it easier to identify and address issues.
You can directly import alerts from VMware NSX (formerly known as VMware NSX-T) into VMware Aria Operations by setting the Import Alerts from NSX field to True while configuring the NSX adapter instance. For details, see the topic 'Configuring the NSX Adapter' in the VMware Aria Operations Configuration Guide.
Depending on the number of alerts and the system's performance, importing the alerts into
VMware Aria Operations may take some time.
Note: Importing alerts is not supported for NSX Integration through VMware Cloud on AWS.
Existing Out-of-the-Box NSX Alerts
| Alert | Description |
|---|---|
| BFD service is disabled | Triggered when the BFD service is not enabled on the logical router. |
| Controller Cluster Status is not stable | Triggered when all the controller nodes are down in NSX. |
| Controller Node Connectivity is broken | Triggered when the controller node connection status is down in NSX. |
| ECMP service is disabled for Logical Router | Triggered when the ECMP service is not enabled on the logical router. |
| 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 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 85 percent | Triggered when the guest file systems usage of the Controller Virtual Machine is more than 85 percent. |
| 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 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 of manager node is more than 85 percent | Triggered when the guest file systems usage of the manager node is more than 85 percent. |
| Less than 3 controller nodes are deployed | Triggered when the NSX server has less than three controller nodes. |
| Less than 3 manager nodes are deployed | Triggered when NSX server has less than 3 manager nodes deployed. |
| Load Balancer Service operational status down | Triggered when the operational status of the load balancer service is down. |
| Load balancer service operational status error | Triggered when the operational status of the load balancer service contains error. |
| Load Balancer virtual server operational state detached | Triggered when the operational state of the load balancer virtual server is detached |
| Load Balancer virtual server operational state down | Triggered when the operational state of the load balancer virtual server is down |
| Logical Switch State has failed | Triggered when the state of logical switch has failed. |
| Logical Switch's admin state is not UP | Triggered when the admin state is disabled on the logical switch. |
| Management cluster's management status is not stable | Triggered when the management status of a management cluster is not stable. |
| Management service monitor runtime state has failed | Triggered when the monitor runtime state of the management service stops running. |
| Management Status is not stable | Triggered when the management status of any node on the controller cluster is down. |
| Manager node connectivity is broken | Triggered when the manager connection status of manager node is down. |
| NAT rule not configured | Triggered when the NAT rule on the logical router is not configured. |
| NSX Management service has failed | Triggered when the runtime state of management service on the NSX host is not running. |
| NTP Service is violating VMware NSX Security Configuration Guide | NTP Service is violating one or more guidelines in VMware NSX Security Configuration Guide |
| Route Advertisement service is disabled | Triggered when the route advertisement service is not enabled on the logical router. |
| Route Redistribution service is disabled | Triggered when the route redistribution service is not enabled on the logical router. |
| SSH Service is violating VMware NSX Security Configuration Guide | SSH Service is violating one or more guidelines in VMware NSX Security Configuration Guide |
| Static Route not configured | Triggered when the static route on the logical router is not configured. |
| Transport Host node is in Failed/Error state | Triggered when the host node in NSX is in error or failed state due to one of the following reasons:
|
| Transport node configuration state has failed | Triggered when the configuration state of transport node has failed. |
| Transport Node Controller/Manager Connectivity is not UP | Triggered when the transport node connectivity status is down in NSX. |
For details on VMware NSX alerts that can be imported into VMware Aria Operations, refer to the VMware NSX Event Catalog.
