Cisco ASR 9000 Series Aggregation Services Router MIB Specification Guide
Chapter 3 - Cisco ASR 9000 Series Routers MIB Specifications
Downloads: This chapterpdf (PDF - 1.99MB) The complete bookPDF (PDF - 2.96MB) | Feedback

Table of Contents

Cisco ASR 9000 Series Routers MIB Specifications

Cisco ASR 9000 Series Routers MIBs

Cisco ASR 9000 Series Routers MIB Categories

Supported MIBs

Unsupported MIBs

MIB Version String Description

MIBs in the Cisco ASR 9000 Series Routers

MIB Notification Names in the Cisco ASR 9000 Series Routers

ATM-MIB

MIB Constraints

ATM-FORUM-MIB

ATM2-MIB

MIB Constraints

BGP4-MIB

MIB Constraints

BRIDGE-MIB

MIB Constraints

CISCO-AAA-SERVER-MIB

CISCO-ACL-MIB

CISCO-ATM-EXT-MIB

MIB Constraints

CISCO-ATM-QOS-MIB

MIB Constraints

CISCO-BGP4-MIB

MIB Constraints

CISCO-BGP-POLICY-ACCOUNTING-MIB

CISCO-BULK-FILE-MIB

MIB Constraints

CISCO-CDP-MIB

MIB Constraints

CISCO-CLASS-BASED-QOS-MIB

MIB Tables

MIB Constraints

CISCO-CONFIG-COPY-MIB

MIB Constraints

CISCO-CONFIG-MAN-MIB

CISCO-CONTEXT-MAPPING-MIB

MIB Constraints

CISCO-DS3-MIB

MIB Constraints

CISCO-ENHANCED-IMAGE-MIB

CISCO-ENHANCED-MEMPOOL-MIB

MIB Constraints

CISCO-ENTITY-ASSET-MIB

MIB Tables

MIB Constraints

CISCO-ENTITY-FRU-CONTROL-MIB

MIB Tables

MIB Constraints

CISCO-ENTITY-REDUNDANCY-MIB

MIB Tables

MIB Constraints

CISCO-ENTITY-SENSOR-MIB

MIB Tables

MIB Constraints

MIB Usage Values for Cisco Transceivers

CISCO-ENTITY-STATE-EXT-MIB

MIB Tables

MIB Constraints

CISCO-FLASH-MIB

MIB Constraints

CISCO-FLOW-CLONE-MIB

MIB Tables

MIB Constraints

CISCO-FLOW-MONITOR-MIB

MIB Constraints

CISCO-FRAME-RELAY-MIB

CISCO-FTP-CLIENT-MIB

CISCO-HSRP-EXT-MIB

MIB Constraints

CISCO-HSRP-MIB

MIB Constraints

CISCO-IETF-BFD-MIB

MIB Tables

MIB Constraints

CISCO-IETF-FRR-MIB

MIB Constraints

CISCO-IETF-MPLS-TE-P2MP-STD-MIB

MIB Objects

MIB Constraints

CISCO-IETF-IPMROUTE-MIB

MIB Constraints

CISCO-IETF-MSDP-MIB

MIB Constraints

CISCO-IETF-PIM-MIB

MIB Constraints

CISCO-IETF-PIM-EXT-MIB

MIB Constraints

CISCO-IETF-PW-ENET-MIB

MIB Constraints

CISCO-IETF-PW-MIB

MIB Constraints

CISCO-IETF-PW-FR-MIB

MIB Objects

MIB Constraints

CISCO-IETF-PW-MPLS-MIB

MIB Constraints

CISCO-IETF-PW-TC-MIB

CISCO-IETF-VPLS-BGP-EXT-MIB

MIB Constraints

CISCO-IETF-VPLS-GENERIC-MIB

MIB Tables

MIB Constraints

CISCO-IETF-VPLS-LDP-MIB

MIB Constraints

CISCO-IF-EXTENSION-MIB

MIB Tables

MIB Constraints

CISCO-IP-CBR-METRICS-MIB

MIB Objects

MIB Constraints

CISCO-IP-TAP-MIB

MIB Tables

MIB Constraints

CISCO-IP-STAT-MIB

MIB Tables

CISCO-IPSEC-MIB

MIB Objects

MIB Constraints

CISCO-IPSEC-FLOW-MONITOR-MIB

MIB Objects

MIB Constraints

CISCO-LICENSE-MGMT-MIB

MIB Objects

MIB Constraints

CISCO-LPTS-MIB

CISCO-MEMORY-POOL-MIB

CISCO-MLD-SNOOPING-MIB

MIB Objects

MIB Constraints

CISCO-MPLS-TE-STD-EXT-MIB

CISCO-NETSYNC-MIB

MIB Objects

MIB Constraints

CISCO-NTP-MIB

MIB Constraints

CISCO-OAM-MIB

MIB Objects

MIB Constraints

CISCO-OTN-IF-MIB

MIB Objects

CISCO-PTP-MIB

MIB Objects

MIB Constraints

CISCO-P2P-IF-MIB

MIB Constraints

CISCO-PIM-MIB

CISCO-PING-MIB

MIB Constraints

CISCO-PROCESS-MIB

CISCO-RF-MIB

MIB Constraints

CISCO-RTTMON-MIB

MIB Constraints

CISCO-SELECTIVE-VRF-DOWNLOAD-MIB

MIB Tables

MIB Constraints

CISCO-SONET-MIB

MIB Tables

MIB Constraints

CISCO-SUBSCRIBER-SESSION-MIB

MIB Tables

CISCO-SYSLOG-MIB

MIB Constraints

CISCO-SYSTEM-MIB

MIB Constraints

CISCO-TAP2-MIB

MIB Objects

MIB Constraints

CISCO-TCP-MIB

CISCO-VPDN-MGMT-MIB

MIB Objects

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB

DISMAN-EXPRESSION-MIB

MIB Tables

DOT3-OAM-MIB

MIB Tables

MIB Constraints

DS1-MIB (RFC 2495)

MIB Tables

MIB Constraints

DS3-MIB

MIB Tables

MIB Constraints

ENERGY-OBJECT-MIB

ENTITY-MIB (RFC 2737)

MIB Tables

MIB Constraints

ENTITY-STATE-MIB

MIB Constraints

ETHERLIKE-MIB (RFC 2665, 3635)

MIB Constraints

EVENT-MIB

MIB Constraints

EXPRESSION-MIB

FRAME-RELAY-DTE-MIB

MIB Constraints

IEEE8021-CFM-MIB

MIB Objects

MIB Constraints

IEEE8023-LAG-MIB

MIB Constraints

IETF-TCP-MIB

MIB Tables

IETF-UDP-MIB

MIB Tables

IF-MIB (RFC 2863)

MIB Tables

MIB Constraints

IMA-MIB

MIB Objects

MIB Constraints

IP-FORWARD-MIB

MIB Constraints

IP-MIB

MIB Tables

MIB Constraints

IPV6-MIB

MIB Tables

MIB Constraints

IPV6-FORWARD-MIB

MIB Objects

MIB Constraints

IPV6-MLD-MIB

MIB Objects

MIB Constraints

IPV6-TC

ISIS-MIB

MIB Constraints

MAU-MIB

MIB Constraints

MEF-SOAM-PM-MIB

MFR-MIB

MIB Objects

MIB Constraints

MGMD-STD-MIB

MIB Objects

MIB Constraints

MPLS-L3VPN-STD-MIB

MIB Constraints

MPLS-LDP-GENERIC-STD-MIB

MIB Constraints

MPLS-LDP-STD-MIB

MIB Constraints

MPLS-LSR-STD-MIB

MIB Constraints

MPLS-TC-STD-MIB

MPLS-TE-STD-MIB

MIB Constraints

NOTIFICATION-LOG-MIB

OSPF-MIB

MIB Tables

MIB Constraints

OSPF-TRAP-MIB

OSPFV3-MIB

MIB Constraints

PIM-M IB

MIB Objects

MIB Constraints

RADIUS-ACC-CLIENT-MIB

RADIUS-AUTH-CLIENT-MIB

RFC1213-MIB

MIB Objects

RFC 2011-MIB

MIB Objects

MIB Constraints

RFC 2465-MIB

MIB Objects

MIB Constraints

RSVP-MIB

MIB Constraints

SNMP-COMMUNITY-MIB (RFC 2576)

SNMP-FRAMEWORK-MIB (RFC 2571)

SNMP-NOTIFICATION-MIB (RFC 2573)

SNMP-TARGET-MIB (RFC 2573)

SNMP-USM-MIB (RFC 2574)

SNMPv2-MIB (RFC 1907)

SNMP-VACM-MIB

SONET-MIB (RFC 2558)

MIB Tables

MIB Constraints

TCP-MIB

MIB Constraints

UDP-MIB

MIB Constraints

VRRP-MIB

MIB Constraints

Cisco ASR 9000 Series Routers MIB Specifications

This chapter describes the Management Information Base (MIB) on the Cisco ASR 9000 Series router. Each MIB description lists any constraints on how the MIB or its object identifiers (OIDs) are implemented on the Cisco ASR 9000 Series router.

Unless noted otherwise, the Cisco ASR 9000 Series router implementation of a MIB follows the standard MIB that has been defined. Any MIB table or object not listed in the table is implemented as defined in the standard MIB definition.

This chapter includes the following sections:

Cisco ASR 9000 Series Routers MIBs

Each MIB description lists relevant constraints about the MIB’s implementation on the Cisco ASR 9000 Series router platform. Any objects not listed in a table are implemented as defined in the MIB. For detailed MIB descriptions, see the standard MIB.


Note • Not all MIBs included in a Cisco IOS XR 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 ASR 9000 Series Router platform.

  • Certain MIBs return a numeric value along with the MIB object. These numerical values are shown in parentheses in the Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide. For example, the CISCO-ENHANCED-FRU-CONTROL-MIB, returns a MIB object cempMemPoolType of value processorMemory and an actual value 2. This is shown as processorMemory(2).

To determine which MIBs are included in other releases, see the “Downloading and Compiling MIBs” section.

Cisco ASR 9000 Series Routers MIB Categories

The MIBs in the Cisco ASR 9000 Series Image on the Cisco ASR 9000 Series router are categorized into three types:

Supported MIBs

The MIB exists in the image, the code is implemented.

Unsupported MIBs

The MIB exists in the image but is not supported. These MIBs are not supported for the Cisco ASR 9000 Series routers.

MIB Version String Description

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

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

Note For example, 9502192015Z and 199509122015Z represent 8:15 GMT on 19 February 1995. Years after 1999 use the four-digit format. Years 1900-1999 may use the two or four digit format.



NoteIn the following table, you might see the termRevision not available. This term refers to the MIB module that does not have a recorded time stamp indicating the latest modification.


MIBs in the Cisco ASR 9000 Series Routers

Table 3-1 lists the MIBs in the Cisco ASR 9000 Series routers:

 

Table 3-1 MIBs in the Cisco ASR 9000 Series Routers

MIB
midb process
Supported
Unsupported
Not in Image

mibd-
interface

 

 

 

  • Release 3.7

 

9810191200Z

 

 

  • Release 3.9

 

9810191200Z

 

 

  • Release 4.0

 

9810191200Z

 

 

  • Release 4.2

 

9810191200Z

 

 

  • Release 4.3

 

9810191200Z

 

 

 

 

 

 

  • Release 3.7

Revision not available

 

 

  • Release 3.9

 

Revision not available

 

 

  • Release 4.0

 

Revision not available

 

 

  • Release 4.2

 

Revision not available

 

 

  • Release 4.3

 

Revision not available

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200309230000Z

 

 

  • Release 3.9

 

200309230000Z

 

 

  • Release 4.0

 

200309230000Z

 

 

  • Release 4.2

 

200309230000Z

 

 

  • Release 4.3

 

200309230000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

RFC 4273

 

 

  • Release 3.9

 

RFC 4273

 

 

  • Release 4.0

 

RFC 4273

 

 

  • Release 4.2

 

RFC 4273

 

 

  • Release 4.3

 

RFC 4273

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

RFC 4188

 

 

  • Release 3.9

 

RFC 4188

 

 

  • Release 4.0

 

RFC 4188

 

 

  • Release 4.2

 

RFC 4188

 

 

  • Release 4.3

 

RFC 4188

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

200311170000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200301060000Z

 

 

  • Release 3.9

 

200301060000Z

 

 

  • Release 4.0

 

200301060000Z

 

 

  • Release 4.2

 

200301060000Z

 

 

  • Release 4.3

 

200301060000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200206100000Z

 

 

  • Release 3.9

 

200206100000Z

 

 

  • Release 4.0

 

200206100000Z

 

 

  • Release 4.2

 

200206100000Z

 

 

  • Release 4.3

 

200206100000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200302240000Z

 

 

  • Release 3.9

 

200302240000Z

 

 

  • Release 4.0

 

200302240000Z

 

 

  • Release 4.2

 

200302240000Z

 

 

  • Release 4.3

 

200302240000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200207260000Z

 

 

  • Release 3.9

 

200207260000Z

 

 

  • Release 4.0

 

200207260000Z

 

 

  • Release 4.2

 

200207260000Z

 

 

  • Release 4.3

 

200207260000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200206100000Z

 

 

  • Release 3.9

 

200206100000Z

 

 

  • Release 4.0

 

200206100000Z

 

 

  • Release 4.2

 

200207260000Z

 

 

  • Release 4.3

 

200206100000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

9812100000Z

 

 

  • Release 3.9

 

9812100000Z

 

 

  • Release 4.0

 

9812100000Z

 

 

  • Release 4.2

 

9812100000Z

 

 

  • Release 4.3

 

9812100000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200901260000Z

 

 

  • Release 3.9

 

200901260000Z

 

 

  • Release 4.0

 

200901260000Z

 

 

  • Release 4.2

 

200901260000Z

 

 

  • Release 4.3

 

200901260000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200504060000Z

 

 

  • Release 3.9

 

200504060000Z

 

 

  • Release 4.0

 

200504060000Z

 

 

  • Release 4.2

 

200504060000Z

 

 

  • Release 4.3

 

200504060000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200704270000Z

 

 

  • Release 3.9

 

200704270000Z

 

 

  • Release 4.0

 

200704270000Z

 

 

  • Release 4.2

 

200704270000Z

 

 

  • Release 4.3

 

200704270000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200811220000Z

 

 

  • Release 3.9

 

200811220000Z

 

 

  • Release 4.0

 

200811220000Z

 

 

  • Release 4.2

 

200811220000Z

 

 

  • Release 4.3

 

200811220000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200205210000Z

 

 

  • Release 3.9

 

200205210000Z

 

 

  • Release 4.0

 

200205210000Z

 

 

  • Release 4.2

 

200205210000Z

 

 

  • Release 4.3

 

200205210000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200501060000Z

 

 

  • Release 3.9

 

200501060000Z

 

 

  • Release 4.0

 

200501060000Z

 

 

  • Release 4.2

 

200501060000Z

 

 

  • Release 4.3

 

200501060000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200812050000Z

 

 

  • Release 3.9

 

200812050000Z

 

 

  • Release 4.0

 

200812050000Z

 

 

  • Release 4.2

 

200812050000Z

 

 

  • Release 4.3

 

200812050000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200309180000Z

 

 

  • Release 3.9

 

200309180000Z

 

 

  • Release 4.0

 

200309180000Z

 

 

  • Release 4.2

 

200309180000Z

 

 

  • Release 4.3

 

200309180000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200810080000Z

 

 

  • Release 3.9

 

200810080000Z

 

 

  • Release 4.0

 

200810080000Z

 

 

  • Release 4.2

 

200810080000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

200510010000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200711120000Z

 

 

  • Release 3.9

 

200711120000Z

 

 

  • Release 4.0

 

200711120000Z

 

 

  • Release 4.2

 

200711120000Z

 

 

  • Release 4.3

 

200711120000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

201006160000Z

 

 

  • Release 3.9

 

201006160000Z

 

 

  • Release 4.0

 

201006160000Z

 

 

  • Release 4.2

 

201006160000Z

 

 

  • Release 4.3

 

201006160000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200906030000Z

 

 

  • Release 3.9

 

200906030000Z

 

 

  • Release 4.0

 

200906030000Z

 

 

  • Release 4.2

 

200906030000Z

 

 

  • Release 4.3

 

200906030000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

201010190000Z

 

 

  • Release 3.9

 

201010190000Z

 

 

  • Release 4.0

 

201010190000Z

 

 

  • Release 4.2

 

201010190000Z

 

 

  • Release 4.3

 

201010190000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

201104190000Z

 

 

  • Release 3.9

 

201104190000Z

 

 

  • Release 4.0

 

201104190000Z

 

 

  • Release 4.2

 

201104190000Z

 

 

  • Release 4.3

 

201104190000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

200010130000Z

 

 

  • Release 3.9

 

200010130000Z

 

 

  • Release 4.0

 

200010130000Z

 

 

  • Release 4.2

 

200010130000Z

 

 

  • Release 4.3

 

200010130000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200603310000Z

 

 

  • Release 3.9

 

200603310000Z

 

 

  • Release 4.0

 

200603310000Z

 

 

  • Release 4.2

 

200603310000Z

 

 

  • Release 4.3

 

200603310000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

9808030000Z

 

 

  • Release 3.9

 

9808030000Z

 

 

  • Release 4.0

 

9808030000Z

 

 

  • Release 4.2

 

9808030000Z

 

 

  • Release 4.3

 

9808030000Z

 

 

mibd-
interface

 

 

 

  • Release 3.7

 

9808030000Z

 

 

  • Release 3.9

 

9808030000Z

 

 

  • Release 4.0

 

9808030000Z

 

 

  • Release 4.2

 

9808030000Z

 

 

  • Release 4.3

 

9808030000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200804240000Z

 

 

  • Release 3.9

 

200804240000Z

 

 

  • Release 4.0

 

200804240000Z

 

 

  • Release 4.2

 

200804240000Z

 

 

  • Release 4.3

 

200804240000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200804291200Z

 

 

  • Release 3.9

 

200804291200Z

 

 

  • Release 4.0

 

200804291200Z

 

 

  • Release 4.2

 

200804291200Z

 

 

  • Release 4.3

 

200804291200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200909300000Z

 

 

  • Release 3.9

 

200909300000Z

 

 

  • Release 4.0

 

200909300000Z

 

 

  • Release 4.2

 

200909300000Z

 

 

  • Release 4.3

 

200909300000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200608240000Z

 

 

  • Release 3.9

 

200608240000Z

 

 

  • Release 4.0

 

200608240000Z

 

 

  • Release 4.2

 

200608240000Z

 

 

  • Release 4.3

 

200608240000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200605190000Z

 

 

  • Release 3.9

 

200605190000Z

 

 

  • Release 4.0

 

200605190000Z

 

 

  • Release 4.2

 

200605190000Z

 

 

  • Release 4.3

 

200605190000Z

 

 

 

 

 

  • Release 3.7

 

200502220000Z

 

 

  • Release 3.9

 

200502220000Z

 

 

  • Release 4.0

 

200502220000Z

 

 

  • Release 4.2

 

200502220000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200608250000Z

 

 

  • Release 3.9

 

200608250000Z

 

 

  • Release 4.0

 

200608250000Z

 

 

  • Release 4.2

 

200608250000Z

 

 

  • Release 4.3

 

200608250000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200512200000Z

 

 

  • Release 3.9

 

200512200000Z

 

 

  • Release 4.0

 

200512200000Z

 

 

  • Release 4.2

 

200512200000Z

 

 

  • Release 4.3

 

200512200000Z

 

 

CISCO-IETF-PW-ENET-MIB

mibd-interface

 

 

 

  • Release 3.7

 

200209221200Z

 

 

  • Release 3.9

 

200209221200Z

 

 

  • Release 4.0

 

200209221200Z

 

 

  • Release 4.2

 

200209221200Z

 

 

  • Release 4.3

 

200209221200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200312160000Z

 

 

  • Release 3.9

 

200312160000Z

 

 

  • Release 4.0

 

200312160000Z

 

 

  • Release 4.2

 

200312160000Z

 

 

  • Release 4.3

 

200312160000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200302261200Z

 

 

  • Release 3.9

 

200302261200Z

 

 

  • Release 4.0

 

200302261200Z

 

 

  • Release 4.2

 

200302261200Z

 

 

  • Release 4.3

 

200302261200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200810240000Z

 

 

  • Release 3.9

 

200810240000Z

 

 

  • Release 4.0

 

200810240000Z

 

 

  • Release 4.2

 

200810240000Z

 

 

  • Release 4.3

 

200810240000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200710221200Z

 

 

  • Release 3.9

 

200710221200Z

 

 

  • Release 4.0

 

200710221200Z

 

 

  • Release 4.2

 

200710221200Z

 

 

  • Release 4.3

 

200710221200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200711221200Z

 

 

  • Release 3.9

 

200711221200Z

 

 

  • Release 4.0

 

200711221200Z

 

 

  • Release 4.2

 

200711221200Z

 

 

  • Release 4.3

 

200711221200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200707230000Z

 

 

  • Release 3.9

 

200707230000Z

 

 

  • Release 4.0

 

200707230000Z

 

 

  • Release 4.2

 

200707230000Z

 

 

  • Release 4.3

 

200707230000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200906110000Z

 

 

  • Release 3.9

 

200906110000Z

 

 

  • Release 4.0

 

200906110000Z

 

 

  • Release 4.2

 

200906110000Z

 

 

  • Release 4.3

 

200906110000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200403110000Z

 

 

  • Release 3.9

 

200403110000Z

 

 

  • Release 4.0

 

200403110000Z

 

 

  • Release 4.2

 

200403110000Z

 

 

  • Release 4.3

 

200403110000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200112202300Z

 

 

  • Release 3.9

 

200112202300Z

 

 

  • Release 4.0

 

200112202300Z

 

 

  • Release 4.2

 

200112202300Z

 

 

  • Release 4.3

 

200112202300Z

 

 

 

 

 

 

  • Release 3.7

mibd-interface

200008071139Z

 

 

  • Release 3.9

 

200008071139Z

 

 

  • Release 4.0

 

200008071139Z

 

 

  • Release 4.2

 

200008071139Z

 

 

  • Release 4.3

 

200008071139Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200710240000Z

 

 

  • Release 3.9

 

200710240000Z

 

 

  • Release 4.0

 

200710240000Z

 

 

  • Release 4.2

 

200710240000Z

 

 

  • Release 4.3

 

200710240000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200107310000Z

 

 

  • Release 3.9

 

200107310000Z

 

 

  • Release 4.0

 

200107310000Z

 

 

  • Release 4.2

 

200107310000Z

 

 

  • Release 4.3

 

200107310000Z

 

 

 

 

 

 

  • Release 3.7

mibd-interface

201007020000Z

 

 

  • Release 3.9

 

201007020000Z

 

 

  • Release 4.0

 

201007020000Z

 

 

  • Release 4.2

 

201007020000Z

 

 

  • Release 4.3

 

201007020000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

201010150000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200607310000Z

 

 

  • Release 3.9

 

200607310000Z

 

 

  • Release 4.0

 

200607310000Z

 

 

  • Release 4.2

 

200607310000Z

 

 

  • Release 4.3

 

200607310000Z

 

 

 

 

 

 

  • Release 3.7

mibd-interface

200602170000Z

 

 

  • Release 3.9

 

200602170000Z

 

 

  • Release 4.0

 

200602170000Z

 

 

  • Release 4.2

 

200602170000Z

 

 

  • Release 4.3

 

200602170000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

201101280000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200808120000Z

 

 

  • Release 3.9

 

200808120000Z

 

 

  • Release 4.0

 

200808120000Z

 

 

  • Release 4.2

 

200808120000Z

 

 

  • Release 4.3

 

200808120000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200011020000Z

 

 

  • Release 3.9

 

200011020000Z

 

 

  • Release 4.0

 

200011020000Z

 

 

  • Release 4.2

 

200011020000Z

 

 

  • Release 4.3

 

200011020000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200108280000Z

 

 

  • Release 3.9

 

200108280000Z

 

 

  • Release 4.0

 

200108280000Z

 

 

  • Release 4.2

 

200108280000Z

 

 

  • Release 4.3

 

200108280000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200910120000Z

 

 

  • Release 3.9

 

200910120000Z

 

 

  • Release 4.0

 

200910120000Z

 

 

  • Release 4.2

 

200910120000Z

 

 

  • Release 4.3

 

200910120000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200803180000Z

 

 

  • Release 3.9

 

200803180000Z

 

 

  • Release 4.0

 

200803180000Z

 

 

  • Release 4.2

 

200803180000Z

 

 

  • Release 4.3

 

200803180000Z

 

 

mibd_entity

 

 

 

  • Release 3.7

 

200803240000Z

 

 

  • Release 3.9

 

200803240000Z

 

 

  • Release 4.0

 

200803240000Z

 

 

  • Release 4.2

 

200803240000Z

 

 

  • Release 4.3

 

200803240000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

201106220000Z

 

 

  • Release 3.9

 

201106220000Z

 

 

  • Release 4.0

 

201106220000Z

 

 

  • Release 4.2

 

201106220000Z

 

 

  • Release 4.3

 

201106220000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200303070000Z

 

 

  • Release 3.9

 

