CISCO-ITP-DSMR-MIB

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

The value of sysUpTime at the time of the last creation or deletion of an entry in the Multi-Layer configurations defined for this signalling point. If the local network management subsystem is re-initialized, then this object contains the sysUpTime at the time when this occurred. This value can be used to prevent unnecessary walks of the various tables supporting Distributed Short Message Routing.

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

The value of sysUpTime at the time of the last load of a file supporting Distributed Short Message Routing for this signalling point.

CItpTcTableLoadStatus1 = loadNotRequested2 = loadInProgress3 = loadComplete4 = loadCompleteWithErrors5 = loadFailedThe status of the current or prior load operation. 'loadNotRequested' : load operations have not been requested. 'loadInProgress' : load request is active. 'loadComplete' : load request complete without errors. 'loadCompleteWithErrors' : Load request completed with some type of errors that prevented the adding of one or more entries. 'loadFailed' : Load request failed. · Integer32

The status of the current load or status from the prior load operation. This object will have a value of loadInProgress while the load operation is in progress. The cdsmrInstLastLoadTime contains a timestamp indicating when the load operation is completed.

CItpTcURLThe URL used to load a configuration file. 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 (0..255) · OCTET STRING

The last URL used to load a file used to configure Distributed Short Message Routing.

Counter32 · packets

Count of the number of times a packet was routed using Short Message Peer-to-Peer protocol.

Counter32 · packets

Count of the number of times a packet was routed using Universal Computer Protocol(UCP).

Counter32 · packets

Count of the number of times a GSM packet was delivered.

Counter32 · packets

Count of the number of times a GSM packet was deferred.

Counter32 · packets

Count of the number GSM status reports issued by device.

Counter32 · packets

Count of the number UCP notifications issued by device.

Counter32 · packets

Count of the number SMPP delivery receipts issued by device.

Counter32 · packets

Count of the number of times a packet could not be delivered because route was not configured.

Counter32 · packets

Count of the number of times processing of packet did not produce valid result.

Counter32 · packets

Count of the number of times processing of packet was not completed due to internal error.

Counter32 · packets

Count of the number of times processing of packet was not completed due to parsing error.

Counter32 · packets

Count of the number of times processing of packet was not completed due to unavailable resources on device.

Counter32 · packets

Count of the number of times processing of packet was not completed due to provisioning errors on device.

Counter32 · packets

Count of the number of times packet was not routed because destination was unreachable.

Counter32 · packets

Count of the number of times packet was not routed because destination had signal error.

Counter32 · packets

Count of the number of times packet was not delivered due to timeout.

Counter32 · packets

Count of the number of times packets were blocked by processing.

Counter32 · packets

Count of the number of routing requests received were traffic was GSM based.

Counter32 · packets

Count of the number of routing requests received were traffic was IS-41 based.

Counter32 · packets

Count of the number of routing requests received were traffic was UCP based.

Counter32 · packets

Count of the number of routing requests received were traffic was SMPP based.

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 cdsmrInstTable following the RowStatus textual convention.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

A name used to define a result group.

INTEGER1 = esme2 = smsc · Integer32

This object specifies the server type as follows. 'esme' - Indicates this result group represents an external short message entity (ESME). Coding this parameter will allow the user to enter ESME specific parameters and enable the Distributed Short Message Routing to properly characterize the routing of the message. 'smsc' - Indicates this result group represents a short message service center (SMSC). Coding this parameter will allow the user to enter SMSC specific parameters and enable the Distributed Short Message Routing to properly characterize the routing of the message.

OCTET STRING SIZE (0..5)

The object provides a one to five ASCII characters ESME (large account) consolidation string. This object only applies when the cdsmrResultGroupServerType object specifies ESME. The object returns the null string when not specified.

Unsigned32 (0 | 100..9999)

The object provides a ESME (large account) identifier. This object only applies when the cdsmrResultGroupServerType object specifies ESME. The zero value is usedt to indicate that the object has not been specified.

Unsigned32 (0..100000)

This object defines the maximum number of elements on outbound queue for any destination. The value of 0 indicates that there is no limit on the number of entries.

Unsigned32 · milliseconds

Maximum time element can exist in outbound queue.

OCTET STRING SIZE (0..15)

When specified this object provides 1 to 15 character ESME system identifier. This object only applies when the cdsmrResultGroupServerType object specifies ESME.

OCTET STRING SIZE (0..12)

When specified this object provides 1 to 12 character ESME system type. This object only applies when the cdsmrResultGroupServerType object specifies ESME. When this object is not specified it will return the null sting.

OCTET STRING SIZE (0..16)

The object provides 1 to 16 character ESME ESME UCP address code. This object only applies when the cdsmrResultGroupServerType object specifies ESME.

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 cdsmrResultGroupTable following the RowStatus textual convention.

CmlrIdA numeric identifier used to specify an entry in a list. Zero is a special value used to indicate no entry. (0..65535) · Unsigned32

This object specifies the index for a list of results specified per result group.

InetPortNumberRepresents a 16 bit port number of an Internet transport layer protocol. Port numbers are assigned by IANA. A current list of all assignments is available from <http://www.iana.org/>. The value zero is object-specific and must be defined as part of the description of any object that uses this syntax. Examples of the usage of zero might include situations where a port number is unknown, or when the value zero is used as a wildcard in a filter.Reference: STD 6 (RFC 768), STD 7 (RFC 793) and RFC 2960 (0..65535) · Unsigned32 · hint d

Remote port number used to establish connection. The value of zero indicates that any port number will be accepted.

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

