All MIBs › ZXR10-LSP-PING-MIB › lspPingLdpPrefix
lspPingLdpPrefix
Module: ZXR10-LSP-PING-MIB
OID (symbolic): ZXR10-LSP-PING-MIB::lspPingLdpPrefix
OID (numeric): 1.3.6.1.4.1.3902.3.104.5.1.1.3
Node type: OBJECT-TYPE
Type: IpAddress
Access: read-write
Description: ldp prefix
What is lspPingLdpPrefix?
The IPv4 destination prefix (FEC) to test reachability for when running an LDP-based LSP ping.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.104.5.1.1.3 snmpwalk -v2c -c public <target> ZXR10-LSP-PING-MIB::lspPingLdpPrefix
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.104.5.1.1.3.1 snmpget -v2c -c public <target> ZXR10-LSP-PING-MIB::lspPingLdpPrefix.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.3902.3.104.5.1.1.3.1 a <value>
Start monitoring ZTE ZXR10 router (MPLS-enabled) (LSP-ping OAM test-result/round-trip status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-LSP-PING-MIB::lspPingLdpPrefix OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 router (MPLS-enabled) (LSP-ping OAM test-result/round-trip status) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.3902 | zte | DPI-MIB |
| 1.3.6.1.4.1.3902.3 | zxr10 | FANS-POWER-MIB |
| 1.3.6.1.4.1.3902.3.104 | zxr10l2vpn | ZXR10-L2VPN-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3902.3.104.5 | zxr10LspPingMIB | ZXR10-LSP-PING-MIB |
| 1.3.6.1.4.1.3902.3.104.5.1 | lspPingTable | ZXR10-LSP-PING-MIB |
| 1.3.6.1.4.1.3902.3.104.5.1.1 | lspPingEntry | ZXR10-LSP-PING-MIB |
| 1.3.6.1.4.1.3902.3.104.5.1.1.3 | lspPingLdpPrefix | ZXR10-LSP-PING-MIB |