200303070000Z

 

 

  • Release 4.0

 

200303070000Z

 

 

  • Release 4.2

 

200303070000Z

 

 

  • Release 4.3

 

200303070000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

201208080000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200512030000Z

 

 

  • Release 3.9

 

200512030000Z

 

 

  • Release 4.0

 

200512030000Z

 

 

  • Release 4.2

 

200512030000Z

 

 

  • Release 4.3

 

200512030000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200709160000Z

 

 

  • Release 3.9

 

200709160000Z

 

 

  • Release 4.0

 

200709160000Z

 

 

  • Release 4.2

 

200709160000Z

 

 

  • Release 4.3

 

200709160000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200809100000Z

 

 

  • Release 3.9

 

200809100000Z

 

 

  • Release 4.0

 

200809100000Z

 

 

  • Release 4.2

 

200809100000Z

 

 

  • Release 4.3

 

200809100000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200111120000Z

 

 

  • Release 3.9

 

200111120000Z

 

 

  • Release 4.0

 

200111120000Z

 

 

  • Release 4.2

 

200111120000Z

 

 

  • Release 4.3

 

200111120000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

 

 

 

  • Release 3.9

 

 

 

 

  • Release 4.0

 

 

 

 

  • Release 4.2

 

 

 

 

  • Release 4.3

 

200906160000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

9904010530Z

 

 

  • Release 3.9

 

9904010530Z

 

 

  • Release 4.0

 

9904010530Z

 

 

  • Release 4.2

 

9904010530Z

 

 

  • Release 4.3

 

9904010530Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200010160000Z

 

 

  • Release 3.9

 

200010160000Z

 

 

  • Release 4.0

 

200010160000Z

 

 

  • Release 4.2

 

200010160000Z

 

 

  • Release 4.3

 

200010160000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200706140000Z

 

 

  • Release 3.9

 

200706140000Z

 

 

  • Release 4.0

 

200706140000Z

 

 

  • Release 4.2

 

200706140000Z

 

 

  • Release 4.3

 

200706140000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

9808011830Z

 

 

  • Release 3.9

 

9808011830Z

 

 

  • Release 4.0

 

9808011830Z

 

 

  • Release 4.2

 

9808011830Z

 

 

  • Release 4.3

 

9808011830Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200205210000Z

 

 

  • Release 3.9

 

200205210000Z

 

 

  • Release 4.0

 

200205210000Z

 

 

  • Release 4.2

 

200205210000Z

 

 

  • Release 4.3

 

200205210000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

RFC 2737

 

 

  • Release 3.9

 

RFC 2737

 

 

  • Release 4.0

 

RFC 2737

 

 

  • Release 4.2

 

RFC 2737

 

 

  • Release 4.3

 

RFC 2737

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200511220000Z

 

 

  • Release 3.9

 

200511220000Z

 

 

  • Release 4.0

 

200511220000Z

 

 

  • Release 4.2

 

200511220000Z

 

 

  • Release 4.3

 

200511220000Z

 

 

mibd-entity

 

 

 

  • Release 3.7

 

200309190000Z

 

 

  • Release 3.9

 

200309190000Z

 

 

  • Release 4.0

 

200309190000Z

 

 

  • Release 4.2

 

200309190000Z

 

 

  • Release 4.3

 

200309190000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

RFC 2981

 

 

  • Release 3.9

 

RFC 2981

 

 

  • Release 4.0

 

RFC 2981

 

 

  • Release 4.2

 

RFC 2981

 

 

  • Release 4.3

 

RFC 2981

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200511240000Z

 

 

  • Release 3.9

 

200511240000Z

 

 

  • Release 4.0

 

200511240000Z

 

 

  • Release 4.2

 

200511240000Z

 

 

  • Release 4.3

 

200511240000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

9705010229Z

 

 

  • Release 3.9

 

9705010229Z

 

 

  • Release 4.0

 

9705010229Z

 

 

  • Release 4.2

 

9705010229Z

 

 

  • Release 4.3

 

9705010229Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200706100000Z

 

 

  • Release 3.9

 

200706100000Z

 

 

  • Release 4.0

 

200706100000Z

 

 

  • Release 4.2

 

200706100000Z

 

 

  • Release 4.3

 

200706100000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200006270000Z

 

 

  • Release 3.9

 

200006270000Z

 

 

  • Release 4.0

 

200006270000Z

 

 

  • Release 4.2

 

200006270000Z

 

 

  • Release 4.3

 

200006270000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200402040000Z

 

 

  • Release 3.9

 

200402040000Z

 

 

  • Release 4.0

 

200402040000Z

 

 

  • Release 4.2

 

200402040000Z

 

 

  • Release 4.3

 

200402040000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200410180000Z

 

 

  • Release 3.9

 

200410180000Z

 

 

  • Release 4.0

 

200410180000Z

 

 

  • Release 4.2

 

200410180000Z

 

 

  • Release 4.3

 

200410180000Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

RFC 2233

 

 

  • Release 3.9

 

RFC 2233

 

 

  • Release 4.0

 

RFC 2233

 

 

  • Release 4.2

 

RFC 2233

 

 

  • Release 4.3

 

RFC 2233

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200303260000Z

 

 

  • Release 3.9

 

200303260000Z

 

 

  • Release 4.0

 

200303260000Z

 

 

  • Release 4.2

 

200303260000Z

 

 

  • Release 4.3

 

200303260000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

RFC 2096

RFC 4292

 

 

  • Release 3.9

 

RFC 2096

RFC 4292

 

 

  • Release 4.0

 

RFC 2096

RFC 4292

 

 

  • Release 4.2

 

RFC 2096

RFC 4292

 

 

  • Release 4.3

 

RFC 2096

RFC 4292

 

 

mibd-interface

 

 

 

  • Release 3.7

 

RFC 2011

 

 

  • Release 3.9

 

RFC 2011

 

 

  • Release 4.0

 

RFC 2011

 

 

  • Release 4.2

 

RFC 2011

 

 

  • Release 4.3

 

RFC 2011

 

 

mibd-interface

 

 

 

  • Release 3.7

 

9802052155Z

 

 

  • Release 3.9

 

9802052155Z

 

 

  • Release 4.0

 

9802052155Z

 

 

  • Release 4.2

 

9802052155Z

 

 

  • Release 4.3

 

9802052155Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200402091200Z

 

 

  • Release 3.9

 

200402091200Z

 

 

  • Release 4.0

 

200402091200Z

 

 

  • Release 4.2

 

200402091200Z

 

 

  • Release 4.3

 

200402091200Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200101250000Z

 

 

  • Release 3.9

 

200101250000Z

 

 

  • Release 4.0

 

200101250000Z

 

 

  • Release 4.2

 

200101250000Z

 

 

  • Release 4.3

 

200101250000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200604040000Z

 

 

  • Release 3.9

 

200604040000Z

 

 

  • Release 4.0

 

200604040000Z

 

 

  • Release 4.2

 

200604040000Z

 

 

  • Release 4.3

 

200604040000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200704210000Z

 

 

  • Release 3.9

 

200704210000Z

 

 

  • Release 4.0

 

200704210000Z

 

 

  • Release 4.2

 

200704210000Z

 

 

  • Release 4.3

 

200704210000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200011300000Z

 

 

  • Release 3.9

 

200011300000Z

 

 

  • Release 4.0

 

200011300000Z

 

 

  • Release 4.2

 

200011300000Z

 

 

  • Release 4.3

 

200011300000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200302240000Z

 

 

  • Release 3.9

 

200302240000Z

 

 

  • Release 4.0

 

200302240000Z

 

 

  • Release 4.2

 

200302240000Z

 

 

  • Release 4.3

 

200302240000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200601230000Z

 

 

  • Release 3.9

 

200601230000Z

 

 

  • Release 4.0

 

200601230000Z

 

 

  • Release 4.2

 

200601230000Z

 

 

  • Release 4.3

 

200601230000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200406030000Z

 

 

  • Release 3.9

 

200406030000Z

 

 

  • Release 4.0

 

200406030000Z

 

 

  • Release 4.2

 

200406030000Z

 

 

  • Release 4.3

 

200406030000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200406030000Z

 

 

  • Release 3.9

 

200406030000Z

 

 

  • Release 4.0

 

200406030000Z

 

 

  • Release 4.2

 

200406030000Z

 

 

  • Release 4.3

 

200406030000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200406030000Z

 

 

  • Release 3.9

 

200406030000Z

 

 

  • Release 4.0

 

200406030000Z

 

 

  • Release 4.2

 

200406030000Z

 

 

  • Release 4.3

 

200406030000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

RFC 3812

 

 

  • Release 3.9

 

RFC 3812

 

 

  • Release 4.0

 

RFC 3812

 

 

  • Release 4.2

 

RFC 3812

 

 

  • Release 4.3

 

RFC 3812

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200011270000Z

 

 

  • Release 3.9

 

200011270000Z

 

 

  • Release 4.0

 

200011270000Z

 

 

  • Release 4.2

 

200011270000Z

 

 

  • Release 4.3

 

200011270000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200611100000Z

 

 

  • Release 3.9

 

200611100000Z

 

 

  • Release 4.0

 

200611100000Z

 

 

  • Release 4.2

 

200611100000Z

 

 

  • Release 4.3

 

200611100000Z

 

 

 

 

 

  • Release 3.7

 

200611100000Z

 

 

  • Release 3.9

 

200611100000Z

 

 

  • Release 4.0

 

200611100000Z

 

 

  • Release 4.2

 

200611100000Z

 

 

  • Release 4.3

 

200611100000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200709171200Z

 

 

  • Release 3.9

 

200709171200Z

 

 

  • Release 4.0

 

200709171200Z

 

 

  • Release 4.2

 

200709171200Z

 

 

  • Release 4.3

 

200709171200Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200300000000Z

 

 

  • Release 3.9

 

200300000000Z

 

 

  • Release 4.0

 

200300000000Z

 

 

  • Release 4.2

 

200300000000Z

 

 

  • Release 4.3

 

200300000000Z

 

 

mibd-infra

 

 

 

  • Release 3.7

 

200300000000Z

 

 

  • Release 3.9

 

200300000000Z

 

 

  • Release 4.0

 

200300000000Z

 

 

  • Release 4.2

 

200300000000Z

 

 

  • Release 4.3

 

200300000000Z

 

 

 

 

 

  • Release 3.7

 

Revision not available

 

 

  • Release 3.9

 

Revision not available

 

 

  • Release 4.0

 

Revision not available

 

 

  • Release 4.2

 

Revision not available

 

 

  • Release 4.3

 

Revision not available

 

 

 

 

 

  • Release 3.7

 

9411010000Z

 

 

  • Release 3.9

 

9411010000Z

 

 

  • Release 4.0

 

9411010000Z

 

 

  • Release 4.2

 

9411010000Z

 

 

  • Release 4.3

 

9411010000Z

 

 

 

 

 

  • Release 3.7

 

9802052155Z

 

 

  • Release 3.9

 

9802052155Z

 

 

  • Release 4.0

 

9802052155Z

 

 

  • Release 4.2

 

9802052155Z

 

 

  • Release 4.3

 

9802052155Z

 

 

mibd-interface

 

 

 

  • Release 3.7

 

9808251820Z

 

 

  • Release 3.9

 

9808251820Z

 

 

  • Release 4.0

 

9808251820Z

 

 

  • Release 4.2

 

9808251820Z

 

 

  • Release 4.3

 

9808251820Z

 

 

snmpd

 

 

 

  • Release 3.7

 

200210140000Z

 

 

  • Release 3.9

 

200210140000Z

 

 

  • Release 4.0

 

200210140000Z

 

 

  • Release 4.2

 

200210140000Z

 

 

  • Release 4.3

 

200210140000Z

 

 

snmpd

 

 

 

  • Release 3.7

 

200210140000Z

 

 

  • Release 3.9

 

200210140000Z

 

 

  • Release 4.0

 

200210140000Z

 

 

  • Release 4.2

 

200210140000Z

 

 

  • Release 4.3

 

200210140000Z

 

 

SNMP-RESEARCH-MIB

snmpd

 

 

 

  • Release 3.7

 

Revision not available

 

 

  • Release 3.9

 

Revision not available

 

 

  • Release 4.0

 

Revision not available

 

 

  • Release 4.2

 

Revision not available

 

 

  • Release 4.3

 

Revision not available

 

 

SNMP-MPD-MIB

snmpd

 

 

 

  • Release 3.7

 

9905041636Z

 

 

  • Release 3.9

 

9905041636Z

 

 

  • Release 4.0

 

9905041636Z

 

 

  • Release 4.2

 

9905041636Z

 

 

  • Release 4.3

 

9905041636Z

 

 

snmpd

 

 

 

  • Release 3.7

 

9808040000Z

 

 

  • Release 3.9

 

9808040000Z

 

 

  • Release 4.0

 

9808040000Z

 

 

  • Release 4.2

 

9808040000Z

 

 

  • Release 4.3

 

9808040000Z

 

 

snmpd

 

 

 

  • Release 3.7

 

9808040000Z

 

 

  • Release 3.9

 

9808040000Z

 

 

  • Release 4.0

 

9808040000Z

 

 

  • Release 4.2

 

9808040000Z

 

 

  • Release 4.3

 

9808040000Z

 

 

SNMP-USM-AES-MIB

snmpd

 

 

 

  • Release 3.7

 

200406140000Z

 

 

  • Release 3.9

 

200406140000Z

 

 

  • Release 4.0

 

200406140000Z

 

 

  • Release 4.2

 

200406140000Z

 

 

  • Release 4.3

 

200406140000Z

 

 

snmpd

 

 

 

  • Release 3.7

 

9901200000Z

 

 

  • Release 3.9

 

9901200000Z

 

 

  • Release 4.0

 

9901200000Z

 

 

  • Release 4.2

 

9901200000Z

 

 

  • Release 4.3

 

9901200000Z

 

 

snmpd

 

 

 

  • Release 3.7

 

RFC 2575

 

 

  • Release 3.9

 

RFC 2575

 

 

  • Release 4.0

 

RFC 2575

 

 

  • Release 4.2

 

RFC 2575

 

 

  • Release 4.3

 

RFC 2575

 

 

snmpd

 

 

 

  • Release 3.7

 

RFC 1904

 

 

  • Release 3.9

 

RFC 1904

 

 

  • Release 4.0

 

RFC 1904

 

 

  • Release 4.2

 

RFC 1904

 

 

  • Release 4.3

 

RFC 1904

 

 

SNMPv2-TM

snmpd

 

 

 

  • Release 3.7

 

Revision not available

 

 

  • Release 3.9

 

Revision not available

 

 

  • Release 4.0

 

Revision not available

 

 

  • Release 4.2

 

Revision not available

 

 

  • Release 4.3

 

Revision not available

 

 

mibd-interface

 

 

 

  • Release 3.7

 

200308110000Z

 

 

  • Release 3.9

 

200308110000Z

 

 

  • Release 4.0

 

200308110000Z

 

 

  • Release 4.2

 

200308110000Z

 

 

  • Release 4.3

 

200308110000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200502180000Z

 

 

  • Release 3.9

 

200502180000Z

 

 

  • Release 4.0

 

200502180000Z

 

 

  • Release 4.2

 

200502180000Z

 

 

  • Release 4.3

 

200502180000Z

 

 

mibd-route

 

 

 

  • Release 3.7

 

200505200000Z

 

 

  • Release 3.9

 

200505200000Z

 

 

  • Release 4.0

 

200505200000Z

 

 

  • Release 4.2

 

200505200000Z

 

 

  • Release 4.3

 

200505200000Z

 

 

 

 

 

  • Release 3.7

 

 

 

Y

  • Release 3.9

 

200003030000Z

 

 

  • Release 4.0

 

200003030000Z

 

 

  • Release 4.2

 

200003030000Z

 

 

  • Release 4.3

 

200003030000Z

 

 

1.These MIBs may have a different behavior on a per-platform basis.

MIB Notification Names in the Cisco ASR 9000 Series Routers

Table 3-2 lists the Notification Names associated with MIBs in the Cisco ASR 9000 Series Routers:

 

Table 3-2 MIB Notification Names in the Cisco ASR 9000 Series Routers

MIB
Notification Name

bgpEstablished,
bgpBackwardTransition

newRoot,
topologyChange

cbgpFsmStateChange,
cbgpBackwardTransition,
cbgpPrefixThresholdExceeded,
cbgpPrefixThresholdClear

cbfDefineFileCompletion

ccCopyCompletion

ciscoConfigManEvent

cefcModuleStatusChange,
cefcPowerStatusChange,
cefcFRUInserted,
cefcFRURemoved,
cefcFanTrayStatusChange

entSensorThresholdNotification

ciscoFlashCopyCompletionTrap,
ciscoFlashDeviceInsertedNotif,
ciscoFlashDeviceRemovedNotif,
ciscoFlashMiscOpCompletionTrap

cpwVcDown,
cpwVcUp

ciscoRFSwactNotif,
ciscoRFProgressionNotif

ciscoSonetSectionStatusChange,
ciscoSonetPathStatusChange,
ciscoSonetLineStatusChange

clogMessageGenerated

dsx1LineStatusChange

entConfigChange

mteTriggerFired,
mteTriggerRising,
mteTriggerFalling,
mteTriggerFailure,
mteEventSetFailure

dot1agCfmFaultAlarm

linkDown,
linkUp

ATM-MIB

The ATM-MIB describes ATM and AAL5-related objects for managing ATM interfaces, ATM virtual links, ATM cross-connects, AAL5 entities, and AAL5 connections.

Table 3-3 lists the tables associated with this MIB.

 

Table 3-3 ATM-MIB Tables and Descriptions

Name
Description

atmInterfaceConfTable

This table contains ATM local interface configuration parameters, one entry per ATM interface port.

atmInterfaceDs3PlcpTable

This table contains ATM interface DS3 PLCP parameters and state variables, one entry per ATM interface port.

atmInterfaceTCTable

This table contains ATM interface TC Sublayer parameters and state variables, one entry per ATM interface port.

atmTrafficDescrParamTable

This table contains information on ATM traffic descriptor type and the associated parameters.

atmVplTable

VPL table. A bi directional VPL is modeled as one entry in this table. This table can be used for PVCs, SVCs, and Soft PVCs. Entries are not present in this table for the VPIs used by entries in the atmVclTable.

atmVclTable

VCL table. A bi directional VCL is modeled as one entry in this table. This table can be used for PVCs, SVCs, and Soft PVCs.

atmVpCrossConnectTable

ATM VP Cross Connect table for PVCs. An entry in this table models two cross-connected VPLs. Each VPL must have its atmConnKind set to pvc(1).

atmVcCrossConnectTable

ATM VC Cross Connect table for PVCs. An entry in this table models two cross-connected VCLs. Each VCL must have its atmConnKind set to pvc(1).

aal5VccTable

This table contains AAL5 VCC performance parameters.

MIB Constraints

Table 3-4 lists the constraints that the router places on objects in the ATM-MIB.

 

Table 3-4 ATM-MIB Constraints

MIB Object
Notes

atmVpCrossConnectAdminStatus

Not supported

atmVpCrossConnectRowStatus

Not supported

atmVcCrossConnectAdminStatus

Not supported

atmVcCrossConnectRowStatus

Not supported

atmTrafficDescrType

Not supported

atmTrafficDescrParam1

Not supported

atmTrafficDescrParam2

Not supported

atmTrafficDescrParam3

Not supported

atmTrafficDescrParam4

Not supported

atmTrafficDescrParam5

Not supported

atmTrafficDescrRowStatus

Not supported

atmServiceCategory

Not supported

atmTrafficFrameDiscard

Not supported

atmVclReceiveTrafficDescrIndex

Not supported

atmVclTransmitTrafficDescrIndex

Not supported

atmVclRowStatus

Not supported

atmVclCastType

Not supported

atmVclConnKind

Not supported

atmInterfaceMaxVpcs

Not supported

atmInterfaceMaxVccs

Not supported

atmInterfaceMaxActiveVpiBits

Not supported

atmInterfaceMaxActiveVciBits

Not supported

atmInterfaceIlmiVpi

Not supported

atmInterfaceIlmiVci

Not supported

atmInterfaceMyNeighborIpAddress

Not supported

atmInterfaceMyNeighborIfName

Not supported

atmInterfaceSubscrAddress

Not supported

atmVplReceiveTrafficDescrIndex

Not supported

atmVplTransmitTrafficDescrIndex

Not supported

atmVplRowStatus

Not supported

atmVplCastType

Not supported

atmVplConnKind

Not supported

ATM-FORUM-MIB

The ATM-FORUM-MIB is one of the ATM Forum's ILMI MIBs, supporting the UNI 4.0 specification.

Table 3-5 lists the tables associated with this MIB:

 

Table 3-5 ATM-FORUM-MIB Tables and Descriptions

Name
Description

atmfPortTable

Table of physical layer status and parameter information for the physical interface of ATM Interface.

atmfAtmLayerTable

Table of ATM layer status and parameter information for the ATM Interface.

atmfAtmStatsTable

This group is deprecated and should not be implemented except as required for backward compatibility with version 3.1 of the UNI specification.

atmfVpcTable

Table of status and parameter information on the virtual path connections which cross this ATM Interface. There is one entry in this table for each permanent virtual path connection.

atmfVpcAbrTable

Table of operational parameters related to the ABR virtual path connections which cross this ATM Interface. There is one entry in this table for each ABR virtual path connection. Each virtual path connection represented in this table must also be represented by an entry in the atmfVpcTable.

atmfVccTable

Table of status and parameter information on the virtual channel connections which are visible at this ATM Interface. There is one entry in this table for each permanent virtual channel connection, including reserved VCCs that are supported; that is, signaling, OAM flows, and ILMI, but not unassigned cells.

atmfVccAbrTable

Table of operational parameters related to the ABR virtual channel connections which cross this ATM Interface. There is one entry in this table for each ABR virtual channel connection. Each virtual channel connection represented in this table must also be represented by an entry in the atmfVccTable.

ATM2-MIB

The ATM2-MIB supplements the ATM-MIB as defined in RFC 2515.

Table 3-6 lists the tables associated with this MIB.

 

Table 3-6 ATM2-MIB Tables and Descriptions

Name
Description

atmSvcVpCrossConnectTable

ATM SVPC Cross-Connect table. A bi directional VP cross-connect between two switched VPLs is modeled as one entry in this table. A Soft PVPC cross-connect, between a soft permanent VPL and a switched VPL, is also modeled as one entry in this table.

atmSvcVcCrossConnectTable

ATM SVCC Cross-Connect table. A bi directional VC cross-connect between two switched VCLs is modeled as one entry in this table. A Soft PVCC cross-connect, between a soft permanent VCL and a switched VCL, is also modeled as one entry in this table.

atmSigStatTable

This table contains ATM interface signaling statistics, one entry per ATM signaling interface.

atmSigSupportTable

This table contains ATM local interface configuration parameters, one entry per ATM signaling interface.

atmSigDescrParamTable

Table contains signaling capabilities of VCLs except the Traffic Descriptor. Traffic descriptors are described in the atmTrafficDescrParamTable.

atmIfRegisteredAddrTable

This table contains a list of ATM addresses that can be used for calls to and from a given interface by a switch or service. The ATM addresses are either registered by the endsystem via ILMI or statically configured. This table does not expose PNNI reachability information. ILMI registered addresses cannot be deleted using this table. This table only applies to switches and network services.

atmVclAddrTable

This table provides a mapping between the atmVclTable and the ATM called party/calling party address . This table can be used to retrieve the calling party and called party ATM address pair for a given VCL. Note that there can be more than one pair of calling party and called party ATM addresses for a VCL in a point to multi-point call.

atmAddrVclTable

This table provides an alternative way to retrieve the atmVclTable. This table can be used to retrieve the indexing to the atmVclTable by an ATM address.

atmVplStatTable

This table contains all statistics counters per VPL. It is used to monitor the usage of the VPL in terms of incoming cells and outgoing cells.

atmVplLogicalPortTable

Indicates whether the VPL is an ATM Logical Port interface (ifType = 80).

atmVclStatTable

This table contains all statistics counters per VCL. It is used to monitor the usage of the VCL in terms of incoming cells and outgoing cells.

atmAal5VclStatTable

This table provides a collection of objects providing AAL5 configuration and performance statistics of a VCL.

atmVclGenTable

General Information for each VC.

atmInterfaceExtTable

This table contains ATM interface configuration and monitoring information not defined in the atmInterfaceConfTable from the ATM-MIB. This includes the type of connection setup procedures, ILMI information, and information on the VPI/VCI range.

atmIlmiSrvcRegTable

This table contains a list of all the ATM network services known by this device. The characteristics of these services are made available through the ILMI, using the ILMI general-purpose service registry MIB. These services may be made available to all ATM interfaces (atmIlmiSrvcRegIndex = 0) or to some specific ATM interfaces only (atmIlmiSrvcRegIndex = ATM interface index).

atmIlmiNetworkPrefixTable

Table specifying per-interface network prefix(es) supplied by the network side of the UNI during ILMI address registration. When no network prefixes are specified for a particular interface, one or more network prefixes based on the switch address(es) may be used for ILMI address registration.

atmVpCrossConnectXTable

This table contains one row per VP Cross-Connect represented in the atmVpCrossConnectTable.

