CISCO-ITP-SP-MIB

CItpTcNetworkIndicator0 = international1 = internationatSpare2 = national3 = nationalSpareNetwork Indicator: international - International network national - National network reserved - Reserved for national use spare - Spare (for international use only) 'international' : International network 'internationalSpare' : International network spare 'national' : National network 'nationalSpare' : National network Spare · Integer32

The network Indicator for this pointcode.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The point code for this SP.

CItpTcPointCodeType1 = primary2 = additional3 = capability4 = xuaList of the possible Point Code types. 'primary' : The primary point used to communicate information on the Signalling point. 'additional' : Additional point codes. 'capability' : capability point codes. 'xua' : MTP3-User Adaptation point codes or SCCP-User Adaptation point codes. · Integer32

The function of this point code

CItpTcDisplayPCThe Point Code in formatted based on the variant and the customer defined parameters. SIZE (1..12) · OCTET STRING

The point code for this SP.

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 object is used by a management station to create or delete the row entry in cItpSpPointCodeTable following the RowStatus textual convention.

CItpTcLinksetIdThe configured name associated with an Signalling Point Linkset. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

The name of the linkset.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The point code to which this linkset is connected.

CItpTcDisplayPCThe Point Code in formatted based on the variant and the customer defined parameters. SIZE (1..12) · OCTET STRING

The point code to which this linkset is connected.

CItpTcPointCodeThe SS7 network node address as specified in the following references. The format of the Point code depends on the variant defined in the CgspSS7Variant object as follows. 33222222222211111111110000000000 10987654321098765432109876543210 ANSI: nnnnnnnn - Network cccccccc - Cluster mmmmmmmm - Member ITU: zzz - Zone aaaaaaaa - Area/Network iii - Identifier NTT: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier TTC: zzzzz - Zone aaaa - Area/Network iiiiiii - Identifier Note: The China variant has the same format as ANSI. This form of the point-code is not intended for for presentation.Reference: The SS7 network node address as specified in the International Telecommunication Union standard Q.708: Specifications of Signalling System No. 7 - Numbering of International Signalling Point Codes, and by ANSI T1.111.8 Numbering of Signalling Point Codes. GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. (0..16777216) · Unsigned32

The point code to which this linkset is connected.

CItpTcDisplayPCThe Point Code in formatted based on the variant and the customer defined parameters. SIZE (1..12) · OCTET STRING

The point code to which this linkset is connected.

INTEGER1 = available2 = shutdown3 = unavailable · Integer32

The list of possible linkset states. 'available' : Traffic may flow over this linkset 'shutdown' : This linkset has been forced to an unavailable state by an administrative action. 'unavailable': The linkset is currently unable to support traffic. Activation of this linkset will occur as required by protocol.

CItpTcAclIdAn numeric Identifier used to specify an access list used to permit and deny packets based on MTP3 information. Either the value 0 or the value of access list identifier. A value of zero indicates that an access list is not specified. (0 | 2700..2999) · Unsigned32

Packets are filtered against this access control list before they are passed to the routing function. A value of zero indicates that no access control list is present.

CItpTcAclIdAn numeric Identifier used to specify an access list used to permit and deny packets based on MTP3 information. Either the value 0 or the value of access list identifier. A value of zero indicates that an access list is not specified. (0 | 2700..2999) · Unsigned32

Packets are filtered against this access control list after they have passed through the routing function. A value of zero indicates that no access control list is present.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Signalling network management messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Signalling network test and maintenance messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for SS7 Signalling Connection Control Part(SCCP) messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Telephone User Part(TUP) messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for ISDN User Part messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Data User Part (call and circuit-related messages).

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Data User Part (facility registration and cancellation messages).

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for MTP Testing User Part messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Broadband ISDN User Part(BISUP) messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

The routing table for Satellite ISDN User Part(SISUP) messages.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

CItpTcRouteTableNameThe configured name associated with an SP Route Table. An octet string specified by an administrator that must be in human-readable form. The names must conform to the allowed characters that can be specified via Command Line Interface(CLI). The names cannot contain control character and should not contain leading or trailing white space. SIZE (1..19) · OCTET STRING

Reference: ITU Q.704 Signalling network functions and messages, section 14.2.1.

This routing table has been defined as a spare routing table by the standards committee.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This indicates if accounting for this linkset is enabled. 'true' Indicates that the accounting function is enabled for this linkset and is being accumulated in cItpSpAccountingTable. 'false' Indicates that the accounting function is disabled.

Unsigned32

The number of links in this linkset.

TimeTicks

Time linkset was providing service related to Q752/Table 4.2.

TimeTicks

Time linkset was Out-of-Service as required for Q752/Table 4.2.

CItpTcTimerMtp2T01Alignment ready timer. The default and valid range is dependant on the value of variant. Min Max Def ------ ------ ------ ANSI 12500 16000 13000 ITU 40000 50000 40000 The SYNTAX statement allows values for both the ANSI, ITU variants and MTP2 Peer-to-Peer Adaptation Layer.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (5000..150000) · Unsigned32 · milliseconds

Alignment ready timer.

CItpTcTimerMtp2T02Not aligned timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 5000 14000 11500 ITU 5000 150000 5000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 5000..150000) · Unsigned32 · milliseconds

Not aligned timer.

CItpTcTimerMtp2T03Aligned timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 5000 14000 11500 ITU 1000 2000 1500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 1000..14000) · Unsigned32 · milliseconds

Aligned timer.

CItpTcTimerMtp2T04EProving period timer emergency timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 540 660 600 ITU 400 600 500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 400..660) · Unsigned32 · milliseconds

Proving period timer emergency timer.

CItpTcTimerMtp2T04NProving period timer normal timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 2007 2530 2300 ITU 7500 9500 8200 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 2007..9500) · Unsigned32 · milliseconds

Proving period timer normal timer.

CItpTcTimerMtp2T05Sending SIB timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 80 120 80 ITU 80 120 100 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 80..120) · Unsigned32 · milliseconds

Sending SIB timer.

