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
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.my.txt
Company: None
Module: CISCO-ITP-RT-MIB
This MIB is for managing information required to
route messages transported over Signalling System
No. 7 (SS7) Network via Cisco IP Transfer
Point.
The Cisco IP Transfer Point (ITP) is a hardware
and software solution that transports SS7 traffic
using IP. Each ITP node provides the functions
necessary to act as a SS7 signalling point. Each
signalling point is connected to other signalling
point using IP based or traditional TDM links.
The relevant ITU documents describing this technology
are the ITU Q series, including ITU Q.700: Introduction
to CCITT Signalling System No. 7 and ITU Q.701
Functional description of the message transfer part
(MTP) of Signalling System No. 7.
Definitions and overview:
Route:
A route consists of one or more linksets used to transport
MTP3 Message Signal Units(MSU) between signalling points.
A route is an association between a destination point
code(DPC) and a linkset, i.e., a linkset that can be used
to send an MSU to the given DPC.
Routeset:
A routeset is a set of routes to a given DPC. Each route
within a routeset is on a possible path toward the DPC.
Each route within the routeset has associated with it a
route priority.
In the following simple configuration, two routes exist
that can be used to transport MSUs from STP1 to STP4.
- STP1
| |
| 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 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: [email protected]" 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 }
ciscoItpRtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 228 }
Vendor: Cisco
Module: CISCO-ITP-RT-MIB
[Automatically extracted from oidview.com]
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: [email protected]" 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 }
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: [email protected]" 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 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.228.0 | cItpRouteNotifications | 1 | 1 | None |
| 1.3.6.1.4.1.9.9.228.1 | cItpRtMIBObjects | 3 | 35 | None |
| 1.3.6.1.4.1.9.9.228.2 | cItpRtMIBConformance | 2 | 8 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.178 | ciscoContentEngineMIB | 3 | 263 | The MIB module for the Cisco Content Engine from Cisco Systems, Inc. |
| 1.3.6.1.4.1.9.9.179 | ciscoCatOSAclQosMIB | 3 | 470 | This MIB module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Ci… |
| 1.3.6.1.4.1.9.9.180 | ciscoWirelessRfMetricsMIB | 5 | 99 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface specification. |
| 1.3.6.1.4.1.9.9.181 | ciscoWirelessLinkMetricsMIB | 4 | 141 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface link metrics specification. Glossary The followin… |
| 1.3.6.1.4.1.9.9.183 | ciscoGprsAccPtMIB | 3 | 338 | This MIB module supports access point configuration for GGSN in a GPRS system. GPRS [1] is a GSM network providing mobile wireles… |
| 1.3.6.1.4.1.9.9.184 | ciscoPimMIB | 3 | 36 | This MIB module defines the cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are a… |
| 1.3.6.1.4.1.9.9.185 | ciscoBertMIB | 2 | 46 | The MIB module to configure and perform Bit Error Rate Testing (BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces. Bit error rate… |
| 1.3.6.1.4.1.9.9.187 | ciscoBgp4MIB | 4 | 137 | An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Protocol… |
| 1.3.6.1.4.1.9.9.188 | cGtpMIB | 3 | 248 | This MIB module manages the GPRS Tunnelling Protocol (GTP) on GGSN and SGSN. GPRS provides wireless access to packet data network… |
| 1.3.6.1.4.1.9.9.189 | ciscoPortQosMIB | 3 | 114 | Cisco PORT QOS MIB - Overview This MIB module is for the management of Cisco's per port rate-limiting and traffic shaping on L3 sw… |
| 1.3.6.1.4.1.9.9.190 | ciscoVoiceAppsMIB | 3 | 40 | The MIB Module for the management of Cisco Voice Applications. This MIB is designed to work in conjunction with the SYSAPPL-MIB … |
| 1.3.6.1.4.1.9.9.191 | ciscoIpUplinkRedirectMIB | 3 | 11 | This MIB module is for the configuration of Cisco IP Uplink Redirect feature. |
| 1.3.6.1.4.1.9.9.192 | ciscoGprsChargingMIB | 3 | 315 | This MIB module manages the charging related function on the GGSN node of a GPRS system. The following diagram illustrates a simp… |
| 1.3.6.1.4.1.9.9.194 | ciscoPppoeMIB | 3 | 89 | Cisco PPPoE sessions management MIB Module. |
| 1.3.6.1.4.1.9.9.195 | ciscoEntityExtMIB | 3 | 64 | This MIB is an extension of the ENTITY-MIB specified in RFC2737. This MIB module contains Cisco-defined extensions to the entit… |
| 1.3.6.1.4.1.9.9.197 | ciscoDistDirMIB | 3 | 123 | Cisco Distributed Director MIB. The Cisco Distributed Director provides global Internet scalability and increased performance as … |
| 1.3.6.1.4.1.9.9.198 | ciscoRfSupMIB | 3 | 58 | This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redund… |
| 1.3.6.1.4.1.9.9.199 | ciscoSmFileDownloadMIB | 3 | 23 | The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller car… |
| 1.3.6.1.4.1.9.9.201 | ciscoSwitchUsageMIB | 3 | 15 | This MIB defines objects related to statistics for the usage of switch fabric. The switch fabric is used by the incoming packets … |
| 1.3.6.1.4.1.9.9.202 | ciscoOscpMIB | 3 | 52 | The MIB module for managing the Cisco Optical Supervisory Channel Protocol (OSCP). The OSCP is used to determine and maintain wav… |
| 1.3.6.1.4.1.9.9.204 | ciscoXdslLineMIB | 2 | 32 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to different t… |
| 1.3.6.1.4.1.9.9.215 | ciscoMacNotificationMIB | 3 | 72 | This MIB module is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring device… |
| 1.3.6.1.4.1.9.9.216 | ciscoContentNetworkMIB | 3 | 34 | This MIB module defines objects for Content Network devices. A Content Network is a collection of devices that optimizes the deli… |
| 1.3.6.1.4.1.9.9.217 | ciscoCat6kCrossbarMIB | 3 | 210 | The Catalyst 6000 Crossbar MIB provides instrumentation for configuration and operation of the crossbar switching fabric module, … |
| 1.3.6.1.4.1.9.9.218 | ciscoIfThresholdMIB | 3 | 65 | ciscoIfthresholdMIB |
| 1.3.6.1.4.1.9.9.219 | ciscoVoiceDnisMIB | 3 | 24 | The MIB module provides management support for Dialer Number Information Service (DNIS) mapping. A DNIS entry is associated with… |
| 1.3.6.1.4.1.9.9.220 | ciscoPaeMIB | 3 | 231 | Cisco Port Access Entity (PAE) module for managing IEEE Std 802.1x. This MIB provides Port Access Entity information that are eith… |
| 1.3.6.1.4.1.9.9.221 | ciscoEnhancedMemPoolMIB | 3 | 87 | New MIB module for monitoring the memory pools of all physical entities on a managed system. |
| 1.3.6.1.4.1.9.9.222 | ciscoEnhancedWredMIB | 3 | 70 | Cisco WRED MIB - Overview Cisco Weighted Random Early Detection/Drop (WRED) is a method which avoids traffic congestion on an outp… |
| 1.3.6.1.4.1.9.9.223 | ciscoWanNcdpMIB | 3 | 58 | This MIB module is intended for the management of network clock distribution and the Network Clock Distribution Protocol (NCDP) i… |
| 1.3.6.1.4.1.9.9.224 | ciscoDevExcepReportMIB | 3 | 29 | This mib defines the SNMP objects to report exceptions to north-bound NMS. The devices implementing this MIB monitor the status of… |
| 1.3.6.1.4.1.9.9.225 | ciscoLagMIB | 3 | 56 | Cisco Link Aggregation module for managing IEEE Std 802.3ad. This MIB provides Link Aggregation information that are either exclud… |
| 1.3.6.1.4.1.9.9.226 | ciscoNDEMIB | 4 | 17 | The Netflow Data Export (NDE) MIB provides instrumentation for configuration and operation of the Netflow Data Export feature. A … |
| 1.3.6.1.4.1.9.9.227 | ciscoItpAclMIB | 3 | 45 | The MIB for managing access lists that control messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Trans… |
| 1.3.6.1.4.1.9.9.229 | ciscoDs1ExtMIB | 2 | 129 | The MIB module to describe DS1/E1 interface objects. This is an extension to the standard DS1/E1 MIB (RFC 2495). Unless mentioned… |
| 1.3.6.1.4.1.9.9.230 | ciscoItpActMIB | 3 | 29 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signalling System No. 7(SS7) Network. This… |
| 1.3.6.1.4.1.9.9.231 | ciscoItpTextualConventions | 0 | 0 | The defines textual conventions used by to manage devices related to the SS7 network. The relevant ITU documents describing this… |
| 1.3.6.1.4.1.9.9.232 | ciscoItpSpMIB | 3 | 384 | The MIB for managing Signalling Points and its associated messages transported over Signalling System No. 7 (SS7) Network via Ci… |
| 1.3.6.1.4.1.9.9.233 | ciscoItpSccpMIB | 3 | 194 | The MIB for Signaling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP … |
| 1.3.6.1.4.1.9.9.234 | ciscoWanTopologyMIB | 3 | 83 | A management station can use this MIB module for the maintenance of persistent topology information of the PNNI network. Previous… |
| 1.3.6.1.4.1.9.9.235 | ciscoImaMIB | 2 | 60 | The MIB module describes Cisco IMA objects. This is an extension to the standard of ATM Forum IMA version 1.1, AF-PHY-0086.001 Spe… |
| 1.3.6.1.4.1.9.9.236 | ciscoWanSctMgmtMIB | 2 | 18 | MIB module to manage SCT files in a node. SCTs (Service Class Templates) are nodal configuration files, which define the traffic … |
| 1.3.6.1.4.1.9.9.237 | ciscoNmsApplHealthMIB | 3 | 21 | This MIB defines Cisco NMS Application (cna) Health Status Notifications and the related objects. These notifications will be sen… |
| 1.3.6.1.4.1.9.9.238 | ciscoIGMPFilterMIB | 2 | 45 | IGMP Filter configuration MIB. This MIB provides a mechanism for users to configure the system to intercept IGMP joins for IP Mul… |
| 1.3.6.1.4.1.9.9.240 | cGgsnMIB | 3 | 389 | This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device provides interworking with external packet-dat… |
| 1.3.6.1.4.1.9.9.241 | cggsnQosMIB | 2 | 89 | This MIB module manages the Quality of Service parameters of GGSN in a GPRS system. GGSN is the Gateway GPRS Support Node in the … |
| 1.3.6.1.4.1.9.9.242 | ciscoCableAvailabilityMIB | 3 | 60 | This is the MIB module for management of Hot Standby Connection to Connection Protocol (HCCP) features. HCCP is a Cisco proprieta… |
| 1.3.6.1.4.1.9.9.243 | ciscoHealthMonitorMIB | 3 | 22 | Health Monitor MIB module. The Health Monitor uses a model based on events of varying severity and frequency, and predefined rule… |
| 1.3.6.1.4.1.9.9.244 | ciscoNbarProtocolDiscoveryMIB | 3 | 84 | Cisco NBAR Protocol Discovery MIB NBAR - Network Based Application Recognition is an intelligent classification engine that reco… |
| 1.3.6.1.4.1.9.9.245 | ciscoGtpDirectorMIB | 3 | 35 | This MIB module defines objects that are used to manage GTP Director Module. In the GPRS network, the APN is the identifier that s… |
| 1.3.6.1.4.1.9.9.246 | ciscoL2TunnelConfigMIB | 3 | 65 | This MIB module is for layer 2 tunneling related configurations on a device. Tunneling allows separate local networks to be consi… |
| 1.3.6.1.4.1.9.9.248 | ciscoItpSp2MIB | 3 | 30 | The MIB for providing information specified in ITU Q752 Monitoring and Measurements for Signaling System No. 7(SS7) Network. This … |
| 1.3.6.1.4.1.9.9.249 | ciscoEnhancedImageMIB | 2 | 44 | Initial version of the MIB. This MIB has Image table containing the following information related to the running IOS image 1. Enti… |
| 1.3.6.1.4.1.9.9.252 | cTapMIB | 3 | 80 | This module manages Cisco's intercept feature. |
| 1.3.6.1.4.1.9.9.253 | ciscoItpXuaMIB | 3 | 250 | The MIB for MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) for Cisco's IP Transfer Point (ITP) implementation. The Cis… |
| 1.3.6.1.4.1.9.9.254 | ciscoSlbExtMIB | 3 | 425 | The extended MIB for managing Server Load Balancing Manager(s). This MIB extends the SLB management functionality in the CISCO-SL… |
| 1.3.6.1.4.1.9.9.255 | ciscoFabricMcastMIB | 3 | 30 | Fabric Multicast Resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource related informa… |
| 1.3.6.1.4.1.9.9.256 | ciscoFabricMcastApplMIB | 3 | 16 | Fabric multicast resource MIB module. This MIB module is used for managing/tracking the fabric multicast resource application rel… |
| 1.3.6.1.4.1.9.9.257 | ciscoFabricHfrMIB | 3 | 90 | Cisco Enhanced Benes fabric MIB module. This MIB module is used for managing/tracking the Ehanced Benes Fabric entities and/or fa… |
| 1.3.6.1.4.1.9.9.259 | ciscoPsaMicrocodeMIB | 3 | 24 | Cisco PSA Microcode MIB - Overview The PSA is the Packet Switching ASIC used in module like engine 2(E2) line cards in GSR for IP … |
| 1.3.6.1.4.1.9.9.260 | ciscoSsgMIB | 3 | 218 | The MIB Module manages Service Selection Gateway(SSG) devices. Service Selection Gateway(SSG) is a switching solution for service… |
| 1.3.6.1.4.1.9.9.261 | ciscoPtopoExtnMIB | 2 | 18 | This MIB module contains extensions to the PTOPO-MIB that provide support to distinguish between bidirectional and unidirectional… |
| 1.3.6.1.4.1.9.9.262 | ciscoVoaMIB | 2 | 14 | This MIB module defines objects to configure and manage the Variable Optical Attenuator (VOA) modules. VOA modules are typically … |
| 1.3.6.1.4.1.9.9.263 | ciscoIgmpSnoopingMIB | 3 | 286 | The MIB module for IGMP Snooping feature. Internet Group Management Protocol (IGMP) is the protocol used by IPv4 end hosts to ind… |
| 1.3.6.1.4.1.9.9.264 | ciscoOpticalMonitorMIB | 3 | 72 | This MIB module defines objects to monitor optical characteristics and set corresponding thresholds on the optical interfaces in … |
| 1.3.6.1.4.1.9.9.265 | ciscoEntityPfeMib | 3 | 58 | The Packet Forwarding Engine technology are Cisco developed Network Processors, which accelerates certain features in order to pr… |
| 1.3.6.1.4.1.9.9.268 | ciscoWlanVlanMIB | 3 | 41 | This MIB module provides network management support for device VLAN configuration on IEEE 802.11 wireless LAN. ACRONYMS AES Advanced… |
| 1.3.6.1.4.1.9.9.269 | ciscoTBridgeDevIfMIB | 2 | 20 | This MIB module provides network management support for configuration and status information of devices supporting transparent br… |
| 1.3.6.1.4.1.9.9.270 | ciscoSyslogEventExtMIB | 2 | 21 | This MIB module extends the Cisco Syslog MIB and provides network management support to handle and process Syslog messages as devi… |
| 1.3.6.1.4.1.9.9.271 | ciscoL2DevMonMIB | 3 | 24 | This MIB module is for monitoring of active layer 2 devices by hot standby layer 2 devices and the configuration of hot standby s… |
| 1.3.6.1.4.1.9.9.272 | ciscoDot11IfMIB | 3 | 212 | This MIB module provides network management support for Cisco IEEE 802.11 Wireless LAN type device (Access Point) radio interface… |
| 1.3.6.1.4.1.9.9.273 | ciscoDot11AssociationMIB | 2 | 91 | This MIB module provides network management information on IEEE 802.11 wireless device association management and data packet for… |
| 1.3.6.1.4.1.9.9.275 | ciscoBcpMIB | 2 | 25 | This MIB module describes the Managed Objects for of Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474. |
| 1.3.6.1.4.1.9.9.276 | ciscoIfExtensionMIB | 3 | 143 | A MIB module for extending the IF-MIB (RFC2863) to add objects which provide additional information about interfaces not availabl… |
| 1.3.6.1.4.1.9.9.277 | ciscoDdpIappMIB | 3 | 22 | This MIB module describes the management support for the Inter-Access Point Protocol (IAPP). IAPP is a Cisco propriety Data Deli… |
| 1.3.6.1.4.1.9.9.278 | ciscoIpProtocolMIB | 3 | 63 | The MIB module is for management of information to support packet filtering on IP protocols. The cippfIpProfileTable allows users… |
| ... | ||||