The MPLS Topology Server reads the standard and enterprise MIB objects that are identified in this section to discover the following L3VPN topology objects and their relationships:
-
VPN
-
VRF
-
RouteTarget
After discovering and creating the L3VPN topology objects in its repository, the MPLS Topology Server monitors the status of the L3VPN objects by periodically establishing SNMP sessions to the managed devices and polling the MIB objects.
MIB objects accessed for L3VPN discovery lists the MIB objects that are accessed by the MPLS Topology Server for L3VPN discovery.
MIB object |
OID |
---|---|
MPLS-VPN-MIB |
|
mplsVpnConfiguredVrfs |
.1.3.6.1.3.118.1.1.1 |
mplsVpnIfConfTable |
.1.3.6.1.3.118.1.2.1 |
mplsVpnVrfTable |
.1.3.6.1.3.118.1.2.2 |
mplsVpnVrfRouteTargetTable |
.1.3.6.1.3.118.1.2.3 |
MPLS-L3VPN-STD-MIB |
|
mplsVpnConfiguredVrfs |
.1.3.6.1.2.1.10.166.11.1.1.1.0 |
mplsVpnIfVpnClassification |
.1.3.6.1.2.1.10.166.11.1.2.1.1.2 |
mplsVpnVrfRouteDistinguisher |
.1.3.6.1.2.1.10.166.11.1.2.2.1.4 |
mplsVpnVrfRouteTarget |
.1.3.6.1.2.1.10.166.11.1.2.3.1.4 |
JUNIPER-VPN-MIB |
|
jnxVpnDescriptionOID |
.1.3.6.1.4.1.2636.3.26.1.2.1.5 |
jnxVpnIdentifierTypeOID |
.1.3.6.1.4.1.2636.3.26.1.2.1.6 |
jnxVpnIdentifierOID |
.1.3.6.1.4.1.2636.3.26.1.2.1.7 |
jnxVpnIfAssociatedPw |
.1.3.6.1.4.1.2636.3.26.1.3.1.6 |
jnxVpnPwAssociatedInterface |
.1.3.6.1.4.1.2636.3.26.1.4.1.6 |
jnxVpnPwLocalSiteId |
.1.3.6.1.4.1.2636.3.26.1.4.1.7 |
jnxVpnPwRemoteSiteId |
.1.3.6.1.4.1.2636.3.26.1.4.1.8 |
jnxVpnRemotePeIdAddrType |
.1.3.6.1.4.1.2636.3.26.1.4.1.9 |
jnxVpnRemotePeIdAddress |
.1.3.6.1.4.1.2636.3.26.1.4.1.10 |
jnxVpnPwTunnelType |
.1.3.6.1.4.1.2636.3.26.1.4.1.11 |
jnxVpnPwTunnelName |
.1.3.6.1.4.1.2636.3.26.1.4.1.12 |
jnxVpnPwReceiveDemux |
.1.3.6.1.4.1.2636.3.26.1.4.1.13 |
jnxVpnPwTransmitDemux |
.1.3.6.1.4.1.2636.3.26.1.4.1.14 |
jnxVpnRTTypeOID |
.1.3.6.1.4.1.2636.3.26.1.5.1.6 |
jnxVpnRTOID |
.1.3.6.1.4.1.2636.3.26.1.5.1.7 |
jnxVpnRTFunctionOID |
.1.3.6.1.4.1.2636.3.26.1.5.1.8 |
mplsVpnIfConfRowStatusOID |
.1.3.6.1.4.1.2636.3.26.1.3.1.4 |
If SNMP discovery is not successful or is not supported for a device, or if additional information is needed for a device, the MPLS Topology Server performs CLI discovery by invoking the commands that are identified in Appendix B, “CLI Commands Invoked for Discovery and LSP Ping.”