Reference record for OID 1.3.6.1.4.1.9.10.133.1.5.1.1.3

parent

1.3.6.1.4.1.9.10.133.1.5.1.1 (cdbpRealmKnownPeersEntry)

node code

3

node name

cdbpRealmKnownPeersChosen

dot oid

1.3.6.1.4.1.9.10.133.1.5.1.1.3

type

OBJECT-TYPE

asn1 oid

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoExperiment(10) ciscoDiameterBasePMIB(133) ciscoDiameterBasePMIBObjects(1) cdbpRealmCfgs(5) cdbpRealmKnownPeersTable(1) cdbpRealmKnownPeersEntry(1) cdbpRealmKnownPeersChosen(3)}

iri oid

/iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

/iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

/iso/org/dod/internet/private/enterprise/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

/iso/org/dod/internet/private/enterprises/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

/iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

/iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoExperiment/ciscoDiameterBasePMIB/ciscoDiameterBasePMIBObjects/cdbpRealmCfgs/cdbpRealmKnownPeersTable/cdbpRealmKnownPeersEntry/cdbpRealmKnownPeersChosen

iri by oid_info

/ISO/Identified-Organization/6/1/4/1/9/10/133/1/5/1/1/3

Description by circitor

How the realm chooses which peer to send
packets to.
roundRobin(1) - The peer used for each transaction
is selected based on the order in
which peers are configured.
loadBalance(2) - The peer used for each transaction
is based on the load metric (maybe
implementation dependent) of all
peers defined for the realm, with
the least loaded server selected
first.
firstPreferred(3) - The first defined server is always
used for transactions unless
failover occurs.
mostRecentFirst(4) - The most recently used server is
used first for each transaction.

Parsed from file CISCO-DIAMETER-BASE-PROTOCOL-MIB.mib
Module: CISCO-DIAMETER-BASE-PROTOCOL-MIB

Description by cisco_v1

How the realm chooses which peer to send
packets to.
roundRobin(1) - The peer used for each transaction
is selected based on the order in
which peers are configured.
loadBalance(2) - The peer used for each transaction
is based on the load metric (maybe
implementation dependent) of all
peers defined for the realm, with
the least loaded server selected
first.
firstPreferred(3) - The first defined server is always
used for transactions unless
failover occurs.
mostRecentFirst(4) - The most recently used server is
used first for each transaction.

Description by mibdepot

How the realm chooses which peer to send
packets to.
roundRobin(1) - The peer used for each transaction
is selected based on the order in
which peers are configured.
loadBalance(2) - The peer used for each transaction
is based on the load metric (maybe
implementation dependent) of all
peers defined for the realm, with
the least loaded server selected
first.
firstPreferred(3) - The first defined server is always
used for transactions unless
failover occurs.
mostRecentFirst(4) - The most recently used server is
used first for each transaction.

Parsed from file CISCO-DIAMETER-BASE-PROTOCOL-MIB.my.txt
Company: None
Module: CISCO-DIAMETER-BASE-PROTOCOL-MIB

Description by cisco

How the realm chooses which peer to send
packets to.
roundRobin(1) - The peer used for each transaction
is selected based on the order in
which peers are configured.
loadBalance(2) - The peer used for each transaction
is based on the load metric (maybe
implementation dependent) of all
peers defined for the realm, with
the least loaded server selected
first.
firstPreferred(3) - The first defined server is always
used for transactions unless
failover occurs.
mostRecentFirst(4) - The most recently used server is
used first for each transaction.

Information by circitor

cdbpRealmKnownPeersChosen OBJECT-TYPE
    SYNTAX          INTEGER  {
                        roundRobin(1),
                        loadBalance(2),
                        firstPreferred(3),
                        mostRecentFirst(4),
                        other(5)
                    }
    MAX-ACCESS      read-only
    STATUS          current
    DESCRIPTION
            "How the realm chooses which peer to send
            packets to.
               roundRobin(1)      - The peer used for each transaction
                                    is selected based on the order in
                                    which peers are configured.
               loadBalance(2)     - The peer used for each transaction
                                    is based on the load metric (maybe
                                    implementation dependent) of all
                                    peers defined for the realm, with
                                    the least loaded server selected
                                    first.
               firstPreferred(3)  - The first defined server is always
                                    used for transactions unless
                                    failover occurs.
               mostRecentFirst(4) - The most recently used server is
                                    used first for each transaction." 
    ::= { cdbpRealmKnownPeersEntry 3 }

Information by cisco_v1

cdbpRealmKnownPeersChosen OBJECT-TYPE
    SYNTAX INTEGER {
        roundRobin(1),
        loadBalance(2),
        firstPreferred(3),
        mostRecentFirst(4),
        other(5)
        }
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "How the realm chooses which peer to send
        packets to.
           roundRobin(1)      - The peer used for each transaction
                                is selected based on the order in
                                which peers are configured.
           loadBalance(2)     - The peer used for each transaction
                                is based on the load metric (maybe
                                implementation dependent) of all
                                peers defined for the realm, with
                                the least loaded server selected
                                first.
           firstPreferred(3)  - The first defined server is always
                                used for transactions unless
                                failover occurs.
           mostRecentFirst(4) - The most recently used server is
                                used first for each transaction."
    ::= { cdbpRealmKnownPeersEntry 3 }

Information by oid_info

Vendor: Cisco
Module: CISCO-DIAMETER-BASE-PROTOCOL-MIB

[Automatically extracted from oidview.com]

Information by mibdepot

cdbpRealmKnownPeersChosen OBJECT-TYPE
    SYNTAX          INTEGER  {
                        roundRobin(1),
                        loadBalance(2),
                        firstPreferred(3),
                        mostRecentFirst(4),
                        other(5)
                    }
    MAX-ACCESS      read-only
    STATUS          current
    DESCRIPTION
            "How the realm chooses which peer to send
            packets to.
               roundRobin(1)      - The peer used for each transaction
                                    is selected based on the order in
                                    which peers are configured.
               loadBalance(2)     - The peer used for each transaction
                                    is based on the load metric (maybe
                                    implementation dependent) of all
                                    peers defined for the realm, with
                                    the least loaded server selected
                                    first.
               firstPreferred(3)  - The first defined server is always
                                    used for transactions unless
                                    failover occurs.
               mostRecentFirst(4) - The most recently used server is
                                    used first for each transaction." 
    ::= { cdbpRealmKnownPeersEntry 3 }

Information by cisco

cdbpRealmKnownPeersChosen OBJECT-TYPE
    SYNTAX          INTEGER  {
                        roundRobin(1),
                        loadBalance(2),
                        firstPreferred(3),
                        mostRecentFirst(4),
                        other(5)
                    }
    MAX-ACCESS      read-only
    STATUS          current
    DESCRIPTION
            "How the realm chooses which peer to send
            packets to.
               roundRobin(1)      - The peer used for each transaction
                                    is selected based on the order in
                                    which peers are configured.
               loadBalance(2)     - The peer used for each transaction
                                    is based on the load metric (maybe
                                    implementation dependent) of all
                                    peers defined for the realm, with
                                    the least loaded server selected
                                    first.
               firstPreferred(3)  - The first defined server is always
                                    used for transactions unless
                                    failover occurs.
               mostRecentFirst(4) - The most recently used server is
                                    used first for each transaction." 
    ::= { cdbpRealmKnownPeersEntry 3 }

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.

Brothers (2)