Cisco ASR 903 Series Aggregation Services Routers MIB Specifications Guide

Cisco ASR 903 Series Router MIB Specifications

---

This chapter describes the Management Information Base (MIB) on the Cisco ASR 903 Series Aggregation Services Routers. It includes the following sections:

• Cisco ASR 903 Series Router MIBs
• Cisco ASR 903 Series Router MIB Categories

Cisco ASR 903 Series Router MIBs

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.

Cisco ASR 903 Series Router MIB Categories

The subsequent tables list the following categories of MIBs in the Cisco ASR 903 Series Router Image on the Cisco ASR 903 Series Router:

• Supported and verified MIBs (tested for Cisco ASR 903 Series Router)—The MIBs exist in the image, the code is implemented, and Cisco has verified that all the supported objects work properly ( Table 3-1 ).
• Supported and unverified MIBs (not tested for Cisco ASR 903 Series Router)—The MIBs exist in the image, the code is implemented, but Cisco has not verified if it is working properly ( Table 3-2 ).
• Unsupported MIBs (no level of support or testing on the Cisco ASR 903 Series Router)—The MIBs may be posted on Cisco.com, but are not present in the image and cannot be queried ( Table 3-3 ).

The MIB version string indicates the date and time that it was most recently modified. The format is YYMMDDHHMMZ or YYYYMMDDHHMMZ, where:

• YY is the last two digits of the year (only years between 1900 and1999).
• YYYY is all four digits of the year (any year).
• MM is the month (01 through 12).
• DD is the day of the month (01 through 31).
• HH is hours (00 through 23).
• MM is minutes (00 through 59).
• Z (the ASCII character Z), denotes Coordinated Universal Time (UTC, formerly Greenwich Mean Time [GMT]). This datatype stores the date and time fields YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, TIMEZONE_HOUR, and TIMEZONE_MINUTE.

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.

ATM-MIB

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.

BGP4-MIB (RFC 1657)

The BGP4-MIB (RFC 1657) provides access to the implementation information for the Border Gateway Protocol (BGP). The MIB provides:

• Information about the BGP configuration
• Information about BGP peers and messages exchanged within
• Information about the advertised networks

CISCO-AAL5-MIB

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.

CISCO-ATM-EXT-MIB

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.

MIB Constraints

Table 3-4 lists the constraint that the Cisco ASR 903 Series Router places on the objects in the CISCO-ATM-EXT-MIB.

 

Table 3-4 CISCO-ATM-EXT-MIB Constraint

MIB Object	Notes
catmxVclOamTable	Not supported.

---

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.

---

CISCO-ATM-IF-MIB

The CISCO-ATM-IF-MIB provides the functionality required for an ATM interface configuration.

CISCO-ATM-PVC-MIB

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).

CISCO-ATM-PVCTRAP-EXTN-MIB

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.

CISCO-BCP-MIB

The CISCO-BCP-MIB contains objects to manage the Bridge Control Protocol (RFC2878). This MIB is influenced by RFC1474.

CISCO-BGP4-MIB

The CISCO-BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:

• Information about the BGP configuration
• Information about BGP peers and messages exchanged with them
• Information about advertised networks

CISCO-BGP-POLICY-ACCOUNTING-MIB

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.

CISCO-BULK-FILE-MIB

The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer.

CISCO-CALLHOME-MIB

The CISCO-CALLHOME-MIB contains objects to manage the Call Home feature within the Cisco Call Home architecture framework.

CISCO-CBP-TARGET-MIB

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.

CISCO-CDP-MIB

The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router.

CISCO-CEF-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.

MIB Constraints

Table 3-8 lists the constraints that the router places on the objects in the CISCO-CEF-MIB.

 

Table 3-8 CISCO-CEF-MIB Constraints

MIB Object	Notes
cefCfgAdminState	Read-only. This object is enabled by default.
cefCCCount	Read-only.
cefCCPeriod	Read-only.
cefCCEnabled	Read-only.

---

Note Cisco Express Forwarding is a high-speed switching mechanism that a router uses to forward packets from the inbound to the outbound interface.

---

CISCO-CIRCUIT-INTERFACE-MIB

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.

CISCO-CLASS-BASED-QOS-MIB

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:

• Match Statement—Indicates the specific match criteria that identifies packets for classification purposes.
• Class Map—Indicates a user-defined traffic class that contains one or more match statements which is used to classify packets into different categories.
• Feature Action—Indicates a QoS feature. Features include policing, traffic shaping, queuing, random detecting, and packet marking. After the traffic is classified, actions are applied to each traffic class.
• Policy Map—Indicates a user-defined policy that associates a QoS feature action to the user-defined class map.
• Service Policy—Indicates a policy map that is attached to an interface.

The MIB uses the following indexes to identify QoS features and distinguish among instances of those features:

• cbQosObjectsIndex—Identifies each QoS feature on the router.
• cbQoSConfigIndex—Identifies a type of QoS configuration. This index is shared by QoS objects that have identical configuration.
• cbQosPolicyIndex—Uniquely identifies a service policy.

QoS MIB information is stored in:

• Configuration instances—This includes all class maps, policy maps, match statements, and feature action configuration parameters. These configuration instances may have multiple identical instances. Multiple instances of the same QoS feature that share a single configuration object is identified by the cbQosConfigIndex.
• Runtime Statistics instances—This includes summary counts and rates sorted by traffic class before and after any configured QoS policies are enforced. In addition, detailed feature-specific statistics are available for select policy map features. Each has a unique run-time instance. Multiple instances of a QoS feature have a separate statistics object. Run-time instances of QoS objects are each assigned a unique identifier (cbQosObjectsIndex) to distinguish among multiple objects with matching configuration.

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.

CISCO-CONFIG-COPY-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:

• Configuration files to and from the network
• Startup configuration to running configuration and running configuration to startup.
• Startup or running configuration files to and from a local Cisco IOS XE file system.

CISCO-CONFIG-MAN-MIB

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.

CISCO-CONTEXT-MAPPING-MIB

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.

CISCO-DATA-COLLECTION-MIB

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.

CISCO-DOT3-OAM-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).

CISCO-EIGRP-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.

CISCO-EMBEDDED-EVENT-MGR-MIB

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.

CISCO-ENHANCED-MEMPOOL-MIB

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:

• 1:Processor memory
• 2:I/O memory
• 3:PCI memory
• 4:Fast memory
• 5:Multibus memory
• Other memory

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.

CISCO-ENTITY-ALARM-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:

• A900-IMA8T ASR 900: 8 port 10/100/1000 Ethernet Interface Module
• A900-IMA8S ASR 900: 8 port SFP Gigabit Ethernet Interface Module
• A900-IMA1X ASR 900: 1 port 10GE XFP Interface Module
• A900-IMA16D ASR 900: 16 port T1/E1 Interface Module

All the other interface types are not supported for this release.

For more information on this MIB, see Appendix A, “CISCO-ENTITY-ALARM-MIB.”

MIB Constraints

Table 3-13 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-ENTITY-ALARM-MIB.

 

Table 3-13 CISCO-ENTITY-ALARM-MIB Constraints

MIB Object	Notes
ceAlarmTable
ceAlarmFilterProfile	Not implemented.
ceAlarmFilterProfileIndexNext	Not implemented.
ceAlarmFilterProfileTable	Not implemented.
ceAlarmDescrTable
ceAlarmDescrSeverity	Read-only.

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:

• Physical entity—The component in the Cisco ASR 903 Series Router that generates the alarm.
• ceAlarmDescrVendorType—The object specifies an identifier (typically an enterprise-specific OID) that uniquely identifies the vendor type of those physical entities to which this alarm description applies.
• Alarm severity—Each alarm type defined by a vendor type and employed by the system is assigned an associated severity:

– 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).

• Alarm description text—Specifies a readable message describing the alarm.
• Alarm type—Identifies the type of alarm that is generated. An arbitrary integer value (0 through 255) uniquely identifies an event relative to a physical entity in the Cisco ASR 903 Series Router.

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-14 Alarms Supported for T1/E1 ports of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
T1/E1 port	cevPortT1E1	minor	Transmitter is sending remote alarm
	cevPortT1E1	minor	Transmitter is sending AIS
	cevPortT1E1	minor	Transmitter is sending TS16 LOMF alarm
	cevPortT1E1	minor	Receiver has loss of multi-frame in TS16
	cevPortT1E1	minor	Receiver has loss of signal
	cevPortT1E1	minor	Receiver is getting AIS
	cevPortT1E1	minor	Receiver has loss of frame
	cevPortT1E1	minor	Receiver has remote alarm
	cevPortT1E1	minor	Receiver is getting AIS in TS16
	cevPortT1E1	minor	Receiver has remote TS16 LOMF alarm
	cevPortT1E1	minor	Other failure
	cevPortT1E1	minor	Ds1 Physical Port Link Down
	cevPortT1E1	info	Ds1 Physical Port Administrative State Down

