All MIBs › ZXR10-LSPPING-MIB › lspPingResultSentPkts
lspPingResultSentPkts
Module: ZXR10-LSPPING-MIB
OID (symbolic): ZXR10-LSPPING-MIB::lspPingResultSentPkts
OID (numeric): 1.3.6.1.4.1.3902.3.104.5.2.1.2
Node type: OBJECT-TYPE
Type: Integer32
Access: read-only
Description: send packet
What is lspPingResultSentPkts?
The number of LSP ping packets actually sent for this test, which an admin compares against lspPingResultRcvPkts to compute packet loss along the LSP.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.104.5.2.1.2 snmpwalk -v2c -c public <target> ZXR10-LSPPING-MIB::lspPingResultSentPkts
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.104.5.2.1.2.1 snmpget -v2c -c public <target> ZXR10-LSPPING-MIB::lspPingResultSentPkts.1
Start monitoring ZTE ZXR10 carrier routers/switches (LSP-ping request/result round-trip-time status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-LSPPING-MIB::lspPingResultSentPkts OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 carrier routers/switches (LSP-ping request/result round-trip-time status) from a single console.
OID Breakdown
Upper-level ancestors (12 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 |
| 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.2 | lspPingResultTable | ZXR10-LSP-PING-MIB |
| 1.3.6.1.4.1.3902.3.104.5.2.1 | lspPingResultEntry | ZXR10-LSP-PING-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3902.3.104.5.2.1.2 | lspPingResultSentPkts | ZXR10-LSPPING-MIB |