Reference record for OID 1.3.6.1.4.1.4874.2.2.32.1.3.1.3



parent
1.3.6.1.4.1.4874.2.2.32.1.3.1 (juniRouterProtocolEntry, usdRouterProtocolEntry)
node code
3
node names
  • juniRouterProtocolRowStatus
  • usdRouterProtocolRowStatus
  • dot oid
    1.3.6.1.4.1.4874.2.2.32.1.3.1.3
    type
    OBJECT-TYPE
    asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniperUni(4874) juniperUniMibs(2) juniMibs(2) juniRouterMIB(32) juniRouterObjects(1) juniRouterProtocolTable(3) juniRouterProtocolEntry(1) juniRouterProtocolRowStatus(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) juniperUni(4874) juniperUniMibs(2) juniMibs(2) juniRouterMIB(32) juniRouterObjects(1) juniRouterProtocolTable(3) juniRouterProtocolEntry(1) usdRouterProtocolRowStatus(3)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) unisphere(4874) usMibs(2) usDataMibs(2) usdRouterMIB(32) usdRouterObjects(1) usdRouterProtocolTable(3) usdRouterProtocolEntry(1) juniRouterProtocolRowStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) unisphere(4874) usMibs(2) usDataMibs(2) usdRouterMIB(32) usdRouterObjects(1) usdRouterProtocolTable(3) usdRouterProtocolEntry(1) usdRouterProtocolRowStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniperUni(4874) juniperUniMibs(2) juniMibs(2) juniRouterMIB(32) juniRouterObjects(1) juniRouterProtocolTable(3) juniRouterProtocolEntry(1) juniRouterProtocolRowStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) juniperUni(4874) juniperUniMibs(2) juniMibs(2) juniRouterMIB(32) juniRouterObjects(1) juniRouterProtocolTable(3) juniRouterProtocolEntry(1) usdRouterProtocolRowStatus(3)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) unisphere(4874) usMibs(2) usDataMibs(2) usdRouterMIB(32) usdRouterObjects(1) usdRouterProtocolTable(3) usdRouterProtocolEntry(1) juniRouterProtocolRowStatus(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) unisphere(4874) usMibs(2) usDataMibs(2) usdRouterMIB(32) usdRouterObjects(1) usdRouterProtocolTable(3) usdRouterProtocolEntry(1) usdRouterProtocolRowStatus(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/juniperUni/juniperUniMibs/juniMibs/juniRouterMIB/juniRouterObjects/juniRouterProtocolTable/juniRouterProtocolEntry/juniRouterProtocolRowStatus
  • /iso/identified-organization/dod/internet/private/enterprise/juniperUni/juniperUniMibs/juniMibs/juniRouterMIB/juniRouterObjects/juniRouterProtocolTable/juniRouterProtocolEntry/usdRouterProtocolRowStatus
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/unisphere/usMibs/usDataMibs/usdRouterMIB/usdRouterObjects/usdRouterProtocolTable/usdRouterProtocolEntry/juniRouterProtocolRowStatus
  • /iso/org/dod/internet/private/enterprise/unisphere/usMibs/usDataMibs/usdRouterMIB/usdRouterObjects/usdRouterProtocolTable/usdRouterProtocolEntry/usdRouterProtocolRowStatus
  • /iso/org/dod/internet/private/enterprises/juniperUni/juniperUniMibs/juniMibs/juniRouterMIB/juniRouterObjects/juniRouterProtocolTable/juniRouterProtocolEntry/juniRouterProtocolRowStatus
  • /iso/org/dod/internet/private/enterprises/juniperUni/juniperUniMibs/juniMibs/juniRouterMIB/juniRouterObjects/juniRouterProtocolTable/juniRouterProtocolEntry/usdRouterProtocolRowStatus
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/unisphere/usMibs/usDataMibs/usdRouterMIB/usdRouterObjects/usdRouterProtocolTable/usdRouterProtocolEntry/juniRouterProtocolRowStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/unisphere/usMibs/usDataMibs/usdRouterMIB/usdRouterObjects/usdRouterProtocolTable/usdRouterProtocolEntry/usdRouterProtocolRowStatus
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/4874/2/2/32/1/3/1/3

    Description by mibdepot

    Administrative control and status of a protocol on a router.

    The following values can be read from this object:
    active(1) - Indicates that the protocol on the designated router
    is created, configured, and running.
    notReady(3) - Indicates that the protocol requires additional
    configuration in a protocol specific MIB module.
    Examples include the BGP and OSPF protocols, which
    require additional configuration of protocol specific
    parameters such as: Autonomous System (AS) for BGP,
    and Process Id for OSPF.
    destroy(6) - The destroy(3) operation can fail if there are
    executing applications dependent on the protocol.
    If an attempt is made to destroy(6) an active(1)
    protocol that other applications are dependent on,
    the rowStatus will read destroy(6). Normally, when
    a row is destroyed, the agent will cleaup and remove
    the entry.

    The following values can be written to this object:
    active(1) - Activate protocol on the designated router.
    createAndGo(4) - Create protocol on designated router. The router
    indicated by usdRouterProtocolRouterIndex must
    already exist in the usdRouterTable. The value of
    the usdRouterProtocolProtocolIndex must be from the
    set of protocol values defined by the
    UsdRouterProtocolIndex type.
    destroy(6) - Destroy protocol on designated router. If the
    operation is successful, the agent will remove the
    entry. If the operation failed, the row will remain
    in the table with a rowStatus value of destroy(6).

    Conditions on destroy(6):
    1) The default router can not be deleted.
    2) The local router can not be deleted. A local router is defined
    as the router that sourced the SNMP request.

    Upon creation of a router in the usdRouterTable, some protocol entries
    will appear in this table by default, which indicates that these
    protocols are created by the action of creating a router. It is
    important to note, that this behavior may change over time by protocol
    type.

    Parsed from file usDataRouter.mi2.txt
    Company: None
    Module: Unisphere-Data-ROUTER-MIB

    Description by circitor

    Administrative control and status of a protocol on a router.

    The following values can be read from this object:
    active(1) - Indicates that the protocol on the designated router
    is created, configured, and running.
    notReady(3) - Indicates that the protocol requires additional
    configuration in a protocol specific MIB module.
    Examples include the BGP and OSPF protocols, which
    require additional configuration of protocol specific
    parameters such as: Autonomous System (AS) for BGP,
    and Process Id for OSPF.
    destroy(6) - The destroy(3) operation can fail if there are
    executing applications dependent on the protocol.
    If an attempt is made to destroy(6) an active(1)
    protocol that other applications are dependent on,
    the rowStatus will read destroy(6). Normally, when
    a row is destroyed, the agent will cleaup and remove
    the entry.

    The following values can be written to this object:
    active(1) - Activate protocol on the designated router.
    createAndGo(4) - Create protocol on designated router. The router
    indicated by juniRouterProtocolRouterIndex must
    already exist in the juniRouterTable. The value of
    the juniRouterProtocolProtocolIndex must be from the
    set of protocol values defined by the
    JuniRouterProtocolIndex type.
    destroy(6) - Destroy protocol on designated router. If the
    operation is successful, the agent will remove the
    entry. If the operation failed, the row will remain
    in the table with a rowStatus value of destroy(6).

    Conditions on destroy(6):
    1) The default router can not be deleted.
    2) The local router can not be deleted. A local router is defined
    as the router that sourced the SNMP request.

    Upon creation of a router in the juniRouterTable, some protocol entries
    will appear in this table by default, which indicates that these
    protocols are created by the action of creating a router. It is
    important to note, that this behavior may change over time by protocol
    type.

    Parsed from file Juniper-ROUTER-MIB.mib
    Module: Juniper-ROUTER-MIB

    Information by oid_info

    Vendor: Juniper Networks/Unisphere
    Module: Juniper-ROUTER-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    usdRouterProtocolRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION "Administrative control and status of a protocol on a router. The following values can be read from this object: active(1) - Indicates that the protocol on the designated router is created, configured, and running. notReady(3) - Indicates that the protocol requires additional configuration in a protocol specific MIB module. Examples include the BGP and OSPF protocols, which require additional configuration of protocol specific parameters such as: Autonomous System (AS) for BGP, and Process Id for OSPF. destroy(6) - The destroy(3) operation can fail if there are executing applications dependent on the protocol. If an attempt is made to destroy(6) an active(1) protocol that other applications are dependent on, the rowStatus will read destroy(6). Normally, when a row is destroyed, the agent will cleaup and remove the entry. The following values can be written to this object: active(1) - Activate protocol on the designated router. createAndGo(4) - Create protocol on designated router. The router indicated by usdRouterProtocolRouterIndex must already exist in the usdRouterTable. The value of the usdRouterProtocolProtocolIndex must be from the set of protocol values defined by the UsdRouterProtocolIndex type. destroy(6) - Destroy protocol on designated router. If the operation is successful, the agent will remove the entry. If the operation failed, the row will remain in the table with a rowStatus value of destroy(6). Conditions on destroy(6): 1) The default router can not be deleted. 2) The local router can not be deleted. A local router is defined as the router that sourced the SNMP request. Upon creation of a router in the usdRouterTable, some protocol entries will appear in this table by default, which indicates that these protocols are created by the action of creating a router. It is important to note, that this behavior may change over time by protocol type." ::= { usdRouterProtocolEntry 3 }

    Information by circitor

    juniRouterProtocolRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-write STATUS current DESCRIPTION "Administrative control and status of a protocol on a router. The following values can be read from this object: active(1) - Indicates that the protocol on the designated router is created, configured, and running. notReady(3) - Indicates that the protocol requires additional configuration in a protocol specific MIB module. Examples include the BGP and OSPF protocols, which require additional configuration of protocol specific parameters such as: Autonomous System (AS) for BGP, and Process Id for OSPF. destroy(6) - The destroy(3) operation can fail if there are executing applications dependent on the protocol. If an attempt is made to destroy(6) an active(1) protocol that other applications are dependent on, the rowStatus will read destroy(6). Normally, when a row is destroyed, the agent will cleaup and remove the entry. The following values can be written to this object: active(1) - Activate protocol on the designated router. createAndGo(4) - Create protocol on designated router. The router indicated by juniRouterProtocolRouterIndex must already exist in the juniRouterTable. The value of the juniRouterProtocolProtocolIndex must be from the set of protocol values defined by the JuniRouterProtocolIndex type. destroy(6) - Destroy protocol on designated router. If the operation is successful, the agent will remove the entry. If the operation failed, the row will remain in the table with a rowStatus value of destroy(6). Conditions on destroy(6): 1) The default router can not be deleted. 2) The local router can not be deleted. A local router is defined as the router that sourced the SNMP request. Upon creation of a router in the juniRouterTable, some protocol entries will appear in this table by default, which indicates that these protocols are created by the action of creating a router. It is important to note, that this behavior may change over time by protocol type." ::= { juniRouterProtocolEntry 3 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.4874)

    Scano John

    Brothers (2)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.4874.2.2.32.1.3.1.1 juniRouterProtocolRouterIndex, usdRouterProtocolRouterIndex 0 0 The routerIndex of this router. This object is the same as the
    usdRouterIndex object defined in the usdRouterTable.
    1.3.6.1.4.1.4874.2.2.32.1.3.1.2 juniRouterProtocolProtocolIndex, usdRouterProtocolProtocolIndex 0 0 Identities the router protocol.