CISCO-ITP-GRT-MIB: View SNMP OID List / Download MIB

This MIB is for managing information required to route messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer Point. The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides the functions necessary to act as a SS7 signalling point. Each signalling point is connected to other signalling point using IP based or traditional TDM links. The relevant ITU documents describing this technology are the ITU Q series, including ITU Q.700: Introduction to CCITT Signalling System No. 7 and ITU Q.701 Functional description of the message transfer part (MTP) of Signalling System No. 7. Definitions and overview: Route: A route consists of one or more linksets used to transport MTP3 Message Signal Units(MSU) between signalling points. A route is an association between a destination point code(DPC) and a linkset, i.e., a linkset that can be used to send an MSU to the given DPC. Routeset: A routeset is a set of routes to a given DPC. Each route within a routeset is on a possible path toward the DPC. Each route within the routeset has associated with it a route priority. In the following simple configuration, two routes exist that can be used to transport MSUs from STP1 to STP4. --------- STP1-STP2 --------- - STP1 ----------------------------- STP2 - --------- --------- | | | STP1-STP3 STP2-STP4 | | | --------- STP3-STP4 --------- - STP3 ----------------------------- STP4 - --------- --------- Routeset on STP1 for DPC = STP4: STP1-STP2, STP1-STP3 Linkset: A linkset is a set of signalling links connecting two signalling points. Combined Linkset: Two linksets with equal number of links and capacity that form routes of equal priority to a given DPC are called Combined Linksets. It is primarily used for load sharing and redundancy. In the following, example, linksets 'SSP1-STP1' and 'SSP1-STP2' form a combined linsket. SSP1-STP1 --------- |------------------------- STP1 - | --------- - - - - - SSP1 - - - - - | SSP1-STP2 --------- |------------------------ STP2 - --------- Routing: The routing of SS7 Message signalling Units(MSU) is based on the DPC. Message Signalling Units are sent from an originating point code(OPC) to DPC. Each MSU will traverse one or more linksets as it is routed to its final destination. When an MSU arrives at a signalling point and the DPC does not match the signalling point's point code the MSU must be directed toward the DPC. Each signalling point has enough routing information to determine which linkset should be used to transmit the MSU toward its final destination. Route statement: Each ITP Signalling Point has route statements needed to determine which linkset should be used to transmit message signalling units to destinations. Each route statement consists of a destination, a priority and a linkset name. The destination is specified as a combination of DPC and mask. The priority, also know as cost, is used to define the order in which the routes are selected. The linkset name specifies which linkset to use to reach the destination. Route table: Each ITP Signalling Point has a table of routes. These route entries are used to determine which linkset should be selected to transmit message signalling units to a given destination. There are two basic type of routing. The first type is fully-qualified and uses all bits of the target DPC. The other type is summary routing that uses a subset of the bits in the target DPC and is used to represent groups of point codes rather than a single point code. Example of route table entries. Example 1: variant = ITU DPC/MASK Priority Linkset-name -------- -------- ----------------------- 5.5.5/14 3 STP1-STP2 5.5.5/14 7 STP1-STP3 Description: Two route table entries that define a primary route using linkset 'STP1-STP2' and an alternate route using linkset 'STP1-STP3' to point-code 5.5.5. Example 2: variant = ITU DPC/MASK Priority Linkset-name -------- -------- ----------------------- 5.5.5/14 3 STP1-STP2 5.5.5/14 3 STP1-STP3 5.5.5/14 7 STP1-STP4 Description: Two route table entries that define a combined linkset consisting of linkset 'STP1-STP2' and 'STP1-STP3' to point code 5.5.5. An alternate route is also defined using linkset 'STP1-STP4'. Example 3: variant = ANSI DPC/MASK Priority Linkset-name -------- -------- ----------------------- 5.5.0/16 3 STP1-STP2 Description: A route table entry that defines routing to a cluster. The cluster represents all point codes in the range from 5.5.0-5.5.255. Example 4: variant = ANSI DPC/MASK Priority Linkset-name -------- -------- ----------------------- 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 Description: The mixing of fully-qualified and summary route table entries allow for different routes to be defined for certain DPC in a cluster. In this configuration, the fully-qualified route will be the primary and the summary route will act as a backup. Route table: A group of route table entries used to route MSU for a particular instance of a signalling point. A sample route table. DPC/MASK Priority Linkset-name -------- -------- ----------------------- 0.0.0/0 7 STP1-STP4 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 . . 122.5.5 5 STP1-STP2 . . 243.200.1 6 STP1-STP3