CItpTcTimerMtp2T06Remote congestion timer. The default and valid range is dependant on the value of variant. Min Max Def ------ ------ ------ ANSI 1000 6000 1000 ITU 3000 6000 3000 The SYNTAX statement allows values for both the ANSI, ITU variants and MTP2 Peer-to-Peer Adaptation Layer.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..6000) · Unsigned32 · milliseconds

Remote congestion timer.

CItpTcTimerMtp2T07Excessive delay of acknowledgement timer. The default and valid range is dependant on the value of variant(). This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 500 2000 1000 ITU 500 2000 1000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 100..6000) · Unsigned32 · milliseconds

Excessive delay of acknowledgement timer.

CItpTcTimerMtp3T01Delay to avoid message mis-sequencing on changeover. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Delay to avoid message mis-sequencing on changeover.

CItpTcTimerMtp3T02Waiting for changeover acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 700 2000 1400 ITU 700 2000 1400 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (700..2000) · Unsigned32 · milliseconds

Waiting for changeover acknowledgement.

CItpTcTimerMtp3T03Time controlled diversion-delay to avoid mis-sequencing on change back. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Time controlled diversion-delay to avoid mis-sequencing on change back.

CItpTcTimerMtp3T04Waiting for change back acknowledgement (first attempt). Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Waiting for change back acknowledgement (first attempt).

CItpTcTimerMtp3T05Waiting for change back acknowledgement (second attempt). Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Waiting for change back acknowledgement (second attempt).

CItpTcTimerMtp3T06Delay to avoid message mis-sequencing on controlled rerouting. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Delay to avoid message mis-sequencing on controlled rerouting.

CItpTcTimerMtp3T07Waiting for Signalling data link connection acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 1000 2000 1500 ITU 1000 2000 1500 The SYNTAX statement allows values for both the ANSI and ITU variants. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 1000..2000) · Unsigned32 · milliseconds

Waiting for Signalling data link connection acknowledgement.

CItpTcTimerMtp3T08Transfer prohibited inhibition timer (transient solution). Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1200 1000 ITU 800 1200 1000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1200) · Unsigned32 · milliseconds

Transfer prohibited inhibition timer (transient solution).

CItpTcTimerMtp3T10Waiting to repeat Signalling routeset test message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 60000 45000 ITU 30000 60000 45000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (30000..60000) · Unsigned32 · milliseconds

Waiting to repeat Signalling routeset test message.

CItpTcTimerMtp3T11Transfer restricted timer. (This is one way of implementing the function described in 13.4/Q.704 and mainly intended to simplify SPs.). Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 90000 60000 ITU 30000 90000 60000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (30000..90000) · Unsigned32 · milliseconds

Transfer restricted timer. (This is one way of implementing the function described in 13.4/Q.704 and mainly intended to simplify SPs.).

CItpTcTimerMtp3T12Waiting for uninhibit acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Waiting for uninhibit acknowledgement.

CItpTcTimerMtp3T13Waiting for force uninhibit. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Waiting for force uninhibit.

CItpTcTimerMtp3T14Waiting for inhibition acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 3000 2500 ITU 2000 3000 2500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (2000..3000) · Unsigned32 · milliseconds

Waiting for inhibition acknowledgement.

CItpTcTimerMtp3T15Waiting to start Signalling routeset congestion test. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 3000 2500 ITU 2000 3000 2500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (2000..3000) · Unsigned32 · milliseconds

Waiting to start Signalling routeset congestion test.

CItpTcTimerMtp3T16Waiting for routeset congestion status update. Ranges by variant. Min Max Def ------ ------ ------ ANSI 1400 2000 1700 ITU 1400 2000 1700 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1400..2000) · Unsigned32 · milliseconds

Waiting for routeset congestion status update.

CItpTcTimerMtp3T17Delay to avoid oscillation of initial alignment failure and link restart. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Delay to avoid oscillation of initial alignment failure and link restart.

CItpTcTimerMtp3T18This timers servers different function based on the variant. ANSI: Repeat TFR once by response method ITU: MTP restart link supervision Min Max Def ------ ------ ------ ANSI 2000 20000 11000 ITU 1000 31000 30000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..31000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: Repeat TFR once by response method ITU: MTP restart link supervision

CItpTcTimerMtp3T19This timers servers different function based on the variant. ANSI: failed craft timer referral timer ITU: supervision timer during MTP restart Min Max Def ------ ------ ------ ANSI 480000 600000 540000 ITU 67000 69000 68000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (67000..600000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: failed craft timer referral timer ITU: supervision timer during MTP restart

CItpTcTimerMtp3T20This timers servers different function based on the variant. ANSI: waiting to repeat local inhibit test ITU: MTP restart timer at the Signalling point Min Max Def ------ ------ ------ ANSI 90000 120000 105000 ITU 1000 61000 60000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..120000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: waiting to repeat local inhibit test ITU: MTP restart timer at the Signalling point

CItpTcTimerMtp3T21This timers servers different function based on the variant. ANSI: waiting to repeat remote inhibit test) ITU: MTP restart timer at adjacent Signalling point Min Max Def ------ ------ ------ ANSI 90000 120000 105000 ITU 63000 65000 64000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (63000..120000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: waiting to repeat remote inhibit test) ITU: MTP restart timer at adjacent Signalling point

CItpTcTimerMtp3T22This timers servers different function based on the variant. ANSI: restarting SP waiting for Signalling links avail ITU: local inhibit test timer Min Max Def ------ ------ ------ ANSI 36000 60000 30000 ITU 80000 360000 300000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (36000..360000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting for Signalling links avail ITU: local inhibit test timer

CItpTcTimerMtp3T23This timers servers different function based on the variant. ANSI: restarting SP waiting to receive all TRA msgs ITU: remote inhibit test timer Min Max Def ------ ------ ------ ANSI 9000 60000 30000 ITU 80000 360000 300000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (9000..360000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting to receive all TRA msgs ITU: remote inhibit test timer

CItpTcTimerMtp3T24This timers servers different function based on the variant. ANSI: restarting SP waiting to broadcast all TRA msgs ITU: stabilizing timer after local processor outage Min Max Def ------ ------ ------ ANSI 9000 60000 30000 ITU 500 500 500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..60000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting to broadcast all TRA msgs ITU: stabilizing timer after local processor outage

CItpTcTimerMtp3T25Timer at Signalling Point (SP) adjacent to restarting SP, waiting for traffic restart allowed message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 35000 30000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 30000..35000) · Unsigned32 · milliseconds

Timer at Signalling Point (SP) adjacent to restarting SP, waiting for traffic restart allowed message.

CItpTcTimerMtp3T26Timer at restarting SP waiting to repeat traffic restart waiting message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 12000 15000 12000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 12000..15000) · Unsigned32 · milliseconds

