CISCO-ITP-GRT-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 route table 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 cgrtRouteTable.

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 the route table using file format.

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 cgrtInstLastLoadTime contains a timestamp indicating when the load operation is completed.

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

The system generated name for the route table for this signalling point instance.

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 url used to load route table.

Gauge32 · entries

The number of destination in the cgrtDestTable Table.

Gauge32 · entries

The number of routes in the cgrtRouteTable Table.

Counter32 · MSUs

The number of MSUs with unknown origination point codes arrived to this signalling point instance. MSUs originated from local pointcode will not be counted as unknown OPCs.

Counter32 · MSUs

Reference: ANSI GR-82-CORE 6.4.2 System Total Measurements Item 32.

The number of MSUs dropped due to no corresponding entry in the destination table for this signalling point instance Q752/5.5.

INTEGER1 = unknown2 = accessible3 = inaccessible4 = restricted · Integer32

List of the possible route state values. 'unknown' : A destination state of unknown occurs when the destination is a summary route. Unknown state is presented to indicate the protocols do not exchange state information for summary routes in certain configurations. 'accessible' : The destination can be reached by one or more routes specified for the destination. When summary routing is enabled, a destination status will also depend on route table entries that specify less specific matches. See Example 4 in the DESCRIPTION section for such a configuration. 'inaccessible' : Destination can not be reached by any route known to this signalling point. 'restricted' : Traffic has been restricted from being sent to the destination. The restricted state indicates that the primary route for the destination is unavailable or that it is impacted by some network event or failure of resource.

Unsigned32 (0..3)

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

The congestion status of this destination. The value indicates congestion on one or more links in one of the linksets used to route traffic to the signalling point specified by the cgrtRouteDpc object. 0 is the least congestion level, 3 is the highest congestion level.

Counter32 · seconds

Duration in seconds that this destination was in the accessible state.

Counter32 · seconds

Duration in seconds that this destination was in the inaccessible state.

Counter32 · seconds

Duration in seconds that this destination was in the restricted state.

Counter32 · MSUs

The number of MSUs that were queued to linkset for transmission to this destination. Management MSUs that originate from this signalling point are also counted. It is important to note that, in rare cases, MSU discards due to any abnormal system resource error conditions may be included in this count.

Counter64 (0..18446744073709551615) · octets

The number of Octets in MSUs that were queued to linkset for transmission to this destination. It is important to note that, in rare cases, octets discarded due to any abnormal system resource error conditions may be included in this count.

Counter32 · MSUs

The number of MSUs that arrived to this signalling point bound for this destination. This includes the received as well as blocked MSUs.

Counter64 (0..18446744073709551615) · octets

The number of Octets in MSUs that arrived to this signalling point bound for this destination.

Counter32 · MSUs

The number of MSUs dropped for this destination due to inaccessible route state.

Counter32 · MSUs

The number of MSUs transferred for this destination during a restricted route state.

Counter32 · MSUs

The number of MSUs dropped for this destination due to local and remote congestion.

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

The destination point code in display format.

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 destination point code.

Unsigned32 (0..16777215)

The mask used to define which part of cgrtRouteDpc is significant when comparing the cgrtRouteDpc to the destination code point in the packet to be routed.

Unsigned32 (1..9)

The cost assigned to this linkset matching this route. Higher numbers represent higher cost.

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

The linkset that the packet is to be forwarded to on matching this route.

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

The quality of service classification to be assigned to the IP packets used to transport the SS7 messages. The value to specify for packets when they will be transported on SCTP/IP based linkset.

INTEGER1 = unknown2 = available3 = restricted4 = unavailable5 = deleted · Integer32

List of the possible route status values. These values are determine using the status of the linkset specified in this route and the route management status. 'unknown' : Status can not be determined. 'available' : Route is available. 'restricted' : Traffic is restricted on route. 'unavailable' : Route is unable to service traffic. 'deleted' : Route has been removed.

INTEGER1 = unknown2 = allowed3 = restricted4 = prohibited5 = deleted · Integer32

List of the possible route management route status values. Route management status are received in transfer-allowed(TFA), transfer-prohibited(TFP), transfer-restricted(TFR), transfer-cluster-allowed(TCA), transfer-cluster-prohibited(TCP) and transfer-cluster-restricted(TFR) management messages. 'unknown' : Status can not be determined. 'allowed' : traffic is allowed. 'restricted' : Traffic is restricted on route. 'prohibited' : Route is prohibited from providing traffic. 'deleted' : Route has been removed.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Routes are either static or dynamic. Static routes are created based on configuration information specified by an administrator. Dynamic routes are created as a by product of an network event in certain situations. Dynamic routes are only created when summary routing has been activated. This object indicates whether this route entry is dynamic or static. 'true' - dynamic route 'false' - static route

INTEGER0 = unknown1 = static2 = cluster3 = summary4 = xlist5 = shadow6 = management7 = alias · Integer32

