CISCO-DS1-EXT-MIB

INTEGER1 = other2 = dsx1ESF3 = dsx1D44 = dsx1E15 = dsx1E1CRC6 = dsx1E1MF7 = dsx1E1CRCMF8 = dsx1Unframed9 = dsx1E1Unframed10 = dsx1DS2M1211 = dsx2E220 = dsx1E1Q5021 = dsx1E1Q50CRC · Integer32

Reference: ITU-T G.704.

This variable indicates the variety of DS1 Line implementing this circuit. The type of circuit affects the number of bits per second that the circuit can reasonably carry, as well as the interpretation of the usage and error statistics. The reasons behind adding 'cds1Linetype' object (apart from 'dsx1LineType' in DS1-MIB.my) for 'line type', with enums from 'other(1)' to 'dsx2E2(11)' replicated, are following: 1) Addition of the two new enums (viz. 'dsx1E1Q50' and 'dsx1E1Q50CRC') in the standard DS1-MIB might not take place in near future; that's why it was decided to have a new object 'cds1LineType'. 2) A way was needed to be provided to configure 'line type' from CLI (Command Line Interface) for service modules supporting line type values from 'dsx1LineType' as well as 'cds1LineType', without having to modify two separate parameters and at the same time, making sure that CLI parameter values directly map to the MIB values. Hence, enums from 'other(1)' to 'dsx2E2(11)' from object 'dsx1LineType' are replicated, and the new enums are added as 'dsx1E1Q50(20)' and 'dsx1E1Q50CRC(21)'. The gap between 'dsx2E2(11)' and 'dsx1E1Q50(20)' provides a safe margin in the case of modifications in 'dsx1LineType' in future; so the CLI can still have the same enums as the standard MIB. It is to be noted that objects 'dsx1LineType' and 'cds1LineType' are mutually exclusive. Setting both in a SET request (with the exception of value 'other(1)') should result into an 'INCONSISTENT VALUE' error. In the case of successive 'SET' requests, the value associated with the latest request should prevail irrespective of the object ('dsx1LineType' or 'cds1LineType') used. Following values reflect the corresponding values in 'dsx1LineType' object in DS1-MIB. dsx1ESF Extended SuperFrame DS1 (T1.107) dsx1D4 AT&T D4 format DS1 (T1.107) dsx1E1 ITU-T Recommendation G.704 (Table 4a) dsx1E1-CRC ITU-T Recommendation G.704 (Table 4b) dsxE1-MF G.704 (Table 4a) with TS16 multiframing enabled dsx1E1-CRC-MF G.704 (Table 4b) with TS16 multiframing enabled dsx1Unframed DS1 with No Framing dsx1E1Unframed E1 with No Framing (G.703) dsx1DS2M12 DS2 frame format (T1.107) dsx1E2 E2 frame format (G.704) The recommended value for 'dsx1LineType' object is 'other'(1) for following values. dsx1E1Q50(20) ITU-T G.704 with TS16 bits 5,7,8 set to 101. In all the other cases TS16 bits 5,7,8 set to 111.(Table 14) dsx1E1Q50CRC(21): dsx1E1Q50 with CRC. For clarification, the capacity for each E1 type is as listed below: dsx1E1Unframed - E1, no framing = 32 x 64k = 2048k dsx1E1 or dsx1E1CRC - E1, with framing, no signalling = 31 x 64k = 1984k dsx1E1MF or dsx1E1CRCMF - E1, with framing, signalling = 30 x 64k = 1920k For further information See ITU-T Recomm G.704

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object is used to enable or disable the detection of far end loop back requests (inband or out-of-band (ESF)). The loopback detection is enabled by setting this object to 'true' and loopback detection is disabled by setting this object to 'false'. The value of this object does not have any impact on the way dsx1LoopbackConfig object is implemented.

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 dsx1ConfigTable and cds1ConfigTable specified in the same SNMP PDU starting from the row indicated by the index of the instance for the number of rows specified in this object. The order of operation is iterated through the logical order of the DS1 lines. Whether the iteration will be applied across the physical boundary or not is depended on the system implmentation. The GET operation on this object will always return 1.

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 checking of the operation specified in cds1Repetition. The value of this object is set by the SNMP manager for its own identifier at the same time as issuing the bulk operation by setting cds1Repetition. Later on, the SNMP manager should check the value of this object, if it is the same with the SNMP manager name, then the value of cds1RepetitionResult indicates the result of bulk operation initiated by this SNMP manager.

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 is used for error checking of the operation specified in cds1Repetition. This object indicates the result of bulk configuraton initiated by the SNMP manager specified in the value of cds1RepetitionOwner.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object specifies whether trunk-condition is enabled. The value 'true' means trunk-condition enable and the value 'false' means trunk-condition disable. If this object is set to 'true', gateway will apply trunk conditioning on the DS0's of this DS1 interface that are in alarm. Trunk Conditioning - gateway will transmit idle code pattern for the first 2.5 secs and then transmit seized code, both idle code and seized code are specified by the 'ds0IdleCode' and 'ds0SeizedCode' MIB objects in the CISCO-CAS-IF-EXT-MIB. This object is applicable for trunking applications only.

