CISCO-WAN-ATM-CONN-MIB

Unsigned32 (0..4095)

The VPI value of a VP or VC connection. The cwaChanVpcFlag serves to distinguish if this is a VP/VC connection

Unsigned32 (0..65535)

The VCI value of VC connection. The cwaChanVpcFlag serves to distinguish if this is a VP/VC connection. For a VPC, the VCI is irrelevant and is set to a value of 0

CiscoAtmServiceCategory1 = cbr12 = vbr1RT3 = vbr2RT4 = vbr3RT5 = vbr1nRT6 = vbr2nRT7 = vbr3nRT8 = ubr19 = ubr210 = abr11 = cbr212 = cbr3The ATM forum service categories. For sake of backward compatibility with UNI3.1, two CBR service types cbr2 and cbr3 have been added.Reference: ATM Forum Traffic Management Specification Version 4.0 Section 4.5.4 · Integer32

This object identifies the service type to which this connection belongs. The service type specified is one among the ATM forum service types and implicitly determines the configuration for GCRA. This Object can be set only during row creation.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indentifies if the endpoint is a VP/VC endpoint. For a VPC, this object is set to true(1); For a VCC, this object is set to false(2). This Object can be set only during row creation.

Unsigned32

This number represents a RESOURCE at the switch that has been assigned for this connection (identified by ifIndex, cwaChanVpi and cwaChanVci). An example of this resource could be the LCN/GLCN used by the switch. Another example could be a record number assigned for this connection in a database of records. When a connection gets deleted, this resource gets released into a free pool. When a new endpoint is added (different ifIndex, cwaChanVpi & cwaChanVci), the switch may re-assign this resource. Thus all connections in a switch would have an unique cwaChanIdentifier. Since the number of resources in the switch is a much lesser subset as compared to all possible combinations of ifIndex, vpi and vci, this number serves as a quick reference index between the switch and the NMS. This is especially useful during the configuration upload of connections from the switch to the NMS.

Unsigned32

This counter tracks the number of configuration changes that happen on a specific endpoint (identified by ifIndex, cwaChanVpi, and cwaChanVci). The value of this object is derived from cwChanGlobalTransactionId. For every connection changes (add/delete/modify/up/down), the value of cwChanGlobalTransactionId is incremented and that value is used for this object. This counter is used by the NMS to determine if a connection configuration had been modified and requires an upload.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Limits imposed by software or hardware implementations could restrict the amount of statistical data that can be maintained in a physical entity (like a service module card). Hence there could be a need to restrict statistics collection to a smaller subset. This object serves the purpose of enabling/disabling statistics collection on a per connection basis. In implementations which do not have such limitations, this object can be set to true(1) for all connections. When set to true(1), statistics collection is enabled; When set to false(2), stats collection is disabled

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object serves to enable or disable continuity check(CC) on a connection endpoint. When continuity check is enabled on an endpoint, the endpoint anticipates OAM CC cells from its peer endpoint. OAM CC cells are sent when the peer endpoint does not have traffic cells to send. If the connection is idle and this endpoint has not received OAM CC cells for a period of 3.5 +/- 0.5 seconds, it declares continuity failure. This object serves to administratively control the CC feature. Typical implementations (of this feature) may choose to ignore this control or impose other conditions to actually enable CC cell flow. However, if this object is set to false(2), then this feature should be disabled

Unsigned32 (0..4095)

This object identifies the internal VPI assigned to a local endpoint, by the switch. The cwaChanLocalVpi, cwaChanLocalVci and the cwaChanLocalNSAPAddr, form a unique identifier for the connection endpoint in the networking domain

Unsigned32 (0..65535)

This object identifies the internal VCI assigned to a local endpoint, by the switch. The cwaChanLocalVpi, cwaChanLocalVci and the cwaChanLocalNSAPAddr, form a unique identifier for the connection endpoint in the networking domain

CiscoWanNsapAtmAddressATM address used by the networking entity. The only address type presently supported is NSAP (20 octets) SIZE (20) · OCTET STRING

This object identifies the internal NSAP assigned to a local endpoint, by the switch. The cwaChanLocalVpi, cwaChanLocalVci and the cwaChanLocalNSAPAddr, form a unique identifier for the connection endpoint in the networking domain

Unsigned32 (0..4095)

This object identifies the VPI of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi and the cwaChanRemoteNSAPAddr, identify the peer endpoint in the networking domain. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful. This Object can be set only during row creation.