atmVcCrossConnectXTable

This table contains one row per VC Cross-Connect represented in the atmVcCrossConnectTable.

atmCurrentlyFailingPVplTable

Table indicating all VPLs for which there is an active row in the atmVplTable having an atmVplConnKind value of pvc and an atmVplOperStatus with a value other than up .

atmCurrentlyFailingPVclTable

Table indicating all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of pvc and an atmVclOperStatus with a value other than up .

MIB Constraints

Table 3-7 lists the constraints that the router places on objects in the ATM2-MIB.

 

Table 3-7 ATM2-MIB Constraints

MIB Object
Notes

atmSigDescrParamAalType

Not supported

atmSigDescrParamAalSscsType

Not supported

atmSigDescrParamBhliType

Not supported

atmSigDescrParamBhliInfo

Not supported

atmSigDescrParamBbcConnConf

Not supported

atmSigDescrParamBlliLayer2

Not supported

atmSigDescrParamBlliLayer3

Not supported

atmSigDescrParamBlliPktSize

Not supported

atmSigDescrParamBlliSnapId

Not supported

atmSigDescrParamBlliOuiPid

Not supported

atmVpCrossConnectUserName

Not supported

atmVcCrossConnectUserName

Not supported

atmSwitchAddressAddress

Not supported

atmSwitchAddressRowStatus

Not supported

atmVplLogicalPortDef

Not supported

atmInterfaceConfMaxSvpcVpi

Not supported

atmInterfaceConfMaxSvccVpi

Not supported

atmInterfaceConfMinSvccVci

Not supported

atmIntfSigVccRxTrafficDescrIndex

Not supported

atmIntfSigVccTxTrafficDescrIndex

Not supported

atmIntfPvcNotificationInterval

Not supported

atmIntfPvcFailuresTrapEnable

Not supported

atmIntfConfigType

Not supported

atmIntfConfigSide

Not supported

atmIntfIlmiAdminStatus

Not supported

atmIntfIlmiEstablishConPollIntvl

Not supported

atmIntfIlmiCheckConPollIntvl

Not supported

atmIntfIlmiConPollInactFactor

Not supported

atmIntfIlmiPublicPrivateIndctr

Not supported

atmIlmiSrvcRegATMAddress

Not supported

atmIlmiSrvcRegParm1

Not supported

atmIlmiSrvcRegRowStatus

Not supported

atmIlmiNetPrefixRowStatus

Not supported

atmSvcVpCrossConnectRowStatus

Not supported

atmSvcVcCrossConnectRowStatus

Not supported

atmIfRegAddrOrgScope

Not supported

atmVclAddrType

Not supported

atmVclAddrRowStatus

Not supported

atmSigSupportClgPtyNumDel

Not supported

atmSigSupportClgPtySubAddr

Not supported

atmSigSupportCldPtySubAddr

Not supported

atmSigSupportHiLyrInfo

Not supported

atmSigSupportLoLyrInfo

Not supported

atmSigSupportBlliRepeatInd

Not supported

atmSigSupportAALInfo

Not supported

BGP4-MIB

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

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

Table 3-8 lists the tables associated with this MIB.

 

Table 3-8 BGP4-MIB Tables and Descriptions

Name
Description

bgpPeerTable

BGP peer table. This table contains one entry per BGP peer and information about the connections with BGP peers.

bgpRcvdPathAttrTable

BGP Received Path Attribute Table contains information about paths to destination networks received from all peers running BGP version 3 or fewer. This table is not supported.

bgp4PathAttrTable

BGP-4 Received Path Attribute Table contains information about paths to destination networks received from all BGP4 peers.

MIB Constraints

Table 3-9 lists the constraints that the router places on objects in the BGP4-MIB.

Table 3-9 BGP4-MIB Constraints

MIB Object
Notes

bgpRcvdPathAttrTable

Not supported

bgpPeerAdminStatus

Not supported

bgpPeerConnectRetryInterval

Not supported

bgpPeerHoldTimeConfigured

Not supported

bgpPeerKeepAliveConfigured

Not supported

bgpPeerMinASOriginationInterval

Not supported

bgpPeerMinRouteAdvertisementInterval

Not supported

BRIDGE-MIB

The BRIDGE-MIB contains objects to manage Media Access Control (MAC) bridges between Local Area Network (LAN) segments, as defined by the IEEE 802.1D-1990 standard. This MIB is extracted from RFC 1493 and is intended for use with network management protocols in TCP/IP based internets.


NoteTo access bridge domain data, the corresponding SNMP context must be used (i.e. v2 comunity or v3 group mapped to context).


Table 3-10 lists the tables associated with this MIB.

 

Table 3-10 BRIDGE-MIB Tables and Descriptions

Name
Description

dot1dBasePortTable

Table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.

dot1dStpPortTable

Table that contains port-specific information for the Spanning Tree Protocol

dot1dTpFdbTable

Table that contains information about unicast entries for which the bridge has forwarding and filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.

dot1dTpPortTable

Table that contains information about every port that is associated with this transparent bridge.

dot1dStaticTable

Table containing filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table, as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and for group and broadcast addresses.

MIB Constraints

Table 3-11 lists the constraints that the router places on objects in the BRIDGE-MIB. For detailed definitions of MIB objects, see the MIB. This MIB only supports managing two types of bridges (CE and VPLS bridges).


NoteSet Operation on BRIDGE-MIB objects is not supported.


 

Table 3-11 BRIDGE-MIB Constraints

MIB Object
Notes

dot1dStp Subtree Objects

Not supported for VPLS Bridges

newRoot

Not supported for VPLS Bridges

TCN Traps

Not supported for VPLS Bridges

dot1dStpPortPathCost32

Not supported

dot1dStaticAddress

Not supported

dot1dStaticReceivePort

Not supported

dot1dStaticAllowedToGoTo

Not supported

dot1dStaticStatus

Not supported

dot1dStpPortPriority

Not supported

dot1dStpPortEnable

Not supported

dot1dStpPortPathCost

Not supported

dot1dStpPortPriority

Not supported

dot1dStpPortEnable

Not supported

dot1dStpPortPathCost32

Not supported

dot1dTpAgingTime

Not supported

dot1dStpPriority

Not supported

dot1dStpBridgeMaxAge

Not supported

dot1dStpBridgeHelloTime

Not supported

dot1dStpBridgeHelloTime

Not supported

CISCO-AAA-SERVER-MIB

The MIB module for monitoring communications and status of AAA Server operation.

Table 3-12 lists the tables associated with this MIB.

 

Table 3-12 CISCO-AAA-SERVER-MIB Tables and Descriptions

Name
Description

casConfigTable

This table shows current configurations for each AAA server, allows existing servers to be removed and new ones to be created.

casStatisticsTable

This table shows statistics for each AAA server.

CISCO-ACL-MIB

This MIB module defines objects that describe Cisco Access Control Lists (ACL). This MIB describes different objects that enable the network administrator to remotely configure ACLs, apply them to interfaces and monitor their usage statistics.

However, A typical application of this MIB module will facilitate monitoring of ACL match (sometimes referred as hit) counts. However, by no means does the definition of this MIB module prevent other applications from using it.

An ACL is an ordered list of statements that deny or permit packets based on matching fields contained within the packet header (layer 3 source and destination addresses, layer 4 protocol, layer 4 source and destination port numbers, etc.) In addition, there is an implicit *Deny All* at the end of the ACL.

ACLs are used to perform packet filtering to control which packets are allowed through the network. Such control can help limit network traffic, and restrict the access of applications and devices on the network. Each one of these statements is referred to as an Access List Control Entry (ACE).

Here is an example of an ACL configuration: ipv4 access-list V4Example 10 permit tcp any any ! ipv6 access-list V6Example 10 permit tcp any any !

The mechanism for monitoring ACL usage is by configuring, in the desired ACEs, a counter label. A counter label is a name that is given to a counter and is defined in any ACE. ACEs that share the same Counter label name will have their counters aggregated into the same label.

Here is an example of how to use counter labels: ipv4 access-list V4CounterExample 10 permit tcp any any counter CountPermits 20 permit udp any any counter CountPermits .

The same applies to IPv6 ACLs.

Table 3-13 lists the tables defined in CISCO-ACL-MIB

 

Table 3-13 CISCO-ACL-MIB Objects

caAclCfgTable

A table of ACL definitions. Each entry in this table defines a unique IPV4 or IPV6 ACL.

caAclIPV4ACECfgTable

A table of IPV4 ACE definitions. The ACE definition controls whether packets are accepted or rejected. The access control may be applied before sending the packet to the forwarding engine, or may be applied after the packet is processed by the forwarding engine. If two ACE entries with the same sequence number are configured the latter will overwrite the former.

caAclIPV6ACECfgTable

A table of IPV6 ACE definitions. The ACE definition controls whether packets are accepted or rejected. The access control may be applied before sending the packet to the forwarding engine, or may be applied after the packet is processed by the forwarding engine.

caAclAccessGroupCfgTable

This table lists the ACLs configured on the device and applied on an interface in the ingress or egress direction.

caAclLabelIntfStatsTable

This table describes the statistics for all ACEs with assigned counter labels, attached to interfaces on the device. An entry in this table is created when an ACL containing an ACE that references the specified counter label name is applied to an interface. An entry in this table is deleted when an ACL containing an ACE that references the specified counter label name is removed from an interface.

CISCO-ATM-EXT-MIB

The CISCO-ATM-EXT-MIB is an extension to the Cisco ATM MIB module for managing ATM implementations.

Table 3-14 lists the tables associated with this MIB.

 

Table 3-14 CISCO-ATM-EXT-MIB Tables and Descriptions

Name
Description

cAal5VccExtTable

This table contains AAL5 VCC performance parameters beyond that provided by cAal5VccEntry.

catmxVclOamTable

This table contains VCL2 Oam configuration and state information. This table augments the atmVclTable.

2.VCL = Virtual Channel Link

MIB Constraints

Table 3-11 lists the constraints that the router places on objects in the BRIDGE-MIB. For detailed definitions of MIB objects, see the MIB. This MIB only supports managing two types of bridges (CE and VPLS bridges).


NoteSet Operation on BRIDGE-MIB objects is not supported.


 

Table 3-15 CISCO-ATM-EXT-MIB Constraints

MIB Object
Notes

catmxVclOamLoopbackFreq

Not supported

catmxVclOamRetryFreq

Not supported

catmxVclOamUpRetryCount

Not supported

catmxVclOamDownRetryCount

Not supported

catmxVclOamEndCCActCount

Not supported

catmxVclOamEndCCDeActCount

Not supported

catmxVclOamEndCCRetryFreq

Not supported

catmxVclOamSegCCActCount

Not supported

catmxVclOamSegCCDeActCount

Not supported

catmxVclOamSegCCRetryFreq

Not supported

catmxVclOamManage

Not supported

CISCO-ATM-QOS-MIB

The CISCO-ATM-QOS-MIB is created to provide ATM QoS information in the following areas:

  • Traffic shaping on a per-VC basis
  • Traffic shaping on a per-VP basis
  • Per-VC queuing or buffering

Although the initial requirements of the MIB are driven to support the GSR TAZ line card, CISCO-ATM-QOS-MIB is designed as a generic MIB to support ATM interfaces cross all platforms.

Table 3-16 lists the tables associated with this MIB.

 

Table 3-16 CISCO-ATM-QOS-MIB Tables and Descriptions

Name
Description

caqVccParamsTable

This table is defined to provide QoS information for each active ATM VC existing on the interface.

caqVpcParamsTable

This table is defined to provide QoS information for each active ATM VP existing on the interface.

caqQueuingParamsTable

This table provides queuing related information for a VC existing on an ATM interface.

caqQueuingParamsClassTable

This table provides queuing information for all queuing classes associating with a VC.

MIB Constraints

Table 3-17 lists the constraints that the router places on objects in the CISCO-ATM-QOS-MIB.

Table 3-17 CISCO-ATM-QOS-MIB Constraints

MIB Object
Notes

caqVccParamsType

Not supported

caqVccParamsPcrIn0

Not supported

caqVccParamsPcrIn01

Not supported

caqVccParamsPcrOut0

Not supported

caqVccParamsPcrOut01

Not supported

caqVccParamsScrIn0

Not supported

caqVccParamsScrIn01

Not supported

caqVccParamsScrOut0

Not supported

caqVccParamsScrOut01

Not supported

caqVccParamsBcsIn0

Not supported

caqVccParamsBcsIn01

Not supported

caqVccParamsBcsOut0

Not supported

caqVccParamsBcsOut01

Not supported

caqVccParamsMcrIn

Not supported

caqVccParamsMcrOut

Not supported

caqVccParamsInvRdf

Not supported

caqVccParamsInvRif

Not supported

caqVccParamsCdvt

Not supported

caqVccParamsIcr

Not supported

caqVccParamsTbe

Not supported

caqVccParamsFrtt

Not supported

caqVccParamsNrm

Not supported

caqVccParamsInvTrm

Not supported

caqVccParamsInvCdf

Not supported

caqVccParamsAdtf

Not supported

CISCO-BGP4-MIB

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

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

Table 3-18 lists the tables associated with this MIB.

 

Table 3-18 CISCO-BGP4-MIB Tables and Descriptions

Name
Description

cbgpRouteTable

This table contains information about routes to destination networks from all BGP4 peers. Because BGP4 can carry routes for multiple Network Layer protocols, this table has the AFI3 of the Network Layer protocol as the first index. Further for a given AFI, routes carried by BGP4 are distinguished based on SAFI. Hence, that is used as the second index. Conceptually there is a separate Loc-RIB maintained by the BGP speaker for each combination of AFI and SAFI supported by it.

cbgpPeerTable

BGP peer table. This table contains, one entry per BGP peer, information about the connections with BGP peers.

cbgpPeerCapsTable

This table contains the capabilities that are supported by a peer. Capabilities of a peer are received during BGP connection establishment. Values corresponding to each received capability are stored in this table. When a new capability is received, this table is updated with a new entry. When an existing capability is not received during the latest connection establishment, the corresponding entry is deleted from the table.

cbgpPeerAddrFamilyTable

This table contains information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

cbgpPeerAddrFamilyPrefixTable

This table contains prefix related information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table.

3.AFI = Address Family Identifiers

MIB Constraints

Table 3-19 lists the constraints that the router places on objects in the CISCO-BGP4-MIB.

 

Table 3-19 CISCO-BGP4-MIB Constraints

MIB Object
Notes

cbgpNotifsEnable

Not supported

cbgpPeer2AdminStatus

Not supported

cbgpPeer2ConnectRetryInterval

Not supported

cbgpPeer2HoldTimeConfigured

Not supported

cbgpPeer2KeepAliveConfigured

Not supported

cbgpPeer2MinASOriginationInterval

Not supported

cbgpPeer2MinRouteAdvertisementInterval

Not supported

cbgpPeer2PrefixAdminLimit

Not supported

cbgpPeer2PrefixThreshold

Not supported

cbgpPeerPrefixAdminLimit

Not supported

cbgpPeerPrefixThreshold

Not supported

CISCO-BGP-POLICY-ACCOUNTING-MIB

The CISCO-BGP-POLICY-ACCOUNTING-MIB describes BGP policy based accounting information. Support is provided for both source and destination IP address based statistics for ingress and egress traffic.


NoteCISCO-BGP-POLICY-ACCOUNTING-MIB support is in the context of IPv4 traffic. This MIB is not supported for IPv6.


Table 3-20 lists the tables associated with this MIB.

Table 3-20 CISCO-BGP-POLICY-ACCOUNTING-MIB Tables and Descriptions

Name
Description

cbpAcctTable

cbpAcctTable provides statistics about ingress and egress traffic on an interface. This data could be used for purposes like billing.

CISCO-BULK-FILE-MIB

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

Table 3-21 lists the tables associated with this MIB.

Table 3-21 CISCO-BULK-FILE-MIB Tables and Descriptions

Name
Description

cbfDefineFileTable

Table of bulk file definition and creation controls

cbfDefineObjectTable

Table of objects to go in bulk files

cbfStatusFileTable

Table of bulk file status

MIB Constraints

Table 3-22 lists the constraints that the router places on objects in the CISCO-BULK-FILE-MIB. For detailed definitions of MIB objects, see the MIB.

 

Table 3-22 CISCO-BULK-FILE-MIB Constraints

MIB Object
Notes
cbfDefineFileTable

 

  • cbfDefinedFileStorage

Only ephemeral type of file storage is supported.

Note The ephemeral bulk file created can be moved to a remote FTP server using CISCO-FTP-CLIENT-MIB.

  • cbfDefinedFileFormat

Only bulkBinary and bulkASCII file formats are supported.

 
The cbfDefienFileTable has objects that are required for defining a bulk file and for controlling its creation. The cbfDefineObjectTable has information regarding the contents (SNMP data) that go into the bulk file.

 
When an entry in the cbfDefineFileTable and its corresponding entries in the cbfDefineObjectTable are active, then cbfDefineFileNow can then be set to create. This causes a bulkFile to be created as defined in cbfDefineFileTable and it will also create an entry in the cbfStatusFileTable.

CISCO-CDP-MIB

The CISCO-CDP-MIB module manages the Cisco Discovery Protocol in Cisco devices.

Table 3-23 lists the tables associated with this MIB.

 

Table 3-23 CISCO-CDP-MIB Tables and Descriptions

Name
Description

cdpInterfaceTable

(conceptual) Table containing the status of CDP on the device interfaces.

cdpInterfaceExtTable

This table contains the additional CDP configuration on the interface of the device. This table is not supported.

cdpCacheTable

(conceptual) Table containing the cached information obtained via receiving CDP messages.

cdpCtAddressTable

(conceptual) Table containing the list of network-layer addresses of a neighbor interface, as reported in the Address TLV of the most recently received CDP message. The first address included in the Address TLV is saved in cdpCacheAddress. This table contains the remainder of the addresses in the Address TLV. This table is not supported.

MIB Constraints

Table 3-24 lists the constraints that the router places on objects in the CISCO-CDP-MIB. For detailed definitions of MIB objects, see the MIB.

 

Table 3-24 CISCO-CDP-MIB Constraints

MIB Object
Notes
cdpInterfaceExtTable

Not supported

cdpCtAddressTable

Not supported

CISCO-CLASS-BASED-QOS-MIB

The CISCO-CLASS-BASED-QOS-MIB provides read access to Quality of Service (QoS) configuration information and statistics for Cisco platforms that support the modular Quality of Service command-line interface (modular QoS CLI).

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 one or more match statements used to classify packets into different categories.
  • Feature action – Action taken on classified traffic. Features include police, traffic shaping, queueing, random detect, and packet marking. After the traffic is classified actions are applied to packets matching each traffic class.
  • Policy map – A user-defined policy that associates QoS feature actions to user-defined class maps as policy maps can have multiple class maps.
  • Service policy – A policy map that has been attached to an interface.

The MIB uses the following indices to identify QoS 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 configurations.
  • cbQosPolicyIndex – Uniquely identifies a service policy.

QoS MIB information is stored in:

  • Configuration instances – Includes all class maps, policy maps, 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 Policy Map features. Each has a unique run-time instance. Run-time instances of QoS objects are each assigned a unique identifier (cbQosObjectsIndex) to distinguish among multiple objects with matching configurations.

MIB Tables

Table 3-25 lists the tables in a CISCO-CLASS-BASED-QOS-MIB:

 

Table 3-25 CISCO-CLASS-BASED-QOS-MIB Tables

MIB Table
Description

cbQosQueueingClassCfgTable

Specifies the configuration information for a weighted queue limit action for each IP precedence.

cbQosMeasureIPSLACfgTable

Specifies the configuration information for measure type IPSLA action. The measure action maps to the policy class to a specific IPSLAs auto group. Use this table to retrieve the measure action configuration information.

cbQosServicePolicyTable

Describes the logical interfaces , media types, and the corresponding policy-maps attached.

cbQosInterfacePolicyTable

Describes the service policies attached to the main and sub-interfaces.

cbQosFrameRelayPolicyTable

Describes the service policies attached to the Frame Relay DLCIs.

cbQosATMPVCPolicyTable

Describes the policies that are attached to an ATM PVC.

cbQosObjectsTable

Specifies the QoS objects (classmap, policymap, match statements, and actions) hierarchy and provides a relationship between each PolicyIndex, ObjectsIndex pair, and the ConfigIndex. ConfigIndex is essential for querying any configuration tables.

cbQosPolicyMapCfgTable

Specifies the policy-map configuration information.

cbQosCMCfgTable

Specifies the class map configuration information.

cbQosMatchStmtCfgTable

Specifies the class map configuration information.

cbQosQueueingCfgTable

Specifies the Queueing Action configuration information.

cbQosREDCfgTable

Specifies the WRED action configuration information.

cbQosREDClassCfgTable

Specifies WRED action configuration information on a per IP precedence basis.

cbQosPoliceCfgTable

Specifies police action configuration information.

cbQosPoliceActionCfgTable

Specifies police action configuration information.

cbQosTSCfgTable

Specifies traffic-shaping action configuration information.

cbQosSetCfgTable

Specifies the packet marking action configuration information.

cbQosCMStatsTable

Specifies the class map related statistical information.

cbQosMatchStmtStatsTable

specifies the match statement related statistical information.

cbQosPoliceStatsTable

Specifies the police action related statistical information.

cbQosQueueingStatsTable

Specifies the queueing action related statistical information.

cbQosTSStatsTable

Specifies the traffic-shaping action related statistical information.

cbQosREDClassStatsTable

Specifies the statistcal information for each precedence WRED action.

cbQosIPHCCfgTable

Specifies the IP header compression configuration information.

cbQosIPHCStatsTable

Specifies the IP header compression statistical information.

cbQosSetStatsTable

Specifies the packet marking statistical information.

cbQosPoliceColorStatsTable

Specifies the police action related statistical information for two rate color aware marker.

cbQosTableMapCfgTable

Specifies the table map basic configuration information.

cbQosTableMapValueCfgTable

Specifies the from-value to to-value conversion pairs for a tablemap.

cbQosTableMapSetCfgTable

Specifies the enhanced packet marking configuration using a pre-defined tablemap.

cbQosEBCfgTable

Specifies the estimate bandwidth related configuration information.

cbQosEBStatsTable

Specifies the estimate bandwidth related statistical information.

cbQosC3plAccountCfgTable

Specifies the C3pl account action configuration information

cbQosC3plAccountStatsTable

Specifies C3pl account action related statistics information.

MIB Constraints

Table 3-26 lists the constraints on objects in the CISCO-CLASS-BASED-QOS-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-26 CISCO-CLASS-BASED-QOS-MIB Constraints

MIB Object
Notes
cbQosATMPVCPolicyTable

Not supported

cbQosC3plAccountCfgTable

Not supported on XR

cbQosC3plAccountStatsTable

Not supported on XR

cbQosCMStatsTable

 

  • CbQosCMNoBufDropPktOverflow

Lack of SRAM buffers, count is negligible.

  • CbQosCMNoBufDropPkt

Lack of SRAM buffers, count is negligible.

  • CbQosCMNoBufDropPkt64

Lack of SRAM buffers, count is negligible.

cbQosEBCfgTable

Not supported in QoS on XR

cbQosEBStatsTable

Not supported

cbQosEVCGroup

Not supported

cbQosFrameRelayPolicyTable

Not supported

cbQosInterfacePolicyTable

Not supported

cbQosIPHCStatsTable

Only RTP supported on XR.

cbQosMeasureIPSLACfgTable

Not supported on XR

cbQosMatchStmtStatsTable

 

  • CbQosMatchPrePolicyPktOverflow

Not supported

  • CbQosMatchPrePolicyPkt

Not supported

  • CbQosMatchPrePolicyPkt64

Not supported

  • CbQosMatchPrePolicyByteOverflow

Not supported

  • CbQosMatchPrePolicyByte

Not supported

  • CbQosMatchPrePolicyByte64

Not supported

  • CbQosMatchPrePolicyBitRate

Not supported

cbQosNoBufferDropTable

Not supported

cbQosPoliceCfgTable

 

  • cbQosPoliceCfgConformAction

Deprecated and defined in cbQosPoliceActionCfgTable

  • cbQosPoliceCfgConformSetValue

Deprecated and defined in cbQosPoliceActionCfgTable

  • cbQosPoliceCfgExceedAction

Deprecated and defined in cbQosPoliceActionCfgTable

  • cbQosPoliceCfgExceedSetValue

Deprecated and defined in cbQosPoliceActionCfgTable

  • cbQosPoliceCfgViolateAction

Deprecated and defined in cbQosPoliceActionCfgTable

  • cbQosPoliceCfgViolateSetValue

Deprecated and defined in cbQosPoliceActionCfgTable

cbQosQueueingCfgTable

 

  • cbQosQueueingCfgFlowEnabled

Not supported

  • cbQosQueueingCfgAggregateQSize

Deprecated by cbQosQueueingCfgAggregateQLimit

  • cbQosQueueingCfgDynamicQNumber

Not supported

  • cbQosQueueingCfgPrioBurstSize

Not supported

cbQosQueueingClassCfgTable

Not supported

cbQosREDCfgTable

 

  • cbQosREDCfgExponWeight

Not supported on XR

  • cbQosREDCfgMeanQSize

