Smarts MPLS: Why do 'Interface OperStatus' and 'AdminStatus' display as 'UNKNOWN' in MPLS Topology Manager?

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Why do Interface OperStatus and AdminStatus display as UNKNOWN in Smarts MPLS Topology Manager?

In MPLS Toplogy Manager Interface OperStatus and AdminStatus are shown as UNKNOWN in MPLS Topology Manager topology
The AM server that MPLS Toplogy Manager Interface synchronizes with shows Interface OperStatus and AdminStatus correctly (UP or Down)

Environment

VMware Smart Assurance - SMARTS

Resolution

MPLS manager has three components: MONITORING, TOPOLOGY and ANALYSIS. The following sections explain why MPLS Toplogy Manager Interface OperStatus and AdminStatus are shown as UNKNOWN in MPLS Topology Manager topology.

MPLS Monitoring server function
The MPLS Monitoring server is used to poll the MPLS VPN status and serve as a proxy for the physical network status from AM. AM monitors the physical network status and generates impact notifications for them. The MPLS Monitoring server simply proxies their status and uses the status to generate corresponding MPLS-VPN related impacts. For the purpose of efficiency, Interface AdminStatus and OperStatus have been combined into one status, StatusInRemote, and proxied to MPLS.

StatusInRemote
This StatusInRemote attribute in the MPLS Topology server reflects the status of the interface in AM. The value of MSI_NA_OK for this attribute indicates the status is OK.

Topology polling and UNKNOWN Interface OperStatus and AdminStatus values
The Topology is imported from AM into the MPLS Topology server, but dynamic attributes like AdminStatus and OperStatus are not subsequently polled here, so they show up with the UNKNOWN values. The Containment columns for Interface OperStatus and AdminStatus are still shown, as this is generated by the SAM Global Console. The columns are empty in Monitoring and Analysis servers as these attributes are not present there.