VMWARE-NSX-MANAGER-MIB
382 objects
This MIB file contains the information that the receiving party needs in order to interpret SNMP traps sent by NSX Manager. VMware NSX for vSphere is a key product in the SDDC architecture. With NSX, virtualization delivers for networking what it has already delivered for compute and storage. In much the same way that server virtualization programmatically creates, snapshots, deletes and restores software-based virtual machines (VMs), NSX network virtualization programmatically creates, snapshots, deletes, and restores software-based virtual networks. The result is a completely transformative approach to networking that not only enables data center managers to achieve orders of magnitude better agility and economics, but also allows for a vastly simplified operational model for the underlying physical network. With the ability to be deployed on any IP network, including both existing traditional networking models and next-generation fabric architectures from any vendor, NSX is a completely non-disruptive solution. In fact, with NSX, the physical network infrastructure you already have is all you need to deploy a software-defined data center. The NSX Manager provides the graphical user interface (GUI) and the REST APIs for creating, configuring, and monitoring NSX components, such as controllers, logical switches, and edge services gateways. The NSX Manager provides an aggregated system view and is the centralized network management component of NSX. NSX Manager is installed as a virtual appliance on any ESX host in your vCenter environment. Support requests can be filed with VMware using KB article: http://kb.vmware.com/kb/2006985 To reach NSX Manager Service Composer UI, login to vSphere UI(https://<vsphere-ip>)->Networking & Security->Service Composer
Imported Objects
| SNMPv2-CONF | MODULE-COMPLIANCE NOTIFICATION-GROUP OBJECT-GROUP |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-IDENTITY OBJECT-TYPE |
| SNMPv2-TC | DateAndTime TEXTUAL-CONVENTION |
| UUID-TC-MIB MISSING | UUID |
| VMWARE-ROOT-MIB | vmwNsxManager |
| OID | Name | Access | Status | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6876.90.1 | IdentityvmwNsxManagerMIB | This MIB file contains the information that the receiving party needs in order to interpret SNMP traps sent by NSX Manager. VMware NSX for vSphere is a key pro… | ||
| 1.3.6.1.4.1.6876.90.1.1 | IdentityvmwNsxMAlertData | current | This members of this group are the OIDs for VarBinds that contain data for ALL Alerts. | |
| 1.3.6.1.4.1.6876.90.1.1.1 | ScalarvmwNsxMEventCode | accessible-for-notify | current | The event code of the alert that was generated. To fetch a list of all the events with their code, severity and description please invoke the nsx-manager url h… |
| 1.3.6.1.4.1.6876.90.1.1.2 | ScalarvmwNsxMEventTimestamp | accessible-for-notify | current | The timestamp when the event was raised in the NSX Manager. |
| 1.3.6.1.4.1.6876.90.1.1.3 | ScalarvmwNsxMEventMessage | accessible-for-notify | current | This object provides a human readable description of the event or group of events |
| 1.3.6.1.4.1.6876.90.1.1.4 | ScalarvmwNsxMEventSeverity | accessible-for-notify | current | The severity for the event that was generated. The severity is pre-defined and can only be changed from the NSX Manager section of vsphere web client if the ad… |
| 1.3.6.1.4.1.6876.90.1.1.5 | ScalarvmwNsxMEventComponent | accessible-for-notify | current | The NSX manager component where this event was generated. |
| 1.3.6.1.4.1.6876.90.1.1.6 | ScalarvmwNsxMUuid | accessible-for-notify | current | The NSX manager UUID where this event was generated. |
| 1.3.6.1.4.1.6876.90.1.1.7 | ScalarvmwNsxMCount | accessible-for-notify | current | The count of the number of events for a particular group raised in the last 5 minute interval. |
| 1.3.6.1.4.1.6876.90.1.1.8 | ScalarvmwNsxMEventSourceID | accessible-for-notify | current | The object ID(s) of the source(s) of the event. |
| 1.3.6.1.4.1.6876.90.1.1.9 | ScalarvmwNsxMEventSourceType | accessible-for-notify | current | The object type(s) of the source(s) of the event. |
| 1.3.6.1.4.1.6876.90.1.1.10 | ScalarvmwNsxMEventSourceIP | accessible-for-notify | current | The IP address(es) of the source(s) of the event. |
| 1.3.6.1.4.1.6876.90.1.2 | IdentityvmwNsxMNotification | current | All notifications for NSX Manager use this oid prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.0 | IdentityvmwNsxMBranch | current | Branch segregated out for various groups and other future requirements. | |
| 1.3.6.1.4.1.6876.90.1.2.0.1 | IdentityvmwNsxMGroupsBranch | current | Grouped Notifications will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.0.1.0 | IdentityvmwNsxMGroupsPrefix | current | Prefix added to place zero in penultimate sub-identifier of group oids. | |
| 1.3.6.1.4.1.6876.90.1.2.0.1.0.1 | NotificationvmwNsxMConfigGroup | current | Configuration notifications that are grouped will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.1 | IdentityvmwNsxMSnmp | current | Notifications that are Snmp related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.1.0 | IdentityvmwNsxMSnmpPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Snmp module. | |
| 1.3.6.1.4.1.6876.90.1.2.1.0.1 | NotificationvmwNsxMSnmpDisabled | current | This notification is sent when the sending out of Snmp traps is disabled. This would most likely be the last Snmp trap the snmp manager receives. You may some … | |
| 1.3.6.1.4.1.6876.90.1.2.1.0.2 | NotificationvmwNsxMSnmpManagerConfigUpdated | current | This notification is sent when the snmp manager configuration has been updated. The event message will carry the semicolon separated new snmp managers' details… | |
| 1.3.6.1.4.1.6876.90.1.2.2 | IdentityvmwNsxMSecurity | current | Notifications that are security related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0 | IdentityvmwNsxMSecurityPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for security module. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.1 | NotificationvmwNsxMIpAddedBlackList | current | Whenever user authentication fails for number of times that user is blacklisted and further login attempts are disabled for that user from given IP address for… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.2 | NotificationvmwNsxMIpRemovedBlackList | current | After user is blacklisted, after blacklist duration expires, user is removed from blacklist. Action required: None Frequency of traps: Whenever blacklist durat… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.3 | NotificationvmwNsxMSsoConfigFailure | current | Whenever configuration of lookup service / SSO fails due to various reasons like invalid credentials, invalid configuration, time sync problem etc. Action requ… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.4 | NotificationvmwNsxMSsoUnconfigured | current | Whenever user unconfigures lookup service. Action required: None Frequency of traps: Once per unconfiguration event of lookup service. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.5 | NotificationvmwNsxMUserRoleAssigned | current | When role is assigned on NSX manager for vCenter user. Action required: None Frequency of traps: Once for each user who is assigned role. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.6 | NotificationvmwNsxMUserRoleUnassigned | current | When role is unassigned on NSX manager for vCenter user. Action: None Frequency of traps: Once for each user where role is removed. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.7 | NotificationvmwNsxMGroupRoleAssigned | current | When role is assigned on NSX manager for vCenter group. Action required: None Frequency of traps: Once for each group who is assigned role. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.8 | NotificationvmwNsxMGroupRoleUnassigned | current | When role is unassigned on NSX manager for vCenter group. Action required: None Frequency of traps: Once for each group where role is removed. | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.9 | NotificationvmwNsxMVcLoginFailed | current | Whenever Connection with vCenter starts failing due to invalid credentials. Action required: Reconfigure NSX Manager vCenter configuration with correct credent… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.10 | NotificationvmwNsxMVcDisconnected | current | Whenever there is disconnectivity for default VCenter Connection maintained by NSX. Action required: Administrator needs to check the connectivity with vCenter… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.11 | NotificationvmwNsxMLostVcConnectivity | current | Whenever there is disconnectivity for default VCenter Connection maintained by NSX. Action required: Administrator needs to check the connectivity with vCenter… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.12 | NotificationvmwNsxMSsoDisconnected | current | Whenever there is disconnection with SSO lookup service. Action required: Please check the configuration for possible disconnection reasons like Invalid Creden… | |
| 1.3.6.1.4.1.6876.90.1.2.2.0.13 | NotificationvmwNsxMSsoTimeout | current | When we try to configure VC on a system where SSO is already configured, we fetch the token to login to the VC using SSO. If it times out during that, this tra… | |
| 1.3.6.1.4.1.6876.90.1.2.3 | IdentityvmwNsxMFirewall | current | Notifications that are firewall related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0 | IdentityvmwNsxMFirewallPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for firewall module. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.1 | NotificationvmwNsxMFltrCnfgUpdateFailed | current | NSX Manager failed to enforce DFW. VMs on this host may not be protected by the DFW. Contextual data provided with this event may indicate the cause of this fa… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.2 | NotificationvmwNsxMFltrCnfgNotAppliedToVnic | current | NSX Manager failed to enforce DFW configuration on a vnic. This particular VM may not be protected by the DFW. Contextual data provided with this event may ind… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.3 | NotificationvmwNsxMFltrCnfgAppliedToVnic | current | Successfully updated filter config. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.4 | NotificationvmwNsxMFltrCreatedForVnic | current | Filter created. DFW is enforced in the datapath for the vnic. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.5 | NotificationvmwNsxMFltrDeletedForVnic | current | Filter deleted. DFW is removed from the vnic. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.6 | NotificationvmwNsxMFirewallConfigUpdateFailed | current | Firewall rule Configuration between the NSX Manager and the host is not in sync. Contextual data provided with this event may indicate the cause of this failur… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.7 | NotificationvmwNsxMFirewallRuleFailedVnic | current | Failed to apply Distributed Firewall configuration. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vmkern… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.8 | NotificationvmwNsxMFirewallRuleAppliedVnic | current | Applied firewall config. Key value will have context info like generation number and also other debugging info. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.9 | NotificationvmwNsxMCntnrCnfgUpdateFailed | current | Failed receive, parse or update the container configuration. Contextual data provided with this event may indicate the cause of this failure. Collect error log… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.10 | NotificationvmwNsxMFlowMissed | current | Flow missed. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vmkernel.log) when firewall configuration was… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.11 | NotificationvmwNsxMSpoofGuardCnfgUpdateFailed | current | Failed to receive, parse or Update the spoofguard configuration. Contextual data provided with this event may indicate the cause of this failure. Verify that t… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.12 | NotificationvmwNsxMSpoofGuardFailed | current | Failed to apply spoofguard to the vnic. Contextual data provided with this event may indicate the cause of this failure. Verify that vsip kernel heaps have eno… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.13 | NotificationvmwNsxMSpoofGuardApplied | current | Enabled spoofguard for vnic. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.14 | NotificationvmwNsxMSpoofGuardDisableFail | current | Failed to disable spoofguard on the vnic. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware.co… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.15 | NotificationvmwNsxMSpoofGuardDisabled | current | Disabled spoofguard for vnic. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.16 | NotificationvmwNsxMLegacyAppServiceDeletionFailed | current | A notification generated when legacy application service VM deletion failed. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.17 | NotificationvmwNsxMFirewallCpuThresholdCrossed | current | vsfwd CPU usage threshold was exceeded. Reduce the amount of traffic of VMs on the host in question. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.18 | NotificationvmwNsxMFirewallMemThresholdCrossed | current | vsfwd heap memory threshold exceeded for the specified heap. Reduce the number of of VMs on the host in question, reduce the number of rules or containers in f… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.19 | NotificationvmwNsxMConnPerSecThrshldCrossed | current | vsfwd Connectons Per Second (CPS) threshold exceeded for the specified vnic. Reduce the amount of new connections of VMs on the host in question. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.20 | NotificationvmwNsxMFirewallCnfgUpdateTimedOut | current | NSX Manager waits for 2 minutes after publishing the Firewall configuration to each host in the cluster. If a host takes more than 2 minutes to process the dat… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.21 | NotificationvmwNsxMSpoofGuardCnfgUpdateTmOut | current | NSX Manager waits for 2 minutes after publishing the Spoofguard configuration to each host in the cluster. If a host takes more than 2 minutes to process the d… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.22 | NotificationvmwNsxMFirewallPublishFailed | current | Firewall Configuration Publishing has failed for a given cluster/host. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsup… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.23 | NotificationvmwNsxMCntnrUpdatePublishFailed | current | Publishing of container (IP/MAC/vNIC) update pdate failed for a given host/cluster object. Please collect ESX and NSX Manager tech support bundle and open a SR… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.24 | NotificationvmwNsxMSpoofGuardUpdatePublishFailed | current | The publishing of the spoofguard updates on this host has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport.… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.25 | NotificationvmwNsxMExcludeListPublishFailed | current | The publishing of the exclude list or updates to the exclude list on this host has failed. Please collect ESX and NSX Manager tech support bundle and open a SR… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.26 | NotificationvmwNsxMFirewallCnfgUpdateOnDltCntnr | current | Deletion of the object referenced in firewall rules. Action required: Go to the NSX manager DFW UI. All the invalid reference are marked invalid on the UI as w… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.27 | NotificationvmwNsxMHostSyncFailed | current | Host-level force synchronization has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.vmware… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.28 | NotificationvmwNsxMHostSynced | current | Force Sync operation for host succeeded. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.29 | NotificationvmwNsxMFirewallInstalled | current | The Distributed Firewall was successfully Installed on the host. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.30 | NotificationvmwNsxMFirewallInstallFailed | current | The Distributed Firewall Installation has failed. Please collect ESX and NSX Manager tech support bundle and open a SR with Vmware techsupport. See http://kb.v… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.31 | NotificationvmwNsxMFirewallClusterInstalled | current | The Distributed Firewall has been installed at the request of a user. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.32 | NotificationvmwNsxMFirewallClusterUninstalled | current | The Distributed Firewall has been uninstalled at the request of a user. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.33 | NotificationvmwNsxMFirewallClusterDisabled | current | The Distributed Firewall has been disabeld on the cluster at the request of a user. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.34 | NotificationvmwNsxMFirewallForceSyncClusterFailed | current | Force Sync operation for the cluster has failed. Use CLI commands to look at the logs and verify if any error messages appeared during the operation. See kb.vm… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.35 | NotificationvmwNsxMFirewallForceSyncClusterSuccess | current | Force Sync operation for cluster succeeded. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.36 | NotificationvmwNsxMFirewallVsfwdProcessStarted | current | vsfwd process started on host. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.37 | NotificationvmwNsxMFirewallRulesetApplyAllFailed | current | Failure to apply all the rule section configuration. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vmker… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.38 | NotificationvmwNsxMFirewallRulesetAppliedAll | current | Successfully applied all rule section config. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.39 | NotificationvmwNsxMCntnrCnfgApplyFailedToVnic | current | Failure to apply the container configuration. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vmkernel.log… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.40 | NotificationvmwNsxMCntnrCnfgApplyAllFailedToVnic | current | Failure to apply all container configuration. Contextual data provided with this event may indicate the cause of this failure. Collect error logs (vmkernel.log… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.41 | NotificationvmwNsxMCntnrCnfgAppliedAllToVnic | current | Successfully applied all container config to all vnics. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.42 | NotificationvmwNsxMSpoofGuardApplyAllFailed | current | Failed to apply all spoofguard to the vnics. Contextual data provided with this event may indicate the cause of this failure. Verify that vsip kernel heaps hav… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.43 | NotificationvmwNsxMSpoofGuardAppliedAll | current | Applied all spoofguard for vnics. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.44 | NotificationvmwNsxMFirewallTimeoutUpdateFailed | current | Firewall session timer timeout configuration parse/update failed. Timeout values are unchanged. Contextual data provided with this event may indicate the cause… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.45 | NotificationvmwNsxMFirewallTimeoutApplyFailed | current | Firewall session timer timeout configuration apply failed. Certain timeout values are unchanged. Contextual data provided with this event may indicate the caus… | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.46 | NotificationvmwNsxMFirewallTimeoutApplied | current | Applied session timeout values for a vnic. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.47 | NotificationvmwNsxMFirewallTimeoutApplyAllFailed | current | Failed to apply all firewall session timer timeout configuration. Some timeout values are unchanged. Contextual data provided with this event may indicate the … | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.48 | NotificationvmwNsxMFirewallTimeoutAppliedAll | current | Applied session timeout values for all vnics. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.49 | NotificationvmwNsxMCntnrCnfgAppliedToVnic | current | Successfully applied container config to all vnics. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.50 | NotificationvmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossed | current | vsfwd maximum concurrent connections threshold was exceeded for the specified vnic. Reduce the amount of traffic on the vnic in question. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.51 | NotificationvmwNsxMFirewallProcessMemoryThresholdCrossed | current | vsfwd memory utilization threshold was exceeded for the specified process. Reduce the number of rules or containers in firewall config. If persists, there may … | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.52 | NotificationvmwNsxMFirewallCpuThresholdCrossCleared | current | vsfwd CPU usage is back to below threshold level. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.53 | NotificationvmwNsxMFirewallMemThresholdCrossCleared | current | vsfwd heap memory usage is back to below threshold level for the specified heap. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.54 | NotificationvmwNsxMConnPerSecThrshldCrossCleared | current | vsfwd Connectons Per Second (CPS) is back to below threshold level for the specified vnic. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.55 | NotificationvmwNsxMFirewallMaxConcurrentConnectionsThresholdCrossCleared | current | vsfwd maximum concurrent connections is back to below threshold level for the specified vnic. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.56 | NotificationvmwNsxMFirewallProcessMemoryThresholdCrossCleared | current | vsfwd memory utilization is back to below threshold level for the specified process. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.57 | NotificationvmwNsxMFirewallThresholdConfigApplied | current | Successfully applied all threshold config. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.58 | NotificationvmwNsxMFirewallThresholdConfigApplyFailed | current | Firewall threshold configuration apply failed. Certain threshold values are unchanged. Contextual data provided with this event may indicate the cause of this … | |
| 1.3.6.1.4.1.6876.90.1.2.3.0.59 | NotificationvmwNsxMUnsupportedIPsetConfigured | current | Whenever an IP address 0.0.0.0 or 0.0.0.0/32 is configured as IPSet. KB article: https://ikb.vmware.com/kb/53157 Action: Information-only event. No action requ… | |
| 1.3.6.1.4.1.6876.90.1.2.4 | IdentityvmwNsxMEdge | current | Notifications that are edge related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0 | IdentityvmwNsxMEdgePrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for edge module. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.1 | NotificationvmwNsxMEdgeNoVmServing | current | None of the Edge VMs found in serving state. There is a possibility of network disruption. Action required: System auto recovers from this state today. Event s… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.2 | NotificationvmwNsxMEdgeGatewayCreated | current | Edge Gateway created. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.3 | NotificationvmwNsxMEdgeVmBadState | current | Edge VM in bad state. Needs a force sync. Action required: System auto triggres force sync but if problem is sustained then manual force sync should be trigger… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.4 | NotificationvmwNsxMEdgeVmCommFailed | current | Failed to communicate with the Edge VM. Action required: Need investigation depending upon comunication channel. Log needs to be checked for VIX error code for… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.5 | NotificationvmwNsxMEdgeVmCnfgChanged | current | A notification generated when NSX Edge VM configuration is changed. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.6 | NotificationvmwNsxMEdgeGatewayDeleted | current | A notification generated when Edge Gateway is deleted. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.7 | NotificationvmwNsxMEdgeGatewayReDeployed | current | A notification generated when Edge Gateway is redeployed. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.8 | NotificationvmwNsxMEdgeVmPowerOff | current | A notification generated when NSX Edge VM is powered off. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.9 | NotificationvmwNsxMEdgeApplianceSizeChanged | current | A notification generated when Edge appliance size has changed. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.10 | NotificationvmwNsxMEdgeUpgrade51x | current | A notification generated when Edge Gateway is upgraded to 5.1.x. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.11 | NotificationvmwNsxMEdgeLicenseChanged | current | A notification generated when Edge licensing changed on vCenter Server. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.12 | NotificationvmwNsxMEdgeApplianceMoved | current | A notification generated when Edge appliance is moved in the vCenter inventory. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.13 | NotificationvmwNsxMEdgeApplianceNotFound | current | A notification generated when Edge appliance not found in the vCenter inventory. Action required: If VM is accidentally deleted, redeploy edge. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.14 | NotificationvmwNsxMEdgeVMHealthCheckMiss | current | A notification generated when Edge VM is not responding to health check. Action required: Communicaiton issues between manager and edge. Log analysis required … | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.15 | NotificationvmwNsxMEdgeHealthCheckMiss | current | A notification generated when none of the Edge VMs are found in serving state. There is a possibility of network disruption. Action required: Commnunicaiton is… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.16 | NotificationvmwNsxMEdgeCommAgentNotConnected | current | A notification generated when Edge Communication Agent is not connected to vCenter Server. Action required: Check VSM and VC connectivity. Try registering VSM … | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.17 | NotificationvmwNsxMApplianceWithDifferentId | current | A notification generated when Edge VM is discovered with a different vmId. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.18 | NotificationvmwNsxMFirewallRuleModified | current | A notification generated when Edge firewall rule is modified. Action required: Revisit firewall rule and perform required updates | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.19 | NotificationvmwNsxMEdgeAntiAffinityRuleViolated | current | A notification generated when powering on NSX Edge appliance violates a virtual machine anti-affinity rule. Action required: Anti affinity rules removed from c… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.20 | NotificationvmwNsxMEdgeHaEnabled | current | A notification generated when NSX Edge HighAvailability is enabled. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.21 | NotificationvmwNsxMEdgeHaDisabled | current | A notification generated when NSX Edge HighAvailability is disabled. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.22 | NotificationvmwNsxMEdgeGatewayRecovered | current | A notification generated when NSX Edge Gateway has recovered and now responding to health check. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.23 | NotificationvmwNsxMEdgeVmRecovered | current | A notification generated when NSX Edge VM has recovered and now responding to health check. Actione required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.24 | NotificationvmwNsxMEdgeGatewayUpgraded | current | A notification generated when Edge Gateway is upgraded. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.25 | NotificationvmwNsxMEdgeVmHlthChkDisabled | current | A notification generated when Edge VM health check is disabled on consecutive critical vix errors. Please redeploy or force sync vm to resume health check. Act… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.26 | NotificationvmwNsxMEdgePrePublishFailed | current | A notification generated when Pre Publish has failed on Edge VM. Action required: Firewall rules might be out of sync. System auto recovers but if problem pers… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.27 | NotificationvmwNsxMEdgeForcedSync | current | A notification generated when Edge VM was force synced. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.28 | NotificationvmwNsxMEdgeVmBooted | current | A notification generated when Edge VM was booted. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.29 | NotificationvmwNsxMEdgeVmInBadState | current | A notification generated when Edge VM is in Bad State. Needs a force sync. Action required: Force sync required. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.30 | NotificationvmwNsxMEdgeVmCpuUsageIncreased | current | A notification generated when Edge VM CPU usage has increased. Action required: Spikes are normal but collect tech support logs for further analysis if high CP… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.31 | NotificationvmwNsxMEdgeVmMemUsageIncreased | current | A notification generated when Edge VM Memory usage has increased. Action required: System recovers but collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.32 | NotificationvmwNsxMEdgeVmProcessFailure | current | A notification generated when Edge VM process monitor detects a process failure. Action required: System recovers but collect tech support logs for further ana… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.33 | NotificationvmwNsxMEdgeVmSysTimeBad | current | A notification generated when Edge VM system time is bad. Action required: System recovers. Check NTP setting on hosts. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.34 | NotificationvmwNsxMEdgeVmSysTimeSync | current | A notification generated when Edge VM system time sync up happens. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.35 | NotificationvmwNsxMEdgeAesniCryptoEngineUp | current | A notification generated when AESNI crypto engine is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.36 | NotificationvmwNsxMEdgeAesniCryptoEngineDown | current | A notification generated when AESNI crypto engine is down. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.37 | NotificationvmwNsxMEdgeVmOom | current | A notification generated when Edge VM is out of memory. The Edge is rebooting in 3 seconds. Action required: Collect tech support for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.38 | NotificationvmwNsxMEdgeFileSysRo | current | A notification generated when Edge file system is read only. Action required: Check datastore issues, once resolved force sync is required. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.39 | NotificationvmwNsxMEdgeHaCommDisconnected | current | A notification generated when Edge HighAvailability communication channel is disconnected from peer node. Action required: User will need to check network infr… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.40 | NotificationvmwNsxMEdgeHaSwitchOverSelf | current | A notification generated when High Availability is disabled for NSX Edge. The primary NSX Edge VM has its state transitioned from ACTIVE to SELF. High Availabi… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.41 | NotificationvmwNsxMEdgeHaSwitchOverActive | current | A notification generated when High Availability switch over has happened for NSX Edge. The secondary NSX Edge VM has its state transitioned from STANDBY to ACT… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.42 | NotificationvmwNsxMEdgeHaSwitchOverStandby | current | A notification generated when High Availability switch over has happened for NSX Edge. The primary NSX Edge VM has its state transitioned from ACTIVE to STANDB… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.43 | NotificationvmwNsxMEdgeMonitorProcessFailure | current | A notification generated when Edge process monitor detected a process failure. Action required: Collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.44 | NotificationvmwNsxMLbVirtualServerPoolUp | current | A notification generated when LoadBalancer virtualServer/pool is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.45 | NotificationvmwNsxMLbVirtualServerPoolDown | current | A notification generated when LoadBalancer virtualServer/pool is down. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.46 | NotificationvmwNsxMLbVirtualServerPoolWrong | current | A notification generated when LoadBalancer virtualServer/pool state is wrong. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.47 | NotificationvmwNsxMLbPoolWarning | current | A notification generated when LoadBalancer pool changed to a warning state. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.48 | NotificationvmwNsxMIpsecChannelUp | current | A notification generated when IPsec Channel is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.49 | NotificationvmwNsxMIpsecChannelDown | current | A notification generated when IPsec Channel is down. Action required: Collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.50 | NotificationvmwNsxMIpsecTunnelUp | current | A notification generated when IPsec Tunnel is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.51 | NotificationvmwNsxMIpsecTunnelDown | current | A notification generated when IPsec Tunnel is down. Action required: Collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.52 | NotificationvmwNsxMIpsecChannelUnknown | current | A notification generated when IPsec Channel status is unknown. Action required: Collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.53 | NotificationvmwNsxMIpsecTunnelUnknown | current | A notification generated when IPsec Tunnel status is unknown. Action required: Collect tech support logs for further analysis. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.54 | NotificationvmwNsxMGlobalLbMemberUp | current | A notification generated when Global Loadbalancer member status is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.55 | NotificationvmwNsxMGlobalLbMemberWarning | current | A notification generated when Global Loadbalancer member status is warning. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.56 | NotificationvmwNsxMGlobalLbMemberDown | current | A notification generated when Global Loadbalancer member status is down. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.57 | NotificationvmwNsxMGlobalLbMemberUnknown | current | A notification generated when Global Loadbalancer member status is unknown. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.58 | NotificationvmwNsxMGlobalLbPeerUp | current | A notification generated when Global Loadbalancer peer status is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.59 | NotificationvmwNsxMGlobalLbPeerDown | current | A notification generated when Global Loadbalancer peer status is down. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.60 | NotificationvmwNsxMDhcpServiceDisabled | current | A notification generated when DHCP Relay Service is disabled. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.61 | NotificationvmwNsxMEdgeResourceReservationFailure | current | Insufficient CPU and/or Memory Resources available on Host or Resource Pool, during resource reservation at the time of NSX Edge deployment. Resources are expl… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.62 | NotificationvmwNsxMEdgeSplitBrainDetected | current | Split Brain detected for NSX Edge with HighAvailability. NSX Edge VM's configured for High Availability are unable to determine if the other VM is alive due to… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.63 | NotificationvmwNsxMEdgeSplitBrainRecovered | current | Resolved Split Brain for NSX Edge with HighAvailability. The network path used by the NSX Edge VM's High Availability has been re-established. NSX Edge VM's ar… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.64 | NotificationvmwNsxMEdgeSplitBrainRecoveryAttempt | current | Attempted Split Brain resolution for NSX Edge. Split Brain recovery is being attempted on NSX Edge by NSX Manager. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.65 | NotificationvmwNsxMEdgeResourceReservationSuccess | current | User specified or system managed CPU and/or Memory Resource reservation for Edge VM is successful on Cluster or Resource Pool, during deployment/redeployment o… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.66 | NotificationvmwNsxMEdgeSddcChannelUp | current | VMCI communication channel to vmcd is up on specified NSX Edge. Action required: None Frequency: Once when the VMCI communication channel come up. URL: Nil | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.67 | NotificationvmwNsxMEdgeSddcChannelDown | current | VMCI communication channel to vmcd is down on specified NSX Edge. Action required: Check status of vmcd daemon process. Go to the ESX host and check vmcd statu… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.68 | NotificationvmwNsxMEdgeDuplicateIpDetected | current | The NSX Edge IP has been assigned to another device on the network. MAC address of the conflicting device is provided. Action required: Change the IP address o… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.69 | NotificationvmwNsxMEdgeDuplicateIpResolved | current | NSX Edge Duplicate IP address issue is resolved. Action required: None Frequency: Once when the Edge detects the duplication is resolved URL: Nil | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.70 | NotificationvmwNsxMEdgeBgpNeighborUp | current | Raised when BGP neighbor is up. BGP neighbor IP address in the eventSourceId tells us for which neighbor this event is getting raised. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.71 | NotificationvmwNsxMEdgeBgpNeighborDown | current | Raised when BGP neighbor is down. Once per neighbor. BGP neighbor IP address in the eventSourceId tells us for which neighbor this event is getting raised. Act… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.72 | NotificationvmwNsxMEdgeBgpNeighborASMismatch | current | Raised when there is a mismatch in AS number configured. Raised repeatedly when BGP neighbor is getting established. BGP neighbor IP address in the eventSource… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.73 | NotificationvmwNsxMEdgeOSPFNeighborUp | current | Raised when OSPF neighbor is up. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.74 | NotificationvmwNsxMEdgeOSPFNeighborDown | current | Raised when OSPF neighbor is down. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.75 | NotificationvmwNsxMEdgeOSPFNeighborMTUMismatch | current | Raised when there is a MTU mismatch in neighbor ship request. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. Act… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.76 | NotificationvmwNsxMEdgeOSPFNeighborAreaIdMisMatch | current | Raised when there is a areaId mismatch in neighbor ship request. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised. … | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.77 | NotificationvmwNsxMEdgeOSPFNeighborHelloTimerMisMatch | current | Raised when there is hello timer mismatch in neighbor ship request. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raise… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.78 | NotificationvmwNsxMEdgeOSPFNeighborDeadTimerMisMatch | current | Raised when there is dead timer mismatch in neighbor ship request. OSPF router Id in the eventSourceId tells us for which neighbor this event is getting raised… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.79 | NotificationvmwNsxMEdgeL2vpnTunnelUp | current | Raised when the l2vpn tunnel is up. Action required: None | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.80 | NotificationvmwNsxMEdgeL2vpnTunnelDown | current | Raised when the l2vpn tunnel is down. We can debug why the l2vpn tunnel is down using the following cli commands, show service l2vpn, show configuration l2vpn,… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.81 | NotificationvmwNsxMEdgeHAForceStandbyRemoved | current | A notification generated when forced standby for edge enforced by NSX Manager gets removed. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.82 | NotificationvmwNsxMEdgeHAForceStandbyRemovalFailed | current | Raised when the force standby removal for edge failed. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.83 | NotificationvmwNsxMEdgeVmBADStateRecovered | current | Raised when edge VM is recovered from bad state. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.84 | NotificationvmwNsxMEdgeVmBADStateAutoHealRecoveryDisabled | current | Raised when VM can not be recovered from bad state after system specified retry of auto recovery ForceSync operation. Action required: Trigger force sync to re… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.85 | NotificationvmwNsxMEdgeHaInUseVnicChanged | current | A notification generated when internally allocated vnic for HA internal communication is changed because vnic configurations have changed. Action required: Non… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.86 | NotificationvmwNsxMEdgeHaCommConnected | current | A notification generated when Edge HighAvailability communication channel is established with peer node. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.87 | NotificationvmwNsxMEdgeVmRenameFailed | current | Raised when Edge VM rename operation failed. Given Edge name has invalid characters or exceeds maximum number of characters permitted. There is no functionalit… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.88 | NotificationvmwNsxMEdgeBgpNeighborshipError | current | Raised when something goes wrong in neighborship establishment. Error message will have error code and sub error code. BGP neighbor IP address in the eventSour… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.89 | NotificationvmwNsxMEdgeVmBadStateNotRecovered | current | Raised when failed to recover NSX Edge VM from Bad State after force sync. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.90 | NotificationvmwNsxMEdgeVmDcnOutOfSync | current | Raised when GroupingObject sync is timed out on NSX Edge VM. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.91 | NotificationvmwNsxMEdgeConsumedResourcesMissingInInventory | current | Raised when missing or deleted resources from inventory are found used in NSX Edges. Action required: Please reconfigure these NSX Edges to use existing resour… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.92 | NotificationvmwNsxMEdgeIpsecDeprecatedComplianceSuiteInUse | current | Raised when a deprecated compliance suite is used in an IPSec site in NSX Edges. Action required: Please reconfigure IPSec site to use supported compliance sui… | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.93 | NotificationvmwNsxMEdgeConnectedToMultipleTZHavingSameClusters | current | Raised when a NSX Distributed Logical Router is connected to multiple transport zones having same clusters. Action required: None. | |
| 1.3.6.1.4.1.6876.90.1.2.4.0.94 | NotificationvmwNsxMEdgeConnectedToMultipleTZHavingDifferentClusters | current | Raised when a NSX Distributed Logical Router is connected to multiple transport zones having different clusters. This may cause network disruption on clusters … | |
| 1.3.6.1.4.1.6876.90.1.2.5 | IdentityvmwNsxMEndpoint | current | Notifications that are Endpoint related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0 | IdentityvmwNsxMEndpointPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Endpoint module. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.1 | NotificationvmwNsxMEndpointThinAgentEnabled | current | A notification generated when Thin agent is enabled. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.2 | NotificationvmwNsxMGuestIntrspctnEnabled | current | A notification generated when Guest Introspection solution is enabled. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.3 | NotificationvmwNsxMGuestIntrspctnIncompatibleEsx | current | A notification generated when Guest Introspection solution was contacted by an incompatible version of the ESX module. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.4 | NotificationvmwNsxMGuestIntrspctnEsxConnFailed | current | A notification generated when connection between the ESX module and the Guest Introspection solution failed. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.5 | NotificationvmwNsxMGuestIntrspctnStatusRcvFailed | current | A notification generated when failed to receive status from Guest Introspection solution. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.6 | NotificationvmwNsxMEsxModuleEnabled | current | A notification generated when ESX module is enabled. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.7 | NotificationvmwNsxMEsxModuleUninstalled | current | A notification generated when ESX module is uninstalled. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.8 | NotificationvmwNsxMGuestIntrspctnHstMxMssngRep | current | A notification generated when Guest Introspection host MUX is missing report. | |
| 1.3.6.1.4.1.6876.90.1.2.5.0.9 | NotificationvmwNsxMEndpointUndefined | current | A notification generated when Endpoint is undefined. | |
| 1.3.6.1.4.1.6876.90.1.2.6 | IdentityvmwNsxMEam | current | Notifications that are Eam related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.6.0 | IdentityvmwNsxMEamPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Eam module. | |
| 1.3.6.1.4.1.6876.90.1.2.6.0.1 | NotificationvmwNsxMEamGenericAlarm | current | EAM reports problems to NSX during vib/service VM install/upgrade as these traps. Action required: Use resolve API to resolve the Alarm. Frequency of traps: N … | |
| 1.3.6.1.4.1.6876.90.1.2.7 | IdentityvmwNsxMFabric | current | Notifications that are Fabric related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.7.0 | IdentityvmwNsxMFabricPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Fabric module. | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.1 | NotificationvmwNsxMFabricDplymntStatusChanged | current | The status of a service on a cluster has changed. It can change to RED(Failure), GREEN(Success), YELLOW(in-progress). Action required: RED state would be accom… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.2 | NotificationvmwNsxMFabricDplymntUnitCreated | current | NSX Manager has created the required objects for deploying a service on a cluster. This would be followed by deployment of the service on all hosts in the clus… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.3 | NotificationvmwNsxMFabricDplymntUnitUpdated | current | NSX Manager has made changes in the objects required for deploying a service on a cluster. This would be followed by updation of the service on all hosts in th… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.4 | NotificationvmwNsxMFabricDplymntUnitDestroyed | current | A service has been removed from all hosts in a cluster. NSX Manager has deleted the objects for the service on the cluster. Action required: None Frequency of … | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.5 | NotificationvmwNsxMDataStoreNotCnfgrdOnHost | current | Datastore could not be configured on host, probably its not connected. Action required: Ensure that datastore is connected to the host. Use resolve API to reso… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.6 | NotificationvmwNsxMFabricDplymntInstallationFailed | current | Installation of service failed, please check if ovf/vib urls are accessible, in correct format and all the properties in ovf environment have been configured i… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.7 | NotificationvmwNsxMFabricAgentCreated | current | The service has been successfully installed on a host. Action required: None Frequency of traps: N times per cluster, where N is number of hosts in a cluster. | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.8 | NotificationvmwNsxMFabricAgentDestroyed | current | The service has been successfully removed from a host. Action required: None Frequency of traps: N times per cluster, where N is number of hosts in a cluster. | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.9 | NotificationvmwNsxMFabricSrvceNeedsRedplymnt | current | Service will need to be redeployed as the location of the OVF / VIB bundles to be deployed has changed. Action required: Use resolve API to resolve the Alarm. … | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.10 | NotificationvmwNsxMUpgradeOfDplymntFailed | current | Upgrade of deployment unit failed, please check if ovf/vib urls are accessible, in correct format and all the properties in ovf environment have been configure… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.11 | NotificationvmwNsxMFabricDependenciesNotInstalled | current | The service being installed is dependent on another service that has not yet been installed. Action required: Deploy the required service on the cluster. Frequ… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.12 | NotificationvmwNsxMFabricErrorNotifSecBfrUpgrade | current | Error while notifying security solution before upgrade. The solution may not be reachable/responding. Action required: Ensure that solution urls are accessible… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.13 | NotificationvmwNsxMFabricErrCallbackNtRcvdUpgrade | current | Did not receive callback from security solution for upgrade notification even after timeout. Action required: Ensure that solution urls are accessible from NSX… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.14 | NotificationvmwNsxMFabricErrCallbackNtRcvdUninstall | current | Uninstallation of service failed. Action required: Ensure that solution urls are accessible from NSX, and NSX is reachable from the solution. Use resolve API t… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.15 | NotificationvmwNsxMFabricUninstallServiceFailed | current | Error while notifying security solution before uninstall. Resolve to notify once again, or delete to uninstall without notification. Action required: Ensure th… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.16 | NotificationvmwNsxMFabricErrorNotifSecBfrUninstall | current | Error while notifying security solution before uninstall. Resolve to notify once again, or delete to uninstall without notification. Action required: Ensure th… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.17 | NotificationvmwNsxMFabricServerRebootUninstall | current | Server rebooted while security solution notification for uninstall was going on. Action required: Ensure that solution urls are accessible from NSX. Use resolv… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.18 | NotificationvmwNsxMFabricServerRebootUpgrade | current | Server rebooted while security solution notification for upgrade was going on. Action required: Ensure that solution urls are accessible from NSX. Use resolve … | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.19 | NotificationvmwNsxMFabricConnEamFailed | current | NSX Manager relies on the ESX Agent Manager service in VC for deploying/monitoring NSX vibs on ESX. The connection to this EAM service has gone down. This coul… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.20 | NotificationvmwNsxMFabricConnEamRestored | current | NSX Manager relies on the EAM service in VC for deploying/monitoring NSX vibs on ESX. The connection of NSX to this EAM service was re-established successfully… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.21 | NotificationvmwNsxMFabricPreUninstallCleanUpFailed | current | Pre Uninstall cleanup failed. Action required: Use resolve API to resolve the Alarm. Service will be removed. Frequency of traps: Once per cluster per user ope… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.22 | NotificationvmwNsxMFabricBackingEamNotFound | current | The backing EAM agency for this deployment could not be found. It is possible that the VC services may still be initializing. Please try to resolve the alarm t… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.23 | NotificationvmwNsxMFabricVibManualInstallationRequired | current | This trap is generated when an attempt is made to upgrade or uninstall NSX vibs on stateless host using EAM. All stateless host should be prepared using the au… | |
| 1.3.6.1.4.1.6876.90.1.2.7.0.24 | NotificationvmwNsxMFabricUninstallDeploymentUnit | current | Deployment unit fabric state is UNINSTALLED and health Status is SUCCEEDED. Resolve this alarm to complete uninstallation. Frequency of traps: Once per cluster. | |
| 1.3.6.1.4.1.6876.90.1.2.8 | IdentityvmwNsxMDepPlugin | current | Notifications that are DeploymentPlugin related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.8.0 | IdentityvmwNsxMDepPluginPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for DeploymentPlugin module. | |
| 1.3.6.1.4.1.6876.90.1.2.8.0.1 | NotificationvmwNsxMDepPluginIpPoolExhausted | current | When deploying Guest Introspection or other VM based service with static IP, NSX Manager needs to have a IP pool, for IP assignment to the VM. This pool has be… | |
| 1.3.6.1.4.1.6876.90.1.2.8.0.2 | NotificationvmwNsxMDepPluginGenericAlarm | current | Deployment plugin generic alarm. Action required: Use resolve API to resolve the Alarm. Service will be deployed. Frequency of traps: N times per cluster, wher… | |
| 1.3.6.1.4.1.6876.90.1.2.8.0.3 | NotificationvmwNsxMDepPluginGenericException | current | Deployment plugin generic exception alarm. Action required: Use resolve API to resolve the Alarm. Service will be deployed. Frequency of traps: N times per clu… | |
| 1.3.6.1.4.1.6876.90.1.2.8.0.4 | NotificationvmwNsxMDepPluginVmReboot | current | VM needs to be rebooted for some changes to be made/take effect. Action required: Use resolve API to resolve the Alarm. Frequency of traps: N times per cluster… | |
| 1.3.6.1.4.1.6876.90.1.2.9 | IdentityvmwNsxMMessaging | current | Notifications that are Messaging related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.9.0 | IdentityvmwNsxMMessagingPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Messaging module. | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.1 | NotificationvmwNsxMMessagingConfigFailed | current | A notification generated when host messaging configuration failed. | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.2 | NotificationvmwNsxMMessagingReconfigFailed | current | A notification generated when host messaging connection reconfiguration failed. | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.3 | NotificationvmwNsxMMessagingConfigFailedNotifSkip | current | A notification generated when host messaging configuration failed and notifications were skipped. | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.4 | NotificationvmwNsxMMessagingInfraUp | current | Manager runs a heartbeat with all hosts it manages. Missing heartbeat responses from a host indicate a communication issue between manager and the host. Such i… | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.5 | NotificationvmwNsxMMessagingInfraDown | current | Manager runs a heartbeat with all hosts it manages. Missing heartbeat responses from a host indicate a communication issue between manager and the host. In the… | |
| 1.3.6.1.4.1.6876.90.1.2.9.0.6 | NotificationvmwNsxMMessagingDisabled | current | A messaging client such as a Host, an Edge appliance or a USVM appliance is expected to change its password within 2 hours of being prepped or deployed. If the… | |
| 1.3.6.1.4.1.6876.90.1.2.10 | IdentityvmwNsxMServiceComposer | current | Notifications that are ServiceComposer related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.10.0 | IdentityvmwNsxMServiceComposerPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for ServiceComposer module. | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.1 | NotificationvmwNsxMServiceComposerPolicyOutOfSync | current | Service Composer encountered an error while attempting to enforce rules on this Policy. Action required: Administrator needs to check the rules on the given Po… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.2 | NotificationvmwNsxMServiceComposerPolicyDeleted | current | A Policy got deleted as a result of the internal SecurityGroup, over which the Policy was created, got deleted. Frequency of traps: This event is generated onc… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.3 | NotificationvmwNsxMServiceComposerFirewallPolicyOutOfSync | current | Service Composer encountered an error while attempting to enforce Firewall rules on this Policy. Firewall related changes on this Policy will not take effect, … | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.4 | NotificationvmwNsxMServiceComposerNetworkPolicyOutOfSync | current | Service Composer encountered an error while attempting to enforce Network Introspection rules on this Policy. Network Introspection related changes on this Pol… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.5 | NotificationvmwNsxMServiceComposerGuestPolicyOutOfSync | current | Service Composer encountered an error while attempting to enforce Guest Introspection rules on this Policy. Guest Introspection related changes on this Policy … | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.6 | NotificationvmwNsxMServiceComposerOutOfSync | current | Service Composer encountered an error synchronizing Policies. Any changes on Service Composer will not be pushed to Firewall/Network Introspection Services, un… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.7 | NotificationvmwNsxMServiceComposerOutOfSyncRebootFailure | current | Service Composer encountered an error while synchronizing Policies on reboot. Action required: Administrator needs to check Policies and/or Firewall config for… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.8 | NotificationvmwNsxMServiceComposerOutOfSyncDraftRollback | current | Service Composer went out of sync due to rollback of drafts from Firewall. Any changes on Service Composer will not be pushed to Firewall/Network Introspection… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.9 | NotificationvmwNsxMServiceComposerOutOfSyncSectionDeletionFailure | current | Service Composer encountered an error while deleting the section corresponding to the Policy. This generally happens if third party(NetX) service's Manager is … | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.10 | NotificationvmwNsxMServiceComposerOutOfSyncPrecedenceChangeFailure | current | Service Composer encountered an error reordering sections to reflect Policy's precedence change. This generally happens if there are Alarms on any other Policy… | |
| 1.3.6.1.4.1.6876.90.1.2.10.0.11 | NotificationvmwNsxMServiceComposerOutOfSyncDraftSettingFailure | current | Service Composer encountered an error while initializing auto save drafts setting. Action required: Administrator needs to check Policies and/or Firewall secti… | |
| 1.3.6.1.4.1.6876.90.1.2.11 | IdentityvmwNsxMSvmOperations | current | Notifications that are SvmOperations related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.11.0 | IdentityvmwNsxMSvmOperationsPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for SvmOperations module. | |
| 1.3.6.1.4.1.6876.90.1.2.11.0.1 | NotificationvmwNsxMInconsistentSvmAlarm | current | Service VMs are deployed per ESX host, to provide functionality like guest introspection and McAfee/Trend virus checking in VMs on the host. An issue is detect… | |
| 1.3.6.1.4.1.6876.90.1.2.11.0.2 | NotificationvmwNsxMSvmRestartAlarm | current | Service VMs are deployed per ESX host, to provide functionality like guest introspection and McAfee/Trend virus checking in VMs on the host. An issue is detect… | |
| 1.3.6.1.4.1.6876.90.1.2.11.0.3 | NotificationvmwNsxMSvmAgentUnavailable | current | An issue is detected while marking agent as available. Kindly check the logs. Resolving this alarm will attempt to mark the agent as available. Action required… | |
| 1.3.6.1.4.1.6876.90.1.2.12 | IdentityvmwNsxMTranslation | current | Notifications that are Translation related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.12.0 | IdentityvmwNsxMTranslationPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Translation module. | |
| 1.3.6.1.4.1.6876.90.1.2.12.0.1 | NotificationvmwNsxMVmAddedToSg | current | A VM has got added to the SecurityGroup. Frequency of traps: Once for every VM getting added to any SecurityGroup. | |
| 1.3.6.1.4.1.6876.90.1.2.12.0.2 | NotificationvmwNsxMVmRemovedFromSg | current | A VM has got removed from the SecurityGroup. Frequency of traps: Once for every VM getting removed from any SecurityGroup. | |
| 1.3.6.1.4.1.6876.90.1.2.13 | IdentityvmwNsxMUniversalSync | current | Notifications that are UniversalSync related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.13.0 | IdentityvmwNsxMUniversalSyncPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for UniversalSync module. | |
| 1.3.6.1.4.1.6876.90.1.2.13.0.1 | NotificationvmwNsxMFullUniversalSyncFailed | current | A failure is encountered when doing full sync of universal objects on a secondary NSX manager. IP address of the secondary NSX manager is present in event's me… | |
| 1.3.6.1.4.1.6876.90.1.2.13.0.2 | NotificationvmwNsxMSecondaryDown | current | Secondary NSX manager is unreachable. Action required: Kindly check if NSX manager is running and is reachable from primary NSX manager. IP address of the seco… | |
| 1.3.6.1.4.1.6876.90.1.2.13.0.3 | NotificationvmwNsxMUniversalSyncFailedForEntity | current | A failure is encountered when doing sync of universal object on a secondary NSX manager. IP address of the secondary NSX manager is present in event's message … | |
| 1.3.6.1.4.1.6876.90.1.2.13.0.4 | NotificationvmwNsxMUniversalSyncStoppedOnSecondary | current | Secondary NSX manager is no longer receiving periodic universal sync updates. IP address of the NSX manager is present in event's message variable. Action requ… | |
| 1.3.6.1.4.1.6876.90.1.2.13.0.5 | NotificationvmwNsxMUniversalSyncResumedOnSecondary | current | Secondary NSX manager has resumed receiving periodic universal sync updates. Frequency of traps: This trap is generated whenever communication between primary … | |
| 1.3.6.1.4.1.6876.90.1.2.14 | IdentityvmwNsxMAsyncRest | current | Notifications that are AsyncRest related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.14.0 | IdentityvmwNsxMAsyncRestPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for AsyncRest module. | |
| 1.3.6.1.4.1.6876.90.1.2.14.0.1 | NotificationvmwNsxMServerUp | current | Denotes that NSX manager server is up and in running state, Informs clients of NSX Manager of the current state. Action required: None Frequency of traps: Once… | |
| 1.3.6.1.4.1.6876.90.1.2.15 | IdentityvmwNsxMExtensionRegistration | current | Notifications that are ExtensionRegistration related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.15.0 | IdentityvmwNsxMExtensionRegistrationPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for ExtensionRegistration module. | |
| 1.3.6.1.4.1.6876.90.1.2.15.0.1 | NotificationvmwNsxMExtensionRegistered | current | Registers NSX manager as a vCenter extenstion. This is applicable when no other NSX Manager is registered with vCenter and the current NSX manager is the one r… | |
| 1.3.6.1.4.1.6876.90.1.2.15.0.2 | NotificationvmwNsxMExtensionUpdated | current | Updates the vCenter extension registration with the new NSX Manager. This is applicable when there already exists another NSX manager that is registered as a v… | |
| 1.3.6.1.4.1.6876.90.1.2.16 | IdentityvmwNsxMDlp | current | Notifications that are Dlp related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.16.0 | IdentityvmwNsxMDlpPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Dlp module. | |
| 1.3.6.1.4.1.6876.90.1.2.16.0.1 | NotificationvmwNsxMDataSecScanStarted | current | A notification generated when NSX Data Security scan started on VirtualMachine. | |
| 1.3.6.1.4.1.6876.90.1.2.16.0.2 | NotificationvmwNsxMDataSecScanEnded | current | A notification generated when NSX Data Security scan ended on VirtualMachine. | |
| 1.3.6.1.4.1.6876.90.1.2.17 | IdentityvmwNsxMSamSystem | current | Notifications that are SamSystem related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.17.0 | IdentityvmwNsxMSamSystemPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for SamSystem module. | |
| 1.3.6.1.4.1.6876.90.1.2.17.0.1 | NotificationvmwNsxMSamDataCollectionEnabled | current | Service Activity Monitoring will start collecting data. Action required: None Frequency of traps: Event is triggered when SAM data collection state is toggled. | |
| 1.3.6.1.4.1.6876.90.1.2.17.0.2 | NotificationvmwNsxMSamDataCollectionDisabled | current | Service Activity Monitoring will stop collecting data. Action required: SAM data collection can be enabled to start collectiing data. Frequency of traps: Event… | |
| 1.3.6.1.4.1.6876.90.1.2.17.0.3 | NotificationvmwNsxMSamDataStoppedFlowing | current | Service Activity Monitoring data stopped flowing from USVM Action required: Check the following - USVM log to see if heartbeats are recieved and sent - is the … | |
| 1.3.6.1.4.1.6876.90.1.2.17.0.4 | NotificationvmwNsxMSamDataResumedFlowing | current | Service Activity Monitoring data resumes flowing from USVM Action required: None Frequency of traps: Event is triggered when SAM data is received from USVM. | |
| 1.3.6.1.4.1.6876.90.1.2.18 | IdentityvmwNsxMUsvm | current | Notifications that are Usvm related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.18.0 | IdentityvmwNsxMUsvmPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Usvm module. | |
| 1.3.6.1.4.1.6876.90.1.2.18.0.1 | NotificationvmwNsxMUsvmHeartbeatStopped | current | USVM stopped sending heartbeats to management plane. Action required: Connection to NSX Manager was lost. Check why the Manager didn't send a heartbeat. Freque… | |
| 1.3.6.1.4.1.6876.90.1.2.18.0.2 | NotificationvmwNsxMUsvmHeartbeatResumed | current | USVM will start sending heartbeats to management plane. Action required: None Frequency of traps: Event is triggered when NSX Manager receives heartbeats from … | |
| 1.3.6.1.4.1.6876.90.1.2.18.0.3 | NotificationvmwNsxMUsvmReceivedHello | current | USVM sent a HELLO message to Mux Action: None Frequency of traps: Event is triggered when Epsec Mux receives HELLO message from USVM during initial connection … | |
| 1.3.6.1.4.1.6876.90.1.2.19 | IdentityvmwNsxMVsmCore | current | Notifications that are VsmCore related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.19.0 | IdentityvmwNsxMVsmCorePrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for VsmCore module. | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.1 | NotificationvmwNsxMUpgradeSuccess | current | A notification generated when NSX Manager upgraded successfully. | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.2 | NotificationvmwNsxMRestoreSuccess | current | A notification generated when NSX Manager restored successfully. | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.3 | NotificationvmwNsxMDuplicateIp | current | The NSX Manager IP has been assigned to another machine Action: None Frequency: This is triggered whenever NSX Manager detects that its IP address is being use… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.4 | NotificationvmwNsxMVirtualMachineMarkedAsSystemResource | current | Virtual machine is marked as system resource Action: None Frequency: This is triggered whenever any virtual machine is marked as system resource | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.5 | NotificationvmwNsxMScaleAboveSupportedLimits | current | The scale value(s) of the mentioned parameter(s) has crossed the supported scale limits Action: Reduce the scale of the parameter(s) mentioned Frequency: This … | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.6 | NotificationvmwNsxMScaleAboveThreshold | current | The scale value(s) of the mentioned parameter(s) has crossed set threshold scale value Action: Reduce the scale of the parameter(s) mentioned Frequency: This i… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.7 | NotificationvmwNsxMScaleNormalized | current | The scale value(s) of the mentioned parameter(s) is back to normal after being above the set threshold or the supported value Action: No action required. Frequ… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.8 | NotificationvmwNsxMScaleNotEqualToRecommendedValue | current | The scale value(s) of the mentioned parameter(s) is not matching the recommended value Action: Increase/Decrease number of objects for the parameter(s) mention… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.10 | NotificationvmwNsxMCertificateExpired | current | Certificate with mentioned id has expired. Action: Replace expired certificate. Please refer to NSX Administration and API guide for details on certificate rel… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.11 | NotificationvmwNsxMCertificateAboutToExpire | current | Certificate with mentioned id will expire on mentioned date. Action: Replace expiring certificate. Please refer to NSX Administration and API guide for details… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.12 | NotificationvmwNsxMCPUHigh | current | NSX Manager CPU usage is currently high.CPU usage is based on load across all cores. Action: If NSX Manager is facing performance issue, please collect the tec… | |
| 1.3.6.1.4.1.6876.90.1.2.19.0.13 | NotificationvmwNsxMCPUNormal | current | NSX Manager CPU usage is back to normal.CPU usage is based on load across all cores. Action: None Frequency: This is triggered whenever NSX Manager CPU is belo… | |
| 1.3.6.1.4.1.6876.90.1.2.20 | IdentityvmwNsxMVxlan | current | Notifications that are Vxlan related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.20.0 | IdentityvmwNsxMVxlanPrefix | current | This group is actually the prefix one uses when creating vmware NSX manager specific trap OID's for Vxlan module. | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.1 | NotificationvmwNsxMVxlanLogicalSwitchImproperlyCnfg | current | This event is triggered if one or more distributed virtual port groups backing a certain Logical Switch were modified and/or removed. Or if migration of Contro… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.2 | NotificationvmwNsxMVxlanLogicalSwitchProperlyCnfg | current | Logical Switch status has been marked good, most probably as result of resolving any errors on it. Action required: None Frequency of traps: Event is triggered… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.3 | NotificationvmwNsxMVxlanInitFailed | current | Failed to configure vmknic as a VTEP, VXLAN traffic through this interface will be dropped until this is resolved. Action required: Check the host's vmkernel.l… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.4 | NotificationvmwNsxMVxlanPortInitFailed | current | Failed to configure VXLAN on the Distributed Virtual Port, the port will be disconnected. Action required: Check the host's vmkernel.log for more details. Freq… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.5 | NotificationvmwNsxMVxlanInstanceDoesNotExist | current | VXLAN configuration was received for a Distributed Virtual Port, but the host has not yet enabled VXLAN on the vSphere Distributed Switch. VXLAN ports on affec… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.6 | NotificationvmwNsxMVxlanLogicalSwitchWrkngImproperly | current | VTEP interface was unable to join the specified multicast address, the VTEP will be unable to receive some traffic from other hosts until this is resolved. The… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.7 | NotificationvmwNsxMVxlanTransportZoneIncorrectlyWrkng | current | The IP address of a VTEP vmknic has changed. Action required: None. Frequency of traps: Every time a VTEP IP changes | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.8 | NotificationvmwNsxMVxlanTransportZoneNotUsed | current | VTEP vmknic does not have a valid IP address assigned, all VXLAN traffic through this vmknic will be dropped. Action required: Verify the IP configuration for … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.9 | NotificationvmwNsxMVxlanOverlayClassMissingOnDvs | current | NSX packages where not installed prior to DVS configuration for VXLAN. All VXLAN ports will fail to connect until resolved. Action required: See KB 2107951 htt… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.10 | NotificationvmwNsxMVxlanControllerRemoved | current | A notification generated when VXLAN Controller has been removed due to the connection cant be built, please check controller IP configuration and deploy again. | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.11 | NotificationvmwNsxMVxlanControllerConnProblem | current | NSX manager detected the connection between two controller nodes is broken. Action required: It is a warning event, users need to check the controller cluster … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.12 | NotificationvmwNsxMVxlanControllerInactive | current | Host Certification information couldn't be sent to NSX Controllers. Action required: Ensure that NSX Controller cluster is in healthy state before preparing a … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.13 | NotificationvmwNsxMVxlanControllerActive | current | A notification generated when Controller cluster state is now active. Controller Synchronization job is in progress. Frequency of traps: Controller cluster bec… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.14 | NotificationvmwNsxMVxlanVmknicMissingOrDeleted | current | VXLAN vmknic is missing or deleted from host. Action required: Issue can be resolved from Logical Network Preparation - VXLAN Transport UI section. Clicking on… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.15 | NotificationvmwNsxMVxlanInfo | current | NSX Manager will raise this event when connection between either of the following component is established/re-established (i) connection between NSX Manager an… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.16 | NotificationvmwNsxMVxlanVmknicPortGrpMissing | current | NSX manager detected one vxlan vmknic is missing on VC. Action required: Check the host, if that vmknic is deleted, click on the resolve button on UI, or call … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.17 | NotificationvmwNsxMVxlanVmknicPortGrpAppears | current | NSX manager detected one vxlan vmknic that was marked as missing has now reappeared on VC. Action required: None Frequency of traps: When that missing vmknic r… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.18 | NotificationvmwNsxMVxlanConnDown | current | This event is triggered when either of the following connections are detected down by NSX Manager: (i) connection between NSX Manager and Host Firewall agent. … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.19 | NotificationvmwNsxMBackingPortgroupMissing | current | NSX manager detected one backing portgroup of a logical switch is missing on VCenter. Action required: Click on the resolve button on UI or call the API (POST … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.20 | NotificationvmwNsxMBackingPortgroupReappears | current | NSX manager detected one backing portgroup of a logical switch that was missing reappears on VC. Action required: None Frequency of traps: Whenever user trigge… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.21 | NotificationvmwNsxMManagedObjectIdChanged | current | NSX manager detected the Managed Objectid of one backing portgroup of a logical switch changed. Action required: None Frequnecy of traps: This typically happen… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.22 | NotificationvmwNsxMHighLatencyOnDisk | current | NSX manager detected some disk on a NSX Controller has high latency. Action required: Rectify the issue on specified device and controller. Frequency of traps:… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.23 | NotificationvmwNsxMHighLatencyOnDiskResolved | current | NSX manager detected the disk high latency alert on a some disk on a NSX Controller has been resolved. Frequency of traps: First time NSX detected, previously … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.24 | NotificationvmwNsxMControllerVmPoweredOff | current | NSX manager detected a Controller Virtual Machine is powered off from vCenter. Action required: Click on the 'Resolve' button on Controller page on UI or call … | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.25 | NotificationvmwNsxMControllerVmDeleted | current | NSX manager detected a Controller Virtual Machine is deleted from vCenter. Action required: Click on the Resolve button on Controller page on UI or call the AP… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.26 | NotificationvmwNsxMVxlanConfigNotSet | current | NSX manager detected the VXLAN configuration is not set on the host (would-block issue). And this event indicates NSX Manager tried to rectify this issue by re… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.27 | NotificationvmwNsxMVxlanPortgroupDeleted | current | NSX Manager will raise this event when a VXLAN portgroup is deleted from a switch. ACTION: User does not have to take any action. This is just a notification f… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.28 | NotificationvmwNsxMVxlanVDSandPgMismatch | current | DESCRIPTION: NSX Manager will raise this event when the teaming policies of a VDS and it's associated VXLAN portgroup are not the same. ACTION: Set the VXLAN p… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.29 | NotificationvmwNsxMVxlanControllerDisconnected | current | DESCRIPTION: NSX Manager raises this event when the Controller VM is Disconnected ie the controller can not reached from the NSX Manager. ACTION: Make sure the… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.30 | NotificationvmwNsxMVxlanControllerConnected | current | DESCRIPTION: NSX Manager will raise this informational event when the controller VM is connected to controller cluster. ACTION: No action to be taken. FREQUENC… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.31 | NotificationvmwNsxMVxlanControllerVmPoweredOn | current | DESCRIPTION: NSX manager detected a Controller Virtual Machine is powered on from vCenter. ACTION: None. FREQUENCY: This event occurs when Controller Virtual M… | |
| 1.3.6.1.4.1.6876.90.1.2.20.0.32 | NotificationvmwNsxMVxlanHostEvents | current | DESCRIPTION: NSX manager receives a notification from the host informing MAC mismatch occurred. ACTION: Contact the administrator to take following action: (1)… | |
| 1.3.6.1.4.1.6876.90.1.2.21 | IdentityvmwNsxMLogserver | current | Notifications that are Domain Controller Event Log server related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.21.0 | IdentityvmwNsxMLogserverPrefix | current | This group is the prefix one uses when creating vmware NSX manager specific trap OID's for VsmCore module. | |
| 1.3.6.1.4.1.6876.90.1.2.21.0.1 | NotificationvmwNsxMLogserverEventGenStopped | current | DESCRIPTION: This event is triggered if the security log on domain controller event log server is full. ACTION: See article regarding the issue : https://suppo… | |
| 1.3.6.1.4.1.6876.90.1.2.22 | IdentityvmwNsxMApplicationRuleManager | current | Notifications that are Application Rule Manager related will have this OID prefix. | |
| 1.3.6.1.4.1.6876.90.1.2.22.0 | IdentityvmwNsxMApplicationRuleManagerPrefix | current | This group is the prefix one uses when creating vmware NSX manager specific trap OID's for Application Rule Manager module. | |
| 1.3.6.1.4.1.6876.90.1.2.22.0.1 | NotificationvmwNsxMApplicationRuleManagerFlowAnalysisStart | current | Started flow analysis on Application Rule Manager session. Action required: None Frequency of traps:This trap is sent once for each session on which analysis h… | |
| 1.3.6.1.4.1.6876.90.1.2.22.0.2 | NotificationvmwNsxMApplicationRuleManagerFlowAnalysisFailed | current | Flow analysis failed on Application Rule Manager session. Contextual data provided with this event may indicate the cause of this failure. Action required: Sta… | |
| 1.3.6.1.4.1.6876.90.1.2.22.0.3 | NotificationvmwNsxMApplicationRuleManagerFlowAnalysisComplete | current | Completed flow analysis on Application Rule Manager session. Action required: None Frequency of traps:This trap is sent once for each session on which analysis… | |
| 1.3.6.1.4.1.6876.90.1.99 | NodevmwNsxManagerMIBConformance | |||
| 1.3.6.1.4.1.6876.90.1.99.1 | NodevmwNsxManagerMIBCompliances | |||
| 1.3.6.1.4.1.6876.90.1.99.1.3 | CompliancevmwNsxManagerMIBBasicCompliance | obsolete | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.1.4 | CompliancevmwNsxManagerMIB630Compliance | deprecated | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB | |
| 1.3.6.1.4.1.6876.90.1.99.1.5 | CompliancevmwNsxManagerMIB64Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB | |
| 1.3.6.1.4.1.6876.90.1.99.1.6 | CompliancevmwNsxManagerMIB636Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB | |
| 1.3.6.1.4.1.6876.90.1.99.1.7 | CompliancevmwNsxManagerMIB641Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB | |
| 1.3.6.1.4.1.6876.90.1.99.1.8 | CompliancevmwNsxManagerMIB637Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.1.9 | CompliancevmwNsxManagerMIB642Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.1.10 | CompliancevmwNsxManagerMIB645Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.1.11 | CompliancevmwNsxManagerMIB646Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.1.12 | CompliancevmwNsxManagerMIB647Compliance | current | The compliance statement for entities which implement VMWARE-NSX-MANAGER-MIB, see VMWARE-NSX-MANAGER-AGENTCAP-MIB. | |
| 1.3.6.1.4.1.6876.90.1.99.2 | NodevmwNsxManagerMIBGroups | |||
| 1.3.6.1.4.1.6876.90.1.99.2.2 | GroupvmwNsxManagerNotificationInfoGroup1 | current | These objects provide details in NSX Manager notifications. | |
| 1.3.6.1.4.1.6876.90.1.99.2.3 | GroupvmwNsxManagerNotificationGroup1 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.4 | GroupvmwNsxManagerNotificationGroup2 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.5 | GroupvmwNsxManagerNotificationGroup3 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.6 | GroupvmwNsxManagerNotificationGroup4 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.7 | GroupvmwNsxManagerNotificationGroup5 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.8 | GroupvmwNsxManagerNotificationGroup6 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.9 | GroupvmwNsxManagerNotificationGroup7 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.10 | GroupvmwNsxManagerNotificationGroup8 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.11 | GroupvmwNsxManagerNotificationGroup9 | current | Group of objects describing notifications (traps, informs). | |
| 1.3.6.1.4.1.6876.90.1.99.2.12 | GroupvmwNsxManagerNotificationGroup10 | current | Group of objects describing notifications (traps, informs). |
Type Definitions
| Name | Syntax | Status | Description |
|---|---|---|---|
| VmwNsxManagerSourceID | OCTET STRING (SIZE (0..256)) | current | The event sources' IDs for the NSX Manager system event. This data type can be used to specify multiple event source IDs seperated by a semicolon. In NSX Manager, we can have multiple event sources and hence multiple ev… |
| VmwNsxManagerSourceIPAddress | OCTET STRING (SIZE (0..256)) vmwNsxMAlertData OBJECT-IDENTITY STATUS current DESCRIPTION "This members of this group are the OIDs for VarBinds that contain data for ALL Alerts." ::= { vmwNsxManagerMIB 1 } vmwNsxMNotification OBJECT-IDENTITY STATUS current DESCRIPTION "All notifications for NSX Manager use this oid prefix." ::= { vmwNsxManagerMIB 2 } | current | The IP address(es) of the source(s) of the NSX Manager event. This data type can be used to specify multiple IP addresses seperated by a semicolon. Using InetAddress and InetAddressType from INET-ADDRESS-MIB would have … |
| VmwNsxManagerSourceType | OCTET STRING (SIZE (0..256)) | current | The event sources' types for the NSX Manager system event. This data type can be used to specify multiple event source types seperated by a semicolon. In NSX Manager, we can have multiple event sources and hence multipl… |
| VmwNsxManagerTypeSeverity | INTEGER { informational(1), low(2), medium(3), major(4), critical(5), high(6) } | current | Severity enumeration definition of NSX Manager events |