Table 3-15 lists the alarm descriptions and severity levels for the Gigabit Ethernet (GE) ports of the Cisco ASR 903 Series Router.

 

Table 3-15 Alarms Supported for the GE Ports of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
GE port	cevPortGE	critical	Physical port link down.
		info	Physical port administrative state down.
10GE port	cevPort10GigEthPhy	critical	Physical port link down.
		info	Physical port administrative state down.

---

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-16 Alarms Supported for the SFP Container of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrText
SFP container	cevContainerSFP	Transceiver missing.

Table 3-17 lists the alarm descriptions and severity levels for the IMs of the Cisco ASR 903 Series Router.

 

Table 3-17 Alarms Supported for the IMs of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
A900-IMA8T A900-IMA8S A900-IMA1X A900-IMA16D	cevIM8pGeCu cevIM8pGeSFP cevIM1p10GeXfp cevIM16pT1E1	major	Unknown state.
		major	Boot state.
		major	Disabled.
		critical	Failed.
		major	Stopped.

Table 3-18 lists the alarm descriptions and severity levels for the Cisco ASR 903 Series Router sensors.

 

Table 3-18 Alarms Supported for Cisco ASR 903 Series Router Sensors

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
Sensor	cevSensor	critical	Faulty Sensor.
		critical	Reading Above Normal (Shutdown).
		critical	Reading Above Normal.
		major	Reading Above Normal.
		minor	Reading Above Normal.
		critical	Reading Below Normal (Shutdown).
		critical	Reading Below Normal.
		major	Reading Below Normal.
		minor	Reading Below Normal.

---

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-19 Alarms Supported for the IM Container of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
IM bay	cevContainerIMBay	critical	Active card removed OIR alarm.
		critical	Card stopped responding.

Table 3-20 lists the alarm descriptions and severity levels for the Cisco ASR 903 Series Router USB ports.

 

Table 3-20 Alarms Supported for Cisco ASR 903 Series Router USB Ports

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
USB port	cevPortUSB	critical	Active card removed OIR alarm.
		critical	Card stopped responding.

Table 3-21 lists the alarm descriptions and severity levels for the RSP containers of the Cisco ASR 903 Series Router.

 

Table 3-21 Alarms Supported for the RSP Container of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
RSP container	cevContainerASR900RSPSlot	critical	RSP removed OIR alarm.
		critical	RSP stopped responding.

Table 3-22 lists the alarm descriptions and severity levels for the power supply bay of the Cisco ASR 903 Series Router.

 

Table 3-22 Alarms Supported for the Power Supply Bay of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
Power Supply Bay	cevContainerASR900 PowerSupplyBay	critical	Power supply/Fan module missing.

Table 3-23 lists the alarm descriptions and severity levels for the RSPs of the Cisco ASR 903 Series Router.

 

Table 3-23 Alarms Supported for the RSP Module of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
RSP Module	cevModuleASR903RSP1A cevModuleASR903RSP1B	major	Unknown state.
		major	Boot state.
		major	Disabled.
		critical	Incompatible
		critical	CPLD incompatible.
		critical	Active RSP CPLD incompatible.
		critical	Failed.
		critical	Cutover.
		major	Secondary failure.
		major	Secondary removed.
		major	Secondary not synchronized.
		critical	No working ESP.
		major	Harddisk Missing.

---

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:

• Secondary RSP is loaded with the valid image and the RSP module is not operational.
• Software does not understand the hardware subtype of the secondary RSP module.
• Secondary RSP is loaded with an invalid image.

Table 3-24 lists the alarm descriptions and severity levels for the unknown RSP modules of the Cisco ASR 903 Series Router.

 

