VMWARE-VRNI-MIB
This MIB module is for VMware Aria Operations for Networks as described here:
https://www.vmware.com/support/pubs/vrealize-network-insight-pubs.html
- Source file
VMWARE-VRNI-MIB- Last revised
- Identity
vmwNetworkInsightMIB- Base OID
1.3.6.1.4.1.6876.100.1
Imported Objects
| SNMP-FRAMEWORK-MIB | SnmpAdminString |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-IDENTITY (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | DateAndTime TEXTUAL-CONVENTION (no object page) |
| VMWARE-ROOT-MIB | vmwNetworkInsight |
| VMWARE-TC-MIB | VmwLongSnmpAdminString |
Net-SNMP examples using the vmware MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'VMWARE-VRNI-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-VRNI-MIB::vmwNetworkInsightMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'VMWARE-VRNI-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'VMWARE-VRNI-MIB::vmwNetworkInsightMIB'
Objects (15)
Showing 15 of 15 objects
Object legend
Table
Row
Column
Scalar
Node
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.6876.100.1 |
||
.1.3.6.1.4.1.6876.100.1.0 |
||
.1.3.6.1.4.1.6876.100.1.1 |
||
.1.3.6.1.4.1.6876.100.1.1.102 |
||
.1.3.6.1.4.1.6876.100.1.1.103 |
||
.1.3.6.1.4.1.6876.100.1.1.104 |
||
.1.3.6.1.4.1.6876.100.1.1.105 |
||
.1.3.6.1.4.1.6876.100.1.1.106 |
||
.1.3.6.1.4.1.6876.100.1.1.107 |
||
.1.3.6.1.4.1.6876.100.1.1.108 |
||
.1.3.6.1.4.1.6876.100.1.1.109 |
||
.1.3.6.1.4.1.6876.100.1.1.110 |
||
.1.3.6.1.4.1.6876.100.1.99 |
||
.1.3.6.1.4.1.6876.100.1.99.1 |
||
.1.3.6.1.4.1.6876.100.1.99.2 |
Dependencies (6) 6 direct Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-CONFrfc
- SNMPv2-TCrfc
- SNMP-FRAMEWORK-MIBrfc
- VMWARE-ROOT-MIBvmware
- VMWARE-TC-MIBvmware
- VMWARE-VRNI-MIBvmwareselected
Type Definitions (1)
| OctetString |
range: 0..255 |
Conformance Groups (20)
Compliance Statements (16)
OID
.1.3.6.1.4.1.6876.100.1.99.1.3The compliance statement for entities which implement
VMWARE-NSX-MANAGER-MIB.
VMWARE-NSX-MANAGER-MIB.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup1 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.30The compliance statement for entities which implement
VMWARE-VRNI-MIB second version.
VMWARE-VRNI-MIB second version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.35The compliance statement for entities which implement
VMWARE-VRNI-MIB second version.
VMWARE-VRNI-MIB second version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.45The compliance statement for entities which implement
VMWARE-VRNI-MIB second version.
VMWARE-VRNI-MIB second version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.60The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.70The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.80The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.90The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.100The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.110The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.120The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.130The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 | |
| mandatory | vmwNetworkInsightNotificationGroup12 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.140The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 | |
| mandatory | vmwNetworkInsightNotificationGroup12 | |
| mandatory | vmwNetworkInsightNotificationGroup13 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.150The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 | |
| mandatory | vmwNetworkInsightNotificationGroup12 | |
| mandatory | vmwNetworkInsightNotificationGroup13 | |
| mandatory | vmwNetworkInsightNotificationGroup14 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.160The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 | |
| mandatory | vmwNetworkInsightNotificationGroup12 | |
| mandatory | vmwNetworkInsightNotificationGroup13 | |
| mandatory | vmwNetworkInsightNotificationGroup14 | |
| mandatory | vmwNetworkInsightNotificationGroup15 |
OID
.1.3.6.1.4.1.6876.100.1.99.1.175The compliance statement for entities which implement
VMWARE-VRNI-MIB latest version.
VMWARE-VRNI-MIB latest version.
Required groups
| mandatory | vmwNetworkInsightNotificationInfoGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup1 | |
| mandatory | vmwNetworkInsightNotificationGroup2 | |
| mandatory | vmwNetworkInsightNotificationGroup3 | |
| mandatory | vmwNetworkInsightNotificationGroup4 | |
| mandatory | vmwNetworkInsightNotificationGroup5 | |
| mandatory | vmwNetworkInsightNotificationGroup6 | |
| mandatory | vmwNetworkInsightNotificationGroup7 | |
| mandatory | vmwNetworkInsightNotificationGroup8 | |
| mandatory | vmwNetworkInsightNotificationGroup9 | |
| mandatory | vmwNetworkInsightNotificationGroup10 | |
| mandatory | vmwNetworkInsightNotificationGroup11 | |
| mandatory | vmwNetworkInsightNotificationGroup12 | |
| mandatory | vmwNetworkInsightNotificationGroup13 | |
| mandatory | vmwNetworkInsightNotificationGroup14 | |
| mandatory | vmwNetworkInsightNotificationGroup15 | |
| mandatory | vmwNetworkInsightNotificationGroup16 |
Notifications / Traps (545)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.6876.100.1.0.100000 |
Latency No Data Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.100001 |
VMware Aria Operations for Networks Collector VM is not receiving network latency metrics from host.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100051 |
Number of VMs in VMC SDDC exceeds limit.
This event is raised when the number of VMs in a VMC SDDC exceeds limits. Delete VMs that are not in use. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100052 |
Number of Hosts in VMC SDDC exceeds limit.
This event is raised when the number of Hosts in a VMC SDDC exceeds limits. Contact VMC Support to increase the host limit within the VMC SDDC. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100053 |
This event is raised when the number of Hosts per Cluster in a VMC SDDC exceeds limit.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100054 |
This event is raised when the number of VMs per Host in a VMC SDDC exceeds limits.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100055 |
This event is raised when the number of Clusters in a VMC SDDC exceeds limits.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100056 |
This alert is raised for VMC on AWS when thresholds of an entity e.g Firewall Rule exceeds.
Please log in to VMC, navigate to listings page of entity type mentioned in the event description vmwOperatorDesc field. Then delete any unused entities to ensure uninterrupted operations. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.100061 |
This event is raised when any system protection limit is exceeded
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.101 |
Initial trap to notify receiver that VMware Aria Operations for Networks is now configured to send SNMP traps
|
|
.1.3.6.1.4.1.6876.100.1.0.102 |
Trap to notify receiver that VMware Aria Operations for Networks is no longer configured to send SNMP traps
|
|
.1.3.6.1.4.1.6876.100.1.0.103 |
Test Trap
|
|
.1.3.6.1.4.1.6876.100.1.0.110000 |
Link MTU Mismatch Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110001 |
Port Mode Mismatch Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110002 |
Port Trunk Mismatch Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110003 |
Port Channel Mismatch Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110004 |
Duplex Mismatch Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110005 |
Underlay Problem
|
|
.1.3.6.1.4.1.6876.100.1.0.110006 |
Switchport Problem
|
|
.1.3.6.1.4.1.6876.100.1.0.110007 |
Duplicate Mac Address Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110008 |
Duplicate IP Address Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110009 |
STP Path Cost Method Inconsistency Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110010 |
HSRP STP Colocation Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110011 |
Native VLAN ID configuration of the ports on each link should match.
Please check mismatch mentioned in the event vmwAffectedObject field and correct the configuration. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.110012 |
Native VLAN tagging of the ports on each link should match.
Please check mismatch mentioned in the event and correct the configuration. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.110013 |
Unable to load latest network map. The last successful network map snapshot was taken over 6 hours ago.
Network map functionality may show obsolete state. If this event persists, please contact VMware support. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.110014 |
HSRP Configuration Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.110015 |
VMware Aria Operations for Networks is experiencing high-system usage. Safe mode has been turned on automatically to keep the system protected and responsive.
Please contact VMware support to fix the problem. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.110016 |
Path Problem
|
|
.1.3.6.1.4.1.6876.100.1.0.110017 |
This alert is raised when incoming SNMP Trap is received by VMware Aria Operations for Networks.
|
|
.1.3.6.1.4.1.6876.100.1.0.111000 |
Invalid Intent Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.111001 |
Stig Account Passwd Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.111002 |
Stig Console Passwd Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.111003 |
Stig Default Passwd Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.111004 |
Stig Mgmt Passwd Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.111005 |
Stig Plaintext Passwd Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.115001 |
Loop Detection Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.115002 |
Reachability Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.115003 |
Segmentation Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.1277 |
BGP routes advertisement failed alert
|
|
.1.3.6.1.4.1.6876.100.1.0.1279 |
This event is raised when BGP status is Down.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.1509 |
Kubernetes Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.1510 |
Event reported by kubernetes cluster. This is Kubernetes System Event.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.20001 |
Discovery Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20002 |
Property Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20003 |
Firewall Not Installed On Host Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20004 |
Host With Stale Firewall Rules Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20005 |
Ip Address Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20006 |
L2 Gateway Anomaly Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20007 |
L2 Network Address Anomaly Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20008 |
L2 Network Diameter Exceeded Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20009 |
L2 Network Uplink Missing Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20010 |
L2 Network With No VMs Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20011 |
Layer2 Network Diameter Changed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20012 |
MTU Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20013 |
Network Isolation Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20014 |
No Path Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20015 |
Spoofguard Disabled Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20018 |
VMotion Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20019 |
VM With Disconnected Vnics Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20020 |
VM With Multiple Vnics On Different Vxlans Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20021 |
VM With Multiple Vnics On Same L2 Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20022 |
VM With No Ip Address Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20023 |
VTEP Missing Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20024 |
L2 Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20025 |
Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20026 |
Security Group Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20027 |
Firewall Rule Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20028 |
Vlan Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20029 |
Vxlan Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20030 |
Delete Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20031 |
VTEP Ping Failure Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20034 |
Search with no results
|
|
.1.3.6.1.4.1.6876.100.1.0.20035 |
Search results changed
|
|
.1.3.6.1.4.1.6876.100.1.0.20036 |
Search with no results (Problem)
|
|
.1.3.6.1.4.1.6876.100.1.0.20037 |
Search results changed (Problem)
|
|
.1.3.6.1.4.1.6876.100.1.0.20038 |
OSPF Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20039 |
Service VM Not Healthy Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20040 |
Service VM Not Powered On Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20041 |
Service VM High CPU Usage Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20042 |
Service VM High Memory Usage Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20043 |
Service VM High Disk Usage Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20050 |
IPSet Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20051 |
Firewall Rule Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20052 |
Security Group Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20053 |
IPSet Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20054 |
Firewall Rule Masked Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20056 |
Security Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20057 |
Security Tag Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20058 |
Security Tag Membership Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20059 |
Host datastores changed
|
|
.1.3.6.1.4.1.6876.100.1.0.20060 |
VM datastores changed
|
|
.1.3.6.1.4.1.6876.100.1.0.20061 |
VM snapshot changed
|
|
.1.3.6.1.4.1.6876.100.1.0.20062 |
Virtual disk migrated
|
|
.1.3.6.1.4.1.6876.100.1.0.20063 |
IPSET Definition Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20064 |
Segment Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20065 |
Vtep Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20066 |
Vtep Configuration Fault Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20067 |
DLR Routing event
|
|
.1.3.6.1.4.1.6876.100.1.0.20068 |
Vtep Subnet Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20069 |
Vtep Count Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20070 |
Edge Routing event
|
|
.1.3.6.1.4.1.6876.100.1.0.20089 |
NI Infra Change
|
|
.1.3.6.1.4.1.6876.100.1.0.20090 |
Data Source Enabled
|
|
.1.3.6.1.4.1.6876.100.1.0.20091 |
Data Source Disabled
|
|
.1.3.6.1.4.1.6876.100.1.0.20092 |
Data Source Created
|
|
.1.3.6.1.4.1.6876.100.1.0.20093 |
Platform CPU Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20094 |
Platform Disk Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20095 |
Platform Memory Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20096 |
Platform Reboot Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20097 |
Collector CPU Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20098 |
Collector Disk Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20099 |
Collector Memory Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20100 |
Collector Reboot Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20101 |
Cluster Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20102 |
System Proxy Change Event
|
|
.1.3.6.1.4.1.6876.100.1.0.20103 |
Cluster Create Event
|
|
.1.3.6.1.4.1.6876.100.1.0.2503 |
Passthrough Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.30001 |
Threshold Exceeded Cpu Ready
|
|
.1.3.6.1.4.1.6876.100.1.0.30002 |
Threshold Exceeded Cpu Co Stop
|
|
.1.3.6.1.4.1.6876.100.1.0.30003 |
Threshold Exceeded Disk Command Abort Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30004 |
Threshold Exceeded IO Device Latency Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30005 |
Threshold Exceeded IO Kernel Latency Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30006 |
Threshold Exceeded Memory Swap In Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30007 |
Threshold Exceeded Memory Swap Out Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30008 |
Threshold Exceeded Memory Rx Drop Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30009 |
Threshold Exceeded Memory Tx Drop Rule
|
|
.1.3.6.1.4.1.6876.100.1.0.30010 |
AWS Region Security Group count near threshold.
|
|
.1.3.6.1.4.1.6876.100.1.0.30011 |
AWS VPC Security Group count near threshold.
|
|
.1.3.6.1.4.1.6876.100.1.0.30012 |
AWS Security Group Inbound Rule count near threshold.
|
|
.1.3.6.1.4.1.6876.100.1.0.30013 |
AWS Security Group Outbound Rule count near threshold.
|
|
.1.3.6.1.4.1.6876.100.1.0.30014 |
AWS VPC Security Group count near threshold.
|
|
.1.3.6.1.4.1.6876.100.1.0.30100 |
Packet Drop Event
|
|
.1.3.6.1.4.1.6876.100.1.0.30101 |
Switch Port Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30102 |
Router Interface Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30103 |
Vnic Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30104 |
VTEP Underlay Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30105 |
PNIC Underlying Switch Port Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30106 |
Device Packet Drop
|
|
.1.3.6.1.4.1.6876.100.1.0.30107 |
Switch Port Buffer Threshold Exceeded Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.30108 |
Router Interface Buffer Threshold Exceeded Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.30109 |
Buffer Threshold Exceeded Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.30110 |
Up time of switch is less than expected.
Check the operational status of the specified switch port. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30111 |
Switchport operational status change detected. It is operationally down. This may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30112 |
Router interface operational status change detected. It is operationally down. This may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30113 |
Port Operational Down Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.30114 |
This is generic representation for events on Underlay device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30115 |
A FEX has gone offline on the device. Please check the FEX status on the device. This may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30116 |
A fan on the device is not either removed or not working. It may impact the overheating of the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30117 |
A module on the device has reported major/minor temperature alarm. Please check the sensor mentioned in the event message on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30118 |
A fan on the FEX chassis is either removed or not working. It may impact the overheating of the FEX device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30119 |
A Power supply on the FEX chassis is either removed or not working. It may impact the FEX device functionality.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30120 |
A module/line card on the device is either removed or not working. This may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30121 |
A Power supply on the device is either removed or not working. It may impact the device functionality.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30122 |
A BFD session is deleted on the device. This will result in routing table changes and may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30123 |
A LLDP neighbour is removed from the device. This will result in the network topology changes and may impact the network traffic on the device.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30124 |
uRPF packet drop ratio is high for switch port. Please check uRPF packet drop on the interface.
|
|
.1.3.6.1.4.1.6876.100.1.0.30198 |
A threshold-crossing CPU usage detected on host FRUs.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30199 |
A threshold-crossing memory usage detected on host FRUs.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30200 |
A threshold-crossing temperature detected on host FRUs.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.30203 |
ThresholdExceededEventDatastoreFreeSpaceWarning
|
|
.1.3.6.1.4.1.6876.100.1.0.30204 |
ThresholdExceededEventDatastoreFreeSpaceCritical
|
|
.1.3.6.1.4.1.6876.100.1.0.30205 |
ThresholdExceededEventDatastoreReadLatency
|
|
.1.3.6.1.4.1.6876.100.1.0.30206 |
ThresholdExceededEventDatastoreWriteLatency
|
|
.1.3.6.1.4.1.6876.100.1.0.35001 |
Distributed Firewall Apply Host Event
|
|
.1.3.6.1.4.1.6876.100.1.0.35002 |
Distributed Firewall Apply VM Event
|
|
.1.3.6.1.4.1.6876.100.1.0.35003 |
NSX Event
|
|
.1.3.6.1.4.1.6876.100.1.0.35004 |
Feature Impacted Event
|
|
.1.3.6.1.4.1.6876.100.1.0.35221 |
NSX Service not running event
|
|
.1.3.6.1.4.1.6876.100.1.0.35222 |
NSX Backup not configured
|
|
.1.3.6.1.4.1.6876.100.1.0.35223 |
Audit Log excluded from NSX Backup
|
|
.1.3.6.1.4.1.6876.100.1.0.35224 |
NSX Backups not using secure FTP
|
|
.1.3.6.1.4.1.6876.100.1.0.35225 |
System Event excluded from NSX Backup
|
|
.1.3.6.1.4.1.6876.100.1.0.35226 |
Scheduled backups are not enabled
|
|
.1.3.6.1.4.1.6876.100.1.0.35227 |
No backup of the environment has been recorded
|
|
.1.3.6.1.4.1.6876.100.1.0.35228 |
NTP Server not configured
|
|
.1.3.6.1.4.1.6876.100.1.0.35229 |
Syslog Server not configured
|
|
.1.3.6.1.4.1.6876.100.1.0.35230 |
Syslog Server not configured
|
|
.1.3.6.1.4.1.6876.100.1.0.35231 |
IPv6 is enabled for NSX Manager
|
|
.1.3.6.1.4.1.6876.100.1.0.35232 |
One or more OSPF Neighbors down
|
|
.1.3.6.1.4.1.6876.100.1.0.3558 |
These are the alarms/events reported by NSXALB platform.
You can see these alerts in NSX ALB platform under Operations -> All alerts. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.36022 |
Cluster Feature Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36023 |
Host Feature Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36024 |
Feature Version Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36025 |
Feature Enabled Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36026 |
Feature Installed Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36027 |
Host Vtep Not Found Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36028 |
Host Vtep Disconnected Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36029 |
Host Vtep Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36030 |
Host Vtep Mtu Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36031 |
Feature Health Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36032 |
NSX Edge High Availability is not enabled Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36033 |
One or More NSX Edge Interfaces are down Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36041 |
Module Unhealthy Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36042 |
Module Not Loaded Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36043 |
Module Network Connection Failure Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36044 |
Control Plane Network Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36045 |
Control Plane Network Connection Failure Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36046 |
Host Control Plane Sync Failure Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36047 |
NSX Controller Cluster Majority Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36048 |
NSX Controllers VM On Same Host Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36049 |
Vxlan range exhaust Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36050 |
NSX Firewall Allow All Rules Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36051 |
The NSX DLR is not configured with default route and may prevent external communication.
Check if the router configuration is only for routing between internal networks, or if external access is required. If external access is required, then configure an uplink interface on the NSX distributed logical router. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.36052 |
NSX Edge not Highly Available Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36053 |
NSX Edge not deployed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36054 |
NSX Edge Running with both ECMP and Stateful Edge Services Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36055 |
Logical Router and ECMP Edge on Same Host Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36056 |
NSX Edge Interface to OSPF Area Mapping Missing Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36057 |
One or more OSPF areas on the NSX Edge are using insecure authentication Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36058 |
NSX Controller count Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36059 |
NSX Controller Not Active Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36060 |
NSX Controller Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36061 |
One or more NSX Edges in the ECMP Cluster are currently down
|
|
.1.3.6.1.4.1.6876.100.1.0.36062 |
The majority of NSX Edges in the ECMP Cluster are currently down
|
|
.1.3.6.1.4.1.6876.100.1.0.36063 |
All NSX Edges in the ECMP Cluster are currently down
|
|
.1.3.6.1.4.1.6876.100.1.0.36064 |
The MTU configured on one or more interfaces on the Edge does not match the MTU on the next hop router
|
|
.1.3.6.1.4.1.6876.100.1.0.36065 |
Both VMs of Edge HA are in active state
|
|
.1.3.6.1.4.1.6876.100.1.0.36066 |
VDR Port Unset Event
|
|
.1.3.6.1.4.1.6876.100.1.0.36067 |
One or more BGP neighbours are not in established state.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.37001 |
Meta event for Analytics Event
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.37002 |
Meta event for Outlier Events
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events. |
|
.1.3.6.1.4.1.6876.100.1.0.37003 |
Meta event for Threshold Events
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.37004 |
Alert generated as a result of the specified combination of metric crosses the upper or lower bound specified in the configuration.
Please check details and remediation steps mentioned in alert. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.37005 |
Threshold Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.37006 |
Alert generated as a result of the specified combination of metric crosses the upper or lower bound specified in the configuration.
Please check details and remediation steps mentioned in alert. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.38001 |
Meta event for VMC Events.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.38003 |
This alert is raised when SDDC within SDDC Group loses connectivity with VTGW(VMware Transit Gateway).
Please contact VMC on AWS Support. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.38004 |
VTGW Duplicate Routes Event
|
|
.1.3.6.1.4.1.6876.100.1.0.400 |
Intent Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40000 |
PNIC Rx Network Usage Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40001 |
Host with VMs running critical services is not accessible
|
|
.1.3.6.1.4.1.6876.100.1.0.40002 |
PNIC Tx Network Usage Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40003 |
PNIC Rx Network Usage Critical Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40004 |
PNIC Tx Network Usage Critical Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40005 |
Management Host High CPU Usage
|
|
.1.3.6.1.4.1.6876.100.1.0.40006 |
Management Host High CPU Usage
|
|
.1.3.6.1.4.1.6876.100.1.0.40007 |
Host Unhealthy Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40008 |
NSX Controller Filesystem Disk Available Threshold Receded Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40011 |
Edge VM VNIC Rx Packet Drop Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40012 |
Edge VM VNIC Tx Packet Drop Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40013 |
Host pNIC Rx Packet Drop Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40014 |
Host pNIC Tx Packet Drop Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.40015 |
Management Host Connection State Disconnected Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.568 |
Number of members in application exceeds supported limit.
Reduce number of members in the application. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.70000 |
NSX System Event (Warning)
|
|
.1.3.6.1.4.1.6876.100.1.0.70001 |
Filter Config Apply On Host Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70002 |
Ruleset Load On Host Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70003 |
Config Update On Host Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70004 |
Spoofguard Config Update On Host Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70005 |
Apply Rule To Vnic Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70006 |
Container Config Update On Vnic Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70007 |
Spoofguard Apply To Vnic Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70008 |
Host Messaging Configuration Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70009 |
Host Messaging Connection Reconfiguration Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70010 |
Host Messaging Configuration Failed Notification Skipped Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70011 |
Host Messaging Infrastructure Down Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70012 |
Edge VM Responding Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70013 |
Edge Health Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70014 |
Edge communication failure Event
|
|
.1.3.6.1.4.1.6876.100.1.0.70015 |
NSX Edge Event
|
|
.1.3.6.1.4.1.6876.100.1.0.71000 |
NSX System Event (Critical)
|
|
.1.3.6.1.4.1.6876.100.1.0.80000 |
Palo Alto Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80001 |
Palo Alto NSX Registration Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80002 |
Palo Alto NSX Dynamic Update Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80003 |
Palo Alto Device Disconnect Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80004 |
Palo Alto Service Device Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80005 |
NSX Fabric Agent Not Found Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80006 |
Palo Alto Service VM Not Found Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80050 |
Dropped flows are detected on Palo Alto device through VMware Aria Operations for Logs.
|
|
.1.3.6.1.4.1.6876.100.1.0.80051 |
Dropped flows are detected on Check Point device through VMware Aria Operations for Logs.
|
|
.1.3.6.1.4.1.6876.100.1.0.80100 |
Check Point Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80102 |
Check Point NSX Fabric Agent Not Found Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80103 |
Check Point Service VM Not Found Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80104 |
Check Point Gateway Sic Status Not Communicating Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80105 |
Check Point Service VM Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80200 |
NSX-T Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80201 |
VC Not Added As Data Source Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80202 |
Standalone hosts added in NSX-T Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80203 |
These are the alarms/events reported by NSX-T. 'Source Component' specifies the entity emmitting this event.
It can be Manager/Controller/Edge. Combination of fields like Source Component, Event Type, Severity and message can be used to troubleshoot NSX-T appliance. For further information, log into NSX-T Manager UI and visit Dashboard |
|
.1.3.6.1.4.1.6876.100.1.0.80205 |
NSX-T Tier-1 logical router is disconnected from Tier-0 router. Networks under this router are not reachable from outside and vice versa.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80206 |
Routing advertisement is disabled for NSX-T Tier-1 logical router. Networks under this router are not reachable from outside.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80207 |
NSX-T Edge Node has lost manager connectivity.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80208 |
NSX-T Edge Node is not able to communicate with one or more controllers.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80209 |
NSX-T Edge Node is not able to communicate with any of the controllers.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80210 |
The MTU configured on interface(s) of Tier-0 logical router do not match with the interface(s) of uplink switch/router from same L2 network. This may impact network performance.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80211 |
One or more VMs are not protected by NSX-T DFW firewall. VMware Aria Operations for Networks will not receive IPFIX flows for these VMs.
Remove the relevant logical switches, logical ports or security groups from the NSX-T firewall exclusion list to enable flows. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80212 |
Communication will be disrupted because Vlan on uplink port of Tier 0 router is different than Vlan on the external gateway.
Vlan is misconfigured on the tier-0 router. Make sure Vlan matches with the Vlan on the external gateway. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80213 |
NSX-T Transport node is not attached to any transport zone. VMs might loose connectivity because of this.
Ensure that the transport node is attached to some transport zone. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80214 |
All vteps are deleted from the transport node. VMs might loose connectivity because of this.
Make sure vteps/vmknics are not deleted from the transport node. You may check all available vteps/vmknics in NSX-T->Fabric Nodes->Transport Node->Monitor of each of the impacted transport nodes. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80215 |
Same Switch or Router is added with different IPs. VM to VM path may not be generated.
Delete duplicate Switches or Routers from Data Source. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80216 |
This event is raised when pool member of load balancer is down.
Ensure that pool member has not been disabled by the administrator. Ensure that pool/pool-member uses the correct Health Monitors which are getting required responses from the backend server. Ensure that backend server used by this pool member is functional. For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools -> Pools List. Also check documentation at https://support.f5.com/csp/article/K12531 Alternatively, you can log into VMware Aria Operations for Networks UI and search 'Pool Member where state = DISABLED'. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80217 |
This event is raised when pool of load balancer is down.
Ensure that pool has at least one functional pool member. For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools Also check documentation at https://support.f5.com/csp/article/K12531 For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80218 |
This event is raised when pool of load balancer is empty.
Ensure that pool has at least one pool member. For more details, log into Load Balancer UI, navigate to Local Traffic -> Pools Also check documentation at https://support.f5.com/csp/article/K12531 Alternatively, you can log into VMware Aria Operations for Networks and search 'Pool where PoolMembers Count = 0'. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80219 |
This event is raised when VM associated with pool member of load balancer is down.
Check if VM associated with pool member is powered on and running. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80220 |
This event is raised when virtual server of load balancer is disabled.
To enable virtual server, open load balancer GUI and check virtual server state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80221 |
This event is raised when no NIC associated with IP of service node of load balancer is found.
Ensure that VM which has IP of Service Node exist. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80222 |
This event is raised when multiple NICs associated with IP of service node of load balancer are found.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events. |
|
.1.3.6.1.4.1.6876.100.1.0.80223 |
VMware Aria Operations for Networks does not support the IPFIX flow data from NSX-T Switches. It is configured to send IPFIX data to one of the VMware Aria Operations for Networks Collector VM. It may have corrupted existing flow data in the system.
Remove VMware Aria Operations for Networks Collector VM IP Address from the NSX-T Switch collector profiles which are used in NSX-T Switch IPFIX profiles. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80224 |
vCenter managing one or more fabric nodes in NSX-T is not added as a data source in VMware Aria Operations for Networks. Virtual Machines on those hosts will not be visible in VMware Aria Operations for Networks.
Please add the vCenter server managing the standalone hosts as a datasource into VMware Aria Operations for Networks at- Settings -> Accounts and Data Sources -> Add Source -> VMware vCenter For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80225 |
NSX-T controller node has no control cluster connectivity.
Check if the node has proper network connectivity with control cluster. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80226 |
NSX-T controller node has no management plane connectivity.
Check if the node has proper network connectivity with management plane. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80227 |
NSX-T management node has no management cluster connectivity.
Check if the node has proper network connectivity with management cluster. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80228 |
NSX-T Host Transport Node Pnic Status is 'Down'.
All the pNICs of the NSX-T Host transport Node are down. Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80229 |
NSX-T Host Transport Node Pnic Status is 'Degraded'
Some of the pNICs of the NSX-T Host transport Node are down. Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80230 |
NSX-T Host Transport Node Pnic Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the pNICs of the NSX-T Host Transport Node Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80231 |
NSX-T Host Transport Node Tunnel Status is 'Down'.
All the tunnel interfaces associated to the NSX-T Host transport Node are down. Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80232 |
NSX-T Host Transport Node Tunnel Status is 'Degraded'.
Some of the tunnel interfaces associated to the NSX-T Host transport Node are down. Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80233 |
NSX-T Host Transport Node Tunnel Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the tunnel interfaces associated to the NSX-T Host Transport Node. Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80234 |
NSX-T Host Transport Node Roll-up Status is 'Down'.
Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node are down. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80235 |
NSX-T Host Transport Node Roll-up Status is 'Degraded'.
Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node are in degraded state. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80236 |
NSX-T Host Transport Node Roll-up Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Host Transport Node. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80237 |
NSX-T Edge Transport Node Pnic Status is 'Down'.
All the pNICs of the NSX-T Edge transport Node are down. Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80238 |
NSX-T Edge Transport Node Pnic Status is 'Degraded'.
Some of the pNICs of the NSX-T Edge transport Node are down. Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80239 |
NSX-T Edge Transport Node Pnic Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the pNICs of the NSX-T Edge Transport Node Please check if all the pNICs are properly connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80240 |
NSX-T Edge Transport Node Tunnel Status is 'Down'.
All the tunnel interfaces associated to the NSX-T Edge transport Node are down. Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80241 |
NSX-T Edge Transport Node Tunnel Status is 'Degraded'.
Some of the tunnel interfaces associated to the NSX-T Edge transport Node are down. Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80242 |
NSX-T Edge Transport Node Tunnel Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the tunnel interfaces associated to the NSX-T Edge Transport Node Please check the status of the tunnel interfaces for this NSX-T Transport Node For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80243 |
NSX-T Edge Transport Node Roll-up Status is 'Down'.
Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node are down. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80244 |
NSX-T Edge Transport Node Roll-up Status is 'Degraded'.
Some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node are in degraded state. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80245 |
NSX-T Edge Transport Node Roll-up Status is 'Unknown'.
NSX-T Manager can't determine the status of some or all of the pNICs, management connection, control connections, tunnel statuses, agent statuses of NSX-T Edge Transport Node. Please check the status of the pNICs, management & control connections, tunnels and agents for this NSX-T Transport Node. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80246 |
NSX-T Host Transport Node has lost connectivity with NSX-T Manager node.
Please ensure all the interfaces connecting the NSX-T Transport Node to manager are up. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80247 |
NSX-T Edge Node Controller connectivity is Unknown.
NSX-T Manager can't determine the status of the Edge Transport Node's connectivity with controller nodes Please ensure all the interfaces connecting the NSX-T Transport Node to manager are up. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80248 |
NSX-T Host Node is not able to communicate with any of the controllers.
NSX-T Host Transport Node has lost connectivity with all the controller nodes Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80249 |
NSX-T Host Node is not able to to communicate with one or more controllers.
NSX-T Host Transport Node has lost connectivity with some (but not all) of the controller nodes Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80250 |
NSX-T Host Node Controller connectivity is Unknown.
NSX-T Manager can't determine the status of the Host Transport Node's connectivity with controller nodes Please ensure all the interfaces connecting the NSX-T Transport Node to controller nodes are up. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80251 |
BGP neighbor connection status change alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80252 |
NSX-T Logical Switch Admin Status is 'Down'.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80253 |
NSX-T Logical Port Operational Status is 'Down'. This could cause a communication failure between two virtual interfaces (VIFs) that are connected to the same logical switch, for example, you cannot ping one VM from another.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80254 |
NSX-T Logical Port Operational Status is 'Unknown'. This could cause a communication failure between two virtual interfaces (VIFs) that are connected to the same logical switch, for example, you cannot ping one VM from another.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80255 |
NSX-T Compute Manager Connection status is not up.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80256 |
NSX-T Manager backup is not scheduled.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80257 |
Distributed Firewall is disabled in the NSX-T Manager.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80258 |
Received packets are getting dropped on the NSX-T Logical Port and associated entities might get affected.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80259 |
Transmitted packets are getting dropped on the NSX-T Logical Port and associated entities might get affected.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80260 |
Received packets are getting dropped on the NSX-T Logical Switch and associated entities might get affected.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80261 |
Transmitted packets are getting dropped on the NSX-T Logical Switch and associated entities might get affected.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80262 |
Received packets are getting dropped on NSX-T Management Node's network interface. This may impact the network traffic related to NSX-T management cluster.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80263 |
Received packets are getting dropped on NSX-T Edge Node's network interface. This may impact the network traffic of edge cluster.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80264 |
Received packets are getting dropped on NSX-T Host Node's network interface. This may impact the network traffic on ESXi Host.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80265 |
Transmitted packets are getting dropped on NSX-T Management Node's network interface. This may impact the network traffic related to NSX-T management cluster.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80266 |
Transmitted packets are getting dropped on NSX-T Edge Node's network interface. This may impact the network traffic of edge cluster.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80267 |
Transmitted packets are getting dropped on NSX-T Host Node's network interface. This may impact the network traffic on ESXi Host.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80268 |
NSX-T Network Interface Received Packet Drop Alert on Management Node
|
|
.1.3.6.1.4.1.6876.100.1.0.80269 |
NSX-T Network Interface Transmission Packet Drop Alert on Management Node
|
|
.1.3.6.1.4.1.6876.100.1.0.80270 |
IP address mentioned in the NAT Rules have a subnet of size greater than 16. Flows will be impacted due to large subnet size.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80271 |
NSX-T Edge Node is in Maintenance Mode.
For uninterrupted operations, please disable Maintenance Mode on this edge node if maintenance activity is completed. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80272 |
NSX-T Host Node is in Maintenance Mode.
For uninterrupted operations, please disable Maintenance Mode on this Host Node if maintenance activity is completed. This event will be closed once host is host is out of maintenance mode. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80273 |
As a protection mechanism, the flow collection for DVPGs, having NSX-T Edges connected, is disabled.
Please enable DFW IPFIX on NSX-T, if not enabled already. Do not enable IPFIX on DVPGs having NSX-T Edge VMs connected. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80274 |
This alert is generated when the RPF packet drop ratio exceeds the threshold value of 1%. Check RPF packet drop on the interface.
|
|
.1.3.6.1.4.1.6876.100.1.0.80275 |
NSX-T Multiple DFW IPFIX Collectors Configured. Please remove the stale collector IPs from NSX Policy DFW IPFIX collector profile. To automatically remove stale collector IPs from NSX Policy IPFIX collector profile, please uncheck the IPFIX checkbox on the Data Source edit page and check again after 30 minutes.
|
|
.1.3.6.1.4.1.6876.100.1.0.80301 |
Hardware Gateway Bindings Mismatch between NSX and switch.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80302 |
Hardware Gateway Binding Switch Port is down.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80402 |
One of the Services of the NSX-T Management Node, namely CM Inventory Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80403 |
One of the Services of the NSX-T Management Node, namely Controller Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80404 |
One of the Services of the NSX-T Management Node, namely DataStore Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80405 |
One of the Services of the NSX-T Management Node, namely HTTP Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80406 |
One of the Services of the NSX-T Management Node, namely Install Upgrade Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80407 |
One of the Services of the NSX-T Management Node, namely LI Agent Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80408 |
One of the Services of the NSX-T Management Node, namely Manager Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80409 |
One of the Services of the NSX-T Management Node, namely Management Plane Bus Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80410 |
One of the Services of the NSX-T Management Node, namely Migration Co-ordinator Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80411 |
One of the Services of the NSX-T Management Node, namely Node Management Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80412 |
One of the Services of the NSX-T Management Node, namely Node Statistics has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80413 |
One of the Services of the NSX-T Management Node, namely Message Bus Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80414 |
One of the Services of the NSX-T Management Node, namely Platform Client Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80415 |
One of the Services of the NSX-T Management Node, namely Upgrade Agent Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80416 |
One of the Services of the NSX-T Management Node, namely NTP Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80417 |
One of the Services of the NSX-T Management Node, namely Policy Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80418 |
One of the Services of the NSX-T Management Node, namely Search Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80419 |
One of the Services of the NSX-T Management Node, namely SNMP Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80420 |
One of the Services of the NSX-T Management Node, namely SSH Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80421 |
One of the Services of the NSX-T Management Node, namely Syslog Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80422 |
One of the Services of the NSX-T Management Node, namely Telemetry Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80423 |
One of the Services of the NSX-T Management Node, namely UI Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80424 |
One of the Services of the NSX-T Management Node, namely Cluster Manager Service has stopped running.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80501 |
Index Lag Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80502 |
IPFIX Flow Data Provider Paused Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80503 |
Grid Processing Stopped Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80504 |
Unable to Send Emails Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80505 |
SMPT Not Configured Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80506 |
SNMP Not Configured Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80507 |
Redindexing In Process Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80508 |
Node Version Mismatch Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80509 |
Not All Services Running Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80510 |
Not All Services Healthy Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80511 |
Expand Partition Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80512 |
Disk Cleanup Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80513 |
Vacuum Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80514 |
Config Store Cleanup Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80515 |
HBASE Retention Tool Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80516 |
Metric Store Updater Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80517 |
Collecter Lag Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80518 |
Collection Lag Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80519 |
Grid Processing Lag Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80520 |
Connection Error Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80521 |
Node Not Active Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80522 |
High Disk Utilization Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80523 |
Indexing Aborted Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80524 |
Upgrade Failed Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80525 |
Flow Processing Suspended Event
|
|
.1.3.6.1.4.1.6876.100.1.0.80526 |
Data Processing Error
|
|
.1.3.6.1.4.1.6876.100.1.0.80527 |
Collector VM configuration is incomplete.
To reconfigure proxy, please run 'setup' CLI from console mode. https://docs.vmware.com/en/VMware-vRealize-Network-Insight/3.8/com.vmware.vrni.cli.doc/GUID-B48AD03A-5FC8-4396-9C27-9523307C688C.html For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80528 |
Appliance Disk not configured according to Disk Guidance.
https://docs.vmware.com/en/VMware-vRealize-Network-Insight/5.1/com.vmware.vrni.using.doc/GUID-C96E9C78-6FA2-49EB-9791-8967A89B7698.html For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80529 |
Appliance Not Registered Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80530 |
Appliance Registration Certificate Expired Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80531 |
Foundation Database (FDB) Config Store Cleanup Failed Event.
Data Retention (Config Store Maintenance) service is not healthy. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80532 |
Capacity configuration is mismatched. Please reconfigure.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80533 |
Backup Failed Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80534 |
Additional Resources Required Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80535 |
Cluster Capacity Reconfiguration Required Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80536 |
Cluster Capacity Reconfiguration Failed Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80537 |
License of this appliance has expired. Please apply a valid license to continue the data collection.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80538 |
Applicance license is in Grace Period. Add valid licenses before grace period ends to continue the data collection.
This event will remain open till it is fixed. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80539 |
VMware Aria Operations for Networks appliance failed to send SNMP Trap. This could be due to temporary network disruption.
If problem persists, please check if SNMP Trap destination is reachable from VMware Aria Operations for Networks appliance. Please note that this trap is only sent if sendto() or getaddrinfo() fails from VMware Aria Operations for Networks appliance. To send a test trap, log into VMware Aria Operations for Networks -> Settings -> Alerts and Definition -> SNMP Trap Destinations page and click 'Send Test Trap'. Also note that ther For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80540 |
Realtime stream processing has failed in VMware Aria Operations for Networks appliance.
Please contact VMware support immediately to resolve the issue. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80541 |
This alert is raised to notify users when there are excessive incoming flow records than what can be processed within the stipulated time window, the ipfix processor lags behind. Once the incoming flow records are back within the limits, the alert gets cleared. The time window for each source is defined in ipfix.configuration.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80542 |
Realtime processing has stopped due to high system load. Some updates may be delayed. It is a temporary condition. The system should recover and clear the error by itself. If this message persists for more than 12 hours, please contact VMware customer support.
|
|
.1.3.6.1.4.1.6876.100.1.0.80543 |
High Disk IO Utilization Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80544 |
One or more services restarted multiple times. Please verify the system is in a healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.80600 |
Analytics Memory Limits Exceeded Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.80601 |
FAILED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80602 |
TIMEOUT_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80603 |
CONNECTION_REFUSED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80604 |
Required privileges are missing for the user in ServiceNow.
Please make sure that the user used in VMware Aria Operations for Networks while adding SNOW account has been necessary privileges in SNOW UI. To check user details, please visit VMware Aria Operations for Networks -> Setting -> Data Sources page. To check required user permissions, please visit https://docs.vmware.com/en/VMware-vRealize-Network-Insight/6.4/com.vmware.vrni.using.doc/GUID-772EC526-DD22-4B3C-87A5-F55CA90ED5AE.html. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80605 |
INCORRECT_CONNECTION_STRING_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80606 |
INVALID_CREDENTIALS_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80608 |
UNKNOWN_HOST_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80609 |
SNMP_CONNECTION_INVALID_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.806100012 |
PWD_AUTH_MODE_DISABLED_ARISTA_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.806100018 |
UNSUPPORTED_NSX_VERSION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80611 |
FAILED_CREDS_ENCRYPT_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80612 |
PWD_AUTH_MODE_DISABLED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80613 |
INSUFFICIENT_PRIVILEGES_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.8061313 |
FLOW_COLLECTION_ERROR_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.8061314 |
AWS_THROTTLING_EXCEPTION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.8061315 |
AWS_FLOW_LOG_ACCESS_DENIED_EXCEPTION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.8061316 |
Azure Flow Collection Error
|
|
.1.3.6.1.4.1.6876.100.1.0.8061317 |
Azure Network Watcher Storage Error
|
|
.1.3.6.1.4.1.6876.100.1.0.80614 |
NOT_FOUND_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80616 |
INVALID_CONFIG_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80617 |
WARN_CONFIG_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80618 |
UNEXPECTED_DS_TYPE_OR_VERSION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80619 |
NSX_CONTROLLER_NOT_FOUND_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80620 |
HOST_NOT_REACHABLE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80621 |
INVALID_RESPONSE_FROM_DATASOURCE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80622 |
DATA_PROVIDER_NOT_RUNNING_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80623 |
PRIMARY_NSX_NOT_ADDED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80624 |
HOSTNAME_RESOLUTION_ERROR_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80625 |
NUM_VMS_OR_HOSTS_NOT_FOUND_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80626 |
NSX_IPFIX_STATUS_MISMATCH_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80627 |
FLOW_PHYSICAL_NODE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80628 |
NOT_EMPTY_NODE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80629 |
UNSUPPORTED_NSXT_VERSION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80630 |
COMPUTE_MANAGERS_NOT_FOUND_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80631 |
COMPUTE_MANAGERS_NOT_ADDED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80632 |
UNSUPPORTED_LOG_INSIGHT_VERSION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80633 |
UNSUPPORTED_vRNI_CONTENT_PACK_VERSION_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80634 |
vRNI_CONTENT_PACK_NOT_INSTALLED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80635 |
WEBHOOK_NOT_ENABLED_ON_ALERT_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80636 |
INCORRECT_WEBHOOK_CONFIGURED_ON_ALERT_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80637 |
WEBHOOK_NOT_RUNNING_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80638 |
The number of A records fetched from Infoblox exceeds the current limit
|
|
.1.3.6.1.4.1.6876.100.1.0.80639 |
Invalid credentials or insufficient privileges
|
|
.1.3.6.1.4.1.6876.100.1.0.80640 |
The version of Infoblox is not supported
|
|
.1.3.6.1.4.1.6876.100.1.0.80641 |
Infoblox version cannot be determined
|
|
.1.3.6.1.4.1.6876.100.1.0.80642 |
NO_DVS_AVAILABLE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80643 |
VC_NOT_ON_SAME_PROXY_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80644 |
NSXT_IPFIX_NO_COLLECTOR_PROFILE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80645 |
NSXT_IPFIX_NO_NEW_COLLECTOR_PROFILE_CAN_BE_ADDED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80646 |
NSXT_IPFIX_NO_IPFIX_PROFILE_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80647 |
NSXT_IPFIX_IPFIX_PROFILE_PRIORITY_NOT_ZERO_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80648 |
NSXT_IPFIX_COLLECTOR_AND_IPFIX_PROFILE_MISMATCH_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80649 |
NSXT_IPFIX_PORT_INCORRECT_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80650 |
NSXT_IPFIX_DFW_STATUS_NOT_ENABLED_EVENT
|
|
.1.3.6.1.4.1.6876.100.1.0.80651 |
DFW IPFIX Profile is absent on VMC Policy Manager.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events. |
|
.1.3.6.1.4.1.6876.100.1.0.80652 |
VMware Aria Operations for Networks IPFIX Collector is absent on VMC Policy Manager.
For more details, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80653 |
The data source identity information such as certificate or the key has changed.
Re-verify the identity information on data source page in VMware Aria Operations for Networks. System will auto accept the new identification. If issue persists for more than an hour, please contact support. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80654 |
Please verify the Kubernetes Cluster API Servers are reachable from Collector VM.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80655 |
One or more Kubernetes Cluster Service Accounts do not have sufficient privileges.
Please verify that all Kubernetes Cluster Service Accounts has List and Watch privileges. Refer - https://kubernetes.io/docs/reference/access-authn-authz/rbac/#service-account-permissions For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80656 |
Number of applications in ServiceNow exceeds System limit
|
|
.1.3.6.1.4.1.6876.100.1.0.80657 |
Configuration file required by Generic Routers & Switches Data Source has not been provided while data source creation. To resolve this issue, please go to VMware Aria Operations for Networks web UI, under settings page, edit intended Generic Routers & Switches Data Source and add configuration file.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80658 |
Configuration file required by Generic Routers & Switches Data Source has been deleted manually or moved. To resolve this issue, please go to VMware Aria Operations for Networks web UI, under settings page, edit intended Generic Routers & Switches Data Source and add configuration file.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80659 |
NSX-T latency collection is not enabled.
Latency collection was disabled in the NSX-T Manager after it was enabled by VMware Aria Operations for Networks. As a result, VMware Aria Operations for Networks is not receiving latency information from the NSX-T. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80661 |
NSX-T, no BFD profile configured Event.
BFD profile was deleted on NSX-T Manager after 'Virtual infrastructure Latency' was enabled at VMware Aria Operations for Networks. As a result, VMware Aria Operations for Networks is not assigning BFD profile on Transport zone. VMware Aria Operations for Networks will not receive Latency information from new transport zones. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80662 |
The collector configured on NSX-T is different from this VMware Aria Operations for Networks deployment. As a result, VMware Aria Operations for Networks is not receiving Latency information from NSX-T.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80663 |
No access to shell(ssh port 22) for F5 Load Balancer. VMware Aria Operations for Networks will not be able to fetch any information required for visibility.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80664 |
Insufficient Partition Access for F5 Load Balancer. VMware Aria Operations for Networks will not be able to fetch any information required for visibility.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80665 |
Insufficient Role for F5 Load Balancer. VMware Aria Operations for Networks will not be able to fetch any information required for visibility.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80666 |
NSX-T System Alert API is timed out
|
|
.1.3.6.1.4.1.6876.100.1.0.80667 |
The Latency Stat profile configured on NSX-T is different from this VMware Aria Operations for Networks deployment. As a result, VMware Aria Operations for Networks is not receiving Latency information from NSX-T.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80668 |
The Latency Node Group configured on NSX-T is different from this VMware Aria Operations for Networks deployment. As a result, VMware Aria Operations for Networks is not receiving Latency information from NSX-T.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80669 |
The Latency Service Config configured on NSX-T is different from this VMware Aria Operations for Networks deployment. As a result, VMware Aria Operations for Networks is not receiving Latency information from NSX-T.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80670 |
The webhook configured to receive push notifications from NSX-T is no longer present in the data source. As a result, notifications received by VMware Aria Operations for Networks might be delayed.
Please log into NSX-T and enable notifications for VMware Aria Operations for Networks. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80672 |
Data Source Update Operation Failed. Details of the data source and failed operation are mentioned in the event vmwOperatorDesc field.
Please check correctness of input data while performing update operations to a data source. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.80700 |
This alert is triggered while adding the NSX ALB data source and if the version of NSX ALB is < 20.1.3.
For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80800 |
This alert is triggered if the Kubernetes Clusters which are managed by TKGI are not reachable from collector.
Please verify the Kubernetes Cluster Master hosts are reachable from Collector VM. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.80801 |
This alert is triggered if the Kubernetes Clusters which are managed by TKGI doesn't sufficient privileges for fetching the k8s entities.
It must have List and Watch privileges. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |
|
.1.3.6.1.4.1.6876.100.1.0.90000 |
VeloCloud Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90001 |
VeloCloud Edge is not connected.
Verify that the VeloCloud Edge is UP. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90002 |
VeloCloud Edge is not connected.
Verify that the VeloCloud Link is UP. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90003 |
VeloCloud Edge Packet Drop Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90004 |
VeloCloud Edge Retransmitted Packet Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90005 |
Transmitted Packet Loss observed on VeloCloud Link.
Verify that the Link is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90006 |
VeloCloud Edge Location Not Set Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90007 |
VeloCloud Link Voice QOE has Degraded.
Verify that the Link is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90008 |
VeloCloud Link Video QOE has Degraded.
Verify that the Link is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90009 |
VeloCloud Link Transactional QOE has Degraded.
Verify that the Link is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90010 |
VeloCloud Edge Voice QOE has Degraded.
Verify that the Edge is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90011 |
VeloCloud Edge Video QOE has Degraded.
Verify that the Edge is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90012 |
VeloCloud Edge Transactional QOE has degraded.
Verify that the Edge is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90013 |
Received Packet Loss observed on VeloCloud Link.
Verify that the Link is in healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90014 |
Velocloud Tunnel Degraded Voice QOE Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90015 |
Velocloud Tunnel Degraded Video QOE Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90016 |
Velocloud Tunnel Degraded Transaction QOE Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90017 |
SD-WAN Link Traffic exceeded the threshold limit configured. Link details are available in event description vmwOperatorDesc field.
Please check the Traffic Utilization section on VeloCloud Edge to get the visibility of Applications and clients for the Link. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.90018 |
VeloCloud QOE Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90500 |
HCX Alert
|
|
.1.3.6.1.4.1.6876.100.1.0.90501 |
HCX Interconnect Service is not Up. Please verify HCX IX Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90502 |
Hybrid Interconnect Service Encryption Tunnel Status is not Up. Please verify HCX IX Appliance Encryption Tunnel is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90503 |
HCX Network Extension Service is not Up. Please verify HCX NE Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90504 |
HCX Network Extension Service Encryption Tunnel Status is not Up. Please verify HCX NE Appliance Encryption Tunnel is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90505 |
Hybrid Interconnect Service Pipeline Status is not Up. Please verify Hybrid Interconnect Service Pipeline is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90506 |
HCX Network Extension Service Pipeline Status is not Up. Please verify HCX Network Extension Service Pipeline is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90507 |
Hybrid Interconnect Service Transport Status is not Up. Please verify Hybrid Interconnect Service Transport is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90508 |
Network Extension Service Transport Status is not Up. Please verify Network Extension Service Transport is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90509 |
Hybrid Interconnect Service System State is not Up. Please verify Hybrid Interconnect Service System is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90510 |
Network Extension Service System State is not Up. Please verify Network Extension Service System is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90511 |
WAN Optimisation Service is not Up. Please verify HCX WAN Optimisation Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90512 |
HCX Bulk Migration Service is not Up. Please verify HCX Bulk Migration Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90513 |
HCX vMotion Service is not Up. Please verify HCX VMotion Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90514 |
Hybrid Interconnect Service is not running. Please verify Hybrid Interconnect Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90515 |
Network Extension Service is not running. Please verify Network Extension Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90516 |
WAN Optimisation Service is not running. Please verify WAN Optimisation Service Service is in healthy state.
|
|
.1.3.6.1.4.1.6876.100.1.0.90517 |
No tunnels are in working state on HCX Appliance. Please verify the tunnels are working for the HCX Appliance.
|
|
.1.3.6.1.4.1.6876.100.1.0.90518 |
HCX Connection Rule is violated for the Firewall Rules. Please verify HCX Applinace Tunnel for the violated firewall rules.
|
|
.1.3.6.1.4.1.6876.100.1.0.90519 |
MTU doesn't match for uplink network profiles in the HCX Service Mesh. Please correct the MTU values for the uplink network profiles.
|
|
.1.3.6.1.4.1.6876.100.1.0.90520 |
Few tunnels on HCX Appliance are unhealthy. Please verify the tunnels are working for the HCX Appliance.
|
|
.1.3.6.1.4.1.6876.100.1.0.90521 |
The paired HCX Managers are running different software versions. Please upgrade the appropriate HCX Manager so that the paired HCX Managers are running similar version of software.
|
|
.1.3.6.1.4.1.6876.100.1.0.90522 |
The paired HCX Appliances are running different software versions. Please upgrade the appropriate HCX Appliance so that the paired HCX Appliances are running similar version of software.
|
|
.1.3.6.1.4.1.6876.100.1.0.974 |
NSX Intelligence Appliance is deployed within NSX-T. NSX-I data collection on the NSX-T Data source can now be enabled.
Please visit to VMware Aria Operations for Networks -> Settings -> Data Sources -> NSX-T data souces to enable this data collection. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.975 |
Enabling data collection from NSX Intelligence was failed.
Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.976 |
Cleanup of NSX Intelligence appliance failed.
Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.977 |
Failed to initiate data collection from NSX Intelligence.
Please check the NSX-Intelligence appliance and ensure it is reachable and in a healthy state For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events |
|
.1.3.6.1.4.1.6876.100.1.0.978 |
NSX Intelligence SSL Handshake Failed.
Please check the SSL certificates configured on NSX Intelligence Appliance. For more details about this event, please log into VMware Aria Operations for Networks, navigate to Settings -> Events -> Alert Definitions page |