Replaced by cbQosREDMeanQsize

  • cbQosREDCfgECNEnabled

Not supported

cbQosREDClassCfgTable

 

  • cbQosREDCfgMinThreshold

Deprecated by cbQosREDClassCfgMInThreshold. For XR, many objects from cbQosRedCfg are now available via cbQosREDClassCfg

  • cbQosREDCfgMaxThreshold

Deprecated by cbQosREDClassCfgMInThreshold. For XR, many objects from cbQosRedCfg are now available via cbQosREDClassCfg

cbQosREDClassStatsTable

 

  • CbQosREDMeanQSizeUnits

Not supported

  • CbQosREDMeanQSize

Not supported

cbQosServicePolicyTable

 

cbQosEntityIndex

Not supported

cbQosSetStatsTable

Marking statistics are not supported on XR

cbQosTableMapCfgTable

Not supported on XR

cbQosTableMapValueCfgTable

Not supported

cbQosTableMapSetCfgTable

Not supported

cbQosTrafficShapingDelayCountersGroup

Not supported

cbQosTSCfgTable

 

  • CbQosTSCfgBurstsize

Not supported

  • CbQosTSCfgAdaptiveEnabled

Not supported

  • CbQosTSCfgAdaptiveRate

Not supported

cbQosTSStatsTable

 

  • CbQosTSStatsCurrentQSize

Not supported

CISCO-CONFIG-COPY-MIB

The CISCO-CONFIG-COPY-MIB contains objects to copy configuration files on the router. For example, the MIB enables the SNMP agent to copy:

  • Configuration files to and from the network
  • The running configuration to the startup configuration and startup to running
  • The startup or running configuration files to and from a local Cisco IOS XR Software file system

Table 3-27 lists the tables associated with this MIB.

Table 3-27 CISCO-CONFIG-COPY-MIB Tables and Descriptions

Name
Description

ccCopyTable

Table of config-copy requests.

ccCopyErrorTable

Table containing information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to 'failed' for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = 'runningConfig' ccCopyDestFileType = 'fabricStartupConfig'. In this case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be 'fabricStartupConfig', it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState 'failed', but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, 'success'. After the config copy operation finishes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. After an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. To prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out.

MIB Constraints

Table 3-28 lists the constraints that the router places on objects in the CISCO-CONFIG-COPY-MIB.

Table 3-28 CISCO-CONTEXT-MAPPING-MIB Constraints

MIB Object
Notes

ccCopyProtocol

rcp (3) is not supported.

ccCopySourceFileType

startupConfig(3) and terminal (5) are not supported.

ccCoypDestFileType

startupConfig(3) and terminal (5) are not supported.

CISCO-CONFIG-MAN-MIB

The CISCO-CONFIG-MAN-MIB contains objects to track and save changes to the router configuration. The MIB represents a model of the configuration data that exists in the router and in the peripheral devices. Its main purpose is to report changes to the running configuration through the SNMP notification ciscoConfigManEvent.

Table 3-29 lists the tables associated with this MIB.

Table 3-29 CISCO-CONFIG-MAN-MIB Tables and Descriptions

Name
Description

ccmHistoryEventTable

Table of configuration events on this router

ccmCLIHistoryCommandTable

Table of CLI commands that took effect during configuration events

CISCO-CONTEXT-MAPPING-MIB

The CISCO-CONTEXT-MAPPING-MIB provides option to associate an SNMP context to a feature package group. This MIB allows manageability of license MIB objects specific to a feature package group.

A single SNMP agent sometimes needs to support multiple instances of the same MIB module, and does so through the use of multiple SNMP contexts. This typically occurs because the technology has evolved to have extra dimensions; that is, one or more extra data value, identifier value or both which are different in the different contexts, but were not defined in INDEX clauses of the original MIB module. In such cases, network management applications need to know the specific data or identifier values in each context, and this MIB module provides mapping tables which contain that information.

Within a network there can be multiple VPNs configured using Virtual Routing and Forwarding Instances (VRFs). Within a VPN there can be multiple topologies when Multi-topology Routing (MTR) is used. Also, Interior Gateway Protocols (IGPs) can have multiple protocol instances running on the device. A network can have multiple broadcast domains configured using Bridge Domain Identifiers.

With MTR routing, VRFs, and Bridge domains, a router now needs to support multiple instances of several existing MIB modules, and this can be achieved if the SNMP agent of the router provides access to each instance of the same MIB module via a different SNMP context (see Section 3.1.1 of RFC 3411). For MTR routing, VRFs, and Bridge domains, a different SNMP context is needed depending on one or more of the following: the VRF, the topology-identifier, the routing protocol instance, and the bridge domain identifier. In other words, the management information of the router can be accessed through multiple SNMP contexts where each such context represents a specific VRF, a specific topology-identifier, a specific routing protocol instance or a bridge domain identifier. This MIB module provides a mapping of each such SNMP context to the corresponding VRF, the corresponding topology, the corresponding routing protocol instance, and the corresponding bridge domain identifier. Some SNMP contexts are independent of VRFs, independent of a topology, independent of a routing protocol instance, or independent of a bridge domain and in such a case, the mapping is to the zero length string.

With the Cisco package licensing strategy, the features available in the image are grouped into multiple packages and each package can be managed to operate at different feature levels based on the available license.

Table 3-30 lists the tables associated with this MIB.

 

Table 3-30 CISCO-CONTEXT-MAPPING-MIB Tables and Descriptions

Name
Description

cContextMappingTable

This table contains information on which cContextMappingVacmContextName is mapped to which VRF, topology, and routing protocol instance. This table is indexed by SNMP VACM context. Configuring a row in this table for an SNMP context does not require that the context be already defined; that is, a row can be created in this table for a context before the corresponding row is created in RFC 3415 vacmContextTable. To create a row in this table, a manager must set cContextMappingRowStatus to either 'createAndGo' or 'createAndWait'. To delete a row in this table, a manager must set cContextMappingRowStatus to 'destroy'.

cContextMappingBridgeDomainTable

This table contains information on which cContextMappingVacmContextName is mapped to which bridge domain. A Bridge Domain is one of the means by which it is possible to define an Ethernet broadcast domain on a bridging device. A network can have multiple broadcast domains configured. This table helps the network management personnel to find out the details of various broadcast domains configured in the network. An entry need to exist in cContextMappingTable, to create an entry in this table.

cContextMappingBridgeInstanceTable

This table contains information on mapping between cContextMappingVacmContextName and bridge instance. Bridge instance is an instance of a physical or logical bridge that has unique bridge-id. If an entry is deleted from cContextMappingTable, the corresponding entry in this table also gets deleted. If an entry needs to be created in this table, the corresponding entry must exist in cContextMappingTable.

cContextMappingLicenseGroupTable

This table contains information on which cContextMappingVacmContextName is mapped to a License Group. Group level licensing is used where each Technology Package is enabled via a License.

MIB Constraints

Table 3-31 lists the constraints that the router places on objects in the CISCO-CONTEXT-MAPPING-MIB.

Table 3-31 CISCO-CONTEXT-MAPPING-MIB Constraints

MIB Object
Notes

cContextMappingBridgeInstName

Not supported

cContextMappingBridgeInstStorageType

Not supported

cContextMappingBridgeInstRowStatus

Not supported

cContextMappingVrfName

Not supported

cContextMappingTopologyName

Not supported

cContextMappingProtoInstName

Not supported

cContextMappingStorageType

Not supported

cContextMappingRowStatus

Not supported

cContextMappingBridgeDomainIdentifier

Not supported

cContextMappingBridgeDomainStorageType

Not supported

cContextMappingBridgeDomainRowStatus

Not supported

CISCO-DS3-MIB

The CISCO-DS3-MIB describes DS3 line objects. This is an extension to the standard DS3 MIB
(RFC 2496).

Table 3-32 lists the tables associated with this MIB.

 

Table 3-32 CISCO-DS3-MIB Tables and Descriptions

Name
Description

cds3ConfigTable

This table has objects for configuring a T3/E3 line.

cds3AlarmConfigTable

This table contains the parameters associated with detecting and declaring alarms for the interface. The parameters include severity of alarm, alarm integration parameters, and 15-minute and 24-hour thresholds.

cds3StatsTable

T3/E3 Statistics table. This table maintains the number of times the line encountered LOS4, LOF5, AIS6, RAI7, CCV8, FE9, from the time it is up. Line fails and goes down. When the line is brought back up again by the user the error statistics are cleared.

cds3AlarmConfigPlcpTable

ATM interface PLCP alarm configuration table. PLCP is a sublayer over the DS3 interface, that carries ATM cells.

cds3AlarmPlcpTable

Plcp interface alarm table. This table maintains the CV,ES,SES, SEFS and UAS for DS3 line with Plcp framing selected. See RFC 2496 for description of these various error statistics.

cds3AlarmPlcpTable

Plcp interface alarm table. This table maintains the CV,ES,SES, SEFS and UAS for DS3 line with Plcp framing selected. See RFC 2496 for description of these various error statistics.

cds3PlcpStatsTable

T3 Plcp Statistics table. This table maintains the errors encountered by the T3 line with Plcp frame format selected, from the time the line is up. Line fails and goes down. When the line is brought back up again by the user after eliminating the error conditions, the statistics are cleared.

cds3PlcpStatsTable

T3 Plcp Statistics table. This table maintains the errors encountered by the T3 line with Plcp frame format selected, from the time the line is up. Line fails and goes down. When the line is brought back up again by the user after eliminating the error conditions, the statistics are cleared.

cds3IntervalTable

DS3 interface interval table.

cds3Current24HrTable

DS3 interface current 24-hour table. This table contains counters for current 24-hour interval. Threshold on this counters are configured through cds3AlarmConfigTable table. 24-hour interval is aligned to wall clock.

cds3Previous24HrTable

DS3 interface previous 24-hour table. This table contains counters for previous 24-hour interval. Implementation of this table is optional.

4.LOS = loss of signal

5.LOF = out of frame

6.AIS = alarm indication signals

7.RAI = remote alarm indications

8.CCV = C-bit coding violations

9.FE = framing errors

MIB Constraints

Table 3-33 lists the constraints that the router places on objects in the CISCO-DS3-MIB.

 

Table 3-33 CISCO-DS3-MIB Constraints

MIB Object
Notes

cds3PlcpStatisticalAlarmSeverity

Not supported

cds3PlcpBip8CV15MinThreshold

Not supported

cds3PlcpBip8CV24HrThreshold

Not supported

cds3PlcpBip8ES15MinThreshold

Not supported

cds3PlcpBip8ES24HrThreshold

Not supported

cds3PlcpBip8SES15MinThreshold

Not supported

cds3PlcpBip8SES24HrThreshold

Not supported

cds3PlcpSEFS15MinThreshold

Not supported

cds3PlcpSEFS24HrThreshold

Not supported

cds3PlcpUAS15MinThreshold

Not supported

cds3PlcpUAS24HrThreshold

Not supported

cds3LineType

Not supported

cds3LineAIScBitsCheck

Not supported

cds3LineRcvFEACValidation

Not supported

cds3LineOOFCriteria

Not supported

cds3TraceToTransmit

Not supported

cds3TraceToExpect

Not supported

cds3InternalEqualizer

Not supported

cds3NEAlarmUpCount

Not supported

cds3NEAlarmDownCount

Not supported

cds3NEAlarmThreshold

Not supported

cds3FEAlarmUpCount

Not supported

cds3FEAlarmDownCount

Not supported

cds3FEAlarmThreshold

Not supported

cds3StatisticalAlarmSeverity

Not supported

cds3LCV15MinThreshold

Not supported

cds3LCV24HrThreshold

Not supported

cds3LES15MinThreshold

Not supported

cds3LES24HrThreshold

Not supported

cds3PCV15MinThreshold

Not supported

cds3PCV24HrThreshold

Not supported

cds3PES15MinThreshold

Not supported

cds3PES24HrThreshold

Not supported

cds3PSES15MinThreshold

Not supported

cds3PSES24HrThreshold

Not supported

cds3SEFS15MinThreshold

Not supported

cds3SEFS24HrThreshold

Not supported

cds3UAS15MinThreshold

Not supported

cds3UAS24HrThreshold

Not supported

cds3CCV15MinThreshold

Not supported

cds3CCV24HrThreshold

Not supported

cds3CES15MinThreshold

Not supported

cds3CES24HrThreshold

Not supported

cds3CSES15MinThreshold

Not supported

cds3CSES24HrThreshold

Not supported

cds3LSES15MinThreshold

Not supported

cds3LSES24HrThreshold

Not supported

CISCO-ENHANCED-IMAGE-MIB

The CISCO-ENHANCED-IMAGE-MIB provides information about events running on the system. This MIB has Image table containing the following information related to the running the Cisco IOS XR Software image:

  • Entity index
  • Image name
  • Family
  • Feature set
  • Version
  • Media
  • Description

NoteOnly ceImageTable is supported in this MIB.


Table 3-34 lists the tables associated with this MIB.

Table 3-34 CISCO-ENHANCED-IMAGE-MIB Tables and Descriptions

Name
Description

ceImageTable

This table provides information describing the executing image. For modular operating systems this table provides base image or MBI.

ceImageLocationTable

This table is applicable to modular operating systems. A location describes where on the file system the installed software is placed. This table consists of list of all locations along with status of image at that location. ceImageLocationRunningStatus is true only for the location from where system is currently operational. The agent may add entries to this table when a new image is installed on the system. The agent may delete entries from this table when an image has been removed from the system.

ceImageInstallableTable

This table specifies a list of software drivers installed on the system. This table is applicable to operating systems which support installables. A modular operating system can consist of base image or MBI and installables. The value of ceImageLocationIndex can be used as index to retrieve installables installed at a particular location. Every image has a table of installables. Entries are added in this table when an installable is installed on the image. Entries are deleted from this table when installables are removed or rolled back from the image.

ceImageTagTable

A tag is a virtual label placed by a user that indicates a point deemed to be stable. It can be used to rollback to a system after an install that negatively impacts the functionality of the system. It gives point in system where user can go back to, to remove drivers installed after that point of time. When a tag is placed on an image, an entry appears in this table. An entry is removed from this table when tag is removed from the system. The value of ceImageLocationIndex is used as index to get all the tags that are placed on the image at this location.

CISCO-ENHANCED-MEMPOOL-MIB

The CISCO-ENHANCED-MEMPOOL-MIB contains objects to monitor memory pools on all of the physical entities on a managed system. Represents the different types of memory pools that may be present in a managed device. Memory use information is provided to users at three different intervals of time: 1 minute, 5 minutes, and 10 minutes. Memory pools can be categorized into two groups, predefined pools and dynamic pools. The following pool types are currently predefined:

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

Dynamic pools have a pool type value greater than any of the predefined types listed above. Only the processor pool is required to be supported by all devices. Support for other pool types is dependent on the device being managed. Table 3-35 lists the tables associated with this MIB.

 

Table 3-35 CISCO-ENHANCED-MEMPOOL-MIB Tables and Descriptions

Name
Description

cempMemPoolTable

Table of memory pool monitoring entries for all physical entities on a managed system.

cempMemBufferPoolTable

Entries in this table define entities (buffer pools in this case) which are contained in an entity (memory pool) defined by an entry from cempMemPoolTable.

cempMemBufferCachePoolTable

Table that lists the cache buffer pools configured on a managed system.

  • To provide a noticeable performance boost, Cache Pool can be used. A Cache Pool is effectively a lookaside list of free buffers that can be accessed quickly. Cache Pool is tied to Buffer Pool.
  • Cache pools can optionally have a threshold value on the number of cache buffers used in a pool. This can provide flow control management by having an implementation specific approach such as invoking a vector when pool cache rises above the optional threshold set for it on creation.

MIB Constraints

Table 3-36 lists the constraints on objects in the CISCO-ENHANCED-MEMPOOL-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-36 CISCO-ENHANCED-MEMPOOL-MIB Constraints

MIB Object
Notes
ciscoMemoryPoolTable

 

cempMemPoolType

Values are:

  • processorMemory (2)
  • ioMemory (3)

cempMemPoolAlternate

Always 0

cempMemPoolPlatformMemory

Always 0

cempMemBufferNotifyEnabled

Not supported

cempMemBufferSize

Not supported

cempMemBufferMin

Not supported

cempMemBufferMax

Not supported

cempMemBufferPermanent

Not supported

cempMemBufferTransient

Not supported

CISCO-ENTITY-ASSET-MIB

The CISCO-ENTITY-ASSET-MIB provides asset tracking information for the physical components in the ENTITY-MIB (RFC 2737) entPhysicalTable.

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.

Most physical components are programmed with a standard Cisco generic Identification Programmable Read-Only Memory (IDPROM) value that specifies asset information for the component. If possible, the MIB accesses the component’s IDPROM information.

MIB Tables

Table 3-37 lists the tables in the CISCO-ENTITY-ASSET-MIB:

 

Table 3-37 CISCO-ENTITY-ASSET-MIB Tables

MIB Table
Description

ceAssetTable

Provides this information for the entities in the ENTITY-MIB entPhysicalTable:

  • Orderable part number
  • Serial number
  • Hardware revision
  • Manufacturing assembly number
  • Revision number
  • FirmwareID and revision if any
  • SoftwareID and revision if any

Table 3-38 gives more information on the objects associated with this MIB.

Table 3-38 CISCO-ENTITY-ASSET-MIB Objects and Value Information

Name
Description

ceAssetMfgAssyNumber

Top-level assembly number stored in IDPROM

ceAssetMfgAssyRevision

This object should reflect the revision of the TAN stored in IDPROM.

ceAssetFirmwareID

This object value should be the same as entPhysicalFirmwareRev of ENTITY-MIB.

ceAssetSoftwareID

This object value should be the same as entPhysicalSoftwareRev of ENTITY-MIB.

ceAssetCLEI

This object should reflect the value of the CLEI stored in the IDPROM supported by the physical entity.

MIB Constraints

Table 3-39 lists the constraints that the Cisco ASR 9000 Series router places on objects in the CISCO-ENTITY-ASSET-MIB.

 

Table 3-39 CISCO-ENTITY-ASSET-MIB Constraints

MIB Object
Notes

ceAssetAlias

Not supported

ceAssetTag

Not supported

CISCO-ENTITY-FRU-CONTROL-MIB

The CISCO-ENTITY-FRU-CONTROL-MIB contains objects to configure and monitor the operational status of field replaceable units (FRUs) on the Cisco ASR 9000 Series router listed in the ENTITY-MIB entPhysicalTable. A FRU is a hardware component (such as a line card and module, fan, or power supply) that can be replaced on site.

MIB Tables

Table 3-40 lists the tables in the CISCO-ENTTY-FRU-CONTROL-MIB:

 

Table 3-40 CISCO-ENTITY-FRU-CONTROL-MIB Tables

MIB Table
Description

cefcFRUPowerSupplyGroupTable

Displays the redundancy mode and the operational status of the power supply groups in the system.

cefcFRUPowerStatusTable

Displays the power-related administrative status and operational status of the manageable components in the system.

cefcFRUPowerSupplyValueTable

Displays the power capacity of a power FRU in the system if it provides variable power. This table supplements the information in the cefcFRUPowerStatusTable for power supply FRUs. The cefcFRUCurrent attribute in cefcFRUPowerStatusTable table indicates the type of power the FRU can supply.

cefcModuleTable

Displays the operational and administrative status information for ENTITY-MIB entPhysicalTable entries for the manageable components of type PhysicalClass module(9).

cefcIntelliModuleTable

A cefcIntelliModuleTable entry lists the information specific to intelligent modules that are not listed under the cefcModuleTable. This table supplements the cefcModuleTable (every row in this table corresponds to a row in the cefcModuleTable but not necessarily vice-versa).

cefcFanTrayStatusTable

Provides the operational status information for all the ENTITY-MIB entPhysicalTable entries that have an entPhysicalClass valus as fan. The entPhysicalClass valus as fan indicates either:

  • A physical fan
  • A combination of multiple fans.

cefcPhysicalTable

Displays a single row for each physical entity.

cefcPowerSupplyInputTable

Provides the power input information for all the power supplies that have entPhysicalTable entries with powerSupply as the entPhysicalClass.

cefcPowerSupplyOutputTable

Displays the output modes for the power supplies and the modes that are operational within the system.

cefcChassisCoolingTable

Displays the cooling capacity information of the chassis (for ENTITY-MIB entPhysicalTable entries having an entPhysicalClass value as chassis).

cefcFanCoolingTable

Displays the cooling capacity information of the fans (for ENTITY-MIB entPhysicalTable entries having an entPhysicalClass value as fanI).

cefcModuleCoolingTable

Specifies the cooling requirement for all the manageable components having entPhysicalClass value as module.

cefcFanCoolingCapTable

Displays the possible cooling capacity modes and properties of the fans(for ENTITY-MIB entPhysicalTable entries having entPhysicalClass value fan).

cefcConnectorRatingTable

Specifies the connector power ratings of FRUs.

cefcModulePowerConsumptionTable

Provides the total power consumption information for modules (for ENTITY-MIB entPhysicalTable entries having entPhysicalClass value as module).

MIB Constraints

Table 3-41 lists the constraints that the router places on objects in the CISCO-ENTITY-FRU-CONTROL-MIB.

 

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

MIB Object
Notes
cefcModuleTable

 

cefcModuleAdminStatus

Set operation not supported

cefcModuleOperStatus

unknown (1)
ok (2)
failed (7)

cefcModuleResetReason

unknown (1)
powerUp (2)
manualReset (5)

cefcModuleLastClearConfigTime

Not implemented

cefcModuleResetReasonDescription

Not implemented

cefcModuleStateChangeReasonDescr

Not implemented

cefcFRUTotalSystemCurrent

Not supported

cefcFRUDrawnSystemCurrent

Not supported

cefcFRUTotalInlineCurrent

Not supported

cefcFRUDrawnInlineCurrent

Not supported

cefcFRUPowerAdminStatus

on(1)

off(2)

cefcFRUPowerOperStatus

offEnvOther(1)

on(2)

offAdmin(3)

cefcPowerRedundancyMode

Not supported

cefcModuleAdminStatus

Not supported

cefcMaxDefaultHighInLinePower

Not supported

cefcFRUPowerSupplyGroupTable

Not supported

cefcFRUPowerSupplyValueTable

Not supported

cefcIntelliModuleTable

Not supported

cefcPowerSupplyInputTable

Not supported

cefcPowerSupplyOutputTable

Not supported

cefcChassisCoolingTable

Not supported

cefcFanCoolingTable

Not supported

cefcModuleCoolingTable

Not supported

cefcFanCoolingCapTable

Not supported

cefcConnectorRatingTable

Not supported

cefcModulePowerConsumptionTable

Not supported

CISCO-ENTITY-REDUNDANCY-MIB

The CISCO-ENTITY-REDUNDANCY-MIB management information module supports configuration, control and monitoring of redundancy protection for various kinds of components on Cisco managed devices. It is meant to be generic enough to handle basic redundancy control and monitoring for many types of redundant member components and redundancy architectures as long as there is an Entity MIB entPhysicalIndex and entPhysicalVendorType assigned to each member component. It is designed so that the tables can be augmented in other extension MIBS which build upon this MIB by adding additional objects that may be specific to a particular type of redundancy or member component. This MIB can also be used in cases where some types of redundancy groups and members don’t require explicit user configuration. One example may be redundant fan assemblies. In those cases, the managed system should internally assign group and member indexes, so that it can provide read-only access to the group and member tables. This allows MIB monitoring for these types of redundant entities. The CISCO-ENTITY-REDUNDANCY-MIB is supported from Release 4.2.1 onwards.

MIB Tables

Table 3-42 lists the tables in CISCO-ENTITY-REDUNDANCY-MIB:

 

Table 3-42 CISCO-ENTITY-REDUNDANCY-MIB Tables

MIB Table
Description

ceRedunGroupTypesTable

This table lists the basic types of redundancy groups supported on the managed device along with additional information about each group type.

ceRedunVendorTypesTable

This table lists all entPhysicalVendorTypes allowed as members for a specific ceRedunGroupTypeIndex on the managed device, inclusive for all configurable values for ceRedunType, ceRedunScope, ceRedunArch, etc. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again. Note: Although a specific ceRedunGroupTypeIndex may allow groups of different entPhysicalVendorTypes, managed devices typically enforce all members within a specific group to have the same entPhysicalVendorType.

ceRedunInternalStatesTable

This table allows the managed system to report a read-only list of internal state numbers and the corresponding descriptions which apply for the members of a particular redundancy group type. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again.

ceRedunSwitchoverReasonTable

This table allows the managed system to report a read-only list of switchover reason indexes and the corresponding descriptions. If the ceRedunGroupDefinitionChanged object changes for a particular ceRedunGroupTypeIndex, then this table may have changed and should be read again.

ceRedunGroupTable

This table lists group configuration and status objects for a specific redundancy group. However, the members are configured separately in the ceRedunMbrTable.

ceRedunMbrConfigTable

This table lists the group members and generic redundancy objects which are associated with configuring redundancy group members. The switchover granularity should be for one member at a time. In other words if a member is allowed to be an individual port, then switchovers on multi-port linecards would be expected to take place independently for each port on the linecard. But if the members are full linecards, then all ports on the linecard would be expected to switch at the same time.