Unsigned32 (0..65535)

This object identifies the VCI of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi and the cwaChanRemoteNSAPAddr, identify the peer endpoint in the networking domain. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful. This Object can be set only during row creation.

CiscoWanNsapAtmAddressATM address used by the networking entity. The only address type presently supported is NSAP (20 octets) SIZE (20) · OCTET STRING

This object identifies the NSAP of the peer endpoint. The cwaChanRemoteVpi, cwaChanRemoteVpi and the cwaChanRemoteNSAPAddr, identify the peer endpoint in the networking domain. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful. This Object can be set only during row creation.

Unsigned32 (1..255)

This object serves to associate an endpoint with a specific controller. Usually resource partitioning makes the association between a controller and a range of vpi-vci. There could be switches where hard partitioning of vpi-vci may not be implemented, in which case this object serves to tie a specific vpi-vci to a controller. This object can not be modified after the row is created.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object, if set to true(1) identifies that this endpoint as the `master' endpoint of the connection. When set to false(2) this identifies the `slave' endpoint of the connection. The slave endpoint is the called party, while the master endpoint is the calling party in the SPVC call setup. The networking entity initiates routing of a SPVC connection only after a master endpoint is added. Mastership of a SPVC cannot be changed, once provisioned, implying that this object can be set only during row creation.

Unsigned32

This object is used by the networking entity to select a route based on administrative weight of possible routes. Administrative weights of links and nodes contained in a path are aggregated and compared against this object. The networking entity prefers a path whose aggregate administrative weight is lesser than the value of this object. Setting this parameter to 0 indicates to the switch that only the best available route should be chosen. If this object is set to a value of 0xFFFFFFFF(4294967295), then switch ignore this metric in making routing decisions. This parameter is not allowed to be set on a slave endpoint. (i.e. if 'cwaChanRoutingMastership' is set to 'false').

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This is used by the administrator to trigger the re-routing of the connection. * Rerouting takes effect, when this object is set to true(1). When set to false(2), no action is taken. * A get on this object always returns false(2). * When this object is set, no other object other than the RowStatus should be set in the MIB. * Reroute can be triggered only from the master endpoint. Any attempt to trigger reroute from the slave endpoint would result in a failure of the SET operation.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

When set to true(1), enables the frame discard feature for the connection. This is applicable only to the master endpoint (cwaChanRoutingMastership is true) and only for VCC connections.

CiscoWanOperStatus1 = operOk2 = operFail3 = adminDownDefines operational status of an endpoint · Integer32

Reflects operational status of an endpoint. * This object is set to operFail(2), if the connection is not routed or if the endpoint receives AIS/RDI or if there is a CC failure. * If the connection is administratively down, this object would be set to adminDown(3). * For a normal case, this is set to operOk(1)

Unsigned32 · cells per second

Peak cell rate (PCR) for the direction local -> remote

Unsigned32 · cells per second

Minimum cell rate (MCR) for the direction local -> remote

Unsigned32 · cells per second

Sustainable cell rate (SCR) for the direction local -> remote

Unsigned32 (0..16777215) · microseconds

Maximum tolerable cell delay variation in the direction local -> remote. Setting this parameter to 0xFFFFFF(16777215) indicates to the switch that this parameter does not have significance in SPVC call setup. This parameter is not allowed to be set on a slave endpoint. (i.e. if 'cwaChanRoutingMastership' is set to 'false').

Unsigned32 (0..65535) · milliseconds

Maximum tolerable network transfer delay in the direction local -> remote. Setting this parameter to 0xFFFF(65535) indicates to the switch that this parameter does not have significance in SPVC call setup. This parameter is not allowed to be set on a slave endpoint. (i.e. if 'cwaChanRoutingMastership' is set to 'false').

Unsigned32 (0..5000000) · cells

Reference: ATM Forum Traffice Management Specification Version 4.0 Annex C

Maximum Burst Size (MBS) used in the direction local -> remote

Unsigned32 · microseconds

Reference: ATM Forum Traffice Management Specification Version 4.0 Annex C

Cell delay variation tolerance(CDVT) used in the direction local -> remote. Setting this parameter to 0xFFFFFFFF(4294967295) indicates to the switch that it may use a default value of CDVT

Unsigned32 (1..100)

This factor provides a per connection control for overbooking bandwidth. This is used in conjunction with the VSI interface policy while performing CAC. This is applied for the direction local -> remote

Unsigned32 · cells per second

