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.445 ciscoQinqVlanMIB325 This MIB defines configuration and monitoring capabilities
relating to 802.1QinQ interfaces. QinQ interfaces are capable
of term…
1.3.6.1.4.1.9.9.447 ciscoScsiFlowMIB399 A SCSI Flow is described as a SCSI Initiator
SCSI Target combination. This MIB is used to
configure and monitor SCSI Flows.

Gloss…
1.3.6.1.4.1.9.9.448 ciscoSsmProvMIB226 This MIB is used to provision features
on a Data Path Processor (DPP) of a Storage Service
Module (SSM). A DPP is assigned to a c…
1.3.6.1.4.1.9.9.449 ciscoEigrpMIB3110 Enhanced Interior Gateway Protocol (EIGRP) is a Cisco
proprietary distance vector routing protocol. It is based on
the Diffusin…
1.3.6.1.4.1.9.9.450 ciscoCableAdmCtrlMIB3123 This MIB module defines the managed objects enabling
the management of Cable Modem Termination System
(CMTS) admission control.

CM…
1.3.6.1.4.1.9.9.451 ciscoIpUrpfMIB347 Unicast Reverse Path Forwarding (URPF) is a function
that checks the validity of the source address of IP
packets received on an …
1.3.6.1.4.1.9.9.454 ciscoDot11LbsMIB323 This MIB module supports network management
for Location Based Services on IEEE 802.11 wireless
LAN devices. Location Based Serv…
1.3.6.1.4.1.9.9.455 ciscoImageTc00 ciscoImageTc MODULE-IDENTITY
LAST-UPDATED "200501120000Z"
ORGANIZATION "Cisco Systems, Inc."
CONTACT-INFO
"Cisco Systems
Custom…
1.3.6.1.4.1.9.9.456 ciscoDot11WidsMIB350 This MIB is intended to be implemented on the
following IOS based network entities for the purpose
of providing network managemen…
1.3.6.1.4.1.9.9.457 ciscoWdsIdsMIB218 This MIB is intended to be implemented on all
IOS based network entities that provide Wireless
Domain Services, for the purpose o…
1.3.6.1.4.1.9.9.458 ciscoApplianceRedundancyMIB347 This mib defines the SNMP objects to report the status of
High Availability (HA) functionality in Cisco network
management applia…
1.3.6.1.4.1.9.9.459 ciscoBitsClockMIB321 This MIB provides information on Building Integrated
Timing Supply(BITS) clocking sources and modes of
operations. It is used to…
1.3.6.1.4.1.9.9.460 ciscoTpcMIB324 The MIB module for Third Party Copy(TPC):
Third Party Copy derives its name from the fact
that there are three entities involved …
1.3.6.1.4.1.9.9.461 ciscoEtherCfmMIB339 This MIB module defines the managed objects
and notifications for Ethernet Connectivity
Fault Management (CFM).

CFM is an end-to-e…
1.3.6.1.4.1.9.9.463 ciscoSanTapMIB330 MIB module to provide information about the SanTap
service configuration.

SanTap is a fibre channel switch based capability that
p…
1.3.6.1.4.1.9.9.466 ciscoEthernetAccessMIB220 The tables defined by this MIB module contain a collection
of managed objects that are general in nature and apply to
an edge dev…
1.3.6.1.4.1.9.9.467 ciscoCryptoAcceleratorMIB3107 The MIB module for monitoring the identity, status,
activity and faults of crypto accelerator (CA) modules
used in devices implem…
1.3.6.1.4.1.9.9.468 ciscoContextMappingMIB235 A single SNMP agent sometimes needs to support multiple
instances of the same MIB module, and does so through the
use of multiple…
1.3.6.1.4.1.9.9.470 ciscoEnhancedSlbMIB3106 The MIB for managing Server Load Balancing
Manager(s), and products supporting Server
Load Balancing(SLB) features.

This MIB exten…
1.3.6.1.4.1.9.9.471 ciscoFlexLinksMIB336 This MIB module is for configuration and status query
of Flex Links feature on the Cisco device.

Flex Links are a pair of Layer 2…
1.3.6.1.4.1.9.9.472 ciscoModuleVirtualizationMIB335 This MIB provides a way to create virtual contexts,
and managing them. A virtual context is logical
partition of a physical devi…
1.3.6.1.4.1.9.9.473 ciscoCcaMIB3200 The Cisco Contact Center Applications (CCCA) Management
Information Base (MIB) module defines management
instrumentation for appl…
1.3.6.1.4.1.9.9.474 ciscoFilterGroupMIB355 The MIB module is for creating and configuring
object groups to support packet filtering and
access control on IP and other proto…
1.3.6.1.4.1.9.9.479 ciscoCableWidebandMIB377 This is the MIB module for the support of Channel Bonding
Protocol for the Cable Modem Termination System (CMTS).

