Cisco 7600 Series Router MIB Specifications Guide - Using MIBs [Cisco 7600 Series Routers]

Table Of Contents

Using MIBs

Cisco Unique Device Identifier Support

Cisco Redundancy Features

Levels of Redundancy

Route Processor Redundancy

Route Processor Redundancy Plus

Nonstop Forwarding/Stateful Switchover

MIB Synchronization

Verifying Cisco 7600 Redundancy

Related Information and Useful Links

Managing Physical Entities

Performing Inventory Management

Determining the ifIndex Value for a Physical Port

Monitoring and Configuring FRU Status

Generating SNMP Notifications

Identifying Hosts to Receive Notifications

Configuration Changes

Environmental Conditions

FRU Status Changes

Monitoring Quality of Service

Cisco 7600 QoS Basics

CISCO-CLASS-BASED-QoS-MIB Overview

CISCO-CLASS-BASED-QoS-MIB Object Relationship

QoS MIB Information Storage

QoS Hardware Configuration and Statistic Support

Viewing QoS Configuration Settings Using the CISCO-CLASS-BASED-QOS-MIB

Monitoring Qos Using the CISCO-CLASS-BASED-QOS-MIB

Considerations for Processing QoS Statistics

Sample QoS Statistics Tables

Sample QoS Applications

Checking Customer Interfaces for Service Policies

Retrieving QoS Billing Information

Monitoring Router Interfaces

Enabling Interface linkUp/linkDown Notifications

SNMP Notification Filtering for linkDown Notifications

Billing Customers for Traffic

Input and Output Interface Counts

Determining the Amount of Traffic to Bill to a Customer

Scenario for Demonstrating QoS Traffic Policing

Service Policy Configuration

Packet Counts before the Service Policy Is Applied

Generating Traffic

Packet Counts after the Service Policy Is Applied

Using IF-MIB Counters

Sample Counters

ATM Support for IF-MIB Counters

Related Information and Useful Links

Overview of SIPs, SSCs, and SPAs

Displaying the SIP and SSC Hardware Type

Using MIBs

This chapter describes how to perform tasks on the Cisco 7600 Series router.

•Cisco Unique Device Identifier Support

•Cisco Redundancy Features

•Managing Physical Entities

•Monitoring Quality of Service

–Cisco 7600 QoS Basics

–CISCO-CLASS-BASED-QoS-MIB Overview

–Viewing QoS Configuration Settings Using the CISCO-CLASS-BASED-QOS-MIB

–Monitoring Qos Using the CISCO-CLASS-BASED-QOS-MIB

–Considerations for Processing QoS Statistics

–Sample QoS Applications

•Monitoring Router Interfaces

•Billing Customers for Traffic

•Using IF-MIB Counters

•Overview of SIPs, SSCs, and SPAs

Cisco Unique Device Identifier Support

The ENTITY-MIB now 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 UDI is composed of three separate data elements which must be stored in the entPhysicalTable:

•Orderable product identifier (PID)—Product Identifier (PID). PID is the alphanumeric identifier used by customers to order Cisco products. Two examples include NM-1FE-TX or CISCO3745. PID is limited to 18 characters and must be stored in the entPhysicalModelName object.

•Version identifier (VID)—Version Identifier (VID). VID is the version of the PID. The VID indicates the number of times a product has versioned in ways that are reported to a customer. For example, the product identifier NM-1FE-TX may have a VID of V04. VID is limited to 3 alphanumeric characters and must be stored in the entPhysicalHardwareRev object.

•Serial number (SN)—Serial number is the 11-character identifier used to identify a specific part within a product and must be stored in the entPhysicalSerialNum object. Serial number content is defined by manufacturing part number 7018060-0000. The SN is accessed at the following website by searching on the part number 701806-0000:

https://mco.cisco.com/servlet/mco.ecm.inbiz.inbiz

Serial number format is defined in four fields:

–Location (L)

–Year (Y)

–Workweek (W)

–Sequential serial ID (S)

The SN label will be represented as: LLLYYWWSSS.

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.

Cisco Redundancy Features

This section describes

•Levels of Redundancy

–Route Processor Redundancy

–Route Processor Redundancy Plus

–Nonstop Forwarding/Stateful Switchover

•MIB Synchronization

•Verifying Cisco 7600 Redundancy

•Related Information and Useful Links

Redundancy creates a duplication of data elements and software functions to provide an alternative in case of failure. The goal of Cisco redundancy features is to cut over without affecting the link and protocol states associated with each interface and continue packet forwarding. The state of the interfaces and subinterfaces is maintained, along with the state of line cards and various packet processing hardware.

Levels of Redundancy

This section describes the levels of redundancy supported on the Cisco 7600 router and how to verify that this feature is available. Cisco 7600 routers support fault resistance by allowing a Cisco redundant supervisor engine (SE) to take over if the active supervisor engine fails. Redundancy prevents equipment failures from causing service outages, and supports hitless maintenance and upgrade activities. The state of the interfaces and subinterfaces are maintained along with the state of line cards and various packet processing hardware.

Redundant systems support two route processors. One acts as the active route processor while the other acts as the standby route processor.

The route processor redundancy feature provides high availability for Cisco routers by switching over to the standby route processor when one of the following conditions occur:

•Cisco IOS software failure

•RP hardware failure

•Software upgrade

•Maintenance procedure

Cisco 7600 routers can operate in one of three redundancy modes:

•Route Processor Redundancy (RPR) mode

•Route Processor Redundancy Plus (RPR+) mode

•Nonstop Forwarding/Stateful Switchover (NSF/SSO) mode

In all modes, the standby RP will take over when the active RP fails.

Route Processor Redundancy

This section describes the Route Processor Redundancy (RPR) mode for the Cisco 7600 routers.

When the switch is powered on, RPR runs between two Cisco supervisor engines. The supervisor engine that boots first becomes the RPR active supervisor engine.

Cisco 7600 series routers support fault resistance by allowing a redundant supervisor engine to take over if the active supervisor engine fails.

Route Processor Redundancy Plus

This section describes Route Processor Redundancy Plus (RPR+) mode.

The RPR+ feature is an enhancement of the RPR feature on Cisco 7600 routers. RPR+ keeps the Virtual Interface Processors (VIPs) from being reset and reloaded when a switchover occurs between the active and standby route switch processors (RSPs)

When RPR+ mode is used, the redundant supervisor engine is fully initialized and configured, which shortens the switchover time. The active supervisor engine checks the image version of the redundant supervisor engine when the redundant supervisor engine comes online. If the image on the redundant supervisor engine does not match the image on the active supervisor engine, RPR redundancy mode is used. The supervisor engine that boots first becomes the active supervisor engine.