Integer32 (1..2147483647)

An unique value identifying an entry in cds1AlarmThresholdGroupTable.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 15 minute threshold for BES.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 24 hour threshold for BES.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 15 minute threshold for CSS.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 24 hour threshold for CSS.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 15 minute threshold for DM.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 24 hour threshold for DM.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for ES.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for ES.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for LCV.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for LCV.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for LES.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for LES.

Integer32 (0..2147483647)

Reference: ANSI T1.231-1997 Section 6.5.1.3

This object identifies 15 minute threshold for LSES.

Integer32 (0..2147483647)

Reference: ANSI T1.231-1997 Section 6.5.1.3

This object identifies 24 hour threshold for LSES.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 15 minute threshold for PCV.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 24 hour threshold for PCV.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 15 minute threshold for PSAS.

Integer32 (0..2147483647)

Reference: RFC2495

This object identifies 24 hour threshold for PSAS.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for SES.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for SES.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for SEFS.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for SEFS.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 15 minute threshold for UAS.

Integer32 (0..2147483647)

Reference: RFC2495, Bellcore TR-TSV-000773

This object identifies 24 hour threshold for UAS.

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

The status of this conceptual row. This object is used for creating, modifying and deleting entries from cds1AlarmThresholdGroupTable. To create a row in this table, a manager must set this object to 'createAndGo(4)'. An entry can be deleted by setting this object to destroy'(6)'. An entry in this table may be modified after creation. The active threshold configuration is indicated by the object 'cds1AlarmThresholdActiveGroup'.

INTEGER1 = minor2 = major3 = none · Integer32

This variable is used to setup the severity of any of the Statistical alarms. So when a Statistical Counter exceeds its specified threshold, the system will send the alarm with appropriate severity. A value of none(3) indicates that no alarm will be raised.

BITS

This is a bitmap of the DS1 Line Statistical alarms. A clear bitmap (i.e. no bit is set) will indicate that no alarms are present. The values of individual bits mean: cds1BES15Min BES current 15 minute threshold exceeded cds1BES24Hr BES 24 hour threshold exceeded cds1CSS15Min CSS current 15 minute threshold exceeded cds1CSS24Hr CSS 24 hour threshold exceeded cds1DM15Min DM current 15 minute threshold exceeded cds1DM24Hr DM 24 hour threshold exceeded cds1ES15Min ES current 15 minute threshold exceeded cds1ES24Hr ES 24 hour threshold exceeded cds1PCV15Min PCV current 15 minute threshold exceeded cds1PCV24Hr PCV 24 hour threshold exceeded cds1LCV15Min LCV current 15 minute threshold exceeded cds1LCV24Hr LCV 24 hour threshold exceeded cds1LES15Min LES current 15 minute threshold exceeded cds1LES24Hr LES 24 hour threshold exceeded cds1LSES15Min LSES current 15 minute threshold exceeded cds1LSES24Hr LSES 24 hour threshold exceeded cds1PSAS15Min PSAS current 15 minute threshold exceeded cds1PSAS24Hr PSAS 24 Hour threshold exceeded cds1SES15Min SES current 15 minute threshold exceeded cds1SES24Hr SES 24 hour threshold exceeded cds1SEFS15Min SEFS current 15 minute threshold exceeded cds1SEFS24Hr SEFS 24 hour threshold exceeded cds1UAS15Min UAS current 15 minute threshold exceeded cds1UAS24Hr UAS 24 hour threshold exceeded

Integer32 (0..2147483647)

This parameter specifies the increment to the Near End alarm integration counters. The local alarms are LOS and LOF. The integration counter is incremented by this value every 100 ms while the alarm persists. When the integration counter exceeds 'cds1AlarmThreshold' an Alarm of the severity specified for the particular alarm is declared. The integration counter is an internal counter specific to the implementation and dictates the slope of integration.