This object contains the type of the remote IP address used to create an session.

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

This object contains the remote IP address allowed to request the session.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the profile used to specify parameter for session as follows. 'smpp': cdsmrSmppProfileName 'ucp': cdsmrUcpProfileName For all other values this object is ignored.

Integer32 (0..10)

This object specifies the weight applied to the weighted round robin distribution algorithm used for multi-layer result group. An integer value in the range of 0 to 10. A value of ten indicates the resource should be selected ten times more than a resource assigned a weight of one.

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 cdsmrResultIpTable following the RowStatus textual convention.

CmlrIdA numeric identifier used to specify an entry in a list. Zero is a special value used to indicate no entry. (0..65535) · Unsigned32

This object specifies the index for a list of results specified per result group.

CdsmrResultDestinationType1 = none2 = gt3 = smpp4 = ucp5 = pc6 = pcSsnList of possible destination types as follows. 'none' : Result not specified. 'gt' : The global title address formatted as CItpTcGtaLongDisplay 'smpp' : Short Message Peer-to-Peer protocol destination. 'ucp' : Universal Computer Protocol destination. 'pc' : Point-code destination. 'pcSsn' : Point-code and subsystem number destination. · Integer32

Destination type.

CdsmrResultParametersIn order to specify the results of DSMR statements different values in the packet can be modified. These values are determined by a combination of variant and operation type. This object indicates which objects will be used to form a result action as follows. This textual convention defines the result actions of DSMR which are determined by a combination of variant and operation type. The possible result actions of DSMR are as follows: 'network' : specifies network 'octet' : specifies octet string 'tranType' : specifies translation type 'gti' : specifies global title indicator 'np' : specifies numbering plan 'nai' : specifies nature of address 'pc' : specifies point-code 'ssn' : specifies subsystem number 'ruleNumber': specifies next rule to execute · BITS

Many of the result parameter used creating result are optional. This object is used to indicate which options are provided as follows. 'tranType' : cdsmrResultTransType 'gti' : cdsmrResultGti 'np' : cdsmrResultNp 'nai' : cdsmrResultNai 'pc' : cdsmrResultPc 'ssn' : cdsmrResultSsn

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the destination as follows based on cdsmrResultDestinationType: 'smpp': cdsmrSmppDestName 'ucp': cdsmrUcpDestName For all other values this object is ignored.

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

A destination point code that must exist in the MTP3 routing table, and its state is extracted from MTP3 for availability purposes. This object only has applies when the cdsmrResultDestinationType object has the 'pc' or 'pcSsn' values. Otherwise, this object will return zero value.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The subsystem number to be inserted into MSU. This object only has applies when the cdsmrResultDestinationType object has the 'pcSsn' value. Otherwise, this object will return zero value.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the CdsmrResultDestinationType is set to 'gt' value.

CgsccpGttTransTypeThe SCCP GTT Translation Type (TT). (0..255) · Unsigned32

The translation type specified within the address in the message signal unit. This object only applies when the CdsmrResultDestinationType is set to 'gt' value and the 'tranType' bit is set in the cdsmrResultResultParameters object.

CgsccpGttGlobalTitleIndThe SCCP GTT Global Title Indicator (GTI). The following values are generally used: No global title included (0), For ITU, GT includes NAI only (1), For ANSI, GT includes TT, NP and encoding scheme (1), GT includes only TT (2), GT includes TT, NP and encoding scheme (3), GT includes TT, NP, encoding scheme, NAI (4), Maximum GTI (15), Invalid GTI (253), Wild GTI (254).Reference: The Global Title Indicator is defined in the International Telecommunication Union standard Q.713: Specifications of Signalling System No. 7 - Signalling Connection Control Part (SCCP) section 3.4.1 Address Indicator. (0..255) · Unsigned32

The global title indicator value for the global tile address specified within the message signal unit. This object only applies when the CdsmrResultDestinationType is set to 'gt' value.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the global tile address specified within the message signal unit. This object only applies when the CdsmrResultDestinationType is set to 'gt' value.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the cdsmrResultDestinationType is set to 'gt' value.

Integer32 (0..10)

This object specifies the weight applied to the weighted round robin distribution algorithm used for multi-layer result group. An integer value in the range of 0 to 10. A value of ten indicates the resource should be selected ten times more than a resource assigned a weight of one.

CItpTcNetworkNameThe network name is used to indicate the network in which this signalling point is participating. One or more instances of signalling points can exist in the same physical device. This identifier will be used to correlate instances of signalling points by network. When multiple instance support is not enable the network name will default to the null string. 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 (0..19) · OCTET STRING

The network name is used to indicate the network in which the result operation will be performed.

Counter32 · matches

Number of times this entry was invoked.

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 cdsmrResultTable following the RowStatus textual convention.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

A name used to define a collection of addresses used to route and modify messages signalling units.

CmlrAddressType1 = bch2 = gsmDaList of possible table types. 'bch' : Binary Coded Hexadecimal 'gsmDa' : GSM 7 bit Default Alphabet · Integer32

The type of addresses in the address tables. The different types will be used to determine how to format and convert cdsmrAddressDigits.

