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 each Management Information Base (MIB) on the Cisco 7200 series router, and the Cisco 7201 router. Each description lists any constraints about how the MIB is implemented on the respective Cisco 7200 series router platform.
Unless noted otherwise, the Cisco 7200 series implementation of a MIB follows the standard. Any objects not listed in a table are implemented as defined in the MIB. For detailed MIB descriptions, see the MIB.
Note Not all MIBs included in a Cisco IOS software release are fully supported by the 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, this does not necessarily mean it is supported by the Cisco 7200 series platform.
The Cisco 7200 series (Cisco 7204VXR, Cisco 7206VXR routers) support the port adapters listed in the following document on Cisco.com":
•Cisco 7200 Series Routers Port Adapter Documentation Roadmap
http://www.cisco.com/en/US/docs/routers/7200/roadmaps/7200_series_port_adapter_doc_roadmap/3530.html
The Cisco 7201 router supports the port adapters listed in the following document on Cisco.com:
•Cisco 7201 Router Port Adapter Documentation Roadmap
http://www.cisco.com/en/US/docs/routers/7200/roadmaps/7201_port_adaper_doc_roadmap/11366pr.html
The following tables list the categories of MIBs in the c7200 Image for Cisco IOS Release 12.2SB REL4 for configurations on the Cisco 7200 router:
•Supported and verified MIBs (tested for Cisco 7200)
•Supported and not verified MIBs (not tested for Cisco 7200 image)
•Not verified and not supported MIBs
Note The RFC versions are listed to show the MIB versions we support.
Note Not all MIBs included in a Cisco IOS software release are fully supported by the 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. The fact that the MIB is included in the image does not necessarily mean it is supported by the Cisco 7200 platform.
Table 3-1 lists the MIBs in the c7200 image that are supported and verified in Cisco IOS Release 12.2SB REL4 on the Cisco 7200 router.
Table 3-2 lists the MIBs in the c7200 image that are supported but not verified in Cisco IOS Release 12.2SB REL4 for the Cisco 7200 router.
Table 3-3 lists the Cisco 7200 MIBs included in c7200 image that are not verified or unsupported in Cisco IOS Release 12.2SB REL4.
CISCO-OAM-MIB |
The ATM-MIB (RFC 1695) contains the ATM and ATM adaptation layer 5 (AAL5) objects used to manage logical and physical entities and the relationship between them, such as ATM interfaces, virtual links, cross connects, and AAL5 entities and connections.
Table 3-4 lists the constraints that the Cisco 7200 router places on objects in the ATM-MIB. For detailed definitions of MIB objects, see the MIB.
The ATM-FORUM-ADDR-REG-MIB contains information about ATM user-network interface (UNI) addresses and ports. The MIB also contains ATM address registration administration information.
There are no constraints on this MIB.
The ATM-FORUM-MIB contains ATM object definitions and object identifiers (OIDs).
The BGP4-MIB (RFC 1657) provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:
•BGP configuration information
•Information about BGP peers and messages exchanged with them
•Information about advertised networks
Table 3-5 lists the constraints that the Cisco 7200 router places on objects in the BGP4-MIB. For detailed definitions of MIB objects, see the MIB.
The BRIDGE-MIB contains objects to manage Media Access Control (MAC) bridges between Local Area Network (LAN) segments, as defined by the IEEE 802.1D-1990 standard. This MIB is extracted from RFC 1493 and is intended for use with network management protocols in TCP/IP-based internets.
The The CISCO-AAA-SERVER-MIB contains information about authentication, authorization, and accounting (AAA) servers within the router and external to the router. The MIB provides:
•Configuration information for AAA servers, including identities of external AAA servers
•Statistics for AAA functions
•Status (state) information for AAA servers
Table 3-6 lists the constraints that the Cisco 7200 router places on objects in the CISCO-AAA-SERVER-MIB. For detailed definitions of MIB objects, see the MIB.
The CISCO-AAA-SESSION-MIB contains information about accounting sessions based on authentication, authorization, and accounting (AAA) protocols.
Table 3-7 lists the constraints that the Cisco 7200 router places on objects in the CISCO-AAA-Session-MIB. For detailed definitions of MIB objects, see the MIB.
The CISCO-AAL5-MIB contains performance statistics for adaptation layer 5 (AAL5) virtual channel connections (VCCs). This MIB provides statistics not found in the cAal5VccTable in RFC 1695 (for example, packets and octets received and transmitted on the VCC).
There are no constraints on this MIB.
The CISCO-ACCESS-ENVMON-MIB indicates the reason for a power supply failure, which is information that is not provided in the ciscoEnvMonSupplyStatusTable in the CISCO-ENVMON-MIB. The CISCO-ACCESS-ENVMON-MIB also defines temperature and voltage notifications to replace those in CISCO-ENVMON-MIB.
The CISCO-ALPS-MIB provides Cisco airline protocol support for IBM-P1024B(ALC) and Unisys-P1024C(UTS) protocol encapsulation over TCP/IP. The MIB contains configuration and operational information for the protocol, which provides a tunneling mechanism to transport airline protocol data across a Cisco router-based TCP/IP network to an X.25-attached mainframe.
The CISCO-ASPP MIB provides configuration and operational information on asynchronous polled protocols such as the asynchronous security protocols that alarm-monitoring companies use. The protocols are handled in Pass-through mode. ASPP handles the receiving and sending of asynchronous blocks.
The CISCO-ATM-EXT-MIB contains extensions to the Cisco ATM module that are used to manage ATM entities. It provides additional AAL5 performance statistics for a virtual channel connection (VCC) on an ATM interface.
Note There are no constraints on this MIB and the ATM-EXT-MIB has only one table. The cAal5VccExtTable augments the aal5VccTable of the AAL5-MIB. The cAal5VccTable contains additional AAL5 performance parameters.
The CISCO-BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:
•BGP configuration information
•Information about BGP peers and messages exchanged with them
•Information about advertised networks
The CISCO-BSC-MIB contains objects to manage binary synchronous communications (BSC) on the router, including BSC ports (serial interfaces) and BSC control units (stations on a port).
The CISCO-BSTUN-MIB contains objects to manage Block Serial Tunnels (BSTUNs) on the router. The MIB provides global BSTUN information and contains configuration and operational information to manage BSTUN groups, ports, and routes.
The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer.
The CISCO-BUS-MIB contains information to manage LANE broadcast and unknown servers.
The CISCO-CAR-MIB contains information about the Committed Access Rate (CAR) assigned to router interfaces. The CAR is used to control the rate of traffic on an interface for packet switching purposes. The MIB provides information about how the router is to handle traffic that conforms and exceeds the CAR on the interface.
The CISCO-CASA-FA-MIB is used in conjunction with the CISCO-CASA-MIB to manage a Cisco Appliance Services Architecture (CASA) forwarding agent (FA).
The CASA protocol allows appliances (software entities such as web caches, firewalls, and load balancers) to control the behavior of forwarding agents (hardware devices such as switches and routers). The appliance tells forwarding agents how to handle packets based on their source and destination IP addresses and ports, and IP protocol fields (this information is called an affinity).
The CISCO-CASA-MIB contains objects to manage a Cisco Appliance Services Architecture (CASA) entity (such as a manager or a forwarding agent). The MIB contains objects to configure CASA, and to retrieve status and operational information about the fixed affinity cache.
The CASA protocol allows appliances (software entities such as web caches, firewalls, and load balancers) to control the behavior of forwarding agents (hardware devices such as switches and routers). The appliance tells forwarding agents how to handle packets based on their source and destination IP addresses and ports, and IP protocol fields (this information is called an affinity).
The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router.
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 access to quality of service (QoS) configuration information and statistics for Cisco platforms that support the Modular Quality of Service command-line interface (Modular QoS CLI).
The MIB uses the following indexes to identify QoS features and distinguish among instances of those features:
•cbQosPolicyIndex—Identifies a service policy that is attached to a logical interface.
•cbQosObjectsIndex—Identifies each QoS feature on the Cisco 7200 router.
•cbQosConfigIndex—Identifies a type of QoS configuration. This index is shared by QoS objects that have identical configurations.
The indexes cbQosPolicyIndex and cbQosObjectsIndex are assigned by the system to uniquely identify each instance of a QoS feature. These indexes are never reused between router reboots, even if the QoS configuration changes.
QoS MIB information is stored in:
•Configuration objects—Includes all ClassMap, PolicyMap, Match Statements, and Feature Actions configuration parameters. Might have multiple identical instances. Multiple instances of the same QoS feature share a single configuration object, which is identified by cbQosConfigIndex.
•Statistics objects—Includes summary counts and rates by traffic class before and after any configured QoS policies are enforced. In addition, detailed feature-specific statistics are available for select PolicyMap features. Each has a unique runtime 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 configurations.
Note The CISCO-CLASS-BASED-QOS-MIB support for the Cisco 7200 NPE-225, the Cisco NPE-400, the Cisco c7200 NPE-G1, and the Cisco 7201 NPE-G2, is the same.
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
•Copy the running configuration to the startup configuration
•Copy the startup or running configuration files to and from a local Cisco IOS file system
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-DLCSW-MIB contains objects to manage Frame-Relay access support (FRAS) sessions to the end-user station. The MIB applies only to downstream or end-user sessions. It does not apply to upstream or host-end sessions, which are managed through the FRAS-HOST-MIB.
The CISCO-DLSW-EXT-MIB is an extension to the CISCO-DLSW-MIB. It contains objects to manage Cisco specific data-link switching (DLSW) protocol enhancements. DLSw provides a way to transport Systems Network Architecture (SNA) and NetBIOS traffic over an IP network.
The CISCO-DLSW-MIB contains objects to manage data-link switches.
The CISCO-DSPU-MIB contains objects to configure and manage Cisco downstream physical unit (DSPU) objects.
The CISCO-ENTITY-ALARM-MIB enables the Cisco 7200 router to monitor alarms generated by system components, such as the chassis, slots, modules, power supplies, fans, and ports.
For a component's alarms to be monitored, the component must be defined by a row in the entPhysicalTable of the ENTITY-MIB in the "ENTITY-MIB (RFC 2737)" section of this guide.
Note The Cisco 7200 router temperature, power supplies, and fan monitoring are implemented in the CISCO-ENTITY-SENSOR-MIB instead of the CISCO-ENTITY-ALARM-MIB.
Table 3-8 lists the constraints that the Cisco 7200 router places on objects in the CISCO-ENTITY-ALARM-MIB. For detailed definitions of MIB objects, see the MIB.
The MIB table, entPhysicalTable, identifies the physical system components in the router. The following list describes the table objects for the CISCO-ENTITY-ALARM-MIB:
•Physical entity—The component in the Cisco 7200 router that generates the alarm.
•Physical vendor type—The object specifies an identifier (typically an enterprise-specific OID) that uniquely identifies the vendor type of those physical entities that this alarm description applies to.
•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 of cards 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), 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 that uniquely identifies an event relative to a physical entity in the Cisco 7200 router. Values 0 through 255.
Table 3-9 lists the alarm descriptions and severity levels for the Cisco 7200 router physical entity, the 6-port clear channel T3 (DS3) card.
Table 3-10 lists the alarm descriptions and severity levels for the Cisco 7200 router physical entities, Gigabit Ethernet and Fast Ethernet port adapter cards.
Table 3-11 lists the alarm descriptions and severity levels for the Cisco 7200 router physical entities, 1 and 2-Port OC-3/STM-1 and 1-Port OC-3c/STM-1 POS port adapters.
Table 3-12 lists the alarm descriptions and severity levels for the Cisco 7200 router physical entities, 1-Port ATM OC-3/STM-1 port adapter.
Table 3-13 lists the alarm descriptions and severity levels for the Cisco 7200 router physical entities, 1-port enhanced ATM T3, and E3 port adapters.
The CISCO-ENTITY-ASSET-MIB provides asset tracking information for the physical components in the ENTITY-MIB (RFC 2737) entPhysicalTable. This MIB is applicable to all line and processor cards.
The ceAssetTable contains an entry (ceAssetEntry) for each physical component on the router. Each entry provides information about the component, such as its orderable part number, serial number, hardware revision, manufacturing assembly number, and manufacturing revision.
Program most physical components with a standard Cisco generic ID PROM value that specifies asset information for the component. If possible, the MIB accesses the component's ID PROM information.
The CISCO-ENTITY-ASSET-MIB contains two object groups:
•ceAssetGroupRev1—The collection of objects which are used to describe and monitor asset-related extension data of ENTITY-MIB (RFC 2737) entPhysicalTable items.
•ceAssetEntityGroup—The ceAssetEntityGroup duplicates the objects in entPhysicalTable of the ENTITY-MIB (RFC 2737).
Table 3-14 lists the constraints that the Cisco 7200 router places on objects in the CISCO-ENTITY-ASSET-MIB. For detailed definitions of MIB objects, see the 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 names for each processor module.
The CISCO-ENTITY-EXT-MIB contains two tables:
•The ceExtPhysicalProcessorTable table contains information related to processor RAM and NVRAM sizes (total and used).
•The ceExtConfigRegTable table contains information related to configuration register settings and boot images.
Table 3-15 lists the constraints that the Cisco 7200 router places on objects in the CISCO-ENTITY-EXT-MIB. For detailed definitions of MIB objects, see the MIB. Any objects not listed in this table are implemented as defined in this MIB.
|
|
---|---|
|
|
|
Read only. |
|
Read only. |
Note The CISCO-ENTITY-EXT-MIB is only supported for the physical entities representing active processors.
The CISCO-ENTITY-FRU-CONTROL-MIB contains objects to configure and monitor the status of field replaceable units (FRUs) on the Cisco 7200 router. An FRU is a hardware component that can be replaced on site.
Table 3-16 lists the constraints that the router places on objects in the CISCO-ENTITY-FRU-CONTROL-MIB. For detailed definitions of MIB objects, see the MIB.
The CISCO-ENTITY-SENSOR-MIB contains objects that monitor the values of sensors in the ENTITY-MIB (RFC 2037) entPhysicalTable. The CISCO-ENTITY-SENSOR-MIB:
•Is a Cisco private MIB to support a monitoring function of sensor devices.
•Discovers the sensor devices in the system and provides the ability to monitor the status of the system.
•Provides the threshold values and notifications for each sensor.
The sensor entities shown in this MIB are the physical entities whose entity class are defined to sensor(8) in the entPhysicalTable.
The CISCO-ENTITY-VENDORTYPE-OID-MIB defines the object identifiers (OIDs) assigned to various Cisco 7200 router components. The OIDs in this MIB are used by the entPhysicalTable of the ENTITY-MIB as values for the entPhysicalVendorType field in entPhysicalTable. Each OID uniquely identifies a type of physical entity, such as a chassis or port adapters.
Table 3-17 lists the objects and OIDs in the CISCO-ENTITY-VENDORTYPE-OID-MIB that describe router entities. For detailed definitions of MIB objects, see the MIB.
The CISCO-ENVMON-MIB contains information about the status of environmental sensors (for voltage, temperature, and power supplies). It also contains MIB objects to enable and disable notifications for changes to the status of these sensors.
The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.
The CISCO-FRAME-RELAY-MIB contains Frame Relay information that is specific to Cisco products or that is missing from RFC 1315.
The CISCO-FRAS-HOST-MIB contains objects specific to upstream or host-end sessions.
The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management.
The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB. It contains objects to perform functions such as assigning secondary HSRP IP addresses, monitoring the operational status of interfaces, and modifying an HSRP group's priority.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281. The following list defines HSRP terms:
•HSRP is a protocol used among a group of routers for the purpose of selecting an active router and a standby router.
•Active router is the router of choice for routing packets.
•Standby router takes over the routing duties when an active router fails, or when preset conditions have been met.
•HSRP group or a standby group is a set of routers which communicate using HSRP. An HSRP group has a group MAC address and a group Virtual IP address. These are the designated addresses. The active router assumes or inherits these group addresses.
•Hello messages indicate that a router is running and is capable of becoming the active or standby router.
•Hellotime is the interval between successive HSRP hello messages from a specific router.
•Holdtime is the interval between the receipt of a hello message and the assumption that the sending router has failed.
The CISCO-IETF-ATM2-PVCTRAP-MIB supplements the ATM-MIB. It implements the virtual channel link (VCL) section of the IETF document "draft-ietf-atommib-atm2-11.txt," Section 9 ATM Related Trap Support.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
The CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN contains information for monitoring ATM interfaces that are not defined in the ATM-MIB or the CISCO-IETF-ATM2-PVCTRAP-MIB.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
The CISCO-IETF-IP-FORWARD-MIB contains objects to manage multipath IP routes in a classless interdomain routing (CIDR) environment. This MIB is based on the IETF document draft-ietf-ipngwg-rfc2096-update-00.txt.
The CISCO-IETF-IP-MIB contains objects to manage the Internet Protocol (IP), but not to manage IP routes. The MIB also contains objects to manage the Internet Control Message Protocol (ICMP). It is based on the IETF document "draft-ietf-ipngwg-rfc2011-update-00.txt."
The CISCO-IMAGE-MIB is the router image MIB which identifies the identifies the characteristics and capabilities of the Cisco IOS software image running on the router.
There are no constraints on this MIB.
The CISCO-IP-STAT-MIB contains objects to manage the collection and display of IP statistics, categorized by IP precedence and the Media Access Control (MAC) address associated with IP packets. To use the MIB to access additional IP statistics, you can execute the following commands from the CLI:
•show interfaces mac-accounting
•show interfaces precedence
The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.
The ciscoIpMRouteInLimit object is obsolete.
Note The CISCO-ENHANCED-MEMORY-POOL-MIB is not supported in this release.
The CISCO-ENHANCED-MEMORY-POOL-MIB contains objects to monitor memory pools on all physical entities on a managed system Memory utilization 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 pool types—Currently predefined as:
–1:processor memory
–2:i/o memory
–3:pci memory
–4:fast memory
–5:multibus memory
•Dynamic pool types—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. For detailed definitions of the CISCO-ENHANCED-MEMORY-POOL-MIB objects, see the MIB.
Note CISCO-ENHANCED-MEMORY-POOL-MIB retrieves used and free information from sysdb namespace. If mempool type is not found, it returns zero length to the SNMP core agent.
Note The OLD-CISCO-MEMORY-MIB contains objects that describe memory pools on devices running an earlier implementation of the Cisco IOS operating system. This MIB was replaced by the CISCO-MEMORY-POOL-MIB.
The CISCO-LEC-DATA-VCC-MIB module is a Cisco extension to the ATM Forum's LANE Client MIB. This extension identifies those VCCs which are being used to carry packets sent on LANE Data Direct VCCs.
The CISCO-LEC-EXT-MIB module is a Cisco extension to the ATM Forum's LANE client MIB.
The CISCO-LECS-MIB contains objects that manage LANE configuration in Cisco devices.
The CISCO-LES-MIB contains objects that manage LANE service in Cisco devices.
The CISCO-MEMORY-POOL-MIB contains objects to monitor memory pools on the router.
There are no constraints on this MIB.
The CISCO-NBAR-PROTOCOL-DISCOVERY-MIB provides SNMP support for Network-Based Application Recognition (NBAR), including enabling and disabling protocol discovery on a per-interface basis and configuring the traps that are generated when certain events occur. You can also display the current NBAR configuration and run-time statistics.
Note The MODULE-IDENTITY for the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB is ciscoNbarProtocolDiscoveryMIB, and its top-level OID is 1.3.6.1.4.1.9.9.244 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoNbarProtocolDiscoveryMIB).
The CISCO-NETFLOW-MIB contains objects that remotely obtains and manages cache flow information, current NetFlow configuration, and statistics.
The Netflow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics.The MIB provides Netflow information in these areas:
•Cache information and configuration.
•Export information and configuration.
•Export Statistics.
•Protocol Statistics.
•Version 9 Export Template information.
•Top Flows information.
Table 3-20 lists object groups supported in the CISCO-NETFLOW-MIB in order to to manage informative and configurable parameters.
SNMP is used to collect network information. SNMP permits retrieval of critical information from network elements such as routers, switches, and workstations. The CISCO-NETFLOW-MIB feature uses SNMP to configure NetFlow and to gather NetFlow statistics.
The CISCO-NETFLOW-MIB contains objects that allow NetFlow statistics and other NetFlow data for the managed devices on your system to be retrieved by SNMP. You can specify retrieval of NetFlow information from a managed device (for example, a router) either by entering commands on that managed device or by entering SNMP commands from the NMS workstation to configure the router through the MIB.
If the NetFlow information is configured from the NMS workstation, no access to the router is required and all configuration can be performed through SNMP. The CISCO-NETFLOW-MIB request for information is sent from an NMS workstation through SNMP to the router and is retrieved from the router. This information is stored or viewed, thus allowing NetFlow information to be easily accessed and transported across a multivendor programming environment.
The CISCO-NETFLOW-MIB feature defines managed objects that enable a network administrator to remotely monitor the following NetFlow information:
•Flow cache configuration information
•NetFlow export information
•General NetFlow statistics
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-PAE-MIB contains objects to manage port access entities (PAEs) on the router, as defined by IEEE Std 802.1x. The MIB contains PAE information that is not included in the IEEE8021-PAE-MIB or that is specific to Cisco products.
The CISCO-PIM-MIB defines Cisco specific objects and variables for managing Protocol Independent Multicast (PIM) 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.
Table 3-22 lists the constraints that the Cisco 7200 router places on objects in the CISCO-PING -MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
|
•ciscoPingVrfName |
Read-only. |
The CISCO-PPPOE-MIB contains objects to manage Point-to-Point Protocol over Ethernet (PPPoE) sessions. These objects represent PPPoE sessions at the system and virtual channel (VC) level.
Table 3-22 lists the constraints that the Cisco 7200 router places on objects in the CISCO-PPPOE -MIB. For detailed definitions of MIB objects, see the MIB.
The CISCO-PROCESS-MIB displays memory and CPU usage on the router, and describes active system processes. This MIB is used to retrieve statistics for both the first and second CPUs. For additional information, see How to Collect CPU Utilization on Cisco IOS Devices Using SNMP, page A-26.
Table 3-23 lists the constraints that the Cisco 7200 router places on objects in the CISCO-PROCESS-MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
|
•cpmCPUTotal5sec |
Deprecated. |
•cpmCPUTotal1min |
Deprecated. |
•cpmCPUTotal5min |
Deprecated. |
The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to Cisco hardware platforms. The following product OID (sysObjectID) are assigned for the CISCO 7200 Series router:
•cisco7206 = 1.3.6.1.4.1.9.1.108 OID
•cisco7204 = 1.3.6.1.4.1.9.1.125 OID
•cisco7206VXR = 1.3.6.1.4.1.9.1.222 OID
•cisco7204VXR = 1.3.6.1.4.1.9.1.223 OID
•cisco7201 = 1.3.6.1.4.1.9.1.821 OID
The CISCO-QLLC01-MIB contains objects to configure and monitor logical connections for the Qualified Logical Link Control (QLLC) protocol.
The CISCO-QUEUE-MIB contains objects to manage interface queues, which can be used for FIFO, priority, custom, and fair queuing.
The CISCO-RSRB-MIB contains objects used to manage remote source-route bridging (RSRB) on the router. This MIB provides information about the attributes of the local-remote RSRB peer relationship.
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 the length of time it took to complete.
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-24 lists the constraints that the Cisco 7200 router places on objects in the CISCO-RTTMON-MIB. For detailed definitions of MIB objects, see the MIB.
The CISCO-SDLLC-MIB contains object to manage SDLC Logical Link Control (SDLLC). The MIB contains read-only configuration and operational information for the Cisco implementation of Synchronous Data Link Control (SDLC) to Logical Link Control, type 2 (LLC2) media translation.
The CISCO-SMI-MIB defines the structure of management information for Cisco enterprise MIBs.
The CISCO-SNAPSHOT-MIB contains objects to manage snapshot routing, which helps improve the use of system resources for static routing and routing for dedicated serial lines.
The CISCO-SSG-MIB contains objects to manage the Service Selection Gateway (SSG) product on the router. SSG enables service providers to offer subscribers access to the Internet, corporate networks, and value-added services through broadband access technology such as digital subscriber lines (DSL), cable modems, and wireless access.
SSG works in conjunction with the Cisco Service Selection Dashboard (SSD) or its successor product, the Cisco Subscriber Edge Services Manager (SESM), to:
•Authenticate the access rights of subscribers
•Provide subscribers with a selection of services available to them
•Connect subscribers to services
Subscribers can:
•Dynamically connect to and disconnect from services (which can be public or private)
•Concurrently connect to a number of different services
SSG communicates with the authentication, authorization, and accounting (AAA) management network where RADIUS, Dynamic Host Configuration Protocol (DHCP), and Simple Network Management Protocol (SNMP) servers reside. SSG also communicates with the Internet service provider (ISP) network, which may connect to the Internet, corporate networks, and value-added services.
Table 3-25 lists the constraints that the Cisco 7200 router places on objects in the CISCO-SSG-MIB. For detailed definitions of MIB objects, see the MIB
The CISCO-STUN-MIB contains objects to configure and monitor serial tunneling (STUN) on the router. The MIB contains global STUN configuration and operational information, and objects to manage STUN groups, ports, and routes.
The CISCO-SYSLOG-MIB contains all system log messages generated by the Cisco IOS software. The MIB provides a way to access syslog messages through SNMP. All Cisco IOS syslog 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 syslog messages and counts related to syslog messages.
Note You can configure the Cisco 7200 router to send syslog messages to a `syslog' server.
The MIB does not keep track of messages generated from commands entered through the command line interface (CLI).
The CISCO-TC-MIB defines the textual conventions used in Cisco enterprise MIBs.
The CISCO-TCP-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router. This MIB is an extension to the IETF TCP MIB.
The CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB contains VLAN-ID and ifIndex information for each routed virtual LAN (VLAN) interface on the router. A routed VLAN interface is the router interface or subinterface to which you attach the IP address used by the router on the VLAN.
On the Cisco 7200 router, the MIB contains information about VLAN subinterfaces created on GigE WAN ports on the 4-port GigE WAN Optical Services Module (OSM-2+4GE-WAN+). The MIB maps each VLAN-ID to an ifIndex, which you can use to access the ipRouteTable to obtain the routing configuration for the routed VLAN interface.
The CISCO-VPDN-MGMT-MIB provides operational information about the Virtual Private Dialup Network (VPDN) feature on the router. You can use the MIB to monitor VPDN tunnel information on the router, but you cannot use the MIB to configure VPDN.
VPDN enables the router to forward Point-to-Point Protocol (PPP) traffic between an Internet service provider (ISP) and a home gateway. The CISCO-VPDN-MGMT-MIB includes several tables that contain VPDN tunneling information:
•cvpdnSystemTable—Provides system-wide VPDN information.
•cvpdnTunnelAttrTable—Provides information about each active tunnel.
•cvpdnSessionAttrTable—Provides information about each active session within each tunnel.
•cvpdnUserToFailHistInfoTable—Provides information about the last failure that occurred for each tunnel user.
•cvpdnTemplateTable—Identifies each VPDN template and indicates the number of active sessions associated with the template. See Table 3-22 for information about template name restrictions and and their effect on SNMP.
Table 3-26 lists the constraints that the Cisco 7200 router places on objects in theCISCO-VPDN-MGMT- MIB. The CISCO-VPDN-MGMT-MIB objects in Table 3-26 have been deprecated. Although currently supported, their use is being phased out and we recommend that you use the replacement object instead. For detailed definitions of MIB objects, see the MIB.
The Cisco VPDN management MIB extension is a supplement to CISCO-VPDN-MGMT-MIB with additional information for VDPN tunnels and sessions.
The MIB contains the following tables, which provide read-only information not found in the CISCO-VPDN-MGMT-MIB:
•cvpdnTunnelExtTable—Provides information about Layer 2 Tunnel Protocol (L2TP) tunnels, such as tunnel statistics and User Datagram Protocol (UDP) port numbers.
•cvpdnSessionExtTable—Provides information about L2TP sessions, as well as information about session packet counts, packet sequencing information, window size, and operating characteristics.
Table 3-27 lists the constraints that the Cisco 7200 router places on objects in the CISCO-VPDN-MGMT-EXT-MIB. For detailed definitions of MIB objects, see the MIB
The DLSW-MIB (RFC 2024) contains objects to manage data-link switching (DLSw) on the router.
The ENTITY-MIB contains a table called, entPhysicalTable that identifies physical system components (logical entities) in the Cisco 7200 router and allows SNMP management of those entities. This MIB is applicable to chassis, processor cards, port adapters, fans, and power supplies.
The following are the five conformance groups contained in the Entity-MIB:
•entityPhysical group—Describes the physical entities managed by a single agent.
•entityLogical group—Describes the logical entities managed by a single agent.
•entityMapping group—Describes the associations between the physical entities, logical entities, interfaces, and non-interface ports managed by a single agent.
•entityGeneral group—Describes general system attributes shared by potentially all types of entities managed by a single agent.
•entityNotifications group—Contains status indication notifications.
The following two groups are added from RFC 2737:
•entityPhysical2 group—This group augments the entityPhysical group.
•entityLogical2 group—Describes the logical entities managed by a single agent, and replaces entityLogical group.
Table 3-28 lists the constraints that the router places on objects in the ENTITY-MIB. For detailed definitions of MIB objects, see the MIB.
The following MIB entities are dependent on each user's configuration:
•entPhysicalIndex—Uniquely identifies each entity in the router. The index is also used to access information about the entity in other MIB tables.
•entPhysicalContainedIn—Indicates the entPhysicalIndex of a component's parent entity. The value of entPhysicalIndex for the physical entity which 'contains' this physical entity. A value of zero indicates this physical entity is not contained in any other physical entity.
•entPhysicalParentRelPos—An integer that shows the relative position of same-type entities that have the same entPhysicalContainedIn value (for example, slots).
The entPhysicalTable contains a single row for the Cisco 7200 chassis and a row for each entity in the chassis. A physical entity may contain other entities (for example, a fan-tray bay may contain a fan-tray module, which may contain one or more fans). The physical hierarchy of system components is determined at runtime, based on the actual configuration.
Table 3-29 lists entPhysicalTable entries for the Cisco 7200 router.
Table 3-30 lists entPhysicalTable entries for the Cisco 7200 router network service engine (NSE) cards.
Table 3-31 lists entPhysicalTable entries for the Cisco 7200 Router OC-3-POS components.
Table 3-32 lists entPhysicalTable Entries for Cisco 7200 Chassis Components.
The ENTITY-MIB supports the Cisco compliance effort for a Cisco unique device identifier (UDI) standard which is stored in IDPROM.
The Cisco UDI provides a unique identity for every Cisco product. The unique device identifier is comprised of an orderable product identifier (PID), the version identifier (VID), and the hardware Serial Number (SN). The UDI is stored in IDPROM. The PID, VID, and SN must be stored in the entPhysicalTable:
•PID shall be stored in the entPhysicalModelName object
•VID shall be stored in the entPhysicalHardwareRev object
•SN shall be stored in the entPhysicalSerialNum object
Note The Version ID returns NULL for those old or existing cards whose IDPROMs do not have the Version ID field. Therefore, corresponding entPhysicalHardwareRev returns NULL for cards that do not have the Version ID field in IDPROM.
Each product that is capable of MIB support is required to populate ENTITY-MIB v2 or later with PID, VID, and SN. This compliance is also a requirement of the Consistent Network Element Manageability initiative. If the product uses both ENTITY-MIB and CISCO-ENTITY-ASSET-MIB, then the data in the following fields should be identical.
ENTITY-MIB v2 (RFC-2737) fields to be populated are:
•Entity-MIB.entPhysicalName (Product Name)
•Entity-MIB.entPhysicalDescr (Product Description)
•Entity-MIB.entPhysicalModelName (PID)
•Entity-MIB.entPhysicalHardwareRev (VID)
•Entity-MIB.entPhysicalSerialNumber (SN)
The ETHERLIKE-MIB (RFC 2665) contains objects to manage Ethernet-like interfaces on the Cisco 7200 router.
Table 3-33 lists the constraints that the Cisco 7200 router places on objects in the ETHERLIKE-MIB. Any objects not listed in this table are implemented as defined in the MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
Not implemented |
|
Not implemented |
|
Not implemented |
Table 3-34 shows usage of ifTable for Ethernet-like layer.
The EVENT-MIB contains objects to define event triggers and actions for network management purposes.
Table 3-35 lists the constraints that the Cisco 7200 router places on objects in the EVENT-MIB. Any objects not listed in this table are implemented as defined in the MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
|
•mteTriggerFrequency |
Read-only. |
The EXPRESSION-MIB contains objects to define expressions of MIB objects for network management purposes.
Table 3-36 lists the constraints that the Cisco 7200 router places on objects in the EXPRESSION-MIB. Any objects not listed in this table are implemented as defined in the MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
|
•expObjectConditional |
Read-only. |
The MIB module for managing remote monitoring device implementations. This MIB module augments the original RMON MIB as specified in RFC 1757 and RFC 1513 and RMON2 MIB as specified in RFC 2021.
The Port Access Entity module for managing IEEE 802.1X.
The IEEE 8023-LAG-MIB is the Link Aggregation module for managing IEEE Standard 802.3ad.
The IF-MIB (RFC 2233) describes the attributes of physical and logical interfaces. The router supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, and ifConnectorPresent).
Table 3-37 lists the constraints that the Cisco 7200 router places on objects in the IF-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-38 contains RFC-1407 MIB constraints..
The IGMP-MIB contains objects to manage the Internet Group Management Protocol (IGMP) on the router.
The INT-SERV-GUARANTEED-MIB describes the guaranteed service of the Integrated Services Protocol (ISP).
The INT-SERV-MIB describes the Integrated Services Protocol (ISP).
The IPMROUTE-MIB contains objects to manage IP multicast routing on the router, independent of the actual multicast routing protocol in use.
This module defines a portion of the management information base (MIB) for managing ATM LAN Emulation Client nodes. It is meant to be used in connection with the AToM MIB and MIB-II / RFC 1573 'ifTable' entries for each LEC / emulated 802.x network interface. The RFC1406-MIB provides access to configuration and performance monitoring information for DS1 controllers and interfaces on the Cisco 7200 router.
The MPLS-LDP-MIB (version 1) provides management information for the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), which is used by label switching routers (LSRs) to communicate the definitions of labels that each router is using. The router supports the IETF draft version of this MIB (draft-ietf-mpls-ldp-mib-08.txt).
For detailed information about this MIB, see its feature module description at the following URL:
http://www.cisco.com/en/US/docs/ios/12_0st/12_0st21/feature/guide/ldpmib21.html
Table 3-39 lists the constraints that the Cisco 7200 router places on objects in the MPLS-LDP-MIB. For detailed definitions of MIB objects, see the MIB. Any object not listed in this table is implemented as defined in the MIB.
The MPLS-LSR-MIB provides configuration and performance monitoring information to manage label switched paths (LSPs) through a label switching router (LSR) that is using the Multiprotocol Label Switching (MPLS) technology. The router supports the IETF version of the MPLS-LSR-MIB.
For detailed information about this MIB, see its feature module description at the following URL:
http://www.cisco.com/en/US/docs/ios/12_0st/release/notes/rn120ST.html
Table 3-40 lists the constraints that the Cisco 7200 router places on objects in the MPLS-LSR-MIB. For detailed definitions of MIB objects, see the MIB. Any object not listed in the table is implemented as defined in the MIB.
The MPLS-TE-MIB enables the Cisco 7200 router to perform traffic engineering for MPLS tunnels. The MIB is based on Revision 05 of the IETF MPLS-TE-MIB.
Traffic engineering support for MPLS tunnels requires the following configuration:
•Setting up MPLS tunnels along with appropriate configuration parameters.
•Configuring tunnel loose and strict source routed hops.
Refer to the Cisco MPLS MIB team web page for more documentation on this MIB: http://mpls-mib-group.cisco.com/
Table 3-41 lists the constraints that the Cisco 7200 router places on objects in the MPLS-TE-MIB. For detailed definitions of MIB objects, see the MIB. Any objects not listed in this table are implemented as defined in the MIB.
The MPLS-VPN-MIB:
•Describes managed objects for modeling a Multi-Protocol Label Switching/Border Gateway Protocol Virtual Private network.
•Configures and monitor routes and route targets for each VRF instance on a router
•Facilitates provisioning VPN Routing and Forwarding (VRF) instances on MPLS interfaces
•Measures the performance of MPLS/BGP VPNs
The MIB is based on Revision 05 of the IETF MPLS-VPN-MIB.
Note Refer to the Cisco MPLS MIB team web page for more documentation on this MIB: http://mpls-mib-group.cisco.com/
Table 3-42 lists the constraints that the Cisco 7200 router places on objects in the MPLS-VPN-MIB. For detailed definitions of MIB objects, see the MIB. Any objects not listed in the table are implemented as defined in the 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 NOTIFICATION-LOG-MIB defines objects that record notification information against lost notifications, whether those are traps or informs (the two types of notifications supported). It provides inventory management and monitoring capabilities. This MIB provides common infrastructure for other MIBs in the form of a local logging function.
The management stations:
•Query the MIB using GET requests to determine if they missed any notifications which were generated but were never received.
•Refine the MIB logs by using the SNMP SET operation on objects which enable control over log sizes. This control can be executed on a global basis (affecting the whole Notification Log MIB database) or on a per named log basis.
•Specify the maximum time a notification can remain logged in the Notification Log MIB.
Note Because this MIB logs all notifications, this ensures that all notifications which are dropped from the trap queue are also logged by this MIB. Inform retries are not logged. Traps sent to multiple recipients are logged only one time. Currently, this MIB logs notifications originating at the local engine only.
The NOVELL-IPX-MIB defines the management information for a system using the IPX protocol. This MIB is designed to provide a basic framework for the management of systems implementing the IPX protocol. This MIB is virtually identical to the IPX MIB distributed as a part of the Novell NetWare Link Services Protocol (NLSP) Specification 1.0, Novell Part Number 100-001708-002, 2nd Edition Feb '94.
The NOVELL-RIPSAP-MIB defines the management information for the RIP and SAP protocols running in an IPX environment. It provides information in addition to that contained in the IPX MIB itself. This MIB is virtually identical to the RIPSAP MIB distributed as a part of the Novell NetWare Link Services Protocol (NLSP) Specification 1.0, Novell Part Number 100-001708-002, 2nd Edition Feb '94.
The OLD-CISCO-APPLETALK-MIB provides information about Appletalk traffic on the router.
The OLD-CISCO-CHASSIS-MIB describes chassis objects in devices running an earlier release of the Cisco IOS operating system. This MIB is deprecated, and is being replaced by the ENTITY-MIB. However, the Cisco 7200 router implements the OLD-CISCO-CHASSIS-MIB to support earlier network management applications that do not implement the ENTITY-MIB.
Network management applications that do not support the ENTITY-MIB can use the OLD-CISCO-CHASSIS-MIB to discover port adapters.
The OLD-CISCO-CHASSIS-MIB is deprecated. Most chassis objects are now described in the ENTITY-MIB; therefore, where possible, we recommend that you use the ENTITY-MIB instead of the OLD-CISCO-CHASSIS-MIB.
The OLD-CISCO-CHASSIS-MIB is supported on the Cisco 7200 router for modules and port adapters. Table 3-43 lists the constraints that the router places on objects in the MIB. For detailed definitions of MIB objects, see the MIB.
The OLD-CISCO-CPU-MIB describes CPU usage and active system processes on devices running an earlier implementation of the Cisco IOS operating system.
The OLD-CISCO-DECNET-MIB provides information about the implementation of DECnet on the router. DECnet is group of communications products (including a protocol suite) developed by Digital Equipment Corporation that supports the Open System Interconnection (OSI) protocol and proprietary Digital protocols.
The OLD-CISCO-INTERFACES-MIB contains objects to manage interfaces on devices running an earlier implementation of the Cisco IOS operating system.
The OLD-CISCO-IP-MIB contains objects to manage IP on devices running an earlier implementation of the Cisco IOS operating system.
Table 3-44 lists the constraints that the router places on objects in the MIB. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
Deprecated. |
|
Deprecated. |
|
Deprecated. |
The OLD-CISCO-MEMORY-MIB contains objects that describe memory pools on devices running an earlier implementation of the Cisco IOS operating system.
The OLD-CISCO-NOVELL-MIB provides information about Novell traffic on the router, including packet counts and IPX accounting and checkpoint accounting information.
The OLD-CISCO-SYSTEM-MIB provides information about the router (such as its name, software bootload, and configuration file), and contains controls for reloading software onto the router and clearing the Address Resolution Protocol (ARP) cache.
Starting with Cisco IOS software Release 10.2, all objects defined in this MIB have been deprecated. They have been replaced with the objects defined in the CISCO-TCP-MIB.my document. Management applications should no longer examine the objects defined in this MIB.
The OLD-CISCO-TS-MIB provides information about the number of terminal lines and virtual lines on this device.
The PIM-MIB contains objects to configure and manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.
Table 3-45 describes the constraints on tables from the PIM-MIB. Any objects or tables not listed in this table are defined as in the MIB.
|
|
---|---|
|
Read-only. |
|
Read-only. |
|
Read-only. |
|
Deprecated. |
The RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets.
The RFC1243-MIB uses the extended OBJECT-TYPE macro as defined in llapEntry 9 (9). The total number of times this LocalTalk interface received a lapRTS packet and expected a data packet, but did not receive any data packet.
Table 3-46 describes the constraints on tables from the PIM-MIB. Any objects or tables not listed in this table are defined as in the MIB.
The RFC1253-MIB contains objects to manage Version 2 of the Open Shortest Path First (OSPF) protocol.
The RFC1315-MIB contains objects to manage a Frame Relay data terminal equipment (DTE) interface, which consists of a single physical connection to the network with many virtual connections to other destinations and neighbors. The MIB contains the objects used to manage:
•The Data Link Connection Management Interface (DLCMI)
•Virtual circuits on each Frame Relay interface
•Errors detected on Frame Relay interfaces
Table 3-47 lists the constraints that the Cisco 7200 router places on objects in theRFC1315-MIB. For detailed definitions of MIB objects, see the MIB.
The RFC1315-MIB contains objects to manage a Frame Relay data terminal equipment (DTE) interface, which consists of a single physical connection to the network with many virtual connections to other destinations and neighbors. The MIB contains the objects used to manage:
•The Data Link Connection Management Interface (DLCMI)
•Virtual circuits on each Frame Relay interface
•Errors detected on Frame Relay interfaces
Table 3-47 lists the constraints that the Cisco 7200 router places on objects in theRFC1315-MIB. For detailed definitions of MIB objects, see the MIB.
The RFC1381-MIB (LAPB MIB file) was extracted from RFC 1381. The LAPB administration table contains objects that can manage a LAPB interface.
The RFC1382-MIB was extracted from RFC 1382. Several changes were made to the MIB to allow it to compile in a Cisco environment:
•Remove IMPORT statements for EntryStatus, PositiveInteger, and IfIndexType.
•Hand-imported the above types by copying the definitions from their respective files.
•The range of x25OperRestartCount was increased to be the largest integer possible.
The DS1-MIB defined by RFC2495 provides access to configuration and performance monitoring information for DS1 controllers (digital signal levels) and interfaces on the Cisco 7200 router.
The DS3-MIB defined by RFC2496 provides access to configuration and performance monitoring information for DS3 controllers and interfaces.
The RFC2006-MIB is the MIB module for the Mobile IP.
The RMON-MIB contains objects to remotely monitor devices in the network. Supports MIB version RFC 1757.
Table 3-49 lists the constraints that the Cisco 7200 router places on objects in the RMON-MIB. For detailed definitions of MIB objects, see the MIB. Any other object not listed in the table is implemented as defined in the RMON-MIB.
The RMON2-MIB contains objects to manage remote monitoring device implementations. This MIB module augments the original RMON MIB as specified in RFC 1757. We support the RFC 2021 version of the MIB.
The RS232-MIB contains objects to manage RS-232-like hardware interfaces and devices.
The RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP).
Table 3-50 lists the constraints that the Cisco 7200 router places on objects in theRSVP-MIB. For detailed definitions of MIB objects, see the MIB. Any other object not listed in the table is implemented as defined in the RSVP-MIB.
|
|
---|---|
|
|
•rsvpSessionNewIndex |
Read-only. |
•rsvpSenderNewIndex |
Read-only. |
•rsvpResvNewIndex |
Read-only. |
•rsvpResvFwdNewIndex |
Read-only. |
The SMON-MIB manages remote monitoring device implementations for Switched Networks. Identifies the source of the data that the associated function is configured to analyze. This Textual Convention extends the DataSource Textual Convention defined by RMON 2 to the following data source types:
•ifIndex
•smonVlanDataSource
•entPhysicalEntry
The SNA-SDLC-MIB contains objects that manage SDLC (synchronous data link control) devices.
The SNMP-FRAMEWORK-MIB (RFC 2571) contains objects that describe the SNMP management architecture.
There are no constraints on this MIB.
The SNMP-NOTIFICATION-MIB contains managed objects for SNMP v3 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 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). There are no constraints on this MIB.
The SNMP-USM-MIB (RFC 2574) contains objects that describe the SNMP User-based Security Model. There are no constraints on this MIB.
The SNMP-VACM-MIB (RFC 2575) contains objects that describe the view-based access control model for SNMP.
Note To access this MIB, you must create an SNMP v3 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
Table 3-51 lists the constraints that the Cisco 7200 router places on objects in the SNMP-VACM-MIB. For detailed definitions of MIB objects, see the MIB. Any other object not listed in the table is implemented as defined in the SNMP-VACM-MIB.
|
|
---|---|
|
|
•vacmViewSpinLock |
Read-only. |
The SNMPv2-MIB contains objects SNMPv2 entities. The SNMPv2-MIB contains the following mandatory object groups:
•SNMP group—Collection of objects providing basic instrumentation and control of an SNMP entity.
•System group—Collection of objects common to all managed systems.
•snmpSetGroup—Collection of objects which allow several cooperating SNMPv2 entities, all acting in a manager role, to coordinate their use of the SNMPv2 set operation.
•snmpBasicNotificationsGroup—The two notifications are coldStart and authenticationFailure which an SNMPv2 entity is required to implement.
The SONET-MIB provides both configuration and performance monitoring objects for SONET interfaces.
Table 3-52 lists the constraints that the Cisco 7200 router places on objects in the SONET-MIB. Any other objects not listed in the table are defined as in the RFC1595 MIB definition. For detailed definitions of MIB objects, see the MIB.
|
|
---|---|
|
|
•sonetPathCurrentStatus |
Range {1 62} |
The SOURCE-ROUTING-MIB contains objects to configure and manage source routing and source routing transparent bridges. We support the RFC 1525 version of the MIB.
The TCP-MIB (RFC 2012) contains objects to manage the Transmission Control Protocol (TCP) implementations on the router. There are no constraints.
The UDP-MIB (RFC 2013) contains objects to manage the User Datagram Protocol (UDP) on the router. There are no constraints.