Timer at restarting SP waiting to repeat traffic restart waiting message.

CItpTcTimerMtp3T27Minimum duration of unavailability for full restart. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 50000 4000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 2000..50000) · Unsigned32 · milliseconds

Minimum duration of unavailability for full restart.

CItpTcTimerMtp3T28Timer at SP adjacent to restarting SP waiting for traffic restart waiting message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 3000 35000 30000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 3000..35000) · Unsigned32 · milliseconds

Timer at SP adjacent to restarting SP waiting for traffic restart waiting message.

CItpTcTimerMtp3T29Timer started when TRA sent in response to unexpected TRA or TRW. Ranges by variant. Min Max Def ------ ------ ------ ANSI 60000 65000 63000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 60000..65000) · Unsigned32 · milliseconds

Timer started when TRA sent in response to unexpected TRA or TRW.

CItpTcTimerMtp3T30Timer to limit sending of TFPs and TFRs in response to unexpected TRA or TRW. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 35000 33000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 30000..35000) · Unsigned32 · milliseconds

Timer to limit sending of TFPs and TFRs in response to unexpected TRA or TRW.

CItpTcTimerMtp3T31False link congestion detection timer. Ranges by variant. Min Max Def ------ ------ ------ ANSI 10000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 10000..120000) · Unsigned32 · milliseconds

False link congestion detection timer.

CItpTcTimerMtp3T32Link oscillation timer - Procedure A. Ranges by variant. Min Max Def ------ ------ ------ ANSI 5000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 5000..120000) · Unsigned32 · milliseconds

Link oscillation timer - Procedure A.

CItpTcTimerMtp3T33Probation timer for link oscillation - Procedure B. Ranges by variant. Min Max Def ------ ------ ------ ANSI 60000 600000 300000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 60000..600000) · Unsigned32 · milliseconds

Probation timer for link oscillation - Procedure B.

CItpTcTimerMtp3T34Suspension timer for link oscillation - Procedure B. Ranges by variant. Min Max Def ------ ------ ------ ANSI 5000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 5000..120000) · Unsigned32 · milliseconds

Suspension timer for link oscillation - Procedure B.

CItpTcTimerLinkTestSignalling Link test acknowledgement timer. Min Max Def ------ ------ ------ ANSI 4000 12000 8000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 4000..12000) · Unsigned32 · milliseconds

Signalling Link test acknowledgement timer.

CItpTcTimerLinkMessageInterval timer for sending test messages. Min Max Def ------ ------ ------ ANSI 30000 90000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 30000..90000) · Unsigned32 · milliseconds

Interval timer for sending test messages.

CItpTcTimerLinkActRetryLink activation retry timer. Min Max Def ------ ------ ------ ANSI 60000 90000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 60000..90000) · Unsigned32 · milliseconds

Link activation retry timer.

Integer32 (0 | 56000..2147483647) · bps

An estimate of the number of bits per second that is expected to be transmitted over a linkset. This attribute will be used by network management stations to generate traps and maintain statistics on linksets based on Stream Control Transmission Protocol. The information for this attribute is specified via CLI by the system administrator. A value of zero for this object indicates that a planning capacity has not been specified. This objects has been deprecated and replaced by cItpSpLinkPlanCapacityRcvd and cItpSpLinkPlanCapacitySent objects.

Unsigned32 (0..255)

Defines the activation priority for linksets. Each linkset can be defined a priority. The linkset with the lowest values will be activated first. If two linksets share the same values they will be activated in the order they were defined.

INTEGER1 = access2 = bridge3 = cross4 = diagonal5 = fullyAssoc · Integer32

The list of possible Signalling link types. All links in the same linkset will be of the same type. 'A-link' : Access link 'B-link' : Bridge link 'C-link' : Cross link 'D-link' : Diagonal link 'E-link' : Fully associated link

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 object is used by a management station to create or delete the row entry in cItpSpLinksetTable following the RowStatus textual convention.

CItpTcNetworkIndicator0 = international1 = internationatSpare2 = national3 = nationalSpareNetwork Indicator: international - International network national - National network reserved - Reserved for national use spare - Spare (for international use only) 'international' : International network 'internationalSpare' : International network spare 'national' : National network 'nationalSpare' : National network Spare · Integer32

The Network Indicator in which the Linkset resides.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..30) · OCTET STRING · hint 255t

A short identifier for each linkset. This value can be set by system administrator or defaults to the linkset name.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..254) · OCTET STRING · hint 255t

A textual description for the Signalling point.

CItpTcSs7Variant1 = ansi2 = itu3 = chinaThe list of SS7 variants. 'ANSI' : The ANSI variant of the SS7 specification. 'ITU' : The ITU variant of the SS7 specification. 'China' : The China national variant. This variant is a combination of ITU and ANSI. The protocol matches ITU except where the point-code has been expanded to ANSI format.Reference: GF 001-9001 - Technical Specifications of Signalling System No. 7 for National Telephone Network of China. · Integer32

The SS7 variant used to format data transmitted on this linkset.

CItpTcLinkSLCThe Signalling Link Code. This is the link identifier within a linkset. (0..15) · Unsigned32

Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP).

The Signalling Link Code for this link.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..254) · OCTET STRING · hint 255t

A textual description for this link.

INTEGER1 = available2 = failed3 = shutdown4 = unavailable · Integer32

The list of possible links states. 'available' : Traffic may flow over this linkset 'failed' : Traffic management has detected a failure that prevents activating this linkset. 'shutdown' : This linkset has been forced to an unavailable state by an administrative action. 'unavailable': The linkset is currently unable to support traffic. Activation of this linkset will occur as required by protocol.