CmlrAddressDigitsThe configured digits of A-address or B-address specified in the format indicated by CmlrAddressType. All values are entered in binary and represent digits All values are encoded as hexidecimal values and represent the following characters by address type are as follows. CmlrAddressType: 'bch' GSM: Encoding Character 0000-1001 0-9 1010 * 1011 # 1100 a 1101 b 1110 c 1111 filler ANSI-41 0000-1001 0-9 1010 Spare 1011 Code 11 1100 Code 12 1101 * 1110 # 1111 ST (or filler) CmlrAddressType: 'gmsDa' |0 0 0 0 1 1 1 1 b7 b b b b |0 0 1 1 0 0 1 1 b6 4 3 2 1 |0 1 0 1 0 1 0 1 b5 ----------------------------------- 0 0 0 0 |@ . SP 0 � P � p 0 0 0 1 |� _ ! 1 A Q a q 0 0 1 0 |$ F DQ 2 B R b r 0 0 1 1 |� G # 3 C S c s 0 1 0 0 |� . � 4 D T d t 0 1 0 1 |� . % 5 E U e u 0 1 1 0 |� . & 6 F V f v 0 1 1 1 |� . ' 7 G W g w 1 0 0 0 |� S ( 8 H X h x 1 0 0 1 |� T ) 9 I Y i y 1 0 1 0 |LF . * : J Z j z 1 0 1 1 |� 1) + ; K � k � 1 1 0 0 |� � , < L � l � 1 1 0 1 |CR � - = M � m � 1 1 1 0 |� � . > N � n . 1 1 1 1 |� � / ? O � o � 'SP' - Space 'LF' - Line Feed 'DQ' - Double quote '.' = Special characters outside standard ASCII See 6.2.1 GSM 7 bit Default Alphabet Table. The string will consists of N Octets were the first n-1 octets represent the hexadecimal address. The last Octet specifies the number of bits used to match the calling address. For example, when CmlrAddressType is Binary Coded Hexadecimal the following entries illustrate why the trailing number of match bits is required. '081000000000000000000C' match '081' '0810000000000000000010' match '0810'Reference: GSM 04.08 Table 10.5.118,ANSI T1.114.5 Figure 8 and ETSI TS 123 038 V5.0.0 (2002-03) SIZE (0..32) · OCTET STRING

The digits of the address in following formats as indicated by cdsmrAddressType object. 'hexadecimal' - The digits are hexadecimal digits specified in ASCII as follows. '0123456789ABCDEF'

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

This object indicates that the address specified by cdsmrAddressDigits object must exactly match value in message signalling unit. 'true' - Exact match is specified. 'false' - Best match is specified.

CdsmrResultParametersIn order to specify the results of DSMR statements different values in the packet can be modified. These values are determined by a combination of variant and operation type. This object indicates which objects will be used to form a result action as follows. This textual convention defines the result actions of DSMR which are determined by a combination of variant and operation type. The possible result actions of DSMR are as follows: 'network' : specifies network 'octet' : specifies octet string 'tranType' : specifies translation type 'gti' : specifies global title indicator 'np' : specifies numbering plan 'nai' : specifies nature of address 'pc' : specifies point-code 'ssn' : specifies subsystem number 'ruleNumber': specifies next rule to execute · BITS

Many of the result parameter used in the processing of address table have default values. These values are determined by a combination of variant and operation type. This object will be provide information which parameter used in setting results have been specified as follows. 'network' : cdsmrAddressSetResultNetwork 'octet' : cdsmrAddressSetResultOctet 'tranType' : cdsmrAddressResultTransType 'gti' : cdsmrAddressResultGti 'np' : cdsmrAddressResultNp 'nai' : cdsmrAddressResultNai 'pc' : cdsmrAddressResultPc 'ssn' : cdsmrAddressResultSsn

CItpTcNetworkNameThe network name is used to indicate the network in which this signalling point is participating. One or more instances of signalling points can exist in the same physical device. This identifier will be used to correlate instances of signalling points by network. When multiple instance support is not enable the network name will default to the null string. 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 (0..19) · OCTET STRING

The network name is used to indicate the network in which the result operation will be performed.

CdsmrResultType0 = none1 = pc2 = pcSsn3 = gt4 = group5 = smpp6 = ucp7 = block8 = ruleNext9 = ruleNumber10 = deliverMt11 = origImsi12 = origImsiNextThis textual convention defines the result type of DSMR. The possible result types are as follows: 'none' : Result not specified. 'block' : Message will be discarded. 'pc' : Message will be routed using the specified destination point code. 'pcSsn' : Message will be routed using the specified destination point code and subsystem number. destination M3UA or SUA Application Server(AS). 'gt' : Message will be routed using SCCP global title. 'group' : Message will be routed using information specified in result group. 'smpp' : Delivery via Short Message Peer-to-Peer 'ucp' : Delivery via Universal Computer Protocol 'ruleNext' : When address matches entry in table processing will continue with next rule. 'ruleNumber' : When address matches entry in table processing will continue with specified rule. 'deliverMt': Indicates that a delivery attempt should be attempted to the destination SME as a mobile device. 'origImsi': Attempt to obtain the original IMSI address and us it to delivery packet. When the IMSI address is unavailable fail packet. 'origImsiNext': Attempt to obtain the original IMSI address and us it to delivery packet. When the IMSI address is unavailable continue processing with next rule. · Integer32

Specified the type of information to be placed into the message signal unit or how the it will be processed.

CdsmrResultOctetAn octet string that contains various types of output from a rule. The information in this textual convention is formatted as follows: CdsmrResultType: None : Octet string with length of zero. pc : Not applicable pcSsn : Not applicable. gt : The global title address formatted as CItpTcGtaLongDisplay group : Result group formatted as CmlrName. smpp : Result group formatted as CmlrName ucp : Result group formatted as CmlrName block : Not applicable. ruleNext : Not applicable. ruleNumber: Not applicable. deliveryMt: Not applicable. origImsi : Not Applicable origImsiNext: Not Applicable When the result octet is not used as a parameter, not applicable, the length will be set to zero. 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 (0..64) · OCTET STRING