Peak cell rate (PCR) for the direction remote -> local. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Unsigned32 · cells per second

Minimum cell rate for the direction remote -> local

Unsigned32 · cells per second

Sustainable cell rate for the direction remote -> local

Unsigned32 (0..16777215) · microseconds

Maximum tolerable cell delay variation for the direction remote -> local. Setting this parameter to 0xFFFFFF(16777215) indicates to the switch that this parameter does not have significance in SPVC call setup. This parameter is not allowed to be set on a slave endpoint. (i.e. if 'cwaChanRoutingMastership' is set to 'false').

Unsigned32 (0..65535) · milliseconds

Maximum tolerable network transfer delay in the direction direction remote -> local. Setting this parameter to 0xFFFF(65535) indicates to the switch that this parameter does not have significance in SPVC call setup. This parameter is not allowed to be set on a slave endpoint. (i.e. if 'cwaChanRoutingMastership' is set to 'false'). If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Unsigned32 (0..5000000) · cells

Reference: ATM Forum Traffice Management Specification Version 4.0 Annex C.

Maximum Burst Size (MBS) used in the direction remote -> local. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Unsigned32 · cells

Reference: ATM Forum Traffice Management Specification Version 4.0 Annex C

Cell delay variation tolerance(CDVT) used in the direction remote -> local. Setting this parameter to 0xFFFFFFFF(4294967295) indicates to the switch that it may use a default value of CDVT. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Unsigned32 (1..100)

This factor provides a per connection control for overbooking bandwidth. This is used in conjunction with the VSI interface policy while performing CAC. This is applied for the direction remote -> local. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Unsigned32 · cells/sec

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Initial cell rate: Rate at which a source should send initially after an idle period. The value must not be larger than the PCR

Unsigned32 (1..1023) · 10 milliseconds

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

ACR Decrease Time Factor. This is the time permitted between sending RM-cells (Resource Mangement Cells) before the rate is decreased to ICR (Initial Cell Rate).

AbrRateFactors1 = oneOver327682 = oneOver163843 = oneOver81924 = oneOver40965 = oneOver20486 = oneOver10247 = oneOver5128 = oneOver2569 = oneOver12810 = oneOver6411 = oneOver3212 = oneOver1613 = oneOver814 = oneOver415 = oneOver216 = oneDefines possible rate factors to be used in increasing/decreasing ABR cell rate. · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Rate Decrease Factor: Controls the rate decrease which occurs when backward RM-cells with CI=1 are received. Larger values lead to faster rate decrease. This factor is applied at both the local and remote endpoints, thus making the loop control symmetrical. Backward RM cells at the local endpoint correspond to RM cells received in the remote->local direction. Backward RM cells at the remote endpoint correspond to RM cells received in the local->remote direction.

AbrRateFactors1 = oneOver327682 = oneOver163843 = oneOver81924 = oneOver40965 = oneOver20486 = oneOver10247 = oneOver5128 = oneOver2569 = oneOver12810 = oneOver6411 = oneOver3212 = oneOver1613 = oneOver814 = oneOver415 = oneOver216 = oneDefines possible rate factors to be used in increasing/decreasing ABR cell rate. · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Rate Increase Factor: Controls the rate increase which occurs when a backward RM-cell is received with CI=0 and NI=0. Larger values lead to faster rate increase This factor is applied at both the local and remote endpoints, thus making the loop control symmetrical. Backward RM cells at the local endpoint correspond to RM cells received in the remote->local direction. Backward RM cells at the remote endpoint correspond to RM cells received in the local->remote direction.

INTEGER1 = nrm22 = nrm43 = nrm84 = nrm165 = nrm326 = nrm647 = nrm1288 = nrm256 · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Maximum number of cells a source may send for each forward RM-cell

INTEGER1 = trm0point781252 = trm1point56253 = trm3point1254 = trm6point255 = trm12point56 = trm257 = trm508 = trm100 · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Upper bound on the time between forward RM-cells for an active source (in milliseconds)

INTEGER1 = cdf02 = cdfOneOver643 = cdfOneOver324 = cdfOneOver165 = cdfOneOver86 = cdfOneOver47 = cdfOneOver28 = cdfOne · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Cutoff Decrease Factor: Controls the rate decrease associated with lost or delayed backward RM cells. Larger values result in faster rate decrease

Unsigned32 (0..16700000) · microseconds

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Fixed round trip time: Sum of the fixed propagation delays from the source to a destination network.