Table 3-24 Alarms Supported for the unknown RSP modules of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
RSP Module	cevModuleUnknownCard	major	Unknown state.
		major	Boot state.
		major	Disabled.
		critical	Failed.
		critical	Stopped.

Table 3-25 lists the alarm descriptions and severity levels for the power supply module of the Cisco ASR 903 Series Router.

 

Table 3-25 Alarms Supported for the Power Supply Module of the Cisco ASR 903 Series Router

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
Power Supply Modules	cevPowerSupplyASR900DC500W	critical	Power Supply Failure.

Table 3-26 lists the alarms that the FanTray module of the Cisco ASR 903 Series Router supports.

 

Table 3-26 Alarms Supported for the Cisco ASR 903 Series Router FanTray Module

Physical Entity	ceAlarmDescrVendorType	ceAlarmDescrSeverity	ceAlarmDescrText
FanTray Modules	cevFanASR903FanTray	critical	FanTray/Module Failure.
		critical	All Fans Failed.
		critical	Multiple Fan Failures.
		major	Fan 0 to Fan 11 failure.

---

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.

---

CISCO-ENTITY-EXT-MIB

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.

CISCO-ENTITY-FRU-CONTROL-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.

CISCO-ENTITY-SENSOR-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.

MIB Constraints

Table 3-29 lists the constraints that the Cisco ASR 903 Series Router places on the CISCO-ENTITY-SENSOR-MIB.

 

Table 3-29 CISCO-ENTITY-SENSOR-MIB Constraints

MIB Object	Notes
entSensorValueTable
entSensorMeasuredEntity	Implemented for all sensors except for transceiver sensors.
entSensorThresholdTable
entSensorThresholdRelation	Read-only.
entSensorThresholdSeverity	Read-only.
entSensorThresholdValue	Read-only.

---

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.

---

MIB Usage Values for Cisco Transceivers

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.

 

Table 3-30 CISCO-ENTITY-SENSOR-MIB Usage Values in the entSensorValueTable for
Cisco ASR 903 Series Router Transceivers

MIB Sensor Object	Notes
Module Temperature Sensor
entSensorType	celsius(8)
entSensorScale	units(9)
entSensorPrecision	3
entSensorStatus	ok(1)
entSensorValue	Reports most recent measurement seen by the sensor.
entSensorValueTimeStamp	Value indicates the age of the value reported by entSensorValue object.
entSensorValueUpdateRate	Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).
entSensorMeasuredEntity	0
Tx Supply Voltage Sensor
entSensorType	voltsDC(4)
entSensorScale	milli(8)
entSensorPrecision	1
entSensorStatus	ok(1)
entSensorValue	Reports most recent measurement seen by the sensor.
entSensorValueTimeStamp	Value indicates the age of the value reported by entSensorValue object.
entSensorValueUpdateRate	Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).
entSensorMeasuredEntity	0
Tx Laser Current Sensor
entSensorType	amperes(5)
entSensorScale	milli(8)
entSensorPrecision	0
entSensorStatus	ok(1)
entSensorValue	Reports most recent measurement seen by the sensor.
entSensorValueTimeStamp	Value indicates the age of the value reported by entSensorValue object.
entSensorValueUpdateRate	Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).
entSensorMeasuredEntity	0
Transmit Power Sensor (Optical Tx) Receive Power Sensor (Optical Rx)
entSensorType	dBm(14)
entSensorScale	units(9)
entSensorPrecision	0
entSensorStatus	ok(1)
entSensorValue	Reports most recent measurement seen by the sensor.
entSensorValueTimeStamp	Value indicates the age of the value reported by entSensorValue object.
entSensorValueUpdateRate	Value indicates the rate that the agent updates entSensorValue in seconds (for example, 60 seconds).
entSensorMeasuredEntity	0

---

Note The RSPs and power supplies support various sensors. These sensors are supported in the CISCO-ENTITY-SENSOR-MIB.

---

CISCO-ENTITY-VENDORTYPE-OID-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:

• Chassis
• RSP module
• IM Module
• Power Supply Module
• Fan Tray

CISCO-ERM-MIB

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:

• Resource Depletion—Handles a situation where the system runs out of a finite resource.
• Resource Separation—Shares resources fairly between different entities in the system such that the activity of one entity does not adversely affect others.

CISCO-ETHER-CFM-MIB

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.

CISCO-ETHERLIKE-EXT-MIB

