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.
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:
OID for MPLS-LSR-STD-MIB
For juniper, we query the table:
For the timetra (TE) mib, we query: vRtrMplsLspEntry