Table Of Contents
MIB Specifications
Overview of MIB Support
MIB Specifications
ATM-MIB
MIB Constraints
BGP4-MIB
MIB Constraints
BRIDGE-MIB
MIB Constraints
CISCO-802-TAP-MIB
CISCO-802-TAP-MIB Tables and Objects
MIB Constraints
CISCO-AAA-SERVER-MIB
MIB Constraints
CISCO-AAL5-MIB
MIB Constraints
CISCO-ACCESS-ENVMON-MIB
MIB Constraints
CISCO-ATM-EXT-MIB
MIB Constraints
CISCO-ATM-PVCTRAP-EXTN-MIB
MIB Constraints
CISCO-BGP4-MIB
MIB Constraints
CISCO-BGP-POLICY-ACCOUNTING-MIB
MIB Constraints
CISCO-BULK-FILE-MIB
MIB Constraint
CISCO-BUS-MIB
MIB Constraints
CISCO-CABLE-ADMISSION-CTRL-MIB
MIB Constraints
CISCO-CABLE-AVAILABILITY-MIB
MIB Constraints
CISCO-CABLE-L2VPN-MIB
MIB Constraints
CISCO-CABLE-METERING-MIB
MIB Constraints
CISCO-CABLE-QOS-MONITOR-MIB
MIB Constraints
CISCO-CABLE-SPECTRUM-MIB
MIB Constraints
MIB Group Objects
CISCO-CABLE-WIDEBAND-MIB
MIB Notes and Constraints
CISCO-CALL-HISTORY-MIB
MIB Constraints
CISCO-CAR-MIB
MIB Constraints
CISCO-CASA-FA-MIB
MIB Constraints
CISCO-CASA-MIB
MIB Constraints
CISCO-CDP-MIB
MIB Constraints
CISCO-CIRCUIT-INTERFACE-MIB
MIB Constraints
CISCO-CLASS-BASED-QOS-MIB
MIB Constraints
CISCO-COMPRESSION-SERVICE-ADAPTER-MIB
MIB Constraints
CISCO-CONFIG-COPY-MIB
MIB Constraints
CISCO-CONFIG-MAN-MIB
MIB Constraints
CISCO-DOCS-EXT-MIB
MIB Tables
MIB Constraints
CISCO-DOCS-REMOTE-QUERY-MIB
MIB Constraints
CISCO-ENHANCED-MEMPOOL-MIB
MIB Constraints
CISCO-ENTITY-ALARM-MIB
MIB Constraints
CISCO-ENTITY-ASSET-MIB
MIB Constraint
CISCO-ENTITY-EXT-MIB
MIB Constraints
CISCO-ENTITY-FRU-CONTROL-MIB
MIB Constraints
CISCO-ENTITY-SENSOR-MIB
MIB Constraints
CISCO-ENTITY-VENDORTYPE-OID-MIB
MIB Constraints
CISCO-ENVMON-MIB
MIB Constraints
CISCO-FLASH-MIB
MIB Constraints
CISCO-FRAME-RELAY-MIB
MIB Constraints
CISCO-FTP-CLIENT-MIB
MIB Constraints
CISCO-HSRP-EXT-MIB
MIB Constraints
CISCO-HSRP-MIB
MIB Constraint
CISCO-IETF-ATM2-PVCTRAP-MIB
MIB Constraint
CISCO-IETF-IP-FORWARD-MIB
MIB Constraints
CISCO-IETF-IP-MIB
MIB Constraints
CISCO-IETF-NAT-MIB
MIB Constraints
CISCO-IETF-PW-MIB
CISCO-IETF-PW-MPLS-MIB
MIB Constraints
CISCO-IMAGE-MIB
MIB Constraints
CISCO-IP-ENCRYPTION-MIB
MIB Constraints
CISCO-IPMROUTE-MIB
MIB Constraints
CISCO-IP-STAT-MIB
MIB Constraints
CISCO-IP-TAP-MIB
CISCO-IP-TAP-MIB Tables and Objects
MIB Constraints
CISCO-IPSEC-FLOW-MONITOR-MIB
MIB Constraints
CISCO-IPSEC-MIB
MIB Constraint
CISCO-IPSEC-POLICY-MAP-MIB
MIB Constraint
CISCO-ISDN-MIB
MIB Constraint
CISCO-LEC-DATA-VCC-MIB
MIB Constraints
CISCO-LEC-EXT-MIB
MIB Constraints
CISCO-LECS-MIB
MIB Constraints
CISCO-LES-MIB
MIB Constraints
CISCO-MEMORY-POOL-MIB
MIB Constraints
CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
MIB Constraints
CISCO-NDE-MIB
MIB Constraints
CISCO-NTP-MIB
MIB Constraints
CISCO-PIM-MIB
MIB Constraints
CISCO-PING-MIB
MIB Constraints
CISCO-PPPOE-MIB
MIB Constraints
CISCO-PROCESS-MIB
MIB Constraints
CISCO-PRODUCTS-MIB
MIB Constraints
CISCO-QUEUE-MIB
MIB Constraints
CISCO-RMON-SAMPLING-MIB
MIB Constraints
CISCO-RTTMON-MIB
CISCO-SLB-EXT-MIB
MIB Constraints
CISCO-SLB-MIB
MIB Constraints
CISCO-SNAPSHOT-MIB
MIB Constraints
CISCO-SRP-MIB
MIB Constraints
CISCO-SYSLOG-MIB
MIB Constraints
CISCO-TAP2-MIB
CISCO-TAP2-MIB Table and Objects
MIB Constraint
CISCO-TCP-MIB
MIB Constraint
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
MIB Constraint
CISCO-VPDN-MGMT-EXT-MIB
MIB Constraints
CISCO-VPDN-MGMT-MIB
MIB Constraints
CISCO-VSIMASTER-MIB
MIB Constraints
CLAB-TOPO-MIB
DOCS-BPI-MIB
MIB Constraints
DOCS-BPI-PLUS-MIB
MIB Constraints
DOCS-CABLE-DEVICE-MIB
MIB Constraints
DOCS-CABLE-DEVICE-TRAP-MIB
MIB Constraints
DOCS-IFEXT2-MIB
MIB Constraints
DOCS-IF-EXT-MIB
MIB Constraints
DOCS-IF-M-CMTS-MIB
MIB Constraints
DOCS-LOADBAL3-MIB
MIB Constraints
DOCS-LOADBALANCING-MIB
MIB Constraints
DOCS-MCAST-AUTH-MIB
MIB Constraints
DOCS-IF3-MIB
MIB Constraints
DOCS-IF-MIB
MIB Constraints
DOCS-DIAG-MIB
DOCS-DRF-MIB
DOCS-DSG-IF-MIB
MIB Constraints
DOCS-IETF-BPI2-MIB
DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB
DOCS-IETF-QOS-MIB
MIB Constraints
DOCS-QOS3-MIB
MIB Constraints
DOCS-QOS-MIB
MIB Constraints and Notes
DOCS-SEC-MIB
DOCS-SUBMGT3-MIB
MIB Constraints
DOCS-SUBMGT-MIB
MIB Constraints
DOCS-TEST-MIB
MIB Constraints
DOCS-L2VPN-MIB
DOCSIS-L2VPN-MIB Tables and Objects
DTI-MIB
MIB Constraints
ENTITY-MIB
MIB Constraints
Cisco uBR100012 SPA-24XWBD-SFP Shared Port Adapter
ENTITY-MIB UDI Support
Overview of the ENTITY-MIB
Changes to Support Virtual Interfaces
Chassis Slot Layout
ENTITY-SENSOR-MIB
MIB Constraints
ETHERLIKE-MIB
MIB Constraints
EVENT-MIB
MIB Constraints
EXPRESSION-MIB
MIB Constraints
HC-RMON-MIB
MIB Constraints
IF-MIB
IF-MIB Notes
IF-MIB Supported Traps
IGMP-MIB
MIB Constraints
IGMP-STD-MIB
MIB Constraint
INT-SERV-MIB
MIB Constraints
IP-MIB
MIB Constraint
IPMROUTE-MIB
MIB Constraint
IPMROUTE-STD-MIB
MIB Constraint
ISDN-MIB
MIB Constraint
LAN-EMULATION-CLIENT-MIB
MIB Constraints
MPLS-LSR-MIB
MIB Constraints
MPLS-LDP-MIB
MIB Constraints
MPLS-TE-MIB
MIB Constraints
MPLS-TE-STD-MIB
MIB Constraints
MSDP-MIB
MIB Constraints
NOTIFICATION-LOG-MIB
MIB Constraints
nruCacheSnmpData
MIB Constraints
OLD-CISCO-CHASSIS-MIB
OLD-CISCO-CPU-MIB
OLD-CISCO-INTERFACES-MIB
OLD-CISCO-IP-MIB
OLD-CISCO-MEMORY-MIB
OLD-CISCO-SYSTEM-MIB
OLD-CISCO-TCP-MIB
OLD-CISCO-TS-MIB
PIM-MIB
MIB Constraints
RFC1213-MIB
MIB Constraints
RFC1231-MIB
MIB Constraint
RFC1253-MIB
MIB Constraints
RFC1315-MIB
MIB Constraints
RFC1381-MIB
MIB Constraint
RFC1382-MIB
MIB Constraint
RFC1406-MIB
MIB Constraints
RFC1407-MIB
MIB Constraints
RFC1595-MIB
MIB Constraint
RFC2558-MIB
MIB Constraints
RMON-MIB
MIB Constraints
RMON2-MIB
MIB Constraints
RS-232-MIB
MIB Constraints
RSVP-MIB
MIB Constraints
SMON-MIB
MIB Constraints
SNMP-COMMUNITY-MIB
MIB Constraints
SNMP-FRAMEWORK-MIB
MIB Constraints
SNMP-MPD-MIB
MIB Constraints
SNMP-NOTIFICATION-MIB
MIB Constraints
SNMP-PROXY-MIB
MIB Constraints
SNMP-TARGET-MIB
MIB Constraints
SNMP-USM-MIB
MIB Constraints
SNMP-VACM-MIB
MIB Constraints
SNMPv2-MIB
MIB Constraints
TCP-MIB
MIB Constraints
UDP-MIB
MIB Constraints
MIB Specifications
This chapter describes each Management Information Base (MIB) on the Cisco CMTS router. Each description lists any constraints on how the MIB or its object identifiers (OIDs) are implemented on the router.
Unless noted otherwise, the Cisco CMTS implementation of a MIB follows the standard MIB that has been defined. Any MIB table or object not listed the tables is implemented as defined in the standard MIB definition.
Note 
Not all MIBs included in a Cisco IOS software release are fully supported by the router. Some MIBs are not supported at all. Other MIBs might work, but they have not been tested on the router. In addition, some MIBs are deprecated but cannot be removed from the software. When a MIB is included in the image, this does not necessarily mean it is supported by the Cisco CMTS platform.
Note For information about how to avoid performance problems when you use Simple Network Management Protocol (SNMP) to poll the router for routing table entries, see the "High CPU Usage When Polling Routing ARP Tables" section on page 2-5.
Overview of MIB Support
Support for a particular MIB is included as part of the Cisco IOS software release. Each version of Cisco IOS software contains code that responds to SNMP requests for objects that are in the MIBs that are supported in that release for that particular software image.
Each new release of Cisco IOS software typically changes that support to some extent, usually involving one or more of the following:
•Fixing a caveat or software defect that is preventing the proper use of the MIB
•Updating the software to support the latest version of the MIB or to support optional objects that were not supported previously
•Adding support for new MIBs that are part of a new feature that is being introduced
The fact that a MIB might be included in a Cisco IOS software release does not imply that the MIB is fully supported on the router. Similarly, the fact that you can access a particular object in a MIB does not imply that the object is fully supported either.
Note As a general rule, deprecated objects and MIBs should not be used, because they have been replaced by other, more functional objects and MIBs. Also, deprecated objects and MIBs can be removed in a future release without notice.
Note The exact MIB support depends on both the Cisco IOS software image and the Cisco IOS software release being used. To determine which MIBs are included in other releases and software images, see the "Determining MIB Support for Cisco IOS Releases" section on page 2-1.
Table 3-1 lists the MIBs that are included in Cisco IOS Release 12.3BC for Cisco CMTS routers, through Cisco IOS Release 12.2(33)SCC. Shaded cells indicate that the MIB is not included for that particular platform and software release. Unless otherwise indicated, each MIB is included in all software images for the indicated release. In some cases, MIBs that are included in the software image are not actually supported or are only partially supported.
Table 3-2 list the specific cable MIBs.
Table 3-2 Cable-Specific MIBs
MIB Name
|
MIB Description
|
DOCS-BPI-MIB
|
Contains objects to configure, operate, and monitor the DOCSIS 3.0 Baseline Privacy Interface (BPI) feature.
|
DOCS-BPI-PLUS-MIB
Narrowband fiber nodes and Multicast supported in Cisco IOS Release 12.3(23)BC and later.
|
Describes the attributes for the DOCSIS 1.1-specified Baseline Privacy Interface Plus (BPI+) on CMS and the CMTS. This is a draft revision 05 of the MIB.
Note This MIB replaces DOCS-BPI-MIB, which was used in the initial DOCSIS 1.0 releases.
|
DOCS-CABLE-DEVICE-MIB
|
Contains objects to configure and monitor DOCSIS-compliant CMTS platforms and cable modem devices.
|
DOCS-CABLE-DEVICE-TRAP-MIB
|
Contains objects that supplement the DOCS-CABLE-DEVICE-MIB to define and configure traps and notifications for DOCSIS-compliant CMTS platforms and cable modems.
|
DOCS-DIAG-MIB
|
Contains objects that enable early error detection, fault management, and troubleshooting the cable network.
|
DOCS-DRF-MIB
|
Contains the management objects to manage Downstream RF Interface specifications.
|
DOCS-DSG-IF-MIB
|
Contains objects to manage the DOCSIS Set-top Gateway (DSG).
|
DOCS-IETF-BPI2-MIB
|
Contains objects to manage baseline privacy plus interface (BPI+) in CMTSs.
|
DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB
|
Contains objects to define and configure traps and notifications for DOCSIS-compliant CMTS platforms and cable modems.
|
DOCS-IETF-QOS-MIB
|
Contains objects to manage information for Quality Of Service (QOS) for DOCSIS 1.1 and 2.0.
|
DOCS-IF3-MIB
|
Contains objects to manage DOCSIS 3.0 features such as primary channel bonding, interface topology, and enhanced signal quality monitoring.
|
DOCS-IF-MIB
|
Describes the Data-over-Cable Service Interface Specifications (DOCSIS)-compliant Radio Frequency (RF) interfaces in cable modems and the CMTS. This MIB has been released as an RFC 2670.
|
DOCS-IFEXT2-MIB
|
Contains management objects to enhance DOCSIS 2.0 feature set.
|
DOCS-IF-EXT-MIB
|
Contains objects that supplement the DOCS-IF-MIB to provide information about the capabilities and status of online cable modems.
|
DOCS-IF-M-CMTS-MIB
|
Contains the management objects to configure and manage theDownstream External PHY Interface (DEPI) of the M-CMTS architecture (Modular CMTS).
|
DOCS-LOADBAL3-MIB
|
Defines objects to support the requirements of CableLabs DOCSIS 3.0 certification.
|
DOCS-LOADBALANCING-MIB
|
Contains objects to support the requirements of CableLabs DOCSIS 2.0 certification.
|
DOCS-MCAST-AUTH-MIB
|
Contains objects to manage the CMTS Multicast Authorization Module.
|
DOCS-QOS3-MIB
|
Contains objects to manage QOS for channel bonding.
|
DOCS-QOS-MIB
|
Contains objects to configure and monitor the QoS features that are available in DOCSIS 1.1 and DOCSIS 2.0 cable networks.
|
DOCS-SEC-MIB
|
Contains the objects to implement and manage the security based on the DOCSIS security specifications.
|
DOCS-SUBMGT3-MIB
|
Defines objects to manage IPv4 and IPv6 traffic across CMs and Customer Premise Equipment (CPE).
|
DOCS-SUBMGT-MIB
|
Contains objects to configure and monitor the subscriber management features in DOCSIS 1.1 and DOCSIS 2.0 cable networks.
|
DOCS-TEST-MIB
|
Contains objects to support programmable test features for DOCSIS 2.0 compliant Cable Modem Termination Systems (CMTS).
|
DOCS-L2VPN-MIB
|
Contains the SNMP management objects that the Cisco CMTS router uses for L2VPN support.
|
CISCO-DOCS-EXT-MIB
|
Extends the DOCSIS standard RFI MIB (DOCS-IF-MIB) with Cisco-specific extensions, such as Quality of Service (QoS) attributes and connection status and other information regarding the cable modems and Customer Premise Equipment (CPE) devices supported by the CMTS.
|
CISCO-DOCS-REMOTE-QUERY-MIB
|
Facilitates SNMP polling of remote cable modems on CMTS.
|
CISCO-CABLE-SPECTRUM-MIB
|
Describes the spectrum management and flap list attributes.
|
CISCO-CABLE-ADMISSION-CTRL-MIB
|
Enables the management of Cable Modem Termination System (CMTS) admission control.
|
CISCO-CABLE-AVAILABILITY-MIB
|
Describes the operation of Hot Standby Connection to Connection Protocol (HCCP) N+1 redundancy on the Cisco CMTS.
|
CISCO-CABLE-L2VPN-MIB
|
Contains objects that manage Cisco devices that comply with the DOCSIS L2VPN feature for IP/MPLS pseudo-wire.
|
CISCO-CABLE-METERING-MIB
|
Describes subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, also known as Usage-Based Billing on the Cisco CMTS.
|
CISCO-CABLE-QOS-MONITOR-MIB
|
Describes SNMP support for the Subscriber Traffic Management (STM) feature.
|
DOCS-QOS-MIB
|
Describes the QoS attributes. This is a draft revision 05 of the MIB.
Note Cisco IOS Software Release 12.1(4)CX implemented revision 02 of this MIB. Revision 05 includes substantial changes to the tables and attributes.
|
DOCS-SUBMGT-MIB
|
Describes the subscriber management attributes. This is revision 02 of the MIB.
|
DOCS-CABLE-DEVICE-MIB
|
Describes the operation of cable modem and CMTS. Only the syslog and Event tables are supported by this MIB, which was released as RFC 2669.
|
DOCS-CABLE-DEVICE-TRAP-MIB
|
This is the extension of the RFC2669 (DOCS-CABLE-DEVICE-MIB). It defines all the traps supported by a cable modem and CMTS.
|
CISCO-CABLE-WIDEBAND-MIB
|
Contains objects that support Wideband DOCSIS on the Cable Modem Termination System (CMTS).
|
CLAB-TOPO-MIB
|
Contains management objects to manage fiber nodes in a cable plant.
|
MIB Specifications
This section gives a short summary of each MIB, along with the MODULE-IDENTITY and top-level object identifier (OID) that can be used to access the MIB when using an SNMP manager.
ATM-MIB
The ATM-MIB contains the Asynchronous Transfer Mode (ATM) and ATM adaptation layer 5 (AAL5) objects used to manage ATM interfaces, virtual links, cross connects, and AAL5 entities and connections, as defined in RFC 1695.
The MODULE-IDENTITY for the ATM-MIB is atmMIB, and its top-level OID is 1.3.6.1.2.1.37 (iso.org.dod.internet.mgmt.mib-2.atmMIB).
MIB Constraints
There are no constraints on this MIB.
BGP4-MIB
The BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP), as defined in RFC 1657. The MIB provides:
•BGP configuration information
•Information about BGP peers and messages exchanged with them
•Information about advertised networks
The MODULE-IDENTITY for the BGP4-MIB is bgp, and its top-level OID is 1.3.6.1.2.1.15 (iso.org.dod.internet.mgmt.mib-2.bgp).
MIB Constraints
There are no constraints on this MIB.
BRIDGE-MIB
The BRIDGE-MIB provides access to information related to Layer 2 bridging that is based on MAC addresses, as defined in RFC 1493.
The MODULE-IDENTITY for the BRIDGE-MIB is dot1dBridge, and its top-level OID is 1.3.6.1.2.1.17 (iso.org.dod.internet.mgmt.mib-2.dot1dBridge).
MIB Constraints
This MIB is supported only on the Cisco uBR7100 series router when running a Cisco IOS "-is-" software image. It is not supported on the Cisco uBR7200 series and Cisco uBR10012 routers, which do not support bridging across cable interfaces.
CISCO-802-TAP-MIB
The CISCO-802-TAP-MIB contains the SNMP management objects to configure and execute lawful intercepts on Layer 2 streams. This MIB is used with the CISCO-TAP2-MIB to intercept traffic based on MAC address.
The Cisco CMTS routers in Cisco IOS Release 12.2(33)SCC support MAC-based intercepts for both the cable modem (CM) and the customer premise equipment (CPE) using SNMPv3.
CISCO-802-TAP-MIB Tables and Objects
Table 3-3 lists CISCO-802-TAP-MIB Tables and Objects.
.
Table 3-3 CISCO-802-TAP-MIB Tables and Objects
Object
|
Description
|
c802tapStreamTable
|
Lists the IEEE 802 data streams to be intercepted.
|
c802tapStreamCapabilities
|
Displays the types of intercept streams that can be configured on this device. This may be dependent on hardware or software capabilities.
|
MIB Constraints
There are no constraints on this MIB.
CISCO-AAA-SERVER-MIB
The CISCO-AAA-SERVER-MIB contains information about authentication, authorization, and accounting (AAA) servers within the router and external to the router. The MIB provides:
•Configuration information for AAA servers, including identities of external AAA servers
•Statistics for AAA functions
•Status (state) information for AAA servers
MIB Constraints
The configuration objects in casConfigTable are implemented as read-only. Table 3-4 lists the constraints that the Cisco CMTS uBR router places on objects in the CISCO-AAA-SERVER-MIB. For detailed definitions of MIB objects, see the MIB.
.
Table 3-4 CISCO-AAA-SERVER-MIB Constraints
MIB Object
|
Notes
|
casConfigTable
|
|
•casAddress
|
Read-only.
|
•casAuthenPort
|
Read-only.
|
•casAcctPort
|
Read-only.
|
•casKey
|
Read-only.
|
•casConfigRowStatus
|
Read-only.
|
casStatisticsTable
|
|
•casAuthorRequests
•casAuthorRequestTimeouts
•casAuthorUnexpectedResponses
•casAuthorServerErrorResponses
•casAuthorIncorrectResponses
•casAuthorResponseTime
•casAuthorTransactionSuccesses
•casAuthorTransactionFailures
|
For TACACS+ servers, these objects have valid values.
For RADIUS servers, these objects are always 0. This is because RADIUS does not make authorization requests. Instead, the attributes received during authentication are stored and later used for authorization.
|
CISCO-AAL5-MIB
The CISCO-AAL5-MIB contains performance statistics for ATM adaptation layer 5 (AAL5) virtual channel connections (VCCs). This MIB provides additional statistics that supplement the information stored in the aal5VccTable in ATM-MIB (RFC 1695), such as packets and octets received and transmitted on the VCC.
The MODULE-IDENTITY for the CISCO-AAL5-MIB is ciscoAal5MIB, and its top-level OID is 1.3.6.1.4.1.9.9.66 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoAal5MIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-ACCESS-ENVMON-MIB
The CISCO-ACCESS-ENVMON-MIB supplements the ciscoEnvMonSupplyStatusTable table in CISCO-ENVMON-MIB, providing additional information about power supply failures. This MIB also defines new temperature and voltage notifications that replace those in CISCO-ENVMON-MIB.
The MODULE-IDENTITY for the CISCO-ACCESS-ENVMON-MIB is ciscoAccessEnvMonMIB, and its top-level OID is 1.3.6.1.4.1.9.9.61 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoAccessEnvMonMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-ATM-EXT-MIB
The CISCO-ATM-EXT-MIB contains extensions to the Cisco ATM module that are used to manage ATM entities. It supplements the CISCO-AAL5-MIB, providing additional AAL5 performance statistics for a virtual channel connection (VCC) on an ATM interface.
The MODULE-IDENTITY for the CISCO-ATM-EXT-MIB is ciscoAtmExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.88 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoAtmExtMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-ATM-PVCTRAP-EXTN-MIB
The CISCO-ATM-PVCTRAP-EXTN-MIB contains extensions to the ATM-MIB, providing additional notifications and traps about the status of permanent virtual circuits (PVCs) on the Cisco CMTS.
The MODULE-IDENTITY for the CISCO-ATM-PVCTRAP-EXTN-MIB is ciscoAtmPvcTrapExtnMIB, and its top-level OID is 1.3.6.1.4.1.9.10.97 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoAtmPvcTrapExtnMIB).
MIB Constraints
The CISCO-ATM-PVCTRAP-EXTN-MIB is not supported in any Cisco IOS Release 12.1EC software image.
Note This is an experimental and obsolete MIB that might be replaced without prior notice.
CISCO-BGP4-MIB
The CISCO-BGP4-MIB contains extensions to the BGP4-MIB that are specific to Cisco, including additional information about the entries in the BGP routing table.
The MODULE-IDENTITY for the CISCO-BGP4-MIB is ciscoBgp4MIB, and its top-level OID is 1.3.6.1.4.1.9.9.187 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoBgp4MIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-BGP-POLICY-ACCOUNTING-MIB
The CISCO-BGP-POLICY-ACCOUNTING-MIB contains objects for BGP policy-based accounting that are specific to Cisco platforms.
The MODULE-IDENTITY for the CISCO-BGP-POLICY-ACCOUNTING-MIB is ciscoBgpPolAcctMIB, and its top-level OID is 1.3.6.1.4.1.9.9.148 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoBgpPolAcctMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers.
•This MIB is not supported on Cisco uBR10012 routers.
•This MIB is not supported in Cisco IOS Release 12.2BC.
CISCO-BULK-FILE-MIB
The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer, in different file formats (ASN.1/BER, binary, and ASCII).
The MODULE-IDENTITY for the CISCO-BULK-FILE-MIB is ciscoBulkFileMIB, and its top-level OID is 1.3.6.1.4.1.9.9.81 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoBulkFileMIB).
MIB Constraint
This MIB is supported only on Cisco uBR7100 series and Cisco uBR7200 series routers that are running a Cisco IOS "-is-" software image.
CISCO-BUS-MIB
The CISCO-BUS-MIB contains objects about the operation of each broadcast and unknown server (BUS) that is operating on an ATM virtual LAN (VLAN) that is using LAN Emulation (LANE) tagging.
The MODULE-IDENTITY for the CISCO-BUS-MIB is ciscoBusMIB, and its top-level OID is 1.3.6.1.4.1.9.9.40 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoBusMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is supported only on Cisco uBR7100 series and Cisco uBR7200 series routers that are running a Cisco IOS "-is-" software image.
•This MIB is not supported on the Cisco uBR10012 router.
CISCO-CABLE-ADMISSION-CTRL-MIB
The CISCO-CABLE-ADMISSION-CTRL-MIB contains objects to manage Cable Modem Termination System (CMTS) admission control. The Cisco Cable Admission Control feature refers to the rules that the Cisco CMTS follows when allocating and monitoring events for the following resources:
•CPU and memory utilization data and thresholds setting on the physical entity, such as the main processor, line card, or Broadband processing Engines (BPE), when a monitoring event occurs.
•Upstream (US) channel bandwidth utilization based on scheduling types or service classes.
•Downstream (DS) channel bandwidth utilization based on voice or data.
The monitored events for Cable Admission Control on the Cisco CMTS include the following:
•Dynamic service flow creation requests—Dynamic service flow allows on-demand reservation on Layer 2 bandwidth resources. CMTS provides special QoS to the cable modem dynamically during a voice call or video session, providing a more efficient use of the available bandwidth.
•Resource requests during cable modem (CM) registration—CMTS resources are required during CM registration. These resources are verified when CM receives a registration request.
Note For detailed information about admission control for Cisco CMTS, go to the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_adm.html
Two types of tables, configuration and status, are defined in this MIB to support Service Flow Admission Control (SFAC) functionality. The configuration table stores the threshold information for the upstream bonding group for all the application types defined by the SFAC feature. The status tables store the status information for the Upstream Bonding Group (UBG) SFAC feature. An entry in status table contains the reservation level for each bucket as well as the number of times a threshold was exceeded. The following configuration tables are defined:
•ccacUsConfigRevTable: Contains configuration information for each cable upstream port.
•ccacDsConfigRevTable: Contains configuration information for each downstream cable interface or downstream cable bonding group.
•ccacUsBGConfigTable: Contains configured treshold for each upstream bonding group. A separate threshold exists for each Application type defined by the SFAC feature.
The following status tables are defined:
•ccacUsRevTable: Contains status information for each Cable upstream port.
•ccacDsRevTable: Contains status information for each cable interface (legacy, integrated, or modular) and downstream bonding groups.
•ccacUsBGTable: Contains status information for each upstream bonding group. An entry contains the reservation level for each bucket and the number of times a threshold was exceeded.
MIB Constraints
Table 3-5 lists the constraints that the router places on CISCO-CABLE-ADMISSION-CTRL-MIB.
.
Table 3-5 CISCO-CABLE-ADMISSION-CTRL-MIB Constraints
MIB Object
|
Notes
|
ccacEventHistTable
|
|
•ccacEventHistTableSize
|
The ccacEventHistTableSize object specifies the number of entries that the ccacEventHistTable can contain.
When the capacity of the ccacEventHistTable has reached the value specified by this object, then the agent deletes the oldest entity in order to accommodate the new entry. A value of zero prevents any history from being retained.
The ccacEventHistTableSize is restricted to 5000.
|
•ccacSysRscConfigStatus
|
Read-only.
|
CISCO-CABLE-AVAILABILITY-MIB
The CISCO-CABLE-AVAILABILITY-MIB contains objects to manage the operations of Hot Standby Connection to Connection Protocol (HCCP) N+1 redundancy on the Cisco CMTS.
The MODULE-IDENTITY for the CISCO-CABLE-AVAILABILITY-MIB is ciscoCableAvailabilityMIB, and its top-level OID is 1.3.6.1.4.1.9.9.242 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableAvailabilityMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is not supported in any Cisco IOS Release 12.1EC software image.
•This MIB is not supported on the Cisco uBR7100 series router.
•This MIB is supported on the Cisco uBR10012 router in Cisco IOS Release 12.2(8)BC1 and later releases.
CISCO-CABLE-L2VPN-MIB
The CISCO-CABLE-L2VPN-MIB contains objects that manage Cisco devices that comply with the DOCSIS L2VPN feature for IP/MPLS pseudo-wire. This MIB compliments the DOCS-L2VPN-MIB by defining additional information such as state and configuration information for the pseudo-wire. The MIB also stores mapping information between various configurations of the pseudo-wire related to DOCSIS BSOD L2VPN. The Cisco CMTS implementation of IP/MPLS pseudo-wire is based on the DOCSIS BSOD L2VPN specification.
MIB Constraints
The objects of CISCO-CABLE-L2VPN-MIB are read-only and the set operation is not supported on the objects of this MIB.
CISCO-CABLE-METERING-MIB
The CISCO-CABLE-METERING-MIB contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, also known as Usage-Based Billing on the Cisco CMTS. This format is specified by the DOCSIS Operations Support System Interface (OSSI) specification.
The MODULE-IDENTITY for the CISCO-CABLE-METERING-MIB is ciscoCableMeteringMIB, and its top-level OID is 1.3.6.1.4.1.9.9.424 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableMeteringMIB).
Before Cisco IOS release 12.2(33)SCB5, the collection interval range was defined from 15 to 1440 for ccmtrCollectionInterval. But the collection interval range can be set from 2 to 1440 by CLI; so from Cisco IOS release 12.2(33)SCB5, a new object, ccmtrCollectionRevInterval, has been defined under the CISCO-CABLE-METERING-MIB with range from 2 to 1440 to replace ccmtrCollectionInterval. The ccmtrCollectionInterval is deprecated but can be set or get using SNMP operations. Table 3-6 lists the behavior of the collection interval range objects ccmtrCollectionInterval and ccmtrCollectionRevInterval:
Table 3-6 Behavior of ccmtrCollectionInterval and ccmtrCollectionRevInterval Objects
Action
|
Behavior of the Objects
|
ccmtrCollectionInterval
|
ccmtrCollectionRevInterval
|
When the interval is set from 2 to 14 using the CLI.
|
Contains 15 as value.
|
Contains the actual value.
|
When the interval is set from 15 to 1440 using the CLI.
|
Contains the actual value.
|
Contains the actual value.
|
When ccmtrCollectionInterval is set to a value range from 2 to 14.
|
Operation fails.
|
Contains the actual value.
|
When ccmtrCollectionInterval is set to a value range from 15 to 1440.
|
Contains the actual value.
|
Contains the actual value.
|
When ccmtrCollectionRevInterval is set to a value range from 2 to 14.
|
Contains 15 as value.
|
Contains the actual value.
|
When ccmtrCollectionRevInterval is set to a value range from 15 to 1440.
|
Contains the actual value.
|
Contains the actual value.
|
Note For complete documentation about Usage-Based Billing feature for Cisco CMTS, go to:
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html
MIB Constraints
This MIB has the following constraints:
•The packet counters displayed by CLI commands are reset to zero whenever the Cisco CMTS router is rebooted. The packet counters displayed by SNMP commands are retained across router resets. These counters are 64-bit values and could roll over to zero during periods of heavy usage.
•This MIB is supported only in Cisco IOS Release 12.3(9a)BC and later releases.
CISCO-CABLE-QOS-MONITOR-MIB
The CISCO-CABLE-QOS-MONITOR-MIB provides SNMP support for the Subscriber Traffic Management (STM) feature, which allows network administrators to identify users who violate their service level agreements (SLA) by using resources beyond their allowable bandwidth. When a user violates the enforce-rules, a SNMP trap notification is generated and sent. The following objects are defined in CISCO-CABLE-QOS-MONITOR-MIB to monitor and manage bandwidth usage by a subscriber:
•ccqmCmtsEnfRulePenaltyEndTime—Specifies the time at which a subscriber is moved out of penalty irrespective of whether the penalty period is over or not. The value of this object ranges from 1 to 23.
•ccqmCmtsEnfRuleWkndMode—Indicates whether the monitoring was performed on weekends or not and what parameters are applicable for weekend monitoring. This object indicates one of the following three states:
–Weekend monitoring is off. This state indicates that no subscriber monitoring is performed during the weekend.
–Default weekend monitoring. This state indicates that monitoring parameters during the weekend default to the weekday parameters. The conditions used to monitor a subscriber during the weekdays is applicable to weekends.
–Configured weekend monitoring. This state indicates that monitoring parameters for weekend are separate from the weekday parameters and are separately configured.
The following are lagacy monitoring parameters for weekend:
–ccqmCmtsEnfRuleWkndMonDuration
–ccqmCmtsEnfRuleWkndAvgRate
–ccqmCmtsEnfRuleWkndSampleRate
•ccqmCmtsEnfRuleWkndAutoEnforce—Used to enforce the legacy and peak-offpeak parameters on weekends.
•ccqmCmtsEnfRuleWkndOff—Used to switch off monitoring duration during the weekend.
The CISCO-CABLE-QOS-MONITOR-MIB also provides objects for monitor peak-offpeak time zones separately for weekend.
•ccqmCmtsEnfRuleWkndFirstPeakTime
•ccqmCmtsEnfRuleWkndFirstDuration
•ccqmCmtsEnfRuleWkndFirstAvgRate
•ccqmCmtsEnfRuleWkndSecondPeakTime
•ccqmCmtsEnfRuleWkndSecondDuration
•ccqmCmtsEnfRuleWkndSecondAvgRate
•ccqmCmtsEnfRuleWkndOffPeakDuration
•ccqmCmtsEnfRuleWkndOffPeakAvgRate
•ccqmCmtsEnfRuleWkndAutoEnforce
The CISCO-CABLE-QOS-MONITOR-MIB also provides objects to represent the peak times in hh:mm format:
•ccqmCmtsEnfRuleFirstPeakTimeMin
•ccqmCmtsEnfRuleSecondPeakTimeMin
•ccqmCmtsEnfRuleWkndFirstPeakTimeMin
•ccqmCmtsEnfRuleWkndSecondPeakTimeMin
To represent the penalty release time in hh:mm format, the ccqmCmtsEnfRulePenaltyEndTimeMin object is defined in CISCO-CABLE-QOS-MONITOR-MIB.
To configure penalty duration uniquely for week-days and weekends, the following objects are defined in CISCO-CABLE-QOS-MONITOR-MIB:
•ccqmCmtsEnfRuleWkPenaltyPeriod
•ccqmCmtsEnfRuleWkndPenaltyPeriod
Since the penalty duration may change for weekends and weekdays, a read-only object, ccqmCmtsEnfRuleCurrPenaltyPeriod, is defined to indicate the current applicable penalty duration. To indicate whether monitoring should continue after release-time ccqmCmtsEnfRuleRelTimeMonitorOn object is defined.
This MIB provides configuration options similar to those provided by the cable qos enforce-rule command. It also provides access to the attributes that are displayed by the show cable qos enforce-rule and show cable subscriber-usage commands.
The MODULE-IDENTITY for the CISCO-CABLE-QOS-MONITOR-MIB is ciscoCableQosMonitorMIB, and its top-level OID is 1.3.6.1.4.1.9.9.341 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableQosMonitorMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is not supported in any Cisco IOS Release 12.1EC software image.
•This MIB is supported starting with Cisco IOS Release 12.2(15)BC1 and later releases.
CISCO-CABLE-SPECTRUM-MIB
The CISCO-CABLE-SPECTRUM-MIB defines objects to provide SNMP support for cable spectrum management and flap-list operations on the DOCSIS compliant Cisco CMTS. Spectrum management enables the CMTS to:
•Identify both downstream and upstream plant impairments.
•Report these impairments to a management entity.
•Automatically resolve these impairmants where possible.
The purpose of cable spectrum management is to:
•Prevent long-term service interruptions caused by upstream noise events in the cable plant
•Provide fault management and troubleshooting on the cable network. The following new tables and objects are supported in this MIB:
–ccsSpecGroupFreqTable
–ccsUpInSpecGroupTable
–ccsUpInCombGroupTable
–ccsUpSpecMgmtSpecGroup
–ccsUpSpecMgmtSharedSpectrum
The MODULE-IDENTITY for the CISCO-CABLE-SPECTRUM-MIB is ciscoCableSpectrumMIB and its top-level OID is 1.3.6.1.4.1.9.9.114 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableSpectrumMIB).
MIB Constraints
Table 3-7 lists the constraints that the router places on CISCO-CABLE-SPECTRUM-MIB.
.
Table 3-7 CISCO-CABLE-SPECTRUM-MIB Constraints
MIB Object
|
Notes
|
ccsUpSpecMgmtTable
|
|
•ccsUpSpecMgmtSNR
|
This object returns zero (0) in three situations: when the actual signal-to-noise ratio (SNR) measures 0 (when ingress noise cancellation is being used), when no cable modems are online the upstream, or when the SNMP agent on the router could not determine a valid SNR value.
|
•ccsUpSpecMgmtSpecGroup
|
Read-only. The value of 0 for this object indicates that the upstream has no spectrum group assigned to it.
|
•ccsUpSpecMgmtSharedSpectrum
|
Read-only. The combiner group assigned to the upstream. Note: Upstreams having same combiner group number indicates that they physically combine together into the same RF domain and must have unique frequency assigned. The value of 0 for the object indicates that the upstream is not physically combine with any others.
|
ccsCmFlapTable
|
|
•ccsFlapAging
ccsFlapListMaxSize ccsFlapInsertionTime ccsFlapMissThreshold ccsFlapPowerAdjustThreshold ccsFlapResetAll, ccsFlapClearAll ccsFlapResetNow
•The following objects are supported in Cisco IOS release 12.3(23)BC and later releases:
ccsCmFlapDownstreamIfIndex
ccsCmFlapUpstreamIfIndex
ccsCmFlapMacAddr
|
These objects are supported on the Cisco uBR10012 router in Cisco IOS Release 12.2(11)BC3 and later releases.
Commencing in Cisco IOS Release 12.3(23)BC, This table keeps the records of modem state changes, and can be used to identify problematic cable modems. The system automatically adds an entry per modem to the table when it detects any state changes to the modem. This table can be deleted but cannot be added by the management system.
The index objects are ccsCmFlapDownstreamIfIndex, ccsCmFlapUpstreamIfIndex, ccsCmFlapMacAddr. This table is used to replace ccsFlapTable, using downstream, upstream and MAC address as indices for the flapped modem.
For NB CMs using SPA Downstream, ccsCmFlapDownstreamIfIndex should be the ifindex of Modular Cable Interface snmp ifindex.
|
MIB Group Objects
Table 3-8 lists the groups and objects added to the CISCO-CABLE-SPECTRUM-MIB.
.
Table 3-8 CISCO-CABLE-SPECTRUM-MIB Group Objects
MIB Object
|
Notes
|
ccsSpecGroupFreqTable
|
Contains the frequency and band configuration of the spectrum group.
|
•ccsSpecGroupNumber
|
|
•ccsSpecGroupFreqIndex
|
Unsigned32
|
•ccsSpecGroupFreqType
|
INTEGER
|
•ccsSpecGroupFreqLower
|
Unsigned32
|
• ccsSpecGroupFreqUpper
|
Unsigned32
|
• ccsSpecGroupStorage
|
StorageType
|
•ccsSpecGroupRowStatus
|
RowStatus
|
ccsUpInSpecGroupTable
|
Contains the cable upstream interfaces assigned to a spectrum group. A spectrum group contains one or more fixed frequencies or frequency bands which can be assigned to cable upstream interfaces in the spectrum group.
|
•ccsSpecGroupNumber
|
Unsigned32
|
• ccsSpecGroupUpstreamIfIndex
|
InterfaceIndex
|
•ccsSpecGroupUpstreamStorage
|
StorageType
|
• ccsSpecGroupUpstreamRowStatus
|
RowStatus
|
ccsUpInCombGroupTable
|
Contains all the cable upstream interfaces in a combiner group. Each combiner group uniquely represents a RF domain. Cable upstream interfaces in same combiner group are physically combined together into same RF domain
|
• ccsCombGroupNumber
|
Unsigned32
|
•ccsCombGroupUpstreamIfIndex
|
InterfaceIndex
|
•ccsCombGroupUpstreamStorage
|
StorageType
|
•ccsCombGroupUpstreamRowStatus
|
RowStatus
|
CISCO-CABLE-WIDEBAND-MIB
CISCO-CABLE-WIDEBAND-MIB in Cisco IOS 12.3(21)SCB
The CISCO-CABLE-WIDEBAND-MIB contains objects that support Wideband DOCSIS and Channel Bonding Protocol on the Cable Modem Termination System (CMTS). Wideband DOCSIS enhances per-cable-modem data rates that exceed the bandwidth of a single 256QAM downstream channel.
The MODULE-IDENTITY for the CISCO-CABLE-WIDEBAND-MIB is ciscoCableWidebandMIBObjects and its top-level OID is 1.3.6.1.4.1.9.9.479.
Wideband DOCSIS simultaneously transmits DOCSIS data over multiple RF channels thereby improving the downstream bandwidth. This DOCSIS data is organized as a sequence of 188-byte MPEG-TS data packets. A wideband channel or bonded group is a logical grouping of one or more physical RF channels over which MPEG-TS packets are carried. The wideband channel carries DOCSIS-bonded packets encapsulated in MPEG-TS packets from a Wideband Cisco CMTS to one or more wideband cable modems.
Narrowband and Wideband Channels in Cisco IOS 12.2(33)SCB and Later Releases
Commencing in Cisco IOS Release 12.3(23)BC and later releases, the Cisco CMTS supports a narrowband channel in a standard DOCSIS downstream channel containing exactly one RF channel. The fiber node in a narrowband channel is an optical node that terminates the fiber-based downstream signal as an electrical signal onto a coaxial RF cable. This type of narrowband channel is distinct from another new narrowband channel that applies to the Shared Port Adaptor (SPA) downstream channel.
Narrowband in Cisco IOS 12.3(23)BC and later releases, has been enhanced to support two tables in the CISCO-CABLE-WIDEBAND-MIB:
•ccwbWBtoRFMappingTable
•ccwbWBtoNBMappingTable
These MIB objects correspond to the two following privileged EXEC commands:
•For SPA
–show hw-module bay all mapping wideband-channel
–show hw-module bay all association wideband-channel
•For MC20x20 (beginning from Cisco IOS Release 12.2(33)SCC )
–show controllers Integrated-Cable slot/subslot/bay mapping wb-channel
–show controllers Integrated-Cable slot/subslot/bay association
•For MC3Gx60 (beginning from Cisco IOS Release 12.2(33)SCE )
–show controllers Modular-Cable slot/subslot/bay mapping wb-channel
–show controllers Modular-Cable slot/subslot/bay association
•For MC8x8 (beginning from Cisco IOS Release 12.2(33)SCD)
–show controllers Integrated-Cable slot/unit mapping wb-channel
–show controllers Integrated-Cable slot/unit association
To support the EQAM RF channel utilization feature, two new objects have been added to CISCO-CABLE-WIDEBAND-MIB. These two objects are:
•ccwbRFChannelUtilization: Added under ccwbRFChannelTable, this object indicates the current utilization of RF channel in percentage. The value of this object ranges from 1 to 100. The ccwbRFChannelUtilization object is read-only.
•ccwbRFChanUtilInterval: A global object, it contains the polling interval for calculating the RF channel utilization. To start utilization polling, you need to configure this object using the SNMP set command. When the ccwbRFChanUtilInterval object is set, a background CMTS process periodically calculates the utilization for each valid RF channel. The value of this object persists across CMTS reboots.
Note Use cable util-interval interval command to update docsIfCmtsChannelUtilizationInterval/ccwbRFChanUtilInterval attribute value.
The value of docsIfCmtsChannelUtilizationInterval ranges from 1 - 86400 seconds. Table 3-9 lists the tables/IPDR schemas affected by docsIfCmtsChannelUtilizationInterval attribute:
Table 3-9 Tables/IPDR Schemas Affected by docsIfCmtsChannelUtilizationInterval Attribute
Table/IPDR Schema
|
Impact
|
docsIfCmtsChannelUtilizationInterval/ccwbRFChanUtilInterval
|
New utilization value is based on the value derived from CLI.
|
docsIfCmtsChannelUtUtilization/ccwbRFChannelUtilization
|
New utilization value is calculated using the new interval value.
|
US-UTIL/DS-UTIL
|
These two IPDR schemas use new interval to calculate channel utilization.
|
Note Although the value of docsIfCmtsChannelUtilizationInterval ranges from 1 - 86400 sec, we suggest to choose a value greater than 300 sec (five minutes).
MIB Notes and Constraints
Table 3-10 lists the constraints that the router places on CISCO-CABLE-WIDEBAND-MIB.
.
Table 3-10 CISCO-CABLE-WIDEBAND-MIB Constraints
MIB Object
|
Notes and Constraints
|
ccwbRFChanUtilInterval
|
|
ccwbRFChannelTable
|
This table contains attributes of the physical RF channels.
|
•ccwbRFChannelFrequency
|
Unsigned32.
Note A range of 54 MHz to 860 MHz is appropriate for a cable plant using a North American Sub-Split channel plan. The spectrum range has been expanded to accommodate a lower edge of 47 MHz and an upper edge of 862 MHz for some European channel plants.
|
•ccwbRFChannelWidth
|
Read-only.
Note The value of 6 MHz is appropriate for cable plants running under NTSC (National Television Standards Committee) standards. The value of 8 MHz is appropriate for cable plants running under ETSI standards.
|
•ccwbRFChannelRowStatus
|
The valid values are:
•active(1)
•createAndGo(4)
•destroy(6)
|
•ccwbRFChannelAnnex
|
Read-create. Value must be the same for all RF channels.
|
•ccwbRFChannelModulation
|
Read-create. Value must be the same for all RF channels.
|
•ccwbRFChannelStorageType
|
Value is volatile(2).
|
•ccwbRFChannelNum
|
Unsigned32
|
•ccwbRFChannelMpegPkts
|
Read-only. Counter64
|
•ccwbRFChannelUtilization
|
Read-only.
|
ccwbRFChannelQamTable
|
This table contains information of the external edge QAM which provide the physical RF channels which are available to the wideband channels.
|
•ccwbRFChanQamTos
|
Not implemented.
|
•ccwbRFChanQamVlanId
|
Not implemented.
|
•ccwbRFChanQamPriorityBits
|
Not implemented.
|
•ccwbWBtoNBRowStatus
|
Read-only.
|
•ccwbWBtoNBStorageType
|
Values:
•volatile(2).
•Read-only.
|
•ccwbRFChanQamIPAddressType
|
Only Internet address type ipv4 is supported.
|
ccwbWBtoRFMappingTable
|
This table contains association information of the wideband channels to RF channels available for WCMTS. This converts to a read-only table.
|
•ccwbWBtoRFStorageType
|
The valid value is volatile(2).
|
•ccwbWBtoRFRowStatus
|
The valid values are:
•active(1)
•createAndGo(4)
•destroy(6)
|
ccwbFiberNodeDescrTable
|
This table contains the description of a fiber node on a CMTS.
|
•ccwbFiberNodeDescription
|
Read-only.
|
•ccwbFiberNodeDescrStorageType
|
The valid values are:
•volatile(2).
•Read-only.
|
• ccwbFiberNodeDescrRowStatus
|
Read-only.
|
ccwbFiberNodeTable
|
This is a read-only table which provides configuration and topology information for each Fiber node, such as, Narrowband Ifindex, Wideband controller Index and the Wideband rf-ports
|
•ccwbFiberNodeNBIfIndx
|
Read-only.
|
• ccwbFiberNodeWBContlrPhyIndx
|
Read-only.
|
•ccwbFiberNodeWBRFPort
|
Read-only.
|
•ccwbFiberNodeStorageType
|
The valid values are:
•volatile(2).
•Read-only.
|
•ccwbFiberNodeRowStatus
|
Read-only.
|
ccwbWBCmStatusTable
|
This table contains wideband cable connectivity status .
|
•ccwbWBCmStatusValue
|
Read-only.
|
ccwbWBBondGrpTable
|
This table provides information on either a primary or non-primary interface for the Wideband Interface.
|
•ccwbWBBondGrpSecondary
|
The valid values are:
• true(1) if the wideband interface (bond group) is secondary
•false(2) for non-secondary
|
ccwbWBtoRFMappingTable
|
This table maps the Wideband Fiber Node and associated interfaces to the RF downstream.
This table is supported only in Cisco IOS Release 12.3(23)BC or later on the Cisco uBR10012 router.
This MIB table corresponds to the show hw-module bay all mapping wideband-channel privileged EXEC command.
|
ccwbWBtoNBMappingTable
|
This table maps the Wideband interfaces to the Narrowband Fiber Node for downstream channels.
This table is supported only in Cisco IOS Release 12.3(23)BC or later on the Cisco uBR10012 router.
This MIB table corresponds to the show hw-module bay all association wideband-channel privileged EXEC command.
|
|
|
CISCO-CALL-HISTORY-MIB
The CISCO-CALL-HISTORY-MIB contains objects about the information that is stored in the router's call history table, which keeps a record of the calls made on the router.
The MODULE-IDENTITY for the CISCO-CALL-HISTORY-MIB is ciscoCallHistoryMib, and its top-level OID is 1.3.6.1.4.1.9.9.27 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCallHistoryMib).
MIB Constraints
This MIB is not supported on the Cisco uBR10012 router.
CISCO-CAR-MIB
The CISCO-CAR-MIB contains objects that provide information about the operation of packet filtering on the interfaces that use weighted rate-limiting, which is also known as the committed access rate (CAR).
The MODULE-IDENTITY for the CISCO-CAR-MIB is ciscoCarMIB, and its top-level OID is 1.3.6.1.4.1.9.9.113 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCarMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-CASA-FA-MIB
The CISCO-CASA-FA-MIB supplements the CISCO-CASA-MIB, containing additional objects to manage a Cisco Appliance Services Architecture (CASA) forwarding agent (FA).
The MODULE-IDENTITY for the CISCO-CASA-FA-MIB is ciscoCasaFaMIB, and its top-level OID is 1.3.6.1.4.1.9.9.115 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCasaFaMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is supported only on Cisco uBR7100 series and Cisco uBR7200 series routers that are running a Cisco IOS "-is-" software image.
•This MIB is not supported on the Cisco uBR10012 router.
CISCO-CASA-MIB
The CISCO-CASA-MIB contains the objects needed to manage a Cisco Appliance Services Architecture (CASA) entity, which can be either a manager agent or forwarding agent.
The MODULE-IDENTITY for the CISCO-CASA-MIB is ciscoCasaMIB, and its top-level OID is 1.3.6.1.4.1.9.9.122 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCasaMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is supported only on Cisco uBR7100 series and Cisco uBR7200 series routers that are running a Cisco IOS "-is-" software image.
•This MIB is not supported on the Cisco uBR10012 router.
CISCO-CDP-MIB
The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router, and to display the contents of the CDP neighbor table.
The MODULE-IDENTITY for the CISCO-CDP-MIB is ciscoCdpMIB, and its top-level OID is 1.3.6.1.4.1.9.9.23 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCdpMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-CIRCUIT-INTERFACE-MIB
The CISCO-CIRCUIT-INTERFACE-MIB contains objects to manage circuits on circuit-based interfaces, such as ATM or Frame Relay.
The MODULE-IDENTITY for the CISCO-CIRCUIT-INTERFACE-MIB is ciscoCircuitInterfaceMIB, and its top-level OID is 1.3.6.1.4.1.9.9.160 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCircuitInterfaceMIB).
MIB Constraints
This MIB is not supported in any Cisco IOS Release 12.1EC software image.
CISCO-CLASS-BASED-QOS-MIB
The CISCO-CLASS-BASED-QOS-MIB provides access to quality of service (QoS) configuration information and statistics. The MIB uses several indexes to identify QoS features and distinguish among instances of those features:
•cbQosPolicyIndex— Uniquely identifies a service policy attached to a logical interface.
•cbQosObjectsIndex— Uniquely identifies each QoS feature on a Cisco uBR7200 and the uBR10k routers.
•cbQosConfigIndex—Uniquely identifies a type of QoS configuration. This index is shared by QoS objects that have identical configurations.
The indexes cbQosPolicyIndex and cbQosObjectsIndex are assigned by the system to uniquely identify each instance of a QoS feature.
Note Do not reuse these indexes between router reboots, even if the QoS configuration changes.
QoS information is stored in:
•Configuration objects—Might have multiple identical instances. Multiple instances of the same QoS feature share a single configuration object, which is identified by cbQosConfigIndex.
•Statistics objects—Each has a unique run-time instance. Multiple instances of a QoS feature have a separate statistics object. Run-time instances of QoS objects are each assigned a unique identifier (cbQosObjectsIndex) to distinguish among multiple objects with matching configurations.
The MODULE-IDENTITY for the CISCO-CLASS-BASED-QOS-MIB is ciscoCBQosMIB, and its top-level OID is 1.3.6.1.4.1.9.9.166 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCBQosMIB).
MIB Constraints
Table 3-11 lists the constraints that the router places on objects in the CISCO-CLASS-BASED-QOS-MIB. For detailed definitions of MIB objects, see the standard MIB file. Any MIB table or object not listed in this table is implemented as defined in the MIB.
Table 3-11 CISCO-CLASS-BASED-QOS-MIB Constraints for the uBR7200 Series Router
MIB Object
|
Notes
|
cbQosServicePolicyTable
|
|
•cbQosFrDLCI
|
Not supported. Always 0.
|
•cbQosAtmVCI
|
Not supported. Always 0.
|
•cbQosAtmVPI
|
Not supported. Always 0.
|
cbQosInterfacePolicyTable
|
|
•cbQosInterfacePolicyIndex
|
Not supported. Always 0.
|
cbQosFrameRelayPolicyTable
|
|
•cbQosFRPolicyIndex
|
Not supported. Always 0.
|
cbQosATMPVCPolicyTable
|
|
•cbQosATMPolicyIndex
|
Not supported. Always 0.
|
cbQosQueueingCfgTable
|
|
•cbQosQueueingCfgFlowEnabled·
|
Not supported. Always false(2).
|
•cbQosQueueingCfgIndividualQSize·
|
Not supported. Always 0.
|
•cbQosQueueingCfgDynamicQNumber·
|
Not supported. Always 0.
|
•cbQosQueueingCfgPrioBurstSize
|
Not supported. Always 0.
|
cbQosREDCfgTable
|
|
•cbQosREDCfgMeanQsize
|
Not supported for PRE1. Always 0.
|
•cbQosREDCfgDscpPrec
|
DSCP-based is not supported.
|
cbQosREDClassCfgTable
|
If IP precedence is configured for the policy:
•For PRE1, this table contains entries for all seven IP precedences. The MIB objects in cbQosREDClassCfgEntry contains 0 if IP precedence is not configured for the policy.
For PRE2, this table contains an entry for the configured IP precedence.
|
cbQosTSCfgTable
|
|
•cbQosTSCfgBurstSize
|
Not supported. Always 0.
|
•cbQosTSCfgExtBurstSize
|
Not supported. Always 0.
|
•cbQosTSCfgAdaptiveEnabled
|
Not supported. Always false(2).
|
•cbQosTSCfgAdaptiveRate
|
Not supported. Always 0.
|
•cbQosTSCfgLimitType
|
Not supported. Always average(1).
|
cbQosCMStatsTable
|
|
•cbQosCMDropByte64
|
Not supported. Always 0.
|
•cbQosCMDropByteOverflow
|
Not supported. Always 0.
|
•cbQosCMDropByte
|
Not supported. Always 0.
|
cbQosPoliceStatsTable
|
|
•cbQosPoliceConformedBitRate
|
Not supported. Always 0.
|
•cbQosPoliceExceededBitRate
|
Not supported. Always 0.
|
•cbQosPoliceViolatedBitRate
|
Not supported. Always 0.
|
cbQosQueueingStatsTable
|
|
•cbQosQueueingDiscardByte64
|
Not supported. Always 0.
|
•cbQosQueueingDiscardByteOverflow
|
Not supported. Always 0.
|
•cbQosQueueingDiscardByte
|
Not supported. Always 0.
|
cbQosTSStatsTable
|
|
•cbQosTSStatsDelayedByteOverflow·
|
Not supported. Always 0.
|
•cbQosTSStatsDelayedByte
|
Not supported. Always 0.
|
•cbQosTSStatsDelayedByte64
|
Not supported. Always 0.
|
•cbQosTSStatsDelayedPktOverflow
|
Not supported. Always 0.
|
•cbQosTSStatsDelayedPkt·
|
Not supported. Always 0.
|
•cbQosTSStatsDelayedPkt64
|
Not supported. Always 0.
|
•cbQosTSStatsDropByteOverflow
|
Not supported. Always 0.
|
•cbQosTSStatsDropByte
|
Not supported. Always 0.
|
•cbQosTSStatsDropByte64
|
Not supported. Always 0.
|
•cbQosTSStatsActive
|
Not dynamic. If traffic shaping is configured, then cbQosTSStatsActive is true(1); otherwise, it is false(2).
|
cbQosREDClassStatsTable
|
|
•cbQosREDRandomDropPktOverflow
•cbQosREDRandomDropPkt
•cbQosREDRandomDropPkt64
|
Counts are recorded per class, not per cbQosREDValue (IP precedence). All counters with the same cbQosPolicyIndex and cbQosObjectsIndex contain the same count.
|
•cbQosREDRandomDropByteOverflow
•cbQosREDRandomDropByte
•cbQosREDRandomDropByte64
|
Not supported. Always 0.
|
•cbQosREDTailDropPktOverflow
•cbQosREDTailDropPkt
•cbQosREDTailDropPkt64
|
Counts are recorded per class, not per cbQosREDValue (IP precedence). All counters with the same cbQosPolicyIndex and cbQosObjectsIndex contain the same count.
|
•cbQosREDTailDropByteOverflow
•cbQosREDTailDropByte
•cbQosREDTailDropByte64
|
Not supported. Always 0.
|
•cbQosREDTransmitPktOverflow
•cbQosREDTransmitPkt
•cbQosREDTransmitPkt64
•cbQosREDTransmitByteOverflow
•cbQosREDTransmitByte
•cbQosREDTransmitByte64
|
Counts are recorded per class, not per cbQosREDValue (IP precedence). All counters with the same cbQosPolicyIndex and cbQosObjectsIndex contain the same count.
|
CISCO-COMPRESSION-SERVICE-ADAPTER-MIB
The CISCO-COMPRESSION-SERVICE-ADAPTER-MIB contains objects with statistics and status information for hardware-based compression service adapters that are installed in the router.
The MODULE-IDENTITY for the CISCO-COMPRESSION-SERVICE-ADAPTER-MIB is ciscoCompressionServiceAdapterMIB, and its top-level OID is 1.3.6.1.4.1.9.9.57 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCompressionServiceAdapterMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB exists on Cisco uBR7100 series and Cisco uBR7200 series routers, but is not supported because these routers do not support any compression service adapter line cards.
•This MIB is not supported on the Cisco uBR10012 router.
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
•Copy the running configuration to the startup config and startup to running
•Copy the startup or running configuration files to and from a local Cisco IOS file system
The MODULE-IDENTITY for the CISCO-CONFIG-COPY-MIB is ciscoConfigCopyMIB, and its top-level OID is 1.3.6.1.4.1.9.9.96 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoConfigCopyMIB).
MIB Constraints
Table 3-12 lists the constraints that the router places on CISCO-CONFIG-COPY-MIB.
.
Table 3-12 CISCO-CONFIG-COPY-MIB Constraints
MIB Object
|
Notes
|
ccCopyTable
|
|
•ccCopyProtocol
|
Only the Trivial File Transfer Protocol (tftp[1]), is supported. The File Transfer Protocol (ftp[2]) and remote copy protocol (rcp([3]) are not supported.
|
•ccCopySourceFileType
ccCopyDestFileType
|
The values iosFile(2) and terminal(5) are not supported for source and destination file types.
|
•cCopyUserName and ccCopyUserPassword
|
Not supported, because it is only valid when FTP and Remote Copy Protocol (RCP) are supported.
|
CISCO-CONFIG-MAN-MIB
The CISCO-CONFIG-MAN-MIB contains objects to track and save changes to the router configuration. The MIB represents a model of the configuration data that exists elsewhere in the router and in peripheral devices. Its main purpose is to report changes to the running configuration through the SNMP notification ciscoConfigManEvent.
The MODULE-IDENTITY for the CISCO-CONFIG-MAN-MIB is ciscoConfigManMIB, and its top-level OID is 1.3.6.1.4.1.9.9.43 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoConfigManMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-DOCS-EXT-MIB
The CISCO-DOCS-EXT-MIB contains objects that support extensions to the Data-over-Cable Service Interface Specifications (DOCSIS) interface MIB, DOCS-IF-MIB. In addition, this MIB:
•Includes attributes to configure the dynamic shared secret (DMIC) feature
•Generate traps when a cable modem fails the shared-secret security checks
•Allows the CMTS to help ensure that every online cable modem uses the DOCSIS configuration file assigned to it
This support protects against theft-of-service attempts from subscribers and safeguards operators against stolen or fraudulently downloaded configuration files. Configuration files are signed with a shared secret that is verified when a cable modem connects to the CMTS.
This MIB includes objects to manage the Cisco CMTS, as well as to manage the following:
•Quality of service (QoS) configuration on the router.
•DOCSIS 1.0 cable modems and customer premises equipment (CPE) devices, including counters for the number of cable modems on each interface.
•Spectrum management of the upstream channels—Objects that keep count of the total # of modems, # of registered and # of active modems on the interface as well as each upstream.
•CM CPE (customer premises equipment) information—Two new tables have been added to the CISCO-DOCS-EXT-MIB to query CPE information:
–cdxCmToCpeTable contains objects about CPE connects behind cable modem. It provides information on IP address and IP address type of each CPE connect to a CM.
–cdxCpeToCmTable contains objects that query information about cable modems with CPE connects.
•In Cisco IOS Release 12.2(33)SCE, cdxCmCpeDeleteNow object has been added to the cdxCmCpeTable. This is a read/write object. When set to true(1), it deletes the CM/CPE. It performs the same function as the following CLI:
clear cable modem xxx delete
For more information on cdxCmCpeDeleteNow object, see "Cable Modem and Customer Premises Equipment Information (cdxCmCpeTable)" in Table B-6 on page B-5.
Note This MIB provides information for DOCSIS 1.0 cable modems. For DOCSIS 1.1 cable modems, see DOCS-QOS-MIB.
The MODULE-IDENTITY for the CISCO-DOCS-EXT-MIB is ciscoDocsExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.116.1.3.7 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoDocsExtMIB). One of the most commonly used OID is ccsFlapObjects.ccsFlapTable.ccsFlapEntry.ccsFlapInsertionFails (1.3.6.1.4.1.9.9.114.1.1.5.1.4).
Wideband Support in Cisco IOS Release 12.2(33)SCC
The CISCO-DOCS-EXT-MIB includes objects for the scheduler that support Quality of Service (QoS) of MCNS/DOCSIS compliant Radio Frequency (RF) interfaces. This MIB also shows various states of the schedulers enabling you to monitor of the current status of the schedulers.
•RateLimit: The MC interface layer is not supported.
•Bandwidth Queue: This is only supported on the Cable interface upstream, and there is no downstream support for MC interfaces.
MIB Tables
Table 3-13 lists the tables in CISCO-DOCS-EXT-MIB.
Table 3-13 CISCO-DOCS-EXT-MIB Tables
MIB Tables
|
Description
|
cdxQosCtrlUpTable
|
Maintains a number of objects related to Quality of Service scheduler, for each upstream interface, which uses these attributes to control cable modem registration.
|
cdxQosIfRateLimitTable
|
Contains the attributes of rate limiting for schedulers in cable upstream and downstream interfaces that support Quality of Service. The rate limiting process is to ensure the Quality of Service and fairness.
|
cdxCmtsServiceExtTable
|
Contains the additional attributes of a single Service ID that provided by docsIfCmtsServiceEntry.
|
cdxUpInfoElemStatsTable
|
Contains the attributes of a particular Information Element type for each instance of the MAC scheduler. It is indexed by upstream ifIndex. An Entry exists for each ifEntry with ifType of docsCableUpstream(129) Since each upstream has an instance of a MAC Scheduler so this table has the per MAC scheduler slot information on a per Information Element basis.
|
cdxBWQueueTable
|
Contains the attributes of queues in cable interfaces schedulers that support Quality of Service.
|
cdxCmCpeTable
|
Contains information about cable modems (CM) or Customer Premises Equipments (CPE).
|
cdxCmtsCmStatusExtTable
|
Contains the additional CM status information.
|
cdxCmtsMacExtTable
|
Contains the additions attributes of a CMTS MAC interface that provided by docsIfCmtsMacTable.
|
cdxCmtsCmChOverTable
|
Contains CMTS operation entries to instruct cable modems to move to a new downstream and/or upstream channel. An entry in this table is an operation that has been initiated from CMTS to generates downstream frequency and/or upstream channel override fields in the RNG-RSP message sent to a cable modem. A RNG-RSP message is sent to a cable modem during initial maintenance opportunity. This operation causes the uBR to place an entry for the cable modem specified into the override request queue. The link is then broken by deleting the modem from its polling list. When the modem attempts initial ranging, the override request causes downstream frequency and upstream channel override fields to be inserted into the RNG-RSP message.
|
cdxCmtsCmTable
|
Contains attributes or configurable parameters for cable modems from a CMTS.
|
cdxCmtsCmStatusDMICTable
|
Contains the list of modems which failed the CMTS Dynamic Message Integrity Check (DMIC). The modems are either Marked: The modems failed the DMIC check but were still allowed to come online.
Locked: The modems failed the DMIC check and hence were allowed to come online with a restrictive QoS profile as defined in cdxCmtsCmDMICLockQos.
Rejected: The modems failed the DMIC check and hence were not allowed to come online. Another objective of the objects in this table is to clear the lock on the modems.
|
cdxCmToCpeTable
|
Contains information about CPE connects behind cable modem. It will return IP address and IP address type of each CPE connect to a CM. It is not intended to walk the whole table. An application would need to query this table based on the specific indices. Otherwise, it will impact the CMTS performance due to the huge size of this table. The agent creates/destroys/modifies an entry whenever there is a CPE connect to a cable modem or disconnect from a cable modem.
|
cdxCpeToCmTable
|
Contains information about cable modems with CPE connects to. It is not intended to walk the whole table. An application would need to query this table base on the specific index. Otherwise, it will impact the CMTS performance due to the huge size of this table. The agent creates/destroys/modifies an entry whenever there is update for the cable modem that CPE connects to.
|
cdxIfUpstreamChannelExtTable
|
Contains upstream channel attributes for automated Spectrum management, in addition to the ones provided by docsIfUpstreamChannelEntry. It also contains upstream channel attributes to count the number of active, registered and total number of cable modems on this upstream.
|
MIB Constraints
Table 3-14 lists the constraints that the router places on CISCO-DOCS-EXT-MIB.
.
Table 3-14 CISCO-DOCS-EXT-MIB Constraints
MIB Object
|
Notes
|
cdxCmToCpeTable
|
|
cdxCpeToCmTable
|
|
cdxCmCpeTable
|
Using GET-NEXT requests to retrieve the rows of this table might require lengthy, time-consuming searches on the MAC address, which could consume excessive amounts of CPU processor time when the table is large.
Retrieve the individual rows using a GET request that uses the device's MAC address as the table index. This avoids possible performance problems and also ensures that the retrieved rows contain the most current, real-time data for those devices.
|
cdxCmCpeAccessGroup
|
The Cisco uBR10012 router does not support the objects in cdxCmCpeAccessGroup (equivalent to the cable host access-group command). On the Cisco uBR10012 router, use the similar functionality in the DOCS-SUBMGT-MIB.
|
cdxIfUpChannelTable
|
|
•cdxIfUpChannelNumActiveUGS cdxIfUpChannelMaxUGSLastOneHour cdxIfUpChannelMinUGSLastOneHour cdxIfUpChannelAvgUGSLastOneHour cdxIfUpChannelMaxUGSLastFiveMins cdxIfUpChannelMinUGSLastFiveMins
cdxIfUpChannelAvgUGSLastFiveMins
|
These objects related to Unsolicited Grant Service (UGS) flows are supported only in Cisco IOS Release 12.1(8)EC, Cisco IOS Release 12.2(15)BC1a, and later releases.
|
• cdxIfUpChannelAvgLastOneHour
|
Displays accurate values only in Cisco IOS Release 12.1(8)EC, Cisco IOS Release 12.2(15)BC1a, and later releases
|
cdxCmtsServiceExtTable
|
Reports the downstream traffic counters only for cable modems that are provisioned for DOCSIS 1.0 operation. For DOCSIS 1.1 and DOCSIS 2.0 cable modems, use the docsQosServiceFlowStatsTable in DOCS-QOS-MIB.
|
cdxCmtsCmTable
|
|
•cdxCmtsCmQosProfile
|
Associating a cable modem to a QoS profile is supported only in Cisco IOS Release 12.1(19)EC and Release 12.2(11)BC2 and later releases.
|
•cdxCmCpeEntry
|
When a Cisco uBR7100 series router is running in bridging mode, it is possible for the same IP address to appear for different MAC addresses in the cdxCmCpeEntry rows. This occurs when the first device goes offline, and its IP address is given to a second device.
Because the router is in bridging mode, it cannot extract the IP addresses from DHCP requests, and so assumes all IP addresses are static. This is expected behavior while in bridging mode and does not occur when the router is operating in the default behavior of routing mode.
•A GET request for cdxCmCpeEntry returns NULL if the router is already processing another request for this table (either by an SNMP GET or CLI show command).
•A null is also returned if the router is processing a request for any other table that is indexed by cable modem or CPE MAC address, such as cdrqCmtsCmStatusTable, docsIfCmtsMacToCmTable, and docsQosCmtsMacToSrvFlowTable. Wait until the first request is done and then repeat the request for cdxCmCpeEntry.
|
cdxCmtsCmStatusExtTable
|
|
• cdxIfCmtsCmStatusLastResetTime
|
|
• cdxIfCmtsCmStatusOnlineTimesNum
|
|
cdxCmtsCmStatusDMICTable
|
This table contains the list of modems which failed the CMTS Dynamic Message Integrity Check (DMIC).
|
• cdxCmtsCmDMICMode
|
The DMIC feature operates in the following modes, depending on what action should be taken for cable modems that fail the CMTS DMIC verification check:
•notConfigured(1)—Indicates that the DMIC is not configured for this cable interface.
•mark(2)—By default, the DMIC feature is enabled on all cable interfaces using the mark option. In this mode, the CMTS allows cable modems to come online even if they fail the CMTS DMIC validity check.
•lock(3)—When the lock option is used, the CMTS assigns a restrictive QoS configuration to CMs that fail the DMIC validity check twice in a row.
A particular QoS profile is used for locked cable modems and is specified by setting cdxCmtsCmDMICLockQos. If a customer resets their CM, the CM reregisters but still uses the restricted QoS profile. A locked CM continues with the restricted QoS profile until it goes offline and remains offline for at least 24 hours, at which point it is allowed to reregister with a valid DOCSIS configuration file. A system operator can manually clear the lock on a CM by setting the cdxCmtsCmStatusDMICUnLock object.
•reject(4)—In the reject mode, the CMs cannot go online if they fail the CMTS DMIC validity check.
|
• cdxCmtsCmDMICLockQos
|
If cdxCmtsCmDMICMode is set to lockingMode(3), this object would contain the restrictive QoS profile number as indicated by docsIfQosProfIndex if set and a value of zero (0) if not applicable or not defined.
If cdxCmtsCmDMICMode is set to lockingMode(3) and this object is not defined, then the CMTS defaults to special QoS profile that limits the downstream and upstream service flows to a maximum rate of 10 kbps. However, for this to happen the modems should have the permission to create a QoS profile.
|
CISCO-DOCS-REMOTE-QUERY-MIB
The CISCO-DOCS-REMOTE-QUERY-MIB contains the objects that are monitored and collected by the remote query feature, which is enabled using the cable modem remote-query command on the Cisco CMTS.
The MODULE-IDENTITY for the CISCO-DOCS-REMOTE-QUERY-MIB is ciscoDocsRemoteQueryMIB, and its top-level OID is 1.3.6.1.4.1.9.10.59 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoDocsRemoteQueryMIB). One of the most commonly used OID is cdrqCmtsCmSigQSignalNoise (1.3.6.1.4.1.9.10.59.1.2.1.1.4).
MIB Constraints
This MIB has the following constraints.
•This MIB is supported only in Cisco IOS Release 12.2(4)BC1 and later releases.
•This MIB is not supported on the Cisco uBR10012 router.
Table 3-15 lists the constraint that the router places on CISCO-DOCS-REMOTE-QUERY-MIB.
.
Table 3-15 CISCO-DOCS-REMOTE-QUERY-MIB Constraints
MIB Object
|
Notes
|
cdrqCmtsCmStatusTable
|
We do not recommend using GET-NEXT requests to retrieve the rows of this table, because it could require lengthy, time-consuming searches on the MAC address, which could consume excessive amounts of CPU processor time when the table is large.
Retrieve the individual rows using a GET request that uses the device's MAC address as the table index. This prevents possible performance problems and also ensures that the retrieved rows contain the most current, real-time data for those devices.
|
| |
A GET request for cdrqCmtsCmStatusTable returns NULL if the router is already processing another request for this table (either by an SNMP GET or CLI show command).
A null is also returned if the router is processing a request for any other table that is indexed by CM or CPE MAC address, such as cdxCmCpeEntry, docsIfCmtsMacToCmTable, and docsQosCmtsMacToSrvFlowTable. Wait until the first request is done and then repeat the request for cdrqCmtsCmStatusTable.
|
CISCO-ENHANCED-MEMPOOL-MIB
The CISCO-ENHANCED-MEMPOOL-MIB contains objects to monitor the status of memory pools of all physical entities in a system, including line cards that contain their own onboard processors and memory.
The CISCO-ENHANCED-MEMPOOL-MIB enables you to monitor CPU and memory utilization for cable line cards and broadband processing engines (BPEs) on the Cisco uBR10012 routers. These would include the Cisco MC16X and Cisco MC28X series line cards.
The MODULE-IDENTITY for the CISCO-ENHANCED-MEMPOOL-MIB is ciscoEnhancedMemPoolMIB, and its top-level OID is 1.3.6.1.4.1.9.9.221 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnhancedMemPoolMIB).
MIB Constraints
This MIB is supported only in Cisco IOS Release 12.3(9a)BC and later releases.
CISCO-ENTITY-ALARM-MIB
The CISCO-ENTITY-ALARM-MIB enables the router to monitor alarms generated by system components, such as the chassis, slots, modules, power supplies, fans, and module ports.
Note The CISCO-ENTITY-ALARM-MIB monitors the alarms of physical entities.
MIB Constraints
Table 3-16 lists the constraints that the router places on objects in the CISCO-ENTITY-ALARM-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-16 CISCO-ENTITY-ALARM-MIB Constraints
MIB Object
|
Notes
|
ceAlarmDescrTable
|
Read-only.
|
ceAlarmFilterProfileTable
|
Not implemented.
|
ceAlarmCutOff
|
Not implemented.
|
CISCO-ENTITY-ASSET-MIB
The CISCO-ENTITY-ASSET-MIB provides asset tracking information for the physical components in the ENTITY-MIB entPhysicalTable. The ceAssetTable object is automatically updated whenever a line card is removed or inserted into a slot, or when you enter a command at the CLI prompt that affects the operation of a line card.
The MODULE-IDENTITY for the CISCO-ENTITY-ASSET-MIB is ciscoEntityAssetMIB, and its top-level OID is 1.3.6.1.4.1.9.9.92 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEntityAssetMIB).
MIB Constraint
This MIB is not supported on any Cisco CMTS platforms, although it is included in the Cisco IOS software images.
CISCO-ENTITY-EXT-MIB
The CISCO-ENTITY-EXT-MIB contains objects that supplement the entityPhysicalTable in the ENTITY-MIB (RFC 2737). These objects provide information about entries in the entityPhysicalTable that have a CPU or other type of onboard processor.
The MODULE-IDENTITY for the CISCO-ENTITY-EXT-MIB is ciscoEntityExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.195 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEntityExtMIB).
MIB Constraints
This MIB has the following constraints:
•This MIB is only supported for the physical entities representing active and standby processors.
•The set operations of ceExtConfigRegNext and ceExtSysBootImageList are only supported on the physical entity representing the active Route Processor (RP).
•Because the ceExtSysBootImageList for the secondary RP is returned from the bootvar (To display information about the BOOT environment variable), the secondary route processor ceExtSysBootImageList is only updated from the active route processor when configuration is synced from the active router processor. Use the write memory command to force the sync process.
CISCO-ENTITY-FRU-CONTROL-MIB
The CISCO-ENTITY-FRU-CONTROL-MIB contains objects that supplement the entityPhysicalTable in the ENTITY-MIB (RFC 2737). These objects provide information about the configuration and operational status of entries in the entityPhysicalTable that are field-replaceable units (FRUs).
The cefcModuleTable object is automatically updated whenever a line card is removed or inserted into a slot or when you enter a command at the CLI prompt that affects the operation of the line card.
The MODULE-IDENTITY for the CISCO-ENTITY-FRU-CONTROL-MIB is ciscoEntityFRUControlMIB, and its top-level OID is 1.3.6.1.4.1.9.9.117 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEntityFRUControlMIB).
MIB Constraints
Table 3-17 lists the constraints that the router places on objects in the CISCO-ENTITY-FRU-CONTROL-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-17 CISCO-ENTITY-FRU-CONTROL-MIB Constraints
MIB Object
|
Notes
|
cefcModuleTable
|
|
•cefcModuleAdminStatus
|
Supported values:
•Enable(1)
•Reset(3)
Write is not supported.
|
•cefcModuleOperStatus
|
Supported values:
•Unknown(1)—Read-only.
•Ok(2)—Read-only.
•Failed(7)—Read-only.
|
•cefcModuleResetReason
|
Supported values:
•Unknown(1)—Read-only.
•PowerUp(2)—Read-only.
•ManualReset(5)—Read-only.
|
cefcFRUPowerSupplyGroupTable
|
Not supported.
|
cefcFRUPowerSupplyTable
|
Not supported.
|
•cefcMaxDefaultInLinePower
|
Not supported.
|
•cefcPowerStatusChange
|
Not supported.
Use ciscoEnvMonSuppStatusChangeNotif for redundant power supply.
|
|
|
CISCO-ENTITY-SENSOR-MIB
The CISCO-ENTITY-SENSOR-MIB defines objects that supplement the entityPhysicalTable for physical sensors in the ENTITY-MIB (RFC 2737). These objects provide additional information about the entries in the entityPhysicalTable, such as temperature sensors. This MIB also implements DOCSIS Baseline Privacy Interface Plus (BPI+) functionality for CMs and CMTSs. The entPhySensorTable object is defined to support DOCSIS BPI+ functionality. This object contains a row for each physical sensor and is associated with entPhysicalTable.
The MODULE-IDENTITY for the CISCO-ENTITY-SENSOR-MIB is entitySensorMIB and its top-level OID is 1.3.6.1.4.1.9.9.91 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.entitySensorMIB).
MIB Constraints
The CISCO-ENTITY-SENSOR-MIB has the following constraints:
•This MIB is supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers.
•This MIB is not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router. For temperature reporting, use the CISCO-ENVMON-MIB.
CISCO-ENTITY-VENDORTYPE-OID-MIB
The CISCO-ENTITY-VENDORTYPE-OID-MIB defines the object identifiers (OIDs) assigned to components in the Cisco CMTS routers. The OIDs in this MIB are used in the ENTITY-MIB as values for the entPhysicalVendorType field in entPhysicalTable. Each OID uniquely identifies a type of physical entity (for example, a fan tray, power supply, or card).
Note This MIB is regularly updated with OIDs for new components in the Cisco IOS software release that introduced support for those components.
The MODULE-IDENTITY for the CISCO-ENTITY-VENDORTYPE-OID-MIB is ciscoEntityVendortypeOIDMIB, and its top-level OID is 1.3.6.1.4.1.9.12.3 (iso.org.dod.internet.private.enterprises.cisco.ciscoModules.ciscoEntityVendortypeOIDMIB).
MIB Constraints
Table 3-18 lists the objects and OIDs in the CISCO-ENTITY-VENDORTYPE-OID-MIB that describe router entities. For detailed definitions of MIB objects, see the MIB.
Table 3-18 CISCO-ENTITY-VENDORTYPE-OID-MIB Objects and Constraints
MIB Object (OID Assignment)
|
Notes
|
cevChassis
|
|
•cevChassisUbr7246 (1.3.6.1.4.1.9.12.3.1.3.57)
|
Cisco uBR7246 chassis
|
•cevChassisUbr7223 (1.3.6.1.4.1.9.12.3.1.3.68)
|
Cisco uBR7223 chassis
|
•cevChassisUbr7246Vxr (1.3.6.1.4.1.9.12.3.1.3.134)
|
Cisco uBR7246VXR chassis
|
•cevChassisUbr10012 (1.3.6.1.4.1.9.12.3.1.3.183)
|
Cisco uBR10012 chassis
|
•cevChassisUbr7111 (1.3.6.1.4.1.9.12.3.1.3.211)
|
Cisco uBR7111 chassis
|
•cevChassisUbr7111E (1.3.6.1.4.1.9.12.3.1.3.212)
|
Cisco uBR7111E chassis
|
•cevChassisUbr7114 (1.3.6.1.4.1.9.12.3.1.3.213)
|
Cisco uBR7114 chassis
|
•cevChassisUbr7114E (1.3.6.1.4.1.9.12.3.1.3.214)
|
Cisco uBR7114E chassis
|
cevPowerSupply
|
|
•cevPowerSupplyUbr10012AC (1.3.6.1.4.1.9.12.3.1.6.150)
|
UBR10012 Series AC Power Entry Module
|
•cevPowerSupplyUbr10012DC (1.3.6.1.4.1.9.12.3.1.6.151)
|
UBR10012 Series DC Power Entry Module
|
•cevPowerSupplyC10KDC (1.3.6.1.4.1.9.12.3.1.6.55)
|
DC power supply
|
•cevPowerSupplyC10KAC (1.3.6.1.4.1.9.12.3.1.6.56)
|
AC power supply
|
cevFan
|
|
•cevFanTrayUbr10012 (1.3.6.1.4.1.9.12.3.1.6.151)
|
UBR10012 Series Fan Assembly Module
|
cevModule
|
|
cevModuleCpuType
|
|
•cevC7200Io1fe (1.3.6.1.4.1.9.12.3.1.9.5.1)
|
UBR7200-I/O-FE controller for Cisco uBR7200 series
|
•cevC7200Io (1.3.6.1.4.1.9.12.3.1.9.5.2)
|
UBR7200-I/O controller for Cisco uBR7200 series
|
•cevCpu7200Npe300 (1.3.6.1.4.1.9.12.3.1.9.5.9)
|
NPE-300 processor for Cisco uBR7200 series
|
•cevCpu7200Npe175 (1.3.6.1.4.1.9.12.3.1.9.5.14)
|
NPE-175 processor for Cisco uBR7200 series
|
•cevCpu7200Npe225 (1.3.6.1.4.1.9.12.3.1.9.5.15)
|
NPE-225 processor for Cisco uBR7200 series
|
•cevCpu7200Npe100 (1.3.6.1.4.1.9.12.3.1.9.5.26)
|
NPE-100 processor for Cisco uBR7200 series
|
•cevCpu7200Npe150 (1.3.6.1.4.1.9.12.3.1.9.5.27)
|
NPE-150 processor for Cisco uBR7200 series
|
•cevCpu7200Npe200 (1.3.6.1.4.1.9.12.3.1.9.5.28)
|
NPE-200 processor for Cisco uBR7200 series
|
•cevCpu7200Npe400 (1.3.6.1.4.1.9.12.3.1.9.5.39)
|
NPE-400 processor for Cisco uBR7246VXR
|
•cevCpu7200Npeg1 (1.3.6.1.4.1.9.12.3.1.9.5.56)
|
NPE-G1 processor for Cisco uBR7246VXR
|
•cevCpuCreRp (1.3.6.1.4.1.9.12.3.1.9.5.29)
|
Central Routing Engine—Route processor for the Cisco uBR10012
|
•cevCpuCreFp (1.3.6.1.4.1.9.12.3.1. 9.5.30)
|
Central Routing Engine—Forwarding processor for the Cisco uBR10012
|
cevModuleC7xxxType
|
|
•cevC7xxxMc14a (1.3.6.1.4.1.9.12.3.1.9.7.1)
|
Cisco uBR-MC14C cable interface line card
|
•cevC7xxxMc16a (1.3.6.1.4.1.9.12.3.1.9.7.2)
|
Cisco uBR-MC16C cable interface line card
|
•cevC7xxxMc11 (1.3.6.1.4.1.9.12.3.1.9.7.3)
|
Cisco uBR-MC11-FPGA cable interface line card
|
•cevC7xxxMc12a (1.3.6.1.4.1.9.12.3.1.9.7.4)
|
Cisco uBR-MC12C cable interface line card
|
•cevC7xxxMc11a (1.3.6.1.4.1.9.12.3.1.9.7.5)
|
Cisco uBR-MC11C cable interface line card
|
•cevC7xxxIo1feTxIsl (1.3.6.1.4.1.9.12.3.1.9.7.6)
|
Fast Ethernet I/O Controller
|
•cevC7xxxMc28 (1.3.6.1.4.1.9.12.3.1.9.7.8)
|
Cisco uBR-MC28C cable interface line card
|
•cevC7xxxIo2FE (1.3.6.1.4.1.9.12.3.1.9.7.12)
|
UBR7200-I/O-2FE/E controller for Cisco uBR7200 series
|
cevModuleUbrType (1.3.6.1.4.1.9.12.3.1.9.27)
|
|
•cevUbrMc16s (1.3.6.1.4.1.9.12.3.1.9.27.2)
|
Cisco uBR-MC16S cable interface line card
|
•cevUbrMc11 (1.3.6.1.4.1.9.12.3.1.9.27.3)
|
Cisco uBR-MC11-FPGA cable interface line card
|
•cevUbrMc11c (1.3.6.1.4.1.9.12.3.1.9.27.4)
|
Cisco uBR-MC11C cable interface line card
|
•cevUbrMc12c (1.3.6.1.4.1.9.12.3.1.9.27.5)
|
Cisco uBR-MC12C cable interface line card
|
•cevUbrMc14c (1.3.6.1.4.1.9.12.3.1.9.27.6)
|
Cisco uBR-MC14C cable interface line card
|
•cevUbrMc16b (1.3.6.1.4.1.9.12.3.1.9.27.8)
|
Cisco uBR-MC16B cable interface line card
|
•cevUbrMc16c (1.3.6.1.4.1.9.12.3.1.9.27.9)
|
Cisco uBR-MC16C cable interface line card
|
•cevUbrMc16e (1.3.6.1.4.1.9.12.3.1.9.27.10)
|
Cisco uBR-MC16E cable interface line card
|
•cevUbrMc28c (1.3.6.1.4.1.9.12.3.1.9.27.11)
|
Cisco uBR-MC28C cable interface line card
|
•cevUbrClk (1.3.6.1.4.1.9.12.3.1.9.27.16)
|
Cisco National Clock Card for the Cisco uBR7246VXR router
|
•cevUbrMc28cBnc (1.3.6.1.4.1.9.12.3.1.9.27.22)
|
Cisco uBR-MC28C-BNC cable interface line card
|
•cevUbrMc520sD (1.3.6.1.4.1.9.12.3.1.9.27.32)
|
Cisco uBR-MC5X20S-D cable interface line card
|
•cevUbrMc28u (1.3.6.1.4.1.9.12.3.1.9.27.34)
|
Cisco uBR-MC28U cable interface line card
|
•cevUbrMc16u (1.3.6.1.4.1.9.12.3.1.9.27.35)
|
Cisco uBR-MC16U cable interface line card
|
•cevUbrMc28ux (1.3.6.1.4.1.9.12.3.1.9.27.36)
|
Cisco uBR-MC28X cable interface line card
|
•cevUbrMc16ux (1.3.6.1.4.1.9.12.3.1.9.27.37)
|
Cisco uBR-MC16X cable interface line card
|
•cevUbrMc520uD (1.3.6.1.4.1.9.12.3.1.9.27.38)
|
Cisco uBR-MC5X20U-D cable interface line card
|
•cevUbrMc2020 (1.3.6.1.4.1.9.12.3.1.9.27.44)
|
DOCSIS compliant intelligent coaxial cable line card with 20 downstream and 20 upstream ports for uBR10000 Series Cable Routers
|
•cevUbrMc3g60 (1.3.6.1.4.1.9.12.3.1.9.27.45)
|
DOCSIS compliant intelligent coaxial cable line card with 72 downstream and 60 upstream ports for uBR10000 Series Cable Router.
|
cevModule100012Type
|
|
•cevPos1oc12 (1.3.6.1.4.1.9.12.3.1.9.32.1)
|
Cisco uBR10-1OC12/P-SMI OC-12 POS uplink line card
|
•cevGe (1.3.6.1.4.1.9.12.3.1.9.32.3)
|
Cisco uBR10-1GE Gigabit Ethernet uplink line card
|
•cevSrpOc48SmSr (1.3.6.1.4.1.9.12.3.1.9.32.11)
|
Cisco uBR10012 OC-48 DPT/POS interface module (short reach)
|
•cevSrpOc48SmLr1 (1.3.6.1.4.1.9.12.3.1.9.32.26)
|
Cisco uBR10012 OC-48 DPT/POS interface module (long reach)
|
•cevC10K48MbFlashCard (1.3.6.1.4.1.9.12.3.1.9.32.18)
|
48MB flash card
|
•cevC10K128MbFlashCard (1.3.6.1.4.1.9.12.3.1.9.32.19)
|
128MB flash card
|
•cevSpa24xWbdSfp(1.3.6.1.4.1.9.12.3.1.9.2.145)
|
Cisco SPA-24-XWBD-SFP shared port adapter (cevPortGe)
|
CISCO-ENVMON-MIB
The CISCO-ENVMON-MIB contains information about the status of environmental sensors (for voltage, temperature, fans, and power supplies). It also contains MIB objects to enable and disable notifications for changes to the status of these sensors. In Cisco IOS Release 12.2BC and later releases, use this MIB instead of CISCO-ENTITY-SENSOR-MIB for temperature monitoring.
When a router temperature test point reaches a critical state, the environmental monitor initiates a shutdown and sends a ciscoEnvMonShutdownNotification if it has been configured to do so (see the "Enabling Notifications" section on page 4-2).
The MODULE-IDENTITY for the CISCO-ENVMON-MIB is ciscoEnvMonMIB, and its top-level OID is 1.3.6.1.4.1.9.9.13 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoEnvMonMIB).
MIB Constraints
The CISCO-ENVMON-MIB is supported on:
•Cisco uBR7100 series and Cisco uBR7200 series routers only in Cisco IOS Release 12.1(11)EC, and Cisco IOS Release 12.2(4)BC1, and later releases.
•Cisco uBR10012 routers only in Cisco IOS Release 12.2(8)BC2 and later releases.
Table 3-19 lists the constraints that the router places on objects in the CISCO-ENVMON-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-19 CISCO-ENVMON-MIB Constraints
MIB Object
|
Notes
|
ciscoEnvMonTable
|
|
•ciscoEnvMonEnableStatChangeNotif
|
Supported in IOS Release 12.3(18)BC and later releases.
This variable indicates whether the system produces the ciscoEnvMonVoltStatusChangeNotif, ciscoEnvMonTempStatusChangeNotif, ciscoEnvMonFanStatusChangeNotif, and ciscoEnvMonSuppStatusChangeNotif. A false value prevents these notifications from being generated by the uBR System.
|
•ciscoEnvMonEnableVoltageNotification
•ciscoEnvMonEnableTemperatureNotification
•ciscoEnvMonEnableFanNotification,
•ciscoEnvMonEnableRedundantSupply
|
Notification had been deprecated. Use ciscoEnvMonEnableStatChangeNotif.
|
ciscoEnvMonTemperatureStatusTable
|
|
•ciscoEnvMonEnableTemperatureNotification
•ciscoEnvMonTemperatureNotification
|
Supported values are:
•ubr7200(8) for the Cisco uBR7100 series and Cisco uBR7200 series routers
•c10000(10) for the Cisco uBR10012 router.
|
ciscoEnvMonVoltageStatusTable
|
|
•ciscoEnvMonVoltageNotification
|
Not supported for the Cisco uBR10012 router.
|
•ciscoEnvMonEnableVoltageNotification
|
Supported in Cisco IOS Release 12.1(19)EC, Cisco IOS Release 12.2(4)BC, and later releases.
|
ciscoEnvMonFanStatusTable
|
•Not supported for Cisco uBR7100 series and Cisco uBR7200 series routers.
•Supported for the Cisco uBR10012 router only in Cisco IOS Release 12.2(11)BC1 and later releases.
|
•ciscoEnvMonFanStatusIndex
|
Always 1. Only one table row supported for fan tray.
|
•ciscoEnvMonFanStatusDescr
|
Always Fan Tray.
|
•ciscoEnvMonFanState
|
Supported values are:
•normal(1)—Both fans are working
•warning(2)—One fan is failing
•critical(3)—Both fans are failing
•notPresent(5)—Fan tray is missing
•notFunctioning(6)—Unable to get status
|
ciscoEnvMonSupplyStatusTable
|
•Supported in Cisco IOS Release 12.1 EC and in Cisco IOS Release 12.2(11)BC1 and later releases.
•On the Cisco uBR7200 series routers, this table reports accurate results only in Cisco IOS Release 12.1(19)EC, Cisco IOS Release 12.2(15)BC1, and later releases.
|
•ciscoEnvMonSupplyStatusIndex
|
For uBR10012:
•1 indicates PEM0
•2 indicates PEM1
|
•ciscoEnvMonSupplyStatusDescr
|
For uBR10012 valid values are PEM0 or PEM1.
|
•ciscoEnvMonSupplyState
|
Supported values are the following:
•normal(1)—Power supply is working
•critical(3)—Power supply is failing
•notPresent(5)—Power supply is missing
|
•ciscoEnvMonSupplySource
|
Supported values are:
•unknown(1)—Missing or unknown power supply
•ac(2)—AC power supply
•dc(3)—DC power supply
|
ciscoEnvMonAlarmContacts
|
Not implemented.
|
CISCO-FLASH-MIB
The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.
The MODULE-IDENTITY for the CISCO-FLASH-MIB is ciscoFlashMIB, and its top-level OID is 1.3.6.1.4.1.9.9.10 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoFlashMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-FRAME-RELAY-MIB
The CISCO-FRAME-RELAY-MIB contains Frame Relay information that is specific to Cisco products or that is missing from RFC 1315.
The MODULE-IDENTITY for the CISCO-FRAME-RELAY-MIB is ciscoFrameRelayMIB, and its top-level OID is 1.3.6.1.4.1.9.9.49 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoFrameRelayMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-FTP-CLIENT-MIB
The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management.
The MODULE-IDENTITY for the CISCO-FTP-CLIENT-MIB is ciscoFtpClientMIB, and its top-level OID is 1.3.6.1.4.1.9.9.80 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoFtpClientMIB).
MIB Constraints
This MIB is not supported on any Cisco CMTS platforms, although it is included in the Cisco IOS software images.
CISCO-HSRP-EXT-MIB
The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB. It contains objects to perform functions such as assigning secondary Hot Standby Router Protocol (HSRP) IP addresses, monitoring the operational status of interfaces, and modifying an HSRP group's priority.
The MODULE-IDENTITY for the CISCO-HSRP-EXT-MIB is ciscoHsrpExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.107 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoHsrpExtMIB).
MIB Constraints
This MIB is not supported on any Cisco CMTS platforms, although it is included in the Cisco IOS software images.
CISCO-HSRP-MIB
The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281.
The MODULE-IDENTITY for the CISCO-HSRP-MIB is ciscoHsrpMIB, and its top-level OID is 1.3.6.1.4.1.9.9.106 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoHsrpMIB).
MIB Constraint
This MIB is not supported on any Cisco CMTS platforms, although it is included in the Cisco IOS software images.
CISCO-IETF-ATM2-PVCTRAP-MIB
The CISCO-IETF-ATM2-PVCTRAP-MIB supplements the ATM-MIB. It implements the virtual channel link (VCL) section of the IETF draft, Definitions of Supplemental Managed Objects for ATM Interface, Section 9, "ATM Related Trap Support", which is available at the following URL :
http://www4.ietf.org/proceedings/03jul/I-D/draft-ietf-atommib-atm2-19.txt
The MODULE-IDENTITY for the CISCO-IETF-ATM2-PVCTRAP-MIB is ciscoIetfAtm2PvctrapMIB, and its top-level OID is 1.3.6.1.4.1.9.10.29 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIetfAtm2PvctrapMIB).
MIB Constraint
This MIB is not supported on any Cisco CMTS platforms, although it is included in the Cisco IOS software images.
CISCO-IETF-IP-FORWARD-MIB
The CISCO-IETF-IP-FORWARD-MIB contains objects that manage and describe the forwarding of IP traffic across networks that might use different versions of IP (IPv4 and IPv6).
This MIB was derived from the initial version of the Internet Draft that is being drafted to replace the current IP-FORWARD-MIB, which is defined in RFC 2096, IP Forwarding Table MIB. Cisco implemented this temporary MIB to provide this functionality until the Internet Draft is finalized and a new RFC is released to replace RFC 2096.
The MODULE-IDENTITY for the CISCO-IETF-IP-FORWARD-MIB is ciscoIetfIpForward, and its top-level OID is 1.3.6.1.4.1.9.10.85 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIetfIpForward).
MIB Constraints
This MIB is not supported on:
•Cisco uBR10012 router.
•Any Cisco IOS Release 12.1EC software image.
CISCO-IETF-IP-MIB
The CISCO-IETF-IP-MIB contains objects to manage the IP and ICMP protocols across networks that might use different versions of IP (IPv4 and IPv6).
This MIB was derived from the initial version of the Internet Draft that is being drafted to replace the current IP-MIB, which is defined in RFC 2011, SNMPv2 Management Information Base for the Internet Protocol using SMIv2. Cisco implemented this temporary MIB to provide this functionality until the Internet Draft is finalized and a new RFC is released to replace RFC 2011.
The MODULE-IDENTITY for the CISCO-IETF-IP-MIB is ciscoIetfIpMIB, and its top-level OID is 1.3.6.1.4.1.9.10.86 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIetfIpMIB).
MIB Constraints
This MIB is not supported on:
•Any Cisco IOS Release 12.1EC software image.
•Cisco uBR10012 router.
CISCO-IETF-NAT-MIB
The CISCO-IETF-NAT-MIB contains objects about the operation of Network Address Translation (NAT) on the router, as defined in RFC 3022. This includes objects about NAT configuration, NAT bindings, and run-time statistics.
This MIB was derived from the initial version of the Internet Draft that is being drafted to provide this support. Cisco implemented this temporary MIB to provide this functionality until the Internet Draft is finalized and a new RFC is released.
The MODULE-IDENTITY for the CISCO-IETF-NAT-MIB is ciscoIetfNatMIB, and its top-level OID is 1.3.6.1.4.1.9.10.77 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIetfNatMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco uBR7100 series and Cisco uBR7200 series routers that are running a Cisco IOS Release 12.2BC "-is-" software image.
•Not supported on any Cisco IOS Release 12.1EC software image.
•Not supported on the Cisco uBR10012 router.
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 enable you to use the underlying PSN.
CISCO-IETF-PW-MPLS-MIB
The CISCO-IETF-PW-MPLS-MIB complements the CISCO-IETF-PW-MIB for pseudo-wire operations over Multiprotocol Label Switching (MPLS).
MIB Constraints
There are no constraints on this MIB.
CISCO-IMAGE-MIB
The CISCO-IMAGE-MIB identifies the characteristics and capabilities of the Cisco IOS software image running on the router.
The MODULE-IDENTITY for the CISCO-IMAGE-MIB is ciscoImageMIB, and its top-level OID is 1.3.6.1.4.1.9.9.25 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoImageMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-IP-ENCRYPTION-MIB
The CISCO-IP-ENCRYPTION-MIB contains objects that provide information about encrypted IP traffic on the router and the crypto maps that are being used.
The MODULE-IDENTITY for the CISCO-IP-ENCRYPTION-MIB is ciscoIpEncryptionMIB, and its top-level OID is 1.3.6.1.4.1.9.9.52 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIpEncryptionMIB).
MIB Constraints
This MIB is:
•Supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router.
CISCO-IPMROUTE-MIB
The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.
The MODULE-IDENTITY for the CISCO-IPMROUTE-MIB is ciscoIpMRouteMIB, and its top-level OID is 1.3.6.1.4.1.9.10.2 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIpMRouteMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-IP-STAT-MIB
The CISCO-IP-STAT-MIB contains objects to manage the collection and display of IP statistics, categorized by IP precedence and the Media Access Control (MAC) address associated with IP packets. To use the MIB to access additional IP statistics, you can issue the ip accounting mac-address and ip accounting precedence commands at the CLI.
The MODULE-IDENTITY for the CISCO-IP-STAT-MIB is ciscoIpStatMIB, and its top-level OID is 1.3.6.1.4.1.9.9.84 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIpStatMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-IP-TAP-MIB
The CISCO-IP-TAP-MIB contains the SNMP management objects to configure and execute lawful intercepts on IP Layer 3 streams. This MIB is used with the CISCO-TAP2-MIB to intercept traffic based on IP address. The Cisco CMTS routers support only IPv4 type intercepts.
CISCO-IP-TAP-MIB Tables and Objects
Table 3-20 lists the CISCO-IP-TAP-MIB Tables and Objects.
.
Table 3-20 Tables and Objects
Object
|
Description
|
citapStreamTable
|
Lists the IP streams to be intercepted.
|
citapStreamCapabilities
|
Displays the type of intercept streams that can be configured on this type of device.
|
MIB Constraints
There are no constraints on this MIB.
CISCO-IPSEC-FLOW-MONITOR-MIB
The CISCO-IPSEC-FLOW-MONITOR-MIB contains objects to manage IPSec-based virtual private networks (VPNs). These objects include information about Internet Key Exchange (IKE) negotiations and tunnels, data tunnels, historical trending analysis, and packet counters. This MIB also defines notifications about possible failures and intrusion attempts on the network.
The MODULE-IDENTITY for the CISCO-IPSEC-FLOW-MONITOR-MIB is ciscoIpSecFlowMonitorMIB, and its top-level OID is 1.3.6.1.4.1.9.9.171 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIpSecFlowMonitorMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-IPSEC-MIB
The CISCO-IPSEC-MIB contains objects about features that are used to configure and manage IPSec-based virtual private networks (VPNs).
The MODULE-IDENTITY for the CISCO-IPSEC-MIB is ciscoIPsecMIB, and its top-level OID is 1.3.6.1.4.1.9.10.62 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoIPsecMIB).
MIB Constraint
This MIB is supported only in Cisco IOS software images that support DES encryption (-k8- or -k9-).
CISCO-IPSEC-POLICY-MAP-MIB
The CISCO-IPSEC-POLICY-MAP-MIB contains objects that supplement the proposed IETF standards for IPSec VPNs. In particular, this MIB maps dynamically instantiated IPSec protocol structures (such as tunnels and security associations) to the policy entities that created them (such as policy definitions, crypto maps, and transforms).
The MODULE-IDENTITY for the CISCO-IPSEC-POLICY-MAP-MIB is ciscoIpSecPolMapMIB, and its top-level OID is 1.3.6.1.4.1.9.9.172 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIpSecPolMapMIB).
MIB Constraint
This MIB is supported only in Cisco IOS software images that support DES encryption (-k8- or -k9-).
CISCO-ISDN-MIB
The CISCO-ISDN-MIB contains objects that describe the status of ISDN interfaces on the router.
The MODULE-IDENTITY for the CISCO-ISDN-MIB is ciscoIsdnMib, and its top-level OID is 1.3.6.1.4.1.9.9.26 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoIsdnMib).
MIB Constraint
This MIB is not supported on the Cisco uBR10012 router.
CISCO-LEC-DATA-VCC-MIB
The CISCO-LEC-DATA-VCC-MIB is a Cisco extension to the standard ATM-MIB. This MIB contains objects that identify the VCCs that carry packets being sent on LAN Emulation (LANE) VLANs over ATM interfaces.
The MODULE-IDENTITY for the CISCO-LEC-DATA-VCC-MIB is ciscoLecDataVccMIB, and its top-level OID is 1.3.6.1.4.1.9.9.69 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoLecDataVccMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco uBR7100 series and Cisco uBR7200 series routers running a Cisco IOS "-is-" software image.
•Not supported on the Cisco uBR10012 router.
CISCO-LEC-EXT-MIB
The CISCO-LEC-EXT-MIB is a Cisco extension to the standard ATM-MIB. This MIB contains objects that map a LAN emulation client (LEC) to its VLAN.
The MODULE-IDENTITY for the CISCO-LEC-EXT-MIB is ciscoLecExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.77 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoLecExtMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco uBR7100 series and Cisco uBR7200 series routers running a Cisco IOS "-is-" software image.
•Not supported on the Cisco uBR10012 router.
CISCO-LECS-MIB
The CISCO-LECS-MIB is a Cisco extension to the standard ATM-MIB. This MIB contains objects about the configuration of LANE VLANs on the Cisco router.
The MODULE-IDENTITY for the CISCO-LECS-MIB is ciscoLecsMIB, and its top-level OID is 1.3.6.1.4.1.9.9.38 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoLecsMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco uBR7100 series and Cisco uBR7200 series routers running a Cisco IOS "-is-" software image.
•Not supported on the Cisco uBR10012 router.
CISCO-LES-MIB
The CISCO-LES-MIB is a Cisco extension to the standard ATM-MIB. This MIB contains objects to manage LAN emulation services (LES) on the router.
The MODULE-IDENTITY for the CISCO-LES-MIB is ciscoLesMIB, and its top-level OID is 1.3.6.1.4.1.9.9.39 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoLesMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco uBR7100 series and Cisco uBR7200 series routers running a Cisco IOS "-is-" software image.
•Not supported on the Cisco uBR10012 router.
CISCO-MEMORY-POOL-MIB
The CISCO-MEMORY-POOL-MIB contains objects to monitor memory pools on the router.
The MODULE-IDENTITY for the CISCO-MEMORY-POOL-MIB is ciscoMemoryPoolMIB, and its top-level OID is 1.3.6.1.4.1.9.9.48 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoMemoryPoolMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-NBAR-PROTOCOL-DISCOVERY-MIB
The CISCO-NBAR-PROTOCOL-DISCOVERY-MIB provides SNMP support for Network-Based Application Recognition (NBAR), including enabling and disabling protocol discovery on a per-interface basis and configuring the traps that are generated when certain events occur. You can also display the current NBAR configuration and run-time statistics.
The MODULE-IDENTITY for the CISCO-NBAR-PROTOCOL-DISCOVERY-MIB is ciscoNbarProtocolDiscoveryMIB, and its top-level OID is 1.3.6.1.4.1.9.9.244 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoNbarProtocolDiscoveryMIB).
MIB Constraints
The CISCO-NBAR-PROTOCOL-DISCOVERY-MIB is supported on:
•Cisco uBR7246VXR universal broadband routers.
•Cisco IOS Release 12.2(15)BC2 and later releases.
•Not supported in Cisco IOS Release 12.1 EC.
CISCO-NDE-MIB
The CISCO-NDE-MIB contains objects about the configuration and operation of the Netflow Data Export (NDE) feature.
The MODULE-IDENTITY for the CISCO-NDE-MIB is ciscoNDEMIB, and its top-level OID is 1.3.6.1.4.1.9.9.226 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoNDEMIB).
MIB Constraints
This MIB is:
•Supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router.
CISCO-NTP-MIB
The CISCO-NTP-MIB contains objects to monitor the Network Time Protocol (NTP) clients and servers that are operating on the router.
The MODULE-IDENTITY for the CISCO-NTP-MIB is ciscoNtpMIB, and its top-level OID is 1.3.6.1.4.1.9.9.168 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoNtpMIB).
MIB Constraints
This MIB is:
•Supported only in Cisco IOS Release 12.2BC and later for the Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router.
CISCO-PIM-MIB
The CISCO-PIM-MIB defines objects and variables for managing Protocol Independent Multicast (PIM) on the router. These MIB definitions are an extension of those in RFC 2934, which is the IETF PIM MIB.
The MODULE-IDENTITY for the CISCO-PIM-MIB is ciscoPimMIB, and its top-level OID is 1.3.6.1.4.1.9.9.184 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoPimMIB).
MIB Constraints
This MIB is supported only in Cisco IOS Release 12.2BC and later software images. It is not supported in Cisco IOS Release 12.1EC software images.
CISCO-PING-MIB
The CISCO-PING-MIB contains objects to manage ICMP echo (ping) requests on the router.
The MODULE-IDENTITY for the CISCO-PING-MIB is ciscoPingMIB, and its top-level OID is 1.3.6.1.4.1.9.9.16 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoPingMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-PPPOE-MIB
The CISCO-PPPOE-MIB contains objects to manage Point-to-Point Protocol over Ethernet (PPPoE) sessions. These objects represent PPPoE sessions at the system and virtual channel (VC) level.
The MODULE-IDENTITY for the CISCO-PPPOE-MIB is ciscoPppoeMIB, and its top-level OID is 1.3.6.1.4.1.9.9.194 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoPppoeMIB).
MIB Constraints
This MIB is not supported:
•On the Cisco uBR10012 router.
•In any Cisco IOS Release 12.1EC software image.
CISCO-PROCESS-MIB
The CISCO-PROCESS-MIB displays memory and CPU usage on the router and describes active system processes. The CISCO-PROCESS-MIB enables you to monitor CPU and memory utilization for line cards, cable interface line cards, and broadband processing engines on the Cisco uBR10012 or Cisco uBR7246VXR routers.
The MODULE-IDENTITY for the CISCO-PROCESS-MIB is ciscoProcessMIB, and its top-level OID is 1.3.6.1.4.1.9.9.109 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoProcessMIB).
MIB Constraints
This MIB supports:
•PRE2 modules on the Cisco uBR10012 routers with Cisco IOS Release 12.3(9a)BC and later BC releases.
•The Cisco uBR7246VXR router and the Cisco uBR10012 router with the PRE1 module in Cisco IOS Release 12.2(15)BC2 and later BC releases.
•CPU statistics for processors are distributed line cards (such as the Broadband Processing Engines) are supported in Cisco IOS Release 12.3(9a)BC and later releases.
Table 3-22 lists the constraints that the router places on CISCO-PROCESS-MIB.
Table 3-21 Cisco CMTS Router CISCO-PROCESS-MIB
Object Name
|
Description
|
cpmCPUTotalTable
|
Maintained only for the active Performance Routing Engine (PRE) on the Cisco uBR10012 router. Statistics are not maintained for the standby PRE or for line cards. This means that cpmCPUTotalPhysicalIndex is always the index of the active PRE.
|
CISCO-PRODUCTS-MIB
The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to Cisco hardware platforms.
The MODULE-IDENTITY for the CISCO-PRODUCTS-MIB is ciscoProductsMIB, and its top-level OID is 1.3.6.1.4.1.9.12.2 (iso.org.dod.internet.private.enterprises.cisco.ciscoModules.ciscoProductsMIB).
MIB Constraints
Table 3-22 lists the relevant OIDs for the Cisco CMTS routers.
Table 3-22 Cisco CMTS Router OIDs from CISCO-PRODUCTS-MIB
Object Name
|
Object Identifier
|
Description
|
ciscoUBR7246
|
1.3.6.1.4.1.9.1.179
|
Cisco uBR7246 universal broadband router
|
ciscoUBR7223
|
1.3.6.1.4.1.9.1.210
|
Cisco uBR7223 universal broadband router
|
ciscoUBR7246VXR
|
1.3.6.1.4.1.9.1.271
|
Cisco uBR7246VXR universal broadband router
|
ciscoUBR10012
|
1.3.6.1.4.1.9.1.317
|
Cisco uBR10012 universal broadband router
|
ciscoUBR7111
|
1.3.6.1.4.1.9.1.344
|
Cisco uBR7111 universal broadband router
|
ciscoUBR7111E
|
1.3.6.1.4.1.9.1.345
|
Cisco uBR7111E universal broadband router
|
ciscoUBR7114
|
1.3.6.1.4.1.9.1.346
|
Cisco uBR7114 universal broadband router
|
ciscoUBR7114E
|
1.3.6.1.4.1.9.1.347
|
Cisco uBR7114E universal broadband router
|
CISCO-QUEUE-MIB
The CISCO-QUEUE-MIB contains objects to manage interface queues on the router.
The MODULE-IDENTITY for the CISCO-QUEUE-MIB is ciscoQueueMIB, and its top-level OID is 1.3.6.1.4.1.9.9.37 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoQueueMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-RMON-SAMPLING-MIB
The CISCO-RMON-SAMPLING-MIB contains objects that supplement the RMON-MIB and the RMON2-MIB, providing additional information about the statistical reliability of the estimated counter values in these MIBs.
The MODULE-IDENTITY for the CISCO-RMON-SAMPLING-MIB is ciscoRmonSamplingMIB, and its top-level OID is 1.3.6.1.4.1.9.9.104 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoRmonSamplingMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-RTTMON-MIB
The CISCO-RTTMON-MIB contains objects to monitor network performance. The MIB provides information about the response times of network resources and applications. Each conceptual round-trip time (RTT) control row in the MIB represents a single probe, which is used to determine an entity response time. The probe defines an RTT operation to perform (for example, an FTP or HTTP GET request), and the results indicate whether the operation succeeded or failed, and how long it took to complete.
The MODULE-IDENTITY for the CISCO-RTTMON-MIB is ciscoRttMonMIB, and its top-level OID is 1.3.6.1.4.1.9.9.42 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoRttMonMIB).
Note An rttMonCtrlOperConnectionLostOccurred trap is generated when an RTT connection cannot be established to the destination router because the router responder application is not running. However, the trap is not generated if the physical connection to the router is lost.
CISCO-SLB-EXT-MIB
The CISCO-SLB-EXT-MIB contains objects to supplement the CISCO-SLB-MIB, which provide additional information about server load balancing (SLB) operations on the router. In particular, the MIB contains objects about the Dynamic Feedback Protocol (DFP) manager and Layer 7 policy load balancing features.
The MODULE-IDENTITY for the CISCO-SLB-EXT-MIB is ciscoSlbExtMIB, and its top-level OID is 1.3.6.1.4.1.9.9.254 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoSlbExtMIB).
MIB Constraints
This MIB is:
•Supported only in Cisco IOS Release 12.1EC "-is-" software images for the Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router.
CISCO-SLB-MIB
The CISCO-SLB-MIB contains objects about the operation of server load balancing (SLB) and the Dynamic Feedback Protocol (DFP) on the router.
The MODULE-IDENTITY for the CISCO-SLB-MIB is ciscoSlbMIB, and its top-level OID is 1.3.6.1.4.1.9.9.161 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoSlbMIB).
MIB Constraints
This MIB is:
•Supported only in Cisco IOS Release 12.1EC "-is-" software images for the Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported in Cisco IOS Release 12.2BC for any Cisco CMTS router.
CISCO-SNAPSHOT-MIB
The CISCO-SNAPSHOT-MIB contains objects to manage snapshot routing, which helps improve the use of system resources for static routing and routing for dedicated serial lines.
The MODULE-IDENTITY for the CISCO-SNAPSHOT-MIB is ciscoSnapshotMIB, and its top-level OID is 1.3.6.1.4.1.9.9.19 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoSnapshotMIB).
MIB Constraints
There are no constraints on this MIB.
CISCO-SRP-MIB
The CISCO-SRP-MIB contains objects to monitor and configure Spatial Reuse Protocol (SRP) interfaces and rings.
The MODULE-IDENTITY for the CISCO-SRP-MIB is ciscosrpMIB, and its top-level OID is 1.3.6.1.4.1.9.10.60 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscosrpMIB).
MIB Constraints
This MIB is not supported on Cisco uBR7100 series and Cisco uBR7200 series routers.
CISCO-SYSLOG-MIB
The CISCO-SYSLOG-MIB contains all system log messages generated by the Cisco IOS software. The MIB provides a way to access these SYSLOG messages through Simple Network Management Protocol (SNMP). All Cisco IOS SYSLOG messages contain the message name and its severity, message text, the name of the entity generating the message, and an optional time stamp. The MIB also contains a history of SYSLOG messages and counts related to SYSLOG messages.
The MODULE-IDENTITY for the CISCO-SYSLOG-MIB is ciscoSyslogMIB, and its top-level OID is 1.3.6.1.4.1.9.9.41 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoSyslogMIB).
MIB Constraints
This MIB does not track messages generated by debug commands that are entered through the CLI.
Note When you plan to enable traps for SYSLOG events, increase the trap queue size from its default of 10, using the snmp-server queue-length command. The size of the queue can range from 1 to 1000 traps, and we recommend a size of at least 100 for systems that are sending traps for SYSLOG events.
CISCO-TAP2-MIB
The CISCO-TAP2-MIB contains SNMP management objects that control lawful intercepts on a router. The mediation device uses the MIB to configure and run lawful intercepts on targets sending traffic through the router. The CISCO-TAP2-MIB MIB is bundled with Cisco IOS software images that support the Service Independent Intercept (SII) feature. The CISCO-TAP2-MIB works with the CISCO-IP-TAP-MIB and the CISCO-802-TAP-MIB to define specific intercepts.
CISCO-TAP2-MIB Table and Objects
Table 3-23 lists tables and objects in CISCO-TAP2-MIB MIB.
.
Table 3-23 CISCO-TAP2-MIB Tables and Objects
Object
|
Description
|
cTap2MediationTable
|
Lists the mediation devices with which the intercepting device communicates.
|
cTap2StreamTable
|
Lists the traffic streams to intercept. The list consists of generic fields that are independent of the type of intercept.
|
cTap2DebugTable
|
Contains Lawful Intercept debug messages generated by the implementing device.
|
cTap2MediationNewIndex
|
Contains a value which may be used as an index value for a new cTap2Mediation Entry.
|
cTap2MediationCapabilities
|
Displays the device capabilities for certain fields in the mediation device table. The device capabilities may be dependent on hardware or software capabilities.
|
cTap2DebugAge
|
Contains the duration in minutes for which an entry in cTap2DebugTable is maintained by the implementing device. The entry is deleted once this duration is reached.
|
cTap2DebugMaxEntries
|
Contains the maximum number of debug messages maintained at a time by the implementing device. When this limit is reached, the oldest messages is deleted from the list.
|
Table 3-24 lists CISCO-IP-TAP-MIB Notifications.
.
Table 3-24 CISCO-IP-TAP-MIB Notifications
Notification
|
Description
|
ciscoTap2MIBActive
|
Sent when an intercepting router or switch is enabled to intercept a packet corresponding to a configured data stream. The value of the corresponding cTap2StreamType object that identifies the actual intercept stream type is included in this notification.
|
ciscoTap2MediationTimedOut
|
Sent when an intercept is removed by an intercepting device. This may be due to the lapse in time duration specified in cTap2MediationTimeout object.
|
ciscoTap2MediationDebug
|
Sent when an intervention is needed for an event listed in the cTap2MediationTable.
|
ciscoTap2StreamDebug
|
Sent when an intervention is needed for an event listed in the cTap2StreamTable.
|
ciscoTap2Switchover
|
Sent when the current active processor has failed and alternate router processor is enabled on the intercepting device to take over the failing processor.
|
MIB Constraint
There are no constraints on this MIB.
CISCO-TCP-MIB
The CISCO-TCP-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router. This MIB is an extension to the TCP-MIB.
The MODULE-IDENTITY for the CISCO-TCP-MIB is ciscoTcpMIB, and its top-level OID is 1.3.6.1.4.1.9.9.6 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoTcpMIB).
MIB Constraint
This MIB is not supported on Cisco CMTS platforms, even though it is included in the Cisco IOS software images.
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB
The CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB maps the Virtual Local Area Network (VLAN) group ID to the interface index for routed VLAN interfaces.
The MODULE-IDENTITY for the CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB is ciscoVlanIfTableRelationshipMIB, and its top-level OID is 1.3.6.1.4.1.9.9.128 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoVlanIfTableRelationshipMIB).
MIB Constraint
This MIB is not supported on Cisco CMTS platforms, even though it is included in the Cisco IOS software images.
CISCO-VPDN-MGMT-EXT-MIB
The CISCO-VPDN-MGMT-EXT-MIB supplements the CISCO-VPDN-MGMT-MIB with additional information about virtual private dial-up network (VPDN) tunnels and sessions. The MIB contains the following tables, which provide read-only information not found in the CISCO-VPDN-MGMT-MIB:
•cvpdnTunnelExtTable—Provides information about Layer 2 Tunnel Protocol (L2TP) tunnels, such as tunnel statistics and User Datagram Protocol (UDP) port numbers.
•cvpdnSessionExtTable—Provides information about L2TP sessions, as well as information about session packet counts, packet sequencing information, window size, and operating characteristics.
The MODULE-IDENTITY for the CISCO-VPDN-MGMT-EXT-MIB is ciscoVpdnMgmtExtMIB, and its top-level OID is 1.3.6.1.4.1.9.10.51 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoVpdnMgmtExtMIB).
MIB Constraints
This MIB is:
•Read-only, which means that you cannot use the MIB to configure VPDN on the router.
•Supported only on Cisco IOS "-is-" software images for Cisco uBR7100 series and Cisco uBR7200 series routers.
•Not supported on the Cisco uBR10012 router.
CISCO-VPDN-MGMT-MIB
The CISCO-VPDN-MGMT-MIB provides operational information about the Virtual Private Dialup Network (VPDN) feature on the router. You can use the MIB to monitor VPDN tunnel information on the router, but you cannot use the MIB to configure VPDN.
VPDN enables the router to forward Point-to-Point Protocol (PPP) traffic between an Internet service provider (ISP) and a home gateway. The CISCO-VPDN-MGMT-MIB includes several tables that contain VPDN tunneling information:
•cvpdnSystemTable—Provides system-wide VPDN information.
•cvpdnTunnelAttrTable—Provides information about each active tunnel.
•cvpdnSessionAttrTable—Provides information about each active session within each tunnel.
•cvpdnUserToFailHistInfoTable—Provides information about the last failure that occurred for each tunnel user.
•cvpdnTemplateTable—Identifies each VPDN template and indicates the number of active sessions associated with the template. See Table 3-25 for information about template name restrictions and and their effect on SNMP.
The MODULE-IDENTITY for the CISCO-VPDN-MGMT-MIB is ciscoVpdnMgmtMIB, and its top-level OID is 1.3.6.1.4.1.9.10.24 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.ciscoVpdnMgmtMIB).
MIB Constraints
This MIB is:
•Read-only, you cannot use the MIB to configure VPDN on the router.
•Supported only on Cisco IOS Release 12.2BC "-is-" software images for Cisco uBR7100 and Cisco uBR7200 series routers.
•Not supported on the Cisco uBR10012 router.
The MIB objects in Table 3-25 have been deprecated. Although currently supported, their use is being phased out and we recommend that you use the replacement object instead. For detailed definitions of MIB objects, see the MIB.
Table 3-25 Deprecated CISCO-VPDN-MGMT-MIB Objects
MIB Object
|
Notes
|
cvpdnTunnelTotal
|
Replaced by cvpdnSystemTunnelTotal.
|
cvpdnSessionTotal
|
Replaced by cvpdnSystemSessionTotal.
|
cvpdnDeniedUsersTotal
|
Replaced by cvpdnSystemDeniedUsersTotal.
|
cvpdnTunnelTable
|
Replaced by cvpdnTunnelAttrTable.
|
cvpdnTunnelSessionTable
|
Replaced by cvpdnSessionAttrTable.
|
cvpdnTemplateTable
|
SNMP limits the size of VPDN template names to 128 characters. If any template name in the cvpdnTemplateTable exceeds this length, then in order to retrieve any table entries, you must use individual GET requests to retrieve each template name (cvpdnTemplateName) that does not exceed 128 characters.
|
CISCO-VSIMASTER-MIB
The CISCO-VSIMASTER-MIB contains objects about the master side of the the Virtual Switch Interface (VSI) protocol that is used to control ATM interfaces.
The MODULE-IDENTITY for the CISCO-VSIMASTER-MIB is ciscoVsiMasterMIB, and its top-level OID is 1.3.6.1.4.1.9.9.162 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoVsiMasterMIB).
MIB Constraints
This MIB is:
•Supported only on Cisco IOS Release 12.2BC software images. It is not supported on Cisco IOS Release 12.1EC software images.
•Not supported on the Cisco uBR10012 router.
CLAB-TOPO-MIB
The CLAB-TOPO-MIB contains the management objects to manage fiber nodes in a cable plant. This MIB is released as a part of CableLabs OSSIv3.0 specification CM-SP-OSSIv3.0-I01-061207.
DOCS-BPI-MIB
The DOCS-BPI-MIB contains objects to configure, operate, and monitor the DOCSIS 3.0 Baseline Privacy Interface (BPI) feature. This MIB has been released as RFC 3083, Baseline Privacy Interface Management Information Base for DOCSIS Compliant Cable Modems and Cable Modem Termination Systems.
The MODULE-IDENTITY for the DOCS-BPI-MIB is docsBpiMIB, and its top-level OID is 1.3.6.1.2.1.10.127.5 (iso.org.dod.internet.mgmt-mib-2.transmission.docsIfMIB.docsBpiMIB).
MIB Constraints
This MIB is supported only in:
•Cisco IOS software images that support DES encryption (-k8- or -k9-).
•DOCSIS 1.0 software images (Cisco IOS Release 12.1EC). In DOCSIS 1.1 software images (Cisco IOS Release 12.2BC and later releases), use the DOCS-BPI-PLUS-MIB instead.
DOCS-BPI-PLUS-MIB
The DOCS-BPI-PLUS-MIB contains objects to configure, operate, and monitor the DOCSIS 3.0 Baseline Privacy Interface Plus (BPI+) feature for CMs and CMTSs.
The MODULE-IDENTITY for the DOCS-BPI-PLUS-MIB is docsBpi2MIB and its top-level OID is 1.3.6.1.2.1.10.127.6 (iso.org.dod.internet.mgmt-mib-2.transmission.docsIfMIB.docsBpi2MIB).
MIB Constraints
This MIB is supported in:
•Cisco IOS software images that support DES encryption (-k8- or -k9-).
•DOCSIS 1.1 and DOCSIS 2.0 software images (Cisco IOS Release 12.2BC and later). In DOCSIS 1.0 software images (Cisco IOS Release 12.1EC), use the DOCS-BPI-MIB instead.
•DOCSIS BPI+ in narrowband fiber node interface configurations are supported only in Cisco IOS Release 12.3(23)BC or later on the Cisco uBR10012 router. This application of narrowband fiber nodes is distinct from additional narrowband functions supported for the Shared Port Adapter (SPA).
Table 3-26 lists the constraints that the router places on DOCS-BPI-PLUS-MIB.
.
Table 3-26 DOCS-BPI-PLUS-MIB Constraints
MIB Object
|
Notes
|
docsBpi2CmtsCACertTable
|
This table cannot be used to load a root Certificate Authority (CA) certificate into the Cisco CMTS router.
The root CA certificate must always be loaded on the local bootflash or Flash Disk. (For security and operational reasons, we recommend always loading the root CA certificate on the bootflash, and not on a removable Flash Disk.
|
docsBpi2CmtsIpMulticastMapTable
docsBpi2CmtsMulticastAuthTable.
|
These tables are supported in the DOCS-BPI-PLUS-MIB in Cisco IOS Release 12.3(23)BC or later on the Cisco uBR10012 router.
|
DOCS-CABLE-DEVICE-MIB
The DOCS-CABLE-DEVICE-MIB contains objects to configure and monitor DOCSIS-compliant CMTS platforms and cable modem devices. This MIB was released as RFC 2669. The MIB is specific to the uBR10K cable platform.
The MODULE-IDENTITY for the DOCS-CABLE-DEVICE-MIB is docsDev and its top-level OID is 1.3.6.1.2.1.69 (iso.org.dod.internet.mgmt-mib-2.docsDev).
MIB Constraints
Table 3-27 lists the constraints that the router places on DOCS-CABLE-DEVICE-MIB.
.
Table 3-27 DOCS-CABLE-DEVICE-MIB Constraints
MIB Object
|
Notes
|
docsDevEventTable
|
This table is supported in Cisco IOS Release 12.1(5)EC and later releases, and holds a maximum number of 50 events.
When the table is full and a new event occurs, the oldest event is removed and replaced by the new event. The docsDevEvIndex, however, continues incrementing, up to its maximum value of 2,147,483,647.
|
•docsDevSerialNumber docsDevRole
docsDevSTPControl
|
Not supported on the CMTS
|
•docsDevSoftware
|
This group of objects is not supported on the CMTS.
|
•docsDevCpeIpMax
|
Initial DOCSIS 1.1 specifications set this object to 1, but CableLabs has determined that this default can prevent PCs from communicating in certain situations (such as when the PC is booted up and defaults to a private IP address before being connected to the cable modem or before the cable modem is turned on). The cable modem must be rebooted to allow the PC to communicate.
A change notice has been introduced to change the default to -1, which disables IP filtering, but this change notice has not been given final approval or been implemented. We therefore recommend configuring this parameter either to -1 or to a value greater than 1.
|
DOCS-CABLE-DEVICE-TRAP-MIB
The DOCS-CABLE-DEVICE-TRAP-MIB contains objects that supplement the DOCS-CABLE-DEVICE-MIB to define and configure traps and notifications for DOCSIS-compliant CMTS platforms and cable modems.
The MODULE-IDENTITY for the DOCS-CABLE-DEVICE-TRAP-MIB is docsDevTrapMIB, and its top-level OID is 1.3.6.1.2.1.69.10 (iso.org.dod.internet.mgmt-mib-2.docsDev.docsDevTrapMIB).
MIB Constraints
Table 3-28 lists the constraints that the router places on DOCS-CABLE-DEVICE-TRAP-MIB.
.
Table 3-28 DOCS-CABLE-DEVICE-TRAP-MIB Constraints
MIB Object
|
Notes
|
docsDevTable
|
|
•docsIfDocsisCapability
•docsIfDocsisOperMode
|
Both objects are deprecated.
|
DOCS-IFEXT2-MIB
ThE DOCS-IFEXT2-MIB contains management objects to enhance DOCSIS 2.0 feature set. It includes objects to manage SCDMA capability for limiting the number of codes assigned to a cable modem over the total active codes, referred to as Maximum Scheduled Codes (MSC).
MIB Constraints
Table 3-29 lists the constraints that the router places on DOCS-IFEXT2-MIB.
.
Table 3-29 DOCS-IFEXT2-MIB Constraints
MIB Object
|
Notes
|
docsIfExt2CmtsUpChannelTable
|
|
•docsIfExt2CmtsUpChannelTotalCMs
|
Read-only.
|
DOCS-IF-EXT-MIB
The DOCS-IF-EXT-MIB contains objects that supplement the DOCS-IF-MIB to provide information about the capabilities and status of online cable modems.
The MODULE-IDENTITY for the DOCS-IF-EXT-MIB is docsIfExtMib, and its top-level OID is 1.3.6.1.2.1.10.127.21 (iso.org.dod.internet.mgmt.mib-2.transmission.docsIfMIB.docsIfExtMib).
MIB Constraints
Table 3-30 lists the constraints that the router places on DOCS-IF-EXT-MIB.
.
Table 3-30 DOCS-IF-EXT-TRAP-MIB Constraints
MIB Object
|
Notes
|
docsDevTable
|
In Cisco IOS Release 12.2(15)BC1 and later releases, this MIB has been deprecated and removed as part of the support for the DOCSIS 2.0 specifications. The objects in this MIB have been replaced by new objects in the DOCS-IF-MIB and the proposed DOCS-RFI-MIB, so as to conform to the requirements given in the DOCSIS 2.0 Operations Support System Interface Specification (SP-OSSIv2.0-I04-030730).
|
•docsIfDocsisBaseCapability
|
Replaces docsIfDocsisCapability and docsIfDocsisOperMode
|
•docsIfCmtsCmStatusDocsisRegMode
|
Replaces docsIfCmtsCmStatusDocsisMode
|
DOCS-IF-M-CMTS-MIB
The DOCS-IF-M-CMTS-MIB contains the management objects to configure and manage theDownstream External PHY Interface (DEPI) of the M-CMTS architecture (Modular CMTS). This MIB defines objects to manage:
•Static configuration of DEPI L2TPv3 tunnels.
•Status information for dynamic DEPI L2TPv3 sessions that may be created by Embedded Resource Manager Infrastructure (ERMI).
MIB Constraints
Table 3-31 lists the constraints that the router places on DOCS-IF-M-CMTS-MIB.
.
Table 3-31 DOCS-IF-M-CMTS-MIB Constraints
MIB Object
|
Notes
|
docsIfMCmtsDepiSessionConfigTable
|
Read-only.
|
docsIfMCmtsDepiRsrcAllocTable
|
Not supported.
|
docsIfMCmtsDepiSessionCinLatency
|
Read-only.
|
docsIfMCmtsDepiPhbPolicyTable
|
Not supported.
|
docsIfMCmtsQosServiceFlowExtTable
|
Not supported.
|
DocsIfMCmtsDepiSessionInfoTable
|
|
•docsIfMCmtsDepiSessionInfoState
|
The valid values are:
•other(1),
•depiSessionUp(2),
•depiSessionError(3),
•depiSessionInProgress(4)
Note The value depiSessionInProgress indicates that the DEPI session is configured but not yet established. The value changes to depiSessionUp after the connection is established.
|
DOCS-LOADBAL3-MIB
The DOCS-LOADBAL3-MIB defines objects to support the requirements of CableLabs DOCSIS 3.0 certification. This MIB is based on the requirement specified by CM-SP-OSSIv3.0-I05-071206.
The following objects are defined in this MIB to support DOCSIS 3.0 certification:
•docsLoadbal3MibObjects
•docsLoadbal3System
•docsLoadbal3ChgOverGroup
•docsLoadbal3ChgOverStatusTable
•docsLoadbal3CmtsCmParamsTable
•docsLoadbal3GeneralGrpDefaults
•docsLoadbal3GeneralGrpCfgTable
•docsLoadbal3ResGrpCfgTable
•docsLoadbal3GrpStatusTable
•docsLoadbal3RestrictCmCfgTable
•docsLoadbal3PolicyTable
•docsLoadbal3BasicRuleTable
MIB Constraints
Table 3-32 lists the constraints that the router places on DOCS-LOADBAL3-MIB.
.
Table 3-32 DOCS-LOADBAL3-MIB Constraints
MIB Object
|
Notes
|
ChChgInitTechMap
|
An empty value or a value with all zero bits is not supported.
|
docsLoadbal3ChgOverGroup
|
DBC operation is not be supported.
|
docsLoadbal3ChgOverStatusTable
|
Contains up to 100 entries. The table is cleared after PRE switchover.
|
docsLoadbal3ResGrpCfgId
|
The valid values are restricted in the range of 1-0x7fffffff since the ID range of 0x80000000-0xffffffff is reserved for DOCSIS 3.0 GLBG.
|
docsLoadbal3ResGrpCfgMdIfIndex
|
The D3.0 RLBG Configuration MIB uses docsLoadbal3ResGrpCfgMdIfIndex, docsLoadbal3ResGrpCfgDsChList, docsLoadbal3ResGrpCfgUsChList to identify the channels, which indicates that all the channels in the RLBG must be within one MAC domain. The RLBG restricted in one MAC domain can be retrieved correctly.
|
docsLoadbal3ResGrpCfgServiceTypeId
|
This object represents a space separated list of ServiceType IDs where all characters in each Service Type ID must be printable.
|
docsLoadbal3GrpStatusId
|
For GLBG, value is MD-CM-SG-ID plus 0x80000000, which is changed after LC switchover.
|
docsLoadbal3GrpStatusChgOverSuccess
docsLoadbal3GrpStatusChgOverFails
|
The values are cleared after PRE switchover.
|
docsLoadbal3BasicRuleEnable
|
Valid values are :
•enabled(1)
•disabled(2)
•disabledPeriod(3).
|
docsLoadbal3PolicyPtr
|
Read-only, equal to the configured rule object.
|
docsLoadbal3CmtsCmParamsProvGrpId
docsLoadbal3CmtsCmParamsProvServiceTypeID
|
Read-only.
|
docsLoadbal3SystemEnableError
|
Read only.
|
docsLoadbal3BasicRuleDisStart
docsLoadbal3BasicRuleDisPeriod
|
The valid values are in the range of 0-86400.
|
docsLoadbal3RestrictCmCfgMacAddrMask
|
The valid value should have consecutive bits set from MSB.
|
docsLoadbal3RestrictCmCfgGrpId
docsLoadbal3RestrictCmCfgServiceTypeId
|
All characters in Service Type ID must be printable. One of the two objects should have a valid value.
|
DOCS-LOADBALANCING-MIB
The DOCS-LOADBALANCING-MIB contains objects to support the requirements of CableLabs DOCSIS 2.0 certification. This MIB is based on detailed requirement specified by CM-SP-OSSIv2.0-I10-070803. The following objects are defined in this MIB to support DOCSIS 2.0 certification:
•docsLoadBalNotifications
•docsLoadBalMibObjects
•docsLoadBalSystem
•docsLoadBalChgOverObjects
•docsLoadBalGrpObjects
•docsLoadBalPolicyObjects
•docsLoadBalChgOverGroup
MIB Constraints
Table 3-33 lists the constraints that the router places on DOCS-LOADBALANCING-MIB.
.
Table 3-33 DOCS-LOADBALANCING-MIB Constraints
MIB Object
|
Notes
|
ChannelChgInitTechMap
|
An empty value or a value with all zero bits is not supported.
|
docsLoadBalChgOverStatusTable
|
Contains up to 100 entries. The table is cleared after PRE switchover.
|
docsLoadBalGrpId
|
The valid values are restricted in the range of 1-0x7fffffff since the ID range of 0x80000000-0xffffffff is reserved for DOCSIS 3.0 GLBG.
|
docsLoadBalGrpChgOverSuccess
docsLoadBalGrpChgOverFails
|
The values are cleared after PRE switchover
|
docsLoadBalChnPairsIfIndexDepart
docsLoadBalChnPairsIfIndexArrive
|
Only the value that is part of the Load Balancing Group is valid.
|
docsLoadBalBasicRuleEnable
|
Valid values are :
•enabled(1)
•disabled(2)
•disabledPeriod(3).
|
docsLoadBalPolicyRulePtr
|
Read-only, equal to the configured rule object.
|
docsLoadBalCmtsCmStatusGroupId
|
Read-only.
|
docsLoadBalRestrictCmMacAddrMask
|
The valid value should have consecutive bits set from MSB.
|
DOCS-MCAST-AUTH-MIB
The DOCS-MCAST-AUTH-MIB contains objects to manage the CMTS Multicast Authorization Module. This MIB enables management of multicast over DOCSIS to support Multicast DSID forwarding and bonded multicast. The IP Multicast Join Authorization feature allows you to control the IP multicast sessions that multicast session join. The multicast sessions are accessed through a CM. The following objects are defined in this MIB to support DOCSIS 3.0 OSS SNMP features:
•docsMcastAuthCmtsCmStatusTable: This object defines attributes to manage status of Multicast Authorization policies for each CM. The CM acquires these policy parameters through the CM registration process. If the required policy parameters are not available, these policies are obtained from the control object.
•docsMcastAuthProfileSessRuleTable: This object defines attributes to store profiles that perform the authorization process. This object supports the creation and deletion of multiple profile instances.
•docsMcastAuthProfilesTable: This object defines attributes to store the description of the Multicast Authorization profiles for administrative purposes. This object supports the creation and deletion of multiple profile instances.
MIB Constraints
Table 3-34 lists the constraints that the router places on DOCS-MCAST-AUTH-MIB.
.
Table 3-34 DOCS-MCAST-MIB Constraints
MIB Object
|
Notes
|
docsMcastCmtsGrpCfgTable
|
|
•docsMcastCmtsGrpCfgCfgId
|
Not accessible.
|
•docsMcastCmtsGrpCfgSrcPrefixAddr
|
Read-only.
|
•docsMcastCmtsGrpCfgSrcPrefixLen
|
Read-only.
|
•docsMcastCmtsGrpCfgSrcPrefixLen
|
Read-only.
|
•docsMcastCmtsGrpCfgGrpPrefixLen
|
Read-only.
|
docsMcastCmtsGrpQosCfgTable
|
|
•docsIf3MdChCfgRowStatus
|
Only CreateAndGo(4) and destory(6) operations supported.
|
docsMcastCmtsGrpEncryptCfgTable
|
|
•docsMcastCmtsGrpEncryptCfgId
|
Not accessible.
|
docsMcastCmtsGrpEncryptCfgTable
|
|
•docsMcastCmtsGrpEncryptCfgId
|
Not accessible.
|
docsMcastCmtsReplSessTable
|
|
•docsMcastCmtsReplSessPrefixAddrType
|
Not accessible.
|
•docsMcastCmtsReplSessGrpPrefix
|
Not accessible.
|
•docsMcastCmtsReplSessSrcPrefix
|
Not accessible.
|
•docsMcastCmtsReplSessMdIfIndex
|
Not accessible.
|
•docsMcastCmtsReplSessDcsId
|
Not accessible.
|
•docsMcastCmtsReplSessServiceFlowId
|
Not accessible.
|
DOCS-IF3-MIB
The DOCS-IF3-MIB contains objects to manage DOCSIS 3.0 features such as primary channel bonding, interface topology, and enhanced signal quality monitoring.
The DOCS-IF3-MIB defines the following objects to support DOCSIS 3.0 feature:
•docsIf3CmtsCmRegStatusTable —Defines attributes to store registration status of the Cable Modem (CM).
•docsIf3MdCfgTable — Defines attributes to store MAC domain level control and configuration information.
•docsIf3CmtsCmUsStatusTable — Defines status information of the CM using upstream logical channels.
•docsIf3MdUsSgStatusTable — Returns the list of upstream channels associated with a MAC Domain MD-US-SGID attribute.
•docsIf3UsBondingGrpStatusTable — Returns administratively configured and CMTS-defined upstream bonding groups.
•docsIf3UsChExtTable — Defines management extensions for upstream channels corresponding to specific SCDMA parameters.
•docsIf3UsChSetTable — Defines a set of upstream channels associated with channel bonding groups such as MD-US-SGs, MD-CM-SGs, or a channel set that the CMTS may derive from other CMTS processes.
•docsIf3SignalQualityExtTable — Defines attributes to store in-channel modulation error ratio metric for CM and CMTS.
•docsIf3CmtsSpectrumAnalysisMeasTable — Defines attributes to configure the logical upstream interfaces for performing the spectrum measurements. This object supports create and delete operations.
•docsIf3BondingGrpCfgTable — Defines statically configured Downstream Bonding Groups and Upstream Bonding Groups on the CMTS.
•docsIf3CmtsSignalQualityExtTable — Defines attributes to manage metrics and parameters associated with received carrier, noise, and interference power levels in the upstream channels of the CMTS.
•docsIf3MdChCfgTable — Defines objects to configure the association between downstream and upstream channels to a particular MAC Domain(MD) on a CMTS.
•docsIf3RccCfgTable — Defines objects to identify the scope of the Receive Channel Configuration (RCC) and provides a top level container for the Receive Module and Receive Channel objects.
•docsIf3RccStatusTable — Defines the objects that provide a read-only view of the statically-configured (from the RccCfg object) and dynamically-created RCCs.
•docsIf3RxChCfgTable — Defines the Receive Channel Configuration on the CMTS.
•docsIf3RxChStatusTable — Defines the Receive Channel Status objects that report the status of the statically-configured and dynamically-created Receive Channels within an RCC.
•docsIf3RxModuleCfgTable — Defines the Receive Module Configuration on the CMTS.
•docsIf3RxModuleStatusTable — Defines the Receive Module Status objects that provide a read-only view of the statically configured and dynamically created Receive Modules within an RCC.
•docsIf3MdNodeStatusTable — Defines objects that report the MD-DS-SG-ID and MD-US-SG-ID associated with a MD-CM-SG-ID within a MAC Domain and the Fiber Nodes available to the MD-CM-SG.
•docsIf3MdDsSgStatusTable — Defines the objects that return a list of downstream channel associated with a MAC Domain MD-DS-SG-ID.
•docsIf3MdUsToDsChMappingTable — Defines the objects that return a set of downstream channels that carry UCDs and MAPs for a particular upstream channel in a MAC Domain.
•docsIf3DsBondingGrpStatusTable — Defines the objects that return administratively-configured and CMTS defined downstream bonding groups.
•docsIf3DsChSetTable — Defines the objects for a set of downstream channels. These channel sets may be associated with channel bonding groups, MD-DS-SGs, MD-CM-SGs, or any other channel set that the CMTS derives from the other CMTS processes.
MIB Constraints
There are no constraints for this MIB.
DOCS-IF-MIB
The DOCS-IF-MIB contains objects to configure and monitor the radio frequency (RF) interfaces on DOCSIS-compliant CMTS platforms and cable modems. This MIB was released as RFC 2670. This MIB has been updated to draft-ietf-ipcdn-rfmibv2-05.txt.
The MODULE-IDENTITY for the DOCS-IF-MIB is docsIfMIB and its top-level OID is 1.3.6.1.2.1.10.127 (iso.org.dod.internet.mgmt.mib-2.transmission.docsIfMIB). One of the most commonly used OIDs is docsIfUpChannelWidth (1.3.6.1.2.1.10.127.1.1.2.1.3). The following tables are added to this MIB to manage logical channels:
•docsIfUpstreamChannelTable
•docsIfCmtsModulationTable
•docsIfSignalQualityTable
•docsIfCmtsCmstatusTable
The following attributes of docsIfCmtsCmStatusTable are not supported because they rely on single upstream channel parameter whereas the DOCSIS 3.0 online cable modem has more than one upstream channels.
•docsIfCmtsCmStatusUpChannelIfIndex
•docsIfCmtsCmStatusRxPower
•docsIfCmtsCmStatusSignalNoise
•docsIfCmtsCmStatusModulationType
•docsIfCmtsCmStatusTimingOffset
•docsIfCmtsCmStatusEqualizationData
MIB Constraints
Table 3-35 lists the constraints that the router places on DOCS-IF-MIB.
.
Table 3-35 DOCS-IF-MIB Constraints
MIB Object
|
Notes
|
docsIfUpstreamChannelTable
|
|
•docsIfUpChannelWidth
docsIfUpChannelSlotSize
|
The channel width and minislot size are related. Trying to set the channel width or minislot size separately fails if the new value is incompatible with the current setting of the other parameter..
In addition, setting both objects together is supported only in Cisco IOS Release 12.2(15)BC2 and later releases.
|
docsIfCmtsMacToCmTable
|
Do not use GET-NEXT requests to retrieve the rows of this table, because it requires lengthy, time-consuming searches on the MAC address, which could consume excessive amounts of CPU processor time when the table is large. Instead, retrieve the individual rows using a GET request that uses the device's MAC address as the table index. This avoids possible performance problems and also ensures that the retrieved rows contain the most current, real-time data for those devices.
A GET request for docsIfCmtsMacToCmTable returns NULL if the router is already processing another request for this table (either by an SNMP GET or CLI show command). A null string is returned if the router is processing a request for any other table that is indexed by CM or CPE MAC address, such as cdxCmCpeEntry, cdrqCmtsCmStatusTable, and docsQosCmtsMacToSrvFlowTable.
Wait until the first request is done and then repeat the request for docsIfCmtsMacToCmTable.
|
docsIfCmtsModulationTable
|
|
•docsIfCmtsModGuardTimeSize
•docsIfCmtsModPreambleLen
|
The SNMP agent might report a guard time (docsIfCmtsModGuardTimeSize) and preamble length (docsIfCmtsModPreambleLen) that do not match the values that are configured using the CLI for a particular modulation profile.
This occurs when the CLI values are not appropriate for the particular PHY type and cable interface being used, and the Cisco IOS overrides the CLI values with values that are more appropriate.
|
docsIfCmtsTable
|
|
•docsIfCmtsUcdInterval
|
Read-only.
|
•docsIfSigQSignalNoise
|
This object cannot be used with Cisco uBR-MC16S cable interface line cards when spectrum groups are configured in Cisco IOS Release 12.2(15)BC2 and earlier releases.
|
•docsIfUpChannelStatus
|
Not implemented.
|
•docsIfUpChannelModulationProfile
|
If the Cisco CMTS is configured with two modulation profiles (dynamic upstream modulation), this object returns whichever of the two profiles is currently active. This means that even if you set this object with one profile, it could return the other profile the next time it is read.
|
•docsIfQosProfMaxTxBurst
|
Deprecated and always returns NULL.
|
•docsIfCmtsCmStatusExtUnerroreds
•docsIfCmtsCmStatusExtCorrecteds
•docsIfCmtsCmStatusExtUncorrectables
|
Supported only in Cisco IOS Release 12.2(15)BC2 and later releases. In previous releases, these objects always return NULL.
|
•docsIfCmtsServiceCreateTime
|
Before Cisco IOS Release 12.2(15)BC1, this object displays the same creation time for all Service IDs (SIDs) for the same cable modem. In Cisco IOS Release 12.2(15)BC1 and later releases, this object shows the correct creation time for each SID.
|
•docsIfCmtsQosProfilePermissions
|
This object accurately sets the QoS profile permissions in Cisco IOS Release 12.1(20)EC, Cisco IOS Release 12.2(4)BC1, and later releases.
|
docsIfCmtsChannelUtilizationTable
|
Read-only.
|
•docsIfCmtsChannelUtIfType
|
Value is IANAifType
|
•docsIfCmtsChannelUtId
|
Value is Integer32
|
•docsIfCmtsChannelUtUtilization
|
Value is Integer32
|
•docsIfCmtsChannelUtilizationInterval
|
Read, write.
|
docsIfUpstreamChannelTable
|
|
•docsIfUpChannelPreEqEnable
|
|
docsIfSignalQualityTable
|
|
•docsIfSigQExtUnerroreds
|
Read-only. Value is 64-bit counter.
|
•docsIfSigQExtCorrecteds
|
Read-only. Value is 64-bit counter.
|
•docsIfSigQExtUncorrectables
|
Read-only. Value is 64-bit counter.
|
docsIfCmtsDownChannelCounterTable
|
Read-only.
|
•docsIfCmtsDownChnlCtrId
|
Value is Integer32
|
•docsIfCmtsDownChnlCtrTotalBytes
|
Value is Counter32
|
•docsIfCmtsDownChnlCtrUsedBytes
|
Value is Counter32
|
•docsIfCmtsDownChnlCtrExtTotalBytes
|
Value is Counter64
|
•docsIfCmtsDownChnlCtrExtUsedBytes
|
Value is Counter64
|
docsIfCmtsUpChannelCounterTable
|
Read-only.
|
•docsIfCmtsUpChnlCtrId
|
Value is Integer32
|
•docsIfCmtsUpChnlCtrTotalMslots
|
Value is Counter32
|
•docsIfCmtsUpChnlCtrUcastGrantedMslot
|
Value is Counter32
|
•docsIfCmtsUpChnlCtrTotalCntnMslots
|
Value is Counter32
|
•docsIfCmtsUpChnlCtrUsedCntnMslots
|
Value is Counter32
|
•docsIfCmtsUpChnlCtrExtTotalMslots
|
Value is Counter64
|
•docsIfCmtsUpChnlCtrExtUcastGrantedMslots
|
Value is Counter64
|
•docsIfCmtsUpChnlCtrExtTotalCntnMslots
|
Value is Counter64
|
•docsIfCmtsUpChnlCtrExtUsedCntnMslots
|
Value is Counter64
|
Note When using docsIfCmtsQosProfilePermissions to remove the create by modem permission from cable modems, prohibits only future activity by cable modems and deletes only unused QoS profiles that have been created by cable modems; it does not affect QoS profiles that are currently in use. This behavior is different than the no cable qos permission modem command, which immediately deletes QoS profiles that have been created by the cable modems and takes those modems offline.
Note Use cable util-interval interval command to update docsIfCmtsChannelUtilizationInterval/ccwbRFChanUtilInterval attribute.
The value of docsIfCmtsChannelUtilizationInterval ranges from 1 - 86400 seconds. Table 3-36 lists the tables/IPDR schemas affected by docsIfCmtsChannelUtilizationInterval attribute:
Table 3-36 Tables/IPDR Schemas Affected by docsIfCmtsChannelUtilizationInterval Attribute
Table/IPDR Schema
|
Impact
|
docsIfCmtsChannelUtilizationInterval/ccwbRFChanUtilInterval
|
New utilization value is based on the value derived from CLI.
|
docsIfCmtsChannelUtUtilization/ccwbRFChannelUtilization
|
New utilization value is calculated using the new interval value.
|
US-UTIL/DS-UTIL
|
These two IPDR schemas use new interval to calculate channel utilization.
|
Note Although the value of docsIfCmtsChannelUtilizationInterval ranges from 1 - 86400 sec, we suggest to choose a value greater than 300 sec (five minutes).
For more information on utilization, see Usage Based Billing for the Cisco CMTS Routers.
Constraints in Cisco IOS Release 12.2(33)SCC
There are no entries for the narrowband SPA downstream channels for the tables docsIfDownstreamChannelTable and docsIfCmtsDownChannelCounterTable in Cisco IOS Release 12.2(33)SCC. Note that the CISCO-CABLE-WIDEBAND-MIB contains narrowband information.
However, the following changes were introduced in the previous release, Cisco IOS release 12.3(23)SCB:
•docsIfCmtsCmStatusDownChannelIfIndex—See Table 3-37. This object points to the corresponding narrowband channel's SNMP IF index, or the Modular Cable Interface SNMP IF index.
Table 3-37 docsIfCmtsCmStatusDownChannelIfIndex
MIB Attribute
|
Value
|
Notes
|
docsIfCmtsCmStatusIndex
|
No impact
|
|
docsIfCmtsCmStatusMacAddress
|
No impact
|
|
docsIfCmtsCmStatusIpAddress
|
No impact
|
|
docsIfCmtsCmStatusDownChannelIfIndex
|
NB channel ifindex
|
Return 0 if is unknown
|
docsIfCmtsCmStatusUpChannelIfIndex
|
Up channel
|
Return 0 if is unknown
|
docsIfCmtsCmStatusRxPower
|
No impact
|
|
docsIfCmtsCmStatusTimingOffset
|
No impact
|
|
docsIfCmtsCmStatusEqualizationData
|
No impact
|
|
docsIfCmtsCmStatusValue
|
No impact
|
|
docsIfCmtsCmStatusUnerroreds
|
No impact
|
|
docsIfCmtsCmStatusCorrecteds
|
No impact
|
|
docsIfCmtsCmStatusUncorrectables
|
No impact
|
|
docsIfCmtsCmStatusSignalNoise
|
No impact
|
|
docsIfCmtsCmStatusMicroreflections
|
No impact
|
|
docsIfCmtsCmStatusExtUnerroreds
|
No impact
|
|
docsIfCmtsCmStatusExtCorrecteds
|
No impact
|
|
docsIfCmtsCmStatusExtUncorrectables
|
No impact
|
|
docsIfCmtsCmStatusDocsisRegMode
|
No impact
|
|
docsIfCmtsCmStatusModulationType
|
No impact
|
|
docsIfCmtsCmStatusInetAddressType
|
No impact
|
|
docsIfCmtsCmStatusInetAddress
|
No impact
|
|
docsIfCmtsCmStatusValueLastUpdate
|
No impact
|
|
DOCS-DIAG-MIB
The DOCS-DIAG-MIB contains objects that enable early error detection, fault management, and troubleshooting the cable network. A diagnostic log is created for CMTS that can be used to to prevent service interruptions.
Note The size of docsDiagLogMaxSize is for total CMTS. The log size is limited to latest 1000 records that are stored in the corresponding linecard. Although we can set docsDiagLogMaxSize to 4294967295, only 1000 records are logged.
DOCS-DRF-MIB
The DOCS-DRF-MIB contains the management objects to manage Downstream RF Interface specifications.
DOCS-DSG-IF-MIB
The DOCS-DSG-IF-MIB contains objects to manage the DOCSIS Set-top Gateway (DSG). The DSG provides a one-way IP datagram transport for Out-of-Band (OOB) messaging to cable set-top clients. The one-way IP datagram transport is called a DSG tunnel. A DSG tunnel carrying either a broadcast, unicast, or multicast IP datagram stream originating at the DOCSIS Set-top Gateway and carrying Out-of-Band messages is intended for set-top clients. It is carried over one or more downstream DOCSIS channels. Multiple DSG tunnels may exist on a single downstream DOCSIS channel.
The following MIB tables were added with this release:
•dsgIfClassifierTable—Contains attributes use to classify inbound packets into the tunnel and classifiers for the DSG clients, encoding in the DCD messages on the downstream channels to which the classifiers apply.
•dsgIfTunnelTable—Contains group(s) of tunnel(s). Each tunnel is associated to the destination MAC address and associated to the QOS service class name.
•dsgIfTunnelGrpToChannelTable—Associates a group of tunnels to one or more downstream channel.
•dsgIfDownstreamChannelTable—Contains the associated timers, vendor specific parameters index and the channel list index to a specific downstream.
•dsgIfClientIdTable—Contains the client identification type and value. It also contains the vendor specific parameter identification.
•dsgIfVendorParamTable—Allows vendors to send specific parameters to the DSG clients within a DSG rule or within the DSG Configuration block in a DCD message.
•dsgIfChannelListTable—Contains list of one or multiple downstream frequencies that are carrying DSG tunnel(s).
•dsgIfTimerTable—Contains timers that are sent to the DSG client(s) through the DCD message.
Note DOCS-DSG-IF-MIB does not support Route Processor Redundancy Plus (RPR+) mode.
Note The DOCS-DSG-IF-MIB defines objects that are used to configure, control, and monitor the operation of the DOCSIS Set-top Gateway (DSG) 1.0 feature on Cisco uBR7200 series and Cisco uBR10012 routers. For detailed information about DOCSIS DSG, go to:
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00802065c8.html
Note The DOCS-DSG-IF-MIB top-level OID is 1.3.6.1.4.1.4491.2.1.3 (iso.org.dod.internet.private.enterprises.cableLabs.clabProject.clabProjDocsis.dsgIfMIB).
MIB Constraints
Prior to Cisco IOS Release 12.3(23)BC, there are no constraints on the DOCS-DSG-IF-MIB. (All objects listed in this MIB are implemented as defined in the MIB definition.)
Wideband Support in Cisco IOS Release 12.2(33)SCB
The DOCS-DSG-IF-MIB is defined to manage DOCSIS Set-top Gateway interfaces in the following manner.
•DSG is configured on the MC interface's CGD master interface.
•A packet transmits via Multicast to the DOCSIS Set-top Gateway (DSG).
•Cisco IOS uses an IGMP configuration command to control the packets.
In Cisco IOS Release 12.3(23)BC and later, Cisco IOS no longer accepts SNMP that is mapped in the the dsgIfTunnelGrpToChannelTable on MC interface. In this circumstance, an INCONSISTENT_VALUE_ERROR system message is reported, and a corresponding error message is prompted as follows:
Cannot set dsg tunnel group to Modular-Cable interface, set on CGD's host downstream
instead.
DOCS-IETF-BPI2-MIB
The DOCS-IETF-BPI2-MIB contains objects to manage baseline privacy plus interface (BPI+) in CMTSs.
DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB
The DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB contains objects to define and configure traps and notifications for DOCSIS-compliant CMTS platforms and cable modems.
DOCS-IETF-QOS-MIB
The DOCS-IETF-QOS-MIB contains objects to manage information for Quality Of Service (QOS) for DOCSIS 1.1 and 2.0.
MIB Constraints
Refer to MIB constraints section under DOCS-QOS-MIB.
DOCS-QOS3-MIB
The DOCS-QOS3-MIB contains objects to manage QOS for channel bonding. This MIB contains the following objects to support DOCSIS 3.0 features:
•docsQos3ParamSetTable — Describes the set of QOS parameters defined in a managed device.
•docsQos3DynamicServiceStatsTable — Defines attributes to store statistics associated with the Dynamic Service Flows, Dynamic Channel Changes, and Dynamic Bonding Changes on a managed device within a MAC Domain.
•docsQos3ServiceClassTable — Defines a provisioned service class on a CMTS.
•docsQos3PktClassTable — Describes the packet classification configured on the CM or CMTS. Each packet, received or transmitted on an interface, is compared against an ordered list of rules related to the packet contents.
•docsQos3GrpServiceFlowTable — Defines attributes to store additional service flow information for Group Service Flows (GSFs).
•docsQos3GrpPktClassTable — Defines attributes to store additional packet classification information for Group Classifier References (GCRs) in a GSF.
•docsQos3UpChCounterExtTable — Defines attributes to store additional information on upstream channel bonding.
•docsQos3ServiceFlowCcfStatsTable — Defines upstream service flow statistics on upstream fragments for Continous Concatenation and Fragmentation (CCF).
•docsQos3ServiceFlowTable: Defines the objects to describe the set of DOCSIS-QOS ServiceFlows in a managed device.
•docsQos3ServiceFlowStatsTable: Defines the objects to describe the statistics associated with the Service Flows in a managed device.
•docsQos3UpstreamStatsTable: Defines the objects to describe the statistics associated with upstream service flows. All counted frames must be received without a Frame Check Sequence (FCS) error.
•docsQos3ServiceFlowLogTable: Defines the objects to store a log of the disconnected Service Flows in a managed device.
•docsQos3PHStable: Defines the objects to describe the set of payload header suppression of Service Flows.
•docsQos3CmtsMacToSrvFlowTable: Defines the object to manage the mapping of unicast service flows with the cable modem the service flows belongs to.
•docsQos3CmtsDsidTable: Defines the objects to describe the DSID information stored in the CMTS.
•docsQos3CmtsDebugDsidTable: Defines the CMTS Debug DSID objects to control the DSID debug statistics reporting.
•docsQos3CmtsDebugDsidStatsTable: Defines the CMTS Debug DSID Stats objects to describe the statistics at the CMTS for forwarding the DSID-labeled downstream packets.
MIB Constraints
Table 3-38 lists the constraints that the router places on DOCS-QOS3-MIB.
.
Table 3-38 DOCS-QOS3-MIB Constraints
MIB Object
|
Notes
|
docsQos3PktClassTable
|
|
•docsQos3PktClassFlowLabel
|
Not supported.
|
•docsQos3PktClassCmInterfaceMask
|
Not supported.
|
docsQosParamSetTable
|
This table describes the set of DOCSIS 1.1 QOS parameters defined in a managed device.
|
•docsQosParamSetMaxTrafficBurst
|
Valid only for Best Effort, non-Real-Time Polling, and Real-Time Polling bursts. For all other bursts, this object reports 0.
|
•docsQosServiceClassDirection
•docsQosServiceClassSchedulingType
|
These objects must be set together as part of the same SET request when configuring a downstream service class.
|
•docsQosParamSetEntry
|
Identifies a unique set of QoS parameters.
|
docsQos3ServiceFlowDsid
|
Contains the downstream traffic counters for cable modems.
|
•docsQosServiceFlowStatsEntry
|
Describes a set of service flow statistics. Each Service Flow ID is logged in the table.
|
docsQos3ServiceClassTable
|
|
•docsQos3ServiceClassStorageType
|
Not supported.
|
•docsQos3ServiceClassDSCPOverwrite
|
Not supported.
|
•docsQos3ServiceClassRequiredAttrMask
|
Not supported.
|
•docsQos3ServiceClassForbiddenAttrMask
|
Not supported.
|
•docsQos3ServiceClassAttrAggrRuleMask
|
Not supported.
|
•docsQos3ServiceClassPeakTrafficRate
|
Not supported.
|
•docsQos3ServiceClassDsResequencing
|
Not supported.
|
•docsQos3ServiceClassName
|
Not accessible.
|
docsQos3CmtsDebugDsidTable
|
|
•docsQos3CmtsDebugDsidRowStatus
|
Valid values are: active(1), createAndGo(4), and destroy(6).
|
docsQos3PktClassTable
|
|
•docsQos3PktClassId
|
Not accessible.
|
•docsQos3PktClassFlowLabel
|
Not supported.
|
docsQos3ParamSetMultiplierContentionReqWindow
|
Default value is eight (8).
|
docsQos3GrpServiceFlowTable
|
The GSFs on the wideband interfaces are not supported.
|
docsQos3GrpPktClassTable
|
The GCRs in a GSF on the wideband interfaces are not supported.
|
docsQos3ParamSetTable
|
|
•docsQos3ParamSetServiceFlowId
|
Not accessible.
|
docsQos3DynamicServiceStatsTable
|
|
•docsQos3IfDirection
|
Not accessible.
|
DOCS-QOS-MIB
The DOCS-QOS-MIB contains objects to configure and monitor the QoS features that are available in DOCSIS 1.1 and DOCSIS 2.0 cable networks. This MIB was published as an Internet Draft, Data Over Cable System Interface Specification Quality of Service Management Information Base.
The MODULE-IDENTITY for the DOCS-QOS-MIB is docsQosMIB, and its top-level OID is 1.3.6.1.2.1.10.127.7 (iso.org.dod.internet.mgmt.mib-2.transmission.docsIfMIB.docsQosMIB).
MIB Constraints and Notes
This MIB is supported only in Cisco IOS Release 12.2(4)BC1 through Release 12.2(11)BC3 to support DOCSIS 1.1 operations. The MIB is deprecated in later releases to conform with the DOCSIS 2.0 specifications. Table 3-39 lists the constraints that the router places on DOCS-QOS-MIB.
.
Table 3-39 DOCS-QOS-MIB Constraints
MIB Object
|
Notes
|
docsQosCmtsMacToSrvFlowTable
|
Do not use GET-NEXT requests to retrieve the rows of this table, because it could require lengthy, time-consuming searches on the MAC address, which could consume excessive amounts of CPU processor time when the table is large. Instead, retrieve the individual rows using a GET request that uses the device's MAC address as the table index. This avoids possible performance problems and also ensures that the retrieved rows contain the most current, real-time data for those devices.
A GET request for docsQosCmtsMacToSrvFlowTable returns NULL if the router is already processing another request for this table (either by an SNMP GET or CLI show command). A null is also returned if the router is processing a request for any other table that is indexed by CM or CPE MAC address, such as cdxCmCpeEntry, cdrqCmtsCmStatusTable, and docsIfCmtsMacToCmTable.
Wait until the first request is done and then repeat the request for docsQosCmtsMacToSrvFlowTable.
|
docsQosParamSetTable
|
This table describes the set of DOCSIS 1.1 QOS parameters defined in a managed device.
|
•docsQosParamSetMaxTrafficBurst
|
Valid only for Best Effort, non-Real-Time Polling, and Real-Time Polling bursts. For all other bursts, this object reports 0.
|
•docsQosServiceClassDirection
•docsQosServiceClassSchedulingType
|
These objects must be set together as part of the same SET request when configuring a downstream service class.
|
•docsQosParamSetEntry**
|
Identifies a unique set of QoS parameters.
|
docsQosServiceFlowStatsTable
|
Reports the downstream traffic counters for cable modems that are provisioned for DOCSIS 1.1 and DOCSIS 2.0 operation. For DOCSIS 1.0 cable modems, use the cdxCmtsServiceExtTable in CISCO-DOCS-EXT-MIB.
|
•docsQosServiceFlowStatsEntry**
|
Describes a set of service flow statistics. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127)."
|
docsQosPHSTable
|
This table describes set of payload header suppression entries.
|
•docsQosPHSEntry**
|
|
docsQosPktClassTable
|
|
•docsQosPktClassEntry**
|
An entry in this table that provides a single packet classifier rule.
|
docsQosServiceFlowTable
|
|
•docsQosServiceFlowEntry**
|
Describes a service flow. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127).
|
docsQosUpstreamStatsTable
|
|
•docsQosUpstreamStatsEntry**
|
Describes a set of upstream service flow statistics.
|
docsQosServiceFlowLogTable
|
Logs deleted DOCSIS 1.1 and DOCSIS 2.0 service flows, but this table does not contain any information until after logging is specifically enabled using the cable sflog command in global configuration mode.
|
docsQosDynamicServiceStatsTable
|
(not applicable for Docsis 1.0 modems)
|
•docsQosDCCReqs
|
Read-only.The number of Dynamic Channel Change Request messages traversing an interface. This count is nonzero only on downstream direction rows.
|
•docsQosDCCRsps
|
Read-only. The number of Dynamic Channel Change Response messages traversing an interface. This count is nonzero only on upstream direction rows.
|
•docsQosDCCAcks
|
Read-only. The number of Dynamic Channel Change Acknowledgement messages traversing an interface. This count is nonzero only on downstream direction rows.
|
•docsQosDCCs
|
Read-only. The number of successful Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows.
|
•docsQosDCCFails
|
Read-only. The number of failed Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows.
|
|
|
Note Two new objects, docsQosDCCRsp-Departs and docsQosDCCRspArrives, are added to docsQosDynamicServiceStatsTable in this release.
Note For detailed information about load balancing and dynamic channel change on CMTS, go to the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html
DOCS-SEC-MIB
The DOCS-SEC-MIB contains the objects to implement and manage the security based on the DOCSIS security specifications.
DOCS-SUBMGT3-MIB
The DOCS-SUBMGT3-MIB defines objects to manage IPv4 and IPv6 traffic across CMs and Customer Premise Equipment (CPE). This MIB also defines objects to manage diagnostic logs to prevent service interruptions. The information logged in a diagnostic log can be used for early detection of a potential problem.
This MIB defines the following objects to support DOCSIS 3.0 features:
•docsSubmgt3CpeCtrlTable — Defines attributes to store traffic policies, which the CMTS enforces for each CM. The CMTS acquires the CM traffic policies through the CM registration process. If the required parameters are not available, CM traffic policies are obtained from thebase object.
•docsSubmgt3CpeIpTable — Defines the list of IP Addresses for each CM.
•docsSubmgt3GrpTable — Defines the set of downstream and upstream filter groups that the CMTS applies to traffic associated with the corresponding CM.
•docsSubmgt3FilterGrpTable — Describes a set of filters or classifiers implemented on a CM. Classifiers are assigned by group to the individual CMs.
MIB Constraints
There are no constraints for this MIB.
DOCS-SUBMGT-MIB
The DOCS-SUBMGT-MIB contains objects to configure and monitor the subscriber management features in DOCSIS 1.1 and DOCSIS 2.0 cable networks. These objects include packet filtering and CPE device control, and help protect the cable network from intentional or accidental misuse by subscribers.
This MIB was published as an Internet Draft, Management Information Base for Data Over Cable Service Interface Specification (DOCSIS) Cable Modem Termination Systems for Subscriber Management.
The MODULE-IDENTITY for the DOCS-SUBMGT-MIB is docsSubMgt, and its top-level OID is 1.3.6.1.3.83.4 (iso.org.dod.internet.experimental.83.docsSubMgt). Because this is an experimental MIB, its top-level OID is expected to change when the specifications are finalized.
MIB Constraints
This MIB has the following constraints:
•The Cisco uBR10012 router does not support the packet filtering objects in this MIB.
•Supported only in Cisco IOS Release 12.2BC and later releases that support DOCSIS 1.1 and DOCSIS 2.0 operations.
•The Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cable interface line cards support this MIB and its objects only in Cisco IOS Release 12.2(15)BC1 and later releases.
Table 3-40 lists the constraints that the router places on DOCS-SUBMGT-MIB.
.
Table 3-40 DOCS-SUBMGT-MIB Constraints
MIB Object
|
Notes
|
docsSubMgtCpeIpTable
|
CPE devices listed for a particular cable modem are not automatically cleared when the cable modem is reset. If a problem occurs, then set the docsSubMgtCpeControlReset object to True for that particular cable modem to erase all of its CPE entries.
|
DOCS-TEST-MIB
The DOCS-TEST-MIB contains objects to support programmable test features for DOCSIS 2.0 compliant Cable Modem Termination Systems (CMTS).
MIB Constraints
Table 3-41 lists the constraints that the router places on DOCS-TEST-MIB.
.
Table 3-41 DOCS-TEST-MIB Constraints
MIB Object
|
Notes
|
docsTestBaseObjects
|
|
•docsTestCapability
|
Read-only.
|
•docsTestStatus
|
Read-only.
|
DOCS-L2VPN-MIB
The DOCSIS-L2VPN-MIB contains the SNMP management objects that the Cisco CMTS router uses for L2VPN support. This MIB is bundled with the Cisco IOS software images that support the L2VPN Support over Cable feature.
DOCSIS-L2VPN-MIB Tables and Objects
Table 3-42 lists the tables in the DOCSIS-L2VPN-MIB that the Cisco CMTS routers support..
.
Table 3-42 DOCSIS-L2VPN-MIB Tables and Objects
MIB Object
|
Description
|
docsL2vpnIdToIndexTable
|
Indexed by the octet string DocsL2vpnIdentifier that provides the local agent's internally assigned docsL2vpnIdx value for that DocsL2vpnIdentifier value.
|
docsL2vpnIndexToIdTable
|
Indexed by agent's local docsL2vpnIdx that provides the global L2VPN Identifier.
|
docsL2vpnCmTable
|
Describes L2VPN per-CM information that is common for all L2VPNs for the CM, independent of forwarding mode.
|
docsL2vpnVpnCmTable
|
Describes the operation of L2VPN forwarding on each CM.
|
docsL2vpnVpnCmStatsTable
|
Contains statistics for forwarding of packets to and from a CM on each VPN.
|
docsL2vpnPortStatusTable
|
Displays summary information for the run-time state of each VPN that is currently operating on each bridge port.
|
docsL2vpnSfStatusTable
|
Displays SF-specific L2VPN forwarding status for each upstream service flow configured with a per-SF L2VPN Encoding.
|
docsL2vpnPktClassTable
|
Provides the L2VPN-specific objects for packet classifiers that apply to only L2VPN traffic. The indices of this table are a subset of the indices of classifiers in docsQosPktClassTable.
|
docsL2vpnCmNsiTable
|
Describes the NSI configuration for a single CM when operating in point-to-point forwarding mode for an L2VPN.
|
DTI-MIB
The DTI-MIB defines objects to manage and support the RF Gateway. The following tables are defined in the DTI-MIB:
•dtiProtocolEntityType—Refer to Table 3-43.
•dtiPathTraceabilityTable—Refer to Table 3-44.
•entPhysicalTable—Refer to these tables:
–Table 3-49—entPhysicalTable Entries for the Cisco DTI Card
–Table 3-49—entPhysicalTable Entries for Cisco DTI Ports
–Table 3-50—entAliasMappingTable Entries for DTI Interfaces
Table 3-43 dtiProtocolEntityType Entries
MIB Attribute
|
Value
|
Notes
|
dtiProtocolEntityType
|
root(1), server(2), client(3)
|
|
dtiProtocolClientClockType
|
ituI(1), ituII(2), ituIII(3), st3(4), dtiClock(5)
|
|
dtiProtocolServerStatusFlag
|
unknown(0), warmup(1), freerun(2), fastTrackingMode(3), normalMode(4), holdoverMode(5), clientStable(6), testMode(7)
|
Server status
|
dtiProtocolClientStatusFlag
|
unknown(0), warmup(1), freerun(2), fastTrackingMode(3), normalMode(4), holdoverMode(5), bridgingMode(6), testMode(7)
|
Client status
|
dtiProtocolServerToDState
|
Valid(1) or Invalid(2)
|
Validity of TOD
|
dtiProtocolServerToDType
|
Default(1), userTime(2), ntpv4(3), gps(4)
|
Current TOD source for DTI connection
|
dtiProtocolServerToDValue
|
String
|
Value of TOD in format DDDDD.YYYY/MM/DD.HH:MM:SS.SHH:F.D
|
dtiProtocolServerCableAdvanceFlag
|
Valid(1), invalid(2), manual(3)
|
Cable advance status
|
dtiProtocolServerCableAdvanceValue
|
String
|
Cable advance value
|
dtiProtocolClientPhaseError
|
Signed number
|
Phase error counter
|
dtiProtocolClientVersion
|
Unsigned number
|
Client DTI version
|
dtiProtocolClientPathTraceability
|
Unsigned number
|
DTI traceability
|
dtiProtocolServerClientStableFlag
|
Valid(1) or Invalid(2)
|
Client performance stable status of DTI server frame
|
Table 3-44 dtiPathTraceabilityTable Entries
MIB Attribute
|
Value
|
Notes
|
dtiPathTraceabilityIndex
|
Unsigned number
|
index
|
dtiPathTraceabilityRootServerInetAddrType
|
unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16)
|
Server address type
|
dtiPathTraceabilityRootServerInetAddr
|
<IP address>
|
Server address
|
dtiPathTraceabilityRootServerOutPhyIdx
|
Physical index
|
|
dtiPathTraceabilityServerInetAddrType
|
unknown(0), ipv4(1), ipv6(2), ipv4z(3), ipv6z(4), dns(16)
|
|
dtiPathTraceabilityServerInetAddr
|
<IP address>
|
|
dtiPathTraceabilityServerOutPhyIdx
|
Physical index
|
|
dtiPathTraceabilityRootServerProtVersion
|
|
DTI version
|
dtiPathTraceabilityServerProtVersion
|
|
DTI protocol version
|
MIB Constraints
This MIB is supported in Cisco IOS Release 12.3(23)BC and later releases.
ENTITY-MIB
The ENTITY-MIB represents physical and logical entities (components) in the router and allow SNMP management of those multiple logical entities. This MIB was released as RFC 2737, Entity MIB (Version 2).
The MIB table entPhysicalTable identifies the physical entities in the router. The entPhysicalTable contains a single row for the chassis and a row for each entity in the chassis. A physical entity may contain other entities (for example, a fan-tray bay may contain a fan-tray module, which may contain one or more fans). The physical hierarchy of system components is determined at run time, based on the actual router configuration.
The ENTITY-MIB shows information only about hardware devices, not virtual devices.
The ENTITY-MIB object, entPhysicalName, returns slot 0A and slot 0B for the slots, PRE A and PRE B, as shown in the Figure 3-1:
Figure 3-1 Front view of Cisco uBR10012 Router Chassis
The MIB object, entPhysicalName, returns the value in the format slot x/y for the slots 1 to 8 as shown in the Figure 3-2, where x represents the slot number and y represents the subslot number.
Figure 3-2 Rear view of Cisco uBR10012 Router Chassis
The MODULE-IDENTITY for the ENTITY-MIB is entityMIB, and its top-level OID is 1.3.6.1.2.1.47 (iso.org.dod.internet.mgmt.mib-2.entityMIB).
MIB objects and related constraints introduced in Cisco IOS Release 12.2(33)SCC are included in Table 3-52.
The MIB attributes for the various physical entities of 3Gx60 card in Cisco IOS Release 12.2(33)SCE are inlcuded in:
•Table 3-45—entPhysicalTable Entries for the 3Gx60 Line Card
•Table 3-46—entPhysicalTable Entries for 3Gx60 Ports
•Table 3-47—entPhysicalTable Entries for 3Gx60 Controller
•Table 3-48—entPhysicalTable Entries for 3Gx60 SFP
Table 3-45 entPhysicalTable Entries for the 3Gx60 Line Card for Cisco IOS Release 12.2(33)SCE
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Physical index
|
Cisco IOS Release 12.2(33)SCE.
Set by Entity MIB when instance is created.
|
entPhysicalDescr
|
UBR-MC3GX60V
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalVendorType
|
cevUbrMc3g60
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalContainedIn
|
Corresponding chassis index
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalClass
|
"module (9)"
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalParentRelPos
|
A number denotes the location of the 3Gx60 card.
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalName
|
Module slot/subslot
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalHardwareRev
|
Hardware revision
|
Cisco IOS Release 12.2(33)SCE.
Read from EEPROM.
|
entPhysicalFirmwareRev
|
Firmware revision
|
Cisco IOS Release 12.2(33)SCE.
Read from EEPROM.
|
entPhysicalSoftwareRev
|
Software revision
|
Cisco IOS Release 12.2(33)SCE.
Read from EEPROM.
|
entPhysicalSerialNum
|
Card serial number
|
Cisco IOS Release 12.2(33)SCE.
Read from EEPROM.
|
entPhysicalMfgName
|
Cisco
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalModelName
|
UBR-MC3Gx60V
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalAlias
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalAssetID
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalIsFRU
|
TRUE(1)
|
Cisco IOS Release 12.2(33)SCE.
|
Table 3-46 entPhysicalTable Entries for 3Gx60 Port for Cisco IOS Release 12.2(33)SCE
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Physical index
|
Cisco IOS Release 12.2(33)SCE.
Set by Entity MIB when instance is created.
|
entPhysicalDescr
|
"UBR10000 CLC" for MAC-domain and "LBT4522E PHY" for upstream
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalVendorType
|
cevPortRfMac for MAC-domain and cevPortRfUs for upstream.
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalContainedIn
|
3Gx60 Card Physical index
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalClass
|
"port (10)"
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalParentRelPos
|
0-14 for MAC domain and 0-59 for upstream.
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalName
|
Cable slot/subslot-MAC<mcdomain> for MAC domain and Cable slot/subslot-US<us num> for upstream.
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalHardwareRev
|
N/A
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalFirmwareRev
|
N/A
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSoftwareRev
|
N/A
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSerialNum
|
N/A
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalMfgName
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalModelName
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalAlias
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalAssetID
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalIsFRU
|
FALSE (2)
|
Cisco IOS Release 12.2(33)SCE.
|
Table 3-47 entPhysicalTable Entries for 3Gx60 Controller for Cisco IOS Release 12.2(33)SCE
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Physical Index
|
Cisco IOS Release 12.2(33)SCE.
Set by Entity MIB when instance is created.
|
entPhysicalDescr
|
Wideband CMTS Controller
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalVendorType
|
cevSpa24xwbdSfp
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalContainedIn
|
3Gx60 Card Physical Index
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalClass
|
"container(5)"
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalParentRelPos
|
0~2
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalName
|
Wideband CMTS Base slot/subslot/<controller number>
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalHardwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalFirmwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSoftwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSerialNum
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalMfgName
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhyCisco CMTS Universal Broadband Series Router MIB Specifications Guide, Release 12.2SCsicalModelName
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalAlias
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalAssetID
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalIsFRU
|
FALSE (2)
|
Cisco IOS Release 12.2(33)SCE.
|
Table 3-48 entPhysicalTable Entries for 3Gx60 SFP for Cisco IOS Release 12.2(33)SCE
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Set by Entity MIB when instance is created
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalDescr
|
SFP slot/subslot/unit/sfp-index
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalVendorType
|
cevSFP1000BaseSx
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalContainedIn
|
Physical index of one of the controllers.
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalClass
|
"module(9)"
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalParentRelPos
|
0,1
|
Cisco IOS Release 12.2(33)SCE.
This value should match any external labeling of the physical component, if possible. For example, for a container (such as a card slot) labeled as "slot #3", the entPhysicalParentRelPos should have the value "3". Note that the entPhysicalEntry for the module plugged in slot 3 should have an entPhysicalParentRelPos value of "1".
|
entPhysicalName
|
SFP slot/subslot/unit/sfp-index
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalHardwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalFirmwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSoftwareRev
|
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalSerialNum
|
Serial number of this SFP
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalMfgName
|
CISCO-AVAGO
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalModelName
|
SFBR-5766PZ
|
Cisco IOS Release 12.2(33)SCE.
|
entPhysicalAlias
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalAssetID
|
|
Cisco IOS Release 12.2(33)SCE.
Null by default, can be set.
|
entPhysicalIsFRU
|
TRUE(1)
|
Cisco IOS Release 12.2(33)SCE.
|
Table 3-49 entPhysicalTable Entries for the DTI Line Card in Cisco IOS Release 12.2(33)SCC
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Physical index
|
Cisco IOS Release 12.2(33)SCC. Set by Entity MIB when instance is created
|
entPhysicalDescr
|
UBR10-DTCC for Fireballs, UBR10-DTCC for EightBells.
|
Cisco IOS Release 12.2(33)SCC. Eightbell is the current value.
|
entPhysicalVendorType
|
cevUbrTccPlus for Fireballs, cevUbrDtcc for Eightbells
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalContainedIn
|
Corresponding chassis index
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalClass
|
module
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalParentRelPos
|
A number denotes the location of the TCC with DTI card.
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalName
|
uBR10k DTI port slot/subslot.
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalHardwareRev
|
Hardware revision
|
Cisco IOS Release 12.2(33)SCC. Read from EEPROM
|
entPhysicalFirmwareRev
|
Firmware revision
|
Cisco IOS Release 12.2(33)SCC. Read from EEPROM
|
entPhysicalSoftwareRev
|
Software revision
|
Cisco IOS Release 12.2(33)SCC. Read from EEPROM
|
entPhysicalSerialNum
|
N/A
|
Cisco IOS Release 12.2(33)SCC. Read from EEPROM
|
entPhysicalMfgName
|
Cisco
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalModelName
|
UBR10-TCC+-T1 for FireBalls, UBR10-DTCC for Eightbells.
|
Cisco IOS Release 12.2(33)SCC.
|
entPhysicalAlias
|
|
Cisco IOS Release 12.2(33)SCC. Null by default, can be set.
|
entPhysicalAssetID
|
|
Cisco IOS Release 12.2(33)SCC. Null by default, can be set.
|
entPhysicalIsFRU
|
TRUE(1)
|
Cisco IOS Release 12.2(33)SCC.
|
Table 3-50 entPhysicalTable Entries for the DTI Ports in Cisco IOS Release 12.2(33)SCC
MIB Attribute
|
Value
|
Notes
|
entPhysicalIndex
|
Physical index
|
Set when the port is enabled.
|
entPhysicalDescr
|
uBR1000 DTI 10BaseT like port
|
|
entPhysicalVendorType
|
cevPortBaseTEther
|
Applying, updates later.
|
entPhysicalContainedIn
|
DTI card physical index
|
e.g. Ge containedin SFP module
|
entPhysicalClass
|
Port(10)
|
|
entPhysicalParentRelPos
|
0
|
A number given when DTI is enabled, increasing from 0.
|
entPhysicalName
|
uBR10k DTI port <slot>/<subslot>/<unit>
|
|
entPhysicalHardwareRev
|
N/A
|
|
entPhysicalFirmwareRev
|
N/A
|
|
entPhysicalSerialNum
|
N/A
|
|
entPhysicalMfgname
|
Cisco
|
|
entPhysicalModelname
|
N/A
|
|
entPhysicalAlias
|
NA
|
|
entPhysicalAssetID
|
NA
|
|
entPhysicalIsFRU
|
False(2)
|
|
Table 3-51 entAliasMappingTable Entries for DTI interfaces
MIB Attribute
|
Value
|
Notes
|
entAliasLogicalIndexOrZero
|
0
|
Logical index.
|
entAliasMappingIdentifier
|
ifIndex.<ifIndex#>
|
ifindex# is corresponding DTI interface's index.
|
MIB Constraints
.
Table 3-52 ENTITY-MIB Constraints Prior to Cisco IOS Release 12.2(33)SCC
MIB Object
|
Notes
|
entPhysicalTable
|
This table does not include the NPE on the Cisco uBR7200 series routers until Cisco IOS Release 12.2(8)BC1 and later releases.
|
•entPhysicalFirmwareRev
|
Not implemented.
|
•entPhysicalAlias
|
Not implemented.
|
•entPhysicalAssetID
|
Not implemented.
|
•entPhysicalSoftwareRev
|
Supported only in Cisco IOS Release 12.2(8)BC2 and later releases.
|
•entPhysicalHardwareRev
•entPhysicalModelName
•entPhysicalSerialNumber
|
Supported only for some cards. In addition, entPhysicalSerialNumber displays the correct serial number only in Cisco IOS Release 12.1(20)EC, 12.2(15)BC2, and later releases.
|
•entPhysicalHardwareRev
|
•Supports the Cisco Unique Device Identifier (UDI).
•Contains the Version Identifier (VID).
|
•entPhysicalModelName
|
•Supports the Cisco Unique Device Identifier (UDI).
•Contains the orderable Product Identifier (PID).
|
•entPhysicalSerialNumber
|
•Supports the Cisco unique device Identifier (UDI).
•Contains the hardware Serial Number (SN).
Note that for non-UDI compliant hardware, these fields might contain a NULL string. Currently, the UDI support is not implemented for the standby PRE. For standby PRE, both entPhysicalHardwareRev and entPhysicalSerialNumber contains NULL string.
|
•entPhysicalIsFRU
|
•Supported on the Cisco uBR7100 series and Cisco uBR7200 series routers in all releases.
•Supported on the Cisco uBR10012 router only in Cisco IOS Release 12.2(11)BC2 and later releases.
|
•entPhysicalDescr
|
This object describes the Cisco uBR10012 router either as UBR10000 or UBR10012, depending on Cisco IOS release.
|
•entPhysicalContainedIn
|
This object accurately displays the location of the FastEthernet network management port on the active PRE-1 module only in Cisco IOS Release 12.2(4)BC1b and later releases.
|
entLPMappingTable
|
Not implemented.
|
entAliasMappingTable
|
•On Cisco uBR10012 routers, this table does not contain entries for the TCC+ cards.
•On Cisco uBR10012 routers with two redundant PRE modules installed, the entPhysicalDesc entries in the entAliasMappingTable contain two sets of apparently identical references for each PRE module to "Forwarding Processor," "Routing Processor," and "Network Management Ethernet" (the Fast Ethernet port on the PRE modules). This occurs because two PRE modules are installed in the chassis, but only one is active. So the SNMP agent points both entries to the same PRE module.
•The entAliasMappingTable supports virtual interfaces only in Cisco IOS Release 12.2(15)BC2 and later releases. The entries in this table show the logical upstream interface (as defined by ifIndex from the IF-MIB) that is using each physical upstream connector. This support also slightly changed the parent-child relationships of the ports on cable interface line cards, as described in the next section, "Changes to Support Virtual Interfaces".
|
|
|
Cisco uBR100012 SPA-24XWBD-SFP Shared Port Adapter
Table 3-53 lists physical entities and values for the Cisco uBR100012 CMTS SPA-24XWBD-SFP.
Table 3-53 entPhysicalTable Objects for Cisco Ubr100012 SPA-24XWBD-SFP
entPhysicalDescr
|
entPhysicalClass
|
entPhysicalVendorType
|
entPhysicalName
|
entPhysical/
IsFRU
|
SPA Bay Container
|
container
|
cevContainerSPABay
|
" "(null)
|
|
uBR10KSPA Card
|
Module(9)
|
cevSpa24xWbdSfp
|
SPA-WB Wideband CMTS SPA 3/00
|
True(1)
(represents a field-replaceable unit)
|
Pluggable Optics Container
|
container
|
cevContainerSFP
|
" "(null)
|
|
Short wavelength gigabit Ethernet SFP
|
Port(10)
|
cevSFP1000BaseSx
|
SFP slot/sub-slot/unit/port
Where port can be 0 or 1. For example, SFP 3/0/0/1
|
True(1)
|
Long wavelength gigabit Ethernet SFP
|
Port(10)
|
cevSFP1000BaseLx
|
SFP slot/sub-slot/unit/port
Where port can be 0 or 1. For example, SFP 3/0/0/1
|
True(1)
|
Copper gigabit Ethernet SFP
|
Port(10)
|
cevSFP1000BaseT
|
SFP slot/sub-slot/unit/port
Where port can be 0 or 1. For example, SFP 3/0/0/1
|
True(1)
|
Extended reach gigabit Ethernet SFP
1000BaseZx
|
Port(10)
|
cevSFP1000BaseZx
|
SFP slot/sub-slot/unit/port
Where port can be 0 or 1. For example, SFP 3/0/0/1
|
True(1)
|
ENTITY-MIB UDI Support
The ENTITY-MIB supports the Cisco compliance effort for a Cisco unique device identifier (UDI) standard which is stored in IDPROM.
The Cisco UDI provides a unique identity for every Cisco product. The unique device identifier is comprised of an orderable product identifier (PID), the VID, and the hardware serial number (SN).
The UDI is stored in IDPROM. The PID, VID, and SN must be stored in the entPhysicalTable:
•PID shall be stored in the entPhysicalModelName object
•VID shall be stored in the entPhysicalHardwareRev object
•SN shall be stored in the entPhysicalSerialNum object
Note The VID returns NULL for those old or existing cards where IDPROMs do not have the VID field. Therefore, corresponding entPhysicalHardwareRev returns NULL for cards that do not have the VID field in IDPROM. See Identifying Cisco Unique Device Identifiers, page A-40 for a complete description of the Cisco UDI feature.
Each product that is capable of MIB support is required to populate ENTITY-MIB v2 or later with PID, VID, and SN. This compliance is also a requirement of the Consistent Network Element Manageability initiative. If the product uses both ENTITY-MIB and CISCO-ENTITY-ASSET-MIB, then the data in the following fields should be identical.
ENTITY-MIB v2 (RFC-2737) fields to be populated are:
•Entity-MIB.entPhysicalName (Product Name)
•Entity-MIB.entPhysicalDescr (Product Description)
•Entity-MIB.entPhysicalModelName (PID)
•Entity-MIB.entPhysicalHardwareRev (VID)
•Entity-MIB.entPhysicalSerialNumber (SN)
Overview of the ENTITY-MIB
The following are the most important objects in the ENTITY-MIB for the management of physical entities on the router:
•entPhysicalTable—Describes each physical component (entity) in the router. The table contains a row entry for the top-most entity (the chassis) and then for each entity in the chassis. Each entry provides the name and description of the entry, its type and vendor, and a description of the reason how the entity was first entered into the containment tree.
•entPhysicalIndex—Uniquely identifies each entry. This value is guaranteed to be unique across all equipment in this chassis and across all MIBs, allowing you to correlate the data from several MIBs for any particular entity.
•entAliasMappingTable—Maps each physical port's entPhysicalIndex value to the corresponding ifIndex value in the ifTable in the IF-MIB. This provides a quick way of identifying a particular port with a particular interface.
In Cisco IOS Release 12.2(15)BC2 and later releases, the entAliasMappingTable also shows the mapping of physical upstream connectors to logical upstream interface when virtual interfaces are configured on the Cisco uBR-MC5X20S and Cisco uBR-MC5X20U cable interface line cards. This support also changed the parent-child relationships of cable interface line cards and their ports. For more information, see the "Changes to Support Virtual Interfaces" section.
•entPhysicalContainsTable—For each physical entity, lists the entPhysicalIndex value for any child objects of the entity. This provides an easy way of creating the container tree for the router, which shows the relationship between physical entities in the chassis.
Typically, the container tree is organized as follows:
–The chassis is the top-most level and contains the processor card and chassis slots.
–Chassis slots contain the individual line cards and I/O controller (if installed).
–Line cards contain ports (interfaces).
–Cable interface line cards contain downstream ports (known as cable line card). In Cisco IOS Release 12.2(15)BC1 and earlier releases, each downstream port then contains the upstream ports that are associated with it. In Cisco IOS Release 12.2(15)BC2 and later releases, the downstream ports and upstream are all children of the cable interface line card.
Figure 3-3 shows an overview of the arrangement of objects in a Cisco uBR7246VXR router, with one Fast Ethernet line card and two cable interface line cards. (This graphic shows the cable interface line cards as they are represented in Cisco IOS Release 12.2(15)BC1 and earlier releases.)
Figure 3-3 ENTITY-MIB for Cisco uBR7246VXR Chassis
Changes to Support Virtual Interfaces
To enable SNMP support for Virtual Interfaces, Cisco IOS Release 12.2(15)BC2 changed how the entPhysicalTable in the ENTITY-MIB displays the information for cable interface line cards. Previously, the cable interface line card was the parent to one or more MAC domains, and each MAC domain then was the parent to one downstream and one or more upstreams.
Because an upstream can now be associated with any MAC domain and downstream in Cisco IOS Release 12.2(15)BC2, the ENTITY-MIB no longer associates upstreams and downstreams with specific MAC domains, but instead shows all of them as being children of the line card. The entityPhysicalParentRelPos also now numbers the upstreams in sequential order, followed by the downstreams, so that on the Cisco uBR-MC5X20S cards, the upstreams are numbered from 0 to 19, and the downstreams from 20 to 24.
Figure 3-4 shows the difference in how the entPhysicalTable in the ENTITY-MIB organized a Cisco uBR-MC5X20S cable interface line card in previous releases and in Cisco IOS Release 12.2(15)BC2. For consistency, all cable interface line cards use this approach, even if they do not support the Virtual Interfaces feature.
Figure 3-4 ENTITY-MIB Changes for Virtual Interface Support on Cable Interface Line Cards
The mapping between the physical upstream connectors and the logical upstream interfaces is shown in the entityAliasMappingTable. Each entry in this table contains the ifDescr index (as defined in the ifTable in the IF-MIB) that maps to the physical connector that is being used for that interface. The entityAliasMappingTable is automatically updated to show the mapping between the physical upstream connectors and the logical interfaces whenever the cable upstream connector command used.
Chassis Slot Layout
Table 3-54 provides information about the entities contained in chassis slots on the Cisco uBR10012 router.
Table 3-54 Cisco uBR10012 Router Chassis Slot Contents
Entity
|
Can Contain
|
Notes
|
Slots 1 to 8
|
One full-size line card per slot.
|
For chassis slot containers:
•entPhysicalContainedIn is always 1 (which is the entPhysicalIndex of the chassis, which contains all chassis slots).
•entPhysicalParentRelPos is different for each chassis slot, to show its position in the chassis.
The Cisco uBR10012 router supports only full-size line cards in chassis slots:
•entPhysicalContainedIn is different for each line card (because each line card is installed in a different chassis slot).
•entPhysicalParentRelPos is always 1 (only one card per slot).
|
Slots A and B
|
One route processor (RP) per slot.
|
Router can have two RPs (one for each PRE installed in slot A and slot B). Each RP contains:
FP
NME
Core temperature sensor
Inlet temperature sensor
Flash card slots (2), which are not modeled in the ENTITY MIB.
|
One forwarding processor (FP) per slot.
|
Router can have two FPs (one for each PRE installed in slot A and slot B).
|
ENTITY-SENSOR-MIB
The ENTITY-SENSOR-MIB defines Entity MIB extensions for physical sensors.
MIB Constraints
There are no constraints on this MIB.
ETHERLIKE-MIB
The ETHERLIKE-MIB contains objects to manage Ethernet-like interfaces on the router. This MIB was released as RFC 2665, Definitions of Managed Objects for the Ethernet-like Interface Types.
The MODULE-IDENTITY for the ETHERLIKE-MIB is etherMIB, and its top-level OID is 1.3.6.1.2.1.35 (iso.org.dod.internet.mgmt.mib-2.etherMIB).
MIB Constraints
Table 3-55 lists the constraints that the router places on ETHERLIKE-MIB.
.
Table 3-55 ETHERLIKE-MIB Constraints
MIB Object
|
Notes
|
dot3StatsTable
|
|
•dot3StatsCarrierSenseErrors
|
Implemented starting in Cisco IOS Release 12.2(15)BC2 and later releases. It returns NULL in earlier releases.
|
•dot3StatsSQETestErrors
|
Not implemented and is always 0.
|
•dot3StatsInternalMacTransmitErrors
|
Not implemented and is always 0.
|
•dot3StatsEtherChipSet
|
Deprecated and is always NULL
|
•dot3StatsFrameTooLongs
|
For Fast Ethernet interfaces and for Gigabit Ethernet interfaces, this object counts only frames of 1545 bytes or larger (not counting the cyclic redundancy check [CRC]), regardless of the maximum transmission unit (MTU) value.
|
dot3CollTable
|
Not implemented.
|
EVENT-MIB
The EVENT-MIB contains objects to define event triggers and actions for network management purposes.
The MODULE-IDENTITY for the EVENT-MIB is dismanEventMIB, and its top-level OID is 1.3.6.1.2.1.88 (iso.org.dod.internet.mgmt.mib-2.dismanEventMIB).
MIB Constraints
This MIB is:
•Not supported in any Cisco IOS Release 12.1EC software image.
•Supported in all Cisco IOS Release 12.2BC and later software images for the Cisco uBR10012 router.
•Supported only in Cisco IOS Release 12.2BC "-is-" software images in Cisco uBR7100 series and Cisco uBR7200 series routers.
EXPRESSION-MIB
The EXPRESSION-MIB contains objects to define expressions of MIB objects for network management purposes.
The MODULE-IDENTITY for the EXPRESSION-MIB is expressionMIB, and its top-level OID is 1.3.6.1.4.1.9.10.22 (iso.org.dod.internet.private.enterprises.cisco.ciscoExperiment.expressionMIB).
MIB Constraints
There are no constraints on this MIB.
HC-RMON-MIB
The HC-RMON-MIB contains objects that provide high capacity (HC) information that supplements the remote monitoring objects in the RMON-MIB and the RMON2-MIB.
The MODULE-IDENTITY for the HC-RMON-MIB is hcRMON, and its top-level OID is 1.3.6.1.2.1.16.20.8 (iso.org.dod.internet.mgmt-mib-2.rmon.rmonConformance.hcRMON).
MIB Constraints
These are no constraints on this MIB.
IF-MIB
The IF-MIB describes the attributes of physical and logical interfaces. The router supports the ifGeneralGroup of MIB objects for all layers (ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifAdminStatus, ifOperStatus, ifLastChange, ifName, ifLinkUpDownTrapEnable, ifHighSpeed, and ifConnectorPresent). This MIB was released as RFC 2233, The Interfaces Group MIB Using SMIv2.
In Cisco IOS Release 12.2(33)SCE, ifTable has 15 MAC-domain interfaces and 60 upstream interfaces for an MC3Gx60 card.
In Cisco IOS Release 12.2(15)BC1c and later releases, the Cisco CMTS routers implemented a cache to allow continuous polling of the ifTable interface counters, without creating spikes in the CPU usage. The cache is updated approximately every 10 seconds, which means that if you read the counter more quickly than that, the SNMP request might not return a new value.
The counters do continue to increment, however, to account for the actual traffic occurring on the interfaces, and another SNMP request in 10 seconds shows the new values. However, the use of the cache means that the counters displayed by the show interface command might not exactly match the values returned by the ifTable interface counters.
Also, you can retrieve interface packet counters for both a cable interface and for the corresponding downstream. When using an ifIndex that points to a downstream (the ifDescr shows "cX/Y/Z-downstream"), the packet counters include not only the data packets but also the DOCSIS MAC-layer packets that are transmitted on that downstream. To retrieve counters for only the data packets (which corresponds to the output from the show interface command), use the ifIndex for the interface itself (the ifDescr shows "cX/Y/Z").
Note A fixed algorithm is used to pre-allocate a value to ifIndex for each channel. The value of ifIndex is not preserved after an upgrade.
The MODULE-IDENTITY for the IF-MIB is ifMIB and its top-level OID is 1.3.6.1.2.1.31 (iso.org.dod.internet.mgmt.mib-2.ifMIB).
The following tables are added to this MIB to manage logical channels:
•ifTable
•ifXTable
•ifStackTable
IF-MIB Notes
Table 3-56 lists the constraints that the router places on IF-MIB.
.
Table 3-56 IF-MIB Notes
MIB Object
|
Notes
|
ifXEntryTable
|
|
•ifAlias
|
Supported for non-cable interfaces on the Cisco uBR10012 router in Cisco IOS Release 12.2(11)BC2 and later releases.
Supported for cable interfaces only in Cisco IOS Release 12.2(15)BC2 and later releases.
|
IfTable
|
|
•ifDescr
|
On the Cisco uBR10012 router, the first ifDescr object is typically "Ethernet0/0/0," which is the internal backplane Ethernet interface that the PRE module uses to communicate with the line cards and the secondary PRE module (if installed). This interface cannot be configured or otherwise used, and therefore should be ignored.
Separate ifDescr entries appear for each cable interface upstream and downstream. These entries have an "upstream" or "downstream" suffix. In addition, an ifDescr entry exists for the cable interface itself (without an "upstream" or "downstream" suffix). This entry represents the MAC-layer interface on the cable interface.
Note that ifDescr supports Virtual Interfaces only in Cisco IOS Release 12.2(15)BC2 and later releases. Also see the ENTITY-MIB for entAliasMappingTable support.
|
•ifType
|
Always reports a value of 6 (Ethernet interface) for Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces. This conforms with the recommendations of RFC 2665, and accommodates 10/100/1000 interfaces that negotiate the link speed with the remote end.
|
•ifInOctets
•ifOutOctets
|
You must use Cisco IOS Release 12.2(11)BC3 or a later release for these objects to reliably count the octets on cable interfaces.
|
•ifSpeed
|
For cable interfaces, this object has valid values only for the upstream and downstream ifDescr entries. The ifSpeed for the MAC-layer cable interface entry is always 0.
|
•ifInUcastPkts
•ifOutMulticast
|
These objects count both data packets and MAC-layer request packets from cable modems on an upstream, so as to conform to RFC 2670.
|
•ifHCInUcastPkts
•ifHCInBroadcastPkts
•ifHCOutUcastPkts
|
Supported only in Cisco IOS Release 12.2(15)BC2 and later releases.
|
•ifInUnknownProtos
|
This object can double-count packets in some circumstances before Cisco IOS Release 12.2(11)BC2.
|
Note The IF-MIB does not contain any information about cable subinterfaces.
Note It is expected that the interface counters displayed by the show interface command might not exactly match the values returned by the ifTable interface counters.
IF-MIB Supported Traps
Cisco IOS Release 12.2(33)SCC enables you to shut down the narrowband downstream ports of a Shared Port Adaptor (SPA) with the shutdown command. The following traps are supported:
•LinkDown
•LinkUp
When an interface is shut down, or enabled with the no shutdown command, traps are sent for each individual channel. The GigE interfaces are not included in this event, and there is no statistical data available per interface for these GigE ports.
Cisco IOS Release 12.2(33)SCC supports new narrowband virtual, and modular-cable interfaces. The RF channels are logical channels that represent external QAMs. The RF channels do not represent an interface, but the narrowband channel represents a logical identity of cable interfaces.
The two GigE ports of the Shared Port Adapter are not supported in the IF-MIB for these reasons. However, the following tables are supported:
•ifTable
•ifXTable
•ifStackTable
Table 3-57 lists the ifTable entries for NB channels.
Table 3-57 ifTable Entries for NB channels
MIB Attribute
|
Value
|
Notes
|
ifIndex
|
index, unsigned integer
|
A unique value for each interface, greater than zero, remains constant between initializations.
|
ifDescr
|
Modular-Cable[slot#]/[subslot#]/[unit#]:[Chan#]
|
|
ifType
|
other
|
Use the option, other, for downstream.
|
ifMtu
|
1500
|
Refer to IF-MIB.
|
ifSpeed
|
NA
|
Set ifSpeed to zero for cable MAC layer.
|
ifPhysAddress
|
MAC Address
|
|
ifAdminStatus
|
Up/Down
|
Represents shut/no-shut of the narrowband downstream narrowband channel. It is always down unless admin status is up, corresponding RF channel is configured and the Modular-Cable interface is configured.
|
ifOperStatus
|
Up/Down
|
Always down unless admin status is up and corresponding RF channel and the Modular-Cable interfaces are configured.
|
ifLastChange
|
Timeticks
|
Refer to IF-MIB.
|
ifInOctets
|
NA - Only out supported
|
In counter not supported
|
ifInUCastPkts
|
NA - Only out supported
|
In counter not supported
|
ifInNUcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifInDiscards
|
NA - Only out supported
|
In counter not supported
|
ifInErrors
|
NA - Only out supported
|
In counter not supported
|
ifInUnknownProtos
|
NA - Only out supported
|
In counter not supported
|
ifOutOctets
|
Counter Value
|
Refer to IF-MIB.
|
ifOutUcastPkts
|
Counter Value
|
Refer to IF-MIB.
|
ifOutNUcastPkts
|
Deprecated
|
Refer to IF-MIB.
|
ifOutDiscards
|
Counter Value - Not Supported
|
Refer to IF-MIB.
|
ifOutErrors
|
Counter Value - NA
|
Refer to IF-MIB.
|
ifOutQLen
|
Deprecated
|
Refer to IF-MIB.
|
ifSpecific
|
Deprecated
|
Refer to IF-MIB.
|
Table 3-58 lists the ifXTable entries for NB channels.
Table 3-58 ifXTable Entries for NB channels
MIB Attribute
|
Value
|
Notes
|
ifName
|
Mo[slot#]/[subslot#]/[unit#]:[Chan#]
|
|
ifInMulticastPkts
|
NA - Only out supported
|
In counter not supported
|
ifInBroadcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifOutMulticastPkts
|
NA
|
Refer to IF-MIB
|
ifOutBroadcastPkts
|
NA
|
Refer to IF-MIB
|
ifHCInOctets
|
NA - Only out supported
|
In counter not supported
|
ifHCInUcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCInMulticastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCInBroadcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCOutOctets
|
Counter Value
|
Refer to IF-MIB
|
ifHCOutUcastPkts
|
Counter Value
|
Refer to IF-MIB
|
ifHCOutMulticastPkts
|
NA
|
Refer to IF-MIB
|
ifHCOutBroadcastPkts
|
NA
|
Refer to IF-MIB
|
ifLinkUpDownTrapEnable
|
enable(1)/disable(2)
|
Default option is enable
|
ifHighSpeed
|
NA - same as ifSpeed
|
RFC2670 requires 0 for Cable MAC layer ifSpeed.
|
ifPromiscuousMode
|
false(2)
|
Always set to false
|
ifConnectorPresent
|
false(2)
|
Always set to false
|
ifAlias
|
Description string
|
|
ifCounterDiscontinuityTime
|
Timeticks
|
Refer to IF-MIB
|
Table 3-59 lists the ifStackTable entries for NB channel.
Table 3-59 ifStackTable Entries for NB channel
MIB Attribute
|
Value
|
Notes
|
ifStackHigherLayer
|
ifIndex or zero
|
ifIndex or zero
|
ifStackLowerLayer
|
zero
|
ifIndex or zero, return always zero
|
ifStackStatus
|
active
|
Read-only, returns always active.
|
Table 3-60 lists the ifTable entries for WB channels.
Table 3-60 ifTable Entries for WB channels
MIB Attribute
|
Value
|
Notes
|
ifIndex
|
index, unsigned integer
|
A unique value for each interface, greater than zero, remains constant between initializations.
|
ifDescr
|
Wideband-Cable[slot#]/[subslot#]/[unit#]:[Chan#]
|
|
ifType
|
other
|
Use other for WB channels
|
ifMtu
|
1500
|
Refer IF-MIB
|
ifSpeed
|
Returns the interface speed according to the bandwidth.
|
|
ifPhysAddress
|
MAC Address
|
|
ifAdminStatus
|
Up/Down
|
It presents shut/no-shut status of the Wideband channel.
|
ifOperStatus
|
Up/Down
|
It is always down unless Admin Status is Up and corresponding RF channel are configured.
|
ifLastChange
|
Timeticks
|
Refer IF-MIB
|
ifInOctets
|
NA - Only out option is supported
|
In counter is option not supported
|
ifInUCastPkts
|
NA - Only out option is supported
|
In counter is option not supported
|
ifInNUcastPkts
|
NA - Only out option is supported
|
In counter is option not supported
|
ifInDiscards
|
NA - Only out option is supported
|
In counter is option not supported
|
ifInErrors
|
NA - Only out option is supported
|
In counter is option not supported
|
ifInUnknownProtos
|
NA - Only out option is supported
|
In counter is option not supported
|
ifOutOctets
|
Counter Value
|
Refer to IF-MIB.
|
ifOutUcastPkts
|
Counter Value
|
Refer to IF-MIB.
|
ifOutNUcastPkts
|
Deprecated
|
Refer to IF-MIB.
|
ifOutDiscards
|
Counter Value - Not Supported
|
Refer to IF-MIB.
|
ifOutErrors
|
Counter Value - NA
|
Refer to IF-MIB.
|
ifOutQLen
|
Deprecated
|
Refer to IF-MIB.
|
ifSpecific
|
Deprecated
|
Refer to IF-MIB.
|
Table 3-61 lists the ifXTable entries for WB channels.
Table 3-61 ifXTable Entries for WB channels
MIB Attribute
|
Value
|
Notes
|
ifName
|
Wi[slot#]/[subslot#]/[unit#]:[Chan#]
|
|
ifInMulticastPkts
|
NA - Only out supported
|
In counter not supported
|
ifInBroadcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifOutMulticastPkts
|
NA
|
Refer to IF-MIB
|
ifOutBroadcastPkts
|
NA
|
Refer to IF-MIB
|
ifHCInOctets
|
NA - Only out supported
|
In counter not supported
|
ifHCInUcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCInMulticastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCInBroadcastPkts
|
NA - Only out supported
|
In counter not supported
|
ifHCOutOctets
|
Counter Value
|
Refer to IF-MIB
|
ifHCOutUcastPkts
|
Counter Value
|
Refer to IF-MIB
|
ifHCOutMulticastPkts
|
NA
|
Refer to IF-MIB
|
ifHCOutBroadcastPkts
|
NA
|
Refer to IF-MIB
|
ifLinkUpDownTrapEnable
|
enable(1)/disable(2)
|
Default option is enable
|
ifHighSpeed
|
Guage value
|
|
ifPromiscuousMode
|
false(2)
|
Always set to false
|
ifConnectorPresent
|
false(2)
|
Always set to false
|
ifAlias
|
Description string
|
|
ifCounterDiscontinuityTime
|
Timeticks
|
Refer to IF-MIB
|
Table 3-62 lists the ifStackTable entries for WB channel.
Table 3-62 ifStackTable Entries for WB channel
MIB Attribute
|
Value
|
Notes
|
ifStackHigherLayer
|
ifIndex or zero
|
If the bundle interface is configured for wideband channel, the higher layer ifIndex is made the bundle interface index, else it is zero.
|
ifStackLowerLayer
|
zero
|
ifIndex or zero, return always zero
|
ifStackStatus
|
active
|
Read-only, returns always active.
|
IGMP-MIB
The IGMP-MIB contains objects to manage the Internet Group Management Protocol (IGMP) on the router. This MIB was published as an experimental Internet Draft that has since been replaced by the IGMP-STD-MIB.
The MODULE-IDENTITY for the IGMP-MIB is igmpMIB, and its top-level OID is 1.3.6.1.3.59 (iso.org.dod.internet.experimental-2.igmpMIB).
MIB Constraints
This MIB is supported only in Cisco IOS Release 12.1EC and only for the Cisco uBR7100 series and Cisco uBR7200 series routers. In other releases, this MIB is deprecated and replaced by the IGMP-STD-MIB (RFC 2933).
IGMP-STD-MIB
The IGMP-STD-MIB contains objects to manage the Internet Group Management Protocol (IGMP) on the router. This MIB was released as RFC 2933, Internet Group Management Protocol MIB, and replaces the IGMP-MIB that was supported in earlier releases.
The MODULE-IDENTITY for the IGMP-STD-MIB is igmpStdMIB, and its top-level OID is 1.3.6.1.2.1.85 (iso.org.dod.internet.mgmt.mib-2.igmpStdMIB).
MIB Constraint
This MIB is supported only in Cisco IOS Release 12.2BC and later releases.
INT-SERV-MIB
The INT-SERV-MIB describes the Integrated Services Protocol (ISP).
The MODULE-IDENTITY for the INT-SERV-MIB is intSrv, and its top-level OID is 1.3.6.1.2.1.52 (iso.org.dod.internet.mgmt.mib-2.intSrv).
MIB Constraints
There are no constraints on this MIB.
IP-MIB
The IP-MIB contains objects to display classless interdomain routing (CIDR) multipath IP routes. This MIB was initially defined as part of RFC1213-MIB and then later released as RFC 4293, SNMPv2 Management Information Base for the Internet Protocol Using SMIv2.
In RFC1213-MIB, the MODULE-IDENTITY for the IP-MIB is ipMIB and its top-level OID is 1.3.6.1.2.1.48 (iso.org.dod.internet.mgmt.mib-2.ipMIB). In RFC 4293, its top-level OID is 1.3.6.1.2.1.48 (iso.org.dod.internet.mgmt.mib-2.ipMIB).
MIB Constraint
The Cisco CMTS routers support the RFC1213-MIB version of this MIB (1.3.6.1.2.1.4).
IPMROUTE-MIB
The IPMROUTE-MIB contains objects to monitor and configure the operation of IP multicast routing on the router. This MIB was published as an experimental Internet Draft that has since expired and has been replaced by the IPMROUTE-STD-MIB.
The MODULE-IDENTITY for the IPMROUTE-MIB is ipMRoute, and its top-level OID is 1.3.6.1.3.60 (iso.org.dod.internet.experimental.ipMRoute).
MIB Constraint
This MIB is supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers.
IPMROUTE-STD-MIB
The IPMROUTE-STD-MIB contains objects to monitor and configure the operation of IP multicast routing on the router. This MIB was released as RFC 2932, IPv4 Multicast Routing MIB, and replaces the IPMROUTE-MIB that was supported in earlier releases.
The MODULE-IDENTITY for the IPMROUTE-STD-MIB is ipMRouteStdMIB, and its top-level OID is 1.3.6.1.2.1.83 (iso.org.dod.internet.mgmt.mib-2.ipMRouteStdMIB).
MIB Constraint
This MIB is not supported on the Cisco uBR10012 router.
ISDN-MIB
The ISDN-MIB contains objects to monitor and configure the ISDN interfaces, both Basic Rate Interface (BRI) and Primary Rate Interface (PRI), on the router. This MIB was released as RFC 2127, ISDN Management Information Base using SMIv2.
The MODULE-IDENTITY for the ISDN-MIB is isdnMIB, and its top-level OID is 1.3.6.1.2.1.10.20 (iso.org.dod.internet.mgmt.mib-2.transmission.isdnMIB).
MIB Constraint
This MIB is not supported on the Cisco uBR10012 router.
LAN-EMULATION-CLIENT-MIB
The LAN-EMULATION-CLIENT-MIB supplements the ATM-MIB and contains objects to manage the ATM-based LAN emulation clients (LECs) on the router.
The MODULE-IDENTITY for the LAN-EMULATION-CLIENT-MIB is atmfLanEmulation, and its top-level OID is 1.3.6.1.4.1.353.5.3 (iso.org.dod.internet.private.enterprises.atmForum.atmForumNetworkManagement.atmfLanEmulation)
MIB Constraints
This MIB is:
•Supported only on Cisco IOS "-is-" software images for Cisco uBR7100 and Cisco uBR7200 series routers.
•Not supported on the Cisco uBR10012 router.
MPLS-LSR-MIB
The MPLS-LSR-MIB defines configuration and remote performance monitoring attributes to manage label switched paths (LSPs) through a label switching router (LSR) that is using the Multiprotocol Label Switching (MPLS) technology. The router supports Version 5 of the IETF MPLS-LSR-MIB.
MIB Constraints
There are no constraints for this MIB.
MPLS-LDP-MIB
The MPLS-LDP-MIB contains objects to store management information for the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), which is used by label switching routers (LSRs) to communicate the definitions of labels that each router is using. The MPLS-LDP-MIB provides objects that perform the following actions:
•Configure LDP sessions on a specific LSR.
•Record information learned through discovery or from the session initialization message.
•Show the actual sessions that are established or are being established.
MIB Constraints
There are no constraints for this MIB.
MPLS-TE-MIB
The MPLS-TE-MIB enables the Cisco CMTS uBR router to perform traffic engineering for MPLS tunnels. The MIB is based on Revision 05 of the IETF MPLS-TE-MIB.
Traffic engineering support for MPLS tunnels requires the following configuration:
•Setting up MPLS tunnels with appropriate configuration parameters.
•Configuring tunnel loose and strict source routed hops.
MIB Constraints
There are no constraints for this MIB.
MPLS-TE-STD-MIB
The MPLS-TE-STD-MIB contains managed object definitions for the MPLS Traffic Engineering (TE).
MIB Constraints
There are no constraints for this MIB.
MSDP-MIB
The MSDP-MIB contains objects to monitor the Multicast Source Discovery Protocol (MSDP). The MIB can be used with SNMPv3 to remotely monitor MSDP speakers. This MIB is currently in development as an IETF draft, Multicast Source Discovery Protocol MIB (the current version is draft-ietf-msdp-mib-07.txt).
For addition information about this MIB, see the document MSDP MIB, at the following URL:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5msdp.html
The MODULE-IDENTITY for the MSDP-MIB is msdpMIB, and its top-level OID is 1.3.6.1.3.92 (iso.org.dod.internet.experimental.msdpMIB).
MIB Constraints
The MSDP-MIB has the following constraints:
•This MIB is not supported in any Cisco IOS Release 12.1EC software images.
•All other MIB objects—Read-only.
Table 3-63 lists the constraints that the router places on MSDP-MIB.
.
Table 3-63 MSDP-MIB Constraints
MIB Object
|
Notes
|
msdpRequestsTable
|
Not supported.
|
•msdpEstablished
|
Not supported.
|
NOTIFICATION-LOG-MIB
The NOTIFICATION-LOG-MIB contains objects that put the SNMP notifications that are sent by the router into a log table for later retrieval or browsing. This MIB was released as RFC 3014, Notification Log MIB.
The MODULE-IDENTITY for the NOTIFICATION-LOG-MIB is notificationLogMIB, and its top-level OID is 1.3.6.1.2.1.92 (iso.org.dod.internet.mgmt.mib-2.notificationLogMIB).
MIB Constraints
This MIB is not supported:
•In any Cisco IOS "-is-" software images for Cisco uBR7100 series and Cisco uBR7200 series routers.
•On Cisco uBR10012 routers.
nruCacheSnmpData
Cisco RF Switch Firmware Version 3.80 adds a new MIB object identifier (OID) to control caching on the Cisco CMTS, and the desired state may be set in the AdminState caching flag. To control caching in this manner, use the SNMP object nruCacheSnmpData, which is a read/write integer at OID 1.3.6.1.4.1.6804.2.1.1.9.
The object information for nruCacheSnmpData is as follows:
•Syntax is an integer of 0 or 1.
•Access is read or write.
•The status is mandatory.
Setting the nruCacheSnmpData object with SNMP alters the run-time setting of the cache flag, but does not effect the state of the non-volatile memory (NVRAM) setting. This allows you to override the setting of the cache flag dynamically to verify the state of the settings, if desired.
The state of the NVRAM setting has been added to the show config firmware command. The current run-time state has been added to the show module firmware command.
SNMP MIB get and set variables can be saved to cache in the AdminState MIB. The SNMP cache can be disabled or reenabled using the system-level set snmp cache firmware command. The setting for this command is stored in non-volatile memory on the Cisco RF Switch.
Refer to the following Cisco document for additional information on commands:
•Release Notes for Cisco RF Switch Firmware, Version 3.92
http://www.cisco.com/en/US/docs/cable/rfswitch/ubr3x10/release/notes/rfswrn36.html
MIB Constraints
This object and related functions are supported strictly in Cisco RF Switch Firmware Version 3.80 or later, to be used in conjunction with Cisco IOS Release 12.3BC on the Cisco CMTS.
OLD-CISCO-CHASSIS-MIB
The OLD-CISCO-CHASSIS-MIB describes chassis objects in devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-CHASSIS-MIB is being phased out and could become unsupported without prior notice. We recommend that you use the ENTITY-MIB instead of OLD-CISCO-CHASSIS-MIB.
Note The one exception to this recommendation is the chassisId object in this MIB, which can be set using the snmp-server chassis-id command. This object provides a convenient location for storing the serial number for the router's chassis, which is typically used to determine the service contract that you have purchased for this router.
OLD-CISCO-CPU-MIB
The OLD-CISCO-CPU-MIB describes CPU usage and active system processes on devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-CPU-MIB is being phased out and could become unsupported without prior notice. Therefore, use care if you implement the MIB.
OLD-CISCO-INTERFACES-MIB
The OLD-CISCO-INTERFACES-MIB contains objects to manage interfaces on devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-INTERFACES-MIB is being phased out and could become unsupported without prior notice. Therefore, use care if you implement the MIB.
OLD-CISCO-IP-MIB
The OLD-CISCO-IP-MIB contains objects to manage IP on devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-IP-MIB is being phased out and could become unsupported without prior notice. Therefore, use care if you implement the MIB.
OLD-CISCO-MEMORY-MIB
The OLD-CISCO-MEMORY-MIB contains objects that describe memory pools on devices running an older implementation of the Cisco IOS operating system. This MIB was replaced by the CISCO-MEMORY-POOL-MIB. Therefore, use care if you implement the OLD-CISCO-MEMORY-MIB, which is being phased out and could become unsupported without prior notice.
OLD-CISCO-SYSTEM-MIB
The OLD-CISCO-SYSTEM-MIB provides information about system resources on devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-SYSTEM-MIB is being phased out and could become unsupported without prior notice. Therefore, use care if you implement the MIB.
OLD-CISCO-TCP-MIB
The OLD-CISCO-TCP-MIB contains information about the TCP implementation on devices running an older implementation of the Cisco IOS operating system. This MIB was replaced by the CISCO-TCP-MIB. Therefore, use care if you implement the OLD-CISCO-TCP-MIB, which is being phased out and could become unsupported without prior notice.
OLD-CISCO-TS-MIB
The OLD-CISCO-TS-MIB contains objects to manage terminals and terminal lines on devices running an older implementation of the Cisco IOS operating system. Although currently supported on the router, the OLD-CISCO-TS-MIB is being phased out and could become unsupported without prior notice. Therefore, use care if you implement the MIB.
PIM-MIB
The PIM-MIB contains objects to manage Protocol Independent Multicast (PIM) on the router. The MIB was released as RFC 2934, Protocol Independent Multicast MIB for IPv4.
Note The MODULE-IDENTITY for the PIM-MIB is pimMIB, and its top-level OID is 1.3.6.1.3.61 (iso.org.dod.internet.experimental.pimMIB).
MIB Constraints
There are no constraints on this MIB.
RFC1213-MIB
The RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets. This MIB was released as RFC 1213, Management Information Base for Network Management of TCP/IP-Based Internets: MIB-II.
The MODULE-IDENTITY for the RFC1213-MIB is mib-2, and its top-level OID is 1.3.6.1.2.1 (iso.org.dod.internet.mgmt.mib-2).
MIB Constraints
Table 3-64 lists the constraints that the router places on RFC1213-MIB.
.
Table 3-64 RFC1213-MIB Constraints
MIB Object
|
Notes
|
atTable
|
|
•ipInAddrErrors
•ipInHdrErrors
|
These objects can provide inaccurate counts in releases before Cisco IOS Release 12.2(11)BC2.
|
RFC1231-MIB
The RFC1231-MIB includes objects to manage Token Ring (IEEE 802.5) interfaces. This MIB was released as RFC 1231, IEEE 802.5 Token Ring MIB, and has since been superseded by TOKENRING-MIB, which is not supported on Cisco CMTS routers.
MIB Constraint
This MIB was an experimental MIB and is no longer supported on Cisco CMTS platforms, although this MIB might be included in software images.
RFC1253-MIB
The RFC1253-MIB contains objects to manage Version 2 of the Open Shortest Path First (OSPF) protocol. This MIB was released as RFC 1253, OSPF Version 2 Management Information Base.
The MODULE-IDENTITY for the RFC1253-MIB is ospf, and its top-level OID is 1.3.6.1.2.1.14 (iso.org.dod.internet.mgmt.mib-2.ospf).
MIB Constraints
There are no constraints on this MIB.
RFC1315-MIB
The RFC1315-MIB contains objects to manage a Frame Relay data terminal equipment (DTE) interface, which consists of a single physical connection to the network with many virtual connections to other destinations and neighbors. The MIB contains the objects used to manage:
•The Data Link Connection Management Interface (DLCMI)
•Virtual circuits on each Frame Relay interface
•Errors detected on Frame Relay interfaces
The MODULE-IDENTITY for the RFC1315-MIB is frame-relay, and its top-level OID is 1.3.6.1.2.1.10.32 (iso.org.dod.internet.mgmt.mib-2.transmission.frame-relay).
MIB Constraints
There are no constraints on this MIB.
RFC1381-MIB
The RFC1381-MIB contains objects to manage the Link Access Procedure, Balanced (LAPB) link layer protocol for X.25 interfaces. This MIB was released as RFC 1381, SNMP MIB Extension for X.25 LAPB.
The MODULE-IDENTITY for the RFC1381-MIB is lapb, and its top-level OID is 1.3.6.1.2.1.10.16 (iso.org.dod.internet.mgmt.mib-2.transmission.lapb).
MIB Constraint
This MIB is not supported on the Cisco uBR10012 router.
RFC1382-MIB
The RFC1382-MIB contains objects to manage each Packet Level Entity (PLE) on X.25 interfaces. This MIB was released as RFC 1382, SNMP MIB Extension for the X.25 Packet Layer.
The MODULE-IDENTITY for the RFC1382-MIB is x25, and its top-level OID is 1.3.6.1.2.1.10.5 (iso.org.dod.internet.mgmt.mib-2.transmission.x25).
MIB Constraint
This MIB is not supported on the Cisco uBR10012 router.
RFC1406-MIB
The RFC1406-MIB contains objects to manage E1 and DS1 (T1) interfaces. This MIB was released as RFC 1406, Definitions of Managed Objects for the DS1 and E1 Interface Types.
The MODULE-IDENTITY for the RFC1595-MIB is ds1, and its top-level OID is 1.3.6.1.2.1.10.18 (iso.org.dod.internet.mgmt.mib-2.transmission.ds1).
MIB Constraints
There are no constraints on this MIB.
RFC1407-MIB
The RFC1407-MIB contains objects to manage E3 and DS3 (T3) interfaces. This MIB was released as RFC 1407, Definitions of Managed Objects for the DS3/E3 Interface Type.
The MODULE-IDENTITY for the RFC1595-MIB is ds3, and its top-level OID is 1.3.6.1.2.1.10.30 (iso.org.dod.internet.mgmt.mib-2.transmission.ds3).
MIB Constraints
There are no constraints on this MIB.
RFC1595-MIB
The RFC1595-MIB contains objects to manage Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This MIB was released as RFC 1595, Definitions of Managed Objects for the SONET/SDH Interface Type and has since been replaced by the RFC2558-MIB.
The MODULE-IDENTITY for the RFC1595-MIB is sonetMIB, and its top-level OID is 1.3.6.1.2.1.10.39 (iso.org.dod.internet.mgmt.mib-2.transmission.sonetMIB).
MIB Constraint
This MIB is not supported in Cisco IOS Release 12.1EC software images.
RFC2558-MIB
The RFC2558-MIB contains objects to manage Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This MIB was released as RFC 2558, Definitions of Managed Objects for the SONET/SDH Interface Type, and it replaces the previous MIB, RFC1595-MIB.
The MODULE-IDENTITY for the RFC2558-MIB is sonetMIB, and its top-level OID is 1.3.6.1.2.1.10.39 (iso.org.dod.internet.mgmt.mib-2.transmission.sonetMIB).
MIB Constraints
This MIB is supported only in Cisco IOS Release 12.1EC and only for Cisco uBR7100 series and Cisco uBR7200 series routers. Cisco IOS Release 12.2BC supports the previous version of this MIB, RFC1595-MIB.
RMON-MIB
The RMON-MIB contains objects to remotely monitor devices in the network. This MIB was released as RFC 1757, Remote Network Monitoring Management Information Base.
The MODULE-IDENTITY for the RMON-MIB is rmon, and its top-level OID is 1.3.6.1.2.1.16 (iso.org.dod.internet.mgmt.mib-2.rmon).
MIB Constraints
There are no constraints on this MIB.
RMON2-MIB
The RMON2-MIB contains supplements to RMON-MIB and contains additional objects to remotely monitor devices in the network.
The MODULE-IDENTITY for the RMON2-MIB is rmon2, and its top-level OID is 1.3.6.1.2.1.16 (iso.org.dod.internet.mgmt.mib-2.rmon2).
MIB Constraints
There are no constraints on this MIB.
RS-232-MIB
The RS-232-MIB contains objects to manage RS-232-like (EIA/TIA-232) serial interfaces. This MIB was derived from RFC 1659, Definitions of Managed Objects for RS-232-like Hardware Devices using SMIv2.
The MODULE-IDENTITY for the RS-232-MIB is rs232, and its top-level OID is 1.3.6.1.2.1.10.33 (iso.org.dod.internet.mgmt.mib-2.transmission.rs232).
MIB Constraints
There are no constraints on this MIB.
RSVP-MIB
The RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP). This MIB was derived from RFC 2206, RSVP Management Information Base Using SMIv2.
The MODULE-IDENTITY for the RSVP-MIB is rsvp, and its top-level OID is 1.3.6.1.2.1.51 (iso.org.dod.internet.mgmt.mib-2.rsvp).
MIB Constraints
There are no constraints on this MIB.
SMON-MIB
The SMON-MIB contains objects that supplement the RMON-MIB and the RMON2-MIB to manage the remote monitoring of switched networks. This MIB was derived from RFC 2613, Remote Network Monitoring MIB Extensions for Switched Networks.
The MODULE-IDENTITY for the SMON-MIB is switchRMON, and its top-level OID is 1.3.6.1.2.1.16.22 (iso.org.dod.internet.mgmt.mib-2.rmon.switchRMON).
MIB Constraints
There are no constraints on this MIB.
SNMP-COMMUNITY-MIB
The SNMP-COMMUNITY-MIB contains objects to help support coexistence between the different SNMP versions (SNMPv1, SNMPv2c, and SNMPv3). This MIB was released as RFC 2576, Coexistence Between Version 1, Version 2, and Version 3 of the Internet-Standard Network Management Framework.
The MODULE-IDENTITY for the SNMP-COMMUNITY-MIB is snmpCommunityMIB, and its top-level OID is 1.3.6.1.6.3.18 (iso.org.dod.internet.snmpv2.snmpModules.snmpCommunityMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-FRAMEWORK-MIB
The SNMP-FRAMEWORK-MIB contains objects that describe the SNMP management architecture. This MIB was released as RFC 2571, An Architecture for Describing SNMP Management Frameworks.
The MODULE-IDENTITY for the SNMP-FRAMEWORK-MIB is snmpFrameworkMIB, and its top-level OID is 1.3.6.1.6.3.10 (iso.org.dod.internet.snmpv2.snmpModules.snmpFrameworkMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-MPD-MIB
The SNMP-MPD-MIB contains objects from the agent's Message Processing and Dispatching (MPD) server that report on the the total number of packets received by the SNMP engine that were dropped because they referred to an unknown security model, were for an unknown application, or were otherwise invalid. This MIB was released as RFC 2572, Message Processing and Dispatching for the Simple Network Management Protocol (SNMP).
The MODULE-IDENTITY for the SNMP-MPD-MIB is snmpMPDMIB, and its top-level OID is 1.3.6.1.6.3.11 (iso.org.dod.internet.snmpv2.snmpModules.snmpMPDMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-NOTIFICATION-MIB
The SNMP-NOTIFICATION-MIB contains objects to manage SNMP v3 notifications. This MIB was released as RFC 2573, SNMP Applications.
The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable). Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of SNMP notifications those entities are to receive.
The MODULE-IDENTITY for the SNMP-NOTIFICATION-MIB is snmpNotificationMIB, and its top-level OID is 1.3.6.1.6.3.13 (iso.org.dod.internet.snmpv2.snmpModules.snmpNotificationMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-PROXY-MIB
The SNMP-PROXY-MIB contains managed objects to remotely configure the parameters used by an SNMP entity for proxy forwarding operations. The MIB contains a single table, snmpProxyTable, which defines the translations to use to forward messages between management targets. This MIB was defined as part of RFC 2573, SNMP Applications.
The MODULE-IDENTITY for the SNMP-PROXY-MIB is snmpProxyMIB, and its top-level OID is 1.3.6.1.6.3.14 (iso.org.dod.internet.snmpv2.snmpModules.snmpProxyMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-TARGET-MIB
The SNMP-TARGET-MIB contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of entities to send SNMP notifications to, and contains a list of tag values that are used to filter the notifications sent to these entities (see the SNMP-NOTIFICATION-MIB). This MIB was defined as part of RFC 2573, SNMP Applications.
The MODULE-IDENTITY for the SNMP-TARGET-MIB is snmpTargetMIB, and its top-level OID is 1.3.6.1.6.3.12 (iso.org.dod.internet.snmpv2.snmpModules.snmpTargetMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-USM-MIB
The SNMP-USM-MIB contains objects that describe the SNMP User-Based Security Model. This MIB was released as RFC 2574, User-Based Security Model (USM) for Version 3 of the Simple Network Management Protocol (SNMPv3).
The MODULE-IDENTITY for the SNMP-USM-MIB is snmpUsmMIB, and its top-level OID is 1.3.6.1.6.3.15 (iso.org.dod.internet.snmpv2.snmpModules.snmpUsmMIB).
MIB Constraints
There are no constraints on this MIB.
SNMP-VACM-MIB
The SNMP-VACM-MIB contains objects to manage the View-Based Access Control Model (VACM) for SNMP clients and managers. This MIB was released as RFC 2575, View-Based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP).
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).
MIB Constraints
There are no constraints on this MIB.
SNMPv2-MIB
The SNMPv2-MIB contains objects to manage SNMPv2 entities on the router. This MIB was released as RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2).
The MODULE-IDENTITY for the SNMPv2-MIB is snmpMIB, and its top-level OIDs are 1.3.6.1.6.3.1 (iso.org.dod.internet.snmpv2.snmpModules.snmpMIB) and 1.3.6.1.2.1.1 (iso.org.dod.internet.mgmt.mib-2.system).
MIB Constraints
There are no constraints on this MIB.
TCP-MIB
The TCP-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router. This MIB was derived from RFC 2012, SNMPv2 Management Information Base for the Transmission Control Protocol Using SMIv2.
The MODULE-IDENTITY for the TCP-MIB is tcpMIB, and its top-level OIDs are 1.3.6.1.2.1.49 (iso.org.dod.internet.mgmt.mib-2.tcpMIB) and 1.3.6.1.2.1.6 (iso.org.dod.internet.mgmt.mib-2.tcp).
MIB Constraints
There are no constraints on this MIB.
UDP-MIB
The UDP-MIB contains objects to manage the User Datagram Protocol (UDP) on the router. This MIB was released as RFC 2013, SNMPv2 Management Information Base for the User Datagram Protocol Using SMIv2.
The MODULE-IDENTITY for the UDP-MIB is udpMIB, and its top-level OIDs are 1.3.6.1.2.1.50 (iso.org.dod.internet.mgmt.mib-2.udpMIB) and 1.3.6.1.2.1.7 (iso.org.dod.internet.mgmt.mib-2.udp).
MIB Constraints
There are no constraints on this MIB.
Feedback
