The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Management Information Base (MIB) on the Cisco ASR 903 Series Aggregation Services Routers. It includes the following sections:
Each MIB description lists relevant constraints about the implementation of the MIB on the Cisco ASR 903 Series Router platform. Any objects not listed in the table are implemented as defined in the MIB. For detailed MIB descriptions, see the standard MIB.
Note Not all the MIBs included in a Cisco IOS XE software release are fully supported by the Cisco ASR 903 Series Router. Some MIBs are not supported at all. Other MIBs might work, but they have not been tested on the router. In addition, some MIBs are deprecated, but cannot be removed from the software. When a MIB is included in the image, it does not necessarily mean that is supported by the Cisco ASR 903 Series Router platform.
The subsequent tables list the following categories of MIBs in the Cisco ASR 903 Series Router Image on the Cisco ASR 903 Series Router:
The MIB version string indicates the date and time that it was most recently modified. The format is YYMMDDHHMMZ or YYYYMMDDHHMMZ, where:
Note For example, 9502192015Z and 199502192015Z represent 8:15 GMT on 19 February 1995. Years after 1999 use the four-digit format. Years 1900-1999 may use the two-digit or four-digit format.
Note In the following tables you might see the term Unknown. This term refers to the MIB that does not have a recorded time stamp indicating the latest modification.
Table 3-1 lists the MIBs that are supported and verified on the Cisco ASR 903 Series Router in the following Cisco IOS XE software release. The table lists the MIBs, corresponding notification names, and applicable MIB versions.
|
|
|
---|---|---|
ciscoFlashPartitioningCompletionTrap ciscoFlashMiscOpCompletionTrap |
||
CISCO-OSPF-TRAP-MIB (draft-ietf-ospf-mib-update-05) |
||
rttMonConnectionChangeNotification |
||
mplsLdpInitSessionThresholdExceeded |
||
Table 3-2 lists the MIBs that are supported and unverified on the Cisco ASR 903 Series Router in the following Cisco IOS XE software release. The table lists the MIBs, corresponding notification names, and applicable MIB versions.
Table 3-3 lists the MIBs that are unsupported and unverified on the Cisco ASR 903 Series Router in the following Cisco IOS XE software release.
|
|
|
---|---|---|
The ATM-MIB (RFC 1695) contains the ATM and ATM adaptation layer 5 (AAL5) objects to manage logical and physical entities. It also provides the functionality to manage the relationship between logical and physical entities, such as ATM interfaces, virtual links, cross connects, and AAL5 entities and connections.
The BGP4-MIB (RFC 1657) provides access to the implementation information for the Border Gateway Protocol (BGP). The MIB provides:
The CISCO-AAL5-MIB contains objects to manage performance statistics for ATM adaptation layer 5 (AAL5) virtual channel connections (VCCs). This MIB also contains information such as packets and octets that are received and transmitted on the VCC, which is missing in cAal5VccTable in RFC 1695.
The CISCO-ATM-EXT-MIB contains extensions to the Cisco ATM that are used to manage ATM entities. This MIB provides additional AAL5 performance statistics for a virtual channel connection (VCC) on an ATM interface.
Table 3-4 lists the constraint that the Cisco ASR 903 Series Router places on the objects in the CISCO-ATM-EXT-MIB.
|
|
---|---|
|
Note The CISCO-ATM-EXT-MIB has only one table, cAal5VccExtTable. This table augments the aal5VccTable of the CISCO-AAL5-MIB. The cAal5VccExtTable contains additional AAL5 performance parameters.
The CISCO-ATM-IF-MIB provides the functionality required for an ATM interface configuration.
The CISCO-ATM-PVC-MIB provides the functionality to configure a permanent virtual channel (PVC) on an ATM uplink card of a Catalyst 5000 device, and to bind that PVC to a virtual LAN (VLAN).
The CISCO-ATM-PVCTRAP-EXTN-MIB contains objects to extend the functionality of the ATM-MIB. This MIB provides additional notifications and traps for permanent virtual circuits (PVCs) on the Cisco ASR 903 Series Router. The CISCO-ATM-PVCTRAP-EXTN-MIB is supplemented by the CISCO-IETF-ATM2-PVCTRAP-MIB.
The CISCO-BCP-MIB contains objects to manage the Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474.
The CISCO-BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:
The CISCO-BGP-POLICY-ACCOUNTING-MIB contains BGP policy-based accounting information (such as ingress traffic on an interface), which can be used for billing purposes. The MIB provides support for BGP Policy Accounting, which enables you to classify IP traffic into different classes and to maintain statistics for each traffic class.
The MIB contains counts of the number of bytes and packets of each traffic type on each input interface. This information can be used to charge customers according to the route that their traffic travels.
The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer.
Table 3-5 lists the constraints that the router places on the objects in the CISCO-BULK-FILE-MIB.
The CISCO-CALLHOME-MIB contains objects to manage the Call Home feature within the Cisco Call Home architecture framework.
The CISCO-CBP-TARGET-MIB (common class-based policy) contains objects that provide a mapping of targets to which class-based features, such as QoS are applied. A target is a logical interface with which a class-based policy is associated.
The configuration objects in the CISCO-CBP-TARGET-MIB are read-only.
Table 3-6 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-CBP-TARGET-MIB.
|
|
---|---|
|
|
Value is always ciscoCbQos(1) to indicate mapping to CLASS-BASED-QOS-MIB. |
|
Contains the cbQosPolicyIndex value for this service-policy. |
|
The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router.
Table 3-7 lists the constraints that the router places on the objects in the CISCO-CDP-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
The CISCO-CEF-MIB contains objects that manage Cisco Express Forwarding (CEF) technology. CEF is the key data plane forwarding path for Layer 3 IP switching technology. The CISCO-CEF-MIB monitors CEF operational data and provides notification when encountering errors in CEF, through SNMP.
Table 3-8 lists the constraints that the router places on the objects in the CISCO-CEF-MIB.
|
|
---|---|
|
|
|
|
|
|
|
Note Cisco Express Forwarding is a high-speed switching mechanism that a router uses to forward packets from the inbound to the outbound interface.
The CISCO-CIRCUIT-INTERFACE-MIB contains objects to configure the circuit description for an interface. The circuit description identifies circuits on interfaces, such as ATM and Frame Relay, and might be used, for example, to correlate performance statistics on the corresponding interfaces.
The CISCO-CLASS-BASED-QOS-MIB provides read access to quality of service (QoS) configuration information and statistics for Cisco platforms that support the modular QoS CLI.
To understand how to navigate the CISCO-CLASS-BASED-QOS-MIB tables, it is important to understand the relationship between the different QoS objects listed here:
The MIB uses the following indexes to identify QoS features and distinguish among instances of those features:
QoS MIB information is stored in:
Note If a class is defined without any action and is mapped to a policy-map, this class and class-default may return incorrect values for the post policy and drop counters represented in the cbQosCMStatsTable.
Table 3-9 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-CLASS-BASED-QOS-MIB.
The CISCO-CONFIG-COPY-MIB contains objects to copy configuration files on the router. For example, the MIB enables the SNMP agent to copy:
The CISCO-CONFIG-MAN-MIB contains objects to track and save changes to the router configuration. The MIB represents a model of the configuration data that exists elsewhere in the router and in peripheral devices. Its main purpose is to report changes to the running configuration through the SNMP notification ciscoConfigManEvent.
The CISCO-CONTEXT-MAPPING-MIB provides mapping tables that contain the information that a single SNMP agent sometimes needs to support multiple instances of the same MIB. In such cases, network management applications need to know the specific data/identifier values in each context. This is accomplished through the use of multiple SNMP contexts.
The CISCO-DATA-COLLECTION-MIB retrieves data periodically when the data displays as a set of discontinuous rows spread across multiple tables. This MIB facilitates data retrieval of tabular objects. This MIB can be used for performance and accounting purposes, where several row instances of a set of objects are polled over a period of time.
The MIB provides the user a way to specify which objects and which instances are required. In addition the MIB provides two ways in which this data can be retrieved.
Table 3-10 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-DATA-COLLECTION-MIB. Any MIB object not listed in this table is implemented as defined in the MIB.
|
|
---|---|
|
|
|
|
|
|
|
The CISCO-DOT3-OAM-MIB contains objects that manage the new Ethernet Operations, Administration, and Maintenance (OAM) features introduced by the Ethernet in the first mile task force (IEEE 802.3ah).
Table 3-11 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-DOT3-OAM-MIB.
The CISCO-EIGRP-MIB defines the tables that are closely aligned with how the router CLI for Enhanced Interior Gateway Protocol (EIGRP) displays information on EIGRP configurations.
The CISCO-EMBEDDED-EVENT-MGR-MIB provides descriptions and stores events generated by the Cisco Embedded Event Manager. The Cisco Embedded Event Manager detects hardware and software faults and other events such as OIR for the system.
The CISCO-ENHANCED-MEMPOOL-MIB contains objects to monitor memory pools on all of the physical entities on a managed system. It represents the different types of memory pools that may be present in a managed device. Memory use information is provided to users at three different intervals of time: 1 minute, 5 minutes, and 10 minutes. Memory pools can be categorized into two groups, predefined pools and dynamic pools. The following pool types are currently predefined:
Dynamic pools have a pool type value greater than any of the predefined types listed above. Only the processor pool is required to be supported by all devices. Support for other pool types is dependent on the device being managed.
The CISCO-ENHANCED-MEMPOOL-MIB is supported only in the Active RSP module. Table 3-12 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-ENHANCED-MEMPOOL-MIB.
|
|
---|---|
|
|
|
|
|
|
The CISCO-ENTITY-ALARM-MIB enables the Cisco ASR 903 Series Router to monitor the alarms generated by system components, such as chassis, slots, modules, power supplies, fans, and ports.
CISCO-ENTITY-ALARM-MIB supports these modules:
All the other interface types are not supported for this release.
For more information on this MIB, see Appendix A, “CISCO-ENTITY-ALARM-MIB.”
Table 3-13 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-ENTITY-ALARM-MIB.
|
|
---|---|
|
|
|
|
|
|
The ENTITY-MIB table, entPhysicalTable, identifies the physical system components in the router. The following list describes the table objects that describe the alarms for the CISCO-ENTITY-ALARM-MIB:
– Critical—Indicates a severe, service-affecting condition has occurred and that immediate corrective action is imperative, regardless of the time of day or day of the week. For example, online insertion and removal or loss of signal failure when a physical port link is down.
– Major—Used for hardware or software conditions. Indicates a serious disruption of service or the malfunctioning or failure of important hardware. Requires immediate attention and response of a technician to restore or maintain system stability. The urgency is less than in critical situations because of a lesser effect on service or system performance.
– Minor—Used for troubles that do not have a serious effect on service to customers or for alarms in hardware that are not essential to the operation of the system.
– Info—Notification about a condition that could lead to an impending problem or notification of an event that improves operation.
The syntax values are critical(1), major(2), minor(3), and info(4).
Table 3-14 lists the alarm descriptions and severity levels for the T1/E1 ports of the Cisco ASR 903 Series Router. The entries for T1/E1 ports mentioned in this table are always populated for ceAlarmDescrTable and ceAlarmDescrVendorType, irrespective of the presence or absence of ports.
|
|
|
|
---|---|---|---|
Table 3-15 lists the alarm descriptions and severity levels for the Gigabit Ethernet (GE) ports of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Note The 10GE Interface Module (IM) card supports only LAN mode.
Table 3-16 lists the alarm descriptions and severity levels for the SFP Container of the Cisco ASR 903 Series Router.
|
|
|
---|---|---|
Table 3-17 lists the alarm descriptions and severity levels for the IMs of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-18 lists the alarm descriptions and severity levels for the Cisco ASR 903 Series Router sensors.
|
|
|
|
---|---|---|---|
Note These alarms are not supported for XCVR sensors. The CISCO-ENTITY-SENSOR-MIB can be used to monitor the alarms listed in Table 3-18.
Table 3-19 lists the alarm descriptions and severity levels for the IM containers of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-20 lists the alarm descriptions and severity levels for the Cisco ASR 903 Series Router USB ports.
|
|
|
|
---|---|---|---|
Table 3-21 lists the alarm descriptions and severity levels for the RSP containers of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-22 lists the alarm descriptions and severity levels for the power supply bay of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-23 lists the alarm descriptions and severity levels for the RSPs of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Note ‘Harddisk Missing’ and ‘No working ESP’ alarms are not supported in Cisco ASR 903 Series Router.
The vendor OID for the RSP Module is set to cevModuleUnknownCard for the following conditions:
Table 3-24 lists the alarm descriptions and severity levels for the unknown RSP modules of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-25 lists the alarm descriptions and severity levels for the power supply module of the Cisco ASR 903 Series Router.
|
|
|
|
---|---|---|---|
Table 3-26 lists the alarms that the FanTray module of the Cisco ASR 903 Series Router supports.
|
|
|
|
---|---|---|---|
Note The ceAlarmHistTable contains alarm data asserted or cleared (or both) in the current active RSP. It does not retain the alarms asserted or cleared (or both) in the previous active RSP. The data contained in ceAlarmHistTable is refreshed after a switchover.
The CISCO-ENTITY-EXT-MIB contains extensions for the processor modules listed in the ENTITY-MIB entPhysicalTable. A processor module is any physical entity that has a CPU, RAM, and NVRAM, and can load a boot image and save a configuration. The extensions in this MIB provide information, such as RAM and NVRAM sizes, configuration register settings, and bootload image name for each processor module.
Only the active RP processor is supported in Cisco ASR 903 Series Router. The standby RSP is not managed in this MIB.
Table 3-27 lists the constraints that the router places on the objects in the CISCO-ENTITY-EXT-MIB.
|
|
---|---|
|
|
|
The CISCO-ENTITY-FRU-CONTROL-MIB contains objects to configure and monitor the status of the field replaceable units (FRUs) on the Cisco ASR 903 Series Router listed in the ENTITY-MIB entPhysicalTable. A FRU is a hardware component (such as, a line card and module, fan, or power supply) that can be replaced on site.
Table 3-28 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-ENTITY-FRU-CONTROL-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The CISCO-ENTITY-SENSOR-MIB contains objects that support the monitoring of sensors. The MIB is applicable to sensors present in various transceiver modules. This MIB allows to monitor sensor values and thresholds on sensors that are discovered by the ENTITY-MIB.
Table 3-29 lists the constraints that the Cisco ASR 903 Series Router places on the CISCO-ENTITY-SENSOR-MIB.
|
|
---|---|
|
|
|
|
Note The MIB object entSensorThresholdEvaluation for shared port adapter (SPA) module is not supported as the SPA sensor is not monitored and the sensor value is updated only on demand. To obtain the entSensorThresholdEvaluation for SPA sensors, compare the entSensorValue retrieved from the agent with thresholds.
Table 3-30 lists CISCO-ENTITY-SENSOR-MIB sensor objects and their usage values for Cisco ASR 903 Series Router transceivers in the entSensorValueTable and entSensorThresholdTable.
Note The RSPs and power supplies support various sensors. These sensors are supported in the CISCO-ENTITY-SENSOR-MIB.
The CISCO-ENTITY-VENDORTYPE-OID-MIB defines the object identifiers (OIDs) assigned to various Cisco ASR 903 Series Router components. The OIDs in this MIB are used as values for the entPhysicalVendorType field in the entPhysicalTable of the ENTITY MIB. Each OID uniquely identifies a type of physical entity:
The CISCO-ERM-MIB contains objects to manage resources, such as CPU, memory, buffers and so on. The two important scenarios where the Embedded Resource Manager (ERM) framework is used are:
The CISCO-ETHER-CFM-MIB defines the managed objects and notifications for Ethernet Connectivity Fault Management (CFM) operation. CFM is an end-to-end per service instance for the Ethernet layer Operations, Administration and Management (OAM) protocol.
The CISCO-ETHERLIKE-EXT-MIB defines generic objects for the Ethernet-like network interfaces.
Table 3-31 lists the constraint that the Cisco ASR 903 Series Router places on the objects in the CISCO-ETHERLIKE-EXT-MIB.
|
|
---|---|
|
The CISCO-EVC-MIB defines the managed objects and notifications describing Ethernet Virtual Connections (EVCs).
Table 3-32 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-EVC-MIB.
|
|
---|---|
|
|
|
|
|
|
The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.
Table 3-33 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-FLASH-MIB.
|
|
---|---|
|
|
|
|
|
|
Note The index of files stored in USB changes frequently since the files are mounted and unmounted after regular intervals.
Note When both primary and secondary RSPs are up and running, entities for the standby USB flash and Flash disk are not populated for CISCO-FLASH-MIB. Compact Flash is not supported in Cisco ASR 903 Series Router. Therefore, it is not modelled in the CISCO-FLASH-MIB.
Note After the file is copied successfully via TFTP, it takes atleast 50 seconds to reflect the correct file size in the ciscoFlashFileSize object.
The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management. This MIB has no known constraints and all objects are implemented as defined in the MIB.
The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB which defines the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281. The extensions cover assigning of secondary IP addresses and modifying an HSRP group’s priority.
The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281.
The CISCO-IETF-ATM2-PVCTRAP-MIB contains objects that supplement the ATM-MIB. This MIB implements the Virtual Channel Link (VCL) section of the IETF document "draft-ietf-atommib-atm2-11.txt," Section 9 ATM Related Trap Support.
The CISCO-IETF-BFD-MIB contains objects to manage the Bidirectional Forwarding Detection (BFD) protocol. BFD detects faults in the bidirectional path between two forwarding engines, including interfaces, data links, and the forwarding engines themselves with potentially very low latency. It operates independently of media, data protocols, and routing protocols.
The CISCO-IETF-DHCP-SERVER-MIB contains objects for the entities implementing the server side of the Bootstrap Protocol (BOOTP) and the DHCP for IP version 4 (IPv4). This MIB does not include support for updating Dynamic Domain Name System (DDNS) and DHCP failover protocol.
The CISCO-IETF-DHCP-SERVER-EXT-MIB is an extension of the CISCO-IETF-DHCP-SERVER-MIB.
The CISCO-IETF-ISIS-MIB introduces network management support for the IS-IS routing protocol through the use of IS-IS MIB table entries, MIB objects, and MIB trap notification objects. A new CLI is added to enable SNMP notifications for the objects. Notifications are provided for errors and other significant event information for the IS-IS network.
The CISCO-IETF-MPLS-ID-STD-03-MIB contains object definitions for Multiprotocol Label Switching (MPLS) Traffic Engineering in transport networks.
Table 3-34 lists the constraints that the router places on the objects in the CISCO-IETF-MPLS-ID-STD-03-MIB.
|
|
---|---|
|
The CISCO-IETF-MPLS-TE-EXT-STD-03-MIB contains generic object definitions for MPLS Traffic Engineering in transport networks.
Table 3-34 lists the constraints that the router places on the objects in the CISCO-IETF-MPLS-TE-EXT-STD-03-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
|
|
The CISCO-IETF-PPVPN-MPLS-VPN-MIB is an extension of the MPLS-VPN-MIB. It contains a new notification, mplsNumVrfRouteMaxThreshCleared, which was added with MPLS-VPN-MIB-DRAFT-05.
The CISCO-IETF-PW-ATM-MIB contains managed object definitions for pseudowire (PW) emulation of ATM over packet-switched networks (PSNs).
Table 3-36 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-IETF-PW-ATM-MIB.
|
|
---|---|
|
|
The CISCO-IETF-PW-ENET-MIB contains objects that describe the model for managing Ethernet point-to-point pseudowire services over a packet-switched network (PSN).
Table 3-37 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-IETF-PW-ENET-MIB.
|
|
---|---|
|
|
|
The CISCO-IETF-PW-MIB contains managed object definitions for pseudowire (PW) operations.
Table 3-38 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-IETF-PW-MIB.
|
|
---|---|
|
|
|
|
|
|
The CISCO-IETF-PW-MPLS-MIB contains objects that complement the CISCO-IETF-PW-MIB for PW operation over MPLS.
Table 3-39 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-IETF-PW-MPLS-MIB.
|
|
---|---|
|
|
|
The CISCO-IETF-PW-TDM-MIB contains managed object definitions for encapsulating TDM (T1,E1, T3, E3, NxDS0) as pseudowires over packet-switching networks (PSNs).
The CISCO-IF-EXTENSION-MIB contains objects that provide additional interface-related information that is not available in the IF-MIB (RFC 2863).
Table 3-40 lists constraints that the Cisco ASR 903 Series Router places on the object in the CISCO-IF-EXTENSION-MIB
The CISCO_IGMP-FILTER-MIB provides a mechanism for users to configure the system to intercept Internet Group Management Protocol (IGMP) joins for IP Multicast groups identified in this MIB and only allow certain ports to join certain multicast groups.
The CISCO-IMAGE-MIB contains objects that identify the capabilities and characteristics of the Cisco IOS XE image.
The CISCO-IMAGE-LICENSE-MGMT-MIB contains objects to manage the running image level of a Cisco device. The licensing mechanism provides flexibility to run a device on a chosen image level. This mechanism is referred to as image level licensing. Image level licensing leverages the universal image-based licensing solution.
The CISCO-IP-STAT-MIB contains objects to manage the collection and display of IP statistics, categorized by IP precedence and the MAC address associated with IP packets. To use the MIB to access additional IP statistics, the ip accounting mac-address and ip accounting precedence commands must be issued at the CLI.
The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.
The CISCO-IPSLA-ETHERNET-MIB contains objects to manage IP SLA Auto-Ethernet-CFM operations and Ethernet Jitter statistics. IP SLA is a capability that utilizes active monitoring for network performance. It can be used for network troubleshooting, network assessment, and health monitoring. Ethernet Jitter is used to measure metrics, such as round-trip time (RTT), Jitter, frame loss, and one-way latency by sending multiple enhanced CFM frames at specified interval to a particular Maintenance End Point (MEP).
The CISCO-LAG-MIB contains objects to manage link aggregation (LAG) on the router, as defined by IEEE Standard 802.3ad. The MIB contains link aggregation information that supplements to IEEE8023-LAG-MIB or is specific to Cisco products.
The CISCO-L2-CONTROL-MIB contains objects that provide a control feature for devices with Layer 2 functions, such as the VLAN MAC limit control.
The CISCO-LICENSE-MGMT-MIB contains objects to manage the licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various features in the system.
The CISCO-MAC-NOTIFICATION-MIB is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring devices when there are MAC addresses learned or removed from the forwarding database of the monitored devices.
The CISCO-MEMORY-POOL-MIB contains objects that represents the different types of memory pools that are present in a managed device. Memory pools are categorized into two groups:
The CISCO-MPLS-LSR-EXT-STD-MIB contains generic object definitions for MPLS Label Switching Router (LSR) in transport networks.
Table 3-41 lists the constraints that the router places on the objects in the CISCO-MPLS-LSR-EXT-STD-MIB.
|
|
---|---|
|
|
|
The CISCO-MPLS-TC-EXT-STD-MIB contains textual conventions for MPLS based transport networks.
Table 3-41 lists the constraints that the router places on the objects in the CISCO-MPLS-TC-EXT-STD-MIB.
|
|
---|---|
|
The CISCO-MVPN-MIB contains managed object definitions for the Cisco implementation of multicast in VPNs defined by the Internet draft, draft-rosen-vpn-mcast-05.txt.
The Multicast VPN MIB feature introduces the capability for Simple Network Management Protocol (SNMP) monitoring of a Multicast VPN (MVPN). Using the MVPN MIB, network administrators can access MVRF information from PE routers. This information can be accessed for VPN traffic across multiple CE sites in real time. SNMP operations can be performed to monitor the MVRFs on the PE routers, using the get and set commands. These commands are entered on the Network management system (NMS) workstation for which the SNMP has been implemented. The NMS workstations is also known as the SNMP manager.
Note Currently only IPv4 is supported.
Note For all MIB objects with "read-create" access privileges, currently only "read-only" access is supported.
For more information on this MIB, please access the following link: https://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/mcvpnmib.html
The CISCO-NETSYNC-MIB contains objects to monitor network synchronization based on ITU-T G.781 clock selection.
The CISCO-NHRP-EXT-MIB module is an extension of the NHRP MIB. It defines notifications associated with critical events in the Next Hop Resolution Protocol (NHRP) as defined in RFC 2332.
The CISCO-NTP-MIB contains objects to monitor a Network Time Protocol (NTP) server. NTP is used to synchronize timekeeping among a set of distributed time servers and clients. Primary time servers, which are synchronized to national time standards, are connected to widely accessible resources such as backbone gateways. These primary servers send timekeeping information to other time servers, and perform clock checking to eliminate timekeeping errors due to equipment or propagation failures.
The CISCO-OSPF-MIB contains objects for managing OSPF implementation. Most of the MIB definitions are based on the IETF draft draft-ietf-ospf-mib-update-05.txt and include support for OSPF sham link. The CISCO-OSPF-MIB is an extension to the OSPF-MIB defined in RFC 1850.
The CISCO-OSPF-TRAP-MIB contains new and modified notification objects and events, which are defined in the latest version of the OSPF-MIB IETF (draft draftietf-ospf-mib-update-05.txt) in addition to support for the OSPF sham link.
The CISCO-PIM-MIB defines Cisco-specific objects and variables for managing Protocol Independent Multicasts (PIMs) on the router. These MIB definitions are an extension of those in RFC 2934, which is the IETF PIM MIB.
The CISCO-PING-MIB contains objects to manage ping requests on the router.
The CISCO-PROCESS-MIB displays memory and CPU usage on the router and describes active system processes. CPU utilization presents a status of how busy the system is. The numbers are a ratio of the current idle time over the longest idle time. (This information should be used only as an estimate.)
Table 3-43 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-PROCESS-MIB.
|
|
---|---|
|
|
|
|
|
Note The cpmCPUTotalTable object contains only one entry for RSP CPUs.
The cpmCPUTotal5sec, cpmCPUTotal1min, and cpmCPUTotal5min objects have been deprecated and replaced by cpmCPUTotal5secRev, cpmCPUTotal1minRev, and cpmCPUTotal5minRev, respectively.
Note When an object is deprecated, it does not mean that an object instance may not be returned. For these deprecated objects, object instances are returned. However, their returned values must be ignored. The values returned by the new objects must be used.
Note The CPU utilization objects, such as cpmCPUTotal5sec, cpmCPUTotal1min, and cpmCPUTotal5min are calculated for all the processes used by the CPU except under idle condition.
Note For the Cisco ASR 903 Series Router, there are no separate FPs.
Table 3-44 lists the support matrix for the CISCO-PROCESS-MIB cpmCPUTotalTable object.
Table 3-45 lists the support matrix for the CISCO-PROCESS-MIB cpmProcessTable and cpmProcessExtRevTable objects for RSP CPU.
Table 3-46 lists the support matrix for the CISCO-PROCESS-MIB cpmVirtualProcessTable object.
The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to the Cisco hardware platforms.
The CISCO-PTP-MIB supports the Precision Timing Protocol (PTP) feature on Cisco devices. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock.
The CISCO-RF-MIB provides configuration control and status information for the redundancy framework subsystem. The redundancy framework subsystem provides a mechanism for logical redundancy of the software functionality and is designed to support 1:1 redundancy for the processor cards.
The CISCO-RESILIENT-ETHERNET-PROTOCOL-MIB defines objects required for managing Resilient Ethernet Protocol (REP). REP is a Cisco proprietary protocol that provides an alternative to Spanning Tree Protocol (STP). REP provides the functionality to control network loops, handle link failures, and improve convergence time.
The CISCO-RTTMON-ICMP-MIB is an extension to the CISCO-RTTMON-MIB for ICMP operations. The ICMP Jitter operation provides capability to measure metrics, such as RTT, Jitter, packet loss, and one-way latency by sending ICMP timestamp streams to destination devices.
The CISCO-RTTMON-IP-EXT-MIB provides extensions for the tables in CISCO-RTTMON-MIB to support IP layer extensions, specifically IPv6 addresses and other information related to IPv6 standards.
The CISCO-RTTMON-MIB contains objects to monitor network performance. The MIB provides information about the response times of network resources and applications. Each conceptual round-trip time (RTT) control row in the MIB represents a single probe, which is used to determine an entity’s response time. The probe defines an RTT operation to perform (for example, an FTP or HTTP get request), and the results indicate whether the operation succeeded or failed, and how long it took to complete.
If you plan to schedule an RTT operation, see Table 3-47 for information about rttMonScheduleAdminRttStartTime in the rttMonScheduleAdminTable.
Note An rttMonCtrlOperConnectionLostOccurred trap is generated when an RTT connection cannot be established to the destination router because the router responder application is not running. However, the trap is not generated if the physical connection to the router is lost.
Table 3-47 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-RTTMON-MIB.
The CISCO-RTTMON-RTP-MIB is an extension to the CISCO-RTTMON-MIB for Cisco IP SLA Real-Time Transport Protocol (RTP) operation. This operation provides the capability to measure voice quality metrics, such as RTT, Jitter, and Mean Opinion Score (MOS) by setting up RTP stream between two routers. In voice communications, particularly Internet telephony, MOS provides a numerical measure of the quality of human speech at the destination end of the circuit.
The CISCO-SNMP-TARGET-EXT-MIB is an extension of the SNMP-TARGET-MIB specified in RFC2273.
The CISCO-STP-EXTENSIONS-MIB contains objects to manage the Cisco extensions to the IEEE 802.1D Spanning Tree Protocol (STP).
Note For the CISCO-STP-EXTENSIONS-MIB, only the traps and notification for the stpxRootInconsistency object have been verified.
The CISCO-SONET-MIB contains objects to describe SONET/SDH interfaces on the router. This MIB is an extension of the standard SONET-MIB (RFC 2558). The CISCO-SONET-MIB has objects that provide additional SONET-related information, which is not found in the SONET-MIB.
Note CISCO-SONET-MIB supports SONET traps that are seen when the line, section, path status changes, and notifications are enabled.
Table 3-48 describes the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-SONET-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note Only the section, line, and path totals objects from the ciscoSonetStatsMIBGroup and the complete ciscoSonetEnableGroup is supported. All network elements containing one or more SONET interfaces should implement this MIB.
The CISCO-SYSLOG-MIB contains all system log messages generated by the Cisco IOS XE software. The MIB provides a way to access these system log messages through the SNMP. All Cisco IOS XE system log messages contain the message name and its severity, message text, the name of the entity generating the message, and an optional time stamp. The MIB also contains a history of system log messages and counts related to system log messages.
Note The Cisco ASR 903 Series Router can be configured to send system log messages to a system log server.
Note The MIB does not keep track of messages generated from debug commands entered through the CLI.
The CISCO-TCP-MIB contains objects to manage the TCP on the router. This MIB is an extension to the IETF TCP MIB.
The CISCO-VRF-MIB contains objects to manage and provision the network virtualization features. Virtual Routing and Forwarding (VRF) is an extension of IP routing that provides multiple routing instances.
The DS1-MIB(RFC-2495) contains a description of the DS1, E1, DS2, and E2 interface objects.
Table 3-49 describes the constraints that the Cisco ASR 903 Series Router places on the objects in the DS1-MIB. For detailed definitions of the MIB objects, see the corresponding MIB.
The ENTITY-MIB (RFC 4133) allows functional component discovery. It is used to represent physical and logical entities (components) in the router and manages those entities. The current software release supports the RFC 4133 version of this MIB.
The following are the conformance groups contained in the ENTITY-MIB:
The following groups are added from RFC 4133:
The MIB table entPhysicalTable identifies the physical entities in the router. The entPhysicalTable contains a single row for the Cisco ASR 903 Series Router chassis and a row for each entity in the chassis. A physical entity may contain other entities. For example, an IM in IM Bay 0 with one A900-IMA8T-CU-IM in subslot 0/1 supports the following entities in this SNMP. Output for IMs, sensors on the subslot, and IM ports:
Note The IM A900-IMA4OS has only four ports modelled.
For more information on the ENTITY-MIB, refer Appendix A, “CISCO-ENTITY-ALARM-MIB.”
For the Cisco ASR 903 Series Router platform, the entPhysicalParentRelPos values are populated with the slot numbers (except for the RP, and PEM slot numbers) provided in the external label.
Table 3-50 lists the mapping between external labels and entPhysicalParentRelPos values.
|
|
|
---|---|---|
|
||
|
||
|
||
|
Table 3-51 lists the values of the affected MIB table objects in the Cisco ASR 903 Series Router:
|
|
|
---|---|---|
|
||
|
||
|
||
|
||
|
||
|
Table 3-52 lists the fans supported on a Cisco ASR 903 Series Router.
|
|
---|---|
|
Table 3-53 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the ENTITY-MIB.
Note When both primary and secondary RSPs are up and running, entities for standby USB flash and boot flash are not populated for the ENTITY-MIB.
Note For cevModuleASR903UnknownRSP object, only the RSP module entry is populated without any child entities.
The ENTITY-SENSOR-MIB (RFC 3433) contains objects that manage physical sensors, which are represented in the Entity-MIB with entPhysicalEntry and an entPhysicalClass value of sensor(8). The ENTITY-SENSOR-MIB contains a single table called the entPhySensorTable.
Note These sensors are supported on the CISCO-ENTITY-SENSOR-MIB. Unit tests can be performed to ensure that all the sensors are modelled in the MIB.
The ENTITY-STATE-MIB defines objects to extend the functionality provided by the ENTITY-MIB. This MIB supports the entities having these entPhysicalClass values:
Table 3-54 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the ENTITY-STATE-MIB.
|
|
---|---|
|
These values indicate the CISCO-ENTITY-ALARM-MIB alarm types. |
|
Note Power supply and fan alarms are generated on either the Power Entry Module or FanTray module. Therefore, no alarm is generated on the entStateAlarm object associated with either the power supply or the fan.
The ETHER-WIS (RFC 3637) MIB contains objects to manage application details for the Ethernet WAN Interface Sublayer (WIS).
Table 3-55 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the ETHER-WIS (RFC 3637) MIB.
|
|
---|---|
|
|
|
|
|
Note WAN-PHY is not fully compliant with the SONET/SDH optical and electrical specifications.
Note SONET layer is not modelled for the Ethernet WIS port.
The ETHERLIKE-MIB contains objects to manage Ethernet-like interfaces.
Table 3-56 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the ETHERLIKE-MIB. Any objects not listed in a table are implemented as defined in the MIB.
|
|
---|---|
|
|
|
|
|
|
|
The EVENT-MIB (RFC 2981) contains objects to define event triggers and actions for network management purposes.
The EXPRESSION-MIB (RFC 2982) contains objects to define the expressions of MIB objects for network management purposes.
The HC-ALARM-MIB defines Remote Monitoring MIB extensions for High Capacity Alarms.
Table 3-57 lists the tables in HC-ALARM-MIB.
|
|
---|---|
|
A list of entries for the configuration of high capacity alarms. |
The HC-RMON- MIB augments the original RMON MIB as specified in RFC 1757 and RFC 1513, and RMON2 MIB as specified in RFC 2021. It manages the remote monitoring device implementations.
The IEEE8021-CFM-MIB is a Connectivity Fault Management (CFM) module for managing IEEE 802.1ag.
Table 3-56 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the IEEE8021-CFM-MIB.
Note The IEEE8021-CFM-MIB does not support SET operation.
The IEEE8021-CFM-V2-MIB is a Connectivity Fault Management (CFM) version 2 module for managing IEEE 802.1ag.
Note The IEEE8021-CFM-V2-MIB does not support SET operation.
The IEEE 8023-LAG-MIB is the Link Aggregation module for managing IEEE Std 802.3ad.
The IF-MIB (RFC 2863) describes the attributes of physical and logical interfaces (network interface sublayers). The router supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, and ifConnectorPresent).
One of the most commonly used identifiers in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface.
Note The ifInDiscards, ifInErrors, ifInUnknownProtos, ifOutDiscards, and ifOutErrors IF-MIB objects are not supported for Gigabit subinterfaces.
Note The IF-MIB supports these modes for A900-IMA4OS:
- Channel-group under c-11 mode in au-3
- Channel-group under c-12 mode in au-4
- CEM under c-12 mode in au-4
- CEM under c-11 mode in au-3
Note BDI interfaces are not supported for IF-MIB as the counter values are not updated for this MIB.
On querying the ifStackStatus object, the CEM interface and the Channel group show the layers as illustrated in Figure 3-1 and Figure 3-2.
Figure 3-1 Layering Shown by the CEM Interface
Figure 3-2 Layering Shown by the Channel Group
Table 3-59 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the IF-MIB.
|
|
---|---|
|
|
|
|
|
The IGMP-STD-MIB(RFC 2933) manages Internet Group Management Protocol (IGMP).
The INT-SERV-GUARANTEED-MIB describes the guaranteed service of the Integrated Services Protocol.
The INTEGRATED-SERVICES-MIB contains objects to manage the Integrated Services Protocol.
The IP-FORWARD-MIB (RFC 4292) contains objects to control the display of classless interdomain routing (CIDR) multipath IP Routes.
The IP-MIB (RFC 4293) module contains objects for managing IP and Internet Control Message Protocol (ICMP) implementations, but not their management of IP routes.
Table 3-60 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the IP-MIB.
|
|
---|---|
|
|
|
The IPMROUTE-STD-MIB (RFC 2932) contains objects to manage IP multicast routing, but independent of the specific multicast routing protocol in use.
Table 3-61 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the IPMROUTE-STD-MIB.
|
|
---|---|
|
The MPLS-L3VPN-STD-MIB contains managed object definitions for the Layer-3 Multiprotocol Label Switching Virtual Private Networks. This MIB is based on RFC 4382 specification.
The MPLS-LDP-GENERIC-STD-MIB (RFC 3815) contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching Label Distribution Protocol (MPLS-LDP) and utilizing ethernet as the Layer 2 media.
The MPLS-LDP-STD-MIB (RFC 3815) contains managed object definitions for the Multiprotocol Label Switching (MPLS) and Label Distribution Protocol (LDP) document.
The MPLS-LSR-STD-MIB (RFC 3031) contains managed object definitions for the Multiprotocol Label Switching (MPLS) router.
The MPLS-TE-STD-MIB contains managed object definitions for Multiprotocol Label Switching Traffic Engineering (MPLS-TE).
The MIB is based on Revision 05 of the IETF MPLS-VPN-MIB.
Table 3-62 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the MPLS-VPN-MIB.
The MSDP-MIB contains objects to monitor the Multicast Source Discovery Protocol (MSDP). The MIB can be used with SNMPv3 to remotely monitor MSDP speakers.
For more information about this MIB, see its feature module description at the following URL:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5msdp.html
The Cisco NHRP MIB feature introduces support for the NHRP MIB, which helps to manage and monitor the Next Hop Resolution Protocol (NHRP) through the Simple Network Management Protocol (SNMP). Statistics can be collected and monitored through standards-based SNMP techniques (get operations) to query objects defined in the NHRP MIB. The NHRP MIB is VRF-aware and supports VRF-aware queries.
For more information about this MIB, refer:
http://www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/sec_dmvpn_nhrp_mib.html
Table 3-63 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the NHRP-MIB.
The NOTIFICATION-LOG-MIB contains objects for logging SNMP notifications; that is, traps and informs types of notifications.
The OSPF-MIB (RFC 1850) contains objects that describe the OSPF Version 2 Protocol. The RFC1253-MIB corresponds to the OSPF-MIB (Open Shortest Path First [OSPF] protocol).
The OSPF-TRAP-MIB (RFC 1850) contains objects that describe traps for the OSPF Version 2 Protocol.
The PIM-MIB (RFC 2934) contains objects to configure and manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.
Table 3-64 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the PIM-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
The RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets. This RFC1213-MIB includes the following groups :
Note For more information, refer to the latest RFCs specified in the RFC-1213-MIB.
The RFC2982-MIB defines expressions of MIB objects for management purposes.
The RFC2006-MIB is the MIB module for the Mobile IP standard.
The RMON-MIB (RFC 1757) contains objects to remotely monitor devices in the network.
Only alarm and event groups are supported in Cisco ASR 903 Series Router.
The RMON2-MIB contains objects to manage remote monitoring device implementations. This MIB module enhances the original RMON MIB as specified in RFC 2021.
The RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP).
The SMON-MIB contains objects to manage remote monitoring device implementations for switched networks. It identifies the source of the data that the associated function is configured to analyze. The textual convention extends the data source textual convention defined by RMON 2 to the following data source types:
The SNMP-COMMUNITY-MIB (RFC 2576) contains objects that help support coexistence among SNMPv1, SNMPv2c, and SNMPv3.
The SNMP-FRAMEWORK-MIB (RFC 2571) contains objects that describe the SNMP management architecture. There are no constraints on this MIB.
The SNMP-MPD-MIB (RFC 2572) contains objects for Message Processing and Dispatching (MPD).
The SNMP-NOTIFICATION-MIB (RFC 2573) contains managed objects for SNMPv3 notifications. The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable).
Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of SNMP notifications those entities are to receive.
The SNMP-PROXY-MIB (RFC 2573) contains managed objects to remotely configure the parameters used by an SNMP entity for proxy forwarding operations. The MIB contains a single table, snmpProxyTable, which defines the translations to use to forward messages between management targets.
The SNMP-TARGET-MIB (RFC 2573) contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of entities to send SNMP notifications to, and contains a list of tag values that are used to filter the notifications sent to these entities (see the SNMP-NOTIFICATION-MIB).
The SNMP-USM-MIB (RFC 2574) contains objects that describe the SNMP user-based security model.
The SNMPv2-MIB (RFC 1907) contains objects to manage SNMPv2 entities. The SNMPv2-MIB contains the following mandatory object groups:
The SNMPv2-SMI is based on RFC1902 and describes the management information structure for Simple Network Management Protocol version 2 (SNMPv2).
The SNMP-VIEW-BASED-ACM-MIB (RFC 2575) contains objects that describe the view-based access control model for SNMP.
To access the SNMP-VIEW-BASED-ACM-MIB, you must create an SNMPv3 user with access to a view that includes all of the information from the Internet subtree. For example:
Router(config)# snmp-server view abcview internet included
Router(config)# snmp-server group abcgroup v3 noauth read abcview write abcview notify abcview
Router(config)# snmp-server user abcuser abcgroup v3
Note Router(config)# snmp-server user abcuser abcgroup v3
The SONET-MIB (RFC 2558) provides both the configuration and performance monitoring objects for the SONET interfaces.
Table 3-65 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the SONET-MIB.
|
|
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note When the SONET path is initialized and no active alarms exist, the value of the sonetPathCurrentStatus object is 0. If an alarm is triggered and cleared, the value of the sonetPathNoDefect object is 1.
The TCP-MIB (RFC 4022) contains objects to manage the Transmission Control Protocol (TCP) implementations on the router.
The TUNNEL-MIB contains objects to manage IP Tunnels independent of the encapsulation scheme in use.
The UDP-MIB (RFC4113) contains objects to manage the User Datagram Protocol (UDP) on the router. There are no constraints.
The VRRP-MIB contains objects to manage Virtual Router Redundancy Protocol (VRRP) routers.