Information to be placed in the message signal unit based on the value specified by the cdsmrAddressResultType object. When the cdsmrAddressResultType object is set to 'group' or 'gt' this object will contain the string specifying output. For all other values the this object will not be used in the result processing and will have a length of zero.

CgsccpGttTransTypeThe SCCP GTT Translation Type (TT). (0..255) · Unsigned32

The translation type specified within the address in the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'gt' value and the 'tranType' bit is set in the cdsmrAddressResultParameters object.

CgsccpGttGlobalTitleIndThe SCCP GTT Global Title Indicator (GTI). The following values are generally used: No global title included (0), For ITU, GT includes NAI only (1), For ANSI, GT includes TT, NP and encoding scheme (1), GT includes only TT (2), GT includes TT, NP and encoding scheme (3), GT includes TT, NP, encoding scheme, NAI (4), Maximum GTI (15), Invalid GTI (253), Wild GTI (254).Reference: The Global Title Indicator is defined in the International Telecommunication Union standard Q.713: Specifications of Signalling System No. 7 - Signalling Connection Control Part (SCCP) section 3.4.1 Address Indicator. (0..255) · Unsigned32

The global title indicator value for the global tile address specified within the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'gt' value.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the global tile address specified within the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'gt' value.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'gt' value.

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 be place in the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'pc' value.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The subsystem number to be place in the message signal unit. This object only applies when the cdsmrAddressResultType is set to 'pcSsn' value.

CmlrIdA numeric identifier used to specify an entry in a list. Zero is a special value used to indicate no entry. (0..65535) · Unsigned32

Processing continues with rule number specified by this object. This object only applies when the cdsmrAddressResultType is set to 'ruleNumber' value.

Counter32 · matches

Count of the number of times address was matched. This counter is only incremented when rule matches.

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 cdsmrAddressTable following the RowStatus textual convention.

CmlrRuleSetNameThe configured name used to identify a set of rules within an specified network. 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 (0..20) · OCTET STRING

A name used to define a set rules used to transform traffic.

CmlrRuleProtocol1 = none2 = gsmMap3 = ansi41The list of possible protocol types. 'none' : Protocol not specified and will default to value based on variant or other configuration information. 'gsmMap' : Global system for mobile communications Mobile Application Part operations should be matched by this rule. 'ansi41' : Indicates that only ANSI-41 operations should be matched by this rule. · Integer32

The object is used to establish a default protocol type for all rules within the rule set. If this object is set to 'none' will default to protocol specified by variant.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The local date and time when this trigger and sub-triggers will become active. When the value is null then the cdsmrInstStartDateAndTime does not apply.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

The local date and time this trigger and sub-triggers will become inactive. When the value is null then the cdsmrInstEndDateAndTime does not apply.

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 cdsmrRuleSetTable following the RowStatus textual convention.

CmlrIdA numeric identifier used to specify an entry in a list. Zero is a special value used to indicate no entry. (0..65535) · Unsigned32

This object specifies the index for a list of secondary triggers specified per routing table. The trigger will be processed in ascending order.

INTEGER1 = all2 = smdPp3 = smsMo4 = smsMt5 = smsSri6 = smsReg7 = smsNot8 = ucpSubmit · Integer32

The list of possible operation types. 'all' - All operations types. 'smdPp' - ANSI-41 Short message service delivery point to point. 'smsMo' - GSM-MAP Short message service mobile originated request. 'smsMt' - GSM-MAP Short message service mobile terminated request. 'smsSri' - GSM-MAP send routing info for short message. 'smsReg' - ANSI-41 Short message service request. 'smsNot' - ANSI-41 Short message service notification request 'ucpSubmit' - Match UCP Submit Short Message requests

INTEGER0 = none1 = available2 = congested3 = unavailable · Integer32

Protocol used to examine message. 'none' : CDR Service queue not specified. 'available' : Matches when CDR service queue is available. 'congested' : Matches when CDR service queue is congested. 'unavailable': Matches when CDR service queue is unavailable.

BITS

