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.679 ciscoIeee8021CfmExtMIB355 A MIB module for extending the IEEE8021-CFM-MIB
and IEEE8021-CFM-V2-MIB to add objects which provide
additional information about…
1.3.6.1.4.1.9.9.680 ciscoNhrpExtMIB336 This MIB module is an extension of the NHRP MIB module as
defined in RFC 2677. It defines notifications associated with
critical …
1.3.6.1.4.1.9.9.683 ciscoEnergywiseMIB3162 The MIB is used to manage and optimize power usage
in networks.

Cisco EnergyWise is a specification of data, discovery and
protoco…
1.3.6.1.4.1.9.9.686 ciscoLwappInterfaceMIB361 ciscoLwappInterfaceMIB MODULE-IDENTITY
LAST-UPDATED "200901090000Z"
ORGANIZATION "Cisco Systems Inc."
CONTACT-INFO
"Cisco Syste…
1.3.6.1.4.1.9.9.688 ciscoFlowMonitorTcMIB00 This MIB module defines textual conventions used by the MIB
modules defining objects describing flow monitoring.

GLOSSARY
========…
1.3.6.1.4.1.9.9.689 ciscoSlbDfpMIB322 This MIB reports the congestion status of the real server.
A server can be in congested state due to high memory
consumption, hig…
1.3.6.1.4.1.9.9.690 ciscoMobilePolicyChargingControlMIB3143 Mobile PCC Infrastructure built on top of Policy Shim Layer, is
a common interface to send and receive PCC related messages for
a…
1.3.6.1.4.1.9.9.691 ciscoEthernetFabricExtenderMIB323 The MIB module for configuring one or more fabric
extenders to connect into a core switch. Since fabric
extenders might not be m…
1.3.6.1.4.1.9.9.692 ciscoFlowMonitorMIB4195 This MIB module defines objects that describe flow monitoring.
A typical application of this MIB module will facilitate
monitorin…
1.3.6.1.4.1.9.9.693 ciscoServiceControlAttackMIB355 This MIB provides data related to different types of
attacks detected by a service control entity.

A service control entity is a …
1.3.6.1.4.1.9.9.694 ciscoCtsTcMIB00 This module defines the textual conventions used within
Cisco Trusted Security framework.
1.3.6.1.4.1.9.9.695 ciscoGtcapMIB3194 The MIB for Transaction Capabilities(TCAP)
messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP Transfer
P…
1.3.6.1.4.1.9.9.696 ciscoBootHwDiagsMIB322 This MIB is used to configure those devices that support
boot-time hardware diagnostics. It provides the reports
about the respe…
1.3.6.1.4.1.9.9.697 ciscoIpCbrMetricsMIB442 This MIB module defines objects that describe the a set of
metrics used to measure the quality of a IP CBR traffic flow. An
IP CB…
1.3.6.1.4.1.9.9.698 ciscoObmiMIB360 The On-Board Management Interface (OBMI) provides an
out-of-band communications channel (in Cisco terms:
a console port), that is…
1.3.6.1.4.1.9.9.699 ciscoMdiMetricsMIB446 This MIB module defines objects that describe the Media
Delivery Index (MDI). The MDI [RFC4445] measurement describes
the qualit…
1.3.6.1.4.1.9.9.700 ciscoCableL2vpnMIB328 This MIB module defines managed objects that facilitate
the management of Cisco devices complying to the DOCSIS
L2VPN Feature for…
1.3.6.1.4.1.9.9.701 ciscoSeuMitigationMIB351 This MIB reports the status of non-automatic and automatic,
rate-adaptive Single Event Upset (SEU) mitigation algorithms and
adju…
1.3.6.1.4.1.9.9.702 ciscoSanBaseSvcMIB357 Common MIB module to manage services in Storage Area
Network (SAN). Service is deployed on service
nodes on multiple switches fo…
1.3.6.1.4.1.9.9.703 ciscoRtpMetricsMIB461 This MIB module defines objects that describe the quality
metrics of RTP streams, similar to those described by an RTCP
Receiver …
1.3.6.1.4.1.9.9.706 ciscoInterfaceXcvrMonitorMIB333 A MIB module that provides monitoring information
about the transceivers plugged into interface on a
system.
1.3.6.1.4.1.9.9.708 ciscoContentDeliveryStreamingMIB230 This MIB instrumentation is for managing the Content Delivery
and Streaming functionality on Cisco devices.

Contents are ingested…
1.3.6.1.4.1.9.9.709 ciscoVlanGroupMIB318 MIB module for monitoring and configuring VLAN Group Mapping
information.
1.3.6.1.4.1.9.9.710 ciscoVirtualNicMIB336 This MIB module defines MIB objects which provide
mechanisms to manage the parameters used by or
related to Virtual NIC.

Virtual s…
1.3.6.1.4.1.9.9.711 ciscoVrfMIB348 The MIB module for provisioning and managing network
virtualization features.