CItpTcLinkType1 = other2 = serial3 = sctpIp4 = hsl5 = virtualThe link types. 'other' : This link is of some type not listed below. 'serial' : This link is a serial link transporting SS7 traffic. 'sctpIp' : This a SCTP/IP link transporting SS7 traffic. 'hsl' : This link is a high speed link using the ATM protocol for transporting SS7 traffic. 'virtual': This link is virtual link used to connect to instance of signalling point running on the same physical device. The link will be used to send and manage traffic between two signalling acting as a gateway. · Integer32

Reference: For SCTP see RFC 2960.

The link type.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

Reference: RFC1213.txt

If the link type specified by cItpSpLinkType is serial or hsl, this is the ifIndex specified in IF-MIB, otherwise no significance is to be placed on this value.

Integer32 (0..65535)

If the link type specified by cItpSpLinkType is 'sctpIp', this is the association identifier defined in the Stream Control Transmission Protocol(SCTP) MIB. Where value greater than zero indicates a valid association and zero one indicates an invalid association. This value will always be set to zero one when cItpSpLinkType is not equal to the 'sctpIp' value.

Counter32 · packets

The number of MTP3 packets received by this link. This measurement is specified in Q752/3.5

Counter32 · packets

The number of MTP3 packets sent by this link. This measurement is specified in Q752/3.3

Counter32 · bytes

The number of MTP3 bytes received by this link. This measurement is specified in Q752/3.4

Counter32 · bytes

The number of MTP3 bytes sent by this link. This measurement is specified in Q752/3.1

CItpTcTimerMtp2T01Alignment ready timer. The default and valid range is dependant on the value of variant. Min Max Def ------ ------ ------ ANSI 12500 16000 13000 ITU 40000 50000 40000 The SYNTAX statement allows values for both the ANSI, ITU variants and MTP2 Peer-to-Peer Adaptation Layer.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (5000..150000) · Unsigned32 · milliseconds

Alignment ready timer.

CItpTcTimerMtp2T02Not aligned timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 5000 14000 11500 ITU 5000 150000 5000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 5000..150000) · Unsigned32 · milliseconds

Not aligned timer.

CItpTcTimerMtp2T03Aligned timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 5000 14000 11500 ITU 1000 2000 1500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 1000..14000) · Unsigned32 · milliseconds

Aligned timer.

CItpTcTimerMtp2T04EProving period timer emergency timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 540 660 600 ITU 400 600 500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 400..660) · Unsigned32 · milliseconds

Proving period timer emergency timer.

CItpTcTimerMtp2T04NProving period timer normal timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 2007 2530 2300 ITU 7500 9500 8200 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 2007..9500) · Unsigned32 · milliseconds

Proving period timer normal timer.

CItpTcTimerMtp2T05Sending SIB timer. The default and valid range is dependant on the value of variant. This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 80 120 80 ITU 80 120 100 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 80..120) · Unsigned32 · milliseconds

Sending SIB timer.

CItpTcTimerMtp2T06Remote congestion timer. The default and valid range is dependant on the value of variant. Min Max Def ------ ------ ------ ANSI 1000 6000 1000 ITU 3000 6000 3000 The SYNTAX statement allows values for both the ANSI, ITU variants and MTP2 Peer-to-Peer Adaptation Layer.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..6000) · Unsigned32 · milliseconds

Remote congestion timer.

CItpTcTimerMtp2T07Excessive delay of acknowledgement timer. The default and valid range is dependant on the value of variant(). This timer is only applicable if cItpTcLinkType is serial. A get on this object will return a zero if the link is not serial. Min Max Def ------ ------ ------ ANSI 500 2000 1000 ITU 500 2000 1000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.703 Signalling Link. ANSI T1.111.3 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 100..6000) · Unsigned32 · milliseconds

Excessive delay of acknowledgement timer.

CItpTcTimerMtp3T01Delay to avoid message mis-sequencing on changeover. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Delay to avoid message mis-sequencing on changeover.

CItpTcTimerMtp3T02Waiting for changeover acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 700 2000 1400 ITU 700 2000 1400 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (700..2000) · Unsigned32 · milliseconds

Waiting for changeover acknowledgement.

CItpTcTimerMtp3T03Time controlled diversion-delay to avoid mis-sequencing on change back. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Time controlled diversion-delay to avoid mis-sequencing on change back.

CItpTcTimerMtp3T04Waiting for change back acknowledgement (first attempt). Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Waiting for change back acknowledgement (first attempt).

CItpTcTimerMtp3T05Waiting for change back acknowledgement (second attempt). Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Waiting for change back acknowledgement (second attempt).

CItpTcTimerMtp3T06Delay to avoid message mis-sequencing on controlled rerouting. Ranges by variant. Min Max Def ------ ------ ------ ANSI 500 1200 800 ITU 500 1200 800 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..1200) · Unsigned32 · milliseconds

Delay to avoid message mis-sequencing on controlled rerouting.

CItpTcTimerMtp3T07Waiting for Signalling data link connection acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 1000 2000 1500 ITU 1000 2000 1500 The SYNTAX statement allows values for both the ANSI and ITU variants. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 1000..2000) · Unsigned32 · milliseconds

Waiting for Signalling data link connection acknowledgement.

CItpTcTimerMtp3T08Transfer prohibited inhibition timer (transient solution). Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1200 1000 ITU 800 1200 1000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1200) · Unsigned32 · milliseconds

Transfer prohibited inhibition timer (transient solution).

CItpTcTimerMtp3T10Waiting to repeat Signalling routeset test message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 60000 45000 ITU 30000 60000 45000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (30000..60000) · Unsigned32 · milliseconds

Waiting to repeat Signalling routeset test message.

CItpTcTimerMtp3T11Transfer restricted timer. (This is one way of implementing the function described in 13.4/Q.704 and mainly intended to simplify SPs.). Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 90000 60000 ITU 30000 90000 60000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (30000..90000) · Unsigned32 · milliseconds

Transfer restricted timer. (This is one way of implementing the function described in 13.4/Q.704 and mainly intended to simplify SPs.).

CItpTcTimerMtp3T12Waiting for uninhibit acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Waiting for uninhibit acknowledgement.

CItpTcTimerMtp3T13Waiting for force uninhibit. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Waiting for force uninhibit.

