cisco 7200 series router mib specifications guide · 1 cisco 7200 router mib specifications guide...

Cisco 7200 Series Router MIB Specifications GuideRelease 12.4(11)T Release 12.4(4)XD7 Release 12.2(31)SB5

April 2007

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

Text Part Number: OL-6384-04

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0903R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

Cisco 7200 Series Routers MIB Specifications Guide © 2009 Cisco Systems, Inc. All rights reserved

OL-6384-04

C O N T E N T S

About This Guide ix

Guide Revision History ix

Audience xii

Organization xiii

Terminology and Definitions xiv

Obtaining Documentation xv

Cisco.com xv

Ordering Documentation xv

Documentation Feedback xv

Obtaining Technical Assistance xvi

Cisco Technical Support Website xvi

Submitting a Service Request xvi

Definitions of Service Request Severity xvii

Obtaining Additional Publications and Information xvii

C H A P T E R 1 Cisco 7200 Router MIB Overview 1-1

Benefits of MIB Enhancements 1-1

SNMP Overview 1-2

MIB Description 1-2

SNMP Notifications 1-3

SNMP Versions 1-3

SNMPv1 and SNMPv2c 1-4

SNMPv3 1-4

SNMP Security Models and Levels 1-4

Requests for Comments 1-5

Object Identifiers 1-6

Related Information and Useful Links 1-6

TAC Information and FAQs 1-6

SNMP Configuration Information 1-6

C H A P T E R 2 Configuring MIB Support 2-1

Determining MIBs Included for Cisco IOS Releases 2-1

Downloading and Compiling MIBs 2-2

1Cisco 7200 Router MIB Specifications Guide

Contents

Considerations for Working with MIBs 2-2

Downloading MIBs 2-3

Compiling MIBs 2-3

Enabling SNMP Support 2-4

C H A P T E R 3 MIB Specifications 3-1

Cisco 7200 MIBs 3-1

Supported and Verified MIBs 3-2

Supported, Not Verified MIBs 3-3

Not Verified or Unsupported MIBs 3-5

ATM-MIB 3-5

MIB Constraints 3-5

ATM-FORUM-ADDR-REG-MIB 3-6

ATM-FORUM-MIB 3-6

BGP4-MIB 3-6

MIB Constraints 3-6

BRIDGE-MIB 3-7

CISCO-AAA-SERVER-MIB 3-7

MIB Constraints 3-7

CISCO-AAA-SESSION-MIB 3-8

MIB Constraints 3-8

CISCO-AAL5-MIB 3-9

CISCO-ACCESS-ENVMON-MIB 3-9

CISCO-ALPS-MIB 3-9

CISCO-ASPP-MIB 3-9

CISCO-ATM-EXT-MIB 3-9

CISCO-BGP4-MIB 3-10

CISCO-BSC-MIB 3-10

CISCO-BSTUN-MIB 3-10

CISCO-BULK-FILE-MIB 3-10

CISCO-BUS-MIB 3-10

CISCO-CAR-MIB 3-10

CISCO-CASA-FA-MIB 3-10

CISCO-CASA-MIB 3-11

CISCO-CDP-MIB 3-11

CISCO-CIRCUIT-INTERFACE-MIB 3-11

CISCO-CLASS-BASED-QOS-MIB 3-11


OL-6384-04

Contents

CISCO-CONFIG-COPY-MIB 3-12

CISCO-CONFIG-MAN-MIB 3-12

CISCO-DLCSW-MIB 3-12

CISCO-DLSW-EXT-MIB 3-12

CISCO-DLSW-MIB 3-12

CISCO-DSPU-MIB 3-13

CISCO-ENTITY-ALARM-MIB 3-13

MIB Constraints 3-13

CISCO-ENTITY-ASSET-MIB 3-19


CISCO-ENTITY-EXT-MIB 3-19

CISCO-ENTITY-FRU-CONTROL-MIB 3-20

CISCO-ENTITY-SENSOR-MIB 3-21

CISCO-ENTITY-VENDORTYPE-OID-MIB 3-21


CISCO-ENVMON-MIB 3-23

CISCO-FLASH-MIB 3-24

CISCO-FRAME-RELAY-MIB 3-24

CISCO-FRAS-HOST-MIB 3-24

CISCO-FTP-CLIENT-MIB 3-24

CISCO-HSRP-EXT-MIB 3-24

CISCO-HSRP-MIB 3-24


CISCO-IETF-ATM2-PVCTRAP-MIB 3-25

CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN 3-25

CISCO-IETF-IP-FORWARD-MIB 3-25

CISCO-IETF-IP-MIB 3-26


CISCO-IMAGE-MIB 3-26

CISCO-IP-STAT-MIB 3-26

CISCO-IPMROUTE-MIB 3-26

Constraint 3-26

CISCO-ENHANCED-MEMORY-POOL-MIB 3-27

CISCO-LEC-DATA-VCC-MIB 3-27

CISCO-LEC-EXT-MIB 3-27

CISCO-LECS-MIB 3-27


OL-6384-04

Contents

CISCO-LES-MIB 3-28

CISCO-MEMORY-POOL-MIB 3-28

CISCO-NBAR-PROTOCOL-DISCOVERY-MIB-MIB 3-28

CISCO-NETFLOW-MIB 3-28

CISCO-NTP-MIB 3-29

CISCO-PAE-MIB 3-30

CISCO-PIM-MIB 3-30

CISCO-PING-MIB 3-30


CISCO-PPPOE-MIB 3-30


CISCO-PROCESS-MIB 3-31


CISCO-PRODUCTS-MIB 3-31

CISCO-QLLC01-MIB 3-32

CISCO-QUEUE-MIB 3-32

CISCO-RSRB-MIB 3-32

CISCO-RTTMON-MIB 3-32


CISCO-SDLLC-MIB 3-34

CISCO-SMI-MIB 3-34

CISCO-SNAPSHOT-MIB 3-34

CISCO-SSG-MIB 3-34


CISCO-STUN-MIB 3-35

CISCO-SYSLOG-MIB 3-36


CISCO-TC-MIB 3-36

CISCO-TCP-MIB 3-36

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB 3-36

CISCO-VPDN-MGMT-MIB 3-36


CISCO-VPDN-MGMT-EXT-MIB 3-37


DLSW-MIB 3-38

ENTITY-MIB (RFC 2737) 3-38


OL-6384-04

Contents


ENTITY-MIB UDI Support 3-45

ETHERLIKE-MIB 3-45


EVENT-MIB 3-46

MIB Constraint 3-46

EXPRESSION-MIB 3-47

MIB Constraint 3-47

HC-RMON-MIB 3-47

IEEE8021-PAE-MIB 3-47

IEEE8023-LAG-MIB 3-47

IF-MIB 3-48


IGMP-MIB 3-49

INT-SERV-GUARANTEED-MIB 3-49

INT-SERV-MIB 3-49

IPMROUTE-MIB 3-49

LAN-EMULATION-CLIENT-MIB 3-50

MPLS-LDP-MIB 3-50


MPLS-LSR-MIB 3-52


MPLS-TE-MIB 3-55


MPLS-VPN-MIB 3-57


MSDP-MIB 3-59

NOTIFICATION-LOG-MIB (RFC 3014) 3-59

NOVELL-IPX-MIB 3-60

NOVELL-RIPSAP-MIB 3-60

OLD-CISCO-APPLETALK-MIB 3-60

OLD-CISCO-CHASSIS-MIB 3-60


OLD-CISCO-CPU-MIB 3-61

OLD-CISCO-DECNET-MIB 3-61

OLD-CISCO-INTERFACES-MIB 3-61

OLD-CISCO-IP-MIB 3-61


OL-6384-04

Contents


OLD-CISCO-MEMORY-MIB 3-62

OLD-CISCO-NOVELL-MIB 3-62

OLD-CISCO-SYSTEM-MIB 3-62

OLD-CISCO-TCP-MIB 3-62

OLD-CISCO-TS-MIB 3-62

PIM-MIB 3-63


RFC1213-MIB 3-63

RFC1243-MIB 3-63


RFC1253-MIB 3-64

RFC1315-MIB 3-64


RFC1315-MIB 3-65


RFC1381-MIB 3-66

RFC1382-MIB 3-66

DS1-MIB (RFC2495) 3-66

DS3-MIB (RFC2496) 3-66

RFC2006-MIB 3-66

RMON-MIB 3-67


RMON2-MIB 3-68

RS-232-MIB 3-68

RSVP-MIB 3-68


SMON-MIB 3-68

SNA-SDLC-MIB 3-68

SNMP-FRAMEWORK-MIB 3-69

SNMP-NOTIFICATION-MIB 3-69

SNMP-PROXY-MIB 3-69

SNMP-TARGET-MIB 3-69

SNMP-USM-MIB 3-69

SNMP-VACM-MIB 3-70



OL-6384-04

Contents

SNMPv2-MIB 3-70

SONET-MIB 3-71


SOURCE-ROUTING-MIB 3-71

TCP-MIB 3-71

UDP-MIB 3-71

C H A P T E R 4 Monitoring Notifications 4-1

Notification Overview 4-1

Enabling Notifications 4-2

Cisco SNMP Notifications 4-3

Environmental or Functional Notifications 4-3

Cisco 7200 Port Adapter Notifications 4-5

Interface Notifications 4-6

Threshold Notifications 4-7

Service Notifications 4-8

Routing Protocol Notifications 4-9

RTT Monitor Notifications 4-10

Environmental Notifications 4-11

A P P E N D I X A Using MIBs A-1

Managing Router Physical Entities A-1

Mapping Information for ENTITY-MIB A-2

Physical Entity Management MIBs A-2

Mapping OLD-CISCO-CHASSIS-MIB to ENTITY-MIB A-3

Entity Containment Tree A-3

Performing Inventory Management A-5

Notes about entPhysicalTable Entries A-5

Samples of ENTITY-MIB entPhysicalTable Entries A-6

Monitoring and Configuring FRU Status A-10

Generating SNMP Traps A-10

Identifying Hosts to Receive Traps A-10

Configuration Changes A-11

Environmental Conditions A-11

FRU Status Changes A-12

Monitoring Router Interfaces A-12

Enabling Interface LinkUp/LinkDown Traps A-12

SNMP Trap Filtering for linkDown Traps A-13


OL-6384-04

Contents

Monitoring Quality of Service A-13

Configuring QoS A-14

Accessing QoS Configuration Information and Statistics A-14

QoS Indexes A-14

Sample QoS Configuration Settings A-15

Monitoring QoS A-18

Considerations for Processing QoS Statistics A-18

Sample QoS Statistics A-18

Sample QoS Applications A-20

Checking Customer Interfaces for Service Policies A-20

Retrieving QoS Billing Information A-21

Billing Customers for Traffic A-22

Input and Output Interface Counts A-23

Determining the Amount of Traffic to Bill to a Customer A-23

Scenario for Demonstrating QoS Traffic Policing A-23

Service Policy Configuration A-24

Packet Counts Before the Service Policy Is Applied A-24

Generating Traffic A-24

Packet Counts After the Service Policy Is Applied A-25

How to Collect CPU Utilization on Cisco IOS Devices Using SNMP A-26

Using CISCO-AAA-SESSION-MIB A-27

G L O S S A R Y

I N D E X


OL-6384-04

About This Guide

This guide describes the implementation of the Simple Network Management Protocol (SNMP) in Cisco IOS Release Release 12.4(11)T, Release 12.4(4)XD7, and Release 12.2(31)SB5, applicable to the Cisco 7200 series routers and Cisco 7201 router. SNMP provides a set of commands for setting and retrieving the values of operating parameters on the Cisco 7200 series routers. Router information is stored in a virtual storage area called a Management Information Base (MIB), which contains many MIB objects that describe router components and provides information about the status of the components.

This Preface provides an overview of this guide with the following sections:

• Guide Revision History, page ix

• Audience, page xii

• Organization, page xiii

• Obtaining Documentation, page xv

• Documentation Feedback, page xv

• Obtaining Technical Assistance, page xvi

• Obtaining Additional Publications and Information, page xvii

Guide Revision HistoryThe following Guide Revision History tables record technical changes, additions, and corrections to this document. The table shows the release number and document revision number for the change, the date of the change, and a brief summary of the change.

Description of Changes in Cisco IOS Release 12.4(4)XD7 and Release 12.2(31)SB5

This edition of the document adds information for MIBs supported on the Cisco 7201 router, and related new traps and MIB restrictions. This document also adds information for supported port adapters associated with the Cisco 7201 router.

The following is a list of MIBs supported for the Cisco 7201 router in this release:

• CISCO-ENTITY-MIB—(is this MIB cited as a class of ENTITY MIBs, or is this distinct from others that cite ENTITY?)

Cisco IOS Release Part Number Publication Date

12.4(4)XD7 and 12.2(31)SB5 OL-6384-04 April 2007

ixCisco 7200 Router MIB Specifications Guide

OL-6384-04

http://www.cisco.com/en/US/products/hw/routers/ps341/products_mib_quick_reference_chapter09186a00803d6197.html

About This GuideGuide Revision History

• CISCO-VENDORTYPE-MIB—Added the OID

• Port adapters—These Cisco IOS releases support several port adapters on the Cisco 7201 router. Refer to Port Adapter (PA) roadmaps cited in multiple locations of this document.

The following MIBs are compliant with and supported on the Cisco 7201 router:

• AppleTalk (RFC1243)

• BGP4-MIB (RFC1657)

• CISCO-ACCESS-ENVMON-MIB

• CISCO-ATM-EXT-MIB

• CISCO-BULK-FILE-MIB

• CISCO-CDP-MIB

• CISCO-CLASS-BASED-QOS-MIB

• CISCO-CONFIG-COPY-MIB

• CISCO-CONFIG-MAN-MIB

• CISCO-ENHANCED-MEMPOOL-MIB

• CISCO-ENTITY-ALARM-MIB

• CISCO-ENTITY-ASSET-MIB

• CISCO-ENTITY-FRU-CONTROL-MIB

• CISCO-ENTITY-SENSOR-MIB

• CISCO-ENTITY-EXT-MIB

• CISCO-ENVMON-MIB

• CISCO-FLASH-MIB

• CISCO-FTP-CLIENT-MIB

• CISCO-HSRP-EXT-MIB

• CISCO-IMAGE-MIB

• CISCO-MEMORY-POOL-MIB

• CISCO-PROCESS-MIB

• CISCO-PRODUCTS-MIB

• CISCO-QUEUE-MIB

• CISCO-RTTMON-MIB

• CISCO-SYSLOG-MIB

• ENTITY-MIB (RFC-2737)

• ETHERLIKE-MIB

• EVENT-MIB

• EXPRESSION-MIB

• IF-MIB

• NOTIFICATION-LOG-MIB

• OLD-CISCO-CHASSIS-MIB

• OLD-CISCO-CPU-MIB

xCisco 7200 Router MIB Specifications Guide

OL-6384-04

About This GuideGuide Revision History

• OLD-CISCO-INTERFACES-MIB

• OLD-CISCO-IP-MIB

• OLD-CISCO-MEMORY-MIB

• OSPF MIB (RFC1253)

• RMON-MIB (RFC 1757)

• RSVP-MIB

• SNMP-NOTIFICATION-MIB

• SNMP-FRAMEWORK-MIB

• SNMP-USM-MIB (RFC 2574)

• SNMP-VACM-MIB (RFC 2575)

• SNMP-TARGET-MIB

• SNMPv2-MIB (RFC 1907)

• TCP-MIB (RFC 2012)

• UDP-MIB (RFC 2013)

Description of Changes in Cisco IOS Release 12.4(11)T

• Updated the following MIBs:

– CISCO-PROCESS-MIB—Second CPU statistics support added. These entries for the second CPU objects help enhance customer's monitoring capabilities.

– IF-MIB—Improved inventory management and monitoring capabilities

• Added information about CPU Utilization. See How to Collect CPU Utilization on Cisco IOS Devices Using SNMP, page 26

• Added the CISCO-NETFLOW-MIB which includes SNMP access to information available in the NetFlow Cache. This is not a replacement for the traditional NetFlow export mechanism, but a method to take a snapshot of the cache register and make it available via SNMP. This functionality is useful for security verification, discovering use of network resources, and identifying top individual contributors to network utilization.

• Added support for the PA-MC-2T3-EC and PA-MC-T3-EC enhanced T3 Multichannel Port Adapters and the PA-T/E3E-EC and PA-2T/E3-EC Clear Channel T3/E3 Port Adapters.

• Updated Cisco7200 platform support for unique device identifier (UDI) compliance. Added support for the unique device identifier (UDI) standard which displays information from any Cisco product that has electronically stored identity information. See ENTITY-MIB UDI Support, page 45.

• Interface mapping improvements—Improved existing CISCO-AAA-SESSION-MIB to map sessions to underlying interfaces. See Using CISCO-AAA-SESSION-MIB, page 27.


12.4(11)T OL-6384-03 January 2007

xiCisco 7200 Router MIB Specifications Guide

OL-6384-04

About This GuideAudience

Description of Changes in Cisco IOS Release 12.2SB

• Added manageability improvements on the Cisco 7200 series router platform port adapters:

– Cisco 7200 NPE-G1, NPE-400, NPE-225

– Port adapters—Refer to additional Port Adapter (PA) documentation roadmaps in this document for additional information.

• Updated the following MIBs for improved inventory management and monitoring capabilities:

– CISCO-ENTITY-VENDORTYPE-OID-MIB

– ENTITY-MIB (RFC 2737)

– CISCO-ENTITY-EXT-MIB

– CISCO-ENTITY-ASSET-MIB

– CISCO-ENTITY-FRU-CONTROL-MIB

– CISCO-ENTITY-SENSOR-MIB

– CISCO-ENTITY-ALARM-MIB

– NOTIFICATION-LOG-MIB (RFC 3014)

– CISCO-FLASH-MIB

– CISCO-ENVMON-MIB

• Added Cisco 7200 series additional port adapter support. For a list of all port adapters supported on the Cisco 7200 series routers.

• Support for DS1 and DS3 MIBs is implemented as defined by RFC2495 and RFC2496, respectively. For detailed information, see DS1-MIB (RFC2495), page 66 and DS3-MIB (RFC2496), page 66.

• Added mapping information regarding the ENTITY-MIB and the CISCO-OLD-CHASSIS-MIB.

Description of Changes in Cisco IOS Release 12.3(14)T

• Cisco 7200 series additional port adapter support. Refer to additional Port Adapter (PA) documentation roadmaps in this document for additional information.

• Support for DS1 and DS3 MIBs is impl mented as defined by RFC2495 and RFC2496, respectively. For detailed information, see “DS1-MIB (RFC2495)” section on page 66 and “DS3-MIB (RFC2496)” section on page 66.

AudienceThis guide is intended for system and network administrators who must configure the Cisco 7200 router for operation and monitor its performance in the network.


12.2SB REL3 OL-6384-02 February 2006


12.3(14)T OL-6384-01 February 2005

xiiCisco 7200 Router MIB Specifications Guide

OL-6384-04

About This GuideOrganization

This guide may also be useful for application developers who are developing management applications for the Cisco 7200 router.

OrganizationThis guide contains the following chapters:

• Chapter 1, “Cisco 7200 Router MIB Overview,” provides background information about SNMP and its implementation on the Cisco 7200 router and a feature history table describing new features implemented since the last Cisco software release.

• Chapter 2, “Configuring MIB Support,” provides instructions for configuring SNMP management support on the Cisco 7200 router.

• Chapter 3, “MIB Specifications,” describes each MIB included on the Cisco 7200 router. Each description lists any constraints as to how the MIB is implemented on the router.

• Chapter 4, “Monitoring Notifications,” describes the SNMP notifications (traps and informs) supported by the Cisco 7200 router.

• Appendix A, “Using MIBs” provides information about how MIBs are used.

• Glossary

• Index

xiiiCisco 7200 Router MIB Specifications Guide

OL-6384-04



About This GuideTerminology and Definitions

Terminology and DefinitionsThis section discusses conventions and terminology used in this guide.

• Alarm—In SNMP, the word alarm is commonly misused to mean the same as a Trap (see Trap definition). Alarm represents a condition which causes a trap to be generated.

Note Many commands use the word traps in the command syntax. Unless there is an option in the command to select either traps or informs, the keyword traps refers to either traps, informs, or both. Use the command, snmp-server enable <notification>, where notification is either trap or inform, to specify whether to send SNMP notifications as traps or informs.

• Element Management System (EMS)—An EMS manages a specific portion of the network. For example, the SunNet Manager, an SNMP management application, is used to manage SNMP manageable elements. Element Managers may manage asynchronous lines, multiplexers, PABX, proprietary systems, or an application.

• Informs—Reliable SNMP notifications which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.

• Management Information Base (MIB)—The objects that are available in an SNMP managed device. The information is represented in Abstract Syntax Notation 1 (ASN.1). It is a way of logically grouping data so that it is easily understood by all.

• MIB-II—The enhancements to MIB-I which was the original standard SNMP MIB.

• Multiprotocol Label Switching (MPLS)—MPLS is the standardized version of the Cisco original tag-switching proposal. It uses a label forwarding paradigm (forward packets based on labels).

• Remote Network Monitoring (RMON) MIB—SNMP MIB for remote management of networks. While other MIBs are usually created to support a network device whose primary function is other than management, RMON was created to provide management of a network. RMON is one of the many SNMP based MIBs that are IETF Standards.

• Simple Network Management Protocol (SNMP)—An application layer protocol that allows you to remotely manage networked devices. The word "simple" in SNMP is only in contrast to protocols which are thought to be even more complex than SNMP. SNMP consists of the following components: a management protocol, a definition of management information and events, a core set of management information and events, and a mechanism and approach used to manage the use of the protocol including security and access control.

• Synchronous Optical Network (SONET)—A physical layer interface standard for fiber optic transmission.

• Trap—SNMP trap is an unsolicited (device initiated) message. The contents of the message might be simply informational, but it is mostly used to report real-time trap information. Traps are used in conjunction with other SNMP mechanisms, as in trap-directed polling, or the SNMP inform mechanism can be used when a reliable fault reporting system is required.

• User Datagram Protocol (UDP)—A connectionless, non-reliable IP-based transport protocol.

xivCisco 7200 Router MIB Specifications Guide

OL-6384-04

About This GuideObtaining Documentation

Obtaining DocumentationCisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/en/US/docs/general/Illus_process/PDI/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation FeedbackYou can send comments about technical documentation to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883

We appreciate your comments.

xvCisco 7200 Router MIB Specifications Guide

OL-6384-04

http://www.cisco.com/univercd/home/home.htm


http://www.cisco.com/public/countries_languages.shtml

http://www.cisco.com/en/US/docs/general/Illus_process/PDI/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml

About This GuideObtaining Technical Assistance

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support WebsiteThe Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service RequestUsing the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

xviCisco 7200 Router MIB Specifications Guide

OL-6384-04

http://www.cisco.com/techsupport

http://tools.cisco.com/RPF/register/register.do

http://www.cisco.com/techsupport/servicerequest

http://www.cisco.com/techsupport/contacts

About This GuideObtaining Additional Publications and Information

Definitions of Service Request SeverityTo ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is “down,” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/index.html

• Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

• World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

xviiCisco 7200 Router MIB Specifications Guide

OL-6384-04

http://www.cisco.com/en/US/products/index.html

http://www.cisco.com/go/marketplace/

http://www.ciscopress.com

http://www.cisco.com/packet

http://www.cisco.com/ipj

http://www.cisco.com/en/US/learning/index.html

About This GuideObtaining Additional Publications and Information

xviiiCisco 7200 Router MIB Specifications Guide

OL-6384-04

OL-6384-04

C H A P T E R 1
Cisco 7200 Router MIB Overview
This chapter provides an overview of the Cisco 7200 series routers enhanced management feature for the Cisco 7204VXR, the Cisco 7206VXR, and the Cisco 7201 routers. The Cisco 7200 series routers support multiprotocol, multimedia routing and bridging over a wide variety of LAN and WAN interface types.

This chapter includes the following sections:

• Benefits of MIB Enhancements, page 1-1

• SNMP Overview, page 1-2

• Object Identifiers, page 1-6

• Related Information and Useful Links, page 1-6

Benefits of MIB EnhancementsThe Cisco 7200 series routers are high-performance Enterprise Edge LAN/WAN integration and service provider aggregation routers. The enhanced management feature of the Cisco 7200 series router and the Cisco 7201 router improves management capabilities. The feature improves core network management areas such as inventory, asset and fault management, and expands the number of Management Information Bases (MIBs) included with the router. See the “SNMP Overview” section on page 1-2 for more information about SNMP and MIBs.

Furthermore, the Cisco 7201 router provides application-specific features for broadband subscriber aggregation and network application services with high processing performance.

Using the enhanced management feature, you can:

• Manage and monitor Cisco 7200 series resources through an SNMP-based network management system (NMS).

• Use SNMP set and get commands to access information in Cisco 7200 series router MIBs..

• Reduce the amount of time and system resources required to perform functions such as inventory management and bulk data transfers.

Other benefits include:

• A standards-based technology (SNMP) for monitoring faults and performance on the router

• Support for all SNMP versions (SNMPv1, SNMPv2c, and SNMPv3)

• Notification of faults, alarms, and conditions that might affect services

• The ability to aggregate fault and alarm information for multiple entities

1-1Cisco 7200 Router MIB Specifications Guide

Chapter 1 Cisco 7200 Router MIB OverviewSNMP Overview

• A way to access router information other than through the command line interface (CLI)

• For a complete list of supported port adapters (PA) supported for the Cisco 7200 Series and the Cisco 7201 router, refer to the following documents 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

– Cisco 7201 Router Port Adapter Documentation Roadmap

http://www.cisco.com/en/US/docs/routers/7200/roadmaps/7201_port_adaper_doc_roadmap/11366pr.html

SNMP OverviewThe Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a standardized framework and a common language used for monitoring and managing devices in a network.

The SNMP framework has three parts:

• SNMP manager—A system used to control and monitor the activities of network hosts using SNMP. The most common managing system is called a Network Management System (NMS). The term NMS can be applied to either a dedicated device used for network management, or the applications used on a network-management device. A variety of network management applications are available for use with SNMP. These features range from simple command-line applications to feature-rich graphical user interfaces (such as the CiscoWorks2000 line of products).

• SNMP agent—A software component in a managed device that maintains the data for the device and reports the data, as needed, to managing systems. The agent and MIB reside on the routing device (router, access server, or switch). To enable the SNMP agent on a managed device, you must define the relationship between the manager and the agent (see the “Enabling SNMP Support” section on page 2-4).