Note For detailed information about RPR and RPR+ features and how they work, go to:
http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SXF/configuration/guide/redund.html

Nonstop Forwarding/Stateful Switchover

This section describes the Nonstop Forwarding/Stateful Switchover mode. With NSF/SSO, Cisco 7600 routers can fail over from the active to the standby route processor almost immediately while continuing to forward packets. Cisco IOS software NSF/SSO support on this platform enables immediate failover.

In networking devices running NSF/SSO, both RPs must be running the same configuration so that the standby RP is always ready to assume control following a fault on the active RP. The configuration information is synchronized from the active RP to the standby RP at startup and each timechanges to the active RP configuration occur.

Following an initial synchronization between the two processors, NFS/SSO maintains RP state information between them, including forwarding information.

Cisco Nonstop Forwarding (NSF) works with the Stateful Switchover (SSO) to minimize the amount of time a network is unavailable to its users following a Route Processor (RP) fail-over in a router with dual RPs. NSF/SSO capability allows routers to detect a switchover and take the necessary actions to continue forwarding network traffic and to recover route information from peer devices.

Cisco NSF works with the Stateful Switchover (SSO) feature in Cisco IOS software to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of Cisco NSF/SSO is to continue forwarding data packets along known routes while the routing protocol information is being restored following a route switchover.

Note For detailed information about the Nonstop Forwarding/Stateful Switchover feature, go to:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s20/
index.htm

MIB Synchronization

This section describes the level of synchronization supported by the MIBs in Cisco IOS Release 12.2(33)SRA and later. MIBs that are not listed in this section do not synchronize data between the redundant units after a failover:

ATM-MIB
CISCO-ATM-EXT
CISCO-AAL5-MIB
CISCO-CLASS-BASED-QOS
RFC1315-MIB
CISCO-FRAME-RELAY-MIB
SONET-MIB
CISCO-SYSLOG-MIB
MPLS-LDP-MIB
MPLS-VPN-MIB
MPLS-TE-MIB
MPLS-LSR-MIB
OLD-CISCO-CHASSIS-MIB
RFC2495-MIB (DS1)
RFC1407-MIB (DS3)
RFC1315-MIB
MPLS-LDP-MIB
MPLS-VPN-MIB
MPLS-TE-MIB
RFC2495-MIB
RFC1407-MIB
CISCO-CAT6K-CROSSBAR-MIB
CISCO-ENVMON-MIB
CISCO-L2L3-INTERFACE-CONFIG-MIB
CISCO-L2-CONTROL-MIB
CISCO-L2-TUNNEL-CONFIG-MIB
CISCO-LAG-MIB
CISCO-MAC-NOTIFICATION-MIB
CISCO-NDE-MIB
CISCO-PAE-MIB
CISCO-PAGP-MIB
CISCO-PRIVATE-VLAN-MIB
CISCO-RMON-CONFIG-MIB
CISCO-STACK-MIB
CISCO-STP-EXTENSIONS-MIB
CISCO-SWITCH-ENGINE-MIB
CISCO-UDLDP-MIB
CISCO-VLAN-MEMBERSHIP-MIB
CISCO-VTP-MIB
IEEE8021-PAE-MIB
IEEE8023-LAG-MIB
IF-MIB
NOTIFICATION-LOG-MIB
SNMP-COMMUNITY-MIB
SNMP-FRAMEWORK-MIB
SNMP-NOTIFICATION-MIB
SNMP-TARGET-MIB
SNMP-USM-MIB
SNMP-VACM-MIB
SNMPv2-MIB
SMON-MIB
BRIDGE-MIB
CISCO-ENTITY-FRU-CONTROL-MIB
CISCO-ENTITY-SENSOR-MIB
ENTITY-MIB

Verifying Cisco 7600 Redundancy

To display information about the active and standby supervisor engines installed in a Cisco 7600 router, use the show redundancy command and show redundancy states command.
Example 
Router# show redundancy 
7609_vortex#sh redundancy 
Redundant System Information :
------------------------------
       Available system uptime = 1 week, 14 hours, 51 minutes
Switchovers system experienced = 8
              Standby failures = 1
        Last switchover reason = user initiated
                 Hardware Mode = Duplex
    Configured Redundancy Mode = Route Processor Redundancy Plus
     Operating Redundancy Mode = Route Processor Redundancy Plus
              Maintenance Mode = Disabled
                Communications = Up
Current Processor Information :
-------------------------------
               Active Location = slot 5
        Current Software state = ACTIVE
       Uptime in current state = 22 hours, 42 minutes
                 Image Version = Cisco Internetwork Operating System Software 
IOS (tm) s72033_rp Software (s72033_rp-JSV-M), Version 12.2(WEEKLY_PIKESPEAK)pikespeak 
ENGINEERING WEEKLY BUILD, synced to const2 PIKESPEAK_BASE
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Sun 28-Mar-04 06:57 by integ
                          BOOT = disk0:,12
                   CONFIG_FILE = 
                       BOOTLDR = 
        Configuration register = 0x2102
Peer Processor Information :
----------------------------
              Standby Location = slot 6
        Current Software state = STANDBY HOT
       Uptime in current state = 6 days, 19 hours, 20 minutes
                 Image Version = Cisco Internetwork Operating System Software 
IOS (tm) s72033_rp Software (s72033_rp-JSV-M), Version 12.2(WEEKLY_PIKESPEAK)pikespeak 
ENGINEERING WEEKLY BUILD, synced to const2 PIKESPEAK_BASE
Copyright (c) 1986-2008 by cisco Systems, Inc.
Compiled Sun 28-Mar-04 06:57 by integ
                          BOOT = disk0:,12
                   CONFIG_FILE = 
                       BOOTLDR = 
        Configuration register = 0x2102
7609_vortex#sh redundancy states
       my state = 13 -ACTIVE 
     peer state = 8  -STANDBY HOT 
           Mode = Duplex
           Unit = Primary
        Unit ID = 5
Redundancy Mode (Operational) = Route Processor Redundancy Plus
Redundancy Mode (Configured)  = Route Processor Redundancy Plus
     Split Mode = Disabled
   Manual Swact = Enabled
 Communications = Up
   client count = 44
 client_notification_TMR = 30000 milliseconds
          keep_alive TMR = 9000 milliseconds
        keep_alive count = 0 
    keep_alive threshold = 18 
           RF debug mask = 0x0 
Related Information and Useful Links

The following URLs provide access to helpful information about the Cisco redundancy feature:

•Detailed information about Cisco nonstop forwarding:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsnsf20s.html