Many of the parameter used in the processing of rules have default values. These values are determined by a combination of variant and operation type. This object will be provide information which parameter has been specified as follows. 'cdrService' : Indicates that CDR service queue parameter is specified in cdsmrRuleCdrServiceQueue 'destPort' : Indicates that the destination Port number is specified in the cdsmrRuleDestPort object. 'destSmeGta' : Indicates that a global title address is specified in the cdsmrRuleDestSmeGta object. 'destSmeExact': Indicates that the cdsmrRuleDestSmeGta address must be an exact match. 'destSmeNai' : Indicates that the nature of specified address is specified in the cdsmrRuleDestSmeNai object. 'destSmeNp' : Indicates that the numbering plan is specified in the cdsmrRuleDestSmeNp object. 'destSmeImsi' : Indicates that the address specified in the International Mobile Subscriber Identification address. This indicator applies to the cdsmrRuleDestSmeGta object. 'destSmeMin' : Indicates that the address specified in the Mobile Identification Number. This indicator applies to the cdsmrRuleDestSmeGta object. 'destSmeMinDigits' : Minimum number global title address digits specified in the cdsmrRuleDestSmeGta object using the cdsmrRuleDestSmeMinDigits object. 'destSmeMaxDigits' : Maximum number global title address digits specified in the cdsmrRuleDestSmeGta object using the cdsmrRuleDestSmeMaxDigits object. 'destSmeTable' : A table of destination short message entity addresses. The name of the table is specified in the cdsmrRuleDestSmeTable object. 'destSmeTableLoc' : Specifies the location of the address table as follows. 'true' - The name specified in the cdsmrRuleDestSmeTable object exists in the cdsmrAddressTable table. 'false' - The name specified in the cdsmrRuleDestSmeTable object exists in the cmlrAddressTableEntry table from the CISCO-ITP-MLR-MIB. 'destSmeTableImsi' : Indicates that the addresses specified in the cdsmrRuleDestSmeTable are International Mobile Subscriber Identification addresses. 'destSmeTableNai' : Indicates that the all nature of specified address is specified in the cdsmrRuleDestSmeTableNai object. 'destSmeTableNp' : Indicates that the numbering plan is specified in the cdsmrRuleDestSmeTableNp object. 'destSmscGta' : Indicates that a global title address is specified in the cdsmrRuleDestSmscGta object. 'destSmscExact' : Indicates that the cdsmrRuleDestSmscGta address must be an exact match. 'destSmscNai' : Indicates that the nature of specified address is specified in the cdsmrRuleDestSmscNai object. 'destSmscNp' : Indicates that the numbering plan is specified in the cdsmrRuleDestSmscNp object. 'destSmscMinDigits' : Minimum number global title address digits specified in the cdsmrRuleDestSmscGta object using the cdsmrRuleDestSmscMinDigits object. 'destSmscMaxDigits' : Maximum number global title address digits specified in the cdsmrRuleDestSmscGta object using the cdsmrRuleDestSmscMaxDigits object. 'origImsiGta' : Indicates that a global title address is specified in the cdsmrRuleDestSmeGta object. 'origImsiExact' : Indicates that the cdsmrRuleDestSmeGta address must be an exact match. 'origImsiUnknown' : Indicates that the rule can match when packets do not contain the orgination IMSI address. That is, when the address is unknown or unspecified. The IMSI address is only specified in map version 3. Therefore, the packets using version 1 or 2 when match when this parameter is specified. 'origImsiNai' : Indicates that the nature of specified address is specified in the cdsmrRuleDestSmeNai object. 'origImsiNp' : Indicates that the numbering plan is specified in the cdsmrRuleDestSmeNp object. 'origImsiMinDigits' : Minimum number global title address digits specified in the cdsmrRuleOrigImsiGta object using the cdsmrRuleOrigImsiMinDigits object. 'origImsiMaxDigits' : Maximum number global title address digits specified in the cdsmrRuleOrigImsiGta object using the cdsmrRuleOrigImsiMaxDigits object. 'origImsiTable' : A table of orgination IMSI addresses. The name of the table is specified in the cdsmrRuleOrigImsiTable object. 'origImsiTableLoc' : Specifies the location of the address table as follows. 'true' - The name specified in the cdsmrRuleOrigImsiTable object exists in the cdsmrAddressTable table. 'false' - The name specified in the cdsmrRuleOrigImsiTable object exists in the cmlrAddressTableEntry table from the CISCO-ITP-MLR-MIB. 'origSmeGta' : Indicates that a global title address is specified in the cdsmrRuleOrigSmeGta object. 'origSmeExact': Indicates that the cdsmrRuleOrigSmeGta address must be an exact match. 'origSmeNai' : Indicates that the nature of specified address is specified in the cdsmrRuleOrigSmeNai object. 'origSmeNp' : Indicates that the numbering plan is specified in the cdsmrRuleOrigSmeNp object. 'origSmeMinDigits' : Minimum number global title address digits specified in the cdsmrRuleOrigSmeGta object using the cdsmrRuleOrigSmeMinDigits object. 'origSmeMaxDigits' : Maximum number global title address digits specified in the cdsmrRuleOrigSmeGta object using the cdsmrRuleOrigSmeMaxDigits object. 'origSmeTable': A table of origination short message entity addresses. The name of the table is specified in the cdsmrRuleOrigSmeTable object. 'origSmeTableLoc': : Specifies the location of the address table as follows. 'true' - The name specified in the cdsmrRuleOrigSmeTable object exists in the cdsmrAddressTable table. 'false' - The name specified in the cdsmrRuleOrigSmeTable object exists in the cmlrAddressTableEntry table from the CISCO-ITP-MLR-MIB. 'origSmeTableNai' : Indicates that the all nature of specified address is specified in the cdsmrRuleOrigSmeTableNai object. 'origSmeTableNp' : Indicates that the numbering plan is specified in the cdsmrRuleOrigSmeTableNp object. 'origSmscGta' : Indicates that a global title address is specified in the cdsmrRuleOrigSmscGta object. 'origSmscExact':Indicates that the cdsmrRuleOrigSmeGta address must be an exact match. 'origSmscNai' : Indicates that the nature of specified address is specified in the cdsmrRuleOrigSmscNai object. 'origSmscNp' : Indicates that the numbering plan is specified in the cdsmrRuleOrigSmscNp object. 'origSmscMinDigits' : Minimum number global title address digits specified in the cdsmrRuleOrigSmscGta object using the cdsmrRuleOrigSmscMinDigits object. 'origSmscMaxDigits' : Maximum number global title address digits specified in the cdsmrRuleOrigSmscGta object using the cdsmrRuleOrigSmscMaxDigits object. 'origSmscTable' : A table of Short Message Service Center addresses. The name of the table is specified in the cdsmrRuleOrigSmscTable object. 'origSmscTableLoc' : Specifies the location of the address table as follows. 'true' - The name specified in the cdsmrRuleOrigSmscTable object exists in the cdsmrAddressTable table. 'false' - The name specified in the cdsmrRuleOrigSmscTable object exists in the cmlrAddressTableEntry table from the CISCO-ITP-MLR-MIB. 'origSmscTableNai' : Indicates that the all nature of specified address is specified in the cdsmrRuleOrigSmscTableNai object. 'origSmscTableNp' : Indicates that the numbering plan is specified in the cdsmrRuleOrigSmscTableNp object. 'pid' : Indicates that the Protocol Identifier has been specified in the cdsmrRuleProtocolId object. 'tid' : Indicates that the Teleservice Identifier has been specified in the cdsmrRuleTeleserviceId object.