This notification is generated whenever one or more destination changes states. This notification contains a list of destination state changes in the cgrtDestNotifChanges object. State changes are accumulated until the cgrtDestNotifChanges is full or the maximum delay time is reached. The delay time is specified by the cgrtDestNotifDelayTime object. It may be necessary to suppress the sending of notification when a large number destinations change state, due the failure of some common resource. The number of notifications can be controlled by specifying values for cgrtDestNotifWindowTime and cgrtDestNotifMaxPerWindow objects. When the number of destination state changes exceed the specified value the last notification will indicate that notifications are suppressed for the remainder of the window. This notification is deprecated by ciscoGrtDestStateChangeRev1.

This notification is generated whenever one or more management routes change state. This notification contains a list of management route state changes in the cgrtMgmtNotifChanges object. State changes are accumulated until the cgrtMgmtNotifChanges is full or the maximum delay time is reached. The delay time is specified by the cgrtMgmtNotifDelayTime object. It may be necessary to suppress the sending of notification when a large number of routes change state, due the failure of some common resource. The number of notifications can be controlled by specifying values for cgrtMgmtNotifWindowTime and cgrtMgmtNotifMaxPerWindow objects. When the number of route state changes exceed the specified value the last notification will indicate that notifications are suppressed for the remainder of the window. This notification is deprecated by ciscoGrtMgmtStateChangeRev1.

This notification is generated whenever a load operation is started or completed. Route table configurations can be loaded by CLI requests. In addition, route tables can loaded using configuration statements. This allows route tables to be reloaded whenever a device restarts.

This notification is generated whenever one or more destination changes states within the cgrtDestNotifWindowTimeRev1 duration. Latest state information at the end of cgrtDestNotifWindowTimeRev1 is provided. It may be necessary to suppress the sending of notification when a large number destinations change state, due the failure of some common resource. The number of notifications can be controlled by specifying values for cgrtDestNotifWindowTimeRev1 and cgrtDestNotifMaxPerWindowRev1 objects. When the number of destination state changes exceed the specified value, the notification will provide a count of notifications that got suppressed for the remainder of the window. This notification deprecates ciscoGrtDestStateChange.

This notification is generated whenever one or more management routes change states within the cgrtMgmtNotifWindowTimeRev1 duration. Latest state information at the end of cgrtMgmtNotifWindowTimeRev1 is provided. It may be necessary to suppress the sending of notification when a large number of routes change state, due the failure of some common resource. The number of notifications can be controlled by specifying values for cgrtMgmtNotifWindowTimeRev1 and cgrtMgmtNotifMaxPerWindowRev1 objects. When the number of route state changes exceed the specified value, the last notification will provide a count of notifications that got suppressed for the remainder of the window. This notification deprecates ciscoGrtMgmtStateChange.

This notification is generated whenever one or more MSU discards happen due to route data error for a specific signalling point instance in the configured cgrtNoRouteMSUsNotifWindowTime. For cases when there is a non-zero number of MSUs discarded, this notification will be sent at the end of the cgrtNoRouteMSUsNotifWindowTime interval, with cgrtIntervalNoRouteMSUs indicating the total count of MSUs discarded for that specific signalling point instance during the entire cgrtNoRouteMSUsNotifWindowTime interval Q752/5.5.

The maximum number of dynamic SS7 routes. This object is used to limit the size of the route table by preventing unbounded growth of dynamic entries. Dynamic entries are created when certain MTP3 management messages are received or sent. The removal of dynamic routes is performed periodically and the older dynamic routes are removed until the specified number is reached.

This object specifies the maximum amount of time to delay before generating the ciscoGrtDestStateChange notification. The delay is introduced to allow multiple destination state changes to be bundled into a single notification. If the value of this object is equal to 0, the device will generate ciscoGrtDestStateChange notification as each route changes states. If the value of this object is greater than 0, the device will not generate notifications as destinations change state. As each destination changes state they are accumulated until the time specified in cgrtDestNotifDelayTime has elapsed or enough state changes have been accumulated to fill up the cgrtDestNotifChanges object. This object is ignored by the agent when the cgrtDestNotifEnabled object is set to the 'false' value.

This object specifies the time interval used to monitor the rate of destination state changes notifications. This object in combination with cgrtDestNotifMaxPerWindow is used to determine the notification transit rate and suppress destination state notifications.

This object specifies the maximum number of destination state changes that can occur in the time interval specified in the cgrtDestNotifWindowTime object. If additional state changes can occur in the specified time interval the notifications are suppressed.

A control to enable or disable ciscoGrtDestStateChange notifications as follows: 'true' Indicates that the ciscoGrtDestStateChange notification should be generated when the state of any destination changes. That is, the notification generation is enabled. 'false' Indicates that ciscoGrtDestStateChange notification generation is disabled.

