VMWARE-NSX-MIB
VMware Inc.In much the same way that server virtualization programmatically creates, snapshots, deletes, and restores software-based virtual machines (VMs), NSX Data Center network virtualization programmatically creates, deletes, and restores software-based virtual networks. With network virtualization, the functional equivalent of a network hypervisor reproduces the complete set of Layer 2 through Layer 7 networking services (for example, switching, routing, access control, firewalling, QoS) in software. As a result, these services can be programmatically assembled in any arbitrary combination, to produce unique, isolated virtual networks in a matter of seconds. For more information about NSX Data Center, please visit: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/
snmptranslate -m VMWARE-NSX-MIB -Tpsnmpwalk -v2c -c <community> -m VMWARE-NSX-MIB <host> 1.3.6.1.4.1.6876.120.1Imports
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
|---|---|
| SNMPv2-SMI | Bits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso |
| SNMPv2-TC | DateAndTime, DisplayString, PhysAddress, TEXTUAL-CONVENTION |
| VMWARE-ROOT-MIB | vmwNSXsys |
OID tree
| Name | OID | Type | Access | Status |
|---|---|---|---|---|
| IvmwNSXsysMIB | 1.3.6.1.4.1.6876.120.1 | |||
identity In much the same way that server virtualization programmatically creates, snapshots, deletes, and restores software-based virtual machines (VMs), NSX Data Center network virtualization programmatically creates, deletes, and restores software-based virtual networks. With network virtualization, the functional equivalent of a network hypervisor reproduces the complete set of Layer 2 through Layer 7 networking services (for example, switching, routing, access control, firewalling, QoS) in software. As a result, these services can be programmatically assembled in any arbitrary combination, to produce unique, isolated virtual networks in a matter of seconds. For more information about NSX Data Center, please visit: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/ | ||||
| NvmwNsxTDataCenterNotifications | 1.3.6.1.4.1.6876.120.1.0 | |||
node · current All event notifications from NSX Data Center fall under this oid. | ||||
| NvmwNsxTManagerHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.1 | |||
node · current Notifications applicable to the ManagerHealth feature have this OID prefix. | ||||
| NvmwNsxTManagerHealthFeature | 1.3.6.1.4.1.6876.120.1.0.1.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for ManagerHealth feature notifications. | ||||
| !vmwNsxTManagerHealthManagerCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.1 | |||
notification · current The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Manager node. Consider adjusting the Manager appliance form factor size. | ||||
| !vmwNsxTManagerHealthManagerCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.2 | |||
notification · current The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthManagerCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.3 | |||
notification · current The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Manager node. Consider adjusting the Manager appliance form factor size. | ||||
| !vmwNsxTManagerHealthManagerCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.4 | |||
notification · current The CPU usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthManagerMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.5 | |||
notification · current The memory usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Manager node. Consider adjusting the Manager appliance form factor size. | ||||
| !vmwNsxTManagerHealthManagerMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.6 | |||
notification · current The memory usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthManagerMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.7 | |||
notification · current The memory usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Manager node. Consider adjusting the Manager appliance form factor size. | ||||
| !vmwNsxTManagerHealthManagerMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.8 | |||
notification · current The memory usage on Manager node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthManagerDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.9 | |||
notification · current The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine the partition with high usage and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTManagerHealthManagerDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.10 | |||
notification · current The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTManagerHealthManagerDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.11 | |||
notification · current The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine the partition with high usage and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTManagerHealthManagerDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.12 | |||
notification · current The disk usage for the Manager node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTManagerHealthManagerConfigDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.13 | |||
notification · current The disk usage for the Manager node disk partition /config has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of rising disk usage by the NSX Datastore service under the /config/corfu directory. Action required: Run the following tool and contact GSS if any issues are reported /opt/vmware/tools/support/inspect_checkpoint_issues.py | ||||
| !vmwNsxTManagerHealthManagerConfigDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.14 | |||
notification · current The disk usage for the Manager node disk partition /config has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthManagerConfigDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.15 | |||
notification · current The disk usage for the Manager node disk partition /config has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of high disk usage by the NSX Datastore service under the /config/corfu directory. Action required: Run the following tool and contact GSS if any issues are reported /opt/vmware/tools/support/inspect_checkpoint_issues.py | ||||
| !vmwNsxTManagerHealthManagerConfigDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.16 | |||
notification · current The disk usage for the Manager node disk partition /config has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthDuplicateIPAddress | 1.3.6.1.4.1.6876.120.1.0.1.0.17 | |||
notification · current Manager node vmwNsxTDataCenterEntityId IP address vmwNsxTDataCenterDuplicateIPAddress is currently being used by another device in the network. Action required: 1. Determine which device is using the Manager's IP address and assign the device a new IP address. Note, reconfiguring the Manager to use a new IP address is not supported. 2. Ensure the static IP address pool/DHCP server is configured correctly. 3. Correct the IP address of the device if it is manually assigned. | ||||
| !vmwNsxTManagerHealthDuplicateIPAddressClear | 1.3.6.1.4.1.6876.120.1.0.1.0.18 | |||
notification · current The device using the IP address assigned to Manager node vmwNsxTDataCenterEntityId appears to no longer be using vmwNsxTDataCenterDuplicateIPAddress. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthOperationsDbDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.19 | |||
notification · current The disk usage for the Manager node disk partition /nonconfig has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of rising disk usage by the NSX Datastore service under the /nonconfig/corfu directory. Action required: run the following tool and contact GSS if any issues are reported /opt/vmware/tools/support/inspect_checkpoint_issues.py --nonconfig | ||||
| !vmwNsxTManagerHealthOperationsDbDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.20 | |||
notification · current The disk usage for the Manager node disk partition /nonconfig has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthOperationsDbDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.1.0.21 | |||
notification · current The disk usage for the Manager node disk partition /nonconfig has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. This can be an indication of high disk usage by the NSX Datastore service under the /nonconfig/corfu directory. Action required: Run the following tool and contact GSS if any issues are reported /opt/vmware/tools/support/inspect_checkpoint_issues.py --nonconfig | ||||
| !vmwNsxTManagerHealthOperationsDbDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.1.0.22 | |||
notification · current The disk usage for the Manager node disk partition /nonconfig has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthStorageError | 1.3.6.1.4.1.6876.120.1.0.1.0.23 | |||
notification · current The following disk partition on the Manager node vmwNsxTDataCenterEntityId is in read-only mode: vmwNsxTDataCenterDiskPartitionName Action required: Examine the read-only partition to see if reboot resolves the issue or the disk needs to be replaced. Contact GSS for more information. | ||||
| !vmwNsxTManagerHealthStorageErrorClear | 1.3.6.1.4.1.6876.120.1.0.1.0.24 | |||
notification · current The following disk partition on the Manager node vmwNsxTDataCenterEntityId has recovered from read-only mode: vmwNsxTDataCenterDiskPartitionName Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthMissingDNSEntryForManagerFQDN | 1.3.6.1.4.1.6876.120.1.0.1.0.28 | |||
notification · current The DNS configuration for Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterEntityId) is incorrect. The Manager node is dual-stack and/or CA-signed API certificate is used, but the IP address(es) of the Manager node do not resolve to an FQDN or resolve to different FQDNs. Action required: 1. Ensure proper DNS servers are configured in the Manager node. 2. Ensure proper A records and PTR records are configured in the DNS servers such that reverse lookup of the IP addresses of the Manager node return the same FQDN, and forward lookup of the FQDN return all IP addresses of the Manager node. 3. Alternatively, if the Manager node is not dual-stack, replace the CA-signed certificate for API service type with a self-signed certificate. | ||||
| !vmwNsxTManagerHealthMissingDNSEntryForManagerFQDNClear | 1.3.6.1.4.1.6876.120.1.0.1.0.29 | |||
notification · current The DNS configuration for Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterEntityId) is correct. Either the Manager node is not dual-stack and CA-signed API certificate is no longer used, or the IP address(es) of the Manager node resolve to the same FQDN. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTManagerHealthMissingDNSEntryForVipFQDN | 1.3.6.1.4.1.6876.120.1.0.1.0.33 | |||
notification · current In case of dual stack or CA-signed API certificate for a NSX Manager, virtual IPv4 address vmwNsxTDataCenterIPv4Address and virtual IPv6 address vmwNsxTDataCenterIPv6Address for Manager node vmwNsxTDataCenterEntityId should resolve to the same FQDN. Action required: Examine the DNS entry for the VIP addresses to see if they resolve to the same FQDN. | ||||
| !vmwNsxTManagerHealthMissingDNSEntryForVipFQDNClear | 1.3.6.1.4.1.6876.120.1.0.1.0.34 | |||
notification · current Dual stack VIP addresses for Manager node vmwNsxTDataCenterEntityId resolved to same FQDN. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTEdgeHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.2 | |||
node · current Notifications applicable to the EdgeHealth feature have this OID prefix. | ||||
| NvmwNsxTEdgeHealthFeature | 1.3.6.1.4.1.6876.120.1.0.2.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for EdgeHealth feature notifications. | ||||
| !vmwNsxTEdgeHealthEdgeCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.1 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Edge node. Consider adjusting the Edge appliance form factor size or rebalancing services to other Edge nodes for the applicable workload. | ||||
| !vmwNsxTEdgeHealthEdgeCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.2 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.3 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Edge node. Consider adjusting the Edge appliance form factor size or rebalancing services to other Edge nodes for the applicable workload. | ||||
| !vmwNsxTEdgeHealthEdgeCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.4 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.5 | |||
notification · current The memory usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Edge node. Consider adjusting the Edge appliance form factor size or rebalancing services to other Edge nodes for the applicable workload. | ||||
| !vmwNsxTEdgeHealthEdgeMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.6 | |||
notification · current The memory usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.7 | |||
notification · current The memory usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the configuration, running services and sizing of this Edge node. Consider adjusting the Edge appliance form factor size or rebalancing services to other Edge nodes for the applicable workload. | ||||
| !vmwNsxTEdgeHealthEdgeMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.8 | |||
notification · current The memory usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.9 | |||
notification · current The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine the partition with high usage and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTEdgeHealthEdgeDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.10 | |||
notification · current The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTEdgeHealthEdgeDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.11 | |||
notification · current The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine the partition with high usage and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTEdgeHealthEdgeDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.12 | |||
notification · current The disk usage for the Edge node disk partition vmwNsxTDataCenterDiskPartitionName has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTEdgeHealthEdgeDatapathCPUHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.17 | |||
notification · current The datapath CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterDatapathResourceUsage% which is at or above the high threshold for at least two minutes. Action required: Review the CPU statistics on the Edge node by invoking the NSX CLI command `get dataplane cpu stats` to show packet rates per CPU core. Higher CPU usage is expected with higher packet rates. Consider increasing the Edge appliance form factor size and rebalancing services on this Edge node to other Edge nodes in the same cluster or other Edge clusters. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathCPUHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.18 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached below the high threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathCPUVeryHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.19 | |||
notification · current The datapath CPU usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterDatapathResourceUsage% which is at or above the very high threshold for at least two minutes. Action required: Review the CPU statistics on the Edge node by invoking the NSX CLI command `get dataplane cpu stats` to show packet rates per CPU core. Higher CPU usage is expected with higher packet rates. Consider increasing the Edge appliance form factor size and rebalancing services on this Edge node to other Edge nodes in the same cluster or other Edge clusters. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathCPUVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.20 | |||
notification · current The CPU usage on Edge node vmwNsxTDataCenterEntityId has reached below the very high threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathConfigurationFailure | 1.3.6.1.4.1.6876.120.1.0.2.0.21 | |||
notification · current Failed to enable the datapath on the Edge node after three attempts. Action required: Ensure the Edge node's connectivity to the Manager node is healthy. From the Edge node's NSX CLI, invoke the command `get services` to check the health of services. If the dataplane service is stopped, invoke the command `start service dataplane` to start it. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathConfigurationFailureClear | 1.3.6.1.4.1.6876.120.1.0.2.0.22 | |||
notification · current Datapath on the Edge node has been successfully enabled. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathCryptodrvDown | 1.3.6.1.4.1.6876.120.1.0.2.0.23 | |||
notification · current Edge node crypto driver vmwNsxTDataCenterEdgeCryptoDrvName is down. Action required: Upgrade the Edge node as needed. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathCryptodrvDownClear | 1.3.6.1.4.1.6876.120.1.0.2.0.24 | |||
notification · current Edge node crypto driver vmwNsxTDataCenterEdgeCryptoDrvName is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathMempoolHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.25 | |||
notification · current The datapath mempool usage for vmwNsxTDataCenterMempoolName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Log in as the root user and invoke the command `edge-appctl -t /var/run/vmware/edge/dpd.ctl mempool/show` and `edge-appctl -t /var/run/vmware/edge/dpd.ctl memory/show malloc_heap` to check DPDK memory usage.
| ||||
| !vmwNsxTEdgeHealthEdgeDatapathMempoolHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.26 | |||
notification · current The datapath mempool usage for vmwNsxTDataCenterMempoolName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.27 | |||
notification · current Global ARP table usage on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterDatapathResourceUsage% which is above the high threshold for over two minutes. Action required: Log in as the root user and invoke the command `edge-appctl -t /var/run/vmware/edge/dpd.ctl neigh/show` and check if neigh cache usage is normal. If it is normal, invoke the command `edge-appctl -t /var/run/vmware/edge/dpd.ctl neigh/set_param max_entries` to increase the ARP table size. | ||||
| !vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.28 | |||
notification · current Global ARP table usage on Edge node vmwNsxTDataCenterEntityId has reached below the high threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeNICLinkStatusDown | 1.3.6.1.4.1.6876.120.1.0.2.0.29 | |||
notification · current Edge node NIC vmwNsxTDataCenterEdgeNICName link is down. Action required: On the Edge node confirm if the NIC link is physically down by invoking the NSX CLI command `get interfaces`. If it is down, verify the cable connection. | ||||
| !vmwNsxTEdgeHealthEdgeNICLinkStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.2.0.30 | |||
notification · current Edge node NIC vmwNsxTDataCenterEdgeNICName link is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeNICOutOfReceiveBuffer | 1.3.6.1.4.1.6876.120.1.0.2.0.31 | |||
notification · current Edge NIC vmwNsxTDataCenterEdgeNICName receive ring buffer has overflowed by vmwNsxTDataCenterRxRingBufferOverflowPercentage% on Edge node vmwNsxTDataCenterEntityId. The missed packet count is vmwNsxTDataCenterRxMisses and processed packet count is vmwNsxTDataCenterRxProcessed. Action required: Run the NSX CLI command `get dataplane cpu stats` on the edge node and check: 1. If cpu usage is high, i.e., > 90%, then take a packet capture on the interface using the command `start capture interface <interface-name> direction input` or `start capture interface <interface-name> direction input core <core-id>` (to capture packets ingressing on specific core whose usage is high). Then analyze the capture to see if there are majority of fragmented packets or ipsec packets. If yes, then it is expected behavior. If not, datapath is probably busy with other operations. If this alarm lasts more than 2-3 minutes, contact VMware Support. 2. If cpu usage is not high, i.e., < 90%, then check if rx pps is high using the command `get dataplane cpu stats` (just to make sure the traffic rate is increasing). Then increase the ring size by 1024 using the command `set dataplane ring-size rx <ring-size>`. NOTE - The continuous increase of ring size by 1024 factor can lead to some performance issues. If even after increasing the ring size, the issue persists then it is an indication that edge needs a larger form factor deployment to accommodate the traffic. 3. If the alarm keeps on flapping i.e., triggers and resolves very soon, then it is due to bursty traffic. In this case check if rx pps as described above, if it is not high during the alarm active period then contact VMware Support. If pps is high it confirms bursty traffic. Consider suppressing the alarm. NOTE - There is no specific benchmark to decide what is regarded as a high pps value. It depends on infrastructure and type of traffic. The comparison can be made by noting down when alarm is inactive and when it is active.
| ||||
| !vmwNsxTEdgeHealthEdgeNICOutOfReceiveBufferClear | 1.3.6.1.4.1.6876.120.1.0.2.0.32 | |||
notification · current Edge NIC vmwNsxTDataCenterEdgeNICName receive ring buffer usage on Edge node vmwNsxTDataCenterEntityId is no longer overflowing. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeNICOutOfTransmitBuffer | 1.3.6.1.4.1.6876.120.1.0.2.0.33 | |||
notification · current Edge NIC vmwNsxTDataCenterEdgeNICName transmit ring buffer has overflowed by vmwNsxTDataCenterTxRingBufferOverflowPercentage% on Edge node vmwNsxTDataCenterEntityId. The missed packet count is vmwNsxTDataCenterTxMisses and processed packet count is vmwNsxTDataCenterTxProcessed. Action required: 1. If a lot of VMs are accommodated along with edge by the hypervisor then edge VM might not get time to run, hence the packets might not be retrieved by hypervisor. Then probably migrating the edge VM to a host with fewer VMs. 2. Increase the ring size by 1024 using the command `set dataplane ring-size tx <ring-size>`. If even after increasing the ring size, the issue persists then contact VMware Support as the ESX side transmit ring buffer might be of lower value. If there is no issue on ESX side, it indicates the edge needs to be scaled to a larger form factor deployment to accommodate the traffic. 3. If the alarm keeps on flapping, i.e., triggers and resolves very soon, then it is due to bursty traffic. In this case check if tx pps using the command `get dataplane cpu stats`. If it is not high during the alarm active period then contact VMware Support. If pps is high it confirms bursty traffic. Consider suppressing the alarm. NOTE - There is no specific benchmark to decide what is regarded as a high pps value. It depends on infrastructure and type of traffic. The comparison can be made by noting down when alarm is inactive and when it is active.
| ||||
| !vmwNsxTEdgeHealthEdgeNICOutOfTransmitBufferClear | 1.3.6.1.4.1.6876.120.1.0.2.0.34 | |||
notification · current Edge NIC vmwNsxTDataCenterEdgeNICName transmit ring buffer usage on Edge node vmwNsxTDataCenterEntityId is no longer overflowing. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthStorageError | 1.3.6.1.4.1.6876.120.1.0.2.0.37 | |||
notification · current The following disk partitions on the Edge node are in read-only mode: vmwNsxTDataCenterDiskPartitionName Action required: Examine the read-only partition to see if reboot resolves the issue or the disk needs to be replaced. Contact GSS for more information. | ||||
| !vmwNsxTEdgeHealthStorageErrorClear | 1.3.6.1.4.1.6876.120.1.0.2.0.38 | |||
notification · current The following disk partitions on the Edge node have recovered from read-only mode: vmwNsxTDataCenterDiskPartitionName Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthDatapathThreadDeadlocked | 1.3.6.1.4.1.6876.120.1.0.2.0.45 | |||
notification · current Edge node datapath thread vmwNsxTDataCenterEdgeThreadName is deadlocked. Action required: Restart the dataplane service by invoking the NSX CLI command `restart service dataplane`. | ||||
| !vmwNsxTEdgeHealthDatapathThreadDeadlockedClear | 1.3.6.1.4.1.6876.120.1.0.2.0.46 | |||
notification · current Edge node datapath thread vmwNsxTDataCenterEdgeThreadName is free from deadlock. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthEdgeDatapathNICThroughputHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.49 | |||
notification · current The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is at or above the high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. Action required: Examine the traffic thoughput levels on the NIC and determine whether configuration changes are needed. The 'get dataplane thoughput <seconds>' command can be used to monitor throughput.
| ||||
| !vmwNsxTEdgeHealthEdgeDatapathNICThroughputHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.50 | |||
notification · current The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is below the high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHigh | 1.3.6.1.4.1.6876.120.1.0.2.0.51 | |||
notification · current The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is at or above the very high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. Action required: Examine the traffic thoughput levels on the NIC and determine whether configuration changes are needed. The 'get dataplane thoughput <seconds>' command can be used to monitor throughput.
| ||||
| !vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.2.0.52 | |||
notification · current The datapath NIC throughput for vmwNsxTDataCenterEdgeNICName on Edge node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterNICThroughput% which is below the very high threshold value of vmwNsxTDataCenterNICThroughputThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTEdgeHealthFailureDomainDown | 1.3.6.1.4.1.6876.120.1.0.2.0.53 | |||
notification · current All members of failure domain vmwNsxTDataCenterTransportNodeId are down. Action required: 1. On the Edge node identified by vmwNsxTDataCenterTransportNodeId, check the connectivity to the management and control planes by invoking the NSX CLI command `get managers` and `get controllers`. 2. Invoke the NSX CLI command `get interface eth0` to check the management interface status. 3. Invoke the CLI `get services` to check the core services status like dataplane/local-controller/nestdb/router, etc. 4. Inspect the /var/log/syslog to find the suspecting error. 5. Reboot the Edge node. | ||||
| !vmwNsxTEdgeHealthFailureDomainDownClear | 1.3.6.1.4.1.6876.120.1.0.2.0.54 | |||
notification · current All members of failure domain vmwNsxTDataCenterTransportNodeId are reachable. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthMegaFlowCacheHitRateLow | 1.3.6.1.4.1.6876.120.1.0.2.0.55 | |||
notification · current Mega Flow Cache hit rate on Edge node vmwNsxTDataCenterEntityId has decreased below the specified threshold of vmwNsxTDataCenterFlowCacheThreshold% for core vmwNsxTDataCenterCoreId, and the Datapath CPU usage has increased for the last 30 minutes. Action required: The Cache Flow hit rate has decreased for the last 30 minutes which is an indication that there may be degradation on Edge performance. The traffic will continue to be forwarded and you may not experience any issues. Check the datapath CPU utilization for Edge vmwNsxTDataCenterEntityId core vmwNsxTDataCenterCoreId if it is high for the last 30 minutes. The Edge will have low flow-cache hit rate when there are continuously new flows getting created because the first packet of any new flow will be used to setup to flow-cache for fast path processing. You may want to increase your Edge appliance size or increase the number of Edge nodes used for Active/Active Gateways. | ||||
| !vmwNsxTEdgeHealthMegaFlowCacheHitRateLowClear | 1.3.6.1.4.1.6876.120.1.0.2.0.56 | |||
notification · current Flow Cache hit rate is in the normal range. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeHealthMicroFlowCacheHitRateLow | 1.3.6.1.4.1.6876.120.1.0.2.0.57 | |||
notification · current Micro Flow Cache hit rate on Edge node vmwNsxTDataCenterEntityId has decreased below the specified threshold of vmwNsxTDataCenterFlowCacheThreshold% for core vmwNsxTDataCenterCoreId, and the Datapath CPU usage has increased for the last 30 minutes. Action required: The Cache Flow hit rate has decreased for the last 30 minutes which is an indication that there may be degradation on Edge performance. The traffic will continue to be forwarded and you may not experience any issues. Check the datapath CPU utilization for Edge vmwNsxTDataCenterEntityId core vmwNsxTDataCenterCoreId if it is high for the last 30 minutes. The Edge will have low flow-cache hit rate when there are continuously new flows getting created because the first packet of any new flow will be used to setup to flow-cache for fast path processing. You may want to increase your Edge appliance size or increase the number of Edge nodes used for Active/Active Gateways. | ||||
| !vmwNsxTEdgeHealthMicroFlowCacheHitRateLowClear | 1.3.6.1.4.1.6876.120.1.0.2.0.58 | |||
notification · current Flow Cache hit rate is in the normal range. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTCertificatesFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.3 | |||
node · current Notifications applicable to the Certificates feature have this OID prefix. | ||||
| NvmwNsxTCertificatesFeature | 1.3.6.1.4.1.6876.120.1.0.3.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Certificates feature notifications. | ||||
| !vmwNsxTCertificatesCertificateExpirationApproaching | 1.3.6.1.4.1.6876.120.1.0.3.0.1 | |||
notification · current Certificate vmwNsxTDataCenterEntityId is approaching expiration. Action required: Ensure services that are currently using the certificate are updated to use a new, non-expiring certificate. Once the expiring certificate is no longer in use, it should be deleted by invoking the DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. | ||||
| !vmwNsxTCertificatesCertificateExpirationApproachingClear | 1.3.6.1.4.1.6876.120.1.0.3.0.2 | |||
notification · current The expiring certificate vmwNsxTDataCenterEntityId has been removed or is no longer approaching expiration. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesCertificateExpired | 1.3.6.1.4.1.6876.120.1.0.3.0.3 | |||
notification · current Certificate vmwNsxTDataCenterEntityId has expired. Action required: Ensure services that are currently using the certificate are updated to use a new, non-expired certificate. Once the expired certificate is no longer in use, it should be deleted by invoking the DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. If the expired certificate is used by NAPP Platform, the connection is broken between NSX and NAPP Platform. Check the NAPP Platform troubleshooting document to use a self-signed NAPP CA certificate for recovering the connection. For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=certificates.certificate_expired | ||||
| !vmwNsxTCertificatesCertificateExpiredClear | 1.3.6.1.4.1.6876.120.1.0.3.0.4 | |||
notification · current The expired certificate vmwNsxTDataCenterEntityId has been removed or is no longer expired. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesCertificateIsAboutToExpire | 1.3.6.1.4.1.6876.120.1.0.3.0.5 | |||
notification · current Certificate vmwNsxTDataCenterEntityId is about to expire. Action required: Ensure services that are currently using the certificate are updated to use a new, non-expiring certificate. Once the expiring certificate is no longer in use, it should be deleted by invoking the DELETE vmwNsxTDataCenterAPICollectionPathvmwNsxTDataCenterEntityId NSX API. | ||||
| !vmwNsxTCertificatesCertificateIsAboutToExpireClear | 1.3.6.1.4.1.6876.120.1.0.3.0.6 | |||
notification · current The expiring certificate vmwNsxTDataCenterEntityId has been removed or is no longer about to expire. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesCABundleUpdateRecommended | 1.3.6.1.4.1.6876.120.1.0.3.0.7 | |||
notification · current The trusted CA bundle vmwNsxTDataCenterEntityId was updated more than vmwNsxTDataCenterCABundleAgeThreshold days ago. Update for the trusted CA bundle is recommended. Action required: Ensure services that are currently using the trusted CA bundle are updated to use a recently-updated trusted CA bundle. Unless it is system-provided bundle, the bundle can be updated using the PUT /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. Once the expired bundle is no longer in use, it should be deleted (if not system-provided) by invoking the DELETE /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. | ||||
| !vmwNsxTCertificatesCABundleUpdateRecommendedClear | 1.3.6.1.4.1.6876.120.1.0.3.0.8 | |||
notification · current The trusted CA bundle vmwNsxTDataCenterEntityId has been removed, updated, or is no longer in use. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesCABundleUpdateSuggested | 1.3.6.1.4.1.6876.120.1.0.3.0.9 | |||
notification · current The trusted CA bundle vmwNsxTDataCenterEntityId was updated more than vmwNsxTDataCenterCABundleAgeThreshold days ago. Update for the trusted CA bundle is suggested. Action required: Ensure services that are currently using the trusted CA bundle are updated to use a recently-updated trusted CA bundle. Unless it is system-provided bundle, the bundle can be updated using the PUT /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. Once the expired bundle is no longer in use, it should be deleted (if not system-provided) by invoking the DELETE /policy/api/v1/infra/cabundles/vmwNsxTDataCenterEntityId NSX API. | ||||
| !vmwNsxTCertificatesCABundleUpdateSuggestedClear | 1.3.6.1.4.1.6876.120.1.0.3.0.10 | |||
notification · current The trusted CA bundle vmwNsxTDataCenterEntityId has been removed, updated, or is no longer in use. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateExpirApproaching | 1.3.6.1.4.1.6876.120.1.0.3.0.17 | |||
notification · current Certificate for Transport node vmwNsxTDataCenterEntityId is approaching expiration. Action required: Replace the Transport node vmwNsxTDataCenterEntityId certificate with a non-expired certificate. The expired certificate should be replaced by invoking the POST /api/v1/trust-management/certificates/action/replace-host-certificate/vmwNsxTDataCenterEntityId NSX API. If the certificate is not replaced, when the certificate expires the connection between the Transport node and the Manager node will be broken. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateExpirApproachingClear | 1.3.6.1.4.1.6876.120.1.0.3.0.18 | |||
notification · current The expiring certificate for Transport node vmwNsxTDataCenterEntityId has been removed or is no longer approaching expiration. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateExpired | 1.3.6.1.4.1.6876.120.1.0.3.0.19 | |||
notification · current Certificate has expired for Transport node vmwNsxTDataCenterEntityId. Action required: Replace the Transport node vmwNsxTDataCenterEntityId certificate with a non-expired certificate. The expired certificate should be replaced by invoking the POST /api/v1/trust-management/certificates/action/replace-host-certificate/vmwNsxTDataCenterEntityId NSX API. If the expired certificate is used by Transport node, the connection is broken between Transport node and Manager node. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateExpiredClear | 1.3.6.1.4.1.6876.120.1.0.3.0.20 | |||
notification · current The expired certificate for Transport node vmwNsxTDataCenterEntityId has been replaced or is no longer expired. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateIsAboutToExpire | 1.3.6.1.4.1.6876.120.1.0.3.0.21 | |||
notification · current Certificate for Transport node vmwNsxTDataCenterEntityId is about to expire. Action required: Replace the Transport node vmwNsxTDataCenterEntityId certificate with a non-expired certificate. The expired certificate should be replaced by invoking the POST /api/v1/trust-management/certificates/action/replace-host-certificate/vmwNsxTDataCenterEntityId NSX API. If the certificate is not replaced, when the certificate expires the connection between the Transport node and the Manager node will be broken. | ||||
| !vmwNsxTCertificatesTransportNodeCertificateIsAboutToExpireClear | 1.3.6.1.4.1.6876.120.1.0.3.0.22 | |||
notification · current The expiring certificate for Transport node vmwNsxTDataCenterEntityId has been removed or is no longer about to expire. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTPasswordManagementFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.4 | |||
node · current Notifications applicable to the PasswordManagement feature have this OID prefix. | ||||
| NvmwNsxTPasswordManagementFeature | 1.3.6.1.4.1.6876.120.1.0.4.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for PasswordManagement feature notifications. | ||||
| !vmwNsxTPasswordManagementPasswordExpirationApproaching | 1.3.6.1.4.1.6876.120.1.0.4.0.1 | |||
notification · current The password for user vmwNsxTDataCenterUsername is approaching expiration in vmwNsxTDataCenterPasswordExpirationDays days. Action required: The password for the user vmwNsxTDataCenterUsername needs to be changed soon. For example, to apply a new password to a user, invoke the following NSX API with a valid password in the request body: PUT /api/v1/node/users/<userid> where <userid> is the ID of the user. | ||||
| !vmwNsxTPasswordManagementPasswordExpirationApproachingClear | 1.3.6.1.4.1.6876.120.1.0.4.0.2 | |||
notification · current The password for the user vmwNsxTDataCenterUsername has been changed successfully or is no longer expired or the user is no longer active. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTPasswordManagementPasswordExpired | 1.3.6.1.4.1.6876.120.1.0.4.0.3 | |||
notification · current The password for user vmwNsxTDataCenterUsername has expired. Action required: The password for user vmwNsxTDataCenterUsername must be changed now to access the system. For example, to apply a new password to a user, invoke the following NSX API with a valid password in the request body: PUT /api/v1/node/users/<userid> where <userid> is the ID of the user. If the admin user (with <userid> 10000) password has expired, admin must login to the system via SSH (if enabled) or console in order to change the password. Upon entering the current expired password, admin will be prompted to enter a new password. | ||||
| !vmwNsxTPasswordManagementPasswordExpiredClear | 1.3.6.1.4.1.6876.120.1.0.4.0.4 | |||
notification · current The password for user vmwNsxTDataCenterUsername has been changed successfully or is no longer expired or the user is no longer active. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTPasswordManagementPasswordIsAboutToExpire | 1.3.6.1.4.1.6876.120.1.0.4.0.5 | |||
notification · current The password for user vmwNsxTDataCenterUsername is about to expire in vmwNsxTDataCenterPasswordExpirationDays days. Action required: Ensure the password for the user vmwNsxTDataCenterUsername is changed immediately. For example, to apply a new password to a user, invoke the following NSX API with a valid password in the request body: PUT /api/v1/node/users/<userid> where <userid> is the ID of the user. | ||||
| !vmwNsxTPasswordManagementPasswordIsAboutToExpireClear | 1.3.6.1.4.1.6876.120.1.0.4.0.6 | |||
notification · current The password for the user vmwNsxTDataCenterUsername has been changed successfully or is no longer expired or the user is no longer active. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTLicensesFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.5 | |||
node · current Notifications applicable to the Licenses feature have this OID prefix. | ||||
| NvmwNsxTLicensesFeature | 1.3.6.1.4.1.6876.120.1.0.5.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Licenses feature notifications. | ||||
| !vmwNsxTLicensesLicenseExpired | 1.3.6.1.4.1.6876.120.1.0.5.0.1 | |||
notification · current The vmwNsxTDataCenterLicenseEditionType license key ending with vmwNsxTDataCenterDisplayedLicenseKey, has expired. Action required: Add a new, non-expired license using the NSX UI by navigating to System | Licenses then click ADD and specify the key of the new license. The expired license should be deleted by checking the checkbox of the license, then click DELETE. | ||||
| !vmwNsxTLicensesLicenseExpiredClear | 1.3.6.1.4.1.6876.120.1.0.5.0.2 | |||
notification · current The expired vmwNsxTDataCenterLicenseEditionType license key ending with vmwNsxTDataCenterDisplayedLicenseKey, has been removed, updated or is no longer about to expire. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLicensesLicenseIsAboutToExpire | 1.3.6.1.4.1.6876.120.1.0.5.0.3 | |||
notification · current The vmwNsxTDataCenterLicenseEditionType license key ending with vmwNsxTDataCenterDisplayedLicenseKey, is about to expire. Action required: The license is about to expire in several days. Plan to add a new, non-expiring license using the NSX UI by navigating to System | Licenses then click ADD and specify the key of the new license. The expired license should be deleted by checking the checkbox of the license, then click DELETE. | ||||
| !vmwNsxTLicensesLicenseIsAboutToExpireClear | 1.3.6.1.4.1.6876.120.1.0.5.0.4 | |||
notification · current The expiring vmwNsxTDataCenterLicenseEditionType license key ending with vmwNsxTDataCenterDisplayedLicenseKey, has been removed, updated or is no longer about to expire. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTIntelligenceHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.6 | |||
node · current Notifications applicable to the IntelligenceHealth feature have this OID prefix. | ||||
| NvmwNsxTIntelligenceHealthFeature | 1.3.6.1.4.1.6876.120.1.0.6.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for IntelligenceHealth feature notifications. | ||||
| !vmwNsxTIntelligenceHealthCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.41 | |||
notification · current The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Use the top command to check which processes have the most CPU usages, and then check /var/log/syslog and these processes' local logs to see if there are any outstanding errors to be resolved. | ||||
| !vmwNsxTIntelligenceHealthCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.42 | |||
notification · current The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.43 | |||
notification · current The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Use the top command to check which processes have the most CPU usages, and then check /var/log/syslog and these processes' local logs to see if there are any outstanding errors to be resolved. | ||||
| !vmwNsxTIntelligenceHealthCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.44 | |||
notification · current The CPU usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthDataDiskPartitionUsageHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.45 | |||
notification · current The disk usage of disk partition /data on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Stop NSX intelligence data collection until the disk usage is below the threshold. Examine disk partition /data and see if there are any unexpected large files that can be removed. | ||||
| !vmwNsxTIntelligenceHealthDataDiskPartitionUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.46 | |||
notification · current The disk usage of disk partition /data on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.47 | |||
notification · current The disk usage of disk partition /data on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Stop NSX intelligence data collection until the disk usage is below the threshold. In the NSX UI, navigate to System | Appliances | NSX Intelligence Appliance. Then click ACTONS, Stop Collecting Data. | ||||
| !vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.48 | |||
notification · current The disk usage of disk partition /data on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.49 | |||
notification · current The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine disk partition vmwNsxTDataCenterDiskPartitionName and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTIntelligenceHealthDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.50 | |||
notification · current The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTIntelligenceHealthDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.51 | |||
notification · current The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Examine disk partition vmwNsxTDataCenterDiskPartitionName and see if there are any unexpected large files that can be removed.
| ||||
| !vmwNsxTIntelligenceHealthDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.52 | |||
notification · current The disk usage of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTIntelligenceHealthMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.53 | |||
notification · current The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Use the top command to check which processes have the most memory usages, and then check /var/log/syslog and these processes' local logs to see if there are any outstanding errors to be resolved. | ||||
| !vmwNsxTIntelligenceHealthMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.54 | |||
notification · current The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.55 | |||
notification · current The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Use the top command to check which processes have the most memory usages, and then check /var/log/syslog and these processes' local logs to see if there are any outstanding errors to be resolved. | ||||
| !vmwNsxTIntelligenceHealthMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.56 | |||
notification · current The memory usage on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthNodeStatusDegraded | 1.3.6.1.4.1.6876.120.1.0.6.0.57 | |||
notification · current Intelligence node vmwNsxTDataCenterIntelligenceNodeId is degraded. Action required: Invoke the NSX API GET /napp/api/v1/platform/monitor/category/health to check which specific pod is down and the reason behind it. Invoke the following CLI command to restart the degraded service: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` | ||||
| !vmwNsxTIntelligenceHealthNodeStatusDegradedClear | 1.3.6.1.4.1.6876.120.1.0.6.0.58 | |||
notification · current Intelligence node vmwNsxTDataCenterIntelligenceNodeId is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIntelligenceHealthStorageLatencyHigh | 1.3.6.1.4.1.6876.120.1.0.6.0.63 | |||
notification · current The storage latency of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold milliseconds. Action required: Transient high storage latency may happen due to spike of I/O requests. If storage latency remains high for more than 30 minutes, consider deploying NSX Intelligence appliance in a low latency disk, or not sharing the same storage device with other VMs.
| ||||
| !vmwNsxTIntelligenceHealthStorageLatencyHighClear | 1.3.6.1.4.1.6876.120.1.0.6.0.64 | |||
notification · current The storage latency of disk partition vmwNsxTDataCenterDiskPartitionName on Intelligence node vmwNsxTDataCenterIntelligenceNodeId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold milliseconds. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTInfrastructureCommunicationFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.7 | |||
node · current Notifications applicable to the InfrastructureCommunication feature have this OID prefix. | ||||
| NvmwNsxTInfrastructureCommunicationFeature | 1.3.6.1.4.1.6876.120.1.0.7.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for InfrastructureCommunication feature notifications. | ||||
| !vmwNsxTInfrastructureCommunicationEdgeTunnelsDown | 1.3.6.1.4.1.6876.120.1.0.7.0.17 | |||
notification · current The overall tunnel status of Edge node vmwNsxTDataCenterEntityId is down. Action required: Invoke the NSX CLI command `get tunnel-ports` to get all tunnel ports, then check each tunnel's stats by invoking NSX CLI command `get tunnel-port <UUID> stats` to check if there are any drops. Also check /var/log/syslog if there are tunnel related errors. | ||||
| !vmwNsxTInfrastructureCommunicationEdgeTunnelsDownClear | 1.3.6.1.4.1.6876.120.1.0.7.0.18 | |||
notification · current The tunnels of Edge node vmwNsxTDataCenterEntityId have been restored. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTIntelligenceCommunicationFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.9 | |||
node · current Notifications applicable to the IntelligenceCommunication feature have this OID prefix. | ||||
| NvmwNsxTIntelligenceCommunicationFeature | 1.3.6.1.4.1.6876.120.1.0.9.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for IntelligenceCommunication feature notifications. | ||||
| !vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnected | 1.3.6.1.4.1.6876.120.1.0.9.0.7 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId is disconnected from the Intelligence node's messaging broker. Data collection is affected. Action required: Restart the messaging service if it is not running in the Intelligence node. Resolve the network connection failure between the Transport node flow exporter and the Intelligence node. | ||||
| !vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnectedClear | 1.3.6.1.4.1.6876.120.1.0.9.0.8 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId has reconnected to the Intelligence node's messaging broker. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTCniHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.10 | |||
node · current Notifications applicable to the CniHealth feature have this OID prefix. | ||||
| NvmwNsxTCniHealthFeature | 1.3.6.1.4.1.6876.120.1.0.10.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for CniHealth feature notifications. | ||||
| !vmwNsxTCniHealthHyperbusManagerConnectionDown | 1.3.6.1.4.1.6876.120.1.0.10.0.3 | |||
notification · current Hyperbus cannot communicate with the Manager node. Action required: The hyperbus vmkernel interface (vmk50) may be missing. Refer to Knowledge Base article https://kb.vmware.com/s/article/67432. | ||||
| !vmwNsxTCniHealthHyperbusManagerConnectionDownClear | 1.3.6.1.4.1.6876.120.1.0.10.0.4 | |||
notification · current Hyperbus can communicate with the Manager node. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCniHealthHyperbusManagerConnectionDownOnDPU | 1.3.6.1.4.1.6876.120.1.0.10.0.5 | |||
notification · current Hyperbus on DPU vmwNsxTDataCenterDPUId cannot communicate with the Manager node. Action required: The hyperbus vmkernel interface (vmk50) on DPU vmwNsxTDataCenterDPUId may be missing. Refer to Knowledge Base article https://kb.vmware.com/s/article/67432. | ||||
| !vmwNsxTCniHealthHyperbusManagerConnectionDownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.10.0.6 | |||
notification · current Hyperbus on DPU vmwNsxTDataCenterDPUId can communicate with the Manager node. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTNCPHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.11 | |||
node · current Notifications applicable to the NCPHealth feature have this OID prefix. | ||||
| NvmwNsxTNCPHealthFeature | 1.3.6.1.4.1.6876.120.1.0.11.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for NCPHealth feature notifications. | ||||
| !vmwNsxTNCPHealthNCPPluginDown | 1.3.6.1.4.1.6876.120.1.0.11.0.3 | |||
notification · current Manager Node has detected the NCP is down or unhealthy. Action required: To find the clusters which are having issues, use the NSX UI and navigate to the Alarms page. The Entity name value for this alarm instance identifies the cluster name. Or invoke the NSX API GET /api/v1/systemhealth/container-cluster/ncp/status to fetch all cluster statuses and determine the name of any clusters that report DOWN or UNKNOWN. Then on the NSX UI Inventory | Container | Clusters page find the cluster by name and click the Nodes tab which lists all Kubernetes and PAS cluster members. For Kubernetes cluster: 1. Check NCP Pod liveness by finding the K8s master node from all the cluster members and log onto the master node. Then invoke the kubectl command `kubectl get pods --all-namespaces`. If there is an issue with the NCP Pod, use kubectl logs command to check the issue and fix the error. 2. Check the connection between NCP and Kubernetes API server. The NSX CLI can be used inside the NCP Pod to check this connection status by invoking the following commands from the master VM. `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` `nsxcli` `get ncp-k8s-api-server status` If there is an issue with the connection, check both the network and NCP configurations. 3. Check the connection between NCP and NSX Manager. The NSX CLI can be used inside the NCP Pod to check this connection status by invoking the following command from the master VM. `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` `nsxcli` `get ncp-nsx status` If there is an issue with the connection, check both the network and NCP configurations. For PAS cluster: 1. Check the network connections between virtual machines and fix any network issues. 2. Check the status of both nodes and services and fix crashed nodes or services. Invoke the command `bosh vms` and `bosh instances -p` to check the status of nodes and services. | ||||
| !vmwNsxTNCPHealthNCPPluginDownClear | 1.3.6.1.4.1.6876.120.1.0.11.0.4 | |||
notification · current Manager Node has detected the NCP is up or healthy again. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTNodeAgentsHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.12 | |||
node · current Notifications applicable to the NodeAgentsHealth feature have this OID prefix. | ||||
| NvmwNsxTNodeAgentsHealthFeature | 1.3.6.1.4.1.6876.120.1.0.12.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for NodeAgentsHealth feature notifications. | ||||
| !vmwNsxTNodeAgentsHealthNodeAgentsDown | 1.3.6.1.4.1.6876.120.1.0.12.0.3 | |||
notification · current The agents running inside the Node VM appear to be down. Action required: For ESX: 1. If Vmk50 is missing, refer to this Knowledge Base article https://kb.vmware.com/s/article/67432. 2. If Hyperbus 4094 is missing, restarting nsx-cfgagent or restarting the container host VM may help. 3. If container host VIF is blocked, check the connection to the Controller to make sure all configurations are sent down. 4. If nsx-cfg-agent has stopped, restart nsx-cfgagent. For KVM: 1. If Hyperbus namespace is missing, restarting the nsx-opsagent may help recreate the namespace. 2. If Hyperbus interface is missing inside the hyperbus namespace, restarting the nsx-opsagent may help. 3. If nsx-agent has stopped, restart nsx-agent. For Both ESX and KVM: 1. If the node-agent package is missing, check whether node-agent package has been successfully installed in the container host vm. 2. If the interface for node-agent in container host vm is down, check the eth1 interface status inside the container host vm. | ||||
| !vmwNsxTNodeAgentsHealthNodeAgentsDownClear | 1.3.6.1.4.1.6876.120.1.0.12.0.4 | |||
notification · current The agents inside the Node VM are running. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPU | 1.3.6.1.4.1.6876.120.1.0.12.0.5 | |||
notification · current The agents running inside the Node VM appear to be down on DPU vmwNsxTDataCenterDPUId. Action required: 1. If Vmk50 on DPU vmwNsxTDataCenterDPUId is missing, refer to this Knowledge Base article https://kb.vmware.com/s/article/67432. 2. If Hyperbus 4094 on DPU vmwNsxTDataCenterDPUId is missing, restarting nsx-cfgagent on DPU vmwNsxTDataCenterDPUId or restarting the container host VM may help. 3. If container host VIF is blocked, check the connection to the Controller to make sure all configurations are sent down. 4. If nsx-cfg-agent on DPU vmwNsxTDataCenterDPUId has stopped, restart nsx-cfgagent on DPU vmwNsxTDataCenterDPUId . 5. If the node-agent package is missing, check whether node-agent package has been successfully installed in the container host vm. 6. If the interface for node-agent in container host vm is down, check the eth1 interface status inside the container host vm. | ||||
| !vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.12.0.6 | |||
notification · current The agents inside the Node VM are running on DPU vmwNsxTDataCenterDPUId. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTEndpointProtectionFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.13 | |||
node · current Notifications applicable to the EndpointProtection feature have this OID prefix. | ||||
| NvmwNsxTEndpointProtectionFeature | 1.3.6.1.4.1.6876.120.1.0.13.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for EndpointProtection feature notifications. | ||||
| !vmwNsxTEndpointProtectionEAMStatusDown | 1.3.6.1.4.1.6876.120.1.0.13.0.1 | |||
notification · current ESX Agent Manager (EAM) service on compute manager vmwNsxTDataCenterEntityId is down. Action required: Start the ESX Agent Manager (EAM) service. SSH into vCenter and invoke the command `service vmware-eam start`. | ||||
| !vmwNsxTEndpointProtectionEAMStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.13.0.2 | |||
notification · current ESX Agent Manager (EAM) service on compute manager vmwNsxTDataCenterEntityId is either up or compute manager vmwNsxTDataCenterEntityId has been removed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEndpointProtectionPartnerChannelDown | 1.3.6.1.4.1.6876.120.1.0.13.0.3 | |||
notification · current The connection between host module and Partner SVM vmwNsxTDataCenterEntityId is down. Action required: Refer to https://kb.vmware.com/s/article/85844 and make sure that Partner SVM vmwNsxTDataCenterEntityId is re-connected to the host module. | ||||
| !vmwNsxTEndpointProtectionPartnerChannelDownClear | 1.3.6.1.4.1.6876.120.1.0.13.0.4 | |||
notification · current The connection between host module and Partner SVM vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTServiceInsertionFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.14 | |||
node · current Notifications applicable to the ServiceInsertion feature have this OID prefix. | ||||
| NvmwNsxTServiceInsertionFeature | 1.3.6.1.4.1.6876.120.1.0.14.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for ServiceInsertion feature notifications. | ||||
| !vmwNsxTServiceInsertionNewHostAdded | 1.3.6.1.4.1.6876.120.1.0.14.0.7 | |||
notification · current New host added in cluster vmwNsxTDataCentervCenterClusterId and SVM will be deployed. Action required: Check for the VM deployment status and wait till it powers on. | ||||
| !vmwNsxTServiceInsertionNewHostAddedClear | 1.3.6.1.4.1.6876.120.1.0.14.0.8 | |||
notification · current New host added successfully. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceDeploymentFailed | 1.3.6.1.4.1.6876.120.1.0.14.0.9 | |||
notification · current The service deployment vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName on cluster vmwNsxTDataCentervCenterClusterId has failed. Reason : vmwNsxTDataCenterFailureReason Action required: Delete the service deployment using NSX UI or API. Perform any corrective action from the KB and retry service deployment again. | ||||
| !vmwNsxTServiceInsertionServiceDeploymentFailedClear | 1.3.6.1.4.1.6876.120.1.0.14.0.10 | |||
notification · current The failed service deployment vmwNsxTDataCenterEntityId has been removed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceDeploymentSucceeded | 1.3.6.1.4.1.6876.120.1.0.14.0.11 | |||
notification · current The service deployment vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName on cluster vmwNsxTDataCentervCenterClusterId has succeeded. Action required: No action needed. | ||||
| !vmwNsxTServiceInsertionServiceDeploymentSucceededClear | 1.3.6.1.4.1.6876.120.1.0.14.0.12 | |||
notification · current The service deployment vmwNsxTDataCenterEntityId on cluster vmwNsxTDataCentervCenterClusterId has succeeded, no action needed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceUndeploymentFailed | 1.3.6.1.4.1.6876.120.1.0.14.0.15 | |||
notification · current The deletion of service deployment vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName on cluster vmwNsxTDataCentervCenterClusterId has failed. Reason : vmwNsxTDataCenterFailureReason Action required: Delete the service deployment using NSX UI or API. Perform any corrective action from the KB and retry deleting the service deployment again. Resolve the alarm manually after checking all the VM and objects are deleted. | ||||
| !vmwNsxTServiceInsertionServiceUndeploymentFailedClear | 1.3.6.1.4.1.6876.120.1.0.14.0.16 | |||
notification · current The failed service deployment name vmwNsxTDataCenterEntityId has been removed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceUndeploymentSucceeded | 1.3.6.1.4.1.6876.120.1.0.14.0.17 | |||
notification · current The deletion of service deployment vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName on cluster vmwNsxTDataCentervCenterClusterId has succeeded. Action required: No action needed. | ||||
| !vmwNsxTServiceInsertionServiceUndeploymentSucceededClear | 1.3.6.1.4.1.6876.120.1.0.14.0.18 | |||
notification · current The deletion of service deployment vmwNsxTDataCenterEntityId on cluster vmwNsxTDataCentervCenterClusterId has succeeded, no action needed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceChainPathDown | 1.3.6.1.4.1.6876.120.1.0.14.0.21 | |||
notification · current Service chain path is down on vmwNsxTDataCenterEntityId and traffic flow is impacted. Action required: Perform any corrective action from the KB and check if the status is up. | ||||
| !vmwNsxTServiceInsertionServiceChainPathDownClear | 1.3.6.1.4.1.6876.120.1.0.14.0.22 | |||
notification · current Service chain path is up and configured as expected. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionSVMHealthStatusDown | 1.3.6.1.4.1.6876.120.1.0.14.0.23 | |||
notification · current The health check for SVM vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName is not working correctly on vmwNsxTDataCenterHostnameOrIPAddressWithPort. Reason : vmwNsxTDataCenterFailureReason. Action required: Delete the service deployment using NSX UI or API. Perform any corrective action from the KB and retry service deployment again if necessary.
| ||||
| !vmwNsxTServiceInsertionSVMHealthStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.14.0.24 | |||
notification · current The SVM vmwNsxTDataCenterEntityId with wrong state has been removed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionSVMHealthStatusUp | 1.3.6.1.4.1.6876.120.1.0.14.0.25 | |||
notification · current The health check for SVM vmwNsxTDataCenterEntityId for service vmwNsxTDataCenterServiceName is working correctly on vmwNsxTDataCenterHostnameOrIPAddressWithPort. Action required: No action needed. | ||||
| !vmwNsxTServiceInsertionSVMHealthStatusUpClear | 1.3.6.1.4.1.6876.120.1.0.14.0.26 | |||
notification · current The SVM vmwNsxTDataCenterEntityId is working correctly, no action needed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionSVMLivenessStateDown | 1.3.6.1.4.1.6876.120.1.0.14.0.27 | |||
notification · current SVM liveness state is down on vmwNsxTDataCenterEntityId and traffic flow is impacted. Action required: Perform any corrective action from the KB and check if the state is up. | ||||
| !vmwNsxTServiceInsertionSVMLivenessStateDownClear | 1.3.6.1.4.1.6876.120.1.0.14.0.28 | |||
notification · current SVM liveness state is up and configured as expected. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTServiceInsertionServiceInsertionInfraStatusDown | 1.3.6.1.4.1.6876.120.1.0.14.0.29 | |||
notification · current SPF not enabled at port level on host vmwNsxTDataCenterTransportNodeId and the status is down. Reason : vmwNsxTDataCenterFailureReason. Action required: Perform any corrective action from the KB and check if the status is up. Resolve the alarm manually after checking the status. | ||||
| !vmwNsxTServiceInsertionServiceInsertionInfraStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.14.0.30 | |||
notification · current Service insertion infrastructure status is up and has been correctly enabled on host. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTVPNFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.15 | |||
node · current Notifications applicable to the VPN feature have this OID prefix. | ||||
| NvmwNsxTVPNFeature | 1.3.6.1.4.1.6876.120.1.0.15.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for VPN feature notifications. | ||||
| !vmwNsxTVPNIPsecPolicyBasedSessionDown | 1.3.6.1.4.1.6876.120.1.0.15.0.7 | |||
notification · current The policy based IPsec VPN session vmwNsxTDataCenterEntityId is down. Reason: vmwNsxTDataCenterSessionDownReason. Action required: Check IPsec VPN session configuration and resolve errors based on the session down reason. | ||||
| !vmwNsxTVPNIPsecPolicyBasedSessionDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.8 | |||
notification · current The policy based IPsec VPN session vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTVPNIPsecPolicyBasedTunnelDown | 1.3.6.1.4.1.6876.120.1.0.15.0.9 | |||
notification · current One or more policy based IPsec VPN tunnels in session vmwNsxTDataCenterEntityId are down. Action required: Check IPsec VPN session configuration and resolve errors based on the tunnel down reason. | ||||
| !vmwNsxTVPNIPsecPolicyBasedTunnelDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.10 | |||
notification · current All policy based IPsec VPN tunnels in session vmwNsxTDataCenterEntityId are up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTVPNIPsecRouteBasedSessionDown | 1.3.6.1.4.1.6876.120.1.0.15.0.11 | |||
notification · current The route based IPsec VPN session vmwNsxTDataCenterEntityId is down. Reason: vmwNsxTDataCenterSessionDownReason. Action required: Check IPsec VPN session configuration and resolve errors based on the session down reason. | ||||
| !vmwNsxTVPNIPsecRouteBasedSessionDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.12 | |||
notification · current The route based IPsec VPN session vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTVPNIPsecRouteBasedTunnelDown | 1.3.6.1.4.1.6876.120.1.0.15.0.13 | |||
notification · current The route based IPsec VPN tunnel in session vmwNsxTDataCenterEntityId is down. Reason: vmwNsxTDataCenterTunnelDownReason. Action required: Check IPsec VPN session configuration and resolve errors based on the tunnel down reason. | ||||
| !vmwNsxTVPNIPsecRouteBasedTunnelDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.14 | |||
notification · current The route based IPsec VPN tunnel in session vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTVPNL2VpnSessionDown | 1.3.6.1.4.1.6876.120.1.0.15.0.15 | |||
notification · current The L2VPN session vmwNsxTDataCenterEntityId is down. Action required: Check L2VPN session status for session down reason and resolve errors based on the reason. | ||||
| !vmwNsxTVPNL2VpnSessionDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.16 | |||
notification · current The L2VPN session vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTVPNIPsecServiceDown | 1.3.6.1.4.1.6876.120.1.0.15.0.17 | |||
notification · current The IPsec service vmwNsxTDataCenterEntityId is down. Reason: vmwNsxTDataCenterServiceDownReason. Action required: 1. Disable and enable the IPsec service from NSX Manager UI. 2. If the issue still persists, check syslog for error logs and contact VMware support. | ||||
| !vmwNsxTVPNIPsecServiceDownClear | 1.3.6.1.4.1.6876.120.1.0.15.0.18 | |||
notification · current The IPsec service vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTAlarmManagementFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.16 | |||
node · current Notifications applicable to the AlarmManagement feature have this OID prefix. | ||||
| NvmwNsxTAlarmManagementFeature | 1.3.6.1.4.1.6876.120.1.0.16.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for AlarmManagement feature notifications. | ||||
| !vmwNsxTAlarmManagementAlarmServiceOverloaded | 1.3.6.1.4.1.6876.120.1.0.16.0.1 | |||
notification · current Due to heavy volume of alarms reported, the alarm service is temporarily overloaded. The NSX UI and GET /api/v1/alarms NSX API have stopped reporting new alarms; however, syslog entries and SNMP traps (if enabled) are still being emitted reporting the underlying event details. When the underlying issues causing the heavy volume of alarms are addressed, the alarm service will start reporting new alarms again. Action required: Review all active alarms using the Alarms page in the NSX UI or using the GET /api/v1/alarms?status=OPEN,ACKNOWLEDGED,SUPPRESSED NSX API. For each active alarm investigate the root cause by following the recommended action for the alarm. When sufficient alarms are resolved, the alarm service will start reporting new alarms again. | ||||
| !vmwNsxTAlarmManagementAlarmServiceOverloadedClear | 1.3.6.1.4.1.6876.120.1.0.16.0.2 | |||
notification · current The heavy volume of alarms has subsided and new alarms are being reported again. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTAlarmManagementHeavyVolumeOfAlarms | 1.3.6.1.4.1.6876.120.1.0.16.0.3 | |||
notification · current Due to heavy volume of vmwNsxTDataCenterEventId alarms, the alarm service has temporarily stopped reporting alarms of this type. The NSX UI and GET /api/v1/alarms NSX API are not reporting new instances of these alarms; however, syslog entries and SNMP traps (if enabled) are still being emitted reporting the underlying event details. When the underlying issues causing the heavy volume of vmwNsxTDataCenterEventId alarms are addressed, the alarm service will start reporting new vmwNsxTDataCenterEventId alarms when new issues are detected again. Action required: Review all active alarms of type vmwNsxTDataCenterEventId using the Alarms page in the NSX UI or using the NSX API GET /api/v1/alarms?status=OPEN,ACKNOWLEDGED,SUPPRESSED. For each active alarm investigate the root cause by following the recommended action for the alarm. When sufficient alarms are resolved, the alarm service will start reporting new vmwNsxTDataCenterEventId alarms again. | ||||
| !vmwNsxTAlarmManagementHeavyVolumeOfAlarmsClear | 1.3.6.1.4.1.6876.120.1.0.16.0.4 | |||
notification · current The heavy volume of vmwNsxTDataCenterEventId alarms has subsided and new alarms of this type are being reported again. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTLoadBalancerFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.17 | |||
node · current Notifications applicable to the LoadBalancer feature have this OID prefix. | ||||
| NvmwNsxTLoadBalancerFeature | 1.3.6.1.4.1.6876.120.1.0.17.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for LoadBalancer feature notifications. | ||||
| !vmwNsxTLoadBalancerLBCPUVeryHigh | 1.3.6.1.4.1.6876.120.1.0.17.0.1 | |||
notification · current The CPU usage of load balancer vmwNsxTDataCenterEntityId is very high. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: If the load balancer CPU utilization is higher than system usage threshold, the workload is too high for this load balancer. Rescale the load balancer service by changing the load balancer size from small to medium or from medium to large. If the CPU utilization of this load balancer is still high, consider adjusting the Edge appliance form factor size or moving load balancer services to other Edge nodes for the applicable workload. | ||||
| !vmwNsxTLoadBalancerLBCPUVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.17.0.2 | |||
notification · current The CPU usage of load balancer vmwNsxTDataCenterEntityId is low enough. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerLBEdgeCapacityInUseHigh | 1.3.6.1.4.1.6876.120.1.0.17.0.3 | |||
notification · current The usage of load balancer service in Edge node vmwNsxTDataCenterEntityId is high. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: If multiple LB instances have been configurerd in this Edge node, deploy a new Edge node and move some LB instances to that new Edge node. If only a single LB instance (small/medium/etc) has been configured in an Edge node of same size (small/medium/etc), deploy a new Edge of bigger size and move the LB instance to that new Edge node. | ||||
| !vmwNsxTLoadBalancerLBEdgeCapacityInUseHighClear | 1.3.6.1.4.1.6876.120.1.0.17.0.4 | |||
notification · current The usage of load balancer service in Edge node vmwNsxTDataCenterEntityId is low enough. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHigh | 1.3.6.1.4.1.6876.120.1.0.17.0.5 | |||
notification · current The usage of pool members in Edge node vmwNsxTDataCenterEntityId is very high. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: Deploy a new Edge node and move the load balancer service from existing Edge nodes to the newly deployed Edge node. | ||||
| !vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.17.0.6 | |||
notification · current The usage of pool members in Edge node vmwNsxTDataCenterEntityId is low enough. The threshold is vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerLBStatusDown | 1.3.6.1.4.1.6876.120.1.0.17.0.7 | |||
notification · current The centralized load balancer service vmwNsxTDataCenterEntityId is down. Action required: On active Edge node, check load balancer status by invoking the NSX CLI command `get load-balancer <lb-uuid> status`. If the LB-State of load balancer service is not_ready or there is no output, make the Edge node enter maintenance mode, then exit maintenance mode. | ||||
| !vmwNsxTLoadBalancerLBStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.17.0.8 | |||
notification · current The centralized load balancer service vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerPoolStatusDown | 1.3.6.1.4.1.6876.120.1.0.17.0.9 | |||
notification · current The load balancer pool vmwNsxTDataCenterEntityId status is down. Action required: Consult the load balancer pool to determine which members are down by invoking the NSX CLI command `get load-balancer <lb-uuid> pool <pool-uuid> status` or NSX API GET /policy/api/v1/infra/lb-services/<lb-service-id>/lb-pools/<lb-pool-id>/detailed-status If DOWN or UNKNOWN is reported, verify the pool member. Check network connectivity from the load balancer to the impacted pool members. Validate application health of each pool member. Also validate the health of each pool member using the configured monitor. When the health of the member is established, the pool member status is updated to healthy based on the 'Rise Count' configuration in the monitor. Remediate the issue by rebooting the pool member or make the Edge node enter maintenance mode, then exit maintenance mode. | ||||
| !vmwNsxTLoadBalancerPoolStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.17.0.10 | |||
notification · current The load balancer pool vmwNsxTDataCenterEntityId status is up Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerVirtualServerStatusDown | 1.3.6.1.4.1.6876.120.1.0.17.0.11 | |||
notification · current The load balancer virtual server vmwNsxTDataCenterEntityId is down. Action required: Consult the load balancer pool to determine its status and verify its configuration. If incorrectly configured, reconfigure it and remove the load balancer pool from the virtual server then re-add it to the virtual server again. | ||||
| !vmwNsxTLoadBalancerVirtualServerStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.17.0.12 | |||
notification · current The load balancer virtual server vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerLBStatusDegraded | 1.3.6.1.4.1.6876.120.1.0.17.0.15 | |||
notification · current The load balancer service vmwNsxTDataCenterEntityId is degraded.
Action required:
For centralized load balancer:
Check the load balancer status on standby Edge node as the degraded status
means the load balancer status on standby Edge node is not ready. On standby
Edge node, invoke the NSX CLI command `get load-balancer <lb-uuid> status`.
If the LB-State of load balancer service is not_ready or there is no output,
make the Edge node enter maintenance mode, then exit maintenance mode.
For distributed load balancer:
1. Get detailed status by invoking NSX API GET
/policy/api/v1/infra/lb-services/<LBService>/detailed-status?source=realtime
2. From API output, find ESXi host reporting a non-zero instance_number
with status NOT_READY or CONFLICT.
3. On ESXi host node, invoke the NSX CLI command `get load-balancer
<lb-uuid> status`.
If 'Conflict LSP'is reported, check whether this LSP is attached
to other load balancer service. Check whether this conflict is
acceptable.
If 'Not Ready LSP' is reported, check the status of this LSP by
invoking NSX CLI command `get logical-switch-port status`.
NOTE: You should ignore the alarm if it can be resolved automatically in 5 mins
because the degraded status can be a transient status. | ||||
| !vmwNsxTLoadBalancerLBStatusDegradedClear | 1.3.6.1.4.1.6876.120.1.0.17.0.16 | |||
notification · current The load balancer service vmwNsxTDataCenterEntityId is not degraded. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerDLBStatusDown | 1.3.6.1.4.1.6876.120.1.0.17.0.17 | |||
notification · current The distributed load balancer service vmwNsxTDataCenterEntityId is down. Action required: On ESXi host node, invoke the NSX CLI command `get load-balancer <lb-uuid> status`. If 'Conflict LSP' is reported, check whether this LSP is attached to other load balancer service. Check whether this conflict is acceptable. If 'Not Ready LSP' is reported, check the status of this LSP by invoking NSX CLI command `get logical-switch-port status`. | ||||
| !vmwNsxTLoadBalancerDLBStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.17.0.18 | |||
notification · current The distributed load balancer service vmwNsxTDataCenterEntityId is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemory | 1.3.6.1.4.1.6876.120.1.0.17.0.19 | |||
notification · current The load balancer configuration vmwNsxTDataCenterEntityId is not realized, due to high memory usage on Edge node vmwNsxTDataCenterTransportNodeId. Action required: Prefer defining small and medium sized load balancers over large sized load balancers. Spread out load balancer services among the available Edge nodes. Reduce number of Virtual Servers defined. | ||||
| !vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemoryClear | 1.3.6.1.4.1.6876.120.1.0.17.0.20 | |||
notification · current The load balancer configuration vmwNsxTDataCenterEntityId is realized on vmwNsxTDataCenterTransportNodeId. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTTransportNodeHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.18 | |||
node · current Notifications applicable to the TransportNodeHealth feature have this OID prefix. | ||||
| NvmwNsxTTransportNodeHealthFeature | 1.3.6.1.4.1.6876.120.1.0.18.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for TransportNodeHealth feature notifications. | ||||
| !vmwNsxTTransportNodeHealthNVDSUplinkDown | 1.3.6.1.4.1.6876.120.1.0.18.0.3 | |||
notification · current Uplink is going down. Action required: Check the physical NICs' status of uplinks on hosts. 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | Host Transport Nodes. 2. In the Host Transport Nodes list, check the Node Status column. Find the Transport node with the degraded or down Node Status. 3. Select <transport node> | Monitor. Check the status details of the bond(uplink) which is reporting degraded or down. To avoid a degraded state, ensure all uplink interfaces are connected and up regardless of whether they are in use or not. | ||||
| !vmwNsxTTransportNodeHealthNVDSUplinkDownClear | 1.3.6.1.4.1.6876.120.1.0.18.0.4 | |||
notification · current Uplink is going up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTransportNodeHealthLAGMemberDown | 1.3.6.1.4.1.6876.120.1.0.18.0.5 | |||
notification · current LACP reporting member down. Action required: Check the connection status of LAG members on hosts. 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | Host Transport Nodes. 2. In the Host Transport Nodes list, check the Node Status column. Find the Transport node with the degraded or down Node Status. 3. Select <transport node> | Monitor. Find the bond(uplink) which is reporting degraded or down. 4. Check the LACP member status details by logging into the failed host and invoking `esxcli network vswitch dvs vmware lacp status get` on an ESXi host or `ovs-appctl bond/show` and `ovs-appctl lacp/show` on a KVM host. | ||||
| !vmwNsxTTransportNodeHealthLAGMemberDownClear | 1.3.6.1.4.1.6876.120.1.0.18.0.6 | |||
notification · current LACP reporting member up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTransportNodeHealthTransportNodeUplinkDown | 1.3.6.1.4.1.6876.120.1.0.18.0.7 | |||
notification · current Uplink is going down. Action required: Check the physical NICs' status of uplinks on hosts. 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | Host Transport Nodes. 2. In the Host Transport Nodes list, check the Node Status column. Find the Transport node with the degraded or down Node Status. 3. Select <transport node> | Monitor. Check the status details of the bond(uplink) which is reporting degraded or down. To avoid a degraded state, ensure all uplink interfaces are connected and up regardless of whether they are in use or not. | ||||
| !vmwNsxTTransportNodeHealthTransportNodeUplinkDownClear | 1.3.6.1.4.1.6876.120.1.0.18.0.8 | |||
notification · current Uplink is going up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTransportNodeHealthLAGMemberDownOnDPU | 1.3.6.1.4.1.6876.120.1.0.18.0.9 | |||
notification · current LACP on DPU vmwNsxTDataCenterDPUId reporting member down. Action required: Check the connection status of LAG members on DPU vmwNsxTDataCenterDPUId. Find out the mapped name of related physical NIC on host, then perform checking on UI. 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | Host Transport Nodes. 2. In the Host Transport Nodes list, check the Node Status column. Find the Transport node with the degraded or down Node Status. 3. Select <transport node> | Monitor. Find the bond(uplink) which is reporting degraded or down. 4. Check the LACP member status details by logging into the failed DPU vmwNsxTDataCenterDPUId and invoking `esxcli network vswitch dvs vmware lacp status get`. | ||||
| !vmwNsxTTransportNodeHealthLAGMemberDownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.18.0.10 | |||
notification · current LACP on DPU vmwNsxTDataCenterDPUId reporting member up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTransportNodeHealthTransportNodeUplinkDownOnDPU | 1.3.6.1.4.1.6876.120.1.0.18.0.11 | |||
notification · current Uplink on DPU vmwNsxTDataCenterDPUId is going down. Action required: Check the physical NICs' status of uplinks on DPU vmwNsxTDataCenterDPUId. Find out the mapped name of this physical NIC on host, then perform checking on UI. 1. In the NSX UI navigate to Fabric | Nodes | Transport Nodes | Host Transport Nodes. 2. In the Host Transport Nodes list, check the Node Status column. Find the Transport node with the degraded or down Node Status. 3. Select <transport node> | Monitor. Check the status details of the bond(uplink) which is reporting degraded or down. To avoid a degraded state, ensure all uplink interfaces are connected and up regardless of whether they are in use or not. | ||||
| !vmwNsxTTransportNodeHealthTransportNodeUplinkDownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.18.0.12 | |||
notification · current Uplink on DPU vmwNsxTDataCenterDPUId is going up. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTInfrastructureServiceFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.19 | |||
node · current Notifications applicable to the InfrastructureService feature have this OID prefix. | ||||
| NvmwNsxTInfrastructureServiceFeature | 1.3.6.1.4.1.6876.120.1.0.19.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for InfrastructureService feature notifications. | ||||
| !vmwNsxTInfrastructureServiceEdgeServiceStatusChanged | 1.3.6.1.4.1.6876.120.1.0.19.0.1 | |||
notification · current The service vmwNsxTDataCenterEdgeServiceName changed from vmwNsxTDataCenterPreviousServiceState to vmwNsxTDataCenterCurrentServiceState. vmwNsxTDataCenterServiceDownReason Action required: On the Edge node, verify the service hasn't exited due to an error by looking for core files in the /var/log/core directory. In addition, invoke the NSX CLI command `get services` to confirm whether the service is stopped. If so, invoke `start service <service-name>` to restart the service.
| ||||
| !vmwNsxTInfrastructureServiceEdgeServiceStatusChangedClear | 1.3.6.1.4.1.6876.120.1.0.19.0.2 | |||
notification · current The service vmwNsxTDataCenterEdgeServiceName changed from vmwNsxTDataCenterPreviousServiceState to vmwNsxTDataCenterCurrentServiceState. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTInfrastructureServiceEdgeServiceStatusDown | 1.3.6.1.4.1.6876.120.1.0.19.0.3 | |||
notification · current The service vmwNsxTDataCenterEdgeServiceName is down for at least one minute. vmwNsxTDataCenterServiceDownReason Action required: On the Edge node, verify the service hasn't exited due to an error by looking for core files in the /var/log/core directory. In addition, invoke the NSX CLI command `get services` to confirm whether the service is stopped. If so, invoke `start service <service-name>` to restart the service. | ||||
| !vmwNsxTInfrastructureServiceEdgeServiceStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.19.0.4 | |||
notification · current The service vmwNsxTDataCenterEdgeServiceName is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTInfrastructureServiceServiceStatusUnknown | 1.3.6.1.4.1.6876.120.1.0.19.0.7 | |||
notification · current The service vmwNsxTDataCenterServiceName has been unresponsive for 10 seconds. Action required: Verify vmwNsxTDataCenterServiceName service is still running by invoking `/etc/init.d/vmwNsxTDataCenterServiceName status`. If the service is reported as running, it may need to get restarted which can be done by `/etc/init.d/vmwNsxTDataCenterServiceName restart`. Rerun the status command to verify the service is now running. If the script `/etc/init.d/vmwNsxTDataCenterServiceName` is unavailable, invoke `systemctl vmwNsxTDataCenterServiceName status` and restart by `systemctl vmwNsxTDataCenterServiceName restart` with root priviledges. If restarting the service does not resolve the issue or if the issue reoccurs after a successful restart, contact VMware Support. | ||||
| !vmwNsxTInfrastructureServiceServiceStatusUnknownClear | 1.3.6.1.4.1.6876.120.1.0.19.0.8 | |||
notification · current The service vmwNsxTDataCenterServiceName is responsive again. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTInfrastructureServiceApplicationCrashed | 1.3.6.1.4.1.6876.120.1.0.19.0.9 | |||
notification · current Application on NSX node vmwNsxTDataCenterNodeDisplayOrHostName has crashed. The number of core files found is vmwNsxTDataCenterCoreDumpCount. Collect the Support Bundle including core dump files and contact VMware Support team. Action required: Collect Support Bundle for NSX node vmwNsxTDataCenterNodeDisplayOrHostName using NSX Manager UI or API. Note, core dumps can be set to move or copy into NSX Tech Support Bundle in order to remove or preserve the local copy on node. Copy of Support Bundle with core dump files is essential for VMware Support team to troubleshoot the issue and it is best recommended to save a latest copy of Tech Support Bundle including core dump files before removing core dump files from system. Refer KB article for more details. | ||||
| !vmwNsxTInfrastructureServiceApplicationCrashedClear | 1.3.6.1.4.1.6876.120.1.0.19.0.10 | |||
notification · current All core dump files are withdrawn from system. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTInfrastructureServiceServiceStatusUnknownOnDPU | 1.3.6.1.4.1.6876.120.1.0.19.0.11 | |||
notification · current The service vmwNsxTDataCenterServiceName on DPU vmwNsxTDataCenterDPUId has been unresponsive for 10 seconds. Action required: Verify vmwNsxTDataCenterServiceName service on DPU vmwNsxTDataCenterDPUId is still running by invoking `/etc/init.d/vmwNsxTDataCenterServiceName status`. If the service is reported as running, it may need to get restarted which can be done by `/etc/init.d/vmwNsxTDataCenterServiceName restart`. Rerun the status command to verify the service is now running. If restarting the service does not resolve the issue or if the issue reoccurs after a successful restart, contact VMware Support. | ||||
| !vmwNsxTInfrastructureServiceServiceStatusUnknownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.19.0.12 | |||
notification · current The service vmwNsxTDataCenterServiceName on DPU vmwNsxTDataCenterDPUId is responsive again. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTInfrastructureServiceMetricsDeliveryFailure | 1.3.6.1.4.1.6876.120.1.0.19.0.19 | |||
notification · current Failed to deliver metrics from SHA to target vmwNsxTDataCenterMetricsTargetAlias(vmwNsxTDataCenterMetricsTargetAddress:vmwNsxTDataCenterMetricsTargetPort).
Action required:
User should perform the following checks in order to exclude the problem causing the failure:
1. Check if target address vmwNsxTDataCenterMetricsTargetAddress and port vmwNsxTDataCenterMetricsTargetPort (default is 443 in the case port is not specified)
passed down to connect is the expected target,
2. Check if the certificate is correct by
`/opt/vmware/nsx-nestdb/bin/nestdb-cli --cmd 'put vmware.nsx.nestdb.CommonAgentHostConfigMsg'`,
3. Check if target vmwNsxTDataCenterMetricsTargetAddress is reachable,
4. Check if the metric manager on target vmwNsxTDataCenterMetricsTargetAddress is running by `docker ps | grep metrics_manager`,
5. Check if port vmwNsxTDataCenterMetricsTargetPort is opened by `netstat -a | grep vmwNsxTDataCenterMetricsTargetPort` on target,
6. Check if ALLOW firewall rule is installed on the node by `iptables -S OUTPUT | grep vmwNsxTDataCenterMetricsTargetPort`(EDGE/UA) or
`localcli network firewall ruleset list | grep nsx-sha-tsdb`(ESX),
7. Restart SHA daemon to see if it could be solved by `/etc/init.d/netopa restart`(ESX) or `/etc/init.d/nsx-netopa restart`(EDGE)
or `/etc/init.d/nsx-sha restart`(UA).
| ||||
| !vmwNsxTInfrastructureServiceMetricsDeliveryFailureClear | 1.3.6.1.4.1.6876.120.1.0.19.0.20 | |||
notification · current Metrics delivery to target vmwNsxTDataCenterMetricsTargetAlias(vmwNsxTDataCenterMetricsTargetAddress:vmwNsxTDataCenterMetricsTargetPort) recovered. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTDHCPFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.20 | |||
node · current Notifications applicable to the DHCP feature have this OID prefix. | ||||
| NvmwNsxTDHCPFeature | 1.3.6.1.4.1.6876.120.1.0.20.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for DHCP feature notifications. | ||||
| !vmwNsxTDHCPPoolLeaseAllocationFailed | 1.3.6.1.4.1.6876.120.1.0.20.0.1 | |||
notification · current The addresses in IP Pool vmwNsxTDataCenterEntityId of DHCP Server vmwNsxTDataCenterDHCPServerId have been exhausted. The last DHCP request has failed and future requests will fail. Action required: Review the DHCP pool configuration in the NSX UI or on the Edge node where the DHCP server is running by invoking the NSX CLI command `get dhcp ip-pool`. Also review the current active leases on the Edge node by invoking the NSX CLI command `get dhcp lease`. Compare the leases to the number of active VMs. Consider reducing the lease time on the DHCP server configuration if the number of VMs are low compared to the number of active leases. Also consider expanding the pool range for the DHCP server by visiting the Networking | Segments | Segment page in the NSX UI. | ||||
| !vmwNsxTDHCPPoolLeaseAllocationFailedClear | 1.3.6.1.4.1.6876.120.1.0.20.0.2 | |||
notification · current IP Pool vmwNsxTDataCenterEntityId of DHCP Server vmwNsxTDataCenterDHCPServerId is no longer exhausted. A lease is successfully allocated to the last DHCP request. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDHCPPoolOverloaded | 1.3.6.1.4.1.6876.120.1.0.20.0.3 | |||
notification · current The DHCP Server vmwNsxTDataCenterDHCPServerId IP Pool vmwNsxTDataCenterEntityId usage is approaching exhaustion with vmwNsxTDataCenterDHCPPoolUsage% IPs allocated. Action required: Review the DHCP pool configuration in the NSX UI or on the Edge node where the DHCP server is running by invoking the NSX CLI command `get dhcp ip-pool`. Also review the current active leases on the Edge node by invoking the NSX CLI command `get dhcp lease`. Compare the leases to the number of active VMs. Consider reducing the lease time on the DHCP server configuration if the number of VMs are low compared to the number of active leases. Also consider expanding the pool range for the DHCP server by visiting the Networking | Segments | Segment page in the NSX UI. | ||||
| !vmwNsxTDHCPPoolOverloadedClear | 1.3.6.1.4.1.6876.120.1.0.20.0.4 | |||
notification · current The DHCP Server vmwNsxTDataCenterDHCPServerId IP Pool vmwNsxTDataCenterEntityId has fallen below the high usage threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTHighAvailabilityFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.21 | |||
node · current Notifications applicable to the HighAvailability feature have this OID prefix. | ||||
| NvmwNsxTHighAvailabilityFeature | 1.3.6.1.4.1.6876.120.1.0.21.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for HighAvailability feature notifications. | ||||
| !vmwNsxTHighAvailabilityTier0GatewayFailover | 1.3.6.1.4.1.6876.120.1.0.21.0.9 | |||
notification · current The tier0 gateway vmwNsxTDataCenterEntityId failover from vmwNsxTDataCenterPreviousGatewayState to vmwNsxTDataCenterCurrentGatewayState, service-router vmwNsxTDataCenterServiceRouterId. Action required: Invoke the NSX CLI command `get logical-router <service_router_id>` to identify the tier0 service-router vrf ID. Switch to the vrf context by invoking `vrf <vrf-id>` then invoke `get high-availability status` to determine the service that is down.
| ||||
| !vmwNsxTHighAvailabilityTier0GatewayFailoverClear | 1.3.6.1.4.1.6876.120.1.0.21.0.10 | |||
notification · current The tier0 gateway vmwNsxTDataCenterEntityId is now up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTHighAvailabilityTier1GatewayFailover | 1.3.6.1.4.1.6876.120.1.0.21.0.11 | |||
notification · current The tier1 gateway vmwNsxTDataCenterEntityId failover from vmwNsxTDataCenterPreviousGatewayState to vmwNsxTDataCenterCurrentGatewayState, service-router vmwNsxTDataCenterServiceRouterId. Action required: Invoke the NSX CLI command `get logical-router <service_router_id>` to identify the tier1 service-router vrf ID. Switch to the vrf context by invoking `vrf <vrf-id>` then invoke `get high-availability status` to determine the service that is down.
| ||||
| !vmwNsxTHighAvailabilityTier1GatewayFailoverClear | 1.3.6.1.4.1.6876.120.1.0.21.0.12 | |||
notification · current The tier1 gateway vmwNsxTDataCenterEntityId is now up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTHighAvailabilityTier0ServiceGroupFailover | 1.3.6.1.4.1.6876.120.1.0.21.0.13 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId currently does not have an active instance. It is in state vmwNsxTDataCenterHaState (where 0 is down, 1 is standby and 2 is active) on Edge node vmwNsxTDataCenterTransportNodeId and in state vmwNsxTDataCenterHaState2 on Edge node vmwNsxTDataCenterTransportNodeId2. Action required: Invoke the NSX CLI command `get logical-router <service_router_id> service_group` to check all service-groups configured under a given service-router. Examine the output for reason for a service-group leaving active state.
| ||||
| !vmwNsxTHighAvailabilityTier0ServiceGroupFailoverClear | 1.3.6.1.4.1.6876.120.1.0.21.0.14 | |||
notification · current Tier0 service-group cluster vmwNsxTDataCenterEntityId now has one active instance on Edge node vmwNsxTDataCenterTransportNodeId. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTHighAvailabilityTier1ServiceGroupFailover | 1.3.6.1.4.1.6876.120.1.0.21.0.15 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId currently does not have an active instance. It is in state vmwNsxTDataCenterHaState (where 0 is down, 1 is standby and 2 is active) on Edge node vmwNsxTDataCenterTransportNodeId and in state vmwNsxTDataCenterHaState2 on Edge node vmwNsxTDataCenterTransportNodeId2. Action required: Invoke the NSX CLI command `get logical-router <service_router_id> service_group` to check all service-groups configured under a given service-router. Examine the output for reason for a service-group leaving active state.
| ||||
| !vmwNsxTHighAvailabilityTier1ServiceGroupFailoverClear | 1.3.6.1.4.1.6876.120.1.0.21.0.16 | |||
notification · current Tier1 service-group cluster vmwNsxTDataCenterEntityId now has one active instance on Edge node vmwNsxTDataCenterTransportNodeId. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTHighAvailabilityTier0ServiceGroupReducedRedundancy | 1.3.6.1.4.1.6876.120.1.0.21.0.17 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId attached to Tier0 service-router vmwNsxTDataCenterServiceRouterId on Edge node vmwNsxTDataCenterTransportNodeId has failed. As a result, the service-group cluster currently does not have a standby instance. Action required: Invoke the NSX CLI command `get logical-router <service_router_id> service_group` to check all service-groups configured under a given service-router. Examine the output for failure reason for a previously standby service-group. | ||||
| !vmwNsxTHighAvailabilityTier0ServiceGroupReducedRedundancyClear | 1.3.6.1.4.1.6876.120.1.0.21.0.18 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId is in state vmwNsxTDataCenterHaState (where 0 is down, 1 is standby and 2 is active) on Edge node vmwNsxTDataCenterTransportNodeId and state vmwNsxTDataCenterHaState2 on Edge node vmwNsxTDataCenterTransportNodeId2. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTHighAvailabilityTier1ServiceGroupReducedRedundancy | 1.3.6.1.4.1.6876.120.1.0.21.0.19 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId attached to Tier1 service-router vmwNsxTDataCenterServiceRouterId on Edge node vmwNsxTDataCenterTransportNodeId has failed. As a result, the service-group cluster currently does not have a standby instance. Action required: Invoke the NSX CLI command `get logical-router <service_router_id> service_group` to check all service-groups configured under a given service-router. Examine the output for failure reason for a previously standby service-group. | ||||
| !vmwNsxTHighAvailabilityTier1ServiceGroupReducedRedundancyClear | 1.3.6.1.4.1.6876.120.1.0.21.0.20 | |||
notification · current Service-group cluster vmwNsxTDataCenterEntityId is in state vmwNsxTDataCenterHaState (where 0 is down, 1 is standby and 2 is active) on Edge node vmwNsxTDataCenterTransportNodeId and state vmwNsxTDataCenterHaState2 on Edge node vmwNsxTDataCenterTransportNodeId2. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTCapacityFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.22 | |||
node · current Notifications applicable to the Capacity feature have this OID prefix. | ||||
| NvmwNsxTCapacityFeature | 1.3.6.1.4.1.6876.120.1.0.22.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Capacity feature notifications. | ||||
| !vmwNsxTCapacityMaximumCapacity | 1.3.6.1.4.1.6876.120.1.0.22.0.1 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount which is above the maximum supported count of vmwNsxTDataCenterMaxSupportedCapacityCount. Action required: Ensure that the number of NSX objects created is within the limits supported by NSX. If there are any unused objects, delete them using the respective NSX UI or API from the system. Consider increasing the form factor of all Manager nodes and/or Edge nodes. Note that the form factor of each node type should be the same. If not the same, the capacity limits for the lowest form factor deployed are used.
| ||||
| !vmwNsxTCapacityMaximumCapacityClear | 1.3.6.1.4.1.6876.120.1.0.22.0.2 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount and is at or below the maximum supported count of vmwNsxTDataCenterMaxSupportedCapacityCount. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTCapacityMaximumCapacityThreshold | 1.3.6.1.4.1.6876.120.1.0.22.0.3 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount which is above the maximum capacity threshold of vmwNsxTDataCenterMaxCapacityThreshold%. Action required: Navigate to the capacity page in the NSX UI and review current usage versus threshold limits. If the current usage is expected, consider increasing the maximum threshold values. If the current usage is unexpected, review the network policies configured to decrease usage at or below the maximum threshold.
| ||||
| !vmwNsxTCapacityMaximumCapacityThresholdClear | 1.3.6.1.4.1.6876.120.1.0.22.0.4 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount and is at or below the maximum capacity threshold of vmwNsxTDataCenterMaxCapacityThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTCapacityMinimumCapacityThreshold | 1.3.6.1.4.1.6876.120.1.0.22.0.5 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount which is above the minimum capacity threshold of vmwNsxTDataCenterMinCapacityThreshold%. Action required: Navigate to the capacity page in the NSX UI and review current usage versus threshold limits. If the current usage is expected, consider increasing the minimum threshold values. If the current usage is unexpected, review the network policies configured to decrease usage at or below the minimum threshold.
| ||||
| !vmwNsxTCapacityMinimumCapacityThresholdClear | 1.3.6.1.4.1.6876.120.1.0.22.0.6 | |||
notification · current The number of objects defined in the system for vmwNsxTDataCenterCapacityDisplayName has reached vmwNsxTDataCenterCapacityUsageCount and is at or below the minimum capacity threshold of vmwNsxTDataCenterMinCapacityThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTAuditLogHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.24 | |||
node · current Notifications applicable to the AuditLogHealth feature have this OID prefix. | ||||
| NvmwNsxTAuditLogHealthFeature | 1.3.6.1.4.1.6876.120.1.0.24.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for AuditLogHealth feature notifications. | ||||
| !vmwNsxTAuditLogHealthAuditLogFileUpdateError | 1.3.6.1.4.1.6876.120.1.0.24.0.1 | |||
notification · current At least one of the monitored log files has read-only permissions or has incorrect user/group ownership on Manager, Global Manager, Edge, Public Cloud Gateway, KVM or Linux Physical Server nodes. Or log folder is missing in Windows Physical Server nodes. Or rsyslog.log is missing on Manager, Global Manager, Edge or Public Cloud Gateway nodes. Action required: 1. On Manager and Global Managaer nodes, Edge and Public Cloud Gateway nodes, Ubuntu KVM Host nodes ensure the permissions for the /var/log directory is 775 and the ownership is root:syslog. One Rhel KVM and BMS Host nodes ensure the permission for the /var/log directory is 755 and the ownership is root:root. 2. On Manager and Global Manager nodes, ensure the file permissions for auth.log, nsx-audit.log, nsx-audit-write.log, rsyslog.log and syslog under /var/log is 640 and ownership is syslog:admin. 3. On Edge and Public Cloud Gateway nodes, ensure the file permissions for rsyslog.log and syslog under /var/log is 640 and ownership is syslog:admin. 4. On Ubuntu KVM Host and Ubuntu Physical Server nodes, ensure the file permissions of auth.log and vmware/nsx-syslog under /var/log is 640 and ownership is syslog:admin. 5. On Rhel KVM Host nodes and Centos/Rhel/Sles Physical Server nodes, ensure the file permission of vmware/nsx-syslog under /var/log is 640 and ownership is root:root. 6. If any of these files have incorrect permissions or ownership, invoke the commands `chmod <mode> <path>` and `chown <user>:<group> <path>`. 7. If rsyslog.log is missing on Manager, Global Manager, Edge or Public Cloud Gateway nodes, invoke the NSX CLI command `restart service syslog` which restarts the logging service and regenerates /var/log/rsyslog.log. 8. On Windows Physical Server nodes, ensure the log folder: C:\ProgramData\VMware\NSX\Logs exists. If not, re-install NSX on the Windows Physical Server nodes. | ||||
| !vmwNsxTAuditLogHealthAuditLogFileUpdateErrorClear | 1.3.6.1.4.1.6876.120.1.0.24.0.2 | |||
notification · current All monitored log files have the correct file permissions and ownership and rsyslog.log exists on Manager, Global Manager, Edge or Public Cloud Gateway nodes. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTAuditLogHealthRemoteLoggingServerError | 1.3.6.1.4.1.6876.120.1.0.24.0.3 | |||
notification · current Log messages to logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) cannot be delivered possibly due to an unresolvable FQDN, an invalid TLS certificate or missing NSX appliance iptables rule. Action required: 1. Ensure that vmwNsxTDataCenterHostnameOrIPAddressWithPort is the correct hostname or IP address and port. 2. If the logging server is specified using a FQDN, ensure the FQDN is resolvable from the NSX appliance using the NSX CLI command `nslookup <fqdn>`. If not resolvable, verify the correct FQDN is specified and the network DNS server has the required entry for the FQDN. 3. If the logging server is configured to use TLS, verify the specified certificate is valid. For example, ensure the logging server is actually using the certificate or verify the certificate has not expired using the openssl command `openssl x509 -in <cert-file-path> -noout -dates`. 4. NSX appliances use iptables rules to explicitly allow outgoing traffic. Verify the iptables rule for the logging server is configured properly by invoking the NSX CLI command `verify logging-servers` which re-configures logging server iptables rules as needed. 5. If for any reason the logging server is misconfigured, it should be deleted using the NSX CLI `del logging-server <hostname-or-ip-address[:port]> proto <proto> level <level>` command and re-added with the correct configuration. | ||||
| !vmwNsxTAuditLogHealthRemoteLoggingServerErrorClear | 1.3.6.1.4.1.6876.120.1.0.24.0.4 | |||
notification · current Configuration for logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) appear correct. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTRoutingFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.28 | |||
node · current Notifications applicable to the Routing feature have this OID prefix. | ||||
| NvmwNsxTRoutingFeature | 1.3.6.1.4.1.6876.120.1.0.28.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Routing feature notifications. | ||||
| !vmwNsxTRoutingBGPDown | 1.3.6.1.4.1.6876.120.1.0.28.0.1 | |||
notification · current In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is down. Reason: vmwNsxTDataCenterFailureReason. Action required: 1. Invoke the NSX CLI command `get logical-routers`. 2. Switch to service-router vmwNsxTDataCenterSrId. If the reason indicates Network or config error - 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. If the reason indicates `Edge is not ready`, check why the Edge node is not in good state. 4. Invoke the NSX CLI command `get edge-cluster status` to check reason why Edge node might be down. 5. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well. 6. Check any Edge health related alarms to get more information. Check /var/log/syslog to see if there are any errors related to BGP connectivity.
| ||||
| !vmwNsxTRoutingBGPDownClear | 1.3.6.1.4.1.6876.120.1.0.28.0.2 | |||
notification · current In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingStaticRoutingRemoved | 1.3.6.1.4.1.6876.120.1.0.28.0.5 | |||
notification · current In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was removed because BFD was down. Action required: The static routing entry was removed because the BFD session was down. 1. Invoke the NSX CLI command `get logical-routers`. 2. Switch to the service-router vmwNsxTDataCenterSrId. 3. Invoke the NSX CLI command `ping <BFD peer IP address>` to verify the connectivity. Also, verify the configuration in both NSX and the BFD peer to ensure that timers have not been changed. | ||||
| !vmwNsxTRoutingStaticRoutingRemovedClear | 1.3.6.1.4.1.6876.120.1.0.28.0.6 | |||
notification · current In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was re-added as BFD recovered. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingBFDDownOnExternalInterface | 1.3.6.1.4.1.6876.120.1.0.28.0.7 | |||
notification · current In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is down. Action required: 1. Invoke the NSX CLI command `get logical-routers`. 2. Switch to the service router vmwNsxTDataCenterSrId 3. Invoke the NSX CLI command `ping vmwNsxTDataCenterPeerAddress` to verify the connectivity. | ||||
| !vmwNsxTRoutingBFDDownOnExternalInterfaceClear | 1.3.6.1.4.1.6876.120.1.0.28.0.8 | |||
notification · current In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingRoutingDown | 1.3.6.1.4.1.6876.120.1.0.28.0.9 | |||
notification · current All BGP/BFD sessions are down. Action required: Invoke the NSX CLI command `get logical-routers` to get the tier0 service router and switch to this vrf, then invoke the following NSX CLI commands. 1. `ping <BFD peer IP address>` to verify connectivity. 2. `get bfd-config` and `get bfd-sessions` to check if BFD is running well. 3. `get bgp neighbor summary` to check if BGP is running well. Also check /var/log/syslog to see if there are any errors related to BGP connectivity. | ||||
| !vmwNsxTRoutingRoutingDownClear | 1.3.6.1.4.1.6876.120.1.0.28.0.10 | |||
notification · current At least one BGP/BFD session up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingOSPFNeighborWentDown | 1.3.6.1.4.1.6876.120.1.0.28.0.11 | |||
notification · current OSPF neighbor vmwNsxTDataCenterPeerAddress moved from full to another state. Action required: 1. Invoke the NSX CLI command `get logical-routers` to get the vrf id and switch to TIER0 service router. 2. Run `get ospf neighbor` to check the current state of this neighbor. If the neighbor is not listed in the output, the neighbor has gone down or out of the network. 3. Invoke the NSX CLI command `ping <OSPF neighbor IP address>` to verify the connectivity. 4. Also, verify the configuration for both NSX and peer router to ensure that timers and area-id match. 5. Check /var/log/syslog to see if there are any errors related to connectivity. | ||||
| !vmwNsxTRoutingOSPFNeighborWentDownClear | 1.3.6.1.4.1.6876.120.1.0.28.0.12 | |||
notification · current OSPF neighbor vmwNsxTDataCenterPeerAddress moved to full state. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingProxyARPNotConfiguredForServiceIP | 1.3.6.1.4.1.6876.120.1.0.28.0.13 | |||
notification · current Proxy ARP for Service IP vmwNsxTDataCenterServiceIP and Service entity vmwNsxTDataCenterEntityId is not configured as the number of ARP proxy entries generated due to overlap of the Service IP with subnet of lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId has exceeded the allowed threshold limit of 16384. Action required: Reconfigure the Service IP vmwNsxTDataCenterServiceIP for the Service entity vmwNsxTDataCenterEntityId or change the subnet of the lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId so that the proxy ARP entries generated due to the overlap between the Service IP and the subnet of lrport is less than the allowed threshold limit of 16384. | ||||
| !vmwNsxTRoutingProxyARPNotConfiguredForServiceIPClear | 1.3.6.1.4.1.6876.120.1.0.28.0.14 | |||
notification · current Proxy ARP for Service entity vmwNsxTDataCenterEntityId is generated successfully as the overlap of service IP with subnet of lrport vmwNsxTDataCenterLrportId on Router vmwNsxTDataCenterLrId is within the allowed limit of 16384 entries. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproaching | 1.3.6.1.4.1.6876.120.1.0.28.0.39 | |||
notification · current Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP reaches vmwNsxTDataCenterPrefixesCountThreshold. Limit defined for this peer is vmwNsxTDataCenterPrefixesCountMax. Action required: 1. Check the BGP routing policies in the external router. 2. Consider reducing the number of routes advertised by the BGP peer by applying routing policies and filters to the external router. 3. If required, increase the maximum prefixes settings under the BGP neighbor configuration section.
| ||||
| !vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproachingClear | 1.3.6.1.4.1.6876.120.1.0.28.0.40 | |||
notification · current Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountThreshold. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceeded | 1.3.6.1.4.1.6876.120.1.0.28.0.41 | |||
notification · current Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP exceeded the limit defined for this peer of vmwNsxTDataCenterPrefixesCountMax. Action required: 1. Check the BGP routing policies in the external router. 2. Consider reducing the number of routes advertised by the BGP peer by applying routing policies and filters to the external router. 3. If required, increase the maximum prefixes settings under the BGP neighbor configuration section.
| ||||
| !vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceededClear | 1.3.6.1.4.1.6876.120.1.0.28.0.42 | |||
notification · current Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountMax. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTRoutingMaximumIPv4RouteLimitApproaching | 1.3.6.1.4.1.6876.120.1.0.28.0.43 | |||
notification · current IPv4 routes limit has reached vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: 1. Check route redistribution policies and routes received from all external peers. 2. Consider reducing the number of routes by applying routing policies and filters accordingly. | ||||
| !vmwNsxTRoutingMaximumIPv4RouteLimitApproachingClear | 1.3.6.1.4.1.6876.120.1.0.28.0.44 | |||
notification · current IPv4 routes are within the limit of vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingMaximumIPv4RouteLimitExceeded | 1.3.6.1.4.1.6876.120.1.0.28.0.45 | |||
notification · current IPv4 routes has exceeded limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: 1. Check route redistribution policies and routes received from all external peers. 2. Consider reducing the number of routes by applying routing policies and filters accordingly. | ||||
| !vmwNsxTRoutingMaximumIPv4RouteLimitExceededClear | 1.3.6.1.4.1.6876.120.1.0.28.0.46 | |||
notification · current IPv4 routes are within the limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproaching | 1.3.6.1.4.1.6876.120.1.0.28.0.47 | |||
notification · current Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP reaches vmwNsxTDataCenterPrefixesCountThreshold. Limit defined for this peer is vmwNsxTDataCenterPrefixesCountMax. Action required: 1. Check the BGP routing policies in the external router. 2. Consider reducing the number of routes advertised by the BGP peer by applying routing policies and filters to the external router. 3. If required, increase the maximum prefixes settings under the BGP neighbor configuration section.
| ||||
| !vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproachingClear | 1.3.6.1.4.1.6876.120.1.0.28.0.48 | |||
notification · current Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountThreshold. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceeded | 1.3.6.1.4.1.6876.120.1.0.28.0.49 | |||
notification · current Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP exceeded the limit defined for this peer of vmwNsxTDataCenterPrefixesCountMax. Action required: 1. Check the BGP routing policies in the external router. 2. Consider reducing the number of routes advertised by the BGP peer by applying routing policies and filters to the external router. 3. If required, increase the maximum prefixes settings under the BGP neighbor configuration section.
| ||||
| !vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceededClear | 1.3.6.1.4.1.6876.120.1.0.28.0.50 | |||
notification · current Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountMax. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTRoutingMaximumIPv6RouteLimitApproaching | 1.3.6.1.4.1.6876.120.1.0.28.0.51 | |||
notification · current IPv6 routes limit has reached vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: 1. Check route redistribution policies and routes received from all external peers. 2. Consider reducing the number of routes by applying routing policies and filters accordingly. | ||||
| !vmwNsxTRoutingMaximumIPv6RouteLimitApproachingClear | 1.3.6.1.4.1.6876.120.1.0.28.0.52 | |||
notification · current IPv6 routes are within the limit of vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTRoutingMaximumIPv6RouteLimitExceeded | 1.3.6.1.4.1.6876.120.1.0.28.0.53 | |||
notification · current IPv6 routes has exceeded limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: 1. Check route redistribution policies and routes received from all external peers. 2. Consider reducing the number of routes by applying routing policies and filters accordingly. | ||||
| !vmwNsxTRoutingMaximumIPv6RouteLimitExceededClear | 1.3.6.1.4.1.6876.120.1.0.28.0.54 | |||
notification · current IPv6 routes are within the limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTDNSFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.30 | |||
node · current Notifications applicable to the DNS feature have this OID prefix. | ||||
| NvmwNsxTDNSFeature | 1.3.6.1.4.1.6876.120.1.0.30.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for DNS feature notifications. | ||||
| !vmwNsxTDNSForwarderDisabled | 1.3.6.1.4.1.6876.120.1.0.30.0.1 | |||
notification · current DNS forwarder vmwNsxTDataCenterEntityId is disabled. Action required: 1. Invoke the NSX CLI command `get dns-forwarders status` to verify if the DNS forwarder is in the disabled state. 2. Use NSX Policy API or Manager API to enable the DNS forwarder it should not be in the disabled state. | ||||
| !vmwNsxTDNSForwarderDisabledClear | 1.3.6.1.4.1.6876.120.1.0.30.0.2 | |||
notification · current DNS forwarder vmwNsxTDataCenterEntityId is enabled. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDNSForwarderDown | 1.3.6.1.4.1.6876.120.1.0.30.0.3 | |||
notification · current DNS forwarder vmwNsxTDataCenterEntityId is not running. This is impacting the identified DNS Forwarder that is currently enabled. Action required: 1. Invoke the NSX CLI command `get dns-forwarders status` to verify if the DNS forwarder is in down state. 2. Check /var/log/syslog to see if there are errors reported. 3. Collect a support bundle and contact the NSX support team. | ||||
| !vmwNsxTDNSForwarderDownClear | 1.3.6.1.4.1.6876.120.1.0.30.0.4 | |||
notification · current DNS forwarder vmwNsxTDataCenterEntityId is running again. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDNSForwarderUpstreamServerTimeout | 1.3.6.1.4.1.6876.120.1.0.30.0.5 | |||
notification · current DNS forwarder vmwNsxTDataCenterIntentPath(vmwNsxTDataCenterDNSId) did not receive a timely response from upstream server vmwNsxTDataCenterDNSUpstreamIP. Compute instance connectivity to timed out FQDNs may be impacted. Action required: 1. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? address=<address>&server_ip=vmwNsxTDataCenterDNSUpstreamIP&source_ip=<source_ip>. This API request triggers a DNS lookup to the upstream server in the DNS forwarder's network namespace. <address> is the IP address or FQDN in the same domain as the upstream server. <source_ip> is an IP address in the upstream server's zone. If the API returns a connection timed out response, there is likely a network error or upstream server problem. Check why DSN lookups are not reaching the upstream server or why the upstream server is not returning a response. If the API response indicates the upstream server is answering, proceed to step 2. 2. Invoke the NSX API GET /api/v1/dns/forwarders/vmwNsxTDataCenterDNSId/nslookup? address=<address>. This API request triggers a DNS lookup to the DNS forwarder. If the API returns a valid response, the upstream server may have recovered and this alarm should get resolved within a few minutes. If the API returns a connection timed out response, proceed to step 3. 3. Invoke the NSX CLI command `get dns-forwarder vmwNsxTDataCenterDNSId live-debug server-ip vmwNsxTDataCenterDNSUpstreamIP`. This command triggers live debugging on the upstream server and logs details and statistics showing why the DNS forwarder is not getting a response. | ||||
| !vmwNsxTDNSForwarderUpstreamServerTimeoutClear | 1.3.6.1.4.1.6876.120.1.0.30.0.6 | |||
notification · current DNS forwarder vmwNsxTDataCenterIntentPath(vmwNsxTDataCenterDNSId) upstream server vmwNsxTDataCenterDNSUpstreamIP is normal. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTDistributedFirewallFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.31 | |||
node · current Notifications applicable to the DistributedFirewall feature have this OID prefix. | ||||
| NvmwNsxTDistributedFirewallFeature | 1.3.6.1.4.1.6876.120.1.0.31.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for DistributedFirewall feature notifications. | ||||
| !vmwNsxTDistributedFirewallDFWCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.31.0.1 | |||
notification · current The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Consider re-balancing the VM workloads on this host to other hosts. Review the security design for optimization. For example, use the apply-to configuration if the rules are not applicable to the entire datacenter. | ||||
| !vmwNsxTDistributedFirewallDFWCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.31.0.2 | |||
notification · current The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.31.0.3 | |||
notification · current The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: View the current DFW memory usage by invoking the NSX CLI command `get firewall thresholds` on the host. Consider re-balancing the workloads on this host to other hosts.
| ||||
| !vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.31.0.4 | |||
notification · current The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTDistributedFirewallDFWSessionCountHigh | 1.3.6.1.4.1.6876.120.1.0.31.0.5 | |||
notification · current The DFW session count is high on Transport node vmwNsxTDataCenterEntityId, it has reached vmwNsxTDataCenterSystemResourceUsage% which is at or above the threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review the network traffic load level of the workloads on the host. Consider re-balancing the workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedFirewallDFWSessionCountHighClear | 1.3.6.1.4.1.6876.120.1.0.31.0.6 | |||
notification · current The DFW session count on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% which is below the the threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWVmotionFailure | 1.3.6.1.4.1.6876.120.1.0.31.0.7 | |||
notification · current The DFW vMotion for DFW filter vmwNsxTDataCenterEntityId on destination host vmwNsxTDataCenterTransportNodeName has failed and the port for the entity has been disconnected. Action required: Check VMs on the host in NSX Manager, manually repush the DFW configuration through NSX Manager UI. The DFW policy to be repushed can be traced by the DFW filter vmwNsxTDataCenterEntityId. Also consider finding the VM to which the DFW filter is attached and restart it. | ||||
| !vmwNsxTDistributedFirewallDFWVmotionFailureClear | 1.3.6.1.4.1.6876.120.1.0.31.0.8 | |||
notification · current The DFW configuration for DFW filter vmwNsxTDataCenterEntityId on the destination host vmwNsxTDataCenterTransportNodeName has succeeded and error caused by DFW vMotion failure cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPervNICExceeded | 1.3.6.1.4.1.6876.120.1.0.31.0.9 | |||
notification · current The DFW rules limit for VIF vmwNsxTDataCenterEntityId on destination host vmwNsxTDataCenterTransportNodeName is about to exceed the maximum limit. Action required: Log in into the ESX host vmwNsxTDataCenterTransportNodeName and invoke the NSX CLI command `get firewall <VIF_UUID> ruleset rules` to get the rule statistics for rules configured on the corresponding VIF. Reduce the number of rules configured for VIF vmwNsxTDataCenterEntityId. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPervNICExceededClear | 1.3.6.1.4.1.6876.120.1.0.31.0.10 | |||
notification · current The DFW rules limit for VIF vmwNsxTDataCenterEntityId on the destination host vmwNsxTDataCenterTransportNodeName dropped below maximum limit. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPerHostApproaching | 1.3.6.1.4.1.6876.120.1.0.31.0.11 | |||
notification · current The DFW rules limit for host vmwNsxTDataCenterTransportNodeName is approaching the maximum limit. Action required: Log in into the ESX host vmwNsxTDataCenterTransportNodeName and invoke the NSX CLI command `get firewall rule-stats total` to get the rule statistics for rules configured on the ESX host vmwNsxTDataCenterTransportNodeName. Reduce the number of rules configured for host vmwNsxTDataCenterTransportNodeName. Check the number of rules configured for various VIFs by using NSX CLI command `get firewall <VIF_UUID> ruleset rules`. Reduce the number of rules configured for various VIFs. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPerHostApproachingClear | 1.3.6.1.4.1.6876.120.1.0.31.0.12 | |||
notification · current The DFW rules limit for host vmwNsxTDataCenterTransportNodeName dropped below the threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPerHostExceeded | 1.3.6.1.4.1.6876.120.1.0.31.0.13 | |||
notification · current The DFW rules limit for host vmwNsxTDataCenterTransportNodeName is about to exceed the maximum limit. Action required: Log in into the ESX host vmwNsxTDataCenterTransportNodeName and invoke the NSX CLI command `get firewall rule-stats total` to get the rule statistics for rules configured on the ESX host vmwNsxTDataCenterTransportNodeName. Reduce the number of rules configured for host vmwNsxTDataCenterTransportNodeName. Check the number of rules configured for various VIFs by using NSX CLI command `get firewall <VIF_UUID> ruleset rules`. Reduce the number of rules configured for various VIFs. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPerHostExceededClear | 1.3.6.1.4.1.6876.120.1.0.31.0.14 | |||
notification · current The DFW rules limit for host vmwNsxTDataCenterTransportNodeName dropped below maximum limit. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPervNICApproaching | 1.3.6.1.4.1.6876.120.1.0.31.0.15 | |||
notification · current The DFW rules limit for VIF vmwNsxTDataCenterEntityId on destination host vmwNsxTDataCenterTransportNodeName is approaching the maximum limit. Action required: Log in into the ESX host vmwNsxTDataCenterTransportNodeName and invoke the NSX CLI command `get firewall <VIF_UUID> ruleset rules` to get the rule statistics for rules configured on the corresponding VIF. Reduce the number of rules configured for VIF vmwNsxTDataCenterEntityId. | ||||
| !vmwNsxTDistributedFirewallDFWRulesLimitPervNICApproachingClear | 1.3.6.1.4.1.6876.120.1.0.31.0.16 | |||
notification · current The DFW rules limit for VIF vmwNsxTDataCenterEntityId on the destination host vmwNsxTDataCenterTransportNodeName dropped below the threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWCPUUsageVeryHighOnDPU | 1.3.6.1.4.1.6876.120.1.0.31.0.17 | |||
notification · current The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% on DPU vmwNsxTDataCenterDPUId which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Consider re-balancing the VM workloads on this host to other hosts. Review the security design for optimization. For example, use the apply-to configuration if the rules are not applicable to the entire datacenter.
| ||||
| !vmwNsxTDistributedFirewallDFWCPUUsageVeryHighOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.31.0.18 | |||
notification · current The DFW CPU usage on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% on DPU vmwNsxTDataCenterDPUId which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighOnDPU | 1.3.6.1.4.1.6876.120.1.0.31.0.19 | |||
notification · current The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% on DPU vmwNsxTDataCenterDPUId which is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: View the current DFW memory usage by invoking the NSX CLI command `get firewall thresholds` on the DPU. Consider re-balancing the workloads on this host to other hosts.
| ||||
| !vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.31.0.20 | |||
notification · current The DFW Memory usage vmwNsxTDataCenterHeapType on Transport node vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterSystemResourceUsage% on DPU vmwNsxTDataCenterDPUId which is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTDistributedFirewallDFWFloodLimitWarning | 1.3.6.1.4.1.6876.120.1.0.31.0.21 | |||
notification · current The DFW flood limit for DFW filter vmwNsxTDataCenterEntityId on host vmwNsxTDataCenterTransportNodeName has reached warning level of 80% of the configured limit for protocol vmwNsxTDataCenterProtocolName. Action required: Check VMs on the host in NSX Manager, check configured flood warning level of the DFW filter vmwNsxTDataCenterEntityId for protocol vmwNsxTDataCenterProtocolName. | ||||
| !vmwNsxTDistributedFirewallDFWFloodLimitWarningClear | 1.3.6.1.4.1.6876.120.1.0.31.0.22 | |||
notification · current The warning flood limit condition for DFW filter vmwNsxTDataCenterEntityId on host vmwNsxTDataCenterTransportNodeName for protocol vmwNsxTDataCenterProtocolName is cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedFirewallDFWFloodLimitCritical | 1.3.6.1.4.1.6876.120.1.0.31.0.23 | |||
notification · current The DFW flood limit for DFW filter vmwNsxTDataCenterEntityId on host vmwNsxTDataCenterTransportNodeName has reached critical level of 98% of the configured limit for protocol vmwNsxTDataCenterProtocolName. Action required: Check VMs on the host in NSX Manager, check configured flood critical level of the DFW filter vmwNsxTDataCenterEntityId for protocol vmwNsxTDataCenterProtocolName. | ||||
| !vmwNsxTDistributedFirewallDFWFloodLimitCriticalClear | 1.3.6.1.4.1.6876.120.1.0.31.0.24 | |||
notification · current The critical flood limit condition for DFW filter vmwNsxTDataCenterEntityId on host vmwNsxTDataCenterTransportNodeName for protocol vmwNsxTDataCenterProtocolName is cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTFederationFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.32 | |||
node · current Notifications applicable to the Federation feature have this OID prefix. | ||||
| NvmwNsxTFederationFeature | 1.3.6.1.4.1.6876.120.1.0.32.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Federation feature notifications. | ||||
| !vmwNsxTFederationRtepBGPDown | 1.3.6.1.4.1.6876.120.1.0.32.0.1 | |||
notification · current RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is down. Reason: vmwNsxTDataCenterFailureReason. Action required: 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node. 2. Switch to REMOTE_TUNNEL_VRF context. 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. 4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary to get the BGP neighbor status. 5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned to the interface with name remote-tunnel-endpoint. 6. Check if the ping is working successfully between assigned RTEP IP address (vmwNsxTDataCenterBGPSourceIP) and the remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP. 7. Check /var/log/syslog for any errors related to BGP. 8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint configuration on the edge node. This will update the RTEP IP assigned to the affected edge node. If the reason indicates `Edge is not ready`, check why the Edge node is not in good state. 1. Invoke the NSX CLI command `get edge-cluster status` to check reason why Edge node might be down. 2. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well. 3. Check any Edge health related alarms to get more information.
| ||||
| !vmwNsxTFederationRtepBGPDownClear | 1.3.6.1.4.1.6876.120.1.0.32.0.2 | |||
notification · current RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is established. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationLmToLmSynchronizationError | 1.3.6.1.4.1.6876.120.1.0.32.0.3 | |||
notification · current The synchronization between vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed for more than 15 minutes. Action required: 1. Invoke the NSX CLI command `get site-replicator remote-sites` to get connection state between the remote locations. If a remote location is connected but not synchronized, it is possible that the location is still in the process of master resolution. In this case, wait for around 10 seconds and try invoking the CLI again to check for the state of the remote location. If a location is disconnected, try the next step. 2. Check the connectivity from Local Manager (LM) in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) to the LMs in location vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, check for flakiness in WAN connectivity. If there are no physical network connectivity issues, try the next step. 3. Check the /var/log/cloudnet/nsx-ccp.log file on the Manager nodes in the local cluster in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) that triggered the alarm to see if there are any cross-site communication errors. In addition, also look for errors being logged by the nsx-appl-proxy subcomponent within /var/log/syslog.
| ||||
| !vmwNsxTFederationLmToLmSynchronizationErrorClear | 1.3.6.1.4.1.6876.120.1.0.32.0.4 | |||
notification · current Remote sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationLmToLmSynchronizationWarning | 1.3.6.1.4.1.6876.120.1.0.32.0.5 | |||
notification · current The synchronization between vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed for more than 3 minutes. Action required: 1. Invoke the NSX CLI command `get site-replicator remote-sites` to get connection state between the remote locations. If a remote location is connected but not synchronized, it is possible that the location is still in the process of master resolution. In this case, wait for around 10 seconds and try invoking the CLI again to check for the state of the remote location. If a location is disconnected, try the next step. 2. Check the connectivity from Local Manager (LM) in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) to the LMs in location vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, check for flakiness in WAN connectivity. If there are no physical network connectivity issues, try the next step. 3. Check the /var/log/cloudnet/nsx-ccp.log file on the Manager nodes in the local cluster in location vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) that triggered the alarm to see if there are any cross-site communication errors. In addition, also look for errors being logged by the nsx-appl-proxy subcomponent within /var/log/syslog.
| ||||
| !vmwNsxTFederationLmToLmSynchronizationWarningClear | 1.3.6.1.4.1.6876.120.1.0.32.0.6 | |||
notification · current Remote locations vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationRtepConnectivityLost | 1.3.6.1.4.1.6876.120.1.0.32.0.7 | |||
notification · current Edge node vmwNsxTDataCenterTransportNodeName lost RTEP (Remote Tunnel Endpoint) connectivity with remote location vmwNsxTDataCenterRemoteSiteName. Action required: 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node vmwNsxTDataCenterTransportNodeName. 2. Switch to REMOTE_TUNNEL_VRF context. 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. 4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary to get the BGP neighbor status. 5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned to the interface with name remote-tunnel-endpoint. 6. Check if the ping is working successfully between assigned RTEP IP address and the RTEP IP addresses on the remote location vmwNsxTDataCenterRemoteSiteName. 7. Check /var/log/syslog for any errors related to BGP. 8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint configuration on the edge node. This will update the RTEP IP assigned to the affected edge node vmwNsxTDataCenterTransportNodeName. | ||||
| !vmwNsxTFederationRtepConnectivityLostClear | 1.3.6.1.4.1.6876.120.1.0.32.0.8 | |||
notification · current Edge node vmwNsxTDataCenterTransportNodeName has restored RTEP (Remote Tunnel Endpoint) connectivity with remote location vmwNsxTDataCenterRemoteSiteName. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationGMToGMSplitBrain | 1.3.6.1.4.1.6876.120.1.0.32.0.9 | |||
notification · current Multiple Global Manager nodes are active: vmwNsxTDataCenterActiveGlobalManagers. Only one Global Manager node must be active at any time. Action required: Configure only one Global Manager node as active and all other Global Manager nodes as standby. | ||||
| !vmwNsxTFederationGMToGMSplitBrainClear | 1.3.6.1.4.1.6876.120.1.0.32.0.10 | |||
notification · current Global Manager node vmwNsxTDataCenterActiveGlobalManager is the only active Global Manager node now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationGMToGMLatencyWarning | 1.3.6.1.4.1.6876.120.1.0.32.0.17 | |||
notification · current Latency is higher than expected between Global Managers vmwNsxTDataCenterFromGMPath and vmwNsxTDataCenterToGMPath. Action required: Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping. If they are not pingable, check for flakiness in WAN connectivity.
| ||||
| !vmwNsxTFederationGMToGMLatencyWarningClear | 1.3.6.1.4.1.6876.120.1.0.32.0.18 | |||
notification · current Latency is below expected levels between Global Managers vmwNsxTDataCenterFromGMPath and vmwNsxTDataCenterToGMPath. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationGMToGMSynchronizationError | 1.3.6.1.4.1.6876.120.1.0.32.0.19 | |||
notification · current Active Global Manager vmwNsxTDataCenterFromGMPath to Standby Global Manager vmwNsxTDataCenterToGMPath cannot synchronize for more than 5 minutes. Action required: Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping.
| ||||
| !vmwNsxTFederationGMToGMSynchronizationErrorClear | 1.3.6.1.4.1.6876.120.1.0.32.0.20 | |||
notification · current Synchronization from active Global Manager vmwNsxTDataCenterFromGMPath to standby vmwNsxTDataCenterToGMPath is healthy. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationGMToGMSynchronizationWarning | 1.3.6.1.4.1.6876.120.1.0.32.0.21 | |||
notification · current Active Global Manager vmwNsxTDataCenterFromGMPath to Standby Global Manager vmwNsxTDataCenterToGMPath can not synchronize. Action required: Check the connectivity from Global Manager vmwNsxTDataCenterFromGMPath(vmwNsxTDataCenterSiteId) to the Global Manager vmwNsxTDataCenterToGMPath(vmwNsxTDataCenterRemoteSiteId) via ping.
| ||||
| !vmwNsxTFederationGMToGMSynchronizationWarningClear | 1.3.6.1.4.1.6876.120.1.0.32.0.22 | |||
notification · current Synchronization from active Global Manager vmwNsxTDataCenterFromGMPath to standby vmwNsxTDataCenterToGMPath is healthy. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTFederationGMToLMSynchronizationError | 1.3.6.1.4.1.6876.120.1.0.32.0.23 | |||
notification · current Data synchronization between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed for the vmwNsxTDataCenterFlowIdentifier for an extended period. Reason: vmwNsxTDataCenterSyncIssueReason. Action required: 1. Check the network connectivity between remote site and local site via ping. 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. 3. Ensure the async-replicator service is running on both local and remote sites. Invoke the GET /api/v1/node/services/async_replicator/status NSX API or the `get service async_replicator` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/async_replicator?action=restart NSX API or the `restart service async_replicator` NSX CLI to restart the service. 4. Check /var/log/async-replicator/ar.log to see if there are errors reported. 5. Collect a support bundle and contact the NSX support team.
| ||||
| !vmwNsxTFederationGMToLMSynchronizationErrorClear | 1.3.6.1.4.1.6876.120.1.0.32.0.24 | |||
notification · current Sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized for vmwNsxTDataCenterFlowIdentifier. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationGMToLMSynchronizationWarning | 1.3.6.1.4.1.6876.120.1.0.32.0.25 | |||
notification · current Data synchronization between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) failed for the vmwNsxTDataCenterFlowIdentifier. Reason: vmwNsxTDataCenterSyncIssueReason Action required: 1. Check the network connectivity between remote site and local site via ping. 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. 3. Ensure the async-replicator service is running on both local and remote sites. Invoke the GET /api/v1/node/services/async_replicator/status NSX API or the `get service async_replicator` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/async_replicator?action=restart NSX API or the `restart service async_replicator` NSX CLI to restart the service. 4. Check /var/log/async-replicator/ar.log to see if there are errors reported.
| ||||
| !vmwNsxTFederationGMToLMSynchronizationWarningClear | 1.3.6.1.4.1.6876.120.1.0.32.0.26 | |||
notification · current Sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) are now synchronized for vmwNsxTDataCenterFlowIdentifier. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationGMToLMLatencyWarning | 1.3.6.1.4.1.6876.120.1.0.32.0.27 | |||
notification · current Latency between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached vmwNsxTDataCenterLatencyValue which is above the threshold value of vmwNsxTDataCenterLatencyThreshold. Action required: 1. Check the network connectivity between remote site and local site via ping. 2. Ensure port TCP/1236 traffic is allowed between the local and remote sites. 3. Check /var/log/async-replicator/ar.log to see if there are errors reported.
| ||||
| !vmwNsxTFederationGMToLMLatencyWarningClear | 1.3.6.1.4.1.6876.120.1.0.32.0.28 | |||
notification · current Latency between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached vmwNsxTDataCenterLatencyValue which below the threshold value of vmwNsxTDataCenterLatencyThreshold. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationQueueOccupancyThresholdExceeded | 1.3.6.1.4.1.6876.120.1.0.32.0.29 | |||
notification · current Queue (vmwNsxTDataCenterQueueName) used for syncing data between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached size vmwNsxTDataCenterQueueSize which is at or above the maximum threshold of vmwNsxTDataCenterQueueSizeThreshold%. Action required: Queue size can exceed threshold due to communication issue with remote site or an overloaded system. Check system performance and /var/log/async-replicator/ar.log to see if there are any errors reported.
| ||||
| !vmwNsxTFederationQueueOccupancyThresholdExceededClear | 1.3.6.1.4.1.6876.120.1.0.32.0.30 | |||
notification · current Queue (vmwNsxTDataCenterQueueName) used for syncing data between sites vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) and vmwNsxTDataCenterRemoteSiteName(vmwNsxTDataCenterRemoteSiteId) has reached size vmwNsxTDataCenterQueueSize which is below the maximum threshold of vmwNsxTDataCenterQueueSizeThreshold%. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTFederationLMRestoreWhileConfigImportInProgress | 1.3.6.1.4.1.6876.120.1.0.32.0.31 | |||
notification · current Config import from site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is in progress. However site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is restored from backup by the administrator leaving it in an inconsistent state. Action required: 1. Log in to NSX Global Manager appliance CLI. 2. Switch to root. 3. Invoke the NSX API DELETE http://localhost:64440/gm/api/v1/infra/sites/<site-name>/onboarding/status in local mode, this will delete site on-boarding status for Global Manager. 4. Re-initiate config on-boarding again. | ||||
| !vmwNsxTFederationLMRestoreWhileConfigImportInProgressClear | 1.3.6.1.4.1.6876.120.1.0.32.0.32 | |||
notification · current Config inconsistency at site vmwNsxTDataCenterSiteName(vmwNsxTDataCenterSiteId) is resolved. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTDistributedIDSIPSFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.33 | |||
node · current Notifications applicable to the DistributedIDSIPS feature have this OID prefix. | ||||
| NvmwNsxTDistributedIDSIPSFeature | 1.3.6.1.4.1.6876.120.1.0.33.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for DistributedIDSIPS feature notifications. | ||||
| !vmwNsxTDistributedIDSIPSMaxEventsReached | 1.3.6.1.4.1.6876.120.1.0.33.0.3 | |||
notification · current The number of intrusion events in the system is vmwNsxTDataCenterIDSEventsCount which is higher than the maximum allowed value vmwNsxTDataCenterMaxIDSEventsAllowed. Action required: There is no manual intervention required. A purge job will kick in automatically every 3 minutes and delete 10% of the older records to bring the total intrusion events count in the system to below the threshold value of 1.5 million events. | ||||
| !vmwNsxTDistributedIDSIPSMaxEventsReachedClear | 1.3.6.1.4.1.6876.120.1.0.33.0.4 | |||
notification · current The number of intrusion events in the system is vmwNsxTDataCenterIDSEventsCount which is below the maximum allowed value vmwNsxTDataCenterMaxIDSEventsAllowed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.7 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the high threshold value of 75%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.8 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the high threshold value of 75%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.9 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the very high threshold value of 95%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.10 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the very high threshold value of 95%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineDown | 1.3.6.1.4.1.6876.120.1.0.33.0.13 | |||
notification · current NSX IDPS is enabled via NSX policy and IDPS rules are configured, but NSX-IDPS engine is down. Action required: 1. Check /var/log/nsx-syslog.log to see if there are errors reported. 2. Invoke the NSX CLI command `get ids engine status` to check if NSX Distributed IDPS is in disabled state. If so, invoke `/etc/init.d/nsx-idps start` to start the service. 3. Invoke `/etc/init.d/nsx-vdpi status` to check if nsx-vdpi is running. If not, invoke `/etc/init.d/nsx-vdpi start` to start the service. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineDownClear | 1.3.6.1.4.1.6876.120.1.0.33.0.14 | |||
notification · current NSX IDPS is in one of the cases below. 1. NSX IDPS is disabled via NSX policy. 2. NSX IDPS engine is enabled, NSX-IDPS engine and vdpi are up, and NSX IDPS has been enabled and IDPS rules are configured via NSX Policy. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.15 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the high threshold value of 75%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.16 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the high threshold value of 75%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.17 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the medium high threshold value of 85%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.18 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the medium high threshold value of 85%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.19 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the very high threshold value of 95%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.20 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the very high threshold value of 95%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.21 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the medium high threshold value of 85%. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.22 | |||
notification · current NSX-IDPS engine CPU usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is below the medium high threshold value of 85%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighOnDPU | 1.3.6.1.4.1.6876.120.1.0.33.0.23 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the high threshold value of 75% on DPU vmwNsxTDataCenterDPUId. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.33.0.24 | |||
notification · current NSX-IDPS engine memory usage has reached on DPU vmwNsxTDataCenterDPUId, vmwNsxTDataCenterSystemResourceUsage%, which is below the high threshold value of 75%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineDownOnDPU | 1.3.6.1.4.1.6876.120.1.0.33.0.31 | |||
notification · current NSX IDPS is enabled via NSX policy and IDPS rules are configured, but NSX-IDPS engine is down on DPU vmwNsxTDataCenterDPUId. Action required: 1. Check /var/log/nsx-idps/nsx-idps.log and /var/log/nsx-syslog.log to see if there are errors reported. 2. Invoke the NSX CLI command `get ids engine status` to check if NSX Distributed IDPS is in disabled state. If so, invoke `/etc/init.d/nsx-idps start` to start the service. 3. Invoke `/etc/init.d/nsx-vdpi status` to check if nsx-vdpi is running. If not, invoke `/etc/init.d/nsx-vdpi start` to start the service. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineDownOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.33.0.32 | |||
notification · current NSX IDPS is in one of the cases below on DPU vmwNsxTDataCenterDPUId. 1. NSX IDPS is disabled via NSX policy. 2. NSX IDPS engine is enabled, NSX-IDPS engine and vdpi are up, and NSX IDPS has been enabled and IDPS rules are configured via NSX Policy. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageMedHighOnDPU | 1.3.6.1.4.1.6876.120.1.0.33.0.33 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the medium high threshold value of 85% on DPU vmwNsxTDataCenterDPUId. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageMedHighOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.33.0.34 | |||
notification · current NSX-IDPS engine memory usage has reached on DPU vmwNsxTDataCenterDPUId, vmwNsxTDataCenterSystemResourceUsage%, which is below the medium high threshold value of 85%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageVeryHighDPU | 1.3.6.1.4.1.6876.120.1.0.33.0.35 | |||
notification · current NSX-IDPS engine memory usage has reached vmwNsxTDataCenterSystemResourceUsage%, which is at or above the very high threshold value of 95% on DPU vmwNsxTDataCenterDPUId. Action required: Consider re-balancing the VM workloads on this host to other hosts. | ||||
| !vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageVeryHighDPUClear | 1.3.6.1.4.1.6876.120.1.0.33.0.36 | |||
notification · current NSX-IDPS engine memory usage has reached on DPU vmwNsxTDataCenterDPUId, vmwNsxTDataCenterSystemResourceUsage%, which is below the very high threshold value of 95%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSBypassedCPUOversubscribed | 1.3.6.1.4.1.6876.120.1.0.33.0.53 | |||
notification · current The IDPS engine has insufficient CPU resources and is unable to keep pace with the incoming traffic resulting in the excess traffic being bypassed. For more details, login to the ESX host and issue the following command: `vsipioctl getdpiinfo -s` and look at oversubscription stats. Action required: Review reason for oversubscription. Move certain applications to different host. | ||||
| !vmwNsxTDistributedIDSIPSIDPSBypassedCPUOversubscribedClear | 1.3.6.1.4.1.6876.120.1.0.33.0.54 | |||
notification · current The distributed IDPS engine has adequate CPU resources and is not bypassing any traffic. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSBypassedNetworkOversubscribed | 1.3.6.1.4.1.6876.120.1.0.33.0.55 | |||
notification · current The IDPS engine is unable to keep pace with the rate of incoming traffic resulting in the excess traffic being bypassed. For more details, login to the ESX host and issue the following command: `vsipioctl getdpiinfo -s` and look at oversubscription stats. Action required: Review reason for oversubscription. Review the IDPS rules to reduce the amount of traffic being subject to IDPS service. | ||||
| !vmwNsxTDistributedIDSIPSIDPSBypassedNetworkOversubscribedClear | 1.3.6.1.4.1.6876.120.1.0.33.0.56 | |||
notification · current The distributed IDPS engine is not bypassing any traffic. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSEngineCPUOversubscriptionHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.57 | |||
notification · current CPU utilization for the distributed IDPS engine is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review reason for oversubscription. Move certain applications to different host. | ||||
| !vmwNsxTDistributedIDSIPSIDPSEngineCPUOversubscriptionHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.58 | |||
notification · current CPU utilization for the distributed IDPS engine is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSCPUOversubscriptionVeryHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.59 | |||
notification · current CPU utilization for the distributed IDPS engine is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review reason for oversubscription. Move certain applications to different host. | ||||
| !vmwNsxTDistributedIDSIPSIDPSCPUOversubscriptionVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.60 | |||
notification · current CPU utilization for the distributed IDPS engine is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSDroppedCPUOversubscribed | 1.3.6.1.4.1.6876.120.1.0.33.0.61 | |||
notification · current The IDPS engine has insufficient CPU resources and is unable to keep pace with the incoming traffic resulting in the excess traffic being dropped. For more details, login to the ESX host and issue the following command: `vsipioctl getdpiinfo -s` and look at oversubscription stats. Action required: Review reason for oversubscription. Move certain applications to different host. | ||||
| !vmwNsxTDistributedIDSIPSIDPSDroppedCPUOversubscribedClear | 1.3.6.1.4.1.6876.120.1.0.33.0.62 | |||
notification · current The distributed IDPS engine has adequate CPU resources and is not dropping any traffic. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSDroppedNetworkOversubscribed | 1.3.6.1.4.1.6876.120.1.0.33.0.63 | |||
notification · current The IDPS engine is unable to keep pace with the rate of incoming traffic resulting in the excess traffic being dropped. For more details, login to the ESX host and issue the following command: `vsipioctl getdpiinfo -s` and look at oversubscription stats. Action required: Review reason for oversubscription. Review the IDPS rules to reduce the amount of traffic being subject to IDPS service. | ||||
| !vmwNsxTDistributedIDSIPSIDPSDroppedNetworkOversubscribedClear | 1.3.6.1.4.1.6876.120.1.0.33.0.64 | |||
notification · current The distributed IDPS engine is not dropping any traffic. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.65 | |||
notification · current Network utilization for the distributed IDPS engine is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review reason for oversubscription. Review the IDPS rules to reduce the amount of traffic being subject to IDPS service. | ||||
| !vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.66 | |||
notification · current Network utilization for the distributed IDPS engine is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionVeryHigh | 1.3.6.1.4.1.6876.120.1.0.33.0.67 | |||
notification · current Network utilization for the distributed IDPS engine is at or above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Review reason for oversubscription. Review the IDPS rules to reduce the amount of traffic being subject to IDPS service. | ||||
| !vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.33.0.68 | |||
notification · current Network utilization for the distributed IDPS engine is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTCommunicationFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.35 | |||
node · current Notifications applicable to the Communication feature have this OID prefix. | ||||
| NvmwNsxTCommunicationFeature | 1.3.6.1.4.1.6876.120.1.0.35.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Communication feature notifications. | ||||
| !vmwNsxTCommunicationManagementChannelToTransportNodeDown | 1.3.6.1.4.1.6876.120.1.0.35.0.1 | |||
notification · current Management channel to Transport Node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is down for 5 minutes. Action required: Ensure there is network connectivity between the Manager nodes and Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) and no firewalls are blocking traffic between the nodes. On Windows Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 status` in the Windows PowerShell. If it is not running, restart it by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 restart`. On all other Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `/etc/init.d/nsx-proxy status`. If it is not running, restart it by invoking the command `/etc/init.d/nsx-proxy restart`. | ||||
| !vmwNsxTCommunicationManagementChannelToTransportNodeDownClear | 1.3.6.1.4.1.6876.120.1.0.35.0.2 | |||
notification · current Management channel to Transport Node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagerControlChannelDown | 1.3.6.1.4.1.6876.120.1.0.35.0.3 | |||
notification · current The communication between the management function and the control function has failed on Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress). Action required: 1. On Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress), invoke the following NSX CLI command: `get service applianceproxy` to check the status of the service periodically for 60 minutes. 2. If the service is not running for more than 60 minutes, invoke the following NSX CLI command: `restart service applianceproxy` and recheck the status. If the service is still down, contact VMware support. | ||||
| !vmwNsxTCommunicationManagerControlChannelDownClear | 1.3.6.1.4.1.6876.120.1.0.35.0.4 | |||
notification · current The communication between the management function and the control function has been restored on Manager node vmwNsxTDataCenterManagerNodeName (vmwNsxTDataCenterApplianceAddress). Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagementChannelToTransportNodeDownLg | 1.3.6.1.4.1.6876.120.1.0.35.0.5 | |||
notification · current Management channel to Transport Node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is down for 15 minutes. Action required: Ensure there is network connectivity between the Manager nodes and Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) and no firewalls are blocking traffic between the nodes. On Windows Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 status` in the Windows PowerShell. If it is not running, restart it by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 restart`. On all other Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `/etc/init.d/nsx-proxy status`. If it is not running, restart it by invoking the command `/etc/init.d/nsx-proxy restart`. | ||||
| !vmwNsxTCommunicationManagementChannelToTransportNodeDownLgClear | 1.3.6.1.4.1.6876.120.1.0.35.0.6 | |||
notification · current Management channel to Transport Node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationControlChannelToManagerNodeDown | 1.3.6.1.4.1.6876.120.1.0.35.0.7 | |||
notification · current The Transport node vmwNsxTDataCenterEntityId control plane connection to Manager node vmwNsxTDataCenterApplianceAddress is down for at least vmwNsxTDataCenterTimeoutInMinutes minutes from the Transport node's point of view. Action required: 1. Check the connectivity from Transport node vmwNsxTDataCenterEntityId to Manager node vmwNsxTDataCenterApplianceAddress interface via ping. If they are not pingable, check for flakiness in network connectivity. 2. Check to see if the TCP connections are established using the netstat output to see if the Controller service on the Manager node vmwNsxTDataCenterApplianceAddress is listening for connections on port 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in the underlay are blocking the required IP ports between Manager nodes and Transport nodes. This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. You can check whether the Transport node is in maintenance mode via the following API: GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid> When maintenance mode is set, the Transport node will not be connected to the Controller service. This is usually the case when host upgrade is in progress. Wait for a few minutes and check connectivity again. Note: This alarm is not critical and should be resolved. GSS need not be contacted for the notification of this alarm unless the alarm remains unresolved over an extended period of time. | ||||
| !vmwNsxTCommunicationControlChannelToManagerNodeDownClear | 1.3.6.1.4.1.6876.120.1.0.35.0.8 | |||
notification · current The Transport node vmwNsxTDataCenterEntityId restores the control plane connection to Manager node vmwNsxTDataCenterApplianceAddress. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationControlChannelToManagerNodeDownTooLong | 1.3.6.1.4.1.6876.120.1.0.35.0.9 | |||
notification · current The Transport node vmwNsxTDataCenterEntityId control plane connection to Manager node vmwNsxTDataCenterApplianceAddress is down for at least vmwNsxTDataCenterTimeoutInMinutes minutes from the Transport node's point of view. Action required: 1. Check the connectivity from Transport node vmwNsxTDataCenterEntityId to Manager node vmwNsxTDataCenterApplianceAddress interface via ping. If they are not pingable, check for flakiness in network connectivity. 2. Check to see if the TCP connections are established using the netstat output to see if the Controller service on the Manager node vmwNsxTDataCenterApplianceAddress is listening for connections on port 1235. If not, check firewall (or) iptables rules to see if port 1235 is blocking Transport node vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in the underlay are blocking the required IP ports between Manager nodes and Transport nodes. This is documented in our ports and protocols tool which is here: https://ports.vmware.com/. 3. It is possible that the Transport node vmwNsxTDataCenterEntityId may still be in maintenance mode. You can check whether the Transport node is in maintenance mode via the following API: GET https://<nsx-mgr>/api/v1/transport-nodes/<tn-uuid>. When maintenance mode is set, the Transport node will not be connected to the Controller service. This is usually the case when host upgrade is in progress. Wait for a few minutes and check connectivity again. | ||||
| !vmwNsxTCommunicationControlChannelToManagerNodeDownTooLongClear | 1.3.6.1.4.1.6876.120.1.0.35.0.10 | |||
notification · current The Transport node vmwNsxTDataCenterEntityId restores the control plane connection to Manager node vmwNsxTDataCenterApplianceAddress. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationControlChannelToTransportNodeDown | 1.3.6.1.4.1.6876.120.1.0.35.0.11 | |||
notification · current Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) to Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) down for at least three minutes from Controller service's point of view. Action required: 1. Check the connectivity from the Controller service vmwNsxTDataCenterCentralControlPlaneId and Transport node vmwNsxTDataCenterEntityId interface via ping and traceroute. This can be done on the NSX Manager node admin CLI. The ping test should not see drops and have consistent latency values. VMware recommends latency values of 150ms or less. 2. Navigate to System | Fabric | Nodes | Transport node vmwNsxTDataCenterEntityId on the NSX UI to check if the TCP connections between the Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) and Transport node vmwNsxTDataCenterEntityId is established. If not, check firewall rules on the network and the hosts to see if port 1235 is blocking Transport node vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in the underlay are blocking the required IP ports between Manager nodes and Transport nodes. This is documented in our ports and protocols tool which is here: https://ports.vmware.com/.
| ||||
| !vmwNsxTCommunicationControlChannelToTransportNodeDownClear | 1.3.6.1.4.1.6876.120.1.0.35.0.12 | |||
notification · current Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) restores connection to Transport node vmwNsxTDataCenterEntityId. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagementChannelToManagerNodeDown | 1.3.6.1.4.1.6876.120.1.0.35.0.13 | |||
notification · current Management channel to Manager Node vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) is down for 5 minutes. Action required: Ensure there is network connectivity between the Transport node vmwNsxTDataCenterTransportNodeId and master Manager node. Also ensure no firewalls are blocking traffic between the nodes. Ensure the messaging manager service is running on Manager nodes by invoking the command `/etc/init.d/messaging-manager status`. If the messaging manager is not running, restart it by invoking the command `/etc/init.d/messaging-manager restart`.
| ||||
| !vmwNsxTCommunicationManagementChannelToManagerNodeDownClear | 1.3.6.1.4.1.6876.120.1.0.35.0.14 | |||
notification · current Management channel to Manager Node vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagerClusterLatencyHigh | 1.3.6.1.4.1.6876.120.1.0.35.0.17 | |||
notification · current The average network latency between Manager nodes vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) and vmwNsxTDataCenterRemoteManagerNodeId (vmwNsxTDataCenterRemoteApplianceAddress) is more than 10ms for the last 5 minutes. Action required: Ensure there are no firewall rules blocking ping traffic between the Manager nodes. If there are other high bandwidth servers and applications sharing the local network, consider moving these to a different network.
| ||||
| !vmwNsxTCommunicationManagerClusterLatencyHighClear | 1.3.6.1.4.1.6876.120.1.0.35.0.18 | |||
notification · current The average network latency between Manager nodes vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) and vmwNsxTDataCenterRemoteManagerNodeId (vmwNsxTDataCenterRemoteApplianceAddress) is within 10ms. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTCommunicationControlChannelToTransportNodeDownLong | 1.3.6.1.4.1.6876.120.1.0.35.0.19 | |||
notification · current Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) to Transport node vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) down for at least 15 minutes from Controller service's point of view. Action required: 1. Check the connectivity from the Controller service vmwNsxTDataCenterCentralControlPlaneId and Transport node vmwNsxTDataCenterEntityId interface via ping and traceroute. This can be done on the NSX Manager node admin CLI. The ping test should not see drops and have consistent latency values. VMware recommends latency values of 150ms or less. 2. Navigate to System | Fabric | Nodes | Transport node vmwNsxTDataCenterEntityId on the NSX UI to check if the TCP connections between the Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) and Transport node vmwNsxTDataCenterEntityId is established. If not, check firewall rules on the network and the hosts to see if port 1235 is blocking Transport node vmwNsxTDataCenterEntityId connection requests. Ensure that there are no host firewalls or network firewalls in the underlay are blocking the required IP ports between Manager nodes and Transport nodes. This is documented in our ports and protocols tool which is here: https://ports.vmware.com/.
| ||||
| !vmwNsxTCommunicationControlChannelToTransportNodeDownLongClear | 1.3.6.1.4.1.6876.120.1.0.35.0.20 | |||
notification · current Controller service on Manager node vmwNsxTDataCenterApplianceAddress (vmwNsxTDataCenterCentralControlPlaneId) restores connection to Transport node vmwNsxTDataCenterEntityId. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagerFQDNLookupFailure | 1.3.6.1.4.1.6876.120.1.0.35.0.21 | |||
notification · current DNS lookup failed for Manager node vmwNsxTDataCenterEntityId with FQDN vmwNsxTDataCenterApplianceFQDN and the publish_fqdns flag was set. Action required: 1. Assign correct FQDNs to all Manager nodes and verify the DNS configuration is correct for successful lookup of all Manager nodes' FQDNs. 2. Alternatively, disable the use of FQDNs by invoking the NSX API PUT /api/v1/configs/management with publish_fqdns set to false in the request body. After that calls from Transport nodes and from Federation to Manager nodes in this cluster will use only IP addresses. | ||||
| !vmwNsxTCommunicationManagerFQDNLookupFailureClear | 1.3.6.1.4.1.6876.120.1.0.35.0.22 | |||
notification · current FQDN lookup succeeded for Manager node vmwNsxTDataCenterEntityId with FQDN vmwNsxTDataCenterApplianceFQDN or the publish_fqdns flag was cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagerFQDNReverseLookupFailure | 1.3.6.1.4.1.6876.120.1.0.35.0.23 | |||
notification · current Reverse DNS lookup failed for Manager node vmwNsxTDataCenterEntityId with IP address vmwNsxTDataCenterApplianceAddress and the publish_fqdns flag was set. Action required: 1. Assign correct FQDNs to all Manager nodes and verify the DNS configuration is correct for successful reverse lookup of the Manager node's IP address. 2. Alternatively, disable the use of FQDNs by invoking the NSX API PUT /api/v1/configs/management with publish_fqdns set to false in the request body. After that calls from Transport nodes and from Federation to Manager nodes in this cluster will use only IP addresses. | ||||
| !vmwNsxTCommunicationManagerFQDNReverseLookupFailureClear | 1.3.6.1.4.1.6876.120.1.0.35.0.24 | |||
notification · current Reverse DNS lookup succeeded for Manager node vmwNsxTDataCenterEntityId with IP address vmwNsxTDataCenterApplianceAddress or the publish_fqdns flag was cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationManagementChannelToManagerNodeDownLong | 1.3.6.1.4.1.6876.120.1.0.35.0.25 | |||
notification · current Management channel to Manager Node vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) is down for 15 minutes. Action required: Ensure there is network connectivity between the Transport node vmwNsxTDataCenterTransportNodeId and master Manager nodes. Also ensure no firewalls are blocking traffic between the nodes. Ensure the messaging manager service is running on Manager nodes by invoking the command `/etc/init.d/messaging-manager status`. If the messaging manager is not running, restart it by invoking the command `/etc/init.d/messaging-manager restart`.
| ||||
| !vmwNsxTCommunicationManagementChannelToManagerNodeDownLongClear | 1.3.6.1.4.1.6876.120.1.0.35.0.26 | |||
notification · current Management channel to Manager Node vmwNsxTDataCenterManagerNodeId (vmwNsxTDataCenterApplianceAddress) is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationNetworkLatencyHigh | 1.3.6.1.4.1.6876.120.1.0.35.0.29 | |||
notification · current The average network latency between manager nodes and host vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is more than 150 ms for 5 minutes. Action required: 1. Wait for 5 minutes to see if the alarm automatically gets resolved. 2. Ping the NSX Transport node from Manager node. The ping test should not see drops and have consistent latency values. VMware recommends latency values of 150ms or less. 3. Inspect for any other physical network layer issues. If the problem persists, contact VMware support. | ||||
| !vmwNsxTCommunicationNetworkLatencyHighClear | 1.3.6.1.4.1.6876.120.1.0.35.0.30 | |||
notification · current The average network latency between manager nodes and host vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterTransportNodeAddress) is normal. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTCommunicationLimitedReachabilityOnDPU | 1.3.6.1.4.1.6876.120.1.0.35.0.31 | |||
notification · current The vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP can not be reached via vmknic(s)(stack vmwNsxTDataCenterStackAlias) on DVS vmwNsxTDataCenterDvsAlias on DPU vmwNsxTDataCenterDPUId, but is reachable via vmknic(s)(stack vmwNsxTDataCenterStackAlias) on other DVS(es). Action required: If the warning is on, it does not mean the collector is unreachable. The exported flows generated by the vertical based on DVS vmwNsxTDataCenterDvsAlias can still reach the collector vmwNsxTDataCenterCollectorIP via vmknic(s) on DVS(es) besides of DVS vmwNsxTDataCenterDvsAlias. If this is unacceptable, user can try to create vmknic(s) with stack vmwNsxTDataCenterStackAlias on DVS vmwNsxTDataCenterDvsAlias and configure it with approriate IPv4(6) address, then check if the vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP can be reached via the newly-created vmknic(s) on DPU vmwNsxTDataCenterDPUId by invoking `vmkping vmwNsxTDataCenterCollectorIP -S vmwNsxTDataCenterStackAlias -I vmkX` with SSH to DPU via ESXi enabled.
| ||||
| !vmwNsxTCommunicationLimitedReachabilityOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.35.0.32 | |||
notification · current The vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP can be reached via vmknic(s) (stack vmwNsxTDataCenterStackAlias) on DVS vmwNsxTDataCenterDvsAlias on DPU vmwNsxTDataCenterDPUId, or the vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP is unreachable completely. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTCommunicationUnreachableCollectorOnDPU | 1.3.6.1.4.1.6876.120.1.0.35.0.33 | |||
notification · current The vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP can not be reached via existing vmknic(s)(stack vmwNsxTDataCenterStackAlias) on any DVS on DPU vmwNsxTDataCenterDPUId. Action required: To make the collector reachable for given vertical on the DVS, user has to make sure there is(are) vmknic(s) with expected stack vmwNsxTDataCenterStackAlias created and configured with approriate IPv4(6) addresses, and the network connection to vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP is also fine. So user has to do the checking on DPU vmwNsxTDataCenterDPUId, and perform required configuration to make sure the condition is met. Finally if `vmkping vmwNsxTDataCenterCollectorIP -S vmwNsxTDataCenterStackAlias` with SSH to DPU via ESXi enabled succeeds, this indicates the problem is gone.
| ||||
| !vmwNsxTCommunicationUnreachableCollectorOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.35.0.34 | |||
notification · current The vmwNsxTDataCenterVerticalName collector vmwNsxTDataCenterCollectorIP can be reached with existing vmknic(s)(stack vmwNsxTDataCenterStackAlias) now on DPU vmwNsxTDataCenterDPUId. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTIdentityFirewallFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.36 | |||
node · current Notifications applicable to the IdentityFirewall feature have this OID prefix. | ||||
| NvmwNsxTIdentityFirewallFeature | 1.3.6.1.4.1.6876.120.1.0.36.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for IdentityFirewall feature notifications. | ||||
| !vmwNsxTIdentityFirewallConnectivityToLDAPServerLost | 1.3.6.1.4.1.6876.120.1.0.36.0.1 | |||
notification · current The connectivity to LDAP server vmwNsxTDataCenterLDAPServer is lost. Action required: Check 1. The LDAP server is reachable from NSX nodes. 2. The LDAP server details are configured correctly in NSX. 3. The LDAP server is running correctly. 4. There are no firewalls blocking access between the LDAP server and NSX nodes. Afer the issue is fixed, use TEST CONNECTION in NSX UI under Identity Firewall AD to test the connection. | ||||
| !vmwNsxTIdentityFirewallConnectivityToLDAPServerLostClear | 1.3.6.1.4.1.6876.120.1.0.36.0.2 | |||
notification · current The connectivity to LDAP server vmwNsxTDataCenterLDAPServer is restored. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIdentityFirewallErrorInDeltaSync | 1.3.6.1.4.1.6876.120.1.0.36.0.3 | |||
notification · current Errors occurred while performing delta sync with vmwNsxTDataCenterDirectoryDomain. Action required: 1. Check if there are any connectivity to LDAP server lost alarms. 2. Find the error details in /var/log/syslog. Around the alarm trigger time, search for text: Error happened when synchronize LDAP objects. 3. Check with AD administrator if there are any recent AD changes which may cause the errors. 4. If the errors persist, collect the technical support bundle and contact VMware technical support. | ||||
| !vmwNsxTIdentityFirewallErrorInDeltaSyncClear | 1.3.6.1.4.1.6876.120.1.0.36.0.4 | |||
notification · current No errors occurred while performing delta sync with vmwNsxTDataCenterDirectoryDomain. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTIPAMFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.38 | |||
node · current Notifications applicable to the IPAM feature have this OID prefix. | ||||
| NvmwNsxTIPAMFeature | 1.3.6.1.4.1.6876.120.1.0.38.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for IPAM feature notifications. | ||||
| !vmwNsxTIPAMIPBlockUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.38.0.1 | |||
notification · current IP block usage of vmwNsxTDataCenterIntentPath is very high. IP block nearing its total capacity, creation of subnet using IP block might fail. Action required: Review IP block usage. Use new IP block for resource creation or delete unused IP subnet from the IP block. To check subnet being used for IP Block. From NSX UI, navigate to Networking | IP Address pools | IP Address pools tab. Select IP pools where IP block being used, check Subnets and Allocated IPs column on UI. If no allocation has been used for the IP pool and it is not going to be used in future then delete subnet or IP pool. Use following API to check if IP block being used by IP pool and also check if any IP allocation done: To get configured subnets of an IP pool, invoke the NSX API GET /policy/api/v1/infra/ip-pools/<ip-pool>/ip-subnets To get IP allocations, invoke the NSX API GET /policy/api/v1/infra/ip-pools/<ip-pool>/ip-allocations Note: Deletion of IP pool/subnet should only be done if it does not have any allocated IPs and it is not going to be used in future. | ||||
| !vmwNsxTIPAMIPBlockUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.38.0.2 | |||
notification · current IP block usage of vmwNsxTDataCenterIntentPath is below threshold level. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTIPAMIPPoolUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.38.0.3 | |||
notification · current IP pool usage of vmwNsxTDataCenterIntentPath is very high. Creation of entity/service depends on IP being allocated from IP pool might fail. Action required: Review IP pool usage. Release unused ip allocations from IP pool or create new IP pool and use it. From NSX UI navigate to Networking | IP Address pools | IP Address pools tab. Select IP pools and check Allocated IPs column, this will show IPs allocated from the IP pool. If user see any IPs are not being used then those IPs can be released. To release unused IP allocations, invoke the NSX API DELETE /policy/api/v1/infra/ip-pools/<ip-pool>/ip-allocations/<ip-allocation> | ||||
| !vmwNsxTIPAMIPPoolUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.38.0.4 | |||
notification · current IP pool usage of vmwNsxTDataCenterIntentPath is normal now. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTGatewayFirewallFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.39 | |||
node · current Notifications applicable to the GatewayFirewall feature have this OID prefix. | ||||
| NvmwNsxTGatewayFirewallFeature | 1.3.6.1.4.1.6876.120.1.0.39.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for GatewayFirewall feature notifications. | ||||
| !vmwNsxTGatewayFirewallICMPFlowCountExceeded | 1.3.6.1.4.1.6876.120.1.0.39.0.21 | |||
notification · current Gateway firewall flow table usage for ICMP traffic on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallICMPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usage for ICMP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallICMPFlowCountExceededClear | 1.3.6.1.4.1.6876.120.1.0.39.0.22 | |||
notification · current Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallICMPFlowCountHigh | 1.3.6.1.4.1.6876.120.1.0.39.0.23 | |||
notification · current Gateway firewall flow table usage for ICMP on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallICMPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usege for ICMP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallICMPFlowCountHighClear | 1.3.6.1.4.1.6876.120.1.0.39.0.24 | |||
notification · current Gateway firewall flow table usage for ICMP on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallIPFlowCountExceeded | 1.3.6.1.4.1.6876.120.1.0.39.0.25 | |||
notification · current Gateway firewall flow table usage for IP traffic on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallIPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usage for IP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallIPFlowCountExceededClear | 1.3.6.1.4.1.6876.120.1.0.39.0.26 | |||
notification · current Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallIPFlowCountHigh | 1.3.6.1.4.1.6876.120.1.0.39.0.27 | |||
notification · current Gateway firewall flow table usage for IP on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallIPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usege for IP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallIPFlowCountHighClear | 1.3.6.1.4.1.6876.120.1.0.39.0.28 | |||
notification · current Gateway firewall flow table usage for non IP flows on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceeded | 1.3.6.1.4.1.6876.120.1.0.39.0.29 | |||
notification · current Gateway firewall flow table usage for TCP half-open traffic on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallHalfopenFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usage for TCP half-open flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceededClear | 1.3.6.1.4.1.6876.120.1.0.39.0.30 | |||
notification · current Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHigh | 1.3.6.1.4.1.6876.120.1.0.39.0.31 | |||
notification · current Gateway firewall flow table usage for TCP on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallHalfopenFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usege for TCP half-open flow. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHighClear | 1.3.6.1.4.1.6876.120.1.0.39.0.32 | |||
notification · current Gateway firewall flow table usage for TCP half-open on logical router vmwNsxTDataCenterEntityId has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallUDPFlowCountExceeded | 1.3.6.1.4.1.6876.120.1.0.39.0.33 | |||
notification · current Gateway firewall flow table usage for UDP traffic on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallUDPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usage for UDP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallUDPFlowCountExceededClear | 1.3.6.1.4.1.6876.120.1.0.39.0.34 | |||
notification · current Gateway firewall flow table usage on logical router vmwNsxTDataCenterEntityId has reached below the high threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTGatewayFirewallUDPFlowCountHigh | 1.3.6.1.4.1.6876.120.1.0.39.0.35 | |||
notification · current Gateway firewall flow table usage for UDP on logical router vmwNsxTDataCenterEntityId has reached vmwNsxTDataCenterFirewallUDPFlowUsage% which is at or above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will be dropped by Gateway firewall when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> interface stats | json` by using right interface uuid and check flow table usege for UDP flows. Check traffic flows going through the gateway is not a DOS attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider increasing the alarm threshold or route new traffic to another Edge node. | ||||
| !vmwNsxTGatewayFirewallUDPFlowCountHighClear | 1.3.6.1.4.1.6876.120.1.0.39.0.36 | |||
notification · current Gateway firewall flow table usage for UDP on logical router vmwNsxTDataCenterEntityId has reached below the high threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTClusteringFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.40 | |||
node · current Notifications applicable to the Clustering feature have this OID prefix. | ||||
| NvmwNsxTClusteringFeature | 1.3.6.1.4.1.6876.120.1.0.40.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Clustering feature notifications. | ||||
| !vmwNsxTClusteringClusterDegraded | 1.3.6.1.4.1.6876.120.1.0.40.0.1 | |||
notification · current Group member vmwNsxTDataCenterManagerNodeId of service vmwNsxTDataCenterGroupType is down. Action required: 1. Invoke the NSX CLI command 'get cluster status' to view the status of group members of the cluster. 2. Ensure the service for vmwNsxTDataCenterGroupType is running on node. Invoke the GET /api/v1/node/services/<service_name>/status NSX API or the `get service <service_name>` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/<service_name>?action=restart NSX API or the `restart service <service_name>` NSX CLI to restart the service. 3. Check /var/log/ of service vmwNsxTDataCenterGroupType to see if there are errors reported. | ||||
| !vmwNsxTClusteringClusterDegradedClear | 1.3.6.1.4.1.6876.120.1.0.40.0.2 | |||
notification · current Group member vmwNsxTDataCenterManagerNodeId of vmwNsxTDataCenterGroupType is up. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTClusteringClusterUnavailable | 1.3.6.1.4.1.6876.120.1.0.40.0.3 | |||
notification · current All group members vmwNsxTDataCenterManagerNodeIDS of service vmwNsxTDataCenterGroupType are down. Action required: 1. Ensure the service for vmwNsxTDataCenterGroupType is running on node. Invoke the GET /api/v1/node/services/<service_name>/status NSX API or the `get service <service_name>` NSX CLI command to determine if the service is running. If not running, invoke the POST /api/v1/node/services/<service_name>?action=restart NSX API or the `restart service <service_name>` NSX CLI to restart the service. 2. Check /var/log/ of service vmwNsxTDataCenterGroupType to see if there are errors reported. | ||||
| !vmwNsxTClusteringClusterUnavailableClear | 1.3.6.1.4.1.6876.120.1.0.40.0.4 | |||
notification · current All group members vmwNsxTDataCenterManagerNodeIDS of service vmwNsxTDataCenterGroupType are up. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTNSXApplicationPlatformCommunicationFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.41 | |||
node · current Notifications applicable to the NSXApplicationPlatformCommunication feature have this OID prefix. | ||||
| NvmwNsxTNSXApplicationPlatformCommunicationFeature | 1.3.6.1.4.1.6876.120.1.0.41.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for NSXApplicationPlatformCommunication feature notifications. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnected | 1.3.6.1.4.1.6876.120.1.0.41.0.1 | |||
notification · current The NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is disconnected from the NSX management cluster. Action required: Check whether the manager cluster certificate, manager node certificates, kafka certificate and ingress certificate match on both NSX Manager and the NSX Application Platform cluster. Check expiration dates of the above mentioned certificates to make sure they are valid. Check the network connection between NSX Manager and NSX Application Platform cluster and resolve any network connection failures. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnectedClear | 1.3.6.1.4.1.6876.120.1.0.41.0.2 | |||
notification · current The NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is reconnected to the NSX management cluster. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflow | 1.3.6.1.4.1.6876.120.1.0.41.0.7 | |||
notification · current The number of pending messages in the messaging topic Over Flow is above the pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. Action required: Add nodes and then scale up the NSX Application Platform cluster. If bottleneck can be attributed to a specific service, for example, the analytics service, then scale up the specific service when the new nodes are added. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflowClear | 1.3.6.1.4.1.6876.120.1.0.41.0.8 | |||
notification · current The number of pending messages in the messaging topic Over Flow is below the pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflow | 1.3.6.1.4.1.6876.120.1.0.41.0.11 | |||
notification · current The number of pending messages in the messaging topic Raw Flow is above the pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. Action required: Add nodes and then scale up the NSX Application Platform cluster. If the bottleneck can be attributed to a specific service, for example, the analytics service, then scale up the specific service when the new nodes are added. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflowClear | 1.3.6.1.4.1.6876.120.1.0.41.0.12 | |||
notification · current The number of pending messages in the messaging topic Raw Flow is below the pending message threshold of vmwNsxTDataCenterNappMessagingLAGThreshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationExpDisconnected | 1.3.6.1.4.1.6876.120.1.0.41.0.13 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId is disconnected from the NSX Application Platform cluster's messaging broker. Data collection is affected. Action required: Restart the messaging service if it is not running in the NSX Application Platform cluster. Resolve the network connection failure between the Transport node flow exporter and the NSX Application Platform cluster. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectedClear | 1.3.6.1.4.1.6876.120.1.0.41.0.14 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId has reconnected to the NSX Application Platform cluster's messaging broker. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectDPU | 1.3.6.1.4.1.6876.120.1.0.41.0.17 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId DPU vmwNsxTDataCenterDPUId is disconnected from the Intelligence node's messaging broker. Data collection is affected. Action required: Restart the messaging service if it is not running in the Intelligence node. Resolve the network connection failure between the Transport node flow exporter and the Intelligence node. | ||||
| !vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectDPUClear | 1.3.6.1.4.1.6876.120.1.0.41.0.18 | |||
notification · current The flow exporter on Transport node vmwNsxTDataCenterEntityId DPU vmwNsxTDataCenterDPUId has reconnected to the Intelligence node's messaging broker. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTMTUCheckFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.42 | |||
node · current Notifications applicable to the MTUCheck feature have this OID prefix. | ||||
| NvmwNsxTMTUCheckFeature | 1.3.6.1.4.1.6876.120.1.0.42.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for MTUCheck feature notifications. | ||||
| !vmwNsxTMTUCheckMTUMismatchWithinTransportZone | 1.3.6.1.4.1.6876.120.1.0.42.0.1 | |||
notification · current MTU configuration mismatch between Transport Nodes (ESXi, KVM and Edge) attached to the same Transport Zone. MTU values on all switches attached to the same Transport Zone not being consistent will cause connectivity issues. Action required: 1. Navigate to System | Fabric | Settings | MTU Configuration Check | Inconsistent on the NSX UI to check more mismatch details. 2. Set the same MTU value on all switches attached to the same Transport Zone by invoking the NSX API PUT /api/v1/host-switch-profiles/<host-switch-profile-id> with mtu in the request body, or API PUT /api/v1/global-configs/SwitchingGlobalConfig with physical_uplink_mtu in request body. | ||||
| !vmwNsxTMTUCheckMTUMismatchWithinTransportZoneClear | 1.3.6.1.4.1.6876.120.1.0.42.0.2 | |||
notification · current All MTU values between Transport Nodes attached to the same Transport Zone are consistent now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTMTUCheckGlobalRouterMTUTooBig | 1.3.6.1.4.1.6876.120.1.0.42.0.3 | |||
notification · current The global router MTU configuration is bigger than MTU of switches in overlay Transport Zone which connects to Tier0 or Tier1. Global router MTU value should be less than all switches MTU value by at least a 100 as we require 100 quota for Geneve encapsulation. Action required: 1. Navigate to System | Fabric | Settings | MTU Configuration Check | Inconsistent on the NSX UI to check more mismatch details. 2. Set the bigger MTU value on switches by invoking the NSX API PUT /api/v1/host-switch-profiles/<host-switch-profile-id> with mtu in the request body, or API PUT /api/v1/global-configs/SwitchingGlobalConfig with physical_uplink_mtu in request body. 3. Or set the smaller MTU value of global router configuration by invoking the NSX API PUT /api/v1/global-configs/RoutingGlobalConfig with logical_uplink_mtu in the request body. | ||||
| !vmwNsxTMTUCheckGlobalRouterMTUTooBigClear | 1.3.6.1.4.1.6876.120.1.0.42.0.4 | |||
notification · current The global router MTU is less than the MTU of overlay Transport Zone now. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTNSXApplicationPlatformHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.43 | |||
node · current Notifications applicable to the NSXApplicationPlatformHealth feature have this OID prefix. | ||||
| NvmwNsxTNSXApplicationPlatformHealthFeature | 1.3.6.1.4.1.6876.120.1.0.43.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for NSXApplicationPlatformHealth feature notifications. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.1 | |||
notification · current The CPU usage of Analytics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.2 | |||
notification · current The CPU usage of Analytics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.3 | |||
notification · current The CPU usage of Analytics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.4 | |||
notification · current The CPU usage of Analytics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.5 | |||
notification · current The disk usage of Analytics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.6 | |||
notification · current The disk usage of Analytics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.7 | |||
notification · current The disk usage of Analytics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.8 | |||
notification · current The disk usage of Analytics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.9 | |||
notification · current The memory usage of Analytics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.10 | |||
notification · current The memory usage of Analytics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.11 | |||
notification · current The memory usage of Analytics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Analytics service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.12 | |||
notification · current The memory usage of Analytics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.13 | |||
notification · current The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the System Load field of individual services to see which service is under pressure. See if the load can be reduced. If more computing power is required, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.14 | |||
notification · current The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.15 | |||
notification · current The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the System Load field of individual services to see which service is under pressure. See if the load can be reduced. If more computing power is required, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.16 | |||
notification · current The CPU usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.17 | |||
notification · current The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Storage field of individual services to see which service is under pressure. See if the load can be reduced. If more disk storage is required, click on the Scale Out button to request more resources. If data storage service is under strain, another way is to click on the Scale Up button to increase disk size. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.18 | |||
notification · current The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.19 | |||
notification · current The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Storage field of individual services to see which service is under pressure. See if the load can be reduced. If more disk storage is required, click on the Scale Out button to request more resources. If data storage service is under strain, another way is to click on the Scale Up button to increase disk size. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.20 | |||
notification · current The disk usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.21 | |||
notification · current The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Memory field of individual services to see which service is under pressure. See if the load can be reduced. If more memory is required, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.22 | |||
notification · current The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.23 | |||
notification · current The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Memory field of individual services to see which service is under pressure. See if the load can be reduced. If more memory is required, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.24 | |||
notification · current The memory usage of NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHi | 1.3.6.1.4.1.6876.120.1.0.43.0.31 | |||
notification · current The CPU usage of Configuration Database service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.32 | |||
notification · current The CPU usage of Configuration Database service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.33 | |||
notification · current The CPU usage of Configuration Database service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.34 | |||
notification · current The CPU usage of Configuration Database service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.35 | |||
notification · current The disk usage of Configuration Database service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.36 | |||
notification · current The disk usage of Configuration Database service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.37 | |||
notification · current The disk usage of Configuration Database service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.38 | |||
notification · current The disk usage of Configuration Database service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.39 | |||
notification · current The memory usage of Configuration Database service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.40 | |||
notification · current The memory usage of Configuration Database service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.41 | |||
notification · current The CPU usage of Data Storage service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Data Storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.42 | |||
notification · current The CPU usage of Data Storage service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.43 | |||
notification · current The CPU usage of Data Storage service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Data Storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.44 | |||
notification · current The CPU usage of Data Storage service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.45 | |||
notification · current The disk usage of Data Storage service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out or scale up the data storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.46 | |||
notification · current The disk usage of Data Storage service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.47 | |||
notification · current The disk usage of Data Storage service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out or scale up the data storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.48 | |||
notification · current The disk usage of Data Storage service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.49 | |||
notification · current The memory usage of Data Storage service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Data Storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.50 | |||
notification · current The memory usage of Data Storage service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.51 | |||
notification · current The memory usage of Data Storage service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Data Storage service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.52 | |||
notification · current The memory usage of Data Storage service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.53 | |||
notification · current The CPU usage of Messaging service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.54 | |||
notification · current The CPU usage of Messaging service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.55 | |||
notification · current The CPU usage of Messaging service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.56 | |||
notification · current The CPU usage of Messaging service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.57 | |||
notification · current The disk usage of Messaging service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.58 | |||
notification · current The disk usage of Messaging service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.59 | |||
notification · current The disk usage of Messaging service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.60 | |||
notification · current The disk usage of Messaging service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.61 | |||
notification · current The memory usage of Messaging service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.62 | |||
notification · current The memory usage of Messaging service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.63 | |||
notification · current The memory usage of Messaging service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services or the Messaging service. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.64 | |||
notification · current The memory usage of Messaging service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.65 | |||
notification · current The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the System Load field of individual services to see which service is under pressure. See if load can be reduced. If only a small minority of the nodes have high CPU usage, by default, Kubernetes will reschedule services automatically. If most nodes have high CPU usage and load cannot be reduced, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.66 | |||
notification · current The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.67 | |||
notification · current The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the System Load field of individual services to see which service is under pressure. See if load can be reduced. If only a small minority of the nodes have high CPU usage, by default, Kubernetes will reschedule services automatically. If most nodes have high CPU usage and load cannot be reduced, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.68 | |||
notification · current The CPU usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.69 | |||
notification · current The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Storage field of individual services to see which service is under pressure. Clean up unused data or log to free up disk resources and see if the load can be reduced. If more disk storage is required, Scale Out the service under pressure. If data storage service is under strain, another way is to click on the Scale Up button to increase disk size. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.70 | |||
notification · current The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.71 | |||
notification · current The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Storage field of individual services to see which service is under pressure. Clean up unused data or log to free up disk resources and see if the load can be reduced. If more disk storage is required, Scale Out the service under pressure. If data storage service is under strain, another way is to click on the Scale Up button to increase disk size. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.72 | |||
notification · current The disk usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.73 | |||
notification · current The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Memory field of individual services to see which service is under pressure. See if load can be reduced. If only a small minority of the nodes have high Memory usage, by default, Kubernetes will reschedule services automatically. If most nodes have high Memory usage and load cannot be reduced, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.74 | |||
notification · current The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.75 | |||
notification · current The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services and check the Memory field of individual services to see which service is under pressure. See if load can be reduced. If only a small minority of the nodes have high Memory usage, by default, Kubernetes will reschedule services automatically. If most nodes have high Memory usage and load cannot be reduced, click on the Scale Out button to request more resources. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.76 | |||
notification · current The memory usage of NSX Application Platform node vmwNsxTDataCenterNappNodeName is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeStatusDegraded | 1.3.6.1.4.1.6876.120.1.0.43.0.77 | |||
notification · current NSX Application Platform node vmwNsxTDataCenterNappNodeName is degraded. Action required: In the NSX UI, navigate to System | NSX Application Platform | Resources to check which node is degraded. Check network, memory and CPU usage of the node. Reboot the node if it is a worker node. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeStatusDegradedClear | 1.3.6.1.4.1.6876.120.1.0.43.0.78 | |||
notification · current NSX Application Platform node vmwNsxTDataCenterNappNodeName is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeStatusDown | 1.3.6.1.4.1.6876.120.1.0.43.0.79 | |||
notification · current NSX Application Platform node vmwNsxTDataCenterNappNodeName is not running. Action required: In the NSX UI, navigate to System | NSX Application Platform | Resources to check which node is down. Check network, memory and CPU usage of the node. Reboot the node if it is a worker node. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNodeStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.43.0.80 | |||
notification · current NSX Application Platform node vmwNsxTDataCenterNappNodeName is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.81 | |||
notification · current The CPU usage of Platform Services service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.82 | |||
notification · current The CPU usage of Platform Services service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.83 | |||
notification · current The CPU usage of Platform Services service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.84 | |||
notification · current The CPU usage of Platform Services service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.85 | |||
notification · current The disk usage of Platform Services service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.86 | |||
notification · current The disk usage of Platform Services service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.87 | |||
notification · current The disk usage of Platform Services service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.88 | |||
notification · current The disk usage of Platform Services service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.89 | |||
notification · current The memory usage of Platform Services service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.90 | |||
notification · current The memory usage of Platform Services service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHi | 1.3.6.1.4.1.6876.120.1.0.43.0.91 | |||
notification · current The memory usage of Platform Services service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.92 | |||
notification · current The memory usage of Platform Services service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded | 1.3.6.1.4.1.6876.120.1.0.43.0.93 | |||
notification · current Service vmwNsxTDataCenterNappServiceName is degraded. The service may still be able to reach a quorum while pods associated with vmwNsxTDataCenterNappServiceName are not all stable. Resources consumed by these unstable pods may be released. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which specific service is degraded and the reason behind it. Invoke the following CLI command to restart the degraded service if necessary: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` Degraded services can function correctly but performance is sub-optimal. | ||||
| !vmwNsxTNSXApplicationPlatformHealthServiceStatusDegradedClear | 1.3.6.1.4.1.6876.120.1.0.43.0.94 | |||
notification · current Service vmwNsxTDataCenterNappServiceName is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthServiceStatusDown | 1.3.6.1.4.1.6876.120.1.0.43.0.95 | |||
notification · current Service vmwNsxTDataCenterNappServiceName is not running. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which specific service is down and the reason behind it. Invoke the following CLI command to restart the degraded service: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` | ||||
| !vmwNsxTNSXApplicationPlatformHealthServiceStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.43.0.96 | |||
notification · current Service vmwNsxTDataCenterNappServiceName is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.97 | |||
notification · current The CPU usage of Metrics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.98 | |||
notification · current The CPU usage of Metrics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.99 | |||
notification · current The CPU usage of Metrics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.100 | |||
notification · current The CPU usage of Metrics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHi | 1.3.6.1.4.1.6876.120.1.0.43.0.101 | |||
notification · current The disk usage of Metrics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.102 | |||
notification · current The disk usage of Metrics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.103 | |||
notification · current The disk usage of Metrics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Clean up files not needed. Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.104 | |||
notification · current The disk usage of Metrics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHi | 1.3.6.1.4.1.6876.120.1.0.43.0.105 | |||
notification · current The memory usage of Metrics service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHiClear | 1.3.6.1.4.1.6876.120.1.0.43.0.106 | |||
notification · current The memory usage of Metrics service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.107 | |||
notification · current The memory usage of Metrics service is above the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.108 | |||
notification · current The memory usage of Metrics service is below the very high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHigh | 1.3.6.1.4.1.6876.120.1.0.43.0.109 | |||
notification · current The memory usage of Configuration Database service is above the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: Scale out all services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHighClear | 1.3.6.1.4.1.6876.120.1.0.43.0.110 | |||
notification · current The memory usage of Configuration Database service is below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNappStatusDegraded | 1.3.6.1.4.1.6876.120.1.0.43.0.117 | |||
notification · current NSX Application Platform cluster vmwNsxTDataCenterNappClusterId overall status is degraded. Action required: Get more information from alarms of nodes and services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNappStatusDegradedClear | 1.3.6.1.4.1.6876.120.1.0.43.0.118 | |||
notification · current NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNappStatusDown | 1.3.6.1.4.1.6876.120.1.0.43.0.119 | |||
notification · current NSX Application Platform cluster vmwNsxTDataCenterNappClusterId overall status is down. Action required: Get more information from alarms of nodes and services. | ||||
| !vmwNsxTNSXApplicationPlatformHealthNappStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.43.0.120 | |||
notification · current NSX Application Platform cluster vmwNsxTDataCenterNappClusterId is running properly. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTEdgeFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.45 | |||
node · current Notifications applicable to the Edge feature have this OID prefix. | ||||
| NvmwNsxTEdgeFeature | 1.3.6.1.4.1.6876.120.1.0.45.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Edge feature notifications. | ||||
| !vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChanged | 1.3.6.1.4.1.6876.120.1.0.45.0.1 | |||
notification · current The Edge node vmwNsxTDataCenterEntityId settings and vSphere configuration are changed and does not match the policy intent configuration. The Edge node configuration visible to user on UI or API is not same as what is realized. The realized Edge node changes made by user outside of NSX Manager are shown in the details of this alarm and any edits in UI or API will overwrite the realized configuration. Fields that differ for Edge node settings and vSphere configuration are listed in runtime data vmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason Action required: Review the node settings and vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. Follow one of following actions to resolve alarm - 1. Manually update Edge Transport Node setting Policy intent using API : PUT https://<manager-ip>/api/v1/transport-nodes/<tn-id>. 2. Accept intent or vSphere realized Edge node configuration or realized Edge node settings for this Edge Transport Node through Edge Transport Node resolver to resolve this alarm. 3. Resolve alarm by accepting the Edge node settings and vSphere realized configuration using refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. | ||||
| !vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChangedClear | 1.3.6.1.4.1.6876.120.1.0.45.0.2 | |||
notification · current Edge node vmwNsxTDataCenterEntityId node settings and vSphere settings are consistent with policy intent now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgeNodeSettingsMismatch | 1.3.6.1.4.1.6876.120.1.0.45.0.3 | |||
notification · current The Edge node vmwNsxTDataCenterEntityId settings configuration does not match the policy intent configuration. The Edge node configuration visible to user on UI or API is not same as what is realized. The realized Edge node changes made by user outside of NSX Manager are shown in the details of this alarm and any edits in UI or API will overwrite the realized configuration. Fields that differ for the Edge node are listed in runtime data vmwNsxTDataCenterEdgeNodeSettingMismatchReason Action required: Review the node settings of this Edge transport node vmwNsxTDataCenterEntityId. Follow one of following actions to resolve alarm - 1. Manually update Edge transport node setting Policy intent using API - PUT https://<manager-ip>/api/v1/transport-nodes/<tn-id>. 2. Accept intent or realized Edge node settings for this Edge transport node through Edge transport node resolver to resolve this alarm. 3. Resolve alarm by accepting the Edge node settings configuration using refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. | ||||
| !vmwNsxTEdgeEdgeNodeSettingsMismatchClear | 1.3.6.1.4.1.6876.120.1.0.45.0.4 | |||
notification · current Edge node vmwNsxTDataCenterEntityId node settings are consistent with policy intent now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgeVmvSphereSettingsMismatch | 1.3.6.1.4.1.6876.120.1.0.45.0.5 | |||
notification · current The Edge node vmwNsxTDataCenterEntityId configuration on vSphere does not match the policy intent configuration. The Edge node configuration visible to user on UI or API is not same as what is realized. The realized Edge node changes made by user outside of NSX Manager are shown in the details of this alarm and any edits in UI or API will overwrite the realized configuration. Fields that differ for the Edge node are listed in runtime data vmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason Action required: Review the vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. Follow one of following actions to resolve alarm - 1. Accept intent or vSphere realized Edge node configuration for this Edge Transport Node through Edge Transport Node resolver to resolve this alarm. 2. Resolve alarm by accepting the Edge node vSphere realized configuration using refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. | ||||
| !vmwNsxTEdgeEdgeVmvSphereSettingsMismatchClear | 1.3.6.1.4.1.6876.120.1.0.45.0.6 | |||
notification · current Edge node vmwNsxTDataCenterEntityId VM vSphere settings are consistent with policy intent now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgevSphereLocationMismatch | 1.3.6.1.4.1.6876.120.1.0.45.0.7 | |||
notification · current The Edge node vmwNsxTDataCenterEntityId has been moved using vMotion. The Edge node vmwNsxTDataCenterEntityId, the configuration on vSphere does not match the policy intent configuration. The Edge node configuration visible to user on UI or API is not same as what is realized. The realized Edge node changes made by user outside of NSX Manager are shown in the details of this alarm. Fields that differ for the Edge node are listed in runtime data vmwNsxTDataCenterEdgevSphereLocationMismatchReason Action required: Review the vSphere configuration of this Edge Transport Node vmwNsxTDataCenterEntityId. Follow one of following actions to resolve alarm - 1. Resolve alarm by accepting the Edge node vSphere realized config using refresh API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=refresh_node_configuration&resource_type=EdgeNode. 2. If you want to return to the previous location use NSX Redeploy API - POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy. vMotion back to the original host is not supported. | ||||
| !vmwNsxTEdgeEdgevSphereLocationMismatchClear | 1.3.6.1.4.1.6876.120.1.0.45.0.8 | |||
notification · current Edge node vmwNsxTDataCenterEntityId node vSphere settings are consistent with policy intent now. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgeVMPresentInNSXInventoryNotPresentInvCenter | 1.3.6.1.4.1.6876.120.1.0.45.0.9 | |||
notification · current The VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId corresponding to the Edge Transport node vmwNsxTDataCenterEntityId vSphere placement parameters is found in NSX inventory but is not present in vCenter. Check if the VM has been removed in vCenter or is present with a different VM moref id. Action required: The managed object reference moref id of a VM has the form vm-number, which is visible in the URL on selecting the Edge VM in vCenter UI. Example vm-12011 in https://<vc-url>/ui/app/vm;nav=h/urn:vmomi:VirtualMachine:vm-12011:164ff798-c4f1-495b-a0be-adfba337e5d2/summary Find the VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId in vCenter for this Edge Transport Node vmwNsxTDataCenterEntityId. If the Edge VM is present in vCenter with a different moref id, follow the below action. Use NSX add or update placement API with JSON request payload properties vm_id and vm_deployment_config to update the new vm moref id and vSphere deployment parameters. POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=addOrUpdatePlacementReferences. If the Edge VM with name vmwNsxTDataCenterPolicyEdgeVMName is not present in vCenter, use the NSX Redeploy API to deploy a new VM for the Edge node. POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy. | ||||
| !vmwNsxTEdgeEdgeVMPresentInNSXInventoryNotPresentInvCenterClear | 1.3.6.1.4.1.6876.120.1.0.45.0.10 | |||
notification · current Edge node vmwNsxTDataCenterEntityId with VM moref id vmwNsxTDataCenterVMMorefId is present in both NSX inventory and vCenter. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgeVMNotPresentInBothNSXInventoryAndvCenter | 1.3.6.1.4.1.6876.120.1.0.45.0.11 | |||
notification · current The VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId corresponding to the Edge Transport node vmwNsxTDataCenterEntityId vSphere placement parameters is not found in both NSX inventory and vCenter. The placement parameters in the vSphere configuration of this Edge Transport node vmwNsxTDataCenterEntityId refer to the VM with moref vmwNsxTDataCenterVMMorefId. Action required: The managed object reference moref id of a VM has the form vm-number, which is visible in the URL on selecting the Edge VM in vCenter UI. Example vm-12011 in https://<vc-url>/ui/app/vm;nav=h/urn:vmomi:VirtualMachine:vm-12011:164ff798-c4f1-495b-a0be-adfba337e5d2/summary Find the VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId in vCenter for this Edge Transport Node vmwNsxTDataCenterEntityId. Follow the below action to resolve the alarm - Check if VM has been deleted in vSphere or is present with a different moref id. 1. If the VM is still present in vCenter, put the Edge Transport node in maintenance mode and then power off and delete the Edge VM in vCenter. Use the NSX Redeploy API to deploy a new VM for the Edge node. Data traffic for the Edge Transport node will be disrupted in the interim duration if the Edge VM is forwarding traffic. 2. If the VM is not present in vCenter, use the redeploy API to deploy a new VM for the Edge node. POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy. | ||||
| !vmwNsxTEdgeEdgeVMNotPresentInBothNSXInventoryAndvCenterClear | 1.3.6.1.4.1.6876.120.1.0.45.0.12 | |||
notification · current Edge node vmwNsxTDataCenterEntityId with VM moref id vmwNsxTDataCenterVMMorefId is present in both NSX inventory and vCenter. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeFailedToDeleteTheOldVMInvCenterDuringRedeploy | 1.3.6.1.4.1.6876.120.1.0.45.0.13 | |||
notification · current Failed to power off and delete the Edge node vmwNsxTDataCenterEntityId VM with moref id vmwNsxTDataCenterVMMorefId in vCenter during Redeploy operation. A new Edge VM with moref id vmwNsxTDataCenterNewVMMorefId has been deployed. Both old and new VMs for this Edge are functional at the same time and may result in IP conflicts and networking issues. Action required: The managed object reference moref id of a VM has the form vm-number, which is visible in the URL on selecting the Edge VM in vCenter UI. Example vm-12011 in https://<vc-url>/ui/app/vm;nav=h/urn:vmomi:VirtualMachine:vm-12011:164ff798-c4f1-495b-a0be-adfba337e5d2/summary Find the VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId in vCenter for this Edge Transport Node vmwNsxTDataCenterEntityId. Power off and delete the old Edge VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId in vCenter. | ||||
| !vmwNsxTEdgeFailedToDeleteTheOldVMInvCenterDuringRedeployClear | 1.3.6.1.4.1.6876.120.1.0.45.0.14 | |||
notification · current Edge node vmwNsxTDataCenterEntityId with stale VM moref id vmwNsxTDataCenterVMMorefId is not found anymore in both NSX inventory and vCenter. New deployed VM with moref id vmwNsxTDataCenterNewVMMorefId is present in both NSX inventory and vCenter. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTEdgeEdgeHardwareVersionMismatch | 1.3.6.1.4.1.6876.120.1.0.45.0.15 | |||
notification · current The Edge node vmwNsxTDataCenterTransportNodeName in Edge cluster vmwNsxTDataCenterEdgeClusterName has a hardware version vmwNsxTDataCenterEdgeTNHwVersion, which is less than the highest hardware version vmwNsxTDataCenterEdgeClusterHighestHwVersion in the Edge cluster. Action required: Follow KB article to resolve hardware version mismatch alarm for Edge node vmwNsxTDataCenterTransportNodeName. For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=edge.edge_hardware_version_mismatch
| ||||
| !vmwNsxTEdgeEdgeHardwareVersionMismatchClear | 1.3.6.1.4.1.6876.120.1.0.45.0.16 | |||
notification · current The Edge node vmwNsxTDataCenterTransportNodeName hardware version mismatch is resolved now. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTNATFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.46 | |||
node · current Notifications applicable to the NAT feature have this OID prefix. | ||||
| NvmwNsxTNATFeature | 1.3.6.1.4.1.6876.120.1.0.46.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for NAT feature notifications. | ||||
| !vmwNsxTNATSNATPortUsageOnGatewayIsHigh | 1.3.6.1.4.1.6876.120.1.0.46.0.1 | |||
notification · current SNAT ports usage on logical router vmwNsxTDataCenterEntityId for SNAT IP vmwNsxTDataCenterSNATIPAddress has reached the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. New flows will not be SNATed when usage reaches the maximum limit. Action required: Log in as the admin user on Edge node and invoke the NSX CLI command `get firewall <LR_INT_UUID> connection state` by using the right interface uuid and check various SNAT mappings for the SNAT IP vmwNsxTDataCenterSNATIPAddress. Check traffic flows going through the gateway is not a denial-of-service attack or anomalous burst. If the traffic appears to be within the normal load but the alarm threshold is hit, consider adding more SNAT IP addresses to distribute the load or route new traffic to another Edge node. | ||||
| !vmwNsxTNATSNATPortUsageOnGatewayIsHighClear | 1.3.6.1.4.1.6876.120.1.0.46.0.2 | |||
notification · current SNAT ports usage on logical router vmwNsxTDataCenterEntityId for SNAT IP vmwNsxTDataCenterSNATIPAddress has reached below the high threshold value of vmwNsxTDataCenterSystemUsageThreshold%. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTPhysicalServerFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.47 | |||
node · current Notifications applicable to the PhysicalServer feature have this OID prefix. | ||||
| NvmwNsxTPhysicalServerFeature | 1.3.6.1.4.1.6876.120.1.0.47.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for PhysicalServer feature notifications. | ||||
| !vmwNsxTPhysicalServerPhysicalServerInstallFailed | 1.3.6.1.4.1.6876.120.1.0.47.0.1 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) installation failed. Action required: Navigate to System > Fabric > Nodes > Host Transport Nodes and resolve the error on the node. | ||||
| !vmwNsxTPhysicalServerPhysicalServerInstallFailedClear | 1.3.6.1.4.1.6876.120.1.0.47.0.2 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) installation completed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTPhysicalServerPhysicalServerUninstallFailed | 1.3.6.1.4.1.6876.120.1.0.47.0.3 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) uninstallation failed. Action required: Navigate to System > Fabric > Nodes > Host Transport Nodes and resolve the error on the node. | ||||
| !vmwNsxTPhysicalServerPhysicalServerUninstallFailedClear | 1.3.6.1.4.1.6876.120.1.0.47.0.4 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) uninstallation completed. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTPhysicalServerPhysicalServerUpgradeFailed | 1.3.6.1.4.1.6876.120.1.0.47.0.5 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) upgrade failed. Action required: Navigate to System > Upgrade and resolve the error, then re-trigger the upgrade. | ||||
| !vmwNsxTPhysicalServerPhysicalServerUpgradeFailedClear | 1.3.6.1.4.1.6876.120.1.0.47.0.6 | |||
notification · current Physical Server vmwNsxTDataCenterTransportNodeName (vmwNsxTDataCenterEntityId) upgrade completed. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTMalwarePreventionHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.48 | |||
node · current Notifications applicable to the MalwarePreventionHealth feature have this OID prefix. | ||||
| NvmwNsxTMalwarePreventionHealthFeature | 1.3.6.1.4.1.6876.120.1.0.48.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for MalwarePreventionHealth feature notifications. | ||||
| !vmwNsxTMalwarePreventionHealthAnalystAPIServiceUnreachable | 1.3.6.1.4.1.6876.120.1.0.48.0.1 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is degraded on NSX Application Platform. It is unable to communicate with analyst_api service. Inspected file verdicts may not be up to date. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which specific service is down and the reason behind it. Invoke the following CLI command to restart the degraded service: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` Determine the status of Malware Prevention Cloud Connector service. For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=malware_prevention_health.analyst_api_service_unreachable | ||||
| !vmwNsxTMalwarePreventionHealthAnalystAPIServiceUnreachableClear | 1.3.6.1.4.1.6876.120.1.0.48.0.2 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is running properly on NSX Application Platform. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTMalwarePreventionHealthDatabaseUnreachable | 1.3.6.1.4.1.6876.120.1.0.48.0.3 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is degraded on NSX Application Platform. It is unable to communicate with Malware Prevention database. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which specific service is down and the reason behind it. Invoke the following CLI command to restart the degraded service: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` Determine the status of Malware Prevention Database service. For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=malware_prevention_health.database_unreachable | ||||
| !vmwNsxTMalwarePreventionHealthDatabaseUnreachableClear | 1.3.6.1.4.1.6876.120.1.0.48.0.4 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is running properly on NSX Application Platform. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTMalwarePreventionHealthFileExtractSvcUnreachable | 1.3.6.1.4.1.6876.120.1.0.48.0.5 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is degraded on vmwNsxTDataCenterTransportNodeName. Unable to communicate with file extraction functionality. All file extraction abilities on the vmwNsxTDataCenterTransportNodeName are paused. Action required: 1. On the Edge node identified by vmwNsxTDataCenterNSXEdgeTNName, invoke the NSX CLI `get ids engine status` to check the status of file_extraction (IDS) service. Inspect /var/log/syslog to find any suspecting error(s) with the file extraction (IDS) service and/or vmwNsxTDataCenterMpsServiceName. 2. On the Host node identified by vmwNsxTDataCenterNSXESXTNName, log into the associated Malware Prevention Service VM vmwNsxTDataCenterEntityId and check the status of file extraction (NXGI) service. Inspect /var/log/syslog on the associated Malware Prevention Service VM vmwNsxTDataCenterEntityId to find any suspecting error(s). For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=malware_prevention_health.file_extraction_service_unreachable
| ||||
| !vmwNsxTMalwarePreventionHealthFileExtractSvcUnreachableClear | 1.3.6.1.4.1.6876.120.1.0.48.0.6 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is running properly on vmwNsxTDataCenterTransportNodeName. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTMalwarePreventionHealthNTICSRepSvcUnreachable | 1.3.6.1.4.1.6876.120.1.0.48.0.7 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is degraded on NSX Application Platform. It is unable to communicate with NTICS reputation service. Inspected file reputations may not be up to date. Action required: In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which specific service is down and the reason behind it. Invoke the following CLI command to restart the degraded service: `kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>` Determine if access to NTICS service is down. | ||||
| !vmwNsxTMalwarePreventionHealthNTICSRepSvcUnreachableClear | 1.3.6.1.4.1.6876.120.1.0.48.0.8 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is running properly on NSX Application Platform. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTMalwarePreventionHealthServiceStatusDown | 1.3.6.1.4.1.6876.120.1.0.48.0.9 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is not running on vmwNsxTDataCenterTransportNodeName. Action required: 1. On the Edge node identified by vmwNsxTDataCenterNSXEdgeTNName, invoke the NSX CLI `get services` to check the status of vmwNsxTDataCenterMpsServiceName. Inspect /var/log/syslog to find any suspecting error(s). 2. On the Host node identified by vmwNsxTDataCenterNSXESXTNName, log into the associated Malware Prevention Service VM vmwNsxTDataCenterEntityId and check the status of vmwNsxTDataCenterMpsServiceName. Inspect /var/log/syslog on the associated Malware Prevention Service VM vmwNsxTDataCenterEntityId to find any suspecting error(s). For more information see: https://www.vmware.com/esx/support/askvmware/index.php?eventtype=malware_prevention_health.service_status_down
| ||||
| !vmwNsxTMalwarePreventionHealthServiceStatusDownClear | 1.3.6.1.4.1.6876.120.1.0.48.0.10 | |||
notification · current Service vmwNsxTDataCenterMpsServiceName is running properly on vmwNsxTDataCenterTransportNodeName. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTEdgeClusterFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.49 | |||
node · current Notifications applicable to the EdgeCluster feature have this OID prefix. | ||||
| NvmwNsxTEdgeClusterFeature | 1.3.6.1.4.1.6876.120.1.0.49.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for EdgeCluster feature notifications. | ||||
| !vmwNsxTEdgeClusterEdgeClusterMemberRelocateFailure | 1.3.6.1.4.1.6876.120.1.0.49.0.5 | |||
notification · current The operation on Edge cluster vmwNsxTDataCenterEdgeClusterId to relocate all service context failed for Edge cluster member index vmwNsxTDataCenterMemberIndexId with Transport node ID vmwNsxTDataCenterTransportNodeId Action required: Review the available capacity for the Edge cluster. If more capacity is required, scale your Edge cluster. Retry the relocate Edge cluster member operation.
| ||||
| !vmwNsxTEdgeClusterEdgeClusterMemberRelocateFailureClear | 1.3.6.1.4.1.6876.120.1.0.49.0.6 | |||
notification · current Edge node with vmwNsxTDataCenterTransportNodeId relocation failure has been resolved now. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTVMCAppFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.50 | |||
node · current Notifications applicable to the VMCApp feature have this OID prefix. | ||||
| NvmwNsxTVMCAppFeature | 1.3.6.1.4.1.6876.120.1.0.50.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for VMCApp feature notifications. | ||||
| !vmwNsxTVMCAppTransitConnectFailure | 1.3.6.1.4.1.6876.120.1.0.50.0.1 | |||
notification · current Transit Connect related configuration is not fully correctly realized. Possible issues could be failing to retrieve provider information or some transient provider communication error. Action required: If this alarm is not auto-resolved within 10 minutes, retry the most recent transit connect related request(s). For example, if a TGW attachment API request triggered this alarm, retry the TGW attachment API request again. If alarm does not resolve even after retry, then try the following steps: 1. Check if the task keeps failing, or the task has recovered. a) Identify leader Manager node. After logging into one of the nodes, run command: - `su admin` - `get cluster status verbose` This will show the leader Manager node b) Log in to NSX leader Manager node. check vmc-app.log on the NSX leader Manager node: - `tail -f /var/log/policy/vmc-app.log` c) Check logs for following prints - If any of these error messages keeps showing every two mins, that means task keeps failing. - Failed to get TGW route table for []. Error: [] - Failed to get TGW routes for attachment [] in route table []. Error - Failed to get TGW attachment VPC ID for []. Error: [] - Failed to get TGW attachment resource ID for []. Error: Unknown resource type - Failed to get TGW attachments for TGW []. Error: [] - Failed to get local TGW attachment []. Error: [] - Failed to find correct TgwAttachment state in AWS, state: [], skipping TGW route update task - TGW attachment [] is not associated with any route table - No local TGW SDDC attachment found for [] 2. Check if all AWS calls from NSX Manager failed, on leader Manager node. Run following command: - `export HTTP_PROXY=http://<pop ip>:3128` - `export HTTPS_PROXY=http://<pop ip>:3128` - `export NO_PROXY=169.254.169.254` - `aws ec2 describe-instances --region <region>` If aws command failed with error, then there might be a system issue in HTTP reverse proxy configuration on pop, or there is AWS service side issue. 3. Check whether TGW attachment still exists in AWS. a) TGW attachment ID could be found with GET cloud-service/api/v1/infra/associated-groups - `aws ec2 describe-transit-gateway-attachments --region <region> --transit-gateway-attachment-id <TGW attachment ID>` If TGW attachment has been deleted, contact VMware Support, share SDDC ID and TGW attachment ID. After VMware support team identified the issue, manually delete the object left behind, if needed. b) Check if this TGW attachment exists on AWS console. c) Another option is logging in to NSX Manager, using aws command to check the state of TGW attachment: - `aws ec2 describe-transit-gateway-attachments --region <region> --transit-gateway-attachment-id <TGW attachment ID>` | ||||
| !vmwNsxTVMCAppTransitConnectFailureClear | 1.3.6.1.4.1.6876.120.1.0.50.0.2 | |||
notification · current Transit Connect failure is remediated. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTTEPHealthFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.51 | |||
node · current Notifications applicable to the TEPHealth feature have this OID prefix. | ||||
| NvmwNsxTTEPHealthFeature | 1.3.6.1.4.1.6876.120.1.0.51.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for TEPHealth feature notifications. | ||||
| !vmwNsxTTEPHealthFaultyTEP | 1.3.6.1.4.1.6876.120.1.0.51.0.1 | |||
notification · current TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. Overlay workloads using this TEP will face network outage. Reason: vmwNsxTDataCenterVtepFaultReason. Action required: 1. Check if TEP has valid IP or any other underlay connectivity issues. 2. Enable TEP HA to failover workloads to other healthy TEPs.
| ||||
| !vmwNsxTTEPHealthFaultyTEPClear | 1.3.6.1.4.1.6876.120.1.0.51.0.2 | |||
notification · current TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId is healthy. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTEPHealthFaultyTEPOnDPU | 1.3.6.1.4.1.6876.120.1.0.51.0.3 | |||
notification · current TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId. Overlay workloads using this TEP will face network outage. Reason: vmwNsxTDataCenterVtepFaultReason. Action required: 1. Check if TEP has valid IP or any other underlay connectivity issues. 2. Enable TEP HA to failover workloads to other healthy TEPs.
| ||||
| !vmwNsxTTEPHealthFaultyTEPOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.51.0.4 | |||
notification · current TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId is healthy. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTTEPHealthTEPAutorecoverFailure | 1.3.6.1.4.1.6876.120.1.0.51.0.5 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId failed. Overlay workloads using this TEP will failover to other healthy TEPs. If no other healthy TEPs, overlay workloads will face network outage. Action required: Check if TEP has valid IP or any other underlay connectivity issues. | ||||
| !vmwNsxTTEPHealthTEPAutorecoverFailureClear | 1.3.6.1.4.1.6876.120.1.0.51.0.6 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId is cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTEPHealthTEPAutorecoverFailureOnDPU | 1.3.6.1.4.1.6876.120.1.0.51.0.7 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId failed. Overlay workloads using this TEP will failover to other healthy TEPs. If no other healthy TEPs, overlay workloads will face network outage. Action required: Check if TEP has valid IP or any other underlay connectivity issues.
| ||||
| !vmwNsxTTEPHealthTEPAutorecoverFailureOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.51.0.8 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId is cleared. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTTEPHealthTEPAutorecoverSuccess | 1.3.6.1.4.1.6876.120.1.0.51.0.9 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId is successful. Action required: None. | ||||
| !vmwNsxTTEPHealthTEPAutorecoverSuccessClear | 1.3.6.1.4.1.6876.120.1.0.51.0.10 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId is cleared. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTEPHealthTEPAutorecoverSuccessOnDPU | 1.3.6.1.4.1.6876.120.1.0.51.0.11 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. on DPU vmwNsxTDataCenterDPUId is successful. Action required: None.
| ||||
| !vmwNsxTTEPHealthTEPAutorecoverSuccessOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.51.0.12 | |||
notification · current Auto Recover for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. on DPU vmwNsxTDataCenterDPUId is cleared. Action required: None, receipt of this notification indicates event cleared.
| ||||
| !vmwNsxTTEPHealthTEPHaActivated | 1.3.6.1.4.1.6876.120.1.0.51.0.13 | |||
notification · current TEP HA activated for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. Action required: Enable AutoRecover or invoke Manual Recover for TEP:vmwNsxTDataCenterVtepName on VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. | ||||
| !vmwNsxTTEPHealthTEPHaActivatedClear | 1.3.6.1.4.1.6876.120.1.0.51.0.14 | |||
notification · current TEP HA cleared for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTTEPHealthTEPHaActivatedOnDPU | 1.3.6.1.4.1.6876.120.1.0.51.0.15 | |||
notification · current TEP HA activated for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId. Action required: Enable AutoRecover or invoke Manual Recover for TEP:vmwNsxTDataCenterVtepName on VDS:vmwNsxTDataCenterDvsName. at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId.
| ||||
| !vmwNsxTTEPHealthTEPHaActivatedOnDPUClear | 1.3.6.1.4.1.6876.120.1.0.51.0.16 | |||
notification · current TEP HA cleared for TEP:vmwNsxTDataCenterVtepName of VDS:vmwNsxTDataCenterDvsName at Transport node:vmwNsxTDataCenterTransportNodeId on DPU vmwNsxTDataCenterDPUId. Action required: None, receipt of this notification indicates event cleared.
| ||||
| NvmwNsxTPolicyConstraintFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.53 | |||
node · current Notifications applicable to the PolicyConstraint feature have this OID prefix. | ||||
| NvmwNsxTPolicyConstraintFeature | 1.3.6.1.4.1.6876.120.1.0.53.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for PolicyConstraint feature notifications. | ||||
| !vmwNsxTPolicyConstraintCreationCountLimitReached | 1.3.6.1.4.1.6876.120.1.0.53.0.1 | |||
notification · current Entity count for type vmwNsxTDataCenterConstraintType in vmwNsxTDataCenterConstraintTypePath is currently at vmwNsxTDataCenterCurrentCount which reached the maximum limit of vmwNsxTDataCenterConstraintLimit. Action required: Review vmwNsxTDataCenterConstraintType usage. Update the constraint to increase the limit or delete unused vmwNsxTDataCenterConstraintType.
| ||||
| !vmwNsxTPolicyConstraintCreationCountLimitReachedClear | 1.3.6.1.4.1.6876.120.1.0.53.0.2 | |||
notification · current vmwNsxTDataCenterConstraintType Count is below threshold. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTGroupsFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.54 | |||
node · current Notifications applicable to the Groups feature have this OID prefix. | ||||
| NvmwNsxTGroupsFeature | 1.3.6.1.4.1.6876.120.1.0.54.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for Groups feature notifications. | ||||
| !vmwNsxTGroupsGroupSizeLimitExceeded | 1.3.6.1.4.1.6876.120.1.0.54.0.3 | |||
notification · current Group vmwNsxTDataCenterGroupId has at least vmwNsxTDataCenterGroupSize translated elements which is at or greater than the maximum numbers limit of vmwNsxTDataCenterGroupMaxNumberLimit. This can result in long processing times and can lead to timeouts and outages. The current count for each element type is as follows. IP sets:vmwNsxTDataCenterIPCount, MAC sets:vmwNsxTDataCenterMacCount, VIFS:vmwNsxTDataCenterVifCount, Logical switch ports:vmwNsxTDataCenterLspCount, Logical router ports:vmwNsxTDataCenterLrpCount, AdGroups:vmwNsxTDataCenterSidCount. Action required: 1. Consider adjusting group elements in oversized group vmwNsxTDataCenterGroupId. 2. Consider splitting oversized group vmwNsxTDataCenterGroupId to multiple smaller groups and distributing members of oversized group to these groups.
| ||||
| !vmwNsxTGroupsGroupSizeLimitExceededClear | 1.3.6.1.4.1.6876.120.1.0.54.0.4 | |||
notification · current Total number of elements in group vmwNsxTDataCenterGroupId is below the maximum limit of vmwNsxTDataCenterGroupMaxNumberLimit. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTSecurityComplianceFeaturePrefix | 1.3.6.1.4.1.6876.120.1.0.56 | |||
node · current Notifications applicable to the SecurityCompliance feature have this OID prefix. | ||||
| NvmwNsxTSecurityComplianceFeature | 1.3.6.1.4.1.6876.120.1.0.56.0 | |||
node · current Sub-identifier added to ensure the next-to-last sub-identifier is zero for SecurityCompliance feature notifications. | ||||
| !vmwNsxTSecurityCompliancePollEAL4NonCompliance | 1.3.6.1.4.1.6876.120.1.0.56.0.1 | |||
notification · current One of the EAL4+ compliance requirements is being violated. That means the NSX configuration is currently non-compliant with regards to EAL4+. Action required: Run the compliance report from the UI Home - Monitoring & Dashboard - Compliance Report menu and resolve all the issues that are marked with the EAL4+ compliance name. | ||||
| !vmwNsxTSecurityCompliancePollEAL4NonComplianceClear | 1.3.6.1.4.1.6876.120.1.0.56.0.2 | |||
notification · current The EAL4+ compliance issues have all been resolved. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTSecurityCompliancePollNDcPPNonCompliance | 1.3.6.1.4.1.6876.120.1.0.56.0.3 | |||
notification · current One of the NDcPP compliance requirements is being violated. That means the NSX configuration is currently non-compliant with regards to NDcPP. Action required: Run the compliance report from the UI Home - Monitoring & Dashboard - Compliance Report menu and resolve all the issues that are marked with the NDcPP compliance name. | ||||
| !vmwNsxTSecurityCompliancePollNDcPPNonComplianceClear | 1.3.6.1.4.1.6876.120.1.0.56.0.4 | |||
notification · current The NDcPP compliance issues have all been resolved. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTSecurityComplianceTriggerEAL4NonCompliance | 1.3.6.1.4.1.6876.120.1.0.56.0.5 | |||
notification · current One of the EAL4+ compliance requirements is being violated. That means the NSX status is currently non-compliant with regards to EAL4+. Action required: Run the compliance report from the UI Home - Monitoring & Dashboard - Compliance Report menu and resolve all the issues that are marked with the EAL4+ compliance name. | ||||
| !vmwNsxTSecurityComplianceTriggerEAL4NonComplianceClear | 1.3.6.1.4.1.6876.120.1.0.56.0.6 | |||
notification · current The EAL4+ compliance issues have all been resolved. Action required: None, receipt of this notification indicates event cleared. | ||||
| !vmwNsxTSecurityComplianceTriggerNDcPPNonCompliance | 1.3.6.1.4.1.6876.120.1.0.56.0.7 | |||
notification · current One of the NDcPP compliance requirements is being violated. That means the NSX status is currently non-compliant with regards to NDcPP. Action required: Run the compliance report from the UI Home - Monitoring & Dashboard - Compliance Report menu and resolve all the issues that are marked with the NDcPP compliance name. | ||||
| !vmwNsxTSecurityComplianceTriggerNDcPPNonComplianceClear | 1.3.6.1.4.1.6876.120.1.0.56.0.8 | |||
notification · current The NDcPP compliance issues have all been resolved. Action required: None, receipt of this notification indicates event cleared. | ||||
| NvmwNsxTDataCenterData | 1.3.6.1.4.1.6876.120.1.1 | |||
node · current All variables that are sent in NSX Data Center event notifications fall under this oid. | ||||
| SvmwNsxTDataCenterTimestamp | 1.3.6.1.4.1.6876.120.1.1.1 | DateAndTime | AN | |
scalar · DateAndTime · accessible-for-notify · current The timestamp when the NSX Data Center event occurred. | ||||
| SvmwNsxTDataCenterFeatureName | 1.3.6.1.4.1.6876.120.1.1.2 | VmwNsxTDataCenterFeatureIdType | AN | |
scalar · VmwNsxTDataCenterFeatureIdType · accessible-for-notify · current The NSX Data Center feature ID associated with the event. | ||||
| SvmwNsxTDataCenterEventType | 1.3.6.1.4.1.6876.120.1.1.3 | VmwNsxTDataCenterEventTypeType | AN | |
scalar · VmwNsxTDataCenterEventTypeType · accessible-for-notify · current The name of the NSX Data Center event. | ||||
| SvmwNsxTDataCenterEventSeverity | 1.3.6.1.4.1.6876.120.1.1.4 | VmwNsxTDataCenterSeverityType | AN | |
scalar · VmwNsxTDataCenterSeverityType · accessible-for-notify · current The severity of the NSX Data Center event. | ||||
| SvmwNsxTDataCenterNodeId | 1.3.6.1.4.1.6876.120.1.1.5 | VmwNsxTDataCenterNodeIdType | AN | |
scalar · VmwNsxTDataCenterNodeIdType · accessible-for-notify · current The node ID from where a NSX Data Center event was emitted. | ||||
| SvmwNsxTDataCenterNodeType | 1.3.6.1.4.1.6876.120.1.1.6 | VmwNsxTDataCenterNodeTypeType | AN | |
scalar · VmwNsxTDataCenterNodeTypeType · accessible-for-notify · current The type of node from where a NSX Data Center event was emitted. | ||||
| SvmwNsxTDataCenterEntityId | 1.3.6.1.4.1.6876.120.1.1.21 | VmwNsxTDataCenterEntityIdType | AN | |
scalar · VmwNsxTDataCenterEntityIdType · accessible-for-notify · current The ID of a NSX Data Center entity an event pertains to. The event description field provides additional details of the entity. For example the ID can be for a specific Load Balancer rule as reported by the NSX API GET /api/v1/loadbalancer/rules or a specific certificate as reported by the NSX API GET /api/v1/trust-management/certificates. | ||||
| SvmwNsxTDataCenterSystemResourceUsage | 1.3.6.1.4.1.6876.120.1.1.22 | VmwNsxTDataCenterSystemResourceUsageType | AN | |
scalar · VmwNsxTDataCenterSystemResourceUsageType · accessible-for-notify · current The CPU, memory, or disk usage percentage of an NSX appliance. The value is an integer between 0 and 100. | ||||
| SvmwNsxTDataCenterDiskPartitionName | 1.3.6.1.4.1.6876.120.1.1.23 | VmwNsxTDataCenterDiskPartitionNameType | AN | |
scalar · VmwNsxTDataCenterDiskPartitionNameType · accessible-for-notify · current The name of a disk partition in an NSX appliance. For example, the name for the /tmp partition is '/tmp'. | ||||
| SvmwNsxTDataCenterLicenseEditionType | 1.3.6.1.4.1.6876.120.1.1.24 | VmwNsxTDataCenterLicenseEditionTypeType | AN | |
scalar · VmwNsxTDataCenterLicenseEditionTypeType · accessible-for-notify · current The edition type of an NSX license. For example, the type for an NSX evaluation license is 'NSX Data Center Evaluation'. | ||||
| SvmwNsxTDataCenterApplianceAddress | 1.3.6.1.4.1.6876.120.1.1.25 | VmwNsxTDataCenterApplianceAddressType | AN | |
scalar · VmwNsxTDataCenterApplianceAddressType · accessible-for-notify · current The NSX appliance's IP address. The value is an IPv4 address. | ||||
| SvmwNsxTDataCenterCurrentGatewayState | 1.3.6.1.4.1.6876.120.1.1.26 | VmwNsxTDataCenterCurrentGatewayStateType | AN | |
scalar · VmwNsxTDataCenterCurrentGatewayStateType · accessible-for-notify · current The current gateway state. The value could be 0, 1 or 2 where 0 is down, 1 is standby and 2 is active | ||||
| SvmwNsxTDataCenterCurrentServiceState | 1.3.6.1.4.1.6876.120.1.1.27 | VmwNsxTDataCenterCurrentServiceStateType | AN | |
scalar · VmwNsxTDataCenterCurrentServiceStateType · accessible-for-notify · current The current service state. The value could be start/stop/restart/crashed. | ||||
| SvmwNsxTDataCenterDatapathResourceUsage | 1.3.6.1.4.1.6876.120.1.1.28 | VmwNsxTDataCenterDatapathResourceUsageType | AN | |
scalar · VmwNsxTDataCenterDatapathResourceUsageType · accessible-for-notify · current The CPU, memory, or disk usage percentage of the datapath on a NSX appliance. The value is an integer between 0 and 100. | ||||
| SvmwNsxTDataCenterDHCPPoolUsage | 1.3.6.1.4.1.6876.120.1.1.29 | VmwNsxTDataCenterDHCPPoolUsageType | AN | |
scalar · VmwNsxTDataCenterDHCPPoolUsageType · accessible-for-notify · current The usage of a DHCP pool. The value is an integer between 0 and 100. | ||||
| SvmwNsxTDataCenterEdgeServiceName | 1.3.6.1.4.1.6876.120.1.1.30 | VmwNsxTDataCenterEdgeServiceNameType | AN | |
scalar · VmwNsxTDataCenterEdgeServiceNameType · accessible-for-notify · current The name of the service running on the Edge node. | ||||
| SvmwNsxTDataCenterFailureReason | 1.3.6.1.4.1.6876.120.1.1.31 | VmwNsxTDataCenterFailureReasonType | AN | |
scalar · VmwNsxTDataCenterFailureReasonType · accessible-for-notify · current The detailed reason of any module failure like BGP down, IKE down, etc. | ||||
| SvmwNsxTDataCenterPreviousGatewayState | 1.3.6.1.4.1.6876.120.1.1.32 | VmwNsxTDataCenterPreviousGatewayStateType | AN | |
scalar · VmwNsxTDataCenterPreviousGatewayStateType · accessible-for-notify · current The previous gateway state. The value could be 0, 1 or 2 where 0 is down, 1 is standby and 2 is active | ||||
| SvmwNsxTDataCenterPreviousServiceState | 1.3.6.1.4.1.6876.120.1.1.33 | VmwNsxTDataCenterPreviousServiceStateType | AN | |
scalar · VmwNsxTDataCenterPreviousServiceStateType · accessible-for-notify · current The previous service state. The value could be start/stop/restart/crashed. | ||||
| SvmwNsxTDataCenterSystemUsageThreshold | 1.3.6.1.4.1.6876.120.1.1.34 | VmwNsxTDataCenterSystemUsageThresholdType | AN | |
scalar · VmwNsxTDataCenterSystemUsageThresholdType · accessible-for-notify · current The configured threshold value for the CPU, memory, or disk usage percentage of an NSX appliance. The value is an integer between 0 and 100. | ||||
| SvmwNsxTDataCenterUsername | 1.3.6.1.4.1.6876.120.1.1.35 | VmwNsxTDataCenterUsernameType | AN | |
scalar · VmwNsxTDataCenterUsernameType · accessible-for-notify · current The name of a user in an NSX appliance. | ||||
| SvmwNsxTDataCenterDHCPServerId | 1.3.6.1.4.1.6876.120.1.1.36 | VmwNsxTDataCenterDHCPServerIdType | AN | |
scalar · VmwNsxTDataCenterDHCPServerIdType · accessible-for-notify · current The UUID of a DHCP server. | ||||
| SvmwNsxTDataCenterServiceName | 1.3.6.1.4.1.6876.120.1.1.37 | VmwNsxTDataCenterServiceNameType | AN | |
scalar · VmwNsxTDataCenterServiceNameType · accessible-for-notify · current The name of the service running in an NSX appliance. | ||||
| SvmwNsxTDataCenterIntelligenceNodeId | 1.3.6.1.4.1.6876.120.1.1.38 | VmwNsxTDataCenterIntelligenceNodeIdType | AN | |
scalar · VmwNsxTDataCenterIntelligenceNodeIdType · accessible-for-notify · current The node ID of an NSX Intelligence node. | ||||
| SvmwNsxTDataCenterHostnameOrIPAddressWithPort | 1.3.6.1.4.1.6876.120.1.1.39 | VmwNsxTDataCenterHostnameOrIPAddressWithPortType | AN | |
scalar · VmwNsxTDataCenterHostnameOrIPAddressWithPortType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEventId | 1.3.6.1.4.1.6876.120.1.1.40 | VmwNsxTDataCenterEventIdType | AN | |
scalar · VmwNsxTDataCenterEventIdType · accessible-for-notify · current The event identifier. | ||||
| SvmwNsxTDataCenterActiveGlobalManager | 1.3.6.1.4.1.6876.120.1.1.41 | VmwNsxTDataCenterActiveGlobalManagerType | AN | |
scalar · VmwNsxTDataCenterActiveGlobalManagerType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterActiveGlobalManagers | 1.3.6.1.4.1.6876.120.1.1.42 | VmwNsxTDataCenterActiveGlobalManagersType | AN | |
scalar · VmwNsxTDataCenterActiveGlobalManagersType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSessionDownReason | 1.3.6.1.4.1.6876.120.1.1.43 | VmwNsxTDataCenterSessionDownReasonType | AN | |
scalar · VmwNsxTDataCenterSessionDownReasonType · accessible-for-notify · current Down reason of the IPsec VPN session. | ||||
| SvmwNsxTDataCenterManagerNodeName | 1.3.6.1.4.1.6876.120.1.1.44 | VmwNsxTDataCenterManagerNodeNameType | AN | |
scalar · VmwNsxTDataCenterManagerNodeNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTransportNodeAddress | 1.3.6.1.4.1.6876.120.1.1.45 | VmwNsxTDataCenterTransportNodeAddressType | AN | |
scalar · VmwNsxTDataCenterTransportNodeAddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTransportNodeName | 1.3.6.1.4.1.6876.120.1.1.46 | VmwNsxTDataCenterTransportNodeNameType | AN | |
scalar · VmwNsxTDataCenterTransportNodeNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCentralControlPlaneId | 1.3.6.1.4.1.6876.120.1.1.47 | VmwNsxTDataCenterCentralControlPlaneIdType | AN | |
scalar · VmwNsxTDataCenterCentralControlPlaneIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTunnelDownReason | 1.3.6.1.4.1.6876.120.1.1.48 | VmwNsxTDataCenterTunnelDownReasonType | AN | |
scalar · VmwNsxTDataCenterTunnelDownReasonType · accessible-for-notify · current Down reason of the IPsec VPN tunnel. | ||||
| SvmwNsxTDataCenterHeapType | 1.3.6.1.4.1.6876.120.1.1.49 | VmwNsxTDataCenterHeapTypeType | AN | |
scalar · VmwNsxTDataCenterHeapTypeType · accessible-for-notify · current Heap type information for DFW memory usage like vsip-attr, vsip-flow, vsip-fqdni, etc. | ||||
| SvmwNsxTDataCenterMempoolName | 1.3.6.1.4.1.6876.120.1.1.50 | VmwNsxTDataCenterMempoolNameType | AN | |
scalar · VmwNsxTDataCenterMempoolNameType · accessible-for-notify · current Name of a memory pool. | ||||
| SvmwNsxTDataCenterPasswordExpirationDays | 1.3.6.1.4.1.6876.120.1.1.51 | VmwNsxTDataCenterPasswordExpirationDaysType | AN | |
scalar · VmwNsxTDataCenterPasswordExpirationDaysType · accessible-for-notify · current The number of days left before expiration of the password of an NSX appliance user. The value is an integer greater than 0. | ||||
| SvmwNsxTDataCenterBGPNeighborIP | 1.3.6.1.4.1.6876.120.1.1.52 | VmwNsxTDataCenterBGPNeighborIPType | AN | |
scalar · VmwNsxTDataCenterBGPNeighborIPType · accessible-for-notify · current IP address of BGP Neighbor. This could be either IPv4 or IPv6 address. | ||||
| SvmwNsxTDataCenterLDAPServer | 1.3.6.1.4.1.6876.120.1.1.53 | VmwNsxTDataCenterLDAPServerType | AN | |
scalar · VmwNsxTDataCenterLDAPServerType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterPeerAddress | 1.3.6.1.4.1.6876.120.1.1.54 | VmwNsxTDataCenterPeerAddressType | AN | |
scalar · VmwNsxTDataCenterPeerAddressType · accessible-for-notify · current IP address of BFD peer. | ||||
| SvmwNsxTDataCenterMaxIDSEventsAllowed | 1.3.6.1.4.1.6876.120.1.1.55 | VmwNsxTDataCenterMaxIDSEventsAllowedType | AN | |
scalar · VmwNsxTDataCenterMaxIDSEventsAllowedType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterStaticAddress | 1.3.6.1.4.1.6876.120.1.1.56 | VmwNsxTDataCenterStaticAddressType | AN | |
scalar · VmwNsxTDataCenterStaticAddressType · accessible-for-notify · current A Static IP address. | ||||
| SvmwNsxTDataCenterDuplicateIPAddress | 1.3.6.1.4.1.6876.120.1.1.57 | VmwNsxTDataCenterDuplicateIPAddressType | AN | |
scalar · VmwNsxTDataCenterDuplicateIPAddressType · accessible-for-notify · current Duplicate IP address. | ||||
| SvmwNsxTDataCenterCapacityDisplayName | 1.3.6.1.4.1.6876.120.1.1.58 | VmwNsxTDataCenterCapacityDisplayNameType | AN | |
scalar · VmwNsxTDataCenterCapacityDisplayNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCapacityUsageCount | 1.3.6.1.4.1.6876.120.1.1.59 | VmwNsxTDataCenterCapacityUsageCountType | AN | |
scalar · VmwNsxTDataCenterCapacityUsageCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeNICName | 1.3.6.1.4.1.6876.120.1.1.60 | VmwNsxTDataCenterEdgeNICNameType | AN | |
scalar · VmwNsxTDataCenterEdgeNICNameType · accessible-for-notify · current The name of the NIC whose link is down or which faced tx/rx ring buffer overflow. | ||||
| SvmwNsxTDataCenterRxRingBufferOverflowPercentage | 1.3.6.1.4.1.6876.120.1.1.61 | VmwNsxTDataCenterRxRingBufferOverflowPercentageType | AN | |
scalar · VmwNsxTDataCenterRxRingBufferOverflowPercentageType · accessible-for-notify · current The NIC's receive descriptor ring buffer on a NSX Edge or Gateway node has no space left to accomodate new incoming packets and there is a significant drop due to it. The value is a float between 0 to 100 describing the overflow percentage due to the packet drops. | ||||
| SvmwNsxTDataCenterTxRingBufferOverflowPercentage | 1.3.6.1.4.1.6876.120.1.1.62 | VmwNsxTDataCenterTxRingBufferOverflowPercentageType | AN | |
scalar · VmwNsxTDataCenterTxRingBufferOverflowPercentageType · accessible-for-notify · current The NIC's transmit descriptor ring buffer on a NSX Edge or Gateway node has no space left to accomodate new outgoing packets and there is a significant drop due to it. The value is a float between 0 to 100 describing the overflow percentage due to the packet drops. | ||||
| SvmwNsxTDataCenterSrId | 1.3.6.1.4.1.6876.120.1.1.63 | VmwNsxTDataCenterSrIdType | AN | |
scalar · VmwNsxTDataCenterSrIdType · accessible-for-notify · current Service Router UUID. | ||||
| SvmwNsxTDataCenterIDSEventsCount | 1.3.6.1.4.1.6876.120.1.1.64 | VmwNsxTDataCenterIDSEventsCountType | AN | |
scalar · VmwNsxTDataCenterIDSEventsCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRemoteSiteName | 1.3.6.1.4.1.6876.120.1.1.65 | VmwNsxTDataCenterRemoteSiteNameType | AN | |
scalar · VmwNsxTDataCenterRemoteSiteNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterBGPSourceIP | 1.3.6.1.4.1.6876.120.1.1.66 | VmwNsxTDataCenterBGPSourceIPType | AN | |
scalar · VmwNsxTDataCenterBGPSourceIPType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRemoteSiteId | 1.3.6.1.4.1.6876.120.1.1.67 | VmwNsxTDataCenterRemoteSiteIdType | AN | |
scalar · VmwNsxTDataCenterRemoteSiteIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSiteId | 1.3.6.1.4.1.6876.120.1.1.68 | VmwNsxTDataCenterSiteIdType | AN | |
scalar · VmwNsxTDataCenterSiteIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSiteName | 1.3.6.1.4.1.6876.120.1.1.69 | VmwNsxTDataCenterSiteNameType | AN | |
scalar · VmwNsxTDataCenterSiteNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLrId | 1.3.6.1.4.1.6876.120.1.1.70 | VmwNsxTDataCenterLrIdType | AN | |
scalar · VmwNsxTDataCenterLrIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRxMisses | 1.3.6.1.4.1.6876.120.1.1.71 | VmwNsxTDataCenterRxMissesType | AN | |
scalar · VmwNsxTDataCenterRxMissesType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRxProcessed | 1.3.6.1.4.1.6876.120.1.1.72 | VmwNsxTDataCenterRxProcessedType | AN | |
scalar · VmwNsxTDataCenterRxProcessedType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTxMisses | 1.3.6.1.4.1.6876.120.1.1.73 | VmwNsxTDataCenterTxMissesType | AN | |
scalar · VmwNsxTDataCenterTxMissesType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTxProcessed | 1.3.6.1.4.1.6876.120.1.1.74 | VmwNsxTDataCenterTxProcessedType | AN | |
scalar · VmwNsxTDataCenterTxProcessedType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLrportId | 1.3.6.1.4.1.6876.120.1.1.75 | VmwNsxTDataCenterLrportIdType | AN | |
scalar · VmwNsxTDataCenterLrportIdType · accessible-for-notify · current Logical Router Port UUID. | ||||
| SvmwNsxTDataCenterServiceIP | 1.3.6.1.4.1.6876.120.1.1.77 | VmwNsxTDataCenterServiceIPType | AN | |
scalar · VmwNsxTDataCenterServiceIPType · accessible-for-notify · current The Ip configured for the service running in an NSX appliance. | ||||
| SvmwNsxTDataCenterRemoteManagerNodeId | 1.3.6.1.4.1.6876.120.1.1.80 | VmwNsxTDataCenterRemoteManagerNodeIdType | AN | |
scalar · VmwNsxTDataCenterRemoteManagerNodeIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterDirectoryDomain | 1.3.6.1.4.1.6876.120.1.1.81 | VmwNsxTDataCenterDirectoryDomainType | AN | |
scalar · VmwNsxTDataCenterDirectoryDomainType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTimeoutInMinutes | 1.3.6.1.4.1.6876.120.1.1.82 | VmwNsxTDataCenterTimeoutInMinutesType | AN | |
scalar · VmwNsxTDataCenterTimeoutInMinutesType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMaxCapacityThreshold | 1.3.6.1.4.1.6876.120.1.1.83 | VmwNsxTDataCenterMaxCapacityThresholdType | AN | |
scalar · VmwNsxTDataCenterMaxCapacityThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMinCapacityThreshold | 1.3.6.1.4.1.6876.120.1.1.84 | VmwNsxTDataCenterMinCapacityThresholdType | AN | |
scalar · VmwNsxTDataCenterMinCapacityThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMaxSupportedCapacityCount | 1.3.6.1.4.1.6876.120.1.1.85 | VmwNsxTDataCenterMaxSupportedCapacityCountType | AN | |
scalar · VmwNsxTDataCenterMaxSupportedCapacityCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLatencySource | 1.3.6.1.4.1.6876.120.1.1.86 | VmwNsxTDataCenterLatencySourceType | AN | |
scalar · VmwNsxTDataCenterLatencySourceType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLatencyThreshold | 1.3.6.1.4.1.6876.120.1.1.87 | VmwNsxTDataCenterLatencyThresholdType | AN | |
scalar · VmwNsxTDataCenterLatencyThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLatencyValue | 1.3.6.1.4.1.6876.120.1.1.88 | VmwNsxTDataCenterLatencyValueType | AN | |
scalar · VmwNsxTDataCenterLatencyValueType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterApplianceFQDN | 1.3.6.1.4.1.6876.120.1.1.89 | VmwNsxTDataCenterApplianceFQDNType | AN | |
scalar · VmwNsxTDataCenterApplianceFQDNType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRemoteApplianceAddress | 1.3.6.1.4.1.6876.120.1.1.90 | VmwNsxTDataCenterRemoteApplianceAddressType | AN | |
scalar · VmwNsxTDataCenterRemoteApplianceAddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterManagerNodeId | 1.3.6.1.4.1.6876.120.1.1.91 | VmwNsxTDataCenterManagerNodeIdType | AN | |
scalar · VmwNsxTDataCenterManagerNodeIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterDisplayedLicenseKey | 1.3.6.1.4.1.6876.120.1.1.92 | VmwNsxTDataCenterDisplayedLicenseKeyType | AN | |
scalar · VmwNsxTDataCenterDisplayedLicenseKeyType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeThreadName | 1.3.6.1.4.1.6876.120.1.1.93 | VmwNsxTDataCenterEdgeThreadNameType | AN | |
scalar · VmwNsxTDataCenterEdgeThreadNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterIntentPath | 1.3.6.1.4.1.6876.120.1.1.94 | VmwNsxTDataCenterIntentPathType | AN | |
scalar · VmwNsxTDataCenterIntentPathType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFirewallHalfopenFlowUsage | 1.3.6.1.4.1.6876.120.1.1.95 | VmwNsxTDataCenterFirewallHalfopenFlowUsageType | AN | |
scalar · VmwNsxTDataCenterFirewallHalfopenFlowUsageType · accessible-for-notify · current Firewall TCP half-open connection usage. | ||||
| SvmwNsxTDataCenterFirewallICMPFlowUsage | 1.3.6.1.4.1.6876.120.1.1.96 | VmwNsxTDataCenterFirewallICMPFlowUsageType | AN | |
scalar · VmwNsxTDataCenterFirewallICMPFlowUsageType · accessible-for-notify · current Firewall ICMP connection usage. | ||||
| SvmwNsxTDataCenterServiceDownReason | 1.3.6.1.4.1.6876.120.1.1.97 | VmwNsxTDataCenterServiceDownReasonType | AN | |
scalar · VmwNsxTDataCenterServiceDownReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFirewallUDPFlowUsage | 1.3.6.1.4.1.6876.120.1.1.98 | VmwNsxTDataCenterFirewallUDPFlowUsageType | AN | |
scalar · VmwNsxTDataCenterFirewallUDPFlowUsageType · accessible-for-notify · current Firewall UDP connection usage. | ||||
| SvmwNsxTDataCenterFirewallIPFlowUsage | 1.3.6.1.4.1.6876.120.1.1.99 | VmwNsxTDataCenterFirewallIPFlowUsageType | AN | |
scalar · VmwNsxTDataCenterFirewallIPFlowUsageType · accessible-for-notify · current Firewall IP connection usage. | ||||
| SvmwNsxTDataCenterDNSId | 1.3.6.1.4.1.6876.120.1.1.100 | VmwNsxTDataCenterDNSIdType | AN | |
scalar · VmwNsxTDataCenterDNSIdType · accessible-for-notify · current DNS forwarder identifier. | ||||
| SvmwNsxTDataCenterDNSUpstreamIP | 1.3.6.1.4.1.6876.120.1.1.101 | VmwNsxTDataCenterDNSUpstreamIPType | AN | |
scalar · VmwNsxTDataCenterDNSUpstreamIPType · accessible-for-notify · current DNS forwarder upstream server IP address. | ||||
| SvmwNsxTDataCenterCABundleAgeThreshold | 1.3.6.1.4.1.6876.120.1.1.121 | VmwNsxTDataCenterCABundleAgeThresholdType | AN | |
scalar · VmwNsxTDataCenterCABundleAgeThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterAPICollectionPath | 1.3.6.1.4.1.6876.120.1.1.122 | VmwNsxTDataCenterAPICollectionPathType | AN | |
scalar · VmwNsxTDataCenterAPICollectionPathType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeNodeSettingMismatchReason | 1.3.6.1.4.1.6876.120.1.1.123 | VmwNsxTDataCenterEdgeNodeSettingMismatchReasonType | AN | |
scalar · VmwNsxTDataCenterEdgeNodeSettingMismatchReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReason | 1.3.6.1.4.1.6876.120.1.1.124 | VmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReasonType | AN | |
scalar · VmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFirewallSNATPortsUsage | 1.3.6.1.4.1.6876.120.1.1.125 | VmwNsxTDataCenterFirewallSNATPortsUsageType | AN | |
scalar · VmwNsxTDataCenterFirewallSNATPortsUsageType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgevSphereLocationMismatchReason | 1.3.6.1.4.1.6876.120.1.1.126 | VmwNsxTDataCenterEdgevSphereLocationMismatchReasonType | AN | |
scalar · VmwNsxTDataCenterEdgevSphereLocationMismatchReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReason | 1.3.6.1.4.1.6876.120.1.1.127 | VmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReasonType | AN | |
scalar · VmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSNATIPAddress | 1.3.6.1.4.1.6876.120.1.1.128 | VmwNsxTDataCenterSNATIPAddressType | AN | |
scalar · VmwNsxTDataCenterSNATIPAddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNappClusterId | 1.3.6.1.4.1.6876.120.1.1.129 | VmwNsxTDataCenterNappClusterIdType | AN | |
scalar · VmwNsxTDataCenterNappClusterIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNappMessagingLAGThreshold | 1.3.6.1.4.1.6876.120.1.1.130 | VmwNsxTDataCenterNappMessagingLAGThresholdType | AN | |
scalar · VmwNsxTDataCenterNappMessagingLAGThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNappNodeId | 1.3.6.1.4.1.6876.120.1.1.131 | VmwNsxTDataCenterNappNodeIdType | AN | |
scalar · VmwNsxTDataCenterNappNodeIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNappServiceName | 1.3.6.1.4.1.6876.120.1.1.132 | VmwNsxTDataCenterNappServiceNameType | AN | |
scalar · VmwNsxTDataCenterNappServiceNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFlowIdentifier | 1.3.6.1.4.1.6876.120.1.1.133 | VmwNsxTDataCenterFlowIdentifierType | AN | |
scalar · VmwNsxTDataCenterFlowIdentifierType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSyncIssueReason | 1.3.6.1.4.1.6876.120.1.1.134 | VmwNsxTDataCenterSyncIssueReasonType | AN | |
scalar · VmwNsxTDataCenterSyncIssueReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterQueueName | 1.3.6.1.4.1.6876.120.1.1.135 | VmwNsxTDataCenterQueueNameType | AN | |
scalar · VmwNsxTDataCenterQueueNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterQueueSize | 1.3.6.1.4.1.6876.120.1.1.136 | VmwNsxTDataCenterQueueSizeType | AN | |
scalar · VmwNsxTDataCenterQueueSizeType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterQueueSizeThreshold | 1.3.6.1.4.1.6876.120.1.1.137 | VmwNsxTDataCenterQueueSizeThresholdType | AN | |
scalar · VmwNsxTDataCenterQueueSizeThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterGroupType | 1.3.6.1.4.1.6876.120.1.1.138 | VmwNsxTDataCenterGroupTypeType | AN | |
scalar · VmwNsxTDataCenterGroupTypeType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterManagerNodeIDS | 1.3.6.1.4.1.6876.120.1.1.139 | VmwNsxTDataCenterManagerNodeIDSType | AN | |
scalar · VmwNsxTDataCenterManagerNodeIDSType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterServiceRouterId | 1.3.6.1.4.1.6876.120.1.1.140 | VmwNsxTDataCenterServiceRouterIdType | AN | |
scalar · VmwNsxTDataCenterServiceRouterIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTransportNodeId | 1.3.6.1.4.1.6876.120.1.1.141 | VmwNsxTDataCenterTransportNodeIdType | AN | |
scalar · VmwNsxTDataCenterTransportNodeIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFromGMPath | 1.3.6.1.4.1.6876.120.1.1.142 | VmwNsxTDataCenterFromGMPathType | AN | |
scalar · VmwNsxTDataCenterFromGMPathType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterToGMPath | 1.3.6.1.4.1.6876.120.1.1.143 | VmwNsxTDataCenterToGMPathType | AN | |
scalar · VmwNsxTDataCenterToGMPathType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNICThroughput | 1.3.6.1.4.1.6876.120.1.1.144 | VmwNsxTDataCenterNICThroughputType | AN | |
scalar · VmwNsxTDataCenterNICThroughputType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNICThroughputThreshold | 1.3.6.1.4.1.6876.120.1.1.145 | VmwNsxTDataCenterNICThroughputThresholdType | AN | |
scalar · VmwNsxTDataCenterNICThroughputThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeCryptoDrvName | 1.3.6.1.4.1.6876.120.1.1.146 | VmwNsxTDataCenterEdgeCryptoDrvNameType | AN | |
scalar · VmwNsxTDataCenterEdgeCryptoDrvNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNappNodeName | 1.3.6.1.4.1.6876.120.1.1.147 | VmwNsxTDataCenterNappNodeNameType | AN | |
scalar · VmwNsxTDataCenterNappNodeNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNewVMMorefId | 1.3.6.1.4.1.6876.120.1.1.148 | VmwNsxTDataCenterNewVMMorefIdType | AN | |
scalar · VmwNsxTDataCenterNewVMMorefIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterPolicyEdgeVMName | 1.3.6.1.4.1.6876.120.1.1.149 | VmwNsxTDataCenterPolicyEdgeVMNameType | AN | |
scalar · VmwNsxTDataCenterPolicyEdgeVMNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVMMorefId | 1.3.6.1.4.1.6876.120.1.1.150 | VmwNsxTDataCenterVMMorefIdType | AN | |
scalar · VmwNsxTDataCenterVMMorefIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterDPUId | 1.3.6.1.4.1.6876.120.1.1.171 | VmwNsxTDataCenterDPUIdType | AN | |
scalar · VmwNsxTDataCenterDPUIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeNode | 1.3.6.1.4.1.6876.120.1.1.172 | VmwNsxTDataCenterEdgeNodeType | AN | |
scalar · VmwNsxTDataCenterEdgeNodeType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterPrefixesCountMax | 1.3.6.1.4.1.6876.120.1.1.173 | VmwNsxTDataCenterPrefixesCountMaxType | AN | |
scalar · VmwNsxTDataCenterPrefixesCountMaxType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterPrefixesCountThreshold | 1.3.6.1.4.1.6876.120.1.1.174 | VmwNsxTDataCenterPrefixesCountThresholdType | AN | |
scalar · VmwNsxTDataCenterPrefixesCountThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRouteLimitMaximum | 1.3.6.1.4.1.6876.120.1.1.175 | VmwNsxTDataCenterRouteLimitMaximumType | AN | |
scalar · VmwNsxTDataCenterRouteLimitMaximumType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterRouteLimitThreshold | 1.3.6.1.4.1.6876.120.1.1.176 | VmwNsxTDataCenterRouteLimitThresholdType | AN | |
scalar · VmwNsxTDataCenterRouteLimitThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSubsequentAddressFamily | 1.3.6.1.4.1.6876.120.1.1.177 | VmwNsxTDataCenterSubsequentAddressFamilyType | AN | |
scalar · VmwNsxTDataCenterSubsequentAddressFamilyType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCentervCenterClusterId | 1.3.6.1.4.1.6876.120.1.1.179 | VmwNsxTDataCentervCenterClusterIdType | AN | |
scalar · VmwNsxTDataCentervCenterClusterIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMpsServiceName | 1.3.6.1.4.1.6876.120.1.1.180 | VmwNsxTDataCenterMpsServiceNameType | AN | |
scalar · VmwNsxTDataCenterMpsServiceNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMemberIndexId | 1.3.6.1.4.1.6876.120.1.1.182 | VmwNsxTDataCenterMemberIndexIdType | AN | |
scalar · VmwNsxTDataCenterMemberIndexIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeClusterId | 1.3.6.1.4.1.6876.120.1.1.184 | VmwNsxTDataCenterEdgeClusterIdType | AN | |
scalar · VmwNsxTDataCenterEdgeClusterIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCoreDumpCount | 1.3.6.1.4.1.6876.120.1.1.185 | VmwNsxTDataCenterCoreDumpCountType | AN | |
scalar · VmwNsxTDataCenterCoreDumpCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNodeDisplayOrHostName | 1.3.6.1.4.1.6876.120.1.1.186 | VmwNsxTDataCenterNodeDisplayOrHostNameType | AN | |
scalar · VmwNsxTDataCenterNodeDisplayOrHostNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNSXEdgeTNName | 1.3.6.1.4.1.6876.120.1.1.187 | VmwNsxTDataCenterNSXEdgeTNNameType | AN | |
scalar · VmwNsxTDataCenterNSXEdgeTNNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNSXESXTNName | 1.3.6.1.4.1.6876.120.1.1.188 | VmwNsxTDataCenterNSXESXTNNameType | AN | |
scalar · VmwNsxTDataCenterNSXESXTNNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCollectorIP | 1.3.6.1.4.1.6876.120.1.1.189 | VmwNsxTDataCenterCollectorIPType | AN | |
scalar · VmwNsxTDataCenterCollectorIPType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterDvsAlias | 1.3.6.1.4.1.6876.120.1.1.190 | VmwNsxTDataCenterDvsAliasType | AN | |
scalar · VmwNsxTDataCenterDvsAliasType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterStackAlias | 1.3.6.1.4.1.6876.120.1.1.191 | VmwNsxTDataCenterStackAliasType | AN | |
scalar · VmwNsxTDataCenterStackAliasType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVerticalName | 1.3.6.1.4.1.6876.120.1.1.192 | VmwNsxTDataCenterVerticalNameType | AN | |
scalar · VmwNsxTDataCenterVerticalNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeClusterHighestHwVersion | 1.3.6.1.4.1.6876.120.1.1.195 | VmwNsxTDataCenterEdgeClusterHighestHwVersionType | AN | |
scalar · VmwNsxTDataCenterEdgeClusterHighestHwVersionType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeTNHwVersion | 1.3.6.1.4.1.6876.120.1.1.196 | VmwNsxTDataCenterEdgeTNHwVersionType | AN | |
scalar · VmwNsxTDataCenterEdgeTNHwVersionType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterEdgeClusterName | 1.3.6.1.4.1.6876.120.1.1.197 | VmwNsxTDataCenterEdgeClusterNameType | AN | |
scalar · VmwNsxTDataCenterEdgeClusterNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterHaState | 1.3.6.1.4.1.6876.120.1.1.220 | VmwNsxTDataCenterHaStateType | AN | |
scalar · VmwNsxTDataCenterHaStateType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterHaState2 | 1.3.6.1.4.1.6876.120.1.1.221 | VmwNsxTDataCenterHaState2Type | AN | |
scalar · VmwNsxTDataCenterHaState2Type · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTransportNodeId2 | 1.3.6.1.4.1.6876.120.1.1.222 | VmwNsxTDataCenterTransportNodeId2Type | AN | |
scalar · VmwNsxTDataCenterTransportNodeId2Type · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterDvsName | 1.3.6.1.4.1.6876.120.1.1.223 | VmwNsxTDataCenterDvsNameType | AN | |
scalar · VmwNsxTDataCenterDvsNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVtepFaultReason | 1.3.6.1.4.1.6876.120.1.1.224 | VmwNsxTDataCenterVtepFaultReasonType | AN | |
scalar · VmwNsxTDataCenterVtepFaultReasonType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVtepName | 1.3.6.1.4.1.6876.120.1.1.225 | VmwNsxTDataCenterVtepNameType | AN | |
scalar · VmwNsxTDataCenterVtepNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMetricsTargetAddress | 1.3.6.1.4.1.6876.120.1.1.226 | VmwNsxTDataCenterMetricsTargetAddressType | AN | |
scalar · VmwNsxTDataCenterMetricsTargetAddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMetricsTargetAlias | 1.3.6.1.4.1.6876.120.1.1.227 | VmwNsxTDataCenterMetricsTargetAliasType | AN | |
scalar · VmwNsxTDataCenterMetricsTargetAliasType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMetricsTargetPort | 1.3.6.1.4.1.6876.120.1.1.228 | VmwNsxTDataCenterMetricsTargetPortType | AN | |
scalar · VmwNsxTDataCenterMetricsTargetPortType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterIPv4Address | 1.3.6.1.4.1.6876.120.1.1.229 | VmwNsxTDataCenterIPv4AddressType | AN | |
scalar · VmwNsxTDataCenterIPv4AddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterIPv6Address | 1.3.6.1.4.1.6876.120.1.1.230 | VmwNsxTDataCenterIPv6AddressType | AN | |
scalar · VmwNsxTDataCenterIPv6AddressType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterConstraintLimit | 1.3.6.1.4.1.6876.120.1.1.231 | VmwNsxTDataCenterConstraintLimitType | AN | |
scalar · VmwNsxTDataCenterConstraintLimitType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterConstraintType | 1.3.6.1.4.1.6876.120.1.1.232 | VmwNsxTDataCenterConstraintTypeType | AN | |
scalar · VmwNsxTDataCenterConstraintTypeType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCurrentCount | 1.3.6.1.4.1.6876.120.1.1.233 | VmwNsxTDataCenterCurrentCountType | AN | |
scalar · VmwNsxTDataCenterCurrentCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterGroupId | 1.3.6.1.4.1.6876.120.1.1.234 | VmwNsxTDataCenterGroupIdType | AN | |
scalar · VmwNsxTDataCenterGroupIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterGroupMaxNumberLimit | 1.3.6.1.4.1.6876.120.1.1.235 | VmwNsxTDataCenterGroupMaxNumberLimitType | AN | |
scalar · VmwNsxTDataCenterGroupMaxNumberLimitType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterGroupSize | 1.3.6.1.4.1.6876.120.1.1.236 | VmwNsxTDataCenterGroupSizeType | AN | |
scalar · VmwNsxTDataCenterGroupSizeType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterIPCount | 1.3.6.1.4.1.6876.120.1.1.237 | VmwNsxTDataCenterIPCountType | AN | |
scalar · VmwNsxTDataCenterIPCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLrpCount | 1.3.6.1.4.1.6876.120.1.1.238 | VmwNsxTDataCenterLrpCountType | AN | |
scalar · VmwNsxTDataCenterLrpCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterLspCount | 1.3.6.1.4.1.6876.120.1.1.239 | VmwNsxTDataCenterLspCountType | AN | |
scalar · VmwNsxTDataCenterLspCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterMacCount | 1.3.6.1.4.1.6876.120.1.1.240 | VmwNsxTDataCenterMacCountType | AN | |
scalar · VmwNsxTDataCenterMacCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterSidCount | 1.3.6.1.4.1.6876.120.1.1.241 | VmwNsxTDataCenterSidCountType | AN | |
scalar · VmwNsxTDataCenterSidCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterTNCount | 1.3.6.1.4.1.6876.120.1.1.244 | VmwNsxTDataCenterTNCountType | AN | |
scalar · VmwNsxTDataCenterTNCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVifCount | 1.3.6.1.4.1.6876.120.1.1.245 | VmwNsxTDataCenterVifCountType | AN | |
scalar · VmwNsxTDataCenterVifCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterVMCount | 1.3.6.1.4.1.6876.120.1.1.246 | VmwNsxTDataCenterVMCountType | AN | |
scalar · VmwNsxTDataCenterVMCountType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterCoreId | 1.3.6.1.4.1.6876.120.1.1.247 | VmwNsxTDataCenterCoreIdType | AN | |
scalar · VmwNsxTDataCenterCoreIdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterFlowCacheThreshold | 1.3.6.1.4.1.6876.120.1.1.248 | VmwNsxTDataCenterFlowCacheThresholdType | AN | |
scalar · VmwNsxTDataCenterFlowCacheThresholdType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterNSXaaSServiceName | 1.3.6.1.4.1.6876.120.1.1.249 | VmwNsxTDataCenterNSXaaSServiceNameType | AN | |
scalar · VmwNsxTDataCenterNSXaaSServiceNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterProtocolName | 1.3.6.1.4.1.6876.120.1.1.250 | VmwNsxTDataCenterProtocolNameType | AN | |
scalar · VmwNsxTDataCenterProtocolNameType · accessible-for-notify · current This value is not expected to be empty. | ||||
| SvmwNsxTDataCenterConstraintTypePath | 1.3.6.1.4.1.6876.120.1.1.251 | VmwNsxTDataCenterConstraintTypePathType | AN | |
scalar · VmwNsxTDataCenterConstraintTypePathType · accessible-for-notify · current This value is not expected to be empty. | ||||
| NvmwNsxTDataCenterConformance | 1.3.6.1.4.1.6876.120.1.2 | |||
| NvmwNsxTDataCenterCompliances | 1.3.6.1.4.1.6876.120.1.2.1 | |||
| MvmwNsxTDataCenterBasicCompliance | 1.3.6.1.4.1.6876.120.1.2.1.1 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB. | ||||
| MvmwNsxTDataCenterBasicCompliance2 | 1.3.6.1.4.1.6876.120.1.2.1.2 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB. | ||||
| MvmwNsxTDataCenterBasicCompliance3 | 1.3.6.1.4.1.6876.120.1.2.1.3 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB. | ||||
| MvmwNsxTDataCenterBasicCompliance4 | 1.3.6.1.4.1.6876.120.1.2.1.4 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance5 | 1.3.6.1.4.1.6876.120.1.2.1.5 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance6 | 1.3.6.1.4.1.6876.120.1.2.1.6 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance7 | 1.3.6.1.4.1.6876.120.1.2.1.7 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance8 | 1.3.6.1.4.1.6876.120.1.2.1.8 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance9 | 1.3.6.1.4.1.6876.120.1.2.1.9 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance10 | 1.3.6.1.4.1.6876.120.1.2.1.10 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance11 | 1.3.6.1.4.1.6876.120.1.2.1.11 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance12 | 1.3.6.1.4.1.6876.120.1.2.1.12 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance13 | 1.3.6.1.4.1.6876.120.1.2.1.13 | deprecated | ||
compliance · deprecated The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| MvmwNsxTDataCenterBasicCompliance14 | 1.3.6.1.4.1.6876.120.1.2.1.14 | |||
compliance · current The compliance statement for entities which implement VMWARE-NSX-MIB.
| ||||
| NvmwNsxTDataCenterSMIBGroups | 1.3.6.1.4.1.6876.120.1.2.2 | |||
| GvmwNsxTDataCenterNotificationInfoGroup | 1.3.6.1.4.1.6876.120.1.2.2.1 | |||
group · current These objects provide details in NSX Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup | 1.3.6.1.4.1.6876.120.1.2.2.2 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup2 | 1.3.6.1.4.1.6876.120.1.2.2.3 | |||
group · current These objects provide details in NSX Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup2 | 1.3.6.1.4.1.6876.120.1.2.2.4 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup3 | 1.3.6.1.4.1.6876.120.1.2.2.5 | |||
group · current These objects provide details in NSX Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup3 | 1.3.6.1.4.1.6876.120.1.2.2.6 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup4 | 1.3.6.1.4.1.6876.120.1.2.2.7 | |||
group · current These objects provide details in NSX Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup4 | 1.3.6.1.4.1.6876.120.1.2.2.8 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationGroup5 | 1.3.6.1.4.1.6876.120.1.2.2.10 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center. | ||||
| GvmwNsxTDataCenterNotificationInfoGroup6 | 1.3.6.1.4.1.6876.120.1.2.2.11 | |||
group · current These objects provide details in NSX Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup6 | 1.3.6.1.4.1.6876.120.1.2.2.12 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center. | ||||
| GvmwNsxTDataCenterNotificationInfoGroup7 | 1.3.6.1.4.1.6876.120.1.2.2.13 | |||
group · current These objects provide details in NSX Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup7 | 1.3.6.1.4.1.6876.120.1.2.2.14 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup8 | 1.3.6.1.4.1.6876.120.1.2.2.15 | |||
group · current These objects provide details in NSX Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup8 | 1.3.6.1.4.1.6876.120.1.2.2.16 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup9 | 1.3.6.1.4.1.6876.120.1.2.2.17 | |||
group · current These objects provide details in NSX Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup9 | 1.3.6.1.4.1.6876.120.1.2.2.18 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup10 | 1.3.6.1.4.1.6876.120.1.2.2.19 | |||
group · current These objects provide details in NSX Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup10 | 1.3.6.1.4.1.6876.120.1.2.2.20 | |||
group · current Group of objects describing event notifications emitted by NSX Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup11 | 1.3.6.1.4.1.6876.120.1.2.2.21 | |||
group · current These objects provide details in NSX-T Data Center event notifications. | ||||
| GvmwNsxTDataCenterNotificationGroup11 | 1.3.6.1.4.1.6876.120.1.2.2.22 | |||
group · current Group of objects describing event notifications emitted by NSX-T Data Center. | ||||
| GvmwNsxTDataCenterNotificationInfoGroup12 | 1.3.6.1.4.1.6876.120.1.2.2.23 | |||
group · current These objects provide details in NSX-T Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup12 | 1.3.6.1.4.1.6876.120.1.2.2.24 | |||
group · current Group of objects describing event notifications emitted by NSX-T Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup13 | 1.3.6.1.4.1.6876.120.1.2.2.25 | |||
group · current These objects provide details in NSX-T Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup13 | 1.3.6.1.4.1.6876.120.1.2.2.26 | |||
group · current Group of objects describing event notifications emitted by NSX-T Data Center.
| ||||
| GvmwNsxTDataCenterNotificationInfoGroup14 | 1.3.6.1.4.1.6876.120.1.2.2.27 | |||
group · current These objects provide details in NSX-T Data Center event notifications.
| ||||
| GvmwNsxTDataCenterNotificationGroup14 | 1.3.6.1.4.1.6876.120.1.2.2.28 | |||
group · current Group of objects describing event notifications emitted by NSX-T Data Center.
| ||||
Textual conventions
VmwNsxTDataCenterAPICollectionPathTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe API path of the collection containing entity_id.
VmwNsxTDataCenterActiveGlobalManagerTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe identifier for the active Global Manager node.
VmwNsxTDataCenterActiveGlobalManagersTypeOCTET STRING (SIZE (0..256))Display hint:
256aA comma delimited list of identifiers for the active Global Manager nodes.
VmwNsxTDataCenterApplianceAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NSX appliance's IP address. The value is an IPv4 address.
VmwNsxTDataCenterApplianceFQDNTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NSX appliance's fully qualified domain name.
VmwNsxTDataCenterBGPNeighborIPTypeOCTET STRING (SIZE (0..256))Display hint:
256aIP address of BGP Neighbor. This could be either IPv4 or IPv6 address.
VmwNsxTDataCenterBGPSourceIPTypeOCTET STRING (SIZE (0..256))Display hint:
256aSource IP address of BGP session. This could be either an IPv4 address in dotted-decimal format or an IPv6 address in IPv6 address format.
VmwNsxTDataCenterCABundleAgeThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe age threshold in days for the CA bundle.
VmwNsxTDataCenterCapacityDisplayNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aDisplay name of type on capacity dashboard.
VmwNsxTDataCenterCapacityUsageCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent usage count of capacity usage type.
VmwNsxTDataCenterCentralControlPlaneIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe UUID of a NSX centrol control plane.
VmwNsxTDataCenterCollectorIPTypeOCTET STRING (SIZE (0..256))Display hint:
256aExternal OPS collector IP address for OPS features.
VmwNsxTDataCenterConstraintLimitTypeOCTET STRING (SIZE (0..256))Display hint:
256aValue of constraint limit.
VmwNsxTDataCenterConstraintTypePathTypeOCTET STRING (SIZE (0..256))Display hint:
256aPath prefix of constraint resource.
VmwNsxTDataCenterConstraintTypeTypeOCTET STRING (SIZE (0..256))Display hint:
256aType of constraint resource.
VmwNsxTDataCenterCoreDumpCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of core dump file generated in system.
VmwNsxTDataCenterCoreIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString to identify the core on which event is triggered.
VmwNsxTDataCenterCurrentCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent count of object.
VmwNsxTDataCenterCurrentGatewayStateTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe current gateway state. The value could be 0, 1 or 2 where 0 is down, 1 is standby and 2 is active
VmwNsxTDataCenterCurrentServiceStateTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe current service state. The value could be start/stop/restart/crashed.
VmwNsxTDataCenterDHCPPoolUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe usage of a DHCP pool. The value is an integer between 0 and 100.
VmwNsxTDataCenterDHCPServerIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe UUID of a DHCP server.
VmwNsxTDataCenterDNSIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe DNS forwarder identifier.
VmwNsxTDataCenterDNSUpstreamIPTypeOCTET STRING (SIZE (0..256))Display hint:
256aIP address of one DNS forwarder upstream server.
VmwNsxTDataCenterDPUIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aData processing unit identifier.
VmwNsxTDataCenterDatapathResourceUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe CPU, memory, or disk usage percentage of the datapath on a NSX appliance. The value is an integer between 0 and 100.
VmwNsxTDataCenterDirectoryDomainTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of a directory domain.
VmwNsxTDataCenterDiskPartitionNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of a disk partition in an NSX appliance. For example, the name for the /tmp partition is '/tmp'.
VmwNsxTDataCenterDisplayedLicenseKeyTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe last 5 characters of the license key of an NSX license.
VmwNsxTDataCenterDuplicateIPAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aDuplicate IP address.
VmwNsxTDataCenterDvsAliasTypeOCTET STRING (SIZE (0..256))Display hint:
256aDVS name to indicate given DVS.
VmwNsxTDataCenterDvsNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe ESXi DVS name.
VmwNsxTDataCenterEdgeClusterHighestHwVersionTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing highest hardware version of Edge Transport Node in edge cluster.
VmwNsxTDataCenterEdgeClusterIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing the edge cluster ID.
VmwNsxTDataCenterEdgeClusterNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Edge cluster display name.
VmwNsxTDataCenterEdgeCryptoDrvNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of the edge crypto driver.
VmwNsxTDataCenterEdgeNICNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the NIC whose link is down or which faced tx/rx ring buffer overflow.
VmwNsxTDataCenterEdgeNodeAndvSphereSettingsMismatchReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Policy/MP intent of Edge transport node settings and vSphere deployment configuration that differs from corresponding Edge transport node settings on Edge NSX CLI and Edge transport node configuration on vSphere.
VmwNsxTDataCenterEdgeNodeSettingMismatchReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Policy/MP intent of Edge transport node settings that differs from corresponding Edge transport node settings on Edge NSX CLI.
VmwNsxTDataCenterEdgeNodeTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing the Edge node UUID.
VmwNsxTDataCenterEdgeServiceNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the service running on the Edge node.
VmwNsxTDataCenterEdgeTNHwVersionTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing hardware version of Edge Transport Node.
VmwNsxTDataCenterEdgeThreadNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the Edge node thread.
VmwNsxTDataCenterEdgeVMvSphereSettingsMismatchReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Policy/MP intent of Edge transport node vSphere deployment configuration that differs from corresponding Edge transport node configuration on vSphere.
VmwNsxTDataCenterEdgevSphereLocationMismatchReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Policy/MP intent of vSphere deployment configuration that differs from corresponding Edge transport node configuration on vSphere when vMotion happens for Edge node.
VmwNsxTDataCenterEntityIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe ID of a NSX Data Center entity an event pertains to. The event description field provides additional details of the entity. For example the ID can be for a specific Load Balancer rule as reported by the NSX API GET /api/v1/loadbalancer/rules or a specific certificate as reported by the NSX API GET /api/v1/trust-management/certificates.
VmwNsxTDataCenterEventIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe event identifier.
VmwNsxTDataCenterEventTypeTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the NSX Data Center event. The complete set of events are reported by the NSX API GET /api/v1/events.
VmwNsxTDataCenterFailureReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe detailed reason of any module failure like BGP down, IKE down, etc.
VmwNsxTDataCenterFeatureIdTypeINTEGERalarmManagement(16)auditLogHealth(24)capacity(22)certificates(3)clustering(40)cniHealth(10)communication(35)dhcp(20)distributedFirewall(31)distributedIdsIps(33)dns(30)edge(45)edgeCluster(49)edgeHealth(2)endpointProtection(13)federation(32)gatewayFirewall(39)groups(54)highAvailability(21)identityFirewall(36)infrastructureCommunication(7)infrastructureService(19)intelligenceCommunication(9)intelligenceHealth(6)ipam(38)licenses(5)loadBalancer(17)malwarePreventionHealth(48)managerHealth(1)mtuCheck(42)nat(46)ncpHealth(11)nodeAgentsHealth(12)nsxApplicationPlatformCommunication(41)nsxApplicationPlatformHealth(43)nsxaasHealth(58)passwordManagement(4)physicalServer(47)policyConstraint(53)routing(28)securityCompliance(56)serviceInsertion(14)tepHealth(51)transportNodeHealth(18)vmcApp(50)vpn(15)The NSX Data Center feature ID associated with the event. For example, this value identifies the feature is managerHealth, edgeHealth, loadBalancer, etc.
VmwNsxTDataCenterFirewallHalfopenFlowUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent firewall TCP half-open connection usage percentage of max supported value. The value is an integer between 0 and 100.
VmwNsxTDataCenterFirewallICMPFlowUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent firewall ICMP connection usage percentage of max supported value. The value is an integer between 0 and 100.
VmwNsxTDataCenterFirewallIPFlowUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent firewall IP connection usage percentage of max supported value. The value is an integer between 0 and 100.
VmwNsxTDataCenterFirewallSNATPortsUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent firewall SNAT ports usage percentage of max supported value. The value is an integer between 0 and 100.
VmwNsxTDataCenterFirewallUDPFlowUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aCurrent firewall UDP connection usage percentage of max supported value. The value is an integer between 0 and 100.
VmwNsxTDataCenterFlowCacheThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString to identify the flow cache threshold.
VmwNsxTDataCenterFlowIdentifierTypeOCTET STRING (SIZE (0..256))Display hint:
256aA flow identifier indicating the direction of flow of data which is one of following. - GM_2_LM - LM_2_GM_NOTIFICATION - LM_2_GM_ONBOARD_CONFIG
VmwNsxTDataCenterFromGMPathTypeOCTET STRING (SIZE (0..256))Display hint:
256aPolicy path of the Global Manager.
VmwNsxTDataCenterGroupIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe group UUID.
VmwNsxTDataCenterGroupMaxNumberLimitTypeOCTET STRING (SIZE (0..256))Display hint:
256aMaximum number of group elements supported.
VmwNsxTDataCenterGroupSizeTypeOCTET STRING (SIZE (0..256))Display hint:
256aTotal number of group elements.
VmwNsxTDataCenterGroupTypeTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe group type of a GMLE cluster.
VmwNsxTDataCenterHaState2TypeOCTET STRING (SIZE (0..256))Display hint:
256aThe current high-availability state. The value could be active/standby/down.
VmwNsxTDataCenterHaStateTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe current high-availability state. The value could be active/standby/down.
VmwNsxTDataCenterHeapTypeTypeOCTET STRING (SIZE (0..256))Display hint:
256aHeap type information for DFW memory usage like vsip-attr, vsip-flow, vsip-fqdni, etc.
VmwNsxTDataCenterHostnameOrIPAddressWithPortTypeOCTET STRING (SIZE (0..256))Display hint:
256aHostname or ip address with port of logging server.
VmwNsxTDataCenterIDSEventsCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aCount of the IDS events in the system currently.
VmwNsxTDataCenterIPCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of IP sets inside one group.
VmwNsxTDataCenterIPv4AddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of IPv4 address in dual stack.
VmwNsxTDataCenterIPv6AddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of IPv6 address in dual stack.
VmwNsxTDataCenterIntelligenceNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe node ID of an NSX Intelligence node.
VmwNsxTDataCenterIntentPathTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe policy intent path.
VmwNsxTDataCenterLDAPServerTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name or IP address of a LDAP server.
VmwNsxTDataCenterLatencySourceTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe source of reported latency.
VmwNsxTDataCenterLatencyThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThreshold value of reported IO latency.
VmwNsxTDataCenterLatencyValueTypeOCTET STRING (SIZE (0..256))Display hint:
256aValue of reported IO latency.
VmwNsxTDataCenterLicenseEditionTypeTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe edition type of an NSX license. For example, the type for an NSX evaluation license is 'NSX Data Center Evaluation'.
VmwNsxTDataCenterLrIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aLogical Router UUID.
VmwNsxTDataCenterLrpCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of logical router port inside one group.
VmwNsxTDataCenterLrportIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aLogical Router Port UUID.
VmwNsxTDataCenterLspCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of logical switch port inside one group.
VmwNsxTDataCenterMacCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of MAC sets inside one group.
VmwNsxTDataCenterManagerNodeIDSTypeOCTET STRING (SIZE (0..256))Display hint:
256aA comma delimited list of identifiers for the Manager nodes.
VmwNsxTDataCenterManagerNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe Manager node UUID.
VmwNsxTDataCenterManagerNodeNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe display name of a NSX Manager node.
VmwNsxTDataCenterMaxCapacityThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aMaximum threshold defined for capacity usage type.
VmwNsxTDataCenterMaxIDSEventsAllowedTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe maximum number of IDS events that are allowed in the system, anything beyond this would be purged at regular intervals.
VmwNsxTDataCenterMaxSupportedCapacityCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aMaximum supported count for capacity usage type.
VmwNsxTDataCenterMemberIndexIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing member index ID.
VmwNsxTDataCenterMempoolNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of a memory pool.
VmwNsxTDataCenterMetricsTargetAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aIP address of specified target metrics being delivered to.
VmwNsxTDataCenterMetricsTargetAliasTypeOCTET STRING (SIZE (0..256))Display hint:
256aAlias of specified target metrics being delivered to.
VmwNsxTDataCenterMetricsTargetPortTypeOCTET STRING (SIZE (0..256))Display hint:
256aListen port of specified target metrics being delivered to.
VmwNsxTDataCenterMinCapacityThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aMinimum threshold defined for capacity usage type.
VmwNsxTDataCenterMpsServiceNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe service name of an NSX Malware Prevention service.
VmwNsxTDataCenterNICThroughputThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NIC throughput threshold, as a percentage. The value is an integer between 0 and 100.
VmwNsxTDataCenterNICThroughputTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NIC throughput, as a percentage. The value is an integer between 0 and 100.
VmwNsxTDataCenterNSXESXTNNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe display name of a NSX Host Transport node.
VmwNsxTDataCenterNSXEdgeTNNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe display name of a NSX Edge Transport node.
VmwNsxTDataCenterNSXaaSServiceNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the service running in NSXaaS.
VmwNsxTDataCenterNappClusterIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe cluster ID of the NSX Application Platform cluster.
VmwNsxTDataCenterNappMessagingLAGThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe configured threshold value for the number of pending messages in an NSX Application Platform messaging topic.
VmwNsxTDataCenterNappNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe node ID of an NSX Application Platform node.
VmwNsxTDataCenterNappNodeNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe node name of an NSX Application Platform node.
VmwNsxTDataCenterNappServiceNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe service name of an NSX Application Platform service.
VmwNsxTDataCenterNewVMMorefIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Edge VM moref details corresponding to Policy/MP intent vSphere deployment configuration.
VmwNsxTDataCenterNodeDisplayOrHostNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aDisplay name or Host name of NSX node.
VmwNsxTDataCenterNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe node ID from where a NSX Data Center event was emitted. A node ID can be for a cluster node as reported by the NSX API GET /api/v1/cluster. Or a node ID can be for a transport node as reported by the NSX API GET /api/v1/transport-nodes.
VmwNsxTDataCenterNodeTypeTypeINTEGERautonomousedge(6)edge(1)esx(2)globalmanager(7)intelligence(5)kvm(3)manager(0)publiccloudgateway(4)The type of node from where a NSX Data Center event was emitted.
VmwNsxTDataCenterPasswordExpirationDaysTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of days left before expiration of the password of an NSX appliance user. The value is an integer greater than 0.
VmwNsxTDataCenterPeerAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aIP address of BFD peer.
VmwNsxTDataCenterPolicyEdgeVMNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Edge VM name corresponding to Policy/MP intent vSphere deployment configuration.
VmwNsxTDataCenterPrefixesCountMaxTypeOCTET STRING (SIZE (0..256))Display hint:
256aMaximum value of prefix count of BGP neighbor.
VmwNsxTDataCenterPrefixesCountThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThreshold Value of prefix count of BGP neighbor.
VmwNsxTDataCenterPreviousGatewayStateTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe previous gateway state. The value could be 0, 1 or 2 where 0 is down, 1 is standby and 2 is active
VmwNsxTDataCenterPreviousServiceStateTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe previous service state. The value could be start/stop/restart/crashed.
VmwNsxTDataCenterProtocolNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing network protocol.
VmwNsxTDataCenterQueueNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the queue used to synchronize data between two sites.
VmwNsxTDataCenterQueueSizeThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aMaximum threshold value of reported queue size.
VmwNsxTDataCenterQueueSizeTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe occupancy size of queue used to synchronize data between two sites.
VmwNsxTDataCenterRemoteApplianceAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe remote NSX appliance's IP address. The value is an IPv4 address.
VmwNsxTDataCenterRemoteManagerNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe remote Manager node UUID.
VmwNsxTDataCenterRemoteSiteIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe identifier for a remote site.
VmwNsxTDataCenterRemoteSiteNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of a remote site in federation. For more information on remote sites and an overview of the federation feature, refer to: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-D5B6DC79-6733-44A7-8072-50221CF2122A.html
VmwNsxTDataCenterRouteLimitMaximumTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing maximum limit for routes.
VmwNsxTDataCenterRouteLimitThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing threshold limit for routes.
VmwNsxTDataCenterRxMissesTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of packets missed while receiving due to rx ring buffer being full.
VmwNsxTDataCenterRxProcessedTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of successful incoming packets while polling for rx buffer full event.
VmwNsxTDataCenterRxRingBufferOverflowPercentageTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NIC's receive descriptor ring buffer on a NSX Edge or Gateway node has no space left to accomodate new incoming packets and there is a significant drop due to it. The value is a float between 0 to 100 describing the overflow percentage due to the packet drops.
VmwNsxTDataCenterSNATIPAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe SNAT IP address which ran out of port threshold.
VmwNsxTDataCenterServiceDownReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aReason service is down.
VmwNsxTDataCenterServiceIPTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe IP configured for the service running in an NSX appliance in dotted-decimal format.
VmwNsxTDataCenterServiceNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of the service running in an NSX appliance.
VmwNsxTDataCenterServiceRouterIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe ID of a service-router that is part of a tier0 or tier1 gateway spanning one or more edges
VmwNsxTDataCenterSessionDownReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aDown reason of the IPsec VPN session.
VmwNsxTDataCenterSeverityTypeINTEGERalert(1)critical(2)debug(7)emergency(0)error(3)informational(6)notice(5)warning(4)The severity of the NSX Data Center event. Currently only the critical(2), error(3), warning(4) and informational(6) levels are used, but the other levels may be used in future releases.
VmwNsxTDataCenterSidCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of security IDs inside one group.
VmwNsxTDataCenterSiteIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe identifier for a local site.
VmwNsxTDataCenterSiteNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of a local site in federation. For more information on local sites and an overview of the federation feature, refer to: https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.0/administration/GUID-D5B6DC79-6733-44A7-8072-50221CF2122A.html
VmwNsxTDataCenterSrIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aService Router UUID.
VmwNsxTDataCenterStackAliasTypeOCTET STRING (SIZE (0..256))Display hint:
256aStack name specified for given vmknic.
VmwNsxTDataCenterStaticAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aA Static IP address.
VmwNsxTDataCenterSubsequentAddressFamilyTypeOCTET STRING (SIZE (0..256))Display hint:
256aString representing subsequent address family (Unicast or Multicast).
VmwNsxTDataCenterSyncIssueReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aA reason for data synchronization issue.
VmwNsxTDataCenterSystemResourceUsageTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe CPU, memory, or disk usage percentage of an NSX appliance. The value is an integer between 0 and 100.
VmwNsxTDataCenterSystemUsageThresholdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe configured threshold value for the CPU, memory, or disk usage percentage of an NSX appliance. The value is an integer between 0 and 100.
VmwNsxTDataCenterTNCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of Transport Nodes inside one group.
VmwNsxTDataCenterTimeoutInMinutesTypeOCTET STRING (SIZE (0..256))Display hint:
256aTimeout value in minutes.
VmwNsxTDataCenterToGMPathTypeOCTET STRING (SIZE (0..256))Display hint:
256aPolicy path of the Global Manager.
VmwNsxTDataCenterTransportNodeAddressTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe IP address of a NSX Transport node.
VmwNsxTDataCenterTransportNodeId2TypeOCTET STRING (SIZE (0..256))Display hint:
256aThe Transport node UUID.
VmwNsxTDataCenterTransportNodeIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe Transport node UUID.
VmwNsxTDataCenterTransportNodeNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe display name of a NSX Transport node.
VmwNsxTDataCenterTunnelDownReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aDown reason of the IPsec VPN tunnel.
VmwNsxTDataCenterTxMissesTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of packets missed while transmitting due to tx ring buffer being full.
VmwNsxTDataCenterTxProcessedTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe number of successful outgoing packets while polling for tx buffer full event.
VmwNsxTDataCenterTxRingBufferOverflowPercentageTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe NIC's transmit descriptor ring buffer on a NSX Edge or Gateway node has no space left to accomodate new outgoing packets and there is a significant drop due to it. The value is a float between 0 to 100 describing the overflow percentage due to the packet drops.
VmwNsxTDataCenterUsernameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe name of a user in an NSX appliance.
VmwNsxTDataCenterVMCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of VMs inside one group.
VmwNsxTDataCenterVMMorefIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aString containing Edge VM moref details corresponding to Policy/MP intent vSphere deployment configuration.
VmwNsxTDataCenterVerticalNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aName of OPS vertical on DPU.
VmwNsxTDataCenterVifCountTypeOCTET STRING (SIZE (0..256))Display hint:
256aNumber of VIFs inside one group.
VmwNsxTDataCenterVtepFaultReasonTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe VTEP fault reason.
VmwNsxTDataCenterVtepNameTypeOCTET STRING (SIZE (0..256))Display hint:
256aThe ESXi VTEP name.
VmwNsxTDataCentervCenterClusterIdTypeOCTET STRING (SIZE (0..256))Display hint:
256aCluster identifier in the Virtual Center.
Traps / Notifications
- vmwNsxTAlarmManagementAlarmServiceOverloaded
1.3.6.1.4.1.6876.120.1.0.16.0.1 - vmwNsxTAlarmManagementAlarmServiceOverloadedClear
1.3.6.1.4.1.6876.120.1.0.16.0.2 - vmwNsxTAlarmManagementHeavyVolumeOfAlarms
1.3.6.1.4.1.6876.120.1.0.16.0.3 - vmwNsxTAlarmManagementHeavyVolumeOfAlarmsClear
1.3.6.1.4.1.6876.120.1.0.16.0.4 - vmwNsxTAuditLogHealthAuditLogFileUpdateError
1.3.6.1.4.1.6876.120.1.0.24.0.1 - vmwNsxTAuditLogHealthAuditLogFileUpdateErrorClear
1.3.6.1.4.1.6876.120.1.0.24.0.2 - vmwNsxTAuditLogHealthRemoteLoggingServerError
1.3.6.1.4.1.6876.120.1.0.24.0.3 - vmwNsxTAuditLogHealthRemoteLoggingServerErrorClear
1.3.6.1.4.1.6876.120.1.0.24.0.4 - vmwNsxTCapacityMaximumCapacity
1.3.6.1.4.1.6876.120.1.0.22.0.1 - vmwNsxTCapacityMaximumCapacityClear
1.3.6.1.4.1.6876.120.1.0.22.0.2 - vmwNsxTCapacityMaximumCapacityThreshold
1.3.6.1.4.1.6876.120.1.0.22.0.3 - vmwNsxTCapacityMaximumCapacityThresholdClear
1.3.6.1.4.1.6876.120.1.0.22.0.4 - vmwNsxTCapacityMinimumCapacityThreshold
1.3.6.1.4.1.6876.120.1.0.22.0.5 - vmwNsxTCapacityMinimumCapacityThresholdClear
1.3.6.1.4.1.6876.120.1.0.22.0.6 - vmwNsxTCertificatesCABundleUpdateRecommended
1.3.6.1.4.1.6876.120.1.0.3.0.7 - vmwNsxTCertificatesCABundleUpdateRecommendedClear
1.3.6.1.4.1.6876.120.1.0.3.0.8 - vmwNsxTCertificatesCABundleUpdateSuggested
1.3.6.1.4.1.6876.120.1.0.3.0.9 - vmwNsxTCertificatesCABundleUpdateSuggestedClear
1.3.6.1.4.1.6876.120.1.0.3.0.10 - vmwNsxTCertificatesCertificateExpirationApproaching
1.3.6.1.4.1.6876.120.1.0.3.0.1 - vmwNsxTCertificatesCertificateExpirationApproachingClear
1.3.6.1.4.1.6876.120.1.0.3.0.2 - vmwNsxTCertificatesCertificateExpired
1.3.6.1.4.1.6876.120.1.0.3.0.3 - vmwNsxTCertificatesCertificateExpiredClear
1.3.6.1.4.1.6876.120.1.0.3.0.4 - vmwNsxTCertificatesCertificateIsAboutToExpire
1.3.6.1.4.1.6876.120.1.0.3.0.5 - vmwNsxTCertificatesCertificateIsAboutToExpireClear
1.3.6.1.4.1.6876.120.1.0.3.0.6 - vmwNsxTCertificatesTransportNodeCertificateExpirApproaching
1.3.6.1.4.1.6876.120.1.0.3.0.17 - vmwNsxTCertificatesTransportNodeCertificateExpirApproachingClear
1.3.6.1.4.1.6876.120.1.0.3.0.18 - vmwNsxTCertificatesTransportNodeCertificateExpired
1.3.6.1.4.1.6876.120.1.0.3.0.19 - vmwNsxTCertificatesTransportNodeCertificateExpiredClear
1.3.6.1.4.1.6876.120.1.0.3.0.20 - vmwNsxTCertificatesTransportNodeCertificateIsAboutToExpire
1.3.6.1.4.1.6876.120.1.0.3.0.21 - vmwNsxTCertificatesTransportNodeCertificateIsAboutToExpireClear
1.3.6.1.4.1.6876.120.1.0.3.0.22 - vmwNsxTClusteringClusterDegraded
1.3.6.1.4.1.6876.120.1.0.40.0.1 - vmwNsxTClusteringClusterDegradedClear
1.3.6.1.4.1.6876.120.1.0.40.0.2 - vmwNsxTClusteringClusterUnavailable
1.3.6.1.4.1.6876.120.1.0.40.0.3 - vmwNsxTClusteringClusterUnavailableClear
1.3.6.1.4.1.6876.120.1.0.40.0.4 - vmwNsxTCniHealthHyperbusManagerConnectionDown
1.3.6.1.4.1.6876.120.1.0.10.0.3 - vmwNsxTCniHealthHyperbusManagerConnectionDownClear
1.3.6.1.4.1.6876.120.1.0.10.0.4 - vmwNsxTCniHealthHyperbusManagerConnectionDownOnDPU
1.3.6.1.4.1.6876.120.1.0.10.0.5 - vmwNsxTCniHealthHyperbusManagerConnectionDownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.10.0.6 - vmwNsxTCommunicationControlChannelToManagerNodeDown
1.3.6.1.4.1.6876.120.1.0.35.0.7 - vmwNsxTCommunicationControlChannelToManagerNodeDownClear
1.3.6.1.4.1.6876.120.1.0.35.0.8 - vmwNsxTCommunicationControlChannelToManagerNodeDownTooLong
1.3.6.1.4.1.6876.120.1.0.35.0.9 - vmwNsxTCommunicationControlChannelToManagerNodeDownTooLongClear
1.3.6.1.4.1.6876.120.1.0.35.0.10 - vmwNsxTCommunicationControlChannelToTransportNodeDown
1.3.6.1.4.1.6876.120.1.0.35.0.11 - vmwNsxTCommunicationControlChannelToTransportNodeDownClear
1.3.6.1.4.1.6876.120.1.0.35.0.12 - vmwNsxTCommunicationControlChannelToTransportNodeDownLong
1.3.6.1.4.1.6876.120.1.0.35.0.19 - vmwNsxTCommunicationControlChannelToTransportNodeDownLongClear
1.3.6.1.4.1.6876.120.1.0.35.0.20 - vmwNsxTCommunicationLimitedReachabilityOnDPU
1.3.6.1.4.1.6876.120.1.0.35.0.31 - vmwNsxTCommunicationLimitedReachabilityOnDPUClear
1.3.6.1.4.1.6876.120.1.0.35.0.32 - vmwNsxTCommunicationManagementChannelToManagerNodeDown
1.3.6.1.4.1.6876.120.1.0.35.0.13 - vmwNsxTCommunicationManagementChannelToManagerNodeDownClear
1.3.6.1.4.1.6876.120.1.0.35.0.14 - vmwNsxTCommunicationManagementChannelToManagerNodeDownLong
1.3.6.1.4.1.6876.120.1.0.35.0.25 - vmwNsxTCommunicationManagementChannelToManagerNodeDownLongClear
1.3.6.1.4.1.6876.120.1.0.35.0.26 - vmwNsxTCommunicationManagementChannelToTransportNodeDown
1.3.6.1.4.1.6876.120.1.0.35.0.1 - vmwNsxTCommunicationManagementChannelToTransportNodeDownClear
1.3.6.1.4.1.6876.120.1.0.35.0.2 - vmwNsxTCommunicationManagementChannelToTransportNodeDownLg
1.3.6.1.4.1.6876.120.1.0.35.0.5 - vmwNsxTCommunicationManagementChannelToTransportNodeDownLgClear
1.3.6.1.4.1.6876.120.1.0.35.0.6 - vmwNsxTCommunicationManagerClusterLatencyHigh
1.3.6.1.4.1.6876.120.1.0.35.0.17 - vmwNsxTCommunicationManagerClusterLatencyHighClear
1.3.6.1.4.1.6876.120.1.0.35.0.18 - vmwNsxTCommunicationManagerControlChannelDown
1.3.6.1.4.1.6876.120.1.0.35.0.3 - vmwNsxTCommunicationManagerControlChannelDownClear
1.3.6.1.4.1.6876.120.1.0.35.0.4 - vmwNsxTCommunicationManagerFQDNLookupFailure
1.3.6.1.4.1.6876.120.1.0.35.0.21 - vmwNsxTCommunicationManagerFQDNLookupFailureClear
1.3.6.1.4.1.6876.120.1.0.35.0.22 - vmwNsxTCommunicationManagerFQDNReverseLookupFailure
1.3.6.1.4.1.6876.120.1.0.35.0.23 - vmwNsxTCommunicationManagerFQDNReverseLookupFailureClear
1.3.6.1.4.1.6876.120.1.0.35.0.24 - vmwNsxTCommunicationNetworkLatencyHigh
1.3.6.1.4.1.6876.120.1.0.35.0.29 - vmwNsxTCommunicationNetworkLatencyHighClear
1.3.6.1.4.1.6876.120.1.0.35.0.30 - vmwNsxTCommunicationUnreachableCollectorOnDPU
1.3.6.1.4.1.6876.120.1.0.35.0.33 - vmwNsxTCommunicationUnreachableCollectorOnDPUClear
1.3.6.1.4.1.6876.120.1.0.35.0.34 - vmwNsxTDHCPPoolLeaseAllocationFailed
1.3.6.1.4.1.6876.120.1.0.20.0.1 - vmwNsxTDHCPPoolLeaseAllocationFailedClear
1.3.6.1.4.1.6876.120.1.0.20.0.2 - vmwNsxTDHCPPoolOverloaded
1.3.6.1.4.1.6876.120.1.0.20.0.3 - vmwNsxTDHCPPoolOverloadedClear
1.3.6.1.4.1.6876.120.1.0.20.0.4 - vmwNsxTDNSForwarderDisabled
1.3.6.1.4.1.6876.120.1.0.30.0.1 - vmwNsxTDNSForwarderDisabledClear
1.3.6.1.4.1.6876.120.1.0.30.0.2 - vmwNsxTDNSForwarderDown
1.3.6.1.4.1.6876.120.1.0.30.0.3 - vmwNsxTDNSForwarderDownClear
1.3.6.1.4.1.6876.120.1.0.30.0.4 - vmwNsxTDNSForwarderUpstreamServerTimeout
1.3.6.1.4.1.6876.120.1.0.30.0.5 - vmwNsxTDNSForwarderUpstreamServerTimeoutClear
1.3.6.1.4.1.6876.120.1.0.30.0.6 - vmwNsxTDistributedFirewallDFWCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.31.0.1 - vmwNsxTDistributedFirewallDFWCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.31.0.2 - vmwNsxTDistributedFirewallDFWCPUUsageVeryHighOnDPU
1.3.6.1.4.1.6876.120.1.0.31.0.17 - vmwNsxTDistributedFirewallDFWCPUUsageVeryHighOnDPUClear
1.3.6.1.4.1.6876.120.1.0.31.0.18 - vmwNsxTDistributedFirewallDFWFloodLimitCritical
1.3.6.1.4.1.6876.120.1.0.31.0.23 - vmwNsxTDistributedFirewallDFWFloodLimitCriticalClear
1.3.6.1.4.1.6876.120.1.0.31.0.24 - vmwNsxTDistributedFirewallDFWFloodLimitWarning
1.3.6.1.4.1.6876.120.1.0.31.0.21 - vmwNsxTDistributedFirewallDFWFloodLimitWarningClear
1.3.6.1.4.1.6876.120.1.0.31.0.22 - vmwNsxTDistributedFirewallDFWMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.31.0.3 - vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.31.0.4 - vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighOnDPU
1.3.6.1.4.1.6876.120.1.0.31.0.19 - vmwNsxTDistributedFirewallDFWMemoryUsageVeryHighOnDPUClear
1.3.6.1.4.1.6876.120.1.0.31.0.20 - vmwNsxTDistributedFirewallDFWRulesLimitPerHostApproaching
1.3.6.1.4.1.6876.120.1.0.31.0.11 - vmwNsxTDistributedFirewallDFWRulesLimitPerHostApproachingClear
1.3.6.1.4.1.6876.120.1.0.31.0.12 - vmwNsxTDistributedFirewallDFWRulesLimitPerHostExceeded
1.3.6.1.4.1.6876.120.1.0.31.0.13 - vmwNsxTDistributedFirewallDFWRulesLimitPerHostExceededClear
1.3.6.1.4.1.6876.120.1.0.31.0.14 - vmwNsxTDistributedFirewallDFWRulesLimitPervNICApproaching
1.3.6.1.4.1.6876.120.1.0.31.0.15 - vmwNsxTDistributedFirewallDFWRulesLimitPervNICApproachingClear
1.3.6.1.4.1.6876.120.1.0.31.0.16 - vmwNsxTDistributedFirewallDFWRulesLimitPervNICExceeded
1.3.6.1.4.1.6876.120.1.0.31.0.9 - vmwNsxTDistributedFirewallDFWRulesLimitPervNICExceededClear
1.3.6.1.4.1.6876.120.1.0.31.0.10 - vmwNsxTDistributedFirewallDFWSessionCountHigh
1.3.6.1.4.1.6876.120.1.0.31.0.5 - vmwNsxTDistributedFirewallDFWSessionCountHighClear
1.3.6.1.4.1.6876.120.1.0.31.0.6 - vmwNsxTDistributedFirewallDFWVmotionFailure
1.3.6.1.4.1.6876.120.1.0.31.0.7 - vmwNsxTDistributedFirewallDFWVmotionFailureClear
1.3.6.1.4.1.6876.120.1.0.31.0.8 - vmwNsxTDistributedIDSIPSIDPSBypassedCPUOversubscribed
1.3.6.1.4.1.6876.120.1.0.33.0.53 - vmwNsxTDistributedIDSIPSIDPSBypassedCPUOversubscribedClear
1.3.6.1.4.1.6876.120.1.0.33.0.54 - vmwNsxTDistributedIDSIPSIDPSBypassedNetworkOversubscribed
1.3.6.1.4.1.6876.120.1.0.33.0.55 - vmwNsxTDistributedIDSIPSIDPSBypassedNetworkOversubscribedClear
1.3.6.1.4.1.6876.120.1.0.33.0.56 - vmwNsxTDistributedIDSIPSIDPSCPUOversubscriptionVeryHigh
1.3.6.1.4.1.6876.120.1.0.33.0.59 - vmwNsxTDistributedIDSIPSIDPSCPUOversubscriptionVeryHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.60 - vmwNsxTDistributedIDSIPSIDPSDroppedCPUOversubscribed
1.3.6.1.4.1.6876.120.1.0.33.0.61 - vmwNsxTDistributedIDSIPSIDPSDroppedCPUOversubscribedClear
1.3.6.1.4.1.6876.120.1.0.33.0.62 - vmwNsxTDistributedIDSIPSIDPSDroppedNetworkOversubscribed
1.3.6.1.4.1.6876.120.1.0.33.0.63 - vmwNsxTDistributedIDSIPSIDPSDroppedNetworkOversubscribedClear
1.3.6.1.4.1.6876.120.1.0.33.0.64 - vmwNsxTDistributedIDSIPSIDPSEngineCPUOversubscriptionHigh
1.3.6.1.4.1.6876.120.1.0.33.0.57 - vmwNsxTDistributedIDSIPSIDPSEngineCPUOversubscriptionHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.58 - vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionHigh
1.3.6.1.4.1.6876.120.1.0.33.0.65 - vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.66 - vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionVeryHigh
1.3.6.1.4.1.6876.120.1.0.33.0.67 - vmwNsxTDistributedIDSIPSIDPSNetworkOversubscriptionVeryHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.68 - vmwNsxTDistributedIDSIPSMaxEventsReached
1.3.6.1.4.1.6876.120.1.0.33.0.3 - vmwNsxTDistributedIDSIPSMaxEventsReachedClear
1.3.6.1.4.1.6876.120.1.0.33.0.4 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.33.0.7 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.8 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHigh
1.3.6.1.4.1.6876.120.1.0.33.0.21 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageMediumHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.22 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.33.0.9 - vmwNsxTDistributedIDSIPSNSXIDPSEngineCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.10 - vmwNsxTDistributedIDSIPSNSXIDPSEngineDown
1.3.6.1.4.1.6876.120.1.0.33.0.13 - vmwNsxTDistributedIDSIPSNSXIDPSEngineDownClear
1.3.6.1.4.1.6876.120.1.0.33.0.14 - vmwNsxTDistributedIDSIPSNSXIDPSEngineDownOnDPU
1.3.6.1.4.1.6876.120.1.0.33.0.31 - vmwNsxTDistributedIDSIPSNSXIDPSEngineDownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.33.0.32 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageMedHighOnDPU
1.3.6.1.4.1.6876.120.1.0.33.0.33 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageMedHighOnDPUClear
1.3.6.1.4.1.6876.120.1.0.33.0.34 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageVeryHighDPU
1.3.6.1.4.1.6876.120.1.0.33.0.35 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemUsageVeryHighDPUClear
1.3.6.1.4.1.6876.120.1.0.33.0.36 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.33.0.15 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.16 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighOnDPU
1.3.6.1.4.1.6876.120.1.0.33.0.23 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageHighOnDPUClear
1.3.6.1.4.1.6876.120.1.0.33.0.24 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHigh
1.3.6.1.4.1.6876.120.1.0.33.0.17 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageMediumHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.18 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.33.0.19 - vmwNsxTDistributedIDSIPSNSXIDPSEngineMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.33.0.20 - vmwNsxTEdgeClusterEdgeClusterMemberRelocateFailure
1.3.6.1.4.1.6876.120.1.0.49.0.5 - vmwNsxTEdgeClusterEdgeClusterMemberRelocateFailureClear
1.3.6.1.4.1.6876.120.1.0.49.0.6 - vmwNsxTEdgeEdgeHardwareVersionMismatch
1.3.6.1.4.1.6876.120.1.0.45.0.15 - vmwNsxTEdgeEdgeHardwareVersionMismatchClear
1.3.6.1.4.1.6876.120.1.0.45.0.16 - vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChanged
1.3.6.1.4.1.6876.120.1.0.45.0.1 - vmwNsxTEdgeEdgeNodeSettingsAndvSphereSettingsAreChangedClear
1.3.6.1.4.1.6876.120.1.0.45.0.2 - vmwNsxTEdgeEdgeNodeSettingsMismatch
1.3.6.1.4.1.6876.120.1.0.45.0.3 - vmwNsxTEdgeEdgeNodeSettingsMismatchClear
1.3.6.1.4.1.6876.120.1.0.45.0.4 - vmwNsxTEdgeEdgeVMNotPresentInBothNSXInventoryAndvCenter
1.3.6.1.4.1.6876.120.1.0.45.0.11 - vmwNsxTEdgeEdgeVMNotPresentInBothNSXInventoryAndvCenterClear
1.3.6.1.4.1.6876.120.1.0.45.0.12 - vmwNsxTEdgeEdgeVMPresentInNSXInventoryNotPresentInvCenter
1.3.6.1.4.1.6876.120.1.0.45.0.9 - vmwNsxTEdgeEdgeVMPresentInNSXInventoryNotPresentInvCenterClear
1.3.6.1.4.1.6876.120.1.0.45.0.10 - vmwNsxTEdgeEdgeVmvSphereSettingsMismatch
1.3.6.1.4.1.6876.120.1.0.45.0.5 - vmwNsxTEdgeEdgeVmvSphereSettingsMismatchClear
1.3.6.1.4.1.6876.120.1.0.45.0.6 - vmwNsxTEdgeEdgevSphereLocationMismatch
1.3.6.1.4.1.6876.120.1.0.45.0.7 - vmwNsxTEdgeEdgevSphereLocationMismatchClear
1.3.6.1.4.1.6876.120.1.0.45.0.8 - vmwNsxTEdgeFailedToDeleteTheOldVMInvCenterDuringRedeploy
1.3.6.1.4.1.6876.120.1.0.45.0.13 - vmwNsxTEdgeFailedToDeleteTheOldVMInvCenterDuringRedeployClear
1.3.6.1.4.1.6876.120.1.0.45.0.14 - vmwNsxTEdgeHealthDatapathThreadDeadlocked
1.3.6.1.4.1.6876.120.1.0.2.0.45 - vmwNsxTEdgeHealthDatapathThreadDeadlockedClear
1.3.6.1.4.1.6876.120.1.0.2.0.46 - vmwNsxTEdgeHealthEdgeCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.2.0.1 - vmwNsxTEdgeHealthEdgeCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.2 - vmwNsxTEdgeHealthEdgeCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.2.0.3 - vmwNsxTEdgeHealthEdgeCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.4 - vmwNsxTEdgeHealthEdgeDatapathCPUHigh
1.3.6.1.4.1.6876.120.1.0.2.0.17 - vmwNsxTEdgeHealthEdgeDatapathCPUHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.18 - vmwNsxTEdgeHealthEdgeDatapathCPUVeryHigh
1.3.6.1.4.1.6876.120.1.0.2.0.19 - vmwNsxTEdgeHealthEdgeDatapathCPUVeryHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.20 - vmwNsxTEdgeHealthEdgeDatapathConfigurationFailure
1.3.6.1.4.1.6876.120.1.0.2.0.21 - vmwNsxTEdgeHealthEdgeDatapathConfigurationFailureClear
1.3.6.1.4.1.6876.120.1.0.2.0.22 - vmwNsxTEdgeHealthEdgeDatapathCryptodrvDown
1.3.6.1.4.1.6876.120.1.0.2.0.23 - vmwNsxTEdgeHealthEdgeDatapathCryptodrvDownClear
1.3.6.1.4.1.6876.120.1.0.2.0.24 - vmwNsxTEdgeHealthEdgeDatapathMempoolHigh
1.3.6.1.4.1.6876.120.1.0.2.0.25 - vmwNsxTEdgeHealthEdgeDatapathMempoolHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.26 - vmwNsxTEdgeHealthEdgeDatapathNICThroughputHigh
1.3.6.1.4.1.6876.120.1.0.2.0.49 - vmwNsxTEdgeHealthEdgeDatapathNICThroughputHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.50 - vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHigh
1.3.6.1.4.1.6876.120.1.0.2.0.51 - vmwNsxTEdgeHealthEdgeDatapathNICThroughputVeryHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.52 - vmwNsxTEdgeHealthEdgeDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.2.0.9 - vmwNsxTEdgeHealthEdgeDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.10 - vmwNsxTEdgeHealthEdgeDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.2.0.11 - vmwNsxTEdgeHealthEdgeDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.12 - vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHigh
1.3.6.1.4.1.6876.120.1.0.2.0.27 - vmwNsxTEdgeHealthEdgeGlobalARPTableUsageHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.28 - vmwNsxTEdgeHealthEdgeMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.2.0.5 - vmwNsxTEdgeHealthEdgeMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.6 - vmwNsxTEdgeHealthEdgeMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.2.0.7 - vmwNsxTEdgeHealthEdgeMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.2.0.8 - vmwNsxTEdgeHealthEdgeNICLinkStatusDown
1.3.6.1.4.1.6876.120.1.0.2.0.29 - vmwNsxTEdgeHealthEdgeNICLinkStatusDownClear
1.3.6.1.4.1.6876.120.1.0.2.0.30 - vmwNsxTEdgeHealthEdgeNICOutOfReceiveBuffer
1.3.6.1.4.1.6876.120.1.0.2.0.31 - vmwNsxTEdgeHealthEdgeNICOutOfReceiveBufferClear
1.3.6.1.4.1.6876.120.1.0.2.0.32 - vmwNsxTEdgeHealthEdgeNICOutOfTransmitBuffer
1.3.6.1.4.1.6876.120.1.0.2.0.33 - vmwNsxTEdgeHealthEdgeNICOutOfTransmitBufferClear
1.3.6.1.4.1.6876.120.1.0.2.0.34 - vmwNsxTEdgeHealthFailureDomainDown
1.3.6.1.4.1.6876.120.1.0.2.0.53 - vmwNsxTEdgeHealthFailureDomainDownClear
1.3.6.1.4.1.6876.120.1.0.2.0.54 - vmwNsxTEdgeHealthMegaFlowCacheHitRateLow
1.3.6.1.4.1.6876.120.1.0.2.0.55 - vmwNsxTEdgeHealthMegaFlowCacheHitRateLowClear
1.3.6.1.4.1.6876.120.1.0.2.0.56 - vmwNsxTEdgeHealthMicroFlowCacheHitRateLow
1.3.6.1.4.1.6876.120.1.0.2.0.57 - vmwNsxTEdgeHealthMicroFlowCacheHitRateLowClear
1.3.6.1.4.1.6876.120.1.0.2.0.58 - vmwNsxTEdgeHealthStorageError
1.3.6.1.4.1.6876.120.1.0.2.0.37 - vmwNsxTEdgeHealthStorageErrorClear
1.3.6.1.4.1.6876.120.1.0.2.0.38 - vmwNsxTEndpointProtectionEAMStatusDown
1.3.6.1.4.1.6876.120.1.0.13.0.1 - vmwNsxTEndpointProtectionEAMStatusDownClear
1.3.6.1.4.1.6876.120.1.0.13.0.2 - vmwNsxTEndpointProtectionPartnerChannelDown
1.3.6.1.4.1.6876.120.1.0.13.0.3 - vmwNsxTEndpointProtectionPartnerChannelDownClear
1.3.6.1.4.1.6876.120.1.0.13.0.4 - vmwNsxTFederationGMToGMLatencyWarning
1.3.6.1.4.1.6876.120.1.0.32.0.17 - vmwNsxTFederationGMToGMLatencyWarningClear
1.3.6.1.4.1.6876.120.1.0.32.0.18 - vmwNsxTFederationGMToGMSplitBrain
1.3.6.1.4.1.6876.120.1.0.32.0.9 - vmwNsxTFederationGMToGMSplitBrainClear
1.3.6.1.4.1.6876.120.1.0.32.0.10 - vmwNsxTFederationGMToGMSynchronizationError
1.3.6.1.4.1.6876.120.1.0.32.0.19 - vmwNsxTFederationGMToGMSynchronizationErrorClear
1.3.6.1.4.1.6876.120.1.0.32.0.20 - vmwNsxTFederationGMToGMSynchronizationWarning
1.3.6.1.4.1.6876.120.1.0.32.0.21 - vmwNsxTFederationGMToGMSynchronizationWarningClear
1.3.6.1.4.1.6876.120.1.0.32.0.22 - vmwNsxTFederationGMToLMLatencyWarning
1.3.6.1.4.1.6876.120.1.0.32.0.27 - vmwNsxTFederationGMToLMLatencyWarningClear
1.3.6.1.4.1.6876.120.1.0.32.0.28 - vmwNsxTFederationGMToLMSynchronizationError
1.3.6.1.4.1.6876.120.1.0.32.0.23 - vmwNsxTFederationGMToLMSynchronizationErrorClear
1.3.6.1.4.1.6876.120.1.0.32.0.24 - vmwNsxTFederationGMToLMSynchronizationWarning
1.3.6.1.4.1.6876.120.1.0.32.0.25 - vmwNsxTFederationGMToLMSynchronizationWarningClear
1.3.6.1.4.1.6876.120.1.0.32.0.26 - vmwNsxTFederationLMRestoreWhileConfigImportInProgress
1.3.6.1.4.1.6876.120.1.0.32.0.31 - vmwNsxTFederationLMRestoreWhileConfigImportInProgressClear
1.3.6.1.4.1.6876.120.1.0.32.0.32 - vmwNsxTFederationLmToLmSynchronizationError
1.3.6.1.4.1.6876.120.1.0.32.0.3 - vmwNsxTFederationLmToLmSynchronizationErrorClear
1.3.6.1.4.1.6876.120.1.0.32.0.4 - vmwNsxTFederationLmToLmSynchronizationWarning
1.3.6.1.4.1.6876.120.1.0.32.0.5 - vmwNsxTFederationLmToLmSynchronizationWarningClear
1.3.6.1.4.1.6876.120.1.0.32.0.6 - vmwNsxTFederationQueueOccupancyThresholdExceeded
1.3.6.1.4.1.6876.120.1.0.32.0.29 - vmwNsxTFederationQueueOccupancyThresholdExceededClear
1.3.6.1.4.1.6876.120.1.0.32.0.30 - vmwNsxTFederationRtepBGPDown
1.3.6.1.4.1.6876.120.1.0.32.0.1 - vmwNsxTFederationRtepBGPDownClear
1.3.6.1.4.1.6876.120.1.0.32.0.2 - vmwNsxTFederationRtepConnectivityLost
1.3.6.1.4.1.6876.120.1.0.32.0.7 - vmwNsxTFederationRtepConnectivityLostClear
1.3.6.1.4.1.6876.120.1.0.32.0.8 - vmwNsxTGatewayFirewallICMPFlowCountExceeded
1.3.6.1.4.1.6876.120.1.0.39.0.21 - vmwNsxTGatewayFirewallICMPFlowCountExceededClear
1.3.6.1.4.1.6876.120.1.0.39.0.22 - vmwNsxTGatewayFirewallICMPFlowCountHigh
1.3.6.1.4.1.6876.120.1.0.39.0.23 - vmwNsxTGatewayFirewallICMPFlowCountHighClear
1.3.6.1.4.1.6876.120.1.0.39.0.24 - vmwNsxTGatewayFirewallIPFlowCountExceeded
1.3.6.1.4.1.6876.120.1.0.39.0.25 - vmwNsxTGatewayFirewallIPFlowCountExceededClear
1.3.6.1.4.1.6876.120.1.0.39.0.26 - vmwNsxTGatewayFirewallIPFlowCountHigh
1.3.6.1.4.1.6876.120.1.0.39.0.27 - vmwNsxTGatewayFirewallIPFlowCountHighClear
1.3.6.1.4.1.6876.120.1.0.39.0.28 - vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceeded
1.3.6.1.4.1.6876.120.1.0.39.0.29 - vmwNsxTGatewayFirewallTcpHalfOpenFlowCountExceededClear
1.3.6.1.4.1.6876.120.1.0.39.0.30 - vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHigh
1.3.6.1.4.1.6876.120.1.0.39.0.31 - vmwNsxTGatewayFirewallTcpHalfOpenFlowCountHighClear
1.3.6.1.4.1.6876.120.1.0.39.0.32 - vmwNsxTGatewayFirewallUDPFlowCountExceeded
1.3.6.1.4.1.6876.120.1.0.39.0.33 - vmwNsxTGatewayFirewallUDPFlowCountExceededClear
1.3.6.1.4.1.6876.120.1.0.39.0.34 - vmwNsxTGatewayFirewallUDPFlowCountHigh
1.3.6.1.4.1.6876.120.1.0.39.0.35 - vmwNsxTGatewayFirewallUDPFlowCountHighClear
1.3.6.1.4.1.6876.120.1.0.39.0.36 - vmwNsxTGroupsGroupSizeLimitExceeded
1.3.6.1.4.1.6876.120.1.0.54.0.3 - vmwNsxTGroupsGroupSizeLimitExceededClear
1.3.6.1.4.1.6876.120.1.0.54.0.4 - vmwNsxTHighAvailabilityTier0GatewayFailover
1.3.6.1.4.1.6876.120.1.0.21.0.9 - vmwNsxTHighAvailabilityTier0GatewayFailoverClear
1.3.6.1.4.1.6876.120.1.0.21.0.10 - vmwNsxTHighAvailabilityTier0ServiceGroupFailover
1.3.6.1.4.1.6876.120.1.0.21.0.13 - vmwNsxTHighAvailabilityTier0ServiceGroupFailoverClear
1.3.6.1.4.1.6876.120.1.0.21.0.14 - vmwNsxTHighAvailabilityTier0ServiceGroupReducedRedundancy
1.3.6.1.4.1.6876.120.1.0.21.0.17 - vmwNsxTHighAvailabilityTier0ServiceGroupReducedRedundancyClear
1.3.6.1.4.1.6876.120.1.0.21.0.18 - vmwNsxTHighAvailabilityTier1GatewayFailover
1.3.6.1.4.1.6876.120.1.0.21.0.11 - vmwNsxTHighAvailabilityTier1GatewayFailoverClear
1.3.6.1.4.1.6876.120.1.0.21.0.12 - vmwNsxTHighAvailabilityTier1ServiceGroupFailover
1.3.6.1.4.1.6876.120.1.0.21.0.15 - vmwNsxTHighAvailabilityTier1ServiceGroupFailoverClear
1.3.6.1.4.1.6876.120.1.0.21.0.16 - vmwNsxTHighAvailabilityTier1ServiceGroupReducedRedundancy
1.3.6.1.4.1.6876.120.1.0.21.0.19 - vmwNsxTHighAvailabilityTier1ServiceGroupReducedRedundancyClear
1.3.6.1.4.1.6876.120.1.0.21.0.20 - vmwNsxTIPAMIPBlockUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.38.0.1 - vmwNsxTIPAMIPBlockUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.38.0.2 - vmwNsxTIPAMIPPoolUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.38.0.3 - vmwNsxTIPAMIPPoolUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.38.0.4 - vmwNsxTIdentityFirewallConnectivityToLDAPServerLost
1.3.6.1.4.1.6876.120.1.0.36.0.1 - vmwNsxTIdentityFirewallConnectivityToLDAPServerLostClear
1.3.6.1.4.1.6876.120.1.0.36.0.2 - vmwNsxTIdentityFirewallErrorInDeltaSync
1.3.6.1.4.1.6876.120.1.0.36.0.3 - vmwNsxTIdentityFirewallErrorInDeltaSyncClear
1.3.6.1.4.1.6876.120.1.0.36.0.4 - vmwNsxTInfrastructureCommunicationEdgeTunnelsDown
1.3.6.1.4.1.6876.120.1.0.7.0.17 - vmwNsxTInfrastructureCommunicationEdgeTunnelsDownClear
1.3.6.1.4.1.6876.120.1.0.7.0.18 - vmwNsxTInfrastructureServiceApplicationCrashed
1.3.6.1.4.1.6876.120.1.0.19.0.9 - vmwNsxTInfrastructureServiceApplicationCrashedClear
1.3.6.1.4.1.6876.120.1.0.19.0.10 - vmwNsxTInfrastructureServiceEdgeServiceStatusChanged
1.3.6.1.4.1.6876.120.1.0.19.0.1 - vmwNsxTInfrastructureServiceEdgeServiceStatusChangedClear
1.3.6.1.4.1.6876.120.1.0.19.0.2 - vmwNsxTInfrastructureServiceEdgeServiceStatusDown
1.3.6.1.4.1.6876.120.1.0.19.0.3 - vmwNsxTInfrastructureServiceEdgeServiceStatusDownClear
1.3.6.1.4.1.6876.120.1.0.19.0.4 - vmwNsxTInfrastructureServiceMetricsDeliveryFailure
1.3.6.1.4.1.6876.120.1.0.19.0.19 - vmwNsxTInfrastructureServiceMetricsDeliveryFailureClear
1.3.6.1.4.1.6876.120.1.0.19.0.20 - vmwNsxTInfrastructureServiceServiceStatusUnknown
1.3.6.1.4.1.6876.120.1.0.19.0.7 - vmwNsxTInfrastructureServiceServiceStatusUnknownClear
1.3.6.1.4.1.6876.120.1.0.19.0.8 - vmwNsxTInfrastructureServiceServiceStatusUnknownOnDPU
1.3.6.1.4.1.6876.120.1.0.19.0.11 - vmwNsxTInfrastructureServiceServiceStatusUnknownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.19.0.12 - vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnected
1.3.6.1.4.1.6876.120.1.0.9.0.7 - vmwNsxTIntelligenceCommunicationTNFlowExporterDisconnectedClear
1.3.6.1.4.1.6876.120.1.0.9.0.8 - vmwNsxTIntelligenceHealthCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.6.0.41 - vmwNsxTIntelligenceHealthCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.42 - vmwNsxTIntelligenceHealthCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.6.0.43 - vmwNsxTIntelligenceHealthCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.44 - vmwNsxTIntelligenceHealthDataDiskPartitionUsageHigh
1.3.6.1.4.1.6876.120.1.0.6.0.45 - vmwNsxTIntelligenceHealthDataDiskPartitionUsageHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.46 - vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.6.0.47 - vmwNsxTIntelligenceHealthDataDiskPartitionUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.48 - vmwNsxTIntelligenceHealthDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.6.0.49 - vmwNsxTIntelligenceHealthDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.50 - vmwNsxTIntelligenceHealthDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.6.0.51 - vmwNsxTIntelligenceHealthDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.52 - vmwNsxTIntelligenceHealthMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.6.0.53 - vmwNsxTIntelligenceHealthMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.54 - vmwNsxTIntelligenceHealthMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.6.0.55 - vmwNsxTIntelligenceHealthMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.56 - vmwNsxTIntelligenceHealthNodeStatusDegraded
1.3.6.1.4.1.6876.120.1.0.6.0.57 - vmwNsxTIntelligenceHealthNodeStatusDegradedClear
1.3.6.1.4.1.6876.120.1.0.6.0.58 - vmwNsxTIntelligenceHealthStorageLatencyHigh
1.3.6.1.4.1.6876.120.1.0.6.0.63 - vmwNsxTIntelligenceHealthStorageLatencyHighClear
1.3.6.1.4.1.6876.120.1.0.6.0.64 - vmwNsxTLicensesLicenseExpired
1.3.6.1.4.1.6876.120.1.0.5.0.1 - vmwNsxTLicensesLicenseExpiredClear
1.3.6.1.4.1.6876.120.1.0.5.0.2 - vmwNsxTLicensesLicenseIsAboutToExpire
1.3.6.1.4.1.6876.120.1.0.5.0.3 - vmwNsxTLicensesLicenseIsAboutToExpireClear
1.3.6.1.4.1.6876.120.1.0.5.0.4 - vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemory
1.3.6.1.4.1.6876.120.1.0.17.0.19 - vmwNsxTLoadBalancerConfigurationNotRealizedDueToLowMemoryClear
1.3.6.1.4.1.6876.120.1.0.17.0.20 - vmwNsxTLoadBalancerDLBStatusDown
1.3.6.1.4.1.6876.120.1.0.17.0.17 - vmwNsxTLoadBalancerDLBStatusDownClear
1.3.6.1.4.1.6876.120.1.0.17.0.18 - vmwNsxTLoadBalancerLBCPUVeryHigh
1.3.6.1.4.1.6876.120.1.0.17.0.1 - vmwNsxTLoadBalancerLBCPUVeryHighClear
1.3.6.1.4.1.6876.120.1.0.17.0.2 - vmwNsxTLoadBalancerLBEdgeCapacityInUseHigh
1.3.6.1.4.1.6876.120.1.0.17.0.3 - vmwNsxTLoadBalancerLBEdgeCapacityInUseHighClear
1.3.6.1.4.1.6876.120.1.0.17.0.4 - vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHigh
1.3.6.1.4.1.6876.120.1.0.17.0.5 - vmwNsxTLoadBalancerLBPoolMemberCapacityInUseVeryHighClear
1.3.6.1.4.1.6876.120.1.0.17.0.6 - vmwNsxTLoadBalancerLBStatusDegraded
1.3.6.1.4.1.6876.120.1.0.17.0.15 - vmwNsxTLoadBalancerLBStatusDegradedClear
1.3.6.1.4.1.6876.120.1.0.17.0.16 - vmwNsxTLoadBalancerLBStatusDown
1.3.6.1.4.1.6876.120.1.0.17.0.7 - vmwNsxTLoadBalancerLBStatusDownClear
1.3.6.1.4.1.6876.120.1.0.17.0.8 - vmwNsxTLoadBalancerPoolStatusDown
1.3.6.1.4.1.6876.120.1.0.17.0.9 - vmwNsxTLoadBalancerPoolStatusDownClear
1.3.6.1.4.1.6876.120.1.0.17.0.10 - vmwNsxTLoadBalancerVirtualServerStatusDown
1.3.6.1.4.1.6876.120.1.0.17.0.11 - vmwNsxTLoadBalancerVirtualServerStatusDownClear
1.3.6.1.4.1.6876.120.1.0.17.0.12 - vmwNsxTMTUCheckGlobalRouterMTUTooBig
1.3.6.1.4.1.6876.120.1.0.42.0.3 - vmwNsxTMTUCheckGlobalRouterMTUTooBigClear
1.3.6.1.4.1.6876.120.1.0.42.0.4 - vmwNsxTMTUCheckMTUMismatchWithinTransportZone
1.3.6.1.4.1.6876.120.1.0.42.0.1 - vmwNsxTMTUCheckMTUMismatchWithinTransportZoneClear
1.3.6.1.4.1.6876.120.1.0.42.0.2 - vmwNsxTMalwarePreventionHealthAnalystAPIServiceUnreachable
1.3.6.1.4.1.6876.120.1.0.48.0.1 - vmwNsxTMalwarePreventionHealthAnalystAPIServiceUnreachableClear
1.3.6.1.4.1.6876.120.1.0.48.0.2 - vmwNsxTMalwarePreventionHealthDatabaseUnreachable
1.3.6.1.4.1.6876.120.1.0.48.0.3 - vmwNsxTMalwarePreventionHealthDatabaseUnreachableClear
1.3.6.1.4.1.6876.120.1.0.48.0.4 - vmwNsxTMalwarePreventionHealthFileExtractSvcUnreachable
1.3.6.1.4.1.6876.120.1.0.48.0.5 - vmwNsxTMalwarePreventionHealthFileExtractSvcUnreachableClear
1.3.6.1.4.1.6876.120.1.0.48.0.6 - vmwNsxTMalwarePreventionHealthNTICSRepSvcUnreachable
1.3.6.1.4.1.6876.120.1.0.48.0.7 - vmwNsxTMalwarePreventionHealthNTICSRepSvcUnreachableClear
1.3.6.1.4.1.6876.120.1.0.48.0.8 - vmwNsxTMalwarePreventionHealthServiceStatusDown
1.3.6.1.4.1.6876.120.1.0.48.0.9 - vmwNsxTMalwarePreventionHealthServiceStatusDownClear
1.3.6.1.4.1.6876.120.1.0.48.0.10 - vmwNsxTManagerHealthDuplicateIPAddress
1.3.6.1.4.1.6876.120.1.0.1.0.17 - vmwNsxTManagerHealthDuplicateIPAddressClear
1.3.6.1.4.1.6876.120.1.0.1.0.18 - vmwNsxTManagerHealthManagerCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.1.0.1 - vmwNsxTManagerHealthManagerCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.2 - vmwNsxTManagerHealthManagerCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.1.0.3 - vmwNsxTManagerHealthManagerCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.4 - vmwNsxTManagerHealthManagerConfigDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.1.0.13 - vmwNsxTManagerHealthManagerConfigDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.14 - vmwNsxTManagerHealthManagerConfigDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.1.0.15 - vmwNsxTManagerHealthManagerConfigDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.16 - vmwNsxTManagerHealthManagerDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.1.0.9 - vmwNsxTManagerHealthManagerDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.10 - vmwNsxTManagerHealthManagerDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.1.0.11 - vmwNsxTManagerHealthManagerDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.12 - vmwNsxTManagerHealthManagerMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.1.0.5 - vmwNsxTManagerHealthManagerMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.6 - vmwNsxTManagerHealthManagerMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.1.0.7 - vmwNsxTManagerHealthManagerMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.8 - vmwNsxTManagerHealthMissingDNSEntryForManagerFQDN
1.3.6.1.4.1.6876.120.1.0.1.0.28 - vmwNsxTManagerHealthMissingDNSEntryForManagerFQDNClear
1.3.6.1.4.1.6876.120.1.0.1.0.29 - vmwNsxTManagerHealthMissingDNSEntryForVipFQDN
1.3.6.1.4.1.6876.120.1.0.1.0.33 - vmwNsxTManagerHealthMissingDNSEntryForVipFQDNClear
1.3.6.1.4.1.6876.120.1.0.1.0.34 - vmwNsxTManagerHealthOperationsDbDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.1.0.19 - vmwNsxTManagerHealthOperationsDbDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.20 - vmwNsxTManagerHealthOperationsDbDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.1.0.21 - vmwNsxTManagerHealthOperationsDbDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.1.0.22 - vmwNsxTManagerHealthStorageError
1.3.6.1.4.1.6876.120.1.0.1.0.23 - vmwNsxTManagerHealthStorageErrorClear
1.3.6.1.4.1.6876.120.1.0.1.0.24 - vmwNsxTNATSNATPortUsageOnGatewayIsHigh
1.3.6.1.4.1.6876.120.1.0.46.0.1 - vmwNsxTNATSNATPortUsageOnGatewayIsHighClear
1.3.6.1.4.1.6876.120.1.0.46.0.2 - vmwNsxTNCPHealthNCPPluginDown
1.3.6.1.4.1.6876.120.1.0.11.0.3 - vmwNsxTNCPHealthNCPPluginDownClear
1.3.6.1.4.1.6876.120.1.0.11.0.4 - vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflow
1.3.6.1.4.1.6876.120.1.0.41.0.7 - vmwNsxTNSXApplicationPlatformCommunicationDelayInOverflowClear
1.3.6.1.4.1.6876.120.1.0.41.0.8 - vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflow
1.3.6.1.4.1.6876.120.1.0.41.0.11 - vmwNsxTNSXApplicationPlatformCommunicationDelayInRawflowClear
1.3.6.1.4.1.6876.120.1.0.41.0.12 - vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectDPU
1.3.6.1.4.1.6876.120.1.0.41.0.17 - vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectDPUClear
1.3.6.1.4.1.6876.120.1.0.41.0.18 - vmwNsxTNSXApplicationPlatformCommunicationExpDisconnected
1.3.6.1.4.1.6876.120.1.0.41.0.13 - vmwNsxTNSXApplicationPlatformCommunicationExpDisconnectedClear
1.3.6.1.4.1.6876.120.1.0.41.0.14 - vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnected
1.3.6.1.4.1.6876.120.1.0.41.0.1 - vmwNsxTNSXApplicationPlatformCommunicationMgrDisconnectedClear
1.3.6.1.4.1.6876.120.1.0.41.0.2 - vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.1 - vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.2 - vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.3 - vmwNsxTNSXApplicationPlatformHealthAnalyticsCPUUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.4 - vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.5 - vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.6 - vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.7 - vmwNsxTNSXApplicationPlatformHealthAnalyticsDiskUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.8 - vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.11 - vmwNsxTNSXApplicationPlatformHealthAnalyticsMemUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.12 - vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.9 - vmwNsxTNSXApplicationPlatformHealthAnalyticsMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.10 - vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.13 - vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.14 - vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.15 - vmwNsxTNSXApplicationPlatformHealthClusterCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.16 - vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.17 - vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.18 - vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.19 - vmwNsxTNSXApplicationPlatformHealthClusterDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.20 - vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.23 - vmwNsxTNSXApplicationPlatformHealthClusterMemUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.24 - vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.21 - vmwNsxTNSXApplicationPlatformHealthClusterMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.22 - vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHi
1.3.6.1.4.1.6876.120.1.0.43.0.31 - vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.32 - vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.33 - vmwNsxTNSXApplicationPlatformHealthConfigDbCPUUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.34 - vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.35 - vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.36 - vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.37 - vmwNsxTNSXApplicationPlatformHealthConfigDbDiskUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.38 - vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.109 - vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.110 - vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.39 - vmwNsxTNSXApplicationPlatformHealthConfigDbMemUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.40 - vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.41 - vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.42 - vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.43 - vmwNsxTNSXApplicationPlatformHealthDatastoreCPUUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.44 - vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.45 - vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.46 - vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.47 - vmwNsxTNSXApplicationPlatformHealthDatastoreDiskUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.48 - vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.51 - vmwNsxTNSXApplicationPlatformHealthDatastoreMemUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.52 - vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.49 - vmwNsxTNSXApplicationPlatformHealthDatastoreMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.50 - vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.53 - vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.54 - vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.55 - vmwNsxTNSXApplicationPlatformHealthMessagingCPUUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.56 - vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.57 - vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.58 - vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.59 - vmwNsxTNSXApplicationPlatformHealthMessagingDiskUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.60 - vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.63 - vmwNsxTNSXApplicationPlatformHealthMessagingMemUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.64 - vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.61 - vmwNsxTNSXApplicationPlatformHealthMessagingMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.62 - vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.97 - vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.98 - vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.99 - vmwNsxTNSXApplicationPlatformHealthMetricsCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.100 - vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHi
1.3.6.1.4.1.6876.120.1.0.43.0.101 - vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.102 - vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.103 - vmwNsxTNSXApplicationPlatformHealthMetricsDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.104 - vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHi
1.3.6.1.4.1.6876.120.1.0.43.0.105 - vmwNsxTNSXApplicationPlatformHealthMetricsMemUasgeHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.106 - vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.107 - vmwNsxTNSXApplicationPlatformHealthMetricsMemUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.108 - vmwNsxTNSXApplicationPlatformHealthNappStatusDegraded
1.3.6.1.4.1.6876.120.1.0.43.0.117 - vmwNsxTNSXApplicationPlatformHealthNappStatusDegradedClear
1.3.6.1.4.1.6876.120.1.0.43.0.118 - vmwNsxTNSXApplicationPlatformHealthNappStatusDown
1.3.6.1.4.1.6876.120.1.0.43.0.119 - vmwNsxTNSXApplicationPlatformHealthNappStatusDownClear
1.3.6.1.4.1.6876.120.1.0.43.0.120 - vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.65 - vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.66 - vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.67 - vmwNsxTNSXApplicationPlatformHealthNodeCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.68 - vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.69 - vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.70 - vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.71 - vmwNsxTNSXApplicationPlatformHealthNodeDiskUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.72 - vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.73 - vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.74 - vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.75 - vmwNsxTNSXApplicationPlatformHealthNodeMemoryUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.76 - vmwNsxTNSXApplicationPlatformHealthNodeStatusDegraded
1.3.6.1.4.1.6876.120.1.0.43.0.77 - vmwNsxTNSXApplicationPlatformHealthNodeStatusDegradedClear
1.3.6.1.4.1.6876.120.1.0.43.0.78 - vmwNsxTNSXApplicationPlatformHealthNodeStatusDown
1.3.6.1.4.1.6876.120.1.0.43.0.79 - vmwNsxTNSXApplicationPlatformHealthNodeStatusDownClear
1.3.6.1.4.1.6876.120.1.0.43.0.80 - vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.81 - vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.82 - vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHigh
1.3.6.1.4.1.6876.120.1.0.43.0.83 - vmwNsxTNSXApplicationPlatformHealthPlatformCPUUsageVeryHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.84 - vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.85 - vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.86 - vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.87 - vmwNsxTNSXApplicationPlatformHealthPlatformDiskUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.88 - vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHi
1.3.6.1.4.1.6876.120.1.0.43.0.91 - vmwNsxTNSXApplicationPlatformHealthPlatformMemUsageVeryHiClear
1.3.6.1.4.1.6876.120.1.0.43.0.92 - vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHigh
1.3.6.1.4.1.6876.120.1.0.43.0.89 - vmwNsxTNSXApplicationPlatformHealthPlatformMemoryUsageHighClear
1.3.6.1.4.1.6876.120.1.0.43.0.90 - vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded
1.3.6.1.4.1.6876.120.1.0.43.0.93 - vmwNsxTNSXApplicationPlatformHealthServiceStatusDegradedClear
1.3.6.1.4.1.6876.120.1.0.43.0.94 - vmwNsxTNSXApplicationPlatformHealthServiceStatusDown
1.3.6.1.4.1.6876.120.1.0.43.0.95 - vmwNsxTNSXApplicationPlatformHealthServiceStatusDownClear
1.3.6.1.4.1.6876.120.1.0.43.0.96 - vmwNsxTNodeAgentsHealthNodeAgentsDown
1.3.6.1.4.1.6876.120.1.0.12.0.3 - vmwNsxTNodeAgentsHealthNodeAgentsDownClear
1.3.6.1.4.1.6876.120.1.0.12.0.4 - vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPU
1.3.6.1.4.1.6876.120.1.0.12.0.5 - vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.12.0.6 - vmwNsxTPasswordManagementPasswordExpirationApproaching
1.3.6.1.4.1.6876.120.1.0.4.0.1 - vmwNsxTPasswordManagementPasswordExpirationApproachingClear
1.3.6.1.4.1.6876.120.1.0.4.0.2 - vmwNsxTPasswordManagementPasswordExpired
1.3.6.1.4.1.6876.120.1.0.4.0.3 - vmwNsxTPasswordManagementPasswordExpiredClear
1.3.6.1.4.1.6876.120.1.0.4.0.4 - vmwNsxTPasswordManagementPasswordIsAboutToExpire
1.3.6.1.4.1.6876.120.1.0.4.0.5 - vmwNsxTPasswordManagementPasswordIsAboutToExpireClear
1.3.6.1.4.1.6876.120.1.0.4.0.6 - vmwNsxTPhysicalServerPhysicalServerInstallFailed
1.3.6.1.4.1.6876.120.1.0.47.0.1 - vmwNsxTPhysicalServerPhysicalServerInstallFailedClear
1.3.6.1.4.1.6876.120.1.0.47.0.2 - vmwNsxTPhysicalServerPhysicalServerUninstallFailed
1.3.6.1.4.1.6876.120.1.0.47.0.3 - vmwNsxTPhysicalServerPhysicalServerUninstallFailedClear
1.3.6.1.4.1.6876.120.1.0.47.0.4 - vmwNsxTPhysicalServerPhysicalServerUpgradeFailed
1.3.6.1.4.1.6876.120.1.0.47.0.5 - vmwNsxTPhysicalServerPhysicalServerUpgradeFailedClear
1.3.6.1.4.1.6876.120.1.0.47.0.6 - vmwNsxTPolicyConstraintCreationCountLimitReached
1.3.6.1.4.1.6876.120.1.0.53.0.1 - vmwNsxTPolicyConstraintCreationCountLimitReachedClear
1.3.6.1.4.1.6876.120.1.0.53.0.2 - vmwNsxTRoutingBFDDownOnExternalInterface
1.3.6.1.4.1.6876.120.1.0.28.0.7 - vmwNsxTRoutingBFDDownOnExternalInterfaceClear
1.3.6.1.4.1.6876.120.1.0.28.0.8 - vmwNsxTRoutingBGPDown
1.3.6.1.4.1.6876.120.1.0.28.0.1 - vmwNsxTRoutingBGPDownClear
1.3.6.1.4.1.6876.120.1.0.28.0.2 - vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproaching
1.3.6.1.4.1.6876.120.1.0.28.0.39 - vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproachingClear
1.3.6.1.4.1.6876.120.1.0.28.0.40 - vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceeded
1.3.6.1.4.1.6876.120.1.0.28.0.41 - vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceededClear
1.3.6.1.4.1.6876.120.1.0.28.0.42 - vmwNsxTRoutingMaximumIPv4RouteLimitApproaching
1.3.6.1.4.1.6876.120.1.0.28.0.43 - vmwNsxTRoutingMaximumIPv4RouteLimitApproachingClear
1.3.6.1.4.1.6876.120.1.0.28.0.44 - vmwNsxTRoutingMaximumIPv4RouteLimitExceeded
1.3.6.1.4.1.6876.120.1.0.28.0.45 - vmwNsxTRoutingMaximumIPv4RouteLimitExceededClear
1.3.6.1.4.1.6876.120.1.0.28.0.46 - vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproaching
1.3.6.1.4.1.6876.120.1.0.28.0.47 - vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproachingClear
1.3.6.1.4.1.6876.120.1.0.28.0.48 - vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceeded
1.3.6.1.4.1.6876.120.1.0.28.0.49 - vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceededClear
1.3.6.1.4.1.6876.120.1.0.28.0.50 - vmwNsxTRoutingMaximumIPv6RouteLimitApproaching
1.3.6.1.4.1.6876.120.1.0.28.0.51 - vmwNsxTRoutingMaximumIPv6RouteLimitApproachingClear
1.3.6.1.4.1.6876.120.1.0.28.0.52 - vmwNsxTRoutingMaximumIPv6RouteLimitExceeded
1.3.6.1.4.1.6876.120.1.0.28.0.53 - vmwNsxTRoutingMaximumIPv6RouteLimitExceededClear
1.3.6.1.4.1.6876.120.1.0.28.0.54 - vmwNsxTRoutingOSPFNeighborWentDown
1.3.6.1.4.1.6876.120.1.0.28.0.11 - vmwNsxTRoutingOSPFNeighborWentDownClear
1.3.6.1.4.1.6876.120.1.0.28.0.12 - vmwNsxTRoutingProxyARPNotConfiguredForServiceIP
1.3.6.1.4.1.6876.120.1.0.28.0.13 - vmwNsxTRoutingProxyARPNotConfiguredForServiceIPClear
1.3.6.1.4.1.6876.120.1.0.28.0.14 - vmwNsxTRoutingRoutingDown
1.3.6.1.4.1.6876.120.1.0.28.0.9 - vmwNsxTRoutingRoutingDownClear
1.3.6.1.4.1.6876.120.1.0.28.0.10 - vmwNsxTRoutingStaticRoutingRemoved
1.3.6.1.4.1.6876.120.1.0.28.0.5 - vmwNsxTRoutingStaticRoutingRemovedClear
1.3.6.1.4.1.6876.120.1.0.28.0.6 - vmwNsxTSecurityCompliancePollEAL4NonCompliance
1.3.6.1.4.1.6876.120.1.0.56.0.1 - vmwNsxTSecurityCompliancePollEAL4NonComplianceClear
1.3.6.1.4.1.6876.120.1.0.56.0.2 - vmwNsxTSecurityCompliancePollNDcPPNonCompliance
1.3.6.1.4.1.6876.120.1.0.56.0.3 - vmwNsxTSecurityCompliancePollNDcPPNonComplianceClear
1.3.6.1.4.1.6876.120.1.0.56.0.4 - vmwNsxTSecurityComplianceTriggerEAL4NonCompliance
1.3.6.1.4.1.6876.120.1.0.56.0.5 - vmwNsxTSecurityComplianceTriggerEAL4NonComplianceClear
1.3.6.1.4.1.6876.120.1.0.56.0.6 - vmwNsxTSecurityComplianceTriggerNDcPPNonCompliance
1.3.6.1.4.1.6876.120.1.0.56.0.7 - vmwNsxTSecurityComplianceTriggerNDcPPNonComplianceClear
1.3.6.1.4.1.6876.120.1.0.56.0.8 - vmwNsxTServiceInsertionNewHostAdded
1.3.6.1.4.1.6876.120.1.0.14.0.7 - vmwNsxTServiceInsertionNewHostAddedClear
1.3.6.1.4.1.6876.120.1.0.14.0.8 - vmwNsxTServiceInsertionSVMHealthStatusDown
1.3.6.1.4.1.6876.120.1.0.14.0.23 - vmwNsxTServiceInsertionSVMHealthStatusDownClear
1.3.6.1.4.1.6876.120.1.0.14.0.24 - vmwNsxTServiceInsertionSVMHealthStatusUp
1.3.6.1.4.1.6876.120.1.0.14.0.25 - vmwNsxTServiceInsertionSVMHealthStatusUpClear
1.3.6.1.4.1.6876.120.1.0.14.0.26 - vmwNsxTServiceInsertionSVMLivenessStateDown
1.3.6.1.4.1.6876.120.1.0.14.0.27 - vmwNsxTServiceInsertionSVMLivenessStateDownClear
1.3.6.1.4.1.6876.120.1.0.14.0.28 - vmwNsxTServiceInsertionServiceChainPathDown
1.3.6.1.4.1.6876.120.1.0.14.0.21 - vmwNsxTServiceInsertionServiceChainPathDownClear
1.3.6.1.4.1.6876.120.1.0.14.0.22 - vmwNsxTServiceInsertionServiceDeploymentFailed
1.3.6.1.4.1.6876.120.1.0.14.0.9 - vmwNsxTServiceInsertionServiceDeploymentFailedClear
1.3.6.1.4.1.6876.120.1.0.14.0.10 - vmwNsxTServiceInsertionServiceDeploymentSucceeded
1.3.6.1.4.1.6876.120.1.0.14.0.11 - vmwNsxTServiceInsertionServiceDeploymentSucceededClear
1.3.6.1.4.1.6876.120.1.0.14.0.12 - vmwNsxTServiceInsertionServiceInsertionInfraStatusDown
1.3.6.1.4.1.6876.120.1.0.14.0.29 - vmwNsxTServiceInsertionServiceInsertionInfraStatusDownClear
1.3.6.1.4.1.6876.120.1.0.14.0.30 - vmwNsxTServiceInsertionServiceUndeploymentFailed
1.3.6.1.4.1.6876.120.1.0.14.0.15 - vmwNsxTServiceInsertionServiceUndeploymentFailedClear
1.3.6.1.4.1.6876.120.1.0.14.0.16 - vmwNsxTServiceInsertionServiceUndeploymentSucceeded
1.3.6.1.4.1.6876.120.1.0.14.0.17 - vmwNsxTServiceInsertionServiceUndeploymentSucceededClear
1.3.6.1.4.1.6876.120.1.0.14.0.18 - vmwNsxTTEPHealthFaultyTEP
1.3.6.1.4.1.6876.120.1.0.51.0.1 - vmwNsxTTEPHealthFaultyTEPClear
1.3.6.1.4.1.6876.120.1.0.51.0.2 - vmwNsxTTEPHealthFaultyTEPOnDPU
1.3.6.1.4.1.6876.120.1.0.51.0.3 - vmwNsxTTEPHealthFaultyTEPOnDPUClear
1.3.6.1.4.1.6876.120.1.0.51.0.4 - vmwNsxTTEPHealthTEPAutorecoverFailure
1.3.6.1.4.1.6876.120.1.0.51.0.5 - vmwNsxTTEPHealthTEPAutorecoverFailureClear
1.3.6.1.4.1.6876.120.1.0.51.0.6 - vmwNsxTTEPHealthTEPAutorecoverFailureOnDPU
1.3.6.1.4.1.6876.120.1.0.51.0.7 - vmwNsxTTEPHealthTEPAutorecoverFailureOnDPUClear
1.3.6.1.4.1.6876.120.1.0.51.0.8 - vmwNsxTTEPHealthTEPAutorecoverSuccess
1.3.6.1.4.1.6876.120.1.0.51.0.9 - vmwNsxTTEPHealthTEPAutorecoverSuccessClear
1.3.6.1.4.1.6876.120.1.0.51.0.10 - vmwNsxTTEPHealthTEPAutorecoverSuccessOnDPU
1.3.6.1.4.1.6876.120.1.0.51.0.11 - vmwNsxTTEPHealthTEPAutorecoverSuccessOnDPUClear
1.3.6.1.4.1.6876.120.1.0.51.0.12 - vmwNsxTTEPHealthTEPHaActivated
1.3.6.1.4.1.6876.120.1.0.51.0.13 - vmwNsxTTEPHealthTEPHaActivatedClear
1.3.6.1.4.1.6876.120.1.0.51.0.14 - vmwNsxTTEPHealthTEPHaActivatedOnDPU
1.3.6.1.4.1.6876.120.1.0.51.0.15 - vmwNsxTTEPHealthTEPHaActivatedOnDPUClear
1.3.6.1.4.1.6876.120.1.0.51.0.16 - vmwNsxTTransportNodeHealthLAGMemberDown
1.3.6.1.4.1.6876.120.1.0.18.0.5 - vmwNsxTTransportNodeHealthLAGMemberDownClear
1.3.6.1.4.1.6876.120.1.0.18.0.6 - vmwNsxTTransportNodeHealthLAGMemberDownOnDPU
1.3.6.1.4.1.6876.120.1.0.18.0.9 - vmwNsxTTransportNodeHealthLAGMemberDownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.18.0.10 - vmwNsxTTransportNodeHealthNVDSUplinkDown
1.3.6.1.4.1.6876.120.1.0.18.0.3 - vmwNsxTTransportNodeHealthNVDSUplinkDownClear
1.3.6.1.4.1.6876.120.1.0.18.0.4 - vmwNsxTTransportNodeHealthTransportNodeUplinkDown
1.3.6.1.4.1.6876.120.1.0.18.0.7 - vmwNsxTTransportNodeHealthTransportNodeUplinkDownClear
1.3.6.1.4.1.6876.120.1.0.18.0.8 - vmwNsxTTransportNodeHealthTransportNodeUplinkDownOnDPU
1.3.6.1.4.1.6876.120.1.0.18.0.11 - vmwNsxTTransportNodeHealthTransportNodeUplinkDownOnDPUClear
1.3.6.1.4.1.6876.120.1.0.18.0.12 - vmwNsxTVMCAppTransitConnectFailure
1.3.6.1.4.1.6876.120.1.0.50.0.1 - vmwNsxTVMCAppTransitConnectFailureClear
1.3.6.1.4.1.6876.120.1.0.50.0.2 - vmwNsxTVPNIPsecPolicyBasedSessionDown
1.3.6.1.4.1.6876.120.1.0.15.0.7 - vmwNsxTVPNIPsecPolicyBasedSessionDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.8 - vmwNsxTVPNIPsecPolicyBasedTunnelDown
1.3.6.1.4.1.6876.120.1.0.15.0.9 - vmwNsxTVPNIPsecPolicyBasedTunnelDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.10 - vmwNsxTVPNIPsecRouteBasedSessionDown
1.3.6.1.4.1.6876.120.1.0.15.0.11 - vmwNsxTVPNIPsecRouteBasedSessionDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.12 - vmwNsxTVPNIPsecRouteBasedTunnelDown
1.3.6.1.4.1.6876.120.1.0.15.0.13 - vmwNsxTVPNIPsecRouteBasedTunnelDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.14 - vmwNsxTVPNIPsecServiceDown
1.3.6.1.4.1.6876.120.1.0.15.0.17 - vmwNsxTVPNIPsecServiceDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.18 - vmwNsxTVPNL2VpnSessionDown
1.3.6.1.4.1.6876.120.1.0.15.0.15 - vmwNsxTVPNL2VpnSessionDownClear
1.3.6.1.4.1.6876.120.1.0.15.0.16
Groups and compliance
- vmwNsxTDataCenterBasicCompliance
- vmwNsxTDataCenterBasicCompliance10
- vmwNsxTDataCenterBasicCompliance11
- vmwNsxTDataCenterBasicCompliance12
- vmwNsxTDataCenterBasicCompliance13
- vmwNsxTDataCenterBasicCompliance14
- vmwNsxTDataCenterBasicCompliance2
- vmwNsxTDataCenterBasicCompliance3
- vmwNsxTDataCenterBasicCompliance4
- vmwNsxTDataCenterBasicCompliance5
- vmwNsxTDataCenterBasicCompliance6
- vmwNsxTDataCenterBasicCompliance7
- vmwNsxTDataCenterBasicCompliance8
- vmwNsxTDataCenterBasicCompliance9
- vmwNsxTDataCenterNotificationGroup
- vmwNsxTDataCenterNotificationGroup10
- vmwNsxTDataCenterNotificationGroup11
- vmwNsxTDataCenterNotificationGroup12
- vmwNsxTDataCenterNotificationGroup13
- vmwNsxTDataCenterNotificationGroup14
- vmwNsxTDataCenterNotificationGroup2
- vmwNsxTDataCenterNotificationGroup3
- vmwNsxTDataCenterNotificationGroup4
- vmwNsxTDataCenterNotificationGroup5
- vmwNsxTDataCenterNotificationGroup6
- vmwNsxTDataCenterNotificationGroup7
- vmwNsxTDataCenterNotificationGroup8
- vmwNsxTDataCenterNotificationGroup9
- vmwNsxTDataCenterNotificationInfoGroup
- vmwNsxTDataCenterNotificationInfoGroup10
- vmwNsxTDataCenterNotificationInfoGroup11
- vmwNsxTDataCenterNotificationInfoGroup12
- vmwNsxTDataCenterNotificationInfoGroup13
- vmwNsxTDataCenterNotificationInfoGroup14
- vmwNsxTDataCenterNotificationInfoGroup2
- vmwNsxTDataCenterNotificationInfoGroup3
- vmwNsxTDataCenterNotificationInfoGroup4
- vmwNsxTDataCenterNotificationInfoGroup6
- vmwNsxTDataCenterNotificationInfoGroup7
- vmwNsxTDataCenterNotificationInfoGroup8
- vmwNsxTDataCenterNotificationInfoGroup9