•Detailed information about the stateful switchover feature:
http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fssso20s.html

•Detailed information about the route processor redundancy plus feature:
http://www.cisco.com/en/US/docs/routers/7600/ios/12.1E/configuration/guide/redund.html

•Detailed information about the route processor redundancy feature:
http://www.cisco.com/en/US/docs/ios/12_1/12_1ex/feature/guide/12e_rpr.html

Managing Physical Entities

This section describes how to use SNMP to manage the physical entities (components) in the router by:

•Performing Inventory Management

–Determining the ifIndex Value for a Physical Port

–Monitoring and Configuring FRU Status

•Monitoring and Configuring FRU Status

•Generating SNMP Notifications

Purpose and Benefits

The physical entity management feature of the Cisco 7600 SNMP implementation does the following:

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

•Provides information about physical port to interface mappings

•Provides asset information for asset tagging

•Provides firmware and software information for chassis components

MIBs Used for Physical Entity Management

•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 and line cards, that are listed in the entPhysicalTable of the ENTITY-MIB.

•CISCO-ENTITY-EXT-MIB - Contains Cisco defined extensions to the entPhysicalTable of the ENTITY-MIB to provide information for entities with an entPhysicalClass value of 'module' that have a CPU, RAM/NVRAM, and/or a configuration register.

•CISCO-ENTITY-SENSOR-MIB and ENTITY-SENSOR-MIB—Contain information about entities in the entPhysicalTable with an entPhysicalClass value of 'sensor'.

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

•CISCO-ENVMON-MIB—Contains information about the status of environmental sensors (for voltage, temperature, fans, and power supplies). For example, this MIB reports the chassis core and inlet temperatures.

•ENTITY-MIB—Contains information for managing physical entities on the router. It also organizes the entities into a containment tree that depicts their hierarchy and relationship to each other. The 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 entAliasMappingTable maps each physical port's entPhysicalIndex value to its corresponding ifIndex value in the IF-MIB ifTable.

–The entPhysicalContainsTable shows the relationship between physical entities in the chassis. For each physical entity, the table lists the entPhysicalIndex for each of the entity's child objects.

Performing Inventory Management

To obtain information about entities in the router, perform a MIB walk on the ENTITY-MIB entPhysicalTable.

As you examine sample 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, and line card ports).

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 is modeled as a container. All removable physical entities should be modeled within a container entity, such as field-replaceable modules, fans, or power supplies.

Sample of ENTITY-MIB entPhysicalTable Entries

The samples in this section show how information is stored in the entPhysicalTable. You can perform asset inventory by examining entPhysicalTable entries.

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

The following display shows the ENTITY-MIB entPhysicalTable sample entries for a FlexWAN card installed in a router chassis and for port adapters inserted into FlexWAN card.

ENTITY-MIB entPhysicalTable Entries
entPhysicalDescr.4000 = WS-X6182-2PA 2 port adapter FlexWAN Rev. 1.3
entPhysicalDescr.4001 = module 5 power-output-fail Sensor
entPhysicalDescr.4002 = module 5 outlet temperature Sensor
entPhysicalDescr.4003 = module 5 inlet temperature Sensor
entPhysicalDescr.4004 = module 5 device-1 temperature Sensor
entPhysicalDescr.4005 = Port Adapter Card Container
entPhysicalDescr.4006 = Port Adapter Card Container
entPhysicalDescr.4100 = ATM WAN E3 Port Adaptor
entPhysicalDescr.4101 = cyBus ENHANCED ATM PA Port
entPhysicalDescr.4200 = ATM WAN OC3 SML Port Adaptor
entPhysicalDescr.4201 = cyBus ENHANCED ATM PA Port
entPhysicalVendorType.4000 = cevC6xxxWsx61822pa
entPhysicalVendorType.4001 = cevSensorModulePowerOutputFail
entPhysicalVendorType.4002 = cevSensorModuleOutletTemp
entPhysicalVendorType.4003 = cevSensorModuleInletTemp
entPhysicalVendorType.4004 = cevSensorModuleDeviceTemp
entPhysicalVendorType.4005 = cevContainerPABay
entPhysicalVendorType.4006 = cevContainerPABay
entPhysicalVendorType.4100 = cevPaAtmdxE3
entPhysicalVendorType.4101 = cevPortAtm
entPhysicalVendorType.4200 = cevPaAtmdxSmlOc3
entPhysicalVendorType.4201 = cevPortAtm
Where entPhysicalVendorType identifies the unique vendor-specific hardware type of the physical entity.
entPhysicalContainedIn.4000 = 6
entPhysicalContainedIn.4001 = 4000
entPhysicalContainedIn.4002 = 4000
entPhysicalContainedIn.4003 = 4000
entPhysicalContainedIn.4004 = 4000
entPhysicalContainedIn.4005 = 4000
entPhysicalContainedIn.4006 = 4000
entPhysicalContainedIn.4100 = 4005
entPhysicalContainedIn.4101 = 4100
entPhysicalContainedIn.4200 = 4006
entPhysicalContainedIn.4201 = 4200
Where entPhysicalContainedIn indicates the entPhysicalIndex of a component's parent entity.
entPhysicalClass.4000 = module(9)
entPhysicalClass.4001 = sensor(8)
entPhysicalClass.4002 = sensor(8)
entPhysicalClass.4003 = sensor(8)
entPhysicalClass.4004 = sensor(8)
entPhysicalClass.4005 = container(5)
entPhysicalClass.4006 = container(5)
entPhysicalClass.4100 = module(9)
entPhysicalClass.4101 = port(10)
entPhysicalClass.4200 = module(9)
entPhysicalClass.4201 = port(10)
Where entPhysicalClass indicates the general type of hardware device.
entPhysicalParentRelPos.4000 = 1
entPhysicalParentRelPos.4001 = 1
entPhysicalParentRelPos.4002 = 2
entPhysicalParentRelPos.4003 = 3
entPhysicalParentRelPos.4004 = 4
entPhysicalParentRelPos.4005 = 0
entPhysicalParentRelPos.4006 = 1
entPhysicalParentRelPos.4100 = 1
entPhysicalParentRelPos.4101 = 0
Where entPhysicalParentRelPos indicates the relative position of this child among the other entities.
entPhysicalName.4000 = 5
entPhysicalName.4001 = module 5 power-output-fail Sensor
entPhysicalName.4002 = module 5 outlet temperature Sensor
entPhysicalName.4003 = module 5 inlet temperature Sensor
entPhysicalName.4004 = module 5 device-1 temperature Sensor
entPhysicalName.4005 = bay 0 of 5
entPhysicalName.4006 = bay 1 of 5
entPhysicalName.4100 = module in bay 0, slot 5
entPhysicalName.4101 = ATM5/0/0
entPhysicalName.4200 = module in bay 1, slot 5
entPhysicalName.4201 = ATM5/1/0
Where entPhysicalName provides the textual name of the physical entity.
entPhysicalHardwareRev.4000 = 1.3
entPhysicalHardwareRev.4001 = 
entPhysicalHardwareRev.4002 = 
entPhysicalHardwareRev.4003 = 
entPhysicalHardwareRev.4004 = 
entPhysicalHardwareRev.4005 = 
entPhysicalHardwareRev.4006 = 
entPhysicalHardwareRev.4100 = 2.01, Board revision B0
entPhysicalHardwareRev.4101 = 
entPhysicalHardwareRev.4200 = 1.00, Board revision A0
Where entPhysicalHardware provides the vendor-specific hardware revision number (string) for the physical entity.
entPhysicalSerialNum.4000 = SAD04480962
entPhysicalSerialNum.4001 = 
entPhysicalSerialNum.4002 = 
entPhysicalSerialNum.4003 = 
entPhysicalSerialNum.4004 = 
entPhysicalSerialNum.4005 = 
entPhysicalSerialNum.4006 = 
entPhysicalSerialNum.4100 = 24155259
entPhysicalSerialNum.4101 = 
entPhysicalSerialNum.4200 = 8239965
Where entPhysicalSerialNumber provides the vendor-specific serial number (string) for the physical entity.
entPhysicalMfgName.4000 = Cisco Systems
entPhysicalMfgName.4001 = 
entPhysicalMfgName.4002 = 
entPhysicalMfgName.4003 = 
entPhysicalMfgName.4004 = 
entPhysicalMfgName.4005 = 
entPhysicalMfgName.4006 = 
entPhysicalMfgName.4100 = Cisco Systems
entPhysicalMfgName.4101 = 
entPhysicalMfgName.4200 = Cisco Systems
entPhysicalMfgName.4201 = 
Where entPhysicalMfgName provides the manufacturer's name for the physical component.
entPhysicalModelName.4000 = WS-X6182-2PA
entPhysicalModelName.4001 = 
entPhysicalModelName.4002 = 
entPhysicalModelName.4003 = 
entPhysicalModelName.4004 = 
entPhysicalModelName.4005 = 
entPhysicalModelName.4006 = 
entPhysicalModelName.4100 = PA-A3-E3
entPhysicalModelName.4101 = 
entPhysicalModelName.4200 = PA-A3-OC3-SML
entPhysicalModelName.4201 = 
Where entPhysicalModelName provides the vendor-specific model name string for the physical component.
entPhysicalIsFRU.4000 = true(1)
entPhysicalIsFRU.4001 = false(2)
entPhysicalIsFRU.4002 = false(2)
entPhysicalIsFRU.4003 = false(2)
entPhysicalIsFRU.4004 = false(2)
entPhysicalIsFRU.4005 = false(2)
entPhysicalIsFRU.4006 = false(2)
entPhysicalIsFRU.4100 = true(1)
entPhysicalIsFRU.4101 = false(2)
entPhysicalIsFRU.4200 = true(1)
entPhysicalIsFRU.4201 = false(2)
Where entPhysicalIsFRU indicates whether or not this physical entity is considered a field replaceable unit (FRU).
Note the following about the sample configuration:

•All chassis slots and line card ports have the same entPhysicalContainedIn value:

–For chassis slots, entPhysicalContainedIn = 1 (the entPhysicalIndex of the chassis).

–For line card ports, entPhysicalContainedIn = 26 (the entPhysicalIndex of the line card).

•Each chassis slot and line card port has a different entPhysicalParentRelPos to show its relative position within the parent object.

Determining the ifIndex Value for a Physical Port

The ENTITY-MIB entAliasMappingIdentifier maps a physical port to an interface by mapping the port's entPhysicalIndex to its corresponding ifIndex value in the IF-MIB ifTable. The following sample shows that the physical port whose entPhysicalIndex is 35 is associated with the interface whose ifIndex value is 4. (See the MIB for detailed descriptions of possible MIB values.)
entAliasMappingIdentifer.35.0 = ifIndex.4
Monitoring and Configuring FRU Status

View objects in the CISCO-ENTITY-FRU-CONTROL-MIB cefcModuleTable to determine the administrative and operational status of FRUs, such as power supplies and line cards:

•cefcModuleAdminStatus—The administrative state of the FRU. Use cefcModuleAdminStatus to enable or disable the FRU.

•cefcModuleOperStatus—The current operational state of the FRU.

Figure A-1 shows a cefcModuleTable entry for a line card whose entPhysicalIndex is 24.

Figure A-1 Sample cefcModuleTable Entry

See the "FRU Status Changes" section for information about how the router generates notifications to indicate changes in FRU status.

Generating SNMP Notifications

This section provides information about the SNMP notifications generated in response to events and conditions on the router, and describes how to identify which hosts are to receive notifications.

•Identifying Hosts to Receive Notifications

•Configuration Changes

•Environmental Conditions

•FRU Status Changes

Identifying Hosts to Receive Notifications