ceRedunMbrStatusTable

This table lists the redundancy status and other read-only redundancy objects which are associated with redundancy group members. Status associated with member alarm conditions should be reported separately using the CISCO-ENTITY-ALARM-MIB.

ceRedunCommandTable

This table allows switchover commands to be sent to members of configured redundancy groups.

MIB Constraints

Table 3-43 lists the constraints that the router places on the objects in the CISCO-ENTITY-REDUNDANCY-MIB. For detailed definitions of MIB objects, see the MIB.

 

Table 3-43 CISCO-ENTITY-REDUNDANCY-MIB Constraints

MIB Object
Notes

ceRedunGroupTypesTable

 

ceRedunGroupTypeName

Supported

ceRedunGroupCounts

Supported

ceRedunNextUnusedGroupIndex

Supported

ceRedunMaxMbrsInGroup

Supported

ceRedunUsesGroupName

Supported

ceRedunGroupDefinitionChanged

Supported

ceRedunVendorTypesTable

 

ceRedunVendorType

Supported

ceRedunInternalStatesTable

 

ceRedunStateCategory

Supported

ceRedunInternalStateDescr

Supported

ceRedunSwitchoverReasonTable

 

ceRedunReasonCategory

Supported

ceRedunSwitchoverReasonDescr

Supported

ceRedunGroupTable

 

ceRedunGroupString

Supported

ceRedunGroupRedunType

Supported

ceRedunGroupScope

Supported

ceRedunGroupArch

Supported

ceRedunGroupRevert

Supported

ceRedunGroupStorageType

Supported

ceRedunGroupRowStatus

Supported

ceRedunMbrConfigTable

 

ceRedunMbrPhysIndex

Supported

ceRedunMbrMode

Supported

ceRedunMbrStorageType

Supported

ceRedunMbrRowStatus

Supported

ceRedunMbrStatusTable

 

ceRedunMbrStatusCurrent

Supported

ceRedunMbrProtectingMbr

Supported

ceRedunMbrInternalState

Supported

ceRedunMbrSwitchoverCounts

Supported

ceRedunMbrLastSwitchover

Supported

ceRedunMbrSwitchoverReason

Supported

Scalar Objects

 

ceRedunGroupLastChanged

Supported

ceRedunMbrLastChanged

Supported

ceRedunMbrStatusLastChanged

Supported


Note • MIB tables and objects which are not included in the above list are not supported.

  • The ceRedunGroupTable and ceRedunMbrConfigTable have RowStatus objects and they are implemented as read-only. The access for other objects in these tables will be implemented as read-only.

CISCO-ENTITY-SENSOR-MIB

The CISCO-ENTITY-SENSOR-MIB contains objects to monitor the values and thresholds of sensors in the ENTITY-MIB entPhysicalTable.

MIB Tables

Table 3-44 lists the tables in CISCO-ENTITY-SENSOR-MIB:

 

Table 3-44 CISCO-ENTITY-SENSOR-MIB Tables

MIB Table
Description

entSensorValueTable

Displays the type, scale, and current value of a sensor listed in the Entity-MIB entPhysicalTable.

entSensorThresholdTable

Displays the threshold severity, relation, and comparison value for a sensor listed in the Entity-MIB entPhysicalTable.

MIB Constraints

Table 3-45 lists the constraints that the router places on the objects in the CISCO-ENTITY-SENSOR-MIB. For detailed definitions of MIB objects, see the MIB.

 

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

MIB Object
Notes
entSensorThresholdTable

 

  • entSensorThresholdRelation

Read-only

  • entSensorThresholdSeverity

Read-only

  • entSensorThresholdValue

Read-only


NoteSPA Transceiver sensors are not support in ASR 9000 release 3.9.


MIB Usage Values for Cisco Transceivers

The tables in this section list each type of sensor value represented in the entSensorValueTable and the entSensorThresholdTable.

Table 3-46 lists CISCO-ENTITY-SENSOR-MIB sensor objects and their usage values for Cisco ASR 9000 Series transceivers in the entSensorValueTable.

 

Table 3-46 CISCO-ENTITY-SENSOR-MIB Usage Values in the entSensorValueTable for Cisco Transceivers

MIB Sensor Object
Notes
Module Temperature Sensor

 

  • entSensorType

celsius (8)

  • entSensorScale

units (9)

  • entSensorPrecision

1

  • entSensorStatus

ok (1)

  • entSensorValue

Reports most recent measurement seen by the sensor

  • entSensorValueTimeStamp

Value indicates the age of the value reported by entSensorValue object

  • entSensorValueUpdateRate

Value indicates the rate that the agent updates entSensorValue in seconds, for example, 60 seconds.

Module Voltage Sensor

 

  • entSensorType

voltsDC(4)

  • entSensorScale

milli (8)

  • entSensorPrecision

1

  • entSensorStatus

ok (1)

  • entSensorValue

Reports most recent measurement seen by the sensor

  • entSensorValueTimeStamp

Value indicates the age of the value reported by entSensorValue object

  • entSensorValueUpdateRate

Value indicates the rate that the agent updates entSensorValue in seconds, for example, 60 seconds.

Tx Laser Current Sensor

 

  • entSensorType

amperes (5)

  • entSensorScale

milli(8)

  • entSensorPrecision

1

  • entSensorStatus

ok (1)

  • entSensorValue

Reports most recent measurement seen by the sensor

  • entSensorValueTimeStamp

Value indicates the age of the value reported by entSensorValue object

  • entSensorValueUpdateRate

Value indicates the rate that the agent updates entSensorValue in seconds, for example, 60 seconds.

Transmit Power Sensor (Optical Tx) and
Receive Power Sensor (Optical Rx)

 

  • entSensorType

watts (6)

  • entSensorScale

milli (8)

  • entSensorPrecision

1

  • entSensorStatus

ok (1)

  • entSensorValue

Reports most recent measurement seen by the sensor

  • entSensorValueTimeStamp

Value indicates the age of the value reported by entSensorValue object

  • entSensorValueUpdateRate

Value indicates the rate that the agent updates entSensorValue in seconds, for example, 60 seconds.

Each Cisco transceiver sensor has four threshold values corresponding to the four alarm states listed in Table 3-47 . The entSensorValueTable is indexed by both entPhysicalIndex and entSensorThresholdIndex. The Cisco ASR 9000 Series router entSensorThresholdIndices range from 1 to 4. For N/A, a value of zero is returned.

Table 3-47 lists the default values for the Cisco transceivers in the entSensorThresholdTable.

 

Table 3-47 Default Values in the entSensorThreshold Table for Cisco Transceivers

MIB Sensor Object
High Alarm
High Warning
Low Warning
Low Alarm
Temperature

70.0

60.0

5.0

0.0

Voltage

N/A

Not applicable

Not applicable

Not applicable

Tx Bias Current

80.0

75.0

15.0

10.0

Tx Optical Power

2.0

0.9

-4.0

-9.7

Rx Optical Power

2.0

0.4

-11.9

-15.0

CISCO-ENTITY-STATE-EXT-MIB

The CISCO-ENTITY-STATE-EXT-MIB is a Cisco Specific extension of ENTITY-STATE-MIB specified in RFC 4268. This MIB module is to add objects which provide additional information related to entity states. This MIB define notifications which are generated when a entity undergoes a redundancy switchover.

MIB Tables

Table 3-48 lists the tables in CISCO-ENTITY-STATE-EXT-MIB :

 

Table 3-48 CISCO-ENTITY-STATE-EXT-MIB Tables

MIB Table
Description

ceStateExtTable

An extension of the entStateTable, defined in ENTITY-STATE-MIB (rfc 4268) providing additional information and control objects for the entities listed in the table.

MIB Constraints

Table 3-49 lists the constraints that the router places on the objects in the CISCO-ENTITY-STATE-EXT-MIB. For detailed definitions of MIB objects, see the MIB.

 

Table 3-49 CISCO-ENTITY-STATE-EXT-MIB Constraints

MIB Object
Notes

ceStateExtPrevStandbyState

Not Supported

ceStateExtSwitchoverNotifEnable

Supported

ceStateExtStandbyStatusNotifEnable

Read-only

ceStateExtOperNotifEnable

Read-only

ceStateExtGlobalSwitchoverNotifEnable

Supported

ceStateExtGlobalStandbyStatusNotifEnable

Read-only

ceStateExtGlobalOperNotifEnable

Read-only

ceStateExtStandbySwitchover

Supported

ceStateExtStandbyStatusChange

Not Supported

CISCO-FLASH-MIB

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

Table 3-50 lists the tables associated with this MIB.

Table 3-50 CISCO-FLASH-MIB Tables and Descriptions

Name
Description

ciscoFlashDeviceTable

Table of Flash device properties for each initialized Flash device. Each Flash device installed in a system is detected, sized, and initialized when the system image boots up. For removable Flash devices, the device properties are dynamically deleted and recreated as the device is removed and inserted. Note that in this case, the newly inserted device may not be the same as the earlier removed one. The ciscoFlashDeviceInitTime object is available for a management station to determine the time at which a device was initialized, and thereby detect the change of a removable device. A removable device that has not been installed also has an entry in this table. This is to let a management station know about a removable device that has been removed. Since a removed device obviously cannot be sized and initialized, the table entry for such a device has ciscoFlashDeviceSize equal to zero, and the following objects have an indeterminate value: ciscoFlashDeviceMinPartitionSize, ciscoFlashDeviceMaxPartitions, ciscoFlashDevicePartitions, and ciscoFlashDeviceChipCount. ciscoFlashDeviceRemovable is true to indicate it is removable.

ciscoFlashChipTable

Table of Flash device chip properties for each initialized Flash device. This table is meant primarily for aiding error diagnosis.

ciscoFlashPartitionTable

Table of flash device partition properties for each initialized flash partition. Whenever there is no explicit partitioning done, a single partition spanning the entire device is assumed to exist. Therefore, there is always at least one partition on a device.

ciscoFlashFileTable

Entry in the table of Flash file properties for each initialized Flash partition. Each entry represents a file and gives details about the file. An entry is indexed using the device number, partition number within the device, and file number within the partition.

ciscoFlashFileByTypeTable

Table of information for files on the manageable flash devices sorted by File Types.

ciscoFlashCopyTable

Table of Flash copy operation entries. Each entry represents a Flash copy operation (to or from Flash) that has been initiated.

ciscoFlashPartitioningTable

Table of Flash partitioning operation entries. Each entry represents a Flash partitioning operation that has been initiated.

ciscoFlashMiscOpTable

Table of misc Flash operation entries. Each entry represents a Flash operation that has been initiated.

MIB Constraints

Table 3-51 lists the constraints that the Cisco ASR 9000 Series router places on the objects in CISCO-FLASH-MIB.

 

Table 3-51 CISCO-FLASH-MIB Constraints

MIB Object
Notes

ciscoFlashCfgDevInsNotifEnable

Not supported

ciscoFlashCfgDevRemNotifEnable

Not supported

miscOpTable

Verify and erase operations not supported

ciscoFlashPartitioningTable

Not supported

ciscoFlashDeviceInitTime

Not supported

ciscoFlashPhyEntIndex

Not supported

ciscoFlashPartitioningCommand

Not supported

ciscoFlashPartitioningDestinationName

Not supported

ciscoFlashPartitioningPartitionCount

Not supported

ciscoFlashPartitioningPartitionSizes

Not supported

ciscoFlashPartitioningNotifyOnCompletion

Not supported

ciscoFlashPartitioningEntryStatus

Not supported

ciscoFlashDeviceSize

Supported, read-only

ciscoFlashDeviceMinPartitionSize

Supported, read-only

ciscoFlashPartitionSize

Supported, read-only

ciscoFlashPartitionFreeSpace

Supported, read-only

ciscoFlashCfgDevInsNotifEnable

Supported, read-only

ciscoFlashCfgDevRemNotifEnable

Supported, read-only

ciscoFlashDeviceCard

Object is deprecated

ciscoFlashDeviceName

Object is deprecated

ciscoFlashDeviceRemovable

Supported, read-only

ciscoFlashDeviceNameExtended

Supported, read-only

CISCO-FLOW-CLONE-MIB

This MIB module defines objects that manage flow cloning feature. A flow cloning can be described as a hardware or software entity, that is responsible to clone (or duplicate) flows to the specified destination port in the device. These cloned packets will be sent to an external device for a more fine-grained analysis of the flows. A typical application of this MIB module will facilitate cloning media flows. However, by no means does the definition of this MIB module prevents other applications from using it.

MIB Tables

Table 3-52 lists the tables in CISCO-FLOW-CLONE-MIB:

 

Table 3-52 CISCO-FLOW-CLONE-MIB Tables

MIB Table
Description

cfcCloneProfileTable

This table lists the clone profiles contained by the device.

cfcFlowIpTable

This table lists the IP traffic flows that are cloned by corresponding clone profile supported by the device. This table has an expansion dependent relationship on the cfcCloneProfileTable, containing zero or more rows for each clone profile.

cfcFlowStatsTable

This table contains data relating to the collection of statistics for the flows cloned by the corresponding clone profiles supported by the device. This table has a sparse dependent relationship on the flow tables, containing a row for each row in the flow table (cfcFlowIpTable in case of IP flows) for which the device is actively cloning the packets.

MIB Constraints

Table 3-53 lists the constraints that the Cisco ASR 9000 Series router places on the objects in CISCO-FLOW-CLONE-MIB.

 

Table 3-53 CISCO-FLOW-CLONE-MIB Constraints

MIB Table
Description

cfcCloneProfileTable

 

cfcCloneProfileId

Not-accessible

cfcCloneProfileStatus

Read-create

cfcCloneProfileStorageType

Read-create

cfcCloneProfileName

Read-create

cfcCloneProfileDescription

Read-create

cfcCloneProfileCreateTime

Not-supported

cfcCloneProfileFlowCount

Not-supported

cfcCloneProfileFlowType

Read-create

cfcCloneTargetType

Not-supported

cfcCloneTargetIfIndex

Not-supported

cfcCloneProfileEgressIfType

Read-create

cfcCloneProfileEgressIf

Read-create

cfcFlowIpTable

 

cfcFlowIndex

Not-accessible

cfcFlowIpStatus

Read-create

cfcFlowIpStorageType

Read-create

cfcFlowIpAddrSrcType

Read-create

cfcFlowIpAddrSrc

Read-create

cfcFlowIpAddrDstType

Read-create

cfcFlowIpAddrDst

Read-create

cfcFlowIpCreateTime

Not-supported

cfcFlowStatsTable

 

cfcFlowPkts

Read-only

cfcFlowOctets

Not-supported

CISCO-FLOW-MONITOR-MIB

This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitoring media flows, especially flows carrying video streams. However, by no means does the definition of this MIB module prevents other applications from using it.

MIB Constraints

Table 3-51 lists the constraints on the objects in CISCO-FLOW-MONITOR-MIB.

Table 3-54 CISCO-FLOW-MONITOR-MIB Constraints

MIB Object
Notes

cfmFlowMonitorTable

 

cfmFlowMonitorId

Not-accessible

cfmFlowMonitorDescr

Read-only

cfmFlowMonitorCaps

Read-only

cfmFlowMonitorFlowCount

Read-only

cfmFlowMonitorConditionsProfile

Read-only

cfmFlowMonitorConditions

Read-only

cfmFlowMonitorAlarms

Read-only

cfmFlowMonitorAlarmSeverity

Read-only

cfmFlowMonitorAlarmCriticalCount

Read-only

cfmFlowMonitorAlarmMajorCount

Read-only

cfmFlowMonitorAlarmMinorCount

Not-supported

cfmFlowMonitorAlarmWarningCount

Not-supported

cfmFlowMonitorAlarmInfoCount

Not-supported

cfmFlowTable

 

cfmFlowId

Not-accessible,

cfmFlowDescr

Read-only

cfmFlowNext

Read-only

cfmFlowCreateTime

Read-only

cfmFlowDiscontinuityTime

Not-supported

cfmFlowExpirationTime

Read-only

cfmFlowDirection

Read-only

cfmFlowAdminStatus

Read-write

cfmFlowOperStatus

Not-supported

cfmFlowIngressType

Read-only

cfmFlowIngress

Read-only

cfmFlowEgressType

Not-supported

cfmFlowEgress

Not-supported

cfmFlowL2VlanTable

 

cfmFlowL2VlanNext

Not-supported

cfmFlowL2VlanId

Not-supported

cfmFlowL2VlanCos

Not-supported

cfmFlowIpTable

 

cfmFlowIpNext

Read-only

cfmFlowIpAddrType

Read-only

cfmFlowIpAddrSrc

Read-only

cfmFlowIpAddrDst

Read-only

cfmFlowIpValid

Read-only

cfmFlowIpTrafficClass

Not-supported

cfmFlowIpHopLimit

Read-only

cfmFlowUdpTable

 

cfmFlowUdpNext

Read-only

cfmFlowUdpPortSrc

Read-only

cfmFlowUdpPortDst

Read-only

cfmFlowTcpTable

 

cfmFlowTcpNext

Not-supported

cfmFlowTcpPortSrc

Not-supported

cfmFlowTcpPortDst

Not-supported

cfmFlowRtpTable

 

cfmFlowRtpNext

Not-supported

cfmFlowRtpVersion

Not-supported

cfmFlowRtpSsrc

Not-supported

cfmFlowRtpPayloadType

Not-supported

cfmFlowMetricsTable

 

cfmFlowMetricsCollected

Read-only

cfmFlowMetricsIntervalTime

Read-only

cfmFlowMetricsMaxIntervals

Read-only

cfmFlowMetricsElapsedTime

Not-supported

cfmFlowMetricsIntervals

Read-only

cfmFlowMetricsInvalidIntervals

Read-only

cfmFlowMetricsConditionsProfile

Read-only

cfmFlowMetricsConditions

Read-only

cfmFlowMetricsAlarms

Not-supported

cfmFlowMetricsAlarmSeverity

Not-supported

cfmFlowMetricsPkts

Read-only

cfmFlowMetricsOctets

Read-only

cfmFlowMetricsBitRateUnits

Read-only

cfmFlowMetricsBitRate

Read-only

cfmFlowMetricsPktRate

Read-only

cfmFlowMetricsIntTable

 

cfmFlowMetricsIntNumber

Not-accessible

cfmFlowMetricsIntValid

Read-only

cfmFlowMetricsIntTime

Read-only

cfmFlowMetricsIntConditions

Read-only

cfmFlowMetricsIntAlarms

Read-only

cfmFlowMetricsIntAlarmSeverity

Read-only

cfmFlowMetricsIntPkts

Read-only

cfmFlowMetricsIntOctets

Read-only

cfmFlowMetricsIntBitRateUnits

Read-only

cfmFlowMetricsIntBitRate

Read-only

cfmFlowMetricsIntPktRate

Read-only

cfmConditionTable

 

cfmConditionProfile

Not-accessible

cfmConditionId

Not-accessible

cfmConditionDescr

Read-only

cfmConditionMonitoredElement

Read-only

cfmConditionType

Read-only

cfmConditionThreshRiseScale

Read-only

cfmConditionThreshRisePrecision

Read-only

cfmConditionThreshRise

Read-only

cfmConditionThreshFallScale

Read-only

cfmConditionThreshFallPrecision

Read-only

cfmConditionThreshFall

Read-only

cfmConditionSampleType

Not-supported

cfmConditionSampleWindow

Not-supported

cfmConditionAlarm

Read-only

cfmConditionAlarmActions

Read-only

cfmConditionAlarmSeverity

Read-only

cfmConditionAlarmGroup

Not-supported

cfmAlarmGroupTable

 

cfmAlarmGroupId

Not-accessible

cfmAlarmGroupDescr

Read-only

cfmAlarmGroupConditionsProfile

Read-only

cfmAlarmGroupConditionId

Read-only

cfmAlarmGroupFlowSet

Read-only

cfmAlarmGroupFlowCount

Read-only

cfmAlarmGroupThresholdUnits

Read-only

cfmAlarmGroupThreshold

Read-only

cfmAlarmGroupRaised

Read-only

cfmAlarmGroupCurrentCount

Read-only

cfmAlarmGroupFlowTable

 

cfmAlarmGroupFlowSetId

Not-accessible

cfmAlarmGroupFlowMonitorId

Not-accessible

cfmAlarmGroupFlowId

Read-only

cfmAlarmHistorySize

Read-write

cfmAlarmHistoryLastId

Read-only

cfmAlarmHistoryTable

 

cfmAlarmHistoryId

Read-only

cfmAlarmHistoryType

Read-only

cfmAlarmHistoryEntity

Read-only

cfmAlarmHistoryConditionsProfile

Read-only

cfmAlarmHistoryConditionId

Read-only

cfmAlarmHistorySeverity

Read-only

cfmAlarmHistoryTime

Read-only

cfmNotifyEnable

Read-write

CISCO-FRAME-RELAY-MIB

The CISCO-FRAME-RELAY-MIB provides Frame Relay specific information that are either excluded by RFC 1315 (FR DTE MIB) or specific to Cisco products.

Table 3-55 lists the tables associated with this MIB.

Table 3-55 CISCO-FRAME-RELAY Tables and Descriptions

Name
Description

cfrLmiTable

Table of Frame Relay LMI information that are either supplemental to the frDlcmiTable of RFC 1315 or specific to Cisco's implementation.

cfrCircuitTable

Table of descriptive and statistics information that are generic to Frame Relay virtual circuits.

cfrExtCircuitTable

Table of Cisco implementation specific FR circuit information. This is a Cisco extension for the frCircuitTable of RFC 1315.

cfrMapTable

Table of protocols and addresses mapping information of FR virtual circuit.

cfrSvcTable

Table of FR SVC specific, descriptive and statistics information.

cfrElmiTable

Table of Cisco Frame Relay ELMI information that is specific to Cisco implementation.

cfrElmiNeighborTable

Table of Cisco Frame Relay Neighbor ELMI information that is specific to Cisco implementation.

cfrFragTable

Table of Frame Relay Fragmentation information. These are specific to Cisco implementation.

cfrConnectionTable

Table of Frame Relay/Frame Relay and Frame Relay/ATM Network/Service Interworking connection information. These are specific to Cisco implementation.

CISCO-FTP-CLIENT-MIB

The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management. This MIB has no known constraints and all objects are implemented as defined in the MIB.

Table 3-56 lists the tables associated with this MIB.

Table 3-56 CISCO-FTP-CLIENT-MIB Tables and Descriptions

Name
Description

cfcRequestTable

Table of FTP client requests

CISCO-HSRP-EXT-MIB

The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB, which defines the Cisco proprietary Hot Standby Routing Protocol (HSRP), defined in RFC 2281. The extensions cover assigning of secondary HSRP ip addresses and modifying priority of an HSRP Group by tracking the operational status of interfaces.

Table 3-57 lists the tables associated with this MIB.

 

Table 3-57 CISCO-HSRP-EXT-MIB Tables and Descriptions

Name
Description

cHsrpExtIfTrackedTable

Table containing information about tracked interfaces per HSRP group

cHsrpExtSecAddrTable

Table containing information about secondary HSRP IP Addresses per interface and group

cHsrpExtIfTable

HSRP-specific configurations for each physical interface

MIB Constraints

Table 3-58 lists the constraints on the objects in CISCO-HSRP-EXT-MIB.

Table 3-58 CISCO-HSRP-EXT-MIB Constraints

MIB Object
Notes

cHsrpExtIfTrackedPriority

Not supported

cHsrpExtIfTrackedRowStatus

Not supported

cHsrpExtSecAddrRowStatus

Not supported

cHsrpExtIfUseBIA

Not supported

cHsrpExtIfRowStatus

Not supported

CISCO-HSRP-MIB

The CISCO-HSRP-MIB provides a means to monitor and configure the Cisco IOS Proprietary Hot Standby Router Protocol (HSRP). Cisco HSRP protocol is defined in RFC 2281.

Table 3-59 lists the tables associated with this MIB.

 

Table 3-59 CISCO-HSRP-MIB Tables and Descriptions

Name
Description

cHsrpGrpTable

Table containing information on each HSRP group for each interface

MIB Constraints

Table 3-60 lists the constraints on the objects in CISCO-HSRP-MIB.

Table 3-60 CISCO-HSRP-MIB Constraints

MIB Object
Notes

cHsrpConfigTimeout

Not supported

cHsrpGrpAuth

Not supported

cHsrpGrpPriority

Not supported

cHsrpGrpPreempt

Not supported

cHsrpGrpPreemptDelay

Not supported

cHsrpGrpConfiguredHelloTime

Not supported

cHsrpGrpConfiguredHoldTime

Not supported

cHsrpGrpVirtualIpAddr

Not supported

cHsrpGrpEntryRowStatus

Not supported

CISCO-IETF-BFD-MIB

The CISCO-IETF-BFD-MIB contains objects to manage Bidirectional Forwarding Detection(BFD) Protocol. BFD is a protocol to detect faults in the bidirectional path between two forwarding engines, including interfaces, and data link(s) with very low latency. This protocol operates independently of media, data protocols, and routing protocols.

MIB Tables

Table 3-61 lists the tables in CISCO-IETF-BFD-MIB:

 

Table 3-61 CISCO-IETF-BFD-MIB Tables

MIB Table
Description

ciscoBfdSessTable

