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 entries that define a
combined linkset consisting of linkset 'STP1-STP2' and
'STP1-STP3' to point code 5.5.5. An alternate route is
also defined using linkset 'STP1-STP4'.
Example 3: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP2
Description: A route table entry that defines routing
to a cluster. The cluster represents all point codes
in the range from 5.5.0-5.5.255.
Example 4: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
Description: The mixing of fully-qualified and summary
route table entries allow for different routes to be
defined for certain DPC in a cluster. In this
configuration, the fully-qualified route will be the
primary and the summary route will act as a backup.
Route table:
A group of route table entries used to route MSU for a
particular instance of a signalling point.
A sample route table.
DPC/MASK Priority Linkset-name
0.0.0/0 7 STP1-STP4
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
.
.
122.5.5 5 STP1-STP2
.
.
243.200.1 6 STP1-STP3
Parsed from file CISCO-ITP-GRT-MIB.mib
Module: CISCO-ITP-GRT-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 entries that define a
combined linkset consisting of linkset 'STP1-STP2' and
'STP1-STP3' to point code 5.5.5. An alternate route is
also defined using linkset 'STP1-STP4'.
Example 3: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP2
Description: A route table entry that defines routing
to a cluster. The cluster represents all point codes
in the range from 5.5.0-5.5.255.
Example 4: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
Description: The mixing of fully-qualified and summary
route table entries allow for different routes to be
defined for certain DPC in a cluster. In this
configuration, the fully-qualified route will be the
primary and the summary route will act as a backup.
Route table:
A group of route table entries used to route MSU for a
particular instance of a signalling point.
A sample route table.
DPC/MASK Priority Linkset-name
0.0.0/0 7 STP1-STP4
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
.
.
122.5.5 5 STP1-STP2
.
.
243.200.1 6 STP1-STP3
Parsed from file CISCO-ITP-GRT-MIB.my.txt
Company: None
Module: CISCO-ITP-GRT-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 entries that define a
combined linkset consisting of linkset 'STP1-STP2' and
'STP1-STP3' to point code 5.5.5. An alternate route is
also defined using linkset 'STP1-STP4'.
Example 3: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP2
Description: A route table entry that defines routing
to a cluster. The cluster represents all point codes
in the range from 5.5.0-5.5.255.
Example 4: variant = ANSI
DPC/MASK Priority Linkset-name
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
Description: The mixing of fully-qualified and summary
route table entries allow for different routes to be
defined for certain DPC in a cluster. In this
configuration, the fully-qualified route will be the
primary and the summary route will act as a backup.
Route table:
A group of route table entries used to route MSU for a
particular instance of a signalling point.
A sample route table.
DPC/MASK Priority Linkset-name
0.0.0/0 7 STP1-STP4
5.5.0/16 3 STP1-STP3
5.5.5/24 3 STP1-STP2
.
.
122.5.5 5 STP1-STP2
.
.
243.200.1 6 STP1-STP3
ciscoGrtMIB MODULE-IDENTITY LAST-UPDATED "200805010000Z" 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 entries that define a combined linkset consisting of linkset 'STP1-STP2' and 'STP1-STP3' to point code 5.5.5. An alternate route is also defined using linkset 'STP1-STP4'. Example 3: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP2 Description: A route table entry that defines routing to a cluster. The cluster represents all point codes in the range from 5.5.0-5.5.255. Example 4: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 Description: The mixing of fully-qualified and summary route table entries allow for different routes to be defined for certain DPC in a cluster. In this configuration, the fully-qualified route will be the primary and the summary route will act as a backup. Route table: A group of route table entries used to route MSU for a particular instance of a signalling point. A sample route table. DPC/MASK Priority Linkset-name 0.0.0/0 7 STP1-STP4 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 . . 122.5.5 5 STP1-STP2 . . 243.200.1 6 STP1-STP3 " REVISION "200805010000Z" DESCRIPTION "Deprecated the following objects: cgrtDestNotifDelayTime, cgrtDestNotifWindowTime, cgrtDestNotifMaxPerWindow, cgrtDestNotifEnabled, cgrtMgmtNotifDelayTime, cgrtMgmtNotifWindowTime, cgrtMgmtNotifMaxPerWindow, cgrtMgmtNotifEnabled. Deprecated the following notifications: ciscoGrtDestStateChange, ciscoGrtMgmtStateChange Deprecated the following objects under cgrtNotificationsInfo: cgrtDestNotifSupFlag, cgrtDestNotifChanges, cgrtMgmtNotifSupFlag, cgrtMgmtNotifChanges. Deprecated the following compliance statement: ciscoGrtMIBCompliance. Deprecated the following object groups: ciscoGrtDestGroup, ciscoGrtRouteGroup. Deprecated the following notification group: ciscoGrtNotificationGroup. Added the following textual convention: CgrtDisplayPCSI. Added the following objects: cgrtDestNotifWindowTimeRev1, cgrtDestNotifMaxPerWindowRev1, cgrtDestNotifEnabledRev1, cgrtMgmtNotifWindowTimeRev1, cgrtMgmtNotifMaxPerWindowRev1, cgrtMgmtNotifEnabledRev1, cgrtOrigTableEnabled, cgrtPCStatsInterval, cgrtNoRouteMSUsNotifEnabled, cgrtNoRouteMSUsNotifWindowTime. Added the following object to cgrtInstTable: cgrtInstUnknownOrigPCs, cgrtInstNoRouteDrops. Added these objects to cgrtDestTable: cgrtDestAccessibleSeconds, cgrtDestInaccessibleSeconds, cgrtDestRestrictedSeconds, cgrtDestMSUsOut, cgrtDestOctetsOut, cgrtDestMSUsIn, cgrtDestOctetsIn, cgrtDestInaccessibleDrops, cgrtDestRestrictedMSUs, cgrtDestCongestionDrops, cgrtDestDisplay. Added these objects to cgrtRouteTable: cgrtRouteAllowedSeconds, cgrtRouteRestrictedSeconds, cgrtRouteProhibitedSeconds, cgrtRouteDisplay. Added a new table cgrtOrigTable with following objects: cgrtOrigPC, cgrtOrigMSUs, cgrtOrigOctets, cgrtOrigDisplay. Added a new table cgrtDestSITable with following objects: cgrtMtp3SI, cgrtDestSIMSUsOut, cgrtDestSIOctetsOut, cgrtDestSIMSUsIn, cgrtDestSIOctetsIn, cgrtDestSIDisplay. Added a new table cgrtOrigSITable with following objects: cgrtOrigSIMSUs, cgrtOrigSIOctets, cgrtOrigSIDisplay. Added the following notifications: ciscoGrtDestStateChangeRev1, ciscoGrtMgmtStateChangeRev1, ciscoGrtNoRouteMSUDiscards. Added the following objects under cgrtNotificationsInfo: cgrtDestNotifSuppressed, cgrtRouteNotifSuppressed, cgrtNoRouteMSUsInterval, cgrtIntervalNoRouteMSUs. Added the following compliance statement: ciscoGrtMIBComplianceRev1. Added the following object groups: ciscoGrtScalarsGroup, ciscoGrtDestGroupRev1, ciscoGrtRouteGroupRev1, ciscoGrtOrigGroup, ciscoGrtDestSIGroup, ciscoGrtOrigSIGroup, ciscoGrtInstGroupSup1. Added the following notification group: ciscoGrtNotificationsGroupRev1." REVISION "200303030000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 334 }
ciscoGrtMIB OBJECT IDENTIFIER ::= { ciscoMgmt 334 }
Vendor: Cisco
Module: CISCO-ITP-GRT-MIB
[Automatically extracted from oidview.com]
ciscoGrtMIB MODULE-IDENTITY LAST-UPDATED "200805010000Z" 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 entries that define a combined linkset consisting of linkset 'STP1-STP2' and 'STP1-STP3' to point code 5.5.5. An alternate route is also defined using linkset 'STP1-STP4'. Example 3: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP2 Description: A route table entry that defines routing to a cluster. The cluster represents all point codes in the range from 5.5.0-5.5.255. Example 4: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 Description: The mixing of fully-qualified and summary route table entries allow for different routes to be defined for certain DPC in a cluster. In this configuration, the fully-qualified route will be the primary and the summary route will act as a backup. Route table: A group of route table entries used to route MSU for a particular instance of a signalling point. A sample route table. DPC/MASK Priority Linkset-name 0.0.0/0 7 STP1-STP4 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 . . 122.5.5 5 STP1-STP2 . . 243.200.1 6 STP1-STP3 " REVISION "200805010000Z" DESCRIPTION "Deprecated the following objects: cgrtDestNotifDelayTime, cgrtDestNotifWindowTime, cgrtDestNotifMaxPerWindow, cgrtDestNotifEnabled, cgrtMgmtNotifDelayTime, cgrtMgmtNotifWindowTime, cgrtMgmtNotifMaxPerWindow, cgrtMgmtNotifEnabled. Deprecated the following notifications: ciscoGrtDestStateChange, ciscoGrtMgmtStateChange Deprecated the following objects under cgrtNotificationsInfo: cgrtDestNotifSupFlag, cgrtDestNotifChanges, cgrtMgmtNotifSupFlag, cgrtMgmtNotifChanges. Deprecated the following compliance statement: ciscoGrtMIBCompliance. Deprecated the following object groups: ciscoGrtDestGroup, ciscoGrtRouteGroup. Deprecated the following notification group: ciscoGrtNotificationGroup. Added the following textual convention: CgrtDisplayPCSI. Added the following objects: cgrtDestNotifWindowTimeRev1, cgrtDestNotifMaxPerWindowRev1, cgrtDestNotifEnabledRev1, cgrtMgmtNotifWindowTimeRev1, cgrtMgmtNotifMaxPerWindowRev1, cgrtMgmtNotifEnabledRev1, cgrtOrigTableEnabled, cgrtPCStatsInterval, cgrtNoRouteMSUsNotifEnabled, cgrtNoRouteMSUsNotifWindowTime. Added the following object to cgrtInstTable: cgrtInstUnknownOrigPCs, cgrtInstNoRouteDrops. Added these objects to cgrtDestTable: cgrtDestAccessibleSeconds, cgrtDestInaccessibleSeconds, cgrtDestRestrictedSeconds, cgrtDestMSUsOut, cgrtDestOctetsOut, cgrtDestMSUsIn, cgrtDestOctetsIn, cgrtDestInaccessibleDrops, cgrtDestRestrictedMSUs, cgrtDestCongestionDrops, cgrtDestDisplay. Added these objects to cgrtRouteTable: cgrtRouteAllowedSeconds, cgrtRouteRestrictedSeconds, cgrtRouteProhibitedSeconds, cgrtRouteDisplay. Added a new table cgrtOrigTable with following objects: cgrtOrigPC, cgrtOrigMSUs, cgrtOrigOctets, cgrtOrigDisplay. Added a new table cgrtDestSITable with following objects: cgrtMtp3SI, cgrtDestSIMSUsOut, cgrtDestSIOctetsOut, cgrtDestSIMSUsIn, cgrtDestSIOctetsIn, cgrtDestSIDisplay. Added a new table cgrtOrigSITable with following objects: cgrtOrigSIMSUs, cgrtOrigSIOctets, cgrtOrigSIDisplay. Added the following notifications: ciscoGrtDestStateChangeRev1, ciscoGrtMgmtStateChangeRev1, ciscoGrtNoRouteMSUDiscards. Added the following objects under cgrtNotificationsInfo: cgrtDestNotifSuppressed, cgrtRouteNotifSuppressed, cgrtNoRouteMSUsInterval, cgrtIntervalNoRouteMSUs. Added the following compliance statement: ciscoGrtMIBComplianceRev1. Added the following object groups: ciscoGrtScalarsGroup, ciscoGrtDestGroupRev1, ciscoGrtRouteGroupRev1, ciscoGrtOrigGroup, ciscoGrtDestSIGroup, ciscoGrtOrigSIGroup, ciscoGrtInstGroupSup1. Added the following notification group: ciscoGrtNotificationsGroupRev1." REVISION "200303030000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 334 }
ciscoGrtMIB MODULE-IDENTITY LAST-UPDATED "200805010000Z" 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 entries that define a combined linkset consisting of linkset 'STP1-STP2' and 'STP1-STP3' to point code 5.5.5. An alternate route is also defined using linkset 'STP1-STP4'. Example 3: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP2 Description: A route table entry that defines routing to a cluster. The cluster represents all point codes in the range from 5.5.0-5.5.255. Example 4: variant = ANSI DPC/MASK Priority Linkset-name 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 Description: The mixing of fully-qualified and summary route table entries allow for different routes to be defined for certain DPC in a cluster. In this configuration, the fully-qualified route will be the primary and the summary route will act as a backup. Route table: A group of route table entries used to route MSU for a particular instance of a signalling point. A sample route table. DPC/MASK Priority Linkset-name 0.0.0/0 7 STP1-STP4 5.5.0/16 3 STP1-STP3 5.5.5/24 3 STP1-STP2 . . 122.5.5 5 STP1-STP2 . . 243.200.1 6 STP1-STP3 " REVISION "200805010000Z" DESCRIPTION "Deprecated the following objects: cgrtDestNotifDelayTime, cgrtDestNotifWindowTime, cgrtDestNotifMaxPerWindow, cgrtDestNotifEnabled, cgrtMgmtNotifDelayTime, cgrtMgmtNotifWindowTime, cgrtMgmtNotifMaxPerWindow, cgrtMgmtNotifEnabled. Deprecated the following notifications: ciscoGrtDestStateChange, ciscoGrtMgmtStateChange Deprecated the following objects under cgrtNotificationsInfo: cgrtDestNotifSupFlag, cgrtDestNotifChanges, cgrtMgmtNotifSupFlag, cgrtMgmtNotifChanges. Deprecated the following compliance statement: ciscoGrtMIBCompliance. Deprecated the following object groups: ciscoGrtDestGroup, ciscoGrtRouteGroup. Deprecated the following notification group: ciscoGrtNotificationGroup. Added the following textual convention: CgrtDisplayPCSI. Added the following objects: cgrtDestNotifWindowTimeRev1, cgrtDestNotifMaxPerWindowRev1, cgrtDestNotifEnabledRev1, cgrtMgmtNotifWindowTimeRev1, cgrtMgmtNotifMaxPerWindowRev1, cgrtMgmtNotifEnabledRev1, cgrtOrigTableEnabled, cgrtPCStatsInterval, cgrtNoRouteMSUsNotifEnabled, cgrtNoRouteMSUsNotifWindowTime. Added the following object to cgrtInstTable: cgrtInstUnknownOrigPCs, cgrtInstNoRouteDrops. Added these objects to cgrtDestTable: cgrtDestAccessibleSeconds, cgrtDestInaccessibleSeconds, cgrtDestRestrictedSeconds, cgrtDestMSUsOut, cgrtDestOctetsOut, cgrtDestMSUsIn, cgrtDestOctetsIn, cgrtDestInaccessibleDrops, cgrtDestRestrictedMSUs, cgrtDestCongestionDrops, cgrtDestDisplay. Added these objects to cgrtRouteTable: cgrtRouteAllowedSeconds, cgrtRouteRestrictedSeconds, cgrtRouteProhibitedSeconds, cgrtRouteDisplay. Added a new table cgrtOrigTable with following objects: cgrtOrigPC, cgrtOrigMSUs, cgrtOrigOctets, cgrtOrigDisplay. Added a new table cgrtDestSITable with following objects: cgrtMtp3SI, cgrtDestSIMSUsOut, cgrtDestSIOctetsOut, cgrtDestSIMSUsIn, cgrtDestSIOctetsIn, cgrtDestSIDisplay. Added a new table cgrtOrigSITable with following objects: cgrtOrigSIMSUs, cgrtOrigSIOctets, cgrtOrigSIDisplay. Added the following notifications: ciscoGrtDestStateChangeRev1, ciscoGrtMgmtStateChangeRev1, ciscoGrtNoRouteMSUDiscards. Added the following objects under cgrtNotificationsInfo: cgrtDestNotifSuppressed, cgrtRouteNotifSuppressed, cgrtNoRouteMSUsInterval, cgrtIntervalNoRouteMSUs. Added the following compliance statement: ciscoGrtMIBComplianceRev1. Added the following object groups: ciscoGrtScalarsGroup, ciscoGrtDestGroupRev1, ciscoGrtRouteGroupRev1, ciscoGrtOrigGroup, ciscoGrtDestSIGroup, ciscoGrtOrigSIGroup, ciscoGrtInstGroupSup1. Added the following notification group: ciscoGrtNotificationsGroupRev1." REVISION "200303030000Z" DESCRIPTION "Initial version of this MIB module." ::= { ciscoMgmt 334 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.334.0 | ciscoGrtNotifications | 6 | 6 | None |
| 1.3.6.1.4.1.9.9.334.1 | ciscoGrtMIBObjects | 2 | 125 | None |
| 1.3.6.1.4.1.9.9.334.2 | ciscoGrtMIBConform | 2 | 16 | 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.284 | ciscoFcRouteMIB | 2 | 55 | The MIB module for configuring and displaying FC (Fibre Channel) Route Information. |
| 1.3.6.1.4.1.9.9.285 | ciscoPortChannelMIB | 2 | 40 | The MIB module for management of Port Channel ports. In addition to this MIB, CISCO-FC-FE-MIB and interface mib (rfc2863) will al… |
| 1.3.6.1.4.1.9.9.286 | ciscoWwnmgrMIB | 2 | 38 | The World Wide Name (WWN) in the fibre channel networking technology is equivalent to the MAC address in Ethernet. There are six … |
| 1.3.6.1.4.1.9.9.287 | ciscoFspfMIB | 4 | 95 | Fabric Shortest Path First (FSPF) MIB. |
| 1.3.6.1.4.1.9.9.288 | ciscoRadiusMIB | 3 | 91 | MIB module for monitoring and configuring authentication and logging services using RADIUS (Remote Authentication Dial In User Se… |
| 1.3.6.1.4.1.9.9.289 | ciscoFcFeMIB | 2 | 315 | This is the Cisco fibre element management MIB module. It covers: - Cisco extension to the interface MIB ( IF-MIB ) - Contains all… |
| 1.3.6.1.4.1.9.9.290 | ciscoVirtualNwIfMIB | 2 | 22 | The MIB module for management of virtual network interfaces to VSAN and VLAN. |
| 1.3.6.1.4.1.9.9.292 | ciscoRscnMIB | 2 | 67 | The MIB module for the management of the Fibre Channel's Registered State Change Notification (RSCN) functionality, which is spec… |
| 1.3.6.1.4.1.9.9.293 | ciscoNsMIB | 2 | 67 | The MIB module for the management of the Cisco Name Server which realizes the FC-GS3 requirements for Name Server (NS). |
| 1.3.6.1.4.1.9.9.294 | ciscoZsMIB | 2 | 254 | The MIB module for the management of zoning within the framework of Cisco's Zoning Server (ZS) Archi- tecture which realizes the … |
| 1.3.6.1.4.1.9.9.295 | ciscoFcPingMIB | 2 | 37 | The MIB module for the management of the Fibre Channel Ping functionality. |
| 1.3.6.1.4.1.9.9.296 | ciscoFcTraceRouteMIB | 2 | 31 | The MIB module for the management of the Fibre Channel Trace Route functionality. |
| 1.3.6.1.4.1.9.9.297 | ciscoFcsMIB | 2 | 122 | The MIB module for the management of a Fabric Configuration Server (FCS). An FCS is defined by the FC-GS3 standard. This MIB ena… |
| 1.3.6.1.4.1.9.9.299 | ciscoExtScsiMIB | 2 | 68 | The Cisco extension to CISCO-SCSI-MIB which is a copy of the Internet draft, the SCSI-MIB, from the IETF. Glossary of terms used i… |
| 1.3.6.1.4.1.9.9.300 | ciscoCallHomeMIB | 3 | 324 | The MIB module for the management of Call Home feature within the framework of Cisco's Call Home architecture. Customers deployin… |
| 1.3.6.1.4.1.9.9.301 | ciscoSyslogExtMIB | 2 | 44 | MIB module for configuring and monitoring System Log related management parameters as defined by RFC 3164. |
| 1.3.6.1.4.1.9.9.302 | ciscoDmMIB | 2 | 85 | The MIB module for the domain management functionality defined by the Fibre Channel standards (FC-SW2). For the purposes of this … |
| 1.3.6.1.4.1.9.9.305 | ciscoSystemExtMIB | 3 | 112 | MIB module for monitoring High Availability, SNMP SET errors and bandwidths. This mib module also provides the information on co… |
| 1.3.6.1.4.1.9.9.309 | ciscoIPIfMIB | 3 | 40 | The MIB module for configuring IP characteristics of the interfaces of a device. |
| 1.3.6.1.4.1.9.9.311 | ciscoEpmNotificationMIB | 3 | 48 | Notifications directly from hardware and software and processed notifications from various management applications can be furthe… |
| 1.3.6.1.4.1.9.9.312 | ciscoDataCollectionMIB | 3 | 84 | The MIB module allows a management application to select a set of MIB object instances whose values need to be collected on a per… |
| 1.3.6.1.4.1.9.9.313 | ciscoL2ControlMIB | 3 | 113 | The CISCO-L2-CONTROL-MIB is used to control some layer 2 functions, including MAC limit function and unicast flooding. This devi… |
| 1.3.6.1.4.1.9.9.314 | ciscoCasIfExtMIB | 3 | 225 | The MIB module is an extension of CISCO-CAS-IF-MIB. It defines the attributes of a voice interface. |
| 1.3.6.1.4.1.9.9.315 | ciscoPortSecurityMIB | 3 | 89 | The MIB module for managing Cisco Port Security. |
| 1.3.6.1.4.1.9.9.317 | ciscoIscsiGwMIB | 3 | 145 | MIB module for monitoring and configuring iSCSI gateway functions. An iSCSI gateway represents FC (Fibre Channel) targets/initiat… |
| 1.3.6.1.4.1.9.9.318 | ciscoXgcpMIB | 3 | 120 | This MIB is an enhancement for existing XGCP-MIB. xGCP is a set of protocols, for example SGCP (Simple Gateway Control Protocol) … |
| 1.3.6.1.4.1.9.9.319 | ciscoPropAtmIfMIB | 3 | 57 | This MIB is designed for Propietary ATM (propAtm) interfaces. The propAtm interfaces are identified in the ifTable entries with if… |
| 1.3.6.1.4.1.9.9.321 | ciscoMgcMIB | 3 | 43 | This MIB is used to support MGC(call agent) and MGC Group configuration. The MGC or MGC group configuration is performed under a s… |
| 1.3.6.1.4.1.9.9.322 | ccacSysMIB | 2 | 60 | This MIB module provides provisioning and monitoring Call Admission Control (CAC). |
| 1.3.6.1.4.1.9.9.323 | ciscoVoiceAalxProfileMIB | 3 | 87 | This MIB defines the objects specific to voice over ATM or voice over IP. Those objects are related to the following areas: 1. COD… |
| 1.3.6.1.4.1.9.9.324 | ciscoMediaGatewayMIB | 3 | 107 | The MIB module for managing Trunk Media Gateway. A Media Gateway is a network element that provides conversion between the audio … |
| 1.3.6.1.4.1.9.9.325 | ciscoXgcpExtMIB | 2 | 65 | This MIB module is an extension to CISCO-XGCP-MIB. It defines the parameters related to the following aspects in xGCP protocols: *… |
| 1.3.6.1.4.1.9.9.326 | ciscoIpLocalPoolMIB | 3 | 57 | This MIB defines the configuration and monitoring capabilities relating to local IP pools. Local IP pools have the following char… |
| 1.3.6.1.4.1.9.9.329 | ciscoFcipMgmtExtMIB | 3 | 75 | A MIB module for extending the CISCO-FCIP-MGMT-MIB to add objects which provide additional information about FCIP interfaces not … |
| 1.3.6.1.4.1.9.9.330 | ciscoSysInfoLogMIB | 3 | 44 | This MIB provides the configuration of System Information Logging feature, which allows a certain number of commands to be execut… |
| 1.3.6.1.4.1.9.9.331 | ciscoCsgMIB | 3 | 86 | This MIB supports the Cisco Content Services Gateway (CSG) product. It includes five traps and four tables that enable querying C… |
| 1.3.6.1.4.1.9.9.332 | ciscoGsp2MIB | 3 | 91 | 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.333 | ciscoGactMIB | 3 | 40 | 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.335 | ciscoGsccpMIB | 3 | 293 | The MIB for signalling Connection Control Part(SCCP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP… |
| 1.3.6.1.4.1.9.9.336 | ciscoGspMIB | 3 | 273 | 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.339 | ciscoSecureShellMIB | 2 | 40 | MIB module for displaying and configuring accounting and Secure Shell (SSH) related features in a device. SSH is a program to log … |
| 1.3.6.1.4.1.9.9.340 | ciscoLreCpeMIB | 3 | 21 | The MIB module for the Cisco Long Reach Ethernet Customer Premise Equipment device information. *** ABBREVIATIONS, ACRONYMS, AND … |
| 1.3.6.1.4.1.9.9.341 | ciscoCableQosMonitorMIB | 3 | 57 | This is the MIB module for subscriber QoS monitoring for DOCSIS-compliant Cable Modem Termination Systems (CMTS). Several subscrib… |
| 1.3.6.1.4.1.9.9.343 | ciscoAuthorizationStatsMibModule | 2 | 25 | The Cisco User Authorization Statistics MIB models counters and objects that are of management interest. |
| 1.3.6.1.4.1.9.9.344 | ciscoEntityDisplayMIB | 2 | 21 | This MIB module provides information about the status of display devices such as Light Emitting Diodes (LEDs) and alphanumeric di… |
| 1.3.6.1.4.1.9.9.350 | ciscoEntityDiagMIB | 3 | 139 | This MIB module defines the managed objects that describe the online diagnostics capabilities supported by the physical entities … |
| 1.3.6.1.4.1.9.9.351 | ciscoAtmTrunkMIB | 3 | 102 | The MIB for voice and Nx64 over ATM Trunking applications. The following lists the abbreviations used in this MIB: AAL ATM … |
| 1.3.6.1.4.1.9.9.356 | ciscoVoiceToneCadenceMIB | 3 | 30 | The MIB defines the attributes of the programmable tones specified in ITU-T E.180 Supplement 2. Each country has its own regulati… |
| 1.3.6.1.4.1.9.9.358 | ciscoBbsmMIB | 3 | 20 | This mib is designed to send BBSM specific notifications. There are variables that contain detail data that are bind to a notifi… |
| 1.3.6.1.4.1.9.9.359 | ciscoLicenseMIB | 3 | 52 | This MIB module provides objects to view the features and services that are licensed to run on a system (usually a network entity… |
| 1.3.6.1.4.1.9.9.360 | ciscoImageUpgradeMIB | 3 | 101 | This mib provides, objects to upgrade images on modules in the system, objects showing the status of the upgrade operation, and o… |
| 1.3.6.1.4.1.9.9.361 | ciscoCommonRolesMIB | 3 | 40 | MIB module for managing the common roles between access methods like Command Line Interface (CLI), SNMP and XML interfaces. Every … |
| 1.3.6.1.4.1.9.9.362 | ciscoPortStormControlMIB | 3 | 41 | The MIB module for managing Cisco Port Storm Control. |
| 1.3.6.1.4.1.9.9.363 | ciscoFcSpanMIB | 2 | 49 | MIB module for displaying and configuring Switched Port Analyzer(SPAN) related features in a Fibre Channel device. SPAN is a featu… |
| 1.3.6.1.4.1.9.9.364 | ciscoPsmMIB | 3 | 213 | The MIB module for the management of the Port Security Manager (PSM). The PSM consists of 2 aspects: Port binding and Fabric bindi… |
| 1.3.6.1.4.1.9.9.365 | ciscoFCCMIB | 3 | 42 | The MIB module for the management of Fibre Channel Congestion Control(FCC). FCC is a Cisco proprietary flow control mechanism tha… |
| 1.3.6.1.4.1.9.9.367 | ciscoAAAServerExtMIB | 2 | 77 | This MIB is an extension to the CISCO-AAA-SERVER-MIB. This MIB module enhances the 'casConfigTable' to include other types of Ser… |
| 1.3.6.1.4.1.9.9.368 | 368 | 0 | 0 | Cisco Content Services (CSS) switch product, also known as Arrowpoint, for version 7.40 and later |
| 1.3.6.1.4.1.9.9.369 | ciscoLicenseMgrMIB | 3 | 74 | The MIB module for a method of managing license files on the system. Licensing mechanism provides more flexibility in supporting v… |
| 1.3.6.1.4.1.9.9.370 | ciscoSslProxyMIB | 3 | 372 | This MIB module is for managing a Secure Socket Layer (SSL) Proxy device which terminates and accelarates SSL and Transport Layer… |
| 1.3.6.1.4.1.9.9.371 | ciscoIvrMIB | 3 | 192 | The MIB module for the management of Inter-VSAN routing within the framework of Cisco's Inter-VSAN Routing (IVR) Architecture. IV… |
| 1.3.6.1.4.1.9.9.372 | ciscoIsnsClientMIB | 3 | 16 | MIB module for monitoring and configuring Internet Storage Name Service (iSNS) client. |
| 1.3.6.1.4.1.9.9.373 | ciscoFdmiMIB | 3 | 47 | Fabric Device Management Interface (FDMI) MIB. This MIB module defines objects for managing the devices such as HBA (Host Bus Ada… |
| 1.3.6.1.4.1.9.9.374 | ciscoDynamicArpInspectionMIB | 3 | 82 | The MIB module is for configuration of Dynamic ARP Inspection feature. Dynamic ARP Inspection is a security mechanism which valid… |
| 1.3.6.1.4.1.9.9.375 | ciscoFiconMIB | 3 | 176 | This is the FICON (FIber CONnection) MIB module. FICON is an IBM standard of transport mechanism for communication between the ma… |
| 1.3.6.1.4.1.9.9.376 | ciscoSVIAutostateMIB | 3 | 19 | The MIB module is for configuration of the switch virtual interface (SVI) autostate feature. Autostate feature is a mechanism to … |
| 1.3.6.1.4.1.9.9.377 | ciscoFeatureCtrlMIB | 3 | 53 | There are two types of features in the system: - Regular features - Optional features The Regular features may or may not need to … |
| 1.3.6.1.4.1.9.9.378 | ciscoSvcInterfaceMIB | 3 | 115 | MIB module for displaying and configuring SVC (SAN Volume Controller) related features in the Storage Area Network (SAN) switches… |
| 1.3.6.1.4.1.9.9.379 | ciscoItpmMIB | 3 | 47 | The MIB for providing information related to monitoring SS7 links. This information can be used to manage the state of software u… |
| 1.3.6.1.4.1.9.9.380 | ciscoDhcpSnoopingMIB | 3 | 127 | The MIB module is for configuration of DHCP Snooping feature. DHCP Snooping is a security mechanism which uses information gleane… |
| 1.3.6.1.4.1.9.9.381 | ciscoDiffServExtMIB | 2 | 49 | This MIB is a Cisco extension to the DIFFSERV-MIB, RFC 3289. This MIB defines a Fibre Channel (FC) Multi Field filter to be used i… |
| 1.3.6.1.4.1.9.9.383 | ciscoCidsMIB | 3 | 183 | Cisco Intrusion Detection System MIB. Provides trap definitions for the evAlert and evError elements of the IDIOM (Intrusion Det… |
| 1.3.6.1.4.1.9.9.384 | ciscoDot11AntennaMIB | 2 | 11 | This MIB is intended to be implemented on 802.11 Access Points and Wireless Bridges to provide information about the antennas con… |
| ... | ||||