CItpTcTimerMtp3T14Waiting for inhibition acknowledgement. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 3000 2500 ITU 2000 3000 2500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (2000..3000) · Unsigned32 · milliseconds

Waiting for inhibition acknowledgement.

CItpTcTimerMtp3T15Waiting to start Signalling routeset congestion test. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 3000 2500 ITU 2000 3000 2500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (2000..3000) · Unsigned32 · milliseconds

Waiting to start Signalling routeset congestion test.

CItpTcTimerMtp3T16Waiting for routeset congestion status update. Ranges by variant. Min Max Def ------ ------ ------ ANSI 1400 2000 1700 ITU 1400 2000 1700 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1400..2000) · Unsigned32 · milliseconds

Waiting for routeset congestion status update.

CItpTcTimerMtp3T17Delay to avoid oscillation of initial alignment failure and link restart. Ranges by variant. Min Max Def ------ ------ ------ ANSI 800 1500 1150 ITU 800 1500 1150 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (800..1500) · Unsigned32 · milliseconds

Delay to avoid oscillation of initial alignment failure and link restart.

CItpTcTimerMtp3T18This timers servers different function based on the variant. ANSI: Repeat TFR once by response method ITU: MTP restart link supervision Min Max Def ------ ------ ------ ANSI 2000 20000 11000 ITU 1000 31000 30000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..31000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: Repeat TFR once by response method ITU: MTP restart link supervision

CItpTcTimerMtp3T19This timers servers different function based on the variant. ANSI: failed craft timer referral timer ITU: supervision timer during MTP restart Min Max Def ------ ------ ------ ANSI 480000 600000 540000 ITU 67000 69000 68000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (67000..600000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: failed craft timer referral timer ITU: supervision timer during MTP restart

CItpTcTimerMtp3T20This timers servers different function based on the variant. ANSI: waiting to repeat local inhibit test ITU: MTP restart timer at the Signalling point Min Max Def ------ ------ ------ ANSI 90000 120000 105000 ITU 1000 61000 60000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (1000..120000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: waiting to repeat local inhibit test ITU: MTP restart timer at the Signalling point

CItpTcTimerMtp3T21This timers servers different function based on the variant. ANSI: waiting to repeat remote inhibit test) ITU: MTP restart timer at adjacent Signalling point Min Max Def ------ ------ ------ ANSI 90000 120000 105000 ITU 63000 65000 64000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (63000..120000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: waiting to repeat remote inhibit test) ITU: MTP restart timer at adjacent Signalling point

CItpTcTimerMtp3T22This timers servers different function based on the variant. ANSI: restarting SP waiting for Signalling links avail ITU: local inhibit test timer Min Max Def ------ ------ ------ ANSI 36000 60000 30000 ITU 80000 360000 300000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (36000..360000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting for Signalling links avail ITU: local inhibit test timer

CItpTcTimerMtp3T23This timers servers different function based on the variant. ANSI: restarting SP waiting to receive all TRA msgs ITU: remote inhibit test timer Min Max Def ------ ------ ------ ANSI 9000 60000 30000 ITU 80000 360000 300000 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (9000..360000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting to receive all TRA msgs ITU: remote inhibit test timer

CItpTcTimerMtp3T24This timers servers different function based on the variant. ANSI: restarting SP waiting to broadcast all TRA msgs ITU: stabilizing timer after local processor outage Min Max Def ------ ------ ------ ANSI 9000 60000 30000 ITU 500 500 500 The SYNTAX statement allows values for both the ANSI and ITU variants.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (500..60000) · Unsigned32 · milliseconds

This timers servers different function based on the variant. ANSI: restarting SP waiting to broadcast all TRA msgs ITU: stabilizing timer after local processor outage

CItpTcTimerMtp3T25Timer at Signalling Point (SP) adjacent to restarting SP, waiting for traffic restart allowed message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 35000 30000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 30000..35000) · Unsigned32 · milliseconds

Timer at Signalling Point (SP) adjacent to restarting SP, waiting for traffic restart allowed message.

CItpTcTimerMtp3T26Timer at restarting SP waiting to repeat traffic restart waiting message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 12000 15000 12000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 12000..15000) · Unsigned32 · milliseconds

Timer at restarting SP waiting to repeat traffic restart waiting message.

CItpTcTimerMtp3T27Minimum duration of unavailability for full restart. Ranges by variant. Min Max Def ------ ------ ------ ANSI 2000 50000 4000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 2000..50000) · Unsigned32 · milliseconds

Minimum duration of unavailability for full restart.

CItpTcTimerMtp3T28Timer at SP adjacent to restarting SP waiting for traffic restart waiting message. Ranges by variant. Min Max Def ------ ------ ------ ANSI 3000 35000 30000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 3000..35000) · Unsigned32 · milliseconds

Timer at SP adjacent to restarting SP waiting for traffic restart waiting message.

CItpTcTimerMtp3T29Timer started when TRA sent in response to unexpected TRA or TRW. Ranges by variant. Min Max Def ------ ------ ------ ANSI 60000 65000 63000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 60000..65000) · Unsigned32 · milliseconds

Timer started when TRA sent in response to unexpected TRA or TRW.

CItpTcTimerMtp3T30Timer to limit sending of TFPs and TFRs in response to unexpected TRA or TRW. Ranges by variant. Min Max Def ------ ------ ------ ANSI 30000 35000 33000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 30000..35000) · Unsigned32 · milliseconds

Timer to limit sending of TFPs and TFRs in response to unexpected TRA or TRW.

CItpTcTimerMtp3T31False link congestion detection timer. Ranges by variant. Min Max Def ------ ------ ------ ANSI 10000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 10000..120000) · Unsigned32 · milliseconds

False link congestion detection timer.

CItpTcTimerMtp3T32Link oscillation timer - Procedure A. Ranges by variant. Min Max Def ------ ------ ------ ANSI 5000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 5000..120000) · Unsigned32 · milliseconds

Link oscillation timer - Procedure A.

CItpTcTimerMtp3T33Probation timer for link oscillation - Procedure B. Ranges by variant. Min Max Def ------ ------ ------ ANSI 60000 600000 300000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 60000..600000) · Unsigned32 · milliseconds