Describes the BFD sessions.

ciscoBfdSessPerfTable

Specifies BFD Session performance counters.

ciscoBfdSessMapTable

Maps the complex indexing of the BFD sessions to the flat CiscoBfdSessIndexTC defined in the ciscoBfdSessTable.

ciscoBfdSessDiscMapTable

Maps a local discriminator value to the associated CiscoBfdSessIndexTC attribute of BFD session defined in the ciscoBfdSessTable.

ciscoBfdSessIpMapTable

Maps the ciscoBfdSessInterface, ciscoBfdSessAddrType, and ciscoBbfdSessAddr to an associated CiscoBfdSessIndexTC attribute of BFD session defined in the ciscoBfdSessTable. This table contains two IP type BFD sessions:

  • singleHop(1)
  • multiHop(2).

MIB Constraints

Table 3-62 lists the constraints on objects in the CISCO-IETF-BFD-MIB.

Table 3-62 CISCO-IETF-BFD-MIB Constraints

MIB Object
Notes
ciscoBfdSessMapTable

Not supported

ciscoBfdSessNotificationsEnable

Not supported

ciscoBfdAdminStatus

Not supported

ciscoBfdSessAddrType

Not supported

ciscoBfdSessAddr

Not supported

ciscoBfdSessUdpPort

Not supported

ciscoBfdSessDemandModeDesiredFlag

Not supported

ciscoBfdSessEchoFuncModeDesiredFlag

Not supported

ciscoBfdSessControlPlanIndepFlag

Not supported

ciscoBfdSessDesiredMinTxInterval

Not supported

ciscoBfdSessReqMinRxInterval

Not supported

ciscoBfdSessReqMinEchoRxInterval

Not supported

ciscoBfdSessDetectMult

Not supported

ciscoBfdSessStorType

Not supported

ciscoBfdSessRowStatus

Not supported

ciscoBfdSessAuthPresFlag

Not supported

ciscoBfdSessAuthenticationType

Not supported

CISCO-IETF-FRR-MIB

The CISCO-IETF-FRR-MIB contains managed object definitions for MPLS Fast Reroute (FRR) as defined in:Pan, P., Gan, D., Swallow, G., Vasseur, J.Ph., Cooper, D., Atlas, A., Jork, M., Fast Reroute Techniques in RSVP-TE, draft-ietf-mpls-rsvp-lsp-fastreroute- 00.txt, January 2002.

Table 3-63 lists the tables associated with this MIB.

 

Table 3-63 CISCO-IETF-FRR-MIB Tables and Descriptions

Name
Description

cmplsFrrConstTable

This table shows detour setup constraints

cmplsFrrLogTable

Fast reroute log table records fast reroute events such as protected links going up or down or the FRR feature starting.

mplsFrrOne2OnePlrTable

This table shows the lists of PLRs that initiated detour LSPs, which affect this node.

mplsFrrDetourTable

This table shows all detour LSPs together with their characteristics.

cmplsFrrFacRouteDBTable

mplsFrrFacRouteDBTable provides information about the fast reroute database. Each entry belongs to an interface, protecting backup tunnel and protected tunnel. MPLS interfaces defined on this node are protected by backup tunnels and are indexed by mplsFrrFacRouteProtectedIndex. Backup tunnels defined to protect the tunnels traversing an interface, and are indexed by mplsFrrFacRouteProtectingTunIndex. Note that the tunnel instance index is not required, because it is implied to be 0, which indicates the tunnel head interface for the protecting tunnel. The protecting tunnel is defined to exist on the PLR in the FRR specification. Protected tunnels are the LSPs that traverse the protected link. These LSPs are uniquely identified by:

  • mplsFrrFacRouteProtectedTunIndex
  • mplsFrrFacRouteProtectedTunInstance,
  • mplsFrrFacRouteProtectedTunIngressLSRId
  • mplsFrrFacRouteProtectedTunEgressLSRId

MIB Constraints

Table 3-64 lists the constraints on objects in the CISCO-IETF-FRR-MIB.

 

Table 3-64 CISCO-IETF-FRR-MIB Constraints

MIB Object
Notes
mplsFrrOne2OnePlrGroup

Not supported

mplsFrrOne2OnePLRDetourGroup

Not supported

cmplsFrrConstProtectionMethod

Not supported

cmplsFrrConstSetupPrio

Not supported

cmplsFrrConstHoldingPrio

Not supported

cmplsFrrConstInclAnyAffinity

Not supported

cmplsFrrConstInclAllAffinity

Not supported

cmplsFrrConstExclAllAffinity

Not supported

cmplsFrrConstHopLimit

Not supported

cmplsFrrConstBandwidth

Not supported

cmplsFrrConstRowStatus

Not supported

cmplsFrrNotifsEnabled

Not supported

cmplsFrrLogTableMaxEntries

Not supported

cmplsFrrNotifMaxRate

Not supported

cmplsFrrFacRouteProtectingTunProtectionType

Not supported

CISCO-IETF-MPLS-TE-P2MP-STD-MIB

This MIB module contains managed object definitions for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) defined in: 1. Signaling Requirements for Point-to-Multipoint Traffic-Engineered MPLS Label Switched Paths (LSPs), S. Yasukawa, RFC 4461, April 2006. 2. Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to-Multipoint TE Label Switched Paths (LSPs), Aggarwal, R., Papadimitriou, D., and Yasukawa, S., RFC 4875, May 2007.

Table 3-65 lists the tables associated with this MIB.

MIB Objects

Table 3-65 CISCO-IETF-MPLS-TE-P2MP-STD-MIB Tables and Description

Name
Description

cmplsTeP2mpTunnelTable

The cmplsTeP2mpTunnelTable allows new P2MP MPLS tunnels to be created between an LSR and one or more remote end-points, and existing P2MP tunnels to be reconfigured or removed. This table sparse augments mplsTunnelTable in MPLS-TE-STD-MIB such that entries in that table can be flagged as point-to-multipoint, and can be configured and monitored appropriately.

cmplsTeP2mpTunnelDestTable

The cmplsTeP2mpTunnelDestTable allows new destinations of P2MP MPLS tunnels to be added to and removed from P2MP tunnels.

cmplsTeP2mpTunnelBranchPerfTable

This table provides per-tunnel branch MPLS performance information. This table is not valid for switching types other than packet.

MIB Constraints

Table 3-64 lists the constraints on objects in the CISCO-IETF-MPLS-TE-P2MP-STD-MIB.

Table 3-66 CISCO-IETF-MPLS-TE-P2MP-STD-MIB Constraints

MIB Object
Notes

cmplsTeP2mpTunnelP2mpIntegrity

Read-only

cmplsTeP2mpTunnelBranchRole

Read-only

cmplsTeP2mpTunnelRowStatus

Read-only

cmplsTeP2mpTunnelStorageType

Read-only

cmplsTeP2mpTunnelDestHopTableIndex

Read-only

cmplsTeP2mpTunnelDestPathInUse

Read-only

cmplsTeP2mpTunnelDestAdminStatus

Read-only

cmplsTeP2mpTunnelDestRowStatus

Read-only

cmplsTeP2mpTunnelDestStorageType

Read-only

cmplsTeP2mpTunnelNotificationEnable

Read-only

CISCO-IETF-IPMROUTE-MIB

The CISCO-IETF-IPMROUTE-MIB is an address family-independent MIB module to manage IP Multicast routing. It is independent of the specific multicast routing protocol. This MIB module is based on RFC 2932 with additional MIB objects to provide address family-independent functionality.

This MIB module contains two scalars and five tables.The tables are:

  • The IP Multicast Route Table containing multicast routing information for IP datagrams sent by a source to the IP multicast groups known to a router.
  • The IP Multicast Routing Next Hop Table containing information on the next hops for the routing IP multicast datagrams.
  • The IP Multicast Routing Interface Table containing multicast routing information specific to interfaces.
  • The IP Multicast Scope Boundary Table containing the boundaries configured for multicast scopes.
  • The IP Multicast Scope Name Table containing names of multicast scope.

Table 3-67 lists the tables associated with this MIB.

Table 3-67 CISCO-IETF-IPMROUTE-MIB Tables and Descriptions

Name
Description

cIpMRouteTable

(conceptual) Table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router.

cIpMRouteNextHopTable

(conceptual) Table containing information on the next- hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next-hops on outgoing interfaces for particular sources sending to a particular multicast group address.

cIpMRouteInterfaceTable

(conceptual) Table containing multicast routing information specific to interfaces.

cIpMRouteBoundaryTable

(conceptual) Table listing the scoped multicast address boundaries of the router.

cIpMRouteScopeNameTable

(conceptual) Table listing the multicast scope names. This table is not supported.

MIB Constraints

Table 3-68 lists the constraints on objects in the CISCO-IETF-IPMROUTE-MIB.

Table 3-68 CISCO-IETF-IPMROUTE-MIB Constraints

MIB Object
Notes
cIpMRouteScopeNameTable

This table is not supported.

cIpMRouteBoundaryStatus

Not supported

cIpMRouteScopeNameString

Not supported

cIpMRouteScopeNameDefault

Not supported

cIpMRouteScopeNameStatus

Not supported

cIpMRouteBoundaryNameString

Not supported

cIpMRouteEnable

Not supported

cIpMRouteInterfaceTtl

Not supported

cIpMRouteInterfaceRateLimit

Not supported

CISCO-IETF-MSDP-MIB

The CISCO-IETF-MSDP-MIB is an experimental MIB module for MSDP Management and Monitoring. Version draft-ietf-mboned-msdp-mib-01.txt is ciscoized.

Table 3-69 lists the tables associated with this MIB.

 

Table 3-69 CISCO-IETF-MSDP-MIB Tables and Descriptions

Name
Description

cMsdpRequestsTable

(conceptual) Table listing group ranges and MSDP peers used when deciding where to send an SA Request message when required. If SA Requests are not enabled, this table may be empty. To choose a peer to whom to send an SA Request for a given group G, the subset of entries in this table whose (cMsdpRequestsPeerType, cMsdpRequestsPeer) tuple represents a peer whose cMsdpPeerState is established are examined. The set is further reduced by examining only those entries for which cMsdpPeerRequestsGroupAddressType equals the address type of G, and the entries with the highest value of cMsdpRequestsGroupPrefix are considered, where the group G falls within the range described by the combination of cMsdpRequestsGroup and cMsdpRequestsGroupPrefix. (This sequence is commonly known as a 'longest-match' lookup.) Finally, if multiple entries remain, the entry with the lowest value of cMsdpRequestsPriority is chosen. The SA Request message is sent to the peer described by this row.

cMsdpPeerTable

(conceptual) Table listing the MSDP speaker's peers.

cMsdpSACacheTable

(conceptual) Table listing the MSDP SA advertisements currently in the MSDP speaker's cache.

cMsdpMeshGroupTable

(conceptual) Table listing MSDP Mesh Group configuration.

MIB Constraints

Table 3-70 lists the constraints on objects in the CISCO-IETF-MSDP-MIB.

Table 3-70 CISCO-IETF-MSDP-MIB Constraints

MIB Object
Notes

cMsdpEnabled

Not supported

cMsdpRPAddress

Not supported

cMsdpCacheLifetime

Not supported

cMsdpSACacheStatus

Not supported

cMsdpMeshGroupStatus

Not supported

cMsdpPeerLocalAddress

Not supported

cMsdpPeerConnectRetryInterval

Not supported

cMsdpPeerHoldTimeConfigured

Not supported

cMsdpPeerKeepAliveConfigured

Not supported

cMsdpPeerStatus

Not supported

cMsdpPeerDataTtl

Not supported

cMsdpPeerEncapsulationType

Not supported

CISCO-IETF-PIM-MIB

The CISCO-IETF-PIM-MIB is based on RFC 2934 with additional MIB objects added to make it address family independent MIB. This Cisco MIB was created because of non availability of RFC or an Internet Draft, which can provide address family independent MIB for management of PIM routers. This MIB may later be deprecated with a stable RFC or an Internet Draft.

Table 3-71 lists the tables associated with this MIB.

 

Table 3-71 CISCO-IETF-PIM-MIB Tables and Descriptions

Name
Description

cPimIfTable

(conceptual) Table listing the router's PIM interfaces. Along with PIM IGMP or MLD is enabled on all interfaces listed in this table

cPimNbrTable

(conceptual) Table listing the router's PIM neighbors

cPimInetMRouteTable

(conceptual) Table listing PIM-specific information on a subset of the rows of the cIpMRouteTable defined in the IP Multicast MIB

cPimInetMRouteNextHopTable

(conceptual) Table listing PIM-specific information on a subset of the rows of the cIpMRouteNextHopTable defined in the IP Multicast MIB. This table is not supported.

cPimRPMapTable

(conceptual) Table listing PIM information for candidate RPs for IP multicast groups. When the local router is the BSR, this information is obtained from received Candidate-RP-Advertisements. When the local router is not the BSR, this information is obtained from received RP-Set messages. This table is not supported.

cPimCRPTable

(conceptual) Table listing the IP multicast groups for which the local router is to advertise itself as a Candidate-RP when the value of cPimComponentCRPHoldTime is non-zero. If this table is empty, then the local router advertises itself as a Candidate-RP for all groups (providing the value of cPimComponentCRPHoldTime is non- zero). This table is not supported.

cPimComponentTable

(conceptual) Table containing objects specific to a PIM domain. One row exists for each domain to which the router is connected. A PIM-SM domain is defined as an area of the network over which Bootstrap messages are forwarded. Typically, a PIM-SM router is a member of exactly one domain. This table also supports routers that may form a border between two PIM-SM domains and do not forward Bootstrap messages between them. This table is not supported.

MIB Constraints

Table 3-72 lists the constraints on objects in the CISCO-IETF-PIM-MIB.

 

Table 3-72 CISCO-IETF-PIM-MIB Constraints

MIB Object
Notes
cPimInetMRouteNextHopTable

This table is not supported.

cPimRPMapTable

This table is not supported.

cPimCRPTable

This table is not supported.

cPimComponentTable

This table is not supported.

CISCO-IETF-PIM-EXT-MIB

The CISCO-IETF-PIM-EXT-MIB extends PIM management capabilities defined in CISCO-IETF-PIM-MIB.

Table 3-73 lists the tables associated with this MIB.

 

Table 3-73 CISCO-IETF-PIM-EXT-MIB Tables and Descriptions

Name
Description

cpimExtIfTable

(conceptual) Table listing the router's PIM interfaces. IGMP and PIM are enabled on all interfaces listed in this table. This table is augmented to cPimIfTable. This table is not supported.

cpimExtNbrTable

(conceptual) Table listing the router's PIM neighbors. This table is augmented to cPimNbrTable. This table is not supported.

cpimExtNbrSecAddressTable

(conceptual) Table listing the Secondary InetAddresses advertised by each PIM neighbor (on a subset of the rows of the cPimNbrTable defined in CISCO-IETF-PIM-MIB)

cpimExtMRouteTable

(conceptual) Table listing PIM-specific information on a subset of the rows of the cIpMRouteTable defined in the IP Multicast MIB. This table is augmented to cPimInetMRouteTable. This table is not supported.

cpimExtMRouteNextHopTable

(conceptual) Table listing PIM-specific information on a subset of the rows of the cIpMRouteNextHopTable defined in the IP Multicast Routing Table MIB-IPMROUTE-MIB. This table is augmented to cPimInetMRouteNextHopTable. This table is not supported.

cpimExtBidirDFTable

(conceptual) Table listing the Per-RP DF10 Election state for each interface for all the RPs in Bidir mode.

cpimExtRPSetTable

(conceptual) Table listing PIM information for available RPs for IP multicast groups. An entry is learnt from one of {static, bsr, embedded} methods, as defined by the cpimExtRPSetType object. When the cpimExtRPSetType object has a value {static}, the entry is a mapping provided by user-configuration. A value of {embedded} indicates that the RP-address is embedded in the Group-address. When the value is {bsr}, this entry is obtained from received Candidate-RP-Advertisements when the local router is the BSR, and is obtained from received RP-Set messages when the local router is not the BSR.

cpimExtCRPTable

(conceptual) Table listing the IP multicast groups for which the local router is to advertise itself as a Candidate-RP when the value of cPimComponentCRPHoldTime is non-zero. If this table is empty, the local router advertises itself as a Candidate-RP for all groups (providing the value of cPimComponentCRPHoldTime is non- zero). This table is not supported.

10.DF = designated forwarder

MIB Constraints

Table 3-74 lists the constraints on objects in the CISCO-IETF-PIM-EXT-MIB.

 

Table 3-74 CISCO-IETF-PIM-EXT-MIB Constraints

MIB Object
Notes
cpimExtIfTable

Not supported

cpimExtNbrTable

Not supported

cpimExtMRouteTable

Not supported

cpimExtMRouteNextHopTable

Not supported

cpimExtCRPTable

Not supported

cpimExtIfTrigHelloInterval

Not supported

cpimExtIfHelloHoldtime

Not supported

cpimExtIfLanPruneDelay

Not supported

cpimExtIfPropagationDelay

Not supported

cpimExtIfOverrideInterval

Not supported

cpimExtIfGenerationID

Not supported

cpimExtIfJoinPruneHoldtime

Not supported

cpimExtIfGraftRetryInterval

Not supported

cpimExtIfMaxGraftRetries

Not supported

cpimExtIfSRTTLThreshold

Not supported

cpimExtIfDRPriority

Not supported

cpimExtIfBSRBorder

Not supported

cpimExtSourceLifetime

Not supported

cpimExtStateRefreshInterval

Not supported

cpimExtStateRefreshLimitInterval

Not supported

cpimExtStateRefreshTimeToLive

Not supported

cpimExtInterfaceStateChangeNotifEnabled

Not supported

cpimExtRPMappingChangeNotifEnabled

Not supported

cpimExtCRPBidir

Not supported

CISCO-IETF-PW-ENET-MIB

The CISCO-IETF-PW-ENET-MIB describes a model for managing Ethernet point-to-point pseudo wire services over a Packet Switched Network (PSN).

Table 3-75 lists the tables associated with this MIB.

 

Table 3-75 CISCO-IETF-PW-ENET-MIB Tables and Descriptions

Name
Description

cpwVcEnetTable

This table contains the index to the Ethernet tables associated with this ETH VC, the VLAN configuration and VLAN mode.

cpwVcEnetMplsPriMappingTable

This table may be used for MPLS PSNs if there is a need to hold multiple VC, each with different COS, for the same user service (port + PW VLAN). Such a need may arise if the MPLS network is capable of L-LSP or E-LSP without multiple COS capabilities. Each row is indexed by the cpwVcIndex and indicate the PRI bits on the packet received from the user port (or VPLS virtual port) that are classified to this VC. Note that the EXP bit value of the VC is configured in the CISCO-IETF-PW-MPLS-MIB.

cpwVcEnetStatsTable

This table contains statistical counters specific for Ethernet PW.

MIB Constraints

Table 3-77 lists the constraints on objects in the CISCO-IETF-PW-ENET-MIB.

Table 3-76 CISCO-IETF-PW-ENET-MIB Constraints

MIB Object
Notes
cpwVcEnetTable

 

cpwVcEnetPwVlan

Read-only

cpwVcEnetVlanMode

Read-only

cpwVcEnetPortVlan

Read-only

cpwVcEnetPortIfIndex

Read-only

cpwVcEnetVcIfIndex

Read-only

cpwVcEnetRowStatus

Read-only

cpwVcEnetStorageType

Read-only

cpwVcEnetStatsTable

 

cpwVcEnetStatsIllegalVlan

Not Implemented

cpwVcEnetStatsIllegalLength

Not Implemented

CISCO-IETF-PW-MIB

The CISCO-IETF-PW-MIB contains managed object definitions for pseudo wire operations. The indexes of CISCO-IETF-PW-MIB are also used to index the PSN-specific tables and the VC-specific tables. This MIB enables you to use the underlying PSN.

Table 3-77 lists the tables associated with this MIB.

 

Table 3-77 CISCO-IETF-PW-MIB Tables and Descriptions

Name
Description

cpwVcTable

This table specifies information for connecting various emulated services to various tunnel type.

cpwVcPerfCurrentTable

This table provides per-VC performance information for the current interval.

cpwVcPerfIntervalTable

This table provides per-VC performance information for each interval.

cpwVcPerfTotalTable

This table provides per-VC Performance information from VC start time.

cpwVcIdMappingTable

This table provides reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.

cpwVcPeerMappingTable

This table provides reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs.

MIB Constraints

Table 3-78 lists the constraints on objects in the CISCO-IETF-PW-MIB.

Table 3-78 CISCO-IETF-PW-MIB Constraints

MIB Object
Notes

cpwVcType

Not supported

cpwVcOwner

Not supported

cpwVcPsnType

Not supported

cpwVcSetUpPriority

Not supported

cpwVcHoldingPriority

Not supported

cpwVcInboundMode

Not supported

cpwVcPeerAddrType

Not supported

cpwVcPeerAddr

Not supported

cpwVcID

Not supported

cpwVcLocalGroupID

Not supported

cpwVcControlWord

Not supported

cpwVcLocalIfMtu

Not supported

cpwVcLocalIfString

Not supported

cpwVcRemoteControlWord

Not supported

cpwVcOutboundVcLabel

Not supported

cpwVcInboundVcLabel

Not supported

cpwVcName

Not supported

cpwVcDescr

Not supported

cpwVcAdminStatus

Not supported

cpwVcRowStatus

Not supported

cpwVcStorageType

Not supported

cpwVcUpDownNotifEnable

Not supported

cpwVcNotifRate

Not supported

CISCO-IETF-PW-FR-MIB

Cisco Pseudo Wire Frame Relay MIB This MIB describes network management objects defined for FRoPW services over a Packet Switched Network (PSN). As described in the IETF Frame Relay over Pseudowire (FRoPW) draft, draft-ietf-pwe3-frame-relay-01.txt, FR VCs and PW can be mapped in 2 modes: One-to-one mapping mode: a FR VC is mapped to a PW. This mode is described by cpwVcFrTable. Many-to-one mapping mode (a.k.a. port mode): multiple FR VCs assigned to a port are mapped to a PW. This mode is addressed by cpwVcFrPortModeTable. In this mode, all data frames are directed to the associated PSN tunnel regardless of DLCI.

Table 3-79 lists the tables associated with this MIB.

MIB Objects

Table 3-79 CISCO-IETF-PW-FR-MIB Tables and Descriptions

Name
Description

cpwVcFrTable

The PW-FR connection table. Each entry in this table represents a FRoPW connection operating in one-to-one mapping mode. This table uses the same index as the generic PW MIB’s VC table. Therefore, each entry in cpwVcFrTable has a mapping entry to the generic PW MIB VC table associated by the PW VC index. An entry is created in this table by the agent for every entry in the generic PW MIB VC table with a VcType of ’frameRelay’.

cpwVcFrPMTable

The PW-FR port mode connection table. Each entry in this table represents a FRoPW connection operating in the port mode. This table uses the same index as the generic PW MIB’s VC table. Therefore, each entry in cpwVcFrTable has a mapping entry to the generic PW MIB VC table associated by the PW VC index. An entry is created in this table by the agent for every entry in the generic PW MIB VC table with a VcType of ’frameRelayPortMode’.

MIB Constraints

Table 3-80 lists the constraints on objects in the CISCO-IETF-PW-FR-MIB.

Table 3-80 CISCO-IETF-PW-FR-MIB Constraints

MIB Object
Notes

cpwVcFrIfIndex

Read-only

cpwVcFrDlci

Read-only

cpwVcFrAdminStatus

Read-only

cpwVcFrRowStatus

Read-only

cpwVcFrStorageType

Read-only

cpwVcFrPMAdminStatus

Not supported

cpwVcFrPMRowStatus

Not supported

cpwVcFrPMStorageType

Not supported

CISCO-IETF-PW-MPLS-MIB

The CISCO-IETF-PW-MPLS-MIB complements the CISCO-IETF-PW-MIB for pseudo wire operation over Multiprotocol Label Switching (MPLS).

Table 3-81 lists the tables associated with this MIB.

 

Table 3-81 CISCO-IETF-PW-MPLS-MIB Tables and Descriptions

Name
Description

cpwVcMplsTable

This table specifies information for VC to be carried over MPLS PSN.

cpwVcMplsOutboundTable

This table associates VCs using MPLS PSN with the outbound MPLS tunnels (that is toward the PSN) or the physical interface in case of VC only.

cpwVcMplsInboundTable

This table associates VCs using MPLS PSN with the inbound MPLS tunnels (that is, for packets coming from the PSN), if such association is desired (mainly for security reasons).

cpwVcMplsNonTeMappingTable

This table maps an inbound/outbound Tunnel to a VC in non-TE applications.

cpwVcMplsTeMappingTable

This table maps an inbound/outbound Tunnel to a VC in MPLS-TE applications.

MIB Constraints

Table 3-82 lists the constraints on objects in the CISCO-IETF-PW-MPLS-MIB.

Table 3-82 CISCO-IETF-PW-MPLS-MIB Constraints

MIB Object
Notes

cpwVcMplsInboundLsrXcIndex

Not supported

cpwVcMplsInboundTunnelIndex

Not supported

cpwVcMplsInboundTunnelInstance

Not supported

cpwVcMplsInboundTunnelLclLSR