• Management Information Base (MIB)—Collection of network-management information, organized in hierarchical manner.

Instead of defining a large set of commands, SNMP places all operations in a get-request, get-next-request, and set-request format. For example, an SNMP manager can get a value from an SNMP agent or set a value in that SNMP agent.

MIB DescriptionA Management Information Base (MIB) is a collection of network-management information, organized in hierarchical fashion. The MIB consists of collections of managed objects identified by object identifiers. MIBs are accessed using a network-management protocol such as SNMP. A managed object (sometimes called a MIB object or an object) is one of a number of characteristics of a managed device, such as a router. Managed objects comprise one or more object instances, which are essentially variables. The Cisco implementation of SNMP uses the definitions of MIB II variables described in RFC 1213.

MIBs can contain two types of managed objects:

• Scalar objects—Define a single object instance (for example, ifNumber in the IF-MIB and bgpVersion in the BGP4-MIB).


OL-6384-04




• Columnar objects—Defines a MIB table that contains no rows or more than one row, and each row can contain one or more scalar objects, (for example, ifTable in the IF-MIB defines the interface).

System MIB variables are accessible through SNMP as follows:

• Accessing a MIB variable—Function is initiated by the SNMP agent in response to a request from the NMS. The agent retrieves the value of the requested MIB variable and responds to the NMS with that value.

• Setting a MIB variable—Function is initiated by the SNMP agent in response to a message from the NMS. The SNMP agent changes the value of the MIB variable to the value requested by the NMS.

SNMP NotificationsAn SNMP agent can notify the manager when important system events occur, such as the following:

• An interface or card starts or stops running

• Temperature thresholds are crossed

• Authentication failures occur

When an agent detects an alarm condition, the agent:

• Logs information about the time, type, and severity of the condition

• Generates a notification message, which it then sends to a designated IP host

SNMP notifications are sent as either:

• Traps—Unreliable messages, which do not require receipt acknowledgment from the SNMP manager.

• Informs—Reliable messages, which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.

Note Many commands use the word traps in the command syntax. Unless there is an option in the command to select either traps or informs, the keyword traps refers to either traps, informs, or both. Use the snmp-server host command to specify whether to send SNMP notifications as traps or informs.

When an agent detects an alarm condition, it logs information about the time, type, and severity of the condition and generates a notification message, which it then sends to a designated IP host. SNMP notifications can be sent as either traps or informs. See the “Enabling SNMP Support” section on page 2-4 for instructions on how to enable traps on the Cisco 7200 series router. See Chapter 4, “Monitoring Notifications,” for information about Cisco 7200 series router traps.

The Cisco implementation of SNMP uses the definitions of SNMP traps described in RFC 1215.

SNMP VersionsCisco IOS software supports the following versions of SNMP:

• SNMPv1—The Simple Network Management Protocol: An Internet standard, defined in RFC 1157. Security is based on community strings.


OL-6384-04


• SNMPv2c—The community-string based administrative framework for SNMPv2. SNMPv2c is an update of the protocol operations and data types of SNMPv2p (SNMPv2 classic), and uses the community-based security model of SNMPv1.

• SNMPv3—Version 3 of SNMP. SNMPv3 uses the following security features to provide secure access to devices:

– Message integrity—Ensuring that a packet has not been tampered with in transit.

– Authentication—Determining that the message is from a valid source.

– Encryption—Scrambling the contents of a packet to prevent it from being learned by an unauthorized source.

SNMPv1 and SNMPv2c

Both SNMPv1 and SNMPv2c use a community-based form of security. The community of managers who are able to access the agent MIB is defined by an IP address Access Control List and password.

SNMPv2c support includes a bulk-retrieval mechanism and more detailed error message reporting to management stations. The bulk-retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trip transmissions required. SNMPv2c improved error handling support includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes now report the error type. Three kinds of exceptions are also reported:

• no such object exceptions

• no such instance exceptions

• end of MIB view exceptions

SNMPv3

SNMPv3 provides the following security models and security levels:

• Security model—Authentication strategy that is set up for a user and the group in which the user resides.

• Security level—Permitted level of security within a security model.

A combination of a security model and a security level determines the security mechanism to be employed when handling an SNMP packet.

SNMP Security Models and Levels

Table 1-1 describes the security models and levels provided by the different SNMP versions.

Table 1-1 SNMP Security Models and Levels

Model Level Authentication Encryption Description

v1 noAuthNoPriv Community string

No Uses match on community string for authentication.

v2c noAuthNoPriv Community string

No Uses match on community string for authentication.


OL-6384-04


You must configure the SNMP agent to use the version of SNMP supported by the management station. An agent can communicate with multiple managers; for this reason, you can configure the Cisco IOS software to support communications with one management station using the SNMPv1 protocol, one using the SNMPv2c protocol, and another using SMNPv3.

Requests for CommentsMIB modules are written in the SNMP MIB module language, and are typically defined in Request For Comments (RFC) documents submitted to the Internet Engineering Task Force (IETF). RFCs are written by individuals or groups for consideration by the Internet Society and the Internet community as a whole. Before being given RFC status, recommendations are published as Internet Draft (I-D) documents. RFCs that have become recommended standards are also labeled as standards (STD) documents. For more information, see the Internet Society and IETF websites (http://www.isoc.org and http://www.ietf.org).

We provide private MIB extensions with each Cisco system. Cisco enterprise MIBs comply with the guidelines described in the relevant RFCs unless otherwise noted in the documentation.

v3 noAuthNoPriv User name No Uses match on user name for authentication.

v3 authNoPriv MD5 or SHA No Provides authentication based on HMAC-MD5 or HMAC-SHA algorithm.

v3 authPriv MD5 or SHA DES Provides authentication based on HMAC-MD5 or HMAC-SHA algorithm. Also provides DES 56-bit encryption based on CBC-DES (DES-56) standard.

Table 1-1 SNMP Security Models and Levels (continued)

Model Level Authentication Encryption Description


OL-6384-04

http://www.isoc.org

http://www.isoc.org

http://www.ietf.org

Chapter 1 Cisco 7200 Router MIB OverviewObject Identifiers

Object IdentifiersAn object identifier (OID) uniquely identifies a MIB object on a managed network device. The OID identifies the MIB object’s location in the MIB hierarchy, and provides a means of accessing the MIB object in a network of managed devices:

• Standard RFC MIB OIDs are assigned by the Internet Assigned Numbers Authority (IANA)

• Enterprise MIB OIDs are assigned by Cisco Assigned Numbers Authority (CANA).

Each number in the OID corresponds to a level of MIB hierarchy. For example, the OID 1.3.6.1.4.1.9.9.xyz represents the xyz-MIB whose location in the MIB hierarchy is as follows. Note that the numbers in parentheses are included only to help show correspondence to the MIB hierarchy. In actual use, OIDs are represented as numerical values only.

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).ciscoMgt(9).nn-MIB

You can uniquely identify a managed object, such as ifNumber in the IF-MIB, by its object name (iso.org.dod.internet.mgmt.mib-2.interfaces.ifNumber) or by its OID (1.3.6.1.2.1.2.1).

For a list of OIDs assigned to MIB objects, go to the following URL:

ftp://ftp.cisco.com/pub/mibs/oid/

Related Information and Useful LinksThe following URL provides access to general information about Cisco MIBs. Use the links on this page to access MIBs for download, and to access related information (such as application notes and OID listings).

• http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

TAC Information and FAQsThe following URLs provide access to SNMP information developed by the Cisco Technical Assistance Center (TAC):

• http://www.cisco.com/en/US/tech/tk648/tk362/tk605/tsd_technology_support_sub-protocol_home.html is the Cisco TAC page for SNMP. It provides links to general SNMP information and tips for using SNMP to gather data.

• http://www.cisco.com/en/US/customer/tech/tk648/tk362/technologies_q_and_a_item09186a0080094bc0.shtml is a list of frequently asked questions (FAQs) about Cisco MIBs.

SNMP Configuration InformationThe following URLs provide information about configuring SNMP:

• http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/12_2sx/cf_12_2sx_book.html provides general information about configuring SNMP support. It is part of the Cisco IOS Configuration Fundamentals Configuration Guide.

• http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/ffun_r.html provides information about SNMP commands. It is part of the Cisco IOS Configuration Fundamentals Command Reference.


OL-6384-04

ftp://ftp.cisco.com/pub/mibs/oid/

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

http://www.cisco.com/en/US/tech/tk648/tk362/tk605/tsd_technology_support_sub-protocol_home.html


http://www.cisco.com/en/US/customer/tech/tk648/tk362/technologies_q_and_a_item09186a0080094bc0.shtml

http://www.cisco.com/en/US/customer/tech/tk648/tk362/technologies_q_and_a_item09186a0080094bc0.shtml

http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/12_2sx/cf_12_2sx_book.html

http://www.cisco.com/en/US/docs/ios/fundamentals/configuration/guide/12_2sx/cf_12_2sx_book.html

http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/ffun_r.html

OL-6384-04

C H A P T E R 2
Configuring MIB Support
This chapter describes how to configure SNMP and MIB support for the Cisco 7200 router and the Cisco 7201 router. It includes the following sections:

• Determining MIBs Included for Cisco IOS Releases, page 2-1

• Downloading and Compiling MIBs, page 2-2

• Enabling SNMP Support, page 2-4

Determining MIBs Included for Cisco IOS ReleasesFollow these steps to determine which MIBs are included in the Cisco IOS release running on the Cisco 7200 router and the Cisco 7201 router:

Step 1 Go to the Feature Navigator home page http://tools.cisco.com/ITDIT/MIBS/servlet/index.

Step 2 Click MIB Locator to launch the application. The MIB Locator application allows you to find a MIB in the following three ways:

a. From the MIB Locator page, you can:

• Click the drop-down menu and select the desired Cisco IOS software release.

• From the Platform Family menu, select 7200 or 7201. If you select the platform first, the system displays only those releases and feature sets that apply to the Cisco 7200 router or the Cisco 7201 router.

• From the Feature Set menu, select Service Provider.

b. From the MIB Locator page, you can search by image name. For example, enter the following input and click the Submit button:

c7200-js56i-mz.12.0-1

c. From the MIB Locator page, you can search for the MIB from the list of MIBs in the menu. You can select one, or for a multiple selection, hold down the CTRL key, then click the Submit button.

Note After you make a selection, follow the links and instructions.


http://tools.cisco.com/ITDIT/MIBS/servlet/index

Chapter 2 Configuring MIB SupportDownloading and Compiling MIBs

Downloading and Compiling MIBsThe following sections provide information about how to download and compile MIBs for the Cisco 7200 router:

• Considerations for Working with MIBs

• Downloading MIBs

• Compiling MIBs

Considerations for Working with MIBsWhile working with MIBs, consider the following:

Mismatches on Datatype Definitions

• Mismatches on datatype definitions might cause compiler errors or warning messages. Although Cisco MIB datatype definitions are not mismatched, standard RFC MIBs do mismatch. For example:

MIB A defines: SomeDatatype ::= INTEGER(0..100) MIB B defines: SomeDatatype ::= INTEGER(1..50)

This example is considered to be a trivial error and the MIB loads successfully with a warning message.

The next example is considered a nontrivial error (even though the two definitions are essentially equivalent), and the MIB is not successfully parsed.

MIB A defines: SomeDatatype ::= DisplayString MIB B defines: SomeDatatype ::= OCTET STRING (SIZE(0..255))

If your MIB compiler treats these as errors, or you want to delete the warning messages, edit one of the MIBs that define this same datatype so that the definitions match.

• Many MIBs import definitions from other MIBs. If your management application requires MIBs to be loaded, and you experience problems with undefined objects, you might want to load the following MIBs in this order:

SNMPv2-SMI.my SNMPv2-TC.my SNMPv2-MIB.my RFC1213-MIB.my IF-MIB.my CISCO-SMI.my CISCO-PRODUCTS-MIB.my CISCO-TC.my

• For additional information and SNMP technical tips, from the Locator page, click SNMP MIB Technical Tips and follow the links or go to the following URL:


• For a list of SNMP object identifiers (OIDs) assigned to MIB objects, go to the following URL and click on SNMP Object Navigator and follow the links:



OL-6384-04



Chapter 2 Configuring MIB SupportDownloading and Compiling MIBs

Note You must have a Cisco CCO name and password to access the MIB Locator.

• For information about how to download and compile Cisco MIBs, go to the following URL:

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00800b4cee.shtml

Downloading MIBsFollow these steps to download the MIBs onto your system if they are not already there:

Step 1 Review the considerations in the previous section (“Considerations for Working with MIBs”).

Step 2 Go to one of the following Cisco URLs. If the MIB you want to download is not there, try the other URL; otherwise, go to one of the URLs in Step 5.

ftp://ftp.cisco.com/pub/mibs/v2 ftp://ftp.cisco.com/pub/mibs/v1

Step 3 Click the link for a MIB to download that MIB to your system.

Step 4 Select File > Save or File > Save As to save the MIB on your system.

Step 5 You can download industry-standard MIBs from the following URLs:

• http://www.ietf.org

• http://www.atmforum.com

Compiling MIBsIf you plan to integrate the Cisco 7200 router or the Cisco 7201 router with an SNMP-based management application, then you must also compile the MIBs for that platform. For example, if you are running HP OpenView on a UNIX operating system, you must compile Cisco 7200 router MIBs with the HP OpenView Network Management System (NMS). For instructions, see the NMS documentation.


OL-6384-04

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00800b4cee.shtml

http://www.ietf.org

ftp://ftp.cisco.com/pub/mibs/v2

ftp://ftp.cisco.com/pub/mibs/v1

http://www.atmforum.com

Chapter 2 Configuring MIB SupportEnabling SNMP Support

Enabling SNMP SupportThe following procedure summarizes how to configure the Cisco 7200 router or the Cisco 7201 router for SNMP support.

For detailed information about SNMP commands, see the following Cisco documents:

• Cisco IOS Release 12.2 Configuration Fundamentals Configuration Guide, “Monitoring the Router and Network” section, available at the following URL:

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html

• Cisco IOS Release 12.2 Configuration Fundamentals Command Reference, Part 3: System Management Commands, “Router and Network Configuration Commands” section, available at the the following URL:

http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/frf012.html

To configure the Cisco 7200 router or the Cisco 7201 router for SNMP support, follow these steps:

Step 1 Set up your basic SNMP configuration through the command line interface (CLI) on the router. Note that these basic configuration commands are issued for SNMPv2c. For SNMPv3, you must also set up SNMP users and groups. (See the preceding list of documents for command and setup information.)

a. Define SNMP read-only and read-write communities:

Router (config)# snmp-server community Read_Only_Community_Name roRouter (config)# snmp-server community Read_Write_Community_Name rw

b. Configure SNMP views (to limit the range of objects accessible to different SNMP user groups):

Router (config)# snmp-server view view_name oid-tree {included | excluded}

Step 2 Identify (by IP address) the host to receive SNMP traps from the router:

Router (config)# snmp-server host host

Step 3 Configure the router to generate traps. You can use keywords to limit the number and types of messages generated.

Router (config)# snmp-server enable traps [notification-type] [notification-option]

Step 4 Optional. Configure the router to generate SNMP traps released to Field Replaceable Units (FRUs):

Router (config)# snmp-server enable traps fru-ctrl

Step 5 Optional. Configure the router to generate SNMP traps related to environmental monitoring:

Router (config)# snmp-server enable traps envmon


OL-6384-04

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html

http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/frf012.html

OL-6384-04

C H A P T E R 3
MIB Specifications
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


The Cisco 7201 router supports the port adapters listed in the following document on Cisco.com:

• Cisco 7201 Router Port Adapter Documentation Roadmap


Cisco 7200 MIBsThe 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.




Chapter 3 MIB SpecificationsCisco 7200 MIBs

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.

Supported and Verified MIBsTable 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-1 Supported and Verified Cisco 7200 MIBs

ATM-MIB (RFC 1695) CISCO-SYSLOG-MIB

BGP4-MIB (RFC 1657) CISCO-TC

CISCO-AAA-SERVER-MIB CISCO-TCP-MIB

CISCO-AAL5-MIB CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB

CISCO-ACCESS-ENVON-MIB CISCO-VPDN-MGMT-MIB

CISCO-ATM-EXT-MIB CISCO-VPDN-MGMT-EXT-MIB

CISCO-BULK-FILE-MIB ENTITY-MIB (RFC 2737)

CISCO-CDP-MIB ETHERLIKE-MIB (RFC 2665)

CISCO-CLASS-BASED-QOS-MIB EVENT-MIB (RFC 2981)

CISCO-CONFIG-COPY-MIB EXPRESSION-MIB

CISCO-CONFIG-MAN-MIB IF-MIB (RFC 2233)

CISCO-ENTITY-ALARM-MIB IP-LOCALPOOL-MIB

CISCO-ENTITY-ASSET-MIB MPLS-LDP-MIB

CISCO-ENTITY-EXT-MIB MPLS-LSR-MIB

CISCO-ENTITY-FRU-CONTROL-MIB MPLS-TE-MIB

CISCO-ENTITY-PFE -MIB MPLS-VPN-MIB

CISCO-ENTITY-SENSOR-MIB NOTIFICATION-LOG-MIB (RFC3014)

CISCO-ENTITY-VENDORTYPE-OID-MIB OLD-CISCO-CHASSIS-MIB

CISCO-ENVMON-MIB OLD-CISCO-CPU-MIB

CISCO-FLASH-MIB OLD-CISCO-INTERFACES-MIB

CISCO-FRAME-RELAY-MIB OLD-CISCO-IP-MIB

CISCO-FTP-CLIENT-MIB OLD-CISCO-MEMORY-MIB

CISCO-HSRP-EXT-MIB PIM-MIB (RFC 2934)

CISCO-HSRP-MIB RFC1213-MIB (MIB II)

CISCO-IETF-IP-MIB RFC1243-MIB (AppleTalk)

CISCO-IMAGE-MIB RFC1253-MIB (OSPF)

CISCO-IPMROUTE-MIB RFC1315-MIB (FRAME RELAY MIB)

CISCO-IP-STAT-MIB RFC2495-MIB (DS1)


OL-6384-04


Supported, Not Verified MIBsTable 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.

CISCO-MEMORY-POOL-MIB RFC2496-MIB (DS3)

CISCO-NBAR-PROTOCOL-DISCOVERY-MIB RMON-MIB (RFC 1757)

CISCO-PING-MIB SNMP-FRAMEWORK-MIB (RFC 2571)

CISCO-PPPOE-MIB SNMPv2-MIB (RFC 1907)

CISCO-PROCESS-MIB SNMP-NOTIFICATION-MIB (RFC 2573)

CISCO-PRODUCTS-MIB SNMP-TARGET-MIB (RFC 2573)

CISCO-QUEUE-MIB SNMP-USM-MIB (RFC 2574)

CISCO-RTTMON-MIB SNMP-VACM-MIB (RFC 2575)

CISCO-SMI SONET MIB

CISCO-SSG-MIB TCP-MIB (RFC 2012)

CISCO-NETFLOW-MIB UDP-MIB (RFC 2013)

CISCO-AAA-SESSION-MIB ---

Table 3-1 Supported and Verified Cisco 7200 MIBs (continued)

Table 3-2 Cisco 7200 Router MIBs—Support Not Verified in the c7200 Image

ATM-FORUM-ADDR-REG-MIB CISCO-SNAPSHOT-MIB

ATM-FORUM-MIB CISCO-STUN-MIB

BRIDGE-MIB (RFC 1493) DLSW-MIB

CISCO-ALPS-MIB HC-RMON-MIB

CISCO-ASPP-MIB SOURCE-ROUTING-MIB

CISCO-BGP4-MIB IGMP-MIB

CISCO-BSC-MIB INT-SERV-GUARANTEED-MIB

CISCO-BSTUN-MIB INT-SERV-MIB

CISCO-BUS-MIB LAN-EMULATION-CLIENT-MIB

CISCO-CAR-MIB CISCO-SNADLC-CONV01-MIB

CISCO-CASA-FA-MIB MSDP-MIB

CISCO-CASA-MIB NOVELL-IPX-MIB

CISCO-CIRCUIT-INTERFACE-MIB NOVELL-RIPSAP-MIB

CISCO-DLCSW-MIB OLD-CISCO-APPLETALK-MIB

CISCO-DLSW-EXT-MIB OLD-CISCO-DECNET-MIB

CISCO-DLSW-MIB OLD-CISCO-NOVELL-MIB

CISCO-DSPU-MIB OLD-CISCO-SYSTEM-MIB

CISCO-FRAS-HOST-MIB OLD-CISCO-TCP-MIB

CISCO-IETF-ATM2-PVCTRAP-MIB OLD-CISCO-TS-MIB


OL-6384-04


CISCO-IETF-IP-FORWARD-MIB RFC1231-MIB (Token Ring MIB)

CISCO-SDLLC-MIB RFC1381-MIB (X.25 LAPB)

CISCO-LEC-DATA-VCC-MIB RFC1382-MIB (X.25 Packet Layer)

CISCO-LEC-EXT-MIB RFC2006-MIB (MIP)

CISCO-LECS-MIB RMON2-MIB

CISCO-LES-MIB RS-232-MIB

CISCO-NTP-MIB RSVP-MIB

CISCO-PIM-MIB SMON-MIB

CISCO-QLLC01-MIB SNA-SDLC-MIB

CISCO-RMON-SAMPLING-MIB SNMP-PROXY-MIB

CISCO-RSRB-MIB —

Table 3-2 Cisco 7200 Router MIBs—Support Not Verified in the c7200 Image (continued)


OL-6384-04

Chapter 3 MIB SpecificationsATM-MIB

Not Verified or Unsupported MIBsTable 3-3 lists the Cisco 7200 MIBs included in c7200 image that are not verified or unsupported in Cisco IOS Release 12.2SB REL4.

ATM-MIBThe 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.

MIB ConstraintsTable 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.

Table 3-3 Not Verified or Unsupported Cisco 7200 Router MIBs in the c7200 Image

CISCO-OAM-MIB

Table 3-4 ATM-MIB Constraints

MIB Object Notes

atmInterfaceDs3PlcpTable Not used in Cisco 7200.

atmInterfaceTCTable Not supported.

atmTrafficDescrParamTable

• atmTrafficDescrType Read-only.

• atmTrafficDescrParam1 Read-only.





• atmTrafficQoSClass Read-only.

atmVplTable Not supported.

atmVclTable

• atmVclAdminStatus Read-only.

• atmVclReceiveTrafficDescrIndex Read-only.

• atmVclTransmitTrafficDescrIndex Read-only.

• atmVccAalType Read-only.

• atmVccAal5CpcsTransmitSduSize Read-only. Default value 4470.

• atmVccAal5CpcsReceiveSduSize Read-only. Default value 4470.

• atmVccAal5EncapsType Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsATM-FORUM-ADDR-REG-MIB

ATM-FORUM-ADDR-REG-MIBThe 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.

ATM-FORUM-MIBThe ATM-FORUM-MIB contains ATM object definitions and object identifiers (OIDs).

BGP4-MIBThe 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

MIB ConstraintsTable 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.

• atmVclCrossConnectIdentifier Read-only.

• atmVclRowStatus Read-only.

• atmVclCastType Not supported.

• atmVclConnKind Not supported.

atmVpCrossConnectTable

• atmVcCrossConnectIndexNext Not supported.

atmVcCrossConnectTable Not implemented.

aal5VccTable

• atmTrafficDescrParamIndexNext Not supported.

1 The ifType for the ifIndex used in the ATM-MIB tables must be of type atm(37).

Table 3-4 ATM-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsBRIDGE-MIB

BRIDGE-MIBThe 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.

CISCO-AAA-SERVER-MIBThe 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

MIB ConstraintsTable 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.

Table 3-5 BGP4-MIB Constraints

MIB Object Notes

bgpPeerTable

• bgpPeerConnectRetryInterval Read-only.

• bgpPeerMinASOriginationInterval Read-only.

• bgpPeerMinRouteAdvertisementInterval Read-only.

• bgpPeerKeepAliveConfigured Read-only.

• bgpPeerHoldTimeConfigured Read-only.

bgpRcvdPathAttrTable

• bgpPathAttrPeer Obsolete.

• bgpPathAttrDestNetwork Obsolete.

• bgpPathAttrOrigin Obsolete.

• bgpPathAttrASPath Obsolete.

• bgpPathAttrNextHop Obsolete.

• bgpPathAttrInterASMetric Obsolete.

Table 3-6 CISCO-AAA-SERVER-MIB Constraints

MIB Object Notes

casConfigTable

• casAddress Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-AAA-SESSION-MIB

CISCO-AAA-SESSION-MIBThe CISCO-AAA-SESSION-MIB contains information about accounting sessions based on authentication, authorization, and accounting (AAA) protocols.

MIB ConstraintsTable 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.

• casAuthenPort Read-only. The default value is 1645.

• casAcctPort Read-only. The default value is 1646.

• casKey Read-only. This value always shown as " " (null string) for security reasons.

• casConfigRowStatus Read-only.

casStatisticsTable

• casAuthorRequests For RADIUS servers, these values are always 0. (RADIUS does not make authorization requests.) Only TACACS+ servers can have nonzero values.

• casAuthorRequestTimeouts

• casAuthorUnexpectedResponses

• casAuthorServerErrorResponses

• casAuthorIncorrectResponses

• casAuthorResponseTime

• casAuthorTransactionSuccesses

• casAuthorTransactionFailures

The configuration objects in the MIB are read-only. To configure AAA servers, use the CLI commands aaa new-model, aaa authentication ppp, aaa authorization, aaa accounting, and radius-server host.

Table 3-6 CISCO-AAA-SERVER-MIB Constraints (continued)

MIB Object Notes

Table 3-7 CISCO-AAA-SESSION-MIB Constraints

MIB Object Notes

casnActiveTable

• casnDisconnect To use this object to disconnect from an AAA server through SNMP, you must have enabled the functionality through the CLI command aaa session-mib disconnect.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-AAL5-MIB

CISCO-AAL5-MIBThe 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).


CISCO-ACCESS-ENVMON-MIBThe 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.

CISCO-ALPS-MIBThe 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.

CISCO-ASPP-MIBThe 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.

CISCO-ATM-EXT-MIBThe 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.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-BGP4-MIB

CISCO-BGP4-MIBThe 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

CISCO-BSC-MIBThe 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).

CISCO-BSTUN-MIBThe 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.

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

CISCO-BUS-MIBThe CISCO-BUS-MIB contains information to manage LANE broadcast and unknown servers.