Probation timer for link oscillation - Procedure B.

CItpTcTimerMtp3T34Suspension timer for link oscillation - Procedure B. Ranges by variant. Min Max Def ------ ------ ------ ANSI 5000 120000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP) (0 | 5000..120000) · Unsigned32 · milliseconds

Suspension timer for link oscillation - Procedure B.

CItpTcTimerLinkTestSignalling Link test acknowledgement timer. Min Max Def ------ ------ ------ ANSI 4000 12000 8000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 4000..12000) · Unsigned32 · milliseconds

Signalling Link test acknowledgement timer.

CItpTcTimerLinkMessageInterval timer for sending test messages. Min Max Def ------ ------ ------ ANSI 30000 90000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 30000..90000) · Unsigned32 · milliseconds

Interval timer for sending test messages.

CItpTcTimerLinkActRetryLink activation retry timer. Min Max Def ------ ------ ------ ANSI 60000 90000 60000 This timer is not used when the variant is ITU. A value of zero indicates a value is not defined for a particular variant or is not supported by the implementation.Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Message Transfer Part (MTP). (0 | 60000..90000) · Unsigned32 · milliseconds

Link activation retry timer.

Gauge32

Number of packets waiting to be sent over this link.

Unsigned32

This is the maximum number of packets waiting to be sent over this link since the last time this value was reset as indicated by cItpSpLinkXmitQueueDepthHighReset. Resetting this object is achieved by setting this object to 0. Attempting to set this object to any other value will result in a wrongValue error.

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 indicates when cItpSpLinkXmitQueueDepthHigh was set to 0.

Unsigned32 (0..3)

Reference: ITU Q.704 Signalling network functions and messages. ANSI T1.111 Telecommunications - Signalling system No. 7 (SS7)-Signalling network functions and messages 2.3.5.2.

The Signalling link congestion status of this link. 0 is the least congestion level, 3 is the highest congestion level.

Unsigned32 (0..65535)

Threshold used to abate congestion level 1.

Unsigned32 (0..65535)

Threshold used to abate congestion level 2.

Unsigned32 (0..65535)

Threshold used to abate congestion level 3.

Unsigned32 (0..65535)

Threshold used to mark onset of congestion level 1.

Unsigned32 (0..65535)

Threshold used to mark onset of congestion level 2.

Unsigned32 (0..65535)

Threshold used to mark onset of congestion level 3.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Indicated if Signalling link test is enabled on this link. true : Signalling link test is enabled. false : Signalling link test not enabled.

TimeTicks

Duration of link in the In-Service state Q752/1.1.

Counter32

Count of Signalling Link failures - All reasons Q752/1.2.

Counter32 · occurrences

Count of Signalling Link failures - Abnormal FIBR/BSNR Q752/1.3.

Counter32 · occurrences

Count of Signalling Link failures - Excessive delay of acknowledgement Q752/1.4.

Counter32 · occurrences

Count of Signalling Link failures - Excessive error rate Q752/1.5.

Counter32 · occurrences

Count of Signalling Link failures - Excessive duration of congestion Q752/1.6.

Counter32 · occurrences

Count of alignment or proving errors Q752/1.7.

Counter32 · occurrences

Count of signal units received in error Q752/1.8.

Counter32 · negative acknowledgements

Count of negative acknowledgements received Q752/1.9.

Counter32 · occurrences

Count of 'local automatic changeover' events Q752/1.10.

Counter32 · occurrences

Count of 'local automatic changeback' events Q752/1.11.

TimeTicks

Duration of Signalling Link unavailable(for any reason) Q752/2.1.

TimeTicks

Duration of Signalling Link unavailable due to local management actions Q752/2.5.

TimeTicks

Duration of Signalling Link unavailable due to remote management actions Q752/2.6.

TimeTicks

Duration of Signalling Link unavailable due to link failure Q752/2.7.

TimeTicks

Duration of Signalling Link unavailable due to remote processor outage Q752/2.9.

Counter32 · occurrences

Count of 'remote processor outage' events Q752/2.10 and Q752/2.11. The standard only requires that events are issued. The entries have been combined into a single entry to track all occurrences of these event types.

TimeTicks

Duration of local busy Q752/2.15.

Counter32 · occurrences

Count of local inhibition Q752/2.16 and Q752/2.17. The standard only requires that events are issued. The entries have been combined into a single entry to track all occurrences of these event types.

Counter32 · occurrences

Count of remote inhibition Q752/2.18 and Q752/2.19. The standard only requires that events are issued. The entries have been combined into a single entry to track all occurrences of these event types.

Counter32 · packets

The number of MTP3 packets retransmitted on this link. This measurement is specified in Q752/3.2

Counter32 · bytes

The number of MTP3 bytes retransmitted on this link. This measurement is specified in Q752/3.2

Counter32 · events

The number times this Signalling link was marked congested. This measurement is specified in Q752/3.6

TimeTicks

Cumulative duration of Signalling link congestion Q752/3.7.

Counter32 · Packets

The number of packets(MSUs) discarded due to Signalling link level 1 congestion Q752/3.10

Counter32 · Packets

The number of packets(MSUs) discard due to Signalling link level 2 congestion Q752/3.10

Counter32 · Packets

The number of packets(MSUs) discard due to Signalling link level 3 congestion Q752/3.10

Counter32 · bytes

The number times this Signalling link entered congestion level 1 and packets were discarded. This measurement is specified in Q752/3.11

Counter32 · bytes

The number times this Signalling link entered congestion level 2 and packets were discarded. This measurement is specified in Q752/3.11

Counter32 · bytes

The number times this Signalling link entered congestion level 3 and packets were discarded. This measurement is specified in Q752/3.11

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

When cItpSpLinkType is set to sctpIp then this object contains the type of the first of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

When cItpSpLinkType is set to sctpIp then this object contains the type of the second of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

When cItpSpLinkType is set to sctpIp then this object contains the type of the third of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32

When cItpSpLinkType is set to sctpIp then this object contains the type of the fourth of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

When cItpSpLinkType is set to sctpIp then this object contains the first of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

When cItpSpLinkType is set to sctpIp then this object contains the second of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