Not supported

cpwVcMplsInboundTunnelPeerLSR

Not supported

cpwVcMplsInboundIfIndex

Not supported

cpwVcMplsInboundRowStatus

Not supported

cpwVcMplsInboundStorageType

Not supported

cpwVcMplsOutboundLsrXcIndex

Not supported

cpwVcMplsOutboundTunnelIndex

Not supported

cpwVcMplsOutboundTunnelInstance

Not supported

cpwVcMplsOutboundTunnelLclLSR

Not supported

cpwVcMplsOutboundTunnelPeerLSR

Not supported

cpwVcMplsOutboundIfIndex

Not supported

cpwVcMplsOutboundRowStatus

Not supported

cpwVcMplsOutboundStorageType

Not supported

cpwVcMplsMplsType

Not supported

cpwVcMplsExpBitsMode

Not supported

cpwVcMplsExpBits

Not supported

cpwVcMplsTtl

Not supported

cpwVcMplsLocalLdpID

Not supported

cpwVcMplsLocalLdpEntityID

Not supported

cpwVcMplsStorageType

Not supported

CISCO-IETF-PW-TC-MIB

The CISCO-IETF-PW-TC-MIB provides textual conventions and OBJECT-IDENTITY objects to be used in pseudo wire services.

CISCO-IETF-VPLS-BGP-EXT-MIB

The CISCO-IETF-VPLS-BGP-EXT-MIB contains table objects to implement the underlying Pseudo Wire network and manage object definitions for BGP signalled VPLS.

Table 3-83 lists the tables defined in CISCO-IETF-VPLS-BGP-EXT-MIB.

 

Table 3-83 CISCO-IETF-VPLS-BGP-EXT-MIB Tables

MIB Table
Description
ciVplsBgpExtConfigTable

Contains attributes to configure and monitor BGP-specific parameters for VPLS.

civplsBgpExtRTTable

Contains the list of Route Targets imported or exported by BGP during VPLS auto-discovery.

ciVplsBgpExtVETable

Contains objets to associates VPLS Edge devices to a VPLS.

ciVplsBgpExtPwBindTable

Contains objects to store BGP-specific information for an association between a VPLS and the corresponding Pseudo Wires. A VPLS service can have association with multiple Pseudo Wires.

MIB Constraints

Table 3-84 lists the constraints on objects in the CISCO-IETF-VPLS-BGP-EXT-MIB.

Table 3-84 CISCO-IETF-VPLS-BGP-EXT-MIB Constraints

MIB Object
Notes

ciVplsBgpExtVEName

Not supported

ciVplsBgpExtVEPreference

Not supported

ciVplsBgpExtVERowStatus

Not supported

ciVplsBgpExtVEStorageType

Not supported

ciVplsBgpExtConfigRouteDistinguisher

Not supported

ciVplsBgpExtConfigVERangeSize

Not supported

ciVplsBgpExtRTType

Not supported

ciVplsBgpExtRT

Not supported

ciVplsBgpExtRTStorageType

Not supported

ciVplsBgpExtRTRowStatus

Not supported

CISCO-IETF-VPLS-GENERIC-MIB

The CISCO-IETF-VPLS-GENERIC-MIB contains table objects to store and manage generic managed object definitions for Virtual Private LAN Services (VPLS). This MIB module enables you to use the underlying pseudo wire network.

This MIB is based on the following IETF document: http://tools.ietf.org/html/draft-ietf-l2vpn-vpls-mib-05

MIB Tables

Table 3-85 lists the tables defined in CISCO-IETF-VPLS-GENERIC-MIB:

 

Table 3-85 CISCO-IETF-VPLS-GENERIC-MIB Tables

MIB Table
Description
cvplsConfigTable

Contains information for configuring and monitoring Virtual Private Lan Services(VPLS).

cvplsStatusTable

Contains information for monitoring Virtual Private Lan Services(VPLS).

cvplsPwBindTable

Contains objects to associates VPLS service and the corresponding Pseudo Wires. A VPLS service can have association with multiple Pseudo Wires.

MIB Constraints

Table 3-86 lists the constraints on objects in the CISCO-IETF-VPLS-GENERIC-MIB.

Table 3-86 CISCO-IETF-VPLS-GENERIC-MIB Constraints

MIB Object
Notes

cvplsConfigName

Not supported

cvplsConfigDescr

Not supported

cvplsConfigAdminStatus

Not supported

cvplsConfigMacLearning

Not supported

cvplsConfigDiscardUnknownDest

Not supported

cvplsConfigMacAging

Not supported

cvplsConfigFwdFullHighWatermark

Not supported

cvplsConfigFwdFullLowWatermark

Not supported

cvplsConfigRowStatus

Not supported

cvplsConfigMtu

Not supported

cvplsConfigServiceType

Not supported

cvplsConfigStorageType

Not supported

cvplsStatusNotifEnable

Not supported

cvplsNotificationMaxRate

Not supported

cvplsPwBindConfigType

Not supported

cvplsPwBindType

Not supported

cvplsPwBindRowStatus

Not supported

cvplsPwBindStorageType

Not supported

CISCO-IETF-VPLS-LDP-MIB

The CISCO-IETF-VPLS-LDP-MIB contains table objects that define managed object definitions for LDP signalled Virtual Private LAN Services. This MIB enables the use of any underlying Pseudo Wire network. This MIB is based on the following IETF document.

http://www1.tools.ietf.org/html/draft-nadeau-l2vpn-vpls-mib-03

Table 3-87 lists the tables defined in CISCO-IETF-VPLS-LDP-MIB.

 

Table 3-87 CISCO-IETF-VPLS-LDP-MIB Tables

MIB Table
Description
cvplsLdpConfigTable

Contains attributes to configure and monitor LDP specific parameters for Virtual Private Lan Services(VPLS).

cvplsLdpPwBindTable

Contains attributes to associate a VPLS service and the corresponding Pseudo Wires. A VPLS service can have association with multiple Pseudo Wires.

MIB Constraints

Table 3-88 lists the constraints on objects in the CISCO-IETF-VPLS-LDP-MIB.

Table 3-88 CISCO-IETF-VPLS-LDP-MIB Constraints

MIB Object
Notes

cvplsLdpConfigMacAddrWithdraw

Not supported

cvplsLdpPwBindMacAddressLimit

Not supported

CISCO-IF-EXTENSION-MIB

The CISCO-IF-EXTENSION-MIB contains objects for extending the IF-MIB (RFC2863) to add objects that provide additional information about interfaces that are not available in other MIBS. This MIB replaces the OLD-CISCO-INTERFACES-MIB.

MIB Tables

Table 3-89 lists the tables in CISCO-IF-EXTENSION-MIB:

Table 3-89 CISCO-IF-EXTENSION-MIB Tables

Name
Description

cieIfPacketStatsTable

Displays interface packet statistics that are not listed in IF-MIB(RFC2863). These interfaces are:

  • Ethernet
  • FastEthernet
  • ATM
  • BRI
  • Sonet
  • GigabitEthernet

cieIfInterfaceTable

Provides extended information about interface properties that are not available in IF-MIB (RFC 2863).

cieIfStatusListTable

Provides information such as ifIndex, interface operational mode, and interface operational cause for all the interfaces in modules. The table contains individual entries for all the 64 interfaces in a module.

cieIfDot1qCustomEtherTypeTable

Displays the interfaces that support the 802.1q custom Ethertype feature.

cieIfUtilTable

Displays the interface utilization rates for inbound and outbound traffic on an interface. The cieIfInOctetRate object and cieIfOutOctetRate object are used for reporting number of bytes of data transferred from/to an interface in a given time period.

cieIfDot1dBaseMappingTable

Contains the mappings between ifIndex of an interface to its corresponding dot1dBasePort value.

cieIfNameMappingTable

Provides mapping information between ifName and ifIndex. This table contains an entry for each valid ifName available in the system.

MIB Constraints

Table 3-90 lists the constraints on objects in the CISCO-IF-EXTENSION-MIB.

Table 3-90 CISCO-IF-EXTENSION-MIB Constraints

MIB Object
Notes

cieSystemMtu

Not supported

cieIfDot1qCustomAdminEtherType

Not supported

cieLinkUpDownEnable

Not supported

cieStandardLinkUpDownVarbinds

Not supported

cieIfDhcpMode

Not supported

cieIfMtu

Not supported

cieIfAutoNegotiate

Not supported

cieIfKeepAliveEnabled

Not supported

cieIfLastInTime 

Not supported

cieIfLastOutTime 

Not supported

cieIfLastOutHangTime

Not supported

cieIfPacketDiscontinuityTime

Not supported

cieIfStatusListIndex

Not supported

cieInterfaceOwnershipBitmap

Not supported

cieIfInterfaceDiscontinuityTime

Not supported

CieIfVlStatsEntry

Not supported

cieIfNoDropVlInPkts

Not supported

cieIfNoDropVlInOctets

Not supported

cieIfNoDropVlOutPkts

Not supported

cieIfNoDropVlOutOctets

Not supported

cieIfDropVlInPkts

Not supported

cieIfDropVlInOctets 

Not supported

cieIfDropVlOutPkts

Not supported

cieIfDropVlOutOctets

Not supported

cieIfIndexPersistence

Not supported

cieIfIndexPersistenceEnabled

Not supported

cieIfIndexPersistenceControl

Not supported

cieDelayedLinkUpDownNotifEnable

Not supported

cieDelayedLinkUpDownNotifDelay

Not supported

cieIfIndexGlobalPersistence

Not supported

cieLinkUpDownConfig

Not supported

cieIfSpeedReceive

Not supported

cieIfHighSpeedReceive

Not supported

cieIfOwner

Not supported

cieIfSharedConfig

Not supported

cieIfSpeedGroupConfig

Not supported

cieIfTransceiverFrequencyConfig

Not supported

cieIfFillPatternConfig

Not supported

cieIfIgnoreBitErrorsConfig

Not supported

cieIfIgnoreInterruptThresholdConfig

Not supported

CISCO-IP-CBR-METRICS-MIB

This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CBR traffic flow consists of a stream of IP datagrams sent from one application to another with a constant packet rate or bit rate.

Table 3-91 lists the tables associated with this MIB.

MIB Objects

Table 3-91 CISCO-IP-CBR-METRICS-MIB Tables and Descriptions

Name
Description

cfmIpCbrMetricsTable

This table contains aggregate data maintained by a flow monitor for traffic flows for which it is computing IP CBR metrics. This table has a sparse dependent relationship on the cfmFlowMetricsTable (defined by the CISCO-FLOW-MONITOR-MIB), containing a row for each row in the cfmFlowMetricsTable having a corresponding instance of cfmFlowMetricsCollected with the ’ipCbr’ bit set to one.

cfmIpCbrMetricsIntTable

This table contains historic IP CBR metrics for the traffic flows monitored by each of the flow monitors supported by the device. This table has a sparse dependent relationship on the cfmFlowMetricsIntTable (defined by the CISCO-FLOW-MONITOR-MIB), containing a row for each row in the cfmFlowMetricsIntTable having a corresponding instance of cfmFlowMetricsCollected with the ’ipCbr’ bit set to one.

MIB Constraints

Table 3-99 lists the constraints on objects in the CISCO-IP-CBR-METRICS-MIB.

 

Table 3-92 CISCO-IP-CBR-METRICS-MIB Constraints

MIB Object
Notes

cfmIpCbrMetricsTable

 

cfmIpCbrMetricsCfgRateType

Read-only

cfmIpCbrMetricsCfgBitRate

Read-only

cfmIpCbrMetricsCfgRate

Read-only

cfmIpCbrMetricsCfgMediaPktSize

Not-supported

cfmIpCbrMetricsValid

Read-only

cfmIpCbrMetricsLostPkts

Read-only

cfmIpCbrMetricsMrvScale

Read-only

cfmIpCbrMetricsMrvPrecision

Read-only

cfmIpCbrMetricsMrv

Read-only

cfmIpCbrMetricsIntTable

 

cfmIpCbrMetricsIntValid

Read-only

cfmIpCbrMetricsIntLostPkts

Read-only

cfmIpCbrMetricsIntVbMin

Not-supported

cfmIpCbrMetricsIntVbMax

Not-supported

cfmIpCbrMetricsIntMrUnits

Read-only

cfmIpCbrMetricsIntMr

Read-only

cfmIpCbrMetricsIntDfScale

Read-only

cfmIpCbrMetricsIntDfPrecision

Read-only

cfmIpCbrMetricsIntDf

Read-only

cfmIpCbrMetricsIntMrvScale

Read-only

cfmIpCbrMetricsIntMrvPrecision

Read-only

cfmIpCbrMetricsIntMrv

Read-only

CISCO-IP-TAP-MIB

The CISCO-IP-TAP-MIB manages Cisco’s intercept feature for IP. This MIB is used along with CISCO-TAP2-MIB to intercept IP traffic. CISCO-TAP2-MIB along with specific filter MIBs like this MIB replace CISCO-TAP-MIB. To create an IP intercept, an entry citapStreamEntry is created which contains the filter details. An entry cTap2StreamEntry of CISCO-TAP2-MIB is created, which is the common stream information for all kinds of intercepts and type of the specific stream is set to ip in this entry.

MIB Tables

Table 3-93 lists the tables in CISCO-IP-TAP-MIB:

Table 3-93 CISCO-IP-TAP-MIB Tables

Name
Description

citapStreamTable

The Intercept Stream IP Table lists the IPv4 and IPv6 streams to be intercepted. The same data stream may be required by multiple taps, and one might assume that often the intercepted stream is a small subset of the traffic that could be intercepted. This essentially provides options for packet selection, only some of which might be used.

MIB Constraints

Table 3-94 lists the constraints on objects in the CISCO-IP-TAP-MIB.

Table 3-94 CISCO-IP-TAP-MIB Constraints

MIB Object
Notes

citapStreamCapabilities

Read-only

citapStreamInterface

Always 0. Read-create

citapStreamAddrType

Read-create

citapStreamDestinationAddress

Read-create

citapStreamDestinationLength

Read-create

citapStreamSourceAddress

Read-create

citapStreamSourceLength

Read-create

citapStreamTosByte

Read-create

citapStreamTosByteMask

Read-create

citapStreamFlowId

Read-create

citapStreamProtocol

Read-create

citapStreamDestL4PortMin

Read-create

citapStreamDestL4PortMax

Read-create

citapStreamSourceL4PortMin

Read-create

citapStreamSourceL4PortMax

Read-create

citapStreamVRF

Read-create

citapStreamStatus

Read-create

CISCO-IP-STAT-MIB

The CISCO-IP-STAT-MIB incorporates objects to provide support for the Cisco IP statistics as implemented in command interfaces.

MIB Tables

Table 3-95 lists the tables in CISCO-IP-STAT-MIB:

Table 3-95 CISCO-IP-STAT-MIB Tables

Name
Description

cipPrecedenceTable

A table of entries sorted by the precedence of IP packets. The table is created and deleted via ip accounting command line interface.

cipMacTable

A table is created and deleted via ip accounting command line interface.

cipMacFreeTable

A table of free space available to store new MAC address information.

cipPrecedenceXTable

This table contains additional objects for the cipPrecedenceTable.

cipMacXTable

This table contains additional objects for the cipMacTable.

CISCO-IPSEC-MIB

The MIB module for modeling Cisco-specific IPsec attributes. This MIB models the Cisco implementation-specific attributes of a Cisco entity that implements IPsec. This MIB is complementary to the standard IPsec MIB proposed jointly by Tivoli and Cisco. The ciscoIPsec MIB provides the operational information on Cisco’s IPsec tunnelling implementation. The following entities are managed: 1) ISAKMP Group: a) ISAKMP global parameters b) ISAKMP Policy Table 2) IPSec Group: a) IPSec Global Parameters b) IPSec Global Traffic Parameters c) Cryptomap Group - Cryptomap Set Table - Cryptomap Table - CryptomapSet Binding Table 3) System Capacity & Capability Group: a) Capacity Parameters b) Capability Parameters 4) Trap Control Group 5) Notifications Group

Table 3-96 lists the tables associated with this MIB.

MIB Objects

Table 3-96 CISCO-IPSEC-MIB Tables and Descriptions

Name
Description

cipsIsakmpPolicyTable

The table containing the list of all ISAKMP policy entries configured by the operator.

cipsStaticCryptomapSetTable

The table containing the list of all cryptomap sets that are fully specified and are not wild-carded. The operator may include different types of cryptomaps in such a set - manual, CET, ISAKMP or dynamic.

cipsDynamicCryptomapSetTable

The table containing the list of all dynamic cryptomaps that use IKE, defined on the managed entity.

cipsStaticCryptomapTable

The table ilisting the member cryptomaps of the cryptomap sets that are configured on the managed entity.

cipsCryptomapSetIfTable

The table lists the binding of cryptomap sets to the interfaces of the managed entity.

MIB Constraints

Table 3-99 lists the constraints on objects in the CISCO-IPSEC-MIB.

 

Table 3-97 CISCO-IPSEC-MIB Constraints

MIB Object
Notes

cipsCntlIsakmpPolicyAdded

Not supported

cipsCntlIsakmpPolicyDeleted

Not supported

cipsCntlCryptomapAdded

Not supported

cipsCntlCryptomapDeleted

Not supported

cipsCntlCryptomapSetAttached

Not supported

cipsCntlCryptomapSetDetached

Not supported

cipsCntlTooManySAs

Not supported

CISCO-IPSEC-FLOW-MONITOR-MIB

This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopted as an IETF standard.

Table 3-98 lists the tables associated with this MIB.

MIB Objects

Table 3-98 CISCO-IPSEC-FLOW-MONITOR-MIB Tables and Descriptions

Name
Description

cikePeerTable

The IPsec Phase-1 Internet Key Exchange Peer Table. There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. The IPsec Phase-1 IKE Tunnel associated with this IPsec Phase-1 IKE peer association may or may not be currently active.

cikeTunnelTable

The IPsec Phase-1 Internet Key Exchange Tunnel Table. There is one entry in this table for each active IPsec Phase-1 IKE Tunnel.

cikePeerCorrTable

The IPsec Phase-1 Internet Key Exchange Peer Association to IPsec Phase-2 Tunnel Correlation Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

cikePhase1GWStatsTable

Phase-1 IKE stats information is included in this table. Each entry is related to a specific gateway which is identified by ’cmgwIndex’.

cipSecTunnelTable

The IPsec Phase-2 Tunnel Table. There is one entry in this table for each active IPsec Phase-2 Tunnel.

cipSecEndPtTable

The IPsec Phase-2 Tunnel Endpoint Table. This table contains an entry for each active endpoint associated with an IPsec Phase-2 Tunnel.

cipSecSpiTable

The IPsec Phase-2 Security Protection Index Table. This table contains an entry for each active and expiring security association.

cipSecPhase2GWStatsTable

Phase-2 IPsec stats information is included in this table. Each entry is related to a specific gateway which is identified by ’cmgwIndex’

cikeTunnelHistTable

The IPsec Phase-1 Internet Key Exchange Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cipSecTunnelHistTable

The IPsec Phase-2 Tunnel History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cipSecEndPtHistTable

The IPsec Phase-2 Tunnel Endpoint History Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object.

cikeFailTable

The IPsec Phase-1 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

cipSecFailTable

The IPsec Phase-2 Failure Table. This table is implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object.

MIB Constraints

Table 3-99 lists the constraints on objects in the CISCO-IPSEC-FLOW-MONITOR-MIB.

Table 3-99 CISCO-IPSEC-FLOW-MONITOR-MIB Constraints

MIB Object
Notes

cikeTunStatus

Not supported

cipSecHistTableSize

Not supported

cipSecHistCheckPoint

Not supported

cipSecFailTableSize

Not supported

cipSecTrapCntlIkeTunnelStart

Not supported

cipSecTrapCntlIkeTunnelStop

Not supported

cipSecTrapCntlIkeSysFailure

Not supported

cipSecTrapCntlIkeCertCrlFailure

Not supported

cipSecTrapCntlIkeProtocolFail

Not supported

cipSecTrapCntlIkeNoSa

Not supported

cipSecTrapCntlIpSecTunnelStart

Not supported

cipSecTrapCntlIpSecTunnelStop

Not supported

cipSecTrapCntlIpSecSysFailure

Not supported

cipSecTrapCntlIpSecSetUpFailure

Not supported

cipSecTrapCntlIpSecEarlyTunTerm

Not supported

cipSecTrapCntlIpSecProtocolFail

Not supported

cipSecTrapCntlIpSecNoSa

Not supported

cipSecTunStatus

Not supported

CISCO-LICENSE-MGMT-MIB

The MIB module for managing licenses on the system. The licensing mechanism provides flexibility to enforce licensing for various features in the system.

Table 3-100 lists the tables associated with this MIB.

MIB Objects

Table 3-100 CISCO-LICENSE-MGMT-MIB Tables and Descriptions

clmgmtLicenseActionTable

A table for invoking license management actions. Management application must create a row in this table to trigger any of the license management actions. The following are different actions that can be executed using this table. 1. install 2. clear 3. processPermissionTicket 4. regenerateLastRehostTicket 5. backup 6. generateEULA Refer to the description of clmgmtLicenseAction for more information on what these actions do on the device. Once the request completes, the management application should retrieve the values of the objects of interest, and then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completion.

clmgmtLicenseActionResultTable

This table contains results of license action if the license action involves multiple licenses. Entries in this table are not created for actions where there is only license that is subject of the action. For example, if there are 3 licenses in a license file when executing license install action, 3 entries will be created in this table, one for each license.

clmgmtLicenseStoreInfoTable

This table contains information about all the license stores allocated on the device.

clmgmtLicenseDeviceInfoTable

This table contains objects that provide licensing related information at the device level. Entries will exist only for entities that support licensing. For example, if it is a stand alone device and supports licensing, then there will be only one entry in this table. If it is stackable switch then there will be multiple entries with one entry for each device in the stack.

clmgmtLicenseInfoTable

This table contains information about all the licenses installed on the device.

clmgmtLicensableFeatureTable

This table contains list of licensable features in the image. All the licensable features will have an entry each in this table irrespective of whether they are using any licenses currently. Entries in this table are created by the agent one for each licensable feature in the image. These entries remain in the table permanently and can not be deleted. Management application can not create or delete entries from this table.

clmgmtDevCredExportActionTable

A table for triggering device credentials export action. Management application must create this entry to trigger the export of device credentials from the device to a file. Once the request completes, the management application should retrieve the values of the objects of interest, and then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completion.

MIB Constraints

Table 3-101 lists the constraints on objects in the CISCO-LICENSE-MGMT-MIB.

Table 3-101 CISCO-LICENSE-MGMT-MIB Constraints

MIB Object
Notes

clmgmtDevCredEntPhysicalIndex

Not supported

clmgmtDevCredTransferProtocol

Not supported

clmgmtDevCredServerAddressType

Not supported

clmgmtDevCredServerAddress

Not supported

clmgmtDevCredServerUsername

Not supported

clmgmtDevCredServerPassword

Not supported

clmgmtDevCredExportFile

Not supported

clmgmtDevCredCommand

Not supported

clmgmtDevCredStorageType

Not supported

clmgmtDevCredRowStatus

Not supported

clmgmtLicenseUsageNotifEnable

Not supported

clmgmtLicenseDeploymentNotifEnable

Not supported

clmgmtLicenseErrorNotifEnable

Not supported

clmgmtLicenseComments

Not supported

CISCO-LPTS-MIB

The MIB module for Local Packet Transport Services(LPTS) related information like the flows and the policer values related to various flows present in the system. The number of packets coming into the system is controlled by the policer values associated with the protocol. Each protocol is classified into different flows and a rate limit is associated with the flows. Policer is a numerical value controlling the number of packets entering the box. The flows represent individual, specific protocols. Flow types also represent the degree of trust for a given packet. Example: BGP packets coming from established session is assigned one flow, packets from configured BGP peer are assigned different flow. Other BGP packets are assigned a third flow.

This table lists the tables associated with this MIB.

 

Name
Description

clGlobalFlowTable

This table respresents the flows configured globally and the configuration will be reflected across all the linecards

clLocalFlowTable

This table represents the configurations for the local flow types & affects a particular nodeID for which config is applied. When local flow type is not configured & we have a global configuration then the clLocalFlowTable has global flow value. If neither local flow nor the global flows are configured, then clLocalFlowTable will have static values derived from the config file. If both the local flow and global flow is configured, then the local flow information takes precedence over the global flow information.

CISCO-MEMORY-POOL-MIB

The CISCO-MEMORY-POOL-MIB contains objects that represents the different types of memory pools that may be present in a managed device. Memory pools are categorized into two groups:

  • Predefined pools
  • Dynamic pools

Table 3-102 lists the tables associated with this MIB.

 

Table 3-102 CISCO-MEMORY-POOL-MIB Tables and Descriptions

Name
Description

ciscoMemoryPoolTable

Table of memory pool monitoring entries.

ciscoMemoryPoolUtilizationTable

Table of memory pool utilization entries. Each of the objects provides a general idea of how much of the memory pool has been used over a given period of time. It is determined as a weighted decaying average.

CISCO-MLD-SNOOPING-MIB