CISCO-CAR-MIBThe 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.

CISCO-CASA-FA-MIBThe CISCO-CASA-FA-MIB is used in conjunction with the CISCO-CASA-MIB to manage a Cisco Appliance Services Architecture (CASA) forwarding agent (FA).


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-CASA-MIB

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

CISCO-CASA-MIBThe 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).

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

CISCO-CIRCUIT-INTERFACE-MIBThe 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-MIBThe 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.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-CONFIG-COPY-MIB

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

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

CISCO-CONFIG-MAN-MIBThe 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-DLCSW-MIBThe 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.

CISCO-DLSW-EXT-MIBThe 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.

CISCO-DLSW-MIBThe CISCO-DLSW-MIB contains objects to manage data-link switches.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-DSPU-MIB

CISCO-DSPU-MIBThe CISCO-DSPU-MIB contains objects to configure and manage Cisco downstream physical unit (DSPU) objects.

CISCO-ENTITY-ALARM-MIBThe 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 on page 3-38 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.

MIB ConstraintsTable 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:

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

MIB Object Notes

ceAlarmDescrTable

• ceAlarmDescrSeverity Read-only.

ceAlarmFilterProfileTable

• ceAlarmFilterIndex

• ceAlarmFilterStatus

• ceAlarmFilterAlias

• ceAlarmFilterAlarmsEnabled

• ceAlarmFilterNotifiesEnabled

• ceAlarmFilterSyslogEnabled

The objects listed are not supported.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENTITY-ALARM-MIB

– Critical—Indicates a severe, service-affecting condition has occurred and that immediate corrective action is imperative, regardless of the time of day or day of the week. For example, online insertion and removal 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-9 entPhysicalTable Objects for Cisco 7200 Router 6-Port Clear Channel T3 Module Ports

Physical Entity entPhysicalVendorTypeceAlarmDescrSeverity ceAlarmDescrText

ceAlarmDescrAlarmType

Clear channel T3 interface

cevPortDs3 major Transmitter is sending remote alarm

0


cevPortDs3 major Transmitter is sending AIS

1


cevPortDs3 major Receiver has loss of signal

2


cevPortDs3 major Receiver is receiving AIS

3


cevPortDs3 major Receiver has loss of frame

4


cevPortDs3 major Receiver has remote alarm

5


cevPortDs3 major Receiver has idle signal

6


cevPortDs3 major Other failure 7


cevPortDs3 major Physical port link down

8


cevPortDs3 info Physical port administrative state down

9


OL-6384-04


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-10 entPhysicalTable Objects for Cisco 7200 Router Port Adapters



Gigabit Ethernet cevPortGe critical Physical port link down

0

Gigabit Ethernet cevPortGe info Physical port administrative state down

1

Fast Ethernet cevPortFEIP critical Physical port link down

0

Fast Ethernet cevPortFEIP info Physical port administrative state down

1

Table 3-11 entPhysicalTable Objects for Cisco 7200 Router Packet over SONET Ports

Physical EntityentPhysicalVendor Type

ceAlarmDescrSeverity ceAlarmDescrText


Packet over SONET cevPortPOS critical Section loss of signal failure

0

Packet over SONET cevPortPOS critical Section loss of frame failure

1

Packet over SONET cevPortPOS critical Section out of frame alignment

2

Packet over SONET cevPortPOS critical Section J0 mismatch

3

Packet over SONET cevPortPOS critical Section bit interleaved parity

4

Packet over SONET cevPortPOS critical Line alarm indication signal

5

Packet over SONET cevPortPOS critical Line remote failure indication

6

Packet over SONET cevPortPOS critical Line bit interleaved parity

7

Packet over SONET cevPortPOS critical Line far end block errors

8

Packet over SONET cevPortPOS critical Path alarm indication signal

9


OL-6384-04


Packet over SONET cevPortPOS critical Path remote failure indication

10

Packet over SONET cevPortPOS critical Path loss of pointer 11

Packet over SONET cevPortPOS critical Path bit interleaved parity

12

Packet over SONET cevPortPOS critical Path far end block errors

13

Packet over SONET cevPortPOS critical Protection switch byte failure

14

Packet over SONET cevPortPOS critical Path pointer justifications

15

Packet over SONET cevPortPOS critical Path positive pointer stuff event

16

Packet over SONET cevPortPOS critical Path negative pointer stuff event

17

Packet over SONET cevPortPOS critical Path payload label mismatch

18

Packet over SONET cevPortPOS critical Path payload unequipped

19

Packet over SONET cevPortPOS critical Count of APS 20

Packet over SONET cevPortPOS critical Receiver data out of lock failure

21

Packet over SONET cevPortPOS critical Signal failure alarm 22

Packet over SONET cevPortPOS critical Signal degrade alarm

23

Packet over SONET cevPortPOS critical Threshold cross alarm–B1

24


25


26

Packet over SONET cevPortPOS critical Port link down alarm

27

Packet over SONET cevPortPOS info Port administrative down alarm

28

Table 3-11 entPhysicalTable Objects for Cisco 7200 Router Packet over SONET Ports (continued)

Physical EntityentPhysicalVendor Type

ceAlarmDescrSeverity ceAlarmDescrText



OL-6384-04


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-12 entPhysicalTable Objects for Cisco 7200 Router OC-3 ATM



ATM over SONET cevPortOc3 critical Loss of signal failure

0

ATM over SONET cevPortOc3 critical Loss of frame 1

ATM over SONET cevPortOc3 critical Out of frame failure

2

ATM over SONET cevPortOc3 critical Loss of path 3

ATM over SONET cevPortOc3 critical Line far end receiver data failure

4

ATM over SONET cevPortOc3 critical Line alarm indication signal

5

ATM over SONET cevPortOc3 critical Path alarm indication signal

6

ATM over SONET cevPortOc3 critical Path far end receiver data failure

7

ATM over SONET cevPortOc3 critical Loss of cell delineation

8

ATM over SONET cevPortOc3 critical Path bit interleaved parity

9

ATM over SONET cevPortOc3 critical Path payload label mismatch

12

ATM over SONET cevPortOc3 critical Section bit interleaved parity

10

ATM over SONET cevPortOc3 critical Line bit interleaved parity

11

ATM over SONET cevPortOc3 critical Path payload unequipped

13

ATM over SONET cevPortOc3 critical Physical port link down

14

ATM over SONET cevPortOc3 Info Physical port administrative state down

15


OL-6384-04


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.

Table 3-13 entPhysicalTable Objects for Cisco 7200 Router ATM over T3 and E3 Port Adapters



ATM over T3 cevPortDs3Atm critical Loss of signal failure

0

ATM over T3 cevPortDs3Atm critical Out of frame failure

1

ATM over T3 cevPortDs3Atm critical Pay load mismatch 2

ATM over T3 cevPortDs3Atm critical Idle 3

ATM over T3 cevPortDs3Atm critical Loss of cell delineation

4

ATM over T3 cevPortDs3Atm critical Far end receiver data failure

5

ATM over T3 cevPortDs3Atm critical Alarm indication signal

6

ATM over T3 cevPortDs3Atm critical Physical port link down

7

ATM over T3 cevPortDs3Atm info Physical port administrative state down

8

ATM over E3 cevPortE3Atm major Loss of signal failure

0

ATM over E3 cevPortE3Atm major Out of frame failure

1

ATM over E3 cevPortE3Atm major Pay load mismatch 2

ATM over E3 cevPortE3Atm major Idle 3

ATM over E3 cevPortE3Atm major Loss of cell delineation

4

ATM over E3 cevPortE3Atm major Far end receiver data failure

5

ATM over E3 cevPortE3Atm major Alarm indication signal

6

ATM over E3 cevPortE3Atm major Physical port link down

7

ATM over E3 cevPortE3Atm info Physical port administrative state down

8


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENTITY-ASSET-MIB

CISCO-ENTITY-ASSET-MIBThe 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).

MIB ConstraintsTable 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.

CISCO-ENTITY-EXT-MIBThe 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-14 CISCO-ENTITY-ASSET-MIB Object Constraints

MIB Object Notes

ceAssetTable

• ceAssetAlias Read-only.

• ceAssetTag Read-only.

• ceAssetCLEI Not supported.

The following objects are read-only objects in the MIB definition. You see values if your platform has any related information on the object. Otherwise, the object is a zero length string, such as ceAssetFirmwareID, ceAssetFirmwareRevision, ceAssetSoftwareI, and ceAssetSoftwareRevision.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENTITY-FRU-CONTROL-MIB

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.

Note The CISCO-ENTITY-EXT-MIB is only supported for the physical entities representing active processors.

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

Table 3-15 CISCO-ENTITY-EXT-MIB Object Constraints

MIB Object Notes

ceExtConfigRegTable

ceExtConfigRegNext Read only.

ceExtSysBootImageList Read only.

Table 3-16 CISCO-ENTITY-FRU-CONTROL-MIB Constraints

MIB Object Notes

cefcModuleTable

• cefcModuleAdminStatus Supported values:

• Enable(1)

• Reset(3)

Note The cefcModuleAdminStatus object cannot be set to reset(3) for processor modules.

• cefcModuleOperStatus Supported values:

– Unknown(1)—Read-only.

– Ok(2)—Read-only.

– Failed(7)—Read-only.

• cefcModuleResetReason Supported values:

– Unknown(1)—Read-only.

– PowerUp(2)—Read-only.

– ManualReset(5)—Read-only.

cefcFRUPowerSupplyGroupTable Not supported.

cefcFRUPowerStatusTable Not supported.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENTITY-SENSOR-MIB

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

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

MIB ConstraintsTable 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.

• cefcMaxDefaultInLinePower Not supported.

1 The entPhysicalEntry (which has module(9) as entPhysicalClass in the entPhysicalTable) has a corresponding entry in the cefcModuleTable.

2 The cefcPowerStatusChange notification is not supported and the cefcModuleStatusChange notification can be supported for a redundant power supply.

Table 3-16 CISCO-ENTITY-FRU-CONTROL-MIB Constraints (continued)

MIB Object Notes

Table 3-17 CISCO-ENTITY-VENDORTYPE-OID-MIB Objects and Constraints

MIB Object (OID Assignment) Notes (Part Number)

cevContainer

• cevContainerSlot (1.3.6.1.4.1.9.12.3.1.5.1)

Chassis slot

cevModule

• cevModuleC7xxxType (1.3.6.1.4.1.9.12.3.1.9.7)

cevPortAdapters

Cisco 7200 PCI Port Adapter Carrier cards (7200-PA-CC)


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENTITY-VENDORTYPE-OID-MIB

• cevPaAtmdxE3 (1.3.6.1.4.1.9.12.3.1.9.4.38)

1-port enhanced ATM E3 port adapter

(PA-A3-E3)

• cevPaAtmdxDs3 (1.3.6.1.4.1.9.12.3.1.9.4.37)

1-port enhanced ATM T3 port adapter

(PA-A3-T3)

cevModuleVipPortAdapters Support for shared port adapters 1.3.6.1.4.1.9.12.3.1.9.4

• cevModuleC7xxxType (1.3.6.1.4.1.9.12.3.1.9.7)

ATM WAN OC3MM PA

• cevPa8e (1.3.6.1.4.1.9.12.3.1.9.4.2)

8-Port Ethernet 10BaseT Port Adapter

• cevPa4t (1.3.6.1.4.1.9.12.3.1.9.4.5)

4-Port Serial Port Adapter, Enhanced

• cevPaA8tV35 (1.3.6.1.4.1.9.12.3.1.9.4.12)

8 Port Serial, V.35 Port Adapter

• cevPaA8tRs232 (1.3.6.1.4.1.9.12.3.1.9.4.43)

8-Port Serial, 232 Port Adapter

• cevPaA8tX21 (1.3.6.1.4.1.9.12.3.1.9.4.42)

8-Port Serial, X.21 Port Adapter

• cevPaAh1t (1.3.6.1.4.1.9.12.3.1.9.4.9)

PA-H PORT ADAPTER:2-PORT HSSI

(High Speed Serial Interface port adapter)

• cevPaAh2t (1.3.6.1.4.1.9.12.3.1.9.4.10)

PA-2H PORT ADAPTER:2-PORT HSSI

• cevPa2feTx (1.3.6.1.4.1.9.12.3.1.9.4.56)

2-Port Fast Ethernet Port Adapter

• cevPa2feFx (1.3.6.1.4.1.9.12.3.1.9.4.57)

2-Port Fast Ethernet Port Adapter

• cevPaGe (1.3.6.1.4.1.9.12.3.1.9.4.59)

Gigabit Ethernet port adapter

• cevPa2t3 (1.3.6.1.4.1.9.12.3.1.9.4.49)

2 Port T3 Serial Port Adapter Enhanced

• cevPa2e3 (1.3.6.1.4.1.9.12.3.1.9.4.47)

1 Port T3 Serial Port Adapter Enhanced

• cevPaAtmdxMmOc3 (1.3.6.1.4.1.9.12.3.1.9.4.41)

1-Port ATM Enhanced OC3c/STM1 Multimode Port Adapter

• cevPaAtmdxSmiOc3 (1.3.6.1.4.1.9.12.3.1.9.4.40)

1-Port ATM Enhanced OC3c/STM1 Singlemode (IR) Port Adapter

• cevPaAtmdxSmlOc3 (1.3.6.1.4.1.9.12.3.1.9.4.39)

1-Port ATM Enhanced OC3c/STM1 Singlemode (LR) Port Adapter

• cevPaMc2t3ec (1.3.6.1.4.1.9.12.3.1.9.4.113)

Enhanced PA-MC-2T3e Port Adapter

Table 3-17 CISCO-ENTITY-VENDORTYPE-OID-MIB Objects and Constraints (continued)



OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENVMON-MIB

CISCO-ENVMON-MIBThe 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.

cevPort

• cevPortFEIP (1.3.6.1.4.1.9.12.3.1.10.16)

NSE Fast Ethernet port

• cevPortGE (1.3.6.1.4.1.9.12.3.1.10.109)

NSE GigabitEthernet port

• cevPortOc3 (1.3.6.1.4.1.9.12.3.1.10.80)

OC-3 ATM port

• cevPortT3 (1.3.6.1.4.1.9.12.3.1.10.20)

Clear Channel T3 port

• cevPortPOS (1.3.6.1.4.1.9.12.3.1.10.52)

Packet over SONET port

• cevPortE3Atm (1.3.6.1.4.1.9.12.3.1.10.176)

PA-A3-E3 port

• cevPortDs3ATM (1.3.6.1.4.1.9.12.3.1.10.177)

PA-A3-T3 port

• cevPortFEIP (1.3.6.1.4.1.9.12.3.1.10.16)

PA-2FE-TX port

cevModuleSFPType

Gigabit Ethernet SFP is a 1000-Mbps optical interface with LC-type duplex connection

• cevSFP1000BaseSx 1.3.6.1.4.1.9.12.3.1.9.51.6

GLC-SX-MM, short wavelength

• cevSFP1000BaseLx 1.3.6.1.4.1.9.12.3.1.9.51.7

GLC-LH-SM, long wavelength, long haul

• cevSFP1000BaseZx 1.3.6.1.4.1.9.12.3.1.9.51.9

GLC-ZX-SM, extended distance wavelength

cevMGBIC

Gigabit Ethernet GBIC is a 1000-Mbps optical interface with an SC-type duplex connection

• cevMGBIC1000BaseSX (1.3.6.1.4.1.9.12.3.1.9.16.2)

GBIC-SX or WS-G5484, short wavelength

• cevMGBIC1000BaseSX (1.3.6.1.4.1.9.12.3.1.9.16.2)

GBIC-LX/LH or WS-G5486, long wavelength, long haul

• cevMGBIC1000BaseSX (1.3.6.1.4.1.9.12.3.1.9.16.2)

GBIC-ZX or WS-G5487, extended distance wavelength

Table 3-17 CISCO-ENTITY-VENDORTYPE-OID-MIB Objects and Constraints (continued)



OL-6384-04

Chapter 3 MIB SpecificationsCISCO-FLASH-MIB

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

CISCO-FRAME-RELAY-MIBThe CISCO-FRAME-RELAY-MIB contains Frame Relay information that is specific to Cisco products or that is missing from RFC 1315.

CISCO-FRAS-HOST-MIBThe CISCO-FRAS-HOST-MIB contains objects specific to upstream or host-end sessions.

CISCO-FTP-CLIENT-MIBThe CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management.

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

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


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-IETF-ATM2-PVCTRAP-MIB

• Holdtime is the interval between the receipt of a hello message and the assumption that the sending router has failed.

MIB Constraints

CISCO-IETF-ATM2-PVCTRAP-MIBThe 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.


CISCO-IETF-ATM2-PVCTRAP-MIB-EXTNThe 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.


CISCO-IETF-IP-FORWARD-MIBThe 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.

Table 3-18 CISCO-HSRP-MIB Constraints

MIB Object Notes

cHsrpGrpGroup

• cHsrpConfigTimeout

• cHsrpGrpAuth

• cHsrpGrpPriority

• cHsrpGrpPreempt

• cHsrpGrpPreemptDelay

• cHsrpGrpConfiguredHelloTime

• cHsrpGrpConfiguredHoldTime

• cHsrpGrpVirtualIpAddr

These objects are read-only.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-IETF-IP-MIB

CISCO-IETF-IP-MIBThe 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.”

MIB Constraints

CISCO-IMAGE-MIBThe 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.


CISCO-IP-STAT-MIBThe 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

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

ConstraintThe ciscoIpMRouteInLimit object is obsolete.

Table 3-19 CISCO-IETF-IP-MIB Constraints

MIB Object Notes

cIpv6InterfaceTable

• cIpv6Forwarding

• cIpv6DefaultHopLimit

• cIpv6InterfaceIdentifier

• cIpv6InterfaceIdentifierLength

• cInetNetToMediaPhysAddress

• cInetNetToMediaType

These objects are all read-only.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-ENHANCED-MEMORY-POOL-MIB

CISCO-ENHANCED-MEMORY-POOL-MIB

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.

CISCO-LEC-DATA-VCC-MIBThe 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.

CISCO-LEC-EXT-MIBThe CISCO-LEC-EXT-MIB module is a Cisco extension to the ATM Forum's LANE client MIB.

CISCO-LECS-MIBThe CISCO-LECS-MIB contains objects that manage LANE configuration in Cisco devices.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-LES-MIB

CISCO-LES-MIBThe CISCO-LES-MIB contains objects that manage LANE service in Cisco devices.

CISCO-MEMORY-POOL-MIBThe CISCO-MEMORY-POOL-MIB contains objects to monitor memory pools on the router.


CISCO-NBAR-PROTOCOL-DISCOVERY-MIB-MIBThe 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).

CISCO-NETFLOW-MIBThe 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.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-NTP-MIB

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

CISCO-NTP-MIBThe 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.

Table 3-20 CISCO-NETFLOW-MIB Object Groups

Objects Group Description

cnfCacheInfo Provides common information for all active/inac-tive flows ( i.e. entries, time out etc) per cache basis.

cnfExportInfo Provides information about export like export version and export destinations(/Collectors).

cnfFeatureAcceleration Provides information about NetFlow Feature Ac-celeration.

cnfExportStatistics Provides export statistics.

cnfProtocolStatistics Provides a summary of NetFlow cache statistics.

cnfExportTemplate Provides Template based Version 9 flow export information and statistic.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-PAE-MIB

CISCO-PAE-MIBThe 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.

CISCO-PIM-MIBThe 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.

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

MIB ConstraintsTable 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.

CISCO-PPPOE-MIBThe 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.

MIB ConstraintsTable 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.

Table 3-21 CISCO-PING-MIB Constraints

MIB Object Notes

cPingTable

• ciscoPingVrfName Read-only.

Table 3-22 CISCO-PPPOE-MIB Constraints

MIB Object Notes

cPppoeVcCfgTable

• cPppoeSystemMaxAllowedSessions Read-only.

• cPppoeSystemThresholdSessions Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-PROCESS-MIB

CISCO-PROCESS-MIBThe 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.

MIB ConstraintsTable 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.

CISCO-PRODUCTS-MIBThe 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

cPppoeVcCfgTable

• cPppoeVcEnable Read-only.

cPppoeVcSessionsTable

• cPppoeVcMaxAllowedSessions Read-only.

• cPppoeVcExceededSessionErrors Read-only.

Table 3-22 CISCO-PPPOE-MIB Constraints (continued)

MIB Object Notes

Table 3-23 CISCO-PROCESS-MIB Constraints

MIB Object Notes

cpmCPUTableTable

• cpmCPUTotal5sec Deprecated.

• cpmCPUTotal1min Deprecated.

• cpmCPUTotal5min Deprecated.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-QLLC01-MIB

CISCO-QLLC01-MIBThe CISCO-QLLC01-MIB contains objects to configure and monitor logical connections for the Qualified Logical Link Control (QLLC) protocol.

CISCO-QUEUE-MIBThe CISCO-QUEUE-MIB contains objects to manage interface queues, which can be used for FIFO, priority, custom, and fair queuing.

CISCO-RSRB-MIBThe 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.

CISCO-RTTMON-MIBThe 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.

MIB ConstraintsTable 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.

Table 3-24 CISCO-RTTMON-MIB Constraints

MIB Object Notes

rttMonCtrlAdminTable

• rttMonCtrlAdminOwner Read-only.

• rttMonCtrlAdminTag Read-only.

• rttMonCtrlAdminRttType Read-only.

• rttMonCtrlAdminThreshold Read-only.

• rttMonCtrlAdminFrequency Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-RTTMON-MIB

• rttMonCtrlAdminTimeout Read-only.

• rttMonCtrlAdminVerifyData Read-only.

• rttMonCtrlAdminNvgen Read-only.

rttMonEchoAdminTable

• rttMonEchoAdminProtocol Read-only.

• rttMonEchoAdminTargetAddress Read-only.

• rttMonEchoAdminPktDataRequestSize Read-only.

• rttMonEchoAdminPktDataResponseSize Read-only.

• rttMonEchoAdminTargetPort Read-only.

• rttMonEchoAdminSourceAddress Read-only.

• rttMonEchoAdminSourcePort Read-only.

• rttMonEchoAdminControlEnable Read-only.

• rttMonEchoAdminTOS Read-only.

• rttMonEchoAdminTargetAddressString Read-only.

• rttMonEchoAdminNameServer Read-only.

• rttMonEchoAdminOperation Read-only.

• rttMonEchoAdminHTTPVersion Read-only.

• rttMonEchoAdminURL Read-only.

• rttMonEchoAdminCache Read-only.

• rttMonEchoAdminInterval Read-only.

• rttMonEchoAdminNumPackets Read-only.

• rttMonEchoAdminProxy Read-only.

• rttMonEchoAdminString1 Read-only.





• rttMonEchoAdminMode Read-only.

• rttMonEchoAdminTOS Read-only.

rttMonScheduleAdminTable

• rttMonScheduleAdminRttLife Read-only.

• rttMonScheduleAdminRttStartTime Read-only.

• rttMonScheduleAdminConceptRowAgeout Read-only.

rttMonStatisticsAdminTable

• rttMonStatisticsAdminNumHourGroups Read-only.

• rttMonStatisticsAdminNumPaths Read-only.

Table 3-24 CISCO-RTTMON-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-SDLLC-MIB

CISCO-SDLLC-MIBThe 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.

CISCO-SMI-MIBThe CISCO-SMI-MIB defines the structure of management information for Cisco enterprise MIBs.

CISCO-SNAPSHOT-MIBThe 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.

CISCO-SSG-MIBThe 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

• rttMonStatisticsAdminNumHops Read-only.

• rttMonStatisticsAdminNumDistBuckets Read-only.

• rttMonStatisticsAdminDistInterval Read-only.

rttMonHistoryAdminTable

• rttMonHistoryAdminNumLives Read-only.

• rttMonHistoryAdminNumBuckets Read-only.

• rttMonHistoryAdminNumSamples Read-only.

• rttMonHistoryAdminFilter Read-only.

rttMonCtrlOperTable

• rttMonCtrlOperState Read-only.

Table 3-24 CISCO-RTTMON-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-STUN-MIB

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.

MIB ConstraintsTable 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

CISCO-STUN-MIBThe 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.

Table 3-25 CISCO-SSG-MIB Constraints

MIB Object Notes

ciscoSsgCfgGroup

• ssgCfgLocalForwarding Not supported.

• ssgCfgAutoDomainNat Not supported.

• ssgCfgTransPassThrough Not supported.

• ssgCfgMaxServicesPerUser The router supports a maximum of 7 services per service group. Each user can only be subscribed to one service group.

• ssgCfgTcpRedirGrpForSMTP Not supported.

• ssgCfgTcpRedirGrpForAdvCapt Not supported.

ssgServiceTable

• ssgServiceDNSPrimaryIpType DNS redirect is not supported.

• ssgServiceDNSPrimary DNS redirect is not supported.

• ssgServiceDNSSecondaryIpType DNS redirect is not supported.

• ssgServiceDNSSecondary DNS redirect is not supported.


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-SYSLOG-MIB

CISCO-SYSLOG-MIBThe 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.

MIB ConstraintsThe MIB does not keep track of messages generated from commands entered through the command line interface (CLI).

CISCO-TC-MIBThe CISCO-TC-MIB defines the textual conventions used in Cisco enterprise MIBs.

CISCO-TCP-MIBThe 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.

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIBThe 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.

CISCO-VPDN-MGMT-MIBThe 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:


OL-6384-04

Chapter 3 MIB SpecificationsCISCO-VPDN-MGMT-EXT-MIB

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

MIB ConstraintsTable 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.

CISCO-VPDN-MGMT-EXT-MIBThe 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-26 CISCO-VPDN-MGMT- MIB Constraints

MIB Object Notes

cvpdnTable

• cvpdnTunnelTotal Replaced by cvpdnSystemTunnelTotal.

• cvpdnSessionTotal Replaced by cvpdnSystemSessionTotal.

• cvpdnDeniedUsersTotal Replaced by cvpdnSystemDeniedUsersTotal.

cvpdnTunnelTable Replaced by cvpdnTunnelAttrTable.

cvpdnTunnelSessionTable Replaced by cvpdnSessionAttrTable.

cvpdnTemplateTable SNMP limits the size of VPDN template names to 128 characters. If any template name in the cvpdnTemplateTable exceeds this length, you cannot use an SNMP getmany request to retrieve any table entries. Instead, you must use individual getone requests to retrieve each template name (cvpdnTemplateName) that does not exceed 128 characters.


