Reference record for OID 1.3.6.1.4.1.9.9.197.1.2.3.1

parent

1.3.6.1.4.1.9.9.197.1.2.3 (cddHostTolCfgTable)

node code

1

node name

cddHostTolCfgEntry

dot oid

1.3.6.1.4.1.9.9.197.1.2.3.1

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoDistDirMIB(197) ciscoDistDirMIBObjects(1) cddHost(2) cddHostTolCfgTable(3) cddHostTolCfgEntry(1)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

/iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

/iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoDistDirMIB/ciscoDistDirMIBObjects/cddHost/cddHostTolCfgTable/cddHostTolCfgEntry

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/9/9/197/1/2/3/1

Description by circitor

An entry containing Distributed Director per-host
metrics tolerance information at a priority level. If
at a priority level two or more remote servers have
metric values that are within a certain tolerance
percentage of each other, they are considered to be the
same and thus causing a 'tie'. In this case, the metrics
at the next priority level will be used in order to
break the tie.

For example, the DRP RTT metric is given priority 1 and
the DRP external metric is given priority 2; and the
tolerance percentage value is set to 20 at priority 1.
If server 'A' has the DRP RTT metric value of 100 and
server 'B' has the value of 119, they will be
considered the same because their difference is within
20% of the metric value of server 'A'. Then the DRP
external metric will be used to select the best server.

Entries in this table may be queried, created or
deleted by NMS. Each entry in this table is dependent
on entries in cddHostTable. If the associated entry in
cddHostTable that has the same cddHostName and
cddHostQueryType values is deleted, the entry in this
table is deleted as well.

Parsed from file CISCO-DIST-DIRECTOR-MIB.mib
Module: CISCO-DIST-DIRECTOR-MIB

Description by cisco_v1

An entry containing Distributed Director per-host
metrics tolerance information at a priority level. If
at a priority level two or more remote servers have
metric values that are within a certain tolerance
percentage of each other, they are considered to be the
same and thus causing a 'tie'. In this case, the metrics
at the next priority level will be used in order to
break the tie.

For example, the DRP RTT metric is given priority 1 and
the DRP external metric is given priority 2; and the
tolerance percentage value is set to 20 at priority 1.
If server 'A' has the DRP RTT metric value of 100 and
server 'B' has the value of 119, they will be
considered the same because their difference is within
20% of the metric value of server 'A'. Then the DRP
external metric will be used to select the best server.

Entries in this table may be queried, created or
deleted by NMS. Each entry in this table is dependent
on entries in cddHostTable. If the associated entry in
cddHostTable that has the same cddHostName and
cddHostQueryType values is deleted, the entry in this
table is deleted as well.

Description by mibdepot

An entry containing Distributed Director per-host
metrics tolerance information at a priority level. If
at a priority level two or more remote servers have
metric values that are within a certain tolerance
percentage of each other, they are considered to be the
same and thus causing a 'tie'. In this case, the metrics
at the next priority level will be used in order to
break the tie.

For example, the DRP RTT metric is given priority 1 and
the DRP external metric is given priority 2; and the
tolerance percentage value is set to 20 at priority 1.
If server 'A' has the DRP RTT metric value of 100 and
server 'B' has the value of 119, they will be
considered the same because their difference is within
20% of the metric value of server 'A'. Then the DRP
external metric will be used to select the best server.

Entries in this table may be queried, created or
deleted by NMS. Each entry in this table is dependent
on entries in cddHostTable. If the associated entry in
cddHostTable that has the same cddHostName and
cddHostQueryType values is deleted, the entry in this
table is deleted as well.

Parsed from file CISCO-DIST-DIRECTOR-MIB.my.txt
Company: None
Module: CISCO-DIST-DIRECTOR-MIB

Description by cisco

An entry containing Distributed Director per-host
metrics tolerance information at a priority level. If
at a priority level two or more remote servers have
metric values that are within a certain tolerance
percentage of each other, they are considered to be the
same and thus causing a 'tie'. In this case, the metrics
at the next priority level will be used in order to
break the tie.

For example, the DRP RTT metric is given priority 1 and
the DRP external metric is given priority 2; and the
tolerance percentage value is set to 20 at priority 1.
If server 'A' has the DRP RTT metric value of 100 and
server 'B' has the value of 119, they will be
considered the same because their difference is within
20% of the metric value of server 'A'. Then the DRP
external metric will be used to select the best server.

Entries in this table may be queried, created or
deleted by NMS. Each entry in this table is dependent
on entries in cddHostTable. If the associated entry in
cddHostTable that has the same cddHostName and
cddHostQueryType values is deleted, the entry in this
table is deleted as well.

Information by circitor

