CISCO-ATM-SWITCH-FR-IWF-MIB

CasfTrafficDescrRowIdentifies an index into the casfTrafficDescrTable. The value 0 signifies that no row has been identified. (1..2147483647) · Unsigned32

Uniquely identifies a row in this table.

Unsigned32 · bits/sec

The value of the Committed Information Rate (CIR) parameter.

Unsigned32 · bits

The value of the Committed Burst Size (Bc) parameter.

Unsigned32 · bits

The value of the Excess Burst Size (Be) parameter.

Unsigned32 · bits/sec

The value of the Peak Information Rate (PIR) parameter.

INTEGER1 = vbrNrt2 = abr3 = ubr4 = vbrRt · Integer32

Reference: ATM Forum Traffic Management Specification, Version 4.0, af-tm-0056.000, June 1996.

The service category, as defined for ATM.

AtmTrafficDescrParamIndexThe value of this object identifies a row in the atmTrafficDescrParamTable. The value 0 signifies that no row has been identified. (0..2147483647) · Integer32

The index of the equivalent entry in the atmTrafficDescrParamTable.

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

Used to create, delete and modify this row. None of the columnar values (other than this one) can be modified while the row is active.

DlciValueA numerical value identifying a Data Link Connection Identifier (DLCI) for a Frame Relay connection. The valid range of values depends on the format of the address field used, as described in ITU Recommendation Q.922. When a 2-octet address field is used, the value ranges from 0 to 1023.Reference: ITU Recommendation Q.922, ISDN Data Link Layer Specification For Frame Mode Bearer Services. (0..4194303) · Integer32

The value of the Data Link Connection Identifier (DLCI) which identifies this connection end-point.

CasfTrafficDescrRowIdentifies an index into the casfTrafficDescrTable. The value 0 signifies that no row has been identified. (1..2147483647) · Unsigned32

Identifies the entry in the casfTrafficDescrTable which applies to the receive direction at this connection end-point. For connections that negotiate traffic parameters through signaling (e.g. ABR connections), this object points to the desired traffic parameters, while the object casfVcEndptRxNegTrafficDescrRow points to the negotiated traffic parameters, for the receive direction.

CasfTrafficDescrRowIdentifies an index into the casfTrafficDescrTable. The value 0 signifies that no row has been identified. (1..2147483647) · Unsigned32

Identifies the entry in the casfTrafficDescrTable which applies to the transmit direction at this connection end-point. For connections that negotiate traffic parameters through signaling (e.g. ABR connections), this object points to the desired traffic parameters, while the object casfVcEndptTxNegTrafficDescrRow points to the negotiated traffic parameter, for the transmit direction.

CasfTrafficDescrRowIdentifies an index into the casfTrafficDescrTable. The value 0 signifies that no row has been identified. (1..2147483647) · Unsigned32

Identifies the entry in the casfTrafficDescrTable which contains negotiated traffic parameters applied to the receive direction of this connection end-point. This object is not instantiated if this is not the calling side of a soft VC, or if there is no traffic negotiation.

CasfTrafficDescrRowIdentifies an index into the casfTrafficDescrTable. The value 0 signifies that no row has been identified. (1..2147483647) · Unsigned32

Identifies the entry in the casfTrafficDescrTable which contains negotiated traffic parameters applied to the transmit direction of this connection endpoint. This object is not instantiated if this is not the calling side of a soft VC, or if there is no traffic negotiation.

ConnectionKind1 = pvc2 = svcIncoming3 = svcOutgoing4 = spvcInitiator5 = spvcTargetThe kind of connection, distinguished by the use of call control. · Integer32

The connection kind. The value can be set prior to the row becoming 'active'. To create a pvc connection endpoint, set this value to pvc(1). To create a soft VC connection endpoint, set this value to spvcInitiator(4), and specify the value of casfVcEndptSpvcRemoteAddr. The values svcIncoming(2), svcOutgoing(3), and spvcTarget(5) can not be written.

INTEGER1 = network2 = serviceTransparent3 = serviceTranslation4 = rfc1973 · Integer32

The type of the interworking function. The value can be set prior to the row becoming 'active'.

INTEGER1 = clpIfDe2 = clpIsZero3 = clpIsOne · Integer32

