Reference record for OID 1.3.6.1.4.1.9.9.228

Parent
1.3.6.1.4.1.9.9 (ciscoMgmt)
Node code
228
Node name
ciscoItpRtMIB
Numeric OID
1.3.6.1.4.1.9.9.228
URN notation
urn:oid:1.3.6.1.4.1.9.9.228
Type
OBJECT IDENTIFIER
ASN.1 notation

{1 3 6 1 4 1 9 9 228}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cisco(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) me1200(9) ciscoMgmt(9) ciscoItpRtMIB(228)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/9/9/228
  • /ISO/Identified-Organization/6/1/4/1/9/9/228
  • /ISO/3/6/1/4/1/9/9/228
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/me1200/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/enterprises/Cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/me1200/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/me1200/ciscoMgmt/ciscoItpRtMIB
  • /iso/identified-organization/dod/internet/private/vendor-objects/Cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/org/dod/internet/private/enterprise/me1200/ciscoMgmt/ciscoItpRtMIB
  • /iso/org/dod/internet/private/enterprise/Cisco/ciscoMgmt/ciscoItpRtMIB
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoItpRtMIB
  • Additional combinations skipped.

Descriptions

Descriptions may differ between sources. The primary description is shown first.

Primary description: Circitor

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

| |
| STP1-STP3 STP2-STP4 |
| |

- STP3


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
|
|
- -
- -
- SSP1 -
- -
- -
| SSP1-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 entrys 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 entrys 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 entrys 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

Parsed from file CISCO-ITP-RT-MIB.mib
Module: CISCO-ITP-RT-MIB

Alternative description: Cisco

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

| |
| STP1-STP3 STP2-STP4 |
| |

- STP3


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
|
|
- -
- -
- SSP1 -
- -
- -
| SSP1-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 entrys 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 entrys 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 entrys 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

Alternative description: MIBdepot

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

| |
| STP1-STP3 STP2-STP4 |
| |

- STP3


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
|
|
- -
- -
- SSP1 -
- -
- -
| SSP1-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 entrys 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 entrys 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 entrys 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

ciscoItpRtMIB — Circitor, Cisco, Cisco MIB copies (LibreNMS/Observium Community), MIBdepot, Netdisco MIB archive copies

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 entrys 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 entrys 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 entrys 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

Source records

ciscoItpRtMIB

Status in source: unspecified.

Names: ciscoItpRtMIB

