Reference record for OID 1.3.6.1.4.1.9.9.95.1.3.4.1.7



parent
1.3.6.1.4.1.9.9.95.1.3.4.1 (alpsCktAscuEntry)
node code
7
node name
alpsCktAscuStatus
dot oid
1.3.6.1.4.1.9.9.95.1.3.4.1.7
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoAlpsMIB(95) ciscoAlpsMIBObjects(1) alpsCktObjects(3) alpsCktAscuTable(4) alpsCktAscuEntry(1) alpsCktAscuStatus(7)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoAlpsMIB/ciscoAlpsMIBObjects/alpsCktObjects/alpsCktAscuTable/alpsCktAscuEntry/alpsCktAscuStatus
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/95/1/3/4/1/7

    Description by circitor

    Reports the ASCU status - ASCUs configured on the circuit
    can be rejected at the host and would then be marked REJECT. Also,
    ASCUs configured after the circuit has been established are not added
    dynamically to the circuit but are marked NEW and get added when the
    circuit gets established the next time. ASCUs waiting for an accept or
    reject response from the host are marked as PENDING. ASCUs that were
    accepted by the host are marked OK.

    Parsed from file CISCO-ALPS-MIB.mib
    Module: CISCO-ALPS-MIB

    Description by cisco_v1

    Reports the ASCU status - ASCUs configured on the circuit
    can be rejected at the host and would then be marked REJECT. Also,
    ASCUs configured after the circuit has been established are not added
    dynamically to the circuit but are marked NEW and get added when the
    circuit gets established the next time. ASCUs waiting for an accept or
    reject response from the host are marked as PENDING. ASCUs that were
    accepted by the host are marked OK.

    Description by oid_info

    alpsCktAscuStatus OBJECT-TYPE
    SYNTAX INTEGER {
    unknown(1),
    ok(2),
    reject(3),
    new(4),
    pending(5)
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "Reports the ASCU status - ASCUs configured on the circuit
    can be rejected at the host and would then be marked REJECT. Also,
    ASCUs configured after the circuit has been established are not added
    dynamically to the circuit but are marked NEW and get added when the
    circuit gets established the next time. ASCUs waiting for an accept or
    reject response from the host are marked as PENDING. ASCUs that were
    accepted by the host are marked OK."

    View at oid-info.com

    Description by mibdepot

    Reports the ASCU status - ASCUs configured on the circuit
    can be rejected at the host and would then be marked REJECT. Also,
    ASCUs configured after the circuit has been established are not added
    dynamically to the circuit but are marked NEW and get added when the
    circuit gets established the next time. ASCUs waiting for an accept or
    reject response from the host are marked as PENDING. ASCUs that were
    accepted by the host are marked OK.

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

    Description by cisco

    Reports the ASCU status - ASCUs configured on the circuit
    can be rejected at the host and would then be marked REJECT. Also,
    ASCUs configured after the circuit has been established are not added
    dynamically to the circuit but are marked NEW and get added when the
    circuit gets established the next time. ASCUs waiting for an accept or
    reject response from the host are marked as PENDING. ASCUs that were
    accepted by the host are marked OK.

    Information by circitor

    alpsCktAscuStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), reject(3), new(4), pending(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "Reports the ASCU status - ASCUs configured on the circuit can be rejected at the host and would then be marked REJECT. Also, ASCUs configured after the circuit has been established are not added dynamically to the circuit but are marked NEW and get added when the circuit gets established the next time. ASCUs waiting for an accept or reject response from the host are marked as PENDING. ASCUs that were accepted by the host are marked OK." ::= { alpsCktAscuEntry 7 }

    Information by cisco_v1

    alpsCktAscuStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), reject(3), new(4), pending(5) } ACCESS read-only STATUS mandatory DESCRIPTION "Reports the ASCU status - ASCUs configured on the circuit can be rejected at the host and would then be marked REJECT. Also, ASCUs configured after the circuit has been established are not added dynamically to the circuit but are marked NEW and get added when the circuit gets established the next time. ASCUs waiting for an accept or reject response from the host are marked as PENDING. ASCUs that were accepted by the host are marked OK." ::= { alpsCktAscuEntry 7 }

    Information by oid_info

    Automatically extracted from Cisco "SNMP v2 MIBs".

    Information by mibdepot

    alpsCktAscuStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), reject(3), new(4), pending(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "Reports the ASCU status - ASCUs configured on the circuit can be rejected at the host and would then be marked REJECT. Also, ASCUs configured after the circuit has been established are not added dynamically to the circuit but are marked NEW and get added when the circuit gets established the next time. ASCUs waiting for an accept or reject response from the host are marked as PENDING. ASCUs that were accepted by the host are marked OK." ::= { alpsCktAscuEntry 7 }

    Information by cisco

    alpsCktAscuStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), ok(2), reject(3), new(4), pending(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "Reports the ASCU status - ASCUs configured on the circuit can be rejected at the host and would then be marked REJECT. Also, ASCUs configured after the circuit has been established are not added dynamically to the circuit but are marked NEW and get added when the circuit gets established the next time. ASCUs waiting for an accept or reject response from the host are marked as PENDING. ASCUs that were accepted by the host are marked OK." ::= { alpsCktAscuEntry 7 }

    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 (6)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.95.1.3.4.1.1 alpsCktAscuCktName 0 0 The name of the ALPS circuit which this ASCU is on. The
    circuit may be always up (for permanent circuits) or get set up
    (dynamic …
    1.3.6.1.4.1.9.9.95.1.3.4.1.2 alpsCktAscuCktDlcType 0 0 Specifies what type of circuit this is. The X.25 circuit is set up
    with the same name as the ALC circuit so we need this
    variable…
    1.3.6.1.4.1.9.9.95.1.3.4.1.3 alpsCktAscuA1 0 0 A1 value. This is used along with the alpsCktAscuA2 value to
    identify the ASCU within the circuit.
    1.3.6.1.4.1.9.9.95.1.3.4.1.4 alpsCktAscuA2 0 0 A2 value. This is used along with the alpsCktAscuA1 value to
    identify the ASCU within the circuit.
    1.3.6.1.4.1.9.9.95.1.3.4.1.5 alpsCktAscuIfIndex 0 0 Reports the interface the ASCU is on. This field, along with
    alpsCktAscuId is provided so that it is possible to correlate this
    i…
    1.3.6.1.4.1.9.9.95.1.3.4.1.6 alpsCktAscuId 0 0 Reports the ASCU Identifier which uniquely
    identifies an ASCU on a given interface. This value is
    the Interface Address (IA) for …