Verifying a Multihomed VPLS Connection Using SNMP MIB Walks
Purpose
Monitor a BGP-based VPLS multihoming configuration.
The Junos OS also enables you to use SNMP MIB walks to validate multihomed VPLS connections. This section explains the various MIB objects and traps that help you monitor BGP-based VPLS.
The SNMP walks show values configured in Example: Configuring a Multihomed VPLS (FEC 128).
Action
user@PE1> show snmp mib walk jnxVpnTablejnxVpnRowStatus.4."vpls1" = 1 jnxVpnRowStatus.4."vpls-multihoming" = 1 jnxVpnStorageType.4."vpls1" = 5 jnxVpnStorageType.4."vpls-multihoming" = 5 jnxVpnDescription.4."vpls1" = vpls1 jnxVpnDescription.4."vpls-multihoming" = vpls-multihoming jnxVpnIdentifierType.4."vpls1" = 5 jnxVpnIdentifierType.4."vpls-multihoming" = 5 jnxVpnIdentifier.4."vpls1" = 5-65052:1 jnxVpnIdentifier.4."vpls-multihoming" = 5-65410:102 jnxVpnConfiguredSites.4."vpls1" = 0 jnxVpnConfiguredSites.4."vpls-multihoming" = 0 jnxVpnActiveSites.4."vpls1" = 0 jnxVpnActiveSites.4."vpls-multihoming" = 0 jnxVpnLocalAddresses.4."vpls1" = 0 jnxVpnLocalAddresses.4."vpls-multihoming" = 0 jnxVpnTotalAddresses.4."vpls1" = 0 jnxVpnTotalAddresses.4."vpls-multihoming" = 0 jnxVpnAge.4."vpls1" = 19395600 jnxVpnAge.4."vpls-multihoming" = 19395600
user@PE1> show snmp mib walk jnxVpnIfTablejnxVpnIfRowStatus.4."vpls1".215 = 1 jnxVpnIfRowStatus.4."vpls1".225 = 1 jnxVpnIfRowStatus.4."vpls-multihoming".247 = 1 jnxVpnIfStorageType.4."vpls1".215 = 5 jnxVpnIfStorageType.4."vpls1".225 = 5 jnxVpnIfStorageType.4."vpls-multihoming".247 = 5 jnxVpnIfAssociatedPw.4."vpls1".215 = 0 jnxVpnIfAssociatedPw.4."vpls1".225 = 0 jnxVpnIfAssociatedPw.4."vpls-multihoming".247 = 0 jnxVpnIfProtocol.4."vpls1".215 = 11 jnxVpnIfProtocol.4."vpls1".225 = 11 jnxVpnIfProtocol.4."vpls-multihoming".247 = 11 jnxVpnIfInBandwidth.4."vpls1".215 = 0 jnxVpnIfInBandwidth.4."vpls1".225 = 0 jnxVpnIfInBandwidth.4."vpls-multihoming".247 = 0 jnxVpnIfOutBandwidth.4."vpls1".215 = 0 jnxVpnIfOutBandwidth.4."vpls1".225 = 0 jnxVpnIfOutBandwidth.4."vpls-multihoming".247 = 0 jnxVpnIfStatus.4."vpls1".215 = 5 jnxVpnIfStatus.4."vpls1".225 = 5 jnxVpnIfStatus.4."vpls-multihoming".247 = 5
user@PE1> show snmp mib walk jnxVpnPwTable jnxVpnPwRowStatus.4."vpls1".262147 = 1 jnxVpnPwRowStatus.4."vpls-multihoming".655380 = 1 jnxVpnPwStorageType.4."vpls1".262147 = 5 jnxVpnPwStorageType.4."vpls-multihoming".655380 = 5 jnxVpnPwAssociatedInterface.4."vpls1".262147 = 269 jnxVpnPwAssociatedInterface.4."vpls-multihoming".655380 = 270 jnxVpnPwLocalSiteId.4."vpls1".262147 = 4 jnxVpnPwLocalSiteId.4."vpls-multihoming".655380 = 10 jnxVpnPwRemoteSiteId.4."vpls1".262147 = 3 jnxVpnPwRemoteSiteId.4."vpls-multihoming".655380 = 20 jnxVpnRemotePeIdAddrType.4."vpls1".262147 = 1 jnxVpnRemotePeIdAddrType.4."vpls-multihoming".655380 = 1 jnxVpnRemotePeIdAddress.4."vpls1".262147 = 192.1.1.6 jnxVpnRemotePeIdAddress.4."vpls-multihoming".655380 = 192.1.1.3 jnxVpnPwTunnelType.4."vpls1".262147 = 6 jnxVpnPwTunnelType.4."vpls-multihoming".655380 = 6 jnxVpnPwTunnelName.4."vpls1".262147 = pe1-to-pe3 jnxVpnPwTunnelName.4."vpls-multihoming".655380 = pe1-to-pe2 jnxVpnPwReceiveDemux.4."vpls1".262147 = 262171 jnxVpnPwReceiveDemux.4."vpls-multihoming".655380 = 262164 jnxVpnPwTransmitDemux.4."vpls1".262147 = 262148 jnxVpnPwTransmitDemux.4."vpls-multihoming".655380 = 262154 jnxVpnPwStatus.4."vpls1".262147 = 2 jnxVpnPwStatus.4."vpls-multihoming".655380 = 2 jnxVpnPwTunnelStatus.4."vpls1".262147 = 0 jnxVpnPwTunnelStatus.4."vpls-multihoming".655380 = 0 jnxVpnPwRemoteSiteStatus.4."vpls1".262147 = 0 jnxVpnPwRemoteSiteStatus.4."vpls-multihoming".655380 = 0 jnxVpnPwTimeUp.4."vpls1".262147 = 19357900 jnxVpnPwTimeUp.4."vpls-multihoming".655380 = 19165500 jnxVpnPwTransitions.4."vpls1".262147 = 1 jnxVpnPwTransitions.4."vpls-multihoming".655380 = 1 jnxVpnPwLastTransition.4."vpls1".262147 = 19357900 jnxVpnPwLastTransition.4."vpls-multihoming".655380 = 19165500 jnxVpnPwPacketsSent.4."vpls1".262147 = 0 jnxVpnPwPacketsSent.4."vpls-multihoming".655380 = 0 jnxVpnPwOctetsSent.4."vpls1".262147 = 0 jnxVpnPwOctetsSent.4."vpls-multihoming".655380 = 0 jnxVpnPwPacketsReceived.4."vpls1".262147 = 0 jnxVpnPwPacketsReceived.4."vpls-multihoming".655380 = 0 jnxVpnPwOctetsReceived.4."vpls1".262147 = 0 jnxVpnPwOctetsReceived.4."vpls-multihoming".655380 = 0 jnxVpnPwLRPacketsSent.4."vpls1".262147 = 0 jnxVpnPwLRPacketsSent.4."vpls-multihoming".655380 = 0 jnxVpnPwLROctetsSent.4."vpls1".262147 = 0 jnxVpnPwLROctetsSent.4."vpls-multihoming".655380 = 0 jnxVpnPwLRPacketsReceived.4."vpls1".262147 = 0 jnxVpnPwLRPacketsReceived.4."vpls-multihoming".655380 = 0 jnxVpnPwLROctetsReceived.4."vpls1".262147 = 0 jnxVpnPwLROctetsReceived.4."vpls-multihoming".655380 = 0
user@PE1> show snmp mib walk jnxVpnRTTablejnxVpnRTRowStatus.4."vpls1".1 = 1 jnxVpnRTRowStatus.4."vpls-multihoming".1 = 1 jnxVpnRTStorageType.4."vpls1".1 = 5 jnxVpnRTStorageType.4."vpls-multihoming".1 = 5 jnxVpnRTType.4."vpls1".1 = 6 jnxVpnRTType.4."vpls-multihoming".1 = 6 jnxVpnRT.4."vpls1".1 = 65052:1 jnxVpnRT.4."vpls-multihoming".1 = 65410:0 jnxVpnRTFunction.4."vpls1".1 = 3 jnxVpnRTFunction.4."vpls-multihoming".1 = 3