All MIBs › ZXR10-TRACE-MIB › zxr10LspTraceHopsType
zxr10LspTraceHopsType
Module: ZXR10-TRACE-MIB
OID (symbolic): ZXR10-TRACE-MIB::zxr10LspTraceHopsType
OID (numeric): 1.3.6.1.4.1.3902.3.318.1.3.1.4
Node type: OBJECT-TYPE
Type: HopType
Access: read-only
Description: Hop Type (0:Ingress,1:Downstream,2:Egress)
What is zxr10LspTraceHopsType?
Classifies this hop's role in the LSP path as ingress, downstream (transit), or egress. Use it to tell where in the path a problem hop actually sits.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3902.3.318.1.3.1.4 snmpwalk -v2c -c public <target> ZXR10-TRACE-MIB::zxr10LspTraceHopsType
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.3902.3.318.1.3.1.4.1 snmpget -v2c -c public <target> ZXR10-TRACE-MIB::zxr10LspTraceHopsType.1
Start monitoring ZTE ZXR10 routers/switches (SNMP-driven traceroute hop/round-trip-latency status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ZXR10-TRACE-MIB::zxr10LspTraceHopsType OID value, configure state conditions and alerts, and monitor any ZTE ZXR10 routers/switches (SNMP-driven traceroute hop/round-trip-latency status) from a single console.
OID Breakdown
Upper-level ancestors (8 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 |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3902.3.318 | trace | ZXR10-TRACE-MIB |
| 1.3.6.1.4.1.3902.3.318.1 | zxr10LspTrace | ZXR10-TRACE-MIB |
| 1.3.6.1.4.1.3902.3.318.1.3 | zxr10LspTraceHopsTable | ZXR10-TRACE-MIB |
| 1.3.6.1.4.1.3902.3.318.1.3.1 | zxr10LspTraceHopsEntry | ZXR10-TRACE-MIB |
| 1.3.6.1.4.1.3902.3.318.1.3.1.4 | zxr10LspTraceHopsType | ZXR10-TRACE-MIB |