OL-6384-04

Chapter 3 MIB SpecificationsDLSW-MIB

MIB ConstraintsTable 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

DLSW-MIBThe DLSW-MIB (RFC 2024) contains objects to manage data-link switching (DLSw) on the router.

ENTITY-MIB (RFC 2737)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.

Table 3-27 CISCO--VPDN-MGMT-EXT-MIB Constraints

MIB Object Notes

cvpdnSessionExtTable

• cvpdnSessionRemoteSendSequence

• cvpdnSessionRemoteRecvSequence

• cvpdnSessionSentZLB

• cvpdnSessionRecvZLB

• cvpdnSessionSentRBits

• cvpdnSessionRecvRBits

• cvpdnSessionLocalWindowSize

• cvpdnSessionRemoteWindowSize

• cvpdnSessionCurrentWindowSize

• cvpdnSessionMinimumWindowSize

• cvpdnSessionATOTimeouts

• cvpdnSessionOutGoingQueueSize

• cvpdnSessionAdaptiveTimeOut

• cvpdnSessionRoundTripTime

• cvpdnSessionPktProcessingDelay

• cvpdnSessionZLBTime

These objects are not implemented.

All other MIB objects are read-only.


OL-6384-04

Chapter 3 MIB SpecificationsENTITY-MIB (RFC 2737)

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

MIB ConstraintsTable 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-28 ENTITY-MIB Constraints

MIB Object Notes

• entPhysicalAlias Zero length string.

• entPhysicalAssetID Zero length string.

entLogicalTable

• entLogicalContextName Not supported.

entLPMappingTable Not supported.

Table 3-29 entPhysicalTable Entries for Cisco 7200 Chassis Components

entPhysicalDescr entPhysicalVendorType entPhysicalClass entPhysicalName Notes

C7200 chassis cevChassis7204 or cevChassis7206

chassis(3) 7200 Chassis

Chassis slot cevContainerSlot container(5) slot1 Contained in the chassis


OL-6384-04


Table 3-30 lists entPhysicalTable entries for the Cisco 7200 router network service engine (NSE) cards.

Chassis slot cevContainerSlot container(5) slot 2 Contained in the chassis.

Chassis slot cevContainerSlot container(5) slot 3 Contained in the chassis




Power supply and fan module

cevPowerSupplyC7200DC

powerSupply(6) Entity description and PS slot number

Device supports AC and DC power supplies. The power supply and fan are in the PS container

Power supply and fan module

cevPowerSupplyC7200AC

powerSupply(6) Entity description and PS slot number

Device supports AC and DC power supplies. The power supply and fan are in the PS container

Table 3-29 entPhysicalTable Entries for Cisco 7200 Chassis Components (continued)



OL-6384-04


Table 3-30 entPhysicalTable Entries for Cisco 7200 Network Service Engine Cards


NSE 100 CPU card

cevCpuC7200Nse100 module(9) Entity description and slot number

7200 NSE occupies 2 slots. It is contained in either slots 0 and 1 or slots 2 and 3.

NSE 100 daughter card

cevC7200Nse100Db module(9) Entity description and slot number

Contained in NSE-100 only.

7200-NPE-G100 cevCpuC7200Npeg100 module(9) Entity description and slot number

7200 network route processor engine is contained in in I/O and CPU Slot 0.

Mistral EOBC cevPortFEIP port(10) FastEthernet0 Only contained in the primary NSE-100.

Pinnacle GE cevPortGE port(10) GigabitEthernet0/0 GigabitEthernet0/1 GigabitEthernet2/0 GigabitEthernet2/1

Contained in the primary and standby NSE-100. There are 2 GE ports per NSE-100.

BCM1250 Internal MAC

cevPortGE port(10) GigabitEthernet0 or GigabitEthernet1 or GigabitEthernet2

Only contained in the primary NPE-G100.

NSE DB temperature sensor

cevSensorC7200NseDbTempVoltage

sensor(8) Entity description and slot number

Contained in the primary NSE DB.

NSE DB 1.65 V sensor





OL-6384-04


NSE DB 1.8 V sensor




Cisco 7200 Series Network Processing Engine NPE-G2

cevCpu7200Npeg2 module(9) NPE-G2 0 Contained in I/O and CPU Slot 0. Supports one FastEthernet management port, three GigabitEthernet ports, and one USB port. The USB port is not supported in the Cisco 12.2(31)SB5 IOS release.

Table 3-30 entPhysicalTable Entries for Cisco 7200 Network Service Engine Cards (continued)



OL-6384-04


Table 3-31 lists entPhysicalTable entries for the Cisco 7200 Router OC-3-POS components.

Table 3-31 entPhysicalTable Entries for Cisco 7200 OC-3-POS Components


2-port POS OC-3 multimode

cevC72002Oc3PosMm module(9) Entity description and slot number

2-port OC-3c/STM-1 POS card

2-port POS OC-3 SM Intermediate Range

cevC72002Oc3PosSmIr module(9) Entity description and slot number


2-port POS OC-3 SM Long Range

cevC72002Oc3PosSmLr module(9) Entity description and slot number


4-port POS OC-3 multimode

cevC72004Oc3PosMm module(9) Entity description and slot number


4-port POS OC-3 SM Intermediate Range

cevC72004Oc3PosSmIr module(9) Entity description and slot number

4-port OC-3c/STM-1 POS line car

4-port POS OC-3 SM Long Range

cevC72004Oc3PosSmLr module(9) Entity description and slot number

4-port OC-3c/STM-1 POS line car

pos_oc3 Temperature Sensor

cevSensorModuleDeviceTemp


Contained in the OC-3 POS card

pos_oc3 1.5 V Sensor

cevSensorModuleDeviceVoltage















pos_oc3 12 V Sensor





OL-6384-04


Table 3-32 lists entPhysicalTable Entries for Cisco 7200 Chassis Components.

Table 3-32 entPhysicalTable Entries for Cisco 7201 Chassis Components

entPhysicalDescr Cisco 7201, 1-slot chassis

entPhysicalVendorType cevChassis7201

entPhysicalClass chassis(3)

entPhysicalName Chassis Notes

entPhysicalDescr PA Slot Container

entPhysicalVendorType cevContainerSlot

entPhysicalClass container(5)

entPhysicalName PA Slot 1

Contained in the chassis.

entPhysicalDescr Power Supply Container

entPhysicalVendorType cevContainerSlot

entPhysicalClass container(5)

entPhysicalName PEM 0 or 1

Two power supply bays contained in the chassis.

entPhysicalDescr Cisco 7201 AC Power Supply :

entPhysicalVendorType cevPowerSupplyC7201AC

entPhysicalClass powerSupply

entPhysicalName Power Supply 1 or 2

The Cisco 7201 supports AC and DC power supplies, contained in the power supply bay.

entPhysicalDescr Cisco 7201 Network Processing Engine

entPhysicalVendorType cevCpu7201Npeg2

entPhysicalClass module(9)

entPhysicalName c7201

Contained in the chassis. Supports one FastEthernet management port, four GigabitEthernet ports, and one USB port. The USB port is not supported in the Cisco 12.2(31)SB release.


OL-6384-04

Chapter 3 MIB SpecificationsETHERLIKE-MIB

ENTITY-MIB UDI Support

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)

ETHERLIKE-MIBThe ETHERLIKE-MIB (RFC 2665) contains objects to manage Ethernet-like interfaces on the Cisco 7200 router.

MIB ConstraintsTable 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.

Table 3-33 ETHERLIKE-MIB Constraints

MIB Table/Object Notes

dot3CollTable Not implemented


OL-6384-04

Chapter 3 MIB SpecificationsEVENT-MIB

Table 3-34 shows usage of ifTable for Ethernet-like layer.

EVENT-MIBThe EVENT-MIB contains objects to define event triggers and actions for network management purposes.

MIB ConstraintTable 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.

dot3ControlTable Not implemented

dot3PauseTable Not implemented

Table 3-33 ETHERLIKE-MIB Constraints (continued)


Table 3-34 ETHERLIKE-MIB ifTable Usage

MIB ifTable Object Use for GigaEthernet Layer

ifDescr GE-WAN<slot>/<port>

ifType EthernetCsmacd(6)

ifSpeed 1000000000

ifPhysAddress MAC Address

ifName GE<slot>/<port>

ifLinkUpDownTrapEnable enabled(1)

ifHighSpeed 1000

ifConnectorPresent true(1)

Table 3-35 EVENT-MIB Constraints


mteTriggerTable

• mteTriggerFrequency Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsEXPRESSION-MIB

EXPRESSION-MIBThe EXPRESSION-MIB contains objects to define expressions of MIB objects for network management purposes.

MIB ConstraintTable 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.

HC-RMON-MIBThe 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.

IEEE8021-PAE-MIBThe Port Access Entity module for managing IEEE 802.1X.

IEEE8023-LAG-MIBThe IEEE 8023-LAG-MIB is the Link Aggregation module for managing IEEE Standard 802.3ad.

Table 3-36 EXPRESSION-MIB Constraints


expObjectTable

• expObjectConditional Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsIF-MIB

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

MIB ConstraintsTable 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..

Table 3-37 IF-MIB Constraints

MIB Object Notes

ifTable

• ifAdminStatus Can not be written in case of atm/aal5 sublayers on an ATM end system, LEC subinterfaces, aal5 sublayer of an ATM switch CPU interface, ATM 2000 physical interface and lex-based interfaces used for accounting

• ifOperStatus Unable to detect states notPresent(6) and lowerLayerDown(7).

ifTestTable Not supported.

ifXTable

• ifPromiscuousMode Read-only.

ifStackTable

• ifStackStatus For creating and removing table entries, the only supported values are createAndGo(4) and destroy(6).

ifRcvAddressTable

• ifRcvAddressStatus For creating and removing table entries, the only supported values are createAndGo(4) and destroy(6).

• ifRcvAddressType The only supported value is other(1).

Table 3-38 RFC1407-MIB Constraints

MIB Object Notes

dsx3ConfigTable

• dsx1LineStatusChangeTrapEnable Supported values: enabled(1) and disabled(2).

• dsx3LineType Supported values is E3 supports e3other(6) and e3Plcp(8)


OL-6384-04

Chapter 3 MIB SpecificationsIGMP-MIB

IGMP-MIBThe IGMP-MIB contains objects to manage the Internet Group Management Protocol (IGMP) on the router.

INT-SERV-GUARANTEED-MIBThe INT-SERV-GUARANTEED-MIB describes the guaranteed service of the Integrated Services Protocol (ISP).

INT-SERV-MIBThe INT-SERV-MIB describes the Integrated Services Protocol (ISP).

IPMROUTE-MIBThe IPMROUTE-MIB contains objects to manage IP multicast routing on the router, independent of the actual multicast routing protocol in use.

• dsx3LineCoding Read-only.

T3 supports dsx3B3ZS(2) value only. E3 supports e3HDB3(3) value only.

• dsx3SendCode Read-only. Supports dsx3SendNoCode value only.

• dsx3CircuitIdentifier Read-only.

• dsx3LoopbackConfig Read-only.

dsx3FarEndConfigTable Not supported.

dsx3FarEndCurrentTable Not supported.

dsx3FarEndIntervalTable Not supported.

dsx3FarEndTotalTable Not supported.

1 All T3/ATM cards only support RO on all variables. See IF-MIB section for use of ifTable.

2 The RFC1407-MIB use supports the following port adapter card types: PA-MC-T3, PA-MC-E3, PA-A3-T3, PA-A3-E3.

Table 3-38 RFC1407-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsLAN-EMULATION-CLIENT-MIB

LAN-EMULATION-CLIENT-MIBThis 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.

MPLS-LDP-MIBThe 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

MIB ConstraintsTable 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.

Table 3-39 MPLS-LDP-MIB Constraints

MIB Object Notes

mplsLdpEntityTable

• mplsLdpEntityProtocolVersion Read-only.

• mplsLdpEntityAdminStatus Read-only.

• mplsLdpEntityWellKnownDiscoveryPort Read-only. Always 646

• mplsLdpEntityMaxPduLength Read-only.

• mplsLdpEntityKeepAliveHoldTimer Read-only.

• mplsLdpEntityHelloHoldTimer Read-only.

• mplsLdpEntityFailedInitSessionTrapEnable Read-only.

• mplsLdpEntityFailedInitSessionThreshold Read-only.

• mplsLdpEntityLabelDistributionMethod Read-only. Value downstreamUnsolicited(2))

• mplsLdpEntityPVLimitMismatchTrapEnable Read-only.

• mplsLdpEntityPathVectorLimit Read-only.

• mplsLdpEntityHopCountLoopDetection Read-only.

• mplsLdpEntityHopCount Read-only.

• mplsLdpEntityTargetedPeer Read-only.


OL-6384-04

http://www.cisco.com/en/US/docs/ios/12_0st/12_0st21/feature/guide/ldpmib21.html

Chapter 3 MIB SpecificationsMPLS-LDP-MIB

• mplsLdpEntityTargetedPeerAddrType Read-only.

• mplsLdpEntityTargetedPeerAddr Read-only.

• mplsLdpEntityOptionalParameters Read-only.

• mplsLdpEntityDiscontinuityTime Read-only.

• mplsLdpEntityStorageType Read-only. (Value volatile(2))

• mplsLdpEntityRowStatus Read-only. (Value active(1))

mplsLdpEntityConfGenericTable

• mplsLdpConfGenericIfIndexOrZero Read-only.

• mplsLdpConfGenericLabel Read-only.

• mplsLdpConfGenericStorageType Read-only.

• mplsLdpConfGenericRowStatus Read-only.

mplsLdpEntityAtmParmsTable

• mplsLdpEntityAtmIfIndexOrZero Read-only.

• mplsLdpEntityAtmMergeCap Read-only. Value vcMerge(2)

• mplsLdpEntityAtmLabelRangeComponents Read-only. Value is 0

• mplsLdpEntityAtmVcDirectionality Read-only. Value unidirectional(1)

• mplsLdpEntityAtmLsrConnectivity Read-only.

• mplsLdpEntityDefaultControlVpi Read-only.

• mplsLdpEntityDefaultControlVci Read-only.

• mplsLdpEntityUnlabTrafVpi Read-only.

• mplsLdpEntityUnlabTrafVci Read-only.

• mplsLdpEntityAtmStorageType Read-only. Value volatile(2)

• mplsLdpEntityAtmRowStatus Read-only. Value iactive(1)

mplsLdpEntityConfAtmLabelRangeTable

• mplsLdpEntityConfAtmLabelRange-MaximumVpi Read-only.

• mplsLdpEntityConfAtmLabelRange-MaximumVci Read-only.

• mplsLdpEntityConfAtmLabelRange-StorageType Read-only.

• mplsLdpEntityConfAtmLabelRange-RowStatus Read-only.

mplsLdpEntityFrameRelayParmsTable

• mplsLdpEntityFrIfIndexOrZero Read-only.

• mplsLdpEntityFrMergeCap Read-only.

• mplsLdpEntityFrLabelRangeComponents Read-only.

• mplsLdpEntityFrLen Read-only.

• mplsLdpEntityFrVcDirectionality Read-only.

• mplsLdpEntityFrParmsStorageType Read-only.

• mplsLdpEntityFrParmsRowStatus Read-only.

Table 3-39 MPLS-LDP-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsMPLS-LSR-MIB

MPLS-LSR-MIBThe 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

mplsLdpEntityConfFrLabelRangeTable

• mplsLdpConfFrMaximumDlci Read-only.

• mplsLdpConfFrStorageType Read-only.

• mplsLdpConfFrRowStatus Read-only.

mplsLdpAtmSessionTable Not supported.

mplsLdpFrameRelaySessionTable Not supported.

mplsLdpSessionPeerAddressTable Not supported.

mplsLdpLibTable Not supported.

mplsLdpFecTable Not supported.

mplsLdpEntityConfGenericTable Not supported.

mplsLdpEntityConfAtmLabelRangeTable Not supported.

mplsLdpEntityFrameRelayParmsTable Not supported.

mplsLdpEntityConfFrLabelRangeTable

• mplsLdpLibLspUp Not supported.

• mplsLdpLibLspDown Not supported.

Table 3-39 MPLS-LDP-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

http://www.cisco.com/en/US/docs/ios/12_0st/release/notes/rn120ST.html


MIB ConstraintsTable 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.

Table 3-40 MPLS-LSR-MIB Constraints

MIB Object Notes

mplsInterfaceConfTable

• mplsInterfaceConfStorageType Default read-only(5).

• mplsInterfaceAvailableBandwidth Read-only. Always 0.

• mplsInterfaceTotalBandwidth Read-only. Always 0.

• mplsInterfaceTotalBuffer Read-only. Always 0.

• MplsInterfaceAvailableBuffer Read-only. Always 0.

mplsInterfacePerfTable

• mplsInterfaceInPackets Read-only. Always 0.

• mplsInterfaceInDiscards Read-only. Always 0.

• mplsInterfaceFailedLabelLookup Read-only. Always 0.

• mplsInterfaceOutPackets Read-only. Always 0.

• mplsInterfaceOutDiscards Read-only. Always 0.

• mplsInterfaceOutFragments Read-only. Always 0.

mplsInSegmentTable

• mplsInSegmentAdminStatus Read-only. Always up(1).

• mplsInSegmentOperStatus Always up(1).

• mplsInSegmentNPop Read-only.

• mplsInSegmentAddrFamily Read-only.

• mplsInSegmentOwner Read-only. Other(1)

• mplsInSegmentTrafficParamPtr Read-only. Always 0.

• mplsInSegmentRowStatus Read-only. Active(5).

• mplsInSegmentStorageType Read-only. Volatile(2)

mplsInSegmentPerfTable

• mplsInSegmentOctets Read-only. Always 0.

• mplsInSegmentPackets Read-only. Always 0.

• mplsInSegmentHCOctets Read-only. Always 0.

• mplsInSegmentErrors Read-only. Always 0.

• mplsInSegmentDiscards Read-only. Always 0.

• mplsInSegmentPerforDiscontinuityTime Read-only. Always 0.

mplsOutSegmentTable

• mplsOutSegmentIfIndex Read-only.


OL-6384-04


• mplsOutSegmentPushTopLabel Read-only.

• mplsOutSegmentTopLabel Read-only.

• mplsOutSegmentNextHopIpAddrType Read-only.

• mplsOutSegmentNextHopIpv4Addr Read-only.

• mplsOutSegmentNextHopIpv6Addr Always 0.

• mplsOutSegmentOwner Read-only. Other(1).

• mplsOutSegmentTrafficParamPtr Always 0.

• mplsOutSegmentRowStatus Read-only. Active(5).

• mplsOutSegmentStorageType Read-only. Volatile(2).

• mplsOutSegmentAdminStatus Read-only. Always up(1).

• mplsOutSegmentOperStatus Always up(1).

mplsOutSegmentPerfTable

• mplsOutSegmentOctets Read-only. Always 0.

• mplsOutSegmentPackets Read-only. Always 0.

• mplsOutSegmentHCOctets Read-only. Always 0.

• mplsOutSegmentErrors Read-only. Always 0.

• mplsOutSegmentDiscards Read-only. Always 0.

• mplsOutSegmentPerfDiscontinuityTime Read-only. Always 0.

mplsXCTable

• mplsXCLspId Read-only. Does not support tunnel IDs.

• mplsXCLabelStackIndex Read-only. Value is set to 0 because XCLabelStack is unsupported.

• mplsXCIsPersistent Read-only.

• mplsXCOwner Read-only. Other(1).

• mplsXCRowStatus Read-only.

• mplsXCStorageType Read-only.

• mplsXCAdminStatus Read-only. Always up(1).

• mplsXCOperStatus Always up(1).

• mplsOutSegmentIndexNext Read-only.

• mplsXCIndexNext, Read-only.

• mplsLabelStackIndexNext Read-only.

• mplsTrafficParamIndexNext Read-only.

mplsLabelStackTable Not supported.

mplsTrafficParamTable

• mplsInSegmentTrapEnable Read-only.

• mplsOutSegmentTrapEnable Read-only.

Table 3-40 MPLS-LSR-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsMPLS-TE-MIB

MPLS-TE-MIBThe 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/

• mplsXCTrapEnable Read-only.

• mplsXCUp *Not supported.

• mplsXCDown *Not supported.

• mplsInSegmentUp *Not supported.

• mplsInSegmentDown *Not supported.

• mplsOutSegmentUp *Not supported.

• mplsOutSegmentDown *Not supported.

* Not implemented due to scalability issues.

* mplsInterfaceConfTable—Provides information for each MPLS-capable interface on an LSR.

* mplsInterfacePerfTable—Augments the MPLS interface configuration table.* mplsInSegmentTable—Contains a description of incoming segments at an LSR and their associated parameters. Administrative and operational status objects for this table control packet transmission. If administrative and operational status objects are down, the LSR does not forward packets. If these status objects are up, the LSR forwards packets.

* mplsInSegmentPerfTable—Augments the MPLS in-segment table, providing performance information and counters for incoming segments on an LSR.

* mplsOutSegmentTable—Contains a description of outgoing segments from an LSR and their associated parameters. Administrative and operational status objects for this table control packet transmission. If administrative and operational status objects are down, the LSR does not forward packets. If these values are up, the LSR forwards packets.

* mplsOutSegmentPerfTable—Augments the MPLS out-segment table, providing performance information and counters for outgoing segments on an LSR.

* mplsXCTable—Associates inSegments (labels) to outSegments (labels) to show the manager how the LSR is currently swapping these labels. A row in this table consists of one cross-connect entry that is indexed by the cross-connect index, the interface index of the incoming segment, the incoming label, and the out-segment index. The administrative and operational objects for this table control packet forwarding to and from a cross-connect entry (XCEntry). The administrative status and operational status are always up in the Cisco implementation. Otherwise, the LSR would not forward packets.

Table 3-40 MPLS-LSR-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsMPLS-TE-MIB

MIB ConstraintsTable 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.

Table 3-41 MPLS-TE-MIB Constraints

MIB Object Notes

mplsTunnelIndexNext Always 0.

mplsTunnelTable

• mplsTunnelName Read-only.

• mplsTunnelDescr Read-only.

• mplsTunnelIsIf Read-only.

• mplsTunnelXCPointer Read-only.

• mplsTunnelSignallingProto Read-only.

• mplsTunnelSetupPrio Read-only.

• mplsTunnelHoldingPrio Read-only.

• mplsTunnelSessionAttributes Read-only.

• mplsTunnelOwner Read-only.

• mplsTunnelLocalProtectInUse Read-only. Always false(2).

• mplsTunnelResourcePointer Read-only.

• mplsTunnelInstancePriority Read-only. Always 0.

• mplsTunnelHopTableIndex Read-only.

• mplsTunnelIncludeAnyAffinity Read-only. Always 0.

• mplsTunnelIncludeAllAffinity Read-only.

• mplsTunnelExcludeAllAffinity Read-only.

• mplsTunnelPathInUse Read-only.

• mplsTunnelRole Read-only.

• mplsTunnelTotalUpTime Read-only.

• mplsTunnelInstanceUpTime Read-only. Always 0.

• mplsTunnelAdminStatus Read-only.

• mplsTunnelRowStatus Read-only. Always active(1).

• mplsTunnelStorageType Read-only. Volatile(2). Always active.

Note: No constraints on other table objects.

mplsTunnelHopListIndexNext Read-only. Always 0.

mplsTunnelHopTable

• mplsTunnelHopAddrType Read-only.

• mplsTunnelHopIpv4Addr Read-only.

• mplsTunnelHopIpv4PrefixLen Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsMPLS-VPN-MIB

MPLS-VPN-MIBThe 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/

• mplsTunnelHopIpv6Addr Read-only.

• mplsTunnelHopIpv6PrefixLen Read-only.

• mplsTunnelHopAsNumber Read-only.

• mplsTunnelHopLspId Read-only.

• mplsTunnelHopType Read-only.

• mplsTunnelHopRowStatus Read-only. Always active(1).

• mplsTunnelHopStorageType Read-only. Volatile(2). Always active.

mplsTunnelResourceIndexNext Read-only. Always 0.

mplsTunnelResourceTable

• mplsTunnelResourceMaxRate Read-only.

• mplsTunnelResourceMeanRate Read-only.

• mplsTunnelResourceMaxBurstSize Read-only.

• mplsTunnelResourceRowStatus Read-only. Always active(1).

• mplsTunnelResourceStorageType Read-only. Volatile(2). Always active.

Table 3-41 MPLS-TE-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

Chapter 3 MIB SpecificationsMPLS-VPN-MIB

MIB ConstraintsTable 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.

Table 3-42 MPLS-VPN-MIB Constraints

MIB Object Notes

MplsNumVrfSecViolationThreshExceeded Not supported.

mplsVpnVrfSecTable

• MplsVpnVrfSecIllegalLabelViolations Read-only. Always 0.

• MplsVpnVrfSecIllegalLabelRcvThresh Read-only. Always 0.

mplsVpnVrfTable

• MplsVpnVrfConfRowStatus Read-only.

• MplsVpnVrfConfStorageType Read-only. Volatile(2).

• MplsVpnVrfConfMidRouteThreshold Read-only.

• MplsVpnVrfConfHighRouteThreshold Read-only

• MplsVpnVrfConfMaxRoutes Read-only

• MplsVpnVrfConfMaxPossibleRoutes Read-only. Always 0.

• MplsVpnVrfDescription Read-only

• MplsVpnInterfaceVpnClassification Read-only

mplsVpnInterfaceConfTable

• MplsVpnInterfaceConfStorageType Read-only. Volatile(2).

• MplsVpnInterfaceConfRowStatus Read-only.

Values: active(1), notInService(2).

• MplsVpnInterfaceLabelEdgeType Read-only. providerEdge(1).

mplsVpnVrfRouteTargetTable

• MplsVpnVrfRouteTargetRowStatus Read-only. Values: active(1), notInService(2).

mplsVpnVrfBgpNbrAddrTable

• MplsVpnVrfBgpNbrRowStatus Read-only. Values: active(1), notInService(2).

• MplsVpnVrfBgpNbrRole Read-only. providerEdge(1).

• MplsVpnVrfBgpNbrType Read-only.

• MplsVpnVrfBgpNbrAddr Read-only.

• MplsVpnVrfBgpNbrStorageType Read-only. Volatile(2).

mplsVpnVrfRouteTable

• MplsVpnVrfRouteInfo Read-only. Value zero length string OID.

• MplsVpnVrfRouteTarget Read-only. Determines the route distinguisher for this target.


OL-6384-04

Chapter 3 MIB SpecificationsMSDP-MIB