Technical details
{
  "smi_kind": "MODULE-IDENTITY",
  "definition": [
    "ciscoItpRtMIB",
    "MODULE-IDENTITY",
    "LAST-UPDATED",
    [
      "literal",
      "223230303330373130303030305a22"
    ],
    "ORGANIZATION",
    "\"Cisco Systems, Inc.\"",
    "CONTACT-INFO",
    "\" Cisco Systems, Inc Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ss7s@cisco.com\"",
    "DESCRIPTION",
    "\"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 entrys 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 entrys 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 entrys 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 \"",
    "REVISION",
    [
      "literal",
      "223230303330373130303030305a22"
    ],
    "DESCRIPTION",
    "\"Updated description to provide overview and additional information. The ability to allow multiple instances of Signalling Points to run in the same device has introduce a new index structure. All objects in this MIB will be deprecated and replaced by objects in the CISCO-ITP-GACT-MIB.my MIB.\"",
    "REVISION",
    [
      "literal",
      "223230303230313037303030305a22"
    ],
    "DESCRIPTION",
    "\"The following objects were added to provide information on time and status of route table loads using the file format. cItpRtConfigLoad cItpRtConfigLoadStatus The following objects were added to provide information on route state changes. cItpRtStateChangeCount cItpRtStateChangeNotifEnabled cItpRtMaxDynamicRoutes cItpRtChangeNotifWindowTime cItpRtChangeNotifMaxPerWindow cItpRtNotifInfoSuppressedFlag cItpRtNotifInfoStateChanges cItpRouteStateChange\"",
    "REVISION",
    [
      "literal",
      "223230303130383239303030305a22"
    ],
    "DESCRIPTION",
    "\"Initial version of this MIB module.\"",
    "::=",
    "{",
    "ciscoMgmt",
    "228",
    "}"
  ],
  "syntax_tree": [
    [
      "LAST-UPDATED",
      "200307100000Z"
    ],
    [
      "ORGANIZATION",
      "Cisco Systems, Inc."
    ],
    [
      "CONTACT-INFO",
      "Cisco Systems, Inc Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-ss7s@cisco.com"
    ],
    [
      "DESCRIPTION",
      "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 entrys 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 entrys 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 entrys 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"
    ],
    [
      "Revisions",
      [
        [
          "200307100000Z",
          [
            "DESCRIPTION",
            "Updated description to provide overview and additional information. The ability to allow multiple instances of Signalling Points to run in the same device has introduce a new index structure. All objects in this MIB will be deprecated and replaced by objects in the CISCO-ITP-GACT-MIB.my MIB."
          ]
        ],
        [
          "200201070000Z",
          [
            "DESCRIPTION",
            "The following objects were added to provide information on time and status of route table loads using the file format. cItpRtConfigLoad cItpRtConfigLoadStatus The following objects were added to provide information on route state changes. cItpRtStateChangeCount cItpRtStateChangeNotifEnabled cItpRtMaxDynamicRoutes cItpRtChangeNotifWindowTime cItpRtChangeNotifMaxPerWindow cItpRtNotifInfoSuppressedFlag cItpRtNotifInfoStateChanges cItpRouteStateChange"
          ]
        ],
        [
          "200108290000Z",
          [
            "DESCRIPTION",
            "Initial version of this MIB module."
          ]
        ]
      ]
    ]
  ]
}
  • Cisco · Publisher's source file: CISCO-ITP-RT-MIB.my

    Module: CISCO-ITP-RT-MIB

    Published definition
    ciscoItpRtMIB MODULE-IDENTITY
            LAST-UPDATED    "200307100000Z"
            ORGANIZATION    "Cisco Systems, Inc."
            CONTACT-INFO
                    "       Cisco Systems, Inc
                            Customer Service
    
                    Postal: 170 W. Tasman Drive
                            San Jose, CA  95134
                            USA
    
                       Tel: +1 800 553-NETS
    
                    E-mail: cs-ss7s@cisco.com"
            DESCRIPTION
              "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 entrys 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 entrys 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 entrys 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
               "
               
            REVISION        "200307100000Z"
            DESCRIPTION
                    "Updated description to provide overview and 
                     additional information. 
                     
                     The ability to allow multiple instances of 
                     Signalling Points to run in the same device
                     has introduce a new index structure.  All
                     objects in this MIB will be deprecated and 
                     replaced by objects in the CISCO-ITP-GACT-MIB.my
                     MIB."
                     
                         
            REVISION        "200201070000Z"
            DESCRIPTION
                    "The following objects were added to provide information
                     on time and status of route table loads using the 
                     file format.
                     
                         cItpRtConfigLoad 
                         cItpRtConfigLoadStatus
                         
                     The following objects were added to provide 
                     information on route state changes.
                         
                         cItpRtStateChangeCount
                         cItpRtStateChangeNotifEnabled
                         cItpRtMaxDynamicRoutes
                         cItpRtChangeNotifWindowTime
                         cItpRtChangeNotifMaxPerWindow
                         cItpRtNotifInfoSuppressedFlag 
                         cItpRtNotifInfoStateChanges   
                         cItpRouteStateChange"
                    
            REVISION        "200108290000Z"
            DESCRIPTION
                    "Initial version of this MIB module."
            ::= { ciscoMgmt 228 }
    Module imports
    {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CISCO-ITP-TC-MIB': ['CItpTcLinksetId', 'CItpTcPointCode', 'CItpTcQos', 'CItpTcRouteTableName', 'CItpTcTableLoadStatus']}
    · Download CISCO-ITP-RT-MIB.my
    Source location: CISCO-ITP-RT-MIB::ciscoItpRtMIB.
    Source version and references

    Downloaded: 2026-10-19T00:18:11.630969+00:00.

  • Preserved mibdepot archive

    Module: CISCO-ITP-RT-MIB

    Published definition
    ciscoItpRtMIB MODULE-IDENTITY
            LAST-UPDATED    "200307100000Z"
            ORGANIZATION    "Cisco Systems, Inc."
            CONTACT-INFO
                    "       Cisco Systems, Inc
                            Customer Service
    
                    Postal: 170 W. Tasman Drive
                            San Jose, CA  95134
                            USA
    
                       Tel: +1 800 553-NETS
    
                    E-mail: cs-ss7s@cisco.com"
            DESCRIPTION
              "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 entrys 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 entrys 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 entrys 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
               "
               
            REVISION        "200307100000Z"
            DESCRIPTION
                    "Updated description to provide overview and 
                     additional information. 
                     
                     The ability to allow multiple instances of 
                     Signalling Points to run in the same device
                     has introduce a new index structure.  All
                     objects in this MIB will be deprecated and 
                     replaced by objects in the CISCO-ITP-GACT-MIB.my
                     MIB."
                     
                         
            REVISION        "200201070000Z"
            DESCRIPTION
                    "The following objects were added to provide information
                     on time and status of route table loads using the 
                     file format.
                     
                         cItpRtConfigLoad 
                         cItpRtConfigLoadStatus
                         
                     The following objects were added to provide 
                     information on route state changes.
                         
                         cItpRtStateChangeCount
                         cItpRtStateChangeNotifEnabled
                         cItpRtMaxDynamicRoutes
                         cItpRtChangeNotifWindowTime
                         cItpRtChangeNotifMaxPerWindow
                         cItpRtNotifInfoSuppressedFlag 
                         cItpRtNotifInfoStateChanges   
                         cItpRouteStateChange"
                    
            REVISION        "200108290000Z"
            DESCRIPTION
                    "Initial version of this MIB module."
            ::= { ciscoMgmt 228 }
    Module imports
    {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CISCO-ITP-TC-MIB': ['CItpTcLinksetId', 'CItpTcPointCode', 'CItpTcQos', 'CItpTcRouteTableName', 'CItpTcTableLoadStatus']}
    · Download CISCO-ITP-RT-MIB.my.txt
    Source location: CISCO-ITP-RT-MIB::ciscoItpRtMIB.
    Source version and references

    Archived: 2026-10-19T00:22:08.313497+00:00.

  • Preserved circitor archive

    Module: CISCO-ITP-RT-MIB

    Published definition
    ciscoItpRtMIB MODULE-IDENTITY
            LAST-UPDATED    "200307100000Z"
            ORGANIZATION    "Cisco Systems, Inc."
            CONTACT-INFO
                    "       Cisco Systems, Inc
                            Customer Service
    
                    Postal: 170 W. Tasman Drive
                            San Jose, CA  95134
                            USA
    
                       Tel: +1 800 553-NETS
    
                    E-mail: cs-ss7s@cisco.com"
            DESCRIPTION
              "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 entrys 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 entrys 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 entrys 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
               "
               
            REVISION        "200307100000Z"
            DESCRIPTION
                    "Updated description to provide overview and 
                     additional information. 
                     
                     The ability to allow multiple instances of 
                     Signalling Points to run in the same device
                     has introduce a new index structure.  All
                     objects in this MIB will be deprecated and 
                     replaced by objects in the CISCO-ITP-GACT-MIB.my
                     MIB."
                     
                         
            REVISION        "200201070000Z"
            DESCRIPTION
                    "The following objects were added to provide information
                     on time and status of route table loads using the 
                     file format.
                     
                         cItpRtConfigLoad 
                         cItpRtConfigLoadStatus
                         
                     The following objects were added to provide 
                     information on route state changes.
                         
                         cItpRtStateChangeCount
                         cItpRtStateChangeNotifEnabled
                         cItpRtMaxDynamicRoutes
                         cItpRtChangeNotifWindowTime
                         cItpRtChangeNotifMaxPerWindow
                         cItpRtNotifInfoSuppressedFlag 
                         cItpRtNotifInfoStateChanges   
                         cItpRouteStateChange"
                    
            REVISION        "200108290000Z"
            DESCRIPTION
                    "Initial version of this MIB module."
            ::= { ciscoMgmt 228 }
    Module imports
    {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CISCO-ITP-TC-MIB': ['CItpTcLinksetId', 'CItpTcPointCode', 'CItpTcQos', 'CItpTcRouteTableName', 'CItpTcTableLoadStatus']}
    · Download CISCO-ITP-RT-MIB.mib
    Source location: CISCO-ITP-RT-MIB::ciscoItpRtMIB.
    Source version and references

    Archived: 2026-10-19T00:22:15.917368+00:00.

  • Cisco MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. Cisco support.

    Module: CISCO-ITP-RT-MIB

    Published definition
    ciscoItpRtMIB MODULE-IDENTITY
            LAST-UPDATED    "200307100000Z"
            ORGANIZATION    "Cisco Systems, Inc."
            CONTACT-INFO
                    "       Cisco Systems, Inc
                            Customer Service
    
                    Postal: 170 W. Tasman Drive
                            San Jose, CA  95134
                            USA
    
                       Tel: +1 800 553-NETS
    
                    E-mail: cs-ss7s@cisco.com"
            DESCRIPTION
              "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 entrys 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 entrys 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 entrys 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
               "
               
            REVISION        "200307100000Z"
            DESCRIPTION
                    "Updated description to provide overview and 
                     additional information. 
                     
                     The ability to allow multiple instances of 
                     Signalling Points to run in the same device
                     has introduce a new index structure.  All
                     objects in this MIB will be deprecated and 
                     replaced by objects in the CISCO-ITP-GACT-MIB.my
                     MIB."
                     
                         
            REVISION        "200201070000Z"
            DESCRIPTION
                    "The following objects were added to provide information
                     on time and status of route table loads using the 
                     file format.
                     
                         cItpRtConfigLoad 
                         cItpRtConfigLoadStatus
                         
                     The following objects were added to provide 
                     information on route state changes.
                         
                         cItpRtStateChangeCount
                         cItpRtStateChangeNotifEnabled
                         cItpRtMaxDynamicRoutes
                         cItpRtChangeNotifWindowTime
                         cItpRtChangeNotifMaxPerWindow
                         cItpRtNotifInfoSuppressedFlag 
                         cItpRtNotifInfoStateChanges   
                         cItpRouteStateChange"
                    
            REVISION        "200108290000Z"
            DESCRIPTION
                    "Initial version of this MIB module."
            ::= { ciscoMgmt 228 }
    Module imports
    {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CISCO-ITP-TC-MIB': ['CItpTcLinksetId', 'CItpTcPointCode', 'CItpTcQos', 'CItpTcRouteTableName', 'CItpTcTableLoadStatus']}
    · Download CISCO-ITP-RT-MIB

    Related source files and packages:


    Source location: CISCO-ITP-RT-MIB::ciscoItpRtMIB.
    Source version and references

    Downloaded: 2026-10-24T02:14:08.411393+00:00.

  • Netdisco MIB archive copies · Publisher's source file: CISCO-ITP-RT-MIB.my

    Vendor MIB copy from the Netdisco archive.

    Module: CISCO-ITP-RT-MIB

    Published definition
    ciscoItpRtMIB MODULE-IDENTITY
            LAST-UPDATED    "200307100000Z"
            ORGANIZATION    "Cisco Systems, Inc."
            CONTACT-INFO
                    "       Cisco Systems, Inc
                            Customer Service
    
                    Postal: 170 W. Tasman Drive
                            San Jose, CA  95134
                            USA
    
                       Tel: +1 800 553-NETS
    
                    E-mail: cs-ss7s@cisco.com"
            DESCRIPTION
              "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 entrys 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 entrys 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 entrys 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
               "
               
            REVISION        "200307100000Z"
            DESCRIPTION
                    "Updated description to provide overview and 
                     additional information. 
                     
                     The ability to allow multiple instances of 
                     Signalling Points to run in the same device
                     has introduce a new index structure.  All
                     objects in this MIB will be deprecated and 
                     replaced by objects in the CISCO-ITP-GACT-MIB.my
                     MIB."
                     
                         
            REVISION        "200201070000Z"
            DESCRIPTION
                    "The following objects were added to provide information
                     on time and status of route table loads using the 
                     file format.
                     
                         cItpRtConfigLoad 
                         cItpRtConfigLoadStatus
                         
                     The following objects were added to provide 
                     information on route state changes.
                         
                         cItpRtStateChangeCount
                         cItpRtStateChangeNotifEnabled
                         cItpRtMaxDynamicRoutes
                         cItpRtChangeNotifWindowTime
                         cItpRtChangeNotifMaxPerWindow
                         cItpRtNotifInfoSuppressedFlag 
                         cItpRtNotifInfoStateChanges   
                         cItpRouteStateChange"
                    
            REVISION        "200108290000Z"
            DESCRIPTION
                    "Initial version of this MIB module."
            ::= { ciscoMgmt 228 }
    Module imports
    {'CISCO-SMI': ['ciscoMgmt'], 'SNMPv2-TC': ['TimeStamp', 'TruthValue'], 'SNMPv2-SMI': ['Counter32', 'Integer32', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'NOTIFICATION-GROUP', 'OBJECT-GROUP'], 'CISCO-ITP-TC-MIB': ['CItpTcLinksetId', 'CItpTcPointCode', 'CItpTcQos', 'CItpTcRouteTableName', 'CItpTcTableLoadStatus']}
    · Download CISCO-ITP-RT-MIB.my

    Related source files and packages:


    Source location: CISCO-ITP-RT-MIB::ciscoItpRtMIB.
    Source version and references

    Downloaded: 2026-10-24T15:28:09.178010+00:00.

Information from Circitor

ciscoItpRtMIB MODULE-IDENTITY
        LAST-UPDATED    "200307100000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "       Cisco Systems, Inc
                        Customer Service

                Postal: 170 W. Tasman Drive
                        San Jose, CA  95134
                        USA

                   Tel: +1 800 553-NETS

                E-mail: cs-ss7s@cisco.com"
        DESCRIPTION
          "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  
             
                 |                                   |
                 | STP1-STP3               STP2-STP4 |
                 |                                   |
             
             - STP3  
             
           
           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             
                |
                |                        
               - - 
             -     -
            -  SSP1 -  
             -     -
               - - 
                |  SSP1-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 entrys 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 entrys 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 entrys 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
           "
           
        REVISION        "200307100000Z"
        DESCRIPTION
                "Updated description to provide overview and 
                 additional information. 
                 
                 The ability to allow multiple instances of 
                 Signalling Points to run in the same device
                 has introduce a new index structure.  All
                 objects in this MIB will be deprecated and 
                 replaced by objects in the CISCO-ITP-GACT-MIB.my
                 MIB."
                 
                     
        REVISION        "200201070000Z"
        DESCRIPTION
                "The following objects were added to provide information
                 on time and status of route table loads using the 
                 file format.
                 
                     cItpRtConfigLoad 
                     cItpRtConfigLoadStatus
                     
                 The following objects were added to provide 
                 information on route state changes.
                     
                     cItpRtStateChangeCount
                     cItpRtStateChangeNotifEnabled
                     cItpRtMaxDynamicRoutes
                     cItpRtChangeNotifWindowTime
                     cItpRtChangeNotifMaxPerWindow
                     cItpRtNotifInfoSuppressedFlag 
                     cItpRtNotifInfoStateChanges   
                     cItpRouteStateChange"
                
        REVISION        "200108290000Z"
        DESCRIPTION
                "Initial version of this MIB module."
        ::= { ciscoMgmt 228 }

Information from Cisco SMIv1

Source file: Download CISCO-ITP-RT-MIB-V1SMI.my · Publisher's file

Publisher path: cisco/cisco-mibs/main/v1/CISCO-ITP-RT-MIB-V1SMI.my; 24,211 bytes

Source file: Download CISCO-ITP-RT-MIB-V1SMI.my.txt

File: cisco/CISCO-ITP-RT-MIB-V1SMI.my.txt; 24,916 bytes

ciscoItpRtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 228 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-ITP-RT-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

ciscoItpRtMIB MODULE-IDENTITY
        LAST-UPDATED    "200307100000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "       Cisco Systems, Inc
                        Customer Service

                Postal: 170 W. Tasman Drive
                        San Jose, CA  95134
                        USA

                   Tel: +1 800 553-NETS

                E-mail: cs-ss7s@cisco.com"
        DESCRIPTION
          "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  
             
                 |                                   |
                 | STP1-STP3               STP2-STP4 |
                 |                                   |
             
             - STP3  
             
           
           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             
                |
                |                        
               - - 
             -     -
            -  SSP1 -  
             -     -
               - - 
                |  SSP1-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 entrys 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 entrys 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 entrys 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
           "
           
        REVISION        "200307100000Z"
        DESCRIPTION
                "Updated description to provide overview and 
                 additional information. 
                 
                 The ability to allow multiple instances of 
                 Signalling Points to run in the same device
                 has introduce a new index structure.  All
                 objects in this MIB will be deprecated and 
                 replaced by objects in the CISCO-ITP-GACT-MIB.my
                 MIB."
                 
                     
        REVISION        "200201070000Z"
        DESCRIPTION
                "The following objects were added to provide information
                 on time and status of route table loads using the 
                 file format.
                 
                     cItpRtConfigLoad 
                     cItpRtConfigLoadStatus
                     
                 The following objects were added to provide 
                 information on route state changes.
                     
                     cItpRtStateChangeCount
                     cItpRtStateChangeNotifEnabled
                     cItpRtMaxDynamicRoutes
                     cItpRtChangeNotifWindowTime
                     cItpRtChangeNotifMaxPerWindow
                     cItpRtNotifInfoSuppressedFlag 
                     cItpRtNotifInfoStateChanges   
                     cItpRouteStateChange"
                
        REVISION        "200108290000Z"
        DESCRIPTION
                "Initial version of this MIB module."
        ::= { ciscoMgmt 228 }

Information from Cisco

ciscoItpRtMIB MODULE-IDENTITY
        LAST-UPDATED    "200307100000Z"
        ORGANIZATION    "Cisco Systems, Inc."
        CONTACT-INFO
                "       Cisco Systems, Inc
                        Customer Service

                Postal: 170 W. Tasman Drive
                        San Jose, CA  95134
                        USA

                   Tel: +1 800 553-NETS

                E-mail: cs-ss7s@cisco.com"
        DESCRIPTION
          "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  
             
                 |                                   |
                 | STP1-STP3               STP2-STP4 |
                 |                                   |
             
             - STP3  
             
           
           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             
                |
                |                        
               - - 
             -     -
            -  SSP1 -  
             -     -
               - - 
                |  SSP1-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 entrys 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 entrys 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 entrys 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
           "
           
        REVISION        "200307100000Z"
        DESCRIPTION
                "Updated description to provide overview and 
                 additional information. 
                 
                 The ability to allow multiple instances of 
                 Signalling Points to run in the same device
                 has introduce a new index structure.  All
                 objects in this MIB will be deprecated and 
                 replaced by objects in the CISCO-ITP-GACT-MIB.my
                 MIB."
                 
                     
        REVISION        "200201070000Z"
        DESCRIPTION
                "The following objects were added to provide information
                 on time and status of route table loads using the 
                 file format.
                 
                     cItpRtConfigLoad 
                     cItpRtConfigLoadStatus
                     
                 The following objects were added to provide 
                 information on route state changes.
                     
                     cItpRtStateChangeCount
                     cItpRtStateChangeNotifEnabled
                     cItpRtMaxDynamicRoutes
                     cItpRtChangeNotifWindowTime
                     cItpRtChangeNotifMaxPerWindow
                     cItpRtNotifInfoSuppressedFlag 
                     cItpRtNotifInfoStateChanges   
                     cItpRouteStateChange"
                
        REVISION        "200108290000Z"
        DESCRIPTION
                "Initial version of this MIB module."
        ::= { ciscoMgmt 228 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.228.0 cItpRouteNotifications11
1.3.6.1.4.1.9.9.228.1 cItpRtMIBObjects335
1.3.6.1.4.1.9.9.228.2 cItpRtMIBConformance28

Siblings (706)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.181 ciscoWirelessLinkMetricsMIB4141 This is the MIB Module for the Cisco Wireless Radio
Point to MultiPoint interface link metrics
specification.

Glossary

The followin…
1.3.6.1.4.1.9.9.183 ciscoGprsAccPtMIB3338 This MIB module supports access point configuration
for GGSN in a GPRS system. GPRS [1] is a GSM network
providing mobile wireles…
1.3.6.1.4.1.9.9.184 ciscoPimMIB336 This MIB module defines the cisco specific variables
for Protocol Independent Multicast (PIM) management.
These definitions are a…
1.3.6.1.4.1.9.9.185 ciscoBertMIB246 The MIB module to configure and perform Bit Error Rate Testing
(BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces.
Bit error rate…
1.3.6.1.4.1.9.9.187 ciscoBgp4MIB4170 An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Proto…
1.3.6.1.4.1.9.9.188 cGtpMIB3248 This MIB module manages the GPRS Tunnelling Protocol
(GTP) on GGSN and SGSN.

GPRS provides wireless access to packet data network…
1.3.6.1.4.1.9.9.189 ciscoPortQosMIB3114 Cisco PORT QOS MIB - Overview

This MIB module is for the management of Cisco's
per port rate-limiting and traffic shaping on L3
sw…
1.3.6.1.4.1.9.9.190 ciscoVoiceAppsMIB340 The MIB Module for the management of Cisco Voice
Applications. This MIB is designed to work in
conjunction with the SYSAPPL-MIB …
1.3.6.1.4.1.9.9.191 ciscoIpUplinkRedirectMIB311 This MIB module is for the configuration of
Cisco IP Uplink Redirect feature.
1.3.6.1.4.1.9.9.192 ciscoGprsChargingMIB3315 This MIB module manages the charging related
function on the GGSN node of a GPRS system.

The following diagram illustrates a simp…
1.3.6.1.4.1.9.9.194 ciscoPppoeMIB389 Cisco PPPoE sessions management MIB Module.
1.3.6.1.4.1.9.9.195 ciscoEntityExtMIB370 This MIB is an extension of the ENTITY-MIB
specified in RFC2737.

This MIB module contains Cisco-defined extensions
to the entit…
1.3.6.1.4.1.9.9.197 ciscoDistDirMIB3123 Cisco Distributed Director MIB.

The Cisco Distributed Director provides global Internet
scalability and increased performance as …
1.3.6.1.4.1.9.9.198 ciscoRfSupMIB365 This MIB was designed to complement the CISCO-RF-MIB by
providing additional optional status and configuration control
for redund…
1.3.6.1.4.1.9.9.199 ciscoSmFileDownloadMIB323 The MIB module for downloading files to the Service
Modules specifically designed for an architecture
containing a controller car…
1.3.6.1.4.1.9.9.201 ciscoSwitchUsageMIB315 This MIB defines objects related to statistics
for the usage of switch fabric. The switch fabric
is used by the incoming packets …
1.3.6.1.4.1.9.9.202 ciscoOscpMIB352 The MIB module for managing the Cisco Optical
Supervisory Channel Protocol (OSCP). The OSCP is used
to determine and maintain wav…
1.3.6.1.4.1.9.9.204 ciscoXdslLineMIB232 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
different t…
1.3.6.1.4.1.9.9.215 ciscoMacNotificationMIB372 This MIB module is for configuration of the MAC notification
feature. MAC notification is a mechanism to inform monitoring
device…
1.3.6.1.4.1.9.9.216 ciscoContentNetworkMIB334 This MIB module defines objects for Content Network devices.

A Content Network is a collection of devices that optimizes the
deli…
1.3.6.1.4.1.9.9.217 ciscoCat6kCrossbarMIB3210 The Catalyst 6000 Crossbar MIB provides instrumentation for
configuration and operation of the crossbar switching fabric
module, …
1.3.6.1.4.1.9.9.218 ciscoIfThresholdMIB365 ciscoIfthresholdMIB
1.3.6.1.4.1.9.9.219 ciscoVoiceDnisMIB324 The MIB module provides management support for Dialer
Number Information Service (DNIS) mapping. A DNIS
entry is associated with…
1.3.6.1.4.1.9.9.220 ciscoPaeMIB3231 Cisco Port Access Entity (PAE) module for managing
IEEE Std 802.1x.

This MIB provides Port Access Entity information
that are eith…
1.3.6.1.4.1.9.9.221 ciscoEnhancedMemPoolMIB387 New MIB module for monitoring the memory pools
of all physical entities on a managed system.
1.3.6.1.4.1.9.9.222 ciscoEnhancedWredMIB370 Cisco WRED MIB - Overview
Cisco Weighted Random Early Detection/Drop (WRED)
is a method which avoids traffic congestion on an
outp…
1.3.6.1.4.1.9.9.223 ciscoWanNcdpMIB358 This MIB module is intended for the management of network clock
distribution and the Network Clock Distribution Protocol (NCDP)
i…
1.3.6.1.4.1.9.9.224 ciscoDevExcepReportMIB329 This mib defines the SNMP objects to report
exceptions to north-bound NMS.

The devices implementing this MIB monitor
the status of…
1.3.6.1.4.1.9.9.225 ciscoLagMIB356 Cisco Link Aggregation module for managing IEEE Std
802.3ad.

This MIB provides Link Aggregation information that are
either exclud…
1.3.6.1.4.1.9.9.226 ciscoNDEMIB417 The Netflow Data Export (NDE) MIB provides instrumentation for
configuration and operation of the Netflow Data Export feature.

A …
1.3.6.1.4.1.9.9.227 ciscoItpAclMIB345 The MIB for managing access lists that control
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP Trans…
1.3.6.1.4.1.9.9.229 ciscoDs1ExtMIB2129 The MIB module to describe DS1/E1 interface objects. This is
an extension to the standard DS1/E1 MIB (RFC 2495).

Unless mentioned…
1.3.6.1.4.1.9.9.230 ciscoItpActMIB329 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signalling System No. 7(SS7) Network.
This…
1.3.6.1.4.1.9.9.231 ciscoItpTextualConventions00 The defines textual conventions used by to manage
devices related to the SS7 network. The
relevant ITU documents describing this…
1.3.6.1.4.1.9.9.232 ciscoItpSpMIB3384 The MIB for managing Signalling Points and its
associated messages transported over Signalling
System No. 7 (SS7) Network via Ci…
1.3.6.1.4.1.9.9.233 ciscoItpSccpMIB3194 The MIB for Signaling Connection Control Part(SCCP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP …
1.3.6.1.4.1.9.9.234 ciscoWanTopologyMIB383 A management station can use this MIB module for the
maintenance of persistent topology information of the
PNNI network. Previous…
1.3.6.1.4.1.9.9.235 ciscoImaMIB260 The MIB module describes Cisco IMA objects.
This is an extension to the standard of
ATM Forum IMA version 1.1, AF-PHY-0086.001
Spe…
1.3.6.1.4.1.9.9.236 ciscoWanSctMgmtMIB218 MIB module to manage SCT files in a node.

SCTs (Service Class Templates) are nodal configuration files,
which define the traffic …
1.3.6.1.4.1.9.9.237 ciscoNmsApplHealthMIB339 This MIB defines Cisco NMS Application (cna) Health
Status Notifications and the related objects. These
notifications will be sen…
1.3.6.1.4.1.9.9.238 ciscoIGMPFilterMIB245 IGMP Filter configuration MIB. This MIB provides a
mechanism for users to configure the system to intercept
IGMP joins for IP Mul…
1.3.6.1.4.1.9.9.240 cGgsnMIB3389 This MIB module manages the Gateway GPRS Support
Node (GGSN) devices.

A GGSN device provides interworking with external
packet-dat…
1.3.6.1.4.1.9.9.241 cggsnQosMIB289 This MIB module manages the Quality of Service
parameters of GGSN in a GPRS system.

GGSN is the Gateway GPRS Support Node in the …
1.3.6.1.4.1.9.9.242 ciscoCableAvailabilityMIB360 This is the MIB module for management of Hot Standby
Connection to Connection Protocol (HCCP) features. HCCP is
a Cisco proprieta…
1.3.6.1.4.1.9.9.243 ciscoHealthMonitorMIB322 Health Monitor MIB module.

The Health Monitor uses a model based on events of varying
severity and frequency, and predefined rule…
1.3.6.1.4.1.9.9.244 ciscoNbarProtocolDiscoveryMIB384 Cisco NBAR Protocol Discovery MIB

NBAR - Network Based Application Recognition is
an intelligent classification engine that reco…
1.3.6.1.4.1.9.9.245 ciscoGtpDirectorMIB335 This MIB module defines objects that are used to
manage GTP Director Module.

In the GPRS network, the APN is the identifier that
s…
1.3.6.1.4.1.9.9.246 ciscoL2TunnelConfigMIB365 This MIB module is for layer 2 tunneling related configurations
on a device.

Tunneling allows separate local networks to be consi…
1.3.6.1.4.1.9.9.248 ciscoItpSp2MIB330 The MIB for providing information specified
in ITU Q752 Monitoring and Measurements for
Signaling System No. 7(SS7) Network.
This …
1.3.6.1.4.1.9.9.249 ciscoEnhancedImageMIB244 Initial version of the MIB. This MIB has Image table
containing the following information related to the
running IOS image
1. Enti…