Specifies how to map from Discard Eligibility (DE) bit on the Frame Relay side to Congestion Loss Priority (CLP) bit on the ATM side. For network interworking, clpIfDe(1) corresponds to Mode 1 as defined in FRF.5, section 4.4.1. clpIsZero(2) and clpIsOne(3) correspond to Mode 2 as defined in FRF.5, section 4.4.1. For service interworking, clpIfDe(1) corresponds to Mode 1 as defined in FRF.8, section 4.2.1. clpIsZero(2) and clpIsOne(3) correspond to Mode 2 as defined in FRF.8, section 4.2.1.

INTEGER1 = deIfClpOrFrsscsDe2 = deIfFrsscsDe3 = deIfClp4 = deIsZero5 = deIsOne · Integer32

Specifies how to map from Congestion Loss Priority (CLP) bit on the ATM side to Discard Eligibility (DE) bit on the Frame Relay side. See the Frame Relay Forum specifications FRF.5 and FRF.8 for definitions of Mode 1 and Mode 2. For network interworking, the valid values are: deIfClpOrFrsscsDe(1) -- Mode 1 of FRF.5 section 4.4.2 deIfFrsscsDe(2) -- Mode 2 of FRF.5 section 4.4.2 For service interworking, the valid values are: deIfClp(3) -- Mode 1 of FRF.8 section 4.2.2 deIsZero(4) and deIsOne(5) -- Mode 2 of FRF.8 section 4.2.2

INTEGER1 = efciIfFecn2 = efciIsZero · Integer32

Specifies how to map from FECN field in the Frame Relay PDU to the EFCI field in ATM cells, in case of service interworking. This object does not apply to network interworking. efciIfFecn(1) and efciIsZero(2) correspond to Mode 1 and Mode 2 (as defined in FRF.8, section 4.3.1.1), respectively.

INTEGER1 = pass2 = tagDrop3 = tag4 = drop · Integer32

Specifies the action taken by Usage Parameter Control (UPC) at the ingress port.

AtmAddrAn ATM address. The semantics are implied by the length. The address types are: - no address (0 octets) - E.164 (8 octets) - NSAP (20 octets) In addition, when subaddresses are used the AtmAddr may represent the concatenation of address and subaddress. The associated address types are: - E.164, E.164 (16 octets) - E.164, NSAP (28 octets) - NSAP, NSAP (40 octets) Address lengths other than defined in this definition imply address types defined elsewhere. Note: The E.164 address is encoded in BCD format. SIZE (0..40) · OCTET STRING · hint 1x

The ATM address of the remote end of the soft VC. The value can be set prior to the row becoming 'active', and if the value of casfVcEndptConnKind is spvcInitiator(4). The agent will return an inconsistentValue error on sets if the value of casfVcEndptConnKind is other than spvcInitiator(4). If the value of casfVcEndptConnKind spvcTarget(5), this object is initialized by the agent. This object is instantiated only if the value of casfVcEndptConnKind is spvcInitiator(4) or spvcTarget(5).

INTEGER1 = other2 = frameRelay3 = atm · Integer32

The type of the remote end of the soft VC. This object is instantiated only if the value of casfVcEndptConnKind is spvcInitiator(4) or spvcTarget(5). The agent will return an inconsistentValue error on sets if the value of casfVcEndptConnKind is other than spvcInitiator(4) or spvcTarget(5).

DlciValueA numerical value identifying a Data Link Connection Identifier (DLCI) for a Frame Relay connection. The valid range of values depends on the format of the address field used, as described in ITU Recommendation Q.922. When a 2-octet address field is used, the value ranges from 0 to 1023.Reference: ITU Recommendation Q.922, ISDN Data Link Layer Specification For Frame Mode Bearer Services. (0..4194303) · Integer32

The DLCI value to be used at the remote end of the soft VC. The value can be set prior to the row becoming 'active', and if the value of casfVcEndptConnKind is spvcInitiator(4), and the value of casfVcEndptSpvcRemoteType is frameRelay(2). The object is instantiated only if the value of casfVcEndptSpvcRemoteType is frameRelay(2). The agent will return an inconsistentValue error on sets if the value of casfVcEndptSpvcRemoteType is other than frameRelay(2).

INTEGER (0..255) · Integer32

The VPI value to be used at the remote end of the soft VC. The value can be set prior to the row becoming 'active', and if the value of casfVcEndptConnKind is spvcInitiator(4), and the value of casfVcEndptSpvcRemoteType is atm(3). The object is instantiated only if the value of casfVcEndptSpvcRemoteType is atm(3). The agent will return an inconsistentValue error on sets if the value of casfVcEndptSpvcRemoteType is other than atm(3).

INTEGER (0..65535) · Integer32