MSDP-MIBThe 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

NOTIFICATION-LOG-MIB (RFC 3014)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.

• MplsVpnVrfRouteTargetDescr Description of the route target. This object is not supported in this Cisco IOS release. Therefore, the object is the same as mplsVpnVrfRouteTarget.

• MplsVpnVrfRouteDistinguisher Read-only.

• MplsVpnVrfRouteNextHopAS Read-only. Value always 0.

• MplsVpnVrfRouteRowStatus Read-only. This object normally reads active(1), but may read notInService(2), if a VRF was recently deleted.

• MplsVpnVrfRouteStorageType Read-only. Volatile(2).

• MplsVpnVrfRouteDestAddrType Read-only.

• MplsVpnVrfRouteMaskAddrType Read-only.

• MplsVpnVrfRouteTos Read-only. Value always 0.

• MplsVpnVrfRouteNextHop Read-only.

• MplsVpnVrfRouteNextHopAddrType Read-only.

• MplsVpnVrfRouteIfIndex Read-only.

• MplsVpnVrfRouteType Read-only.

• MplsVpnVrfRouteProto Read-only.

mplsVpnVrfBgpNbrPrefixTable Not supported.

The mplsVpnVrfConfTable represents all the MPLS/BGP VPNs configured. The NMS configures an entry in this table for each MPLS/BGP VPN configured to run in this MPLS domain. The mplsVPNInterfaceConfTable extends the interface MIB to provide specific MPLS/BGP VPN information on MPLS/BGP VPN-enabled interfaces. The mplsVPNPerfTable enhances the mplsVpnVrfConfTable to provide performance information.

The mplsVpnVrfRouteTable and the mplsVpnRouteTargetTable facilitate the configuration and monitoring of routes and route targets, respectively, for each VRF instance.

Table 3-42 MPLS-VPN-MIB Constraints (continued)

MIB Object Notes


OL-6384-04

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5msdp.html

Chapter 3 MIB SpecificationsNOVELL-IPX-MIB

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.

NOVELL-IPX-MIBThe 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.

NOVELL-RIPSAP-MIBThe 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.

OLD-CISCO-APPLETALK-MIBThe OLD-CISCO-APPLETALK-MIB provides information about Appletalk traffic on the router.

OLD-CISCO-CHASSIS-MIBThe 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.


OL-6384-04

Chapter 3 MIB SpecificationsOLD-CISCO-CPU-MIB

MIB ConstraintsThe 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.

OLD-CISCO-CPU-MIBThe OLD-CISCO-CPU-MIB describes CPU usage and active system processes on devices running an earlier implementation of the Cisco IOS operating system.

OLD-CISCO-DECNET-MIBThe 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.

OLD-CISCO-INTERFACES-MIBThe OLD-CISCO-INTERFACES-MIB contains objects to manage interfaces on devices running an earlier implementation of the Cisco IOS operating system.

OLD-CISCO-IP-MIBThe OLD-CISCO-IP-MIB contains objects to manage IP on devices running an earlier implementation of the Cisco IOS operating system.

Table 3-43 OLD-CISCO-CHASSIS-MIB Constraints for Port Adapters

MIB Object Notes

cardTable

• cardType The following values are used for 7200 router cards:

Module or Port Adapter cardType Value

PA-A3-T3—pa-atmdx-ds3(406) PA-A3-E3—pa-atmdx-e3(407)

• cardOperStatus Port adapter status matches module status.

cardIfIndexTable Used for port adapters only.


OL-6384-04

Chapter 3 MIB SpecificationsOLD-CISCO-MEMORY-MIB

MIB ConstraintsTable 3-44 lists the constraints that the router places on objects in the MIB. For detailed definitions of MIB objects, see the MIB.

OLD-CISCO-MEMORY-MIBThe OLD-CISCO-MEMORY-MIB contains objects that describe memory pools on devices running an earlier implementation of the Cisco IOS operating system.

OLD-CISCO-NOVELL-MIBThe OLD-CISCO-NOVELL-MIB provides information about Novell traffic on the router, including packet counts and IPX accounting and checkpoint accounting information.

OLD-CISCO-SYSTEM-MIBThe 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.

OLD-CISCO-TCP-MIBStarting 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.

OLD-CISCO-TS-MIBThe OLD-CISCO-TS-MIB provides information about the number of terminal lines and virtual lines on this device.

Table 3-44 OLD-CISCO-IP-MIB Constraints for Port Adapters

MIB Object Notes

lipCkAccountingTable Deprecated.

lipAccountingTable Deprecated.

lipRouteTable Deprecated.


OL-6384-04

Chapter 3 MIB SpecificationsPIM-MIB

PIM-MIBThe PIM-MIB contains objects to configure and manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.

MIB ConstraintsTable 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.

RFC1213-MIBThe RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets.

RFC1243-MIBThe 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.

MIB ConstraintsTable 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.

Table 3-45 PIM-MIB Object or Table Constraints

MIB Object Notes

pimInterfaceTable Read-only.

pimComponentTable Read-only.

pimCandidateRPTable Read-only.

pimRPTable Deprecated.

Table 3-46 RFC1243-MIB Object or Table Constraints

MIB Object Notes

atportTable

• atportType Read-only.

• atportNetStart Read-only.

• atportNetEnd Read-only.

• atportNetAddress Read-only.

• atportStatus Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsRFC1253-MIB

RFC1253-MIBThe RFC1253-MIB contains objects to manage Version 2 of the Open Shortest Path First (OSPF) protocol.

RFC1315-MIBThe 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

MIB ConstraintsTable 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.

• atportZone Read-only.

• atportIfIndex Read-only.

Table 3-46 RFC1243-MIB Object or Table Constraints (continued)

MIB Object Notes


MIB Object Notes

frDlcmiTable

• frDlcmiAddressLen Read-only.

• frDlcmiMaxSupportedVCs Read-only.

frCircuitTable

• frCircuitState Read-only.

• frCircuitCommittedBurst Read-only.

• frCircuitExcessBurst Read-only.

• frCircuitThroughput Read-only.

frTErrable

• frErrIfIndex Read-only.

• frErrType Read-only.

• frErrData Read-only.

• frErrTime Read-only.


OL-6384-04


RFC1315-MIBThe 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

MIB ConstraintsTable 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.


MIB Object Notes

frDlcmiTable

• frDlcmiAddressLen Read-only.

• frDlcmiMaxSupportedVCs Read-only.

frCircuitTable

• frCircuitCommittedBurst Normally, the QoS configuration entered through the Modular QoS CLI (MQC) syntax does not appear in these frCircuitTable objects.

However, when QoS is configured through the MQC and the following conditions are met, these frCircuitTable objects contain the QoS values as they are entered through the MQC:

• The default class is configured on the policy-map only.

• An output policy is attached to the Frame Relay (FR) Permanent Virtual Circuit (PVC).

• The Cisco-class-based-QoS (CBQ) enhancement only supports two MQC actions: police cir and shape.

• If both police cir and shape actions exist, then the FR traffic-shaping

• frCircuitExcessBurst

• frCircuitThroughput

• frCircuitState Read-only.

frTErrable

• frErrIfIndex Read-only.

• frErrType Read-only.

• frErrData Read-only.

• frErrTime Read-only.


OL-6384-04


RFC1381-MIBThe RFC1381-MIB (LAPB MIB file) was extracted from RFC 1381. The LAPB administration table contains objects that can manage a LAPB interface.

RFC1382-MIBThe 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.

DS1-MIB (RFC2495)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.

DS3-MIB (RFC2496)The DS3-MIB defined by RFC2496 provides access to configuration and performance monitoring information for DS3 controllers and interfaces.

RFC2006-MIBThe RFC2006-MIB is the MIB module for the Mobile IP.


OL-6384-04

Chapter 3 MIB SpecificationsRMON-MIB

RMON-MIBThe RMON-MIB contains objects to remotely monitor devices in the network. Supports MIB version RFC 1757.

MIB ConstraintsTable 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.

Table 3-49 RMON-MIB Constraints

MIB Object Notes

hostTopNControlTable

• hostTopNHostIndex Range {1 65535}

• hostTopNRateBase Range {1 11}

• hostTopNRequestedSize Range {0 2147483647}

• hostTopNTimeRemaining Range {0 2147483647}

channelTable

• channelIfIndex Range {1 65535}

• alarmInterval Range {1 2147483647}

rmonEtherStatsGroup

• etherStatsOwner Range {0 127}

• historyControlOwner Range {0 127}

• hostControlOwner Range {0 127}

• hostTopNOwner Range {0 127}

• matrixControlOwner Range {0 127}

• channelOwner Range {0 127}

rmonEventGroup

• eventCommunity Range {0 127}

• filterOwner Range "{0 127}

• bufferControlOwner Range {0 127}

• alarmOwner Range {0 127}

• eventOwner Range {0 127}

filterTable

• filterPktData Range {0 255}

• filterPktDataMask Range {0 255}

• filterPktDataNotMask Range {0 255}


OL-6384-04

Chapter 3 MIB SpecificationsRMON2-MIB

RMON2-MIBThe 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.

RS-232-MIBThe RS232-MIB contains objects to manage RS-232-like hardware interfaces and devices.

RSVP-MIBThe RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP).

MIB ConstraintsTable 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.

SMON-MIBThe 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

SNA-SDLC-MIBThe SNA-SDLC-MIB contains objects that manage SDLC (synchronous data link control) devices.

Table 3-50 RSVP-MIB Constraints

MIB Object Notes

rsvpObjectsTable

• rsvpSessionNewIndex Read-only.

• rsvpSenderNewIndex Read-only.

• rsvpResvNewIndex Read-only.

• rsvpResvFwdNewIndex Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsSNMP-FRAMEWORK-MIB

SNMP-FRAMEWORK-MIBThe SNMP-FRAMEWORK-MIB (RFC 2571) contains objects that describe the SNMP management architecture.


SNMP-NOTIFICATION-MIBThe 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.

SNMP-PROXY-MIBThe 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.

SNMP-TARGET-MIBThe 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.

SNMP-USM-MIBThe SNMP-USM-MIB (RFC 2574) contains objects that describe the SNMP User-based Security Model. There are no constraints on this MIB.


OL-6384-04

Chapter 3 MIB SpecificationsSNMP-VACM-MIB

SNMP-VACM-MIBThe 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

MIB ConstraintsTable 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.

SNMPv2-MIBThe 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.

Table 3-51 SNMP-VACM-MIB Constraints

MIB Object Notes

vacmBasicGroup

• vacmViewSpinLock Read-only.


OL-6384-04

Chapter 3 MIB SpecificationsSONET-MIB

SONET-MIBThe SONET-MIB provides both configuration and performance monitoring objects for SONET interfaces.

MIB ConstraintsTable 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.

SOURCE-ROUTING-MIBThe 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.

TCP-MIBThe TCP-MIB (RFC 2012) contains objects to manage the Transmission Control Protocol (TCP) implementations on the router. There are no constraints.

UDP-MIBThe UDP-MIB (RFC 2013) contains objects to manage the User Datagram Protocol (UDP) on the router. There are no constraints.

Table 3-52 SONET-MIB Constraints

MIB Object Notes

sonetPathCurrentTable

• sonetPathCurrentStatus Range {1 62}


OL-6384-04

Chapter 3 MIB SpecificationsUDP-MIB


OL-6384-04

OL-6384-04

C H A P T E R 4
Monitoring Notifications
This chapter describes the Cisco 7200 router notifications supported by the MIB enhancements feature introduced in Cisco IOS Release 12.2SB REL4. SNMP uses notifications to report events on a managed device. The notifications are traps or informs for different events. The router also supports other notifications not listed.

Note Many commands use the keyword traps in the command syntax. The keyword traps refers to notifications that are either traps, informs, or both. The tables in this chapter use the term traps even though the event might be an inform.

This chapter contains the following sections:

• Notification Overview, page 4-1

• Enabling Notifications, page 4-2

• Cisco SNMP Notifications, page 4-3

Notification OverviewAn SNMP agent can notify the manager when important system events occur, such as the following:

• An interface or card starts or stops running

• Temperature thresholds are crossed

• Authentication failures occur

When an agent detects an alarm condition, the agent:

• Logs information about the time, type, and severity of the condition

• Generates a notification message, which it then sends to a designated IP host

SNMP notifications are sent as either:

• Traps—Unreliable messages, which do not require receipt acknowledgement from the SNMP manager.

• Informs—Reliable messages, which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.

To use SNMP notifications on your system, you must specify trap recipients. These recipients indicate where Network Registrar notifications are directed. By default, all notifications are enabled, but no trap recipients are defined. Until you define the recipients, no notifications are sent.


Chapter 4 Monitoring NotificationsEnabling Notifications

Many commands use the word traps in the command syntax. Unless there is an option in the command to select either traps or informs, the keyword traps refers to either traps, informs, or both. Use the snmp-server host command to specify whether to send SNMP notifications as traps or informs. The types of traps can be specified in both commands.

Note Most notification types are disabled by default. However, some notification types cannot be controlled with the snmp command. For example, some notification types are always enabled and other types are enabled by a different command. The linkUpDown notifications are controlled by the snmp trap link-status command. If you enter this command with no notification-type keywords, the default is to enable all notification types controlled by this command.

Specify the trap types if you don't want all traps to be sent. Then use multiple snmp-server enable traps commands, one for each of the trap types that you used in the snmp host command. The Event Table must have an entry that specifies the action that is to be performed.

For detailed information about notifications and a list of notification types, go to the following URLs:

• http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_1/

• http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008021de3e.shtml

• http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf014.html

Enabling NotificationsYou can enable MIB notifications using either of the following procedures:

Command line interface (CLI)—Specify the recipient of the trap message and specify the types of traps sent. This command also specifies which types of informs are enabled.

• For detailed procedures, go to:

– http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008021de3e.shtml

– http://www.cisco.com/en/US/docs/ios/11_3/feature/guide/snmpinfm.html

• Performing an SNMP SET operation using the setany command— To enable or disable MIB notifications, perform an SNMP SET operation on the a specific object.

– To enable the notifications set the object to true(1)

– To disable the notifications, set the object to false(2)

Foe detailed procedures, go to:

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/catos/6.x/configuration/guide/snmp.html

Note If you issue the snmp-server enable traps command without a notification-type argument, the router generates traps for all types of events, which might not be desirable. Some MIBs require the user to set additional objects to enable some notifications.


OL-6384-04

http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_1

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008021de3e.shtml

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf014.html

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a008021de3e.shtml

http://www.cisco.com/en/US/docs/ios/11_3/feature/guide/snmpinfm.html

Chapter 4 Monitoring NotificationsCisco SNMP Notifications

Cisco SNMP NotificationsThis section contains tables that describe a MIB event, why the event occurred, and a recommendation as to how to handle the event. Each table lists the following information:

• Text string—The event display

• Brief description—What the event indicates

• Probable cause—What might have caused the notification

• Recommended action—Recommendation as to what should be done when the particular notification occurs

Note In the following tables, where no action required is documented, there might be instances where an application, such as trouble ticketing (An application that processes certain alarms and generates a ticket for a person or a system to manage before that ticket closes for some event.) occurs. For example, if a field replaceable unit (FRU) is replaced, then a message must be sent to close the trouble ticket according to operations and processes installed in your system.

Environmental or Functional NotificationsTable 4-1 lists notifications generated for events that might indicate the failure of the Cisco 7200 router or conditions that might affect the router’s functionality.

Table 4-1 Environmental Notifications

Event Description Probable Cause Recommended Action

cefcModuleStatusChange Indicates that the status of a module has changed.

Module has unknown state Enter the show module command to view error message details. For Syslog messages associated with this event, consult Messages and Recovery Procedures.

Module is operational No action is required.

Module has failed due to some condition

Enter the show module command to view error message details. For Syslog messages associated with this event, consult Messages and Recovery Procedures.

cefcPowerStatusChange Indicates that the power status of a field replaceable unit has changed.

FRU is powered off because of an unknown problem.

Enter the show power command to check the actual power usage.For Syslog messages associated with this event, consult Messages and Recovery Procedures

FRU is powered on No action is required.

FRU is administratively off No action is required.


OL-6384-04


FRU is powered off because available system power is insufficient

Enter the show power command to check the actual power usage.

cefcFRUInserted Indicates that a FRU was inserted.

A new field replaceable unit like a GBIC, fan, port, power supply, or redundant power supply was added.

No action is required.

cefcFRURemoved Indicates that a FRU was removed.

A field replaceable unit like GBIC, fan, ports, power supply, or redundant power supply was removed.

Replace the field replaceable unit.

chassisAlarmOn Indicates that a FRU status has changed. The chassisTempAlarm, chassisMinorAlarm, or chassisMajorAlarm object in this MIB has changed to the on (2) state.

The chassis temperature is too high, a minor or major alarm has been detected.

Inspect the indicated component closely to determine why it is operating out of the normal operating temperature range and whether it will eventually exceed the allowed operating temperature range.

A redundant power supply has been powered off.

Replace the FRU.

One or more fans in the system fan tray have failed. Although this is a minor alarm, system components could overheat and be shut down.

Replace the system fan tray.

chassisAlarmOff Indicates that a FRU status has changed. The chassisTempAlarm, chassisMinorAlarm, or chassisMajorAlarm object in this MIB has changed to the off (1) state.

A redundant power supply has been powered on.

No action required.

cefcMIBEnableStatusNotification Operational status changed. Indicates whether the system produces the cefcMIBNotifications.

Table 4-1 Environmental Notifications (continued)



OL-6384-04


Cisco 7200 Port Adapter NotificationsTable 4-2 lists notifications generated by Cisco 7200 router port adapters (PA). These traps indicate the failure of a port adapter or error conditions on the PA card that might affect the functionality of all interfaces and connected customers. All of the sensors generate traps if the voltage passes the threshold level.

Table 4-2 Cisco 7200 Port Adapter Notifications


entConfigChange There has been an informational configuration change.

An entry for the card is removed from the entPhysicalTable (which causes the value of entLastchangeTime to change).

A card was removed. Replace the field replaceable unit.

A PA card was added. No action required.

A PA card operational status change occurred.

No action required.

entSensorThresholdNotification Indicates that the sensor value crossed the threshold listed in entSensorThresholdTable. This variable reports the most recent measurement seen by the sensor and This variable indicates the value of the threshold.

A specific module exceeded major sensor thresholds.

Remove the configuration that bypasses the module shutdown due to sensor thresholds being exceeded. Shut down the module after removing the configuration. It exceeded major sensor thresholds. The command that shuts down the module in the event of a major sensor alarm has been overridden, so the specified module will not be shut down. The command used to override the shutdown is no environment-monitor shutdown.

ceAlarmAsserted Sent when the alarm Card Stopped Responding OIR is asserted.

You manually shut down the PA card, then you get the error.

ceAlarmCleared A previously asserted alarm is cleared.

The agent generates this trap when a physical entity clears a previously asserted alarm.


OL-6384-04


Interface NotificationsTable 4-3 lists IF-MIB notifications generated by the router for link-related (interface) events.

Table 4-3 Link Notifications


linkDown An interface is down. This is cleared by one or more Link Up traps for the same interface

It can not transmit or receive traffic. The ifOperStatus object shows the link’s previous state. Value is down(2).

To see if link traps are enabled or disabled on an interface, check ifLinkUpDownTrapEnable (IF-MIB) for the interface. To enable link traps, set ifLinkUpDownTrapEnable to enabled(1).

Enable the IETF (RFC 2233) format of link traps by issuing the CLI command snmp-server trap link ietf.

linkUp An interface is now up after being down.

Indicates that a link’s status is no longer down. The value of ifOperStatus indicates the link’s new state. Value is up(1).

The port manager reactivated a port in the link-down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisor engines.



OL-6384-04


Threshold NotificationsTable 4-4 lists MPLS-VPN-MIB notifications which are traps and informs that can occur when an environmental threshold is exceeded. Indicates that a threshold violation occurred.

Table 4-4 MPLS-VPN Notifications


mplsNumVrfRouteMidThreshExceeded Indicates that the warning threshold is exceeded.

The system limit of four route processors per VPN has been exceeded. The number of routes created has crossed the warning threshold. This warning is sent only at the time the warning threshold is exceeded.

The configured RPs are too large to fit in the DF table for one VPN. Try to configure the groups among existing RPs in the hardware, or configure the RP in another VPN.

mplsNumVrfRouteMaxThreshExceeded Indicates that the maximum route limit was reached.

A route creation was unsuccessful because the maximum route limit was reached. Another notification is not sent until the number of routes falls below the maximum threshold and reaches the maximum threshold again.

Set the threshold value. The max-threshold value is determined by the maximum routes command in VRF configuration mode.

mplsLdpFailedInitSessionThreshold Exceeded

Indicates that a local LSR and an adjacent LDP peer attempt to set up an LDP session between them, but fail to do so after a specified number of attempts.

Eight failed attempts occurred to establish an LDP session between a local LSR and an LDP peer, due to some type of incompatibility between the devices.

Cisco routers support the same features across multiple platforms. Therefore, the most likely incompatibility to occur between Cisco LSRs is a mismatch of their respective ATM VPI/VCI label ranges.

If you specify a range of valid labels for an LSR that does not overlap the range of its adjacent LDP peer, the routers will try eight times to create an LDP session between themselves before the mplsLdpFailedInitSessionThresholdExceedednotification is generated and sent to the NMS as an informational message.

Operationally, the LSRs whose label ranges do not overlap continue their attempt to create an LDP session between themselves after the eight retry threshold is exceeded.

In such cases, the LDP threshold exceeded notification alerts the network administrator to the existence of a condition in the network that may warrant attention.


OL-6384-04


Service NotificationsTable 4-5 lists MPLS service notifications (MPLS-TE-MIB, MPLS-LDP-MIB,MPLS-VPN-MIB) which generated by the router to indicate conditions for services.

Table 4-5 MPLS-Service Notifications


mplsVrfIfUp Indicates that a VPN routing or forwarding instance (VRF) was assigned to an interface that is operational or for the transition of a VRF interface to the operationally up state.

A VPN routing or forwarding instance (VRF) was assigned to an interface that is operational or a VRF interface transitions to the up state.


mplsVrfIfDown, Indicates that a VRF was removed from an interface or a VRF interface transitioned to the operationally up state.

A VRF was removed from an interface or a VRF of an interface transitioned to the down state.

Check the operation state of the interface OR the state of the connected interface on the adjacent router OR add the removed VRF.

mplsLdpSessionUp Indicates that the MPLS LDP session is in the up state.

Trap generated when an LDP entity (a local LSR) establishes an LDP session with another LDP entity (an adjacent LDP peer in the network).


mplsLdpSessionDown Indicates that the MPLS LDP session is in the down state.

Trap generated when an LDP session between a local LSR and its adjacent LDP peer is terminated.

Check if the LDP session exists between the local LSR and adjacent LDP peer.

mplsLdpPVLMismatch Indicates that a local LSR establishes an LDP session with its adjacent peer LSR, but the two LSRs have dissimilar path vector limits.

An LDP session has two adjacent peer LSRs with dissimilar path vector limits.

The value of the path vector limit can range from 0 through 255; a value of “0” indicates that loop detection is off; any value other than zero up to 255 indicates that loop detection is on.

Configure all LDP-enabled routers in the network with the same path vector limit. Accordingly, the mplsLdpPathVectorLimitMismatch object exists in the MPLS LDP MIB to provide a warning message to the NMS when two routers engaged in LDP operations have a dissimilar path vector limit.

mplsTunnelUp Indicates that a mplsTunnelOperStatus object for a configured tunnel is about to transition from the Down state to any state except NotPresent.

A configured tunnel transitioned from the Down state to any state except NotPresent.

May be caused by an administrative or operational status check of the tunnel.



OL-6384-04


Routing Protocol NotificationsTable 4-6 lists BGP4-MIB notifications generated by the Cisco 7200 router to indicate error conditions for routing protocols and services.

mplsTunnelDown Indicates that the mplsTunnelOperStatus object for a configured MPLS traffic engineering tunnel is about to transition to the up(1) or the down(2) respectively.

A configured tunnel is transitioning to the down state.

May be caused by an administrative or operational status check of the tunnel.

To see the operational status of the tunnel.

mplsTunnelRerouted Indicates that the signalling path for an MPLS traffic engineering tunnel changed.

A tunnel was rerouted or reoptimized.

If you use the actual path, then write the new path to mplsTunnelRerouted after the notification is issued.

Table 4-5 MPLS-Service Notifications (continued)


Table 4-6 Routing Protocol Notifications


bgpEstablished Indicates that the BGP protocol becomes active on the router (it enters the Established state).

The BGP routing protocol changed status.


bgpBackwardTransition Indicates that the BGP protocol transitions from a higher-level state to a lower-level state.

The BGP routing protocol changed status.


OL-6384-04


RTT Monitor NotificationsTable 4-7 lists CISCO-RTTMON-MIB notifications that can occur during round-trip time (RTT) monitoring.

Table 4-7 RTT Monitor Notifications


rttMonConnectionChangeNotification Sent when the value of rttMonCtrlOperConnectionLostOccurred changes.

Occurs when the connection to a target has either failed to be established or was lost and then re-established.

Check for the connectivity to the target. There could be link problems to the target through different hops.

rttMonTimeoutNotification A timeout occurred or was cleared.

An RTT probe occurred and the system sends the notice when the value of rttMonCtrlOperTimeoutOccurred changes.

Check for the end-to-end connectivity if rttMonCtrlOperTimeoutOccurred if the notification returns true.

No action is required if rttMonCtrlOperTimeoutOccurred is false.

rttMonThresholdNotification Threshold violation occurred.

An RTT probe occurred or a previous violation has subsided in a subsequent RTT operation.

Check for the end-to-end connectivity if rttMonCtrlOperOverThresholdOccurred in the notification is true otherwise no action required.


OL-6384-04


Environmental NotificationsTable 4-8 lists CISCO-ENVMON-MIB notifications generated for events that might indicate the failure of the Cisco 7200 router or conditions that might affect the router’s functionality.

Table 4-8 Environmental Notifications


ciscoEnvMonShutdownNotification Indicates a status change or failure. Critical condition. Shutdown imminent.

A test point nears a critical state and the router is about to shut down (for example, if auto-shutdown is enabled and the chassis core or inlet temperature reaches critical state and remains there for more than 2 minutes).

This message indicates that the system has a configuration to shut down a module if its operating temperature exceeds a temperature threshold. This configuration has been bypassed, and a module will still operate in an over-temperature condition. Operating at an over-temperature condition can damage the hardware.

