vmwNsxTEdgeEdgeVMNotPresentInBothNSXInventoryAndvCenter

VMWARE-NSX-MIB · .1.3.6.1.4.1.6876.120.1.0.45.0.11

Object

notification
The VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId corresponding to the Edge Transport node
vmwNsxTDataCenterEntityId vSphere placement parameters is not found in both NSX inventory and vCenter.
The placement parameters in the vSphere configuration of this Edge Transport
node vmwNsxTDataCenterEntityId refer to the VM with moref vmwNsxTDataCenterVMMorefId.
          
Action required:
The managed object reference moref id of a VM has the form vm-number, which is
visible in the URL on selecting the Edge VM in vCenter UI.  Example vm-12011 in
https://<vc-url>/ui/app/vm;nav=h/urn:vmomi:VirtualMachine:vm-12011:164ff798-c4f1-495b-a0be-adfba337e5d2/summary
Find the VM vmwNsxTDataCenterPolicyEdgeVMName with moref id vmwNsxTDataCenterVMMorefId in vCenter for this Edge
Transport Node vmwNsxTDataCenterEntityId.
Follow the below action to resolve the alarm -
Check if VM has been deleted in vSphere or is present with a different moref id.
1. If the VM is still present in vCenter, put the Edge Transport node in
maintenance mode and then power off and delete the Edge VM in vCenter. Use the NSX
Redeploy API to deploy a new VM for the Edge node. Data traffic for the Edge Transport
node will be disrupted in the interim duration if the Edge VM is forwarding traffic.
2. If the VM is not present in vCenter, use the redeploy API to deploy a new VM for the Edge node.
POST https://<manager-ip>/api/v1/transport-nodes/<tn-id>?action=redeploy.

Context

MIB
VMWARE-NSX-MIB
OID
.1.3.6.1.4.1.6876.120.1.0.45.0.11
Type
notification
Status
current
Parent
vmwNsxTEdgeFeature
Siblings
15

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
Notification Objects