Unsigned32 (0..16777215)

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Transient Buffer Exposure. This is a negotiated number of cells that the network would like to limit the source to sending during startup periods, before the first RM-cell returns

CiscoWanERSConfg1 = none2 = enableIngress3 = enableEgress4 = enableBothDefines possible configuration for Explicit Rate Stamping (ERS): None : Disable the ERS on connection enableIngress : Enable ERS in the Ingress direction ONLY enableEgress : Enable ERS in the Engress direction ONLY enableBoth : Enable ERS in both direction · Integer32

Configuration of an endpoint for Explicit Rate Stamping. Refer the Textual convention for possible values

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

Abr connections require close loop control to limit the transmission rate, depending on the network bandwidth. Now this close loop can be end to end or between intermediate network segments. When terminating an Abr VPL, the endpoint needs to act like a Virtual Destination to the incoming traffic and generate backward RM cells. While doing this it also needs to act as a virtual source and send forward RM cells to the real destination. This is a feature that can be enabled/disabled under the control of this object. When set to true(1), this feature is enabled; and is disabled when set to false(2)

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object is used to create, modify or delete an entry in the ciscoWanAtmChanTable. * A row may be created using the 'CreateAndGo' option. When the row is successfully created, the RowStatus would be set to 'active' by the agent. Following mandatory objects need to be specified for the successful creation of the row(for both master and slave endpoints): cwaChanServiceCategory cwaChanVpcFlag cwaChanRoutingMastership Following mandatory objects are needed for creation of master endpoint: cwaChanRemoteVpi cwaChanRemoteVci cwaChanRemoteNSAPAddr * A row may be deleted by setting the RowStatus to 'destroy'. * When there is a need to administratively down the connection, the RowStatus could be set to 'notInService'. When the switch completes the 'down' operation, the value of this object would be 'notInService'. * The connection can be made active again, by setting this object to 'active'. * RowStatus modification from 'notInService' to 'active' or vice-versa will impact only the administrative status of the connection. * Administrative status control is limited to the master endpoint only. The switch would reject any request for administrative state change on the slave endpoint. * Other options such as `CreateAndWait' will not be used.

CiscoWanVSVDConfg1 = vsvdOff2 = vsvdOn3 = switchDefaultDefines possible VSVD configuration applicable to an endpoint: vsvdOff : Disable VSVD vsvdOn : Enable VSVD switchDefault : Use default settings on switch. · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

This object is used for enabling/disabling VSVD internal to a segment i.e the closed loop control is in effect between the two provisioned endpoints of the SPVC.

CiscoWanVSVDConfg1 = vsvdOff2 = vsvdOn3 = switchDefaultDefines possible VSVD configuration applicable to an endpoint: vsvdOff : Disable VSVD vsvdOn : Enable VSVD switchDefault : Use default settings on switch. · Integer32

Reference: ATM Forum Traffic Management Specification Version 4.0 Section 5.10.2

This object is used for enabling/disabling VSVD external to the segment which hosts the two endpoints of the SPVC i.e the closed loop control will be in effect outside the segment either towards a CPE or towards another segment.

CiscoWanAisIW1 = e2eAisCapable2 = segAisCapableDefines an SPVC endpoint's AIS capability: e2eAisCapable : Endpoint capable of detecting/generating e2e AIS. segAisCapable : Endpoint capable of detecting/generating seg AIS. · Integer32

This object is used for achieving OAM inter-operability between switches that cannot generate/detect segment AIS cells. This attribute enables the newer generation of switches to understand the OAM capability of the peer endpoint and accordingly generate/detect seg/e2e AIS as required. The value of this attribute is decided during provisioning time by network management.

Unsigned32 (1..15)

Encoded value representing the maximum tolerable cell loss ratio in the direction local -> remote. The actual CLR value is derived as the negative logarithm of this value.

Unsigned32 (1..15)

Encoded value representing the maximum tolerable cell loss ratio in the direction remote -> local. The actual CLR value is derived as the negative logarithm of this value. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

INTEGER1 = oamSegEp2 = nonOamSegEp · Integer32

This object controls the setting / resetting of the OAM segment endpoint. When set to OamSegEp (1), the SPVC endpoint would terminate all segment OAM FM cells and loopback all OAM segment loopback cells. When set to NonOamSegEp (2), the SPVC endpoint would be configured as a non-endpoint for OAM cells. This means that all OAM FM cells and loopback cells would pass transparently through this endpoint. If this object is not specified during a SET operation, the switch would apply a default configuration maintained for the port.

INTEGER1 = persistentSlave2 = nonPersistentSlave · Integer32

This object indicates whether a master endpoint has a persistent slave or not. A connection with a master and a non-persistent slave is considered a single-ended SPVC. This object is only meaningful when 'cwaChanRoutingMastership' contains the value of 'true(1)'. And this variable must be used with 'cwaChanRoutingMastership' to decide if a connection is single-ended or not. If the object 'cwaChanP2MP' is set to 'true', this object should not be 'set' and the value of this object, if any, is not meaningful.

Integer32 (1..15)

This object is the routing priority of the connection. When adding the connection, a default routing priority of 8 is used if this is not specified. This parameter is not allowed to be set at the slave endpoint(i.e. if 'cwaChanRoutingMastership' is set to 'false(2)'). Any attempt to change the priority at the slave endpoint would result in a failure of the SET operation. A connection tagged with a routing priority of 1 is routed (and derouted) ahead of connections tagged with other priorities.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This is used by the administrator to configure this master endpoint to be the root of a point-to-multipoint connection. When this variable is set to 'true', this master endpoint is the root of a point-to-multipoint connection. The objects 'cwaChanRemoteVpi', 'cwaChanRemoteVci', 'cwaChanRemoteNSAPAddr', 'cwaChanRemotePCR', 'cwaChanRemoteMCR' 'cwaChanRemoteSCR', 'cwaChanRemoteCDV', 'cwaChanRemoteCTD', 'cwaChanRemoteMBS', 'cwaChanRemoteCDVT', 'cwaChanRemotePercentUtil', 'cwaChanRemoteCLR' and 'cwaChanSlaveType' should not be set and the values of these objects are not meaningful. When this variable is set to 'false', this master endpoint is not a root of a point-to-multipoint connection. If the object 'cwaChanPrefRouteId' is non-zero, this object could not be set to true.

Integer32 (0..65535)

This object serves to to associate a preferred route with a connection. The value '0' means no preferred route is associated with this connection. Usage: - If the value of this set to 0, the object cwaChanDirectRoute is automatically set to FALSE by the switch. - The preferred route is defined in cwaPrefRouteConfTable object. If the object 'cwaChanP2MP' is true, this object could not be set to a non-zero value.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object serves to associate a prefer route as directed route (correspond to the prefer route object cwaChanPrefRouteId). A directed route specifies that the associated preferred route is the only permission route for the connection to take. Should the associated preferred route be unavailable, the connection is failed. The object is not applicable if there is no associated preferred route with the connection.

CiscoWanAlarmState1 = ingAisRdi2 = egrAisRdi4 = conditioned8 = interfaceFail16 = ccFail32 = mismatch64 = ingAbitFailDefines possible alarms at an endpoint: ingAisRdi : Endpoint receiving AIS or RDI cells in ingress direction egrAisRdi : Endpoint receiving AIS or RDI cells in egress direction conditioned : Networking entity has forced the endpoint out of service. This could be attributed to either routing failure or to a maintenance operation initiated by the networking entity. interfaceFail : The interface to which this connection belongs has failed. ccFail : The OAM continuity check between the connection and its peer endpoint has detected a failure. mismatch : connection exists in SM database, but not in the network controller database ingAbitFail : Feeder connection detects A-bit failure in the ingress direction. Each of the alarm conditions is represented as a bit of an integer. Hence a value of zero indicates that there are no alarms. · Integer32

Defines alarms associated with an endpoint. Refer description in the textual convention.

CiscoWanXmtState1 = normal2 = sendingAIS3 = sendingRDIDefines possible transmit states of an endpoint: normal : Endpoint transmitting normal traffic. sendingAIS : Endpoint inhibits regular traffic, sends AIS on egress sendingRDI : Endpoint inhibits regular traffic, sends AIS on egress · Integer32

This is the state of the transmit portion of the endpoint in the egress direction

CiscoWanRcvState1 = normal2 = receivingRDI3 = receivingAIS4 = ccFailureDefines possible receive states of an endpoint normal : Endpoint receiving normal traffic. receivingAIS : Endpoint receiving AIS, in either ingress/egress receivingRDI : Endpoint receiving RDI, in either ingress/egress ccFailure : Endpoint does not receive OAM CC cells · Integer32

This is the state of the receive portion of the endpoint in the egress direction

CiscoWanXmtState1 = normal2 = sendingAIS3 = sendingRDIDefines possible transmit states of an endpoint: normal : Endpoint transmitting normal traffic. sendingAIS : Endpoint inhibits regular traffic, sends AIS on egress sendingRDI : Endpoint inhibits regular traffic, sends AIS on egress · Integer32

This is the state of the transmit portion of the endpoint in the ingress direction

CiscoWanRcvState1 = normal2 = receivingRDI3 = receivingAIS4 = ccFailureDefines possible receive states of an endpoint normal : Endpoint receiving normal traffic. receivingAIS : Endpoint receiving AIS, in either ingress/egress receivingRDI : Endpoint receiving RDI, in either ingress/egress ccFailure : Endpoint does not receive OAM CC cells · Integer32

This is the state of the receive portion of the endpoint in the ingress direction

CiscoWanLpbkTypes1 = noLpbk2 = destructive3 = nonDestructiveDefines possible loopback configurations for a connection: noLoopback : no loopback or clear configured loopback destructive : loopback all cells, causing data disruption. nonDestructive: loopback performed using OAM loopback cells. Does not disrupt regular traffic. · Integer32

This object configures an endpoint in loopback: This is a mandatory object. * To configure a destructive loopback, this object needs to be set to destructive (2). The direction in which this destructive loopback needs to be effected, should be specified using the cwaChanTestDir object. To de-configure destructive loopback, this object needs to be set to noLpbk(1). * To configure a non-destructive loopback, this object needs to be set to nonDestructive(3). The direction in which this non-destructive loopback needs to be effected, should be specified using the cwaChanTestDir object. Non-destructive loopback gets de-configured automatically at the switch after a certain timeout. However, if there is a need to abort a non-destructive loopback, a set operation on this object should be performed with a value noLpbk (1). * Attempting to set a channel in loopback, when one is already in progress results in a failure of the set operation (with appropriate error code)

CiscoWanLpbkDir1 = external2 = internal3 = forward4 = reverseDirection in which looped should be effected: external : loop port traffic back to port. Applicable only for destructive mode. internal : loop switch's egress traffic back to switch. Applicable only for destructive mode. forward : inject OAM loopback cells towards the switching fabric (ingress). Applicable only for non-destructive mode. reverse : inject OAM loopback cells towards the port (egress). Applicable only for non- destructive mode. · Integer32

Specifies the direction in which loopback should be effected: This is a mandatory object. * For destructive loopback, this takes values external (1) and internal (2). * For non-destructive loopback, this takes values forward (3) and reverse (4). * When cwaChanTestType is noLpbk (1), this object is ignored.

Unsigned32 (1..255)

Specifies number of loopback cells to inject. This applies to the non-destructive mode of loopback tests only. Get operation on this object returns the successful number of loopback iterations performed on the endpoint.

CiscoWanTestStatus1 = noStatus2 = lpbkInProgress3 = lpbkSuccess4 = lpbkAbort5 = lpbkTimeOut6 = lpbkInEffectDefines possible loopback test status at an endpoint. · Integer32

This object reflects the status of the last requested test: * If a loopback had never been effected on an endpoint, this object reads noStatus (1). * If a destructive mode of loopback is configured on an endpoint, this object always reads lpbkInEffect(6). * If a non-destructive mode of loopback is in progress, this reads lpbkInProgress(2). * If a non-destructive mode of loopback has completed successfully, this reads lpbkSuccess(3). * If a non-destructive mode of loopback has aborted, either due to user request or switch's limitation, this reads lpbkAbort (4). * If a non-destructive mode of loopback has failed, this reads lpbkTimeOut(5).

Unsigned32 (1..100000000) · microseconds

This object is applicable only for non-destructive mode of loopback. It returns the round trip delay measured during the last non-destructive loopback test

Unsigned32 (1..429496729)

This object's value generally corresponds to the Slot number where the module resides. However, System wide uniqueness is the only true requirement.

Unsigned32

Reference: frChanCnfChangeCount in CISCO-WAN-FR-CONN-MIB.my

This reflects the transaction Identifier of the last successful connection configuration on the slot (represented by cwSlotIndex). The value of this object is incremented every time a connection(ATM/Frame Relay) is successfully added, deleted, modified or administratively up/down. The transaction identifier of the each provisioned ATM connection endpoint is represented by cwaChanUploadCounter in the cwaChanCnfgTable. The transcation identifer of the each provisioned Frame Relay connection endpoint is represented by frChanCnfChangeCount in frChanCnfGrpTable.