Do not override the sensor alarms that act on an over-temperature condition. Enter the environment-monitor shutdown temperature command to bring the system back to standard temperature detection.

ciscoEnvMonRedundantSupplyNotification Sent if the redundant power supply (if available) fails.

An environmental condition, an over-temperature condition, or inconsistent voltage to the module occurred. Since such a notification is usually generated before the shutdown state is reached, it can convey more data and has a better chance of being sent than does the ciscoEnvMonShutdownNotification.

Ensure that the system power supplies are optimally redundant. Use power supplies with identical output ratings or reduce system power consumption.


OL-6384-04


ciscoEnvMonTemperatureNotification The core or inlet temperature is outside its normal range, when ciscoEnvMonState is at the Warning or Critical state.

During previous reloads, this module experienced a timeout while accessing the temperature sensor. All further access to the temperature sensor will be disabled. This condition indicates a possible problem with the temperature sensor.

Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

1 The cefcFRUPowerAdminStatus is on(1) when a power supply is disabled. When there is a power supply, the cefcFRUPowerAdminStatus is always on(1) for both power supplies, regardless if the power supply is disabled.

2 ENVON-MIB traps occur; but they are not supported.

3 To enable and disable CISCO-ENTITY-FRU-CONTROL MIB traps, use the <no> snmp-server enable trap fru-ctrl CLI command.

Table 4-8 Environmental Notifications (continued)



OL-6384-04

OL-6384-04

A
P P E N D I X A Using MIBs
This chapter describes how to perform tasks on the Cisco 7200 Router.

• Managing Router Physical Entities, page A-1

• Mapping Information for ENTITY-MIB, page A-2

• Generating SNMP Traps, page A-10

• Monitoring Router Interfaces, page A-12

• Monitoring Quality of Service, page A-13

• Billing Customers for Traffic, page A-22

• Using CISCO-AAA-SESSION-MIB

Managing Router Physical EntitiesThe physical entity management feature of the Cisco 7200 SNMP implementation:

• Monitors and configures the status of field replaceable units (FRUs)

• Provides information about physical port to interface mappings

• Provides firmware and software information for chassis components

The entPhysicalTable enumerates the physical entities contained by the system. In addition, it classifies each physical entity into a vendor type and class.

Note The sample outputs and values that appear throughout this chapter are only examples of what you can view when using MIBs.

A-1Cisco 7200 Router MIB Specifications Guide

Appendix A Using MIBsMapping Information for ENTITY-MIB

Mapping Information for ENTITY-MIB

Physical Entity Management MIBsThe following MIBs are used to manage physical entities on the Cisco 7200:

• CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (ID PROM contents) for the physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.

• CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the administrative and operational status of field replaceable units (FRUs), such as power supplies that are listed in the entPhysicalTable of the ENTITY-MIB.

• CISCO-ENTITY-VENDORTYPE-OID-MIB—Contains the object identifiers (OIDs) for all physical entities in the router in the entPhysicalTable.

• CISCO-ENVMON-MIB—Contains information about the status of environmental sensors. For example, the MIB reports the chassis core inlet temperatures.

• ENTITY-MIB—Contains information for managing physical entities on the router. It also organizes the physical entities contained by a system into a tree, referred to as a containment tree. This tree describes the relationship of each physical entity to all others. The ENTITY-MIB contains the following tables:

– The entPhysicalTable describes each physical component (entity) in the router. The table contains an entry for the top-level entity (the chassis) and for each entity in the chassis. Each entry provides information about that entity: its name, type, vendor, and a description, and describes how the entity fits into the hierarchy of chassis entities. Each entity is identified by a unique index (entPhysicalIndex) that is used to access information about the entity in this and other MIBs.

The entPhysicalTable which contains two managed objects that describe a physical entity’s relationship to its parent:

• entPhysicalContainedIn – this object specifies the entPhysicalIndex of the physical entity representing this physical entity’s parent; that is, the physical entity that contains this physical entity. For example, a physical entity representing a slot (within a chassis) typically contains a physical entity representing a card. The slot is the parent of the card.

• entPhysicalParentRelPos – this object specifies an integer value that represents this physical entity’s relationship relative to its parent. For example, a physical entity representing a slot will have an entPhysicalParentRelPos equal to the slot number of the physical slot it represents.

– The entPhysicalContainsTable, which lists the children of each physical entity contained by the system. This table provides the management client with another view of the parent-child relationship between physical entities.


OL-6384-04


Mapping OLD-CISCO-CHASSIS-MIB to ENTITY-MIBUse the ENTITY-MIB instead fo the OLD-CISCO-CHASSIS-MIB on the 7200 platform starting with the following releases:

• 12.3T

• 12.2SB

Serial numbers for the new port adapter hardware has been revised to be alphanumeric values instead of numeric values. As a result, all new hardware might display a zero (0) as cardSerial number in the OLD-CISCO-CHASSIS-MIB, including port adapters.

The key mappings for the OLD-CISCO-CHASSIS-MIB attributes are:

• CardType (integer value) -> entPhysicalVendorType (OID)

• cardSerial (integer value) -> entPhysicalSerialNum (String)

• cardSlotNumber -> entPhysicalContainedIn and entPhysicalParentRelPos

The difference between the ENTITY-MIB and the OLD-CISCO-CHASSIS-MIB is that the entity physical table in the ENTITY-MIB contains all physical entities supported in the router and the card table in the OLD-CISCO-CHASSIS-MIB only contains entries for the modules, such as the processor card and the port adapter which is in the router. The entity physical entry contains corresponding data for the cardType, cardSerial, and the cardSlotNumber objects which are in the card table entry of the OLD-CISCO-CHASSIS-MIB.

Entity Containment Tree

Each entity physical entry contains entPhysicalContainedIn and entPhysicalParentRelPos. The entire entity physical table represents a entity containment tree started from root, which is the chassis.

The following is a example of the entity containment tree for the C7200R which contains PA-A6-OC3MM in the PA slot 4. Each row has entPhysicalIndex, MIB variable, entPhysicalName, entPhysicalModelName, and entPhysicalVendorType (vendor OID) for the MIB variable.

Note Not all MIB objects in the entPhysicalentry are shown in this example.

Example A-1 Example of the Entity Containment Tree:

1 (cevChassis7204Vxr) : Chassis : CISCO7200 : 1.3.6.1.4.1.9.12.3.1.3.75 2 (cevContainerSlot) : I/O and CPU Slot 0 : {} : 1.3.6.1.4.1.9.12.3.1.5.1 7 (cevCpu7200Npeg1) : NPE-G1 0 : NPE-G1 : 1.3.6.1.4.1.9.12.3.1.9.5.56 other entities conatined under the NPE-G1…3 (cevContainerSlot) : PA Slot 1 : {} : 1.3.6.1.4.1.9.12.3.1.5.14 (cevContainerSlot) : PA Slot 2 : {} : 1.3.6.1.4.1.9.12.3.1.5.15 (cevContainerSlot) : PA Slot 3 : {} : 1.3.6.1.4.1.9.12.3.1.5.16 (cevContainerSlot) : PA Slot 4 : {} : 1.3.6.1.4.1.9.12.3.1.5.1 30 (cevPaA6mmOc3) : module 4 : PA-A6-OC3MM= : 1.3.6.1.4.1.9.12.3.1.9.4.106 other entities info (i.e port) contained under PA-A6…other entities contained under the CISCO7200…

Table A-1 lists the OLD-CISCO-CHASSIS-MIB variables and shows the equivalent MIB variable from the ENTITY-MIB and CISCO-ENTITY-EXT-MIB.


OL-6384-04


Table A-2 lists the OLD-CISCO-CHASSIS-MIB card variables and shows the equivalent MIB variable from the ENTITY-MIB.

Table A-1 MIB Containment Information

Variables OLD-CISCO-CHASSIS-MIB Equivalent MIB

Chassis cards

CardIndex entPhysicalIndex ENTITY-MIB

CardType entPhysicalVendorType ENTITY-MIB

CardDescr entPhysicalDescr ENTITY-MIB

CardSerial EntPhysicalSerialNum ENTITY-MIB

CardHwVersion entPhysicalHardwareRev ENTITY-MIB

CardSwVersion entPhysicalSoftwareRev ENTITY-MIB

CardSlotNumber

cardContainedByIndex entPhysicalContainedIn ENTITY-MIB

CardSlots

Chassis

ChassisId entPhysicalSerialNum ENTITY-MIB

ChassisType entPhysicalVendorType ENTITY-MIB

ChassisVersion entPhysicalVendorType ENTITY-MIB

RomVersion entPhysicalFirmwareRev ENTITY-MIB

RomSysVersion entPhysicalSoftwareRev ENTITY-MIB

ProcessorRam ceExtProcessorRam CISCO-ENTITY-EXT-MIB

NvRAMSize ceExtNVRAMSize CISCO-ENTITY-EXT-MIB

NvRAMUsed ceExtNVRAMUsed CISCO-ENTITY-EXT-MIB

ConfigRegister ceExtConfigRegister CISCO-ENTITY-EXT-MIB

configRegNext CeExtConfigRegNext CISCO-ENTITY-EXT-MIB

Table A-2 Interface Correlation for Chassis Cards

OLD-CISCO-CHASSIS-MIB Description Equivalent MIB

CardIfIndex ifIndex entAliasMappingIdentifier ENTITY-MIB

CardIfPortNumber To identify the ports corresponding to a card

ENTITY-MIB

CardIfCardIndex Used together with cardifindex for correlating cards with interface

entAliasMappingIdentifier ENTITY-MIB


OL-6384-04


Performing Inventory ManagementTo obtain information about a particular physical entity in the Cisco 7200 Router walk through the entPhysicalTable in the ENTITY-MIB. The entPhysicalDescr gives a textual description of the entity. Using the entPhysicalIndex that corresponds to the description of the entity, you can obtain other parameters.

Notes about entPhysicalTable Entries

As you examine entries in the ENTITY-MIB entPhysicalTable, consider the following:

• entPhysicalIndex—Uniquely identifies each entity in the chassis. This index is also used to access information about the entity in other MIBs.

• entPhysicalContainedIn—Indicates the entPhysicalIndex of a component’s parent entity.

• entPhysicalParentRelPos—Shows the relative position of same-type entities that have the same entPhysicalContainedIn value (for example, chassis slots).

Note The container is applicable if the physical entity class is capable of containing one or more removable physical entities. For example, each (empty or full) slot in a chassis will be modeled as a container. All removable physical entities should be modeled within a container entity, such as field-replaceable modules, fans, or power supplies.

The following output shows how the information from the MIB walk displays (this is only a section of the complete output):

entPhysicalDescr.1 = 7200 ChassisentPhysicalDescr.2 = Chassis SlotentPhysicalDescr.3 = Chassis SlotentPhysicalDescr.4 = Chassis SlotentPhysicalDescr.5 = Chassis SlotentPhysicalDescr.6 = Chassis SlotentPhysicalDescr.7 = Chassis SlotentPhysicalDescr.8 = Power Supply SlotentPhysicalDescr.9 = Power Supply SlotentPhysicalDescr.10 = Network Service Engine 100 CPU CardentPhysicalDescr.11 = Network Service Engine 100 Daughter CardentPhysicalDescr.12 = Mistral EOBCentPhysicalDescr.13 = GBIC Port ContainerentPhysicalDescr.14 = 1000BaseSXentPhysicalDescr.15 = Pinnacle GEentPhysicalVendorType.1 = cevChassis7200entPhysicalVendorType.2 = cevContainerSlotentPhysicalVendorType.3 = cevContainerSlotentPhysicalVendorType.4 = cevContainerSlotentPhysicalVendorType.5 = cevContainerSlotentPhysicalVendorType.6 = cevContainerSlotentPhysicalVendorType.7 = cevContainerSlotentPhysicalVendorType.8 = cevContainerC7200PowerSupplyBayentPhysicalVendorType.9 = cevContainerC7200PowerSupplyBayentPhysicalVendorType.10 = cevCpuC7200Nse100entPhysicalVendorType.11 = cevC7200Nse100DbentPhysicalVendorType.12 = cevPortFEIPentPhysicalVendorType.13 = cevContainerGbicentPhysicalVendorType.14 = cevMGBIC1000BaseSXentPhysicalVendorType.15 = cevPortGeentPhysicalContainedIn.1 = 0entPhysicalContainedIn.2 = 1


OL-6384-04


entPhysicalContainedIn.3 = 1entPhysicalContainedIn.4 = 1entPhysicalContainedIn.5 = 1entPhysicalContainedIn.6 = 1entPhysicalContainedIn.7 = 1entPhysicalContainedIn.8 = 1entPhysicalContainedIn.9 = 1entPhysicalContainedIn.10 = 2entPhysicalContainedIn.11 = 10entPhysicalContainedIn.12 = 10entPhysicalContainedIn.13 = 10entPhysicalContainedIn.14 = 13entPhysicalContainedIn.15 = 14...

Samples of ENTITY-MIB entPhysicalTable Entries

The output samples in this section show how information is stored in the entPhysicalTable. You can determine the Cisco 7200 Router configuration by examining entPhysicalTable entries. For example, the entPhysicalIndex = 1 corresponds to chassis type and the other information such as vendortype and physical class can be obtained by walking through the table.

Note The entPhysicalEntry.entPhysicalIndex uniquely identifies each entity in the chassis. Use this index to access information about the entity in other MIB tables.

entPhysicalTEntry.1entPhysicalDescr.1 = 7200 ChassisentPhysicalVendorType.1 = cevChassis7200entPhysicalContainedIn.1 = 0entPhysicalClass.1 = chassis(3)entPhysicalParentRelPos.1 = -1entPhysicalName.1 = 7200 ChassisentPhysicalHardwareRev.1 = EentPhysicalFirmwareRev.1 = entPhysicalSoftwareRev.1 = entPhysicalSerialNum.1 = SCA070400D8entPhysicalMfgName.1 = Cisco Systems IncentPhysicalModelName.1 = 73-5916-02entPhysicalAlias.1 = entPhysicalAssetID.1 = entPhysicalIsFRU.1 = true(1)...


OL-6384-04


Table A-3 describes the configuration information that you can obtain from the sample entPhysicalEntry output for entPhysicalEntry.1 and entPhysicalEntry.11.

Table A-3 entPhysicalEntry Configuration Information

entPhysicalTEntries entPhysicalTEntry Description

entPhysicalIndex = 1 Identifies the chassis type.

entPhysicalVendorType = cevChassis7200 An indication of the vendor-specific hardware type of the physical entity.

An agent should set this object to a enterprise-specific registration identifier value indicating the specific equipment type in detail. The associated instance of entPhysicalClass is used to indicate the general type of hardware device (autonomous type).

If no vendor-specific registration identifier exists for this physical entity or the value is unknown, then the value, 00, returns.

entPhysicalContainedIn = 0 An integer with a range value of 0 through 2147483647. The value of entPhysicalIndex for the physical entity which contains this physical entity.

The container is applicable if the physical entity class is capable of containing one or more removable physical entities, possibly of different types. For example, each (empty or full) slot in a chassis will be modeled as a container.

Note A value of zero indicates this physical entity is not contained in any other physical entity; therefore this is a chassis because the value is zero.

entPhysicalClass = chassis(3) An indication of the general hardware type, such as a chassis and a module, of the physical entity.

An agent should set this object to the standard enumeration value which most accurately indicates the general class of the physical entity or the primary class if there is more than one.

If no appropriate standard registration identifier exists for this physical entity, then the value other(1) is returned. If the value is unknown by this agent, then the value unknown(2) is returned.


OL-6384-04


entPhysicalParentRelPos = -1 An integer with a range value of -1 through 2147483647.

An indication of the relative position of this child component among all its sibling components. Sibling components are defined as entPhysicalEntries that share the same instance values of each of the entPhysicalContainedIn and entPhysicalClass objects.

This object identifies the relative ordering for all sibling components of a particular parent (identified by the entPhysicalContainedIn instance in each sibling entry). This value should match any external labeling of the physical component if possible.

