The Management Pack for NSX for vSphere collects metrics for the NSX for vSphere Logical Router objects.

Table 1. NSX for vSphere Logical Router Metrics
Name Category Unit Description Instanced
Status Status String Indicates if the NSX for vSphere Logical Router is currently deployed and available. No
Attached VMs Status Integer Number of virtual machines using the NSX for vSphere Logical Router. No
Connected Interface Binary Specifies if the interface is currently configured. Yes
Connection Health Interface Integer Health of the connection between this interface and the attached interface. A value of 100 means the connection is healthy: 50 means there is a warning alert that is impacting the connection: 25 means there this an immediate alert impacting the connection: 0 means there is a critical alert impacting the connection. Yes
Status Interface String Current status of the interface Yes
Used Interface Integer Number of interfaces currently configured on the NSX for vSphere Logical Router. No
Used Route Integer Number of static routes currently configured on the NSX for vSphere Logical Router. No
Type OSPF Area String Type of the OSPF routing area on the NSX for vSphere Logical Router. Yes
Authentication Type OSPF Area String Type of authentication used for the OSPF area. None, Password, or MD5. Yes
Hello Interval Interface|OSPF String OSPF area hello interface configured on each interface on the NSX Logical Router. Yes
Dead Interval Interface|OSPF String OSPF area dead interval configured on each interface on the NSX Logical Router. Yes
Priority Interface|OSPF String OSPF area priority configured on each interface on the NSX Logical Router. Yes
Cost Interface|OSPF String OSPF area cost configured on each interface on the NSX Logical Router. Yes
Ignore MTU Interface|OSPF String Specifies if the MTU is being ignored for each interface on the NSX Logical Router. This metric is either True or False. Yes
MTU Mismatch Interface String The MTU configured on a logical router/routing edge service should match the MTU of its next hop in order to prevent unnecessary network fragmentation. Yes