The operation to be performed on the virtual connection.
To add a connection, first reserve an unallocated ctIndex
value by getting ctIndexNext. Next, set all desired and/or
non-defaulting read-write objects in the row, and then set
ctOperation to 'add'. Upon a successful add operation, the
connection will be held in a 'not valid' and 'pending add'
state for a short period of time, until the hardware has
been fully updated, at which point the connection will be
put in a 'valid' state. Upon an unsuccessful add operation,
the reason for the failure may be determined by getting the
ctFailureCode object, using the same index value as was used
in the unsuccessful add operation.
To delete a connection, set ctOperation to 'delete'. Upon a
successful delete operation, the connection will be held in
a 'valid' and 'pending delete' state for a short period of
time, until the hardware has been fully updated, at which
point the connection will be put in a 'not valid' state. An
attempt to delete an already invalid connection will always
be successful, although the connection will not pass through
a 'pending delete' state.
Although the parameters of an existing connection may not be
modified directly, a 'modify' operation may be simulated by a
'delete' operation followed by an 'add' operation. Note that
since the added connection is essentially new, it needs an
entirely new ctIndex value reserved for it, since the ctIndex
value previously used for the deleted connection may not be
freed in time for use by the new connection to be added. It
is thus strongly urged that a new connection be added using a
unique ctIndex value that has been safely dispensed by first
getting ctIndexNext.
Parsed from file CP300.mib.txt
Company: marconi
Module: AAC3-MIB
Vendor: ADC Kentrox
Module: AAC3-MIB (aac3-140.mib)
Type: TABULAR
Access: read-write
Syntax: INTEGER
Automatically extracted from www.mibdepot.com
ctOperation OBJECT-TYPE SYNTAX INTEGER { add(1), delete(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The operation to be performed on the virtual connection. To add a connection, first reserve an unallocated ctIndex value by getting ctIndexNext. Next, set all desired and/or non-defaulting read-write objects in the row, and then set ctOperation to 'add'. Upon a successful add operation, the connection will be held in a 'not valid' and 'pending add' state for a short period of time, until the hardware has been fully updated, at which point the connection will be put in a 'valid' state. Upon an unsuccessful add operation, the reason for the failure may be determined by getting the ctFailureCode object, using the same index value as was used in the unsuccessful add operation. To delete a connection, set ctOperation to 'delete'. Upon a successful delete operation, the connection will be held in a 'valid' and 'pending delete' state for a short period of time, until the hardware has been fully updated, at which point the connection will be put in a 'not valid' state. An attempt to delete an already invalid connection will always be successful, although the connection will not pass through a 'pending delete' state. Although the parameters of an existing connection may not be modified directly, a 'modify' operation may be simulated by a 'delete' operation followed by an 'add' operation. Note that since the added connection is essentially new, it needs an entirely new ctIndex value reserved for it, since the ctIndex value previously used for the deleted connection may not be freed in time for use by the new connection to be added. It is thus strongly urged that a new connection be added using a unique ctIndex value that has been safely dispensed by first getting ctIndexNext." ::= { ctEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.181.1.13.7.4.1.1 | ctIndex | 0 | 0 | The index value which uniquely identifies the virtual connection, for the purposes of setting or getting the connection's paramet… |
| 1.3.6.1.4.1.181.1.13.7.4.1.2 | ctConnStatus | 0 | 0 | The current status of the virtual connection, represented as a sum of the following bit values: 1 valid Connectio… |
| 1.3.6.1.4.1.181.1.13.7.4.1.4 | ctFailureCode | 0 | 0 | The specific reason for a failed 'add' operation. |
| 1.3.6.1.4.1.181.1.13.7.4.1.5 | ctAsidePortId | 0 | 0 | The port ID on the A-side of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.6 | ctAsideVPI | 0 | 0 | The VPI used on the A-side link of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.7 | ctAsideVCI | 0 | 0 | The VCI used on the A-side link of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.8 | ctBsidePortId | 0 | 0 | The port ID on the B-side of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.9 | ctBsideVPI | 0 | 0 | The VPI used on the B-side link of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.10 | ctBsideVCI | 0 | 0 | The VCI used on the B-side link of the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.11 | ctAsideToBsideScrIndex | 0 | 0 | The index into the rate table for the Sustained Cell Rate (SCR) traffic bandwidth on the virtual connection in the direction from… |
| 1.3.6.1.4.1.181.1.13.7.4.1.12 | ctBsideToAsideScrIndex | 0 | 0 | The index into the rate table for the Sustained Cell Rate (SCR) traffic bandwidth on the virtual connection in the direction from… |
| 1.3.6.1.4.1.181.1.13.7.4.1.13 | ctAsideToBsidePcrIndex | 0 | 0 | The index into the rate table for the Peak Cell Rate (PCR) traffic bandwidth on the virtual connection in the direction from the … |
| 1.3.6.1.4.1.181.1.13.7.4.1.14 | ctBsideToAsidePcrIndex | 0 | 0 | The index into the rate table for the Peak Cell Rate (PCR) traffic bandwidth on the virtual connection in the direction from the … |
| 1.3.6.1.4.1.181.1.13.7.4.1.15 | ctAsideToBsidePriority | 0 | 0 | The priority of the traffic on the virtual connection in the direction from the A-side towards the B-side. A lower value indicat… |
| 1.3.6.1.4.1.181.1.13.7.4.1.16 | ctBsideToAsidePriority | 0 | 0 | The priority of the traffic on the virtual connection in the direction from the B-side towards the A-side. A lower value indicat… |
| 1.3.6.1.4.1.181.1.13.7.4.1.17 | ctCastType | 0 | 0 | An indication of whether the virtual connection is a unicast connection or a multicast connection. A unicast connection may in tu… |
| 1.3.6.1.4.1.181.1.13.7.4.1.18 | ctConnType | 0 | 0 | An indication of whether the virtual connection is a virtual channel connection (VCC) or a virtual path connection (VPC). |
| 1.3.6.1.4.1.181.1.13.7.4.1.19 | ctTrafficType | 0 | 0 | The type of traffic supported on the virtual connection. |
| 1.3.6.1.4.1.181.1.13.7.4.1.20 | ctAalType | 0 | 0 | The type of ATM Adaptation Layer (AAL) used on the virtual connection. This corresponds only to the Segmentation and Reassembly … |
| 1.3.6.1.4.1.181.1.13.7.4.1.21 | ctSscsType | 0 | 0 | The type of AAL Service Specific Convergence Sublayer (SSCS) used on the virtual connection, if any. |
| 1.3.6.1.4.1.181.1.13.7.4.1.22 | ctEncapType | 0 | 0 | The type of network layer encapsulation used on the virtual connection. The value of this object must be the default value unkno… |
| 1.3.6.1.4.1.181.1.13.7.4.1.23 | ctRemoteIpAddr | 0 | 0 | The IP address, if any, of the device interface at the remote end of the virtual connection. The value of this object must be th… |
| 1.3.6.1.4.1.181.1.13.7.4.1.24 | ctAsideNext | 0 | 0 | The ctIndex value for the next virtual connection on the A-side of this port, sorted primarily by the VPI/VCI values on the A-sid… |
| 1.3.6.1.4.1.181.1.13.7.4.1.25 | ctAsidePrev | 0 | 0 | The ctIndex value for the previous virtual connection on the A-side of this port, sorted primarily by the VPI/VCI values on the A… |
| 1.3.6.1.4.1.181.1.13.7.4.1.26 | ctBsideNext | 0 | 0 | The ctIndex value for the next virtual connection on the B-side of this port, sorted by the VPI/VCI values on the B-side. In the… |
| 1.3.6.1.4.1.181.1.13.7.4.1.27 | ctBsidePrev | 0 | 0 | The ctIndex value for the previous virtual connection on the B-side of this port, sorted by the VPI/VCI values on the B-side. In… |