Unsigned32 (0..65535)

A destination application port number. The value of the port number maps to the values specified in the User Data Header (UDH) of the SMS message. This object only applies when the 'destPort' bit is set in the cdsmrRuleInputParameters object.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The destination short message entity global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the 'destSmeGta' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the destination short message entity global title address specified within the message signal unit. This object only applies when the 'destSmeNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the destination short message entity global title address specified within the message signal unit. This object only applies when the 'destSmeNp' bit is set in the cdsmrRuleInputParameters object.

CdsmrMinimumDigitsMinimum number of digits that global title address can contain and match rule. The minimum number of digits must be greater than or equal to the length of the specified address. A value of zero indicates the ranges is not be applied. does not apply when the global title address length is set to zero. (0..20) · Unsigned32

Specifies the minimum number of digits that the global title address specified by the cdsmrRuleDestSmeGta object can contain for rule to match. This object only applies when the 'destSmeMinDigits' bit is set in the cdsmrRuleInputParameters object.

CdsmrMaximumDigitsMaximum number of digits that global title address can contain and match rule. The maximum number of digits must be greater than or equal to the length of the specified address. Also, the maximum number of digits must be greater than or equal to minimum number of digits. A value of zero indicates the ranges is not be applied. (0..20) · Unsigned32

Specifies the maximum number of digits that the global title address specified by the cdsmrRuleDestSmeGta object can contain for rule to match. This object only applies when the 'destSmeMaxDigits' bit is set in the cdsmrRuleInputParameters object.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the entry in the cdsmrAddressTable that will be searched for matches. The table will be search for the following types of addresses based on values set in the cdsmrRuleInputParameters object. This object only applies when the 'destSmeTable' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the 'destSmeTableNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the destination short message service center global title address specified within the message signal unit. This object only applies when the 'destSmeTableNp' bit is set in the cdsmrRuleInputParameters object.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The destination short message service center global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the 'destSmscGta' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the destination short message service center global title address specified within the message signal unit. This object only applies when the 'destSmscNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the destination short message service center global title address specified within the message signal unit. This object only applies when the 'destSmscNp' bit is set in the cdsmrRuleInputParameters object.

CdsmrMinimumDigitsMinimum number of digits that global title address can contain and match rule. The minimum number of digits must be greater than or equal to the length of the specified address. A value of zero indicates the ranges is not be applied. does not apply when the global title address length is set to zero. (0..20) · Unsigned32

Specifies the minimum number of digits that the global title address specified by the cdsmrRuleDestSmscGta object can contain for rule to match. This object only applies when the 'destSmscMinDigits' bit is set in the cdsmrRuleInputParameters object.

CdsmrMaximumDigitsMaximum number of digits that global title address can contain and match rule. The maximum number of digits must be greater than or equal to the length of the specified address. Also, the maximum number of digits must be greater than or equal to minimum number of digits. A value of zero indicates the ranges is not be applied. (0..20) · Unsigned32

Specifies the maximum number of digits that the global title address specified by the cdsmrRuleDestSmscGta object can contain for rule to match. This object only applies when the 'destSmscMaxDigits' bit is set in the cdsmrRuleInputParameters object.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The origination short message entity global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the 'origImsiGta' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the origination short message entity global title address specified within the message signal unit. This object only applies when the 'origImsiNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the origination short message entity global title address specified within the message signal unit. This object only applies when the 'origImsiNp' bit is set in the cdsmrRuleInputParameters object.

CdsmrMinimumDigitsMinimum number of digits that global title address can contain and match rule. The minimum number of digits must be greater than or equal to the length of the specified address. A value of zero indicates the ranges is not be applied. does not apply when the global title address length is set to zero. (0..20) · Unsigned32

Specifies the minimum number of digits that the global title address specified by the cdsmrRuleOrigImsiGta object can contain for rule to match. This object only applies when the 'origImsiMinDigits' bit is set in the cdsmrRuleInputParameters object.

CdsmrMaximumDigitsMaximum number of digits that global title address can contain and match rule. The maximum number of digits must be greater than or equal to the length of the specified address. Also, the maximum number of digits must be greater than or equal to minimum number of digits. A value of zero indicates the ranges is not be applied. (0..20) · Unsigned32

Specifies the maximum number of digits that the global title address specified by the cdsmrRuleOrigImsiGta object can contain for rule to match. This object only applies when the 'origImsiMaxDigits' bit is set in the cdsmrRuleInputParameters object.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the entry in the cdsmrAddressTable that will be searched for matches. The table will be search for the following types of addresses based on values set in the cdsmrRuleInputParameters object. This object only applies when the 'origImsiTable' bit is set in the cdsmrRuleInputParameters object.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The origination short message entity global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the 'origSmeGta' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the origination short message entity global title address specified within the message signal unit. This object only applies when the 'origSmeNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the origination short message entity global title address specified within the message signal unit. This object only applies when the 'origSmeNp' bit is set in the cdsmrRuleInputParameters object.