When summary or cluster routes are specified this field will provide additional information about the fully qualified routes within the specified clusters. Since, summary or cluster routes represent a group of destinations it is necessary to collect and maintain status information on routes that are not available. Additional, route statements are created dynamically whenever a TFP or TFR is received on a fully qualified route represented by a defined summary route. There are three four types of dynamic route as follows. List of the possible route status values. 'unknown': Undefined type of route. 'static': A fully-qualified route configured by system administrator. 'cluster': An ANSI cluster route. A DPC and mask with length of 16 bits configured by system administrator. 'summary': An DPC and a mask with length 0-10 for ITU and 0-15,17-23 for ANSI. A summary route is configured by a system administrator. 'xlist': This route is dynamic and is create whenever TFP or TFR is received for a point-code represented by a ANSI cluster route. 'shadow': When a TFP or TFR is received for a point-code represented by a summary or cluster route all route statements specified for the summary or cluster destination are copied. These new routes appear under the specific fully-qualified destination. The route will be marked as a shadow when a TFP or TFR has not been received for that particular route. 'management' : When a TFP or TFR is received for a point-code represented by a summary route all route statements specified for the summary destination are copied. The new routes appear under the fully-qualified destination specified in the TFR or TFP. The route specified in the TFR or TFP will be marked as a dynamic to indicate that MTP3 route management information is available for this route. 'alias': Route statement is created in response to conversion statements defined to alias point-codes across networks.

INTEGER0 = none1 = unknown2 = available3 = restricted4 = unavailable5 = deleted · Integer32

List of the possible administration route status values. 'none' : none. 'unknown' : Status can not be determined. 'available' : Route is available. 'restricted' : Traffic is restricted on route. 'unavailable' : Route is unable to service traffic. 'deleted' : Route has been removed. When the cgrtRouteAdminStatus object is set to the none value the cgrtRouteStatus status will be based on the cgrtRouteMgmtStatus and linkset availability. Otherwise the cgrtRouteStatus will be set to the value specified in cgrtRouteAdminStatus object.

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, modify or delete the row entry in cgspPointCodeTable following the RowStatus textual convention. The only object available for modification is the cgrtRouteAdminStatus object.

Counter32 · seconds

Duration in seconds during which forwarding was allowed for this route.

Counter32 · seconds

Duration in seconds during which forwarding was restricted for this route.

Counter32 · seconds

Duration in seconds during which forwarding was prohibited for this route.

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

The destination point code associated with the route in display format.

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 origination point code.

Counter32 · MSUs

The number of incoming MSUs from this origination.

Counter64 (0..18446744073709551615) · octets

The number of incoming octets from this origination.

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

The origination point code associated with the table entry in display format.

CItpTcServiceIndicator0 = snmm1 = sntm2 = spare23 = sccp4 = tup5 = isup6 = dupc7 = dupf8 = mtup9 = bisup10 = sisup11 = spare1112 = spare1213 = spare1314 = spare1415 = spare15The list of possible Service Indicator values. This identifies the type of SS7 packet. The service indicator codes for the international Signalling network are allocated as follows: 'SNMM' : Signalling network management messages (SNMM) 'SNTM' : Signalling network testing and maintenance messages (SNTM) 'Spare2' : Spare 2 'SCCP' : SCCP 'TUP' : Telephone User Part (TUP) 'ISUP' : ISDN User Part (ISUP) 'DUPC' : Data User Part, call and circuit-related messages (DUPC) 'DUPF' : Data User Part, facility registration and cancellation messages (DUPF) 'MTUP' : Reserved for MTP Testing User Part (MTUP) 'BISUP' : Broadband ISDN User Part (BISUP) 'SISUP' : Satellite ISDN User Part (SISUP) 'Spare11' : Spare 11 'Spare12' : Spare 12 'Spare13' : Spare 13 'Spare14' : Spare 14 'Spare15' : Spare 15Reference: ITU Q.704 Signalling network functions and messages section 14.2.1 Service indicator. · Integer32

The service indicator.

Counter32 · MSUs

The number of outgoing MSUs that were queued to linkset for transmission to this specific destination and service indicator. Management MSUs that originate from this signalling point are also counted. It is important to note that, in rare cases, MSU discards due to any abnormal system resource error conditions may be included in this count.

Counter64 (0..18446744073709551615) · octets

The number of outgoing octets that were queued to linkset for transmission to this specific destination and service indicator. It is important to note that, in rare cases, octets discarded due to any abnormal system resource error conditions may be included in this count.

Counter32 · MSUs

The number of incoming MSUs for this specific destination and service indicator. This includes the received as well as blocked MSUs.

Counter64 (0..18446744073709551615) · octets

The number of incoming octets for this specific destination and service indicator.

CgrtDisplayPCSIThe point code and service indicator information formatted for display. Point code will be formatted based on the variant and the customer defined parameters. SIZE (1..20) · OCTET STRING

The destination point code and service indicator associated with the table entry in display format.

Counter32 · MSUs

The number of incoming MSUs for this specific origination and service indicator.

Counter64 (0..18446744073709551615) · octets

The number of incoming MSUs for this specific origination and service indicator.

CgrtDisplayPCSIThe point code and service indicator information formatted for display. Point code will be formatted based on the variant and the customer defined parameters. SIZE (1..20) · OCTET STRING

The origination point code and service indicator associated with the table entry in display format.