Integer32 (0..2147483647)

This parameter specifies the decrement to the Near End alarm integration counters. The alarms are LOS and LOF. The integration counter is decremented by this value every 100 ms while no alarm persists. The counter does not decrement below zero. When the integration counter reaches zero any Alarm previously declared is removed.

Integer32 (0..2147483647)

The value set in this object determines the value that the alarm integration counter must reach for an near end alarm to be declared. If the up count is 6, and the threshold 150, an Alarm is integrated in 2.5 seconds. If the down count is 1, then alarm will be cleared in 15 seconds.

Integer32 (1..2147483647)

The value of this object identifies the row in the cds1AlarmThresholdGroupTable which contains the threshold values for different statistics, and is currently active.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Reference: ANSI T1.231-1997 Section 6.5.1.3

The number of LSES (Line Severely Errored Seconds) encountered by the interface.

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Reference: ANSI T1.231-1997 Section 6.5.1.3

The number of Path SEF/AIS (PSAS) encountered by the ds1 interface.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32

Reference: ANSI T1.231-1997 Section 6.5.1.3

The number of LSES (Line Severely Errored Seconds) encountered by the interface.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32

The number of PSAS encountered by the interface.

PerfTotalCountA counter associated with a performance measurements aggregating the previous valid 15 minute measurement intervals. (Intervals for which no valid data was available are not counted) · Gauge32

The sum of Line Severely Errored Seconds (LSES) encountered by a DS1 interface in the previous 96 fifteen minutes intervals.

PerfTotalCountA counter associated with a performance measurements aggregating the previous valid 15 minute measurement intervals. (Intervals for which no valid data was available are not counted) · Gauge32

The sum of Path SEF/AIS (PSAS) encountered by a DS1 interface in the previous 96 fifteen minutes intervals

PerfCurrentCountA counter associated with a performance measurement in a current 15 minute measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 15 minute interval. At that time the value of the counter is stored in the first 15 minute history interval, and the CurrentCount is restarted at zero. In the case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

The number of Loss Of Frame Counts in the current 15 minute interval.

PerfIntervalCountA counter associated with a performance measurement in a previous 15 minute measurement interval. In the case where the agent has no valid data available for a particular interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). In a system supporting a history of n intervals with IntervalCount(1) and IntervalCount(n) the most and least recent intervals respectively, the following applies at the end of a 15 minute interval: - discard the value of IntervalCount(n) - the value of IntervalCount(i) becomes that of IntervalCount(i-1) for n >= i > 1 - the value of IntervalCount(1) becomes that of CurrentCount - the TotalCount, if supported, is adjusted. · Gauge32

The number of Loss Of Frame Counts encountered by the interface.

PerfTotalCountA counter associated with a performance measurements aggregating the previous valid 15 minute measurement intervals. (Intervals for which no valid data was available are not counted) · Gauge32

The number of Loss Of Frame Counts encountered by the interface in the previous 96 fifteen minutes interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of ESs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of SESs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of SEFSs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of UASs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of CSSs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of PCVs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of LESs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of BESs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of DMs encountered in current 24 hour interval.

PerfCurrent24HourCountA counter associated with a performance measurement in the current 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of LCVs encountered in current 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of ESs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of SESs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of SEFSs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of UASs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of CSSs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of PCVs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of LESs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of BESs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of DMs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of LCVs encountered in previous 24 hour interval.

PerfPrevious24HourCountA counter associated with a performance measurement in the previous 24 hour measurement interval. The value of this counter starts from zero and is increased when associated events occur, until the end of the 24 hour interval. In case where the agent has no valid data available for the current interval the corresponding object instance is not available and upon a retrieval request a corresponding error message shall be returned to indicate that this instance does not exist (for example, a noSuchName error for SNMPv1 and a noSuchInstance for SNMPv2 GET operation). · Gauge32

Number of LSESs encountered in previous 24 hour interval.

Counter32

The number of times the Loss Of Signal defect was detected with or without integrating to LOS alarm.

Counter32

The number of times the Out of Frame (OOF) was detected with or without integrating to OOF alarm.

Counter32

The number of times Yellow Alarms was detected with or without integrating to RAI alarm.

Counter32

The number of Framing Pattern Errors encountered by the DS1 interface.