Cisco ASR 9000 Series Aggregation Services Router MIB ... · PDF fileCisco ASR 9000 Series...

Cisco Systems, Inc. www.cisco.com

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide

Cisco IOS XR Software Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

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

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Contents

2

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R) Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide © 2014 Cisco Systems, Inc. All rights reserved.


3

Contents Contents ................................................................................................................................................... 3

Preface ................................................................................................................................................... 18

Revision History ........................................................................................................................................................ 18

Audience .................................................................................................................................................................... 19

Organization .............................................................................................................................................................. 19

Terminology and Definitions .................................................................................................................................. 20

Obtaining Documentation and Submitting a Service Request ...................................................................... 20

Chapter 1 - Cisco ASR 9000 Series Routers MIB Overview ............................................................... 21

Benefits of MIB Enhancements ............................................................................................................................. 21

SNMP Overview ....................................................................................................................................................... 21

MIB Description .................................................................................................................................................... 22

SNMP Notifications .............................................................................................................................................. 22

SNMP Versions ..................................................................................................................................................... 23

Object Identifiers ...................................................................................................................................................... 25

Chapter 2 - Configuring MIB Support................................................................................................... 26

Downloading and Compiling MIBs ....................................................................................................................... 26

Considerations for Working with MIBs ............................................................................................................ 26

Downloading MIBs ............................................................................................................................................... 27

Compiling MIBs .................................................................................................................................................... 27

Enabling SNMP Support ......................................................................................................................................... 27

Chapter 3 - Cisco ASR 9000 Series Routers MIB Specifications ....................................................... 29

Cisco ASR 9000 Series Routers MIBs................................................................................................................. 29


4

Cisco ASR 9000 Series Routers MIB Categories ............................................................................................. 29

Supported MIBs .................................................................................................................................................... 29

Unsupported MIBs ............................................................................................................................................... 30

MIB Version String Description ............................................................................................................................. 30

MIBs in the Cisco ASR 9000 Series Routers ................................................................................................. 31

MIB Notification Names in the Cisco ASR 9000 Series Routers ............................................................... 54

ATM-MIB .................................................................................................................................................................... 56

MIB Constraints .................................................................................................................................................... 56

ATM-FORUM-MIB ................................................................................................................................................... 57

ATM2-MIB ................................................................................................................................................................. 58

MIB Constraints .................................................................................................................................................... 60

BGP4-MIB .................................................................................................................................................................. 62

MIB Constraints .................................................................................................................................................... 62

BRIDGE-MIB .............................................................................................................................................................. 63

MIB Constraints .................................................................................................................................................... 64

CISCO-AAA-SERVER-MIB .................................................................................................................................... 65

CISCO-ACL-MIB ...................................................................................................................................................... 65

CISCO-ATM-EXT-MIB ........................................................................................................................................... 66

MIB Constraints .................................................................................................................................................... 66

CISCO-ATM-QOS-MIB .......................................................................................................................................... 67

MIB Constraints .................................................................................................................................................... 68

CISCO-BGP4-MIB ................................................................................................................................................... 69

MIB Constraints .................................................................................................................................................... 70

CISCO-BGP-POLICY-ACCOUNTING-MIB ........................................................................................................ 70


5

CISCO-BULK-FILE-MIB .......................................................................................................................................... 70

MIB Constraints .................................................................................................................................................... 72

CISCO-CDP-MIB ..................................................................................................................................................... 72

MIB Constraints .................................................................................................................................................... 73

CISCO-CLASS-BASED-QOS-MIB ...................................................................................................................... 73

MIB Tables ............................................................................................................................................................. 74

MIB Constraints .................................................................................................................................................... 76

CISCO-CONFIG-COPY-MIB ................................................................................................................................. 78

MIB Constraints .................................................................................................................................................... 79

CISCO-CONFIG-MAN-MIB ................................................................................................................................... 80

CISCO-CONTEXT-MAPPING-MIB ....................................................................................................................... 80

MIB Constraints .................................................................................................................................................... 81

CISCO-DS3-MIB ...................................................................................................................................................... 82

MIB Constraints .................................................................................................................................................... 83

CISCO-ENHANCED-IMAGE-MIB ......................................................................................................................... 85

CISCO-ENHANCED-MEMPOOL-MIB .................................................................................................................. 86

MIB Constraints .................................................................................................................................................... 87

CISCO-ENTITY-ASSET-MIB ................................................................................................................................. 88

MIB Tables ............................................................................................................................................................. 88

MIB Constraints .................................................................................................................................................... 89

CISCO-ENTITY-FRU-CONTROL-MIB ................................................................................................................. 89

MIB Tables ............................................................................................................................................................. 89

MIB Constraints .................................................................................................................................................... 90

CISCO-ENTITY-REDUNDANCY-MIB ................................................................................................................... 92


6

MIB Tables ............................................................................................................................................................. 92

MIB Constraints .................................................................................................................................................... 93

CISCO-ENTITY-SENSOR-MIB .............................................................................................................................. 95

MIB Tables ............................................................................................................................................................. 95

MIB Constraints .................................................................................................................................................... 95

MIB Usage Values for Cisco Transceivers ..................................................................................................... 95

CISCO-ENTITY-STATE-EXT-MIB ........................................................................................................................ 97

MIB Tables ............................................................................................................................................................. 97

MIB Constraints .................................................................................................................................................... 98

CISCO-FLASH-MIB ................................................................................................................................................. 98

MIB Constraints .................................................................................................................................................. 100

CISCO-FLOW-CLONE-MIB ................................................................................................................................. 101

MIB Tables ........................................................................................................................................................... 101

MIB Constraints .................................................................................................................................................. 101

CISCO-FLOW-MONITOR-MIB ............................................................................................................................ 102

MIB Constraints .................................................................................................................................................. 103

CISCO-FRAME-RELAY-MIB ................................................................................................................................ 108

CISCO-FTP-CLIENT-MIB ..................................................................................................................................... 110

CISCO-HSRP-EXT-MIB ........................................................................................................................................ 110

MIB Constraints .................................................................................................................................................. 110

CISCO-HSRP-MIB ................................................................................................................................................. 111

MIB Constraints .................................................................................................................................................. 111

CISCO-IETF-BFD-MIB .......................................................................................................................................... 112

MIB Tables ........................................................................................................................................................... 112


7

MIB Constraints .................................................................................................................................................. 112

CISCO-IETF-FRR-MIB .......................................................................................................................................... 113

MIB Constraints .................................................................................................................................................. 114

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

MIB Objects ......................................................................................................................................................... 115

MIB Constraints .................................................................................................................................................. 115

CISCO‐IETF‐IPMROUTE‐MIB ....................................................................................................................................... 116

MIB Constraints ...................................................................................................................................................... 117

CISCO‐IETF‐MSDP‐MIB ............................................................................................................................................... 117

MIB Constraints ...................................................................................................................................................... 118

CISCO‐IETF‐PIM‐MIB .................................................................................................................................................. 119

MIB Constraints ...................................................................................................................................................... 120

CISCO‐IETF‐PIM‐EXT‐MIB ........................................................................................................................................... 120

MIB Constraints ...................................................................................................................................................... 122

CISCO‐IETF‐PW‐ENET‐MIB .......................................................................................................................................... 122

MIB Constraints ...................................................................................................................................................... 124

CISCO‐IETF‐PW‐MIB ................................................................................................................................................... 124

MIB Constraints ...................................................................................................................................................... 125

CISCO‐IETF‐PW‐FR‐MIB .............................................................................................................................................. 126

MIB Objects ............................................................................................................................................................ 127

MIB Constraints ...................................................................................................................................................... 127

CISCO‐IETF‐PW‐MPLS‐MIB ......................................................................................................................................... 128

MIB Constraints ...................................................................................................................................................... 128

CISCO‐IETF‐PW‐TC‐MIB .............................................................................................................................................. 130

CISCO‐IETF‐VPLS‐BGP‐EXT‐MIB .................................................................................................................................. 130


8

MIB Constraints ...................................................................................................................................................... 131

CISCO‐IETF‐VPLS‐GENERIC‐MIB ................................................................................................................................. 131

MIB Tables .............................................................................................................................................................. 131

MIB Constraints ...................................................................................................................................................... 132

CISCO‐IETF‐VPLS‐LDP‐MIB .......................................................................................................................................... 132

MIB Constraints ...................................................................................................................................................... 133

CISCO‐IF‐EXTENSION‐MIB .......................................................................................................................................... 133

MIB Tables .............................................................................................................................................................. 133

MIB Constraints ...................................................................................................................................................... 134

CISCO‐IP‐ADDRESS‐POOL‐MIB ................................................................................................................................... 136

MIB Objects ............................................................................................................................................................ 137

MIB Constraints ...................................................................................................................................................... 137

CISCO‐IP‐CBR‐METRICS‐MIB ...................................................................................................................................... 140

MIB Objects ............................................................................................................................................................ 140

MIB Constraints ...................................................................................................................................................... 140

CISCO‐IP‐TAP‐MIB ...................................................................................................................................................... 141

MIB Tables .............................................................................................................................................................. 141

MIB Constraints ...................................................................................................................................................... 142

CISCO‐IP‐STAT‐MIB .................................................................................................................................................... 142

MIB Tables .............................................................................................................................................................. 143

CISCO‐IPSEC‐MIB ........................................................................................................................................................ 143

MIB Objects ............................................................................................................................................................ 144

MIB Constraints ...................................................................................................................................................... 144

CISCO‐IPSEC‐FLOW‐MONITOR‐MIB ........................................................................................................................... 144

MIB Objects ............................................................................................................................................................ 145


9

CISCO‐LICENSE‐MGMT‐MIB ....................................................................................................................................... 147

MIB Constraints ...................................................................................................................................................... 149

CISCO‐MDI‐METRICS‐MIB .......................................................................................................................................... 150

MIB Objects ............................................................................................................................................................ 150

CISCO‐LPTS‐MIB ......................................................................................................................................................... 150

CISCO‐MEMORY‐POOL‐MIB ....................................................................................................................................... 151

CISCO‐MLD‐SNOOPING‐MIB ...................................................................................................................................... 151

MIB Objects ............................................................................................................................................................ 153

MIB Constraints ...................................................................................................................................................... 153

CISCO‐MPLS‐TE‐STD‐EXT‐MIB .................................................................................................................................... 154

CISCO‐NETSYNC‐MIB .................................................................................................................................................. 154

MIB Objects ............................................................................................................................................................ 155

MIB Constraints ...................................................................................................................................................... 155

CISCO‐NTP‐MIB .......................................................................................................................................................... 157

MIB Constraints ...................................................................................................................................................... 159

CISCO‐OAM‐MIB ........................................................................................................................................................ 160

MIB Objects ............................................................................................................................................................ 160

MIB Constraints ...................................................................................................................................................... 160

CISCO‐OTN‐IF‐MIB ...................................................................................................................................................... 160

MIB Objects ............................................................................................................................................................ 161

CISCO‐PTP‐MIB ........................................................................................................................................................... 163

MIB Objects ............................................................................................................................................................ 163

MIB Constraints ...................................................................................................................................................... 164

CISCO-P2P-IF-MIB .............................................................................................................................. 172

MIB Constraints ...................................................................................................................................................... 172


10

CISCO‐PIM‐MIB .......................................................................................................................................................... 173

CISCO‐PING‐MIB ......................................................................................................................................................... 173

MIB Constraints ...................................................................................................................................................... 173

CISCO‐PROCESS‐MIB .................................................................................................................................................. 174

CISCO‐RF‐MIB ............................................................................................................................................................. 174

MIB Constraints ...................................................................................................................................................... 176

CISCO‐RTP‐METRICS‐MIB ........................................................................................................................................... 177

MIB Objects ............................................................................................................................................................ 177

CISCO‐RTTMON‐MIB .................................................................................................................................................. 177

MIB Constraints ...................................................................................................................................................... 189

CISCO‐SELECTIVE‐VRF‐DOWNLOAD‐MIB ................................................................................................................... 191

MIB Tables .............................................................................................................................................................. 191

MIB Constraints ...................................................................................................................................................... 191

CISCO‐SONET‐MIB ...................................................................................................................................................... 192

MIB Tables .............................................................................................................................................................. 192

MIB Constraints ...................................................................................................................................................... 193

CISCO‐SUBSCRIBER‐SESSION‐MIB .............................................................................................................................. 194

MIB Tables .............................................................................................................................................................. 194

CISCO‐SYSLOG‐MIB .................................................................................................................................................... 195

MIB Constraints ...................................................................................................................................................... 196

CISCO‐SYSTEM‐MIB .................................................................................................................................................... 196

MIB Constraints ...................................................................................................................................................... 196

CISCO‐TAP2‐MIB ........................................................................................................................................................ 196

MIB Objects ............................................................................................................................................................ 197

MIB Constraints ...................................................................................................................................................... 197


11

CISCO‐TCP‐MIB ........................................................................................................................................................... 199

CISCO‐VPDN‐MGMT‐MIB ........................................................................................................................................... 200

MIB Objects ............................................................................................................................................................ 200

CISCO‐VLAN‐IFTABLE‐RELATIONSHIP‐MIB ................................................................................................................. 200

DISMAN‐EXPRESSION‐MIB ......................................................................................................................................... 201

MIB Tables .............................................................................................................................................................. 201

DOT3‐OAM‐MIB ......................................................................................................................................................... 201

MIB Tables .............................................................................................................................................................. 201

MIB Constraints ...................................................................................................................................................... 202

DS1‐MIB (RFC 2495) ................................................................................................................................................... 207

MIB Tables .............................................................................................................................................................. 207

MIB Constraints ...................................................................................................................................................... 209

DS3‐MIB ..................................................................................................................................................................... 210

MIB Tables .............................................................................................................................................................. 211

MIB Constraints ...................................................................................................................................................... 212

ENERGY‐OBJECT‐MIB ................................................................................................................................................. 213

ENTITY‐MIB (RFC 2737) .............................................................................................................................................. 213

MIB Tables .............................................................................................................................................................. 215

MIB Constraints ...................................................................................................................................................... 216

ENTITY‐STATE‐MIB ..................................................................................................................................................... 216

MIB Constraints ...................................................................................................................................................... 217

ETHERLIKE‐MIB (RFC 2665, 3635) .............................................................................................................................. 217

MIB Constraints ...................................................................................................................................................... 217

EVENT‐MIB ................................................................................................................................................................. 217

MIB Constraints ...................................................................................................................................................... 218


12

EXPRESSION‐MIB ........................................................................................................................................................ 218

FRAME‐RELAY‐DTE‐MIB ............................................................................................................................................. 220

MIB Constraints ...................................................................................................................................................... 220

IEEE8021‐CFM‐MIB .................................................................................................................................................... 222

MIB Objects ............................................................................................................................................................ 222

MIB Constraints ...................................................................................................................................................... 224

IEEE8023‐LAG‐MIB ..................................................................................................................................................... 225

MIB Constraints ...................................................................................................................................................... 226

IETF‐OSPF‐TRAP‐MIB .................................................................................................................................................. 228

MIB Objects ............................................................................................................................................................ 228

IETF‐TCP‐MIB .............................................................................................................................................................. 228

MIB Tables .............................................................................................................................................................. 228

IETF‐UDP‐MIB ............................................................................................................................................................. 229

MIB Tables .............................................................................................................................................................. 229

IF‐MIB (RFC 2863) ...................................................................................................................................................... 229

MIB Tables .............................................................................................................................................................. 229

MIB Constraints ...................................................................................................................................................... 231

IMA‐MIB ..................................................................................................................................................................... 231

MIB Objects ............................................................................................................................................................ 232

MIB Constraints ...................................................................................................................................................... 232

IP‐FORWARD‐MIB ...................................................................................................................................................... 233

MIB Constraints ...................................................................................................................................................... 233

IP‐MIB ......................................................................................................................................................................... 235

MIB Tables .............................................................................................................................................................. 235

MIB Constraints ...................................................................................................................................................... 236


13

IPV6‐MIB .................................................................................................................................................................... 238

MIB Tables .............................................................................................................................................................. 238

MIB Constraints ...................................................................................................................................................... 240

IPV6‐FORWARD‐MIB .................................................................................................................................................. 242

MIB Objects ............................................................................................................................................................ 242

MIB Constraints ...................................................................................................................................................... 242

IPV6‐MLD‐MIB ............................................................................................................................................................ 244

MIB Objects ............................................................................................................................................................ 244

MIB Constraints ...................................................................................................................................................... 244

IPV6‐TC ....................................................................................................................................................................... 244

ISIS‐MIB ...................................................................................................................................................................... 244

MIB Constraints ...................................................................................................................................................... 248

MAU‐MIB ................................................................................................................................................................... 253

MIB Constraints ...................................................................................................................................................... 253

MEF‐SOAM‐PM‐MIB .................................................................................................................................................. 254

MIB Objects ............................................................................................................................................................ 254

MIB Constraints ...................................................................................................................................................... 255

MFR‐MIB .................................................................................................................................................................... 256

MIB Objects ............................................................................................................................................................ 256

MIB Constraints ...................................................................................................................................................... 257

MGMD‐STD‐MIB ........................................................................................................................................................ 258

MIB Objects ............................................................................................................................................................ 259

MIB Constraints ...................................................................................................................................................... 259

MPLS‐L3VPN‐STD‐MIB ............................................................................................................................................... 261

MIB Constraints ...................................................................................................................................................... 261


14

MPLS‐LDP‐GENERIC‐STD‐MIB .................................................................................................................................... 263

MIB Constraints ...................................................................................................................................................... 264

MPLS‐LDP‐STD‐MIB .................................................................................................................................................... 264

MIB Constraints ...................................................................................................................................................... 265

MPLS‐LSR‐STD‐MIB .................................................................................................................................................... 266

MIB Constraints ...................................................................................................................................................... 269

MPLS‐TC‐STD‐MIB ...................................................................................................................................................... 270

MPLS‐TE‐STD‐MIB ...................................................................................................................................................... 270

MIB Constraints ...................................................................................................................................................... 273

NOTIFICATION‐LOG‐MIB ............................................................................................................................................ 275

OSPF‐MIB ................................................................................................................................................................... 277

MIB Tables .............................................................................................................................................................. 277

MIB Constraints ...................................................................................................................................................... 279

OSPF‐TRAP‐MIB .......................................................................................................................................................... 280

OSPFV3‐MIB ............................................................................................................................................................... 280

MIB Constraints ...................................................................................................................................................... 281

PIM‐MIB ..................................................................................................................................................................... 283

MIB Objects ............................................................................................................................................................ 284

MIB Constraints ...................................................................................................................................................... 285

RADIUS‐ACC‐CLIENT‐MIB ........................................................................................................................................... 285

RADIUS‐AUTH‐CLIENT‐MIB ........................................................................................................................................ 285

RFC1213‐MIB ............................................................................................................................................................. 286

MIB Objects ............................................................................................................................................................ 286

RFC 2011‐MIB ............................................................................................................................................................. 286

MIB Objects ............................................................................................................................................................ 287


15

MIB Constraints ...................................................................................................................................................... 287

RFC 2465‐MIB ............................................................................................................................................................. 287

MIB Objects ............................................................................................................................................................ 288

MIB Constraints ...................................................................................................................................................... 288

RSVP‐MIB ................................................................................................................................................................... 289

MIB Constraints ...................................................................................................................................................... 289

SNMP‐COMMUNITY‐MIB (RFC 2576) ......................................................................................................................... 292

SNMP‐FRAMEWORK‐MIB (RFC 2571) ........................................................................................................................ 292

SNMP‐NOTIFICATION‐MIB (RFC 2573) ....................................................................................................................... 292

SNMP‐TARGET‐MIB (RFC 2573) ................................................................................................................................. 292

SNMP‐USM‐MIB (RFC 2574) ...................................................................................................................................... 293

SNMPv2‐MIB (RFC 1907) ............................................................................................................................................ 293

SNMP‐VACM‐MIB ...................................................................................................................................................... 293

SONET‐MIB (RFC 2558) .............................................................................................................................................. 293

MIB Tables .............................................................................................................................................................. 294

MIB Constraints ...................................................................................................................................................... 294

TCP‐MIB ...................................................................................................................................................................... 295

MIB Constraints ...................................................................................................................................................... 296

UDP‐MIB ..................................................................................................................................................................... 296

MIB Constraints ...................................................................................................................................................... 297

VRRP‐MIB ................................................................................................................................................................... 298

MIB Constraints ...................................................................................................................................................... 298

Chapter 4 - Monitoring Notifications ................................................................................................. 299

SNMP Notification Overview ..................................................................................................................................... 299

Enabling Notifications ................................................................................................................................................ 300


16

Cisco SNMP Notifications ........................................................................................................................................... 300

Environmental or Functional Notifications ................................................................................................................ 301

Flash Card Notifications ............................................................................................................................................. 303

Interface Notifications ............................................................................................................................................... 303

Routing Protocol Notifications ................................................................................................................................... 303

Redundancy Framework Notifications ....................................................................................................................... 304

Netsync Notifications ................................................................................................................................................. 305

Subscriber Session Notifications ................................................................................................................................ 305

Appendix 1 - Using MIBs ..................................................................................................................... 306

Cisco Redundancy Features ....................................................................................................................................... 307

Levels of Redundancy ............................................................................................................................................ 307

Verifying the Cisco ASR 9000 Series Router Redundancy ...................................................................................... 308

Managing Physical Entities ......................................................................................................................................... 308

Purpose and Benefits ............................................................................................................................................. 310

Performing Inventory Management ...................................................................................................................... 310

Monitoring and Configuring FRU Status ................................................................................................................ 318

Generating SNMP Notifications ............................................................................................................................. 318

Monitoring Quality of Service .................................................................................................................................... 320

Cisco ASR 9000 Series Router QoS Basics .............................................................................................................. 321

CISCO‐CLASS‐BASED‐QOS‐MIB Overview .............................................................................................................. 321

Viewing QoS Configuration Settings Using the CISCO‐CLASS‐BASED‐QOS‐MIB .................................................... 323

Monitoring QoS Using the CISCO‐CLASS‐BASED‐QOS‐MIB .................................................................................... 324

Considerations for Processing QoS Statistics ......................................................................................................... 325

Sample QoS Applications ....................................................................................................................................... 328

Monitoring Router Interfaces .................................................................................................................................... 331


17

Billing Customers for Traffic ....................................................................................................................................... 332

Input and Output Interface Counts ........................................................................................................................ 332

Determining the Amount of Traffic to Bill to a Customer ...................................................................................... 333

Scenario for Demonstrating QoS Traffic Policing ................................................................................................... 333

Using IF‐MIB Counters ............................................................................................................................................... 337

Sample Counters .................................................................................................................................................... 339

Appendix 2 - QoS MIB Implementation .............................................................................................. 340

Implementing the CISCO‐CLASS‐BASED‐QOS‐MIB ..................................................................................................... 340

QoS MIB Policy Action Support Matrix ...................................................................................................................... 345

Glossary ............................................................................................................................................... 356

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Preface

18

Preface This guide describes the implementation of the Simple Network Management Protocol (SNMP) and Management Information Base (MIB) for Cisco ASR 9000 Series Aggregation Services Routers. SNMP provides a set of commands for setting and retrieving the values of operating parameters on the Cisco ASR 9000 Series router. The router information is stored in a virtual storage area called a Management Information Base (MIB), which contains many MIB objects that describe router components and provides information about the status of the components. This preface provides an overview of this guide with the following sections:

■ Revision History

■ Audience

■ Organization

■ Terminology and Definitions

■ Obtaining Documentation and Submitting a Service Request

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

Cisco IOS XR Release Part Number/Date of Change

Summary

6.1.4 October 2017 Updated with Cisco IOS XR Release 6.1.4. CISCO-RTTMON-MIB Tables and Descriptions was updated to include support for rttMonStatsCollectTable and rttMonLatestJitterOperTable.

All Releases October 2016 The following MIBS are updated:

IEEE8021-CFM-MIB

MEF-SOAM-PM-MIB

5.3.2 - Updated with Cisco IOS XR Release 5.3.2. CISCO-FLOW-MONITOR-MIB

The following MIBS are added: CISCO-MDI-METRICS-MIB

CISCO-RTP-METRICS-MIB


19

5.2.0 OL-29006-05Updated with Cisco IOS XR Release 5.2.0 MIB

implementation.

The following MIBS are added: Energy Monitoring MIB

LPTS MIB

Y.1731 Performance Monitoring MIB

5.1.2 OL-29006-04Updated with Cisco IOS XR Release 5.1.2 CFM MIB

enhancement information. 5.1.1 OL-29006-03

Updated with Cisco IOS XR Release 5.1.0 and Cisco IOS

XR Release 5.1.1 MIB support information.4.3.1 OL-29006-02

June 2013

Audience This guide is intended for system and network administrators who must configure the Cisco ASR 9000 Series router for operation and monitor its performance in the network. This guide may also be useful for application developers who are developing management applications for the Cisco ASR 9000 Series router.

Organization This guide contains the following chapters:

Chapter DescriptionChapter 1, “Chapter 1 - Cisco ASR 9000 Series Routers MIB Overview”

Provides background information about SNMP and its implementation on the Cisco ASR 9000 Series router.

Chapter 2, “Chapter 2 - Configuring MIB Support”

Provides instructions for configuring SNMP management support on the Cisco ASR 9000 Series router.

Chapter 3, “Cisco ASR 9000 Series Routers MIB Specifications”

Describes each MIB included on the Cisco ASR 9000 Series router. Each description lists any constraints as to how the MIB is implemented on the router.

Chapter 4, “Monitoring Notifications” Describes the SNMP notifications supported by the Cisco ASR 9000 Series router, provides a description of each notification, a probable cause, and recommended action to take.

Appendix 1, “Using MIBs” Provides information about how to use SNMP to perform system functions such as bulk-file retrieval and Quality of Service (QoS).

Appendix 2, “QoS MIB Implementation” Provides information about how to implement Quality of Service (QoS) in addition to a matrix that defines which


20

objects support QoS policy actions.

Terminology and Definitions This section discusses conventions and terminology used in this guide. Alarm—In SNMP, the word alarm is commonly misused to mean the same as a trap (see the Trap definition below).

Alarm represents a condition which causes an SNMP trap to be generated.

Note: Many commands use the word traps in the command syntax. Unless there is an option in the command to select traps. Use the snmp-server host and snmp-server notification command to specify whether to send SNMP notifications as traps.

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

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

MIB-II—The successor to MIB-I, which was the original standard SNMP MIB.

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

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

Trap—A device-initiated SNMP notification message. The contents of the message might be simply informational, but it is mostly used to report real-time trap information. Traps can be used in conjunction with other SNMP mechanisms, as in trap-directed polling.

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

Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Chapter 1 - Cisco ASR 9000 Series Routers MIB Overview

21

Chapter 1 - Cisco ASR 9000 Series Routers MIB Overview

This chapter provides an overview of the Cisco ASR 9000 Series router management feature. This chapter contains the following topics: Benefits of MIB Enhancements, page 21

SNMP Overview, page 21

Object Identifiers, page 25

Benefits of MIB Enhancements The Cisco ASR 9000 Series router management feature allows the router to be managed through the Simple Network Management Protocol (SNMP). Using the Cisco ASR 9000 Series router management feature, you can:

Manage and monitor the Cisco ASR 9000 Series router resources through an SNMP-based Network Management

System (NMS)

Use SNMP set and get requests to access information in Cisco ASR 9000 Series router MIBs

Reduce the amount of time and system resources required to perform functions such as inventory management

Other benefits include: A standards-based technology (SNMP) for monitoring faults and performance on the router

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

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

A way to access router information other than through the Command-Line Interface (CLI) or Extensible Markup Language (XML).

SNMP Overview The Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a standardized framework and a common language used for monitoring and managing devices in a network. The SNMP framework has three parts: SNMP manager—A system used to control and monitor the activities of network hosts using SNMP. The most

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

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


22

Management Information Base (MIB)— A MIB is a database of objects that can be managed on a device. This database describes various components and provides information about the attributes of the components of a network device.

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

MIB Description A MIB is a database of the objects that can be managed on a device. The managed objects or variables can be set or read to provide information on the network devices and interfaces and are organized hierarchically. The MIB consists of collections of managed objects identified by object identifiers. MIBs are accessed using a network management protocol such as SNMP. A managed object (sometimes called a MIB object or an object) is one of a number of characteristics of a managed device, such as a router. Managed objects comprise one or more object instances, which are essentially variables. The Cisco implementation of SNMP uses the definitions of MIB II variables described in RFC 1213. MIBs contain two types of managed objects:

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

MIB).

Columnar objects—Define multiple related objects such as zero, one, or more instances at any point in time that are grouped together in MIB tables (for example, ifTable in the IF-MIB defines the interface).

System MIB variables are accessible through SNMP as follows: Accessing a MIB variable—Function is initiated by the SNMP agent in response to a request from the NMS. The agent

retrieves the value of the requested MIB variable and responds to the NMS with that value.

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

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

An interface or card starts or stops running

Temperature thresholds are crossed

Authentication failures occur

When an agent detects an alarm condition, the agent:

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

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

SNMP notifications are sent as one of the following: Traps—Unreliable messages, which do not require receipt acknowledgment from the SNMP manager.

The Cisco implementation of SNMP uses the definitions of SNMP traps described in RFC 1215. When an agent detects an alarm condition, it logs information about the time, type, and severity of the condition and


23

generates a notification message, which it then sends to a designated IP host. A SNMP notification is sent as traps. See the “Enabling Notifications” for instructions on how to enable notifications and traps on the Cisco ASR 9000 Series router. Use the snmp-server host command to specify that SNMP notifications are sent as traps. See Chapter 4, “Monitoring Notifications,” for information about Cisco ASR 9000 Series router traps.

SNMP Versions Cisco IOS XR Software supports the following versions of SNMP:

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

on community strings.

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

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

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

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

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

SNMPv1 and SNMPv2c Both SNMPv1 and SNMPv2c use a community-based form of security. The community of managers who are able to access the agent MIB is defined by an IP address access control list and password. SNMPv2c support includes a bulk-retrieval mechanism and more detailed error message reporting to management stations. The bulk-retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trip transmissions required. SNMPv2c improved error-handling support includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes report the error type. Three kinds of exceptions are also reported: No such object

No such instance

End of MIB view

SNMPv3 SNMPv3 provides security models and security levels: A security model is an authentication strategy that is set up for a user and the group in which the user resides.

A security level is the permitted level of security within a security model.

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

SNMP Security Models and Levels

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


24

Table 1-1 SNMP Security Models and Levels

Model Level Authentication Encryption Description

v1 noAuthNoPriv Community No Uses match on community string for

string authentication.

v2c noAuthNoPriv Community No Uses match on community string for

string authentication.

v3 noAuthNoPriv User name No Uses match on user name for

authentication.

authNoPriv MD5 or SHA No Provides authentication based on

HMAC-MD5 or HMAC-SHA

algorithm.

authPriv MD5 or SHA DES Provides authentication based on

HMAC-MD5 or HMAC-SHA

algorithm. Also provides DES 56-bit

encryption based on CBC-DES

(DES-56) standard.

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

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


25

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

Object Identifiers An object identifier (OID) uniquely identifies a MIB object on a managed network device. The OID identifies the MIB object’s location in the MIB hierarchy, and provides a means of accessing the MIB object in a network of managed devices: Standard RFC MIB OIDs are assigned by the Internet Assigned Numbers Authority (IANA).

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

Each number in the OID corresponds to a level of MIB hierarchy. For example, the OID 1.3.6.1.4.1.9.9.xyz represents the.xyz with the location in the MIB hierarchy as follows. Note that the numbers in parentheses are included to help show correspondence to the MIB hierarchy. In actual use, OIDs are represented as numerical values only. iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cisco(9).ciscoMgt(9).nn-MIB You can uniquely identify a managed object, such as ifNumber in the IF-MIB, by its object name (iso.org.dod.internet.mgmt.enterprises.interfaces.ifNumber) or by its OID (1.3.6.1.2.1.2.1). For a list of OIDs assigned to MIB objects, go to the following URL: ftp://ftp.cisco.com/pub/mibs/oid/

SNMP Configuration Information The following references provide information about configuring SNMP:

Implementing SNMP module provides general information about configuring and implementing SNMP support. It is

part of the Cisco IOS XR System Management Configuration Guide.

SNMP Server Commands module provides information about SNMP commands. It is part of the

Cisco IOS XR System Management Command Reference.

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Chapter 2 - Configuring MIB Support

26

Chapter 2 - Configuring MIB Support This chapter describes how to configure SNMP and MIB support for the Cisco ASR 9000 Series router. It includes the following sections: Downloading and Compiling MIBs, page 26

Enabling SNMP Support, page 27

Downloading and Compiling MIBs The following sections provide information about how to download and compile MIBs for the Cisco ASR 9000 Series router: Considerations for Working with MIBs, page 26

Downloading MIBs, page 27

Compiling MIBs, page 27

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

Mismatches on datatype definitions might cause compiler errors or warning messages. Although Cisco MIB datatype

definitions are not mismatched, some standard RFC MIBs do mismatch, as in the following example:

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

This example is considered to be a trivial error and the MIB loads successfully with a warning message. The following example is considered as a nontrivial error (even though the two definitions are essentially equivalent), and the MIB is not successfully parsed: MIB A defines: SomeDatatype ::= DisplayString MIB B defines: SomeDatatype ::= OCTET STRING (SIZE(0..255)) If your MIB compiler treats these as errors, or you want to delete the warning messages, edit one of the MIBs that define this same datatype so that the definitions match.

Many MIBs import definitions from other MIBs. If your management application requires MIBs to be loaded, and you

experience problems with undefined objects, you might want to load the following MIBs in this order:

1. SNMPv2-SMI.my

2. SNMPv2-TC.my

3. SNMPv2-MIB.my

4. IF-MIB.my


27

5. CISCO-SMI.my

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

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

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

1. Review the considerations in the “Considerations for Working with MIBs” section.

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

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

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

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

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

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

— http://www.ietf.org

— http://www.ipmplsforum.org

Compiling MIBs If you plan to integrate the Cisco ASR 9000 Series router with an SNMP-based management application, then you must compile the MIBs for that platform. For example, if you are running HP OpenView on a UNIX operating system, you must compile Cisco ASR 9000 Series router MIBs with the HP OpenView Network Management System (NMS).

Enabling SNMP Support The following procedure summarizes how to configure the Cisco ASR 9000 Series router for SNMP support. For detailed information about SNMP commands, go to the following URL: Implementing SNMP module provides general information about configuring and implementing SNMP support. It is

part of the Cisco IOS XR System Management Configuration Guide.

SNMP Server Commands provides information about SNMP commands. It is part of the Cisco IOS XR System Management Command Reference.

To configure the Cisco ASR 9000 Series router for SNMP support, follow these steps:

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


28

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

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

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

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

2. Identify (by IP address) the host to receive SNMP notifications from the router:

Router (config)# snmp-server host host

3. Configure the router to generate notifications. You can use keywords to limit the number and types of messages generated. Router (config)# snmp-server traps [notification-type] [notification-option]

For information about how to configure SNMP community strings, refer the SNMP Server Commands module in the Cisco IOS XR System Management Command Reference.

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Chapter 3 - Cisco ASR 9000 Series Routers MIB Specifications

29

Chapter 3 - 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

Cisco ASR 9000 Series Routers MIB Categories

MIB Version String Description

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 on page 26.

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

Unsupported MIBs

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


30

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.

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


31

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 mibd process Supported Unsupported Not in Image

ATM-MIB 1 mibd-interface Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3

9810191200Z

9810191200Z

9810191200Z

9810191200Z

9810191200Z

ATM-FORUM-MIB 1 Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3

— Revision not available Revision not available

Revision not available



ATM2-MIB 1 mibd-interface Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3

200309230000Z

200309230000Z

200309230000Z

200309230000Z

200309230000Z

BGP4-MIB mibd-route Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3

RFC 4273 RFC 4273

RFC 4273

RFC 4273

RFC 4273

BRIDGE-MIB 1 mibd-interface Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3

RFC 4188 RFC 4188

RFC 4188

RFC 4188

RFC 4188

CISCO-AAA-SERVER-MIB 1

mibd-interface

Release 3.7 Release 3.9


32

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

MIB mibd process Supported Unsupported Not in Image Release 4.0

Release 4.2

Release 4.3 200311170000Z

CISCO-ATM-EXT-MIB 1 mibd-interface Release 3.7 200301060000Z

Release 3.9 200301060000Z

Release 4.0 200301060000Z Release 4.2 200301060000Z

Release 4.3 200301060000Z

CISCO-ATM-QOS-MIB 1 mibd-interface Release 3.7 200206100000Z

Release 3.9 200206100000Z

Release 4.0 200206100000Z

Release 4.2 200206100000Z

Release 4.3 200206100000Z

CISCO-BGP4-MIB mibd-route Release 3.7 200302240000Z

Release 3.9 200302240000Z

Release 4.0 200302240000Z

Release 4.2 200302240000Z

Release 4.3 200302240000Z

CISCO-BGP-POLICY-ACCOUNTING-MIB

mibd-interface

Release 3.7 200207260000Z

Release 3.9 200207260000Z

Release 4.0 200207260000Z

Release 4.2 200207260000Z

Release 4.3 200207260000Z

CISCO-BULK-FILE-MIB 1 mibd-infra Release 3.7 200206100000Z Release 3.9 200206100000Z

Release 4.0 200206100000Z

Release 4.2 200207260000Z

Release 4.3 200206100000Z


33


MIB mibd process Supported Unsupported Not in Image CISCO-CDP-MIB mibd-interface

Release 3.7 9812100000Z

Release 3.9 9812100000Z

Release 4.0 9812100000Z

Release 4.2 9812100000Z

Release 4.3 9812100000Z

CISCO-CLASS-BASED-QOS- MIB 1

mibd-interface

Release 3.7 200901260000Z

Release 3.9 200901260000Z

Release 4.0 200901260000Z

Release 4.2 200901260000Z

Release 4.3 200901260000Z

CISCO-CONFIG-COPY-MIB mibd-infra Release 3.7 200504060000Z

Release 3.9 200504060000Z

Release 4.0 200504060000Z

Release 4.2 200504060000Z

Release 4.3 200504060000Z

CISCO-CONFIG-MAN-MIB mibd-infra Release 3.7 200704270000Z

Release 3.9 200704270000Z

Release 4.0 200704270000Z

Release 4.2 200704270000Z

Release 4.3 200704270000Z

CISCO-CONTEXT-MAP- PING-MIB

mibd-infra

Release 3.7 200811220000Z

Release 3.9 200811220000Z

Release 4.0 200811220000Z

Release 4.2 200811220000Z

Release 4.3 200811220000Z

CISCO-DS3-MIB 1 mibd-interface Release 3.7 200205210000Z

Release 3.9 200205210000Z


34


MIB mibd process Supported Unsupported Not in Image Release 4.0 200205210000Z Release 4.2 200205210000Z Release 4.3 200205210000Z

CISCO-ENHANCED-IMAGE- MIB 1

mibd-entity

Release 3.7 200501060000Z Release 3.9 200501060000Z Release 4.0 200501060000Z Release 4.2 200501060000Z Release 4.3 200501060000Z

CISCO-ENHANCED-MEM- POOL-MIB 1

mibd-entity


CISCO-ENTITY-ASSET-MIB1 mibd-entity Release 3.7 200309180000Z Release 3.9 200309180000Z Release 4.0 200309180000Z Release 4.2 200309180000Z Release 4.3 200309180000Z

CISCO-ENTITY-FRU-CONTROL-MIB 1

mibd-entity

Release 3.7 200810080000Z Release 3.9 200810080000Z Release 4.0 200810080000Z Release 4.2 200810080000Z

CISCO-ENTITY-REDUNDANCY-MIB 1

mibd-entity

Release 3.7 Release 3.9 Release 4.0 Release 4.2 Release 4.3 200510010000Z

CISCO-ENTITY-SENSOR-MIB 1

mibd-entity


35


MIB mibd process Supported Not in Image Not in Image Release 3.7 200711120000Z Release 3.9 200711120000Z Release 4.0 200711120000Z Release 4.2 200711120000Z Release 4.3 200711120000Z

CISCO-ENTITY-STATE-EXT- MIB1

mibd-infra


CISCO-FLASH-MIB 1 mibd-infra Release 3.7 200906030000Z Release 3.9 200906030000Z Release 4.0 200906030000Z Release 4.2 200906030000Z Release 4.3 200906030000Z

CISCO-FLOW-CLONE-MIB mibd-entity Release 3.7 201010190000Z Release 3.9 201010190000Z Release 4.0 201010190000Z Release 4.2 201010190000Z Release 4.3 201010190000Z

CISCO-FLOW-MONITOR-MIB

mibd-entity

Release 3.7 201104190000Z Release 3.9 201104190000Z Release 4.0 201104190000Z Release 4.2 201104190000Z Release 4.3 Release 5.3.2

201104190000Z

CISCO-FRAME-RELAY-MIB 1 mibd-interface Release 3.7 200010130000Z Release 3.9 200010130000Z Release 4.0 200010130000Z Release 4.2 200010130000Z


36


MIB mibd process Supported Unsupported Not in Image Release 4.3 200010130000Z

CISCO-FTP-CLIENT-MIB1 mibd-infra Release 3.7 200603310000Z Release 3.9 200603310000Z

Release 4.0 200603310000Z

Release 4.2 200603310000Z

Release 4.3 200603310000Z

CISCO-HSRP-EXT-MIB mibd-interface Release 3.7 9808030000Z

Release 3.9 9808030000Z

Release 4.0 9808030000Z

Release 4.2 9808030000Z

Release 4.3 9808030000Z

CISCO-HSRP-MIB mibd-interface Release 3.7 9808030000Z

Release 3.9 9808030000Z

Release 4.0 9808030000Z

Release 4.2 9808030000Z

Release 4.3 9808030000Z

CISCO-IETF-BFD-MIB mibd-route Release 3.7 200804240000Z

Release 3.9 200804240000Z

Release 4.0 200804240000Z

Release 4.2 200804240000Z

Release 4.3 200804240000Z

CISCO-IETF-FRR-MIB mibd-route Release 3.7 200804291200Z

Release 3.9 200804291200Z

Release 4.0 200804291200Z

Release 4.2 200804291200Z

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

mibd-interface

Release 3.7 200909300000Z

Release 3.9 200909300000Z


37



Release 4.2 200909300000Z

Release 4.3 200909300000Z

CISCO-IETF-IPMROUTE-MIB mibd-interface Release 3.7 200608240000Z

Release 3.9 200608240000Z

Release 4.0 200608240000Z

Release 4.2 200608240000Z

Release 4.3 200608240000Z

CISCO-IETF-MSDP-MIB mibd-interface Release 3.7 200605190000Z

Release 3.9 200605190000Z

Release 4.0 200605190000Z

Release 4.2 200605190000Z

Release 4.3 200605190000Z

CISCO-IETF-PIM-MIB — Release 3.7 200502220000Z

Release 3.9 200502220000Z

Release 4.0 200502220000Z

Release 4.2 200502220000Z

CISCO-IETF-PIM-EXT-MIB mibd-interface Release 3.7 200608250000Z

Release 3.9 200608250000Z

Release 4.0 200608250000Z

Release 4.2 200608250000Z

Release 4.3 200608250000Z

CISCO-IETF-PW-MIB mibd-interface Release 3.7 200512200000Z

Release 3.9 200512200000Z

Release 4.0 200512200000Z

Release 4.2 200512200000Z

Release 4.3 200512200000Z


38


MIB mibd process Supported Unsupported Not in Image CISCO-IETF-PW-ENET-MIB mibd-inter face

Release 3.7 200209221200Z

Release 3.9 200209221200Z

Release 4.0 200209221200Z

Release 4.2 200209221200Z

Release 4.3 200209221200Z

CISCO-IETF-PW-FR-MIB mibd-interface

Release 3.7 200312160000Z

Release 3.9 200312160000Z

Release 4.0 200312160000Z

Release 4.2 200312160000Z

Release 4.3 200312160000Z

CISCO-IETF-PW-MPLS-MIB mibd-interface

Release 3.7 200302261200Z

Release 3.9 200302261200Z

Release 4.0 200302261200Z

Release 4.2 200302261200Z

Release 4.3 200302261200Z

CISCO-IETF-VPLS-BGP-EXT-MIB mibd-interface

Release 3.7 200810240000Z

Release 3.9 200810240000Z

Release 4.0 200810240000Z

Release 4.2 200810240000Z

Release 4.3 200810240000Z

CISCO-IETF-VPLS-GENERIC- MIB1 mibd-interface

Release 3.7 200710221200Z

Release 3.9 200710221200Z

Release 4.0 200710221200Z

Release 4.2 200710221200Z

Release 4.3 200710221200Z

CISCO-IETF-VPLS-LDP-MIB1 mibd-interface Release 3.7 200711221200Z


39


MIBS mibd process Supported Unsupported Not in Image Release 3.9 200711221200Z

Release 4.0 200711221200Z

Release 4.2 200711221200Z

Release 4.3 200711221200Z

CISCO-IF-EXTENSION-MIB1 mibd-interface

Release 3.7 200707230000Z

Release 3.9 200707230000Z

Release 4.0 200707230000Z

Release 4.2 200707230000Z

Release 4.3 200707230000Z

CISCO-IP-ADDRESS-POOL-MIB mibd-interface Release 4.3.0 201006070000Z

CISCO-IP-CBR-METRICS-MIB mibd-interface

Release 3.7 200906110000Z

Release 3.9 200906110000Z

Release 4.0 200906110000Z

Release 4.2 200906110000Z

Release 4.3 200906110000Z

CISCO-IP-TAP-MIB mibd-interface Release 3.7 200403110000Z

Release 3.9 200403110000Z

Release 4.0 200403110000Z

Release 4.2 200403110000Z

Release 4.3 200403110000Z

CISCO-IP-STAT-MIB mibd-interface Release 3.7 200112202300Z

Release 3.9 200112202300Z

Release 4.0 200112202300Z

Release 4.2 200112202300Z

Release 4.3 200112202300Z

CISCO-IPSEC-MIB Release 3.7 mibd-interface 200008071139Z


40



Release 3.9 200008071139Z

Release 4.0 200008071139Z

Release 4.2 200008071139Z

Release 4.3 200008071139Z

CISCO-IPSEC-FLOW-MONITOR-MIB

mibd-interface

Release 3.7 200710240000Z

Release 3.9 200710240000Z

Release 4.0 200710240000Z

Release 4.2 200710240000Z

Release 4.3 200710240000Z

CISCO-LICENSE-MGMT-MIB mibd-infra

Release 3.7 200107310000Z

Release 3.9 200107310000Z

Release 4.0 200107310000Z

Release 4.2 200107310000Z

Release 4.3 200107310000Z

CISCO-MDI-METRICS-MIB Release

— 200911020000Z $

CISCO-MLD-SNOOPING-MIB mibd-interface Release 3.7 201007020000Z

Release 3.9 201007020000Z

Release 4.0 201007020000Z

Release 4.2 201007020000Z

Release 4.3 201007020000Z

CISCO-NETSYNC-MIB mibd-interface Release 3.7

Release 3.9

Release 4.0

Release 4.2

Release 4.3 201010150000Z

CISCO-NTP-MIB mibd-interface Release 3.7 200607310000Z

Release 3.9 200607310000Z

Release 4.0 200607310000Z


41



Release 4.3 200607310000Z

CISCO-OAM-MIB Release 3.7 mibd-interface 200602170000Z

Release 3.9 200602170000Z

Release 4.0 200602170000Z

Release 4.2 200602170000Z

Release 4.3 200602170000Z

CISCO-PTP-MIB mibd-interface

Release 3.7

Release 3.9

Release 4.0

Release 4.2

Release 4.3 201101280000Z

CISCO-P2P-IF-MIB mibd-interface

Release 3.7 200808120000Z

Release 3.9 200808120000Z

Release 4.0 200808120000Z

Release 4.2 200808120000Z

Release 4.3 200808120000Z

CISCO-PIM-MIB mibd-interface Release 3.7 200011020000Z

Release 3.9 200011020000Z

Release 4.0 200011020000Z

Release 4.2 200011020000Z

Release 4.3 200011020000Z

CISCO-PING-MIB mibd-route Release 3.7 200108280000Z

Release 3.9 200108280000Z

Release 4.0 200108280000Z

Release 4.2 200108280000Z

Release 4.3 200108280000Z

CISCO-PROCESS-MIB 1 mibd-entity


42



Release 3.9 200910120000Z

Release 4.0 200910120000Z

Release 4.2 200910120000Z

Release 4.3 200910120000Z

CISCO-RF-MIB 1 mibd-infra Release 3.7 200803180000Z Release 3.9 200803180000Z

Release 4.0 200803180000Z

Release 4.2 200803180000Z

Release 4.3 200803180000Z

CISCO-RTP-METRICS-MIB Release

— 200906170000Z $

CISCO-SELECTIVE- VRF-DOWNLOAD-MIB

mibd-entity

Release 3.7 200803240000Z

Release 3.9 200803240000Z

Release 4.0 200803240000Z

Release 4.2 200803240000Z

Release 4.3 200803240000Z

CISCO-SELEC-MIB mibd-infra Release 3.7 201106220000Z

Release 3.9 201106220000Z

Release 4.0 201106220000Z

Release 4.2 201106220000Z

Release 4.3 201106220000Z

CISCO-SONET-MIB1 mibd-interface Release 3.7 200303070000Z

Release 3.9 200303070000Z

Release 4.0 200303070000Z

Release 4.2 200303070000Z

Release 4.3 200303070000Z

CISCO-SUBSCRIBER-SESSION-MIB

mibd-infra

Release 3.7 Release 3.9 Release 4.0 Release 4.2


43



Release 4.3 201208080000Z

CISCO-SYSLOG-MIB mibd-infra

Release 3.7 200512030000Z

Release 3.9 200512030000Z

Release 4.0 200512030000Z

Release 4.2 200512030000Z

Release 4.3 200512030000Z

CISCO-SYSTEM-MIB mibd-infra

Release 3.7 200709160000Z

Release 3.9 200709160000Z

Release 4.0 200709160000Z

Release 4.2 200709160000Z

Release 4.3 200709160000Z

CISCO-TAP2-MIB mibd-route

Release 3.7 200809100000Z

Release 3.9 200809100000Z

Release 4.0 200809100000Z

Release 4.2 200809100000Z

Release 4.3 200809100000Z

CISCO-TCP-MIB mibd-route

Release 3.7 200111120000Z

Release 3.9 200111120000Z

Release 4.0 200111120000Z

Release 4.2 200111120000Z

Release 4.3 200111120000Z

CISCO-VPDN-MGMT-MIB mibd-interface

Release 3.7

Release 3.9

Release 4.0

Release 4.2

Release 4.3 200906160000Z

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB mibd-interface

Release 3.7 9904010530Z

Release 3.9 9904010530Z

Release 4.0 9904010530Z


44


MIB mibd process Supported Unsupported Not in Image Release 4.2 9904010530Z Release 4.3 9904010530Z

DISMAN-EXPRESSION-MIB mibd-interface Release 3.7 200010160000Z Release 3.9 200010160000Z Release 4.0 200010160000Z Release 4.2 200010160000Z Release 4.3 200010160000Z

DOT3-OAM-MIB mibd-interface Release 3.7 200706140000Z Release 3.9 200706140000Z Release 4.0 200706140000Z Release 4.2 200706140000Z Release 4.3 200706140000Z

DS1-MIB (RFC 2495) 1 mibd-interface Release 3.7 9808011830Z Release 3.9 9808011830Z Release 4.0 9808011830Z Release 4.2 9808011830Z Release 4.3 9808011830Z

DS3-MIB 1 mibd-interface Release 3.7 200205210000Z Release 3.9 200205210000Z Release 4.0 200205210000Z Release 4.2 200205210000Z Release 4.3 200205210000Z

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

ENTITY-STATE-MIB mibd-entity


45



Release 3.7 200511220000Z

Release 3.9 200511220000Z

Release 4.0 200511220000Z

Release 4.2 200511220000Z

Release 4.3 200511220000Z

ETHERLIKE-MIB (RFC 2665, 3635) mibd-entity

Release 3.7 200309190000Z

Release 3.9 200309190000Z

Release 4.0 200309190000Z

Release 4.2 200309190000Z

Release 4.3 200309190000Z

EVENT-MIB mibd-infra

Release 3.7 RFC 2981





EXPRESSION-MIB mibd-infra

Release 3.7 200511240000Z

Release 3.9 200511240000Z

Release 4.0 200511240000Z

Release 4.2 200511240000Z

Release 4.3 200511240000Z

FRAME-RELAY-DTE-MIB1 mibd-interface

Release 3.7 9705010229Z

Release 3.9 9705010229Z

Release 4.0 9705010229Z

Release 4.2 9705010229Z

Release 4.3 9705010229Z

IEEE8021-CFM-MIB mibd-interface

Release 3.7 200706100000Z

Release 3.9 200706100000Z

Release 4.0 200706100000Z

Release 4.2 200706100000Z


46



IEEE8023-LAG-MIB mibd-interface Release 3.7 200006270000Z Release 3.9 200006270000Z Release 4.0 200006270000Z Release 4.2 200006270000Z Release 4.3 200006270000Z

IETF-OSPF-TRAP-MIB

Release 3.7

- - - -

IETF-TCP-MIB 1 mibd-interface Release 3.7 200402040000Z Release 3.9 200402040000Z Release 4.0 200402040000Z Release 4.2 200402040000Z Release 4.3 200402040000Z

IETF-UDP-MIB 1 mibd-interface Release 3.7 200410180000Z Release 3.9 200410180000Z Release 4.0 200410180000Z Release 4.2 200410180000Z Release 4.3 200410180000Z

IF-MIB (RFC 2863)1 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

IMA-MIB mibd-interface Release 3.7 200303260000Z Release 3.9 200303260000Z Release 4.0 200303260000Z Release 4.2 200303260000Z Release 4.3 200303260000Z

IP-FORWARD-MIB mibd-route


47


MIB mibd process Supported Unsupported Not in Image Release 3.7 RFC 2096

RFC 4292 Release 3.9 RFC 2096




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

IPV6-MIB mibd-interface Release 3.7 9802052155Z Release 3.9 9802052155Z Release 4.0 9802052155Z Release 4.2 9802052155Z Release 4.3 9802052155Z

IPV6-FORWARD-MIB mibd-interface Release 3.7 200402091200Z Release 3.9 200402091200Z Release 4.0 200402091200Z Release 4.2 200402091200Z Release 4.3 200402091200Z

IPV6-MLD-MIB mibd-interface Release 3.7 200101250000Z Release 3.9 200101250000Z Release 4.0 200101250000Z Release 4.2 200101250000Z


48



ISIS-MIB mibd-route Release 3.7 200604040000Z Release 3.9 200604040000Z Release 4.0 200604040000Z Release 4.2 200604040000Z Release 4.3 200604040000Z

MAU-MIB mibd-route Release 3.7 200704210000Z Release 3.9 200704210000Z Release 4.0 200704210000Z Release 4.2 200704210000Z Release 4.3 200704210000Z

MEF-SOAM-PM-MIB mibd-interface Release 5.2 201201131200Z

MFR-MIB mibd-route Release 3.7 200011300000Z Release 3.9 200011300000Z Release 4.0 200011300000Z Release 4.2 200011300000Z Release 4.3 200011300000Z

MGMD-STD-MIB mibd-route Release 3.7 200302240000Z Release 3.9 200302240000Z Release 4.0 200302240000Z Release 4.2 200302240000Z Release 4.3 200302240000Z

MPLS-L3VPN-STD-MIB mibd-route Release 3.7 200601230000Z Release 3.9 200601230000Z Release 4.0 200601230000Z Release 4.2 200601230000Z Release 4.3 200601230000Z

MPLS-LDP-GENERIC-STD-MIB mibd-route Release 3.7 200406030000Z Release 3.9 200406030000Z Release 4.0 200406030000Z


49


MIB mibd process Supported Unsupported Release 4.2 200406030000Z Release 4.3 200406030000Z

MPLS-LDP-STD-MIB mibd-route Release 3.7 200406030000Z Release 3.9 200406030000Z Release 4.0 200406030000Z Release 4.2 200406030000Z Release 4.3 200406030000Z

MPLS-LSR-STD-MIB mibd-route Release 3.7 200406030000Z Release 3.9 200406030000Z Release 4.0 200406030000Z Release 4.2 200406030000Z Release 4.3 200406030000Z

MPLS-TE-STD-MIB 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

NOTIFICATION-LOG-MIB mibd-infra Release 3.7 200011270000Z Release 3.9 200011270000Z Release 4.0 200011270000Z Release 4.2 200011270000Z Release 4.3 200011270000Z

OSPF-MIB mibd-route Release 3.7 200611100000Z Release 3.9 200611100000Z Release 4.0 200611100000Z Release 4.2 200611100000Z Release 4.3 200611100000Z

OSPF-TRAP-MIB — Release 3.7 200611100000Z Release 3.9 200611100000Z Release 4.0 200611100000Z


50




OSPFV3-MIB mibd-route Release 3.7 200709171200Z Release 3.9 200709171200Z Release 4.0 200709171200Z Release 4.2 200709171200Z Release 4.3 200709171200Z

RADIUS-ACC-CLIENT-MIB 1 mibd-infra Release 3.7 200300000000Z Release 3.9 200300000000Z Release 4.0 200300000000Z Release 4.2 200300000000Z Release 4.3 200300000000Z

RADIUS-AUTH-CLIENT-MIB 1 mibd-infra Release 3.7 200300000000Z Release 3.9 200300000000Z Release 4.0 200300000000Z Release 4.2 200300000000Z Release 4.3 200300000000Z

RFC1213-MIB1 — 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

RFC 2011-MIB — Release 3.7 9411010000Z Release 3.9 9411010000Z Release 4.0 9411010000Z Release 4.2 9411010000Z Release 4.3 9411010000Z

RFC 2465-MIB — Release 3.7 9802052155Z Release 3.9 9802052155Z Release 4.0 9802052155Z


51




RSVP-MIB1 mibd-interface Release 3.7 9808251820Z Release 3.9 9808251820Z Release 4.0 9808251820Z Release 4.2 9808251820Z Release 4.3 9808251820Z

SNMP-COMMUNITY-MIB(RFC 2576) snmpd


SNMP-FRAMEWORK-MIB(RFC 2571) snmpd


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

SNMP-NOTIFICATION-MIB (RFC 2573) snmpd

Release 3.7 9808040000Z


52


MIB mibd process Supported Unsupported Not in Image Release 3.9 9808040000Z Release 4.0 9808040000Z Release 4.2 9808040000Z Release 4.3 9808040000Z

SNMP-TARGET-MIB (RFC 2573) snmpd


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

SNMP-USM-MIB (RFC 2574) snmpd Release 3.7 9901200000Z Release 3.9 9901200000Z Release 4.0 9901200000Z Release 4.2 9901200000Z Release 4.3 9901200000Z

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

SNMPv2-MIB (RFC 1907) 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


53


MIB mibd process Supported Unsupported Not in Image 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

SONET-MIB (RFC 2558)1 mibd-interface


TCP-MIB mibd-route Release 3.7 200502180000Z Release 3.9 200502180000Z Release 4.0 200502180000Z Release 4.2 200502180000Z Release 4.3 200502180000Z

UDP-MIB mibd-route Release 3.7 200505200000Z Release 3.9 200505200000Z Release 4.0 200505200000Z Release 4.2 200505200000Z Release 4.3 200505200000Z

VRRP-MIB — 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.


54

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 BGP4-MIB bgpEstablished, bgpBackwardTransition BRIDGE-MIB newRoot, topologyChange CISCO-BGP4-MIB cbgpFsmStateChange, cbgpBackwardTransition, cbgpPrefixThresholdExceeded, cbgpPrefixThresholdClear CISCO-BULK-FILE-MIB cbfDefineFileCompletion CISCO-CONFIG-COPY-MIB ccCopyCompletion CISCO-CONFIG-MAN-MIB ciscoConfigManEvent CISCO-ENTITY-FRU-CONTROL-MIB cefcModuleStatusChange, cefcPowerStatusChange, cefcFRUInserted, cefcFRURemoved, cefcFanTrayStatusChange CISCO-ENTITY-SENSOR-MIB entSensorThresholdNotification CISCO-FLASH-MIB ciscoFlashCopyCompletionTrap, ciscoFlashDeviceInsertedNotif, ciscoFlashDeviceRemovedNotif, ciscoFlashMiscOpCompletionTrap CISCO-IETF-PW-MIB cpwVcDown, cpwVcUp CISCO-RF-MIB ciscoRFSwactNotif, ciscoRFProgressionNotif CISCO-SONET-MIB ciscoSonetSectionStatusChange, ciscoSonetPathStatusChange, ciscoSonetLineStatusChange CISCO-SYSLOG-MIB clogMessageGenerated DS1-MIB (RFC 2495) dsx1LineStatusChange ENTITY-MIB (RFC 2737) entConfigChange EVENT-MIB mteTriggerFired, mteTriggerRising, mteTriggerFalling, mteTriggerFailure, mteEventSetFailure IEEE8021-CFM-MIB dot1agCfmFaultAlarm


55

IF-MIB (RFC 2863) linkDown, linkUp


56

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 lists the constraints that the router places on objects in the ATM-MIB.

MIB Object Notes

atmVpCrossConnectAdminStatus Not supported atmVpCrossConnectRowStatus Not supported atmVcCrossConnectAdminStatus Not supported

atmVcCrossConnectRowStatus Not supported atmTrafficDescrType Not supported


57

Table 3-4 ATM-MIB Constraints

MIB Object Notes

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


58

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.



59

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


60

Table 3-6 ATM2-MIB Tables and Descriptions (continued)

Name Description 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


61

Table 3-7 ATM2-MIB Constraints

MIB Object Notes 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


62

Table 3-7 ATM2-MIB Constraints

MIB Object Notes

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


63

Table 3-9 BGP4-MIB Constraints

MIB Object Notes

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. Note: To access bridge domain data, the corresponding SNMP context must be used (i.e. v2 comunity or v3 group mapped to context).


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.


64

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

Note: Set 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


65

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


66

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 VCL1 Oam configuration and state information. This table augments the atmVclTable. 1. 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).

Note: Set Operation on BRIDGE-MIB objects is not supported.


67

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.


68

Table 3-16 CISCO-ATM-QOS-MIB Tables and Descriptions (continued) Name Description

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


69

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

1. AFI = Address Family Identifiers


70

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 cbgpPeer2MinRouteAdvertisementInte Not supportedrval 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. Note: CISCO-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.


71



72

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.

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


73

Table 3-23 CISCO-CDP-MIB Tables and Descriptions (continued) Name Description

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.


74

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


75


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.


76


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 supportedcbQosEVCGroup Not supportedcbQosFrameRelayPolicyTable Not supportedcbQosInterfacePolicyTable Not supported cbQosIPHCStatsTable Only RTP supported on XR. cbQosMeasureIPSLACfgTable Not supported on XR cbQosMatchStmtStatsTableCbQosMatchPrePolicyPktOverflow Not supportedCbQosMatchPrePolicyPkt Not supportedCbQosMatchPrePolicyPkt64 Not supportedCbQosMatchPrePolicyByteOverflow Not supportedCbQosMatchPrePolicyByte Not supportedCbQosMatchPrePolicyByte64 Not supportedCbQosMatchPrePolicyBitRate Not supportedcbQosNoBufferDropTable Not supportedcbQosPoliceCfgTable cbQosPoliceCfgConformAction Deprecated and defined in

cbQosPoliceAction CfgTable


77

Table 3‐26 CISCO‐CLASS‐BASED‐QOS‐MIB Constraints (continued) MIB Object Notes

cbQosPoliceCfgConformSetValue Deprecated and defined in cbQosPoliceAc tionCfgTable

cbQosPoliceCfgExceedAction Deprecated and defined in cbQosPoliceAc tionCfgTable

cbQosPoliceCfgExceedSetValue Deprecated and defined in cbQosPoliceAc tionCfgTable

cbQosPoliceCfgViolateAction Deprecated and defined in cbQosPoliceAc tionCfgTable

cbQosPoliceCfgViolateSetValue Deprecated and defined in cbQosPoliceAc tionCfgTable

cbQosQueueingCfgTable cbQosQueueingCfgFlowEnabled Not supported

cbQosQueueingCfgAggregateQSize Deprecated by cbQosQueueing CfgAggregateQLimit

cbQosQueueingCfgDynamicQNum- Not supported ber cbQosQueueingCfgPrioBurstSize Not supported cbQosQueueingClassCfgTable Not supported cbQosREDCfgTable

cbQosREDCfgExponWeight Not supported on XR

cbQosREDCfgMeanQSize Replaced by cbQosREDMeanQsize cbQosREDCfgECNEnabled Not supported cbQosREDClassCfgTable

cbQosREDCfgMinThreshold

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

cbQosREDCfgMaxThreshold

Deprecated by cbQosREDClassCfg- MInThreshold. 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


78

Table 3-26 CISCO-CLASS-BASED-QOS-MIB Constraints (continued)

MIB Object Notes cbQosTrafficShapingDelayCountersGroup Not supportedcbQosTSCfgTable

CbQosTSCfgBurstsize Not supportedCbQosTSCfgAdaptiveEnabled Not supportedCbQosTSCfgAdaptiveRate Not supportedcbQosTSStatsTable

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


79


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.


80

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.



81

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


82

Table 3-31 CISCO-CONTEXT-MAPPING-MIB Constraints cContextMappingBridgeInstRowStatus Not supported cContextMappingVrfName Not supported cContextMappingTopologyName Not supported cContextMappingProtoInstName Not supported cContextMappingStorageType Not supported cContextMappingRowStatus Not supported cContextMappingBridgeDomainIdentifier Not supported cContextMappingBridgeDomainStora-geType Not supported cContextMappingBridgeDomainRow- Status 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. cds3StatsTablele CCV5, FE6, 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.


83

Table 3-32 CISCO-DS3-MIB Tables and Descriptions (continued) Name Description

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.

1. LOS = loss of signal 2. LOF = out of frame 3. AIS = alarm indication signals 4. RAI = remote alarm indications 5. CCV = C-bit coding violations 6. 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


84

Table 3-33 CISCO-DS3-MIB Constraints

MIB Object Notes

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

Table 3-33 CISCO-DS3-MIB Constraints


85

MIB Object Notes

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 Note: Only ceImageTable is supported in 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.


86

Table 3-34 CISCO-ENHANCED-IMAGE-MIB Tables and Descriptions (continued)

Name Description

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.


87

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


88

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


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.


89

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


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


90


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


91

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


92

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.


93

MIB Table DescriptionceRedunSwitchoverReasonTable 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


94

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

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


95

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


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

Note SPA 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.


96

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)






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)



97

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

MIB Sensor Object Notes





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


98

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.


99

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.


100

Table 3-50 CISCO-FLASH-MIB Tables and Descriptions (continued) Name Description

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


101

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


cfcCloneProfileTable

cfcCloneProfileId Not-accessible

cfcCloneProfileStatus Read-create

cfcCloneProfileStorageType Read-create

cfcCloneProfileName Read-create


102


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 prevent other applications from using it. FLOW MONITORS— At the top level, this MIB module describes the notion of a flow monitor. A flow monitor is hardware or software entity that classifies traffic flows, collects data on conforming traffic flows, and periodically computes metrics that reflect the quality of the traffic flows. Because a device can support more than one flow monitor, the MIB module defines the cfmFlowMonitorTable. Consider an edge router that supports a certain line card that has an integrated capability to monitor video flows. In this example, the cfmFlowMonitorTable would contain a row describing each line card installed in the device. TRAFFIC FLOWS— At the next level, this MIB module describes the notion of a traffic flow. This MIB module uniquely identifies a traffic flow using an auxiliary variable called cfmFlowId; however, an implementation only has guarantee its uniqueness within the scope of the flow monitor that has the responsibility for monitoring the traffic flow. Thus, we can think of the flow monitor as a container for the traffic flows for which it collects data and periodically computes metrics, as the figure below illustrates.


103

+----------------------------+ | cfmFlowTable | | | +----------------------+ +--------------------------------+ | cfmFlowMonitorId = 3 -----| +------------------------+ | +----------------------+ | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 101 | | | +------------------------+ | | +------------------------+ | | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 102 | | | +------------------------+ | | : | | : | | +------------------------+ | | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 150 | | | +------------------------+ | +--------------------------------+ | | +----------------------+ +--------------------------------+ | cfmFlowMonitorId = 4 -----| +------------------------+ | +----------------------+ | | cfmFlowMonitorId = 4 | | | | cfmFlowId = 1 | | | +------------------------+ | | +------------------------+ | | | cfmFlowMonitorId = 4 | | | | cfmFlowId = 2 | | | +------------------------+ | | : | | : | | +------------------------+ | | | cfmFlowMonitorId = 4 | | | | cfmFlowId = 150 | | | +------------------------+ | +--------------------------------+ | | +----------------------------+ While the identifying of a traffic flow using this auxiliary variable is convenient for the MIB module, it is does suffice for an EMS/NMS trying to isolate faults in a network delivering these traffic flows. To aid an EMS/NMS in this task, this MIB module defines a number of tables that provide layers of data relating to a traffic flow, including: cfmFlowL2VlanTable— describes L2 VLAN data relating to traffic flows.

cfmFlowIpTable—describes IP data relating to traffic flows.

cfmFlowUdpTable—describes UDP data relating to traffic flows.

cfmFlowTcpTable—describes TCP data relating to traffic flows.

cfmFlowRtpTable—describes RTP data relating to traffic flows.

Each of these tables have a sparse dependent relationship on the cfmFlowTable, as there exist situations when the data may not be available for a traffic flow, including:

1. The flow monitor simply may not collect the particular data for the traffic flows that it has the responsibility of monitoring. For example, a flow monitor may not have any concern for L2 VLAN data.

2. The data may not apply to a traffic flow. For example, a TCP and RTP data do not apply for a UDP traffic flow. To help an EMS/NMS navigate the data collected for a traffic flow, the corresponding rows are daisy-chained using ’next objects’. An EMS/NMS starts with cfmFlowNext, which indicates a reference to the row in the next table containing data related to the traffic flow. The first object contained by each of these tables is a ’next object’. Consider a RTP traffic flow for which the flow monitor has collected IP, UDP, and RTP data. The figure below illustrates how this MIB module daisy chains this data through the relevant tables.

+-------------------------------------------+ | cfmFlowTable | | +---------------------------------------+ | | | cfmFlowMonitorId = 3 | | | | cfmFlowId = 42 | | | | cfmFlowNext = cfmFlowIpNext.3.42 ----------+ | +---------------------------------------+ | | +-------------------------------------------+ | | +-------------------------------------------+ | | cfmFlowIpTable | | | +---------------------------------------+ | | | | cfmFlowMonitorId = 3 |

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


104

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


105

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

MIB Object Notes

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


106

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

MIB Object Notes

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


107


MIB Object Notes

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


MIB Object Notes

cfmFlowL2InnerVlanCos Not-supported cfmFlowL2InnerVlanId Not-supportedcfmFlowIpMaxHopLimit Not-supportedcfmFlowIpMinHopLimit Not-supportedcfmFlowIpDscp Not-supportedcfmFlowMetricsErrorSecsScale Read-only

cfmFlowMetricsErrorSecsPrecision Read-only

cfmFlowMetricsErrorSecsNew Read-onlycfmFlowMetricsTransportAvailabilityScale Read-onlycfmFlowMetricsTransportAvailabilityPrecision Read-onlycfmFlowMetricsTransportAvailability Read-onlycfmFlowMetricsPktDropped Not-supportedcfmFlowMetricsStreamBitRateUnits Not-supportedcfmFlowMetricsStreamBitRate Not-supportedcfmFlowMetricsStreamPktRate Not-supportedcfmFlowMetricsStreamBitRateMaxUnits Not-supportedcfmFlowMetricsStreamBitRateMax Not-supported


108

cfmFlowMetricsStreamBitRateMinUnits Not-supportedcfmFlowMetricsStreamBitRateMin Not-supportedcfmFlowMetricsIntErrorSecsScale Read-onlyMIBObject NotescfmFlowMetricsIntErrorSecsPrecision Read-onlycfmFlowMetricsIntErrorSecs Read-onlycfmFlowMetricsIntTransportAvailabilityScale Read-onlycfmFlowMetricsIntTransportAvailabilityPrecision Read-onlycfmFlowMetricsIntTransportAvailability Read-onlycfmFlowMetricsIntStreamCount Not-supportedcfmFlowMetricsIntRtpStreamCount Not-supportedcfmFlowMetricsIntTcpStreamCount Not-supportedcfmFlowMetricsIntPktDropped Not-supportedcfmFlowMetricsIntStreamBitRateUnits Not-supportedcfmFlowMetricsIntStreamBitRate Not-supportedcfmFlowMetricsIntStreamPktRate Not-supportedcfmFlowMetricsIntStreamBitRateMaxUnits Not-supportedcfmFlowMetricsIntStreamBitRateMax Not-supportedcfmFlowMetricsIntStreamBitRateMinUnits Not-supportedcfmFlowMetricsIntStreamBitRateMin Not-supportedcfmConditionAlarmClonePortType Read-onlycfmConditionAlarmClonePortType Read-only

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.


109

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.


110

Table 3-55 CISCO-FRAME-RELAY Tables and Descriptions (continued) Name Description 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.


111

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


112

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


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


113

Table 3-62 CISCO-IETF-BFD-MIB Constraints (continued) MIB Object Notes

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.


114

Table 3-63 CISCO-IETF-FRR-MIB Tables and Descriptions (continued) Name Description

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


115

Table 3-64 CISCO-IETF-FRR-MIB Constraints (continued) MIB Object Notes

cmplsFrrNotifMaxRate Not supported

cmplsFrrFacRouteProtectingTunProtec- Not supportedtionType

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-66 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


116

Table 3-66 CISCO-IETF-MPLS-TE-P2MP-STD-MIB Constraints (continued) MIB Object Notes

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


117

Table 3-67 CISCO-IETF-IPMROUTE-MIB Tables and Descriptions (continued) Name Description

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.


118

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


119

Table 3-70 CISCO-IETF-MSDP-MIB Constraints (continued) MIB Object Notes

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


120

Table 3-71 CISCO-IETF-PIM-MIB Tables and Descriptions (continued)

Name Description

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.


121

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 IPMulticast 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 DF1 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.

1. DF = designated forwarder


122

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.


123


124

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


125

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


126

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

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.


127

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


128

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 Note

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


129

cpwVcMplsOutboundTunnelIndex Not supported

cpwVcMplsOutboundTunnelInstance Not supported

cpwVcMplsOutboundTunnelLclLSR Not supported

cpwVcMplsOutboundTunnelPeerLSR Not supported


130

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

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


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.


131

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


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.


132

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://tools.ietf.org/html/draft-nadeau-l2vpn-vpls-mib-03 Table 3-87 lists the tables defined in CISCO-IETF-VPLS-LDP-MIB.


133

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


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.


134

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


135

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

MIB Object Notes

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 supportedcieIfNoDropVlInOctets 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


136

CISCO-IP-ADDRESS-POOL-MIB This MIB modules defines objects that describe common aspects of IP address pools. IP Address Pool Manager: The IP address pool manager consists of the software that maintains IP address pools and supports the following capabilities: Create an IP address pool group. Destroy an IP address pool group. Create an IP address pool and add it to an IP address pool group. Remove an IP address pool from an IP address pool group and destroy it. Create a range of IP addresses and add it to an IP address pool. Remove a range of IP addresses from an IP address pool and destroy it. Allocate an IP address from an IP address pool. Return a previously allocated IP address to the IP address pool that it was allocated from. Create a set of IP prefixes and adding it to an IP address pool. Remove a set of IP prefixes from an IP address pool and destroy it. Allocate an IP prefix from an IP address pool. Return a previously allocated IP prefix to the IP address pool that it was allocated from.

IP Address Pool: An IP address pool consists of a collection of IP addresses from which a client (e.g., PPP or DHCP) can allocate an IP address for the purpose of assigning it to a remote peer. This collection consists of a one or more range of IP addresses. Observe that human interfaces allow a user to specify ranges of IP addresses using a variety of means to simplify the process. For example, a human interface may simply allow a user to specify a subnet. No matter what abstraction a human interface employs, the end result is always one or more range of IP addresses. Thus, this MIB module abstracts an IP address pool as one or more range of IP addresses. This places the burden on any application employing other abstractions to transform to the abstraction defined by this MIB module. Alternatively, an IP address pool can also consist of a collection of IP prefixes from which a client can allocate an IP prefix for the purpose of assigning it to a remote peer. This collection consists of one or more set of IP prefixes. Observe that the term ’IP prefix’ here can refer to an IPv4 subnet or an IPv6 prefix. IP Address Pool Group: An IP address pool group contains the IP address pools belonging to the same administrative domain. Examples of administrative domains include a Virtual Route Forwarding (VRF) instance and a Virtual Private Network (VPN). Observe that the IP addresses contained by the IP address pools in two distinct IP address pool groups may overlap. IP Address Pool Threshold Monitoring: An IP address pool manager maintains a number of gauges for the purpose of monitoring the number of allocated IP addresses. We refer to these gauges as ’in-use gauges’. Each in-use gauge has a corresponding state that can have one of two values:

1. Off The IP address pool manager monitors the number of allocated addresses or prefixes. If this value is greater than the configured rising threshold and the previous value was less than or equal to the same rising threshold, then the IP address manager transitions the state to ’On’.

2. On The IP address pool manager monitors the number of allocated addresses or prefixes. If the value is less than the configured falling threshold and the previous value was greater than or equal to the same falling threshold, then the IP address manager transitions the state to ’Off’. Observe that while the values of the configured rising and falling thresholds may be the same, this may result in undesirable behavior (i.e., the IP address pool manager may generate more threshold crossing notifications than desirable).


137

The IP address pool manager only generates threshold crossing notifications when it transitions the corresponding state of an in-use gauge and the value of ciapGlobalNotifyEnable is ’true’. The IP address pool manager may maintain in-use gauges for the following: A range of IP addresses comprising an IP address pool

A set of IP prefixes comprising an IP address pool

An IP address pool - An IP address pool group

Observe that the IP address pool manager must initialize the state of each in-use gauge to ’Off’ for threshold monitoring to operate in the prescribed manner.

MIB Objects Table 3-91 CISCO-IP-ADDRESS-POOL-MIB Tables and Descriptions

Name Description

ciapPoolTable This table lists the IP address pools maintained by the IP address pool manager.

ciapRangeTable This table lists the ranges of IP addresses contained by each IP address pool maintained by

the IP address pool manager.

ciapPrefixTable This table lists the IP prefixes contained by each IP address pool maintained by the IP address pool manager.

ciapPoolGroupTable This table lists the IP address pool groups maintained by the IP address pool manager.

ciapPoolGroupContainsTable This table lists the IP address pools contained by each IP address pool group maintained by the IP address pool manager.

ciapAllocatedAddressTable This table lists of the IP addresses, IPv4 subnets, and IPv6 prefixes allocated from the IP address pools maintained by the IP address pool manager.

MIB Constraints Table 3-92 lists the constraints on objects in the CISCO-IP-ADDRESS-POOL-MIB.

Table 3-92 CISCO-IP-ADDRESS-POOL-MIB Constraints MIB Object Notes Global Objects Not-supported. ciapGlobalNotifyEnable Not-supported. ciapGlobalThresholdUnits Not-supported. ciapGlobalThresholdRising Not-supported. ciapGlobalThresholdFalling Not-supported.


138

Table 3-92 CISCO-IP-ADDRESS-POOL-MIB Constraints MIB Object Notes

ciapPoolIdNext Supported.

Pool Table Objects

ciapPoolStatus Supported.

ciapPoolStorage Not-supported.

ciapPoolName Supported.

ciapPoolType Supported.

ciapPoolContainedIn Supported.

ciapPoolThresholdUnits Supported.

ciapPoolThresholdRising Supported.

ciapPoolThresholdFalling Supported.

ciapPoolAddressesInUse Supported.

ciapPoolAddressesFree Supported.

ciapPoolTableChanged Not-supported.

Pool Address Range Objects

ciapRangeStatus Supported.

ciapRangeStorage Not-supported.

ciapRangeAddressUpper Supported.

ciapRangeCacheSize Not-supported.

ciapRangeRecycleDelay Not-supported.

ciapRangePriority Not-supported.

ciapRangeThresholdUnits Not-supported.

ciapRangeThresholdRising Not-supported.

ciapRangeThresholdFalling Not-supported.

ciapRangeAddressesInUse Supported.

ciapRangeAddressesFree Supported.

ciapRangeTableChanged Not-supported.

Pool Prefix Range Objects (applicable only for IPv6 prefixes)

ciapPrefixStatus Supported.

ciapPrefixStorage Not-supported.

ciapPrefixAssignedLength Supported.

ciapPrefixCacheSize Not-supported.

ciapPrefixRecycleDelay Not-supported.

ciapPrefixPriority Not-supported.

ciapPrefixThresholdUnits Not-supported.

ciapPrefixThresholdRising Not-supported.


139

Table 3-92 CISCO-IP-ADDRESS-POOL-MIB Constraints MIB Object Notes

ciapPrefixThresholdFalling Not-supported.

ciapPrefixPrefixesInUse Supported.

ciapPrefixPrefixesFree Supported.

ciapPrefixTableChanged Not-supported.

ciapPoolGroupIdNext Supported.

Pool Group (VRF) Related Objects

ciapPoolGroupName Supported.

ciapPoolGroupThresholdUnits Not-supported.

ciapPoolGroupThresholdRising Not-supported.

ciapPoolGroupThresholdFalling Not-supported.

ciapPoolGroupAddressesInUse Supported.

ciapPoolGroupAddressesFree Supported.

ciapPoolGroupContainsId Supported.

Allocated Address Objects

ciapAllocatedAddressMask Not-supported.

Notification Objects

ciapNotifyResource Supported.

ciapNotifyThresholdUnits Supported.

ciapNotifyThresholdRising Supported.

ciapNotifyThresholdFalling Supported.

ciapNotifyInUse Supported.

ciapNotifyFree Supported.

ciapEventThresholdRising Supported.

ciapEventThresholdFalling Supported.


140

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-93 lists the tables associated with this MIB.

MIB Objects Table 3-93 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-94 lists the constraints on objects in the CISCO-IP-CBR-METRICS-MIB.

Table 3-94 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


141

Table 3-94 CISCO-IP-CBR-METRICS-MIB Constraints MIB Object Notes

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-95 lists the tables in CISCO-IP-TAP-MIB


142

Table 3-95 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-96 lists the constraints on objects in the CISCO-IP-TAP-MIB.

Table 3-96 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.


143

MIB Tables

Table 3-97 lists the tables in CISCO-IP-STAT-MIB. Table 3-97 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-98 lists the tables associated with this MIB.


144

MIB Objects

Table 3-98 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-99 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-100 lists the tables associated with this MIB.


145

MIB Objects Table 3-100 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.


146

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

Name Description

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-101 lists the constraints on objects in the CISCO-IPSEC-FLOW-MONITOR-MIB.

Table 3-101 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


147

Table 3-101 CISCO-IPSEC-FLOW-MONITOR-MIB Constraints MIB Object Notes

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-102 lists the tables associated with this MIB.


148

MIB Objects

Table 3-102 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. regenerateLastRe-hostTicket 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.


149

Table 3-102 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. regenerateLastRe- hostTicket 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.

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-103 lists the constraints on objects in the CISCO-LICENSE-MGMT-MIB.

Table 3-103 CISCO-LICENSE-MGMT-MIB Constraints MIB Object Notes clmgmtDevCredEntPhysicalIndex Not supported clmgmtDevCredTransferProtocol Not supported clmgmtDevCredServerAddressType Not supported clmgmtDevCredServerAddress Not supported clmgmtDevCredServerUsername Not supported


150

Table 3-103 CISCO-LICENSE-MGMT-MIB Constraints MIB Object Notes

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-MDI-METRICS-MIB This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the quality indicator of a network intended to delivery applications such as streaming media, MPEG video, VoIP, or other information sensitive to arrival time and packet loss.

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

Table 3-217 CISCO-LICENSE-MGMT-MIB Constraints Name Description

cfmMdiMetricsTable This table contains aggregate data maintained by a flow monitor for traffic flows for which it is computing MDI metrics. This table has an 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 ’mdi’ bit set to one.

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

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


151

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-104 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


152

context related to that particular bridge domain. Table 3-105 lists the tables associated with this MIB.


153

MIB Objects Table 3-105 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-106 lists the constraints on objects in the CISCO-MLD-SNOOPING-MIB.

Table 3-106 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


154

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-107 lists the tables defined in CISCO-MPLS-TE-STD-EXT-MIB.

Table 3-107 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.


155

MIB Objects

Table 3-108 CISCO-NETSYNC-MIB Tables and DescriptionsName 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-109 lists the constraints on objects in the CISCO-NETSYNC-MIB.

Table 3-109 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


156

Table 3-109 CISCO-NETSYNC-MIB Constraints (continued) MIB Object Notes

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


157

Table 3-109 CISCO-NETSYNC-MIB Constraints (continued) MIB Object Notes

cnsExtOutIntfType Supported

cnsExtOutQualityLevel Supported

cnsExtOutPriority Supported

cnsExtOutFSW Always false

cnsExtOutMSW Always false

cnsExtOutSquelch Supported

cnsT4ClockSourceTable

cnsT4ClkSrcNetsyncIndex Supported

cnsT4ClkSrcName Supported

cnsT4ClkSrcIntfType Supported

cnsT4ClkSrcPriority SupportedcnsT4ClkSrcESMCCap 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.


158

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-110 lists the tables associated with this MIB.

MIB


159

Table 3-110 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

Note: CISCO-NTP-MIB has very limited support. cntpSysSrvStatus is supported. Table 3-111 lists the constraints on objects in the CISCO-NTP-MIB.

Table 3-111 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


160

cntpPeersPeerType Not supported

CISCO-OAM-MIB

A MIB module for invoking OAM loopback Ping on ATM connections. Table 3-112 lists the tables associated with this MIB.

MIB Objects Table 3-112 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-113 lists the constraints on objects in the CISCO-OAM-MIB.

Table 3-113 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


161

corresponding threshold value, a threshold crossing alarm (TCA) is generated. The TCAs provide early detection of performance degradation.

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


162

Table 3-114 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.


163

Table 3-114 CISCO-OTN-IF-MIB Tables and Descriptions (continued) Name Description

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-115 lists the tables associated with this MIB. Table 3-115 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.


164

Table 3-115 CISCO-PTP-MIB Tables and Descriptions (continued) Name Description

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-116 lists the constraints that the Cisco ASR 9000 Series router places on objects in the CISCO-PTP-MIB.

Table 3-116 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

cPtpDomainClockPortPhysicalInter- Supported facesTotal

cPtpSystemDomainTable

cPtpSystemDomainClockTypeIndex Supported


165

Table 3-116 CISCO-PTP-MIB Constraints (continued) MIB Object Notes

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

cPtpClockParentDSGMClockQuality-Class Supported

cPtpClockParentDSGMClockQualityAccuracy Supported

cPtpClockParentDSGMClockQuality- Offset Supported

cPtpClockParentDSOffset Not supported

cPtpClockParentDSClockPhChRate Not supported


166

cPtpClockDefaultDSTable

cPtpClockDefaultDSDomainIndex Supported

cPtpClockDefaultDSClockTypeIndex Always "boundary clock"

cPtpClockDefaultDSInstanceIndex Always 0

cPtpClockDefaultDSTwoStepFlag Always true

cPtpClockDefaultDSClockIdentity Supported

cPtpClockDefaultDSPriority1 Supported


167

Table 3-116 CISCO-PTP-MIB Constraints (continued) MIB Object Notes 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

cPtpClockTimePropertiesDSCurrentUT COffsetValid Supported

cPtpClockTimePropertiesDSCurrentUTCOffset Supported

cPtpClockTimePropertiesDSLeap59 Supported

cPtpClockTimePropertiesDSLeap61 Supported

cPtpClockTimePropertiesDSTimeTraceable Supported

cPtpClockTimePropertiesDSFreqTraceable Supported

cPtpClockTimePropertiesDSPTPTimescale Supported

cPtpClockTimePropertiesDSSource Supported

cPtpClockTransDefaultDSTable Not supported

cPtpClockPortTable

cPtpClockPortDomainIndex Supported


168

cPtpClockPortClockTypeIndex Always "boundary clock"

cPtpClockPortClockInstanceIndex Always 0

cPtpClockPortTablePortNumberIndex Supported

cPtpClockPortName Supported

cPtpClockPortRole Supported

cPtpClockPortSyncOneStep Supported

cPtpClockPortCurrentPeerAddressType Supported


169

Table 3-116 CISCO-PTP-MIB Constraints (continued) MIB Object Notes

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


170

cPtpClockPortRunningState Supported

cPtpClockPortRunningRole Supported

cPtpClockPortRunningInterfaceIndex Supported

cPtpClockPortRunningIPversion Supported

cPtpClockPortRunningTxMode Supported


171

Table 3-116 CISCO-PTP-MIB Constraints (continued) MIB Object Notes cPtpClockPortRunningPacketsReceived Supported

cPtpClockPortRunningPacketsSent Supported

cPtpClockPortRunningRxMode Not supported

cPtpClockPortRunningEncapsulation-Type Not supported

cPtpClockPortTransDSTable Not supported

cPtpClockPortAssociateTable cPtpClockPortCurrentDomainIndex Supported

cPtpClockPortCurrentClockTypeIndex Always "boundary clock"

cPtpClockPortCurrentClockInstanceIn dex Always 0

cPtpClockPortCurrentPortNumberIndex Supported cPtpClockPortAssociatePortIndex Supported cPtpClockPortAssociateAddressType Supported cPtpClockPortAssociateAddress Supported cPtpClockPortAssociatePacketsSent Supported cPtpClockPortAssociatePacketsReceived Supported cPtpClockPortAssociateInErrors Supported cPtpClockPortAssociateOutErrors Not supported

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide CISCO-P2P-IF-MIB

172

CISCO-P2P-IF-MIB

The CISCO-P2P-IF-MIB is a Point to Point Interface MIB module. This MIB defines table objects to manage the generic objects for Serial link or SONET/SDH like point to point network interfaces with the encapsulations of PPP (Point to Point Protocol), HDLC (High Level Data Link Control) or cHDLC (Cisco extension to High Level Data Link Control) framing. Table 3-117 lists the tables defined in CISCO-P2P-IF-MIB.

Table 3-117 CISCO-P2P-IF-MIB Tables


cp2pIfCfgTable Contains Point to Point generic Configuration information.

cp2pIfStatsTable Contains Point to Point Interface Statistics

information including the error statistics.

MIB Constraints

Table 3-118 lists the constraints on objects in the CISCO-P2P-IF-MIB.

Table 3-118 CISCO-P2P-IF-MIB Constraints MIB Object Notes

cp2pIfCfgCrcMode Not supported

cp2pIfCfgScramblingMode Not supported

cp2pIfCfgTransmitDelay Not supported


173

CISCO-PIM-MIB

The CISCO-PIM-MIB defines the Cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are an extension of those defined in the UETF PIM MIB (RFC 2934). This MIB has no tables. A Management Station pinging different Network elements can use this MIB to ping and get back the results if the Network Element is accessible or not. The number of packets, packet size, timeout, delay can be set to the appropriate values and tested. This MIB is superseded by the CISCO-RTTMON-MIB that provides this functionality in addition to other features.

CISCO-PING-MIB

The CISCO-PING-MIB is used to determine connectivity and reachability of network elements and devices via use of the PING protocol. Table 3-119 lists the tables associated with this MIB.

Table 3-119 CISCO-PING-MIB Tables and Descriptions

Name Description

ciscoPingTable Ping request entry. A management station wishing to create an entry should first generate a pseudo-random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row owner objects. It must also, either in the same or in successive PDUs, create the associated instance of the protocol and address objects. It should also modify the default values for the other configuration objects if the defaults are not appropriate. After the appropriate instance of all the configuration objects have been created, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. After the ping sequence has been activated, it cannot be stopped—it runs until the configured number of packets have been sent. After the sequence completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. To prevent old entries from clogging the table, entries are aged out, but an entry is never deleted within 5 minutes of completing barring an explicit delete request from the management station.

MIB Constraints IPv6 support is not available for CISCO-PING-MIB.


174

CISCO-PROCESS-MIB

The CISCO-PROCESS-MIB describes active system processes. Virtual Machine refers to those OS which can run the code or process of a different executional model OS. Virtual processes assume the executional model of a OS which is different from Native IOS. Virtual Processes are also referred to as Tasks. Thread is a sequence of instructions to be executed within a program. A thread which adheres to POSIX standard is referred to as a POSIX thread. Table 3-120 lists the tables associated with this MIB.

Table 3-120 CISCO-PROCESS-MIB Tables and Descriptions

Name Description

cpmCPUTotalTable Table of overall CPU statistics.

cpmProcessTable Table of generic information on all active processes on this device.

cpmProcessExtTable This table contains information that may or may not be available on all cisco devices. It contains additional objects for the more general cpmProcessTable. This object is deprecated by cpmProcessExtRevTable.

cpmProcessExtRevTable This table contains information that may or may not be available on all Cisco devices. It contains additional objects for the more general cpmProcessTable. This object deprecates cpmProcessExtTable.

cpmCPUThresholdTable This table contains the information about the thresholding values for CPU, configured by the user. cpmCPUHistoryTable List of CPU utilization history entries.

cpmThreadTable This table contains generic information about POSIX threads in the device.

cpmVirtualProcessTable This table contains information about virtual processes in a virtual machine.

cpmCPUProcessHistoryTable List of process history entries. This table contains CPU utilization of processes which crossed the cpmCPUHistoryThreshold.

CISCO-RF-MIB

The CISCO-RF-MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logical redundancy of software functionality and is designed to support 1:1 redundancy on Route Switch Processors (RSPs). Redundancy duplicates data elements and software functions to provide an alternative in case of failure. Note: For information about the levels of redundancy and how to verify that the redundancy feature is available on the Cisco ASR 9000 Series routers, see Appendix 1, “Using MIBs.” Table 3-121 lists the tables defined in CISCO-RF-MIB.


175


176

Table 3-121 CISCO-RF-MIB Tables MIB Table Description

cRFStatusRFModeCapsTable This table containing a list of redundancy modes that can be supported on the device.

cRFStatusRFClientTable This table contains a list of RF clients that are registered on the device. RF clients are applications that have registered with the Redundancy Facility (RF) to receive RF events and notifications. The purpose of RF clients is to synchronize any relevant data with the standby unit.

cRFHistorySwitchOverTable A table that tracks the history of all switchovers that have occurred since system initialization. The maximum number of entries permissible in this table is defined by cRFHistoryTableMaxLength. When the number of entries in the table reaches the maximum limit, the next entry would replace the oldest existing entry in the table.

MIB Constraints Table 3-122 lists the constraints that the Cisco ASR 9000 Series router places on objects in the CISCO-RF-MIB.

Table 3-122 CISCO-RF-MIB Constraints

MIB Object Notes

cRFCfgGroup

cRFCfgSplitMode Object is deprecated.

cRFCfgRedundancyMode Values: 6, 7, and 8.

cRFCfgMaintenanceMode Read-only. Supported value is false (2).

cRFHistoryGroup

cRFHistory There are three switchover modes: coldstand- by, warmstandby, and hoststandby. The only entries saved are those generated from a hot standby switchover.

cRFCfgKeepaliveThresh Not supported

cRFCfgKeepaliveTimer Not supported

cRFCfgNotifTimer Not supported

cRFCfgAdminAction Not supported

cRFCfgNotifsEnabled Not supported

cRFCfgMaintenanceMode Not supported


177

Table 3-122 CISCO-RF-MIB Constraints (continued) MIB Object Notes

cRFCfgRedundancyMode Not supported

cRFHistoryTableMaxLength Not supported

Note: SNMP process placement was introduced in Cisco IOS XR Release 3.8.3. cRFStatusRFClientTable in CISCO-RF-MIB lists the status of all processes on DSC and their redundancy status. However, the redundancy status of all the processes (for example bgp, ospf) that are placeable is not correct when the process is placed on a different RP or DRP. To overcome this issue, use RFClientStatus definition to get redundancy information about the process and to get the process state use Processmib.

CISCO-RTP-METRICS-MIB This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver Report packet [RFC3550].

MIB Objects

Table218 This table lists the MIB objects associated with CISCO-RTP-METRICS-MIB. CISCO-RTP-METRICS-MIBName Description

cfmRtpMetricsTable This table contains aggregate data maintained by a flow monitor for traffic flows for which it is computing RTP metrics. This table has an 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 ’rtp’ bit set to one.

cfmRtpMetricsIntTable This table contains historic RTP metrics for the traffic flows monitored by each of the flow monitors supported by the device. This table has an 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 ’rtp’ bit set to one.

CISCO-RTTMON-MIB The CISCO-RTTMON-MIB defines a MIB for Round Trip Time (RTT) monitoring of a list of targets, using a variety of protocols. Table 3-123 lists the tables associated with this MIB.

Table 3-123 CISCO-RTTMON-MIB Tables and Descriptions Name Description

rttMonApplSupportedRttTypesTable Table of which contains the supported Rtt Monitor Types. See the RttMonRttType textual convention for the definition of each type.

rttMonApplSupportedProtocolsTable Table of which contains the supported Rtt Monitor Protocols. See the RttMonProtocol textual convention for the

definition of each protocol.


178

rttMonApplPreConfigedTable Not supported.

rttMonApplAuthTable Not supported.

rttMonCtrlAdminTable Table of RTT monitoring definitions. The RTT administration control is in multiple tables. This first table, is used to create a conceptual RTT control row. The following tables contain objects which configure scheduling, information gathering, and notification/trigger generation. All of these tables create the same conceptual RTT control row as this table using this table index as their own index. This table is limited in size by the agent implementation. The object rttMonApplNumCtrlAdminEntry reflects this tables maximum number of entries.

rttMonEchoAdminTable Table that contains RTT specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

rttMonFileIOAdminTable Not supported.


179

Table 3-123 CISCO-RTTMON-MIB Tables and Descriptions (continued)

Name Description

rttMonScriptAdminTable Not supported.

rttMonScheduleAdminTable Table of RTT monitoring scheduling specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object.

rttMonReactAdminTable Not supported. This table was replaced by rttMonReactTable.

rttMonStatisticsAdminTable Table of Round Trip Time (RTT) monitoring statistics definitions. The definitions in this table control what and how many entries are placed into the rttMonStatsCaptureTable. The statistics capture table is a rollover table. When the rttMonStatisticsAdminNumHourGroups index value exceeds its value defined in this table, the oldest corresponding group is deleted and is replaced with the new group. All other indices only fill to there maximum size. NOTE: The maximum size of this table is defined to be the product of the ttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets. Note: Each of the 'Num' objects values in this have a special behavior. When one of the objects is set to a value larger than the RTT application can support the set succeeds, but the resultant value is set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable.


180


Name Description




rttMonStatisticsAdminTable Table of Round Trip Time (RTT) monitoring statistics definitions. The definitions in this table control what and how many entries are placed into the rttMonStatsCaptureTable. The statistics capture table is a rollover table. When the rttMonStatisticsAdminNumHourGroups index value exceeds its value defined in this table, the oldest corresponding group is deleted and is replaced with the new group. All other indices only fill to there maximum size.

NOTE: The maximum size of this table is defined to be

the product of the ttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets.

Note: Each of the 'Num' objects values in this have a special behavior. When one of the objects is set to a value larger than the RTT application can support the set succeeds, but the resultant value is set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable.


181


Name Description





NOTE: The maximum size of this table is defined to be the

product of the ttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets.

Note: Each of the 'Num' objects values in this have aspecial behavior. When one of the objects is set to a value larger than the RTT application can support the set succeeds, but the resultant value is set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable.


182


Name Description





NOTE: The maximum size of this table is defined to be

the product of the ttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets.

Note: Each of the 'Num' objects values in this have a special behavior. When one of the objects is set to a value larger than the RTT application can support the set succeeds, but the resultant value is set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable.


183

Table 3-123 CISCO-RTTMON-MIB Tables and Descriptions (continued) Name Description

rttMonHistoryAdminTable Table of RTT monitoring history definitions. The definitions in this table control what and how many entries are placed into the rttMonHistoryCollectionTable. The history collection table is a rollover table. When the rttMonHistoryAdminNumLives index value exceeds its value defined in this table, the oldest corresponding 'lives' group are deleted and are replaced with the new 'lives' group. All other indices only fill to their maximum size. Note: The maximum size of this table is defined to be the product of the rttMonCtrlAdminIndex times rttMonHistoryAdminNumLives times rttMonHistoryAdminNumBuckets times rttMonHistoryAdminNumSamples.

Note: Each of the 'Num' objects values in this have a special behavior. When one of the objects is set to a value larger than the RTT application can support the set succeeds, but the resultant value is set to the applications maximum value. The setting management station must reread this object to verify the actual value. Note: This table is not applicable to http and jitter probes.


184


Name Description

rttMonReactTriggerAdminTable Table that contains the list of conceptual RTT control rows that start to collect data when a reaction condition is violated and when rttMonReactAdminActionType is set to one of the following:

triggerOnly

trapAndTrigger

nmvtAndTrigger

violated and when any of the row in

rttMonReactTable has rttMonReactActionType as one

of the following:

triggerOnly

trapAndTrigger

The goal of this table is to define one or more additional conceptual RTT control rows that become active and start to collect additional history and statistics (depending on the rows configuration values), when a problem has been detected. If the conceptual RTT control row is undefined, and a trigger occurs, no action takes place. If the conceptual RTT control row is scheduled to start at a later time, triggering that row has no effect. If the conceptual RTT control row is currently active, triggering that row has no effect on that row, but the rttMonReactTriggerOperState object transitions to 'active'. An entry in this table can only be triggered when it is not currently in a triggered state. The object rttMonReactTriggerOperState reflects the state of each entry in this table.

rttMonReactTriggerOperTable Table of which contains the operational state of each entry in the rttMonReactTriggerAdminTable. This table augments the RTT trigger definition table, rttMonReactTriggerAdminTable.

rttMonEchoPathAdminTable

Table to store the hop addresses in a Loose Source Routing path. Response times are computed along the specified path using ping. This maximum table size is limited by the size of the maximum number of hop addresses that can fit in an IP header, which is eight. The object rttMonEchoPathAdminEntry reflects this tables maximum number of entries. This table is coupled with rttMonCtrlAdminStatus.

rttMonGrpScheduleAdminTable Not supported


185


Name Description

rttMplsVpnMonCtrlTable Table of Auto SAA Layer 3 MPLS VPN definitions. The Auto SAA Layer 3 MPLS VPN administration control is in multiple tables. This first table, is used to create a conceptual Auto SAA Layer 3 MPLS VPN control row. The following tables contain objects which used in type specific configurations, scheduling and reaction configurations. All of these tables create the same conceptual control row as this table using this table index as their own index. In order for a row in this table to become active, the following objects must be defined. rttMplsVpnMonCtrlRttType, rttMplsVpnMonCtrlVrfName, and rttMplsVpnMonSchedulePeriod.

rttMplsVpnMonTypeTable Table that contains Auto SAA Layer 3 MPLS VPN configured RTT operation specific definitions. Table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object.

rttMplsVpnMonScheduleTable Table of Auto SAA Layer 3 MPLS VPN monitoring scheduling specific definitions. This table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object.

rttMplsVpnMonReactTable Table of Auto SAA Layer 3 MPLS VPN Notification definitions. This table augments the rttMplsVpnMonCtrlTable.

rttMonReactTable Table that contains the reaction configurations. Each conceptual row in rttMonReactTable corresponds to a reaction configured for the probe defined in rttMonCtrlAdminTable. For each reaction configured for a probe there is an entry in the table. Each Probe can have multiple reactions and hence there can be multiple rows for a particular probe. This table is coupled with rttMonCtrlAdminTable.


186


Name Description

rttMonStatsCaptureTable The statistics capture database. The statistics capture table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly 'group(s)'. Each 'group' contains a series of 'path(s)', each 'path' contains a series of 'hop(s)', each 'hop' contains a series of 'statistics distribution bucket(s)'. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group is kept in the table until the table contains rttMonStatisticsAdminNumHourGroups groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonStatsCaptureStartTimeIndex object. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to 'inactive', the corresponding current hourly group in this table is 'frozen', and a new hourly group is created when activity is resumed. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to 'pending' this whole table will be cleared and reset to its initial state. When the RttMonRttType is 'pathEcho', the path exploration RTT request statistics will

not be accumulated in this table.

Note: When the RttMonRttType is 'pathEcho', a source to target rttMonStatsCapturePathIndex path will be created for each rttMonStatsCaptureStartTimeIndex to hold all errors that occur when a specific path had not been found or connection has not be setup.

Using this rttMonStatsCaptureTable, a managing application can retrieve summarized data from accurately measured periods, which is synchronized across multiple conceptual RTT control rows. With the new hourly group creation being performed on a 60-minute period, the managing station has plenty of time to collect the data, and need not be concerned with the vagaries of network delays and lost PDU's when trying to get matching data. Also, the managing station can spread the data gathering over a longer period, which removes the need for a flood of get requests in a short period which otherwise would occur.


187

Table 3-123 CISCO-RTTMON-MIB Tables and Descriptions (continued) Name Description

rttMonStatsCollectTable This table is a statistics collection database. Each entry in the table is an RttMonStatsCollectEntry. This table has the exact same behavior as the rttMonStatsCaptureTable, except that it does not hold statistical distribution information.

rttMonLatestJitterOperTable This table contains the status of the latest Jitter operation. Each entry in the table is an RttMonLatestJitterOperEntry. The Jitter statistics table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly 'group(s)'. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table stores only the latest entry.

rttMonStatsTotalsTable Not supported.

rttMonHTTPStatsTable Not supported.

rttMonJitterStatsTable Jitter statistics collection database. The Jitter statistics table contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly 'group(s)'. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table stores 2 hours of data.

rttMonLpdGrpStatsTable Auto SAA Layer 3 MPLS VPN LPD Group Database. The LPD Group statistics table contains summarized performance statistics for the LPD group. LPD Group—Set of 'single probes' which are subset of the 'lspGroup' probe traversing set of paths between two PE end points are grouped together and called as the LPD group. The LPD group is uniquely referenced by the LPD Group ID. A rolling accumulated history of this information is maintained in a series of hourly 'group(s)'. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group(s) is kept in the table until the table contains rttMplsVpnMonTypeLpdStatHours groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonLpdGrpStatsStartTimeIndex object.

rttMonHistoryCollectionTable History collection database. The history table contains a point by point rolling history of the most recent RTT operations for each conceptual RTT control row. The rolling history of this information is maintained in a series of 'live(s)', each containing a series of 'bucket(s)', each 'bucket' contains a series of 'sample(s)'. Each conceptual


188

history row can have lives. A life is defined by the rttMonCtrlOperRttLife object. A new life is created when rttMonCtrlOperState transitions 'active'. When the number of lives become greater than rttMonHistoryAdminNumLives the oldest life is discarded and a new life is created by incrementing the index. The path exploration RTT operation is kept as an entry in this table.


189

MIB Constraints

Table 3-124 lists the constraints on objects in the CISCO-RTTMON-MIB.

Table 3-124 CISCO-RTTMON-MIB Constraints

MIB Object Notes

rttMonApplPreConfigedTable Not supported—No back end IP SLA.

rttMonApplAuthTable Not supported—No back end IP SLA.

rttMonFileIOAdminTable Not supported—No back end IP SLA.

rttMonScriptAdminTable Not supported—No back end IP SLA.

rttMonReactAdminTable Not supported. This table is replaced by rtt- MonReactTable.

rttMonLatestHTTPOperTable Not supported—IP SLA in XR does not support HTTP probes.

rttMonGrpScheduleAdminTable Not supported—No back end IP SLA.

rttMonStatsTotalsTable Not supported—No back end IP SLA.

rttMonHTTPStatsTable Not supported—IP SLA in XR does not support HTTP probes.

rttMonGrpScheduleAdminProbes Not supported

rttMonGrpScheduleAdminPeriod Not supported

rttMonGrpScheduleAdminFrequency Not supported

rttMonGrpScheduleAdminLife Not supported

rttMonGrpScheduleAdminAgeout Not supported

rttMonGrpScheduleAdminStatus Not supported

rttMonGrpScheduleAdminStartTime Not supported

rttMonGrpScheduleAdminAdd Not supported

rttMonGrpScheduleAdminDelete Not supported

rttMonGrpScheduleAdminReset Not supported

rttMonApplAuthKeyChain Not supported

rttMonApplAuthKeyString1 Not supported





rttMonApplAuthStatus Not supported

rttMonGrpScheduleAdminFreqMax Not supported

rttMonGrpScheduleAdminFreqMin Not supported


190


191

CISCO-SELECTIVE-VRF-DOWNLOAD-MIB The CISCO-SELECTIVE-VRF-DOWNLOAD-MIB module defines objects describing selective VRF download. The selective VRF download feature makes a best effort to download only those prefixes and labels to a physical entity required to forward traffic through the physical entity. The feature accomplishes this by characterizing roles for physical entities based on their configuration. For more information about the commands related to the CISCO-SELECTIVE-VRF-DOWNLOAD-MIB, see http://www.cisco.com/en/US/docs/routers/asr9000/software/asr9k_r4.2/system_management/command _reference/b_sysman_cr42asr9k_chapter_01101.html#wp2072088589

MIB Tables

Table 3-125 lists the table defined under CISCO-SELECTIVE-VRF-DOWNLOAD-MIB.

Table 3-125 CISCO-SELECTIVE-VRF-DOWNLOAD-MIB Tables


csvdStateTable This table lists the state relating to the selective VRF download feature for each physical entity capable of forwarding packets. This table has an expansion dependent relationship on the entPhysicalTable, containing zero or more rows each row in the entPhysicalEntity. If the physical entity is capable of forwarding packets, it contains a row for each address family it supports.

csvdRoleHistoryTable This table lists the role change history per address family (ipv4 and ipv6) for each physical entity capable of forwarding packets. This table has an expansion dependant relationship on csvdStateTable, containing zero or more rows for each row in csvdStateTable.

csvdVrfTable This table lists VRF tables selectively downloaded to each physical entity capable of forwarding packets. This table has an expansion dependent relationship on the csvdStateTable, containing zero or more rows for each address family supported by each physical entity capable of forwarding packets.

MIB Constraints

Table 3-126 lists the constraints that the Cisco ASR 9000 Series router places on objects in the CISCO-SELECTIVE-VRF-DOWNLOAD-MIB.


192

Table 3-126 CISCO-SELECTIVE-VRF-DOWNLOAD-MIB Constraints MIB Object Notes

csvdEntityRoleChangeNotificationEnable Read-only. By default, this object is set to “False”.

csvdRoleHistorySize Read-only. By default, this object is set to 100.

Note: All objects are defined as read-only for the CISCO-SELECTIVE-VRF-DOWNLOAD-MIB.

CISCO-SONET-MIB The CISCO-SONET-MIB contains objects to manage SONET/SDH interfaces on the router. This MIB is an extension to the standard SONET-MIB (RFC 2558) and has objects that provide additional SONET-related information not found in the SONET-MIB. Note: CISCO-SONET-MIB supports SONET traps that are seen when the linestatus, sectionstatus, pathstatus changes, and Notifications are enabled.

MIB Tables Table 3-127 lists the table defined under CISCO-SONET-MIB.

Table 3-127 CISCO-SONET-MIB Tables


csConfigTable Displays the objects to configure the sonet lines.

csVTConfigTable Displays the objects to configure the VT/VC (Virtual Tributary / Virtual Container) related properties of SONET/SDH lines.

csApsConfigTable Displays the objects to configure APS (Automatic Protection Switching) in a SONET Line. APS is the functionality to configure a pair of SONET lines for redundancy so that the hardware automatically switches the active line from working line to the backup line, within 60milliseconds, when the active line fails.

cssTotalTable Displays the cumulative sum of the various CSS total statistics for the 24 hour period preceding

the current interval.

cssTraceTable Displays objects for tracing the sonet section.


193


cslTotalTable Displays the cumulative sum of the various CSL total statistics for the 24 hour period preceding


cslFarEndTotalTable Displays the cumulative sum of the various SCL far end total statistics for the 24 hour period preceding the current interval.

cspTotalTable Displays the cumulative sum of the various CSP total statistics for the 24 hour period preceding


cspFarEndTotalTable Displays the cumulative sum of the various CSP far end total statistics for the 24 hour period preceding the current interval. Far End is the remote end of the line.

cspTraceTable Displays the objects for tracing the sonet path.

csStatsTable Specifies the number of times a line encounters: Loss of signal(LOS) Loss of frame(LOF) Alarm indication signals(AISs) Remote failure indications(RFIs).

cspConfigTable Displays the Cisco extension to the SONET Path current table.

csAu4Tug3ConfigTable Displays the objects that configure the VC( Virtual Container) related properties of a TUG-3 within a AU-4 paths. This multiplexing structure is created using this table: STM-1/AU-4/TUG-3/TU-3/DS3 STM-1/AU-4/TUG-3/TU-3/E3 STM-1/AU-4/TUG-3/TUG-2/TU-11/DS1 STM-1/AU-4/TUG-3/TUG-2/TU-12/E1. Three entries are created in this table for a given AU-4 path when cspSonetPathPayload object is set to one of these: vt15vc11(4) vt2vc12(5) ds3(3) e3(8) vtStructured(9)

MIB Constraints

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


194

Table 3-128 CISCO-SONET-MIB Constraints

MIB Object Notes

csConfigLoopbackType Not supported

csConfigXmtClockSource Not supported

csConfigFrameScramble Not supported

csConfigRDIPType Not supported

csConfigRDIVType Not supported

cspSonetPathPayload Not supported

csTributaryType Not supported

csTributaryMappingType Not supported

csTributaryFramingType Not supported

csSignallingTransportMode Not supported

csTributaryGroupingType Not supported

csAu4Tug3Payload Not supported

cspTributaryMappingType Not supported

cspSignallingTransportMode Not supported

cspTributaryGroupingType Not supported

csApsProtectionIndex Not supported

csApsEnable Not supported

csApsArchMode Not supported

csApsSigFaultBER Not supported

csApsSigDegradeBER Not supported

csApsWaitToRestore Not supported

csApsDirection Not supported

csApsRevertive Not supported

csApsChannelProtocol Not supported

CISCO-SUBSCRIBER-SESSION-MIB

This MIB defines objects describing subscriber sessions, or more specifically, subscriber sessions terminated by a RAS. A subscriber session consists of the traffic between a CPE and a NAS.

MIB Tables

Table 3-129 lists the table defined under CISCO-SUBSCRIBER-SESSION-MIB:


195

Table 3-129 CISCO-SUBSCRIBER-SESSION-MIB Tables


csubAggStatsTable

csubAggStatsUpSessions Current number of active sessions.

csubAggStatsHighUpSessions Highest number of concurrently active sessions.

csubAggStatsDiscontinuityTime Time when the last event occurred where an event

could be missed to invalidate the counters supported.

csubAggThreshTable

csubSessionRisingThresh Threshold for triggering csubSessionRisingNotif when session count rises above

csubSessionFallingThresh Threshold for triggering csubSessionFallingNotif when session count drops below

csubSessionDeltaPercentFallingThresh Threshold for triggering csubSessionDeltaPercentLossNotif when session count drops by the percentage over the measurement interval.

csubSessionThreshEvalInterval Interval of time for the periodic sampling of the session values.

CISCO-SYSLOG-MIB The CISCO-SYSLOG-MIB contains objects to manage all the system log messages generated by the Cisco IOS XR Software. The MIB provides a way to access the syslog messages through SNMP. All Cisco IOS XR syslog messages contain the message name and its severity, message text, the name of the entity generating the message, and an optional time stamp. The MIB also contains a history of syslog messages and counts related to syslog messages. Note: You can configure the Cisco ASR 9000 Series router to send syslog messages to a syslog server. Note: The MIB does not keep track of messages generated from debug commands entered through the command-line interface (CLI). Table 3-130 lists the tables associated with this MIB.


196

Table 3-130 CISCO-SYSLOG-MIB Tables and Descriptions Name Description

clogHistoryTable Table of syslog messages generated by this device. All 'interesting' syslog messages (that is, severity <= clogMaxSeverity) are entered into this table.

clogServerConfigTable This table contains entries that allow application to configure syslog servers for the system. The maximum number of entries that can be created for this table is limited by the object clogMaxServers.

MIB Constraints Table 3-131 lists the constraints on objects in the CISCO-SYSLOG-MIB.

Table 3-131 CISCO-SYSLOG-MIB Constraints

MIB Object Notes

clogServerMaxTable Not supported

CISCO-SYSTEM-MIB The CISCO-SYSTEM-MIB provides a standard set of basic system information. This MIB module contains Cisco-defined extensions to the systemGroup. This MIB has no tables.

MIB Constraints Table 3-132 lists the constraints on objects in the CISCO-SYSTEM-MIB.

Table 3-132 CISCO-SYSTEM-MIB Constraints

MIB Object Notes

csyNotificationsEnable Not supported

CISCO-TAP2-MIB

The CISCO-TAP2-MIB manages Cisco’s intercept feature. This MIB replaces CISCO-TAP-MIB. This MIB defines a generic stream table that contains fields common to all intercept types. Specific intercept filters are defined in extension MIBs. They are CISCO-IP-TAP-MIB for IP intercepts, CISCO-802-TAP-MIB for IEEE 802 intercepts and CISCO-USER-CONNECTION-TAP-MIB for RADIUS-based user connection intercepts.


197


Table 3-133 CISCO-TAP2-MIB Tables and Descriptionsame Description

cTap2MediationTable This table lists the Mediation Devices with which the intercepting device communicates. These may be on the same or different Mediation Devices. This table is written by the Mediation Device, and is always volatile. This is because intercepts may disappear during a restart of the intercepting equipment. Entries are added to this table via cTap2MediationStatus in accordance with the RowStatus convention.

cTap2StreamTable This table lists the traffic 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. The Table consists of generic fields that are independent of the type of intercept. It contains type of the specific filter which is defined in an extension MIB and counters to account for packets intercepted or dropped by the attached filter specification. Note that the Mediation Device must make sure there is only one type of specific filter created with the same indices as that of a row in this table, otherwise the later creations will fail.

cTap2DebugTable This table contains Lawful Intercept debug messages generated

by the implementing device. This table is used by ciscoTap2MediationDebug and ciscoTap2StreamDebug notifications. An entry in this table contains a debug message which is regarding either a Mediation Device or a intercept stream created by a Mediation Device.

cTap2DebugUserTable This table lists information of all the users configured in the system who are given permission by different Mediation Devices to access Lawful Intercept CLIs. This table will have dependancy on cTap2MediationTable. When entry in cTap2MediationTable is deleted or moved to ’notInService’, entries corresponding cTap2MediationContentId in this table will be deleted.

MIB Constraints

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


198

Table 3-134 CISCO-TAP2-MIB Constraints

MIB Object Notes

cTap2MediationDestAddressType Read-create

cTap2MediationDestAddress Read-create

cTap2mediationDestPort Read-create

cTap2MediationSrcInterface Read-create

cTap2MediationRtcpPort Not Supported. Read-only

cTap2MediationDscp Read-create

cTap2MediationDataType Not Supported. Read-create

cTap2MediationRetransmitType Not Supported. Read-create

cTap2MediationTimeout Read-create

cTap2MediationTransport Read-create

cTap2MediationNotificationEnable Read-create

cTap2MediationStatus Read-create

cTap2MediationNewIndex Read-only

cTap2MediationCapabilities Read-only

cTap2StreamType Read-create

cTap2StreamInterceptEnable Read-create

cTap2StreamInterceptedPackets Read-only

cTap2StreamInterceptDrops Read-only

cTap2StreamStatus Read-create

cTap2DebugAge Read-only

cTap2DebugMaxEntries Read-only

cTap2DebugMediationId Read-only

cTap2DebugStreamId Read-only

cTap2DebugMessage Read-only

cTap2DebugStatus Read-write


199

CISCO-TCP-MIB The CISCO-TCP-MIB is an extension to the IETF MIB module for managing TCP implementations. Table 3-135 lists the tables associated with this MIB.

Table 3-135 CISCO-TCP-MIB Tables and Descriptions

Name Description

ciscoTcpConnTable Table containing TCP connection-specific information.


200

CISCO-VPDN-MGMT-MIB

This MIB is to support the Virtual Private Dialup Network (VPDN) feature. VPDN handles the forwarding of PPP links from an Internet Provider (ISP) to a Home Gateway. The VPDN MIB provides the operational information on Cisco’s VPDN tunnelling implementation. The following entities are managed:

1. Global VPDN information 2. VPDN tunnel information 3. VPDN tunnel’s user information 4. Failure history per user


Table 3-136 CISCO-VPDN-MGMT-MIB Tables and Descriptions Name Description

cvpdnSystemEntryTable

cvpdnSystemTunnelTotal.21 Indicates total number of tunnels

cvpdnSystemSessionTotal.2 Indicates total number of sessions.

1. .2 indicates tunnel type and VPDN mib supports l2 tunnels only.

CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB The CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB lists VLAN-id and ifIndex information for routed VLAN interfaces. The MIB contains entries for all sub-interfaces that have a basic 802.1Q VLAN Id configured, but excludes any sub-interfaces configured with a more complex encapsulation (that is double tagged, 802.1ad tagged, VLAN ranges). Table 3-137 lists the tables associated with this MIB.

Table 3-137 CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB Tables and Descriptions Name Description

cviVlanInterfaceIndexTable cviVlanInterfaceIndexTable provides a way to translate a VLAN-id in to an ifIndex, so that the routed VLAN interface routing configuration can be obtained from interface entry in ipRouteTable. Note that some routers can have interfaces to multiple VLAN management domains, and therefore can have multiple routed VLAN interfaces which connect to different VLANs having the same VLAN-id. Thus, it is possible to have multiple rows in this table for the same VLAN-id. The cviVlanInterfaceIndexTable also provides a way to find the VLAN-id from an ifTable VLAN ifIndex.


201

DISMAN-EXPRESSION-MIB The DISMAN-EXPRESSION-MIB module is used for defining expressions of MIB objects for management purposes.

MIB Tables Table 3-138 lists the tables in DISMAN-EXPRESSION-MIB:

Table 3-138 DISMAN-EXPRESSION-MIB Tables and Descriptions

Name Description

expExpressionTable A table of expression definitions.

expErrorTable A table of expression errors.

expObjectTable A table of object definitions for each expExpression. Wildcarding instance IDs: It is legal to omit all or part of the instance portion for

some or all of the objects in an expression.

expValueTable A table of values from evaluated expressions.

DOT3-OAM-MIB This MIB module manages the new Ethernet OAM features introduced by the Ethernet in the First Mile taskforce (IEEE 802.3ah). The functionality presented here is based on IEEE 802.3ah [802.3ah], released in October, 2004. [802.3ah] was prepared as an addendum to the standing version of IEEE 802.3 [802.3-2002]. Since then, [802.3ah] has been merged into the base IEEE 802.3 specification in [802.3-2005]. In particular, this MIB focuses on the new OAM functions introduced in Clause 57 of [802.3ah]. The OAM functionality of Clause 57 is controlled by new management attributes introduced in Clause 30 of [802.3ah]. The OAM functions are not specific to any particular Ethernet physical layer, and can be generically applied to any Ethernet interface of [802.3-2002]. An Ethernet OAM protocol data unit is a valid Ethernet frame with a destination MAC address equal to the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), a lengthOrType field equal to the reserved type for Slow Protocols, and a Slow Protocols subtype equal to that of the subtype reserved for Ethernet OAM.

MIB Tables

Table 3-139 lists the tables in DOT3-OAM-MIB:

Table 3-139 DOT3-OAM-MIB Tables and Descriptions

Name Description

dot3OamTable This table contains the primary controls and status for the OAM capabilities of an Ethernet-like interface. There will be one row in this

table for each Ethernet-like interface in the system that supports the OAM functions defined in [802.3ah].


202

Table 3-139 DOT3-OAM-MIB Tables and Descriptions (continued) Name Description

dot3OamPeerTable This table contains information about the OAM peer for a particular Ethernet-like interface. OAM entities communicate with a single OAM peer entity on Ethernet links on which OA is enabled and operating properly. There is one entry in this table for each entry in the dot3OamTable for which information on the peer OAM entity is available.

dot3OamLoopbackTable

This table contains controls for the loopback state of the local link as well as indicates the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set).

dot3OamStatsTable This table contains statistics for the OAM function on a particular Ethernet-like interface. There is an entry in the table for every entry in the dot3OamTable. The counters in this table are defined as 32-bit entries to match the counter size as defined in [802.3ah]. Given that the OA protocol is a slow protocol, the counters increment at a slow rate.

dot3OamEventConfigTable

Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This table contains the mechanisms to enable Event Notifications and configure the thresholds to generate the standard Ethernet OAM events.

dot3OamEventLogTable This table records a history of the events that have occurred at the Ethernet OAM level.

MIB Constraints Table 3-140 lists the constraints that the Cisco ASR 9000 Series router places on objects in the DOT3-OAM-MIB. Table 3-140 DOT3-OAM-MIB Constraints

MIB Object Notes

dot3OamTable

dot3OamEntry Read-only

dot3OamAdminState Read-only

dot3OamOperStatus Read-only

dot3OamMode Read-only

dot3OamMaxOamPduSize Read-only

dot3OamConfigRevision Read-only

dot3OamFunctionsSupported Read-only

dot3OamPeerTable


203

dot3OamPeerEntry Read-only

dot3OamPeerMacAddress Read-only


204

Table 3-140 DOT3-OAM-MIB Constraints (continued) MIB Object Notes

dot3OamPeerVendorOui Read-only

dot3OamPeerVendorInfo Read-only

dot3OamPeerMode Read-only

dot3OamPeerMaxOamPduSize Read-only

dot3OamPeerConfigRevision Read-only

dot3OamPeerFunctionsSupported Read-only

dot3OamLoopbackTable

dot3OamLoopbackEntry Read-only

dot3OamLoopbackStatus Read-only

dot3OamLoopbackIgnoreRx Read-only

dot3OamStatsTable

dot3OamStatsEntry Read-only

dot3OamInformationTx Read-only

dot3OamInformationRx Read-only

dot3OamUniqueEventNotificationTx Read-only

dot3OamUniqueEventNotificationRx Read-only

dot3OamDuplicateEventNotificationTx Read-only

dot3OamDuplicateEventNotificationRx Read-only

dot3OamLoopbackControlTx Read-only

dot3OamLoopbackControlRx Read-only

dot3OamVariableRequestTx Read-only

dot3OamVariableRequestRx Read-only

dot3OamVariableResponseTx Read-only


205

dot3OamVariableResponseRx Read-only

dot3OamOrgSpecificTx Read-only

dot3OamOrgSpecificRx Read-only

dot3OamUnsupportedCodesTx Read-only

dot3OamUnsupportedCodesRx Read-only

dot3OamFramesLostDueToOam Read-only

dot3OamEventConfigTable

dot3OamEventConfigEntry Read-only

dot3OamErrSymPeriodWindowHi Read-only


206

Table 3-140 DOT3-OAM-MIB Constraints (continued)

MIB Object Notes dot3OamErrSymPeriodWindowLo Read-only

dot3OamErrSymPeriodThresholdHi Read-only

dot3OamErrSymPeriodThresholdLo Read-only

dot3OamErrSymPeriodEvNotifEnable Read-only

dot3OamErrFramePeriodWindow Read-only

dot3OamErrFramePeriodThreshold Read-only

dot3OamErrFramePeriodEvNotifEnable Read-only

dot3OamErrFrameWindow Read-only

dot3OamErrFrameThreshold Read-only

dot3OamErrFrameEvNotifEnable Read-only

dot3OamErrFrameSecsSummaryWindow Read-only

dot3OamErrFrameSecsSummaryThreshold Read-only

dot3OamErrFrameSecsEvNotifEnable Read-only

dot3OamDyingGaspEnable Read-only

dot3OamCriticalEventEnable Read-only

dot3OamEventLogTabledot3OamEventLogEntry Read-only

dot3OamEventLogIndex Read-only

dot3OamEventLogTimestamp Read-only

dot3OamEventLogOui Read-only

dot3OamEventLogType Read-only

dot3OamEventLogLocation Read-only

dot3OamEventLogWindowHi Read-only

dot3OamEventLogWindowLo Read-only

dot3OamEventLogThresholdHi Read-only

dot3OamEventLogThresholdLo Read-only


207

dot3OamEventLogValue Read-only

dot3OamEventLogRunningTotal Read-only

dot3OamEventLogEventTotal Read-only

DS1-MIB (RFC 2495) The DS1-MIB(RFC-2495) contains a description of DS1, E1, DS2, and E2 interfaces objects.

MIB Tables Table 3-141 lists the tables in DS1-MIB:


208

Table 3-141 DS1-MIB Tables and Descriptions Name Description

dsx1ConfigTable DS1 Configuration table.

dsx1CurrentTable DS1 current table contains various statistics being collected for the current 15-minute interval.

dsx1IntervalTable DS1 Interval Table contains various statistics collected by each DS1 Interface over the previous 24-hours of operation. The past 24 hours are broken into 96 completed 15-minute intervals. Each row in this table represents one such interval (identified by dsx1IntervalNumber) for one specific instance (identified by dsx1IntervalIndex).

dsx1TotalTable DS1 Total Table contains the cumulative sum of the various statistics for the 24-hour period preceding the current interval.

dsx1ChanMappingTable DS1 Channel Mapping table. This table maps a DS1 channel number on a particular DS3 into an ifIndex. In the presence of DS2s, this table can be used to map a DS2 channel number on a DS3 into an ifIndex, or used to map a DS1 channel number on a DS2 onto an ifIndex.

dsx1FarEndCurrentTable DS1 Far End Current table contains various statistics being collected for the current 15-minute interval. The statistics are collected from the far end messages on the Facilities Data Link. The definitions are the same as described for the near-end information.

dsx1FarEndIntervalTable DS1 Far End Interval Table contains various statistics collected by each DS1 interface over the previous 24-hours of operation. The past 24 hours are broken into 96 completed 15-minute intervals. Each row in this table represents one such interval (identified by dsx1FarEndIntervalNumber) for one specific instance (identified by dsx1FarEndIntervalIndex).

dsx1FarEndTotalTable DS1 Far End Total Table contains the cumulative sum of the various statistics for the 24-hour period preceding the current interval.


209

Table 3-141 DS1-MIB Tables and Descriptions (continued) Name Description

dsx1FracTable Table is deprecated, use ifStackTable. The table was mandatory for systems dividing a DS1 into channels containing different data streams that are of local interest. Systems which are indifferent to data content, such as CSUs, need not implement it. The DS1 fractional table identifies which DS1 channels associated with a CSU are being used to support a logical interface, that is, an entry in the interfaces table from the Internet-standard MIB. Consider an application managing a North American ISDN Primary Rate link whose division is a 384 kbit/s H1 _B_Channel for Video, a second H1 for data to a primary routing peer, and 1264 kbit/s H0 _B_ Channels. Consider that some subset of the H0 channels are used for voice and the remainder are available for dynamic data calls. There is a total of 14 interfaces multiplexed onto the DS1 interface. Six DS1 channels (for example, channels 1 to 6) are used for Video, six more (7 to 11 and 13) are used for data. The remaining 12 are in channels 12 and 14 to 24. If ifIndex 2 is of type DS1 and refers to the DS1 interface, and that the interfaces layered onto it are numbered 3 to 16. dsx3FracIfIndex.2.1 = 3 dsx3FracIfIndex.2.2 = 3 dsx3FracIfIndex.2.3 = 3 dsx3FracIfIndex.2.4 = 3 dsx3FracIfIndex.2.5 = 3 dsx3FracIfIndex.2.6 = 3 dsx3FracIfIndex.2.7 = 4 dsx3FracIfIndex.2.8 = 4 dsx3FracIfIndex.2.9 = 4 dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.13 = 4 dsx3FracIfIndex.2.14 = 6 dsx3FracIfIndex.2.15 = 7 dsx3FracIfIndex.2.16 = 8 dsx3FracIfIndex.2.17 = 9 dsx3FracIfIndex.2.18 = 10 dsx3FracIfIndex.2.19 = 11 dsx3FracIfIndex.2.20 = 12 dsx3FracIfIndex.2.21 = 13 dsx3FracIfIndex.2.22 = 14 dsx3FracIfIndex.2.23 = 15 dsx3FracIfIndex.2.24 = 16 For North American (DS1) interfaces, there are 24 legal channels, numbered 1 through 24. For G.704 interfaces, there are 31 legal channels, numbered 1 through 31. The channels (1 to 31) correspond directly to the equivalently numbered time-slots.

MIB Constraints


210

Table 3-142 lists the constraints that the Cisco ASR 9000 Series router places on objects in the DSI-MIB(RFC-2495).

Table 3-142 DS1-MIB Constraints MIB Object Notes

dsx1LineType Not supported

dsx1LineCoding Not supported

dsx1SendCode Not supported

dsx1CircuitIdentifier Not supported

dsx1LoopbackConfig Not supported

dsx1SignalMode Not supported

dsx1TransmitClockSource Not supported

dsx1Fdl Not supported

dsx1LineLength Not supported

dsx1Channelization Not supported

dsx1LineStatusChangeTrapEnable Not supported




dsx1SignalMode Not supported



Note: The intervals in a dsx1IntervalTable are reset during an OIR operation whereas the SONET intervals are not reset.

DS3-MIB

The DS3-MIB contains objects that describe DS3 and E3 interfaces objects.


211

MIB Tables Table 3-143 lists the tables in DS3-MIB.


212

Table 3-143 DS3-MIB TablesMIB Table Descriptiondsx3ConfigTable Provides the D3/S3 configuration information.dsx3CurrentTable Provides statistics collected for the current 15

minute interval.dsx3IntervalTable1 Provides statistics collected by each DS3/E3

Interface over the previous 24 hours of operation. The previous 24 hours are broken into 96 completed 15 minute intervals. Each row in this table represents one such interval (identified by dsx3IntervalNumber) and a specific interface (identifed by dsx3IntervalIndex).

dsx3TotalTable Provides cumulative statistics logged for the 24 hour period preceding the current interval.

dsx3FarEndConfigTable Provides configuration information reported in the C-bits from the remote end.

dsx3FarEndCurrentTable Provides statistics collected for the current 15 minute interval. The statistics are collected from the far end block error code within the C- bits.

dsx3FarEndIntervalTable provides statistics collected by each DS3 interface over the previous 24 hours of operation. The past 24 hours are broken into 96 completed 15 minute intervals.

dsx3FarEndTotalTable Provides cumulative sum of the various statistics for the 24 hour period preceding the current interval.

dsx3FracTable Deprecated, use ifStackTable instead. 1. Interval information in dsx3IntervalTable resets after an OIR operation is performed.

MIB Constraints Table 3-144 lists the constraints that the Cisco ASR 9000 Series router places on objects in the DS3-MIB: Table 3-144 DS3-MIB Constraints

MIB Object Notes

dsx3FarEndEquipCode Not supported

dsx3FarEndLocationIDCode Not supported

dsx3FarEndFrameIDCode Not supported

dsx3FarEndUnitCode Not supported

dsx3FarEndFacilityIDCode Not supported

dsx3LineStatusChangeTrapEnable Not supported



213

Table 3-144 DS3-MIB Constraints (continued)

MIB Object Notes



dsx3CircuitIdentifier Not supported

dsx3LoopbackConfig Not supported


dsx3LineLength Not supported


dsx3Ds1ForRemoteLoop Not supported

ENERGY-OBJECT-MIB

This MIB is used to monitor power and energy in devices. This table sparse extension of the eoTable from the ENERGY-AWARE-MIB. As a requirement [EMAN-AWARE-MIB] should be implemented. Module Compliance of ENTITY-MIB v4 with respect to entity4CRCompliance should be supported which requires implementation of 3 MIB objects (entPhysicalIndex, entPhysicalName and entPhysicalUUID). This table lists the tables associated with this MIB.

Name Description

eoPowerTable This table lists Energy Objects.

eoPowerStateTable This table enumerates the maximum power usage, in watts, for every single supported Power State of each Energy Object. This table has an expansion-dependent relationship on the eoPowerTable, containing rows describing each Power State for the corresponding Energy Object. For every Energy Object in the eoPowerTable, there is a corresponding entry in this table.

ENTITY-MIB (RFC 2737) The ENTITY-MIB (RFC 2737) allows functional component discovery. It is used to represent physical and logical entities (components) in the router and manages those entities. It defines managed objects for representing multiple logical entities supported by a single SNMP agent. The entity modeling is: Line card port with line card as the parent The Xcvr container with Line card port as the parent If Xcvr is present, Xcvr module with Xcvr container as parent


214

The current software release supports the RFC 2737 version of this MIB.


215

The following are the conformance groups contained in the ENTITY-MIB: entityPhysical group—Describes the physical entities managed by a single agent. entityLogical group—Describes the logical entities managed by a single agent. entityMapping group—Describes the associations between the physical entities, logical entities, interfaces, and non-

interface ports managed by a single agent. entityGeneral group—Describes general system attributes shared by potentially all types of entities managed by a

single agent. entityNotifications group—Contains status indication notifications.

The following groups are added from RFC 2737: entityPhysical2 group—This group augments the entityPhysical group. entityLogical2 group—Describes the logical entities managed by a single agent, and replaces entityLogical group.

The MIB table entPhysicalTable identifies the physical entities in the router. The entPhysicalTable contains a single row for the Cisco ASR 9000 Series router chassis and a row for each entity in the chassis. A physical entity may contain other entities.

MIB Tables

Table 3-145 lists the MIB tables in ENTITY-MIB Table 3-145 ENTITY-MIB Tables


entPhysicalTable Displays a single row for each physical entity.

entLogicalTable Displays a single row for each logical entity.

entLPMappingTable Displays rows representing association between a logical entity and the corresponding physical equipment. For each logical entity, there are zero or more mappings to the physical resources, which are used to identify the logical entity.

entAliasMappingTable Displays rows representing mappings of logical entity and physical component to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical naming scope of an entity.

entPhysicalContainsTable Displays the container-to-containee relationships between the various physical entities. If a physical entity is contained by more than one physical entities (for example, double-wide modules), this table includes the additional mappings, which cannot be represented in the entPhysicalTable virtual containment tree.


216

MIB Constraints Table 3-146 lists the constraints that the Cisco ASR 9000 Series router places on objects in the ENTITY-MIB.

Table 3-146 ENTITY-MIB ConstraintsMIB Object Notes

entPhysicalTable SNMP sets are not supported. Unable to show information for powered down LC modules. No entry for preconfigured interfaces

cefcFRUPowerStatusTable SNMP sets not supported. (cefcFRUPowerAdminStatus)

entModuleTable SNMP sets not supported. (cefcModuleAd- minStatus)

entLogicalTable entLogicalType not supported. entLPMpapingTable entLogicalCommunity Not supported. entLogicalTAddress Not supported. entLogicalTDomain Not supported. entLogicalContextEngineID Not supported. entLogicalContextName Not supported. entPhysicalSerialNum Not supported. entPhysicalAlias Not supported. entPhysicalAssetID Not supported.

Note: SPA Transceiver sensors are not modeled in ASR 9000 release 3.9.

ENTITY-STATE-MIB

The ENTITY-STATE-MIB defines a state extension to the Entity MIB. Copyright (C) The Internet Society 2005. This version of this MIB module is part of RFC 4268; see the RFC itself for full legal notices. Table 3-147 lists the tables associated with this MIB.


217

Table 3-147 ENTITY-STATE-MIB Tables and Descriptions Name Description

entStateTable A table of information about state/status of entities. This is a sparse augment of the entPhysicalTable. Entries appear in this table for values of entPhysicalClass [RFC4133] that in this implementation are able to report any of the state or status stored in this table.

MIB Constraints Table 3-148 lists the constraints on objects in the ENTITY-STATE-MIB.

Table 3-148 ENTITY-STATE-MIB Constraints

MIB Object Notes

entStateLastChanged Supported

entStateAdmin Read-only

entStateOper Supported

entStateUsage Not Supported

entStateAlarm Not Supported

entStateStandby Supported

ETHERLIKE-MIB (RFC 2665, 3635) The ETHERLIKE-MIB (RFC 2665) contains objects to manage Ethernet-like interfaces.

MIB Constraints Table 3-149 lists the constraints on objects in the ETHERLIKE-MIB.

Table 3-149 ETHERLIKE-MIB Constraints

MIB Object Notes

dot3PauseAdminMode Not supported

EVENT-MIB The EVENT-MIB contains objects to define event triggers and actions for network management purposes. Table 3-150 lists the tables associated with this MIB.


218

Table 3-150 EVENT-MIB Tables and Descriptions Name Description

mteTriggerTable Table of management event trigger information

mteTriggerDeltaTable Table of management event trigger information for delta sampling

mteTriggerExistenceTable Table of management event trigger information for existence triggers

mteTriggerBooleanTable Table of management event trigger information for boolean triggers

mteTriggerThresholdTable Table of management event trigger information for threshold triggers

mteObjectsTable Table of objects that can be added to notifications based on the trigger, trigger test, or event, as pointed to by entries in those tables

mteEventTable Table of management event action information

mteEventNotificationTable Table of information about notifications to be sent as a consequence of management events

mteEventSetTable Table of management event action information

MIB Constraints

Table 3-151 lists the constraints on objects in the EVENT-MIB.

Table 3-151 EVENT-MIB Constraints MIB Object Notes

mteTriggerDeltaDiscontinuityID Not supported.

mteTriggerDeltaDiscontinuityIDWildcard Not supported.

mteTriggerDeltaDiscontinuityIDType Not supported.

EXPRESSION-MIB

The EXPRESSION-MIB defines expressions of MIB objects for network management purposes. This MIB is an early snapshot of work done by the IETF Distributed Management working group. After this snapshot was taken, the MIB was modified, had new OIDs assigned, and then published as RFC 2982. Table 3-152 lists the tables associated with this MIB.


219


220

Table 3-152 EXPRESSION-MIB Tables and Descriptions Name Description

expNameTable Table of expression names, for creating and deleting expressions

expExpressionTable Table of expression definitions

expObjectTable

Table of object definitions for each expExpression. Wildcarding instance IDs: It is legal to omit all or part of the instance portion for some or all of the objects in an expression. (See the description of expObjectID for details). However, note that if more than one object in the same expression is wildcarded in this way, they all must be objects where that portion of the instance is the same. In other words, all objects may be in the same sequence or in different sequences but with the same semantic index value (that is, a value of ifIndex) for the wildcarded portion.

expValueTable Table of values from evaluated expressions

FRAME-RELAY-DTE-MIB

The FRAME-RELAY-DTE-MIB describes the use of a Frame Relay interface by a DTE. Table 3-153 lists the tables associated with this MIB.

Table 3-153 FRAME-RELAY-DTE-MIB Tables and Descriptions Name Description

frDlcmiTable Parameters for the Data Link Connection Management Interface for the frame relay service on this interface.

frCircuitTable Table containing information about specific DLC1 or virtual circuits.

frErrTable Table containing information about Errors on the Frame Relay interface. Discontinuities in the counters contained in this table are the same as apply to the ifEntry associated with the Interface.

1. DLC = data link connections

MIB Constraints Table 3-154 lists the constraints on objects in the FRAME-RELAY-DTE-MIB.


221

Table 3-154 FRAME-RELAY-DTE-MIB Constraints

MIB Object Notes

frTrapState Not supported.

frTrapMaxRate Not supported.

frCircuitState Not supported.

frCircuitCommittedBurst Not supported.

frCircuitExcessBurst Not supported.

frCircuitThroughput Not supported.

frDlcmiState Not supported.

frDlcmiAddress Not supported.

frDlcmiAddressLen Not supported.

frDlcmiPollingInterval Not supported.

frDlcmiFullEnquiryInterval Not supported.

frDlcmiErrorThreshold Not supported.

frDlcmiMonitoredEvents Not supported.

frDlcmiMaxSupportedVCs Not supported.

frDlcmiMulticast Not supported.

frDlcmiState Not supported.

frDlcmiAddress Not supported.

frDlcmiAddressLen Not supported.

frDlcmiPollingInterval Not supported.

frDlcmiFullEnquiryInterval Not supported.

frDlcmiErrorThreshold Not supported.

frDlcmiMonitoredEvents Not supported.

frDlcmiMaxSupportedVCs Not supported.

frDlcmiMulticast Not supported.

frDlcmiRowStatus Not supported.

frCircuitState Not supported.


222

frCircuitCommittedBurst Not supported.

frCircuitExcessBurst Not supported.

frCircuitThroughput Not supported.

frCircuitMulticast Not supported.

frCircuitLogicalIfIndex Not supported.

frCircuitRowStatus Not supported.

frTrapState Not supported.

IEEE8021-CFM-MIB

The IEEE8021-CFM-MIB is a Connectivity Fault Management (CFM) module for managing IEEE 802.1ag. Table 3-155 lists the tables associated with this MIB.

MIB Objects Table 3-155 IEEE8021-CFM-MIB Tables and Descriptions Names Descriptions

dot1agCfmStackTable This MIB table lists the Maintenance Points (MPs) that exist on each interface.

dot1agCfmVlanTable This MIB table lists the VLAN IDs associated with each service (Maintenance Association or MA). In IOS-XR, services are not associated with VLAN IDs (rather they are associated with Bridge Domains), hence this table is unsupported.

dot1agCfmDefaultMdTable The default Maintenance Domain (MD) level table is unsupported, since the concept of a default MD level does not exist in the IOS-XR implementation of CFM.

dot1agCfmConfigErrorListTable This table exports four configuration errors described in the 802.1ag standard. Of the four errors, two cannot be detected due to the distributed nature of the IOS-XR implementation (CFMleak and ConflictingVids), and two never occur (ExcessiveLevels and OverlappedLevels). Therefore, an empty table is returned.

dot1agCfmMdTable This MIB table lists the MDs that are configured.

dot1agCfmMaNetTable This MIB table lists the MAs that are configured for each MD.

dot1agCfmMaCompTable This MIB table lists the MAs that are configured for each MD, within each ‘bridge component’ in the router. This is to


223

handle routers which, for example, support 802.1ad by implementing separate virtual S-bridges and C-bridges. In IOS-XR there is only ever one ‘bridge component’ for a service, and hence this table has one entry per MA.

dot1agCfmMaMepListTable This MIB table contains the list of all Maintenance End Points (MEPs) configured for cross-check in an MA.

dot1agCfmMepTable This MIB table lists local MEPs.

dot1agCfmLtrTable This MIB table lists entries in the traceroute cache. Note that the results of exploratory linktrace operations are not presented in this MIB table.

dot1agCfmMepDbTable This MIB table lists peer MEPs for each local MEP.


224

MIB Constraints Table 3-156 lists the constraints on objects in the IEEE8021-CFM-MIB. Table 3-156 IEEE8021-CFM-MIB Constraints

MIB Object Notes dot1agCfmMdMaNextIndex Always 0 dot1agCfmMdMhfCreation Not supported dot1agCfmMdMhfIdPermission Always sendIdChassis(2) dot1agCfmMdRowStatus Always 'active' dot1agCfmMaNetRowStatus Always 'active' dot1agCfmMaComponentId Always '1' dot1agCfmMaCompPrimaryVlanId Not supported dot1agCfmMaCompIdPermission Always sendIdChassis(2) dot1agCfmMaCompNumberOfVids Not supported dot1agCfmMaCompRowStatus Always 'active' dot1agCfmMaMepListRowStatus Always 'active' dot1agCfmMepActive Not supported dot1agCfmMepErrorCcmLastFailure Not supported dot1agCfmMepFngAlarmTime Always 2.5s dot1agCfmMepFngResetTime Always 10s dot1agCfmMepLowPrDef Supported, if there is no ‘Report Defects’

configuration, or the ‘Report Defects’ configuration is compatible with the IEEE defects sets. Unsupported otherwise.

dot1agCfmMepPrimaryVid Not supported

dot1agCfmMepRowStatus Always 'active'

dot1agCfmMepTransmitLbmDataTlv Not supported

dot1agCfmMepTransmitLbmDestIsMepId Not supported dot1agCfmMepTransmitLbmDestMacAddress Not supported dot1agCfmMepTransmitLbmDestMepId Not supported dot1agCfmMepTransmitLbmMessages Not supported dot1agCfmMepTransmitLbmResultOK Not supported dot1agCfmMepTransmitLbmSeqNumber Not supported dot1agCfmMepTransmitLbmStatus Not supported dot1agCfmMepTransmitLbmVlanDropEnable Not supported dot1agCfmMepTransmitLbmVlanPriority Not supported dot1agCfmMepTransmitLtmEgressIdentifier Not supported dot1agCfmMepTransmitLtmFlags Not supported dot1agCfmMepTransmitLtmResult Not supported dot1agCfmMepTransmitLtmSeqNumber Not supported dot1agCfmMepTransmitLtmStatus Not supported dot1agCfmMepTransmitLtmTargetIsMepId Not supported dot1agCfmMepTransmitLtmTargetMacAddress Not supported dot1agCfmMepTransmitLtmTargetMepId Not supported dot1agCfmMepTransmitLtmTtl Not supported


225

Table 3-156 IEEE8021-CFM-MIB Constraints (continued) MIB Object Notesdot1agCfmMepXconCcmLastFailure Not Supported

dot1agCfmLtrReceiveOrder

Supported; the entries are not returned in the actual order they were received.

IEEE8023-LAG-MIB

The IEEE8023-LAG-MIB is the Link Aggregation module for managing IEEE Std. 802.3ad. Table 3-157 lists the tables associated with this MIB.

Table 3-157 IEEE8023-LAG-MIB Tables and Descriptions Name Description

dot3adAggTable Table that contains information about every Aggregator running the IEEE 802.3ad Link Aggregation Control Protocol that is associated with this System


226

Table 3-157 IEEE8023-LAG-MIB Tables and Descriptions (continued) Name Description

dot3adAggPortListTable Table that contains a list of all the ports associated with each Aggregator running the IEEE 802.3ad Link Aggregation Control Protocol.

dot3adAggPortTable Table that contains Link Aggregation Control configurationinformation about every Aggregation Port running the IEEE 802.3ad Link Aggregation Control Protocol associated with this device. A row appears in this table for each physical port

dot3adAggPortStatsTable Table that contains Link Aggregation information about every port running the IEEE 802.3ad Link Aggregation Control Protocol that is associated with this device. A row appears in this table for each physical port

dot3adAggPortDebugTable Table that contains Link Aggregation debug information about every port running the IEEE 802.3ad Link Aggregation Control Protocol that is associated with this device. A row appears in this table for each physical port

dot3adTablesLastChanged This object indicates the time of the most recent change to the dot3adAggTable, dot3adAggPortListTable or dot3AggPortTable.

MIB Constraints Table 3-158 lists the constraints on objects in the IEEE8023-LAG-MIB. Table 3-158 IEEE8023-LAG-MIB Constraints

MIB Object Notes

dot3adAggPortListTable dot3adAggPortListPorts is not supported. dot3adAggActorSystemPriority Not supported dot3adAggActorAdminKey Not supported dot3adAggCollectorMaxDelay Not supported dot3adAggPortActorSystemPriority Not supported dot3adAggPortActorAdminKey Not supported dot3adAggPortActorOperKey Not supported dot3adAggPortPartnerAdminSystemPriority Not supported dot3adAggPortPartnerAdminSystemID Not supported dot3adAggPortPartnerAdminKey Not supported


227

dot3adAggPortActorPortPriority Not supported dot3adAggPortPartnerAdminPort Not supported

dot3adAggPortPartnerAdminPortPriority Not supported


228

Table 3-158 IEEE8023-LAG-MIB Constraints (continued) MIB Object Notes

dot3adAggPortActorAdminState Not supported

dot3adAggPortPartnerAdminState Not supported

IETF-OSPF-TRAP-MIB

An ospfIfStateChange trap signifies that there has been a change in the state of a non-virtual OSPF interface. This trap should be generated when the interface state regresses (e.g., goes from Dr to Down) or progresses to a terminal state (i.e., Point-to-Point, DR Other, Dr, or Backup).

MIB Objects

IETF-OSPF-TRAP-MIB Objects MIB Object Notes

ospfIfStateChange Supported

ospfRouterId SupportedospfIfIpAddress SupportedospfIfState SupportedospfAddressLessIf Supported

IETF-TCP-MIB

The IETF-TCP-MIB module is used for managing TCP implementations. Copyright (C) The Internet Society (2004). This version of this MIB module is a part of RFC xxxx; see the RFC itself for full legal notices.

MIB Tables Table 3-159 lists the tables in IETF-TCP-MIB:

Table 3-159 IETF-TCP-MIB Tables


tcpConnectionTable A table containing information about existing TCP connections. Note that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state.

tcpListenerTable A table containing information about TCP listeners.


229

IETF-UDP-MIB

The IETF-UDP-MIB module manages UDP implementations.

MIB Tables

Table 3-160 lists the tables in IETF-UDP-MIB.

Table 3-160 IETF-UDP-MIB Tables


udpEndpointTable A table containing information about this entity’s UDP endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction.

IF-MIB (RFC 2863)

The IF-MIB (RFC 2863) describes the attributes of physical and logical interfaces (network interface sublayers). The router supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, and ifHighSpeed). One of the most commonly used identifiers in SNMP-based network management applications is the Interface Index (ifIndex) value. IfIndex is a unique identifying number associated with a physical or logical interface. To provide access to information on selected interfaces stored in IF-MIB table to a user, this MIB is made vrf-aware. This makes management of IF-MIB table for VRF based networks more secure. Context based community can be used only when VRF based polling needs to be done.

Note: The ifHighSpeed and ifSpeed for an interface with type ds1 is zero. The object ifNumber is not commited on SNMP Data Collection Manager (DCM).

MIB Tables Table 3-161 lists the tables in IF-MIB:

Table 3-161 IF-MIB Tables


ifTable List of the interface entries (represented by the


230

value of ifNumber). This table is vrf-aware.

ifXTable List of interface entries (represented by the value of ifNumber). This table contains additional objects for the interface table. This table is vrf-aware.

ifStackTable Provides the information about the relationships between the multiple sub-layers of network interfaces.


231


ifRcvAddressTable Displays an entry for each address (broadcast, multicast, or unicast) for which the system receives packets/frames on a particular interface. The ifRcvAddressTable is vrf-aware. Exceptions are (Exceptions are not clear, please explain):

For an interface operating in promiscuous mode, entries are only required for those addresses for which the system would receive frames were it not operating in promiscuous mode. For 802.5 functional addresses, only one entry is required, for the address which has the functional address bit ANDed with the bit mask of all functional addresses for which the interface will accept frames. A system is able to use any unicast address, which corresponds to an entry in this table as a source address.

ifTestTable Displays an entry for each interface and lists the objects that allow a network manager to instruct an agent to test an interface for various faults. Tests for an interface are defined in the media-specific MIB for that interface.

MIB Constraints Table 3-162 lists the constraints on objects in the IF-MIB.

Table 3-162 IF-MIB Constraints MIB Object Notes

dot3adAggPortListTable dot3adAggPortListPorts is not supported. ifRcvAddressStatus Supported ifRcvAddressType Supported ifStackStatus Supported ifTestTable Not supported

IMA-MIB The MIB module describes Cisco IMA objects. This is an extension to the standard of ATM Forum IMA version 1.1.


232

MIB Objects

Name Description

cimaGroupTable The Cisco IMA group table. This table contains Cisco extension objects for the imaGroupTable. Each entry in the table contains Cisco specific configuration, control, and status information for each IMA group.

cimaLinkMappingTable The link mapping table is an IMA group oriented mapping table which associates an IMA group to its corresponding IMA links. It provides an efficient way of accessing to IMA links based on the knowledge of an IMA group. This is a read-only mapping table. The agent creates an entry when an IMA link identified by ’imaLinkIfIndex’ is added to an IMA group identified by ’imaGroupIndex’. The agent removes an entry when an IMA link identified by ’imaLinkIfIndex’ is removed from an IMA group identified by ’imaGroupIndex’. A state object ’cimaLinkState’ provides the link state in either ’active’ or ’nonactive’. The management station can query detailed information in imaGroupTable, and imaLinkTable with the two index readily available.

cimaLinkTable The Cisco IMA link table. This table has Cisco specific configuration, and status management information for IMA links.

cimaFeatureTable The Cisco IMA feature table. This table provides IMA features supported in a Cisco card. Any SNMP set to the writable object has card wide impact on all IMA groups and IMA links.

MIB Constraints Table 3-163 lists the constraints on objects in the IMA-MIB. Table 3-163 IMA-MIB Constraints

MIB Object Notes

imaLinkRowStatus Not supported

imaLinkGroupIndex Not supported

imaGroupTestLinkIfIndex Not supported

imaGroupTestPattern Not supported

imaGroupTestProcStatus Not supported

imaGroupRowStatus Not supported

imaGroupSymmetry Not supported


233

Table 3-163 IMA-MIB Constraints (continued)

MIB Object Notes

imaGroupMinNumTxLinks Not supported

imaGroupMinNumRxLinks Not supported

imaGroupNeTxClkMode Not supported

imaGroupTxImaId Not supported

imaGroupTxFrameLength Not supported

imaGroupDiffDelayMax Not supported

imaGroupAlphaValue Not supported

imaGroupBetaValue Not supported

imaGroupGammaValue Not supported

IP-FORWARD-MIB The IP-FORWARD-MIB contains objects to control the display of Classless Interdomain Routing (CIDR) multipath IP routes. To provide selective access to information stored in IP forwarding table to user, the IP-FORWARD-MIB is made vrf-aware. This makes management of IP forwarding table for VRF based networks more secure. Table 3-164 lists the tables associated with this MIB.

Table 3-164 IP-FORWARD-MIB Tables and Descriptions

Name Description

inetCidrRouteTable This entity’s IP Routing table (when MIB is used to poll IPv6 route information).

ipCidrRouteTable This entity’s IP Routing table. This table has been deprecated in favor of the IP version neutral inetCidrRouteTable. The ipCidrRouteTable is vrf-aware.

ipForwardTable This entity’s IP Routing table. The ipForwardNumber object is vrf-aware.

MIB Constraints Table 3-165 lists the constraints on objects in the IP-FORWARD-MIB. Table 3-165 IP-FORWARD-MIB Constraints

MIB Object Notes

ipCidrRouteIfIndex Supported

ipCidrRouteType Supported


234

ipCidrRouteInfo Supported

ipCidrRouteNextHopAS Supported


235

Table 3-165 IP-FORWARD-MIB Constraints (continued) MIB Object

Notes

ipCidrRouteMetric1 Supported ipCidrRouteMetric2 Supported ipCidrRouteMetric3 Supported ipCidrRouteMetric4 Supported ipCidrRouteMetric5 Supported ipCidrRouteStatus Supported

IP-MIB

The IP-MIB contains objects for managing IP and Internet Control Message Protocol (ICMP) implementations. Note: The IP-MIB does not provide functionality to manage IP routes.

MIB Tables Table 3-166 lists the tables in IP-MIB:

Table 3-166 IP-MIB Tables


ipv4InterfaceTable Provides IPv4-specific information for each interface.

ipv6InterfaceTable Provides IPv6-specific information for each interface.

ipSystemStatsTable Provides system wide IP version specific traffic statistics.

ipIfStatsTable Provides traffic statistics for each interface.

ipAddressPrefixTable Provides information that helps a user to addresses. The information in this table is linked to other tables through reference. For example, when the node configures both a unicast and anycast address for a prefix, the ipAddressPrefix objects for those addresses point to a single row in this table. This table primarily provides support for IPv6 prefixes.


236

MIB Table DescriptionipAddressTable Provides addressing information related to the interfaces.

This table does not contain multicast address information. This table is used for storing and managing temporary interface entries. Note: When including IPv6 link-local addresses in this table, the entry must use an InetAddressType of ipv6z to differentiate between the possible interfaces.

ipNetToPhysicalTable Provides mapping information between IP determine the source of an IP address or set of IP addresses and physical addresses. The address translation tables contain the IP address to the corresponding physical address. Some interfaces do not use translation tables for determining address equivalences (for example, DDN-X.25 has an algorithmic method); if all interfaces do not use this table, then this table is empty.

ipv6ScopeZoneIndexTable Displays IPv6 unicast and multicast scope zones.ipDefaultRouterTable Displays the default routers known to a specific entity.

ipv6RouterAdvertTable Provides information used to construct router advertisements.

icmpStatsTable Displays the generic system-wide ICMP counters. icmpMsgStatsTable Displays the system-wide per-version, per-message

type ICMP counters.ipAddrTable Provides addressing information pertinent to IPv4

addresses for an entity. Deprecated, use ipAddressTable instead.

ipNetToMediaTable Provides mapping between IPv4 addresses and physical addresses. Deprecated, use ipNetToPhysicalTable instead.

MIB Constraints

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

Note: Tables which are specific to IPv4 are not implemented.


237

Table 3-167 IP-MIB Constraints MIB Object Notes ipv6InterfaceTable ipv6InterfaceIdentifier Lower n bits of link local address, where n=128 - prefix-

len ipv6InterfaceEnableStatus up (1) if link local address is configured else down (2) ipv6InterfaceForwarding ipv6InterfaceForwarding(1) if IPv6 is configured on LC or

notForwarding(2) if IPv6 is configured on RP ipSystemStatsTable ipSystemStatsinOctets Not supported ipSystemStatsinNoRoutes Not supported ipSystemStatsInAddrErrors Not supported ipSystemStatsInDiscards Not supported ipSystemStatsOutNoRoutes Not supported ipSystemStatsOutForwDatagrams Not supported ipSystemStatsOutDiscards Not supported ipSystemStatsOutTransmits Not supported ipSystemStatsOutOctets Not supported ipSystemStatsInMcastPkts Not supported ipSystemStatsInMcastOctets Not supported ipSystemStatsOutMcastPkts Not supported ipSystemStatsOutMcastOctets Not supported ipSystemStatsInBcastPkts Not supported ipSystemStatsOutBcastPkts Not supported ipSystemStatsDiscontinuityTime Not supported ipIfStatsTable Table only applicable to IPv6 ipIfStatsRefreshRate Not supported Protocol related counters on per-

interface basis (22 objects in this table)Not supported

ipAddressPrefixTable ipAddressPrefixPrefix First n bits of ipv6_addr () where n=prefix_len ipAddressPrefixLength prefix_len field ipAddressPrefixOrigin manual(2) if prefix is taken from global address or well-

known(3) if prefix is taken from link local address ipAddressPrefixAutonomousFlag False(2) for link local and True(1) for others ipAddressPrefixAdvPreferredLife-time Not supported ipAddressPrefixAdvValidLife-time Not supported


238

Table 3-167 IP-MIB Constraints (continued)

MIB Object Notes

ipAddressTable

ipAddressPrefix First n bits of ipv6_addr () where n=prefix_len

ipAddressOrigin ‘manual’ is address if global or ‘linklayer’ if it is link

local

ipAddressCreated Not supported

ipAddressLastChanged Not supported

ipv6ScopeZoneIndexTable Not supported ipDefaultRouterTable Not supported ipRouterAdvertTable Not supported icmpStatsTable icmpStatsOutErrors Not supported

Scalar Objects

ipv6InterfaceTableLastChange Not supported

ipv6IpDefaultHopLimit Not supported

IPV6-MIB

The MIB module for entities implementing the IPv6 protocol.

MIB Tables Table 3-168 lists the Tables in IPV6-MIB

Table 3-168 IPV6-MIB Tables

MIB Tables Description

ipv6IfTable Provides information on the entity internetwork-layer interfaces. An IPv6 interface constitutes a logical network layer attachedt to the layer immediately below IPv6 layer including internet layer tunnels.

ipv6IfStatsTable Provides IPv6 interface traffic statistics.

ipv6AddrPrefixTable Displays IPv6 address prefixes for IPv6 interfaces.

ipv6AddrTable Provides information related to interface addresses for a node.


239


240


ipv6RouteTable Not supported

ipv6NetToMediaTable Provides mapping information from IPv6 addresses to physical addresses. The IPv6 address translation table contain the Ipv6Address to the corresponding physical address.

MIB Constraints Table 3-169 lists the constraints that the router places on objects in the IPV6-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-169 IPV6-MIB Constraints MIB Object Notes ipDefaultRouterTable Not supported ipv6ScopeZoneIndexTable Not supported ipv4InterfaceTable Not supported ipIfStatsTableLastChange Not supported ipAddressSpinLock Not supported ipAddressIfIndex Not supported ipAddressType Not supported ipAddressStatus Not supported ipAddressRowStatus Not supported ipAddressStorageType Not supported ipv6IpForwarding Not supported ipv6IpDefaultHopLimit Not supported

ipv4InterfaceEnableStatus Not supported

ipNetToPhysicalPhysAddress Not supported ipNetToPhysicalType Not supported ipNetToPhysicalRowStatus Not supported ipv6InterfaceEnableStatus Not supported ipv6InterfaceForwarding Not supported ipv6RouterAdvertSpinLock Not supported ipv6RouterAdvertSendAdverts Not supported ipv6RouterAdvertMaxInterval Not supported ipv6RouterAdvertMinInterval Not supported ipv6RouterAdvertManagedFlag Not supported


241

ipv6RouterAdvertOtherConfigFlag Not supported ipv6RouterAdvertLinkMTU Not supported


242

Table 3-169 IPV6-MIB Constraints (continued)

MIB Object Notes

ipDefaultRouterTable Not supported ipv6RouterAdvertReachableTime Not supported ipv6RouterAdvertRetransmitTime Not supported ipv6RouterAdvertCurHopLimit Not supported ipv6RouterAdvertDefaultLifetime Not supported ipv6RouterAdvertRowStatus Not supported

IPV6-FORWARD-MIB The MIB module describes the management of CIDR multipath IP Routes. Table 3-170 lists the tables associated with this MIB.

MIB Objects Table 3-170 IPV6-MLD-MIB Tables and Descriptions Name Description

inetCidrRouteTable This entity's IP Routing table.

inetCidrRouteEntry A particular route to a particular destination, under a particular policy (as reflected in the inetCidrRoutePolicy object).

MIB Constraints Table 3-171 lists the constraints that the router places on objects in the IPV6-FORWARD-MIB. For detailed definitions of MIB objects, see the MIB. Table 3-171 IPV6-FORWARD-MIB Constraints

MIB Object Notes

ipv6Forwarding Not supported

ipv6DefaultHopLimit Not supported

ipv6IfDescr Not supported

ipv6IfIdentifier Not supported

ipv6IfIdentifierLength Not supported

ipv6IfAdminStatus Not supported


243

ipv6RouteValid Not supported

ipv6NetToMediaValid Not supported


244

IPV6-MLD-MIB The IPV6-MLD-MIB is the MIB module for MLD management. Table 3-172 lists the tables associated with this MIB.

MIB Objects Table 3-172 IPV6-MLD-MIB Tables and Descriptions Name Description

mldInterfaceTable (conceptual) Table listing the interfaces on which MLD is enabled

mldCacheTable (conceptual) Table listing the IPv6 multicast groups for which there are members on a particular interface

MIB Constraints Table 3-173 lists the constraints that the router places on objects in the IPV6-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-173 IPV6-MIB Constraints

MIB Object Notes

mldInterfaceProxyIfIndex Not supported

mldInterfaceQueryInterval Not supported

mldInterfaceVersion Not supported

mldInterfaceQueryMaxRespDelay Not supported

mldInterfaceRobustness Not supported

mldInterfaceLastListenQueryIntvl Not supported

mldCacheSelf Not supported

mldCacheStatus Not supported

mldInterfaceStatus Not supported

IPV6-TC The IPV6-TC contains TCs for IPV6. There are no tables associated with this MIB.

ISIS-MIB

The IS-IS MIB describes a management information base for the IS-IS Routing protocol, as described in ISO 10589,


245

when it is used to construct routing tables for IP networks, as described in RFC 1195.


246

Table 3-174 lists the tables associated with this MIB. Table 3-174 ISIS-MIB Tables and Descriptions Name Description

isisManAreaAddrTable

Set of manual area addresses configured on this Intermediate System. At least one row in which the value of isisManAreaAddrExistState is active must be present. The maximum number of rows in this table for which the object isisManAreaAddrExistState has the value active is three. An attempt to create more than three rows of isisManAreaAddrEntry with state 'active' in one instance of the IS-IS protocol should return inconsistentValue

isisAreaAddrTable

Union of the sets of area addresses reported in all Level 1 LSPs with fragment number zero generated by this Intermediate System, or received from other Intermediate Systems that are reachable via Level 1 routing

isisSummAddrTable

Set of IP summary addresses to use in forming summary TLVs originated by this Intermediate System. An administrator may use a summary address to combine and modify IP Reachability announcements. If the Intermediate system can reach any subset of the summary address, the summary address must be announced instead, at the configured metric

isisRedistributeAddrTable

This table provides criteria to decide if a route should be leaked from Layer 2 to Layer 1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table MUST be announced at Layer 1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are announced as is, without being summarized. Routes that do not match a summary mask are not announced

isisRouterTable Set of hostnames and router ID

isisSysLevelTable Level specific information about the System

isisCircTable The table of circuits used by this Intermediate System

isisCircLevelTable Level specific information about circuits used by IS-IS

isisSystemCounterTable System-wide counters for this Intermediate System

isisCircuitCounterTable Circuit specific counters for this Intermediate System

isisPacketCounterTable Information about IS-IS protocol traffic at one level, on one circuit, in one direction

isisISAdjTable Table of adjacencies to Intermediate Systems

isisISAdjAreaAddrTable This table contains the set of Area Addresses of neighboring Intermediate Systems as reported in received IIH PDUs

isisISAdjIPAddrTable This table contains the set of IP Addresses of neighboring


247

Intermediate Systems as reported in received IIH PDUs


248

Table 3-174 ISIS-MIB Tables and Descriptions (continued)

Name Description

isisISAdjProtSuppTable This table contains the set of protocols supported by neighboring Intermediate Systems as reported in received IIH PDUs

isisRATable Table of Reachable Addresses to NSAPs or Address Prefixes

isisIPRATable Table of IP Reachable Addresses to networks, subnetworks, or hosts either manually configured or learned from another protocol

isisLSPSummaryTable Table of LSP Headers

isisLSPTLVTable Table of LSPs in the database

MIB Constraints Table 3-175 lists the constraints that the router places on objects in the ISIS-MIB. For detailed definitions of MIB objects, see the MIB. SNMP sets are not supported.

Table 3-175 ISIS-MIB Constraints

MIB Object Notes

isisAreaAddrTable isisAreaAddr not supported

isisCircuitGroup Not supported

isisISAdjGroup Not supported

isisISIPRADestGroup Not supported

isisLSPGroup Not supported

isisManAreaAddrTable isisManAreaAddrExistState not supported

isisNotificationTable Not supported

isisRATable Group Not supported

isisRedistributeAddrEntry isisRedistributeAddrExistState

isisRouterTable isisRouterID is not supported

isisSummAddrTable

isisSummAddrExistState Not supported

isisSummAddrMetric Not supported


249

isisSummAddrFullMetric Not supported

isisSysLevelType Not supported

isisSysID Not supported

isisSysMaxPathSplits Not supported

isisSysMaxLSPGenInt Not supported


250

Table 3-175 ISIS-MIB Constraints

MIB Object Notes

isisSysPollESHelloRate Not supported

isisSysWaitTime Not supported

isisSysAdminState Not supported

isisSysL2toL1Leaking Not supported

isisSysMaxAge Not supported

isisSysNotificationEnable Not supported

isisManAreaAddrExistState Not supported

isisSysLevelOrigLSPBuffSize Not supported

isisSysLevelMinLSPGenInt Not supported

isisSysLevelSetOverload Not supported

isisSysLevelSetOverloadUntil Not supported

isisSysLevelMetricStyle Not supported

isisSysLevelSPFConsiders Not supported

isisSysLevelTEEnabled Not supported

isisSysReceiveLSPBufferSize Not supported

isisSummAddrExistState Not supported

isisSummAddrMetric Not supported

isisSummAddrFullMetric Not supported

isisRedistributeAddrExistState Not supported

isisRAExistState Not supported

isisRAAdminState Not supported

isisRAAddrPrefix Not supported

isisRAMapType Not supported

isisRAMetric Not supported

isisRAMetricType Not supported

isisRASNPAAddress Not supported

isisRASNPAMask Not supported

isisRASNPAPrefix Not supported

isisRAType Not supported

isisIPRANextHopType Not supported

isisIPRANextHop Not supported


251

isisIPRAType Not supported

isisIPRAExistState Not supported

isisIPRAAdminState Not supported

isisIPRAMetric Not supported

isisIPRAFullMetric Not supported


252

Table 3-175 ISIS-MIB Constraints MIB Object Notes

isisIPRAMetricType Not supported

isisIPRASNPAAddress Not supported

isisCircAdminState Not supported

isisCircExistState Not supported

isisCircType Not supported

isisCircExtDomain Not supported

isisCircLevelType Not supported

isisCircPassiveCircuit Not supported

isisCircMeshGroupEnabled Not supported

isisCircMeshGroup Not supported

isisCircSmallHellos Not supported

isisCirc3WayEnabled Not supported

isisCircExtendedCircID Not supported

isisCircIfIndex Not supported

isisCircLevelMetric Not supported

isisCircLevelWideMetric Not supported

isisCircLevelISPriority Not supported

isisCircLevelHelloMultiplier Not supported

isisCircLevelHelloTimer Not supported

isisCircLevelDRHelloTimer Not supported

isisCircLevelLSPThrottle Not supported

isisCircLevelMinLSPRetransInt Not supported

isisCircLevelCSNPInterval Not supported

isisCircLevelPartSNPInterval Not supported


253

MAU-MIB This section describes the management information for 802.3 MAUs. This MIB has no tables.

MIB Constraints Table 3-176 lists the constraints that the router places on objects in the MAU-MIB. For detailed definitions of MIB objects, see the MIB.


254

Table 3-176 MAU-MIB Constraints MIB Object Notes

ifMauStatus Not supported

ifMauAutoNegRemoteFaultAdvertised Not supported

ifMauAutoNegAdminStatus Not supported

ifMauAutoNegCapAdvertisedBits Not supported

ifMauAutoNegRestart Not supported

ifMauDefaultType Not supported

MEF-SOAM-PM-MIB This MIB module contains the management objects for the management of Ethernet Services Operations, Administration and Maintenance for Performance Monitoring. Table 3-219 lists the tables associated with this MIB.

MIB Objects Table 3-219 MEF-SOAM-PM-MIB Tables and Descriptions Name Description

mefSoamPmMepTable This MIB table extends the dot1agCfmMepTable, listing Performance Monitoring configuration for all Maintenance End Points (MEPs) that are configured.

mefSoamLmCfgTable This MIB table lists configuration for Frame Loss Measurement operations configured on local MEPs.

mefSoamLmMeasuredStatsTable

This MIB table lists the last measured statistics for Frame Loss Measurement operations configured on local MEPs. In IOS-XR, these statistics are not calculated, hence this table is unsupported.

mefSoamLmCurrentAvailStatsTable

This MIB table lists the current availability statistics for Frame Loss Measurement operations configured on local MEPs. In IOS-XR, these statistics are not calculated, hence this table is unsupported.

mefSoamLmCurrentStatsTable

This MIB table lists current statistics for Frame Loss Measurement operations configured on local MEPs.

mefSoamLmHistoryAvailStatsTable

This MIB table lists historical availability statistics for Frame Loss Measurement operations configured on local MEPs. In IOS-XR, these statistics are not calculated, hence this table is unsupported.

mefSoamLmHistoryStatsTable

This MIB table lists historical statistics for Frame Loss Measurement operations configured on local MEPs.

mefSoamDmCfgTable This MIB table lists configuration for Delay Measurement


255

operations configured on local MEPs.

mefSoamDmCfgMeasBinTable

This MIB table lists bin configuration for buckets in Delay Measurement operations configured on local MEPs.

mefSoamDmMeasuredStatsTable

This MIB table lists the last measured statistics for Delay Measurement operations configured on local MEPs.

mefSoamDmCurrentStatsTable

This MIB table lists current statistics for Delay Measurement operations configured on local MEPs.

mefSoamDmCurrentStatsBinsTable

This MIB table lists the result bins for the current bucket in Delay Measurement operations configured on local MEPs.

mefSoamDmHistoryStatsTable

This MIB table lists historical statistics for Delay Measurement operations configured on local MEPs.

mefSoamDmHistoryStatsBinsTable

This MIB table lists the results bins for historical statistics for Delay Measurement operations configured on local MEPs.

mefSoamLmThresholdCfgTable

This MIB table lists threshold configuration for Frame Loss Measurement operations configured on local MEPs. In IOS-XR, this configuration is not available, hence this table is unsupported.

mefSoamDmThresholdCfgTable

This MIB table lists threshold configuration for Delay Measurement operations configured on local MEPs. In IOS-XR, this configuration is not available, hence this table is unsupported.

MIB Constraints Table 3-220 lists the constraints that the router places on objects in the MEF-SOAM-PM-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-2220 MEF-SOAM-PM-MIB Constraints

MIB Object Notes

mefSoamPmMepLmSingleEndedResponder Always TRUE

mefSoamPmMepSlmSingleEndedResponder Always TRUE

mefSoamPmMepDmSingleEndedResponder Always TRUE

mefSoamLmCfgMeasurementEnable Supported (never bAvail* or bMeasuredStats*)

mefSoamLmCfgStartTimeType Always ‘absolute’

mefSoamLmCfgFixedStartDateAndTime Supported (for OD operations)

mefSoamLmCfgRelativeStartTime N/A

mefSoamLmCfgStopTimeType‘none’ for configured operations, ‘relative’ for OD operations

mefSoamLmCfgFixedStopDateAndTime N/A


256

mefSoamLmCfgHistoryClear Always FALSE

mefSoamLmCfgRowStatus Always ‘active’

mefSoamDmCfgMeasurementEnableSupported (never bFrameDelayRange* or bMeasuredStats*)

mefSoamDmCfgSourceMacAddress Not supported

All other mefSoamDmCfg* field constraints are as per mefSoamLmCfg* above

mefSoamDmCurrentStatsFrameDelayRange* Not supported

All mefSoamDmHistoryStats* field constraints are as per mefSoamDmCurrentStats* above

MFR-MIB The MFR-MIB is used to control and monitor the multilink frame relay (MFR) function described in FRF.16. Table 3-177 lists the tables associated with this MIB.

MIB Objects Table 3-177 MFR-MIB Tables and

Descriptions Name Descriptions

mfrBundleTable The bundle configuration and status table. There is a one-to-one correspondence between a bundle and an interface represented in the ifTable. The following objects of the ifTable have specific meaning for an MFR bundle: ifAdminStatus - the bundle admin status ifOperStatus - the bundle operational status ifSpeed - the current bandwidth of the bundle ifInUcastPkts - the number of frames received on the bundle ifOutUcastPkts - the number of frames transmitted on the bundle ifIn-Errors - frame (not fragment) errors ifOutErrors -frame (not fragment) errors

mfrBundleIfIndexMappingTable A table mapping the values of ifIndex to the- mfrBundleIndex. This is required in order to find the mfrBundleIndex given an ifIndex. The mapping of mfrBundleIndex to ifIndex is provided by the mfrBundleIfIndex entry in the mfrBundleTable.

mfrBundleLinkTable The bundle link configuration and status table. There is a one-to-one correspondence between a bundle link and a physical interface represented in the ifTable. The ifIndex of the physical interface is used to index the bundle link table, and to create rows. The following objects of the ifTable have specific meaning for an MFR bundle link: ifAdminStatus - the bundle link admin status ifOper-Status - the bundle link operational status ifSpeed- the


257

bandwidth of the bundle link interface ifInU-castPkts - the number of frames received on the bundle link ifOutUcastPkts - the number of frames transmitted on the bundle link ifInErrors - frame and fragment errors ifOutErrors - frame and fragment errors

MIB Constraints Table 3-178 lists the constraints that the router places on objects in the MFR-MIB.


258

Table 3-178 MFR-MIB Constraints MIB Object Notes

mfrBundleLinkRowStatus Not supported

mfrBundleLinkConfigBundleIndex Not supported

mfrBundleLinkNearEndName Not supported

mfrBundleNextIndex Not supported

mfrBundleRowStatus Not supported

mfrBundleNearEndName Not supported

mfrBundleFragmentation Not supported

mfrBundleMaxFragSize Not supported

mfrBundleTimerHello Not supported

mfrBundleTimerAck Not supported

mfrBundleCountMaxRetry Not supported

mfrBundleActivationClass Not supported

mfrBundleThreshold Not supported

mfrBundleMaxDiffDelay Not supported

mfrBundleSeqNumSize Not supported

MGMD-STD-MIB

This MIB describes the MIB module for MGMD Management.


259

MIB Objects

Table 3-179 MGMD-STD-MIB Tables and Descriptions Name Description

mgmdHostInterfaceTable The (conceptual) table listing the interfaces on which IGMP or MLD is enabled.

mgmdRouterInterfaceTable The (conceptual) table listing the interfaces on which IGMP or MLD is enabled.

mgmdHostCacheTable The (conceptual) table listing the IP multicast groups for which the host is a member on a particular interface.

mgmdRouterCacheTable The (conceptual) table listing the IP multicast groups for which there are members on a particular router interface.

mgmdInverseHostCacheTable The (conceptual) table listing the interfaces which are members of a particular group. This is a reverse lookup table for entries in the mgmdHost-CacheTable.

mgmdInverseRouterCacheTable The (conceptual) table listing the interfaces which are members of a particular group. This is a reverse lookup table for entries in the mgmdRouterCacheTable.

mgmdHostSrcListTable The (conceptual) table listing the Source List entries corresponding to each interface and multicast group pair on a host.

mgmdRouterSrcListTable The (conceptual) table listing the Source List entries corresponding to each interface and multicast group pair on a Router.

MIB Constraints Table 3-180 lists the constraints that the router places on objects in the MGMD-STD-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-180 MGMD-STD-MIB Constraints

MIB Object Notes

mgmdHostInterfaceStatus Not supported

mgmdRouterInterfaceVersion Not supported

mgmdRouterInterfaceQueryMaxResponseTime Not supported

mgmdRouterInterfaceRobustness Not supported


260

mgmdRouterInterfaceLastMembQuery- Intvl Not supported

mgmdRouterInterfaceStatus Not supported


261

Table 3-180 MGMD-STD-MIB Constraints (continued)

MIB Object Notes

mgmdRouterInterfaceQueryInterval Not supported

mgmdRouterInterfaceProxyIfIndex Not supported

MPLS-L3VPN-STD-MIB The MPLS-L3VPN-STD-MIB contains managed object definitions for the Layer-3 Multiprotocol Label Switching Virtual Private Networks. Table 3-181 lists the tables associated with this MIB.

Table 3-181 MPLS-L3VPN-STD-MIB Tables and Descriptions

Name Description

mplsL3VpnIfConfTable This table specifies per-interface MPLS capability and associated information

mplsL3VpnVrfTable

This table specifies per-interface MPLS L3VPN VRF Table capability and associated information. Entries in this table define VRF routing instances associated with MPLS/VPN interfaces. Note that multiple interfaces can belong to the same VRF instance. The collection of all VRF instances comprises an actual VPN

mplsL3VpnVrfRTTable

This table specifies per-VRF route target association. Each entry identifies a connectivity policy supported as part of a VPN

mplsL3VpnVrfSecTable This table specifies per MPLS L3VPN VRF Table security-related counters

mplsL3VpnVrfPerfTable This table specifies per MPLS L3VPN VRF Table performance information

mplsL3VpnVrfRteTable

This table specifies per-interface MPLS L3VPN VRF Table routing information. Entries in this table define VRF routing entries associated with the specified MPLS/VPN interfaces. Note that this table contains both BGP and Interior Gateway Protocol IGP routes, as both may appear in the same VRF

MIB Constraints

Table 3-182 lists the constraints that the router places on objects in the MPLS-L3VPN-STD-MIB. For detailed definitions of MIB objects, see the MIB.


262

Table 3-182 MPLS-L3VPN-STD-MIB Constraints

MIB Object Notes

mplsL3VpnVrfRteInetCidrIfIndex Not supported

mplsL3VpnVrfRteInetCidrType Not supported

mplsL3VpnVrfRteInetCidrNextHopAS Not supported

mplsL3VpnVrfRteInetCidrMetric1 Not supported





mplsL3VpnVrfRteXCPointer Not supported

mplsL3VpnVrfRteInetCidrStatus Not supported

mplsL3VpnIfVpnClassification Not supported

mplsL3VpnIfVpnRouteDistProtocol Not supported

mplsL3VpnIfConfStorageType Not supported

mplsL3VpnIfConfRowStatus Not supported

mplsL3VpnNotificationEnable Not supported

mplsL3VpnIllLblRcvThrsh Not supported

mplsL3VpnVrfVpnId Not supported

mplsL3VpnVrfDescription Not supported

mplsL3VpnVrfRD Not supported

mplsL3VpnVrfConfMidRteThresh Not supported

mplsL3VpnVrfConfHighRteThresh Not supported

mplsL3VpnVrfConfMaxRoutes Not supported

mplsL3VpnVrfConfRowStatus Not supported

mplsL3VpnVrfConfAdminStatus Not supported

mplsL3VpnVrfConfStorageType Not supported


263

mplsL3VpnVrfRTDescr Not supported

mplsL3VpnVrfRT Not supported

mplsL3VpnVrfRTRowStatus Not supported

mplsL3VpnVrfRTStorageType Not supported

MPLS-LDP-GENERIC-STD-MIB The MPLS-LDP-GENERIC-STD-MIB contains managed object definitions for configuring and monitoring the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP), utilizing ethernet as the Layer 2 media. Table 3-183 lists the tables associated with this MIB.


264

Table 3-183 MPLS-LDP-GENERIC-STD-MIB Tables and Descriptions Name Description

mplsLdpEntityGenericLRTable MPLS LDP Entity Generic LR Table. The purpose of this table is to provide a mechanism for configurating a contiguous range of generic labels, or a 'label range' for LDP Entities. LDP Entities, which use Generic Labels, must have at least one entry in this table. In other words, this table 'extends' the mpldLdpEntityTable for Generic Labels. There is read-only support for all objects in this table.

MIB Constraints Table 3-184 lists the constraints that the router places on objects in the MPLS-LDP-GENERIC-STD-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-184 MPLS-LDP-GENERIC-STD-MIB Constraints MIB Object Notes

mplsLdpEntityGenericLabelSpace Not supported

mplsLdpEntityGenericIfIndexOrZero Not supported

mplsLdpEntityGenericLRStorageType Not supported

mplsLdpEntityGenericLRRowStatus Not supported

MPLS-LDP-STD-MIB

The MPLS-LDP-STD-MIB contains managed object definitions for the ‘Multiprotocol Label Switching, Label Distribution Protocol, LDP document’. Note: Only MANDATORY-GROUPS, which include mplsLdpGeneralGroup and mplsLdpNotificationGroup, are supported.

Table 3-185 lists the tables associated with this MIB. Table 3-185 MPLS-LDP-STD-MIB Tables and Descriptions

Name Description

mplsLdpEntityTable This table contains information about the MPLS Label Distribution Protocol Entities which exist on this LSR or LER

mplsLdpEntityStatsTable This table is a read-only table which augments the mplsLdpEntityTable. The purpose of this table is to keep statistical information about the LDP Entities on the LSR


265

Table 3-185 MPLS-LDP-STD-MIB Tables and Descriptions (continued) Name Description

mplsLdpPeerTable Information about LDP peers known by Entities in the mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer interaction during session initialization but is not appropriate for the mplsLdpSessionTable, because objects in this table may or may not be used in session establishment

mplsLdpSessionTable Table of Sessions between the LDP Entities and LDP Peers. This table AUGMENTS the mplsLdpPeerTable. Each row in this table represents a single session

mplsLdpSessionStatsTable Table of statistics for Sessions between LDP Entities and LDP Peers. This table AUGMENTS the mplsLdpPeerTable

mplsLdpHelloAdjacencyTable Table of Hello Adjacencies for Sessions

mplsFecTable This table represents the FEC Information associated with an LSP

mplsLdpSessionPeerAddrTable This table 'extends' the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated when Label Withdraw Address Messages are received, that is, Rows should be deleted as appropriate. NOTE: since more than one address may be contained in a Label Address Message, this table 'sparse augments', the mplsLdpSessionTable's information

MIB Constraints Table 3-186 lists the constraints that the router places on objects in the MPLS-LDP-STD-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-186 MPLS-LDP-STD-MIB Constraints

MIB Object Notes mplsLdpLspFecStorageType Not supported mplsLdpLspFecRowStatus Not supported mplsLdpEntityProtocolVersion Not supported mplsLdpEntityAdminStatus Not supported mplsLdpEntityTcpPort Not supported mplsLdpEntityUdpDscPort Not supported mplsLdpEntityMaxPduLength Not supported mplsLdpEntityKeepAliveHoldTimer Not supported mplsLdpEntityHelloHoldTimer Not supported


266

Table 3-186 MPLS-LDP-STD-MIB Constraints (continued) MIB Object Notes

mplsLdpEntityInitSessionThreshold Not supported

mplsLdpEntityLabelDistMethod Not supported

mplsLdpEntityLabelRetentionMode Not supported

mplsLdpEntityPathVectorLimit Not supported

mplsLdpEntityHopCountLimit Not supported

mplsLdpEntityTransportAddrKind Not supported

mplsLdpEntityTargetPeer Not supported

mplsLdpEntityTargetPeerAddrType Not supported

mplsLdpEntityTargetPeerAddr Not supported

mplsLdpEntityLabelType Not supported

mplsLdpEntityStorageType Not supported

mplsLdpEntityRowStatus Not supported

mplsFecType Not supported

mplsFecAddrType Not supported

mplsFecAddr Not supported

mplsFecAddrPrefixLength Not supported

mplsFecStorageType Not supported

mplsFecRowStatus Not supported

MPLS-LSR-STD-MIB

The MPLS-LSR-STD-MIB contains managed object definitions for the Multiprotocol Label Switching (MPLS) Router as defined in: Rosen, E., Viswanathan, A., and R. Callon, Multiprotocol Label Switching Architecture, RFC 3031, January 2001. Note: Only MANDATORY-GROUPS which include mplsInterfaceTable, mplsInSegmentTable, mplsOutSegmentTable, mplsXCTable and mplsInterfacePerfTable are supported. Table 3-187 lists the tables associated with this MIB.


267

Table 3-187 MPLS-LSR-STD-MIB Tables and Descriptions

Name Description

mplsInterfaceTable This table specifies per-interface MPLS capability and associated information

mplsInterfacePerfTable This table provides MPLS performance information on a per-interface basis


268

Table 3-187 MPLS-LSR-STD-MIB Tables and Descriptions (continued) Name Description

mplsInSegmentTable This table contains a description of the incoming MPLS segments (labels) to an LSR and their associated parameters. The index for this table is mplsInSegmentIndex. The index structure of this table is specifically designed to handle many different MPLS implementations that manage their labels both in a distributed and centralized manner. The table is also designed to handle existing MPLS labels as defined in RFC 3031 as well as longer ones that may be necessary in the future. In cases where the label cannot fit into the mplsInSegmentLabel object, the mplsInSegmentLabelPtr indicates this by being set to the first accessible column in the appropriate extension table's row. In this case an additional table MUST be provided and MUST be indexed by at least the indexes used by this table. In all other cases when the label is represented within the mplsInSegmentLabel object, the mplsInSegmentLabelPtr MUST be set to 0.0. Due to the fact that MPLS labels may not exceed 24 bits, the mplsInSegmentLabelPtr object is only a provision for future-proofing the MIB module. Thus, the definition of any extension tables is beyond the scope of this MIB module

mplsInSegmentPerfTable This table contains statistical information for incoming MPLS segments to an LSR

mplsOutSegmentTable This table contains a representation of the outgoing segments from an LSR

mplsOutSegmentPerfTable This table contains statistical information about outgoing segments from an LSR. The counters in this entry should behave in a manner similar to that of the interface

mplsXCTable This table specifies information for switching between LSP segments. It supports point-to-point, point-to-multipoint and multipoint-to-point connections. mplsLabelStackTable specifies the label stack information for a cross-connect LSR and is referred to from mplsXCTable

mplsLabelStackTable This table specifies the label stack to be pushed onto a packet, beneath the top label. Entries into this table are referred to from mplsXCTable

mplsInSegmentMapTable This table specifies the mapping from the mplsInSegmentIndex to the corresponding mplsInSegmentInterface and mplsInSegmentLabel objects. The purpose of this table is to provide the manager with an alternative means by which to locate in-segments


269

MIB Constraints Table 3-188 lists the constraints that the router places on objects in the MPLS-LSR-STD-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-188 MPLS-LSR-STD-MIB Constraints

MIB Object Notes

mplsInSegmentInterface Not supported

mplsInSegmentLabel Not supported

mplsInSegmentLabelPtr Not supported

mplsInSegmentNPop Not supported

mplsInSegmentAddrFamily Not supported

mplsInSegmentRowStatus Not supported

mplsInSegmentStorageType Not supported

mplsInSegmentTrafficParamPtr Not supported

mplsLabelStackLabel Not supported

mplsLabelStackLabelPtr Not supported

mplsLabelStackRowStatus Not supported

mplsLabelStackStorageType Not supported

mplsXCLspId Not supported

mplsXCLabelStackIndex Not supported

mplsXCStorageType Not supported

mplsXCAdminStatus Not supported

mplsXCRowStatus Not supported

mplsXCNotificationsEnable Not supported

mplsOutSegmentInterface Not supported

mplsOutSegmentPushTopLabel Not supported

mplsOutSegmentTopLabel Not supported

mplsOutSegmentTopLabelPtr Not supported

mplsOutSegmentNextHopAddrType Not supported


270

mplsOutSegmentNextHopAddr Not supported

mplsOutSegmentRowStatus Not supported

mplsOutSegmentStorageType Not supported

mplsOutSegmentTrafficParamPtr Not supported

MPLS-TC-STD-MIB The MPLS-TC-STD-MIB defines TEXTUAL-CONVENTIONs for concepts used in Multiprotocol Label Switching (MPLS) networks. This MIB has no tables.

MPLS-TE-STD-MIB The MPLS-TE-STD-MIB contains managed object definitions for the MPLS Traffic Engineering (TE). Table 3-189 lists the tables associated with this MIB.

Table 3-189 MPLS-TE-STD-MIB Tables and Descriptions Name Description

mplsTunnelTable mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multipoint-to-point and point- to-multipoint connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can have one out-segment originating at this LSR or one in-segment terminating at this LSR

mplsTunnelHopTable mplsTunnelHopTable is used to indicate the hops, strict orloose, for an instance of an MPLS tunnel defined in mplsTunnelTable, when it is established via signaling, for the outgoing direction of the tunnel. Thus at a transit LSR, this table contains the desired path of the tunnel from this LSR onwards. Each row in this table is indexed by mplsTunnelHopListIndex which corresponds to a group of hop lists or path options. Each row also has a secondary index mplsTunnelHopIndex, which indicates a group of hops (also known as a path option). Finally, the third index, mplsTunnelHopIndex indicates the specific hop information for a path option. To specify a particular interface on the originating LSR of an outgoing tunnel for packets to exit the LSR, specify this as the first hop for this tunnel in mplsTunnelHopTable

mplsTunnelResourceTable mplsTunnelResourceTable allows a manager to specify which resources are desired for an MPLS tunnel. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources


271


272

Table 3-189 MPLS-TE-STD-MIB Tables and Descriptions (continued) Name Description mplsTunnelARHopTable mplsTunnelARHopTable is used to indicate the hops for an MPLS

tunnel defined in mplsTunnelTable, as reported by the MPLS signaling protocol. Thus at a transit LSR, this table (if the table is supported and if the signaling protocol is recording actual route information) contains the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the mplsTunnelHopTable or the mplsTunnelCHopTable. Each row in this table is indexed by mplsTunnelARHopListIndex. Each row also has a secondary index mplsTunnelARHopIndex, corresponding to the next hop that this row corresponds to. Note that since the information necessary to build entries within this table is not provided by some MPLS signaling protocols, implementation of this table is optional. Furthermore, because the information in this table is actually provided by the MPLS signaling protocol after the path has been set-up, the entries in this table areprovided only for observation, and hence, all variables in this table are accessible exclusively as read-only. Note also that the contents of this table may change while it is being read because of re-routing activities. A network administrator may verify that the actual route read is consistent by reference to the mplsTunnelLastPathChange object

mplsTunnelCHopTable mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint- based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Thus at a transit LSR, this table (if the table is supported) MAY contain the path computed by the CSPF engine on (or on behalf of) this LSR. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, corresponding to the next hop that this row corresponds to. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelCHopTable

mplsTunnelPerfTable This table provides per-tunnel instance MPLS performance information

mplsTunnelCRLDPResTable mplsTunnelCRLDPResTable allows a manager to specify which CR-LDP-specific resources are desired for an MPLS tunnel if that tunnel is signaled using CR-LDP. Note that these attributes are in addition to those specified in mplsTunnelResourceTable. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources


273

MIB Constraints Table 3-190 lists the constraints on objects in the MPLS-TE-STD-MIB. Table 3-190 MPLS-TE-STD-MIB Constraints

MIB Object Notes

mplsTunnelCRLDPResTable CRLDP signaling not supported for Traffic Engineering. mplsTunnelNotificationMaxRate Not supported mplsTunnelSetupPrio Not supported mplsTunnelHoldingPrio Not supported mplsTunnelSignallingProto Not supported mplsTunnelLocalProtectInUse Not supported

mplsTunnelSessionAttributes Not supported

mplsTunnelHopAddrType Not supported

mplsTunnelHopIpAddr Not supported

mplsTunnelHopIpPrefixLen Not supported

mplsTunnelHopAddrUnnum Not supported

mplsTunnelHopAsNumber Not supported

mplsTunnelHopLspId Not supported

mplsTunnelHopType Not supported

mplsTunnelHopInclude Not supported

mplsTunnelHopPathOptionName Not supported

mplsTunnelHopEntryPathComp Not supported

mplsTunnelHopRowStatus Not supported

mplsTunnelHopStorageType Not supported

mplsTunnelIsIf Not supported

mplsTunnelCRLDPResMeanBurstSize Not supported mplsTunnelCRLDPResExBurstSize Not supported mplsTunnelCRLDPResFrequency Not supported mplsTunnelCRLDPResWeight Not supported mplsTunnelCRLDPResFlags Not supported mplsTunnelCRLDPResRowStatus Not supported mplsTunnelCRLDPResStorageType Not supported mplsTunnelSignallingProto Not supported


274

mplsTunnelIsIf Not supported

mplsTunnelName Not supported

mplsTunnelDescr Not supported

mplsTunnelXCPointer Not supported


275

Table 3-190 MPLS-TE-STD-MIB Constraints (continued)

MIB Object Notes

mplsTunnelHopTableIndex Not supported

mplsTunnelAdminStatus Not supported

mplsTunnelRowStatus Not supported

mplsTunnelNotificationEnable Not supported

mplsTunnelStorageType Not supported

mplsTunnelIncludeAnyAffinity Not supported

mplsTunnelIncludeAllAffinity Not supported

mplsTunnelExcludeAnyAffinity Not supported

mplsTunnelResourcePointer Not supported

mplsTunnelInstancePriority Not supported

mplsTunnelPathInUse Not supported

mplsTunnelRole Not supported

mplsTunnelResourceMaxRate Not supported

mplsTunnelResourceMeanRate Not supported

mplsTunnelResourceMaxBurstSize Not supported

mplsTunnelResourceMeanBurstSize Not supported

mplsTunnelResourceExBurstSize Not supported

mplsTunnelResourceFrequency Not supported

mplsTunnelResourceWeight Not supported

mplsTunnelResourceRowStatus Not supported

mplsTunnelResourceStorageType Not supported

NOTIFICATION-LOG-MIB The NOTIFICATION-LOG-MIB is for logging SNMP Notifications, that is, Traps and Informs. Table 3-191 lists the tables associated with this MIB.

Table 3-191 NOTIFICATION-LOG-MIB Tables and Descriptions


276

Name Description

nlmConfigLogTable Table of logging control entries

nlmStatsLogTable Table of Notification log statistics entries


277

Table 3-191 NOTIFICATION-LOG-MIB Tables and Descriptions Name Description

nlmLogTable Table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general, one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset must be set to 0

nlmLogVariableTable Table of variables to go with Notification log entries

OSPF-MIB The OSPF-MIB contains objects to describe the OSPF Version 2 Protocol.

MIB Tables Table 3-192 lists the tables in OSPF-MIB:

Table 3-192 OSPF-MIB Tables


ospfAreaTable Provides information about the configured parameters and cumulative statistics of the router’s attached areas. The interfaces and virtual links are configured as part of these areas. For example, area 0.0.0.0, is defined as the backbone area.

ospfStubAreaTable Displays the set of metrics that are advertised by a default area border router into a stub area.

ospfLsdbTable Contains the OSPF Process link state database (LSDB) that provides the information about the link state advertisements in the area for the attached devices.

ospfAreaRangeTable Displays the address range summaries and supplements the information available in the ospfAreaTable. It contains a set of IP address ranges specified by an IP address/IP network mask pair. Deprecated, use ospfAreaAggregateTable.


278


ospfHostTable Provides this information about the host: List of the hosts that are directly attached

to the router.

Lists the metrics and types of service that

should be advertised.

Lists the areas where the host is visible.

ospfIfTable Provides information about interfaces and supplements the information contained in ipAddrTable.

ospfIfMetricTable Displays the metrics to be advertised for an interface at the various types of service.

ospfVirtIfTable Provides information about the virtual interfaces for which an OSPF process is configured for a router.

ospfNbrTable Lists all the non-virtual neighbors in the locality of the OSPF router.

ospfVirtNbrTable Lists all virtual neighbors. This table is read-only because the virtual links are configured in the virtual interface table.

ospfExtLsdbTable Provides the external link state advertisement information. This table is basically external LSA link state database for OSPF processes.

ospfAreaAggregateTable Displays the address aggregates that are configured to be propagated from an area. The ospfAreaAggregateTable suplements the information provided in the ospfAreaTable. It contains a set of IP address ranges specified by an IP address/IP network mask pair.

ospfLocalLsdbTable Displays the link-local Link State Advertisements for non-virtual links. This table lists the link-local LSAs for each non-virtual interface.

ospfVirtLocalLsdbTable Displays the link-local Link State Advertisements for virtual links. This table lists the link-local LSAs for each virtual interface.

ospfAsLsdbTable Displays the AS-scope link state advertisements received from the connected areas. This table lists AS-scope LSAs for each router.

ospfAreaLsaCountTable Displays per-area per-LSA-type counters.


279

Note: To access OSPF data, the corresponding SNMP context must be used (i.e. v2 comunity or v3 group mapped to context).

MIB Constraints Table 3-193 lists the constraints on objects in the OSPF-MIB.

Table 3-193 OSPF-MIB Constraints

MIB Object Notes ospfHostMetric Not supported ospfHostStatus Not supported ospfHostCfgAreaID Not supported ospfVirtIfTransitDelay Not supported ospfVirtIfRetransInterval Not supported ospfVirtIfHelloInterval Not supported ospfVirtIfAuthType Not supported ospfVirtIfAuthKey Not supported ospfVirtIfStatus Not supported ospfRouterId Not supported ospfAdminStat Not supported ospfASBdrRtrStatus Not supported ospfTOSSupport Not supported ospfExtLsdbLimit Not supported ospfMulticastExtensions Not supported ospfExitOverflowInterval Not supported ospfDemandExtensions Not supported ospfRFC1583Compatibility Not supported ospfReferenceBandwidth Not supported ospfRestartSupport Not supported ospfRestartInterval Not supported ospfRestartStrictLsaChecking Not supported ospfStubRouterAdvertisement Not supported ospfAreaAggregateStatus Not supported ospfAreaAggregateEffect Not supported ospfAreaAggregateExtRouteTag Not supported ospfStubMetric Not supported ospfStubMetricType Not supported ospfIfMetricValue Not supported ospfIfMetricStatus Not supported ospfIfAreaId Not supported ospfIfType Not supported


280

Table 3-193 OSPF-MIB Constraints (continued)

MIB Object Notes

ospfIfAdminStat Not supported

ospfIfRtrPriority Not supported

ospfIfTransitDelay Not supported

ospfIfRetransInterval Not supported

ospfIfHelloInterval Not supported

ospfIfRtrDeadInterval Not supported

ospfIfPollInterval Not supported

ospfIfAuthType Not supported

ospfIfAuthKey Not supported

ospfIfStatus Not supported

ospfIfMulticastForwarding Not supported

ospfIfDemand Not supported

ospfNbrPriority Not supported

ospfNbmaNbrStatus Not supported

ospfImportAsExtern Not supported

ospfAreaSummary Not supported

ospfAreaStatus Not supported

ospfAreaNssaTranslatorRole Not supported

ospfAreaNssaTranslatorStabilityInterval Not supported

OSPF-TRAP-MIB The OSPF-TRAP-MIB describes the traps for OSPF Version 2 Protocol. This MIB has no tables.

OSPFV3-MIB The OSPFV3-MIB is the MIB module for OSPF version 3. Table 3-194 lists the tables associated with this MIB.

Table 3-194 OSPFV3-MIB Tables and Descriptions Name Description

ospfv3AreaTable OSPFv3 Process's AS-Scope LSDB. The LSDB contains

the AS-Scope Link State Advertisements from throughout the areas that the device is attached to.

ospfv3AsLsdbTable OSPFv3 Process's AS-Scope LSDB. The LSDB contains

the AS-Scope Link State Advertisements from throughout the areas that the device is attached to.


281

Table 3-194 OSPFV3-MIB Tables and Descriptions (continued) Name Description

ospfv3AreaLsdbTable OSPFv3 Process's Area-Scope LSDB. The LSDB contains the Area-Scope Link State Advertisements from throughout the area that the device is attached to.

ospfv3LinkLsdbTable OSPFv3 Process's Link-Scope LSDB for non-virtualinterfaces. The LSDB contains the Link-Scope Link State Advertisements from the interfaces that the device is attached to

ospfv3HostTable Host/Metric Table indicates what hosts are directly attached to the router and their corresponding

metrics

ospfv3IfTable OSPFv3 Interface Table describes the interfaces from the viewpoint of OSPFv3

ospfv3VirtIfTable Information about this router's virtual interfaces that the OSPFv3 Process is configured to carry on

ospfv3NbrTable A table describing all neighbors in the locality of theOSPFv3 router

ospfv3CfgNbrTable Table describing all configured neighbors

ospfv3VirtNbrTable Table describing all virtual neighbors

ospfv3AreaAggregateTable Area Aggregate Table acts as an adjunct to the Area Table. It describes those address aggregates that are configured to be propagated from an area. Its purpose is to reduce the amount of information that is known beyond an Area's borders. A range of IPv6 prefixes specified by a prefix/prefix length pair. Note that if ranges are configured such that one range subsumes another range the most specific match is the preferred one

ospfv3VirtLinkLsdbTable OSPFv3 Process's Link-Scope LSDB for virtual interfaces. The LSDB contains the Link-Scope Link

State Advertisements from virtual interfaces

MIB Constraints Table 3-195 lists the constraints on objects in the OSPFV3-MIB. Table 3-195 OSPFV3-MIB Constraints

MIB Object Notes

ospfv3RouterId Not supported

ospfv3AdminStat Not supported

ospfv3ASBdrRtrStatus Not supported ospfv3ExtAreaLsdbLimit Not supported

ospfv3MulticastExtensions Not supported

ospfv3ExitOverflowInterval Not supported


282

Table 3-195 OSPFV3-MIB Constraints (continued)

MIB Object Notes ospfv3DemandExtensions Not supported

ospfv3TrafficEngineeringSupport Not supported

ospfv3ReferenceBandwidth Not supported

ospfv3RestartSupport Not supported

ospfv3RestartInterval Not supported

ospfv3ImportAsExtern Not supported

ospfv3AreaSummary Not supported

ospfv3AreaStatus Not supported

ospfv3StubMetric Not supported

ospfv3AreaNssaTranslatorRole Not supported ospfv3AreaNssaTranslatorStabilityInterval Not supported ospfv3AreaStubMetricType Not supported ospfv3NbmaNbrPriority Not supported ospfv3NbmaNbrStorageType Not supported ospfv3NbmaNbrStatus Not supported ospfv3VirtIfIndex Not supported ospfv3VirtIfTransitDelay Not supported ospfv3VirtIfRetransInterval Not supported

ospfv3VirtIfHelloInterval Not supported ospfv3VirtIfRtrDeadInterval Not supported

ospfv3VirtIfStatus Not supported ospfv3AreaAggregateStatus Not supported

ospfv3AreaAggregateEffect Not supported

ospfv3AreaAggregateRouteTag Not supported ospfv3IfAreaId Not supported

ospfv3IfType Not supported ospfv3IfAdminStat Not supported

ospfv3IfRtrPriority Not supported

ospfv3IfTransitDelay Not supported ospfv3IfRetransInterval Not supported

ospfv3IfHelloInterval Not supported ospfv3IfRtrDeadInterval Not supported

ospfv3IfPollInterval Not supported ospfv3IfStatus Not supported ospfv3IfMulticastForwarding Not supported


283

Table 3-195 OSPFV3-MIB Constraints (continued)

MIB Object Notes

ospfv3IfDemand Not supported

ospfv3IfMetricValue Not supported

ospfv3IfInstId Not supported

ospfv3IfDemandNbrProbe Not supported

ospfv3IfDemandNbrProbeRetxLimit Not supported

ospfv3IfDemandNbrProbeInterval Not supported

ospfv3HostMetric Not supported

ospfv3HostStatus Not supported

ospfv3HostAreaID Not supported

PIM-MIB

The MIB module for management of PIM routers. Table 3-196 lists the tables associated with this MIB.


284

MIB Objects Table 3-196 PIM-MIB Tables and Descriptions

Name Description

pimInterfaceTable The (conceptual) table listing the router’s PIMinterfaces. IGMP and PIM are enabled on all interfaces listed in this table.

pimNeighborTable The (conceptual) table listing the router’s PIMneighbors.

pimIpMRouteTable The (conceptual) table listing PIM-specificinformation on a subset of the rows of the ipMRouteTable defined in the IP Multicast MIB.

pimIpMRouteNextHopTable The (conceptual) table listing PIM-specificinformation on a subset of the rows of the ipMRouteNextHopTable defined in the IP Multicast MIB.

pimRPTable The (conceptual) table listing PIM version 1information for the Rendezvous Points (RPs) for IP multicast groups. This table is deprecated since its function is replaced by the pimRPSetTable for PIM version 2.

pimRPSetTable The (conceptual) table listing PIM information for candidate Rendezvous Points (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.

pimCandidateRPTable The (conceptual) table listing the IP multicastgroups for which the local router is to advertise itself as a Candidate-RP when the value of pimComponentCRPHoldTime is non-zero. If this table is empty, then the local router will advertiseitself as a Candidate-RP for all groups (providing the value of pimComponentCRPHoldTime is non-zero).

pimComponentTable The (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 will be a member of exactly one domain. This table also supports, however, routers which may form a border between two PIM-SM domains and do not forward Bootstrap messages between them.


285

MIB Constraints Table 3-197 lists the constraints on objects in the PIM-MIB.

Table 3-197 PIM-MIB Constraints MIB Object Notes

pimInterfaceHelloInterval Not supported

pimInterfaceStatus Not supported

pimInterfaceMode Not supported

pimCandidateRPAddress Not supported

pimCandidateRPRowStatus Not supported

pimJoinPruneInterval Not supported

pimInterfaceJoinPruneInterval Not supported

pimInterfaceCBSRPreference Not supported

pimComponentCRPHoldTime Not supported

pimComponentStatus Not supported

RADIUS-ACC-CLIENT-MIB The RADIUS-ACC-CLIENT-MIB is the MIB module for entities implementing the client side of the RADIUS accounting protocol. Table 3-198 lists the tables associated with this MIB.

Table 3-198 RADIUS-ACC-CLIENT-MIB Tables and Descriptions

Name Description

radiusAccServerTable (conceptual) Table listing the RADIUS accounting servers with which the client shares a secret.

RADIUS-AUTH-CLIENT-MIB The RADIUS-AUTH-CLIENT-MIB is the MIB module for entities implementing the client side of the RADIUS authentication protocol. Table 3-199 lists the tables associated with this MIB.

Table 3-199 RADIUS-AUTH-CLIENT-MIB Tables and Descriptions Name Description

radiusAuthServerTable (conceptual) Table listing the RADIUS authentication servers with which the client shares a secret.


286

RFC1213-MIB The RFC1213-MIB is the second version of the MIB-II used with network management protocols in TCP-based networks. Table 3-200 lists the tables associated with this MIB.

MIB Objects Table 3-200 RFC 1213-MIB Tables and DescriptionsName Description

ifTable List of interface entries. The number of entries is given by

the value of ifNumber.

atTable Address Translation tables contain the NetworkAddress to

`physical' address equivalences. Some interfaces do not

use translation tables for determining address equivalences (for example, DDN-X.25 has an

algorithmic method); if all interfaces are of this type, then the

Address Translation table is empty, in other words, has zero

entries.

ipAddrTable Table of addressing information relevant to this entity's IP

addresses.

ipRouteTable This entity's IP Routing table.

ipNetToMediaTable IP Address Translation table used for mapping from IP

addresses to physical addresses.

tcpConnTable Table containing TCP connection-specific information.

udpTable Table containing UDP listener information.

egpNeighTable EGP neighbor table.

RFC 2011-MIB This MIB describes the module for managing IP and ICMP implementations, but excluding their management of IP routes. Table 3-201 lists the tables associated with this MIB.


287

MIB Objects Table 3-201 RFC 2011-MIB Tables and Descriptions

Name Description

ipAddrTable The table of addressing information relevant to

this entity’s IP addresses.

ipNetToMediaTable The IP Address Translation table used for mapping from IP addresses to physical

addresses.

MIB Constraints

Table 3-202 lists the constraints on objects in the RFC 2011-MIB.

Table 3-202 RFC 2011-MIB Constraints MIB Object Notes

ipForwarding Not supported

ipDefaultTTL Not supported

RFC 2465-MIB

The MIB module for entities implementing the IPv6 protocol. Table 3-203 lists the tables associated with this MIB.


288

MIB Objects Table 3-203 RFC 2465-MIB Tables and Descriptions

Name Descriptionipv6IfTable The IPv6 Interfaces table contains information

on the entity’s internetwork-layer interfaces. An IPv6 interface constitutes a logical network layer attachment to the layer immediately below IPv6 including internet layer ’tunnels’, such as tunnels over IPv4 or IPv6 itself.

ipv6IfStatsTable IPv6 interface traffic statistics. ipv6AddrPrefixTable The list of IPv6 address prefixes of IPv6

interfaces. ipv6AddrTable The table of addressing information relevant

to this node’s interface addresses. ipv6RouteTable IPv6 Routing table. This table contains an

entry for each valid IPv6 unicast route that can be used for packet forwarding determination.

ipv6NetToMediaTable The IPv6 Address Translation table used for mapping from IPv6 addresses to physical addresses. The IPv6 address translation table contain the Ipv6Address to ‘physical’ address equivalencies. Some interfaces do not use translation tables for determining address equivalencies; if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries.

MIB Constraints Table 3-204 lists the constraints on objects in the RFC 2465-MIB.

Table 3-204 RFC 2465-MIB Constraints

MIB Object Notesipv6Forwarding Not supportedipv6DefaultHopLimit Not supportedipv6IfDescr Not supportedipv6IfIdentifier Not supportedipv6IfIdentifierLength Not supportedipv6IfAdminStatus Not supportedipv6RouteValid Not supportedipv6NetToMediaValid Not supported


289

RSVP-MIB The RSVP-MIB defines table objects to describe Resource Reservation Protocol (RSVP). Table 3-205 lists the tables defined in RSVP-MIB.

Table 3-205 RSVP-MIB Tables and Descriptions

Name Description

ifTable List of interface entries. The number of entries is given by the value of ifNumber.

atTable Address Translation tables contain theNetwork Address to physical address equivalences. Some interfaces do not use translation tables for determining address equivalences (that is, DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, that is, has zero entries.

ipAddrTable Table of addressing information relevant to this entity's IP addresses.

ipRouteTable This entity's IP Routing table.

ipNetToMediaTable IP Address Translation table used for mapping from IP addresses to physical addresses.

tcpConnTable Table containing TCP connection-specific information.

udpTable Table containing UDP listener information.

egpNeighTable EGP neighbor table.

MIB Constraints Table 3-206 lists the constraints on objects in the RSVP-MIB. Table 3-206 RSVP-MIB Constraints

MIB Object Notes

rsvpResvFwdNewIndex Not supported

rsvpResvFwdStatus Not supported

rsvpSenderType Not supported

rsvpSenderDestAddr Not supported

rsvpSenderAddr Not supported

rsvpSenderDestAddrLength Not supported

rsvpSenderAddrLength Not supported

rsvpSenderProtocol Not supported

rsvpSenderDestPort Not supported

rsvpSenderPort Not supported

rsvpSenderHopAddr Not supported

Table 3-206 RSVP-MIB Constraints (continued) MIB Object Notes


290

rsvpSenderHopLih Not supported rsvpSenderInterface Not supported rsvpSenderTSpecRate Not supported rsvpSenderTSpecPeakRate Not supported rsvpSenderTSpecBurst Not supported rsvpSenderTSpecMinTU Not supported rsvpSenderTSpecMaxTU Not supported rsvpSenderInterval Not supported rsvpSenderStatus Not supported rsvpSenderRSVPHop Not supported rsvpSenderPolicy Not supported rsvpSenderAdspecBreak Not supported rsvpSenderAdspecHopCount Not supported rsvpSenderAdspecPathBw Not supported rsvpSenderAdspecMinLatency Not supported rsvpSenderAdspecMtu Not supported rsvpSenderAdspecGuaranteedSvc Not supported rsvpSenderAdspecGuaranteedBreak Not supported rsvpSenderAdspecGuaranteedCtot Not supported rsvpSenderAdspecGuaranteedDtot Not supported rsvpSenderAdspecGuaranteedCsum Not supported rsvpSenderAdspecGuaranteedDsum Not supported rsvpSenderAdspecGuaranteedHopCount Not supported rsvpSenderAdspecGuaranteedPathBw Not supported rsvpSenderAdspecGuaranteedMinLatency Not supported rsvpSenderAdspecGuaranteedMtu Not supported rsvpSenderAdspecCtrlLoadSvc Not supported rsvpSenderAdspecCtrlLoadBreak Not supported rsvpSenderAdspecCtrlLoadHopCount Not supported rsvpSenderAdspecCtrlLoadPathBw Not supported rsvpSenderAdspecCtrlLoadMinLatency Not supported rsvpSenderAdspecCtrlLoadMtu Not supported rsvpSenderNewIndex Not supported rsvpIfEnabled Not supported rsvpIfUdpRequired Not supported


291

Table 3-206 RSVP-MIB Constraints (continued) MIB Object Notes rsvpIfRefreshBlockadeMultiple Not supported rsvpIfRefreshMultiple Not supported rsvpIfRefreshInterval Not supported rsvpIfTTL Not supported rsvpIfRouteDelay Not supported rsvpIfStatus Not supported rsvpResvType Not supported rsvpResvDestAddr Not supported rsvpResvSenderAddr Not supported rsvpResvDestAddrLength Not supported rsvpResvSenderAddrLength Not supported rsvpResvProtocol Not supported rsvpResvDestPort Not supported rsvpResvPort Not supported rsvpResvHopAddr Not supported rsvpResvHopLih Not supported rsvpResvInterface Not supported rsvpResvService Not supported rsvpResvTSpecRate Not supported rsvpResvTSpecBurst Not supported rsvpResvTSpecPeakRate Not supported rsvpResvTSpecMinTU Not supported rsvpResvTSpecMaxTU Not supported rsvpResvRSpecRate Not supported rsvpResvRSpecSlack Not supported rsvpResvInterval Not supported rsvpResvScope Not supported rsvpResvShared Not supported rsvpResvExplicit Not supported rsvpResvRSVPHop Not supported rsvpResvPolicy Not supported rsvpResvStatus Not supported rsvpResvNewIndex Not supported rsvpSessionNewIndex Not supported rsvpNbrProtocol Not supported rsvpNbrStatus Not supported


292

SNMP-COMMUNITY-MIB (RFC 2576) The SNMP-COMMUNITY-MIB (RFC 2576) contains objects that help support coexistence between SNMPv1, SNMPv2c, and SNMPv3. Table 3-207 lists the tables associated with this MIB.

Table 3-207 SNMP-COMMUNITY-MIB Tables and Descriptions Name Description

snmpCommunityTable Table of community strings configured in the SNMP engine's LCD.

snmpTargetAddrExtTable Table of mask and mms values associated with thesnmpTargetAddrTable. The snmpTargetAddrExtTable augments the snmpTargetAddrTable with a transport address mask value and a maximum message size value. The transport address mask allows entries in the snmpTargetAddrTable to define a set of addresses instead of just a single address. The maximum message size value allows the maximum message size of another SNMP entity to be configured for use in SNMPv1 (and SNMPv2c) transactions, where the message format does not specify a maximum message size.

SNMP-FRAMEWORK-MIB (RFC 2571) The SNMP-FRAMEWORK-MIB (RFC 2571) contains objects that describe the SNMP management architecture. There are no constraints on this MIB.

SNMP-NOTIFICATION-MIB (RFC 2573) The SNMP-NOTIFICATION-MIB contains managed objects for SNMPv3 notifications. The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable). Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of supported SNMP notifications.

SNMP-TARGET-MIB (RFC 2573)

The SNMP-TARGET-MIB (RFC 2573) contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of the destination entities for SNMP notifications and contains a list of tag values that are used to filter the notifications sent to the entities (see the SNMP-NOTIFICATION-MIB). There are no constraints on this MIB. Table 3-208 lists the tables associated with this MIB.


293

Table 3-208 SNMP-TARGET-MIB Tables and Descriptions

Name Description

snmpTargetAddrTable Table of transport addresses to be used in the generation of SNMP messages

snmpTargetParamsTable Table of SNMP target information to be used in the generation of SNMP messages

SNMP-USM-MIB (RFC 2574) The SNMP-USM-MIB (RFC 2574) contains objects that describe the SNMP user-based security model.

SNMPv2-MIB (RFC 1907)

The SNMPv2-MIB contains objects SNMPv2 entities. The SNMPv2-MIB contains the following mandatory object groups: SNMP group—Collection of objects providing basic instrumentation and control of an SNMP entity. System group—Collection of objects common to all managed systems. snmpSetGroup—Collection of objects that allow several cooperating SNMPv2 entities, all acting in a manager role, to

coordinate their use of the SNMPv2 set operation. snmpBasicNotificationsGroup—The two notifications are coldStart and authenticationFailure, which an SNMPv2 entity

is required to implement.

SNMP-VACM-MIB The SNMP-VACM-MIB contains objects to manage the View-Based Access Control Model (VACM) for SNMP clients and managers. The MODULE-IDENTITY for the SNMP-VACM-MIB is snmpVacmMIB, and its top-level OID is 1.3.6.1.6.3.16 (iso.org.dod.internet.snmpv2.snmpModules.snmpVacmMIB).

SONET-MIB (RFC 2558) The SONET-MIB (RFC 2558) provides both configuration and performance monitoring objects for SONET interfaces. Note: When the SONET path is initialized and no active alarms exist, the value of sonetPathCurrentStatus object is zero.

Note: If an alarm is triggered and cleared, the value of sonetPathNoDefect object is one. Note: The intervals in a dsx1IntervalTable are reset during an OIR operation whereas the SONET intervals are not reset.


294

MIB Tables Table 3-209 lists the tables in SONET-MIB:

Table 3-209 SONET-MIB Tables


sonetMediumTable The SONET/SDH Medium table.

sonetSectionCurrentTable The SONET/SDH Section Current table

sonetSectionIntervalTable The SONET/SDH Section Interval table.

sonetLineCurrentTable The SONET/SDH Line Current table.

sonetLineIntervalTable The SONET/SDH Line Interval table.

sonetFarEndLineCurrentTable The SONET/SDH Far End Line Current table.

sonetFarEndLineIntervalTable The SONET/SDH Far End Line Interval table.

sonetPathCurrentTable The SONET/SDH Path Current table.

sonetPathIntervalTable The SONET/SDH Path Interval table.

sonetFarEndPathCurrentTable The SONET/SDH Far End Path Current table.

sonetFarEndPathIntervalTable The SONET/SDH Far End Path Interval table.

sonetVTCurrentTable The SONET/SDH VT Current table.

sonetVTIntervalTable The SONET/SDH VT Interval table.

sonetFarEndVTCurrentTable The SONET/SDH Far End VT Current table.

sonetFarEndVTIntervalTable The SONET/SDH Far End VT Interval table.

MIB Constraints

Table 3-210 lists the constraints that the Cisco ASR 9000 Series router places on objects in the Sonet-MIB(RFC 2558).

Table 3-210 Sonet-MIB Constraints MIB Object Notes sonetPathCurrentTable

sonetPathCurrentWidth Read-only

sonetVTCurrentTable Not Implemented.


295

Table 3-210 Sonet-MIB Constraints (continued) MIB Object Notes

sonetVTIntervalTable Not Implemented.

sonetFarEndVTCurrentTable Not Implemented.

sonetFarEndVTIntervalTable Not Implemented.

SonetMediumTable

sonetMediumLineCoding Read-only. sonetMediumLineType Read-only. sonetMediumCircuitIdentifier Read-only. sonetMediumLoopbackConfig Read-only.

sonetSESthresholdSet Not Implemented.

TCP-MIB The TCP-MIB is the MIB module for managing TCP implementations. Table 3-211 lists the tables associated with this MIB.

Table 3-211 TCP-MIB Tables and Descriptions

Name Description

tcpConnectionTable Table containing information about existing TCP connections. Note:

that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state


296

Table 3-211 TCP-MIB Tables and Descriptions (continued)

Name Description

tcpListenerTable Table containing information about TCP listeners. A listening application can be represented in three possible ways: 1. An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a tcpListenerLocalAddressType of unknown (0) and a tcpListenerLocalAddress of ‘h’ (a zero-length octet-string). 2. An application that is willing to accept only IPv4 or IPv6 datagrams is represented by a tcpListenerLocalAddressType of the appropriate address type and a tcpListenerLocalAddress of '0.0.0.0' or '::' respectively. 3. An application that is listening for data destined only to a specific IP address, but from any remote system, is represented by a tcpListenerLocalAddressType of an appropriate address type, with tcpListenerLocalAddress as the specific local address. Note The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType IPv4(1))

tcpConnTable Table containing information about existing IPv4-specific TCP connections or listeners. This table has been deprecated in favor of the version neutral tcpConnectionTable

MIB Constraints Table 3-212 lists the constraints that the router places on objects in the TCP-MIB.

Table 3-212 TCP-MIB Constraints MIB Object Notes

tcpConnectionTable

tcpConnectionProcess Not supported

UDP-MIB The UDP-MIB is the MIB module for UDP implementations. See RFC 4113. Table 3-213 lists the tables associated with this MIB.


297

Table 3-213 UDP-MIB Tables and Descriptions

Name Description

udpEndpointTable Table containing information about this entity's UDP endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 'sockets' to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType IPv4(1). Unlike the udpTable in RFC 2013, this table also allows the representation of an application that completely specifies both local and remote addresses and ports. A listening application is represented in three possible ways: 1) An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a udpEndpointLocalAddressType of unknown(0) and a udpEndpointLocalAddress of h (a zero-length octet-string). 2) An application that is willing to accept only IPv4 or only IPv6 datagrams is represented by a udpEndpointLocalAddressType of the appropriate address type and a udpEndpointLocalAddress of '0.0.0.0' or '::' respectively. 3) An application that is listening for datagrams only for a specific IP address but from any remote system is represented by a udpEndpointLocalAddressType of the appropriate address type, with udpEndpointLocalAddress specifying the local address. In all cases where the remote is a wildcard, the udpEndpointRemoteAddressType is unknown(0), the udpEndpointRemoteAddress is h (a zero-length octet-string), and the udpEndpointRemotePort is 0. If the operating system is demultiplexing UDP packets by remote address and port, or if the application has 'connected' the socket specifying a default remote address and port, the udpEndpointRemote* values should be used to reflect this.

udpTable Table containing IPv4-specific UDP listener information. It containsinformation about all local IPv4 UDP end-points on which an application is currently accepting datagrams. This table has been replaced by the version neutral udpEndpointTable but is currently still supported on IOS XR.

MIB Constraints Table 3-214 lists the constraints that the router places on objects in the UDP-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-214 UDP-MIB Constraints

MIB Object Notes

tcpConnectionTable

udpEndPointProcess Not supported


298

VRRP-MIB

The VRRP-MIB defines table objects to manage Virtual Router Redundancy Protocol (VRRP) routers. Table 3-215 lists the tables defined in VRRP-MIB.

Table 3-215 VRRP-MIB Tables


vrrpOperTable Defines vrrpOperEntry attribute that containsinformation about the state of each VRRP virtual router.

vrrpAssoIpAddrTable Contains the virtual IP addresses (operational) associated with a virtual router

vrrpRouterStatsTable Contains statistical information about the state changes and packets sent or received for a virtual router.

MIB Constraints Table 3-216 lists the constraints that the router places on objects in the VRRP-MIB. For detailed definitions of MIB objects, see the MIB.

Table 3-216 VRRP-MIB Constraints

MIB Object Notes

vrrpNotificationCntl Not supported

vrrpOperAdminState Not supported

vrrpOperPriority Not supported

vrrpOperPrimaryIpAddr Not supported

vrrpOperAuthType Not supported

vrrpOperAuthKey Not supported

vrrpOperAdvertisementInterval Not supported

vrrpOperPreemptMode Not supported

vrrpOperProtocol Not supported

vrrpOperRowStatus Not supported

vrrpAssoIpAddrRowStatus Not supported

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Chapter 4 - Monitoring Notifications

299

Chapter 4 - Monitoring Notifications

This chapter describes the Cisco ASR 9000 Series router notifications supported by the MIB enhancements feature introduced in Cisco IOS XR Software Release 3.7. SNMP uses notifications to report events on a managed device. The notifications are traps for different events. The router also supports other notifications not listed. This chapter contains the following sections: SNMP Notification Overview, page 299

Enabling Notifications, page 300

Cisco SNMP Notifications, page 300

SNMP Notification Overview

An SNMP agent can notify the SNMP manager when important system events occur, such as the following: An interface or card starts or stops running

Temperature thresholds are crossed

Authentication failures occur

When an agent detects an alarm condition, the agent: Logs information about the time, type, and severity of the condition

Generates a notification message, which it then sends to a designated IP host SNMP notifications are sent as one of the following:

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

To use SNMP notifications on your system, you must specify their recipients. These recipients indicate where Network Registrar notifications are directed. By default, all notifications are enabled, but no recipients are defined. Until you define the recipients, no notifications are sent. Many commands use the keyword traps in the command syntax.


300

Note: Most notification types are disabled by default. However, some notification types cannot be controlled with the snmp command. For example, some notification types can be enabled by snmp or CLI and other types are enabled by a combination of CLI and snmp. The linkUpDown notifications are controlled by the snmp trap link-status and snmp-server trap link ietf commands. Specify the trap types if you do not want all traps to be sent. Then use multiple snmp-server traps commands, one for each of the trap types that you used in the snmp host command.

Enabling Notifications

You can enable MIB notifications using either of the following procedures: Using the command-line interface (CLI)—Specify the recipient of the trap message and specify the types of traps

sent. The enabling command also specifies which types of traps are enabled.

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

— To enable the notifications, set the object to true (1).

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

For detailed procedures, go to the following URL: http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/system_management/command/reference/yr3 7snmp.html Note: If you issue the snmp-server traps command without a notification-type argument, the router generates traps for all types of events, which might not be desirable. Some MIBs require the user to set additional objects to enable some notifications.

Cisco SNMP Notifications

This section contains tables that describe a MIB event, why the event occurred, and a recommendation as to how to handle the event. Each table lists the following information: Event—The event display

Description—What the event indicates

Probable cause—What might have caused the notification

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

Note: In the following tables, where “no action is required” is documented, there might be instances where an application, such as trouble ticketing, occurs. For detailed information, go to the following URL: http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.7/system_management/command/reference/yr3 7snmp.html


301

Environmental or Functional Notifications Table 4-1 lists notifications generated for events that might indicate the failure of the Cisco ASR 9000 Series router or conditions that might affect router functionality.

Table 4-1 Environmental or Functional Notifications

Event Description Probable Cause Recommended ActioncefcModuleStatusChange

Indicates that the status of a module has changed.

Module has unknown state.

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

Module is operational. No action is required.

Module has failed due to some condition.

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

cefcPowerStatusChange

Indicates that the power status of a FRU has changed.

FRU is powered off due to unknown problem.

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

FRU is powered on. No action is required.

FRU is administratively off.

No action is required.

FRU is powered off as the available system power is insufficient.

Enter the show environmentcommand to check the actual power usage.

cefcFRUInserted Indicates that a FRU was inserted.

A new field-replaceable unit such as a fan, transceiver, power supply, or redundant power supply was added.


cefcFRURemoved Indicates that a FRU was removed.

A field-replaceable unit such as a fan, transceiver, power supply, or redundant power supply was removed.

Replace the field-replaceable unit.


302

Table 4-1 Environmental or Functional Notifications (continued)

Event Description Probable Cause Recommended Action dsx1LineStatus-Change

The dsx1LineStatus is a bit map that contains loopback state and failure state information.

When a failure is detected, the corresponding dsx1LineStatus bit should change to reflect the failure. For example, when a Receiving LOS failure is detected, the corresponding bit (bit 64) should be set to indicate the failure and as a result the dsx1LineStatus changes.

When the dsx1LineStatus reports failures, the recommended action is correction of the conditions causing the error.

ciscoSonetSectionStatusChange

Indicates that the value of sonetSection-CurrentStatus has changed.

Section loss of: Frame failure Signal failure

Enter the show controllers command for the interface and check that the Alarm Defects are None and Active Alarms are Zero.

ciscoSonetPathStatusChange

Indicates that the value of sonetPathCurrent-Status has changed.

Caused due to: sonetPathSTSLOP sonetPathSTSAIS sonetPathSTSRDI sonetPathUnequipped sonetPathSignalLabel-

Mismatch

Enter the show controllers command for the interface and check that the Alarm defects are None and Active Alarms are Zero.

ciscoSonetLineStatusChange

Indicates that the value of sonetLineCurrent- Status has changed.

Caused due to: sonetLineAIS sonetLineRDI

Enter the show controllers command for the interface and check that the Alarm Defects are None and Active Alarms are Zero.

dsx3LineStatus-Change

Indicates that the value of dsx3LineStatus has changed. It is a bit map containing loopback state and failure state information.

Caused due to: link failure hardware issue

If a link fails or a hardware issue appears, alarms (single or mulitple depending on the failure) are generated. A bit position is defined for each failure and the sum of all the failed bit positions is set to dsx3LineStaus. A dsx3LineStatus-Change notification is generated whenever there is a change in the value of dsx3LineStatus.

When the dsx3LineStatus reports failures, check for the bit position to identify the cause of failure.


303

Flash Card Notifications Table 4-2 lists CISCO-FLASH-MIB notifications generated by Cisco ASR 9000 Series router flash cards. These notifications indicate the failure of a flash card or error conditions on the card that might affect the functionality of all interfaces.

Table 4-2 Flash Card Notifications Event Description Probable Cause Recommended Action ciscoFlashDeviceInsertedNotif Indicates a removable

flash device was inserted into the router.

A removable flash device was inserted into the router.

Check for the flash card that was inserted from ciscoFlashDeviceTable. This information is also provided in the notification itself.

ciscoFlashDeviceRemovedNotif Indicates a removable flash card was removed from the router.

A removable flash device was removed from the router.

Check the ciscoFlashDeviceTable to identify the removed flash card. This information is also provided in the notification itself.

Interface Notifications

Table 4-3 lists notifications generated by the router for link-related (interface) events. Table 4-3 Interface Notifications

Event Description Probable Cause Recommended Action linkDown Indicates that a link is

about to enter the down state, which means it cannot transmit or receive traffic. The ifOperStatus object shows the previous state of the link. Value is down(2).

An internal software error might have occurred.

Use the CLI command, show ip interface brief, to determine the cause of the interface down.

linkUp Indicates that the link is up. The value of ifOperStatus indicates the new link state. Value is up(1).

The port manager reactivated a port in the linkdown state during a switchover.


Routing Protocol Notifications Table 4-4 lists BGP4-MIB notifications that are Border Gateway Protocol (BGP) state changes generated by the Cisco ASR 9000 Series router to indicate error conditions for routing protocols and services.


304

Table 4-4 Routing Protocol Notifications

Event Description Probable Cause Recommended Action

bgpEstablished The BGP Finite State Machine (FSM) enters the ESTABLISHED state. It becomes active on the router.

The BGP routing protocol changed status.


bgpBackwardTransition Indicates BGP protocol transition from a higher-level state to a lower-level state. The prefix count for an address family on a BGP session exceeded the configured threshold value.

The BGP routing protocol changed status.

This threshold value is configured using the CLI command neighbor nbr_addr max_prefixes [threshold] [warning-only]

Redundancy Framework Notifications Table 4-5 lists CISCO-RF-MIB notifications that can occur in a redundant system. There are two types of notifications: Switch of Activity (SWACT)—Either a forced or automatic switch of active status from the active unit to the standby unit. The former standby unit is now referred to as the active unit. Progression—The process of making the redundancy state of the standby unit equivalent to that of the active unit. This includes transitioning the RF state machine through several states, which drives the clients on the active unit to synchronize any relevant data with their peer on the standby unit. Table 4-5 Redundancy Framework Notifications

Event Description Probable Cause Recommended Action ciscoRFSwactNotif Indicates that the RF

state changed. A switch of activity notification is sent by the newly active redundant unit.

A switch of activity occurs. If a SWACT event is indistinguishable from a reset event, then a network management station should use this notification to differentiate the activity.

If the switchover occurred because the active unit failed (indicated by cRFStatusLastSwact-ReasonCode), see if there are any hardware failures; otherwise, no action is required.

ciscoRFProgressionNotif Indicates that the RF state changed.

The active redundant unit RF state changed or the RF state of the peer unit changed.

To avoid an increase of notifications for all state transitions, send notifications for transitions to the following RF states:

standbyCold(5) standbyHot(9) active(14) activeExtraload(15)


305

Netsync Notifications Table 4-6 lists CISCO-NETSYNC-MIB notifications that can occur in a system.

Table 4-6 Netsync Notifications

Event Description Probable Cause Recommended Action ciscoNetsyncSelectedT0Clock

Indicates that the source selected for T0 (system timing input) has changed.

Change in system timing input.


ciscoNetsyncSelectedT4Clock

Indicates that the source selected for a T4 output (external clock output) has changed.

Change in external clock output.


ciscoNetsyncInputSignalFailureStatus

Indicates that there has been a signal failure on an input

A signal going out-of-band.

The trap indicates the cause of the failure, and the user will have to investigate further.

ciscoNetsyncInputAlarmStatus

Indicates that there has been an alarm on the input

An interface going down.

The trap indicates the cause of the failure, and the user will have to investigate further.

Subscriber Session Notifications Table 4-7 lists CISCO-SUBSCRIBER-SESSION-MIB notifications that can occur in a system. Table 4-7 Netsync Notifications Event Description Probable Cause Recommended Action csubSessionRisingThreshNotif

Indicates that the the subscriber count is exceeding the configured rising threshold value.

An instance of csubAggStatsUpSessions exceeding the corresponding instance of csubSessionRisingThresh.


csubSessionFallingThreshNotif

Indicates that the subscriber count drops below the configured falling threshold value.

An instance of csubAggStatsUpSessions falling below the corresponding instance of csubSessionFallingThresh


csubSessionDeltaPercentThresh Notif

Indicates that tfalling percent of subscriber session exceeds the configured delta percent value in the configured evaluation time.

An instance of csubAggStatsUpSessions dropping by the percentage indicated by the corresponding csubSessionDeltaPercentLossThre sh within the amount of time indicated by the corresponding subSessionThresholdEvalInterval.


Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Appendix 1 - Using MIBs

306

Appendix 1 - Using MIBs

This chapter describes how to work with MIBs on the Cisco ASR 9000 Series router. This appendix contains the following sections: Cisco Unique Device Identifier Support, page 306

Cisco Redundancy Features, page 307

Managing Physical Entities, page 308

Monitoring Quality of Service, page 320

Monitoring Router Interfaces, page

Billing Customers for Traffic, page

Using IF-MIB Counters, page

Cisco Unique Device Identifier Support

The ENTITY-MIB supports the Cisco compliance effort for a unique device identifier (UDI) standard stored in Identification Programmable Read-Only Memory (IDPROM). The Cisco UDI provides a unique identity for every Cisco product. The UDI is composed of three separate data elements that must be stored in the entPhysicalTable:

Orderable product identifier (PID)—The alphanumeric identifier used by customers to order Cisco products. Two

examples include A9K-RSP-4G and A9K-4T-E. PID is limited to 18 characters and must be stored in the entPhysicalModelName object.

Version identifier (VID)— The version of the PID. The VID indicates the number of times a product has versioned in ways that are reported to a customer. For example, the product identifier A9K-RSP-4G may have a VID of V04. VID is limited to three alphanumeric characters and must be stored in the entPhysicalHardwareRev object.

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

https://tools.cisco.com/emco/inbiz/inbiz/Home Serial number format is defined in four fields:

— Location (L)

— Year (Y)

— Workweek (W)

— Sequential serial ID (S)

The SN label is represented as: LLLYYWWSSS.


307

Note: The Version ID returns NULL for those old or existing cards with IDPROMs that do not have the Version ID field. Therefore, corresponding entPhysicalHardwareRev returns NULL for cards that do not have the Version ID field in IDPROM.

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

Levels of Redundancy, page 307

Verifying the Cisco ASR 9000 Series Router Redundancy, page 308

Levels of Redundancy This section describes the levels of redundancy supported on the Cisco ASR 9000 Series router and how to verify that this feature is available. The Cisco ASR 9000 Series routers supports fault resistance by allowing a Cisco redundant Route Switch Processor (RSP) to take over if the active RSP fails. Redundancy prevents equipment failures from causing service outages, and supports hitless maintenance and upgrade activities. The state of the interfaces and subinterfaces is maintained along with the state of line cards and various packet processing hardware. Redundant systems support two RSP. One acts as the active RSPs while the other acts as the standby RSPs. The redundancy feature provides high availability for the Cisco routers by switching when one of the following conditions occur:

Cisco IOS XR Software failure

Software upgrade

Maintenance procedure

The Cisco ASR 9000 Series routers operates in Nonstop Forwarding/Stateful Switchover (NSF/SSO) mode.

Nonstop Forwarding/Stateful Switchover

This section describes the Nonstop Forwarding/Stateful Switchover mode. With NSF/SSO, the Cisco ASR 9000 Series routers can change from the active to the standby RSPs almost immediately while continuing to forward packets. Cisco IOS XR Software NSF/SSO support on this platform enables immediate failover.


308

In networking devices running NSF/SSO, both RSPs must be running the same configuration so that the standby RSP is always ready to assume control following a fault on the active RSP. The configuration information is synchronized from the active RSP to the standby RSP at startup and each timechanges to the active RSP configuration occur. Following an initial synchronization between the two RSPs, NFS/SSO maintains RSP state information between them, including forwarding information. The Cisco Nonstop Forwarding (NSF) works with Stateful Switchover (SSO) to minimize the amount of time a network is unavailable to its users following a Route Switching Processor (RSP) fail-over in a router with dual RSPs. NSF/SSO capability allows routers to detect a switchover and take the necessary actions to continue forwarding network traffic and to recover route information from peer devices. The Cisco NSF works with the Stateful Switchover (SSO) feature in Cisco IOS XR Software to minimize the amount of time a network is unavailable to its users following a switchover. The main objective of the Cisco NSF/SSO is to continue forwarding data packets along known routes while the routing protocol information is restored following a route switchover.

Verifying the Cisco ASR 9000 Series Router Redundancy To display information about the active and standby RSP engines installed in the Cisco ASR 9000 Series router, use the show redundancy command and show redundancy states command.

Example RSP/0/RSP0/CPU0:aus-ASR-9010-18#show redundancy Fri Feb 20 01:15:10.213 PST PST Redundancy information for node 0/RSP0/CPU0: ========================================== Node 0/RSP0/CPU0 is in ACTIVE role Partner node (0/RSP1/CPU0) is in STANDBY role Standby node in 0/RSP1/CPU0 is ready Standby node in 0/RSP1/CPU0 is NSR-ready Reload and boot info ---------------------- A9K-RSP-4G reloaded Thu Feb 19 09:29:24 2009: 15 hours, 45 minutes ago Active node booted Thu Feb 19 10:40:02 2009: 14 hours, 35 minutes ago Last switch-over Thu Feb 19 21:45:59 2009: 3 hours, 29 minutes ago Standby node boot Thu Feb 19 21:46:57 2009: 3 hours, 28 minutes ago Standby node last went not ready Thu Feb 19 21:49:06 2009: 3 hours, 26 minutes ago Standby node last went ready Thu Feb 19 21:49:06 2009: 3 hours, 26 minutes ago Standby node last went not NSR-ready Thu Feb 19 21:49:27 2009: 3 hours, 25 minutes ago Standby node last went NSR-ready Thu Feb 19 21:49:27 2009: 3 hours, 25 minutes ago There have been 2 switch-overs since reload

Managing Physical Entities This section describes how to use SNMP to manage the physical entities (components) in the router by: Performing Inventory Management, page 310


309

Monitoring and Configuring FRU Status, page 318

Generating SNMP Notifications, page 318


310

Purpose and Benefits

The physical entity management feature of the Cisco ASR 9000 Series router SNMP implementation does the following: Monitors and configures the status of field-replaceable units (FRUs)

Provides information about physical port to interface mappings

Provides asset information for asset tagging

Provides firmware and software information for chassis components

MIBs Used for Physical Entity Management CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (IDPROM contents) for the physical entities listed

in the entPhysicalTable of the ENTITY-MIB. The MIB provides device-specific information for physical entities, including orderable part number, serial number, manufacturing assembly number, and hardware, software, and firmware information.

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

CISCO-ENTITY-SENSOR-MIB—Contains information about entities in the entPhysicalTable with an entPhysicalClass value of sensor.

ENTITY-MIB—Contains information for managing physical entities on the router. It also organizes the entities into a containment tree that depicts their hierarchy and relationship to each other.

The MIB contains the following tables:

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

— The entAliasMappingTable maps each physical port’s entPhysicalIndex value to its corresponding ifIndex value in the IF-MIB ifTable.

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

Performing Inventory Management To obtain information about entities in the router, perform a MIB walk on the ENTITY-MIB entPhysicalTable. As you examine sample entries in the ENTITY-MIB entPhysicalTable, consider the following objects:

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

the entity in other MIBs.

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

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


311

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

Sample of ENTITY-MIB entPhysicalTable Entries The samples in this section show how information is stored in the entPhysicalTable. You can perform asset inventory by examining entPhysicalTable entries. Note: The sample outputs and values that appear throughout this appendix are examples of data you can view when using MIBs.

The following display shows the ENTITY-MIB entPhysicalTable sample entries: entPhysicalDescr.186 = 4-Port 10GE Extended Line Card, Requires XFPs entPhysicalDescr.187 = Ten GigabitEthernet Port entPhysicalDescr.188 = GigeEthernet XFP container entPhysicalDescr.189 = entPhysicalDescr.190 = Transceiver Temperature Sensor entPhysicalDescr.191 = Transceiver Tx Power Sensor entPhysicalDescr.192 = Transceiver Rx Power Sensor entPhysicalDescr.193 = Transceiver Transmit Bias Current Sensor entPhysicalDescr.194 = Line Card host entPhysicalDescr.195 = Inlet Temperature Sensor entPhysicalDescr.196 = Hot Temperature Sensor entPhysicalDescr.197 = Voltage Sensor - IBV entPhysicalDescr.198 = Voltage Sensor - 5.0V entPhysicalDescr.199 = Voltage Sensor - VP3P3_CAN entPhysicalDescr.200 = Voltage Sensor - 3.3V Where entPhysicalDescr identifies the manufacturer name for the physical entity. entPhysicalVendorType.186 = cevModuleA9K4x10GEE entPhysicalVendorType.187 = cevPortGEXFP entPhysicalVendorType.188 = cevContainerXFP entPhysicalVendorType.189 = cevXFPUnknown entPhysicalVendorType.190 = cevSensorTransceiverTemp entPhysicalVendorType.191 = cevSensorTransceiverTxPwr entPhysicalVendorType.192 = cevSensorTransceiverRxPwr entPhysicalVendorType.193 = cevSensorTransceiverCurrent entPhysicalVendorType.194 = cevModuleASR9KHost entPhysicalVendorType.195 = cevSensorModuleInletTemp entPhysicalVendorType.196 = cevSensorHotTemperature entPhysicalVendorType.197 = cevSensorModuleDeviceVoltage entPhysicalVendorType.198 = cevSensorModuleDeviceVoltage entPhysicalVendorType.199 = cevSensorModuleDeviceVoltage entPhysicalVendorType.200 = cevSensorModuleDeviceVoltage


312

Where entPhysicalVendorType identifies the unique vendor-specific hardware type of the physical entity. entPhysicalContainedIn.186 = 92 entPhysicalContainedIn.187 = 186 entPhysicalContainedIn.188 = 187 entPhysicalContainedIn.189 = 188 entPhysicalContainedIn.190 = 189 entPhysicalContainedIn.191 = 189 entPhysicalContainedIn.192 = 189 entPhysicalContainedIn.193 = 189 entPhysicalContainedIn.194 = 186 entPhysicalContainedIn.195 = 194 entPhysicalContainedIn.196 = 194 entPhysicalContainedIn.197 = 194 entPhysicalContainedIn.198 = 194 entPhysicalContainedIn.199 = 194 entPhysicalContainedIn.200 = 194

Where entPhysicalContainedIn indicates the entPhysicalIndex of a parent entity (component). entPhysicalClass.186 = module(9) entPhysicalClass.187 = port(10) entPhysicalClass.188 = container(5) entPhysicalClass.189 = module(9) entPhysicalClass.190 = sensor(8) entPhysicalClass.191 = sensor(8) entPhysicalClass.192 = sensor(8) entPhysicalClass.193 = sensor(8) entPhysicalClass.194 = module(9) entPhysicalClass.195 = sensor(8) entPhysicalClass.196 = sensor(8) entPhysicalClass.197 = sensor(8) entPhysicalClass.198 = sensor(8) entPhysicalClass.199 = sensor(8) entPhysicalClass.200 = sensor(8)


313

Where entPhysicalClass indicates the general type of hardware device. entPhysicalParentRelPos.186 = 0 entPhysicalParentRelPos.187 = 1 entPhysicalParentRelPos.188 = 0 entPhysicalParentRelPos.189 = 0 entPhysicalParentRelPos.190 = 0 entPhysicalParentRelPos.191 = 1 entPhysicalParentRelPos.192 = 2 entPhysicalParentRelPos.193 = 3 entPhysicalParentRelPos.194 = 0 entPhysicalParentRelPos.195 = 0 entPhysicalParentRelPos.196 = 1 entPhysicalParentRelPos.197 = 2 entPhysicalParentRelPos.198 = 3 entPhysicalParentRelPos.199 = 4 entPhysicalParentRelPos.200 = 5

Where entPhysicalParentRelPos indicates the relative position of this child among the other entities. entPhysicalName.186 = module 0/5/CPU0 entPhysicalName.187 = TenGigE0/5/0/1 entPhysicalName.188 = slot mau 0/5/CPU0/1 entPhysicalName.189 = module mau 0/5/CPU0/1 entPhysicalName.190 = temperature 0/5/CPU0/1 entPhysicalName.191 = power Tx 0/5/CPU0/1 entPhysicalName.192 = power Rx 0/5/CPU0/1 entPhysicalName.193 = current 0/5/CPU0/1 entPhysicalName.194 = module 0/5/CPU0 entPhysicalName.195 = temperature 0/5/CPU0 entPhysicalName.196 = temperature 0/5/CPU0 entPhysicalName.197 = voltage 0/5/CPU0 entPhysicalName.198 = voltage 0/5/CPU0 entPhysicalName.199 = voltage 0/5/CPU0 entPhysicalName.200 = voltage 0/5/CPU0

Where entPhysicalName provides the textual name of the physical entity. entPhysicalHardwareRev.186 = entPhysicalHardwareRev.187 = entPhysicalHardwareRev.188 = entPhysicalHardwareRev.189 = entPhysicalHardwareRev.190 = entPhysicalHardwareRev.191 = entPhysicalHardwareRev.192 = entPhysicalHardwareRev.193 = entPhysicalHardwareRev.194 =


314

entPhysicalHardwareRev.195 = entPhysicalHardwareRev.196 = entPhysicalHardwareRev.197 = entPhysicalHardwareRev.198 = entPhysicalHardwareRev.199 = entPhysicalHardwareRev.200 = Where entPhysicalHardwareRev provides the vendor-specific hardware revision number (string) for the physical entity. entPhysicalFirmwareRev.186 = Version 0.63(20081010:215422) entPhysicalFirmwareRev.187 = entPhysicalFirmwareRev.188 = entPhysicalFirmwareRev.189 = entPhysicalFirmwareRev.190 = entPhysicalFirmwareRev.191 = entPhysicalFirmwareRev.192 = entPhysicalFirmwareRev.193 = entPhysicalFirmwareRev.194 = entPhysicalFirmwareRev.195 = entPhysicalFirmwareRev.196 = entPhysicalFirmwareRev.197 = entPhysicalFirmwareRev.198 = entPhysicalFirmwareRev.199 = entPhysicalFirmwareRev.200 = Where entPhysicalFirmwareRev provides the vendor-specific firmware revision number (string) for the physical entity. entPhysicalSoftwareRev.186 = 3.7.2.24I entPhysicalSoftwareRev.187 = entPhysicalSoftwareRev.188 = entPhysicalSoftwareRev.189 = 3.7.2.24I entPhysicalSoftwareRev.190 = entPhysicalSoftwareRev.191 = entPhysicalSoftwareRev.192 = entPhysicalSoftwareRev.193 = entPhysicalSoftwareRev.194 = 3.7.2.24I entPhysicalSoftwareRev.195 = entPhysicalSoftwareRev.196 = entPhysicalSoftwareRev.197 = entPhysicalSoftwareRev.198 = entPhysicalSoftwareRev.199 = entPhysicalSoftwareRev.200 =

Where entPhysicalSoftwareRev provides the software revision number for the physical entity.

entPhysicalSerialNum.186 = FHH1213002A entPhysicalSerialNum.187 =


315

entPhysicalSerialNum.188 = entPhysicalSerialNum.189 = ECL114704JD entPhysicalSerialNum.190 = entPhysicalSerialNum.191 = entPhysicalSerialNum.192 = entPhysicalSerialNum.193 = entPhysicalSerialNum.194 = entPhysicalSerialNum.195 = entPhysicalSerialNum.196 = entPhysicalSerialNum.197 = entPhysicalSerialNum.198 = entPhysicalSerialNum.199 = entPhysicalSerialNum.200 =

Where entPhysicalSerialNum provides the vendor-specific serial number (string) for the physical entity.

entPhysicalMfgName.186 = Cisco Systems Inc. entPhysicalMfgName.187 = entPhysicalMfgName.188 = entPhysicalMfgName.189 = entPhysicalMfgName.190 = entPhysicalMfgName.191 = entPhysicalMfgName.192 = entPhysicalMfgName.193 = entPhysicalMfgName.194 = entPhysicalMfgName.195 = entPhysicalMfgName.196 = entPhysicalMfgName.197 = entPhysicalMfgName.198 = entPhysicalMfgName.199 = entPhysicalMfgName.200 =

Where entPhysicalMfgName provides the manufacturer name for the physical component. entPhysicalModelName.186 = A9K-4T-E entPhysicalModelName.187 = entPhysicalModelName.188 = entPhysicalModelName.189 = ONS-XC-10G-S1 entPhysicalModelName.190 = entPhysicalModelName.191 = entPhysicalModelName.192 = entPhysicalModelName.193 = entPhysicalModelName.194 = entPhysicalModelName.195 = entPhysicalModelName.196 = entPhysicalModelName.197 = entPhysicalModelName.198 = entPhysicalModelName.199 = entPhysicalModelName.200 =


316

Where entPhysicalModelName provides the vendor-specific model name string for the physical component. entPhysicalAlias.186= entPhysicalAlias.187= entPhysicalAlias.188= entPhysicalAlias.189 = entPhysicalAlias.190 = entPhysicalAlias.191 = entPhysicalAlias.192 = entPhysicalAlias.193 = entPhysicalAlias.194 = host entPhysicalAlias.195 = entPhysicalAlias.196 = entPhysicalAlias.197 = entPhysicalAlias.198 = entPhysicalAlias.199 = entPhysicalAlias.200 =

Where entPhysicalAlias provides the alias name for the physical component. entPhysicalAssetID.186 = entPhysicalAssetID.187 = entPhysicalAssetID.188 = entPhysicalAssetID.189 = entPhysicalAssetID.190 = entPhysicalAssetID.191 = entPhysicalAssetID.192 = entPhysicalAssetID.193 = entPhysicalAssetID.194 = entPhysicalAssetID.195 = entPhysicalAssetID.196 = entPhysicalAssetID.197 = entPhysicalAssetID.198 = entPhysicalAssetID.199 = entPhysicalAssetID.200 =

Where entPhysicalAssetID provides the vendor-specific asset ID for the physical component. entPhysicalIsFRU.186 = true(1) entPhysicalIsFRU.187 = false(2)


317

entPhysicalIsFRU.188 = false(2) entPhysicalIsFRU.189 = true(1) entPhysicalIsFRU.190 = false(2) entPhysicalIsFRU.191 = false(2) entPhysicalIsFRU.192 = false(2) entPhysicalIsFRU.193 = false(2) entPhysicalIsFRU.194 = false(2) entPhysicalIsFRU.195 = false(2) entPhysicalIsFRU.196 = false(2) entPhysicalIsFRU.197 = false(2) entPhysicalIsFRU.198 = false(2) entPhysicalIsFRU.199 = false(2) entPhysicalIsFRU.200 = false(2)

Where entPhysicalIsFRU indicates whether or not this physical entity is considered a field-replaceable unit (FRU).

Note the following about the sample configuration: All chassis slots and line card ports have the same entPhysicalContainedIn value:

— For chassis slots, entPhysicalContainedIn = 1 (the entPhysicalIndex of the chassis). — For line card ports, entPhysicalContainedIn = 26 (the entPhysicalIndex of the line card).

Each chassis slot and line card port has a different entPhysicalParentRelPos to show its relative position within

the parent object.

Determining the ifIndex Value for a Physical Port

The ENTITY-MIB entAliasMappingIdentifier maps a physical port to an interface by mapping the port’s entPhysicalIndex to its corresponding ifIndex value in the IF-MIB ifTable. The following sample shows that the physical port with a entPhysicalIndex value of 35 is associated with the interface with the ifIndex value of four: entAliasMappingIdentifer.35.0 = ifIndex.4 Note: See the MIB for detailed descriptions of possible MIB values.


318

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

cefcModuleAdminStatus—The administrative state of the FRU. This object is read-only and returns enable.

cefcModuleOperStatus—The current operational state of the FRU.

Figure 1-1 shows a cefcModuleTable entry for a line card with the entPhysicalIndex value of 24.

See the “FRU Status Changes” section on page 320 for information about how the router generates notifications to indicate changes in FRU status.

Generating SNMP Notifications

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

Identifying Hosts to Receive Notifications, page 319

Configuration Changes, page 319

FRU Status Changes, page 320

cefcModuleEntry.entPhysicalIndex

cefcModuleEntry.24 cefcModuleAdminStatus = enabled(1) cefcModuleOperStatus = ok(2) cefcModuleResetReason = manual reset(5) cefcModuleStatusLastChangeTime = 7714


319

Identifying Hosts to Receive Notifications

You can use the CLI or SNMP to identify hosts to receive SNMP notifications and to specify the types of notifications they are to receive (notifications). For CLI instructions, see the “Enabling Notifications”. To use SNMP to configure this information: Use SNMP-NOTIFICATION-MIB objects, including the following, to select target hosts and specify the types of notifications to generate for those hosts:

snmpNotifyTable—Contains objects to select hosts and notification types:

— snmpNotifyTag is an arbitrary octet string (a tag value) used to identify the hosts to receive SNMP

notifications. Information about target hosts is defined in the snmpTargetAddrTable (SNMP-TARGET-MIB), and each host has one or more tag values associated with it. If a host in snmpTargetAddrTable has a tag value that matches this snmpNotifyTag value, the host is selected to receive the types of notifications specified by snmpNotifyType.

— snmpNotifyType is the type of SNMP notification to send: notification(1) or inform(2).

snmpNotifyFilterProfileTable and snmpNotifyFilterTable—Use objects in these tables to create notification filters

to limit the types of notifications sent to target hosts.

Use SNMP-TARGET-MIB objects to configure information about the hosts to receive notifications:

snmpTargetAddrTable—Transport addresses of hosts to receive SNMP notifications. Each entry provides

information about a host address, including a list of tag values:

— snmpTargetAddrTagList—A set of tag values associated with the host address. If a host tag value

matches snmpNotifyTag, the host is selected to receive the types of notifications defined by snmpNotifyType.

snmpTargetParamsTable—SNMP parameters to use when generating SNMP notifications.

Use the notification enable objects in appropriate MIBs to enable and disable specific SNMP notifications.

Configuration Changes

If entity notifications are enabled, the router generates an entConfigChange notification (ENTITY-MIB) when the information in any of the following tables changes (which indicates a change to the router configuration):


320

entPhysicalTable

entAliasMappingTable

entPhysicalContainsTable

Note: A management application that tracks configuration changes checks the value of the entLastChangeTime object to detect any entConfigChange notifications that were missed as a result of throttling or transmission loss.

Enabling Notifications for Configuration Changes To configure the router to generate an entConfigChange notification each time its configuration changes, enter the snmp-sever trap entity command from the CLI. Use the no form of the command to disable the notifications.

Router (config) # snmp-server traps entity Router (config) # no snmp-server traps entity

FRU Status Changes If FRU notifications are enabled, the router generates the following notifications in response to changes in the status of a FRU: cefcModuleStatusChange—The operational status (cefcModuleOperStatus) of a FRU changes.

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

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

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

Enabling FRU Notifications To configure the router to generate notifications for FRU events, enter the snmp-server traps fru-ctrl command from the CLI. Use the no form of the command to disable the notifications.

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

To enable FRU notifications through SNMP, set cefcMIBEnableStatusNotification to true(1). Disable the notifications by setting cefcMIBEnableStatusNotification to false(2).

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

Cisco ASR 9000 Series Router QoS Basics, page 321

CISCO-CLASS-BASED-QOS-MIB Overview, page 321

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

Monitoring QoS Using the CISCO-CLASS-BASED-QOS-MIB, page 324

Considerations for Processing QoS Statistics, page 325


321

Sample QoS Applications, page 328

Cisco ASR 9000 Series Router QoS Basics The Cisco ASR 9000 Series router distributes QoS features across the line cards. Line cards are designed to provide QoS features on packets that flow through the line cards.

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

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

Match statement—Specific match criteria to identify packets for classification purposes.

Class map—A user-defined traffic class that contains 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 and distinguish among instances of those features: cbQosObjectsIndex – Identifies each QoS feature on the router.

cbQoSConfigIndex – Identifies a type of QoS configuration. This index is shared by QoS objects that have identical configurations.

cbQosPolicyIndex – Identifies a unique service policy.

QoS MIB Information Storage CISCO-CLASS-BASED-QOS-MIB information is stored as: Configuration information— Includes all the QoS configuration objects, such as class maps, policy map, match statements, and feature action configuration parameters. The configuration may have multiple identical instances. Configuration objects are identified by cbQosConfigIndex attribute. Multiple instances of the same QoS feature share a single configuration object that is identified by the same cbQosConfigIndex value. Service-policy information— Includes instances of all QoS objects, such as service-policies, classes, match statements, and feature actions. Service-policies are identified by cbQosPolicyIndex and instances of QoS objects are identified by the combination of cbQosPolicyIndex and cbQosObjectsIndex attributes.


322

QoS Hardware Configuration and Statistic Support The CISCO-CLASS-BASED-QOS-MIB does not cover all the Cisco ASR 9000 Series router QoS hardware configuration and statistics. The Cisco ASR 9000 Series router supports the concept of ‘shared policy instance’ where, based on the configuration, the resources for individual service policies are shared among multiple interfaces. The cbQosMIB attribute does not indicate whether the service-policies are shared-policy instances or non-shared policy instances. The interfaces associated with the shared policy instance have a separate entry in the cbQosServicePolicyTable. The MIB entries, associated with each interface that is a part of the same shared-policy-instance, have the same data values, for example, everything except for the cbQosServicePolicyTable is identical for the rows associated with the values of cbQosPolicyIndex for such interfaces. Figure 1-2 shows how the indexes provide access to QoS configuration information and statistics.

Figure 1-2 The Cisco ASR 9000 Series Router QoS Indexes cbQosServicePolicyTable

cbQosPolicyIndex cbQosxxxStatsTable QoS Statistics

cbQosObjectsTable cbQosObjectsIndex

. . . cbQosConfigIndex cbQosxxxCfgTable

Configuration Information

5


323

Accessing QoS Configuration Information

To access QoS configuration information and statistics for a particular QoS feature: Step 1 Look in cbQosServicePolicyTable and find the cbQosPolicyIndex assigned to the policy in which the feature is used. Step 2 Use cbQosPolicyIndex to access the cbQosObjectsTable, and find the cbQosObjectsIndex and cbQosConfigIndex assigned to the QoS feature.

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

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

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

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

Note This is only a partial display of all QoS information.

ASR 9000# getmany -v3 10.86.0.94 test-user ciscoCBQosMIB CbQosServicePolicyTable cbQosIfType.1047 = subInterface(2) cbQosIfType.1052 = subInterface(2) cbQosPolicyDirection.1047 = input(1) cbQosPolicyDirection.1052 = output(2) cbQosIfIndex.1047 = 36 cbQosIfIndex.1052 = 36 cbQosFrDLCI.1047 = 0 cbQosFrDLCI.1052 = 0 cbQosAtmVPI.1047 = 0 cbQosAtmVPI.1052 = 0 cbQosAtmVCI.1047 = 0 cbQosAtmVCI.1052 = 0 cbQosConfigIndex.1047.1047 = 1045 cbQosConfigIndex.1047.1048 = 1025 cbQosConfigIndex.1047.1050 = 1027 cbQosConfigIndex.1047.1051 = 1046 cbQosConfigIndex.1052.1052 = 1045 cbQosConfigIndex.1052.1053 = 1025 cbQosConfigIndex.1052.1055 = 1027 cbQosConfigIndex.1052.1056 = 1046 cbQosObjectsType.1047.1047 = policymap(1) cbQosObjectsType.1047.1048 = classmap(2) cbQosObjectsType.1047.1050 = matchStatement(3) cbQosObjectsType.1047.1051 = police(7)


324

cbQosObjectsType.1052.1052 = policymap(1) cbQosObjectsType.1052.1053 = classmap(2) cbQosObjectsType.1052.1055 = matchStatement(3) cbQosObjectsType.1052.1056 = police(7) cbQosParentObjectsIndex.1047.1047 = 0 cbQosParentObjectsIndex.1047.1048 = 1047 cbQosParentObjectsIndex.1047.1050 = 1048 cbQosParentObjectsIndex.1047.1051 = 1048 cbQosParentObjectsIndex.1052.1052 = 0 cbQosParentObjectsIndex.1052.1053 = 1052 cbQosParentObjectsIndex.1052.1055 = 1053 cbQosParentObjectsIndex.1052.1056 = 1053 cbQosPolicyMapName.1045 = pm-1Meg cbQosPolicyMapDesc.1045 = cbQosCMName.1025 = class-default cbQosCMDesc.1025 = cbQosCMInfo.1025 = matchAny(3)

Monitoring QoS Using the CISCO-CLASS-BASED-QOS-MIB This section describes how to monitor QoS on the router by checking the QoS statistics in the CISCO-CLASS-BASED-QOS-MIB tables. Note: The CISCO-CLASS-BASED-QOS-MIB may contain more information than what is displayed in the output of CLI show commands. Table 1-1 lists the types of QoS statistics tables.

QoS Table Statistics

cbQosCMStatsTable Class map—Counts of packets, bytes, and bit rate before andafter QoS policies are executed. Counts of dropped packets and bytes.

cbQosPoliceStatsTable Police action—Counts of packets, bytes, and bit rate thatconforms to, exceeds, and violates police actions.

cbQosQueueingStatsTable

Queueing—Counts of discarded packets and bytes, and queue depths.

Table 1-1 QoS Statistics Tables QoS Table Statistics cbQosTSStatsTable Traffic shaping—Counts of delayed and

dropped packets and bytes, the state of a feature, and queue size.

cbQosREDClassStatsTable Random early detection—Counts of packets and bytes dropped when queues are full, and counts of bytes and octets transmitted.


325

Considerations for Processing QoS Statistics The router maintains 64-bit counters for most QoS statistics. However, some QoS counters are implemented as a 32-bit counter with a 1-bit overflow flag. In the following samples, the counters are shown as 33-bit counters. When accessing QoS counter statistics, consider the following: SNMPv2c or SNMPv3 applications—Access the entire 64 bits of the QoS counter through cbQosxxx64

MIB objects.

SNMPv1 applications—Access QoS statistics in the MIB as follows:

— Access the lower 32 bits of the counter through cbQosxxx MIB objects. — Access the upper 32 bits of the counter through cbQosxxxOverflow MIB objects.

Sample QoS Statistics Tables

The samples in this section show the counters in CISCO-CLASS-BASED-QOS-MIB statistics tables: Figure 1-3 shows the counters in the cbQosCMStatsTable and the indexes for accessing these and

other statistics.

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

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

cbQosCMPrePolicyByte

cbQosCMPrePolicyByte64


326

Figure 1-3 QoS Class Map Statistics and Indexes

cbQosServicePolicyTable

cbQosPolicyIndex = 1047

. . .

cbQosObjectsTable

cbQosObjectsIndex = 1048

cbQosCMStatsTable

. . .

cbQosCMStatsEntry.cbQosPolicyIndex.cbQosObjectsIndex

cbQosCMStatsEntry.1047.1048

cbQosCMPrePolicyPkt

cbQosCMPrePolicyByte

cbQosCMPrePolicyBitRate

Use the cbQosPolicyIndex and cbQosCMPostPolicyByte

cbQosObjectsIndex of a QoS cbQosCMPostPolicyBitRate

feature to access its statistics. cbQosCMDropPkt

cbQosCMDropByte

cbQosCMDropBitRate

cbQosCMNoBufDropPkt

6974

0


327

Figure 1-4 QoS Statistics Tables

cbQosMatchStmtStatsTable cbQosMatchStmtStatsEntry.cbQosPolicyIndex

.cbQosObjectsIndex

cbQosMatchPrePolicyPkt cbQosMatchPrePolicyByte cbQosMatchPrePolicyBitRate

cbQosPoliceStatsTable cbQosPoliceStatsEntry.cbQosPolicyIndex

.cbQosObjectsIndex

cbQosPoliceConformedPkt cbQosPoliceConformedByte cbQosPoliceConformedBitRate cbQosPoliceExceededPkt cbQosPoliceExceededByte cbQosPoliceExceededBitRate cbQosPoliceViolatedPkt cbQosPoliceViolatedByte cbQosPoliceViolatedBitRate

cbQosREDClassCfgTable cbQosREDClassCfgEntry.cbQosConfigIndex

.cbQosREDValue

cbQosREDClassCfgEntry.1042.0 cbQosREDCfgMinThreshold 11 cbQosREDCfgMaxThreshold 21 cbQosREDCfgPktDropProb 9

. . . cbQosREDClassCfgEntry.1042.1



. . .

Each cbQosREDValue is an index to

the statistics for that RED class.

cbQosQueueingStatsTable cbQosQueueingStatsEntry.cbQosPolicyIndex

.cbQosObjectsIndex

cbQosQueueingCurrentQDepth cbQosQueueingMaxQDepth cbQosQueueingDiscardByte cbQosQueueingDiscardPkt

cbQosTSStatsTable cbQosTSStatsEntry.cbQosPolicyIndex

.cbQosObjectsIndex

cbQosTSStatsDelayedByte cbQosTSStatsDelayedPkt cbQosTSStatsDropByte cbQosTSStatsDropPkt cbQosTSStatsActive cbQosTSStatsCurrentSize

cbQosREDClassStatsTable cbQosREDClassStatsEntry.cbQosPolicyIndex

.cbQosObjectsIndex .cbQosREDValue

cbQosREDClassStatsEntry.1055.1062.0

cbQosREDRandomDropPkt cbQosREDRandomDropByte cbQosREDTailDropPkt cbQosREDTailDropByte cbQosTransmitPkt cbQosTransmitByte

. . .

cbQosREDClassStatsEntry.1055.1062.1 . . .



* Counts in cbQosREDClassStatsTable are

maintained per class, not cbQosREDValue. All instances of a counter that have the same cbQosREDValue also have the same count.

6974

1


328

Sample QoS Applications

This section presents examples of code showing how to retrieve information from the CISCO-CLASS-BASED-QOS-MIB to use for QoS billing operations. You can use the examples to help you develop billing applications. The topics include:

Checking Customer Interfaces for Service Policies

Retrieving QoS Billing Information


329

Checking Customer Interfaces for Service Policies This section describes a sample algorithm that checks the CISCO-CLASS-BASED-QOS-MIB for customer interfaces with service policies, and marks those interfaces for further application processing (such as billing for QoS services). The algorithm uses two SNMP get-next requests for each customer interface. For example, if the router has 2000 customer interfaces, 4000 SNMP get-next requests are required to determine if those interfaces have transmit and receive service policies associated with them. Note: This algorithm is for informational purposes only. Your application needs may be different. Check the MIB to see which interfaces are associated with a customer. Create a pair of flags to show if a service policy has been associated with the transmit and receive directions of a customer interface. Mark noncustomer interfaces TRUE (so no more processing is required for them).

FOR each ifEntry DO

IF (ifEntry represents a customer interface) THEN servicePolicyAssociated[ifIndex].transmit = FALSE; servicePolicyAssociated[ifIndex].receive = FALSE;

ELSE servicePolicyAssociated[ifIndex].transmit = TRUE; servicePolicyAssociated[ifIndex].receive = TRUE;

END-IF END-FOR

Examine the cbQosServicePolicyTable and mark each customer interface that has a service policy attached to it. Also note the direction of the interface.

x = 0; done = FALSE; WHILE (!done)

status = snmp-getnext ( ifIndex = cbQosIfIndex.x, direction = cbQosPolicyDirection.x

); IF (status != ‘noError’) THEN done =

TRUE ELSE

x = extract cbQosPolicyIndex from response; IF (direction == ‘output’) THEN

servicePolicyAssociated[ifIndex].transmit = TRUE; ELSE servicePolicyAssociated[ifIndex].receive = TRUE; END-IF

END-IF END-WHILE

Manage cases in which a customer interface does not have a service policy attached to it.

FOR each ifEntry DO

IF (!servicePolicyAssociated[ifIndex].transmit) THEN Perform processing for customer interface without a transmit service policy.

END-IF IF (!servicePolicyAssociated[ifIndex].receive) THEN

Perform processing for customer interface without a receive service policy. END-IF

END-FOR


330

Retrieving QoS Billing Information

This section describes a sample algorithm that uses the CISCO-CLASS-BASED-QOS-MIB for QoS billing operations. The algorithm periodically retrieves post-policy input and output statistics, combines them, and sends the result to a billing database. The algorithm uses the following: One SNMP get request per customer interface—To retrieve the ifAlias.

Two SNMP get-next requests per customer interface—To retrieve service policy indexes.

Two SNMP get-next requests per customer interface for each object in the policy—To retrieve post-policy bytes. For example, if there are 100 interfaces and 10 objects in the policy, the algorithm requires 2000 get-next requests (2 x 100 x 10).

Note: This algorithm is for informational purposes only. Your application needs may be different.

Set up customer billing information.

FOR each ifEntry DO

IF (ifEntry represents a customer interface) THEN status = snmp-getnext (id = ifAlias.ifIndex); IF (status != ‘noError’) THEN

Perform error processing. ELSE

billing[ifIndex].isCustomerInterface = TRUE; billing[ifIndex].customerID = id; billing[ifIndex].transmit = 0; billing[ifIndex].receive = 0;

END-IF ELSE

billing[ifIndex].isCustomerInterface = FALSE; END-IF END-FOR

Retrieve billing information.

x = 0; done = FALSE; WHILE (!done)

response = snmp-getnext ( ifIndex = cbQosIfIndex.x, direction = cbQosPolicyDirection.x

); IF (response.status != ‘noError’) THEN done =

TRUE ELSE

x = extract cbQosPolicyIndex from response; IF (direction == ‘output’) THEN

billing[ifIndex].transmit = GetPostPolicyBytes (x); ELSE billing[ifIndex].receive = GetPostPolicyBytes (x); END-IF

END-IF END-WHILE


331

Determine the number of post-policy bytes for billing purposes. GetPostPolicyBytes (policy) x =

policy; y = 0; total = 0; WHILE (x == policy)

response = snmp-getnext (type = cbQosObjectsType.x.y); IF (response.status == ‘noError’)

x = extract cbQosPolicyIndex from response; y = extract cbQosObjectsIndex from response; IF (x == policy AND type == ‘classmap’)

status = snmp-get (bytes = cbQosCMPostPolicyByte64.x.y); IF (status == ‘noError’)

total += bytes; END-IF

END-IF END-IF

END-WHILE RETURN total;

Monitoring Router Interfaces

This section provides information about how to monitor the status of router interfaces to see if there is a problem or a condition that might affect service on the interface. To determine if an interface is down or experiencing problems, you can:

Check the Operational and Administrative Status of Interface

Monitor linkDown and linkUp Notifications

Check the Operational and Administrative Status of Interface

To check the status of an interface, view the following IF-MIB objects for the interface:

ifAdminStatus—The administratively configured (desired) state of an interface. Use ifAdminStatus to enable or disable the interface.

ifOperStatus—The current operational state of an interface.

Monitor linkDown and linkUp Notifications

To determine if an interface has failed, you can monitor linkDown and linkUp notifications for the interface. See the “Enabling Interface linkUp and linkDown Notifications” section on page 332 for instructions on how to enable the following notifications: linkDown—Indicates that an interface failed or is about to fail.

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


332

Enabling Interface linkUp and linkDown Notifications To configure SNMP to send a notification when a router interface changes state to up (ready) or down (not ready), perform the following steps to enable linkUp and linkDown notifications:

Step 1 Issue the following CLI command to enable linkUp and linkDown notifications for most, but not necessarily

all, interfaces:

Router(config)# snmp-server interface <Interface Type> <Interface Number> notification linkupdown Step 2 View the setting of the ifLinkUpDownTrapEnable object (IF-MIB ifXTable) for each interface to determine if

linkUp and linkDown notifications are enabled or disabled for that interface. Step 3 To enable linkUp and linkDown notifications on an interface, set ifLinkUpDownTrapEnable to enabled (1). Step 4 To enable the Internet Engineering Task Force (IETF) standard for linkUp and linkDown notifications, issue

the snmp-server trap link ietf command. (The IETF standard is based on RFC 2233.)

Router (config) # snmp-server trap link ietf Step 5 To disable notifications, use the no form of the snmp-server command.

Billing Customers for Traffic

This section describes how to use SNMP interface counters and QoS data information to determine the amount to bill customers for traffic. It also includes a scenario for demonstrating that a QoS service policy attached to an interface is policing traffic on that interface. This section contains the following topics: Input and Output Interface Counts, page 332

Determining the Amount of Traffic to Bill to a Customer, page

Scenario for Demonstrating QoS Traffic Policing, page

Input and Output Interface Counts The router maintains information about the number of packets and bytes that are received on an input interface and transmitted on an output interface. For detailed constraints about IF-MIB counter support, see the “IF-MIB (RFC 2863)” section on page 3-176. Consider the following important information about IF-MIB counter support: Unless noted, all IF-MIB counters are supported on the Cisco ASR 9000 Series router interfaces.

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

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


333

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

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

When a QoS service policy is attached to an interface, the router applies the rules of the policy to traffic on the

interface and increments the packet and byte counts on the interface.

The following CISCO-CLASS-BASED-QOS-MIB objects provide interface counts: cbQosCMDropPkt and cbQosCMDropByte (cbQosCMStatsTable)—Total number of packets and bytes that were

dropped as they exceeded the limits set by the service policy. These counts include only those packets and bytes that were dropped as they exceeded service policy limits. The counts do not include packets and bytes dropped for other reasons.

cbQosPoliceConformedPkt and cbQosPoliceConformedByte (cbQosPoliceStatsTable)—Total number of packets and bytes that conformed to the limits of the service policy and were transmitted.

Determining the Amount of Traffic to Bill to a Customer

Perform the following steps to determine how much traffic on an interface is billable to a particular customer: Step 1 Determine which service policy on the interface applies to the customer. Step 2 Determine the index values of the service policy and class map used to define the customer’s traffic.

You need this information in the following steps. Step 3 Access the cbQosPoliceConformedPkt object (cbQosPoliceStatsTable) for the customer to determine

the amount of traffic on the interface that is billable to this customer. Step 4 (Optional) Access the cbQosCMDropPkt object (cbQosCMStatsTable) for the customer to

determine how much of the customer’s traffic was dropped as it exceeded service policy limits.

Scenario for Demonstrating QoS Traffic Policing This section describes a scenario that demonstrates the use of SNMP QoS statistics to determine how much traffic on an interface is billable to a particular customer. It also shows how packet counts are affected when a service policy is applied to traffic on the interface. To create the scenario, perform the following steps (each step described in the section below):

1. Create and attach a service policy to an interface.

2. View packet counts before the service policy is applied to traffic on the interface.

3. Issue a ping command to generate traffic on the interface. Note that the service policy is applied to the traffic.

4. View packet counts after the service policy is applied to determine how much traffic to bill the customer for:

Conformed packets—The number of packets within the range set by the service policy and for which you can charge

the customer.


334

Exceeded or dropped packets—The number of packets that were not transmitted because they were outside the range of the service policy. These packets are not billable to the customer.

Note: In this scenario, the Cisco ASR 9000 Series router is used as an interim device (that is, traffic originates elsewhere and is destined for another device).


335

Service Policy Configuration

The following example uses policy map configuration. policy-map police-out class BGPclass

police 8000 1000 2000 conform-action transmit exceed-action drop

interface GigabitEthernet0/1/0/0.10 description VLAN voor klant encapsulation dot1Q 10

ip address 10.0.0.17 255.255.255.248 service-policy output police-out

Packet Counts Before the Service Policy Is Applied

The following CLI and SNMP output shows the output traffic for interface before the service policy is applied: CLI Command Output RSP/0/RSP0/CPU0:ios-xr#show policy-map interface GigabitEthernet0/7/0/0.1 GigabitEthernet0/7/0/0.1 input: policy-police Class class-out Classification statistics (packets/bytes) (rate - kbps) Matched : 0/0 0 Transmitted : Un-determined Total Dropped : Un-determined Policing statistics (packets/bytes) (rate - kbps) Policed(conform) : 0/0 0 Policed(exceed) : 0/0 0 Policed(violate) : 0/0 0 Policed and dropped : 0/0 Class class-default Classification statistics (packets/bytes) (rate - kbps) Matched : 0/0 0 Transmitted : Un-determined Total Dropped : Un-determined

SNMP Output ASR 9000# getone -v2c 10.86.0.63 public ifDescr.65 ifDescr.65 = GigabitEthernet0/6/0/0.10

Generating Traffic

The following set of ping commands generates traffic: ASR 9000#ping Protocol [ip]:

Target IP address: 10.0.0.18 Repeat count [5]: 99 Datagram size [100]: 1400


336

Timeout in seconds [2]: 1 Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 100, 1400-byte ICMP Echos to 10.0.0.18, timeout is 1 seconds: ..!!..!..!..!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.!.!..!.!..!.!..!.!.!.. !.!..!.!..!.!.!..!.!..!.!..!.! Success rate is 42 percent (42/100), round-trip min/avg/max = 1/1/1 ms

Packet Counts After the Service Policy Is Applied

After you generate traffic using the ping command, look at the number of packets that exceeded and conformed to the committed access rate (CAR) set by the police command:

42 packets conformed to the police rate and were transmitted

57 packets exceeded the police rate and were dropped

The following CLI and SNMP output show the counts on the interface after the service policy is applied. (In the output, conformed and exceeded packet counts are shown in boldface.) CLI Command Output

ASR 9000# show policy-map interface g6/0/0.10

GigabitEthernet6/0/0.10 Service-policy output: police-out Class-map: BGPclass (match-all) 198 packets, 281556 bytes 30 second offered rate 31000 bps, drop rate 11000 bps Match: access-group 101 Police: 8000 bps, 1000 limit, 2000 extended limit conformed 42 packets, 59892 bytes; action: transmit exceeded 57 packets, 81282 bytes; action: drop Class-map: class-default (match-any) 15 packets, 1086 bytes 30 second offered rate 0 bps, drop rate 0 bps Match: any Output queue: 0/8192; 48/59940 packets/bytes output, 0 drops

SNMP Output ASR 9000# getmany -v2c 10.86.0.63 public ciscoCBQosMIB . . . cbQosCMDropPkt.1143.1145 = 57 . . . cbQosPoliceConformedPkt.1143.1151 = 42 . . .


337

Using IF-MIB Counters

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

The IF-MIB counters are defined with respect to lower and upper layers: ifInDiscards—The number of inbound packets that were discarded, even though no errors were detected to prevent

their being deliverable to a higher-layer protocol. One reason for discarding such a packet is to free up buffer space.

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

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

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

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

The logical flow for counters works as follows:

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

a. Error in packet—If any errors are detected, increment ifInErrors and drop the packet. b. Protocol errors—If any errors are detected, increment ifInUnknownProtos and drop the packet. c. Resources (buffers)—If unable to get resources, increment ifInDiscards and drop the packet. d. Increment ifInUcastPkts/ifInNUcastPkts and process the packet (at this point, increment ifInOctets with the

size of packet).

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

a. Increment ifOutUcastPkts/ifOutNUcastPkts (increment ifOutOctets with the size of packet). b. Check for errors in packet and if there are any errors in packet, increment ifOutErrors and drop the packet. c. Check for resources (buffers) and if you cannot get resources, then increment ifOutDiscards and drop the

packet.


338

This following output is an example of IF-MIB entries: IfXEntry ::=

SEQUENCE {

ifName DisplayString,

ifInMulticastPkts Counter32,

ifInBroadcastPkts Counter32,

ifOutMulticastPkts Counter32,

ifOutBroadcastPkts Counter32,

ifHCInOctets Counter64,

ifHCInUcastPkts Counter64,

ifHCInMulticastPkts Counter64,

ifHCInBroadcastPkts Counter64,

ifHCOutOctets Counter64,

ifHCOutUcastPkts Counter64,

ifHCOutMulticastPkts Counter64,

ifHCOutBroadcastPkts Counter64,

ifLinkUpDownTrapEnable INTEGER, ifHighSpeed Gauge32, ifPromiscuousMode TruthValue, ifAlias DisplayString, ifCounterDiscontinuityTime TimeStamp


339

Sample Counters

The high capacity counters are 64-bit versions of the basic ifTable counters. They have the same basic semantics as their 32-bit counterparts; their syntax is extended to 64 bits. Table 1-2 lists capacity counters object identifiers (OIDs).

Name Object Identifier (OID)

ifHCInOctets ::= { ifXEntry 6 }

ifHCInUcastPkts ::= { ifXEntry 7 }

ifHCInMulticastPkts ::= { ifXEntry 8 }

ifHCInBroadcastPkts ::= { ifXEntry 9 }

ifHCOutOctets ::= { ifXEntry 10 }

ifHCOutUcastPkts ::= { ifXEntry 11 }

ifHCOutMulticastPkts ::= { ifXEntry 12 }

ifHCOutBroadcastPkts ::= { ifXEntry 13 }

ifLinkUpDownTrapEnable ::= { ifXEntry 14 }

ifHighSpeed ::= { ifXEntry 15 }

ifPromiscuousMode ::= { ifXEntry 16 }

ifAlias ::= { ifXEntry 18 }

ifCounterDiscontinuityTime ::= { ifXEntry 19 }

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Appendix 2 - QoS MIB Implementation

340

Appendix 2 - QoS MIB Implementation

This appendix provides information about QoS-based features that are implemented on the Cisco ASR 9000 Series router line cards and what tables and objects in the QoS MIB support these QoS features. The Cisco ASR 9000 Series router line card families each have a different QoS implementation. Do not assume that the QoS features across line card families are equivalent. Some of the QOS configuration is done at the PFC2 (policy feature card) level and others at the parallel express forwarding (PXF) processor level in each line card. This appendix contain the following topics: Implementing the CISCO-CLASS-BASED-QOS-MIB, page 340

QoS MIB Policy Action Support Matrix, page 345

Implementing the CISCO-CLASS-BASED-QOS-MIB

This section describes which objects from the CISCO-CLASS-BASED-QOS-MIB are implemented, which objects are relevant to the features available for the Cisco ASR 9000 Series router line cards, and which QoS features are supported by each Cisco ASR 9000 Series router line card.


341

Table 2-1 defines the expected values for Policy Actions. Policy Action Definition Notes

Bandwidth A rate limiting function. The difference between the highest and lowest frequencies available for network signals. Bandwidth divides the link bandwidth among different traffic streams into multiple queues.

Must be set before you enable WRED. Aggregate bandwidth rate limits match all of the packets on an interface or subinterface. Granular bandwidth rate limits match a particular type of traffic based on precedence, MAC address, or other parameters.

Priority Priority queuing allows you to assign a

guaranteed minimum bandwidth to one queue to minimize the packet delay variance for delay-sensitive traffic.

A routing feature in which frames in an output queue are prioritized based on various characteristics, such as packet size and interface type.

Shape A shaper typically delays excess

traffic using a buffer or queueing mechanism to hold packets and shape the flow when the data rate of the source is higher than expected. (For example, Generic traffic Shaping (GTS) uses a weighted fair queue to delay packets to shape the flow, and Frame Relay Traffic Shaping (FRTS) uses either a priority queue (PQ), a custom queue (CQ), or a first-in, first-out (FIFO) queue for the same, depending on how you configure it.)

Shapers identify traffic descriptor violations.

Police A policer typically drops traffic. (For

example, Committed Access Rate (CAR) rate-limiting policer either drops the packet or rewrites its IP precedence, resetting the packet header type of service bits.)

Policing is the process by which the OSR limits the bandwidth consumed by a flow of traffic. Policing can mark or drop traffic.


342


343

Table 2-1 QoS Policy Action Parameters (continued)

Policy Action Definition Notes

Queue limit

Parameter specifies the number of packets held by the queue. It operates on the default packet drop method of congestion management.

A Cisco queuing technique. A flow-based queuing algorithm that creates bit-wise fairness by allowing each queue to be serviced fairly in terms of byte count. For example, if queue 1 has 100-byte packets and queue 2 has 50-byte packets, the Weighted Fair Queuing (WFQ) algorithm takes two packets from queue 2 for each one packet from queue 1. This makes service fair for each queue: 100 bytes each time the queue is serviced. WFQ ensures that queues do not starve for bandwidth and that traffic gets predictable service. Low-volume traffic streams–which comprise the majority of traffic–receive increased service, transmitting the same number of bytes as high-volume streams. This behavior results in what appears to be preferential treatment for low-volume traffic, when in actuality it is creating fairness.

Fair queue Traffic shaping smooths traffic by storing traffic above the configured rate in a queue. When a packet arrives at the interface for transmission, the following happens: If the queue is empty, the arriving packet is processed by the traffic shaper. If possible, the traffic shaper sends the packet. Otherwise, the packet is placed in the queue. If the queue is not empty, the packet is placed in the queue.

A Cisco queuing technique. A flow-based queuing algorithm that creates bit-wise fairness by allowing each queue to be serviced fairly in terms of byte count. For example, if queue 1 has 100-byte packets and queue 2 has 50-byte packets, the WFQ algorithm takes two packets from queue 2 for each one packet from queue 1. This makes service fair for each queue: 100 bytes each time the queue is serviced.

When there are packets in the queue, the traffic shaper removes the number of packets it can transmit from the queue at each time interval.


344


345

Table 2-1 QoS Policy Action Parameters (continued) Policy Action Definition Notes

Weighted Random Early Detection (WRED)

Action that randomly discards packetsduring IP precedence settings congestion.

Precedence is a value of 0 to 7 where zero is low priority traffic and 7 represents high priority traffic.

Set (precedence)

The IP precedence (QoS) bits in thepacket header are rewritten. The packet is then transmitted. You can use this action to either color (set precedence) or recolor (modify existing packet precedence) the packet.

—

Notes About QoS: Congestion-management tools include priority queuing (PQ), custom queuing (CQ), weighted fair queuing (WFQ),

and class-based weighted fair queuing (CBWFQ).

Police and shape are traffic regulation mechanisms:

— Shaping is used to create a traffic flow that limits the full bandwidth potential of the flows. This is used

many times to prevent the overflow problem. For instance, many network topologies use Frame Relay in a hub-and-spoke design. In this case, the central site normally has a high-bandwidth link (such as T1), while remote sites have a low-bandwidth link in comparison (such as 384 Kbps). In this case, it is possible for traffic from the central site to overflow the low bandwidth link at the other end. Shaping is a good way to pace traffic closer to 384 Kbps to avoid the overflow of the remote link. Traffic above the configured rate is buffered for transmission later to maintain the rate configured.

— Policing is similar to shaping, but it differs in one important way; traffic that exceeds the configured rate is not buffered (and normally is discarded).

QoS MIB Policy Action Support Matrix

The tables in this section describe which objects from the CISCO-CLASS-BASED-QOS-MIB are implemented and which ones are relevant to the different features available for the Cisco ASR 9000 Series router line cards. The tables are divided into objects on the Cisco ASR 9000 Series router platform that are:

Supported, implemented, and instrumented (works as defined in the MIB)— Table 2-3

Not supported or support is limited— Table 2-4


346


347

Table 2-2 lists the definitions of the values that are returned by objects listed in Table 2-3 and Table 2-4. Policy actions are dependent on return values.

Table 2-2 QoS Table Return Values

Identifier Definition

Value is V. Returns valid data

Value is I. The object is not supported by this platform.

Returns invalid data

Value is a dash (–). Not instantiated (Does not instantiate [return] any value for this object.)

Table 2-3 lists QoS MIB table objects that are supported and implemented on the Cisco ASR 9000 Series router platform and the QoS policy actions that these objects support.

Policy Actions

MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Noteswidth Limit Queue

cbQosCMStatsTable cbQosCMPrePolicyPkt Overflow

V V V V V V V V The objects listedwith a value of V are supported and return valid data.

cbQosCMPrePolicyPkt V V V V V V V V

cbQosCMPrePolicyPkt64 V V V V V V V V

cbQosCMPrePolicyByte Overflow

V V V V V V V V

cbQosCMPrePolicyByte V V V V V V V V

cbQosCMPrePolicyByte64 V V V V V V V V

cbQosCMPrePolicyBitRate V V V V V V V V

cbQosCMPostPolicyByte Overflow

V V V V V V V V

cbQosCMPostPolicyByte V V V V V V V V

cbQosCMPostPolicy Byte64 V V V V V V V V

cbQosCMPostPolicyBit Rate V V V V V V V V

cbQosCMDropPkt Overflow V V V V V V V V

cbQosCMDropPkt V V V V V V V V

cbQosCMDropPkt64 V V V V V V V V

cbQosCMDropByte Overflow V V V V V V V V


348

Table 2-3 Supported QoS MIB Objects (continued)

MIB Tables and Objects Band- width

Priority Shape Police Queue Limit

Fair Queue

WRED Set Notes

cbQosCMDropByte V V V V V V V V cbQosCMDropByte64 V V V V V V V V cbQosCMDropBitRate V V V V V V V V cbQosMatchStmtStatsTable

cbQosMatchPrePolicyPkt Overflow

I I I V I I I I The objects listed with a value of I (invalid) are supported but return invalid data for all actions except for Police action (the return data is valid).

cbQosMatchPrePolicyPkt I I I V I I I I cbQosMatchPrePolicy Pkt64

I I I V I I I I

cbQosMatchPrePolicyByte Overflow

I I I V I I I I

cbQosMatchPrePolicyByte I I I V I I I I cbQosMatchPrePolicyBit Rate

I I I V I I I I

cbQosMatchPrePolicy Byte64

I I I V I I I I

cbQosPoliceStatsTable cbQosPoliceConformed PktOverflow

– – – V – – – – The objects listed are supported but only return V data for Police action.

cbQosPoliceConformedPkt – – – V – – – – cbQosPoliceConformed Pkt64

– – – V – – – – The objects listed are supported but only return V data for Police action.

cbQosPoliceConformed ByteOverflow

– – – V – – – –

cbQosPoliceConformed Byte

– – – V – – – –

cbQosPoliceConformed Byte64

– – – V – – – –

cbQosPoliceConformed BitRate

– – – V – – – –


349


Policy Actions MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Notes

width Limit Queue

cbQosPoliceExceededPkt Overflow

– – – V – – – –

cbQosPoliceExceededPkt – – – V – – – –

cbQosPoliceExceeded Pkt64

– – – V – – – –

cbQosPoliceExceeded ByteOverflow

– – – V – – – –

cbQosPoliceExceededByte – – – V – – – –

cbQosPoliceExceeded Byte64

– – – V – – – –

cbQosPoliceExceeded BitRate

– – – V – – – –

cbQosQueueingStatsTable

cbQosQueueingCurrent QDepth

V V – – V V – – The objects listed are supported but return valid data only for Bandwidth, Priority, Queue Limit, and Fair Queue.

cbQosQueueingMax QDepth

V V – – V V – –

cbQosQueueingDiscard ByteOverflow

V V – – V V – –

cbQosQueueingDiscard Byte

V V – – V V – –

cbQosQueueingDiscard Byte64

V V – – V V – –

cbQosQueueingDiscard PktOverflow

V V – – V V – –

cbQosQueueingDiscardPkt V V – – V V – –

cbQosQueueingDiscard Pkt64

V V – – V V – –

cbQosTSStatsTable The objects listed are supported but only V data for only Shape, Queue Limit, Fair Queue, and WRED.

cbQosTSStatsDropByte Overflow

– – V – V V V –


350

Table 2-3 Supported QoS MIB Objects (continued) Policy Actions

MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Notes width Limit Queue cbQosTSStatsDropByte – – V – V V V –

cbQosTSStatsDropByte64 – – V – V V V –

cbQosTSStatsDropPkt Overflow

– – V – V V V –

cbQosTSStatsDropPkt – – V – V V V –

cbQosTSStatsDropPkt64 – – V – V V V –

cbQosTSStatsCurrentQSize – – V – V V V –

cbQosREDClassStatsTable Not instantiated forShape even though the CLI shows values for random and tail counters.

cbQosREDRandomDrop PktOverflow

– – – – – – V – The objects aresupported but only V data for WRED action only.

cbQosREDRandomDropPkt – – – – – – V –

cbQosREDRandomDrop – – – – – – V – Pkt64

cbQosREDRandom – – – – – – V – DropByteOverflow

cbQosREDRandomDrop – – – – – – V – Byte

cbQosREDRandomDrop – – – – – – V – Byte64

cbQosREDTailDropPkt – – – – – – V – Overflow

cbQosREDTailDropPkt – – – – – – V – The objects are supported but only V data for WRED action only.

cbQosREDTailDropPkt64 – – – – – – V –

cbQosREDTailDropByte – – – – – – V – Overflow

cbQosREDTailDropByte – – – – – – V –


351


MIB Tables and Objects Band- width Priority Shape Police

Queue Limit

Fair Queue

WRED Set

cbQosREDTailDrop – – – – – – V –

Byte64

V –

cbQosREDTransmitPkt – – – – – –

Overflow

V –

cbQosREDTransmitPkt – – – – – – V –

cbQosREDTransmitPkt64 – – – – – – V –

cbQosREDTransmitByte – – – – – – V –

Overflow

cbQosREDTransmitByte – – – – – – V –

cbQosREDTransmitByte64 – – – – – – V –


352

Table 2-4 lists QoS MIB table objects that are unsupported or have limited support on the Cisco ASR 9000 Series router platform and the QoS policy actions that these objects support.

Policy Actions

MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Notes width Limit Queue

cbQosCMStatsTable The objects listed are not supported, but return valid data which is always zero (0).

cbQosCMNoBufDropPkt V V V V V V V V Overflow

cbQosCMNoBufDropPkt V V V V V V V V

cbQosCMNoBufDrop V V V V V V V V Pkt64

cbQosPoliceStatsTable The objects listed are not supported, but return valid data for Police action which is always zero (0).

cbQosPoliceViolatedPkt – – – V – – – – Overflow

cbQosPoliceViolatedPkt – – – V – – – –

cbQosPoliceViolatedPkt64 – – – V – – – –

cbQosPoliceViolated – – – V – – – – ByteOverflow

cbQosPoliceViolatedByte – – – V – – – –

cbQosPoliceViolated – – – V – – – – Byte64

cbQosPoliceViolated – – – V – – – – BitRate

cbQosTSStatsTable The objects listed are not supported but do return valid data which is always zero (0) for Shape, Queue Limit, Fair Queue, and WRED.


353

Table 2-4 QoS MIB Objects—Unsupported or Limited Support (continued)

MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Notes width Limit Queue cbQosTSStatsDelayed – – V V V V – ByteOverflow

cbQosTSStatsDelayedByte – – V V V V –

cbQosTSStatsDelayed – – V V V V – Byte64 cbQosTSStatsDelayed PktOverflow

– – V V V V –

cbQosTSStatsDelayed – – V V V V –

cbQosTSStatsDelayedPkt – – V V V V –

cbQosTSStatsDelayed – – V V V V –


354

Table 2-4 QoS MIB Objects—Unsupported or Limited Support (continued) MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Notes width Limit Queue

cbQosTSStatsActive – – I I I I – This object is not

supported and

returns invalid data

which is always zero

(0) for a truthValue

type.not supported.

cbQosREDECNMarkPkt – – – – – – – – Overflow

cbQosREDECNMarkPkt – – – – – – – –

cbQosREDECNMarkPkt64 – – – – – – – –

cbQosREDECNMarkByte – – – – – – – – Overflow

cbQosREDECNMarkByte – – – – – – – –

cbQosREDECNMarkByte64 – – – – – – – –

cbQosREDMeanQSizeUnits – – – – – – – –

cbQosREDMeanQSize – – – – – – – –

cbQosSetStatsTable

cbQosSetDscpPkt64 – – – – – – – –

cbQosSetPrecedencePkt64 – – – – – – – –

cbQosSetQosGroupPkt64 – – – – – – – –

cbQosSetFrDePkt64 – – – – – – – –

cbQosSetAtmClpPkt64 – – – – – – – –

cbQosSetL2CosPkt64 – – – – – – – –

cbQosSetMplsExpImposition – – – – – – – – Pkt64

cbQosSetDiscardClassPkt64 – – – – – – – –

cbQosSetMplsExpTopMost – – – – – – – – Pkt64

cbQosSetSrpPriorityPkt64 – – – – – – – –


355

Table 2-4 QoS MIB Objects—Unsupported or Limited Support (continued)

Policy Actions

MIB Tables and Objects Band- Priority Shape Police Queue Fair WRED Set Noteswidth Limit Queue

cbQosSetFrFecnBecnPkt64 – – – – – – – –

cbQosSetDscpTunnelPkt64 – – – – – – – –

cbQosSetPrecedenceTunnel – – – – – – – – Pkt64

cbQosPoliceColorStatsTable The objects listed with a dash (-) are not supported.

cbQosPoliceCfmColorCfm – – – – – – – – Pkt64

cbQosPoliceCfmColorCfm – – – – – – – – Byte64

cbQosPoliceCfmColorExd – – – – – – – – Pkt64

cbQosPoliceCfmColorExd – – – – – – – – Byte64

cbQosPoliceCfmColorVlt – – – – – – – – Pkt64

cbQosPoliceCfmColorVlt – – – – – – – – Byte64

cbQosPoliceExdColorExdPkt64 – – – – – – – –

cbQosPoliceExdColorExd – – – – – – – – Byte64

cbQosPoliceExdColorVltPkt64 – – – – – – – –

cbQosPoliceExdColorVlt – – – – – – – – Byte64

cbQosPoliceVltColorVltPkt64 – – – – – – – –

cbQosPoliceVltColorVlt – – – – – – – – Byte64

Cisco ASR 9000 Series Aggregation Services Routers MIB Specifications Guide Glossary

356

Glossary B bandwidth

The difference between the highest and lowest frequencies available for network signals. The term is also used to describe the rated throughput capacity of a given network medium or protocol.

broadcast storm

Undesirable network event in which many broadcasts are sent simultaneously across all network segments. A broadcast storm uses substantial network bandwidth and, typically, causes network time-outs

C CANA

Cisco Assigned Numbers Authority. The central clearing house for allocation of unique names and numbers that are embedded in Cisco software.

CLI command-line interfaceCNEM Consistent Network Element Manageabilitycolumnar object

One type of managed object that defines a MIB table that contains no rows or more than one row, and each row can contain one or more scalar objects (for example, ifTable in the IF-MIB defines the interface).

community name

Defines an access environment for a group of NMSs. NMSs within the community are said to exist within the same administrative domain. Community names serve as a weak form of authentication because devices that do not know the proper community name are precluded from SNMP operations.

critical alarm severity type

Indicates a severe, service-affecting condition has occurred and that immediate corrective action is imperative, regardless of the time of day or day of the week. For example, online insertion and removal of line cards or loss of signal failure when a physical port link is down.

CWDM Coarse Wavelength Division MultiplexingD dBm

Decibel (milliwatts). 10 * log10 (power in milliwatts). For example, 2 milliwatts is 10 * log10 (2) = 10 * 0.3010 = 3.01 dBm

DF Delay Factor. The maximum observed value of the flow rate imbalance over a measurement interval.

DOM Digital Optical Monitoringdisplay string

A printable ASCII string. It is typically a name or description. For example, the variable netConfigName provides the name of the network configuration file for a device.

E EHSA Enhanced High System AvailabilityEMS Element Management System. An EMS manages a specific portion of the network. For example the

SunNet Manager, an SNMP management application, is used to manage SNMP manageable elements. Element Managers may manage asynchronous lines, multiplexers, PABXs, proprietary systems, or an application.

encapsulation

The wrapping of data in a particular protocol header. For example, Ethernet data is wrapped in a specific Ethernet header before network transit. Also, when bridging dissimilar networks, the entire frame from one network is simply placed in the header used by the data link layer protocol of the other network.


357

Expected Packets This value is formally defined as the extended last sequence number received less the initial sequence

number received. An extended last sequence number is a 32‐bit value, where the most significant 16‐

bit word indicates the number of sequence number cycles, and the least significant 16‐bit word

indicates the highest sequence number received. F FRU

field-replaceable unit. Term applied to the Cisco 6400 components that can be replaced in the field, including the NLC, NSP, NRP, and PEM units, and the blower fans.

Flow Metric A measurement that reflects the quality of a traffic flow.Flow Monitor A hardware or software entity that classifies traffic flows, collects flow data, and periodically

computes flow metrics forwarding Process of sending a frame toward its ultimate destination by way of an internetworking device.frame Logical grouping of information sent as a data link layer unit over a transmission medium. Often

refers to the header and trailer, used for synchronization and error control that surround the user data contained in the unit. The terms cell, datagram, message, packet, and segment are also used to describe logical information groupings at various layers of the OSI reference model and in various technology circles.

H HSRP Hot Standby Routing Protocol. Protocol used among a group of routers for selecting an active

router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met.)

I IEEE 802.2 IEEE LAN protocol that specifies an implementation of the LLC sublayer of the data link layer. IEEE

802.2 handles errors, framing, flow control, and the network layer (Layer 3) service interface. Used in IEEE 802.3 and IEEE 802.5 LANs.

IEEE 802.3 IEEE LAN protocol that specifies an implementation of the physical layer and the MAC sublayer of the data link layer. IEEE 802.3 uses CSMA/CD access at a variety of speeds over a variety of physical media. Extensions to the IEEE 802.3 standard specify implementations for Fast Ethernet.

IEEE 802.5 IEEE LAN protocol that specifies an implementation of the physical layer and the MAC sublayer of the data link layer. IEEE 802.5 uses token passing access at 4 or 16 Mbps over STP cabling and is similar to IBM Token Ring.

IETF The Internet Engineering Task ForceifIndex Each row of the interfaces table has an associated number, called an ifIndex. You use the ifIndex

number to get a specific instance of an interfaces group object. For example, ifInNUcastPkts.1 would find you the number of broadcast packets received on interface number one. You can then find the description of interface number one by looking at the object that holds the interface description (from MIB-II) ifDescr.

info Notification about a condition that could lead to an impending problem or notification of an event that improves operation.

integer A numeric value that can be an actual number. For example, the number of lost IP packets on an interface. It also can be a number that represents a nonnumeric value. For example, the variable tsLineType returns the type of terminal services line to the SNMP manager.


358

interface counters

Interface management over SNMP is based on two tables: ifTable and its extension, ifXTable, described in RFC 1213 and RFC 2233. Interfaces can have several layers, depending on the media, and each sublayer is represented by a separate row in the table. The relationship between the higher layer and lower layers is described in the ifStackTable.

internetwork Collection of networks interconnected by routers and other devices that functions as a single network Sometimes called an internet, which is not to be confused with the Internet.

interoperability Ability of computing equipment manufactured by different vendors to communicate with one another successfully over a network.

Inter-Arrival Jitter

An estimate of the statistical variance of the RTP data packet inter-arrival time. The inter-arrival jitter, J, is formally defined to be the mean deviation (smoothed absolute value) of the difference, D, in packet spacing at the flow monitor compared to the sender for a pair of packets. This is equivalent to the difference in the relative transit time for two packets; the relative transit time is the difference between a packet’s RTP timestamp and the device’s clock at the time of arrival (measured in the same units): D(i,j) = (Rj - Ri) - (Sj - Si) = (Rj - Sj) - (Ri - Si) where Si is the RTP timestamp from packet i, and Ri is the time of arrival in RTP timestamp units for packet i. The inter-arrival jitter SHOULD be calculated continuously for each RTP data packet received from source SSRCn, using this equation to compute difference for each packet and the previous packet (in order of arrival, not necessarily in sequence). |D(i-1,i)| - J(i-1) J(i) = J(i-1) + ------------------- 16

IP Address The variable hostConfigAddr indicates the IP address of the host that provided the host configuration file for a device.

K keepalive message

Message sent by one network device to inform another network device that the virtual circuit between the two is still active.

L label A short, fixed-length identifier that is used to determine the forwarding of a packet.LDP Label Distribution ProtocolLoss Distance The difference between the sequence numbers delimiting the start of two consecutive loss

intervals. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 Loss Interval | Loss Distance ===============+=============== 1 | 2 | 7 3 | 8 4 | 8 5 | 4 6 | 5

Loss Fraction The fraction of RTP data packets from source SSRCn lost during a measurement interval, expressed as a fixed-point number: Li Fi = ---- Ei where Fi is the loss fraction for measurement interval i, Li is the lost packets during measurement interval i, and Ei is the expected packets during measurement interval i. Observe that the number of packets lost includes packets that are late or duplicates, and hence this number can can have a theoretical theoretical value between negative infinity and one. The cumulative loss fraction is the fraction of RTP data packets from source SSRCn lost over the duration monitoring the flow: n sum [Li] i=1 Fn = ---------- n sum [Ei] i=1 where Fn is the cumulative loss fraction over n measurement intervals.

Loss Interval An interval in which consecutive packet losses were experienced. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 LI1 through LI6 indicates the start of loss intervals observed in this sequence.


359

Loss Interval Duration

The number of packets lost in a loss interval. Consider the following sequence of RTP data packets: 111111 111222 2233 33333 444 444 5 123456x890123xxxx8901xxx56789x123xx678x0 ^ ^ ^ ^ ^ ^ | | | | | | LI1 LI2 LI3 LI4 LI5 LI6 Loss Interval | Duration ===============+========== 1 | 1 2 | 4 3 | 3 4 | 1 5 | 2 6 | 1

Lost Packets This value is formally defined as the number of packets expected less the number of packets actually received, where the number of packets received includes those which are late or duplicates

LR Long Reach LSR Label Switching Router. A device that forwards MPLS packets based on the value of a fixed-length

label encapsulated in each packet. LSP Label Switched Path LX/LH Long wavelength/long haulM major alarm severity type

Used for hardware or software conditions. Indicates a serious disruption of service or the malfunctioning or failure of important hardware. Requires immediate attention and response of a technician to restore or maintain system stability. The urgency is less than in critical situations because of a lesser effect on service or system performance.

Measurement Interval

The length of time over which a flow monitor collects data related to a traffic flow, after which the flow monitor computes flow metrics using the collected data

Media Loss Rate

The number of lost or out-of-order packets over a measurement interval

Media Rate The effective bit rate of the media content carried by a traffic flow.

minor alarm severity type

Used for troubles that do not have a serious effect on service to customers or for alarms in hardware those are not essential to the operation of the system.

MIB Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved by means of SNMP commands, usually through a network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.

MIB II MIB-II is the follow on to MIB-I which was the original standard SNMP MIB. MIB-II provided some much needed enhancements to MIB-I. MIB-II is very old, and most of it has been updated (that which has not is mostly obsolete). It includes objects that describe system related data, especially data related to a system’s interfaces.

MLR Media Loss Rate MPLS Multiprotocol Label Switching. MPLS is a method for forwarding packets (frames) through a

network. It enables routers at the edge of a network to apply labels to packets (frames). ATM switches or existing routers in the network core can switch packets according to the labels with minimal lookup overhead.

MPLS interface An interface on which MPLS traffic is enabled. MPLS is the standardized version of Cisco original tag switching proposal. It uses a label forwarding paradigm (forward packets based on labels).

MR Media Rate MTU Maximum transmission unit. Maximum packet size, in bytes, that a particular interface can handle.N


360

NAS Network access server. Cisco platform or collection of platforms such as an AccessPath system, which interfaces between the Internet and the circuit world, Public Switched Telephone Network (PSTN).

NHLFE Next Hop Label Forwarding EntryNMS Network management system. System responsible for managing at least part of a network. An

NMS is generally a reasonably powerful and well-equipped computer, such as an engineering workstation. NMSs communicate with agents to help keep track of network statistics and resources.

O OID Object identifier. Values are defined in specific MIB modules. The EVENT-MIB allows you or an

NMS to watch over specified objects and to set event triggers based on existence, threshold, and Boolean tests. An event occurs when a trigger is fired; this means that a specified test on an object returns a value of true. To create a trigger, you or an NMS configures a trigger entry in the mteTriggerTable of the EVENT-MIB. This trigger entry specifies the OID of the object to be watched. For each trigger entry type, corresponding tables (existence, threshold, and Boolean tables) are populated with the information required for carrying out the test. The MIB can be configured so that when triggers are activated (fired) either an SNMP Set is performed, a notification is sent out to the interested host, or both.

OIR online insertion and removalP PAP Password Authentication Protocol. Authentication protocol that allows PPP peers to authenticate

one another. The remote router attempting to connect to the local router is required to send an authentication request.

PEM Power Entry Module polling Access method in which a primary network device inquires, in an orderly fashion, whether

secondaries have data to transmit. The inquiry occurs in the form of a message to each secondary that gives the secondary the right to transmit.

PPP Point-to-Point Protocol. Provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. PPP is designed to work with several network layer protocols, such as IP, IPX, and ARA. PPP also has built-in security mechanisms, such as CHAP and PAP. PPP relies on two protocols: LCP and NCP.

Q QoS Quality of Service. Measure of performance for a transmission system that reflects its transmission

quality and service availability. R RADIUS Remote Authentication Dial-In User Service. RADIUS is a distributed client/server system that

secures networks against unauthorized access. In the Cisco implementation, RADIUS clients run on Cisco routers and send authentication requests to a central RADIUS server that contains all user authentication and network service access information.

read-only A read-only variable can be used to monitor information only. For example, the locIPUnreach variable, whose access is read-only, indicates whether Internet Control Message Protocol (ICMP) packets concerning an unreachable address will be sent.


361

read-write A read-write variable can be used to monitor information and to set a new value for the variable. For example, the tsMsgSend variable, whose access is read-write, determines what action to take after a message has been sent. The possible integer values for this variable follow: 1 = nothing 2 = reload 3 = message done 4 = abort

RFC Requests for Comments, started in 1969, form a series of notes about the Internet (originally the ARPANET). The notes discuss many aspects of computer communication, focusing on networking protocols, procedures, programs, and concepts, but also include meeting notes, opinions, and sometimes humor. The specification documents of the Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group, the Internet Engineering Steering Group (IESG), are published as RFCs. Thus, the RFC publication process plays an important role in the Internet standards process.

RSVP Resource Reservation Protocol. Protocol that supports the reservation of resources across an IP network. Applications running on IP end systems can use RSVP to indicate to other nodes the nature (bandwidth, jitter, maximum burst, and so forth) of the packet streams they want to receive. RSVP depends on IPv4. Also known as Resource Reservation Setup Protocol.

S scalar object One type of managed object that is a single object instance (for example, ifNumber in the IF-MIB

and bgpVersion in the BGP4-MIB). security model A security model is an authentication strategy that is set up for a user and the group in which the

user resides. A security level is the permitted level of security within a security model. A combination of a security model and a security level determines which security mechanism is employed when handling an SNMP packet.

SEEPROM Serial Electrically Erasable Programmable Read-only MemorySR Short Reach SNMPv1 The Simple Network Management Protocol: An Internet standard, defined in RFC 1157. Security is

based on community strings. SNMPv1 uses a community-based form of security. The community of managers who are able to access the agent MIB is defined by an IP address access control list and password.


362

SNMPv2 The community-string based administrative framework for SNMPv2. SNMPv2c is an update of the protocol operations and data types of SNMPv2p (SNMPv2 classic), and uses the community-based security model of SNMPv1. SNMPv2c support includes a bulk-retrieval mechanism and more detailed error message reporting to management stations. The bulk-retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trip transmissions required. SNMPv2c improved error-handling support includes expanded error codes that distinguish different kinds of error conditions; these conditions are reported through a single error code in SNMPv1. Error return codes now report the error type. Three kinds of exceptions are also reported:

No such object exceptions No such instance exceptions End of MIB view exceptions

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

Message integrity—Ensuring that a packet has not been tampered with in transit. Authentication—Determining that the message is from a valid source. Encryption—Scrambling the contents of a packet to prevent it from being learned by an

unauthorized source. SNMP agent A software component in a managed device that maintains the data for the device and reports the

data, as needed, to managing systems. The agent and MIB reside on the routing device (router, access server, or switch). To enable the SNMP agent on a managed device, you must define the relationship between the manager and the agent.

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

SSRCn The SSRC identifier of the source.SX Short wavelength T

TE Traffic engineered time stamp Provides the amount of time that has elapsed between the last network re-initialization and

generation of the trap. TLV Type Length Value. Dynamic format for storing data in any order. Used by the Cisco Generic ID

PROM for storing asset information. traffic engineering tunnel

A label-switched tunnel that is used for traffic engineering. Such a tunnel is set up through means other than normal Layer 3 routing; it is used to direct traffic over a path different from the one that Layer 3 routing could cause the tunnel to take.

Traffic Flow A unidirectional stream of packets conforming to a classifier. For example, packets having a particular source IP address, destination IP address, protocol type, source port number, and destination port number.

Transit Time The latency from the insertion into the network to the flow monitor. This value can be computed by taking the

difference between a packet’s RTP timestamp and the device’s clock at the time of arrival (measured in the same

units).


363

trap An trap is an unsolicited (device-initiated) message. The contents of the message might be simply informational, but it is mostly used to report real-time trap information. Because a trap is a UDP datagram, sole reliance upon them to inform you of network problems (for example, passive network monitoring) is not wise. A trap can be used in conjunction with other SNMP mechanisms, as in trap-directed polling,

tunnel A secure communication path between two peers, such as routers. U UDI Cisco Unique Device IdentifierUDP User Datagram ProtocolV VRF VPN Routing and Forwarding TablesVB Virtual Buffer. A virtual buffer is a construct used to simulate a real buffer used by a media

application for the purpose of storing media packets until the application can render their content. VTP VLAN Trunking ProtocolW WFQ Weighted Fair Queueingwrite-only The write-only variable can be used to set a new value for the variable only. For example, the

writeMem variable, whose access is write-only, writes the current (running) router configuration into nonvolatile memory where it can be stored and retained even if the router is reloaded. If the value is set to 0, the writeMem variable erases the configuration memory.

write view A view name (not to exceed 64 characters) for each group; the view name defines the list of object identifiers (OIDs) that can be created or modified by users of the group.

X XCVR Transceiver

Date post:	26-Mar-2018
Category:	Documents
Upload:	buithien
View:	276 times
Download:	6 times

Cisco ASR 9000 Series Aggregation Services Router MIB ... · PDF fileCisco ASR 9000 Series...

Documents