The VCI value to be used at the remote end of the soft VC. The value can be set prior to the row becoming 'active', and if the value of casfVcEndptConnKind is spvcInitiator(4), and the value of casfVcEndptSpvcRemoteType is atm(3). The object is instantiated only if the value of casfVcEndptSpvcRemoteType is atm(3). The agent will return an inconsistentValue error on sets if the value of casfVcEndptSpvcRemoteType is other than atm(3).

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The time when this row was created.

INTEGER1 = deleted2 = active3 = inactive4 = none · Integer32

Reference: Q.933 Annex A. This object is a copy of frPVCEndptRcvdSigStatus from RFC1604.

The value of this object identifies the PVC status received via the local in-channel signaling procedures for this PVC end-point. This object is only pertinent for interfaces that perform the bidirectional procedures. For user-to-network network side procedures, the value of this object should be none(4).

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

Used to create, modify or delete this row.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Reference: ATM Forum specification AF-CS-0127.000 for standard encoding of Soft PVC IE.

Specifies whether or not to signal the standard (from the ATM-Forum PNNI Soft PVC Addendum) format of the Called Soft PVC IE, as opposed to the proprietary encoding we have used for the network-interworking case to a frame-relay destination.

INTEGER1 = none2 = lmi3 = ansiT1617D4 = ansiT1617B5 = ccittQ933A · Integer32

Identifies the Local In-Channel Signaling Protocol that is used for this frame relay port.

INTEGER1 = dte2 = dce3 = nni · Integer32

Identifies the Local In-Channel Signaling Procedure that is used for this frame relay port. A dte performs only user-side procedures. A dce performs only network-side procedures. An nni performs bidirectional procedures.

INTEGER (1..255) · Integer32

Reference: Draft American National Standard T1.617-1991, Section D.7 Counter N391.

Number of status enquiry intervals that pass before issuance of a full status enquiry mes- sage.

INTEGER (1..10) · Integer32

Reference: Draft American National Standard T1.617-1991, Section D.5.1 Counter N392.

The maximum number of unanswered Status Enquiries the device shall accept before declaring the interface down.

INTEGER (1..10) · Integer32

Reference: Draft American National Standard T1.617-1991, Section D.5.2 Counter N393.

The number of status polling intervals over which the error threshold is counted. For example, if within N393 number of events the device receives N392 number of errors, the interface is marked as down.

INTEGER (5..30) · Integer32 · seconds

Reference: Draft American National Standard T1.617-1991, Section D.7 Timer T391.

The number of seconds between successive status enquiry messages.

INTEGER (1..10) · Integer32

Reference: Draft American National Standard T1.617-1991, Section D.7 Timer N392.

The value of the network-side error threshold for this frame relay port.

INTEGER (0..10) · Integer32

Reference: Draft American National Standard T1.617-1991, Section D.7 Timer N393.

The value of the network-side monitored events count for this frame relay port. If, within N393 number of events, the network-side receives N392 number of errors, the interface is marked as down.

INTEGER (5..30) · Integer32 · seconds

Reference: Draft American National Standard T1.617-1991, Section D.7 Timer T392.

The value of the network-side polling verification timer for this frame relay port.

Counter32 · messages

Number of Status Enquiry messages received.

Counter32 · messages

Number of Status Enquiry messages sent.

Counter32 · messages

Number of Status messages received.

Counter32 · messages

Number of Status messages sent.

Counter32

Number of times when timeout occurred on waiting for Status message

Counter32

Number of times when timeout occurred on waiting for Status Enquiry message

AtmAddrAn ATM address. The semantics are implied by the length. The address types are: - no address (0 octets) - E.164 (8 octets) - NSAP (20 octets) In addition, when subaddresses are used the AtmAddr may represent the concatenation of address and subaddress. The associated address types are: - E.164, E.164 (16 octets) - E.164, NSAP (28 octets) - NSAP, NSAP (40 octets) Address lengths other than defined in this definition imply address types defined elsewhere. Note: The E.164 address is encoded in BCD format. SIZE (0..40) · OCTET STRING · hint 1x

The ATM Address that identifies this interface. This address can be used to setup soft VC's to this interface over an ATM network.

INTEGER1 = pass2 = tagDrop3 = tag4 = drop · Integer32

Specifies the default Usage Parameter Control (UPC) action to use at this interface for connections that do not explicitly specify a UPC action.

Integer32 (0..32768) · bits

Specifies the default Committed Burst Size (Bc) value to use at this interface for connections that do not explicitly specify the value of Bc.