entPhysicalName = 7200 Chassis The textual name of the physical entity. The value of this object should be the name of the component as assigned by the local device and should be suitable for use in commands entered at the device console. This might be a text name, such as `console' or a simple component number, for example, port or module number, such as 1, depending on the physical component naming syntax of the device.

If there is no local name, or this object is otherwise not applicable, then this object contains a zero-length string.

entPhysicalHardwareRev = E The vendor-specific hardware revision string for the physical entity. The preferred value is the hardware revision identifier actually printed on the component itself (if present).

entPhysicalFirmwareRev = The vendor-specific firmware revision string for the physical entity. If no specific firmware programs are associated with the physical component, or this information is unknown to the agent, then this object will contain a zero-length string.

entPhysicalSoftwareRev =<user input> The vendor-specific software revision string for the physical entity.

entPhysicalSerialNum = SCA070400D8 The vendor-specific serial number string for the physical entity.

entPhysicalMfgName = Cisco Systems Inc The name of the manufacturer of this physical component.

entPhysicalModelName = 73-5916-02 The vendor-specific model name identifier string associated with this physical component. The preferred value is the customer-visible part number, which may be printed on the component itself.

Table A-3 entPhysicalEntry Configuration Information (continued)



OL-6384-04


The following sample output illustrates a physical entity containment tree for a Cisco 7200 chassis containing a Cisco 7200 NSE-100 daughter card.

entPhysicalTEntry.11entPhysicalDescr.11 = Network Service Engine 100 Daughter CardentPhysicalVendorType.11 = cevC7200Nse100DbentPhysicalContainedIn.11 = 10entPhysicalClass.11 = module(9)entPhysicalParentRelPos.11 = 1entPhysicalName.11 = Network Service Engine 100 Daughter Card 0entPhysicalHardwareRev.11 = 5.0entPhysicalFirmwareRev.11 = entPhysicalSoftwareRev.11 =entPhysicalSerialNum.11 = CAT07050DSNentPhysicalMfgName.11 = Cisco Systems IncentPhysicalModelName.11 = 73-5673-07entPhysicalAlias.11 =entPhysicalAssetID.11 = entPhysicalIsFRU.11 = false(2)...

entPhysicalAlias = This object is an alias name for the physical entity as specified by a network manager, and provides a non-volatile handle for the physical entity.

On the first instantiation of an physical entity, the value of entPhysicalAlias associated with that entity is set to the zero-length string. However, agent may set the value to a locally unique default value, instead of a zero-length string.

entPhysicalAssetID = This object is a user-assigned asset tracking identifier for the physical entity as specified by a network manager, and provides non-volatile storage of this information.

On the first instantiation of an physical entity, the value of entPhysicalAssetID associated with that entity is set to the zero-length string.

entPhysicalIsFRU = true(1) This object indicates whether or not this physical entity is considered a field replaceable unit (FRU) by the vendor. This object contains the value true(1), therefore, this entPhysicalEntry identifies a field replaceable unit.

Note For all entPhysicalEntries which represent components that are permanently contained within a field replaceable unit, the value false(2) should be returned for this object.

Table A-3 entPhysicalEntry Configuration Information (continued)



OL-6384-04

Appendix A Using MIBsGenerating SNMP Traps

Monitoring and Configuring FRU StatusView objects in the CISCO-ENTITY-FRU-CONTROL-MIB cefcModuleTable to determine the administrative and operational status of field replaceable units (FRU), such as power supplies:

• cefcModuleAdminStatus—The administrative state of the FRU. Use cefcModuleAdminStatus to enable or disable the FRU.

• cefcModuleOperStatus—The current operational state of the FRU.

Note Currently, the CISCO-ENTITY-FRU-CONTROL-MIB supports Cisco 7200. For additional MIB constraints, see the “CISCO-ENTITY-FRU-CONTROL-MIB” section on page 3-20.

The following example shows a cefcModuleTable entry for a Cisco 7200 card whose entPhysicalIndex is 9.

cefcModuleAdminStatus.9 = enabled(1)cefcModuleOperStatus.9 = ok(2)cefcModuleResetReason.9 = powerUp(2)cefcModuleStatusLastChangeTime.9 = 3360

Generating SNMP TrapsThis section provides information about the SNMP traps generated in response to events and conditions on the router, and describes how to identify which hosts are to receive traps.

• Identifying Hosts to Receive Traps

• Configuration Changes

• Environmental Conditions

• FRU Status Changes

Identifying Hosts to Receive TrapsYou can use the CLI or SNMP to identify hosts to receive SNMP notifications and to specify the types of notifications they are to receive (traps or informs). For CLI instructions, see the “Enabling Notifications” section on page 4-2. To use SNMP to configure this information, use the following MIB objects:

Use SNMP-NOTIFICATION-MIB objects, including the following, to select target hosts and specify the types of notifications to generate for those hosts:

• snmpNotifyTable—Contains objects to select hosts and notification types:

– snmpNotifyTag is an arbitrary octet string (a tag value) used to identify the hosts to receive SNMP notifications. Information about target hosts is defined in the snmpTargetAddrTable (SNMP-TARGET-MIB), and each host has one or more tag values associated with it. If a host in snmpTargetAddrTable has a tag value that matches this snmpNotifyTag value, the host is selected to receive the types of notifications specified by snmpNotifyType.

– snmpNotifyType is the type of SNMP notification to send: trap(1) or inform(2).

• snmpNotifyFilterProfileTable and snmpNotifyFilterTable—Use objects in these tables to create notification filters to limit the types of notifications sent to target hosts.

Use SNMP-TARGET-MIB objects to configure information about the hosts to receive notifications:


OL-6384-04

Appendix A Using MIBsGenerating SNMP Traps

• snmpTargetAddrTable—Transport addresses of hosts to receive SNMP notifications. Each entry provides information about a host address, including a list of tag values:

– snmpTargetAddrTagList—A set of tag values associated with the host address. If a host’s tag value matches snmpNotifyTag, the host is selected to receive the types of notifications defined by snmpNotifyType.

• snmpTargetParamsTable—SNMP parameters to use when generating SNMP notifications.

Use the notification enable objects in appropriate MIBs to enable and disable specific SNMP traps. For example, to generate mplsLdpSessionUp or mplsLdpSessionDown traps, the MPLS-LDP-MIB object mplsLdpSessionUpDownTrapEnable must be set to enabled(1).

Configuration ChangesIf entity traps are enabled, the router generates an entConfigChange trap (ENTITY-MIB) when the information in any of the following tables changes (which indicates a change to the router configuration):

• entPhysicalTable

• entAliasMappingTable

• entPhysicalContainsTable

Note A management application that tracks configuration changes should occasionally check the value of entLastChangeTime (ENTITY-MIB) to detect any entConfigChange traps that were missed due to throttling or transmission loss.

Enabling Traps for Configuration Changes

To configure the router to generate an entConfigChange trap whenever its configuration changes, enter the following command from the CLI. Use the no form of the command to disable the traps.

Router(config)# snmp-server enable traps entity Router(config)# no snmp-server enable traps entity

Environmental ConditionsThe CISCO-ENVMON-MIB sends the following notifications to alert you to conditions detected by environmental sensors in the router:

• ciscoEnvMonShutdownNotification—Sent when the router is about to shut down.

• ciscoEnvMonTemperatureNotification—Sent when a temperature is outside its normal range.

• ciscoEnvMonRedundantSupplyNotification—Sent when a redundant Power Entry Module fails.

Enabling Environmental Traps

To configure the router to generate traps for environmental conditions, enter the following command from the CLI. Use the no form of the command to disable the traps.

Router(config)# snmp-server enable traps envmon Router(config)# no snmp-server enable traps envmon

To enable environmental traps through SNMP, set the appropriate notification enable object to true(1). For example, ciscoEnvMonEnableShutdownNotification enables shutdown notifications. Disable the traps by setting the notification object to false(2).


OL-6384-04

Appendix A Using MIBsMonitoring Router Interfaces

FRU Status ChangesIf FRU traps are enabled, the router generates the following traps in response to changes in the status of an FRU. See the CISCO-ENTITY-FRU-CONTROL-MIB for more information about these traps.

• cefcModuleStatusChange—The operational status (cefcModuleOperStatus) of an FRU changes.

• cefcFRUInserted—An FRU is inserted in the chassis. The trap indicates the entPhysicalIndex of the FRU and the container it was inserted in.

• cefcFRURemoved—An FRU is removed from the chassis. The trap indicates the entPhysicalIndex of the FRU and the container it was removed from.

Enabling FRU Traps

To configure the router to generate traps for FRU events, enter the following command from the CLI. Use the no form of the command to disable the traps.

Router(config)# snmp-server enable traps fru-ctrl Router(config)# no snmp-server enable traps fru-ctrl

To enable FRU traps through SNMP, set cefcMIBEnableStatusNotification to true(1). Disable the traps by setting cefcMIBEnableStatusNotification to false(2).

Monitoring Router InterfacesThis section provides information about how to monitor the status of router interfaces to see if there is a problem or a condition that might affect service on the interface. To determine if an interface is down or experiencing problems, you can:

Check the Interface’s Operational and Administrative Status

To check the status of an interface, view the following IF-MIB objects for the interface:

• ifAdminStatus—The administratively configured (desired) state of an interface. Use ifAdminStatus to enable or disable the interface.

• ifOperStatus—The current operational state of an interface.

Monitor linkDown and linkUp Traps

To determine if an interface has failed, you can monitor linkDown and linkUp traps for the interface. See the “Enabling Interface LinkUp/LinkDown Traps” section on page A-12 for instructions on how to enable these traps.

• linkDown—Indicates that an interface has failed or is about to fail.

• linkUp—Indicates that an interface is no longer in the Down state.

Enabling Interface LinkUp/LinkDown TrapsTo configure SNMP to send a notification when a router interface changes state to Up (ready) or Down (not ready), perform the following steps to enable linkUp and linkDown traps:

Step 1 Issue the following CLI command to enable linkUp and linkDown traps for most, but not necessarily all, interfaces:

Router(config)# snmp-server enable traps snmp linkdown linkup


OL-6384-04

Appendix A Using MIBsMonitoring Quality of Service

Step 2 View the setting of the ifLinkUpDownTrapEnable object (IF-MIB ifXTable) for each interface to determine if linkUp and linkDown traps are enabled or disabled for that interface.

Step 3 To enable linkUp and linkDown traps on an interface, set ifLinkUpDownTrapEnable to enabled(1). For information about how to configure the router to send linkDown traps only for the lowest layer of an interface, see the “SNMP Trap Filtering for linkDown Traps” section on page A-13.

Step 4 To enable the Internet Engineering Task Force (IETF) standard for linkUp and linkDown traps, issue the following command. (The IETF standard is based on RFC 2233.)

Router(config)# snmp-server trap link ietf

Step 5 To enable linkUp and linkDown traps on ATM subinterfaces, issue the following command:

Router(config)# snmp-server enable traps atm subif

Step 6 To enable linkUp and linkDown traps on an ATM permanent virtual circuit (PVC), issue the following commands. In the first command, interval specifies the minimum interval between successive traps, and fail-interval specifies the minimum interval for storing failed time stamps.

Router(config)# snmp-server enable traps atm pvc interval seconds fail-interval seconds Router(config)# interface atm slot/subslot/port Router(config-if)# pvc vpi/vci Router(config-if-atm-vc)# oam-pvc manage

Step 7 To disable traps, use the no form of the appropriate command.

SNMP Trap Filtering for linkDown TrapsUse the SNMP trap filtering feature to filter linkDown traps so that SNMP sends a linkDown trap only if the main interface goes down. If an interfaces goes down, all of its subinterfaces go down, which results in numerous linkDown traps for each subinterface. This feature filters out those subinterface traps.

This feature is turned off by default. To enable the SNMP trap filtering feature, issue the following CLI command. Use the no form of the command to disable the feature.

[no] snmp ifmib trap throttle

Monitoring Quality of ServiceThis section provides an example of how to use SNMP to access QoS configuration information and statistics on the router. It contains the following sections:

• Configuring QoS, page A-14

• Accessing QoS Configuration Information and Statistics, page A-14

• Monitoring QoS, page A-18

• Sample QoS Applications, page A-20

Purpose and Benefits

Previously, the only way to access QoS configuration information and statistics was to enter show commands at the CLI.


OL-6384-04


With the enhanced management feature, you can use SNMP to access QoS configuration information and statistics on the router. This means that you can now collect and store QoS information for use in management applications. You can also use bulk-file transfer to copy the information to another system.

MIBs Used for QoS

• CISCO-CLASS-BASED-QOS-MIB

Configuring QoSYou configure QoS through the command line interface (CLI). For instructions, see the Cisco 7200 Internet Series Router Software Configuration Guide, “Configuring Quality of Service.”

Accessing QoS Configuration Information and StatisticsThe CISCO-CLASS-BASED-QOS-MIB provides access to QoS configuration information and statistics. Although you cannot use SNMP to configure QoS on the router, you can use SNMP to access QoS configuration information that has been configured through the CLI.

QoS Indexes

The indexes for accessing QoS configuration information and QoS statistics are:

• cbQosPolicyIndex—System-assigned index that identifies a policy map attached to an interface. (When attached to an interface, a policy map is known as a service policy.)

• cbQosObjectsIndex—System-assigned index that identifies each unique run-time instance of a QoS feature (for example, policy map, class map, match statement, and feature action).

• cbQosConfigIndex—System-assigned index that identifies each unique configuration of a QoS feature (for example, a class map or police action). Note that QoS objects with the same configuration share the same cbQosConfigIndex.

• cbQosREDValue—The IP precedence or IP differentiated services code point (DSCP) of a Weighted Random Early Detection (WRED) action. It is used as the index for configuration information and statistics for each RED class.


OL-6384-04


Figure A-1 shows how these indexes provide access to QoS configuration information and statistics.

Figure A-1 Cisco 7200 Router QoS Indexes

To access QoS configuration information and statistics for a particular QoS feature:

1. Look in cbQosServicePolicyTable and find the cbQosPolicyIndex assigned to the policy in which the feature is used.

2. Use cbQosPolicyIndex to access the cbQosObjectsTable, and find the cbQosObjectsIndex and cbQosConfigIndex assigned to the QoS feature.

• Use cbQosConfigIndex to access configuration tables (cbQosxxxCfgTable) for information about the feature.

• Use cbQosPolicyIndex and cbQosObjectsIndex to access QoS statistics tables (cbQosxxxStatsTable) for information about the QoS feature.

Sample QoS Configuration Settings

This section shows how QoS configuration settings are stored in CISCO-CLASS-BASED-QOS-MIB tables and shows information grouped by QoS object. However, the actual output of an SNMP query might show QoS information similar to the following. This is only a partial display of all QoS information.

7200# getmany -v3 10.86.0.94 test-user ciscoCBQosMIBcbQosIfType.9583 = mainInterface(1)cbQosIfType.9619 = mainInterface(1)cbQosPolicyDirection.9583 = input(1)cbQosPolicyDirection.9619 = output(2)cbQosIfIndex.9583 = 3cbQosIfIndex.9619 = 3cbQosFrDLCI.9583 = 0cbQosFrDLCI.9619 = 0cbQosAtmVPI.9583 = 0cbQosAtmVPI.9619 = 0cbQosAtmVCI.9583 = 0cbQosAtmVCI.9619 = 0cbQosConfigIndex.9583.9583 = 9457cbQosConfigIndex.9583.9585 = 9451cbQosConfigIndex.9583.9587 = 9455cbQosConfigIndex.9583.9589 = 9459

6973

5

cbQosServicePolicyTable

cbQosPolicyIndex

cbQosxxxCfgTable

Configuration Information

cbQosObjectsTable

cbQosObjectsIndex . . . cbQosConfigIndex

cbQosxxxStatsTable

QoS Statistics


OL-6384-04


cbQosConfigIndex.9583.9591 = 9445cbQosConfigIndex.9583.9593 = 9449cbQosConfigIndex.9583.9595 = 9461cbQosConfigIndex.9583.9597 = 1025cbQosConfigIndex.9583.9599 = 1027cbQosConfigIndex.9619.9619 = 9609cbQosConfigIndex.9619.9621 = 9601cbQosConfigIndex.9619.9623 = 9605cbQosConfigIndex.9619.9625 = 9607cbQosConfigIndex.9619.9627 = 9611cbQosConfigIndex.9619.9629 = 1025cbQosConfigIndex.9619.9631 = 1027cbQosObjectsType.9583.9583 = policymap(1)cbQosObjectsType.9583.9585 = classmap(2)cbQosObjectsType.9583.9587 = matchStatement(3)cbQosObjectsType.9583.9589 = police(7)cbQosObjectsType.9583.9591 = classmap(2)cbQosObjectsType.9583.9593 = matchStatement(3)cbQosObjectsType.9583.9595 = police(7)cbQosObjectsType.9583.9597 = classmap(2)cbQosObjectsType.9583.9599 = matchStatement(3)cbQosObjectsType.9619.9619 = policymap(1)cbQosObjectsType.9619.9621 = classmap(2)cbQosObjectsType.9619.9623 = matchStatement(3)cbQosObjectsType.9619.9625 = matchStatement(3)cbQosObjectsType.9619.9627 = queueing(4)cbQosObjectsType.9619.9629 = classmap(2)cbQosObjectsType.9619.9631 = matchStatement(3)cbQosParentObjectsIndex.9583.9583 = 0cbQosParentObjectsIndex.9583.9585 = 9583cbQosParentObjectsIndex.9583.9587 = 9585cbQosParentObjectsIndex.9583.9589 = 9585cbQosParentObjectsIndex.9583.9591 = 9583cbQosParentObjectsIndex.9583.9593 = 9591cbQosParentObjectsIndex.9583.9595 = 9591cbQosParentObjectsIndex.9583.9597 = 9583cbQosParentObjectsIndex.9583.9599 = 9597cbQosParentObjectsIndex.9619.9619 = 0cbQosParentObjectsIndex.9619.9621 = 9619cbQosParentObjectsIndex.9619.9623 = 9621cbQosParentObjectsIndex.9619.9625 = 9621cbQosParentObjectsIndex.9619.9627 = 9621cbQosParentObjectsIndex.9619.9629 = 9619cbQosParentObjectsIndex.9619.9631 = 9629cbQosPolicyMapName.9457 = carcbQosPolicyMapDesc.9457 = cbQosCMName.1025 = class-defaultcbQosCMDesc.1025 = cbQosCMInfo.1025 = matchAny(3) . . .

The following samples are QoS CLI show command outputs.

7200# show class-mapclass-map match-any prec1_dscp16match ip prec 1match ip dscp 16

7200# show policy-mappolicy-map cbwfq-wred


OL-6384-04


class prec1_dscp16 bandwidth percent 20 random-detect random-detect exponential-weighting-constant 10 random-detect precedence 0 10 126 10 random-detect precedence 1 11 126 10 random-detect precedence 2 12 126 10 random-detect precedence 3 13 126 10 random-detect precedence 4 14 126 10 random-detect precedence 5 15 126 10 random-detect precedence 6 16 126 10 random-detect precedence 7 17 126 10 interface gi0/1service-policy output cbwfq-wredpolicy-map car class prec1 police 20000000 24000 24000 conform-action set-dscp-transmit 5 exceed-action drop class dscp16 police 20000000 24000 24000 conform-action transmit exceed-action transmit interface pos4/0service-policy input car

Note the following about the sample QoS configuration:

• Policy maps that are not attached to an interface are not included with SNMP data or displayed by the show policy-map interface command. This is why pm-1Meg is shown but pm1 is not.

• The default class map is always included with the SNMP data.

• Class maps that have no action defined are not included with the SNMP data.

The following output is a sample of RED configuration information stored in MIB tables applied to a Cisco 7200 interface.

cbQosREDCfgExponWeight.9776 = 10cbQosREDCfgMeanQsize.9776 = 0cbQosREDCfgDscpPrec.9776 = precedence(1)cbQosREDCfgMinThreshold.9776.0 = 10cbQosREDCfgMinThreshold.9776.1 = 11cbQosREDCfgMinThreshold.9776.2 = 12cbQosREDCfgMinThreshold.9776.3 = 13cbQosREDCfgMinThreshold.9776.4 = 14cbQosREDCfgMinThreshold.9776.5 = 15cbQosREDCfgMinThreshold.9776.6 = 16cbQosREDCfgMinThreshold.9776.7 = 17cbQosREDCfgMaxThreshold.9776.0 = 126cbQosREDCfgMaxThreshold.9776.1 = 126cbQosREDCfgMaxThreshold.9776.2 = 126cbQosREDCfgMaxThreshold.9776.3 = 126cbQosREDCfgMaxThreshold.9776.4 = 126cbQosREDCfgMaxThreshold.9776.5 = 126cbQosREDCfgMaxThreshold.9776.6 = 126cbQosREDCfgMaxThreshold.9776.7 = 126cbQosREDCfgPktDropProb.9776.0 = 10cbQosREDCfgPktDropProb.9776.1 = 10cbQosREDCfgPktDropProb.9776.2 = 10cbQosREDCfgPktDropProb.9776.3 = 10cbQosREDCfgPktDropProb.9776.4 = 10cbQosREDCfgPktDropProb.9776.5 = 10cbQosREDCfgPktDropProb.9776.6 = 10cbQosREDCfgPktDropProb.9776.7 = 10. . .


OL-6384-04


Monitoring QoSThis section provides information about how to monitor QoS on the router by checking the QoS statistics in the MIB tables described in Table A-4. For information about how to determine the amount of traffic to bill customers for, see the “Billing Customers for Traffic” section on page A-22.

Note The CISCO-CLASS-BASED-QOS-MIB might contain more information than what is displayed in the output of CLI show commands.

Considerations for Processing QoS Statistics

The router maintains 64-bit counters for most QoS statistics. However, some QoS counters are implemented as a 32-bit counter with a 1-bit overflow flag. In the following figures, these counters are shown as 33-bit counters.

When accessing QoS statistics in counters, consider the following:

• SNMPv2c or SNMPv3 applications—Access the entire 64 bits of the QoS counter through cbQosxxx64 MIB objects.

• SNMPv1 applications—Access QoS statistics in the MIB as follows:

– Access the lower 32 bits of the counter through cbQosxxx MIB objects.

– Access the upper 32 bits of the counter through cbQosxxxOverflow MIB objects.

Sample QoS StatisticsThis section shows how QoS statistics are displayed in show commands and stored in CISCO-CLASS-BASED-QOS-MIB tables.

For ease-of-use, the display shows some counters as a single object even though the counter is implemented as three objects. For example, cbQosCMPrePolicyByte is implemented as:

cbQosCMPrePolicyByteOverflowcbQosCMPrePolicyByte

Table A-4 QoS Statistics Tables

QoS Table Statistics

cbQosCMStatsTable Class Map—Counts of packets, bytes, and bit rate before and after QoS policies are executed. Counts of dropped packets and bytes.

cbQosMatchStmtStatsTable Match Statement—Counts of packets, bytes, and bit rate before executing QoS policies.

cbQosPoliceStatsTable Police Action—Counts of packets, bytes, and bit rate that conforms to, exceeds, and violates police actions.

cbQosQueueingStatsTable Queueing—Counts of discarded packets and bytes, and queue depths.

cbQosTSStatsTable Traffic Shaping—Counts of delayed and dropped packets and bytes, the state of a feature, and queue size.

cbQosREDClassStatsTable Random Early Detection—Counts of packets and bytes dropped when queues were full and also when transmitted.


OL-6384-04


cbQosCMPrePolicyByte64

Note Due to implementation features, some of the QoS statistics counters might wrap before they reach the maximum value they can accommodate.

The following is a sample of QoS class map statistics.

class-map dscp16 match ip dscp 16 class-map prec1 match ip prec 1 policy-map car class prec1 police 20000000 24000 24000 conform-action set-dscp-transmit 5 exceed-action drop class dscp16police 20000000 24000 24000 conform-action transmit exceed-action transmit interface atm3/0pvc 1/99service-policy input car

class-map prec2 match ip prec 2 class-map prec1 match ip prec 1 policy-map cbwfq class prec1 bandwidth perc 40 queue-limit 33 class prec2 bandwidth perc 50 queue-limit 55 interface atm3/0pvc 1/99service-policy output cbwfq

cbQosPoliceStatsTablecbQosPoliceStatsEntry

cbQosPoliceConformedPktOverflow.9535.9541 = 0cbQosPoliceConformedPkt.9535.9541 = 226961cbQosPoliceConformedPkt64.9535.9541 = 0x000037691cbQosPoliceConformedByte.9535.9541 = 230592376cbQosPoliceConformedByteOverflow.9535.9541 = 0cbQosPoliceConformedByte64.9535.9541 = 0x00dbe8f78cbQosPoliceConformedBitRate.9535.9541 = 0cbQosPoliceExceededPktOverflow.9535.9541 = 0cbQosPoliceExceededPkt64.9535.9541 = 0x000000000cbQosPoliceExceededByte.9535.9541 = 0cbQosPoliceExceededBitRate.9535.9541 = 0cbQosPoliceViolatedPktOverflow.9535.9541 = 0cbQosPoliceViolatedPkt.9535.9541 = 0cbQosPoliceViolatedByteOverflow.9535.9541 = 0cbQosPoliceViolatedByte.9535.9541 = 0cbQosPoliceViolatedBitRate.9535.9541 = 0

cbQosQueueingStatsTablecbQosQueueingStatsEntry

cbQosQueueingCurrentQDepth.9619.9627 = 0cbQosQueueingMaxQDepth.9619.9627 = 0


OL-6384-04


cbQosQueueingDiscardByte.9619.9627 = 700700636cbQosQueueingDiscardPkt.9619.9627 = 697909

Sample QoS ApplicationsThis section presents examples of sample code showing how to retrieve information from the CISCO-CLASS-BASED-QOS-MIB to use for QoS billing operations. You can use these examples to help you develop billing applications. The sample code shows how to:

• Checking Customer Interfaces for Service Policies

• Retrieving QoS Billing Information

Checking Customer Interfaces for Service Policies

This section describes a sample algorithm that checks the CISCO-CLASS-BASED-QOS-MIB for customer interfaces with service policies, and marks those interfaces for further application processing (such as billing for QoS services).

The algorithm uses two SNMP get-next requests for each customer interface. For example, if the router has 2000 customer interfaces, 4000 SNMP get-next requests are required to determine whether those interfaces have transmit and receive service policies associated with them.

Note This algorithm is for informational purposes only. Your application needs may be different.

Check the MIB to see which interfaces are associated with a customer. Create a pair of flags to show whether a service policy has been associated with the transmit and receive directions of a customer interface. Mark non-customer interfaces TRUE (so no more processing is required for them).

FOR each ifEntry DO IF (ifEntry represents a customer interface) THEN servicePolicyAssociated[ifIndex].transmit = FALSE; servicePolicyAssociated[ifIndex].receive = FALSE; ELSE servicePolicyAssociated[ifIndex].transmit = TRUE; servicePolicyAssociated[ifIndex].receive = TRUE; END-IFEND-FOR

Examine the cbQosServicePolicyTable and mark each customer interface that has a service policy attached to it. Also note the direction of the interface.

x = 0;done = FALSE;WHILE (!done) status = snmp-getnext ( ifIndex = cbQosIfIndex.x, direction = cbQosPolicyDirection.x ); IF (status != ‘noError’) THEN done = TRUE ELSE x = extract cbQosPolicyIndex from response; IF (direction == ‘output’) THEN servicePolicyAssociated[ifIndex].transmit = TRUE; ELSE servicePolicyAssociated[ifIndex].receive = TRUE;


OL-6384-04


END-IF END-IFEND-WHILE

Manage cases in which a customer interface does not have a service policy attached to it.

FOR each ifEntry DO IF (!servicePolicyAssociated[ifIndex].transmit) THEN Perform processing for customer interface without a transmit service policy. END-IF IF (!servicePolicyAssociated[ifIndex].receive) THEN Perform processing for customer interface without a receive service policy. END-IFEND-FOR

Retrieving QoS Billing Information

This section describes a sample algorithm that uses the CISCO-CLASS-BASED-QOS-MIB for QoS billing operations. The algorithm periodically retrieves post-policy input and output statistics, combines them, and sends the result to a billing database.

The algorithm uses the following:

• One SNMP get request per customer interface—to retrieve the ifAlias.

• Two SNMP get-next requests per customer interface—to retrieve service policy indexes.

• Two SNMP get-next requests per customer interface for each object in the policy—to retrieve post-policy bytes. For example, if there are 100 interfaces and 10 objects in the policy, the algorithm requires 2000 get-next requests (2 x 100 x 10).

Note This algorithm is for informational purposes only. Your application needs may be different.

Set up customer billing information.

FOR each ifEntry DO IF (ifEntry represents a customer interface) THEN status = snmp-getnext (id = ifAlias.ifIndex); IF (status != ‘noError’) THEN Perform error processing. ELSE billing[ifIndex].isCustomerInterface = TRUE; billing[ifIndex].customerID = id; billing[ifIndex].transmit = 0; billing[ifIndex].receive = 0; END-IF ELSE billing[ifIndex].isCustomerInterface = FALSE; END-IFEND-FOR


OL-6384-04

Appendix A Using MIBsBilling Customers for Traffic

Retrieve billing information.

x = 0;done = FALSE;WHILE (!done) response = snmp-getnext ( ifIndex = cbQosIfIndex.x, direction = cbQosPolicyDirection.x ); IF (response.status != ‘noError’) THEN done = TRUE ELSE x = extract cbQosPolicyIndex from response; IF (direction == ‘output’) THEN billing[ifIndex].transmit = GetPostPolicyBytes (x); ELSE billing[ifIndex].receive = GetPostPolicyBytes (x); END-IF END-IFEND-WHILE

Determine the number of post-policy bytes for billing purposes.

GetPostPolicyBytes (policy) x = policy; y = 0; total = 0; WHILE (x == policy) response = snmp-getnext (type = cbQosObjectsType.x.y); IF (response.status == ‘noError’) x = extract cbQosPolicyIndex from response; y = extract cbQosObjectsIndex from response; IF (x == policy AND type == ‘classmap’) status = snmp-get (bytes = cbQosCMPostPolicyByte64.x.y); IF (status == ‘noError’) total += bytes; END-IF END-IF END-IF END-WHILERETURN total;

Billing Customers for TrafficThis section describes how to use SNMP QoS information to determine the amount of traffic to bill to your customers. It also includes a scenario for demonstrating that a QoS service policy attached to an interface is policing traffic on that interface.

This section describes the following topics:

• Determining the Amount of Traffic to Bill to a Customer, page A-23

• Scenario for Demonstrating QoS Traffic Policing, page A-23


OL-6384-04


Input and Output Interface Counts

The router maintains information about the number of packets and bytes that are received on an input interface and transmitted on an output interface. When a QoS service policy is attached to an interface, the router applies the rules of the policy to traffic on the interface and increments the packet and bytes counts on the interface.

The following CISCO-CLASS-BASED-QOS-MIB objects provide interface counts:

• cbQosCMDropPkt and cbQosCMDropByte (cbQosCMStatsTable)—Total number of packets and bytes that were dropped because they exceeded the limits set by the service policy. These counts include only those packets and bytes that were dropped because they exceeded service policy limits. The counts do not include packets and bytes dropped for other reasons.

• cbQosPoliceConformedPkt and cbQosPoliceConformedByte (cbQosPoliceStatsTable)—Total number of packets and bytes that conformed to the limits of the service policy and were transmitted.

Determining the Amount of Traffic to Bill to a CustomerPerform these steps to determine how much traffic on an interface is billable to a particular customer:

Step 1 Determine which service policy on the interface applies to the customer.

Step 2 Determine the index values of the service policy and class map used to define the customer’s traffic. You will need this information in the following steps.

Step 3 Access the cbQosPoliceConformedPkt object (cbQosPoliceStatsTable) for the customer to determine how much traffic on the interface is billable to this customer.

Step 4 (Optional) Access the cbQosCMDropPkt object (cbQosCMStatsTable) for the customer to determine how much of the customer’s traffic was dropped because it exceeded service policy limits.

Scenario for Demonstrating QoS Traffic PolicingThis section describes a scenario that demonstrates the use of SNMP QoS statistics to determine how much traffic on an interface is billable to a particular customer. It also shows how packet counts are affected when a service policy is applied to traffic on the interface.

To create the scenario, follow these steps, each of which is described in the sections that follow:

1. Create and attach a service policy to an interface.

2. View packet counts before the service policy is applied to traffic on the interface.

3. Issue a ping command to generate traffic on the interface. Note that the service policy is applied to the traffic.

4. View packet counts after the service policy has been applied to determine how much traffic to bill the customer for:

• Conformed packets—The number of packets within the range set by the service policy and for which you can charge the customer.

• Exceeded or dropped packets—The number of packets that were not transmitted because they were outside the range of the service policy. These packets are not billable to the customer.


OL-6384-04


Note In the above scenario, the Cisco 7200 Router is used as an interim device (that is, traffic originates elsewhere and is destined for another device).

Service Policy Configuration

This scenario uses the following policy-map configuration. For information on how to create a policy map, see “Configuring Quality of Service” in the Cisco 7200 Internet Series Router Software Configuration Guide.

policy-map police-out class BGPclass police 8000 1000 2000 conform-action transmit exceed-action drop

interface GigabitEthernet1/0/0.10 description VLAN voor klant encapsulation dot1Q 10 ip address 10.0.0.17 255.255.255.248 service-policy output police-out

Packet Counts Before the Service Policy Is Applied

The following CLI and SNMP output shows the interface’s output traffic before the service policy is applied:

Sample CLI Command Output7200# show policy-map interface g6/0/0.10

GigabitEthernet6/0/0.10

Service-policy output: police-out

Class-map: BGPclass (match-all) 0 packets, 0 bytes 30 second offered rate 0 bps, drop rate 0 bps Match: access-group 101 Police: 8000 bps, 1000 limit, 2000 extended limit conformed 0 packets, 0 bytes; action: transmit exceeded 0 packets, 0 bytes; action: drop

Class-map: class-default (match-any) 4 packets, 292 bytes 30 second offered rate 0 bps, drop rate 0 bps Match: any Output queue: 0/8192; 2/128 packets/bytes output, 0 drops

Sample SNMP Output7200# getone -v2c 10.86.0.63 public ifDescr.65ifDescr.65 = GigabitEthernet6/0/0.10-802.1Q vLAN subif

Generating Traffic

The following set of ping commands generates traffic:

7200# pingProtocol [ip]:Target IP address: 10.0.0.18


OL-6384-04


Repeat count [5]: 99 Datagram size [100]: 1400Timeout in seconds [2]: 1Extended commands [n]:Sweep range of sizes [n]: Type escape sequence to abort.

Sending 100, 1400-byte ICMP Echos to 10.0.0.18, timeout is 1 seconds:.!!.!..!.!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.! Success rate is 42 percent (42/100), round-trip min/avg/max = 1/1/1 ms

Packet Counts After the Service Policy Is Applied

After you generate traffic using the ping command, look at the number of packets that exceeded and conformed to the committed access rate (CAR) set by the police command:

• 42 packets conformed to the police rate and were transmitted

• 57 packets exceeded the police rate and were dropped

The following CLI and SNMP output show the counts on the interface after the service policy is applied. (In the output, conformed and exceeded packet counts are shown in boldface.)

CLI Command Output7200# show policy-map interface g6/0/0.10

FastEthernet6/0/0.10

Service-policy output: police-out

Class-map: BGPclass (match-all) 198 packets, 281556 bytes 30 second offered rate 31000 bps, drop rate 11000 bps Match: access-group 101 Police: 8000 bps, 1000 limit, 2000 extended limit conformed 42 packets, 59892 bytes; action: transmit exceeded 57 packets, 81282 bytes; action: drop

Class-map: class-default (match-any) 15 packets, 1086 bytes 30 second offered rate 0 bps, drop rate 0 bps Match: any Output queue: 0/8192; 48/59940 packets/bytes output, 0 drops

SNMP Output7200# getmany -v2c 10.86.0.63 public ciscoCBQosMIB . . . cbQosCMDropPkt.1143.1145 = 57 . . . cbQosPoliceConformedPkt.1143.1151 = 42 . . .


OL-6384-04


How to Collect CPU Utilization on Cisco IOS Devices Using SNMPIf your IOS device has several CPUs, you must use CISCO-PROCESS MIB and its object cpmCPUTotal5minRev from the table called cpmCPUTotalTable , indexed with cpmCPUTotalIndex . This table allows CISCO-PROCESS MIB to keep CPU statistics for different physical entities in the router, such as different CPU chips, group of CPUs, or CPUs in different cards. In the case of a single CPU, cpmCPUTotalTable has only one entry.

Information about different physical entities in the router is stored in the entPhysicalTable of RFC 2737 standard-based ENTITY-MIB. You can link between two tables ( cpmCPUTotalTable and entPhysicalTable ) easily: each row of cpmCPUTotalTable has an object cpmCPUTotalPhysicalIndex that keeps the value of the entPhysicalIndex (index of entPhysicalTable ), and points to the entry in entPhysicalTable , correspondent to the physical entity for which these CPU statistics are maintained.

This implies that the IOS device must support both CISCO-PROCESS MIB and ENTITY-MIB for you to be able to retrieve relevant information about CPU utilization.

The only case where you do not need to have or use ENTITY-MIB is when you only have a single CPU.

For detailed description about CPU unitlization, go to the following URL:

http://www.cisco.com/warp/public/477/SNMP/collect_cpu_util_snmp.pdf


OL-6384-04

http://www.cisco.com/warp/public/477/SNMP/collect_cpu_util_snmp.pdf

Appendix A Using MIBsUsing CISCO-AAA-SESSION-MIB

Using CISCO-AAA-SESSION-MIBThe following object support was added to the CISCO-AAA-SESSION-MIB to improve interface mapping sessions:

• casnNasPort—Identifies a particular conceptual row associated with the session identified by casnSessionId. The conceptual row that this object points to represents a port that is used to transport a session. If the port transporting the session cannot be determined, the value of this object will be zeroDotZero

For example, a session is established using an ATM PVC. If the ifIndex of the ATM interface is 7 and the VPI/VCI values of the PVC are 1, 100 respectively, then the value of this object is (in this example):

• casnVaiIfIndex—Identifies the ifIndex of the Virtual Access Interface (VAI) that is associated with the PPP session. This interface may not be represented in the IF-MIB in which case the value of this object will be zero.

casnNasPort.15 = atmVc1AdminStatus.7.1.100

casnSessionId

ifIndex

atmVc1Vpi

atmVc1Vci

Where atmVc1AdminStatus is the first accessible object of the atmVcTable of the ATM-MIB.


OL-6384-04

Appendix A Using MIBsUsing CISCO-AAA-SESSION-MIB


OL-6384-04

OL-6384-04

G L O S S A R Y

A

AAA Authentication, authorization, and accounting.

Alarm The word alarm represents a condition that causes a trap to be generated.

Alarm Severity Each alarm type defined by a vendor type and employed by the system is assigned an associated sever-ity. See critical, major, minor and informational for severity types.

ATM Asynchronous Transfer Mode. The international standard for cell relay in which multiple service types (such as voice, video, or data) are conveyed in fixed-length (53-byte) cells. Fixed-length cells allow cell processing to occur in hardware, thereby reducing transit delays. ATM is designed to take advantage of high-speed transmission media, such as E3, SONET, and T3.

ATM-AAL5 ATM adaptation layer 5. One of four AALs recommended by the ITU-T. AAL5 supports connec-tion-oriented variable bit rate (VBR) services and is used predominantly for the transfer of classical IP over ATM and LAN emulation (LANE) traffic. AAL5 uses simple and efficient AAL (SEAL) and is the least complex of the current AAL recommendations. It offers low bandwidth overhead and simpler pro-cessing requirements in exchange for reduced bandwidth capacity and error-recovery capability.

B

Bandwidth The difference between the highest and lowest frequencies available for network signals. The term is also used to describe the rated throughput capacity of a given network medium or protocol.

Broadcast storm Undesirable network event in which many broadcasts are sent simultaneously across all network seg-ments. A broadcast storm uses substantial network bandwidth and, typically, causes network time-outs.

C

CANA Cisco Assigned Numbers Authority. The central clearing house for allocation of unique names and numbers that are embedded in Cisco software.

Columnar object One type of managed object that defines a MIB table that contains no rows or more than one row, and each row can contain one or more scalar objects, (for example, ifTable in the IF-MIB defines the interface).

GL-1Cisco 7200 Router MIB Specifications Guide

Glossary

Community Name Defines an access environment for a group of NMSs. NMSs within the community are said to exist within the same administrative domain. Community names serve as a weak form of authentication because devices that do not know the proper community name are precluded from SNMP operations.

Critical alarm sever-

ity type

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 line cards or loss of signal failure when a physical port link is down.

D

Display String A printable ASCII string. It is typically a name or description. For example, the variable netConfig-Name provides the name of the network configuration file for a device.

DS0 Digital signal level 0. Framing specification used in transmitting digital signals at 64 Kbps. Twenty-four DS0s equal one DS1.

DS1 Digital signal level 1. Framing specification used in transmitting digital signals at 1.544 Mbps on a T1 facility.

DS3 Digital signal level 3. Framing specification used for transmitting digital signals at 44.736 Mbps on a T3 facility.

E

EHSA Enhanced High System Availability.

EMS Element Management System. An EMS manages a specific portion of the network. For example the SunNet Manager, an SNMP management application, is used to manage SNMP manageable elements. Element Managers may manage async lines, multiplexers, PABX's, proprietary systems or an application.

Encapsulation The wrapping of data in a particular protocol header. For example, Ethernet data is wrapped in a spe-cific Ethernet header before network transit. Also, when bridging dissimilar networks, the entire frame from one network is simply placed in the header used by the data link layer protocol of the other network.

F

FRU Field Replaceable Unit. Term applied to the Cisco 6400 components that can be replaced in the field, including the NLC, NSP, NRP, and PEM units, plus the blower fans.

Forwarding Process of sending a frame toward its ultimate destination by way of an internetworking device.

Frame Logical grouping of information sent as a data link layer unit over a transmission medium. Often refers to the header and trailer, used for synchronization and error control, that surround the user data con-tained in the unit. The terms cell, datagram, message, packet, and segment are also used to describe logical information groupings at various layers of the OSI reference model and in various technology circles.


OL-6384-04

Glossary

G

Gb gigabit

Gbps gigabits per second

GB gigabyte

GBps gigabytes per second

H

HSRP Hot Standby Routing Protocol. Protocol used among a group of routers for selecting an active router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met.)

I

IEEE 802.2 IEEE LAN protocol that specifies an implementation of the LLC sublayer of the data link layer. IEEE 802.2 handles errors, framing, flow control, and the network layer (Layer 3) service interface. Used in IEEE 802.3 and IEEE 802.5 LANs. See also IEEE 802.3 and IEEE 802.5.

IEEE 802.3 IEEE LAN protocol that specifies an implementation of the physical layer and the MAC sublayer of the data link layer. IEEE 802.3 uses CSMA/CD access at a variety of speeds over a variety of physical media. Extensions to the IEEE 802.3 standard specify implementations for Fast Ethernet.

IEEE 802.5 IEEE LAN protocol that specifies an implementation of the physical layer and MAC sublayer of the data link layer. IEEE 802.5 uses token passing access at 4 or 16 Mbps over STP cabling and is similar to IBM Token Ring. See also Token Ring.

Info Notification about a condition that could lead to an impending problem or notification of an event that improves operation.

Informs Reliable messages, which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.

ifIndex Each row of the interfaces table has an associated number, called an ifIndex. You use the ifIndex num-ber to get a specific instance of an interfaces group object. For example, ifInNUcastPkts.1 would find you the number of broadcast packets received on interface number one. You can then find the descrip-tion of interface number one by looking at the object which holds the interface description (from MIB-II) ifDescr.

Integer A numeric value that can be an actual number. For example, the number of lost IP packets on an inter-face. It also can be a number that represents a nonnumeric value. For example, the variable tsLineType returns the type of terminal services line to the SNMP manager.


OL-6384-04

Glossary

Interface Counters Interface management over SNMP is based on two tables: ifTable and its extension, ifXTable described in RFC1213/RFC2233. Interfaces can have several layers, depending on the media, and each sub-layer is represented by a separate row in the table. The relationship between the higher layer and lower layers is described in the ifStackTable.

The ifTable defines 32-bit counters for inbound and outbound octets (ifInOctets / ifOutOctets), packets (ifInUcastPkts / ifOutUcastPkts, ifInNUcastPkts / ifOutNUcastPkts), errors, and discards.

The ifXTable provides similar 64-bit counters, also called high capacity (HC) counters: ifHCInOctets / ifHCOutOctets, and ifHCInUcastPkts / ifHCOutUcastPkts.

Internetwork Collection of networks interconnected by routers and other devices that functions as a single network. Sometimes called an internet, which is not to be confused with the Internet.

Interoperability Ability of computing equipment manufactured by different vendors to communicate with one another successfully over a network.

IP Address The variable hostConfigAddr indicates the IP address of the host that provided the host configuration file for a device.

J

K

Keepalive message Message sent by one network device to inform another network device that the virtual circuit between the two is still active.

L

label A short, fixed-length identifier that is used to determine the forwarding of a packet.

LDP Label Distribution Protocol.

LSR Label Switching Router. A device that forwards MPLS packets based on the value of a fixed-length label encapsulated in each packet.

LSP Label Switched Path.


OL-6384-04

Glossary

M

Major alarm severity

type

Used for hardware or software conditions. Indicates a serious disruption of service or the malfunction-ing 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. For example, a minor alarm is generated if a secondary NSE-100 or NPE-G100 card fails or it is removed.

Minor alarm sever-

ity type

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.

MIB Management Information Base. Database of network management information that is used and main-tained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved by means of SNMP commands, usually through a network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.

MIB II MIB-II is the follow on to MIB-I which was the original standard SNMP MIB. MIB-II provided some much needed enhancements to MIB-I. MIB-II is very old, and most of it has been updated (that which has not is mostly obsolete). It includes objects that describe system related data, especially data related to a system’s interfaces.

MPLS Multiprotocol Label Switching. MPLS is a method for forwarding packets (frames) through a network. It enables routers at the edge of a network to apply labels to packets (frames). ATM switches or existing routers in the network core can switch packets according to the labels with minimal lookup overhead.

MPLS Interface An interface on which MPLS traffic is enabled. MPLS is the standardized version of Cisco original tag switching proposal. It uses a label forwarding paradigm (forward packets based on labels).

MTU Maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle.

N

NAS Network access server. Cisco platform or collection of platforms such as an AccessPath system which interfaces between the Internet and the circuit world (the PSTN).

NMS Network management system. System responsible for managing at least part of a network. An NMS is generally a reasonably powerful and well-equipped computer, such as an engineering workstation. NMSs communicate with agents to help keep track of network statistics and resources.

NHLFE Next Hop Label Forwarding Entry.


OL-6384-04

Glossary

O

OID Object identifier. Values are defined in specific MIB modules. The Event MIB allows you or an NMS to watch over specified objects and to set event triggers based on existence, threshold, and Boolean tests. An event occurs when a trigger is fired; this means that a specified test on an object returns a value of true. To create a trigger, you or an NMS configures a trigger entry in the mteTriggerTable of the Event MIB. This trigger entry specifies the OID of the object to be watched. For each trigger entry type, corresponding tables (existence, threshold, and Boolean tables) are populated with the information required for carrying out the test. The MIB can be configured so that when triggers are activated (fired) either an SNMP Set is performed, a notification is sent out to the interested host, or both.

OIR Online Insertion and Removal.

P

PAP Password Authentication Protocol. Authentication protocol that allows PPP peers to authenticate one another. The remote router attempting to connect to the local router is required to send an authentication request. Unlike CHAP, PAP passes the password and host name or username in the clear (unencrypted). PAP does not itself prevent unauthorized access, but identifies the remote end. The router or access server determines if that user is allowed access. PAP is supported only on PPP lines.

PEM Power Entry Module.

Polling Access method in which a primary network device inquires, in an orderly fashion, whether secondaries have data to transmit. The inquiry occurs in the form of a message to each secondary that gives the sec-ondary the right to transmit.

PPP Point-to-Point Protocol. Provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. PPP is designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.

Q

QoS Quality of service. Measure of performance for a transmission system that reflects its transmission quality and service availability.

R

RADIUS Remote Authentication Dial-In User Service. RADIUS is a distributed client/server system that secures networks against unauthorized access. In the Cisco implementation, RADIUS clients run on Cisco rout-ers and send authentication requests to a central RADIUS server that contains all user authentication and network service access information.

Read-only This variable can be used to monitor information only. For example, the locIPUnreach variable, whose access is read-only, indicates whether Internet Control Message Protocol (ICMP) packets concerning an unreachable address will be sent.


OL-6384-04

Glossary

Read-write This variable can be used to monitor information and to set a new value for the variable. For example, the tsMsgSend variable, whose access is read-write, determines what action to take after a message has been sent.

The possible integer values for this variable follow:

1 = nothing

2 = reload

3 = message done

4 = abort

RFC Requests for Comments, started in 1969, form a series of notes about the Internet (originally the ARPA-NET). The notes discuss many aspects of computer communication, focusing on networking protocols, procedures, programs, and concepts, but also include meeting notes, opinions, and sometimes humor.

The RFC Editor is the publisher of RFCs and is responsible for the final editorial review of the docu-ments. The RFC Editor also maintains a master file of RFCs, the RFC index, that you can search online here.

The specification documents of the Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group, the Internet Engineering Steering Group (IESG), are published as RFCs. Thus, the RFC publication process plays an important role in the Internet standards process. Go to the following URL for details: http://www.cisco.com/univercd/cc/td/doc/product/software/ios103/mib_doc/80516.htm#xtocid13

RMON The Remote Network Monitoring MIB is a SNMP MIB for remote management of networks. RMON is one of the many SNMP based MIBs that are IETF Standards. RMON allows network operators to monitor the health of the network with a Network Management System (NMS). RMON watches several variables, such as Ethernet collisions, and triggers an event when a variable crosses a threshold in the specified time interval.

RSVP Resource Reservation Protocol. Protocol that supports the reservation of resources across an IP net-work. Applications running on IP end systems can use RSVP to indicate to other nodes the nature (bandwidth, jitter, maximum burst, and so forth) of the packet streams they want to receive. RSVP depends on IPv4. Also known as Resource Reservation Setup Protocol.

S

Scalar Object One type of managed object which is a single object instance (for example, ifNumber in the IF-MIB and bgpVersion in the BGP4-MIB)

SNMPv1 The Simple Network Management Protocol: An Internet standard, defined in RFC 1157. Security is based on community strings. SNMPv1 uses a community-based form of security. The community of managers who are able to access the agent MIB is defined by an IP address Access Control List and password.


OL-6384-04

http://www.cisco.com/univercd/cc/td/doc/product/software/ios103/mib_doc/80516.htm#xtocid13

Glossary

SNMPv2 The community-string based administrative framework for SNMPv2. SNMPv2c is an update of the pro-tocol operations and data types of SNMPv2p (SNMPv2 classic), and uses the community-based security model of SNMPv1.

SNMPv2c support includes a bulk-retrieval mechanism and more detailed error message reporting to management stations. The bulk-retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trip transmissions required. SNMPv2c improved error handling support includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes now report the error type. Three kinds of exceptions are also reported:

• no such object exceptions

• no such instance exceptions

• end of MIB view exceptions

SNMPv3 SNMPv3—Version 3 of SNMP. SNMPv3 uses the following security features to provide secure access to devices:

• Message integrity—Ensuring that a packet has not been tampered with in transit.

• Authentication—Determining that the message is from a valid source.

• Encryption—Scrambling the contents of a packet to prevent it from being learned by an unautho-rized source.

SNMP Agent A software component in a managed device that maintains the data for the device and reports the data, as needed, to managing systems. The agent and MIB reside on the routing device (router, access server, or switch). To enable the SNMP agent on a managed device, you must define the relationship between the manager and the agent.

SNMP Manager A system used to control and monitor the activities of network hosts using SNMP. The most common managing system is called a Network Management System (NMS). The term NMS can be applied to either a dedicated device used for network management, or the applications used on a network-man-agement device. A variety of network management applications are available for use with SNMP. These features range from simple command-line applications to feature-rich graphical user interfaces (such as the CiscoWorks2000 line of products).

SONET Synchronous Optical Network. A physical layer interface standard for fiber optic transmission. High-speed synchronous network specification developed by Telcordia Technologies, Inc. and designed to run on optical fiber. STS-1 is the basic building block of SONET. Approved as an interna-tional standard in 1988.

T

TE Traffic Engineered

Time Stamp Provides the amount of time that has elapsed between the last network reinitialization and generation of the trap.

TLV Type Length Value. Dynamic format for storing data in any order. Used by Cisco’s Generic ID PROM for storing asset information.


OL-6384-04

Glossary

Traffic engineering

tunnel

A label-switched tunnel that is used for traffic engineering. Such a tunnel is set up through means other than normal Layer 3 routing; it is used to direct traffic over a path different from the one that Layer 3 routing could cause the tunnel to take.

Trap An trap is an unsolicited (device initiated) message. The contents of the message might be simply infor-mational, but it is mostly used to report real-time trap information. Since a trap is a UDP datagram, sole reliance upon them to inform you of network problems (i.e. passive network monitoring) is not wise. They can be used in conjunction with other SNMP mechanisms as in trap-directed polling or the SNMP inform mechanism can be used when a reliable fault reporting system is required.

Tunnel A secure communication path between two peers, such as routers.

U

UBR Unspecified bit rate. QOS class defined by the ATM Forum for ATM networks. UBR allows any amount of data up to a specified maximum to be sent across the network, but there are no guarantees in terms of cell loss rate and delay. Compare with ABR (available bit rate), CBR, and VBR.

UDP User Datagram Protocol. A connections, non-reliable IP based transport protocol.

V

VBR Variable bit rate. QOS class defined by the ATM Forum for ATM networks. VBR is subdivided into a real time (RT) class and non-real time (NRT) class. VBR (RT) is used for connections in which there is a fixed timing relationship between samples. VBR (NRT) is used for connections in which there is no fixed timing relationship between samples, but that still need a guaranteed QOS.

VRF VPN Routing and Forwarding Tables.

W

Write-only This variable can be used to set a new value for the variable only. For example, the writeMem variable, whose access is write-only, writes the current (running) router configuration into nonvolatile memory where it can be stored and retained even if the router is reloaded. If the value is set to 0, the writeMem variable erases the configuration memory


OL-6384-04

Glossary


OL-6384-04

OL-6384-04

I N D E X

A

ATM-FORUM-ADDR-REG-MIB 3-6

ATM-FORUM-MI 3-6

ATM-FORUM-MIB 3-6

ATM-MIB 3-5, 3-7, 3-8

audience 1-xii

B

BGP4-MIB 3-6

billing application samples (QoS) A-21, A-22

billing customers for traffic A-22, A-25

BRIDGE-MIB 3-7

C

changes in this guide 1-ix

Cisco 7304 router

billing customers for traffic A-22, A-25

enabling

SNMP 2-4

enabling SNMP 2-4

enhanced management feature 1-1, 1-2

linkUp and linkDown traps A-13

monitoring interfaces A-12

QoS A-25

SNMP notifications 1-3 to 1-5

SNMP traps A-11, A-13


CISCO-AAL5-MIB 3-9


CISCO-ALPS-MIB 3-9



CISCO-CDP-MIB 3-11

CISCO-CLASS-BASED-QOS-MIB 3-11, 3-12

CISCO-CLASS-BASED-QOS-MIB, using A-14


CISCO-ENHANCED-MEMORY-POOL-MIB 3-27


CISCO-ENTITY-ASSET-MIB A-2

CISCO-ENTITY-FRU-CONTROL-MIB A-2

CISCO-ENTITY-VENDORTYPE-OID-MIB 3-21, 3-21 to 3-23, A-2


CISCO-FLASH-MI 3-24


CISCO-FRAME-RELAY-MI 3-24


CISCO-FRAS-HOST-MIB 3-24



CISCO-HSRP-MIB 3-24


CISCO-IETF-IP-FORWARD-MIB 3-25

CISCO-IETF-IP-MIB 3-26, 3-28


CISCO-IPM-ROUTE-MIB 3-26



CISCO-LEC-DATA-VCC-MIB 3-27

CISCO-LEC-EXT-MIB 3-27

CISCO-LECS-MIB 3-27

CISCO-LES-MIB 3-28

CISCO-MEMORY-POOL-MIB 3-27, 3-28

IN-1Cisco 7200 Router MIB Specifications Guide

Index

CISCO-NTP-MIB 3-29

CISCO-PAE-MIB 3-30

CISCO-PIM-MIB 3-30

CISCO-PING-MIB 3-30


CISCO-PRODUCTS-MIB 3-31

CISCO-QLLC01-MIB 3-32

CISCO-QUEUE-MIB 3-32

CISCO-RSRB-MIB 3-32


CISCO-SDLLC-MIB 3-34

CISCO-SMI-MIB 3-34



CISCO-TC-MIB 3-36

CISCO-TCP-MIB 3-36, 3-62


commands, SNMP 2-4

compiling MIBs 2-3

conventions, list 1-xiv

D

DLSW-MIB 3-38

document revision history 1-ix

downloading MIBs 2-2, 2-3

DS1-MIB 3-50, 3-66

DS3-MIB 3-66

E

enabling SNMP 2-4

ENTITY-MIB 3-38

environmental traps A-11

ETHERLIKE-MIB 3-45

EVENT-MIB 3-46

EXPRESSION-MIB 3-47


F

FAQs, SNMP and Cisco MIBs 1-6

I

IF-MIB 3-48

IGMP-MIB 3-49


INT-SERV-MIB 3-49

IPMROUTE-MIB 3-49

L

linkDown and linkUp traps A-12

linkUp and linkDown traps 4-6, A-13

M

mapping A-2

mapping sessions A-27

MIB descriptions

ATM 3-5, 3-7, 3-8

ATM-FORUM-ADDR-REG 3-6

ATM-FORUM-MIB 3-6

BGP4-MIB 3-6


CISCO-AAL5-MIB 3-9




CISCO-CDP-MIB 3-11

CISCO-CLASS-BASED-QOS-MIB 3-11, 3-12



CISCO-ENTITY-ASSET-MIB A-2

CISCO-ENTITY-FRU-CONTROL-MIB A-2

CISCO-ENTITY-VENDORTYPE-OID-MIB 3-21, 3-21 to 3-23, A-2

OL-6384-04

Index






CISCO-HSRP-MIB 3-24





CISCO-MEMORY-POOL-MIB 3-27, 3-28

CISCO-PIM-MIB 3-30

CISCO-PING-MIB 3-30





CISCO-TCP-MIB 3-36


DS1-MIB 3-50, 3-66

DS3-MIB 3-66

EVENT-MIB 3-46

EXPRESSION-MIB 3-47

IF-MIB 3-48

IGMP-MIB 3-49


INT-SERV-MIB 3-49

IPMROUTE-MIB 3-49

MPLS 3-50 to 3-59

MPLS-LDP-MIB 3-50

MPLS-LSR-MIB 3-52

MPLS-TE-MIB 3-57

MPLS-VPN-MIB 3-57

MSDP-MIB 3-59

OLD-CISCO-CHASSIS-MIB 3-60, 3-61, 3-62




OL-6384-04


PIM-MIB 3-63

RFC1213-MIB 3-63

RFC1253-MIB 3-64

RFC1315-MIB 3-64, 3-65

RMON-MIB 3-67

RS232-MIB 3-68

RSVP-MIB 3-68



SNMP-PROXY-MIB 3-69


SNMP-USM-MIB 3-69

SNMP-VACM-MIB 3-70

SONET-MIB 3-71

TCP-MIB 3-71

MIBs

benefits of 1-1, 1-2

compiling 2-3

descriptions, see MIB descriptions 3-1

downloading 2-2, 2-3

OID assignments 1-6

overview 1-2, 1-3

related information 2-2

RFCs 1-5

MIB specifications, see MIB descriptions 3-1

monitoring

QoS A-18, A-22

router interfaces A-12

MPLS-LDP-MIB 3-50

MPLS-LSR-MIB 3-52

MPLS-TE-MIB 3-57

MPLS-VPN-MIB 3-57

MSDP-MI 3-59

MSDP-MIB 3-59

N

new in this guide 1-ix


Index

NOTIFICATION-LOG-MIB 3-59

notifications

description 4-1

NOVELL-IPX-MIB 3-60

NOVELL-RIPSAP-MIB 3-60

O

object identifiers (OIDs) 1-6

OLD-CISCO-APPLETALK-MIB 3-60

OLD-CISCO-CHASSIS-MIB 3-60, 3-61, 3-62


OLD-CISCO-DECNET-MIB 3-61




OLD-CISCO-NOVELL-MIB 3-62

OLD-CISCO-SYSTEM-MIB 3-62

OLD-CISCO-TS-MIB 3-62

P

PIM-MIB 3-63

Q

QoS

configuration information A-14, A-16

indexes A-14, A-15

sample applications A-20, A-22

statistics A-18, A-22

traffic billing A-22, A-25

R

RFC 1213-MIB 3-63

RFC1213-MIB 3-63

RFC 1243-MIB 3-63


RFC 1253-MIB 3-64

RFC1253-MIB 3-64

RFC 1315-MIB 3-64, 3-65

RFC1315-MIB 3-64, 3-65

RFC 1381-MIB 3-66

RFC 1382-MIB 3-66

RFC 2006-MIB 3-66

RFC 2013 3-71

RFC 2571 3-69

RFCs, description of 1-5

RMON2-MIB 3-68

RMON-MIB 3-67

RS232-MIB 3-68

RSVP-MIB 3-68

S

security levels, SNMP 1-4

serial numbers A-3

SMON-MI 3-68

SNMP

benefits 1-1, 1-2

enabling 2-4

FAQs 1-6

MIBs 1-2, 1-3

overview 1-2

Quality of Service, see QoS A-1

related information 1-6

security 1-4

traps 1-3

versions 1-3, 1-4

SNMP agent 4-1

snmpBasicNotificationsGroup

defined 3-70

SNMP commands 2-4


SNMP group

defined 3-70


OL-6384-04

Index

SNMP notifications

description 1-3

SNMP-PROXY-MIB 3-69

snmpSetGroup

defined 3-70


SNMP traps

configuration changes A-11

environmental conditions 4-11, A-11

FRUs A-12

generating A-10, A-11

linkDown and linkUp A-12

linkUp and linkDown 4-6, A-12, A-13

SNMP-USM-MIB 3-69

SNMPv1 1-3

SNMPv2c 1-4

SNMPv2-MIB 3-70

SNMPv3 1-4, GL-8

SNMP-VACM-MIB 3-70

SONET-MIB 3-71

SOURCE-ROUTING-MIB 3-71

specifications, MIB

see MIB descriptions 3-1

System group

defined 3-70

T

TCP-MIB 3-71

terminology 1-xiv

traffic, billing customers for A-22, A-25

traps

description 4-1

traps, description 1-3

U

UDP-MIB 3-71

OL-6384-04

unique device identifier 3-45


Index


OL-6384-04

cisco 7200 series router mib specifications guide · 1 cisco 7200 router mib specifications guide...

Documents