When cItpSpLinkType is set to sctpIp then this object contains the third of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING

When cItpSpLinkType is set to sctpIp then this object contains the fourth of four possible local IP addresses used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

Unsigned32 (0..65535)

When cItpSpLinkType is set to sctpIp then this object contains the local port number used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

Unsigned32 (0..65535)

When cItpSpLinkType is set to sctpIp then this object contains the remote port number used to create the association supporting this link. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

CItpTcQosThe quality of service classification to be assigned to the IP packets used to transport the SS7 messages. The value can be from one to seven when selecting a Qos class or 255 to indicate the packet will not be assigned a Qos class. This value will be set to zero when cItpSpLinkType indicates that Quality of Service does not apply to this link. (0..7 | 255) · Unsigned32

When cItpSpLinkType is set to sctpIp then this object contains the quality of service class to be assigned to packets sent on this association. When cItpSpLinkType is not set to sctpIp then no significance is to be placed on this value.

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 object is used by a management station to create or delete the row entry in cItpSpLinkTable following the RowStatus textual convention.

BITS

This object provides additional information on the state of a link as follows. 'localInhibit' : Link has been inhibited by a local management operation. 'remoteInhibit' : LInk has been inhibited by a remote management operation. 'blocked' : Link is blocked because of a remote processor outage.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..30) · OCTET STRING · hint 255t

A short identifier for each link linkset. This value can be set by system administrator or defaults to the linkset name and SLC formatted as an ASCII string.

Counter32 · packets

The number of packets that were dropped by this link.

Counter32 · LSSU

The number of Link Status Signal Units sent on this link.

Counter32 · LSSU

The number of Link Status Signal Units received on this link.

BITS

This object provide details on the protocol states for this link as follows. Changeback control(TCBC) 'tcbcBuffering': Changeback control is buffering data on this link. Changeover control(TCOC) 'tcocBuffering': Changeover control is buffering data on this link Link availability control(TLAC) 'tlacAdjacentSpRestarting': Adjacent Signalling point is restarting. 'tlacEmergencyCoInProgress': Emergency changeover is in progress on this link. 'tlacChangebackInProgress': Changeback is in progress on this link. 'tlacChangeoverInProgress': Changeover is in progress on this link. 'tlacChangeoverFailed': The last changeover operation failed on this link. 'tlacInhibitRetry': Inhibit command will be retried. 'tlacManagementRequest': Management request in progress for this link. 'tlacSpRestarting': Signalling point is in the process of a restart. Signalling routing control(TSRC) 'tsrcChangeOverComplete': Changeove request is complete. 'tsrcAdjacentSpRestart': Adjacent Signalling Point is restarting.

INTEGER1 = undefined2 = inactive3 = active4 = activatingRestoring5 = failed6 = actT17wait7 = actAnsiWaitDeloaded8 = actItuWaitStmReady · Integer32

Reference: Figure 37/Q.704 - Signalling link management; Signalling link activity control (LSAC)

Signalling link activity control state: 'undefined(1)' - link is an undefined state 'inactive(2)' - A Signalling link that is not in operation. 'active(3)' - A Signalling link that is in operation. 'activatingRestoring(4)' - A Signalling that is not operational and is being activated or restored. 'failed(5)' - A Signalling link which is available (not blocked) is marked by level 3 as failed when a changeover order is received. 'actT17wait(6)' - Link activation has failed. Link is placed into this state to wait for timer T17 to expire in order to avoid the oscillation of initial alignment failure and link restart. 'actAnsiWaitDeloaded(7) - Waiting for change back acknowledgement (second attempt). 'actItuWaitStmReady(8)' Wait for Signalling Traffic Management ready event.

INTEGER1 = undefined2 = idle3 = wait5 · Integer32

Reference: Figure 29/Q.704 - Signalling traffic management; Signalling routing control (TSRC)

Signalling traffic management routing control state: 'undefined(1)' - link is an undefined state 'idle(2)' - traffic mangement is idle 'wait5(3)' - traffic management is active and in the sending status phase

INTEGER1 = undefined2 = idle3 = wait24 = waitForAck5 = retrieving6 = wait57 = wait78 = wait8 · Integer32

Reference: Figure 30/Q.704 - Signalling traffic management; changeover control (TCOC)

Changeover control State: 'undefined(1)' - Link is an undefined state. 'idle(2)' - Link is available and idle. 'wait2(3)' - Wait for MTP2 to initialize link. 'waitForAck(4)' - Waiting for changeover acknowledgement. 'retrieving(5)' - Packets are being retrieved from link. 'wait5(6)' - Wait state when transitioning from idle state. 'wait7(7)' - Delay to avoid message mis-sequencing on changeover 'wait8(8)' - Wait state prior to processing changeover order or emergency changeover order events.

CItpSpSequenceNumberThis textual convention defines all of the allowed values for a sequence of integers used by the SS7 protocol to transmit and acknowledge packets. The range is specified from 0 to maximum allowed value for extended sequence numbers. The actual range will depend on the type of link and the variant. The value will increase and then wrap to the zero value. The following are examples of valid sequences. 0..126,127,0.. 0..254,255,0.. 0..32766,32767,0.. 0..65534,65535,0.. (0..65535) · Unsigned32

The local backward sequence number to be transmitted.

CItpSpSequenceNumberThis textual convention defines all of the allowed values for a sequence of integers used by the SS7 protocol to transmit and acknowledge packets. The range is specified from 0 to maximum allowed value for extended sequence numbers. The actual range will depend on the type of link and the variant. The value will increase and then wrap to the zero value. The following are examples of valid sequences. 0..126,127,0.. 0..254,255,0.. 0..32766,32767,0.. 0..65534,65535,0.. (0..65535) · Unsigned32

The remote backward sequence number to be transmitted.

INTEGER1 = undefined2 = idle3 = firstAttempt4 = secondAttempt5 = timeControlledDiversion · Integer32

Changeback control State: 'undefined(1)' - link is an undefined state. 'idle(2)' - Link is available and idle. 'firstAttempt(3)' - First attempt at changeback. 'secondAttempt(4)' - Second attempt at changeback 'timeControlledDiversion(5)' - Changeback using time controlled Diversion.

Counter32 · SIB