CdsmrMinimumDigitsMinimum number of digits that global title address can contain and match rule. The minimum number of digits must be greater than or equal to the length of the specified address. A value of zero indicates the ranges is not be applied. does not apply when the global title address length is set to zero. (0..20) · Unsigned32

Specifies the minimum number of digits that the global title address specified by the cdsmrRuleOrigSmeGta object can contain for rule to match. This object only applies when the 'origSmeMinDigits' bit is set in the cdsmrRuleInputParameters object.

CdsmrMaximumDigitsMaximum number of digits that global title address can contain and match rule. The maximum number of digits must be greater than or equal to the length of the specified address. Also, the maximum number of digits must be greater than or equal to minimum number of digits. A value of zero indicates the ranges is not be applied. (0..20) · Unsigned32

Specifies the maximum number of digits that the global title address specified by the cdsmrRuleOrigSmeGta can contain for rule to match. This object only applies when the 'origSmeMaxDigits' bit is set in the cdsmrRuleInputParameters object.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the entry in the cdsmrAddressTable that will be searched for matches. The table will be search for the following types of addresses based on values set in the cdsmrRuleInputParameters object. This object only applies when the 'origSmeTable' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the 'origSmeTableNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the destination short message service center global title address specified within the message signal unit. This object only applies when the 'origSmeTableNp' bit is set in the cdsmrRuleInputParameters object.

CItpTcGtaLongDisplayThe configured digits in the SCCP GTT Global Title Address. It consists of ASCII representation of GTA hex digits. SIZE (0..64) · OCTET STRING

The origination short message service center global title address. When the length of the global title address is zero it specified a wildcard match and all global title will match GTA clause of rule. This object only applies when the 'origSmscGta' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the origination short message service center global title address specified within the message signal unit. This object only applies when the 'origSmscNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the origination short message service center global title address specified within the message signal unit. This object only applies when the 'origSmscNp' bit is set in the cdsmrRuleInputParameters object.

CdsmrMinimumDigitsMinimum number of digits that global title address can contain and match rule. The minimum number of digits must be greater than or equal to the length of the specified address. A value of zero indicates the ranges is not be applied. does not apply when the global title address length is set to zero. (0..20) · Unsigned32

Specifies the minimum number of digits that the global title address specified by the cdsmrRuleOrigSmscGta object can contain for rule to match. This object only applies when the 'origSmscMinDigits' bit is set in the cdsmrRuleInputParameters object.

CdsmrMaximumDigitsMaximum number of digits that global title address can contain and match rule. The maximum number of digits must be greater than or equal to the length of the specified address. Also, the maximum number of digits must be greater than or equal to minimum number of digits. A value of zero indicates the ranges is not be applied. (0..20) · Unsigned32

Specifies the maximum number of digits that the global title address specified by the cdsmrRuleOrigSmscGta object can contain for rule to match. This object only applies when the 'origSmscMaxDigits' bit is set in the cdsmrRuleInputParameters object.

CmlrNameThe configured name used to identify various tables used by MLR. 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 (0..20) · OCTET STRING

The name of the entry in the cdsmrAddressTable that will be searched for matches. The table will be search for the following types of addresses based on values set in the cdsmrRuleInputParameters object. This object only applies when the 'origSmscTable' bit is set in the cdsmrRuleInputParameters object.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the 'origSmscTableNai' bit is set in the cdsmrRuleInputParameters object.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the destination short message service center global title address specified within the message signal unit. This object only applies when the 'origSmscTableNp' bit is set in the cdsmrRuleInputParameters object.

Unsigned32 (0..255)

The protocol identifier value used for the 'smsMo and 'smsMt' operations specified by the cdsmrRuleParmsOperationType object. The value of the cdsmrRuleParmsMatchPid object maps to the values specified for the TP-PID SMS parameter. This object only applies when the 'pid' bit is set in the cdsmrRuleInputParameters object.

Unsigned32 (0..65535)

The Teleservice identifier value for the following types of operations specified by the cdsmrRuleParmsOperationType object. 'smdPp' 'smsMo' 'smsMt' 'smsNotify' The value of the cdsmrRuleParmsMatchTid object maps to the values specified for the SMS_TeleserviceIdentifier parameter in ANSI-41. This object only applies when the 'tid' bit is set in the cdsmrRuleInputParameters object.

CdsmrResultParametersIn order to specify the results of DSMR statements different values in the packet can be modified. These values are determined by a combination of variant and operation type. This object indicates which objects will be used to form a result action as follows. This textual convention defines the result actions of DSMR which are determined by a combination of variant and operation type. The possible result actions of DSMR are as follows: 'network' : specifies network 'octet' : specifies octet string 'tranType' : specifies translation type 'gti' : specifies global title indicator 'np' : specifies numbering plan 'nai' : specifies nature of address 'pc' : specifies point-code 'ssn' : specifies subsystem number 'ruleNumber': specifies next rule to execute · BITS

Many of the parameter used in the processing of rules have default values. These values are determined by a combination of variant and operation type. This object will be provide information on which parameter have been specified as follows. 'network' : cdsmrRuleSetResultNetwork 'octet' : cdsmrRuleSetResultOctet 'tranType' : cdsmrRuleResultTransType 'gti' : cdsmrRuleResultGti 'np' : cdsmrRuleResultNp 'nai' : cdsmrRuleResultNai 'pc' : cdsmrRuleResultPc 'ssn' : cdsmrRuleResultSsn 'ruleNumber': cdsmrRuleResultRuleNumber

