About the MPLS topology collection sets

When the DisableMPLSDiscovery parameter in IP Availability Manager’s tpmgr-param.conf file is set to FALSE, IP Availability Manager not only performs its traditional discovery of network objects, but it also creates MPLS topology collection sets from the discovered network objects. By default, it queries the SNMP agent of every device in the managed network for the following OIDs:

• .1.3.6.1.3.118.1.2.1.1.2

• .1.3.6.1.3.96.1.6.1.2

• .1.3.6.1.2.1.10.166.2.1.7.1.2

• .1.3.6.1.4.1.2636.3.2.3.1.2

  If a polled OID for a device returns valid information, IP Availability Manager classifies the device as MPLS-enabled and adds the device to a topology collection set named MPLS-System, and adds the device’s SNMP agent to a topology collection set named MPLS-Agent. An MPLS-enabled device is a PE, P, or Multi-VRF CE device, where a Multi-VRF CE has a VRF configuration and uses BGP to interface with the corresponding PE VRF.

  IP Availability Manager also adds to MPLS-System any non-MPLS-enabled device that connects directly to an MPLS-enabled device. A non-MPLS-enabled device is any provider device, such as a CE (non-Multi-VRF CE), that has no MPLS functionality.

  Note:

  The MPLS Topology Server also creates an MPLS topology collection set named MPLS-Interface, in which it stores the interfaces that are involved in MPLS impact analysis.

  The MPLS light discovery feature is described in the VMware Smart Assurance IP Manager Concepts Guide and the VMware Smart Assurance IP Manager User Guide. Instructions for enabling the MPLS light discovery feature are given in “Enabling and customizing MPLS light discovery” on page 76.