The CISCO-ETHERLIKE-EXT-MIB defines generic objects for the Ethernet-like network interfaces.

CISCO-EVC-MIB

The CISCO-EVC-MIB defines the managed objects and notifications describing Ethernet Virtual Connections (EVCs).

CISCO-FLASH-MIB

The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.

MIB Constraints

Table 3-33 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-FLASH-MIB.

 

Table 3-33 CISCO-FLASH-MIB Constraints

MIB Object	Notes
ciscoFlashDeviceTable
ciscoFlashDeviceInitTime	Not implemented.
ciscoFlashPhyEntIndex	Not implemented.
ciscoFlashPartitionTable
ciscoFlashPartitionFileCount	Not implemented.
ciscoFlashPartitionChecksumAlgorithm	Not implemented.
ciscoFlashPartitionUpgradeMethod	Not implemented.
ciscoFlashPartitionNeedErasure	Not implemented.
ciscoFlashPartitionFileNameLength	Not implemented.
ciscoFlashFileTable
ciscoFlashFileChecksum	Not implemented.
ciscoFlashFileType	Values not supported: config(2) image(3) crashinfo(5)

---

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.

---

CISCO-FTP-CLIENT-MIB

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.

CISCO-HSRP-EXT-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.

CISCO-HSRP-MIB

The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281.

CISCO-IETF-ATM2-PVCTRAP-MIB

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.

CISCO-IETF-BFD-MIB

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.

CISCO-IETF-DHCP-SERVER-MIB

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.

CISCO-IETF-DHCP-SERVER-EXT-MIB

The CISCO-IETF-DHCP-SERVER-EXT-MIB is an extension of the CISCO-IETF-DHCP-SERVER-MIB.

CISCO-IETF-ISIS-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.

CISCO-IETF-MPLS-ID-STD-03-MIB

The CISCO-IETF-MPLS-ID-STD-03-MIB contains object definitions for Multiprotocol Label Switching (MPLS) Traffic Engineering in transport networks.

CISCO-IETF-MPLS-TE-EXT-STD-03-MIB

The CISCO-IETF-MPLS-TE-EXT-STD-03-MIB contains generic object definitions for MPLS Traffic Engineering in transport networks.

CISCO-IETF-PPVPN-MPLS-VPN-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.

CISCO-IETF-PW-ATM-MIB

The CISCO-IETF-PW-ATM-MIB contains managed object definitions for pseudowire (PW) emulation of ATM over packet-switched networks (PSNs).

CISCO-IETF-PW-ENET-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).

CISCO-IETF-PW-MIB

The CISCO-IETF-PW-MIB contains managed object definitions for pseudowire (PW) operations.

CISCO-IETF-PW-MPLS-MIB

The CISCO-IETF-PW-MPLS-MIB contains objects that complement the CISCO-IETF-PW-MIB for PW operation over MPLS.

CISCO-IETF-PW-TDM-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).

CISCO-IF-EXTENSION-MIB

The CISCO-IF-EXTENSION-MIB contains objects that provide additional interface-related information that is not available in the IF-MIB (RFC 2863).

CISCO-IGMP-FILTER-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.

CISCO-IMAGE-MIB

The CISCO-IMAGE-MIB contains objects that identify the capabilities and characteristics of the Cisco IOS XE image.

CISCO-IMAGE-LICENSE-MGMT-MIB

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.

CISCO-IP-STAT-MIB

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.

CISCO-IPMROUTE-MIB

The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.

CISCO-IPSLA-ETHERNET-MIB

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).

CISCO-LAG-MIB

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.

CISCO-L2-CONTROL-MIB

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.

CISCO-LICENSE-MGMT-MIB

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.

CISCO-MAC-NOTIFICATION-MIB

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.

CISCO-MEMORY-POOL-MIB

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:

• Predefined pools
• Dynamic pools

CISCO-MPLS-LSR-EXT-STD-MIB

The CISCO-MPLS-LSR-EXT-STD-MIB contains generic object definitions for MPLS Label Switching Router (LSR) in transport networks.

CISCO-MPLS-TC-EXT-STD-MIB

The CISCO-MPLS-TC-EXT-STD-MIB contains textual conventions for MPLS based transport networks.

CISCO-MVPN-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