This MIB module defines objects that describe IGMP/MLD snooping. It provides remote network management system the ability to manage the IGMP/MLD Snooping feature when snooping is operating at the system and port level. Virtual systems and related ports data can be accessed by NMS using appropriate SNMP context. For example, in order to access data related to a particular L2VPN bridge domain system, the user shall specify on the SNMP request the SNMP context related to that particular bridge domain.

Table 3-103 lists the tables associated with this MIB.

MIB Objects

Table 3-103 CISCO-MLD-SNOOPING-MIB Tables and Descriptions

Name
Description

cmsProfileTable

This table lists IGMP/MLD configuration for each profile available on the system.

cmsConfigPortTable

This table lists snooping configuration for each port.

cmsMcastInfoTable

This table lists the snooping multicast operational data for group/source addresses associated to a port.

cmsMRouterPortInfoTable

This table provides IGMP/MLD snooping operational data for the multicast router ports available on the system.

cmsStatsPortTrfTable

This table provides the IGMP/MLD snooping port traffic statistics. Each row contains traffic statistical data associated with a unique bridge domain port identified by the indexes. Conceptual rows can be seen by SNMP agents or NMS as containing statistical informations related to the indexes discovered on cbdBridgeDomainTable and cbdPortTable

MIB Constraints

Table 3-104 lists the constraints on objects in the CISCO-MLD-SNOOPING-MIB.

 

Table 3-104 CISCO-MLD-SNOOPING-MIB Constraints

MIB Object
Notes

cmsConfigPortProfileName

Not supported

cmsProfileSnoopMinVersion

Not supported

cmsProfileStatus

Not supported

cmsProfileStorageType

Not supported

cmsProfileIPAddress

Not supported

cmsProfileRobustnessVariable

Not supported

cmsProfileIntQuerierVersion

Not supported

cmsProfileIPAddrType

Not supported

cmsConfigPortStatus

Not supported

cmsConfigPortStorageType

Not supported

CISCO-MPLS-TE-STD-EXT-MIB

This MIB module contains Cisco specific managed object definitions for MPLS Traffic Engineering (TE), not contained in MPLS-TE-STD-MIB. The auto bandwidth feature enables MPLS TE Tunnels to adapt automatically their bandwidth to their actual load.

Table 3-105 lists the tables defined in CISCO-MPLS-TE-STD-EXT-MIB.

 

Table 3-105 CISCO-MPLS-TE-STD-EXT-MIB Objects

cmplsTunnelAutoBWTable

This table is used in order to manage auto bandwidth data. This table is sparse dependent on the mplsTunnelTable. An entry in this table exists for each mplsTunnelEntry with a mplsTunnelRole of ’head’ or ’headTail’. Each row contains auto-bandwidth data for the tunnel identified by the indexes defined later. An entry is created as soon as a ’head’ or ’headTail’ MPLS TE tunnel is configured in the system.

CISCO-NETSYNC-MIB

The Synchronous Ethernet (SyncE) MIB is defined for monitoring network synchronization based on ITU-T G.781 clock selection. Synchronous Ethernet (SyncE) is a standard defined for delivering timing to the remote NEs through a Packet Network. SyncE is well defined by ITU-T which included G.8261, G.8262, G.8264 and G.781. It leverages the PHY layer of Ethernet to transmit frequency to the remote sites. Its functionality and accuracy mimics that of the SONET/SDH network because of its physical layer characteristic. In order to allow best clock source traceability, define the timing source correctly helps prevent timing loop. Synchronization Status Message is required for SyncE. This is similar to SONET/SDH. However, since SONET/SDH use 4 bits from the two S bytes in the SONET/SDH overhead frame for such message, Ethernet relies on a different channel called ESMC (Ethernet Synchronization Messaging Channel) which is based on IEEE 802.3 Organization Specific Slow Protocol.

MIB Objects

Table 3-106 CISCO-NETSYNC-MIB Tables and Descriptions

Name
Description

cnsClkSelGlobalTable

G.781 clock selection process table. This table contains the global parameters for the G.781 clock selection process.

cnsSelectedInputSourceTable

T0 selected clock source table. This table contains the selected clock source for the input T0 clock.

cnsInputSourceTable

T0 clock source table. This table contains a list of input sources for input T0 clock selection.

cnsExtOutputTable

T4 external output table. This table contains a list of T4 external outputs. Each T4 external output is associated with clock source(s) to be found in cnsT4ClockSourceTable. The clock selection process considers all the available clock sources and select the T4 clock source based on the G.781 clock selection algorithm.

cnsT4ClockSourceTable

T4 clock source table. This table contains a list of input sources for a specific T4 external output. An entry shall be added to cnsExtOutputTable first. Then clock sources shall be added in this table for the selection process to select the appropriate T4 clock source.

MIB Constraints

Table 3-107 lists the constraints on objects in the CISCO-NETSYNC-MIB.

Table 3-107 CISCO-NETSYNC-MIB Constraints

MIB Object
Notes

cnsClkSelGlobalTable

 

cnsClkSelGloProcIndex

Always 1

cnsClkSelGlobNetsyncEnable

Supported

cnsClkSelGlobRevertiveMode

Always FALSE

cnsClkSelGlobESMCMode

Always TRUE

cnsClkSelGlobEECOption

Supported

cnsClkSelGlobNetworkOption

Supported

cnsClkSelGlobWtrTime

Supported

cnsClkSelGlobNofSources

Supported

cnsClkSelGlobLastHoldoverSeconds

Supported

cnsClkSelGlobCurrHoldoverSeconds

Supported

cnsClkSelGlobClockMode

Supported

cnsClkSelGlobProcessMode

Not supported

cnsClkSelGlobHoldoffTime

Not supported

cnsSelectedInputSourceTable

 

cnsSelInpSrcNetsyncIndex

Supported

cnsSelInpSrcName

Supported

cnsSelInpSrcIntfType

Supported

cnsSelInpSrcQualityLevel

Supported

cnsSelInpSrcPriority

Supported

cnsSelInpSrcFSW

Always FALSE

cnsSelInpSrcMSW

Always FALSE

cnsSelInpSrcTimestamp

Not supported

cnsInputSourceTable

 

cnsInpSrcNetsyncIndex

Supported

cnsInpSrcName

Supported

cnsInpSrcIntfType

Supported

cnsInpSrcPriority

Supported

cnsInpSrcESMCCap

Supported

cnsInpSrcSSMCap

Supported

cnsInpSrcQualityLevelTxCfg

Supported

cnsInpSrcQualityLevelRxCfg

Supported

cnsInpSrcQualityLevelTx

Supported

cnsInpSrcQualityLevelRx

Supported

cnsInpSrcQualityLevel

Supported

cnsInpSrcWtrTime

Supported

cnsInpSrcLockout

Always false

cnsInpSrcSignalFailure

Supported

cnsInpSrcAlarm

Supported

cnsInpSrcFSW

Always false

cnsInpSrcMSW

Always false

cnsInpSrcAlarmInfo

Not supported

cnsInpSrcHoldoffTime

Not supported

cnsExtOutputTable

 

cnsExtOutListIndex

Supported

cnsExtOutSelNetsyncIndex

Supported

cnsExtOutName

Supported

cnsExtOutIntfType

Supported

cnsExtOutQualityLevel

Supported

cnsExtOutPriority

Supported

cnsExtOutFSW

Always false

cnsExtOutMSW

Always false

cnsExtOutSquelch

Supported

cnsT4ClockSourceTable

 

cnsT4ClkSrcNetsyncIndex

Supported

cnsT4ClkSrcName

Supported

cnsT4ClkSrcIntfType

Supported

cnsT4ClkSrcPriority

Supported

cnsT4ClkSrcESMCCap

Supported

cnsT4ClkSrcSSMCap

Supported

cnsT4ClkSrcQualityLevelTxCfg

Supported

cnsT4ClkSrcQualityLevelRxCfg

Supported

cnsT4ClkSrcQualityLevelTx

Supported

cnsT4ClkSrcQualityLevelRx

Supported

cnsT4ClkSrcQualityLevel

Supported

cnsT4ClkSrcWtrTime

Supported

cnsT4ClkSrcLockout

Always false

cnsT4ClkSrcSignalFailure

Supported

cnsT4ClkSrcAlarm

Supported

cnsT4ClkSrcFSW

Always false

cnsT4ClkSrcMSW

Always false

cnsT4ClkSrcAlarmInfo

Not supported

cnsT4ClkSrcHoldoffTime

Not supported

CISCO-NTP-MIB

The CISCO-NTP-MIB provides mechanisms to monitor an Network Time Protocol (NTP) server. The (NTP) Version 3 is used to synchronize timekeeping among a set of distributed time servers and clients. The service model is based on a returnable-time design which depends only on measured clock offsets, but does not require reliable message delivery. The synchronization subnet uses a self-organizing, hierarchical master-slave configuration, with synchronization paths determined by a minimum-weight spanning tree. While multiple masters (primary servers) may exist, there is no requirement for an election protocol.

In the NTP model several primary reference sources, synchronized by wire or radio to national standards, are connected to widely accessible resources, such as backbone gateways, and operated as primary time servers. The purpose of NTP is to convey timekeeping information from these servers to other time servers via the Internet and also to cross-check clocks and mitigate errors because of equipment or propagation failures. Some number of local-net hosts or gateways, acting as secondary time servers, run NTP with one or more of the primary servers. To reduce the protocol overhead, the secondary servers distribute time via NTP to the remaining local-net hosts. In the interest of reliability, selected hosts can be equipped with less accurate but less expensive radio clocks and used for backup in case of failure of the primary or secondary servers or communication paths between them.

NTP is designed to produce three products: clock offset, round-trip delay, and dispersion, all of which are relative to a selected reference clock. Clock offset represents the amount to adjust the local clock to bring it into correspondence with the reference clock. Roundtrip delay provides the capability to launch a message to arrive at the reference clock at a specified time. Dispersion represents the maximum error of the local clock relative to the reference clock. Because most host time servers synchronize via another peer time server, there are two components in each of these three products, those determined by the peer relative to the primary reference source of standard time and those measured by the host relative to the peer. Each of these components are maintained separately in the protocol to facilitate error control and management of the subnet itself. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the user interface can determine not only the time, but the quality of the time as well.

In what may be the most common client/server model, a client sends an NTP message to one or more servers and processes the replies as received. The server interchanges addresses and ports, overwrites certain fields in the message, recalculates the checksum and returns the message immediately. Information included in the NTP message allows the client to determine the server time with respect to local time and adjust the local clock accordingly. Also, the message includes information to calculate expected timekeeping accuracy and reliability, as well as select the best from possibly several servers. Although the client/server model may suffice for use on local nets involving a public server and perhaps many workstation clients, the full generality of NTP requires distributed participation of a number of client/servers or peers arranged in a dynamically reconfigurable, hierarchically distributed configuration. It also requires sophisticated algorithms for association management, data manipulation and local-clock control.

Table 3-108 lists the tables associated with this MIB.

 

Table 3-108 CISCO-NTP-MIB Tables and Descriptions

Name
Description

cntpPeersVarTable

This table provides information on the peers with which the local NTP server has associations. The peers are also NTP servers but running on different hosts.

cntpFilterRegisterTable

Contains NTP state variables used by the NTP clock filter and selection algorithms. This table depicts a shift register. Each stage in the shift register is a 3-tuple consisting of the measured clock offset, measured clock delay, and measured clock dispersion associated with a single observation. An important factor affecting the accuracy and reliability of time distribution is the complex of algorithms used to reduce the effect of statistical errors and falsetickers because of failure of various subnet components, reference sources or propagation media. The NTP clock-filter and selection algorithms are designed to do exactly this. The objects in the filter register table below are used by these algorithms to minimize the error in the calculated time.

MIB Constraints


NoteCISCO-NTP-MIB has very limited support. cntpSysSrvStatus is supported.


Table 3-109 lists the constraints on objects in the CISCO-NTP-MIB.

Table 3-109 CISCO-NTP-MIB Constraints

MIB Object
Notes
cntpPeersVarTable

Not supported

cntpFilterRegisterTable

Not supported

cntpSysLeap

Not supported

cntpSysStratum

Not supported

cntpPeersPrefPeer

Not supported

cntpPeersPeerAddress

Not supported

cntpPeersHostAddress

Not supported

cntpPeersMode

Not supported

cntpPeersEntryStatus

Not supported

cntpPeersPeerName

Not supported

cntpPeersPeerType

Not supported

CISCO-OAM-MIB

A MIB module for invoking OAM loopback Ping on ATM connections.

Table 3-110 lists the tables associated with this MIB.

MIB Objects

Table 3-110 CISCO-OAM-MIB Tables and Descriptions

Name
Description

oamLoopbackPingTable

A table of OAM loopback request entries. (This table is similar to the CISCO-PING-MIB.)

oamLoopbackSegEndPointTable

This table contains a list of OAM loopback segment endpoints. When the endpoint is an OAM segment endpoint, it is able to send ATM segment loop back cells or loop back the cells to the originator which initiates the OAM loop back ping test. The provisioning of this table is required if the loopback ping test type (oamLoopbackPingType) in oamLoopbackPingTable is ’segment’, and the endpoint under test or the remote ping endpoint is not OAM segment loopback endpoints.

MIB Constraints

Table 3-109 lists the constraints on objects in the CISCO-OAM-MIB.

Table 3-111 CISCO-OAM-MIB Constraints

MIB Object
Notes

oamLoopSegRowStatus

Not supported

CISCO-OTN-IF-MIB

The CISCO-OTN-IF-MIB defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performance statistics objects for protocol specific error counters in DWDM optical devices.

Performance monitoring (PM) parameters are used by service providers to gather, store, set thresholds for and report performance data for early detection of problems. Thresholds are used to set error levels for each PM parameter. During the accumulation cycle, if the current value of a performance monitoring parameter reaches or exceeds its corresponding threshold value, a threshold crossing alarm (TCA) is generated. The TCAs provide early detection of performance degradation.

MIB Objects

Table 3-112 lists the tables associated with this MIB.

Table 3-112 CISCO-OTN-IF-MIB Tables and Descriptions

Name
Description

coiIfControllerTable

This table provides management information for physical layer related attributes of interfaces with an ifType of opticalChannel (195).

coiOtnNearEndThresholdsTable

This table provides objects for configuring OTN (G.709) near end error thresholds on interfaces of ifType opticalChannel (195).

coiOtnFarEndThresholdsTable

This table provides objects for configuring OTN (G.709) thresholds for far end of interfaces of ifType opticalChannel (195).

coiOtnNearEndCurrentTable

This table contains the cumulative OTN (G.709) PM statistics for the near end of interfaces of ifType opticalChannel (195). The statistics are for the current interval of interval type identified by coiOtnNearEndCurIntervalType. The current PM statistics is the accumulated statistics for the time period defined by the interval type.

coiOtnFarEndCurrentTable

This table contains the cumulative OTN (G.709) PM stats for the far end of interfaces of ifType opticalChannel (195). The statistics are for the current interval of interval type identified by coiOtnFarEndCurIntervalType. The current PM statistics is the accumulated statistics for the time period defined by the interval type.

coiOtnNearEndIntervalTable

This table contains historical cumulative OTN (G.709) PM stats for the near end of interfaces of ifType opticalChannel (195), for the interval type identified by the index coiOtnNearEndIntervalType and the interval number as identified by the index coiOtnNearEndIntervalNum. The PM statistics is the accumulated stats for the time period defined by the interval type in the time interval as defined by interval number.

coiOtnFarEndIntervalTable

This table contains historical cumulative OTN (G.709) PM stats for the far end interfaces of ifType opticalChannel (195), for the interval type identified by the index coiOtnFarEndIntervalType and the interval number as identified by coiOtnFarEndIntervalNum. The PM statistics is the accumulated stats for the time period defined by the interval type in the time interval as defined by interval number.

coiFECThresholdsTable

This table contains the configurable thresholds for Forward Error Correction statistics.

coiFECCurrentTable

This table contains the cumulative FEC PM stats for the interfaces of ifType opticalChannel (195) for the current interval of interval type identified coiFECCurIntervalType.

coiFECIntervalTable

This table contains historical cumulative FEC PM stats for the interfaces of ifType opticalChannel (195), for the interval type identified by the index coiFECIntervalType and the interval number as identified by index coiFECIntervalNum. The PM statistics is the accumulated stats for the time period defined by the interval type in the time interval as defined by interval number.

CISCO-PTP-MIB

The MIB module for PTPv2 (IEEE1588 - 2008) Overview of PTPv2 (IEEE 1588-2008) This IEEE standard defines a protocol enabling precise synchronization of clocks in measurement and control systems implemented with packet-based networks, the IEEE Standard PTPv2 1588 (2008). This MIB does not address the standard IEEE 1588 (2002). The protocol is applicable to network elements communicating using IP. The protocol enables heterogeneous systems that include clocks of various inherent precision, resolution, and stability to synchronize to a grandmaster clock. The protocol supports system-wide synchronization accuracy in the sub-microsecond range with minimal network and local clock computing resources. The standard uses UDP/IP. It includes formal mechanisms for message extensions, higher sampling rates, correction for asymmetry, a clock type to reduce error accumulation in large topologies, and specifications on how to incorporate the resulting additional data into the synchronization protocol. The standard defines conformance and management capability also. MIB description This MIB is to support the Precision Timing Protocol (PTP) feature of Cisco System devices.

MIB Objects

Table 3-113 lists the tables associated with this MIB.

Table 3-113 CISCO-PTP-MIB Tables and Descriptions

Name
Description

cPtpSystemTable

Table of count information about the PTP system for all domains.

cPtpSystemDomainTable

Table of information about the PTP system for all clock modes -- ordinary, boundary or transparent.

cPtpClockNodeTable

Table of information about the PTP system for a given domain.

cPtpClockCurrentDSTable

Table of information about the PTP clock Current Datasets for all domains.

cPtpClockParentDSTable

Table of information about the PTP clock Parent Datasets for all domains.

cPtpClockDefaultDSTable

Table of information about the PTP clock Default Datasets for all domains.

cPtpClockRunningTable

Table of information about the PTP clock Running Datasets for all domains.

cPtpClockTimePropertiesDSTable

Table of information about the PTP clock Timeproperties Datasets for all domains.

cPtpClockTransDefaultDSTable

Table of information about the PTP Transparent clock Default Datasets for all domains.

cPtpClockPortTable

Table of information about the clock ports for a particular domain.

cPtpClockPortDSTable

Table of information about the clock ports dataset for a particular domain.

cPtpClockPortRunningTable

Table of information about the clock ports running dataset for a particular domain.

cPtpClockPortTransDSTable

Table of information about the Transparent clock ports running dataset for a particular domain.

cPtpClockPortAssociateTable

Table of information about a given port’s associated ports. For a master port - multiple slave ports which have established sessions with the current master port. For a slave port - the list of masters available for a given slave port. Session information (pkts, errors) to be displayed based on availability and scenario.

MIB Constraints

Table 3-114 lists the constraints that the Cisco ASR 9000 Series router places on objects in the CISCO-PTP-MIB.

 

Table 3-114 CISCO-PTP-MIB Constraints

MIB Object
Notes
cPtpSystemDomainTable

 

cPtpSystemDomainClockTypeIndex

Always “boundary clock”

cPtpSystemDomainTotals

Always 1

ciscoPtpMibSystemInfo

 

cPtpSystemProfile

Always "vendor specific"

cPtpSystemTable

 

cPtpDomainIndex

Supported

cPtpInstanceIndex

Always 0

cPtpDomainClockPortsTotal

Supported

cPtpDomainClockPortPhysicalInterfacesTotal

Supported

cPtpSystemDomainTable

 

cPtpSystemDomainClockTypeIndex

Supported

cPtpSystemDomainTotals

Supported

cPtpClockNodeTable

Not supported

cPtpClockCurrentDSTable

 

cPtpClockCurrentDSDomainIndex

Supported

cPtpClockCurrentDSClockTypeIndex

Always "boundary clock"

cPtpClockCurrentDSInstanceIndex

Always 0

cPtpClockCurrentDSStepsRemoved

Supported

cPtpClockCurrentDSOffsetFromMaster

Not supported

cPtpClockCurrentDSMeanPathDelay

Not supported

cPtpClockParentDSTable

 

PtpClockParentDSDomainIndex

Supported

cPtpClockParentDSClockTypeIndex

Always "boundary clock"

cPtpClockParentDSInstanceIndex

Always 0

cPtpClockParentDSParentPortIdentity

Supported

cPtpClockParentDSParentStats

Supported

cPtpClockParentDSGMClockIdentity

Supported

cPtpClockParentDSGMClockPriority1

Supported

cPtpClockParentDSGMClockPriority2

Supported

cPtpClockParentDSGMClockQualityClass

Supported

cPtpClockParentDSGMClockQualityAccuracy

Supported

cPtpClockParentDSGMClockQualityOffset

Supported

cPtpClockParentDSOffset

Not supported

cPtpClockParentDSClockPhChRate

Not supported

cPtpClockDefaultDSTable

 

cPtpClockDefaultDSDomainIndex

Supported

cPtpClockDefaultDSClockTypeIndex

Always "boundary clock"

cPtpClockDefaultDSInstanceIndex

Always 0

cPtpClockDefaultDSTwoStepFlag

Always true

cPtpClockDefaultDSClockIdentity

Supported

cPtpClockDefaultDSPriority1

Supported

cPtpClockDefaultDSPriority2

Supported

cPtpClockDefaultDSSlaveOnly

Always false

cPtpClockDefaultDSQualityClass

Supported

cPtpClockDefaultDSQualityAccuracy

Supported

cPtpClockDefaultDSQualityOffset

Supported

cPtpClockRunningTable

 

cPtpClockRunningDomainIndex

Supported

cPtpClockRunningClockTypeIndex

Always "boundary clock"

cPtpClockRunningInstanceIndex

Always 0

cPtpClockRunningState

Supported

cPtpClockRunningPacketsSent

Supported

cPtpClockRunningPacketsReceived

Supported

cPtpClockTimePropertiesDSTable

 

cPtpClockTimePropertiesDSDomainIndex

Supported

cPtpClockTimePropertiesDSClockTypeIndex

Always "boundary clock"

cPtpClockTimePropertiesDSInstanceIndex

Always 0

cPtpClockTimePropertiesDSCurrentUTCOffsetValid

Supported

cPtpClockTimePropertiesDSCurrentUTCOffset

Supported

cPtpClockTimePropertiesDSLeap59

Supported

cPtpClockTimePropertiesDSLeap61

Supported

cPtpClockTimePropertiesDSTimeTraceable

Supported

cPtpClockTimePropertiesDSFreqTraceable

Supported

cPtpClockTimePropertiesDSPTPTimescale

Supported

cPtpClockTimePropertiesDSSource

Supported

cPtpClockTransDefaultDSTable

Not supported

cPtpClockPortTable

 

cPtpClockPortDomainIndex

Supported

cPtpClockPortClockTypeIndex

Always "boundary clock"

cPtpClockPortClockInstanceIndex

Always 0

cPtpClockPortTablePortNumberIndex

Supported

cPtpClockPortName

Supported

cPtpClockPortRole

Supported

cPtpClockPortSyncOneStep

Supported

cPtpClockPortCurrentPeerAddressType

Supported

cPtpClockPortCurrentPeerAddress

Supported

cPtpClockPortNumOfAssociatedPorts

Supported

cPtpClockPortDSTable

 

cPtpClockPortDSDomainIndex

Supported

cPtpClockPortDSClockTypeIndex

Always "boundary clock"

cPtpClockPortDSClockInstanceIndex

Always 0

cPtpClockPortDSPortNumberIndex

Supported

cPtpClockPortDSName

Supported

cPtpClockPortDSPortIdentity

Supported

cPtpClockPortDSAnnouncementInterval

Supported

cPtpClockPortDSAnnounceRctTimeout

Supported

cPtpClockPortDSSyncInterval

Supported

cPtpClockPortDSMinDelayReqInterval

Supported

cPtpClockPortDSDelayMech

Always "e2e"

cPtpClockPortDSPTPVersion

Always 2

cPtpClockPortDSPeerDelayReqInterval

Not supported

cPtpClockPortDSPeerMeanPathDelay

Not supported

cPtpClockPortDSGrantDuration

Not supported

cPtpClockPortRunningTable

 

cPtpClockPortRunningDomainIndex

Supported

cPtpClockPortRunningClockTypeIndex

Always "boundary clock"

cPtpClockPortRunningClockInstanceIndex

Always 0

cPtpClockPortRunningPortNumberIndex

Supported

cPtpClockPortRunningName

Supported

cPtpClockPortRunningState

Supported

cPtpClockPortRunningRole

Supported

cPtpClockPortRunningInterfaceIndex

Supported

cPtpClockPortRunningIPversion

Supported

cPtpClockPortRunningTxMode

Supported

cPtpClockPortRunningPacketsReceived

Supported

cPtpClockPortRunningPacketsSent

Supported

cPtpClockPortRunningRxMode

Not supported

cPtpClockPortRunningEncapsulationType

Not supported

cPtpClockPortTransDSTable

Not supported

cPtpClockPortAssociateTable

 

cPtpClockPortCurrentDomainIndex

Supported

cPtpClockPortCurrentClockTypeIndex

Always "boundary clock"

cPtpClockPortCurrentClockInstanceIndex

Always 0