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
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.
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
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
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.
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 }
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 }
Automatically extracted from Cisco "SNMP v2 MIBs".
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 }
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 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
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 … |