cddHostTolCfgEntry OBJECT-TYPE
    SYNTAX CddHostTolCfgEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "An entry containing Distributed Director per-host
        metrics tolerance information at a priority level. If
        at a priority level two or more remote servers have
        metric values that are within a certain tolerance
        percentage of each other, they are considered to be the
        same and thus causing a 'tie'. In this case, the metrics
        at the next priority level will be used in order to
        break the tie.
        
        For example, the DRP RTT metric is given priority 1 and
        the DRP external metric is given priority 2; and the
        tolerance percentage value is set to 20 at priority 1.
        If server 'A' has the DRP RTT metric value of 100 and
        server 'B' has the value of 119, they will be
        considered the same because their difference is within
        20% of the metric value of server 'A'. Then the DRP
        external metric will be used to select the best server.
        
        Entries in this table may be queried, created or
        deleted by NMS. Each entry in this table is dependent
        on entries in cddHostTable. If the associated entry in
        cddHostTable that has the same cddHostName and
        cddHostQueryType values is deleted, the entry in this
        table is deleted as well."
    INDEX { cddHostName, cddHostQueryType, cddHostTolCfgPrio }
    ::= { cddHostTolCfgTable 1 }

Information by cisco_v1

cddHostTolCfgEntry OBJECT-TYPE
    SYNTAX CddHostTolCfgEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
        "An entry containing Distributed Director per-host
        metrics tolerance information at a priority level. If
        at a priority level two or more remote servers have
        metric values that are within a certain tolerance
        percentage of each other, they are considered to be the
        same and thus causing a 'tie'. In this case, the metrics
        at the next priority level will be used in order to
        break the tie.
        
        For example, the DRP RTT metric is given priority 1 and
        the DRP external metric is given priority 2; and the
        tolerance percentage value is set to 20 at priority 1.
        If server 'A' has the DRP RTT metric value of 100 and
        server 'B' has the value of 119, they will be
        considered the same because their difference is within
        20% of the metric value of server 'A'. Then the DRP
        external metric will be used to select the best server.
        
        Entries in this table may be queried, created or
        deleted by NMS. Each entry in this table is dependent
        on entries in cddHostTable. If the associated entry in
        cddHostTable that has the same cddHostName and
        cddHostQueryType values is deleted, the entry in this
        table is deleted as well."
    INDEX { cddHostName, cddHostQueryType, cddHostTolCfgPrio }
    ::= { cddHostTolCfgTable 1 }

Information by oid_info

Vendor: Cisco
Module: CISCO-DIST-DIRECTOR-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

cddHostTolCfgEntry OBJECT-TYPE
    SYNTAX     CddHostTolCfgEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
        "An entry containing Distributed Director per-host
        metrics tolerance information at a priority level. If
        at a priority level two or more remote servers have
        metric values that are within a certain tolerance
        percentage of each other, they are considered to be the
        same and thus causing a 'tie'. In this case, the metrics
        at the next priority level will be used in order to
        break the tie.

        For example, the DRP RTT metric is given priority 1 and
        the DRP external metric is given priority 2; and the
        tolerance percentage value is set to 20 at priority 1.
        If server 'A' has the DRP RTT metric value of 100 and
        server 'B' has the value of 119, they will be
        considered the same because their difference is within
        20% of the metric value of server 'A'. Then the DRP
        external metric will be used to select the best server.

        Entries in this table may be queried, created or
        deleted by NMS. Each entry in this table is dependent
        on entries in cddHostTable. If the associated entry in
        cddHostTable that has the same cddHostName and
        cddHostQueryType values is deleted, the entry in this
        table is deleted as well."
    INDEX    { cddHostName, cddHostQueryType, cddHostTolCfgPrio }
    ::= { cddHostTolCfgTable 1 }

Information by cisco

cddHostTolCfgEntry OBJECT-TYPE
    SYNTAX     CddHostTolCfgEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
        "An entry containing Distributed Director per-host
        metrics tolerance information at a priority level. If
        at a priority level two or more remote servers have
        metric values that are within a certain tolerance
        percentage of each other, they are considered to be the
        same and thus causing a 'tie'. In this case, the metrics
        at the next priority level will be used in order to
        break the tie.

        For example, the DRP RTT metric is given priority 1 and
        the DRP external metric is given priority 2; and the
        tolerance percentage value is set to 20 at priority 1.
        If server 'A' has the DRP RTT metric value of 100 and
        server 'B' has the value of 119, they will be
        considered the same because their difference is within
        20% of the metric value of server 'A'. Then the DRP
        external metric will be used to select the best server.

        Entries in this table may be queried, created or
        deleted by NMS. Each entry in this table is dependent
        on entries in cddHostTable. If the associated entry in
        cddHostTable that has the same cddHostName and
        cddHostQueryType values is deleted, the entry in this
        table is deleted as well."
    INDEX    { cddHostName, cddHostQueryType, cddHostTolCfgPrio }
    ::= { cddHostTolCfgTable 1 }

First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Children (3)