CISCO-NETSYNC-MIB

The CISCO-NETSYNC-MIB contains objects to monitor network synchronization based on ITU-T G.781 clock selection.

CISCO-NHRP-EXT-MIB

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.

CISCO-NTP-MIB

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.

CISCO-OSPF-MIB

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.

CISCO-OSPF-TRAP-MIB

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.

CISCO-PIM-MIB

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.

CISCO-PING-MIB

The CISCO-PING-MIB contains objects to manage ping requests on the router.

CISCO-PROCESS-MIB

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.)

MIB Constraints

Table 3-43 lists the constraints that the Cisco ASR 903 Series Router places on the objects in the CISCO-PROCESS-MIB.

 

Table 3-43 CISCO-PROCESS-MIB Constraints

MIB Object	Notes
cpmProcessTable
cpmProcExtPriority	Read-only.
cpmCPURisingThreshold	Not supported.
cpmCPUFallingThreshold	Not supported.

---

Note The cpmCPUTotalTable object contains only one entry for RSP CPUs.

---

CISCO-PROCESS-MIB Usage

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-44 Support-Matrix for cpmCPUTotalTable

cpmCPUTotalTable Objects	RSP CPU	Stdby RSP CPU
cpmCPULoadAvg1min	Yes	No
cpmCPULoadAvg5min	Yes	No
cpmCPULoadAvg15min	Yes	No
cpmCPUMemoryCommitted	Yes	No
cpmCPUTotalPhysicalIndex	Yes	No
cpmCPUTotal5sec	Yes	No
cpmCPUTotal1min	Yes	No
cpmCPUTotal5min	Yes	No
cpmCPUTotal5secRev	Yes	No
cpmCPUTotal1minRev	Yes	No
cpmCPUTotal5minRev	Yes	No
cpmCPUMonInterval	No	No
cpmCPUTotalMonIntervalValue	No	No
cpmCPUInterruptMonIntervalValue	No	No
cpmCPUMemoryUsed	Yes	No
cpmCPUMemoryFree	Yes	No
cpmCPUMemoryKernelReserved	No	No
cpmCPUMemoryLowest	Yes	No

Table 3-45 lists the support matrix for the CISCO-PROCESS-MIB cpmProcessTable and cpmProcessExtRevTable objects for RSP CPU.

Table 3-45 Support-Matrix for cpmProcessTable and cpmProcessExtRevTable for RSP CPU

cpmProcessTable and cpmProcessRevExtTable Objects	IOSD Process [Process Name: ppc_linux_iosd-]	Other Process [Process Name: Cmand, hman, iomd ]
cpmProcessName	Yes	Yes
cpmProcessuSecs	No	No
cpmProcessTimeCreated	Yes	Yes
cpmProcessAverageUSecs	Yes	Yes
cpmProcExtMemAllocatedRev	Yes	Yes
cpmProcExtMemFreedRev	No	No
cpmProcExtInvokedRev	No	No
cpmProcExtRuntimeRev	No	No
cpmProcExtUtil5SecRev	No	No
cpmProcExtUtil1MinRev	No	No
cpmProcExtUtil5MinRev	No	No
cpmProcExtPriorityRev	Yes	Yes
cpmProcessType	No	No
cpmProcessRespawn	No	No
cpmProcessRespawnCount	No	No
cpmProcessRespawnAfterLastPatch	No	No
cpmProcessMemoryCore	No	No
cpmProcessLastRestartUser	No	No
cpmProcessTextSegmentSize	No	No
cpmProcessDataSegmentSize	No	No
cpmProcessStackSize	No	No
cpmProcessDynamicMemorySize	No	No

Table 3-46 lists the support matrix for the CISCO-PROCESS-MIB cpmVirtualProcessTable object.

Table 3-46 Support-matrix for cpmVirtualProcessTable

cpmVirtualProcessTable Objects	Process running under Active RSP IOSD Process
cpmVirtualProcessName	Yes
cpmVirtualProcessUtil5Sec	Yes
cpmVirtualProcessUtil1Min	Yes
cpmVirtualProcessUtil5Min	Yes
cpmVirtualProcessMemAllocated	Yes
cpmVirtualProcessMemFreed	Yes
cpmVirtualProcessInvokeCount	Yes
cpmVirtualProcessRuntime	Yes