The MIB for voice and Nx64 over ATM Trunking applications.
The following lists the abbreviations used in this MIB:
AAL ATM Adaption Layer
AIS Alarm Indication Signal
CID Channel Identifier
DSP Digital Signal Processing
DTMF Dual Tone Multi Frequency
FCS Frame Check Sequence
TDM Time Division Multiplexing
PVC Permanent Virtual Circuit
RAI Remote Alarm Indication
RDI Remote Defect Indication
SID Silence Insertion Descriptor
SVC Switched Virtual Circuit
VAD Voice Activity Detection
VBD Voice Band Data
VC Virtual Circuit
This table is used to establish the mapping of one or more DS0 channels from a single DS1 interface to an AAL2 connection identified by a Channel IDentification number(CID).
This table is created and used for ATM AAL2 trunking applications including both voice and data.
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
A unique value, greater than zero, for each interface. 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.
catmtCidVpi
1.3.6.1.4.1.9.9.351.1.1.1.1.1
Unsigned32 (0..4095)
This object is the VPI value of an ATM PVC connection.
catmtCidVci
1.3.6.1.4.1.9.9.351.1.1.1.1.2
Unsigned32 (0..65535)
This object is the VCI value of an ATM PVC connection.
catmtCid
1.3.6.1.4.1.9.9.351.1.1.1.1.3
Integer32 (8..255)
This object is the CID of an ATM AAL2 connection, it is unique within a PVC or SVC connection.
The CID number at both sides of an AAL2 connection must be the same.
Value of 0 is not used, and values of 1 to 7 are reserved for layer management by ITU-T I.366.2 standard. Reference: ITU-T recommendation I.366.2.
catmtCidDs1
1.3.6.1.4.1.9.9.351.1.1.1.1.4
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 value of this object equals to the 'ifIndex' of the DS1 interface.
This object is mandatory when adding a CID entry. Once a CID entry is added, this object can not be modified.
catmtCidDs0GroupIndex
1.3.6.1.4.1.9.9.351.1.1.1.1.5
Integer32 (0..30)
An arbitrary index that uniquely identifies a DS0 group which contains one or more DS0(s) within a DS1 interface specified by 'catmtCidDs1'.
This object is mandatory when adding a CID entry. Once a CID entry is added, this object can not be modified.
catmtCidProfileType
1.3.6.1.4.1.9.9.351.1.1.1.1.6
CiscoAal2ProfileType1 = itu2 = customIn VoATM, an AAL2 profile is used for the parameters of bearer traffic during the call setup between the call agent and the media gateway.
In AAL2 profile negotiation, some call agents provide the profile, some do not. If the AAL2 profile in the call setup is not provided by the call agent, the gateway can select its own configured AAL2 profiles.
Those AAL2 profiles can be ITU standard AAL2 profiles or customized AAL2 profiles.
This textual convention defines the profile type which is either standard profile from ITU or customized profile.
There are two groups of profile types:
itu - ITU standard profiles
custom - Customized profiles.Reference: ITU I.366.2 ATM forum af-vtoa-0113.000 · Integer32
This object specifies the type of the AAL2 CODEC profile. The combination of the profile type and profile number specified by 'catmtCidProfileNumber' defines an AAL2 CODEC profile.
This parameter is mandatory for adding and a voice trunking CID entry.
This object is applicable when catmtCidNx64Enable is is set to 'false'. It is used for voice trunking applications only.
catmtCidProfileNumber
1.3.6.1.4.1.9.9.351.1.1.1.1.7
CiscoAal2ProfileNumber1 = profileITU12 = profileITU23 = profileITU37 = profileITU78 = profileITU812 = profileITU12100 = profileCustom100101 = profileCustom101110 = profileCustom110200 = profileCustom200210 = profileCustom210This textual convention defines the profile number.
A profile contains a set of entries, each entry specifies an encoding format with an UUI (User-to-User Indicator) range and length. The profile set defines a mapping that the receiver of an AAL2 type 1 packet uses to interpret the the packet contents. (AAL2 has 3 different packet types : type 1: carry voice, type 2: not used, type 3: event, alarm.)
In other words, the profile set defines which encoding format from the profile is being used.
The following are the legitimate combinations of CiscoAal2ProfileType and CiscoAal2ProfileNumber:
ITU: 1, 2, 3, 7, 8, 12
Custom: 100, 101, 110, 200, 210Reference: ITU I.366.2 ATM forum af-vtoa-0113.000 · Integer32
This object specifies the AAL2 CODEC profile number. The combination of profile type and profile number defines an AAL2 CODEC profile.
A profile contains one or more entries, with each entry specifying an encoding algorithm and information regarding how the TDM data is to be packed into a packet.
This parameter is mandatory for adding a voice trunking CID entry.
This object is applicable when catmtCidNx64Enable is is set to 'false'. It is used for voice trunking applications only. Reference: ITU-T recommendation I.366.2.
This object specifies the CODEC type used for the AAL2 trunking connection.
The following table lists the CODEC types specified in each profile table by ITU I.366.2 standard.
----------------------------------------------------
Profile Profile Packet
type Number CODEC SID time(ms)
----------------------------------------------------
ITU 1 G.711u No SID 5
G.711a No SID 5
----------------------------------------------------
ITU 2 G.711u SIDG 5
G.711a SIDG 5
----------------------------------------------------
ITU 3 G.711u SIDG 5
G.711a SIDG 5
G726-40 SIDG 5
G726-32 SIDG 5
G726-24 SIDG 5
G726-16 SIDG 5
----------------------------------------------------
ITU 7 G.711u SIDG 5
G.711a SIDG 5
G.729ab SID729 10
G.729a No SID 10
----------------------------------------------------
ITU 8 G.711u No SID 5
G.711a No SID 5
G.726-32 No SID 5
G.729ab SID729 10
G.729a SID729 10
----------------------------------------------------
Custom 100 G.711u SIDG 5
G.711a SIDG 5
G.726-32 SIGD 10
----------------------------------------------------
Custom 101 G.711u No SID 5
G.711a No SID 5
G.726-32 No SID 10
G.729ab SID729 10
G.729a No SID 10
----------------------------------------------------
Custom 110 G.711u SIDG 5
G.711a SIDG 5
G.726-32 SIDG 10
G.729ab SID729 30
G.729a No SID 30
----------------------------------------------------
Custom 200 clearChan No SID 5
----------------------------------------------------
This object can only be set to the CODECs defined by the profile specified by catmtCidProfileType and catmtCidProfileNumber.
This object is applicable when catmtCidNx64Enable is is set to 'false'. It is used for voice trunking applications only.
This object is mandatory when adding a voice trunking CID entry.
This object specifies the CODEC type to be used for Voice Band Data (VBD) upspeed.
Upspeed is to change the transmission rate of a voice interface to a higher rate of CODEC type for fax/modem transportation.
This object is applicable when catmtCidNx64Enable is is set to 'false'. It is used for voice trunking applications only.
This object is mandatory when adding a voice trunking CID entry.
catmtCidNx64Enable
1.3.6.1.4.1.9.9.351.1.1.1.1.10
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object specifies whether a CID entry is in the Nx64 packet stream mode.
When this object is set to 'false', the CID connection is for voice trunking applications only; when it is set to 'true', the CID connection is for data trunking using Nx64 packet stream (N>=1).
This object can not be modified.
catmtCidNx64Profile
1.3.6.1.4.1.9.9.351.1.1.1.1.11
Integer32 (1..65535)
This object specifies the Nx64 data profile for an AAL2 data trunking connection.
The value of this object is a valid index of the cdapNx64ProfileTable in the CISCO-DATA-AALX-PROFILE-MIB.
This object is only applicable when catmtCidNx64Enable is set to 'true'.
catmtCidStateBitMap
1.3.6.1.4.1.9.9.351.1.1.1.1.12
BITS
This object is used to indicate the state of the CID.
All bits setting to 0 which means status 'okay'. Reference: ITU-T recommendation I.366.2 Annex N.
catmtCidRepetition
1.3.6.1.4.1.9.9.351.1.1.1.1.13
ConfigIteratorThis object type is a control object type which applies to writable objects in the same SNMP PDU related to the same table containing those objects. It controls an operation which repeatedly applies the specified configuration data to more than one rows in a table. The operation starts from the row specified by the index of the instance and repeats for the number of rows as the value of the object.
ConfigIterator object needs to be accompanied by one set of writable objects which are of the same instance to apply to.
For example, a SNMP PDU contains { objectA.10 = 1, objectB.10 = 'E1', objectC.10 = 44, objectRepetition.10 = 100 }
The SYNTAX of objectRepetition is ConfigIterator. This will apply value 1 to objectA, value 'E1' to objectB, value 44 to objectC in the table starting from row 10 repeatedly for 100 rows.
The iteration is based on the number of rows, not based on the value of the index. For sparse tables, the index 10, 20, 30, 110, and 120 counts for 5 rows, the operation will go beyond index 100 in the previous SNMP PDU example.
The iteration will stop prematurely when it comes to the following situations: (1) When the number of the rows in the table is less than the designated row indicated by the ConfigIterator object. (2) When it encounters the first error in any row, the operation won't continue to next row.
The operation of ConfigIterator object applies only to the writable objects having the same index as the ConfigIterator object in one SNMP PDU.
For example, a SNMP PDU contains { objectD.5 = 38, objectE.6 = 'T1', objectF.5 = 'false', objectIterator.5 = 10 }
The SYNTAX of objectIterator is ConfigIterator. This will apply value 38 to objectD, value 'false' to objectF in the table starting from row 5 repeatedly for 10 rows. Since the object objectE.6 has different index (6) from the index of objectIterator, the repetition won't be applied to it. However the value of objectE in the row 6 will be set to 'T1' according to regular SNMP SET orperation.
If there is row overlapping of the iteration in a SNMP PDU, it will be operated as they are in two different SNMP PDUs.
For example, a SNMP PDU contains { objectD.5 = 38, objectD.6 = 40, objectE.6 = 'T1', objectF.5 = 'false', objectIterator.5 = 10 objectIterator.6 = 10 }
This will apply value 38 to objectD, value 'false' to objectF starting from row 5 repeatedly for 10 rows, and apply value 40 to objectD, value 'T1' to objectE starting from row 6 repeatedly for 10 rows. The final value of objectD.6 can be 38 or 40, it depends on the SNMP stack of the system starts SNMP SET for the row 5 before the row 6 or the other way around.
The object defined as ConfigIterator will be set to value 1 after the iteration operation is kick-off regardless the system has completed the operation to the designated rows or not. Therefore retrieving the value of this object is meaningless. It acts as the one time operation for bulk configuration.
The object defined as ConfigIterator has no meaning by itself, it has to be combined with one or more than one writable objects from the same table and within the same SNMP PDU for the repetition operation.
For example, a SNMP PDU contains { objectG.2 = 49, objectH.2 = 'AE'h objectIterator.4 = 20 }
The SYNTAX of objectIterator is ConfigIterator. Since there are no objects having the same index as the index of objectIterator in the PDU, the result of this SNMP operation will set value 49 to objectG and value 0xAE to objectH of the row 2 only as regular SNMP SET operation.
The index of the instance indicates the starting row for the iteration. The order of the iteration depends, for instance, on: (1) physical hardware position, or (2) logical index.
It depends on the characters of the table which contains the ConfigIterator object.
Iteration can be done through some or all the components of the index for a table. The description of the iterator object in that table should describe which part of the index the iteration is applied to.
The operation for this object type is based on the best effort. When the agent receives a SNMP PDU containing this data type, the return status of the SNMP request reflects only the result of the SET operation has applied to the starting row. It may return a SNMP response with SUCCESS status regardless the number of rows for the data actually been deployed later on. Therefore it is possible the data might not be completely deployed to the number of rows designated by the ConfigIterator and the operation stops prematurely due to an error it first encounters after n rows (n < the value of ConfigIterator object).
Usually the error report mechanism for this type of operation is accomplished by combining this type of object with the other two objects in the same table:
(1) An OwnerString object (2) An object indicates the result of the operation.
When issuing this bulk configuration request, the SNMP manager should provide its identifier in (1) object. After issuing the request, it should check the value of (1) object if it is the same with it own name. If they are the same, then the value of the object presents in (2) is the result from the previous operation from this manager. Otherwise, another SNMP manager might issue the bulk configuration to the same table before the previous bulk operation has been completed. These two objects will represent the last bulk operation in the table. (1..4294967295) · Unsigned32
This object is used to repeatedly apply the writable objects of catmtCidTable specified in the same SNMP PDU starting from the row defined by the index object for the number of rows specified by this object.
The repetition operation works differently for data trunking and voice trunking applications. When catmtCidNx64Enable is set to 'false' (voice trunking), it is iterated through the value of DS0's and CID number. When catmtCidNx64Enable is set to 'true' (data trunking), the order of repetition operation is iterated through the value of DS1 index and CID number.
(1) For voice trunking applications: At each iteration, the value of CID (catmtCid), DS0 (catmtCidDs0GroupIndex) and DS1(catmtCidDs1) will be incremented. When the value of catmtCidDs0GroupIndex reaches its maximum, catmtCidDs1 will be incremented to the next logical order of DS1 interface.
(2) For data trunking applications: At each iteration, the value of catmtCid, catmtCidDs1
will be incremented. In other words, the Nx64 packet
stream repetition iterates on the DS1, with each DS1 interface having the same DS0 group (catmtCidDs0GroupIndex) configuration.
The repetition iteration will stop once the value of catmtCid reaches its maximum value 255 or when the next CID is not available or already configured for different type of trunking application. For example, a non-Nx64 repetition will stop if the next CID has been configured for Nx64 packet stream trunking, and vise versa. The repetition will also stop if the next contiguous DS0 group index is not available.
The maximum value of this object is 248 which is the maximum number of CID or AAL2 connections allowed within a VC connection.
catmtCidRepetitionOwner
1.3.6.1.4.1.9.9.351.1.1.1.1.14
OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences.
It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'.
SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING
This object is used for error reporting of the bulk provisioning operation specified by catmtCidRepetition.
The value of this object is set by the SNMP manager with its own identifier at the time of setting catmtCidRepetition to issue the bulk provisioning operation.
Later on, the SNMP manager checks the value of this object. If it matches its own name, the value of catmtCidRepetitionResult will be set to indicate the result of bulk operation initiated by this SNMP manager.
catmtCidRepetitionResult
1.3.6.1.4.1.9.9.351.1.1.1.1.15
BulkConfigResultThis textual convention defines the format of the displayable textual result from the bulk configuration operation specified as ConfigIterator type.
The format should be:
'COMPLETION= error occured>/,
ERROR=/: '
For example: 'COMPLETION=22/100,ERROR=38/44:Invalid Ds1 line coding for the line type' SIZE (0..255) · OCTET STRING
This object indicates the result of the bulk provisioning specified in catmtCidRepetition.
The format might look at (but not limited to): 'COMPLETION=<number of rows completed before any error occurred>/<number of rows was designated>, ERROR=<error code>/<index where the error occurred>: <error text>'
For example: 'COMPLETION=22/100,ERROR=38/44:Invalid DS1 line coding for the line type'
catmtCidRowStatus
1.3.6.1.4.1.9.9.351.1.1.1.1.16
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 for adding/deleting the entries from the catmtCidTable.
In order to create a CID entry, the following parameters are mandatory and must be provided:
For voice trunking applications: catmtDs1, catmtDs0GroupIndex, catmtCidProfileType, catmtCidProfileNumber, catmtCidVoiceCodec, catmtCidVBDCodec
For data trunking applications: catmtDs1, catmtDs0GroupIndex
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
A unique value, greater than zero, for each interface. 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.
catmtCidSentPackets
1.3.6.1.4.1.9.9.351.1.2.1.1.1
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · packets
This object indicates the number of packets sent towards network side since the connection setup.
catmtCidRcvdPackets
1.3.6.1.4.1.9.9.351.1.2.1.1.2
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · packets
This object indicates the count of packets received from network side since the connection setup.
catmtCidSentOctets
1.3.6.1.4.1.9.9.351.1.2.1.1.3
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · bytes
This object indicates the count of bytes sent towards network side since connection setup.
catmtCidRcvdOctets
1.3.6.1.4.1.9.9.351.1.2.1.1.4
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · bytes
This object indicates the count of bytes received from network since connection setup.
catmtCidLostPackets
1.3.6.1.4.1.9.9.351.1.2.1.1.5
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · packets
This object indicates the count of packets lost in the egress direction (from the network).
This number is computed based on the expected number of packets and the actual number of packets arrived from the network.
catmtCidJitter
1.3.6.1.4.1.9.9.351.1.2.1.1.6
Gauge32 (0..65535) · milliseconds
This object indicates the jitter (a.k.a interarrival jitter). This value is determined by the gateway DSP and obtained by the processor running on gateway upon querying the DSP periodically.
catmtCidExtAISCnts
1.3.6.1.4.1.9.9.351.1.2.1.1.7
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of external AIS AAL2 Type3 packets received.
External AIS : alarm indication signal associated with a maintenance alarm detected on a defective maintenance span, that is transmitted in the direction of the defect as a substitute for normal signal. The purpose is to show the downstream entities that a defect has been identified and to prevent other maintenance alarms consequent to this first defect. Reference: ITU-T G.366.2 Annex N
catmtCidExtRAICnts
1.3.6.1.4.1.9.9.351.1.2.1.1.8
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of external RAI AAL2 Type3 packets received.
External RAI is transmitted upstream from an entity that has detected defects persisting long enough to constitute a received signal failure. External RAI is to report in the backward direction to indicate there is an interruption of service in the forward direction. Reference: ITU-T G.366.2 Annex N
catmtCidConnAISCnts
1.3.6.1.4.1.9.9.351.1.2.1.1.9
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of external connection AIS AAL2 packets received.
External Conn AIS is a Alarm Indicating Signal transmitted in the downstream direction from the AAL2 connecting point that first detects the defect affecting the AAL2 connection including defects indicated by the lower layers. Reference: ITU-T G.366.2 Annex N
catmtCidConnRDICnts
1.3.6.1.4.1.9.9.351.1.2.1.1.10
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of external connection RDI AAL2 packets received.
External Connection RDI - is a signal transmitted in the
upstream direction by an AAL2 endpoint that is in alarm state, as the result of having received an AAL2 connection AIS or having detected a defect that affects the AAL2 connection. Reference: ITU-T G.366.2 Annex N
catmtCidNx64FramesTxToTDM
1.3.6.1.4.1.9.9.351.1.2.1.1.11
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of frames transmitted to the TDM interface.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64FramesRxFromTDM
1.3.6.1.4.1.9.9.351.1.2.1.1.12
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of frames received from the TDM interface.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64EncBytesTxToTDM
1.3.6.1.4.1.9.9.351.1.2.1.1.13
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of encoded bytes transmitted to the TDM interface.
catmtCidNx64EncBytesRxFromTDM
1.3.6.1.4.1.9.9.351.1.2.1.1.14
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of encoded bytes received from the TDM interface.
catmtCidNx64InvalidFCSFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.15
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with invalid Frame Check Sequence (FCS) error.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64AbortSeqFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.16
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with invalid frame abort sequence error.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64InvalidShortFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.17
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid short frames (length less than minimum length) received.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64InvalidLongFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.18
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid long frames (length greater than maximum length) received.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64NoByteAlignErrorFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.19
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with no byte alignment.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidNx64RASTimeOutFrames
1.3.6.1.4.1.9.9.351.1.2.1.1.20
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of frames received with RAS timer timeout.
This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
catmtCidLastResetTime
1.3.6.1.4.1.9.9.351.1.2.1.1.21
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
This object contains the value of sysUpTime when the last counter reset occurred.
If no counter reset has occurred since the last time connection is established, this object will contain value of zero.
catmtCidCounterClear
1.3.6.1.4.1.9.9.351.1.2.1.1.22
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
When this object is set to value of true(1), all statistics counters with type of Counter32SinceReset in the table catmtCidStatsTable will be reset to zero.
Setting this object to a value of false(2) has no implication.
This object will always return 'false' upon any SNMP get operation. I
catmtAal1Table
1.3.6.1.4.1.9.9.351.1.3.1
Index: ifIndex · catmtAal1Vpi · catmtAal1Vci
This table is used to establish the mapping of a DS0 to an AAL1 ATM connection.
This table is created and used for ATM AAL1 trunking applications only.
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
A unique value, greater than zero, for each interface. 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.
catmtAal1Vpi
1.3.6.1.4.1.9.9.351.1.3.1.1.1
Unsigned32 (0..4095)
This object is the VPI value of an ATM PVC connection.
catmtAal1Vci
1.3.6.1.4.1.9.9.351.1.3.1.1.2
Unsigned32 (0..65535)
This object is the VCI value of an ATM PVC connection.
catmtAal1Ds1
1.3.6.1.4.1.9.9.351.1.3.1.1.3
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 value of this object is equivalent to the 'ifIndex' of the DS1 interface.
This object is mandatory when adding an AAL1 entry. Once an AAL1 entry is added, this object can not be modified.
catmtAal1Ds0GroupIndex
1.3.6.1.4.1.9.9.351.1.3.1.1.4
Integer32 (0..30)
An arbitrary index that uniquely identifies one or a group of DS0s to be connected to an AAL1 trunking connection.
When catmtAal1Nx64Enable is set to 'false', the AAL1 trunking connection can only be a mapping of one single DS0 to one AAL1 ATM connection.
This object is mandatory when adding an AAL1 entry. Once an AAL1 entry is added, this object can not be modified.
catmtAal1Nx64Profile
1.3.6.1.4.1.9.9.351.1.3.1.1.5
Integer32 (1..65535)
This object specifies the Nx64 AAL1 data profile for an AAL1 trunking connection.
The value of this object is a valid index of cdapNx64Aal1ProfileTable in CISCO-DATA-AALX-PROFILE-MIB.
catmtAal1RowStatus
1.3.6.1.4.1.9.9.351.1.3.1.1.6
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 for adding/deleting the entries from the catmtAal1Table.
In order to create an AAL1 trunking entry, the following parameters are mandatory and must be provided: catmtAal1Ds1, catmtAal1Ds0GroupIdx
catmtAal1StatsTable
1.3.6.1.4.1.9.9.351.1.4.1
Index: ifIndex · catmtAal1Vpi · catmtAal1Vci
This table contains the statistics information on a per AAL1 connection basis for ATM AAL1 Trunking applications.
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
A unique value, greater than zero, for each interface. 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.
catmtAal1TxCells
1.3.6.1.4.1.9.9.351.1.4.1.1.1
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of ATM AAL1 cells transmitted from gateway to ATM network.
catmtAal1RxCells
1.3.6.1.4.1.9.9.351.1.4.1.1.2
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of ATM AAL1 cells gateway has received from ATM network.
catmtAal1TxPayloadBytes
1.3.6.1.4.1.9.9.351.1.4.1.1.3
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of payload bytes transmitted from gateway to ATM network.
catmtAal1RxPayloadBytes
1.3.6.1.4.1.9.9.351.1.4.1.1.4
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of payload bytes gateway has received from ATM network.
catmtAal1Jitter
1.3.6.1.4.1.9.9.351.1.4.1.1.5
Gauge32
This object indicates the jitter (a.k.a interarrival jitter).
The value of this object is determined by the gateway DSP and obtained by the processor running on gateway upon querying the DSP periodically.
catmtAal1LastResetTime
1.3.6.1.4.1.9.9.351.1.4.1.1.6
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
This object contains the value of sysUpTime when the last counter reset occurred.
If no counter reset has occurred since the last time system is up, this object will contain value of zero.
catmtAal1CounterClear
1.3.6.1.4.1.9.9.351.1.4.1.1.7
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
When this object is set to value of true(1), all statistics counters with type of Counter32SinceReset in the table catmtAal1StatsTable will be reset to zero.
Setting this object to value of false(2) has no implication.
This object will always return 'false' upon any SNMP get operation. I
catmtAal5Table
1.3.6.1.4.1.9.9.351.1.5.1
Index: ifIndex · catmtAal5Vpi · catmtAal5Vci
This table is used to establish the mapping of a DS0 to an AAL5 ATM connection.
This table is created and used for ATM AAL5 trunking applications only.
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
A unique value, greater than zero, for each interface. 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.
catmtAal5Vpi
1.3.6.1.4.1.9.9.351.1.5.1.1.1
Unsigned32 (0..4095)
This object is the VPI value of an ATM PVC connection.
catmtAal5Vci
1.3.6.1.4.1.9.9.351.1.5.1.1.2
Unsigned32 (0..65535)
This object is the VCI value of an ATM PVC connection.
catmtAal5Ds1
1.3.6.1.4.1.9.9.351.1.5.1.1.3
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 value of this object equals to the 'ifIndex' of the DS1 interface.
This object is mandatory when adding an AAL5 entry. Once an AAL5 entry is added, this object can not be modified.
catmtAal5Ds0GroupIndex
1.3.6.1.4.1.9.9.351.1.5.1.1.4
Integer32 (0..30)
An arbitrary index that uniquely identifies a DS0 group containing one or more DS0 that connect to an AAL5 trunking connection.
This object is mandatory when adding an AAL5 entry. Once an AAL5 entry is added, this object can not be modified.
catmtAal5Nx64Profile
1.3.6.1.4.1.9.9.351.1.5.1.1.5
Integer32 (1..65535)
This object specifies the Nx64 data profile for an AAL5 trunking connection.
The value of this object is a valid index of the cdapNx64ProfileTable in CISCO-DATA-AALX-PROFILE-MIB.
catmtAal5RowStatus
1.3.6.1.4.1.9.9.351.1.5.1.1.6
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 for adding/deleting the entries from the catmtAal5Table.
In order to create an AAL5 trunking entry, the following parameters are mandatory and must be provided: catmtAal5Ds1, catmtAal5Ds0GroupIdx
catmtAal5StatsTable
1.3.6.1.4.1.9.9.351.1.6.1
Index: ifIndex · catmtAal5Vpi · catmtAal5Vci
This table contains the statistical information on a per AAL5 connection basis for ATM AAL5 Trunking applications.
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
A unique value, greater than zero, for each interface. 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.
catmtAal5SentPackets
1.3.6.1.4.1.9.9.351.1.6.1.1.1
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · packets
This object indicates the number of packets sent towards network side since the connection is up.
catmtAal5RcvdPackets
1.3.6.1.4.1.9.9.351.1.6.1.1.2
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · packets
This object indicates the count of packets received from network side since the connection setup.
catmtAal5SentOctets
1.3.6.1.4.1.9.9.351.1.6.1.1.3
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · bytes
This object indicates the count of bytes sent towards network side since connection setup.
catmtAal5RcvdOctets
1.3.6.1.4.1.9.9.351.1.6.1.1.4
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32 · bytes
This object indicates the count of bytes received from network since connection setup.
catmtAal5FramesTxToTDM
1.3.6.1.4.1.9.9.351.1.6.1.1.5
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of frames transmitted to the TDM interface.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5FramesRxFromTDM
1.3.6.1.4.1.9.9.351.1.6.1.1.6
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of frames received from the TDM interface.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5EncBytesTxToTDM
1.3.6.1.4.1.9.9.351.1.6.1.1.7
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of encoded bytes transmitted to the TDM interface.
catmtAal5EncBytesRxFromTDM
1.3.6.1.4.1.9.9.351.1.6.1.1.8
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of encoded bytes received from TDM interface.
catmtAal5InvalidFCSFrames
1.3.6.1.4.1.9.9.351.1.6.1.1.9
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with invalid Frame Check Sequence (FCS) error.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5AbortSeqFrames
1.3.6.1.4.1.9.9.351.1.6.1.1.10
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with invalid frame abort sequence error.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5InvalidShortFrames
1.3.6.1.4.1.9.9.351.1.6.1.1.11
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid short frames (length less than minimum length) received.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5InvalidLongFrames
1.3.6.1.4.1.9.9.351.1.6.1.1.12
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid long frames (length greater than maximum length) received.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5NoByteAlignErrorFrames
1.3.6.1.4.1.9.9.351.1.6.1.1.13
Counter32SinceResetThis textual convention defines a counter type that is similar to Counter32 but can be reset. The value of the objects of this type indicates the statistics since last counter reset.
Once the value of the counter object of this type reaches its maximum, it will restart from zero again. (0..2147483647) · Unsigned32
This object contains the number of invalid frames received with no byte alignment.
This object is only applicable when catmtAal5Nx64Mode is set to to 'hdlc'.
catmtAal5LastResetTime
1.3.6.1.4.1.9.9.351.1.6.1.1.14
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
This object contains the value of sysUpTime when the last counter reset occurred.
If no counter reset has occurred since the last time system is up, this object will contain value of zero.
catmtAal5CounterClear
1.3.6.1.4.1.9.9.351.1.6.1.1.15
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
When this object is set to value of true(1), all statistics counters with type of Counter32SinceReset in the table catmtAal5StatsTable will be reset to zero.
Setting this object to a value of false(2) has no implication.
This object will always return 'false' upon any SNMP get operation. I