You can use the CLI or SNMP to identify hosts to receive SNMP notifications and to specify the types of notifications they are to receive (notifications 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: notification(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:

•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 notifications. For example, to generate mplsLdpSessionUp or mplsLdpSessionDown notifications, the MPLS-LDP-MIB object mplsLdpSessionUpDownTrapEnable must be set to enabled(1).

Configuration Changes

If entity notifications are enabled, the router generates an entConfigChange notification (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 checks the value of the entLastChangeTime object to detect any entConfigChange notifications that were missed as a result of throttling or transmission loss.

Enabling notifications for Configuration Changes

To configure the router to generate an entConfigChange notification each time its configuration changes, enter the following command from the CLI. Use the no form of the command to disable the notifications.
Router(config)# snmp-server enable traps entity 
Router(config)# no snmp-server enable traps entity 
Environmental Conditions

The 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 notifications

To configure the router to generate notifications for environmental conditions, enter the following command from the CLI. Use the no form of the command to disable the notifications.
Router(config)# snmp-server enable traps envmon 
Router(config)# no snmp-server enable traps envmon 
To enable environmental notifications through SNMP, set the appropriate notification enable object to true(1). For example, ciscoEnvMonEnableShutdownNotification enables shutdown notifications. Disable the notifications by setting the notification object to false(2).

FRU Status Changes

If FRU notifications are enabled, the router generates the following notifications in response to changes in the status of an FRU:

•cefcModuleStatusChange—The operational status (cefcModuleOperStatus) of an FRU changes.

•cefcFRUInserted—An FRU is inserted in the chassis. The notification indicates the entPhysicalIndex of the FRU and the container it was inserted in.

•cefcFRURemoved—An FRU is removed from the chassis. The notification indicates the entPhysicalIndex of the FRU and the container it was removed from.

Note See the CISCO-ENTITY-FRU-CONTROL-MIB for more information about these notifications.

Enabling FRU Notifications

To configure the router to generate notifications for FRU events, enter the following command from the CLI. Use the no form of the command to disable the notifications.
Router(config)# snmp-server enable traps fru-ctrl 
Router(config)# no snmp-server enable traps fru-ctrl 
To enable FRU notifications through SNMP, set cefcMIBEnableStatusNotification to true(1). Disable the notifications by setting cefcMIBEnableStatusNotification to false(2).

Monitoring Quality of Service

This section provides the following information about using Quality of Service (QoS) in your configuration:

•Cisco 7600 QoS Basics

•CISCO-CLASS-BASED-QOS-MIB Overview

•Viewing QoS Configuration Settings Using the CISCO-CLASS-BASED-QOS-MIB

•Monitoring QoS Using the CISCO-CLASS-BASED-QOS-MIB

•Considerations for Processing QoS Statistics

•Sample QoS Applications

Cisco 7600 QoS Basics

The Cisco 7600 distributes QoS features across the PFC in the Supervisor720/RSP720 and the line cards. Line cards are designed to provide QoS features applicable to their roles.

The QoS features are distributed as follows:

•PFC3 on Supervisor/RSP720 - provides centralized policing and marking for Catalyst non DFC3 capable LAN and OSM cards. Does not provide packet buffering or queueing capabilities.

•PFC3 or DFC3 integrate in SIP-600 - provides policing and marking in the line card. Does not provide packet buffering or queueing capabilities.

•Catalyst LAN Ports- provides distributed packet buffering, queueing (hardware based), scheduling, strict priority, WRR, DWWR, WRED.

•SIP-600 Ports - packet buffering, queueing (software based), scheduling, shaping, CBWFQ, LLQ, WRED, etc. NOTE - policing and marking done by integrated DFC3.

•OSM WAN cards- provides distributed packet buffering, queueing (software based), scheduling, shaping, CBWFQ, LLQ, WRED.

•FlexWAN, SIP-200, SIP-400 - policing without depending on PFC3, marking without depending on PFC3, packet buffering, queueing (software based), scheduling, shaping, CBWFQ, LLQ, WRED, etc. FlexWAN and SIP-200 support WFQ.

Table A-1 lists the QoS mechanisms in the Cisco 7600 and the component function.

Table A-1 Cisco QoS Mechanism Functions

QoS Mechanism

Component Performing Function

Input Queue Scheduling

Performed by line card port ASICs

Classification

•Performed by PFC3/DFC3 for LAN card, OSM, SIP-600

•Performed by FlexWAN, SIP-200, SIP-400 processor

Marking

•Performed by PFC3/DFC3 for LAN card, OSM, SIP-600

•Performed by FlexWAN, SIP-200, SIP-400 processor

Policing

•Performed by PFC3/DFC3 for LAN card, OSM, SIP-600

•Performed by FlexWAN, SIP-200, SIP-400 processor

Packet Re-write

Performed by line card port ASICs

Output Queue Scheduling

Performed by line card port ASICs

CISCO-CLASS-BASED-QoS-MIB Overview

The CISCO-CLASS-BASED-QOS-MIB provides read only 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).

CISCO-CLASS-BASED-QoS-MIB Object Relationship

To understand how to navigate the CISCO-CLASS-BASED-QOS-MIB tables, it is important to understand the relationship among different QoS objects. QoS objects consists of:

•Match Statement—specific match criteria to identify packets for classification purposes.

•Class Map—a user-defined traffic class that contains 1 or more match statements used to classify packets into different categories.

•Feature Action—a QoS feature. Features include police, traffic shaping, queueing, random detect, and packet marking. After the traffic has been classified we apply actions to each traffic class.

•Policy Map—a user-defined policy that associates a Qos feature action to the user-define class map.

•Service Policy—a policy map that has been attached to an interface.

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

•cbQosObjectsIndex - identifies each QoS feature on the router.

•cbQoSConfigIndex n- identifies a type of QoS configuration. This index is shared by QoS objects that have identical configuration.

•cbQosPolicyIndex - identifies a unique service policy.

QoS MIB Information Storage

CISCO-CLASS-BASED-QOS-MIB information is stored in:

•Configuration instances - includes all class maps, policy map, match statements, and feature action configuration parameters. Might have multiple identical instances. Multiple instances of the same QoS feature share a single configuration object, which is identified by cbQosConfigIndex.

•Runtime Statistics instances—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.

QoS Hardware Configuration and Statistic Support

The CISCO-CLASS-BASED-QOS-MIB does not cover all the Cisco 7600 QoS hardware configuration and statistics.

•For Catalyst LAN cards, the MIB only provides:

–Policer configuration

–Class map configuration

–Aggregate policer stats for MQC based policer

–Class map stats

For Catalyst LAN cards, the MIB does not provide:

–Queueing configuration

–Queueing statistics

–Microflow policers stats

–Aggregate policer stats for named policer

Figure A-2 shows how these indexes provide access to QoS configuration information and statistics.

Figure A-2 Cisco 7600 Series Internet Router QoS Indexes

Accessing QoS Configuration Information

To access QoS configuration information and statistics for a particular QoS feature:

Step 1 Look in cbQosServicePolicyTable and find the cbQosPolicyIndex assigned to the policy in which the feature is used.

Step 2 Use cbQosPolicyIndex to access the cbQosObjectsTable, and find the cbQosObjectsIndex and cbQosConfigIndex assigned to the QoS feature.

a. Use cbQosConfigIndex to access configuration tables (cbQosxxxCfgTable) for information about the

b. Use cbQosPolicyIndex and cbQosObjectsIndex to access QoS statistics tables (cbQosxxxStatsTable) for information about the QoS feature.

Viewing QoS Configuration Settings Using the CISCO-CLASS-BASED-QOS-MIB

This section contains examples that show how QoS configuration settings are stored in CISCO-CLASS-BASED-QOS-MIB tables. The samples show information grouped by QoS object; however, the actual output of an SNMP query might show QoS information similar to the following.

Note This is only a partial display of all QoS information.
7600# getmany -v3 10.86.0.94 test-user ciscoCBQosMIB
cbQosIfType.1047 = subInterface(2)
cbQosIfType.1052 = subInterface(2)
cbQosPolicyDirection.1047 = input(1)
cbQosPolicyDirection.1052 = output(2)
cbQosIfIndex.1047 = 36
cbQosIfIndex.1052 = 36
cbQosFrDLCI.1047 = 0
cbQosFrDLCI.1052 = 0
cbQosAtmVPI.1047 = 0
cbQosAtmVPI.1052 = 0
cbQosAtmVCI.1047 = 0
cbQosAtmVCI.1052 = 0
cbQosConfigIndex.1047.1047 = 1045
cbQosConfigIndex.1047.1048 = 1025
cbQosConfigIndex.1047.1050 = 1027
cbQosConfigIndex.1047.1051 = 1046
cbQosConfigIndex.1052.1052 = 1045
cbQosConfigIndex.1052.1053 = 1025
cbQosConfigIndex.1052.1055 = 1027
cbQosConfigIndex.1052.1056 = 1046
cbQosObjectsType.1047.1047 = policymap(1)
cbQosObjectsType.1047.1048 = classmap(2)
cbQosObjectsType.1047.1050 = matchStatement(3)
cbQosObjectsType.1047.1051 = police(7)
cbQosObjectsType.1052.1052 = policymap(1)
cbQosObjectsType.1052.1053 = classmap(2)
cbQosObjectsType.1052.1055 = matchStatement(3)
cbQosObjectsType.1052.1056 = police(7)
cbQosParentObjectsIndex.1047.1047 = 0
cbQosParentObjectsIndex.1047.1048 = 1047
cbQosParentObjectsIndex.1047.1050 = 1048
cbQosParentObjectsIndex.1047.1051 = 1048
cbQosParentObjectsIndex.1052.1052 = 0
cbQosParentObjectsIndex.1052.1053 = 1052
cbQosParentObjectsIndex.1052.1055 = 1053
cbQosParentObjectsIndex.1052.1056 = 1053
cbQosPolicyMapName.1045 = pm-1Meg
cbQosPolicyMapDesc.1045 =
cbQosCMName.1025 = class-default
cbQosCMDesc.1025 =
cbQosCMInfo.1025 = matchAny(3)
. . .
Monitoring Qos Using the CISCO-CLASS-BASED-QOS-MIB

This section describes how to monitor QoS on the router by checking the QoS statistics in the CISCO-CLASS-BASED-QOS-MIB tables.

Note The CISCO-CLASS-BASED-QOS-MIB might contain more information than what is displayed in the output of CLI show commands.

Table A-2 lists the types of QoS statistics tables.

Table A-2 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 counts of bytes and octets transmitted.

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 samples, these counters are shown as 33-bit counters.

When accessing QoS counter statistics, 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 Statistics Tables

The samples in this section show the counters in CISCO-CLASS-BASED-QOS-MIB statistics tables:

•Figure A-3 shows the counters in the cbQosCMStatsTable and the indexes for accessing these and other statistics.

•Figure A-4 shows the counters in cbQosMatchStmtStatsTable, cbQosPoliceStatsTable, cbQosQueueingStatsTable, cbQosTSStatsTable, and cbQosREDClassStatsTable.

For ease-of-use, the following figures show some counters as a single object even though the counter is implemented as three objects. For example, cbQosCMPrePolicyByte is implemented as:

•cbQosCMPrePolicyByteOverflow

•cbQosCMPrePolicyByte

•cbQosCMPrePolicyByte64

Figure A-3 QoS Class Map Statistics and Indexes

Figure A-4 QoS Statistics Tables

Sample QoS Applications

This section presents examples of 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 topics include:

•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 if 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 if a service policy has been associated with the transmit and receive directions of a customer interface. Mark noncustomer 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-IF
END-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;
     END-IF
  END-IF
END-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-IF
END-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-IF
END-FOR
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-IF
END-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-WHILE
RETURN total;
Monitoring Router Interfaces

This 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 Notifications

To determine if an interface has failed, you can monitor linkDown and linkUp notifications for the interface. See the "Enabling Interface linkUp/linkDown Notifications" section for instructions on how to enable these notifications.

•linkDown—Indicates that an interface failed or is about to fail.

•linkUp—Indicates that an interface is no longer in the Down state.

Enabling Interface linkUp/linkDown Notifications

To 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 notifications:

Step 1 Issue the following CLI command to enable linkUp and linkDown notifications for most, but not necessarily all, interfaces:
Router(config)# snmp-server enable traps snmp linkdown linkup 
Step 2 View the setting of the ifLinkUpDownTrapEnable object (IF-MIB ifXTable) for each interface to determine if linkUp and linkDown notifications are enabled or disabled for that interface.

Step 3 To enable linkUp and linkDown notifications on an interface, set ifLinkUpDownTrapEnable to enabled(1). To configure the router to send linkDown notifications only for the lowest layer of an interface, see the "SNMP Notification Filtering for linkDown Notifications" section.

Step 4 To enable the Internet Engineering Task Force (IETF) standard for linkUp and linkDown notifications, 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 notifications on ATM subinterfaces, issue the following command:
Router(config)# snmp-server enable traps atm subif 
Step 6 To enable linkUp and linkDown notifications on an ATM permanent virtual circuit (PVC), issue the following commands. In the first command, interval specifies the minimum interval between successive notifications, 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 notifications, use the no form of the appropriate command.

SNMP Notification Filtering for linkDown Notifications

Use the SNMP notification filtering feature to filter linkDown notifications so that SNMP sends a linkDown notification only if the main interface goes down. If an interfaces goes down, all of its subinterfaces go down, which results in numerous linkDown notifications for each subinterface. This feature filters out those subinterface notifications.

This feature is turned off by default. To enable the SNMP notification filtering feature, issue the following CLI command. Use the no form of the command to disable the feature.
[no] snmp ifmib trap throttle 
Billing Customers for Traffic

This section describes how to use SNMP interface counters and QoS data information to determine the amount to bill customers for traffic. It also includes a scenario for demonstrating that a QoS service policy attached to an interface is policing traffic on that interface.

This section contains the following topics:

•Determining the Amount of Traffic to Bill to a Customer

•Scenario for Demonstrating QoS Traffic Policing

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.

For detailed constraints about IF-MIB counter support, see the "IF-MIB (RFC 2863)" section on page 3-110.

Read the following important information about the IF-MIB counter support:

•Unless noted, all IF-MIB counters are supported on Cisco 7600 interfaces.

•For IF-MIB high capacity counter support, Cisco conforms to the RFC 2863 standard. The RFC 2863 standard states that for interfaces that operate:

–At 20 million bits per second or less, 32-bit byte and packet counters must be supported.

–Faster than 20 million bits per second and slower than 650,000,000 bits per second, 32-bit packet counters and 64-bit octet counters must be supported.

–At 650,000,000 bits per second or faster, 64-bit packet counters and 64-bit octet counters must be supported.

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

Perform 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 need this information in the following steps.

Step 3 Access the cbQosPoliceConformedPkt object (cbQosPoliceStatsTable) for the customer to determine the amount of traffic on the interface that 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 Policing

This 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 is 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.

Note In the above scenario, the Cisco 7600 Series 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 7600 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:

CLI Command Output
7600# 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
SNMP Output
7600# getone -v2c 10.86.0.63 public ifDescr.65
ifDescr.65 = GigabitEthernet6/0/0.10-802.1Q vLAN subif
Generating Traffic

The following set of ping commands generates traffic:
7600# ping
Protocol [ip]:
Target IP address: 10.0.0.18
Repeat count [5]: 99 
Datagram size [100]: 1400
Timeout in seconds [2]: 1
Extended 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 Output
7600# show policy-map interface g6/0/0.10
GigabitEthernet6/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 Output
7600# getmany -v2c 10.86.0.63 public ciscoCBQosMIB
        . . .
      cbQosCMDropPkt.1143.1145 = 57
        . . .
      cbQosPoliceConformedPkt.1143.1151 = 42
        . . .
Using IF-MIB Counters

This section describes the IF-MIB counters and how you can use them on various interfaces and subinterfaces. The subinterface counters are specific to the protocols. This section addresses the IF-MIB counters for ATM interfaces.

The IF-MIB counters are defined with respect to lower and upper layers:

•ifInDiscards—The number of inbound packets which were discarded, even though no errors were detected to prevent their being deliverable to a higher-layer protocol. One reason for discarding such a packet could be to free up buffer space.

•IfInErrors—The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol for packet-oriented interfaces.

•ifInUnknownProtos—The number of packets received through the interface which were discarded because of an unknown or unsupported protocol for packet-oriented interfaces.

•ifOutDiscards—The number of outbound packets which were discarded even though no errors were detected to prevent their being transmitted. One reason for discarding such a packet is to free up buffer space.

•ififOutErrors—The number of outbound packets that could not be transmitted because of errors for packet-oriented interfaces.

The logical flow for counters works as follows:

1. When a packet arrives on an interface, check for the following:

a. Error in packet—If any errors are detected, increment ifInErrors and drop the packet.

b. Protocol errors—If any errors are detected, increment ifInUnknownProtos and drop the packet.

c. Resources (buffers)—If unable to get resources, increment ifInDiscards and drop the packet.

d. Increment ifInUcastPkts/ ifInNUcastPkts and process the packet (At this point, increment the ifInOctets with the size of packet).

2. When a packet is to be sent out of an interface:

a. Increment ifOutUcasePkts/ ifOutNUcastPkts (Here we also increment ifOutOctets with the size of packet).

b. Check for error in packet and if there are any errors in packet, increment ifOutErrors and drop the packet.

c. Check for resources (buffers) and if you cannot get resources then increment ifOutDiscards and drop packet.

This following output is an example IF-MIB entries:

IfXEntry ::=
    SEQUENCE {
        ifName                  DisplayString,
        ifInMulticastPkts       Counter32,
        ifInBroadcastPkts       Counter32,
        ifOutMulticastPkts      Counter32,
        ifOutBroadcastPkts      Counter32,
        ifHCInOctets            Counter64,
        ifHCInUcastPkts         Counter64,
        ifHCInMulticastPkts     Counter64,
        ifHCInBroadcastPkts     Counter64,
        ifHCOutOctets           Counter64,
        ifHCOutUcastPkts        Counter64,
        ifHCOutMulticastPkts    Counter64,
        ifHCOutBroadcastPkts    Counter64,
        ifLinkUpDownTrapEnable  INTEGER,
        ifHighSpeed             Gauge32,
        ifPromiscuousMode       TruthValue,
        ifConnectorPresent      TruthValue,
        ifAlias                 DisplayString,
        ifCounterDiscontinuityTime TimeStamp
Sample Counters

The high capacity counters are 64-bit versions of the basic ifTable counters. They have the same basic semantics as their 32-bit counterparts; their syntax is extended to 64 bits.

Table A-3 lists capacity counter object identifiers (OIDs).

Table A-3 Capacity Counters Object Identifiers

Name

Object Identifier (OID)

ifHCInOctets

::= { ifXEntry 6 }

ifHCInUcastPkts

::= { ifXEntry 7 }

ifHCInMulticastPkts

::= { ifXEntry 8 }

ifHCInBroadcastPkts

::= { ifXEntry 9 }

ifHCOutOctets

::= { ifXEntry 10 }

ifHCOutUcastPkts

::= { ifXEntry 11 }

ifHCOutMulticastPkts

::= { ifXEntry 12 }

ifHCOutBroadcastPkts

::= { ifXEntry 13 }

ifLinkUpDownTrapEnable

::= { ifXEntry 14 }

ifHighSpeed

::= { ifXEntry 15 }

ifPromiscuousMode

::= { ifXEntry 16 }

ifConnectorPresent

::= { ifXEntry 17 }

ifAlias

::= { ifXEntry 18 }

ifCounterDiscontinuityTime

::= { ifXEntry 19 }

ATM Support for IF-MIB Counters

This section describes the IF-MIB counters and how they can be used on various interfaces and subinterfaces. The subinterface counters are specific to the protocol. Table A-4 lists the support of the counters on ATM interfaces.

Note Discards and errors are not supported on all platforms and high capacity 64-bit counters are not supported on all platforms. Check with your system administrator.
ATM sub-interfaces:
Layering:
AAL5 sub layer 	AAL5 sub-interface sub-layer
  |   
ATM sub layer 	ATM sub-interface sun-layer
  |
ATM Physical Layer
Example:
[15] ATM4/0 (sonet)
   `- [16] ATM4/0-atm layer (atm)
        +- [17] ATM4/0.0-atm subif (atmSubInterface)
        |    `- [19] ATM4/0.0-aal5 layer (aal5)
        `- [18] ATM4/0-aal5 layer (aal5)
ATM sublayer does not support any counters including the octet counters (ifInOctets/ ifOutOctets). Packets and octet counts are available only at the AAL5 layer entries because most ATM interfaces do not support cell layer counts.

Note The following counters are not supported at the ATM sublayer: ifInUcastPkts, ifInNUcastPkts, ifOutUcastPkts, ifOutNUcastPkts,fInBroadcastPkts, ifOutBroadcastPkts, ifInMulticastPkts, ifOutMulticastPkts, ifInDiscards, ifHCInUcastPkts, ifHCInMulticastPkts, ifHCInBroadcastPkts, ifHCOutUcastPkts, ifHCOutMulticastPkts, ifHCOutBroadcastPkts, ifSpecific

Note At the AAL5 sublayer, all packet counts are at 48-byte cell count. AAL5 layer supports octet and packets counters, but not broadcast and multicast counters.

Table A-4 Cisco 7600 ATM Support for IF-MIB Counters

Counter

Main Interface

Subinterface

Physical

ATM

AAL5

ATM

AAL5

ifInOCtets

Y

N

Y

N

Y

ifInUcastPkts

Y

N

Y

N

Y

ifInNUcastPkts

Y

N

Y

N

Y

ifInDiscards

Y

N

Y

N

Y

ifInErrors

Y

N

Y

N

Y

ifInUnknownProtos

Y

N

Y

N

Y

ifOutOctets

Y

N

Y

N

Y

ifOutUcastPkts

Y

N

Y

N

Y

ifOutNUcastPkts

Y

N

Y

N

Y

ifOutDiscards

Y

N

Y

N

Y

ifOutErrors

Y

N

Y

N

N

ifInMulticastPkts

N

N

N

N

N

ifInBroadcastPkts

N

N

N

N

N

ifOutMulticastPkts

N

N

N

N

N

ifOutBroadcastPkts

N

N

N

N

N

ifHCInOctets

Y

N

Y

N

Y

ifHCInUcastPkts

Y

N

Y

N

Y

ifHCInMulticastPkts

N

N

N

N

N

ifHCInBroadcastPkts

N

N

N

N

N

ifHCOutOctets

Y

N

Y

N

Y

ifHCOutUcastPkts

Y

N

Y

N

Y

ifHCOutMulticastPkts

N

N

N

N

N

ifHCOutBroadcastPkts

N

N

N

N

N

Related Information and Useful Links

The following URLs provide access to helpful information about Cisco IF-MIB counters:

•Frequently asked questions about SNMP counters:

http://www.cisco.com/warp/public/477/SNMP/faq-snmpcounter.shtml

•Access Cisco IOS MIB Tools from the following URL:

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

Overview of SIPs, SSCs, and SPAs

The following list describes some of the general characteristics of Cisco SIPs, SPAs (shared port adapter), and SSCs.

•A SIP (SPA Interface Processor) is a carrier card that:

–Inserts into a router slot like a line card. It provides no network connectivity on its own.

–Contains one or more subslots, which are used to house one or more SPAs. The SPA provides interface ports for network connectivity.

–Resides in the router fully populated either with functional SPAs in all subslots during normal operation or with a blank filler plate (SPA-BLANK=) inserted in all empty subslots.

–Support online insertion and removal (OIR) with SPAs inserted in their subslots. SPAs also support OIR and can be inserted or removed independently from the SIP.

•A SSC (SPA Service Card) is a carrier card that:

–Inserts into a router slot like a line card. It provides no network connectivity.

–Provides one or more subslots, which are used to house one or more SPAs. The supported SPAs do not provide interface ports for network connectivity, but provide certain services.

–Rresides in the router fully populated either with functional SPAs in all subslots during normal operation or with a blank filler plate (SPA-BLANK=) inserted in all empty subslots.

–Supports online insertion and removal (OIR) with SPAs inserted in their subslots. SPAs also support OIR and can be inserted or removed independently from the SSC.

•A SPA (Shared Port Adapter) is a modular type of port adapter that:

–Inserts into a subslot of a compatible SIP carrier card to provide network connectivity and increased interface port density. A SIP can hold one or more SPAs, depending on the SIP type.

–Provides services rather than network connectivity and insert into subslots of compatible SSCs. For example, the IPSec VPN SPA provides services such as IP Security (IPSec) encryption/decryption, generic routing encapsulation (GRE), and Internet Key Exchange (IKE) key generation.

–Are available in single-height (inserts into one SIP subslot) and double-height (inserts into two single, vertically aligned SIP subslots).

Displaying the SIP and SSC Hardware Type

To verify the SIP or SSC hardware type that is installed in your Cisco 7600 series router, you can use the show module command. There are other commands on the Cisco 7600 series router that also provide SIP hardware information, such as the show idprom command and show diagbus command. For a summary of some other SIP and SSC commands, see http://www.cisco.com/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a0080440139.html

Table 3-1 shows the hardware description that appears in the show module and show idprom command output for each type of SIP that is supported on the Cisco 7600 series router.

Table A-5 Cisco 7600 SIP Hardware Descriptions

SIP

Description in show module and show idprom Commands

Cisco 7600 SIP-200

4-subslot SPA Interface Processor-200 / 7600-SIP-200

Cisco 7600 SIP-400

4-subslot SPA Interface Processor-400 / 7600-SIP-400

Cisco 7600 SIP-600

1-subslot SPA Interface Processor-600 / 7600-SIP-600

Cisco 7600 SSC-400

2-subslot Services SPA Carrier-400 / 7600-SSC-400

Example A-1 Example of the show module Command

The following example shows output from the show module command on the Cisco 7600 series router with a Cisco 7600 SIP-400 installed in slot 13:

Router# show module 13

Mod Ports Card Type Model Serial No.

--- ----- -------------------------------------- ------------------ -----------

13 0 4-subslot SPA Interface Processor-400 7600-SIP-400 JAB0851042X

Mod MAC addresses Hw Fw Sw Status

--- ---------------------------------- ------ ------------ ------------ -------

13 00e0.aabb.cc00 to 00e0.aabb.cc3f 0.525 12.2(PP_SPL_ 12.2(PP_SPL_ Ok

Mod Online Diag Status

--- -------------------

13 Pass

Example A-2 Example of the show idprom Command

The following example shows sample output for a Cisco 7600 SIP-200 installed in slot 4 of the router:

Router# show idprom module 4

IDPROM for module #4

(FRU is '4-subslot SPA Interface Processor-200')

OEM String = 'Cisco Systems'

Product Number = '7600-SIP-200'

Serial Number = 'SAD0738006Y'

Manufacturing Assembly Number = '73-8272-03'

Manufacturing Assembly Revision = '03'

Hardware Revision = 0.333

Current supplied (+) or consumed (-) = -4.77A

Note For an overview of the Management Information Base (MIB) support for the Cisco 7600 SIP-200, Cisco 7600 SIP-400, Cisco 7600 SIP-600, and Cisco 7600 SSC-400, see:
http://www.cisco.com/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a008044013b.html#wp1073614