Wideband DOCSIS…
1.3.6.1.4.1.9.9.480 ciscoL4L7moduleResourceLimitMIB4100 The MIB module for managing resource classes
and configuring limits(max/min) to different
resources. The resource referenced in …
1.3.6.1.4.1.9.9.482 ciscoInterfaceTopNExtMIB316 This MIB module is an extension to INTERFACETOPN-MIB.
It provides additional management information for
sorting device interfaces.
1.3.6.1.4.1.9.9.483 ciscoIpRanBackHaulMIB3248 This MIB provides information on the IP-RAN traffic
from cell site to aggregation site in the following
situations. In an GSM en…
1.3.6.1.4.1.9.9.484 ciscoNacNadMIB3157 This MIB module is for the configuration of a Network
Access Device (NAD) on the Cisco Network Admission
Control (NAC) system.

End…
1.3.6.1.4.1.9.9.485 ciscoRttMonTCMIB00 This MIB contains textual conventions used by
CISCO-RTTMON-MIB, CISCO-RTTMON-RTP-MIB and
CISCO-RTTMON-ICMP-MIB, but they are not …
1.3.6.1.4.1.9.9.486 ciscoRttMonIcmpMIB37 An extension to the CISCO-RTTMON-MIB for ICMP
operations. The ICMP Jitter operation provides capability
to measure metrics such a…
1.3.6.1.4.1.9.9.487 ciscoRttMonRtpMIB38 An extension to the CISCO-RTTMON-MIB for Cisco IP SLA
RTP operation, Real-Time Transport Protocol(RFC 1889). This
operation provi…
1.3.6.1.4.1.9.9.488 ciscoFirewallTc00 This MIB module defines textual conventions that
are commonly used in modeling management information
pertaining to configuration…
1.3.6.1.4.1.9.9.490 ciscoNetintMIB311 This MIB module is for Network Interrupt information
on Cisco device.
1.3.6.1.4.1.9.9.491 ciscoUnifiedFirewallMIB3360 Overview of Cisco Firewall MIB
==============================
This MIB Module models status and performance
statistics pertaining …
1.3.6.1.4.1.9.9.492 ciscoCefMIB3192 Cisco Express Forwarding (CEF) describes a high speed
switching mechanism that a router uses to forward packets
from the inbound …
1.3.6.1.4.1.9.9.493 ciscoCefTextualConventions00 ciscoCeftextualConventions
1.3.6.1.4.1.9.9.494 ciscoEntityRedunTcMIB00 This module defines the textual conventions used within
Cisco Entity Redundancy MIBs.
1.3.6.1.4.1.9.9.495 ciscoPsdClientMIB344 This MIB module manages the client side
functionality of the Persistent Storage Device(PSD).

This MIB instrumentation is for conf…
1.3.6.1.4.1.9.9.497 cGgsnSAMIB3247 This MIB module manages the service-aware feature of
Gateway GPRS Support Node (GGSN).

This MIB is an enhancement of the CISCO-GG…
1.3.6.1.4.1.9.9.498 ciscoEntityRedunMIB393 This management information module supports
configuration, control and monitoring of redundancy
protection for various kinds of c…
1.3.6.1.4.1.9.9.500 ciscoStackWiseMIB3111 This MIB module contain a collection of managed objects
that apply to network devices supporting the Cisco
StackWise(TM) technolo…
1.3.6.1.4.1.9.9.504 ciscoSwitchMulticastMIB3108 This MIB module defines management objects for the
Multicast Switching features on Cisco Layer 2/3
devices.

Definition of some of …
1.3.6.1.4.1.9.9.505 cpkiMIB344 A networking device may provide several security services
and protocols like SSL, SSH, IPSec/IKE etc. which need
identities …
1.3.6.1.4.1.9.9.507 ciscoPolicyGroupMIB335 The MIB module is for configuration of policy and
policy group. A policy group can be described as a set
of entities identified b…
1.3.6.1.4.1.9.9.508 ciscoSlbHealthMonMIB362 An extension to the CISCO-SLB-EXT-MIB for SLB
health monitoring probes.

SLB: Server Load Balancing. Server load balancing
provides…
1.3.6.1.4.1.9.9.509 ciscoWdsInfoMIB3141 This MIB is intended to be implemented on all Cisco
network entities that provide Wireless Domain Services
(WDS). The WDS provide…
1.3.6.1.4.1.9.9.510 ciscoErmMIB, ciscoVoiceLmrMIB3176 This MIB module provides management of voice tone
signal as static injected tone for Land Mobile Radio
The tone signal includes …
1.3.6.1.4.1.9.9.511 ciscoCbpTargetTCMIB00 This MIB module defines Textual Conventions for
representing targets which have class based policy
mappings. A target can be any …
1.3.6.1.4.1.9.9.512 ciscoLwappWlanMIB3378 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weigh…
1.3.6.1.4.1.9.9.513 ciscoLwappApMIB51009 This MIB is intended to be implemented on all those
devices operating as Central Controllers (CC) that
terminate the Light Weight…