All MIBs › DTI-MIB › dtiProtocolClientPathTraceability
dtiProtocolClientPathTraceability
Module: DTI-MIB
OID (symbolic): DTI-MIB::dtiProtocolClientPathTraceability
OID (numeric): 1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: A reference to the index of dtiPathTraceabilityTable to which this DTI Client-Server connection has associated its traceable path. It is likely that many traceable paths of DTI clients would have the same rootServer and proxy server for multiple Client Server. A manager application can build the Traceability Path, e.g., of a DTI client, if reading this entry from a proxy DTI server as follows:
Client: This entry DTI Client IP Address, This entry ifIndex, (see below) dtiProtocolClientVersion Proxy Server: dtiPathTraceabilityServerInetAddr, dtiPathTraceabilityServerOutPhyIdx, dtiPathTraceabilityServerProtVersion RootServer: dtiPathTraceabilityRootServerInetAddr, dtiPathTraceabilityRootServerOutPhyIdx, dtiPathTraceabilityRootServerProtVersion
For the DTI client the Physical port would correspond to: PhysicalIndex where entAliasMappingIdentifier.PhysicalIndex = ifIndex
What is dtiProtocolClientPathTraceability?
Points to the row in dtiPathTraceabilityTable describing the traceable clock-distribution path (root server and any proxy server) this client-server connection uses, so an admin can walk the chain back to the ultimate timing source.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12 snmpwalk -v2c -c public <target> DTI-MIB::dtiProtocolClientPathTraceability
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12.1 snmpget -v2c -c public <target> DTI-MIB::dtiProtocolClientPathTraceability.1
Start monitoring DOCSIS 3.1 CMTS/CCAP timing server/client (DOCSIS Timing Interface) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DTI-MIB::dtiProtocolClientPathTraceability OID value, configure state conditions and alerts, and monitor any DOCSIS 3.1 CMTS/CCAP timing server/client (DOCSIS Timing Interface) from a single console.
OID Breakdown
Upper-level ancestors (10 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.4491 | cableLabs | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2 | clabProject | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2.1 | clabProjDocsis | CLAB-DEF-MIB |
| 1.3.6.1.4.1.4491.2.1.7 | dtiMib | CLAB-DEF-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.4491.2.1.7.1 | dtiMibObjects | DTI-MIB |
| 1.3.6.1.4.1.4491.2.1.7.1.1 | dtiProtocolObjects | DTI-MIB |
| 1.3.6.1.4.1.4491.2.1.7.1.1.1 | dtiProtocolTable | DTI-MIB |
| 1.3.6.1.4.1.4491.2.1.7.1.1.1.1 | dtiProtocolEntry | DTI-MIB |
| 1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12 | dtiProtocolClientPathTraceability | DTI-MIB |