MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 4491 (cableLabs). 2 (clabProject). 1 (clabProjDocsis). 7 (dtiMib). 1 (dtiMibObjects). 1 (dtiProtocolObjects). 1 (dtiProtocolTable). 1 (dtiProtocolEntry). 12 (dtiProtocolClientPathTraceability)
OID : 1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12
TXT : iso. org. dod. internet. private. enterprises. cableLabs. clabProject. clabProjDocsis. dtiMib. dtiMibObjects. dtiProtocolObjects. dtiProtocolTable. dtiProtocolEntry. dtiProtocolClientPathTraceability
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.4491.2.1.7.1.1.1.1.12
Module DTI-MIB (CISCO)
NomdtiProtocolClientPathTraceability
Accesreadonly
Statuscurrent
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
SyntaxeUnsigned32 (0...4294967295)