This object specifies the maximum amount of time to delay before generating the ciscoGrtMgmtStateChange notification. The delay is introduced to allow multiple route state changes to be bundled into a single notification. If the value of this object is equal to 0, the device will generate ciscoGrtMgmtStateChange notification as each route changes states. If the value of this object is greater than 0, the device will not generate notifications as routes change state. As routes change state they are accumulated until the time specified in cgrtMgmtNotifDelayTime has elapsed or enough state changes have been accumulated to fill up the cgrtRouteNotifChanges object. This object is ignored by the agent when the cgrtMgmtNotifEnabled object is set to the 'false' value.

This object specifies the time interval used to monitor the rate of route state changes notifications. This object in combination with cgrtMgmtNotifMaxPerWindow is used to determine the notification transit rate and suppress route management state notifications.

This object specifies the maximum number of route management state changes that can occur in the time interval specified in the cgrtMgmtNotifWindowTime object. If additional state changes can occur in the specified time interval the notifications are suppressed.

A control to enable or disable ciscoGrtMgmtStateChange notifications as follows: 'true' Indicates that the ciscoGrtMgmtStateChange notification should be generated when the state of any route changes. That is, the notification generation is enabled. 'false' Indicates that ciscoGrtMgmtStateChange notification generation is disabled.

A control to enable or disable ciscoGrtRouteTableLoad notifications as follows: 'true' Indicates that the ciscoGrtRouteTableLoad notification should be generated when the load operations is started or completed. That is, the notification generation is enabled. 'false' Indicates that ciscoGrtRouteTableLoad notification generation is disabled.

The number of dynamic route entries created in response to MTP3 management messages. The maximum number for dynamic route entries is defined by the cgrtRouteMaxDynamic object. When a MTP3 management message is received and this limit is reached the request is dropped. The cgrtDynamicRoutesDropped object will be incremented in these situations.

The number of dynamic route entries that could not be created because the limit specified by the cgrtRouteMaxDynamic object had been reached.

This object specifies the time interval used to monitor the rate of destination state changes notifications. This object in combination with cgrtDestNotifMaxPerWindowRev1 is used to determine the notification transit rate and suppress destination state notifications.

This object specifies the maximum number of destination state changes that can occur in the time interval specified in the cgrtDestNotifWindowTimeRev1 object. If additional state changes do occur in the specified time interval the notifications are suppressed.

A control to enable or disable ciscoGrtDestStateChangeRev1 notifications as follows: 'true' Indicates that the ciscoGrtDestStateChangeRev1 notification should be generated when the state of any destination changes. That is, the notification generation is enabled. 'false' Indicates that ciscoGrtDestStateChangeRev1 notification generation is disabled.

This object specifies the time interval used to monitor the rate of route state changes notifications. This object in combination with cgrtMgmtNotifMaxPerWindowRev1 is used to determine the notification transit rate and suppress route management state notifications.

This object specifies the maximum number of route management state changes that can occur in the time interval specified in the cgrtMgmtNotifWindowTimeRev1 object. If additional state changes can occur in the specified time interval the notifications are suppressed.

A control to enable or disable ciscoGrtMgmtStateChangeRev1 notifications as follows: 'true' Indicates that the ciscoGrtMgmtStateChangeRev1 notification should be generated when the state of any route changes. That is, the notification generation is enabled. 'false' Indicates that ciscoGrtMgmtStateChangeRev1 notification generation is disabled.

A control to enable or disable the support of optional cgrtOrigTable. 'true' Enables the OrigTable optional feature. 'false' Disables the OrigTable optional feature.

This object indicates the allowed values for the statistics sampling interval. A value of zero is only valid for a single processor platform. For distributed platforms, the value in seconds specifies how often information on measurements will be refreshed on supervisor. The valid range for distributed platforms is from 15 minutes., i.e., 900 seconds to 1 hour.

A control to enable or disable ciscoGrtNoRouteMSUDiscards notifications as follows: 'true' Indicates that the ciscoGrtNoRouteMSUDiscards notification generation is enabled. 'false' Indicates that ciscoGrtNoRouteMSUDiscards notification generation is disabled.

This object specifies the time interval used to monitor the ciscoGrtNoRouteMSUDiscards notifications generated for a signalling point instance. The first occurrence of ciscoGrtNoRouteMSUDiscards notifications in this interval is sent and the further occurrences of notifications in this interval are suppressed. At the end of this interval, a notification is sent with total number of MSUs discarded due to routing data error during this interval.

A route table exist per instance of signalling point. This table defines the routes defined for a particular instance.

A collection of route statements used to forward packets to requested destinations. Each table entry represents a route statement that was either configured or added in response to events in the network.

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.

The value of sysUpTime at the time of the last load of the route table using file format.

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.

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

The url used to load route table.

The number of destination in the cgrtDestTable Table.

The number of routes in the cgrtRouteTable Table.

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.

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

The destination table provides state information on the ability to route MTP packets to a particular destination point code.

Each table entry represents a specific destination point code(DPC).

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. Enumeration: 'accessible': 2, 'unknown': 1, 'inaccessible': 3, 'restricted': 4.

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.

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

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

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

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.

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.

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

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

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

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

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