The number of status indicator 'busy' link status signal units received on this link. The SIB indicates that level two is congested at the transmitting Signalling point.

Counter32 · SIB

The number of status indicator 'busy' link status signal units transmitted on this link. The SIB indicates that level two is congested at the transmitting Signalling point.

Counter32

The number of times the alignment ready timer has expired on this link.

Counter32

The number of times the not alignment ready timer has expired on this link.

Counter32

The number of times the aligned timer has expired on this link.

Counter32

The number of times the proving period timer has expired on this link.

Counter32

The number of times the sending status indicator busy timer has expired on this link.

Counter32

The number of times the remote congestion timer has expired on this link.

Counter32

The number of times the excessive delay of acknowledgement timer has expired on this link.

Counter32

The number of times the Alignment Error Rate Monitor procedure was started on this link.

Counter32

The number of times the Alignment Error Rate Monitor procedure failed on this link.

Counter32

The number of times the Signal Unit Error Rate Monitor procedure was started on this link.

Counter32

The number of times the Signal Unit Error Rate Monitor procedure failed on this link.

CItpSpLinkCapacityThis textual convention defines the planned capacity of a SS7 link in bit per second. If the link type is serial or HSL the link capacity can be obtained from information in the IF-MIB. If the link type is sctp/ip a value of zero indicates that link utilization should not be calculated for this SS7 link. (0 | 56000..2147483647) · Unsigned32 · bits per second

An estimate of the number of bits per second that is expected to be received from this link. This object will be used in combination with cItpSpUtilSampleInterval, cItpSpUtilThreshold, cItpSpUtilThreshold and cItpSpLinkUtilThresholdRcvd to generate the cItpSpLinkRcvdUtilChange notification.

CItpSpPercentThresholdThis textual convention defines the allowed values for a thresholds specified as percentage of link utilization. A value of zero indicates that this specific threshold is to be ignored. (0..100) · Unsigned32 · percent

This object specifies the threshold used to to generate the cItpSpLinkRcvdUtilChange notification. The value of zero indicates the threshold has not been defined at the link level and the value from the cItpSpUtilThreshold object will be used to generate the cItpSpLinkRcvdUtilChange notification.

CItpSpLinkUtilizationThis textual convention defines a range of percentages that represent the utilization of a link. Any value over 999 will be represented as 999. For SS7 links based on IP/SCTP the link capacity is not directly related to the interface speed used to transmit packets. This is different from serial and HSL links. The capacity of these types of links depend on the amount of resources available in the IP cloud. The IP cloud must be provisioned to support traffic for all SS7 links. In order to monitor link utilization on IP/SCTP based SS7 links a planned capacity must be specified. If this value is incorrectly estimated or traffic exceeds this expected value link utilization may exceed 100 percent. This is possible because the IP cloud may be provisioned with additional capacity or may discard less important traffic based on Qos parameters. When a SS7 link has not be configured for link utilization monitoring this value object will have a value of zero. (0..999) · Unsigned32 · percent

An estimate of the utilization of this link for traffic received on this link in the prior time period defined by the cItpSpUtilSampleInterval object.

CItpSpLinkUtilizationState0 = unMonitored1 = underThreshold2 = overThresholdLink Utilization State as follows: 'unMonitored(0)' - traffic for a specified direction is not being monitored. 'underThreshold(1)' - traffic for a specified direction on a link is below the specified threshold. 'overThreshold(2)' - traffic for a specified direction on a link is above to or exceeds the specified threshold. · Integer32

Link Utilization State for in bound traffic.

Counter32

A count of the bytes received on the link including the additional bytes required by underlying protocols. This provides a transport independent mechanism for collection information on link utilization.

CItpSpLinkCapacityThis textual convention defines the planned capacity of a SS7 link in bit per second. If the link type is serial or HSL the link capacity can be obtained from information in the IF-MIB. If the link type is sctp/ip a value of zero indicates that link utilization should not be calculated for this SS7 link. (0 | 56000..2147483647) · Unsigned32 · bits per second

An estimate of the number of bits per second that is expected to be sent on this link. This object will be used in combination with cItpSpUtilSampleInterval, cItpSpUtilThreshold and cItpSpLinkUtilThresholdRcvd to generate the cItpSpLinkSentUtilChange notification.

CItpSpPercentThresholdThis textual convention defines the allowed values for a thresholds specified as percentage of link utilization. A value of zero indicates that this specific threshold is to be ignored. (0..100) · Unsigned32 · percent

This object specifies the threshold used to generate the cItpSpLinkRcvdUtilChange notification. The value of zero indicates the threshold has not been defined at the link level and the value from the cItpSpUtilThreshold object will be used to generate the cItpSpLinkRcvdUtilChange notification.

CItpSpLinkUtilizationThis textual convention defines a range of percentages that represent the utilization of a link. Any value over 999 will be represented as 999. For SS7 links based on IP/SCTP the link capacity is not directly related to the interface speed used to transmit packets. This is different from serial and HSL links. The capacity of these types of links depend on the amount of resources available in the IP cloud. The IP cloud must be provisioned to support traffic for all SS7 links. In order to monitor link utilization on IP/SCTP based SS7 links a planned capacity must be specified. If this value is incorrectly estimated or traffic exceeds this expected value link utilization may exceed 100 percent. This is possible because the IP cloud may be provisioned with additional capacity or may discard less important traffic based on Qos parameters. When a SS7 link has not be configured for link utilization monitoring this value object will have a value of zero. (0..999) · Unsigned32 · percent

An estimate of the utilization of this link for traffic sent on this link in the prior time period defined by the cItpSpUtilSampleInterval object.

CItpSpLinkUtilizationState0 = unMonitored1 = underThreshold2 = overThresholdLink Utilization State as follows: 'unMonitored(0)' - traffic for a specified direction is not being monitored. 'underThreshold(1)' - traffic for a specified direction on a link is below the specified threshold. 'overThreshold(2)' - traffic for a specified direction on a link is above to or exceeds the specified threshold. · Integer32

Link Utilization State for out bound traffic.

Counter32

A count of the bytes sent on the link including the additional bytes required by underlying protocols. This provides a transport independent mechanism for collection information on link utilization.