This module provides manageability for VRF, VRF-Lit…
1.3.6.1.4.1.9.9.712 ciscoWirelessNotificationMIB330 This MIB is intended to be implemented on those Network
Management applications that manage a network of wireless
devices through…
1.3.6.1.4.1.9.9.713 ciscoTrustSecPolicyMIB3204 This MIB module defines managed objects that facilitate the
management of various policies within the Cisco Trusted Security
(Tru…
1.3.6.1.4.1.9.9.714 ciscoHwModuleControlMIB327 The MIB module providing configuration and control
information for management of hardware modules and
components on Cisco devices…
1.3.6.1.4.1.9.9.715 ciscoEntityQfpMIB382 This MIB module defines managed objects that facilitate the
management of Quantum Flow Processors (QFP), which are listed
in the …
1.3.6.1.4.1.9.9.716 ciscoVoIpTapMIB318 This module manages Cisco's intercept feature for Voice
over IP (VoIP). This MIB is used along with CISCO-TAP2-MIB
to intercept V…
1.3.6.1.4.1.9.9.718 ciscoCuicappsMIB3130 The Cisco Unified Intelligence Center (CUIC) is a scalable
robust and secure reporting solution for contact center
applications.

T…
1.3.6.1.4.1.9.9.719 ciscoUnifiedComputingMIB526787 This MIB module defines the managed objects for
Unified Computing System (UCS) Manager.

Cisco UCS Manager provides centralized m…
1.3.6.1.4.1.9.9.720 ciscoTrustSecSxpMIB3144 This MIB module is for the configuration and status query
of SGT Exchange Protocol over TCP (SXPoTCP) feature of the
device on th…
1.3.6.1.4.1.9.9.721 ciscoMldSnoopingMIB3215 This MIB module defines objects that describe IGMP/MLD
snooping.
It provides remote network management system the ability
to manag…
1.3.6.1.4.1.9.9.724 cggsnGeoMIB212 This MIB provide additional information for passive interface
configured for each OSPF process, independent of object creation
in…
1.3.6.1.4.1.9.9.725 ciscoSmartInstallMIB3101 This MIB module defines managed objects that facilitate the management of Smart Install feature. Smart Install is a plug-and-pl…
1.3.6.1.4.1.9.9.729 ciscoCdstvServicesMIB321 This MIB module defines service monitoring objects that
faciliate the management of the Cisco Content Delivery System
for TV (CDS…
1.3.6.1.4.1.9.9.730 ciscoTrustSecMIB3128 This MIB module is for the configuration of a network
device on the Cisco Trusted Security (TrustSec) system.

TrustSec secures a …
1.3.6.1.4.1.9.9.731 ciscoEpcGatewayMIB3130 This MIB module manages the features and configuration
for PDN Gateway(PGW) and Serving Gateway(SGW) in Evolved
Packet Core(EPC) …
1.3.6.1.4.1.9.9.732 ciscoDeviceLocationMIB349 This MIB is used for managing location information
of end point devices(Telepresence, IP Camera, Digital media
player etc) connec…
1.3.6.1.4.1.9.9.733 ciscoMeetingPlaceMIB370 This MIB allows management of Cisco Unified MeetingPlace (CUMP)
features, CUMP is the key conferencing solution component for
Cis…
1.3.6.1.4.1.9.9.734 ciscoGtpv2MIB2160 This MIB module manages the GPRS Tunneling Protocol
version 2(GTPv2) statistics for the Evolved Packet
Core(EPC) architecture.

SGW…
1.3.6.1.4.1.9.9.735 ciscoCdstvFsiMIB325 This MIB module defines FSI configurartion objects that
faciliate the management of the Cisco Content Delivery System
for TV (CDS…
1.3.6.1.4.1.9.9.736 ciscoRadiusExtMIB252 This MIB module defines objects describing RADIUS (Remote
Access Dialin User Service), serving as an extension of the
following M…
1.3.6.1.4.1.9.9.737 ciscoSwitchNetflowMIB340 This MIB module defines management objects for the
Netflow features on Cisco Layer 2 and Layer 3 devices.
1.3.6.1.4.1.9.9.738 cmplsTeStdExtMIB372 This MIB module contains Cisco specific managed object
definitions for MPLS Traffic Engineering (TE), not contained in
MPLS-TE-ST…
1.3.6.1.4.1.9.9.739 ciscoCdstvIngestmgrMIB369 This MIB module defines ingest manager configuration objects
that faciliate the management of the Cisco Content Delivery
System f…
1.3.6.1.4.1.9.9.740 ciscoTrustSecIfMIB3143 This MIB module defines management objects for
configuration and monitoring of the interfaces in Cisco
Trusted Security environme…
1.3.6.1.4.1.9.9.741 ciscoTrustSecServerMIB385 This MIB module defines management objects for
configuration and monitoring of the AAA servers
in Cisco Trusted Security environm…
1.3.6.1.4.1.9.9.742 ciscoIpAddressPoolTcMIB00 This MIB module defines textual conventions used by MIB
modules defining objects describing IP address pools.