The destination point code in display format.

The route table for determining the linkset that a packet must traverse to arrive at its destination given by the destination point code.

Each table entry represents a configured route statement.

The destination point code.

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.

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

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

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.

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. Enumeration: 'available': 2, 'unknown': 1, 'deleted': 5, 'unavailable': 4, 'restricted': 3.

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. Enumeration: 'deleted': 5, 'unknown': 1, 'prohibited': 4, 'restricted': 3, 'allowed': 2.

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

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. Enumeration: 'management': 6, 'xlist': 4, 'alias': 7, 'unknown': 0, 'summary': 3, 'cluster': 2, 'static': 1, 'shadow': 5.

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. Enumeration: 'available': 2, 'none': 0, 'unavailable': 4, 'deleted': 5, 'unknown': 1, 'restricted': 3.

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.

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

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

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

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

A flag to indicate whether destination notifications notifications have been suppressed in the current time interval specified by the cgrtDestNotifWindowTime object. 'true' Indicates that the device has suppressed the sending of ciscoGrtDestStateChange notifications for the remainder of the time interval. 'false' Indicates that the device has not suppressed the sending of ciscoGrtDestStateChange notifications in the current time interval.

This object contains a list of destination state changes accumulated until the list is full or the time interval specified in cgrtDestNotifDelayTime has passed. It consists of one or more tuples packed together in the format of '...'. Each tuple consist of 36 octets in the following format. ' 20 octets null padded 4 octets 4 octets 4 octets 4 octets The cgrtRouteDpc, cgrtRouteMask cgrtDestStatus, cgrtDestCongestion and cgrtDestAdminState are encoded in network byte order. The maximum number of tuples is 7.

A flag to indicate whether management route notifications have been suppressed in the current time interval specified by the cgrtMgmtNotifWindowTime object. 'true' Indicates that the device has suppressed the sending of ciscoGrtDestStateChange notifications for the remainder of the time interval. 'false' Indicates that the device has not suppressed the sending of ciscoGrtMgmtStateChange notifications in the current time interval.

This object contains a list of management route state changes accumulated until the list is full or the time interval specified in cgrtMgmtNotifDelayTime has passed. It consists of one or more tuples packed together in the format of '...'. Each tuple consist of 68 octets in the following format. ' 20 octets null padded 4 octets 4 octets 4 octets 20 octets null padded 4 octets 4 octets 4 octets 4 octets' The cgrtRouteDpc, cgrtRouteMask, cgrtRouteDestLsCost, cgrtRouteStatus, cgrtRouteMgmtStatus, cgrtRouteDynamic and cgrtRouteAdminStatus are encoded in network byte order. The maximum number of tuples is 3.

Number of ciscoGrtDestStateChangeRev1 notifications suppressed for the specific cgrtDestNotifWindowTimeRev1 duration.

Number of ciscoGrtMgmtStateChangeRev1 notifications suppressed for the specific cgrtRouteNotifWindowTimeRev1 duration.

Duration elapsed since the start of cgrtNoRouteMSUsNotifWindowTime interval. This duration value can range from 0 upto cgrtNoRouteMSUsNotifWindowTime. For the notifications generated at the end of the interval, this value will be equal to cgrtNoRouteMSUsNotifWindowTime.

Number of MSUs discarded due to routing data error in this specific cgspNoRouteMSUsInterval interval.

The origination table provides information on the incoming MTP packets from a particular origination point code.

Each table entry represents a specific origination point code(OPC).

The origination point code.

The number of incoming MSUs from this origination.

The number of incoming octets from this origination.

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

The Destination Service Indicator table contains information about the number of MSUs and octets at the MTP3 transport layer for a specific destination and service indicator. The information is collected from both directions. This provides the granularity of information required by Q752 table 6.

Each table entry represents a specific destination point code(DPC) and Service Indicator(SI).

The service indicator.

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.

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.

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

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

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

The Origination Service Indicator table contains information about the number of incoming MSUs and octets at the MTP3 transport layer from a specific origination and service indicator. This provides the granularity of information required by Q752 table 6.

Each table entry represents a specific origination point code(OPC) and Service Indicator(SI).

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

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

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

The compliance statement for entities which implement the Cisco CISCO-ITP-GRT-MIB.my MIB

The compliance statement for entities which implement the Cisco CISCO-ITP-GRT-MIB.my MIB

SS7 route instance group.

SS7 Destination group.

SS7 Route group.

Gateway route notification objects.

Scalars Group for Gateway Signalling Point Route Table.

SS7 Destination group.

SS7 Route group.

SS7 Origination group.

SS7 Destination and Service Indicator group.

SS7 Destination and Service Indicator group.

Gateway route notification objects.

Additional Inst table objects.