The table explains system event messages for NSX Edge of major, critical, or high severity. System events with informational severity are listed if such events trigger the alarm.
| Event Code | Event Severity | Alarm Code | Event Message | Description |
|---|---|---|---|---|
| 30011 | High | N/A | None of the NSX Edge VMs found in serving state. There is a possibility of network disruption. | The NSX Edge VMs should recover automatically from this state. Check for a trap with event code 30202 or 30203. Action: See "Edge Appliance Troubleshooting" in the NSX Troubleshooting Guide. |
| 30013 | Critical | 130013 | NSX Manager found NSX Edge VM (vmId : {#}) in bad state. Needs a force sync. | NSX Managerreports that the NSX Edge VM is in a bad state and might not be functioning correctly. Action: An automatic force sync is triggered when a problematic state is detected. If the automatic force sync fails, try a manual force sync. |
| 30014 | Major | N/A | Failed to communicate with the NSX Edge VM. | The NSX Manager communicates with NSX Edge Message Bus. This event indicates that NSX Manager has lost communication with the NSX Edge. Action: See "Edge Appliance Troubleshooting" in the NSX Troubleshooting Guide. |
| 30027 | Informational | 130027 | NSX Edge VM (vmId : {#}) is powered off. | The NSX Edge VM was powered off. Action: Information-only event. |
| 30032 | High | 130032 | NSX Edge appliance with vmId : {#} not found in the vCenter inventory. | The NSX Edge VM was likely deleted directly from vCenter Server. This is not a supported operation as NSX-managed objects must be added or deleted from the vSphere Web Client interface for NSX. Action: Redeploy the edge or deploy a new edge. |
| 30033 | High | 130033 | NSX Edge VM (vmId : {#}) is not responding to NSX manager health check. Please check NSX manager logs for details. | The NSX Edge VM is not responding to the health check sent by the NSX Manager. Action: Make sure that the NSX Edge VM is powered on, and investigate the NSX manager logs. |
| 30034 | Critical | 130034 | None of the NSX Edge VMs found in serving state. There is a possibility of network disruption. | The Edge VM is not responding to the health check sent by the NSX Manager. Action: Confirm the edge VM is powered on. Then collect the edge logs and contact VMware technical support. |
| 30037 | Critical | N/A | Edge firewall rule modified as {#} is no longer available for {#}. | An invalid GroupingObject (IPSet, securityGroup, and so on) is present in the firewall rule. Action: Revisit the firewall rule and make required updates. |
| 30038 | Critical | N/A | Powered-on NSX Edge appliance : {EdgeId #}, {vmName #} violates the virtual machine anti-affinity rule. | NSX Edge High Availability applies anti-affinity rules to vSphere hosts automatically so that the active and standby edge VMs are deployed on different hosts. This event indicates that these anti-affinity rules were removed from the cluster and that both edge VMs are running on the same host. Action: Go to vCenter Server, and verify the anti-affinity rules. |
| 30046 | Critical | N/A | Pre rules publish failed on edge: {EdgeID#}, vm: {#} for generation number {#}. Refer logs for detail. It may need forcesync. | The NSX Edge firewall rules might be out of sync. This error is generated if the pre rules (configured from DFW UI/API) fails. Action: If the problem is not resolved automatically by the built-in recovery process, do a manual force sync. |
| 30100 | Critical | N/A | NSX Edge was force synced. | The NSX Edge VM was force synced. Action: If the force sync does not resolve the problem, collect the technical support logs for NSX Manager and NSX Edge, and contact VMware technical support. |
| 30102 | High | 130102 | NSX Edge (vmId : {IP Address}) is in Bad State. Needs a force sync. | The NSX Edge VM is experiencing an internal error. Action: If the problem is not resolved automatically by the built-in recovery process, try a manual force sync. |
| 30148 | Critical | N/A | NSX Edge CPU usage has increased. {#} Top processes are: {#}. | The NSX Edge VM CPU utilization is high for sustained periods. Action: Refer to "Edge Appliance Troubleshooting" in the NSX Troubleshooting Guide. If the problem persists, collect the technical support logs for NSX Manager and NSX Edge, and contact VMware technical support. |
| 30153 | Major | N/A | AESNI crypto engine is up. | AESNI crypto engine is up. Action: None required. |
| 30154 | Major | N/A | AESNI crypto engine is down. | AESNI crypto engine is down. Action: None required. This status is expected. |
| 30155 | High | 130155 | Insufficient CPU and/or Memory Resources available on Host or Resource Pool, during resource reservation at the time of NSX Edge deployment. |
Insufficient CPU and/or memory resources on host or resource pool. You can view the available resources and reserved resources by navigating to the > page. After checking the available resources, specify the resources as part of appliance configuration again, so that resource reservation limit succeeds. |
| 30157 | Critical | 130157 | NSX Edge (Edge ID} detected duplicate IP {IP address} with macAddress {MAC address}. | An NSX Edge interface IP address is detected on another device on the network. Action: Investigate the network to locate the other device. |
| 30180 | Critical | N/A | NSX Edge is out of memory. The Edge is rebooting in 3 seconds. Top 5 processes are: {#}. | The NSX Edge VM has run out of memory. A reboot was initiated to recover. Action: Refer to "Edge Appliance Troubleshooting" in the NSX Troubleshooting Guide. If the problem persists, collect the technical support logs for NSX Manager and NSX Edge, and contact VMware technical support. |
| 30181 | Critical | 130181 | NSX Edge {EdgeID#} VM name {#} file system is read only. | There is connectivity issue with the storage device backing the NSX Edge VM. Action: Check and correct any connectivity issue with the backing datastore. You might need to execute a manual force sync after the connectivity issue is resolved. |
| 30202 | Major | N/A | NSX Edge {EdgeID#} HighAvailability switch over happened. VM {#} name {#} has moved to ACTIVE state. | An HA failover has occurred, and the secondary NSX Edge VM has transitioned from the STANDBY to ACTIVE state. Action: No action is required. |
| 30203 | Major | N/A | NSX Edge {EdgeID} HighAvailability switch over happened. VM {#} name {#} has moved to STANDBY state. | An HA failover occurred, and the primary NSX Edge VM transitioned from the ACTIVE to STANDBY state. Action: No action is required. |
| 30205 | Critical | 130205 | Split Brain detected for NSX Edge {EdgeID} with HighAvailability. | Due to network failure, NSX Edge VM's configured for HA are unable to determine if the other VM is online. In such a scenario, both the VMs think the other is not online and take on the ACTIVE state. This may cause network disruption. Action : Check network infrastructure (virtual and physical) to look for any failures, specially on the interfaces and the path configured for HA. |
| 30206 | Critical | N/A | Resolved Split Brain for NSX Edge {EdgeID} with HighAvailability. | The two NSX Edge HA appliances are able to communicate with each other and have re-negotiated active and standby status. Action: Refer to "Troubleshooting NSX Edge High Availability (HA) issues: (http://kb.vmware.com/kb/2126560). |
| 30207 | Critical | N/A | Attempted Split Brain resolution for NSX Edge {EdgeID} with count {value}. | The two NSX Edge HA appliances are attempting to re-negotiate and recover from a split brain condition.
Note: : The recovery mechanism reported by this event occurs only in
NSX Edge releases earlier than 6.2.3.
Action: Refer to "Troubleshooting NSX Edge High Availability (HA) issues: (http://kb.vmware.com/kb/2126560). |
| 30302 | Critical | 130302 | LoadBalancer virtualServer/pool : {virtualServerName]} Protocol : {#} serverIp : {IP Address} changed the state to down. | A virtual server or pool on the NSX Edge load balancer is down. Action: Refer to the "Load Balancing" section in the NSX Troubleshooting Guide. |
| 30303 | Major | N/A | LoadBalancer virtualServer/pool : {0} Protocol : {#} serverIp : {IP Address} changed to a wrong state. | A virtual server or pool on the NSX Edge load balancer is experiencing an internal error. Action: Refer to the "Load Balancing" section in the NSX Troubleshooting Guide. |
| 30304 | Major | 130304 | LoadBalancer pool : {0} Protocol : {#} serverIp : {IP address} changed to a warning state. | An NSX Edge load balancer pool changed its state to warning. Action: Refer to the "Load Balancing" section in the NSX Troubleshooting Guide. |
| 30402 | Critical | 130402 | IPsec Channel from localIp : {IP address} to peerIp : {IP address} changed the status to down. | An NSX Edge IPSec VPN channel is down. Action: Refer to the "Virtual Private Networks (VPN)" section in the NSX Troubleshooting Guide. |
| 30404 | Critical | 130404 | IPsec Tunnel from localSubnet : {subnet} to peerSubnet : {subnet} changed the status to down. | An NSX Edge IPSec VPN channel is down. Action: Refer to the "Virtual Private Networks (VPN)" section in the NSX Troubleshooting Guide. |
| 30405 | Major | N/A | IPsec Channel from localIp : {IP address} to peerIp : {IP address} changed the status to unknown. | An NSX Edge IPSec VPN channel's status cannot be determined. Action: Refer to the "Virtual Private Networks (VPN)" section in the NSX Troubleshooting Guide. |
| 30406 | Major | N/A | IPsec Channel from localIp : {IP address} to peerIp : {IP address} changed the status to unknown. | An NSX Edge IPSec VPN channel's status cannot be determined. Action: Refer to the "Virtual Private Networks (VPN)" section in the NSX Troubleshooting Guide. |
| 30701 | Critical | N/A | NSX Edge DHCP Relay service on edge {EdgeID} is disabled because there is no external DHCP server provided. Please check server IP or referenced grouping object. | The NSX Edge DHCP Relay service is disabled. Possible reasons: (1) The DHCP Relay process is not running. (2) There is no external DHCP server. This might be caused by the deletion of grouping object referenced by the relay. Action: See "Configuring DHCP Relay" in the NSX Administration Guide. |
| 30902 | Critical | 130902 | BGP Neighbor {Neighbor ID} is down. | The state of an NSX Edge BGP neighbor has changed to down. Action: Use the Edge CLI to troubleshoot the routing or network condition. |
| 30903 | Critical | 130903 | BGP Neighbor {Neighbor ID} AS Mismatch {AS Number} is not matching. | The autonomous system (AS) number of the BGP neighbor does not match the AS number of the NSX Edge. Action: Make sure that the AS number that you have configured on the BGP neighbor matches the AS number on the NSX Edge. |
| 30905 | Critical | 130905 | OSPF Neighbor is down. Source ip address:{IP address}, routerId: {ID}. | The state of an NSX Edge OSPF neighbor relationship has changed to down. Action: Investigate the network or configuration issue. |
| 30906 | Critical | 130906 | OSPF MTU mismatch. Source routerId:{Router ID}. Configured MTU: {Value}. Source MTU: {Value}. | An NSX Edge OSPF neighbor relationship cannot be established because of MTU mismatch. Action: Check the MTU configured on both OSPF neighbors and make sure that the MTU matches. |
| 30907 | Critical | 130907 | OSPF areaId mismatch. Source routerId:{ID}. Configured areaId: {Value}. Source areaId: {Value}. | An NSX Edge OSPF neighbor relationship cannot be established because of mismatch in the OSPF area ID. Action: Check the area ID configured on both OSPF neighbors and make sure that the area ID matches. |
| 30908 | Critical | 130908 | OSPF helloTimer mismatch. Source routerId:{ID}. Configured helloTimer: {Value}. Source helloTimer: {Value}. | An NSX Edge OSPF neighbor relationship cannot be established because of mismatch in the OSPF hello interval. Action: Check the hello interval configured on both OSPF neighbors and make sure that the hello interval matches. |
| 30909 | Critical | 130909 | OSPF deadTimer mismatch. Source routerId:{ID}. Configured deadTimer: {Value}. Source deadTimer: {Value}. | An NSX Edge OSPF neighbor relationship cannot be established because of mismatch in the OSPF dead interval. Action: Check the dead interval configured on both OSPF neighbors and make sure that the dead interval matches. |
| 31002 | Critical | 131002 | L2VPN tunnel for {user ID} and {server IP} is down. Failure message: {message}. | This event is a client-side event. L2VPN client failed to establish tunnel with the L2VPN server. This event might be due to a misconfiguration issue, or the L2VPN server might not be reachable.
Action: Try one of the following steps to resolve the problem:
|
| 31004 | Critical | 131004 | L2VPN tunnel to {site} is down. Failure message: {message}. | This event is a server-side event and it occurs in the following situations:
Action: Perform the following steps:
|
| 31005 | Critical | 131005 | L2VPN tunnel to {site} with {client IP} got reconnected. | This event is a server-side event and it occurs in the following situations:
Action: No action is required. |
