What OID's are used to discover MPLS in the Spectrum MPLS transport Manager

Products

• CA Spectrum
• DX NetOps

Issue/Introduction

Looking for clarification on the discovery mechanism behind the MPLS transport manager. We are looking to understand what OID's or what process of discovery is invoked when you click the "Run" button within the MPLS Transport Manager --> Configuration --> LSP Discovery.

Environment

Release: All Supported Releases
Component: SPCAPP - Applications

Resolution

MPLS Transport Manager runs across selected landscapes and models the relationships between the PE routers, Paths, devices, and hops to monitor any changes in the Primary/Secondary Label Switched Paths.

The default oid for the MPLS TE are:
1.3.6.1.3.95.1.1.0
1.3.6.1.3.95.2.2.1.31
1.3.6.1.3.95.2.2.1.7

OID for MPLS-LSR-STD-MIB
1.3.6.1.2.1.10.166

For Juniper, we query the tables:
mplsLspEntry 1.3.6.1.4.1.2636.3.2.3.1
mplsVersion 1.3.6.1.4.1.2636.3.2.1.1.0
mplsLspInfoState 1.3.6.1.4.1.2636.3.2.5.1.2

For the timetra (TE) mib, we query: vRtrMplsLspEntry
1.3.6.1.4.1.6527.3.1.2.6.1.1

Additional Information

For Juniper the initial code would query mpslLspEntry table to discover the LSPs.  This has been deprecated by Juniper.   The Juniper Networks enterprise-specific MPLS MIB, whose object identifier is {jnxMibs 2}, provides information about MPLS paths and defines MPLS notifications. 
The table mplsLspList and the sequence for mplsLspEntry have been deprecated and replaced by a new table mplsLspInfoList to extend support for LSP names longer than 32 characters.  mplsLspInfoState is contained within the mplsLspInfoList table.