INTEGER1 = deIfClpOrFrsscsDe2 = deIfFrsscsDe · Integer32

Reference: ATM Forum specification AF-CS-0127.000 for standard encoding of Soft PVC IE.

Specifies the default mapping from Congestion Loss Priority (CLP) bit on the ATM side to Discard Eligibility (DE) bit on the Frame Relay side. This is used when receiving a soft PVC Setup using the standard encoding of the called Soft PVC IE. Otherwise a proprietary encoding provides this information.

INTEGER1 = clpIfDe2 = clpIfIsZero3 = clpIfIsOne · Integer32

Reference: ATM Forum specification AF-CS-0127.000 for standard encoding of Soft PVC IE.

Specifies the default mapping from Discard Eligibility (DE) bit on the Frame Relay side to Congestion Loss Priority (CLP) bit on the ATM side.This is used when receiving a soft PVC Setup using the standard encoding of the called Soft PVC IE. Otherwise a proprietary encoding provides this information.

Counter32 · frames

Number of frames received.

Counter32 · octets

Number of octets received. This counter counts octets from the beginning of the frame relay header field to the end of user data.

Counter32 · frames

Number of frames received from the network with the FECN (Forward Explicit Congestion Notification) bit set.

Counter32 · frames

Number of frames received from the network with the BECN (Backward Explicit Network Congestion) bit set.

Counter32 · frames

Number of frames received with the Discard Eligibility (DE) bit set.

Counter32 · frames

Number of frames received that were discarded at ingress. Possible reasons are policing, congestion.

Counter32 · frames

Number of frames that were to be transmitted but were discarded. Possible reasons are policing, lack of buffers.

Counter32 · frames

Number of frames sent.

Counter32 · octets

Number of octets sent. This counter counts octets from the beginning of the frame relay header field to the end of user data.

Counter32 · frames

Number of frames that were sent with the FECN bit set.

Counter32 · frames

Number of frames sent with the BECN bit set.

Counter32 · frames

Number of frames sent with the DE bit set.

Counter32 · frames

Number of frames for which the switch set the FECN bit.

Counter32 · frames

Number of frames for which the switch set the BECN bit.

Counter32 · frames

Number of frames for which the switch set the DE bit.

Counter32

Frames received with unknown protocol. This event is counted only for connections with service interworking in translation mode. For other types of connections, this count will remain at zero.

Counter32

Outbound frames that were not transmitted because they contained an unknown protocol. This event is counted only for connections with service interworking in translation mode. For other types of connections, this count will remain at zero.

Counter32

The number of frames which could not be completely reassembled due to a reassembly timeout, and were thus discarded before being transmitted on this connection.

Counter32

The number of reassembled frames intended to be transmitted on this connection for which the AAL5 PDU trailer length fields did not match the actual PDU length, and were thus discarded.

Counter32

The number of reassembled frames intended to be transmitted on this connection for which the AAL5 PDU had CRC errors, and were thus discarded.

Counter32

The number of frames intended to be transmitted on this connection that were discarded due to any reason including those described in other objects in this table (e.g., frames that were discarded because insufficient buffer space was available for reassembling the frame).

DlciValueA numerical value identifying a Data Link Connection Identifier (DLCI) for a Frame Relay connection. The valid range of values depends on the format of the address field used, as described in ITU Recommendation Q.922. When a 2-octet address field is used, the value ranges from 0 to 1023.Reference: ITU Recommendation Q.922, ISDN Data Link Layer Specification For Frame Mode Bearer Services. (0..4194303) · Integer32

The DLCI value.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

The ifIndex of the internal ATM interface to which this DLCI is mapped.

INTEGER (0..255) · Integer32

The VPI value to which this DLCI is mapped.

INTEGER (0..65535) · Integer32

The VCI value to which this DLCI is mapped.

INTEGER (0..255) · Integer32

The VPI value of the Virtual Channel Link (VCL) on the ATM interface.

INTEGER (0..65535) · Integer32

The VCI value of the Virtual Channel Link (VCL) on the ATM interface.

InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d

The ifIndex of the frame relay interface that this VCL maps to.

DlciValueA numerical value identifying a Data Link Connection Identifier (DLCI) for a Frame Relay connection. The valid range of values depends on the format of the address field used, as described in ITU Recommendation Q.922. When a 2-octet address field is used, the value ranges from 0 to 1023.Reference: ITU Recommendation Q.922, ISDN Data Link Layer Specification For Frame Mode Bearer Services. (0..4194303) · Integer32

The DLCI on the frame relay interface that this VCL maps to.