This table provides information on the traffic in MUS
for each processor in both directions. Any MSU in which
a processor is involved will be counted. Here are some
examples of how MSUs would be counted.
Traditional SS7 Links:
MSU is received on Line card 1 that supports SS7 link and
MSU is routed directly to line card 2 that supports output
link. Line card 1 processor information will be updated to
indicate it received MSU and line card 2 processor
information will be updated to indicate it sent MSU.
IP/SCTP based SS7 Links:
IP based SS7 Links can be terminated on linecard or owned
by the main processor. When SS7 link is terminated on main
processor only the main processor information will be
updated. The line card processor that owns the IP interface
will be involved but will not be included in measurements.
When the SS7 link is terminated on line card its processor
information will be updated.
It is important to note that packets exchanged for SCTP
associations are different from SS7 MSUs. More than one
SS7 MSU can be transmitted in a single IP packet. Also,
the SCTP association exchanges control packets that are
not counted as SS7 MSUs.
Parsed from file CISCO-ITP-MSU-RATES-MIB.mib
Module: CISCO-ITP-MSU-RATES-MIB
This table provides information on the traffic in MUS
for each processor in both directions. Any MSU in which
a processor is involved will be counted. Here are some
examples of how MSUs would be counted.
Traditional SS7 Links:
MSU is received on Line card 1 that supports SS7 link and
MSU is routed directly to line card 2 that supports output
link. Line card 1 processor information will be updated to
indicate it received MSU and line card 2 processor
information will be updated to indicate it sent MSU.
IP/SCTP based SS7 Links:
IP based SS7 Links can be terminated on linecard or owned
by the main processor. When SS7 link is terminated on main
processor only the main processor information will be
updated. The line card processor that owns the IP interface
will be involved but will not be included in measurements.
When the SS7 link is terminated on line card its processor
information will be updated.
It is important to note that packets exchanged for SCTP
associations are different from SS7 MSUs. More than one
SS7 MSU can be transmitted in a single IP packet. Also,
the SCTP association exchanges control packets that are
not counted as SS7 MSUs.
This table provides information on the traffic in MUS
for each processor in both directions. Any MSU in which
a processor is involved will be counted. Here are some
examples of how MSUs would be counted.
Traditional SS7 Links:
MSU is received on Line card 1 that supports SS7 link and
MSU is routed directly to line card 2 that supports output
link. Line card 1 processor information will be updated to
indicate it received MSU and line card 2 processor
information will be updated to indicate it sent MSU.
IP/SCTP based SS7 Links:
IP based SS7 Links can be terminated on linecard or owned
by the main processor. When SS7 link is terminated on main
processor only the main processor information will be
updated. The line card processor that owns the IP interface
will be involved but will not be included in measurements.
When the SS7 link is terminated on line card its processor
information will be updated.
It is important to note that packets exchanged for SCTP
associations are different from SS7 MSUs. More than one
SS7 MSU can be transmitted in a single IP packet. Also,
the SCTP association exchanges control packets that are
not counted as SS7 MSUs.
Parsed from file CISCO-ITP-MSU-RATES-MIB.my.txt
Company: None
Module: CISCO-ITP-MSU-RATES-MIB
This table provides information on the traffic in MUS
for each processor in both directions. Any MSU in which
a processor is involved will be counted. Here are some
examples of how MSUs would be counted.
Traditional SS7 Links:
MSU is received on Line card 1 that supports SS7 link and
MSU is routed directly to line card 2 that supports output
link. Line card 1 processor information will be updated to
indicate it received MSU and line card 2 processor
information will be updated to indicate it sent MSU.
IP/SCTP based SS7 Links:
IP based SS7 Links can be terminated on linecard or owned
by the main processor. When SS7 link is terminated on main
processor only the main processor information will be
updated. The line card processor that owns the IP interface
will be involved but will not be included in measurements.
When the SS7 link is terminated on line card its processor
information will be updated.
It is important to note that packets exchanged for SCTP
associations are different from SS7 MSUs. More than one
SS7 MSU can be transmitted in a single IP packet. Also,
the SCTP association exchanges control packets that are
not counted as SS7 MSUs.
cimrMsuTrafficTable OBJECT-TYPE SYNTAX SEQUENCE OF CimrMsuTrafficEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides information on the traffic in MUS for each processor in both directions. Any MSU in which a processor is involved will be counted. Here are some examples of how MSUs would be counted. Traditional SS7 Links: MSU is received on Line card 1 that supports SS7 link and MSU is routed directly to line card 2 that supports output link. Line card 1 processor information will be updated to indicate it received MSU and line card 2 processor information will be updated to indicate it sent MSU. IP/SCTP based SS7 Links: IP based SS7 Links can be terminated on linecard or owned by the main processor. When SS7 link is terminated on main processor only the main processor information will be updated. The line card processor that owns the IP interface will be involved but will not be included in measurements. When the SS7 link is terminated on line card its processor information will be updated. It is important to note that packets exchanged for SCTP associations are different from SS7 MSUs. More than one SS7 MSU can be transmitted in a single IP packet. Also, the SCTP association exchanges control packets that are not counted as SS7 MSUs." ::= { cimrTables 2 }
cimrMsuTrafficTable OBJECT-TYPE SYNTAX SEQUENCE OF CimrMsuTrafficEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "This table provides information on the traffic in MUS for each processor in both directions. Any MSU in which a processor is involved will be counted. Here are some examples of how MSUs would be counted. Traditional SS7 Links: MSU is received on Line card 1 that supports SS7 link and MSU is routed directly to line card 2 that supports output link. Line card 1 processor information will be updated to indicate it received MSU and line card 2 processor information will be updated to indicate it sent MSU. IP/SCTP based SS7 Links: IP based SS7 Links can be terminated on linecard or owned by the main processor. When SS7 link is terminated on main processor only the main processor information will be updated. The line card processor that owns the IP interface will be involved but will not be included in measurements. When the SS7 link is terminated on line card its processor information will be updated. It is important to note that packets exchanged for SCTP associations are different from SS7 MSUs. More than one SS7 MSU can be transmitted in a single IP packet. Also, the SCTP association exchanges control packets that are not counted as SS7 MSUs." ::= { cimrTables 2 }
Vendor: Cisco
Module: CISCO-ITP-MSU-RATES-MIB
[Automatically extracted from oidview.com]
cimrMsuTrafficTable OBJECT-TYPE SYNTAX SEQUENCE OF CimrMsuTrafficEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides information on the traffic in MUS for each processor in both directions. Any MSU in which a processor is involved will be counted. Here are some examples of how MSUs would be counted. Traditional SS7 Links: MSU is received on Line card 1 that supports SS7 link and MSU is routed directly to line card 2 that supports output link. Line card 1 processor information will be updated to indicate it received MSU and line card 2 processor information will be updated to indicate it sent MSU. IP/SCTP based SS7 Links: IP based SS7 Links can be terminated on linecard or owned by the main processor. When SS7 link is terminated on main processor only the main processor information will be updated. The line card processor that owns the IP interface will be involved but will not be included in measurements. When the SS7 link is terminated on line card its processor information will be updated. It is important to note that packets exchanged for SCTP associations are different from SS7 MSUs. More than one SS7 MSU can be transmitted in a single IP packet. Also, the SCTP association exchanges control packets that are not counted as SS7 MSUs." ::= { cimrTables 2 }
cimrMsuTrafficTable OBJECT-TYPE SYNTAX SEQUENCE OF CimrMsuTrafficEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides information on the traffic in MUS for each processor in both directions. Any MSU in which a processor is involved will be counted. Here are some examples of how MSUs would be counted. Traditional SS7 Links: MSU is received on Line card 1 that supports SS7 link and MSU is routed directly to line card 2 that supports output link. Line card 1 processor information will be updated to indicate it received MSU and line card 2 processor information will be updated to indicate it sent MSU. IP/SCTP based SS7 Links: IP based SS7 Links can be terminated on linecard or owned by the main processor. When SS7 link is terminated on main processor only the main processor information will be updated. The line card processor that owns the IP interface will be involved but will not be included in measurements. When the SS7 link is terminated on line card its processor information will be updated. It is important to note that packets exchanged for SCTP associations are different from SS7 MSUs. More than one SS7 MSU can be transmitted in a single IP packet. Also, the SCTP association exchanges control packets that are not counted as SS7 MSUs." ::= { cimrTables 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.529.1.2.2.1 | cimrMsuTrafficEntry | 9 | 9 | Each entry represents a processor traffic in a particular direction and is updated at end of interval specified by the cimrMsuRa… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.529.1.2.1 | cimrMsuProcTable | 1 | 10 | This table provides information associated with each processor. Thresholds are provided to control the behavior of the following… |
| 1.3.6.1.4.1.9.9.529.1.2.3 | cimrMsuDistTable | 1 | 11 | This table provides distribution of MSU rates per processor in both the transmit and receive directions. The MSU rates are conver… |