CISCO-ITP-MLR-MIB
The CISCO-ITP-MLR-MIB provides management access to Cisco IP Transfer Point (ITP) hardware and software for monitoring and controlling Multi-layer Routing (MLR) of SS7 Message Signal Units (MSUs) transported over IP. It exposes metrics and control parameters for routing decisions based on SCCP, TCAP, and MAP layer attributes (such as A/B addresses, protocol identifiers, and operation codes) to manage SMS Mobile Originated/Terminated traffic via Global Title Translation, trigger processing, and Weighted Round Robin load balancing.
Imported Objects
Objects
179 total| Object Name |
|---|
ciscoMlrMIB MODULE-IDENTITY .1.3.6.1.4.1.9.9.396 |
ciscoMlrMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.396.0 |
ciscoMlrTableLoad NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.396.0.1 |
ciscoMlrMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.396.1 |
cmlrScalars OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.396.1.0 |
cmlrTableLoadNotifEnabledrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.0.1 |
cmlrInstTable SEQUENCE OF CmlrInstTableEntry .1.3.6.1.4.1.9.9.396.1.1 |
cmlrInstTableEntry CmlrInstTableEntry .1.3.6.1.4.1.9.9.396.1.1.1 |
cmlrInstLastChangedro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.1.1.1 |
cmlrInstLastLoadTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.1.1.2 |
cmlrInstLoadStatusro CItpTcTableLoadStatus (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.1.1.3 |
cmlrInstLastURLro CItpTcURL (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.1.1.4 |
cmlrInstRoutedCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.5 |
cmlrInstAbortCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.6 |
cmlrInstContinueCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.7 |
cmlrInstSmsMoCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.8 |
cmlrInstSmsMtCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.9 |
cmlrInstSriSmCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.10 |
cmlrInstSmdPpCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.11 |
cmlrInstAlertScCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.12 |
cmlrInstSmsRequestCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.13 |
cmlrInstSmsNotifCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.14 |
cmlrInstUnsupSCCPmsgTypeCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.15 |
cmlrInstUnsupSegSCCPmsgCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.16 |
cmlrInstUnsupportedMsgCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.17 |
cmlrInstParsingErrorCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.18 |
cmlrInstNoResultCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.19 |
cmlrInstResultContinueCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.20 |
cmlrInstNoServerDiscardCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.21 |
cmlrInstResultGttCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.22 |
cmlrInstUnparsedCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.23 |
cmlrInstResultBlockCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.24 |
cmlrInstGTImismatchCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.25 |
cmlrInstAddrConvFailureCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.26 |
cmlrInstDestUnavailableCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.27 |
cmlrInstFailedTrigMatchCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.28 |
cmlrInstDiscontinuityTimero TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.1.1.29 |
cmlrInstNoServerContinueCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.30 |
cmlrInstResultAsCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.31 |
cmlrInstResultPcCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.32 |
cmlrInstResultPcSsnCountsro Counter32 UNITS "packets" .1.3.6.1.4.1.9.9.396.1.1.1.33 |
cmlrTriggerTable SEQUENCE OF CmlrTriggerTableEntry .1.3.6.1.4.1.9.9.396.1.2 |
cmlrTriggerTableEntry CmlrTriggerTableEntry .1.3.6.1.4.1.9.9.396.1.2.1 |
cmlrTableName CmlrName .1.3.6.1.4.1.9.9.396.1.2.1.1 |
cmlrTriggerNumber CmlrId .1.3.6.1.4.1.9.9.396.1.2.1.2 |
cmlrTriggerParametersrw Bits .1.3.6.1.4.1.9.9.396.1.2.1.3 |
cmlrTriggerGtrw CItpTcGtaLongDisplay (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.4 |
cmlrTriggerTransTyperw CgsccpGttTransType (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.5 |
cmlrTriggerGtirw CgsccpGttGlobalTitleInd (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.6 |
cmlrTriggerNprw CItpTcNumberingPlan (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.7 |
cmlrTriggerNairw CItpTcNAI (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.8 |
cmlrTriggerPcrw CItpTcPointCode (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.9 |
cmlrTriggerSsnrw CItpTcSubSystemNumber (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.10 |
cmlrTriggerDpcrw CItpTcPointCode (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.11 |
cmlrTriggerOpcrw CItpTcPointCode (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.12 |
cmlrTriggerOpcMaskrw CItpTcPointCodeMask (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.13 |
cmlrTriggerSirw CItpTcServiceIndicator (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.14 |
cmlrTriggerNetworkrw CItpTcNetworkName (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.2.1.15 |
cmlrTriggerRulesetrw CmlrRuleSetName .1.3.6.1.4.1.9.9.396.1.2.1.16 |
cmlrTriggerActivero TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.2.1.17 |
cmlrTriggerStartDateAndTimerw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.2.1.18 |
cmlrTriggerEndDateAndTimerw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.2.1.19 |
cmlTriggerPreliminaryMatchCountsro Counter32 .1.3.6.1.4.1.9.9.396.1.2.1.20 |
cmlrTriggerMatchCountsro Counter32 .1.3.6.1.4.1.9.9.396.1.2.1.21 |
cmlrTriggerRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.2.1.22 |
cmlrSubTriggerTable SEQUENCE OF CmlrSubTriggerTableEntry .1.3.6.1.4.1.9.9.396.1.3 |
cmlrSubTriggerTableEntry CmlrSubTriggerTableEntry .1.3.6.1.4.1.9.9.396.1.3.1 |
cmlrSubTriggerNumber CmlrId .1.3.6.1.4.1.9.9.396.1.3.1.1 |
cmlrSubTriggerParametersrw Bits .1.3.6.1.4.1.9.9.396.1.3.1.2 |
cmlrSubTriggerGtrw CItpTcGtaLongDisplay (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.4 |
cmlrSubTriggerTransTyperw CgsccpGttTransType (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.5 |
cmlrSubTriggerGtirw CgsccpGttGlobalTitleInd (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.6 |
cmlrSubTriggerNprw CItpTcNumberingPlan (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.7 |
cmlrSubTriggerNairw CItpTcNAI (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.8 |
cmlrSubTriggerPcrw CItpTcPointCode (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.9 |
cmlrSubTriggerSsnrw CItpTcSubSystemNumber (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.10 |
cmlrSubTriggerNetworkrw CItpTcNetworkName (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.3.1.11 |
cmlrSubTriggerRulesetrw CmlrRuleSetName .1.3.6.1.4.1.9.9.396.1.3.1.12 |
cmlrSubTriggerMatchCountsro Counter32 .1.3.6.1.4.1.9.9.396.1.3.1.13 |
cmlrSubTriggerRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.3.1.14 |
cmlrAddressTable SEQUENCE OF CmlrAddressTableEntry .1.3.6.1.4.1.9.9.396.1.4 |
cmlrAddressTableEntry CmlrAddressTableEntry .1.3.6.1.4.1.9.9.396.1.4.1 |
cmlrAddressTableName CmlrName .1.3.6.1.4.1.9.9.396.1.4.1.1 |
cmlrAddressType CmlrAddressType .1.3.6.1.4.1.9.9.396.1.4.1.2 |
cmlrAddressDigits CmlrAddressDigits .1.3.6.1.4.1.9.9.396.1.4.1.3 |
cmlrAddressExactMatch TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.4.1.4 |
cmlrAddressResultParametersrw CmlrResultParameters .1.3.6.1.4.1.9.9.396.1.4.1.5 |
cmlrAddressResultNetworkrw CItpTcNetworkName (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.6 |
cmlrAddressResultTyperw CmlrResultType .1.3.6.1.4.1.9.9.396.1.4.1.7 |
cmlrAddressResultOctetrw CmlrResultOctet .1.3.6.1.4.1.9.9.396.1.4.1.8 |
cmlrAddressResultTransTyperw CgsccpGttTransType (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.9 |
cmlrAddressResultGtirw CgsccpGttGlobalTitleInd (CISCO-ITP-GSCCP-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.10 |
cmlrAddressResultNprw CItpTcNumberingPlan (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.11 |
cmlrAddressResultNairw CItpTcNAI (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.12 |
cmlrAddressResultPcrw CItpTcPointCode (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.13 |
cmlrAddressResultSsnrw CItpTcSubSystemNumber (CISCO-ITP-TC-MIB) .1.3.6.1.4.1.9.9.396.1.4.1.14 |
cmlrAddressMatchCountsro Counter32 .1.3.6.1.4.1.9.9.396.1.4.1.15 |
cmlrAddressRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.396.1.4.1.16 |
cmlrRuleSetTable SEQUENCE OF CmlrRuleSetTableEntry .1.3.6.1.4.1.9.9.396.1.5 |
cmlrRuleSetTableEntry CmlrRuleSetTableEntry .1.3.6.1.4.1.9.9.396.1.5.1 |
CISCO-ITP-MLR-MIB Technical Reference Overview
The CISCO-ITP-MLR-MIB SNMP MIB module published by Cisco defines 179 managed OID objects, including 155 scalar/column metrics, 8 SNMP tables, and 1 trap/notification events anchored at base OID .1.3.6.1.4.1.9.9.396. Key tabular structures include cmlrInstTable, cmlrTriggerTable, cmlrSubTriggerTable, cmlrAddressTable, cmlrRuleSetTable, cmlrRuleTable. Monitored SNMP traps/notifications include ciscoMlrTableLoad.
Key OID Definitions in CISCO-ITP-MLR-MIB
.1.3.6.1.4.1.9.9.396The MIB for providing information about Multi-layer Routing(MLR). This MIB will provide information used to control and measure SS7 messages signalling units in a SS7 Network. Message Signalling Units are routed based on information found in the SCCP, TCAP, MAP, and MAP-user layers. It uses information from these layers to make customizable routing decision based on the following criteria. - message A-address (origination SME) - message B-address (destination SME) - protocol identifier - operation code - called party address - calling party address The Cisco IP Transfer Point (ITP) is a hardware and software solution that transports SS7 traffic using IP. Each ITP node provides function similar to SS7 signalling point. The Multi-layer SMS router will be developed in compliance to the following standards. - GSM MAP v1, v2 and v3 MO SMS formats - GSM MAP SMS user information for MO messages - IS-41 MAP Mobile Originated SMS formats for Revisions A thru D. Acronyms and Terms A-address The originating SME of the short message. ANSI-41 ANSI standard for defining cellular radio telecommunications inter-system operation. B-address The destination SME of the short message. BCH Binary Coded Hexadecimal CdPA The SCCP Called Party Address field. CgPA The SCCP Calling Party Address field. GSM ITU standard for defining the Global System for Mobile communications. GTT Global Title Translation. A function normally performed in an STP, GTT is the procedure by which the destination signalling point and subsystem number(SSN) is determined from GTA digits (i.e., the global title) present in the signalling message. IMEI International Mobile Equipment Identity IMSI International Mobile Station Identity or International Mobile Subscriber Identity A mobile station identifier typically used in GSM networks, but is also defined for use in IS-41 networks via IS-751. IS-41 ANSI standard for defining cellular radio telecommunications inter-system operation. Unless otherwise stated, this refers to the IS-41-D specification. MAP SS7 Mobile Application Part. This layer provides mobility procedures to SS7 network applications. MAP is generically used to refer to both GSM-MAP, and the IS-41-D MAP Protocol. MC Message Center. Network element responsible for relaying and store-and-forwarding of short messages in ANSI-41 networks. MDN Mobile Directory Number. A 10-digit North American Numbering Plan number assigned to mobile users in IS-41 networks. It may be different from the MIN. MIN Mobile Identification Number. The 10-digit North American Numbering Plan number assigned to mobile users in IS-41 networks. It may be different from the MDN. MLR Multi-layer Routing MO Mobile Originated. This term is used to refer to an SMS message that is being sent from an MS to the SMSC. MS Mobile Subscriber. MS mobile station MSU Message Signal Unit MT Mobile Terminated. This term is used to refer to an SMS message that is being sent from an SMSC to an MS. MTP Message Transfer Part MTP1 Layers 1 (physical) MTP2 Layer 2 (data) and MTP3 Layer 3 (network) M2PA SS7 MTP2-User Peer-to-Peer Adaptation Layer specified by the IETF SIGTRAN working group, which provides SCTP/IP based links for MTP3. M3UA SS7 MTP3 User Adaptation Layer specified by RFC 3332 for MTP3 users like ISUP. RR Round Robin. A balancing algorithm that evenly distributes traffic among available servers. SCCP Signalling Connection Control Part. As part of the SS7 signalling protocol, it provides connectionless and connection-oriented network services above MTP Level 3. SCP Service Control Point. An element of an SS7-based Intelligent Network which performs various service functions, such as number translation, call setup and tear down, etc. SCTP Stream Control Transmission Protocol. A protocol designed by the SigTran working group of the IETF to transport messages reliably over IP networks(RFC 2960). It has been specifically designed with PSTN signalling in mind, but is meant to be a general IP transport protocol. SG Signalling Gateway. SIM Subscriber Identity Module SME Short Message Entity. An entity that may send or receive short messages, and may be fixed or mobile. SM Short Message SMD-PP Short Message Delivery Point to Point. SMS Short Message Service, as defined in GSM and IS-41-D. SMS-MO Short Message Service Mobile Originated. SMS-MT Short Message Service Mobile Terminated. SMSC Short Message Service Center. Network element responsible for relaying and store-and-forwarding of short messages. SRI Send Routing Information or Send Routing Information for Short Messages. Refers to the procedure by which an SMSC requests the HLR to send current routing information for a particular mobile user. SRI-SM Send Routing Information Short Message SSP Service Switching Point. An element of an SS7-based Intelligent Network that performs call origination, termination, or tandem switching. STP Signal Transfer Point. An element of an SS7-based Intelligent Network that performs routing of the SS7 signalling. SUA SS7 SCCP User Adaptation Layer specified by IETF SIGTRAN for SCCP users, like GSM MAP, UMTS RANAP, CDMA IS-41, CDMA IS-634, IN INAP, CAMEL CAP. TCAP Transaction Capability Application Part. The application layer of the SS7 signalling protocol. WRR Weighted Round Robin. A variation of the round robin algorithm that uses server weights to allow uneven distribution of traffic among a set of available servers. Multi-layer processing consists of four basic phases as follows. Global Title Processing Trigger Processing(primary and secondary) Rule Set Processing Result group Processing Example scenario. The SMS messages sent by origin SME (typically a mobile handset) and sent to the MSC controlling the area in which the origin SME resides. The MSC then initiates a dialogue with the home SMSC specified by the origin SME to route the SMS MO message. SMS MO traffic will arrive as an SCCP packet, and the Routing Indicator(RI) may specify either 'route-on-global-title' (RI=GT) or 'route-on-subsystem' (RI=PC/SSN). The destination GT will be used to locate the global title address that applies to the destination address. Triggers are applied directly to global title addresses. Therefore, trigger processing consists of checking for the existence of primary trigger and then processing of secondary triggers. If the message matches a trigger then rule set processing can be performed to determine what will be modified in message and how the message will be routed. The messages may be sent to new destination address, application server, point-code or result group. Or it could be forwarded without any modification (CONTINUE) or it could be dropped (BLOCK). Result processing balances the delivery of messages to Point-codes or application servers based on Weighted Round Robin(WRR). ********************************************
.1.3.6.1.4.1.9.9.396.1.1A table that is used to provide information and measurements related to multi-layer routing per per signalling point.
.1.3.6.1.4.1.9.9.396.1.2A table that is used to configure specific routing keys to act as trigger for multi-layer routing. Entries are added to this table via cmlrTriggerRowStatus in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.3A table that is used to define additional triggers that work in combination with values specified in specific cmlrTriggerTable. Entries are added to this table via cmlrSubTriggerRowStatus in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.4A table used to create a collection of addresses that can be searched for exact or best matches. Entries are added to this table via cmlrAddressRowStatus in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.5A table that is used to specify attributes of an application-layer message to be matched and the resulting behavior for handling the message. Entries are added to this table via cmlrRuleSetRowStatus in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.6A table that is used to specify attributes of an application-layer message to be matched and the resulting behavior for handling the message. Entries are added to this table via cmlrRuleRowStatus in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.8A table used to identify a group of results and define parameter that apply to all result within the group. Entries are added to this table via cmlrResultSetRowStatus object in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.1.9A table used to identify a group of destination resources The result group lists the appropriate destination resources, and the mechanism used to select a single destination for a given packet. State information is determined for each possible destination. Congested resources will only be used if no available, non-congested destinations exist. Only available destinations are considered for routing. Entries are added to this table via cmlrResultRowStatus object in accordance with the RowStatus convention.
.1.3.6.1.4.1.9.9.396.0.1This notification is generated whenever a load operation is started or completed. Route table configurations can be loaded by CLI requests. In addition, route tables can loaded using configuration statements. This allows mlr tables to be reloaded whenever a device restarts.
.1.3.6.1.4.1.9.9.396.1.0.1A control to enable or disable ciscoMlrTableLoad notifications as follows: 'true' Indicates that the ciscoMlrTableLoad notification should be generated when the load operations is started or completed. That is, the notification generation is enabled. 'false' Indicates that ciscoMlrTableLoad notification generation is disabled.
.1.3.6.1.4.1.9.9.396.1.1.1Each entry in this table provides information on each signalling pointer supported by this device. Each entry provides information on modification to the configuration statements related to multi-layer routing and general measurements.
.1.3.6.1.4.1.9.9.396.1.1.1.1The value of sysUpTime at the time of the last creation or deletion of an entry in the Multi-Layer routing table defined for this signalling point. If the local network management subsystem is re-initialized, then this object contains the sysUpTime at the time when this occurred. This value can be used to prevent unnecessary walks of the various take supporting multi-layer routing.
.1.3.6.1.4.1.9.9.396.1.1.1.2The value of sysUpTime at the time of the last load of the Multi-Layer Routing table using file format for this signalling point.
.1.3.6.1.4.1.9.9.396.1.1.1.3The status of the current load or status from the prior load operation. This object will have a value of loadInProgress while the load operation is in progress. The cmlrInstLastLoadTime contains a timestamp indicating when the load operation is completed.
.1.3.6.1.4.1.9.9.396.1.1.1.4The last URL used to load MLR table.
.1.3.6.1.4.1.9.9.396.1.1.1.5Count of the number of times a packet was routed by MLR. This value is incremented when packet is routed with result type of 'asname', 'gt', 'pc' or 'pcSsn'.
.1.3.6.1.4.1.9.9.396.1.1.1.6Count of message signal units that could not be processed because of invalid data or were explicitly blocked as a result of MLR processing. The message signalling units will be discarded.
.1.3.6.1.4.1.9.9.396.1.1.1.7Count of message signal units that were passed back to normal SCCP processing.
.1.3.6.1.4.1.9.9.396.1.1.1.8Count of message signal units with operation type GSM-MAP SMS-MO.
.1.3.6.1.4.1.9.9.396.1.1.1.9Count of message signal units with operation type GSM-MAP SMS-MT.
.1.3.6.1.4.1.9.9.396.1.1.1.10Count of message signal units with operation type GSM-MAP SRI-SM.
.1.3.6.1.4.1.9.9.396.1.1.1.11Count of message signal units with operation type ANSI-41 SMD-PP.
.1.3.6.1.4.1.9.9.396.1.1.1.12Count of message signal units with operation type GSM-MAP AlertSC.
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.
The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.
The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.
SNMP MIB module
The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.
The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.