CItpTcNetworkNameThe network name is used to indicate the network in which this signalling point is participating. One or more instances of signalling points can exist in the same physical device. This identifier will be used to correlate instances of signalling points by network. When multiple instance support is not enable the network name will default to the null string. 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 (0..19) · OCTET STRING

The network name is used to indicate the network in which the result operation will be performed.

CdsmrResultType0 = none1 = pc2 = pcSsn3 = gt4 = group5 = smpp6 = ucp7 = block8 = ruleNext9 = ruleNumber10 = deliverMt11 = origImsi12 = origImsiNextThis textual convention defines the result type of DSMR. The possible result types are as follows: 'none' : Result not specified. 'block' : Message will be discarded. 'pc' : Message will be routed using the specified destination point code. 'pcSsn' : Message will be routed using the specified destination point code and subsystem number. destination M3UA or SUA Application Server(AS). 'gt' : Message will be routed using SCCP global title. 'group' : Message will be routed using information specified in result group. 'smpp' : Delivery via Short Message Peer-to-Peer 'ucp' : Delivery via Universal Computer Protocol 'ruleNext' : When address matches entry in table processing will continue with next rule. 'ruleNumber' : When address matches entry in table processing will continue with specified rule. 'deliverMt': Indicates that a delivery attempt should be attempted to the destination SME as a mobile device. 'origImsi': Attempt to obtain the original IMSI address and us it to delivery packet. When the IMSI address is unavailable fail packet. 'origImsiNext': Attempt to obtain the original IMSI address and us it to delivery packet. When the IMSI address is unavailable continue processing with next rule. · Integer32

Specified the type of information to be placed into the message signal unit or how the it will be processed.

CdsmrResultOctetAn octet string that contains various types of output from a rule. The information in this textual convention is formatted as follows: CdsmrResultType: None : Octet string with length of zero. pc : Not applicable pcSsn : Not applicable. gt : The global title address formatted as CItpTcGtaLongDisplay group : Result group formatted as CmlrName. smpp : Result group formatted as CmlrName ucp : Result group formatted as CmlrName block : Not applicable. ruleNext : Not applicable. ruleNumber: Not applicable. deliveryMt: Not applicable. origImsi : Not Applicable origImsiNext: Not Applicable When the result octet is not used as a parameter, not applicable, the length will be set to zero. 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 (0..64) · OCTET STRING

Information to be placed in the message signal unit based on the value specified by the cdsmrRuleSetResultType object. When the cdsmrRuleSetResultType object is set to 'pc' or 'none' this object will not be used in the result processing and will have a length of zero.

CgsccpGttTransTypeThe SCCP GTT Translation Type (TT). (0..255) · Unsigned32

The translation type specified within the address in the message signal unit. This object only applies when the cdsmrRuleSetResultType is set to 'gt' value.

CgsccpGttGlobalTitleIndThe SCCP GTT Global Title Indicator (GTI). The following values are generally used: No global title included (0), For ITU, GT includes NAI only (1), For ANSI, GT includes TT, NP and encoding scheme (1), GT includes only TT (2), GT includes TT, NP and encoding scheme (3), GT includes TT, NP, encoding scheme, NAI (4), Maximum GTI (15), Invalid GTI (253), Wild GTI (254).Reference: The Global Title Indicator is defined in the International Telecommunication Union standard Q.713: Specifications of Signalling System No. 7 - Signalling Connection Control Part (SCCP) section 3.4.1 Address Indicator. (0..255) · Unsigned32

The global title indicator value for the global tile address specified within the message signal unit. This object only applies when the cdsmrRuleSetResultType is set to 'gt' value.

CItpTcNumberingPlanThe SCCP GTT Numbering Plan (NP). The following values are generally used: Unknown NP (0), ISDN/Telephony NP (1), Spare (2), Data NP (3), Telex NP (4), Maritime Mobile NP (5), Land Mobile NP (6), ISDN/Mobile NP (7), Private NP (8). Max NP (15), Invalid NP (253), Wild NP (254). (0..255) · Integer32

The numbering plan for the global tile address specified within the message signal unit. This object only applies when the cdsmrRuleSetResultType is set to 'gt' value.

CItpTcNAIThe SCCP GTT Network Address Indicator (NAI). The following values are generally used: Unknown Nature of Address (0), Subscriber Number (1), Reserved for national use (2), National Significant Number (3), International Number (4), Maximum NAI (127), Invalid NAI (253), Wild NAI (254). (0..255) · Integer32

The nature of specified address for the global tile address specified within the message signal unit. This object only applies when the cdsmrRuleSetResultType is set to 'gt' value.

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 be place in the message signal unit. This object only applies when the cdsmrRuleResultType is set to 'pc' value.

CItpTcSubSystemNumberThe SCCP Subsystem Number . A value of zero indicates that a subsystem is not specified. (0 | 2..255) · Unsigned32

The subsystem number to be place in the message signal unit. This object only applies when the cdsmrRuleResultType is set to 'ssn' value.

CmlrIdA numeric identifier used to specify an entry in a list. Zero is a special value used to indicate no entry. (0..65535) · Unsigned32

This object specifies the next rule to execute when rule matches. The specified rule number must be greater than current rule.

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 cdsmrRuleTable following the RowStatus textual convention.

Counter32 · checks

Count of the number of times this rule was checked.

Counter32 · matches

Count of the number of times this rule was matched.

Counter32 · successes

Count of the number of times this rule was matched and packet was routed using mechanism specified by result.