vmwNsxMVxlanVDSandPgMismatch
VMWARE-NSX-MANAGER-MIB ·
.1.3.6.1.4.1.6876.90.1.2.20.0.28
Object
notification
DESCRIPTION: NSX Manager will raise this event when the teaming policies of a VDS and it's associated VXLAN portgroup are not the same. ACTION: Set the VXLAN portgroup teaming policy back to the original value. Below is the workaround to correctly update the teaming policy in a deployed cluster: The supported method to correct teaming policy inconsistencies is to create and prepare a new NSX cluster with the required teaming policy, and to migrate ESXi hosts to that cluster. Changing the teaming policy in the manager DB by some other means only applies to newly created virtual wires after the DB change is made. FREQUENCY: This event will generate whenever the VXLAN portgroup teaming policy is changed to something different than the VDS teaming policy. AFFECTS: The VXLAN traffic on the switch may be interrupted.
Context
- MIB
- VMWARE-NSX-MANAGER-MIB
- OID
.1.3.6.1.4.1.6876.90.1.2.20.0.28- Type
- notification
- Status
- current
- Parent
- vmwNsxMVxlanPrefix
- Siblings
- 31
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vmwNsxMVxlanLogicalSwitchImproperlyCnfg This event is triggered if one or more distributed virtual
port groups backing a certain Logical Switch were modified and/or removed.
Or if migration of Control plane mode for a L… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.1 |
| vmwNsxMVxlanControllerRemoved A notification generated when VXLAN Controller has been removed due to
the connection cant be built, please check controller IP configuration
and deploy again. | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.10 |
| vmwNsxMVxlanControllerConnProblem NSX manager detected the connection between two controller
nodes is broken.
Action required: It is a warning event, users need to check the controller
cluster for the further step… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.11 |
| vmwNsxMVxlanControllerInactive Host Certification information couldn't be sent to NSX
Controllers.
Action required: Ensure that NSX Controller cluster is in healthy state
before preparing a new Host. Invoke Con… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.12 |
| vmwNsxMVxlanControllerActive A notification generated when Controller cluster state is
now active. Controller Synchronization job is in progress.
Frequency of traps: Controller cluster becomes active again fr… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.13 |
| vmwNsxMVxlanVmknicMissingOrDeleted VXLAN vmknic is missing or deleted from host.
Action required: Issue can be resolved from Logical Network
Preparation - VXLAN Transport UI section. Clicking on resolve will try to… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.14 |
| vmwNsxMVxlanInfo NSX Manager will raise this event when connection between
either of the following component is established/re-established
(i) connection between NSX Manager and Host Firewall agen… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.15 |
| vmwNsxMVxlanVmknicPortGrpMissing NSX manager detected one vxlan vmknic is missing on VC.
Action required: Check the host, if that vmknic is deleted, click on the
resolve button on UI, or call the remediate API (P… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.16 |
| vmwNsxMVxlanVmknicPortGrpAppears NSX manager detected one vxlan vmknic that was marked as
missing has now reappeared on VC.
Action required: None
Frequency of traps: When that missing vmknic re-appears again.
Aff… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.17 |
| vmwNsxMVxlanConnDown This event is triggered when either of the following
connections are detected down by NSX Manager:
(i) connection between NSX Manager and Host Firewall agent.
(ii) connection betw… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.18 |
| vmwNsxMBackingPortgroupMissing NSX manager detected one backing portgroup of a logical
switch is missing on VCenter.
Action required: Click on the resolve button on UI or call the API
(POST https://<nsx-manager… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.19 |
| vmwNsxMVxlanLogicalSwitchProperlyCnfg Logical Switch status has been marked good, most probably as
result of resolving any errors on it.
Action required: None
Frequency of traps: Event is triggered when user resolves … | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.2 |
| vmwNsxMBackingPortgroupReappears NSX manager detected one backing portgroup of a logical
switch that was missing reappears on VC.
Action required: None
Frequency of traps: Whenever user triggered remediate API on… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.20 |
| vmwNsxMManagedObjectIdChanged NSX manager detected the Managed Objectid of one backing
portgroup of a logical switch changed.
Action required: None
Frequnecy of traps: This typically happens when user restores… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.21 |
| vmwNsxMHighLatencyOnDisk NSX manager detected some disk on a NSX Controller has high
latency.
Action required: Rectify the issue on specified device and controller.
Frequency of traps: First time NSX dete… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.22 |
| vmwNsxMHighLatencyOnDiskResolved NSX manager detected the disk high latency alert on a some
disk on a NSX Controller has been resolved.
Frequency of traps: First time NSX detected, previously raised disk
latency … | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.23 |
| vmwNsxMControllerVmPoweredOff NSX manager detected a Controller Virtual Machine is powered
off from vCenter.
Action required: Click on the 'Resolve' button on Controller page on UI or
call the API (POST https:… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.24 |
| vmwNsxMControllerVmDeleted NSX manager detected a Controller Virtual Machine is deleted
from vCenter.
Action required: Click on the Resolve button on Controller page on UI or
call the API (POST https://<nsx… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.25 |
| vmwNsxMVxlanConfigNotSet NSX manager detected the VXLAN configuration is not set on
the host (would-block issue). And this event indicates NSX Manager tried
to rectify this issue by resending the VXLAN co… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.26 |
| vmwNsxMVxlanPortgroupDeleted NSX Manager will raise this event when a VXLAN portgroup is deleted from
a switch.
ACTION: User does not have to take any action. This is just a notification
for the user.
FREQUEN… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.27 |
| vmwNsxMVxlanControllerDisconnected DESCRIPTION: NSX Manager raises this event when the Controller VM is
Disconnected ie the controller can not reached from the NSX Manager.
ACTION: Make sure the IP is assigned to t… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.29 |
| vmwNsxMVxlanInitFailed Failed to configure vmknic as a VTEP, VXLAN traffic through
this interface will be dropped until this is resolved.
Action required: Check the host's vmkernel.log for more details.… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.3 |
| vmwNsxMVxlanControllerConnected DESCRIPTION: NSX Manager will raise this informational event when the
controller VM is connected to controller cluster.
ACTION: No action to be taken.
FREQUENCY: Event occurs as c… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.30 |
| vmwNsxMVxlanControllerVmPoweredOn DESCRIPTION: NSX manager detected a Controller Virtual Machine is powered on from vCenter.
ACTION: None.
FREQUENCY: This event occurs when Controller Virtual Machine is powered On… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.31 |
| vmwNsxMVxlanHostEvents DESCRIPTION: NSX manager receives a notification from the host informing MAC mismatch occurred.
ACTION: Contact the administrator to take following action:
(1) Look for V… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.32 |
| vmwNsxMVxlanPortInitFailed Failed to configure VXLAN on the Distributed Virtual Port,
the port will be disconnected.
Action required: Check the host's vmkernel.log for more details.
Frequency of traps: Ever… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.4 |
| vmwNsxMVxlanInstanceDoesNotExist VXLAN configuration was received for a Distributed Virtual
Port, but the host has not yet enabled VXLAN on the vSphere Distributed
Switch. VXLAN ports on affected Host will fail t… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.5 |
| vmwNsxMVxlanLogicalSwitchWrkngImproperly VTEP interface was unable to join the specified multicast
address, the VTEP will be unable to receive some traffic from other hosts
until this is resolved. The host will periodica… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.6 |
| vmwNsxMVxlanTransportZoneIncorrectlyWrkng The IP address of a VTEP vmknic has changed.
Action required: None.
Frequency of traps: Every time a VTEP IP changes | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.7 |
| vmwNsxMVxlanTransportZoneNotUsed VTEP vmknic does not have a valid IP address assigned, all
VXLAN traffic through this vmknic will be dropped.
Action required: Verify the IP configuration for the interface, and t… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.8 |
| vmwNsxMVxlanOverlayClassMissingOnDvs NSX packages where not installed prior to DVS configuration
for VXLAN. All VXLAN ports will fail to connect until resolved.
Action required: See KB 2107951 https://kb.vmware.com/s… | notification | - | .1.3.6.1.4.1.6876.90.1.2.20.0.9 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vmwNsxMEventCode The event code of the alert that was generated. To fetch a list of all the
events with their code, severity and description please invoke the
nsx-manager url https://<nsx-manager-… | scalar | Integer32 | .1.3.6.1.4.1.6876.90.1.1.1 |
| vmwNsxMEventTimestamp The timestamp when the event was raised in the NSX Manager. | scalar | SNMPv2-TCDateAndTime | .1.3.6.1.4.1.6876.90.1.1.2 |
| vmwNsxMEventMessage This object provides a human readable description of the event or group
of events | scalar | OctetString | .1.3.6.1.4.1.6876.90.1.1.3 |
| vmwNsxMEventSeverity The severity for the event that was generated. The severity is
pre-defined and can only be changed from the NSX Manager section
of vsphere web client if the administrator so wishe… | scalar | VmwNsxManagerTypeSeverity | .1.3.6.1.4.1.6876.90.1.1.4 |
| vmwNsxMEventComponent The NSX manager component where this event was generated. | scalar | OctetString | .1.3.6.1.4.1.6876.90.1.1.5 |
| vmwNsxMUuid The NSX manager UUID where this event was generated. | scalar | UUID-TC-MIBUUID | .1.3.6.1.4.1.6876.90.1.1.6 |
| vmwNsxMEventSourceID The object ID(s) of the source(s) of the event. | scalar | VmwNsxManagerSourceID | .1.3.6.1.4.1.6876.90.1.1.8 |
| vmwNsxMEventSourceType The object type(s) of the source(s) of the event. | scalar | VmwNsxManagerSourceType | .1.3.6.1.4.1.6876.90.1.1.9 |
| vmwNsxMEventSourceIP The IP address(es) of the source(s) of the event. | scalar | VmwNsxManagerSourceIPAddress | .1.3.6.1.4.1.6876.90.1.1.10 |