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.
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.
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)SCF. 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
|
|
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-QOS3-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-QOS3-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).
ATM-MIB Tables and Objects
Table 3-3 lists ATM-MIB Tables and Objects..
Table 3-3 ATM-MIB Tables and Objects
|
|
|
Contains ATM local interface configuration parameters, one entry per ATM interface port. |
|
Contains ATM interface DS3 PLCP parameters and state variables, one entry per ATM interface port. |
|
Contains ATM interface TC Sublayer parameters and state variables, one entry per ATM interface port. |
atmTrafficDescrParamTable
|
Contains information on ATM traffic descriptor type and the associated parameters. |
|
Contains a bi-directional VPL is modeled as one entry in the Virtual Path Link (VPL) table. This table can be used for PVCs, SVCs and Soft PVCs. Entries are not present in this table for the VPIs used by entries in the atmVclTable. |
|
Contains a bi-directional VCL is modeled as one entry in the Virtual Channel Link (VCL) table. This table can be used for PVCs, SVCs and Soft PVCs. |
|
Contains an entry modelling two cross-connected VPLs. Each VPL must have its atmConnKind set to pvc(1). |
|
Contains an entry modelling two cross-connected VCLs. Each VCL must have its atmConnKind set to pvc(1). |
|
Contains AAL5 VCC performance parameters. |
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).
BGP4-MIB Tables and Objects
Table 3-4 lists BGP4-MIB Tables and Objects..
Table 3-4 BGP4-MIB Tables and Objects
|
|
|
Contains one entry per BGP peer, information about the connections with BGP peers. |
|
Contains information about paths to destination networks received from all peers running BGP version 3 or less. |
|
Contains information about paths to destination networks received from all BGP4 peers. |
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).
BRIDGE-MIB Tables and Objects
Table 3-5 lists BGP4-MIB Tables and Objects..
Table 3-5 BRIDGE-MIB Tables and Objects
|
|
|
Contains information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included. |
|
Contains port-specific information for the Spanning Tree Protocol. |
|
Contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame. |
|
Contains information about every port that is associated with this transparent bridge. |
|
Contains filtering information configured into the bridge by local or network management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table, as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and group/broadcast addresses. |
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-6 lists CISCO-802-TAP-MIB Tables and Objects.
.
Table 3-6 CISCO-802-TAP-MIB Tables and Objects
|
|
|
Contains the IEEE 802 data streams to be intercepted. The same data stream may be required by multiple taps, and one might assume that often the intercepted stream is a small subset of the traffic that could be intercepted. This essentially provides options for packet selection, only some of which might be used. For example, if all traffic to or from a given interface is to be intercepted, one would configure an entry which lists the interface, and wild-card everything else. If all traffic to or from a given MAC Address is to be intercepted, one would configure two such entries listing the MAC Address as source and destination respectively, and wild-card everything else. The first index indicates which Mediation Device the intercepted traffic will be diverted to. The second index permits multiple classifiers to be used together, such as having a MAC address as source or destination. Entries are added to this table via c802tapStreamStatus in accordance with the RowStatus convention. |
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
CISCO-AAA-SERVER-MIB Tables and Objects
Table 3-7 lists CISCO-AAA-SERVER-MIB Tables and Objects.
.
Table 3-7 CISCO--AAA-SERVER-MIB Tables and Objects
|
|
|
Contains the current configurations for each AAA server, allows existing servers to be removed and new ones to be created. |
|
Contains statistics for each server. |
MIB Constraints
The configuration objects in casConfigTable are implemented as read-only. Table 3-8 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-8 CISCO-AAA-SERVER-MIB Constraints
|
|
|
|
|
Read-only. |
|
Read-only. |
|
Read-only. |
|
Read-only. |
|
Read-only. |
|
|
- 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).
CISCO-AAL5-MIB Tables and Objects
Table 3-9 lists CISCO-AAL5-MIB Tables and Objects.
.
Table 3-9 CISCO-AAL5-MIB Tables and Objects
|
|
|
Contains AAL5 VCC performance parameters beyond that provided by aal5VccEntry defined in RFC1695. |
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).
CISCO-ACCESS-ENVMON-MIB Tables and Objects
Table 3-10 lists CISCO-ACCESS-ENVMON-MIB Tables and Objects.
.
Table 3-10 CISCO-ACCESS-ENVMON-MIB Tables and Objects
|
|
|
Contains the additional power supply information that are not covered in the ciscoEnvMonSupplyStatusTable of CISCO-ENVMON-MIB. |
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).
CISCO-ATM-EXT-MIB Tables and Objects
Table 3-11 lists CISCO-ATM-EXT-MIB Tables and Objects.
.
Table 3-11 CISCO-ATM-EXT-MIB Tables and Objects
|
|
|
Contains AAL5 VCC performance parameters beyond that provided by cAal5VccEntry. |
|
Contains Virtual Channel Link (VCL) Oam configuration and state information. This table augments the atmVclTable. |
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).
CISCO-ATM-PVCTRAP-EXTN-MIB Tables and Objects
Table 3-12 lists CISCO-ATM-PVCTRAP-EXTN-MIB Tables and Objects.
.
Table 3-12 CISCO-ATM-PVCTRAP-EXTN-MIB Tables and Objects
|
|
|
Contains ATM interface monitoring information not defined in the atmInterfaceConfTable from the ATM-MIB and atmInterfaceExtTable CISCO-IETF-ATM2-PVCTRAP-MIB. |
catmCurStatChangePVclTable
|
Contains all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed in the last corresponding PVC notification. |
catmStatusChangePVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed in the same direction in the last corresponding PVC notification. |
catmSegCCStatusChPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed due to segment CC failure in the same direction in the last PVC corresponding notification. |
catmEndCCStatusChPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed due to End CC failure in the same direction in the last PVC notification interval. |
catmAISRDIStatusChPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed due to AIS/RDI failure in the same direction in the last corresponding PVC notification. |
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have detected as Down in the last corresponding PVC notification. |
|
Contains all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to have changed to UP in the last corresponding PVC notification. |
catmStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and loopback OAM status to have detected as recovered in the last corresponding PVC notification. |
catmSegCCStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and Segment CC OAM status to have detected as recovered in the last corresponding PVC notification. |
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to be detected as Down in the last corresponding PVC notification. |
|
Contains all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to be changed to UP in the last corresponding PVC notification. |
catmStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and loopback OAM status to be detected as recovered in the last corresponding PVC notification. |
catmSegCCStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and Segment CC OAM status to be detected as recovered in the last corresponding PVC notification. |
catmEndCCStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and End-to-End CC OAM status to be detected as recovered in the last corresponding PVC notification. |
catmAISRDIStatusUpPVclRangeTable
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and AISRDI OAM status to be detected as recovered in the last corresponding PVC notification. |
|
Contains more than one VCLs in a consecutive range and for each VCL there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and atmVclOperStatus to be detected as Up in the last corresponding PVC notification. |
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).
CISCO-BGP4-MIB Tables and Objects
Table 3-13 lists CISCO-BGP4-MIB Tables and Objects.
.
Table 3-13 CISCO-BGP4-MIB Tables and Objects
|
|
|
Contains information about routes to destination networks from all BGP4 peers. Since BGP4 can carry routes for multiple Network Layer protocols, this table has the Address Family Identifier(AFI) of the Network Layer protocol as the first index. Further for a given AFI, routes carried by BGP4 are distinguished based on Subsequent Address Family Identifiers(SAFI). Hence that is used as the second index. Conceptually there is a separate Loc-RIB maintained by the BGP speaker for each combination of AFI and SAFI supported by it. |
|
Contains one entry per BGP peer, information about the connections with BGP peers. |
|
Contains the capabilities that are supported by a peer. Capabilities of a peer are received during BGP connection establishment. Values corresponding to each received capability are stored in this table. When a new capability is received, this table is updated with a new entry. When an existing capability is not received during the latest connection establishment, the corresponding entry is deleted from the table. |
|
Contains information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table. |
cbgpPeerAddrFamilyPrefixTable
|
Contains prefix related information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table. |
|
Contains one entry per BGP peer, information about the connections with BGP peers. |
|
Contains the capabilities that are supported by a peer. Capabilities of a peer are received during BGP connection establishment. Values corresponding to each received capability are stored in this table. When a new capability is received, this table is updated with a new entry. When an existing capability is not received during the latest connection establishment, the corresponding entry is deleted from the table. |
|
Contains information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table. |
cbgpPeer2AddrFamilyPrefixTable
|
Contains prefix related information related to address families supported by a peer. Supported address families of a peer are known during BGP connection establishment. When a new supported address family is known, this table is updated with a new entry. When an address family is not supported any more, corresponding entry is deleted from the table. |
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).
CISCO-BGP-POLICY-ACCOUNTING-MIB Tables and Objects
Table 3-14 lists CISCO-BGP-POLICY-ACCOUNTING-MIB Tables and Objects.
.
Table 3-14 CISCO-BGP-POLICY-ACCOUNTING-MIB Tables and Objects
|
|
|
Contains statistics about ingress and egress traffic on an interface. This data could be used for purposes like billing. |
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).
CISCO-BULK-FILE-MIB Tables and Objects
Table 3-15 lists CISCO-BULK-FILE-MIB Tables and Objects.
.
Table 3-15 CISCO-BULK-FILE-MIB Tables and Objects
|
|
|
Contains bulk file definition and creation controls. |
|
Contains objects to go in bulk files. |
|
Contains bulk file status. |
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).
CISCO-BUS-MIB Tables and Objects
Table 3-16 lists CISCO-BUS-MIB Tables and Objects.
.
Table 3-16 CISCO-BUS-MIB Tables and Objects
|
|
|
A (conceptual) table representing all the instantiations of BUSs on the designated device. This table may or may not allow the creation of rows depending on whether the LANE service elements allow the separate creation of LES and BUS components. In the event that separate components are not allowed then the MINIMUM-ACCESS detailed in the MODULE-COMPLIANCE should be used by those BUS implementations |
|
A (conceptual) table listing the clients associated with a BUS. Note that the local or network management will not create or destroy rows in this table but may only inspect what LECs are currently joined with the BUS. |
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.
CISCO-CABLE-ADMISSION-CTRL-MIB Tables and Objects
Table 3-17 lists ISCO-CABLE-ADMISSION-CTRL-MIB Tables and Objects..
Table 3-17 CISCO-CABLE-ADMISSION-CTRL-MIB Tables and Objects
|
|
|
Contains a sparse matrix of system resource utilization thresholds to be monitored by Cable Admission Control. The entPhysicalIndex uniquely identifies the physical entity with a set of system resource utilization thresholds being associated. The ccacSysRscConfigResourceType identifies the system resource to be monitored. The physical entities, for example, processors or linecards, are being expanded upon, and the expansion entails zero or more sets of system resource utilization thresholds. The agent creates/destroys/modifies an entry whenever the local console affects this configuration. The management application may create/destroy/modify an entry. When an entry is created and ccacSysRscConfigStatus is equal to ’active’, CMTS monitors the system resources based on the configurable thresholds, minor, major and critical for different monitoring system resources type and the main processor or a linecard. |
|
This table is deprecated by ccacUsConfigRevTable and abstracts a sparse matrix of upstream channel utilization thresholds to be monitored by Cable Admission Control. The ifIndex uniquely identifies all upstream channels, upstream channels associated with an interface or an upstream channel with a set of upstream channel utilization thresholds being associated. The ccacUsConfigSchedType identifies the scheduling type to be monitored. The ccacUsConfigServiceClassName identifies the cable service class to be monitored. The agent creates/destroys/modifies an entry whenever the local console affects this configuration. The management application may create/destroy/modify an entry. When an entry is created and ccacUsConfigStatus is equal to ’active’, CMTS monitors the upstream channel bandwidth utilization based on the configurable thresholds, minor, major and exclusive percentage, for different scheduling type or service class for an upstream channel. |
|
This table is deprecated by ccacDsConfigRevTable and abstracts a sparse matrix of downstream channel utilization thresholds to be monitored by Cable Admission Control. The ifIndex uniquely identifies all downstream channels, or a downstream channel with a set of upstream channel utilization thresholds being associated. The ccacDsConfigTrafficType identifies the downstream traffic type to be monitored. The agent creates/destroys/modifies an entry whenever the local console affects this configuration. The management application may create/destroy/modify an entry. When an entry is created and ccacDsConfigStatus is equal to ’active’, CMTS monitors the downstream bandwidth utilization based on the configurable thresholds, minor, major and exclusive percentage, for different traffic type for a downstream. |
|
Contains a sparse matrix of upstream channel utilization thresholds to be monitored by Cable Admission Control. The ifIndex uniquely identifies all upstream channels, upstream channels associated with an interface or an upstream channel with a set of upstream channel utilization thresholds being associated. The ccacUsConfigRevAppBucketIndex identifies the application bucket number being configured. The agent creates/destroys/modifies an entry whenever the local console affects this configuration. The management application may create/destroy/modify an entry. When an entry is created and ccacUsConfigRevStatus is equal to ’active’, CMTS monitors the upstream channel bandwidth utilization based on the configurable thresholds, minor, major and exclusive percentage, for different scheduling type or service class for an upstream channel. |
|
Contains a sparse matrix of downstream channel utilization thresholds to be monitored by Cable Admission Control. The ifIndex uniquely identifies all downstream channels, or a downstream channel with a set of upstream channel utilization thresholds being associated. The ccacDsConfigRevAppBucketIndex identifies the application bucket number being configured. The agent creates/destroys/modifies an entry whenever the local console affects this configuration. The management application may create/destroy/modify an entry. When an entry is created and ccacDsConfigRevStatus is equal to ’active’, CMTS monitors the downstream bandwidth utilization based on the configurable thresholds, minor, major and exclusive percentage, for different traffic type for a downstream. |
|
This table contains statistical data relating to system resource utilization for all configured physical entities and resource types. |
|
This table is deprecated by ccacUsRevTable. It contains statistical data relating to an upstream channel bandwidth utilization for every monitored upstream channel. There will be an entry in this table for each scheduling service per upstream channel being monitored. |
|
This table is deprecated by ccacDsRevTable. It contains the statistical data relating to downstream bandwidth utilization for every monitored downstream. There will be an entry in this table for each traffic type per downstream being monitored. |
|
Contains statistical data related to upstream channel bandwidth utilization for every monitored upstream channel and application bucket. For every upstream channel that is being monitored, if an application bucket has been configured in ccacUsConfigRevTable for that upstream channel, there will be one entry in this table. |
|
Containss the statistical data related to downstream bandwidth utilization for every monitored downstream channel and application bucket. For every downstream channel that is being monitored, if an application bucket has been configured in ccacDsConfigRevTable for that downstream channel, there will be one entry in this table. |
|
Contains a history of the monitored event in which the configured threshold is crossed. The number of most recent notifications will be saved based on the table size. |
MIB Constraints
Table 3-18 lists the constraints that the router places on CISCO-CABLE-ADMISSION-CTRL-MIB.
.
Table 3-18 CISCO-CABLE-ADMISSION-CTRL-MIB Constraints
|
|
|
|
|
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. |
|
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).
CISCO-CABLE-AVAILABILITY-MIB Tables and Objects
Table 3-19 lists CISCO-CABLE-AVAILABILITY-MIB Tables and Objects.
.
Table 3-19 CISCO-CABLE-AVAILABILITY-MIB Tables and Objects
|
|
|
Contains information of the HCCP groups on the CMTS. A HCCP group consists of a set of Working along with a Protect and each group is identified by a unique group ID number. Only members within a group are allowed to communicate with each other via HCCP messaging. |
|
Contains the mapping of the RF MAC interfaces on the CMTS to its functionality in the HCCP group. It indicates if the RF MAC interface has been configured as Protect or as a Working.It provides interface specific configuration and state information as well as statistics. |
ccaHCCPGroupTrackInterfaceTable
|
Contains the attributes of all the interfaces that are being tracked by this group. The interface can be any interface on the chassis, which is monitored by a keep alive timer. |
|
Contains the attributes of HCCP members. Each RF MAC interface configured for HCCP is called a HCCP member. Entries in this table are created for all members. In the case of Protect, it gives information of all the Working members under it’s protection group. In the case of Working, it gives information about itself. |
ccaHCCPMemChanSwitchTable
|
Provides information of HCCP member channel switches. It specifies the RF channel switch type, the RF switch over group and the RF switch module. The upconvertor IP addresses can also be retrieved from this table. This table does not exist if no channel switch has been enabled for this member in the group. |
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.
CISCO-CABLE-L2VPN-MIB Tables and Objects
Table 3-20 lists CISCO-CABLE-L2VPN-MIB Tables and Objects.
.
Table 3-20 CISCO-CABLE-L2VPN-MIB Tables and Objects
|
|
ccl2vpnMacVpnIdL2vpnIndexTable
|
Every L2VPN provisioned Cable Modem can be a part of multiple VPNs and the CMTS assigns a L2vpnIndex for each {Cable Modem MAC address, VPN-id} pair. This table maps {Cable Modem MAC address, VPN-id} to the L2vpnIndex. |
|
Every L2VPN Cable Modem can be provisioned with multiple VPNs and for each {Cable Modem MAC address, VPN-id} pair, there is a IP/MPLS pseudo-wire established. The pseudo-wire is specified by {peer IP address, VCID}. This table maps {peer IP address, VCID} to the L2vpnIndex. |
|
Every VPN provisioned for the L2VPN Cable Modem, the CMTS establishes pseudo-wire. This table maps L2vpnIndex to pseudo-wire configuration parameters. |
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-21 lists the behavior of the collection interval range objects ccmtrCollectionInterval and ccmtrCollectionRevInterval:
Table 3-21 Behavior of ccmtrCollectionInterval and ccmtrCollectionRevInterval Objects
|
|
|
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
CISCO-CABLE-METERING-MIB Tables and Objects
Table 3-22 lists CISCO-CABLE-METERING-MIB Tables and Objects.
.
Table 3-22 CISCO-CABLE-METERING-MIB Tables and Objects
|
|
|
This table is used only if ccmtrCollectionType object is stream which indicates that the metering records are to be streamed to an external collection server. It contains IP address information of the collection server. In addition it contains other configurable parameters like interval, retries etc needed for streaming the metering records. |
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).
CISCO-CABLE-QOS-MONITOR-MIB Tables and Objects
Table 3-23 lists CISCO-CABLE-QOS-MONITOR-MIB Tables and Objects..
Table 3-23 CISCO-CABLE-QOS-MONITOR-MIB Tables and Objects
|
|
|
Contains the attributes of the QoS enforce rules present on the CMTS. These enforce rules define the criteria for identifying subscribers who over consume resources. This could be as simple as bytes transmitted over the last monitoring duration and checked at a rate equal to the sample rate. In the sliding window concept used, the monitoring duration is the size of the window. This window slides by an amount that is equal to the sample rate. At every sample rate the bytes transmitted in the time equal to a monitoring duration is checked. If this is found to be larger than the threshold limit which is calculated by multiplying the defined average rate by the monitoring duration per monitoring duration, the subscriber is flagged as over consuming. Else the monitoring will continue. For example let the monitoring duration be 360 minutes and sample rate be 30 minutes. If the average rate is 2kbits/sec then every 30 minutes we check if the bytes transmitted in the last 360 minutes exceeded 5.4Mbytes bytes. If so, the subscriber is over consuming. The enforce rule has a one to one mapping to QoS profiles in case of DOCSIS1.0 (and DOCSIS1.0+ modems) and to service class names in case of DOCSIS1.1 and DOCSIS2.0 modems. It defines the registered QoS parameter set and an enforced QoS parameter set be applied if found to be violating the registered QoS parameter set. The enforce rule also defines a penalty period for which the enforced QoS parameter set will be applied. The registered QoS parameter set will be restored when the penalty period expires. The monitoring can be of two types: 1) Legacy/Basic monitoring: There is only one threshold and one monitoring-duration and the monitoring-duration can be more than one day and within a day there is no distinction among hours as peak or offpeak hours. An example would be: monitoring duration : 2 days Average rate : 2kbits/sec 2) Peak-offPeak monitoring: A maximum of two peak durations can be defined with in a day and the remaining hours are treated as off-peak and the monitoring will happen during these offpeak hours if the offpeak duration and threhold are defined. The monitoring-duration and threshold for all three, first peak, second peak and offpeak can be different. Here, the monitoring duration for any of the peaks or offpeak cannot be more than a day. An example when both peaks and offpeak are defined is: First peak: monitoring duration: Between 6am to 9am i.e., 3hours Average rate : 2kbits/sec Second peak: monitoring duration: Between 6pm to 10pm i.e., 4hrs Average rate : 3kbits/sec Off peak: Remaining hours in the day i.e., 12 midnight to 6:00am, 9am to 6pm and 10pm to 12mignight. monitoring duration: 2 hours Average rate : 1kbits/sec. |
|
Contains information of the subscribers who violated their enforce rule over the monitoring duration. In the sliding window concept used, the monitoring duration is the size of the window. This window slides by an amount that is equal to the sample rate. At every sample rate the bytes transmitted in the time equal to a monitoring duration is checked. If this is found to be larger than the defined byte count limit per monitoring duration, the subscriber is flagged as over consuming or to have violated his enforce rule. This table has entries for each of these violating subscribers. In case the violating subscriber has a enforced QoS parameter set, the QoS parameter set for such subscribers will be changed to the enforced QoS parameter set for the penalty time. When the penalty time expires, the subscriber gets his registered QoS parameter set restored and will no longer appear in this table but will be monitored. |
|
Contains the attributes which define the bandwidth utilization thresholds for the upstream and downstream interfaces and when the load on these interfaces exceeds the upper threshold, the monitoring of the associated modems service flows starts, and it stops when the interface utilization drops below the lower threshold. For the monitoring to start, there should be appropriate enforce-rules defined. In case no thresholds are defined, by default the monitoring of modems would take place if the appropriate enforce-rules are present. |
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).
CISCO-CABLE-SPECTRUM-MIB Tables and Objects
Table 3-24 lists CISCO-CABLE-SPECTRUM-MIB Tables and Objects.
.
Table 3-24 CISCO-CABLE-SPECTRUM-MIB Tables and Objects
|
|
|
Contains the records of modem state changes. It can be used to identify the problematic cable modems. An entry can be deleted from the table but can not be added to the table. |
|
Contains the records of modem state changes, so it can be used to identify the problematic cable modems. An entry per modem is added to the table automatically by the system when it detects any state changes to the modem. Therefore, it can be deleted but can not be added by the management system. |
|
Contains the spectrum data requests. There are two types of request: background noise and SNR. Refer to ccsSpectrumRequestIfIndex and ccsSpectrumRequestMacAddr DESCRIPTIONS on how the type of request is determined. |
|
Contains the receiving power or background noise measurement based on the criteria that is set in the ccsSpectrumRequestEntry. |
|
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. |
|
Contains the cable upstream interfaces in a fiber-node.Each fiber-node uniquely represents an RF domain.Cable upstream interfaces in the same fiber-node are physically combined together into the same RF domain. |
|
Contains the attributes of the cable upstream interfaces, ifType of docsCableUpstream(129), to be used for improving performance and proactive hopping. Proactive hopping is achieved by setting the SNR polling period over the in-use band without CM signals. |
|
Contains the frequency and band configuration of the spectrum group. |
MIB Constraints
Table 3-25 lists the constraints that the router places on CISCO-CABLE-SPECTRUM-MIB.
.
Table 3-25 CISCO-CABLE-SPECTRUM-MIB Constraints
|
|
|
|
|
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. |
|
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. |
|
|
- 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-26 lists the groups and objects added to the CISCO-CABLE-SPECTRUM-MIB.
.
Table 3-26 CISCO-CABLE-SPECTRUM-MIB Group Objects
|
|
|
Contains the frequency and band configuration of the spectrum group. |
|
|
|
Unsigned32 |
|
INTEGER |
|
Unsigned32 |
|
Unsigned32 |
|
StorageType |
|
RowStatus |
|
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. |
|
Unsigned32 |
- ccsSpecGroupUpstreamIfIndex
|
InterfaceIndex |
- ccsSpecGroupUpstreamStorage
|
StorageType |
- ccsSpecGroupUpstreamRowStatus
|
RowStatus |
|
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 |
|
Unsigned32 |
- ccsCombGroupUpstreamIfIndex
|
InterfaceIndex |
- ccsCombGroupUpstreamStorage
|
StorageType |
- ccsCombGroupUpstreamRowStatus
|
RowStatus |
CISCO-CABLE-WIDEBAND-MIB
The CISCO-CABLE-WIDEBAND-MIB supporst the Channel Bonding Protocol for the Cable Modem Termination System (CMTS). This MIB also allows for configuration of the RF channels on the Wideband CMTS, as well as the association between the RF and narrowband downstream channels with the Bonding Group channel.
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.
CISCO-CABLE-WIDEBAND-MIB Tables and Objects
Table 3-27 lists CISCO-CABLE-WIDEBAND-MIB Tables and Objects.
.
Table 3-27 CISCO-CABLE-WIDEBAND-MIBTables and Objects
|
|
|
Contains attributes of the physical RF channels. MPEG-TS packets are sent across RF channels within a wideband channel. These physical RF channels might be present on a different system but the WCMTS entity requires the knowledge of that system for its operation. |
|
Contains information of the external edge QAM which provide the physical RF channels which are available to the wideband channels. |
|
A wideband channel is a logical grouping of one or more physical RF channels over which Wideband MPEG-TS packets are carried. This table contains association information of the wideband channels to the RF channels that are available for the WCMTS. |
|
Contains information of the mapping of the wideband channels to the Narrowband channels that are available on the WCMTS. The wideband protocol utilizes the existing narrowband downstream channel for carrying the MAC management and signaling messages and the associated narrowband upstream for return data traffic and signaling. |
|
Contains information about a Wideband BG interface, whether its configured to carry multicast or non-multicast traffic. For multicast the BG interface type is Secondary and for non-multicast its non-Secondary. Other objects could be added to this later in the future. |
|
Contains Wideband Cable Modem(WCM) connectivity state. A WCM connectivity state can be associated with multiple Wideband interfaces. |
|
An entry in this table exists for each Wideband Cable Modem which links to one or more WB interface. |
|
Contains the description of a Fiber Node on a CMTS. An entry in this table exists for each FiberNode ID. |
|
Contains configuration information of each Fiber node. It will provide topology information of each Fiber node, which includes information such as, Narrowband and Wideband QAMs. |
Starting Cisco IOS Release 12.2(33)SCG, the DEPI tunnel in the RF channel may be configured using SNMP on the Cisco uBR10012 router. The ccwbRFChanQamDepiTunnel and ccwbRFChanQamTsid,MIB objects are added to the ccwbRFChannelTable. (See Table 3-28).
Table 3-28 ccwbRFChannelTable MIB Attributes
|
|
|
Contains attributes of the physical RF channels. |
|
Specifies the name of the DEPI tunnel which determines the DEPI data session configuration associated with this RF channel. |
|
Specifies the MPEG2 transport stream ID associated with this RF channel. |
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:
– show hw-module bay all mapping wideband-channel
– show hw-module bay all association wideband-channel
- For Cisco UBR-MC20X20V (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 Cisco uBR-MC8X8V (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
- For Cisco uBR-MC3GX60V (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
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 to 86400 seconds. Table 3-29 lists the tables/IPDR schemas affected by docsIfCmtsChannelUtilizationInterval attribute:
Table 3-29 Tables/IPDR Schemas Affected by docsIfCmtsChannelUtilizationInterval Attribute
|
|
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 to 86400 seconds, we suggest to choose a value greater than 300 sec (five minutes).
Starting with Cisco IOS Release 12.2(33)SCF, the ifIndex object (ccwbFiberNodeNBIfIndex) that pointed to the Integrated or Modular cable interface SNMP IF Index now points to the RF channel SNMP IF Index in table CcwbFiberNodeTable. Querying the CcwbFiberNodeTable displays the cable interfaces and RF channels for the Cisco uBR-MC3GX60V, Cisco UBR-MC20X20V, and Cisco uBR-MC88V line cards and SPAs. The DS-UTIL Schema points to RF channels.
Note In Cisco IOS Release 12.2(33)SCE and earlier releases, the ifIndex object pointed to the downstream or upstream channel of the cable interface or the Integrated cable or Modular cable SNMP IF Index.
MIB Constraints
Table 3-30 lists the constraints that the router places on CISCO-CABLE-WIDEBAND-MIB.
.
Table 3-30 CISCO-CABLE-WIDEBAND-MIB Constraints
|
|
|
|
|
Contains attributes of the physical RF channels. |
|
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. |
|
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. |
|
The valid values are:
- active(1)
- createAndGo(4)
- destroy(6)
|
|
Read-create. Value must be the same for all RF channels. |
|
Read-create. Value must be the same for all RF channels. |
|
Value is volatile(2). |
|
Unsigned32 |
|
Read-only. Counter64 |
|
Read-only. |
|
Contains information of the external edge QAM which provide the physical RF channels which are available to the wideband channels. |
|
Not implemented. |
|
Not implemented. |
- ccwbRFChanQamPriorityBits
|
Not implemented. |
|
Read-only. |
|
Values:
|
- ccwbRFChanQamIPAddressType
|
Only Internet address type ipv4 is supported. |
|
This table contains association information of the wideband channels to RF channels available for WCMTS. This converts to a read-only table. |
|
The valid value is volatile(2). |
|
The valid values are:
- active(1)
- createAndGo(4)
- destroy(6)
|
|
This table contains the description of a fiber node on a CMTS. |
|
Read-only. |
- ccwbFiberNodeDescrStorageType
|
The valid values are:
|
- ccwbFiberNodeDescrRowStatus
|
Read-only. |
|
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 |
|
Read-only. |
- ccwbFiberNodeWBContlrPhyIndx
|
Read-only. |
|
Read-only. |
|
The valid values are:
|
|
Read-only. |
|
This table contains wideband cable connectivity status. |
|
Read-only. |
|
This table provides information on either a primary or non-primary interface for the Wideband Interface. |
|
The valid values are:
- true(1) if the wideband interface (bond group) is secondary
- false(2) for non-secondary
|
|
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. |
|
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. |
This is a Cisco-only proprietary MIB which supports the DOCSIS 3.0 standard. |
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).
CISCO-CALL-HISTORY-MIB Tables and Objects
Table 3-31 lists CISCO-CALL-HISTORY-MIB Tables and Objects.
.
Table 3-31 CISCO-CALL-HISTORY-MIB Tables and Objects
|
|
|
Contains information about specific calls to a specific destination. |
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).
CISCO-CAR-MIB Tables and Objects
Table 3-32 lists CISCO-CAR-MIB Tables and Objects.
.
Table 3-32 CISCO-CAR-MIB Tables and Objects
|
|
|
Contains rate limit configuration entries. Rate Limit is a method of traffic control. It allows a set of rate limits to be configured and applied to packets flowing into/out of an interface to regulate network traffic. |
|
Contains rate limit status entries. |
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).
CISCO-CASA-FA-MIB Tables and Objects
Table 3-33 lists CISCO-CASA-FA-MIB Tables and Objects.
.
Table 3-33 CISCO-CASA-FA-MIB Tables and Objects
|
|
|
Contain stats on each Wildcard Affinity supported by the Forwarding Agent. This is a dynamic table. Entries are created when the Service Manager sends Wildcard Affinities to this Forwarding Agent, and deleted upon instruction from the Service Manager. |
|
A table of traffic statistics between this Forwarding Agent and the dispatch IP address. |
ccfaAdvertisedDispatchTable
|
This table correlates dispatch addresses with their corresponding advertised address. |
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).
CISCO-CASA-MIB Tables and Objects
Table 3-34 lists CISCO-CASA-MIB Tables and Objects.
.
Table 3-34 CISCO-CASA-MIB Tables and Objects
|
|
|
A Table of CASA configuration parameters. |
|
A Table of Multicast ports used by the Casa Entity to listen for Wildcard Affinities in the case of a Forwarding Agent, or for sending Wildcard Affinities in the case of a Service Manager. Adding entries to this table allows Forwarding Agents and Service Managers to exchange Wildcard Affinities on that multicast port. In this way, groups of Forwarding Agents may be configured to participate with particular groups of Service Managers. |
cCasaAffinityCacheStatsTable
|
A Table of Fixed Affinity cache statistics. The CASA Entity maintains a cache of Fixed Affinities. It contains objects that detail the dynamics of the cache. |
cCasaAffinityCacheSrcTable
|
A Table of Fixed Affinity cache entries. The number of entries for the specific Casa Entity is given by cCasaAffinityCacheNumOf. |
cCasaAffinityCacheDestTable
|
A Table of Fixed Affinity cache entries. The number of entries for the specific Casa Entity is given by cCasaAffinityCacheNumOf. It contains the same entries as cCasaAffinityCacheSrcTable. The order of the entries are in accordance with the described indices. |
cCasaAffinityCacheDispatchTable
|
A Table of Fixed Affinity cache entries. The number of entries for the specific Casa Entity is given by cCasaAffinityCacheNumOf. It contains the same entries as cCasaAffinityCacheSrcTable. The order of the entries are in accordance with the described indices. |
|
A Table of CASA statistics. |
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-CDOC-CHGRP-MIB
The CISCO-CDOC-CHGRP-MIB contains object that support Cisco Remote-PHY channel group SNMP management.
Version: 201309050000Z
MIB Tables and Objects
|
|
ciscoCdocChgrpTable |
Contains the Cisco Remote-PHY channel group table. A channel group consists of upstream channels, downstream channels and Cisco Coaxial Media Converters (CMC). |
ciscoCdocChgrpChanTable |
Contains the Cisco Remote-PHY channel group channel mapping table. |
ciscoCdocChgrpCmcTable |
Contains the Cisco Remote-PHY channel group Cisco CMC mapping table. |
MIB Constraints
There are no constraints on this MIB.
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).
CISCO-CDP-MIB Tables and Objects
Table 3-35 lists CISCO-CDP-MIB Tables and Objects.
.
Table 3-35 CISCO-CDP-MIB Tables and Objects
|
|
|
The (conceptual) table containing the status of CDP on the device’s interfaces. |
|
This table contains the additional CDP configuration on the device’s interfaces. |
|
The (conceptual) table containing the cached information obtained via receiving CDP messages. |
|
The (conceptual) table contains the list of network-layer addresses of a neighbor interface, as reported in the Address TLV of the most recently received CDP message. The first address included in the Address TLV is saved in cdpCacheAddress. This table contains the remainder of the addresses in the Address TLV. |
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).
CISCO-CIRCUIT-INTERFACE-MIB Tables and Objects
Table 3-36 lists CISCO-CIRCUIT-INTERFACE-MIB Tables and Objects.
.
Table 3-36 CISCO-CIRCUIT-INTERFACE-MIB Tables and Objects
|
|
|
Contains a circuit description to identify circuit based interfaces like ATM, Frame-Relay etc. The circuit description could be used for example, to correlate performance statistics associated with the corresponding interfaces. |
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).
CISCO-CLASS-BASED-QOS-MIB Tables and Objects
Table 3-37 lists CISCO-CLASS-BASED-QOS-MIB Tables and Objects.
.
Table 3-37 CISCO-CLASS-BASED-QOS-MIB Tables and Objects
|
|
cbQosQueueingClassCfgTable
|
Specifies the configuration information for weighted queue limit action per IP precedence basis. |
cbQosMeasureIPSLACfgTable
|
Specifies configuration information for measure type IPSLA action. The measure action relates the policy class to a specific IPSLAs auto group. Configuration of measure action of type IPSLA results in automatic generation of IPSLAs synthetic test operations when the policy is attached to interface. The operations are created according to the characteristics specified and to the destinations specified in IPSLA auto group. The IPSLAs sythentic test operations measure network statistics such as latency, packet loss and jitter. This table is to be used only for retrieving the measure action configuration information. |
|
Describes the logical interfaces/media types and the policymap that are attached to it. |
cbQosInterfacePolicyTable
|
Describes the service polices that are attached to main and sub interfaces. |
cbQosFrameRelayPolicyTable
|
Describes the service polices that are attached to Frame Relay DLCIs. |
|
Describes the policies that are attached to a ATM PVC. |
|
Specifies QoS objects (classmap, policymap, match statements, and actions) hierarchy. It also provide relationship between each PolicyIndex/ObjectsIndex pair and the ConfigIndex. ConfigIndex is essential for querying any configuration tables. |
|
Specifies Policymap configuration information |
|
Specifies ClassMap configuration information |
|
Specifies ClassMap configuration information |
|
Specifies Queueing Action configuration information |
|
Specifies WRED Action configuration information |
|
Specifies WRED Action configuration information on a per IP precedence basis. |
|
Specifies Police Action configuration information. |
cbQosPoliceActionCfgTable
|
Specifies Police Action configuration information. |
|
Specifies traffic-shaping Action configuration information. |
|
Specifies Packet Marking Action configuration information. |
|
Specifies ClassMap related Statistical information. |
|
This table specifies Match Statement related statistical information. |
|
Specifies Police Action related Statistical information. |
|
Specifies Queueing Action related Statistical information. |
|
Specifies traffic-shaping Action related Statistical information. |
|
Specifies per Precedence WRED Action related Statistical information. |
|
Specifies IP Header Compression configuration information. |
|
Specifies IP Header Compression statistical information. |
|
Specifies packet marking statistical information. |
cbQosPoliceColorStatsTable
|
Specifies Police Action related Statistical information for two rate color aware marker. |
|
Specifies Table Map basic configuration information. |
cbQosTableMapValueCfgTable
|
Specifies Specifies the from-value to to-value conversion pairs for a tablemap. |
|
Specifies enhanced packet marking configuration using a pre-defined tablemap. |
|
Specifies Estimate Bandwidth related configuration information. |
|
Specifies Estimate Bandwidth related statistical information. |
|
Specifies C3pl Account Action configuration information |
cbQosC3plAccountStatsTable
|
Specifies C3pl Account Action related statistics information. |
MIB Constraints
Table 3-38 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-38 CISCO-CLASS-BASED-QOS-MIB Constraints for the uBR7200 Series Router
|
|
|
|
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
Not supported. Always 0. |
cbQosInterfacePolicyTable
|
|
- cbQosInterfacePolicyIndex
|
Not supported. Always 0. |
cbQosFrameRelayPolicyTable
|
|
|
Not supported. Always 0. |
|
|
|
Not supported. Always 0. |
|
|
- cbQosQueueingCfgFlowEnabled·
|
Not supported. Always false(2). |
- cbQosQueueingCfgIndividualQSize·
|
Not supported. Always 0. |
- cbQosQueueingCfgDynamicQNumber·
|
Not supported. Always 0. |
- cbQosQueueingCfgPrioBurstSize
|
Not supported. Always 0. |
|
|
|
Not supported for PRE1. Always 0. |
|
DSCP-based is not supported. |
|
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. |
|
|
|
Not supported. Always 0. |
|
Not supported. Always 0. |
- cbQosTSCfgAdaptiveEnabled
|
Not supported. Always false(2). |
|
Not supported. Always 0. |
|
Not supported. Always average(1). |
|
|
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
|
- cbQosPoliceConformedBitRate
|
Not supported. Always 0. |
- cbQosPoliceExceededBitRate
|
Not supported. Always 0. |
- cbQosPoliceViolatedBitRate
|
Not supported. Always 0. |
|
|
- cbQosQueueingDiscardByte64
|
Not supported. Always 0. |
- cbQosQueueingDiscardByteOverflow
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
|
- cbQosTSStatsDelayedByteOverflow·
|
Not supported. Always 0. |
|
Not supported. Always 0. |
- cbQosTSStatsDelayedByte64
|
Not supported. Always 0. |
- cbQosTSStatsDelayedPktOverflow
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
Not supported. Always 0. |
- cbQosTSStatsDropByteOverflow
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
Not supported. Always 0. |
|
Not dynamic. If traffic shaping is configured, then cbQosTSStatsActive is true(1); otherwise, it is false(2). |
|
|
- 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-CMC-MGR-MIB
The CISCO-CMC-MGR-MIB contains objects that support Cisco CMC management for the Cisco Remote-PHY solution. Cisco CMC is a remote-PHY system, which includes both upstream and downstream PHY. Cisco CMC can be installed near or inside the buildings. Cisco CMC has both RFI and GigE interfaces. The Cisco uBR-MC3GX60V-RPHY line card for Cisco Remote-PHY solution does not have RFI interface, it has the GigE interface for both upstream and downstream.
Version: 201405120000Z
MIB Tables and Objects
|
|
ciscoCmcTable |
Contains the basic attributes of the Cisco CMC, including MAC Address, IP Address, status, and so on. |
ciscoCmcFrxTable |
Contains the basic attributes of the FRx module in the Cisco CMC, including FRx PID, VID, hardware version, and so on. |
ciscoCmcMacToIndexMappingTable |
Contains the mapping between the Cisco CMC MAC address and index. |
ciscoCmcMappingTable |
Contains information on the channel group that is used by the specified Cisco CMC index. |
MIB Constraints
There are no constraints on this MIB.
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).
CISCO-COMPRESSION-SERVICE-ADAPTER-MIB Tables and Objects
Table 3-39 lists CISCO-COMPRESSION-SERVICE-ADAPTER-MIB Tables and Objects.
.
Table 3-39 CISCO-COMPRESSION-SERVICE-ADAPTER-MIB Tables and Objects
|
|
csaStatsTable |
Describes performance statistics and status of compression service adapter. |
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).
CISCO-CONFIG-COPY-MIB Tables and Objects
Table 3-40 lists CISCO-CONFIG-COPY-MIB Tables and Objects.
.
Table 3-40 CISCO-CONFIG-COPY-MIB Tables and Objects
|
|
|
Contains config-copy requests. |
|
Contains information about the failure cause of the config copy operation. An entry is created only when the value of ccCopyState changes to ’failed’ for a config copy operation. Not all combinations of ccCopySourceFileType and ccCopyDestFileType need to be supported. For example, an implementation may choose to support only the following combination: ccCopySourceFileType = ’runningConfig’ ccCopyDestFileType = ’fabricStartupConfig’. In the case where a fabric wide config copy operation is being performed, for example by selecting ccCopyDestFileType value to be ’fabricStartupConfig’, it is possible that the fabric could have more than one device. In such cases this table would have one entry for each device in the fabric. In this case even if the operation succeeded in one device and failed in another, the operation as such has failed, so the global state represented by ccCopyState ’failed’, but for the device on which it was success, ccCopyErrorDescription would have the distinguished value, ’success’. Once the config copy operation completes and if an entry gets instantiated, the management station should retrieve the values of the status objects of interest. Once an entry in ccCopyTable is deleted by management station, all the corresponding entries with the same ccCopyIndex in this table are also deleted. In order to prevent old entries from clogging the table, entries age out at the same time as the corresponding entry with same ccCopyIndex in ccCopyTable ages out. |
MIB Constraints
Table 3-41 lists the constraints that the router places on CISCO-CONFIG-COPY-MIB.
.
Table 3-41 CISCO-CONFIG-COPY-MIB Constraints
|
|
|
|
|
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).
CISCO-CONFIG-MAN-MIB Tables and Objects
Table 3-42 lists CISCO-CONFIG-MAN-MIB Tables and Objects.
.
Table 3-42 CISCO-CONFIG-MAN-MIB Tables and Objects
|
|
ccmCLIHistoryCommandTable
|
Contains CLI commands that took effect during configuration events. |
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.
- Wideband Support—In Cisco IOS Release 12.2(33)SCC and later releases, the CISCO-DOCS-EXT-MIB includes objects for the scheduler that supports quality of service (QoS) of MCNS/DOCSIS compliant 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 supported only on the cable upstream interface. Bandwidth queue is not supported on the cable downstream for MC interfaces.
- Wideband Modem Resiliency—Starting with Cisco IOS Release 12.2(33)SCG2 and later releases, the following MIB tables and objects are added for the Wideband Resilency feature.
– cdxWBResilRFChangeDampenTime
– cdxWBResilRFChangeTriggerPercentage
– cdxWBResilRFChangeTriggerCount
– cdxWBResilRFChangeTriggerMoveSecondary
These MIB objects represent the threshold values configured using the cable rf-change-trigger percent | count | secondary command and the cable rf-change-dampen-time command.
Note Cisco IOS Release 12.2(33)SCG2 introduces new traps that are sent when the logical RF channel changes from the UP or DOWN state. For more information about the CISCO-DOCS-EXT-MIB notifications, see the “Cable MIB Notifications” section.
For more information on the Wideband resiliency feature, see Wideband Modem Resiliency.
- Physical Channel Interface Mapping—This feature, which was introduced in Cisco IOS Release 12.2(33)SCG2 and later releases provides an SNMP interface to access information between the physical channel interface and the primary channel interface. The following MIB objects can be queried for information about the physical channel interface and the primary channel interface.
– cdxRFtoPrimaryChannelMappingTable
– cdxPrimaryChanneltoRFMappingTable
The IfIndex entry is updated in both the tables,when a physical channel is added into a channel group domain as a primary channel.
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).
MIB Tables
Table 3-43 lists the tables in CISCO-DOCS-EXT-MIB.
Table 3-43 CISCO-DOCS-EXT-MIB Tables
|
|
|
Maintains a number of objects related to Quality of Service scheduler, for each upstream interface, which uses these attributes to control cable modem registration. |
|
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. |
|
Contains the additional attributes of a single Service ID that provided by docsIfCmtsServiceEntry. |
|
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. |
|
Contains the attributes of queues in cable interfaces schedulers that support Quality of Service. |
|
Contains information about cable modems (CM) or Customer Premises Equipments (CPE). |
|
Contains the additional CM status information. |
|
Contains the additions attributes of a CMTS MAC interface that provided by docsIfCmtsMacTable. |
|
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. |
|
Contains attributes or configurable parameters for cable modems from a CMTS. |
|
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. |
|
Contains information about CPE connects behind cable modem. It returns 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 impacts 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. |
|
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 impacts 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. |
|
Contains a list CPE’s IP Prefix management information. |
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. |
cdxRFtoPrimaryChannelMappingTable
|
Contains information of the mapping of the physical RF channels to the primary RF channels. |
cdxPrimaryChanneltoRFMappingTable
|
Contains information of the mapping of the primary RF channels to the physical RF channels. |
|
Contains the CM management information of a Transmit Channel Set (TCS) in the system. |
|
Contains the Upstream Channel Bonding Service Flow management information. |
cdxCmtsMtcCmTable
The CdxCmtsMtcCmEntry provides the CM statistics and management information of a specific TCS.
Table 3-44 lists the MIB objects in CdxCmtsMtcCmEntry.
Table 3-44 MIB Objects in CdxCmtsMtcCmEntry
|
|
|
Indicates the ID of the Transmit Channel Set. |
|
Indicates the total number of cable modems which use this TCS in the MAC domain. |
|
Indicates the number of operational cable modems which use this TCS in the MAC domain. |
|
Indicates the number of registered cable modems which use this TCS in the MAC domain. |
|
Indicates the number of unregistered cable modems which use this TCS in the MAC domain. |
|
Indicates the number of offline cable modems which use this TCS in the MAC domain. |
|
Indicates the number of operational cable modems, which are in wideband state and use this TCS in the MAC domain. |
cdxCmtsMtcUpstreamBondGrp
|
Specifies the upstream channel bonding group. |
cdxCmtsUscbSflowTable
The cdxCmtsUscbSflowEntry contains the service flow statistics for a specific upstream channel bonding group.
Table 3-45 lists the MIB objects in cdxCmtsUscbSflowEntry.
Table 3-45 MIB Objects in cdxCmtsUscbSflowEntry
|
|
|
Indicates the upstream bonding group identifier within the MAC Domain. |
|
Indicates the number of service flows which use this upstream channel bonding group. |
|
Indicates the number of primary service flows which use this upstream channel bonding group. |
|
Indicates the number of static BE service flows which use this upstream channel bonding group. |
|
Indicates the number of static UGS service flows which use this upstream channel bonding group. |
|
Indicates the number of static UGS-AD service flows which use this upstream channel bonding group. |
|
Indicates the number of static RTPS service flows which use this upstream channel bonding group. |
|
Indicates the number of static NRTPS service flows which use this upstream channel bonding group. |
|
Indicates the number of dynamic BE service flows which use this upstream channel bonding group. |
|
Indicates the number of dynamic UGS service flows which use this upstream channel bonding group. |
|
Indicates the number of dynamic UGS-Ad service flows which use this upstream channel bonding group. |
|
Indicates the number of dynamic RTPS service flows which use this upstream channel bonding group. |
|
Indicates the number of dynamic NRTPS service flows which use this upstream channel bonding group. |
|
Describes the upstream channel bonding group. |
MIB Constraints
Table 3-46 lists the constraints that the router places on CISCO-DOCS-EXT-MIB.
.
Table 3-46 CISCO-DOCS-EXT-MIB Constraints
|
|
|
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. |
|
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. |
|
|
- 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 |
|
|
- cdxIfCmtsServiceOutOctets—Counter 32
cdxIfCmtsServiceOutPackets—Counter32
|
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. |
- cdxIfCmtsServiceHCInOctets—Counter64
cdxIfCmtsServiceHCInPackets—Counter64 cdxIfCmtsServiceHCOutOctets—Counter64 cdxIfCmtsServiceHCOutPackets—Counter64
|
Effective with Cisco IOS Release 12.2(33)SCF5, 12.2(33)SCG2, and later releases, four 64-counter objects are added. cdxIfCmtsServiceHCInOctets and cdxIfCmtsServiceHCInPackets report the upstream traffic counters. cdxIfCmtsServiceHCOutOctets and cdxIfCmtsServiceHCOutPackets report the downstream traffic counters. |
|
|
|
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. |
|
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.
|
|
|
- cdxIfCmtsCmStatusLastResetTime
|
|
- cdxIfCmtsCmStatusOnlineTimesNum
|
|
|
This table contains the list of modems which failed the CMTS Dynamic Message Integrity Check (DMIC). |
|
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.
|
|
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. |
cdxRFtoPrimaryChannelMappingTable
|
This table contains the physical RF channel to primary RF channel mapping information. This object is used to map the physical channel interface to the primary channel interface. The cdxPrimaryChannelIfIndex object defines the ifIndex of the primary interface. Note The physical interface and the primary interface are the same on the Cisco uBR10-MC5X20 line card. For line card interfaces such as Cisco uBR-MC3G60V, Cisco UBR-MC20X20V, Cisco MC8X8V, and SPA interfaces, when a physical channel is added to the channel group domain (CGD) as a primary channel, an entry for this physical channel is automatically added to the table. |
- cdxRFtoPrimaryChannelMappingEntry
|
This entry provides the association between the physical RF channels and the primary RF channels. |
|
This is the ifIndex of the primary channel interface. |
cdxPrimaryChanneltoRFMappingTable
|
This table contains the primary RF channel to physical RF channel mapping information. This MIB object maps the primary interface to the physical channel interface by ifIndex. The cdxPhysicalRFIfIndex object defines the ifIndex of the physical channel interface. Note The physical interface and the primary interface are the same on the Cisco uBR10-MC5X20 line card. For line card interfaces such as Cisco uBR-MC3G60V, Cisco UBR-MC20X20V, Cisco MC8X8V, and SPA interfaces, when a physical channel is added into a CGD as a primary channel and the ifIndex of the primary interface is known, the ifIndex of the physical channel interface can be queried using this table. |
- cdxPrimaryChanneltoRFMappingEntry
|
This entry provides the association between the primary RF channels and the physical RF channels. |
|
The is the ifIndex of the physical RF channel interface. |
cdxWBResilRFChangeDampenTime
|
This object defines the amount of time an RF channel must remain in its new state, either UP or DOWN, before the transition is considered valid. This value applies to all non-primary RF channels in the Cisco CMTS. |
cdxWBResilRFChangeTriggerPercentage
|
This object denotes the percentage of cable modems with a particular non-primary RF channel in DOWN state, before the channel is removed from any or all bonding groups. The value of 0 will prevent any bonding group modifications. To dampen the change of state of an RF channel, the trigger for a channel is restored by using half the number of channels in DOWN state. For example, if this object is set to 20, and 20 percent of the CMs report an RF channel in DOWN state, then the logical state is changed to DOWN. If only 10 percent of the CMs report the affected RF channel, the logical state will change to UP state. |
cdxWBResilRFChangeTriggerCount
|
This object denotes the total numbers of CMs reporting the RF impairment. In scenarios where small numbers of wideband modems exist, an absolute value for triggering can be specified in addition to the percentage. |
cdxWBResilRFChangeTriggerMoveSecondary
|
This object denotes whether the secondary service flows are allowed to be moved and created on the narrowband interface. |
Table 3-47 CISCO-DOCS-EXT-MIB Notification Objects
|
|
cdxWBResilNotificationEnable
|
This obkect indicates whether the cdxWBResilRFDown object and cdxWBResilRFUp object are enabled. The default value is false. |
cdxWBResilNotificationsInterval
|
This object denotes the interval when cdxWBResilEvent traps could be sent per CM. This object is used to avoid too many cdxWBResilEvent traps sent for a cable modem during a short period. The default value is 1 second. If the value is 0, then the cdxWBResilEvent trap is sent for every wideband resiliency event. |
|
This object defines the priority level of this event. |
|
This object indicates the type of event that is received by Cisco CMTS. |
|
This object indicates the time interval when Cisco CMTS receives this event from system startup. |
cdxWBResilEventTotalCount
|
The object indicates the count of events the Cisco CMTS receives. |
cdxWBResilEventTotalDupCount
|
The object indicates the duplicated count of events he Cisco CMTS receives. |
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).
CISCO-DOCS-REMOTE-QUERY-MIB Tables and Objects
Table 3-48 lists CISCO-DOCS-REMOTE-QUERY-MIB Tables and Objects.
.
Table 3-48 CISCO-DOCS-REMOTE-QUERY-MIB Tables and Objects
|
|
|
Contains the status of the cable modems that are polled by the CMTS CM Poller. The information will be overwritten when a new polling cycle starts. The removal of CM from the list or adding a new CM to the list won’t be reflected until the next polling cycle. Depending on how many CMs that the poller is polling, polling this table constantly can be quite expensive; Therefore, it is best to poll upon receipt of the cdrqCmtsCmRQDoneNotification. As a hedge against lost notifications, periodic background polling should be performed. Howerver, excessive polling could degrade performance. |
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-49 lists the constraint that the router places on CISCO-DOCS-REMOTE-QUERY-MIB.
.
Table 3-49 CISCO-DOCS-REMOTE-QUERY-MIB Constraints
|
|
|
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).
CISCO-ENHANCED-MEMPOOL-MIB Tables and Objects
Table 3-50 lists CISCO-ENHANCED-MEMPOOL-MIB Tables and Objects.
.
Table 3-50 CISCO-ENHANCED-MEMPOOL-MIB Tables and Objects
|
|
|
Contains memory pool monitoring entries for all physical entities on a managed system. |
|
Contains entries in this table define entities (buffer pools in this case) which are contained in an entity (memory pool) defined by an entry from cempMemPoolTable. -- Basic Pool Architecture -- 1)Pools are classified as being either Static or Dynamic. Static pools make no attempt to increase the number of buffers contained within them if the number of free buffers (cempMemBufferFree) are less than the number of minimum buffers (cempMemBufferMin). With Dynamic pools, the pool attempts to meet the demands of its users. 2)Buffers in a pool are classified as being either Permanent or Temporary. Permanent buffers, as their name suggests, are always in the pool and are never destroyed unless the number of permanent buffers (cempMemBufferPermanent) is changed. Temporary buffers are transient buffers that are created in dynamic pools whenever the free count (cempMemBufferFree) of buffers in the pool drops below the minimum (cempMemBufferMin). 3)Buffers pools are classified as either Public or Private. Public pools are available for all users to allocate buffers from. Private pools are primarily used by interface drivers. |
cempMemBufferCachePoolTable
|
Lists the cache buffer pools configured on a managed system. 1)To provide a noticeable performance boost, Cache Pool can be used. A Cache Pool is effectively a lookaside list of free buffers that can be accessed quickly. Cache Pool is tied to Buffer Pool. 2)Cache pools can optionally have a threshold value on the number of cache buffers used in a pool. This can provide flow control management by having a implementation specific approach such as invoking a vector when pool cache rises above the optional threshold set for it on creation. |
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. To monitor alarms generated by a physical entity, it must be represented by a row in the entPhysicalTable (see ENTITY-MIB).
Note The CISCO-ENTITY-ALARM-MIB monitors the alarms of physical entities.
CISCO-ENTITY-ALARM-MIB Tables and Objects
The following table lists CISCO-ENTITY-ALARM-MIB Tables and Objects.
Table 3-51 CISCO-ENTITY-ALARM-MIB Tables and Objects
|
|
|
For each type of entity (represented entPhysicalVendorType OID), this table contains a mapping between a unique ceAlarmDescrIndex and entPhysicalvendorType OID. |
|
Contains a description for each alarm type defined by each vendor type employed by the system. Observe that this table is sparse in nature, as it is rarely the case that a physical entity type needs to define every alarm in its alarm space. |
|
Specifies alarm control and status information related to each physical entity contained by the system, including the alarms currently being asserted by each physical entity capable of generating alarms. |
|
Contains a history of ceAlarmIndicate and ceAlarmClear traps generated by the agent. |
ceAlarmFilterProfileTable
|
Contains a list of alarm filter profiles. |
MIB Constraints
The following table 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-52 CISCO-ENTITY-ALARM-MIB Constraints
|
|
|
Read-only. |
ceAlarmFilterProfileTable
|
Not implemented. |
|
Not implemented. |
CISCO-ENTITY-ASSET-MIB
The CISCO-ENTITY-ASSET-MIB provides asset tracking information for the physical components in the ENTITY-MIB (RFC 2037) entPhysical table. 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).
CISCO-ENTITY-ASSET-MIB Tables and Objects
The following table lists the CISCO-ENTITY-ASSET-MIB Tables and Objects.
Table 3-53 CISCO-ENTITY-ASSET-MIB Tables and Objects
|
|
|
Lists the orderable part number, serial number, hardware revision, manufacturing assembly number and revision, firmwareID and revision if any, and softwareID and revision if any, of relevant entities listed in the ENTITY-MIB entPhysicalTable. Entities for which none of this data is available are not listed in this table. This is a sparse table so some of these variables may not exist for a particular entity at a particular time. For example, a powered-off module does not have softwareID and revision; a power-supply does not have firmware or software information. Although the data may have other items encoded in it (for example, manufacturing-date in the serial number) treat all data items as monolithic. Do not decompose or parse them. Use only string equals and unequals operations on them. |
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).
CISCO-ENTITY-EXT-MIB Tables and Objects
Table 3-54 lists CISCO-ENTITY-EXT-MIB Tables and Objects.
.
Table 3-54 CISCO-ENTITY-EXT-MIB Tables and Objects
|
|
ceExtPhysicalProcessorTable
|
The ceExtPhysicalProcessorTable extends the ENTITY-MIB entPhysicalTable for modules (Non FRUs(Field Replacable Units) or FRUs). |
|
The ceExtConfigRegTable extends the ENTITY-MIB entPhysicalTable. |
|
Contains information of LED on an entity. |
|
Contains additional information about a particular physical entity. This table augments the ’entPhysicalTable’ of the ENTITY-MIB. |
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). FRUs include assemblies such as power supplies, fans, processor modules, interface modules, and so on.
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).
CISCO-ENTITY-FRU-CONTROL-MIB Tables and Objects
The following table lists CISCO-ENTITY-FRU-CONTROL-MIB Tables and Objects.
Table 3-55 CISCO-ENTITY-FRU-CONTROL-MIB Tables and Objects
|
|
cefcFRUPowerSupplyGroupTable
|
Lists the redundancy mode and the operational status of the power supply groups in the system. |
|
Lists the power-related administrative status and operational status of the manageable components in the system. |
cefcFRUPowerSupplyValueTable
|
Lists the power capacity of a power FRU in the system if it provides variable power. Power supplies usually provide either system or inline power. They cannot be controlled by software to dictate how they distribute power. We can also have what are known as variable power supplies. They can provide both system and inline power and can be varied within hardware defined ranges for system and inline limited by a total maximum combined output. They could be configured by the user via CLI or SNMP or be controlled by software internally. This table supplements the information in the cefcFRUPowerStatusTable for power supply FRUs. The cefcFRUCurrent attribute in that table provides the overall current the power supply FRU can provide while this table gives us the individual contribution towards system and inline power. |
|
A cefcModuleTable entry lists the operational and administrative status information for ENTITY-MIB entPhysicalTable entries for manageable components of type PhysicalClass module(9). |
|
Sparsely augments the cefcModuleTable (that is, every row in this table corresponds to a row in the cefcModuleTable but not necessarily vice-versa). A cefcIntelliModuleTable entry lists the information specific to intelligent modules which cannot be provided by the cefcModuleTable. |
cefcModuleLocalSwitchingTable
|
Sparsely augments the cefcModuleTable (that is, every row in this table corresponds to a row in the cefcModuleTable but not necessarily vice-versa). A cefcModuleLocalSwitchingTable entry lists the information specific to local switching capable modules which cannot be provided by the cefcModuleTable. |
|
Contains the operational status information for all ENTITY-MIB entPhysicalTable entries which have an entPhysicalClass of ’fan’; specifically, all entPhysicalTable entries which represent either; one physical fan, or a single physical ’fan tray’ which is a manufactured (inseparable in the field) combination of multiple fans. |
|
Contains one row per physical entity. |
cefcPowerSupplyInputTable
|
Contains the power input information for all the power supplies that have entPhysicalTable entries with ’powerSupply’ in the entPhysicalClass. The entries are created by the agent at the system power-up or power supply insertion. Entries are deleted by the agent upon power supply removal. The number of entries is determined by the number of power supplies and number of power inputs on the power supply. |
cefcPowerSupplyOutputTable
|
Contains a list of possible output mode for the power supplies, whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of ’powerSupply’. It also indicates which mode is the operational mode within the system. |
|
Contains the cooling capacity information of the chassis whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of ’chassis’. |
|
Contains the cooling capacity information of the fans whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of ’fan’. |
|
Contains the cooling requirement for all the manageable components of type entPhysicalClass ’module’. |
|
Contains a list of the possible cooling capacity modes and properties of the fans, whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of ’fan’. |
|
Contains the connector power ratings of FRUs. Only components with power connector rating management are listed in this table. |
cefcModulePowerConsumptionTable
|
Contains the total power consumption information for modules whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of ’module’. |
MIB Constraints
The following tale 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-56 CISCO-ENTITY-FRU-CONTROL-MIB Constraints
|
|
|
|
|
Supported values:
Write is not supported. |
|
Supported values:
- Unknown(1)—Read-only.
- Ok(2)—Read-only.
- Failed(7)—Read-only.
|
|
Supported values:
- Unknown(1)—Read-only.
- PowerUp(2)—Read-only.
- ManualReset(5)—Read-only.
|
cefcFRUPowerSupplyGroupTable
|
Not supported. |
|
Not supported. |
- cefcMaxDefaultInLinePower
|
Not supported. |
|
Not supported. Use ciscoEnvMonSuppStatusChangeNotif for redundant power supply. |
1. The entPhysicalEntry (which has module(9) as entPhysicalClass in the entPhysicalTable) has a corresponding entry in the cefcModuleTable. |
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).
CCISCO-ENTITY-SENSOR-MIB Tables and Objects
Table 3-57 lists CISCO-ENTITY-SENSOR-MIB Tables and Objects.
.
Table 3-57 CISCO-ENTITY-SENSOR-MIB Tables and Objects
|
|
|
Lists the type, scale, and present value of a sensor listed in the Entity-MIB entPhysicalTable. |
|
Lists the threshold severity, relation, and comparison value, for a sensor listed in the Entity-MIB entPhysicalTable. |
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) that are assigned to components in the Cisco CMTS routers. The OIDs in this MIB are used in the ENTITY-MIB as values for the entPhysicalTable. Each OID uniquely identifies a type of physical entry (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
The following table 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-58 CISCO-ENTITY-VENDORTYPE-OID-MIB Objects and Constraints
MIB Object (OID Assignment)
|
|
|
|
- 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 |
|
|
- 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 |
|
|
- cevFanTrayUbr10012 (1.3.6.1.4.1.9.12.3.1.6.151)
|
UBR10012 Series Fan Assembly Module |
|
|
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) |
- cevSpaHDwbdSfp (1.3.6.1.4.1.9.12.3.1.9.2.365)
|
Cisco Next Generation Wideband SPA card |
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).
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).
CISCO-ENVMON-MIB Tables and Objects
The following table lists the CISCO-ENVMON-MIB Tables and Objects.
Table 3-59 CISCO-ENVMON-MIB Tables and Objects
|
|
ciscoEnvMonVoltageStatusTable
|
Contains voltage status maintained by the environmental monitor. |
ciscoEnvMonTemperatureStatusTable
|
Contains ambient temperature status maintained by the environmental monitor. |
ciscoEnvMonFanStatusTable
|
Contains fan status maintained by the environmental monitor. |
ciscoEnvMonSupplyStatusTable
|
Contains power supply status maintained by the environmental monitor card. |
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.
The following table 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-60 CISCO-ENVMON-MIB Constraints
|
|
|
|
- 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. |
|
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. |
|
Supported values are the following:
- normal(1)—Power supply is working
- critical(3)—Power supply is failing
- notPresent(5)—Power supply is missing
|
|
Supported values are:
- unknown(1)—Missing or unknown power supply
- ac(2)—AC power supply
- dc(3)—DC power supply
|
|
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).
CISCO-FLASH-MIB Tables and Objects
The following table lists CISCO-FLASH-MIB Tables and Objects.
Table 3-61 CISCO-FLASH-MIB Tables and Objects
|
|
|
Contains Flash device properties for each initialized Flash device. Each Flash device installed in a system is detected, sized, and initialized when the system image boots up. For removable Flash devices, the device properties will be dynamically deleted and recreated as the device is removed and inserted. Note that in this case, the newly inserted device may not be the same as the earlier removed one. The ciscoFlashDeviceInitTime object is available for a management station to determine the time at which a device was initialized, and thereby detect the change of a removable device. A removable device that has not been installed will also have an entry in this table. This is to let a management station know about a removable device that has been removed. Since a removed device obviously cannot be sized and initialized, the table entry for such a device will have ciscoFlashDeviceSize equal to zero, and the following objects will have an indeterminate value: ciscoFlashDeviceMinPartitionSize, ciscoFlashDeviceMaxPartitions, ciscoFlashDevicePartitions, and ciscoFlashDeviceChipCount. ciscoFlashDeviceRemovable will be true to indicate it is removable. |
|
Contains Flash device chip properties for each initialized Flash device. This table is meant primarily for aiding error diagnosis. |
|
Contains flash device partition properties for each initialized flash partition. Whenever there is no explicit partitioning done, a single partition spanning the entire device will be assumed to exist. There will therefore always be atleast one partition on a device. |
|
Contains information for files in a Flash partition. |
ciscoFlashFileByTypeTable
|
Contains information for files on the manageable flash devices sorted by File Types. |
|
Contains Flash copy operation entries. Each entry represents a Flash copy operation (to or from Flash) that has been initiated. |
ciscoFlashPartitioningTable
|
Contains Flash partitioning operation entries. Each entry represents a Flash partitioning operation that has been initiated. |
|
Contains miscellaneous Flash operation entries. Each entry represents a Flash operation that has been initiated. |
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).
CISCO-FRAME-RELAY-MIB Tables and Objects
Table 3-62 lists CISCO-FRAME-RELAY-MIB Tables and Objects.
.
Table 3-62 CISCO-FRAME-RELAY-MIB Tables and Objects
|
|
|
Contains Frame Relay LMI information that are either supplemental to the frDlcmiTable of RFC 1315 or specific to Cisco’s implementation. |
|
Contains descriptive and statistics information that are generic to Frame Relay virtual circuits. |
|
Contains Cisco implementation specific FR circuit information. This is a Cisco extension for the frCircuitTable of RFC 1315. |
|
Contains protocols and addresses mapping information of FR virtual circuit. |
|
Contains FR SVC specific, descriptive and statistics information. |
|
Contains CISCO Frame Relay ELMI information that is specific to CISCO implementation |
|
Contains CISCO Frame Relay Neighbor ELMI information that is specific to CISCO implementation. |
|
Contains Frame Relay Fragmentation information. These are specific to Cisco’s implementation. |
|
Contains Frame Relay/Frame Relay and Frame Relay/ATM Network/Service Interworking connection information. These are specific to Cisco’s implementation. |
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).
CISCO-FTP-CLIENT-MIB Tables and Objects
Table 3-63 lists CISCO-FTP-CLIENT-MIB Tables and Objects.
.
Table 3-63 CISCO-FTP-CLIENT-MIB Tables and Objects
|
|
|
Contains FTP client requests. |
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).
CISCO-HSRP-EXT-MIB Tables and Objects
Table 3-64 lists CISCO-HSRP-EXT-MIB Tables and Objects.
.
Table 3-64 CISCO-HSRP-EXT-MIB Tables and Objects
|
|
|
Contains information about tracked interfaces per HSRP group. |
|
Contains information about secondary HSRP IP Addresses per interface and group. |
|
Contains information about standby interfaces per HSRP group. |
|
HSRP-specific configurations for each physical interface. |
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).
CISCO-HSRP-MIB Tables and Objects
Table 3-65 lists CISCO-HSRP-MIBTables and Objects.
.
Table 3-65 CISCO-HSRP-MIB Tables and Objects
|
|
|
Contains information on each HSRP group for each interface. |
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).
CISCO-IETF-ATM2-PVCTRAP-MIB Tables and Objects
Table 3-66 lists CISCO-IETF-ATM2-PVCTRAP-MIB Tables and Objects.
.
Table 3-66 CISCO-IETF-ATM2-PVCTRAP-MIB Tables and Objects
|
|
|
Contains ATM interface monitoring information not defined in the atmInterfaceConfTable from the ATM-MIB. |
atmCurrentlyFailingPVclTable
|
Indicates all VCLs for which there is an active row in the atmVclTable having an atmVclConnKind value of ‘pvc’ and an atmVclOperStatus with a value other than ‘up’. |
MIB 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).
CISCO-IETF-IP-FORWARD-MIB Tables and Objects
Table 3-67 lists CISCO-IETF-IP-FORWARD-MIB Tables and Objects.
.
Table 3-67 CISCO-IETF-IP-FORWARD-MIB Tables and Objects
|
|
|
This entity’s IP Routing table. |
|
This entity’s IP Routing table. This table has been deprecated in favor of the IP version neutral cInetCidrRouteTable. |
|
This entity’s IP Routing table. |
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).
CISCO-IETF-IP-MIB Tables and Objects
Table 3-68 lists CISCO-IETF-IP-MIB Tables and Objects.
.
Table 3-68 CISCO-IETF-IP-MIB Tables and Objects
|
|
|
Contains per-interface IPv6-specific information. |
|
Inet prefix table. |
|
Inet address table. |
|
The IP Address Translation table used for mapping from IP addresses to physical addresses. The Address Translation tables contain the IP address to ’physical’ address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. |
|
Describe IPv6 unicast and multicast scope zones. |
|
Contains generic ICMP counters. These counters may be kept per-interface and/or system-wide. |
|
Contains per-message ICMP counters. These counters may be kept per-interface and/or system-wide. |
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).
CISCO-IETF-NAT-MIB Tables and Objects
Table 3-69 lists CISCO-IETF-NAT-MIB Tables and Objects.
.
Table 3-69 CISCO-IETF-NAT-MIB Tables and Objects
|
|
|
Specifies the configuration attributes for a device supporting NAT function. |
cnatConfStaticAddrMapTable
|
Lists configuration for static NAT entries. This table has an expansion dependent relationship on the cnatConfTable. When an SNMP entity deletes a conceptual row from the cnatConfTable, then the corresponding entries are deleted from cnatConfStaticAddrMapTable. |
|
Lists dynamic NAT entries. This table has an expansion dependent relationship on the cnatConfTable. When an SNMP entity deletes a conceptual row from the cnatConfTable, then the corresponding entries are deleted from cnatConfDynAddrMapTable. |
|
Contains information regarding the interface on which NAT is enabled. |
|
Contains information about the currently active NAT BINDs. |
|
Contains information about the currently active NAPT BINDs. |
|
The (conceptual) table contains one entry for each NAT session currently active on this NAT device. |
|
The (conceptual) table containing per protocol NAT statistics. |
|
The (conceptual) table containing per address map NAT statistics. |
|
Augments the cnatInterfaceTable and provides statistics information pertaining to the specified interface. |
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-MIB Tables and Objects
Table 3-70 lists CISCO-IETF-PW-MIB Tables and Objects.
.
Table 3-70 CISCO-IETF-PW-MIB Tables and Objects
|
|
|
Contains information for connecting various emulated services to various tunnel type. |
|
Contains per-VC performance information for the current interval. |
|
Contains per-VC performance information for each interval. |
|
Contains per-VC Performance information from VC start time. |
|
Contains reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs. |
|
Contains reverse mapping of the existing VCs based on vc type and VC ID ordering. This table is typically useful for EMS ordered query of existing VCs. |
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).
CISCO-IETF-PW-MPLS-MIB Tables and Objects
Table 3-71 lists CISCO-IETF-PW-MPLS-MIB Tables and Objects.
.
Table 3-71 CISCO-IETF-PW-MPLS-MIB Tables and Objects
|
|
|
Specifies information for VC to be carried over MPLS PSN. |
|
Associates VCs using MPLS PSN with the outbound MPLS tunnels (i.e. toward the PSN) or the physical interface in case of VC only. |
|
Associates VCs using MPLS PSN with the inbound MPLS tunnels (i.e. for packets coming from the PSN), if such association is desired (mainly for security reasons). |
|
Maps an inbound/outbound Tunnel to a VC in non- TE applications. |
|
Maps an inbound/outbound Tunnel to a VC in MPLS-TE applications. |
MIB Constraints
There are no constraints on this MIB.
CISCO-IETF-ISIS-MIB
The CISCO-IETF-ISIS MIB describes a management information base for the IS-IS Routing protocol, as described in ISO 10589, when it is used to construct routing tables for IP networks, as described in RFC 1195. This MIB is entirely based upon the IETF draft draft-ietf-isis-wg-mib-16.
Note This CISCO-IETF-ISIS MIB is not supported on the Cisco uBR10012 router in the following Cisco IOS Releases:
- Cisco IOS Release 12.2(33)SCC5
- Cisco IOS Release 12.2(33)SCE4
- Cisco IOS Release 12.2(33)SCF2
MIB Objects
Table 3-72 CISCO-IETF-ISIS-MIB Tables and Objects
|
|
|
Lists the set of manual area addresses configured on this Intermediate System. |
|
List the union of the sets of area addresses reported in all Level 1 LSPs with fragment number zero generated by this Intermediate System, or received from other Intermediate Systems which are reachable via Level 1 routing. |
|
Contains the manually configured set of protocols supported by this Intermediate System. |
|
Contains the set of IP summary addresses to use in forming summary TLVs originated by this Intermediate System. |
|
Provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when ciiSysL2toL1Leaking is enabled. |
|
List the set of hostnames and router ID. |
|
List the level specific information about the System. |
|
List the circuits used by this Intermediate System. |
|
Provides level specific information about circuits used by IS-IS |
|
Lists the aystem wide counters for this Intermediate System. |
|
Lists the circuit specific counters for this Intermediate System. |
|
Provides information about IS-IS protocol traffic at one level on one circuit in one direction |
|
Lists the adjacencies to Intermediate Systems. |
|
Contains the set of Area Addresses of neighboring Intermediate Systems as reported in received IIH PDUs. |
|
Contains the set of IP Addresses of neighboring Intermediate Systems as reported in received IIH PDUs. |
|
Contains the set of protocols supported by neighboring Intermediate Systems as reported in received IIH PDUs. |
|
Contains reachable addresses to NSAPs or address prefixes. |
|
Contains IP reachable addresses to networks, subnetworks or hosts either manually configured or learned from another protocol. |
|
Contains LSP Headers. |
|
Provides the contents of each LSP. |
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).
CISCO-IMAGE-MIB Tables and Objects
Table 3-73 lists CISCO-IMAGE-MIB Tables and Objects.
.
Table 3-73 CISCO-IMAGE-MIB Tables and Objects
|
|
|
Provides content describing the executing IOS image. |
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).
CISCO-IP-ENCRYPTION-MIB Tables and Objects
Table 3-74 lists CISCO-IP-ENCRYPTION-MIB Tables and Objects.
.
Table 3-74 CISCO-IP-ENCRYPTION-MIB Tables and Objects
|
|
|
Describes status of all encryption engines present within the router. |
|
Describes all encrypted IP traffic created by the router, between the protected entity (cieProtectedAddr) and the unprotected entity (cieUnprotectedAddr). Each entry in this table describes a virtual encrypted IP tunnel. |
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).
CISCO-IPMROUTE-MIB Tables and Objects
Table 3-75 lists CISCO-IPMROUTE-MIB Tables and Objects.
.
Table 3-75 CISCO-IPMROUTE-MIB Tables and Objects
|
|
|
The (conceptual) table contains multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router. This table is augmented to the ipMRouteTable. |
ciscoIpMRouteNextHopTable
|
The (conceptual) table contains information on the next hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next hops on outgoing interfaces for particular sources sending to a particular multicast group address. |
ciscoIpMRouteHeartBeatTable
|
The (conceptual) table listing sets of IP Multicast heartbeat parameters. If no IP Multicast heartbeat is configured, this table would be empty. |
ciscoIpMRouteInterfaceTable
|
The (conceptual) table contains multicast routing information specific to interfaces. This table augments the ipMRouteInterfaceTable. |
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).
CISCO-IP-STAT-MIB Tables and Objects
Table 3-76 lists CISCO-IP-STAT-MIB Tables and Objects.
.
Table 3-76 CISCO-IP-STAT-MIB Tables and Objects
|
|
|
Contains entries sorted by the precedence of IP packets. The table is created and deleted via ip accounting command line interface. |
|
A table is created and deleted via ip accounting command line interface. |
|
Contains free space available to store new MAC address information. |
|
Contains additional objects for the cipPrecedenceTable. |
|
Contains additional objects for the cipMacTable. |
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-77 lists CISCO-IP-TAP-MIB Tables and Objects.
.
Table 3-77 CISCO-IP-TAP-MIB Tables and Objects.
|
|
|
The Intercept Stream IP Table lists the IPv4 and IPv6 streams to be intercepted. The same data stream may be required by multiple taps, and one might assume that often the intercepted stream is a small subset of the traffic that could be intercepted. This essentially provides options for packet selection, only some of which might be used. For example, if all traffic to or from a given interface is to be intercepted, one would configure an entry which lists the interface, and wild-card everything else. If all traffic to or from a given IP Address is to be intercepted, one would configure two such entries listing the IP Address as source and destination respectively, and wild-card everything else. If a particular voice on a teleconference is to be intercepted, on the other hand, one would extract the multicast (destination) IP address, the source IP Address, the protocol (UDP), and the source and destination ports from the call control exchange and list all necessary information. The first index indicates which Mediation Device the intercepted traffic will be diverted to. The second index permits multiple classifiers to be used together, such as having an IP address as source or destination. The value of the second index is that of the stream’s counter entry in the cTap2StreamTable. Entries are added to this table via citapStreamStatus in accordance with the RowStatus convention. |
|
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).
CISCO-IPSEC-FLOW-MONITOR-MIB Tables and Objects
Table 3-78 lists CISCO-IPSEC-FLOW-MONITOR-MIB Tables and Objects.
.
Table 3-78 CISCO-IPSEC-FLOW-MONITOR-MIB Tables and Objects
|
|
|
There is one entry in this table for each IPsec Phase-1 IKE peer association which is currently associated with an active IPsec Phase-1 Tunnel. The IPsec Phase-1 IKE Tunnel associated with this IPsec Phase-1 IKE peer association may or may not be currently active. |
|
There is one entry in this table for each active IPsec Phase-1 IKE Tunnel. |
|
There is one entry in this table for each active IPsec Phase-2 Tunnel. |
|
Each entry is related to a specific gateway which is identified by ’cmgwIndex’. |
|
There is one entry in this table for each active IPsec Phase-2 Tunnel. |
|
Contains an entry for each active endpoint associated with an IPsec Phase-2 Tunnel. |
|
Contains an entry for each active and expiring security association. |
|
Each entry is related to a specific gateway which is identified by ’cmgwIndex’ |
|
Implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object. |
|
Implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object. |
|
Implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecHistTableSize object. |
|
Implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object. |
|
Implemented as a sliding window in which only the last n entries are maintained. The maximum number of entries is specified by the cipSecFailTableSize object. |
MIB Constraints
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).
CISCO-IPSEC-MIB Tables and Objects
Table 3-79 lists CISCO-IPSEC-MIB Tables and Objects.
.
Table 3-79 CISCO-IPSEC-MIB Tables and Objects
|
|
|
Contains the list of all ISAKMP policy entries configured by the operator. |
cipsStaticCryptomapSetTable
|
Contains the list of all cryptomap sets that are fully specified and are not wild-carded. The operator may include different types of cryptomaps in such a set - manual, CET, ISAKMP or dynamic. |
cipsDynamicCryptomapSetTable
|
Contains a list of all dynamic cryptomaps that use IKE, defined on the managed entity. |
|
Contains the member cryptomaps of the cryptomap sets that are configured on the managed entity. |
|
Contains the binding of cryptomap sets to the interfaces of the managed entity. |
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).
CISCO-IPSEC-POLICY-MAP-MIB Tables and Objects
Table 3-80 lists CISCO-IPSEC-POLICY-MAP-MIB Tables and Objects.
.
Table 3-80 CISCO-IPSEC-POLICY-MAP-MIB Tables and Objects
|
|
|
The IPSec Phase-1 Internet Key Exchange Tunnel to Policy Mapping Table. There is one entry in this table for each active IPSec Phase-1 Tunnel. |
|
The IPSec Phase-2 Tunnel to Policy Mapping Table. There is one entry in this table for each active IPSec Phase-2 Tunnel. |
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).
CISCO-ISDN-MIB Tables and Objects
Table 3-81 lists CISCO-ISDN-MIB Tables and Objects.
.
Table 3-81 CISCO-ISDN-MIB Tables and Objects
|
|
|
Contains a list of neighbors from which the router will accept calls or to which it will place them. |
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).
CISCO-LEC-DATA-VCC-MIB Tables and Objects
Table 3-82 lists CISCO-LEC-DATA-VCC-MIB Tables and Objects.
.
Table 3-82 CISCO-LEC-DATA-VCC-MIB Tables and Objects
|
|
|
Contain entries for all VCCs used as LAN-Emulation Data Direct VCCs. |
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).
CISCO-LEC-EXT-MIB Tables and Objects
Table 3-83 lists CISCO-LEC-EXT-MIB Tables and Objects.
.
Table 3-83 CISCO-LEC-EXT-MIB Tables and Objects
|
|
|
An extension to the lecConfig table in the LAN-EMULATION-CLIENT-MIB that identifies which VLAN a LEC is associated with. |
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).
CISCO-LECS-MIB Tables and Objects
Table 3-84 lists CISCO-LECS-MIB Tables and Objects.
.
Table 3-84 CISCO-LECS-MIB Tables and Objects
|
|
|
The (conceptual) table contains the interface specific information of the LECS on a particular device and its associated statistics for that interface. |
|
A (conceptual) table of ATM addresses which are listened to by LECSs on this device. |
lecsConfigDirectConnTable
|
This (conceptual) table allows a manager to view what LE clients have established configure direct connections to the LECS over the designated interface. |
|
A (conceptual) table of the configuration tables in existence on the device. Note that an entry must exist in this table before it can be used in the lecsTable, lecsElanConfigTable, lecsMacConfigTable or lecsAtmAddrConfigTable. |
|
A (conceptual) configuration table that represents the names of the ELANs known to a LECS and their corresponding LES ATM addresses. |
|
A (conceptual) table utilized by a LECS to map a registered MAC address of a LEC to an ELAN name. This table is used be the LECS to assign a LEC to an ELAN. It is, however, not mandatory for all configurable LECs to be in this table as they may opt to use the lecsAtmAddrConfigTable instead or perhaps rely on the default ELAN set in the lecsConfigTblTable. Also note that a LES may opt to use this table to determine authorization of a LEC to join an ELAN. |
|
This (conceptual) table is used by the LECS to map between an ATM address of a LEC and ELAN name. |
|
A table of LESs servicing an ELAN. |
|
A (conceptual) table utilized by a LECS to map a registered Route Descriptor of a LEC to an ELAN name. This table is used by the LECS to assign a LEC to an ELAN. It is, however, not mandatory for all configurable LECs to be in this table as they may opt to use the lecsAtmAddrConfigTable or lecsMacConfigTable instead or perhaps rely on the default ELAN set in the lecsConfigTblTable. Also note that a LES may opt to use this table to determine authorization of a LEC to join an ELAN. |
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).
CISCO-LES-MIB Tables and Objects
Table 3-85 lists CISCO-LES-MIB Tables and Objects.
.
Table 3-85 CISCO-LES-MIB Tables and Objects
|
|
|
A (conceptual) table contains all instances of LESs on this device. |
|
A (conceptual) table of statistics associated with LES instances on the device. |
|
A (conceptual) table listing the clients associated with a LES. Note that the local or network management will not create or destroy rows in this table but may only inspect what LECs are currently joined with the LES. |
|
A (conceptual) table of MAC addresses registered with the LES by its clients. |
|
A (conceptual) table of Route Descriptors registered with the LES by its clients. |
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).
CISCO-MEMORY-POOL-MIB Tables and Objects
Table 3-86 lists CISCO-MEMORY-POOL-MIB Tables and Objects.
.
Table 3-86 CISCO-MEMORY-POOL-MIB Tables and Objects
|
|
|
Contains memory pool monitoring entries. |
ciscoMemoryPoolUtilizationTable
|
Contains memory pool utilization entries. Each of the objects provides a general idea of how much of the memory pool has been used over a given period of time. It is determined as a weighted decaying average. |
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).
CISCO-NBAR-PROTOCOL-DISCOVERY-MIB Tables and Objects
Table 3-87 lists CISCO-NBAR-PROTOCOL-DISCOVERY-MIB Tables and Objects.
.
Table 3-87 CISCO-NBAR-PROTOCOL-DISCOVERY-MIB Tables and Objects
|
|
cnpdSupportedProtocolsTable
|
Lists all the protocols and applications which NBAR is currently capable of recognizing. |
|
It is used to enable and disable Protocol Discovery on an interface. |
|
Contains all the statistics available for all the protocols/applications currently recognized by NBAR Protocol Discovery for a particular interface. In the event of an overflow, the 32 bit counters are not valid. There is no overflow support. |
|
It is used to configure cnpdTopNStatsTable’s. |
|
Describes an ordered list of protocols. |
|
Allows the management station to create thresholds for the purpose of sending notifications if breached, and creating a history of breached thresholds. |
cnpdThresholdHistoryTable
|
Notifications are unreliable so this table provides a history of the last 5000 threshold breached events. A notification can be traced back to its cnpdThresholdHistoryEntry. |
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).
CISCO-NDE-MIB Tables and Objects
Table 3-88 lists CISCO-NDE-MIB Tables and Objects.
.
Table 3-88 CISCO-NDE-MIB Tables and Objects
|
|
|
A control table to configure the NDE collectors. The maximum number of entries is limited by cndeMaxCollectors. The agent sends the NDE packets to each address configured in this table. |
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).
CISCO-NTP-MIB Tables and Objects
Table 3-89 lists CISCO-NTP-MIB Tables and Objects.
.
Table 3-89 CISCO-NTP-MIB Tables and Objects
|
|
|
Provides information on the peers with which the local NTP server has associations. The peers are also NTP servers but running on different hosts. |
|
Contains NTP state variables used by the NTP clock filter and selection algorithms. This table depicts a shift register. Each stage in the shift register is a 3-tuple consisting of the measured clock offset, measured clock delay and measured clock dispersion associated with a single observation. An important factor affecting the accuracy and reliability of time distribution is the complex of algorithms used to reduce the effect of statistical errors and falsetickers due to failure of various subnet components, reference sources or propagation media. The NTP clock-filter and selection algorithms are designed to do exactly this. The objects in the filter register table below are used by these algorthims to minimize the error in the calculated time. |
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).
Table 3-90 lists CISCO-PIM-MIB Tables and Objects.
.
Table 3-90 CISCO-PIM-MIB Tables and Objects
|
|
cpimInvalidJoinPruneMsgsRcvd
|
A count of the number of invalid PIM Join/Prune messages received by this device. A PIM Join/Prune message is termed invalid if the RP specified in the packet is not the RP for the group in question. |
|
The type of the last invalid message that was received by this device. |
|
Represents the type of address stored in cpimLastErrorOrigin. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
This object represents the Network Layer Address of the source that originated the last invalid packet. The type of address stored depends on the value in cpimLastErrorOriginType. The value of this object represents the Network Layer Address of the Designated Router (DR) whenever the value of cpimLastErrorGroup is a zero-length address, for eg. when encapsulated IP header is malformed. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
Represents the type of address stored in cpimLastErrorGroup. The value of this object is unknown(0) if there is a problem in the packet received from the DR. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
The IP multicast group address to which the last invalid packet was addressed. The type of address stored depends on the value in cpimLastErrorGroupType. The value of this object is a zero-length InetAddress if there is a problem in the packet received from the DR, for eg. a malformed encapsulated IP header. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
Represents the type of address stored in cpimLastErrorRP. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
The address of the RP, as per the last invalid packet. The type of address stored depends on the value in cpimLastErrorRPType. The value of this object is irrelevant if the value of cpimLastErrorType is none(1). |
|
Describes the operation that resulted in generation of cpimRPMappingChange notification. |
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).
CISCO-PING-MIB Tables and Objects
Table 3-91 lists CISCO-PING-MIB Tables and Objects.
.
Table 3-91 CISCO-PING-MIB Tables and Objects
|
|
|
Contains ping request entries. |
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).
CISCO-PPPOE-MIB Tables and Objects
Table 3-92 lists CISCO-PPPOE-MIB Tables and Objects.
.
Table 3-92 CISCO-PPPOE-MIB Tables and Objects
|
|
|
Contains the PPPoE protocol related configuration for the VCLs(ATM Interface Virtual Channel Link). |
|
Contains configuration and statistics about the number of PPPoE sessions on a list of VCLs(ATM Interface Virtual Channel Link). |
cPppoeSessionsPerInterfaceTable
|
A list of interfaces’ PPPoE session information. |
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).
CISCO-PROCESS-MIB Tables and Objects
Table 3-93 lists CISCO-PROCESS-MIB Tables and Objects.
.
Table 3-93 CISCO-PROCESS-MIB Tables and Objects
|
|
|
Contains overall CPU statistics. |
|
Contains generic information on all active processes on this device. |
|
Contains information that may or may not be available on all cisco devices. It contains additional objects for the more general cpmProcessTable. This object is deprecated by cpmProcessExtRevTable. |
|
Contains information that may or may not be available on all cisco devices. It contains additional objects for the more general cpmProcessTable. This object deprecates cpmProcessExtTable. |
|
Contains the information about the thresholding values for CPU, configured by the user. |
|
A list of CPU utilization history entries. |
|
Contains generic information about POSIX threads in the device. |
|
Contains information about virtual processes in a virtual machine. |
cpmCPUProcessHistoryTable
|
Contains CPU utilization of processes which crossed the cpmCPUHistoryThreshold. |
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-94 lists the constraints that the router places on CISCO-PROCESS-MIB.
Table 3-94 Cisco CMTS Router CISCO-PROCESS-MIB
|
|
|
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-95 lists the relevant OIDs for the Cisco CMTS routers.
Table 3-95 Cisco CMTS Router OIDs from CISCO-PRODUCTS-MIB
|
|
|
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).
CISCO-QUEUE-MIB Tables and Objects
Table 3-96 lists CISCO-QUEUE-MIB Tables and Objects.
.
Table 3-96 CISCO-QUEUE-MIB Tables and Objects
|
|
|
Contains objects that describe the queues on a Cisco Interface. An interface queue is modeled as a collection of one or more secondary queues that feed into a device’s hardware queue. The hardware queue has a maximum depth set by the MCI tx-queue-limit command or equivalent. The secondary queues (also known as the ’hold queue’) have maximum depths set by the hold-queue command or equivalent. This table parallels the ifTable, and indicates the type of queuing in use on the interface, number of queues, and similar parameters. |
|
Contains statistical objects that for the sub-queues of a Cisco Interface. |
|
Describes the rotation of Custom Queuing on an Interface. |
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).
CISCO-RMON-SAMPLING-MIB Tables and Objects
Table 3-97 lists CISCO-RMON-SAMPLING-MIB Tables and Objects.
.
Table 3-97 CISCO-RMON-SAMPLING-MIB Tables and Objects
|
|
|
Extends the port copy capability found in the SMON MIB portCopyTable. This table is intended to augment every portCopyEntry, but not all features provided may be available on all RMON platforms. In such a case, a particular MIB object will be implemented with read-only access. |
|
Controls the configuration of RMON collection based on statistical sampling techniques, for each monitored interface on the RMON probe. It is a SPARSE-AUGMENTS of the ifEntry found in the IF-MIB module. An entry is created in this table at the same time the augmented ifEntry is created (usually at system startup time), for each interface which can be monitored by the RMON agent. An associated entry in the SMON MIB dataSourceCapsTable is also created for each RMON-capable interface at the same time. An RMON collection is associated with a particular interface if the control table dataSource OBJECT IDENTIFIER is of the form ’ifIndex.I’, and ’I’ is the same value as the ifIndex value for the ifEntry and rmonSampleConfigEntry. |
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-RTTMON-MIB Tables and Objects
Table 3-98 lists CISCO-RTTMON-MIB Tables and Objects.
.
Table 3-98 CISCO-RTTMON-MIB Tables and Objects
|
|
rttMonApplSupportedRttTypesTable
|
Contains the supported Rtt Monitor Types. See the RttMonRttType textual convention for the definition of each type. |
rttMonApplSupportedProtocolsTable
|
Contains the supported Rtt Monitor Protocols. See the RttMonProtocol textual convention for the definition of each protocol. |
rttMonApplPreConfigedTable
|
Contains the previously configured Script Names and File IO targets. These Script Names and File IO targets are installed via a different mechanism than this application, and are specific to each platform. |
|
Contains the definitions for key-strings that will be used in authenticating RTR Control Protocol. |
|
The RTT administration control is in multiple tables. This first table, is used to create a conceptual RTT control row. The following tables contain objects which configure scheduling, information gathering, and notification/trigger generation. All of these tables will create the same conceptual RTT control row as this table using this tables’ index as their own index. This table is limited in size by the agent implementation. The object rttMonApplNumCtrlAdminEntry will reflect this tables maximum number of entries. |
|
Contains Round Trip Time (RTT) specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object. |
|
Contains Round Trip Time (RTT) monitoring ’fileIO’ specific definitions. When the RttMonRttType is not ’fileIO’ this table is not valid. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object. |
|
Contains Round Trip Time (RTT) monitoring ’script’ specific definitions. When the RttMonRttType is not ’script’ this table is not valid. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object. |
|
Contains Round Trip Time (RTT) monitoring scheduling specific definitions. This table is controlled via the rttMonCtrlAdminTable. Entries in this table are created via the rttMonCtrlAdminStatus object. |
|
Contains Round Trip Time (RTT) monitoring Notification and Trigger definitions. All Notification/Reactions are applied to all RTT End-to-End operations. Thus, they do not apply to hops along a path to the target, when RttMonRttType is ’pathEcho’. The format and content of SNA NMVT’s are not defined within this module. It can be noted, however, that there are Alert NMVT’s, and traps which are sent when an abnormal condition occurs, i.e. when one of rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred or rttMonCtrlOperOverThresholdOccurred are changed to true, and Resolution NMVT’s, and Resolution traps which are sent when that condition clears, i.e. when one of rttMonCtrlOperConnectionLostOccurred, rttMonCtrlOperTimeoutOccurred or rttMonCtrlOperOverThresholdOccurred is changed back to false. When rttMonReactAdminActionType is set to one of the following: - triggerOnly - trapAndTrigger - nmvtAndTrigger - trapNmvtAndTrigger The corresponding rows in the rttMonReactTriggerAdminTable defined via the rttMonCtrlAdminIndex will become active. This table augments the rttMonCtrlAdminTable. |
rttMonStatisticsAdminTable
|
Contains Round Trip Time (RTT) monitoring statistics definitions. The definitions in this table control what and how many entries will be placed into the rttMonStatsCaptureTable. The statistics capture table is a rollover table. When the rttMonStatisticsAdminNumHourGroups index value exceeds its value defined in this table, the oldest corresponding group will be deleted and will be replaced with the new group. All other indices will only fill to there maximum size. NOTE: The maximum size of this table is defined to be the product of the rttMonCtrlAdminIndex times rttMonStatisticsAdminNumHourGroups times rttMonStatisticsAdminNumPaths times rttMonStatisticsAdminNumHops times rttMonStatisticsAdminNumDistBuckets. NOTE WELL: Each of the ’Num’ objects values in this have a special behavior. When one of the objects is set to a value larger than the Rtt application can support the set will succeed, but the resultant value will be set to the applications maximum value. The setting management station must reread this object to verify the actual value. This table augments the rttMonCtrlAdminTable. |
|
Contains Round Trip Time (RTT) monitoring history definitions. The definitions in this table control what and how many entries will be placed into the rttMonHistoryCollectionTable. The history collection table is a rollover table. When the rttMonHistoryAdminNumLives index value exceeds its value defined in this table, the oldest corresponding ’lives’ group will be deleted and will be replaced with the new ’lives’ group. All other indices will only fill to their maximum size. NOTE: The maximum size of this table is defined to be the product of the rttMonCtrlAdminIndex times rttMonHistoryAdminNumLives times rttMonHistoryAdminNumBuckets times rttMonHistoryAdminNumSamples. NOTE WELL: Each of the ’Num’ objects values in this have a special behavior. When one of the objects is set to a value larger than the Rtt application can support the set will succeed, but the resultant value will be set to the applications maximum value. The setting management station must reread this object to verify the actual value. NOTE: this table is not applicable to http and jitter probes |
|
Contains the Operational values for the probe, and the conceptual RTT control row. This table augments the rttMonCtrlAdminTable. |
|
Contains the status of latest RTT operation. When the RttMonRttType is ’pathEcho’, operations performed to the hops along the path will be recorded in this table. This table augments the RTT definition table, rttMonCtrlAdminTable. |
rttMonLatestHTTPOperTable
|
Contains the status of latest HTTP RTT operation. |
rttMonLatestJitterOperTable
|
Containsthe status of latest Jitter operation. |
rttMonReactTriggerAdminTable
|
Contains the list of conceptual RTT control rows that will start to collect data when a reaction condition is violated and when rttMonReactAdminActionType is set to one of the following: - triggerOnly - trapAndTrigger - nmvtAndTrigger - trapNmvtAndTrigger or when a reaction condition is violated and when any of the row in rttMonReactTable has rttMonReactActionType as one of the following: - triggerOnly - trapAndTrigger The goal of this table is to define one or more additional conceptual RTT control rows that will become active and start to collect additional history and statistics (depending on the rows configuration values), when a problem has been detected. If the conceptual RTT control row is undefined, and a trigger occurs, no action will take place. If the conceptual RTT control row is scheduled to start at a later time, triggering that row will have no effect. If the conceptual RTT control row is currently active, triggering that row will have no effect on that row, but the rttMonReactTriggerOperState object will transition to ’active’. An entry in this table can only be triggered when it is not currently in a triggered state. The object rttMonReactTriggerOperState will reflect the state of each entry in this table. |
rttMonReactTriggerOperTable
|
Contains the operational state of each entry in the rttMonReactTriggerAdminTable. This table augments the RTT trigger definition table, rttMonReactTriggerAdminTable. |
|
Contains the hop addresses in a Loose Source Routing path. Response times are computed along the specified path using ping. This maximum table size is limited by the size of the maximum number of hop addresses that can fit in an IP header, which is 8. The object rttMonEchoPathAdminEntry will reflect this tables maximum number of entries. This table is coupled with rttMonCtrlAdminStatus. |
rttMonGrpScheduleAdminTable
|
Contains Round Trip Time (RTT) monitoring group scheduling specific definitions. This table is used to create a conceptual group scheduling control row. The entries in this control row contain objects used to define group schedule configuration parameters. The objects of this table will be used to schedule a group of probes identified by the conceptual rows of the rttMonCtrlAdminTable. |
|
Contains auto SAA L3 MPLS VPN definitions. The Auto SAA L3 MPLS VPN administration control is in multiple tables. This first table, is used to create a conceptual Auto SAA L3 MPLS VPN control row. The following tables contain objects which used in type specific configurations, scheduling and reaction configurations. All of these tables will create the same conceptual control row as this table using this table’s index as their own index. In order to a row in this table to become active the following objects must be defined. rttMplsVpnMonCtrlRttType, rttMplsVpnMonCtrlVrfName and rttMplsVpnMonSchedulePeriod. |
|
Contains Auto SAA L3 MPLS VPN configured RTT operation specific definitions. This table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object. |
rttMplsVpnMonScheduleTable
|
Contains auto SAA L3 MPLS VPN monitoring scheduling specific definitions. This table is controlled via the rttMplsVpnMonCtrlTable. Entries in this table are created via the rttMplsVpnMonCtrlStatus object. |
|
Contains auto SAA L3 MPLS VPN Notification definitions. This table augments the rttMplsVpnMonCtrlTable. |
|
Contains the reaction configurations. Each conceptual row in rttMonReactTable corresponds to a reaction configured for the probe defined in rttMonCtrlAdminTable. For each reaction configured for a probe there is an entry in the table. Each Probe can have multiple reactions and hence there can be multiple rows for a particular probe. This table is coupled with rttMonCtrlAdminTable. |
|
Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. Each ’group’ contains a series of ’path(s)’, each ’path’ contains a series of ’hop(s)’, each ’hop’ contains a series of ’statistics distribution bucket(s)’. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group(s) is kept in the table until the table contains rttMonStatisticsAdminNumHourGroups groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonStatsCaptureStartTimeIndex object. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to ’inactive’, the corresponding current hourly group in this table is ’frozen’, and a new hourly group is created when activity is resumed. If the activity for a conceptual RTT control row ceases because the rttMonCtrlOperState object transitions to ’pending’ this whole table will be cleared and reset to its initial state. When the RttMonRttType is ’pathEcho’, the path exploration RTT requests’ statistics will not be accumulated in this table. NOTE: When the RttMonRttType is ’pathEcho’, a source to target rttMonStatsCapturePathIndex path will be created for each rttMonStatsCaptureStartTimeIndex to hold all errors that occur when a specific path had not been found or connection has not be setup. Using this rttMonStatsCaptureTable, a managing application can retrieve summarized data from accurately measured periods, which is synchronized across multiple conceptual RTT control rows. With the new hourly group creation being performed on a 60 minute period, the managing station has plenty of time to collect the data, and need not be concerned with the vagaries of network delays and lost PDU’s when trying to get matching data. Also, the managing station can spread the data gathering over a longer period, which removes the need for a flood of get requests in a short period which otherwise would occur. |
|
Contains the exact behavior as the rttMonStatsCaptureTable, except it does not keep statistical distribution information. For a complete table description see the rttMonStatsCaptureTable object. |
|
Contains the exact same behavior as the rttMonStatsCaptureTable, except it only keeps 60 minute group values. For a complete table description see the rttMonStatsCaptureTable object. |
|
Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table can only store a maximum of 2 hours of data. |
|
Contains summarized information of the results for a conceptual RTT control row. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. The operation of this table is same as that of rttMonStatsCaptureTable, except that this table will store 2 hours of data. |
|
The Auto SAA L3 MPLS VPN LPD Group Database. The LPD Group statistics table contains summarized performance statistics for the LPD group. LPD Group - The set of ’single probes’ which are subset of the ’lspGroup’ probe traversing set of paths between two PE end points are grouped together and called as the LPD group. The LPD group will be uniquely referenced by the LPD Group ID. A rolling accumulated history of this information is maintained in a series of hourly ’group(s)’. Each conceptual statistics row has a current hourly group, into which RTT results are accumulated. At the end of each hour a new hourly group is created which then becomes current. The counters and accumulators in the new group are initialized to zero. The previous group(s) is kept in the table until the table contains rttMplsVpnMonTypeLpdStatHours groups for the conceptual statistics row; at this point, the oldest group is discarded and is replaced by the newly created one. The hourly group is uniquely identified by the rttMonLpdGrpStatsStartTimeIndex object. |
rttMonHistoryCollectionTable
|
Contains a point by point rolling history of the most recent RTT operations for each conceptual RTT control row. The rolling history of this information is maintained in a series of ’live(s)’, each containing a series of ’bucket(s)’, each ’bucket’ contains a series of ’sample(s)’. Each conceptual history row can have lives. A life is defined by the rttMonCtrlOperRttLife object. A new life will be created when rttMonCtrlOperState transitions ’active’. When the number of lives become greater than rttMonHistoryAdminNumLives the oldest life will be discarded and a new life will be created by incrementing the index. The path exploration RTT operation will be kept as an entry in this table. |
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).
CISCO-SLB-EXT-MIB Tables and Objects
Table 3-99 lists CISCO-SLB-EXT-MIB Tables and Objects.
.
Table 3-99 CISCO-SLB-EXT-MIB Tables and Objects
|
|
|
Contains global SLB statistics for all local SLB entities. It contains addition information to the slbStatsTable. |
|
Contains server farms, each of which is a group of real servers to be used by SLB for load balancing. It contains additional configurations to the slbSeverFarmTable. |
|
Contains HTTP redirect servers. Entry attributes may be modified regardless of the value of cslbxRedirectSvrState. |
cslbxServerFarmProbeTable
|
Contains probes in the server farms. |
cslbxSfarmHttpReturnCodeTable
|
Contains the objects that are related to HTTP return code checking in a server farm. |
cslbxServerFarmStatsTable
|
Contains the statistics of server farms |
|
Contains IP NAT pools. |
|
Contains Sticky Groups. |
|
Contains existing sticky entries. Sticky entries allow related connections to be sent to the same real server on a per client basis. This table supports the Content Switching Module (CSM) feature which is not supported by the slbStickyObjectTable in the CISCO-SLB-MIB. |
|
Contains additional objects related to sticky group. |
|
Contains SLB map groups. A SLB map group contains a list of matching criteria. |
|
A table of HTTP field and regular expressions. |
|
Contains rules associating ReturnCode maps and intervals of HTTP return codes with actions to perform when particular HTTP return codes are seen in the data stream. |
|
A table of load balancing policies. |
|
Contains virtual servers. It contains additional configurations for the slbVirtualServerTable. |
|
Contains the function to apply the policies to the virtual servers. Using different policies, the SLB can direct traffic matching different patterns to different server farms. |
|
Contains the configuration of VLANs configured on the SLB. |
|
Contains the configuration of alias IP addresses on the SLB device. The SLB device will respond to an ARP request for alias IP addresses if the ARP request arrives on the configured VLAN. A given VLAN may be associated with multiple alias IP addresses. |
|
Contains the configuration of static routes on the SLB device. |
|
A table of Fault Tolerance settings. |
|
Contains XML interface settings. |
|
ContainsExtended Connections being load-balanced by SLB. This table supports the Content Switching Module (CSM) feature which is not supported by the slbConnectionTable in the CISCO-SLB-MIB. |
|
Contains Owners of the load balancing objects. |
|
Contains Script files to be downloaded into a particular SLB device. The content of these text files can be excuted by the SLB device to provide additional health check functionality. |
|
Contains Script tasks to be executed by the SLB device when it is online. The scripts from the cslbxScriptFileTable are referenced in this table by the named labels. |
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).
CISCO-SLB-MIB Tables and Objects
Table 3-100 lists CISCO-SLB-MIB Tables and Objects.
.
Table 3-100 CISCO-SLB-MIB Tables and Objects
|
|
|
Contains SLB statistics for all local SLB entities. |
|
A table of server farms, each of which is a group of real servers to be used by SLB for load balancing. Columnar objects can be modified when the row is ’active’. Rows can be created and destroyed. Entries are added to this table via slbServerFarmRowStatus in accordance with the RowStatus convention. |
|
Columnar objects can be modified when the row is ’active’. Rows can be created and destroyed. Entries are added to this table via slbRealRowStatus in accordance with the RowStatus convention. |
|
Columnar objects can be modified when the row is ’active’. Rows can be created and destroyed. Entries are added to this table via slbVirtualRowStatus in accordance with the RowStatus convention. |
|
Contains information on virtual servers. |
|
Contains the IP Addresses configured for virtual servers. A virtual server can have more than one IP Address configured in it. |
|
Contains connections being load-balanced by SLB. |
|
Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbVirtualClientRowStatus in accordance with the RowStatus convention. |
|
Sticky objects allow related connections to be sent to the same real server on a per client basis. Sticky objects are useful for FTP and SSL connections. Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbStickyObjectRowStatus in accordance with the RowStatus convention. |
|
Contains password values which a local Server Load Balancing Manager uses so that it can communicate with remote DFP agents. Entries are added to this table via slbDfpPasswordRowStatus in accordance with the RowStatus convention. Columnar objects can be modified when in row is ’active’. Rows can be created and destroyed. |
|
Contains remote DFP agents with which the local DFP managers communicate. Rows can be created and destroyed. Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbDfpAgentRowStatus in accordance with the RowStatus convention. |
|
Contains information about Real Servers obtained through communications between local DFP manager and remote DFP agents. Rows can be created and destroyed. Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbDfpRowStatus in accordance with the RowStatus convention. |
|
Contains information about the Server Application State Protocol (SASP). There is only one entry for each load balancer. This entry is created by the load balancer during initialization. |
|
Contains information about the SASP Agents. Rows can be created and destroyed. Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbSaspAgentRowStatus. A SASP Agent is an application or device that is responsible for aggregating information regarding the performance of a SASP Member. The information is used to calculate a weight that is reported to the load balancer. |
|
Contains information about the SASP Groups. Rows can be created and destroyed. Entries are added to this table via slbSaspGroupRowStatus. A SASP Group is a logical entity used within the SASP implementation to group SASP Members that are equivalent in function. |
|
Contains information about the SASP Members. Rows can be created and destroyed. Columnar objects can be modified when the row is ’active’. Entries are added to this table via slbSaspMemberRowStatus. A SASP Member is an entity configured on the load balancer to help distribute the load for one or more services. |
|
Contains information about the Server Application State Protocol Statistics. Rows are created and destroyed when an entry for the slbSaspAgentTable is created or destroy via the slbSaspAgentRowStatus. |
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).
CISCO-SNAPSHOT-MIB Tables and Objects
Table 3-101 lists CISCO-SNAPSHOT-MIB Tables and Objects.
.
Table 3-101 CISCO-SNAPSHOT-MIB Tables and Objects
|
|
ciscoSnapshotInterfaceTable
|
Contains list of Snapshot Routing configuration entries. |
ciscoSnapshotActivityTable
|
Contains list of snapshot routing activity entries. |
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).
CISCO-SRP-MIB Tables and Objects
Table 3-102 lists CISCO-SRP-MIB Tables and Objects.
.
Table 3-102 CISCO-SRP-MIB Tables and Objects
|
|
|
Contains SRP interface. |
|
Contains information about the sides of SRP interfaces. |
|
Contains list of SRP ring topology map entries. |
|
Contains MAC layer traffic Counters. |
srpRingCountersCurrentTable
|
Contains physical medium dependent layer Current counters. |
srpRingCountersIntervalTable
|
Contains physical medium dependent layer Interval counters. |
srpHostCountersCurrentTable
|
Contains Higher Layer Current counters. |
srpHostCountersIntervalTable
|
Contains Higher Layer Interval counters. |
srpErrorsCountersCurrentTable
|
Contains SRP Errors Current counters. |
srpErrorsCountersIntervalTable
|
Contains SRP Errors Interval counters. |
|
Contains SRP Errors Current counters. |
|
Contains SRP Errors Interval counters. |
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).
CISCO-SYSLOG-MIB Tables and Objects
Table 3-103 lists CISCO-SYSLOG-MIB Tables and Objects.
.
Table 3-103 CISCO-SYSLOG-MIB Tables and Objects
|
|
|
Contains syslog messages generated by this device. All ’interesting’ syslog messages (i.e. severity |
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-TAP-MIB
The CISCO-TAP-MIB contains SNMP management objects that manage Cisco’s intercept feature.
MIB Objects
Table 3-104 CISCO-TAP-MIB Tables and Objects
|
|
|
Lists the mediation devices with which the intercepting device communicates. These may be on the same or different mediation devices. |
|
Lists the IPv4 and IPv6 streams to be intercepted. The same data stream may be required by multiple taps.This essentially provides options for packet selection, only some of which might be used. For example, if all traffic to or from a given interface is to be intercepted, one would configure an entry which lists the interface, and wild-card everything else. If all traffic to or from a given IP Address is to be intercepted, one would configure two such entries listing the IP Address as source and destination respectively, and wild-card everything else. |
|
Lists the IEEE 802 data streams to be intercepted. The same data stream may be required by multiple taps. This essentially provides options for packet selection, only some of which might be used. For example, if all traffic to or from a given interface is to be intercepted, one would configure an entry which lists the interface, and wild-card everything else. If all traffic to or from a given MAC Address is to be intercepted, one would configure two such entries listing the MAC Address as source and destination respectively, and wild-card everything else. |
|
Contains Lawful Intercept debug information available on this device. This table is used to map an error code to a text message for further information. |
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 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 Tables and Objects
Table 3-105 lists CISCO-TAP2-MIB tables and objects.
.
Table 3-105 CISCO-TAP2-MIB Tables and Objects
|
|
|
Contains the mediation devices with which the intercepting device communicates. |
|
Contains the traffic streams to intercept. The list consists of generic fields that are independent of the type of intercept. |
|
Contains Lawful Intercept debug messages generated by the implementing device. |
|
Contains information of all the users configured in the system who are given permission by different Mediation Devices to access Lawful Intercept CLIs. This table will have dependancy on cTap2MediationTable. When entry in cTap2MediationTable is deleted or moved to ’notInService’, entries corresponding cTap2MediationContentId in this table will be deleted. |
|
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. |
|
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. |
|
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-106 lists CISCO-IP-TAP-MIB Notifications.
.
Table 3-106 CISCO-IP-TAP-MIB Notifications
|
|
|
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. |
|
Sent when an intervention is needed for an event listed in the cTap2MediationTable. |
|
Sent when an intervention is needed for an event listed in the cTap2StreamTable. |
|
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).
CISCO-TCP-MIB Tables and Objects
Table 3-107 lists CISCO-TCP-MIB Tables and Objects.
.
Table 3-107 CISCO-TCP-MIB Tables and Objects
|
|
|
Contains TCP connection-specific information. |
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).
CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB Tables and Objects
Table 3-108 lists CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB Tables and Objects.
.
Table 3-108 CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB Tables and Objects
|
|
cviVlanInterfaceIndexTable
|
The cviVlanInterfaceIndexTable provides a way to translate a VLAN-id in to an ifIndex, so that the routed VLAN interface’s routing configuration can be obtained from interface entry in ipRouteTable. Note that some routers can have interfaces to multiple VLAN management domains, and therefore can have multiple routed VLAN interfaces which connect to different VLANs having the same VLAN-id. Thus, it is possible to have multiple rows in this table for the same VLAN-id. The cviVlanInterfaceIndexTable also provides a way to find the VLAN-id from an ifTable VLAN’s ifIndex. |
cviVlanInterfaceIndexTable
|
The cviVlanInterfaceIndexTable provides a way to translate a VLAN-id in to an ifIndex, so that the routed VLAN interface’s routing configuration can be obtained from interface entry in ipRouteTable. Note that some routers can have interfaces to multiple VLAN management domains, and therefore can have multiple routed VLAN interfaces which connect to different VLANs having the same VLAN-id. Thus, it is possible to have multiple rows in this table for the same VLAN-id. The cviVlanInterfaceIndexTable also provides a way to find the VLAN-id from an ifTable VLAN’s ifIndex. |
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).
CISCO-VPDN-MGMT-EXT-MIB Tables and Objects
Table 3-109 lists CISCO-VPDN-MGMT-EXT-MIB Tables and Objects.
.
Table 3-109 CISCO-VPDN-MGMT-EXT-MIB Tables and Objects
|
|
|
Contains all tunnels configured. |
|
Contains all Sessions currently active. |
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-111 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).
CISCO-VPDN-MGMT-MIB Tables and Objects
Table 3-110 lists CISCO-VPDN-MGMT-MIB Tables and Objects.
.
Table 3-110 CISCO-VPDN-MGMT-MIB Tables and Objects
|
|
|
Contains information about the VPDN system for all tunnel types. |
|
Contains about the active VPDN tunnels. |
|
Contains about the active VPDN tunnels. An entry is added to the table when a new tunnel is initiated and removed from the table when the tunnel is terminated. |
|
Contains about individual user sessions within the active tunnels. Entry is added to the table when new user session is initiated and be removed from the table when the user session is terminated. |
|
Contains about individual sessions within the active tunnels. An entry is added to the table when a new session is initiated and removed from the table when the session is terminated. |
cvpdnUserToFailHistInfoTable
|
Contains the record of failure objects which can be referenced by an user name. Only a name that has a valid item in the Cisco IOS VPDN failure history table will yield a valid entry in this table. The table has a maximum size of 50 entries. Only the newest 50 entries will be kept in the table. |
|
Contains about the VPDN templates. The VPDN template is a grouping mechanism that allows configuration settings to be shared among multiple VPDN groups. One such setting is a limit on the number of active sessions across all VPDN groups associated with the template. The template table allows customers to monitor template-wide information such as tracking the allocation of sessions across templates. |
|
Describes the multilink PPP attributes of the active VPDN sessions. |
|
Exposes the containment relationship between a multilink PPP bundle and a VPDN tunnel. |
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-111 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-111 Deprecated CISCO-VPDN-MGMT-MIB Objects
|
|
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 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).
CISCO-VSIMASTER-MIB Tables and Objects
Table 3-112 lists CISCO-VSIMASTER-MIB Tables and Objects.
.
Table 3-112 CISCO-VSIMASTER-MIBTables and Objects
|
|
|
Contains a set of VSI controllers. Each controller represents an instance of the VSI Master control protocol. A controller communicates with a set of VSI Slaves across a control interface. Running the VSI protocol, the controller supports a network control application. Through VSI, such an application can control the Virtual Circuit cross-connect table inside the ATM switch, perform monitoring and statistics collection of interfaces and virtual circuits on the switch, and discover configuration information from within the switch. |
|
Contains VSI master-slave session status information. Each VSI controller manages a set of VSI slaves, via a protocol instance called a Session. VSI slaves are entities that reside on the controlled ATM switch. Their number and characteristics are discovered by the VSI controller via the VSI protocol. This table has an entry for each slave so discovered. |
|
Contains information about logical interfaces on the slave switch controlled via VSI. Logical interfaces are an abstraction of exposed, external ATM interfaces that are available for connections. When two external interfaces, represented by two logical interfaces, are paired, they provide physical paths through the switch. These physical pathways support cross-connects. |
|
Contains information about cross-connects on the slave switch controlled via VSI. cross-connects represent virtual links across two interfaces. The participating interfaces that support these links are represented in this MIB by the vsiLogicalIfTable entries. |
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.
Starting with Cisco IOS Release 12.2(33)SCF, the ifIndex object that pointed to the Integrated and Modular cable interface SNMP IF index now points to the RF channel SNMP IF Index in table clabTopoChFnCfgTable.
Querying the clabTopoChFnCfgTable displays the cable interfaces and RF channels for the Cisco BR-MC3GX60V, Cisco UBR-MC20X20V, and Cisco uBR-MC88V line cards and SPAs.
Note In Cisco IOS Release 12.2(33)SCE and earlier releases, the ifIndex object pointed to the downstream or upstream channel of the cable interface or the Integrated cable or Modular cable SNMP IF Index.
CLAB-TOPO-MIB Tables and Objects
Table 3-113 lists CLAB-TOPO-MIB Tables and Objects.
Table 3-113 CLAB-TOPO-MIB Objects
|
|
clabTopoFiberNodeCfgTable
|
Defines the cable HFC plant Fiber Nodes known at a CMTS. |
|
Defines the RF topology by defining the connectivity of a CMTS’s downstream and upstream channels to the fiber nodes. |
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).
DOCS-BPI-MIB Tables and Objects
Table 3-114 lists DOCS-BPI-MIB Tables and Objects.
.
Table 3-114 DOCS-BPI-MIB Tables and Objects
|
|
|
Describes the basic and authorization-related Baseline Privacy attributes of each CM MAC interface. |
|
Describes the attributes of each CM Traffic Encryption Key (TEK) association. The CM maintains (no more than) one TEK association per SID per CM MAC interface. |
|
Describes the basic Baseline Privacy attributes of each CMTS MAC interface. |
|
Describes the attributes of each CM authorization association. The CMTS maintains one authorization association with each Baseline Privacy-enabled CM on each CMTS MAC interface. |
|
Describes the attributes of each CM Traffic Encryption Key (TEK) association. The CMTS maintains one TEK association per BPI SID on each CMTS MAC interface. |
docsBpiIpMulticastMapTable
|
Describes the mapping of IP multicast address prefixes to multicast SIDs on each CMTS MAC interface. |
docsBpiMulticastAuthTable
|
Describes the multicast SID authorization for each CM on each CMTS MAC interface. |
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).
DOCS-BPI-PLUS-MIB Tables and Objects
Table 3-115 lists DOCS-BPI-PLUS-MIB Tables and Objects.
.
Table 3-115 DOCS-BPI-PLUS-MIB Tables and Objects
|
|
|
Describes the basic and authorization related Baseline Privacy Plus attributes of each CM MAC interface. |
|
Describes the attributes of each CM Traffic Encryption Key(TEK) association. The CM maintains (no more than) one TEK association per SAID per CM MAC interface. |
docsBpi2CmIpMulticastMapTable
|
Maps multicast IP addresses to SAIDs. It is intended to map multicast IP addresses associated with SA MAP Request messages. |
docsBpi2CmDeviceCertTable
|
Describes the Baseline Privacy Plus device certificates for each CM MAC interface. |
docsBpi2CmCryptoSuiteTable
|
Describes the Baseline Privacy Plus cryptographic suite capabilites for each CM MAC interface. |
|
This table describes the basic Baseline Privacy attributes of each CMTS MAC interface. |
|
This table describes the attributes of each CM authorization association. The CMTS maintains one authorization association with each Baseline Privacy-enabled CM on each CMTS MAC interface. |
|
Describes the attributes of each Traffic Encryption Key (TEK) association. The CMTS maintains one TEK association per SAID on each CMTS MAC interface. |
docsBpi2CmtsIpMulticastMapTable
|
Maps multicast IP addresses to SAIDs. |
docsBpi2CmtsMulticastAuthTable
|
Describes the multicast SAID authorization for each CM on each CMTS MAC interface. |
docsBpi2CmtsProvisionedCmCertTable
|
Contains CM certificate trust entries provisioned to the CMTS. The trust object for a certificate in this table has an overriding effect on the validity object of a certificate in the authorization table, as long as the entire contents of the two certificates are identical. |
|
Contains known certificate authority certificates acquired by this device. |
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-116 lists the constraints that the router places on DOCS-BPI-PLUS-MIB.
.
Table 3-116 DOCS-BPI-PLUS-MIB Constraints
|
|
|
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).
DOCS-CABLE-DEVICE-MIB Tables and Objects
Table 3-117 lists DOCS-CABLE-DEVICE-MIB Tables and Objects.
.
Table 3-117 DOCS-CABLE-DEVICE-MIB Tables and Objects
|
|
|
Controls access to SNMP objects by network management stations. If the table is empty, access to SNMP objects is unrestricted. The objects in this table MUST NOT persist across reboots. The objects in this table are only accessible from cable devices that are not capable of operating in SNMP Coexistence mode (RFC 3584) or in SNMPv3 mode (RFC 3410). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevNmAccess mode for backward compatibility. This table is deprecated. Instead, use the SNMP coexistence MIBs from RFC 3584, the TARGET and NOTIFICATION MIBs from RFC 3413, and the View-Based Access Control Model (VACM) MIBs for all SNMP protocol versions from RFC 3415. |
|
Allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen. The mapping of event types to priorities is vendor dependent. Vendors may also choose to allow the user to control that mapping through proprietary means. Table entries MUST persist across reboots for CMTS devices and MUST NOT persist across reboots for CM devices. |
|
Contains a log of network and device events that may be of interest in fault isolation and troubleshooting. If the local(0) bit is set in docsDevEvReporting, entries in this table MUST persist across reboots. |
|
Contains a list of filters to apply to (bridged) LLC traffic. The filters in this table are applied to incoming traffic on the appropriate interface(s) prior to any further processing (e.g., before the packet is handed off for level 3 processing, or for bridging). The specific action taken when no filter is matched is controlled by docsDevFilterLLCUnmatchedAction. Table entries MUST NOT persist across reboots for any device. |
|
An ordered list of filters or classifiers to apply to IP traffic. Filter application is ordered by the filter index, rather than by a best match algorithm (note that this implies that the filter table may have gaps in the index values). Packets that match no filters will have policy 0 in the docsDevFilterPolicyTable applied to them, if it exists. Otherwise, Packets that match no filters are discarded or forwarded according to the setting of docsDevFilterIpDefault. Any IP packet can theoretically match multiple rows of this table. When considering a packet, the table is scanned in row index order (e.g., filter 10 is checked before filter 20). If the packet matches that filter (which means that it matches ALL criteria for that row), actions appropriate to docsDevFilterIpControl and docsDevFilterPolicyId are taken. If the packet was discarded processing is complete. If docsDevFilterIpContinue is set to true, the filter comparison continues with the next row in the table, looking for additional matches. If the packet matches no filter in the table, the packet is accepted or dropped for further processing according to the setting of docsDevFilterIpDefault. If the packet is accepted, the actions specified by policy group 0 (e.g., the rows in docsDevFilterPolicyTable that have a value of 0 for docsDevFilterPolicyId) are taken, if that policy group exists. Logically, this table is consulted twice during the processing of any IP packet: once upon its acceptance from the L2 entity, and once upon its transmission to the L2 entity. In actuality, for cable modems, IP filtering is generally the only IP processing done for transit traffic. This means that inbound and outbound filtering can generally be done at the same time with one pass through the filter table. The objects in this table are only accessible from cable devices that are not operating in DiffServ MIB mode (RFC 3289). See the conformance section for details. Note that some devices are required by other specifications (e.g., the DOCSIS OSSIv1.1 specification) to support the legacy SNMPv1/v2c docsDevFilter mode for backward compatibility. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289. |
|
Maps between a policy group ID and a set of pointers to policies to be applied. All rows with the same docsDevFilterPolicyId are part of the same group of policy pointers and are applied in the order in this table. docsDevFilterPolicyTable exists to allow multiple policy actions (referenced by policy pointers) to be applied to any given classified packet. The policy actions are applied in index order. For example: Index ID Type Action 1 1 TOS 1 9 5 TOS 1 12 1 IPSEC 3 This says that a packet that matches a filter with policy id 1 first has TOS policy 1 applied (which might set the TOS bits to enable a higher priority) and next has the IPSEC policy 3 applied (which may result in the packets being dumped into a secure VPN to a remote encryptor). Policy ID 0 is reserved for default actions and is applied only to packets that match no filters in docsDevFilterIpTable. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289. |
|
Describes Type of Service (TOS) bits processing. This table is an adjunct to the docsDevFilterIpTable and the docsDevFilterPolicy table. Entries in the latter table can point to specific rows in this (and other) tables and cause specific actions to be taken. This table permits the manipulation of the value of the Type of Service bits in the IP header of the matched packet as follows: Set the tosBits of the packet to (tosBits & docsDevFilterTosAndMask) | docsDevFilterTosOrMask This construct allows you to do a clear and set of all the TOS bits in a flexible manner. Table entries MUST NOT persist across reboots for any device. This table is deprecated. Instead, use the DiffServ MIB from RFC 3289. |
|
Lists the IPv4 addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. Table entries MUST NOT persist across reboots for any device. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically. This table is deprecated and is replaced by docsDevCpeInetTable. |
|
Lists the IP addresses seen (or permitted) as source addresses in packets originating from the customer interface on this device. In addition, this table can be provisioned with the specific addresses permitted for the CPEs via the normal row creation mechanisms. N.B. Management action can add entries in this table and in docsDevCpeIpTable past the value of docsDevCpeIpMax. docsDevCpeIpMax ONLY restricts the ability of the CM to add learned addresses automatically. Table entries MUST NOT persist across reboots for any device. This table exactly mirrors docsDevCpeTable and applies to IPv4 and IPv6 addresses. |
MIB Constraints
Table 3-118 lists the constraints that the router places on DOCS-CABLE-DEVICE-MIB.
.
Table 3-118 DOCS-CABLE-DEVICE-MIB Constraints
|
|
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 |
|
This group of objects is not supported on the CMTS. |
|
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).
DOCS-CABLE-DEVICE-TRAP-MIB Tables and Objects
Table 3-121 lists DOCS-CABLE-DEVICE-TRAP-MIB Tables and Objects.
.
Table 3-119 DOCS-CABLE-DEVICE-TRAP-MIB Tables and Objects
|
|
|
The object is used to enable CM traps. From left to right, the set bit indicates the corresponding CM trap is enabled. |
|
The object is used to enable CMTS traps. From left to right, the set bit indicates the corresponding CMTS trap is enabled. |
MIB Constraints
Table 3-120 lists the constraints that the router places on DOCS-CABLE-DEVICE-TRAP-MIB.
.
Table 3-120 DOCS-CABLE-DEVICE-TRAP-MIB Constraints
|
|
|
|
- docsIfDocsisCapability
- docsIfDocsisOperMode
|
Both objects are deprecated. |
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 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 line card. Although we can set docsDiagLogMaxSize to 4294967295, only 1000 records are logged.
DOCS-DIAG-MIB Tables and Objects
Table 3-121 lists DOCS-DIAG-MIB Tables and Objects.
.
Table 3-121 DOCS-DIAG-MIB Tables and Objects
|
|
|
Contains the Diagnostic Log of the Cable Modems, it is indexed by docsIf3CmtsCmRegStatusId. |
|
Contains detailed diagnostic information for Cable Modems already in docsDiagLogTable. |
DOCS-DRF-MIB
The DOCS-DRF-MIB contains the management objects to manage Downstream RF Interface specifications.
Starting with Cisco IOS Release 12.2(33)SCF, the ifIndex object that pointed to the Integrated or Modular cable interfaces SNMP IF Index now points to the RF channel SNMP IF Index in tables docsDrfDownstreamTable, docsDrfDownstreamCapabilitiesTable, and the ifIndex object (docsDrfChannelBlockTestIfIndex) points to the RF channel SNMP IF Index in the table docsDrfChannelBlockTable.
Querying these tables displays the cable interfaces and RF channels for the Cisco uBR-MC3GX60V, Cisco UBR-MC20X20V, and Cisco uBR-MC88V line cards and SPAs.
Note In Cisco IOS Release 12.2(33)SCE and earlier releases, the ifIndex object pointed to the downstream channel of the cable interface or the Integrated cable or Modular cable SNMP IF Index.
DOCS-DRF-MIB Tables and Objects
Table 3-122 lists DOCS-DRF-MIB Tables and Objects.
Table 3-122 DOCS-DRF-MIB Tables and Objects
|
|
|
Describes the extensions for the DOCSIS RFI Downstream docsIfDownstreamChannelTable. |
docsDrfDownstreamCapabilitiesTable
|
Contains the QAM channel capabilities for the Downstream Interface PHY parameters. |
docsDrfGroupDependencyTable
|
Describes the rules that identify groups of QAM channels with PHY parameters dependencies. |
|
Configures attributes of block channels and Controls channel Block Tests. |
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/docs/ios/cable/configuration/guide/cmts_docsis_gw12_ps2209_TSD_Products_Configuration_Guide_Chapter.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).
DOCS-DSG-IF-MIB Tables and Objects
Table 3-123 lists DOCS-DSG-IF-MIB Tables and Objects.
.
Table 3-123 DOCS-DSG-IF-MIB Tables and Objects
|
|
|
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. |
|
Contains group(s) of tunnel(s). Each tunnel is associated to the destination MAC address. |
dsgIfTunnelGrpToChannelTable
|
Associates a group of tunnels to one or more downstream channel. |
|
Contains the associated timers, vendor specific parameters index and the channel list index to a specific downstream. |
|
Contains the client identification type and value. It also contains the vendor specific parameter identification. There could be multiple client ids associated to a tunnel, grouped by the dsgIfClientIdListIndex. |
|
Allows vendors to send specific parameters to the DSG clients within a DSG rule or within the DSG Configuration block in a DCD message. |
|
Contains list of one or multiple downstream frequencies that are carrying DSG tunnel(s). |
|
Contains timers that are sent to the DSG client(s) via the DCD message. |
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-BPI2-MIB Tables and Objects
Table 3-124 lists DOCS-IETF-BPI2-MIB Tables and Objects.
.
Table 3-124 DOCS-IETF-BPI2-MIB Tables and Objects
|
|
|
Describes the basic and authorization related Baseline Privacy Plus attributes of each CM MAC interface. |
|
Describes the attributes of each CM Traffic Encryption Key (TEK) association. The CM maintains (no more than) one TEK association per SAID per CM MAC interface. |
docsIetfBpi2CmIpMulticastMapTable
|
Maps multicast IP addresses to SAIDs per CM MAC Interface. It is intended to map multicast IP addresses associated with SA MAP Request messages. |
docsIetfBpi2CmDeviceCertTable
|
Describes the Baseline Privacy Plus device certificates for each CM MAC interface. |
docsIetfBpi2CmCryptoSuiteTable
|
Describes the Baseline Privacy Plus cryptographic suite capabilities for each CM MAC interface. |
docsIetfBpi2CmtsBaseTable
|
Describes the basic Baseline Privacy attributes of each CMTS MAC interface. |
docsIetfBpi2CmtsAuthTable
|
Describes the attributes of each CM authorization association. The CMTS maintains one authorization association with each Baseline Privacy- enabled CM, registered on each CMTS MAC interface, regardless of whether the CM is authorized or rejected. |
|
Describes the attributes of each Traffic Encryption Key (TEK) association. The CMTS Maintains one TEK association per SAID on each CMTS MAC interface. |
docsIetfBpi2CmtsIpMulticastMapTable
|
Maps multicast IP addresses to SAIDs. If a multicast IP address is mapped by multiple rows in the table, the row with the lowest docsIetfBpi2CmtsIpMulticastIndex must be utilized for the mapping. |
docsIetfBpi2CmtsMulticastAuthTable
|
Describes the multicast SAID authorization for each CM on each CMTS MAC interface. |
docsIetfBpi2CmtsProvisionedCmCertTable
|
Contains CM certificate trust entries provisioned to the CMTS. The trust object for a certificate in this table has an overriding effect on the validity object of a certificate in the authorization table, as long as the entire contents of the two certificates are identical. |
docsIetfBpi2CmtsCACertTable
|
Contains known Certificate Authority certificates acquired by this device. |
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.
Table 3-125 lists DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB Tables and Objects.
.
Table 3-125 DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB Tables and Objects
|
|
|
The object is used to enable specific CM notifications. For example, if the first bit is set, then docsDevCmInitTLVUnknownNotif is enabled. If it is not set, the notification is disabled. Note that notifications are also under the control of the MIB modules defined in RFC3413. |
|
The object is used to enable specific CMTS notifications. For example, if the first bit is set, then docsDevCmtsInitRegRspFailNotif is enabled. If it is not set, the notification is disabled. Note that notifications are also under the control of the MIB modules defined in RFC3413. |
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.
Table 3-126 lists DOCS-IETF-QOS-MIB Tables and Objects.
.
Table 3-126 DOCS-IETF-QOS-MIB Tables and Objects
|
|
|
Describes the packet classification configured on the CM or CMTS. |
|
Provides a single packet classifier rule. |
|
Index assigned to packet classifier entry by the CMTS, which is unique per Service Flow. |
docsIetfQosPktClassDirection
|
Indicates the direction to which the classifier is applied. |
docsIetfQosPktClassPriority
|
The value specifies the order of evaluation of the classifiers. |
docsIetfQosPktClassIpTosLow
|
The low value of a range of TOS byte values. If the referenced parameter is not present in a classifier, this object reports the value of 0. |
docsIetfQosPktClassIpTosHigh
|
The 8-bit high value of a range of TOS byte values. |
docsIetfQosPktClassIpTosMask
|
The mask value is bitwise ANDed with TOS byte in an IP packet, and this value is used for range checking of TosLow and TosHigh. |
docsIetfQosPktClassIpProtocol
|
Indicates the value of the IP Protocol field required for IP packets to match this rule. |
docsIetfQosPktClassInetAddressType
|
The type of the Internet address for docsIetfQosPktClassInetSourceAddr, docsIetfQosPktClassInetSourceMask, docsIetfQosPktClassInetDestAddr, and docsIetfQosPktClassInetDestMask. |
docsIetfQosPktClassInetSourceAddr
|
This object specifies the value of the IP Source Address required for packets to match this rule. |
docsIetfQosPktClassInetSourceMask
|
Specifies which bits of a packet's IP Source Address are compared to match this rule. |
docsIetfQosPktClassInetDestAddr
|
Specifies the value of the IP Destination Address required for packets to match this rule. |
docsIetfQosPktClassInetDestMask
|
This object specifies which bits of a packet's IP Destination Address are compared to match this rule. |
docsIetfQosPktClassSourcePortStart
|
Specifies the low-end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. |
docsIetfQosPktClassSourcePortEnd
|
Specifies the high-end inclusive range of TCP/UDP source port numbers to which a packet is compared. This object is irrelevant for non-TCP/UDP IP packets. |
docsIetfQosPktClassDestPortStart
|
Specifies the low-end inclusive range of TCP/UDP destination port numbers to which a packet is compared. |
docsIetfQosPktClassDestPortEnd
|
Specifies the high-end inclusive range of TCP/UDP destination port numbers to which a packet is compared. |
docsIetfQosPktClassDestMacAddr
|
An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsIetfQosPktClassDestMacMask equals the value of docsIetfQosPktClassDestMacAddr. |
docsIetfQosPktClassDestMacMask
|
An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsIetfQosPktClassDestMacMask equals the value of docsIetfQosPktClassDestMacAddr. |
docsIetfQosPktClassSourceMacAddr
|
An Ethernet packet matches this entry when its source MAC address equals the value of this object. |
docsIetfQosPktClassEnetProtocolType
|
Indicates the format of the layer 3 protocol ID in the Ethernet packet. A value of none(0) means that the rule does not use the layer 3 protocol type as a matching criteria. |
docsIetfQosPktClassEnetProtocol
|
If docsIetfQosEthPktClassProtocolType is none(0), this object is ignored when considering whether a packet matches the current rule. |
docsIetfQosPktClassUserPriLow
|
Applies only to Ethernet frames using the 802.1P/Q tag header (indicated with EtherType 0x8100). Such frames include a 16-bit Tag that contains a 3-bit Priority field and a 12-bit VLAN number. |
docsIetfQosPktClassUserPriHigh
|
Applies only to Ethernet frames using the 802.1P/Qtag header (indicated with EtherType 0x8100). Such frames include a 16-bit Tag that contains a 3-bit Priority field and a 12-bit VLAN number. |
docsIetfQosPktClassVlanId
|
Applies only to Ethernet frames using the 802.1P/Q tag header. |
docsIetfQosPktClassStateActive
|
Indicates whether or not the classifier is enabled to classify packets to a Service Flow. |
|
Counts the number of packets that have been classified using this entry. This includes all packets delivered to a Service Flow maximum rate policing function, whether or not that function drops the packets. |
docsIetfQosPktClassBitMap
|
Indicates which parameter encodings were actually present in the DOCSIS packet classifier encoding signaled in the DOCSIS message that created or modified the classifier. |
|
Describes the set of DOCSIS 1.1 and 2.0 QOS parameters defined in a managed device. |
|
A unique set of QOS parameters. |
docsIetfQosParamSetServiceClassName
|
Refers to the Service Class Name from which the parameter set values were derived. |
docsIetfQosParamSetPriority
|
The relative priority of a Service Flow. Higher numbers indicate higher priority. This priority should only be used to differentiate Service Flow from identical parameter sets. |
docsIetfQosParamSetMaxTrafficRate
|
Maximum sustained traffic rate allowed for this Service Flow in bits/sec. |
docsIetfQosParamSetMaxTrafficBurst
|
Specifies the token bucket size in bytes for this parameter set. |
docsIetfQosParamSetMinReservedRate
|
Specifies the guaranteed minimum rate in bits/sec for this parameter set. |
docsIetfQosParamSetMinReservedPkt
|
Specifies an assumed minimum packet size in bytes for which the docsIetfQosParamSetMinReservedRate will be provided. |
docsIetfQosParamSetActiveTimeout
|
Specifies the maximum duration in seconds that resources remain unused on an active service flow before CMTS signals that both active and admitted parameters set are null. |
docsIetfQosParamSetAdmittedTimeout
|
Specifies the maximum duration in seconds that resources remain in admitted state before resources must be released. |
docsIetfQosParamSetMaxConcatBurst
|
Specifies the maximum concatenated burst in bytes that an upstream Service Flow is allowed. The value is calculated from the FC byte of the Concatenation MAC Header to the last CRC byte in of the last concatenated MAC frame, inclusive. |
docsIetfQosParamSetSchedulingType
|
Specifies the upstream scheduling service used for upstream Service Flow. |
docsIetfQosParamSetNomPollInterval
|
Specifies the nominal interval in microseconds between successive unicast request opportunities on an upstream Service Flow. |
docsIetfQosParamSetTolPollJitter
|
Specifies the maximum amount of time in microseconds that the unicast request interval may be delayed from the nominal periodic schedule on an upstream Service Flow. |
docsIetfQosParamSetUnsolicitGrantSize
|
Specifies the unsolicited grant size in bytes. The grant size includes the entire MAC frame data PDU from the Frame Control byte to the end of the MAC frame. |
docsIetfQosParamSetNomGrantInterval
|
Specifies the nominal interval in microseconds between successive data grant opportunities on an upstream Service Flow. |
docsIetfQosParamSetTolGrantJitter
|
Specifies the maximum amount of time in microseconds that the transmission opportunities may be delayed from the nominal periodic schedule. |
docsIetfQosParamSetGrantsPerInterval
|
Specifies the number of data grants per Nominal Grant Interval (docsIetfQosParamSetNomGrantInterval). |
docsIetfQosParamSetTosAndMask
|
Specifies the AND mask for the IP TOS byte for overwriting IP packet's TOS value. |
docsIetfQosParamSetTosOrMask
|
Specifies the OR mask for the IP TOS byte. |
docsIetfQosParamSetMaxLatency
|
Specifies the maximum latency between the reception of a packet by the CMTS on its NSI and the forwarding of the packet to the RF interface. |
|
Defines the type of the QOS parameter set defined by this row. |
docsIetfQosParamSetRequestPolicyOct
|
Specifies which transmit interval opportunities the CM omits for upstream transmission requests and packet transmissions. |
docsIetfQosParamSetBitMap
|
This object indicates the set of QOS Parameter Set parameters actually signaled in the DOCSIS registration or dynamic service request message that created or modified the QOS Parameter Set. |
docsIetfQosServiceFlowTable
|
Describes the set of DOCSIS-QOS Service Flows in a managed device. |
docsIetfQosServiceFlowEntry
|
Describes a Service Flow. An entry in the table exists for each Service Flow ID. |
|
An index assigned to a Service Flow by CMTS. |
docsIetfQosServiceFlowSID
|
Service Identifier (SID) assigned to an admitted or active Service Flow. |
docsIetfQosServiceFlowDirection
|
The direction of the Service Flow. |
docsIetfQosServiceFlowPrimary
|
Object reflects whether Service Flow is the primary or a secondary Service Flow. |
docsIetfQosServiceFlowStatsTable
|
Describes statistics associated with the Service Flows in a managed device. |
docsIetfQosServiceFlowStatsEntry
|
Describes a set of Service Flow statistics. An entry in the table exists for each Service Flow ID. |
docsIetfQosServiceFlowPkts
|
For outgoing Service Flows, this object counts the number of Packet Data PDUs forwarded to this Service Flow. |
docsIetfQosServiceFlowOctets
|
The number of octets from the byte after the MAC header HCS to the end of the CRC for all packets counted in the docsIetfQosServiceFlowPkts object for this row. |
docsIetfQosServiceFlowTimeCreated
|
Indicates the value of sysUpTime when the service flow gets created. |
docsIetfQosServiceFlowTimeActive
|
Indicates the number of seconds that the service flow has been active. |
docsIetfQosServiceFlowPHSUnknowns
|
Counts the number of packets received with an unknown payload header suppression index for incoming upstream CMTS service flows. |
docsIetfQosServiceFlowPolicedDropPkts
|
For outgoing service flows, this object counts the number of Packet Data PDUs classified to this service flow dropped due to: – Implementation-dependent excessive delay while enforcing the Maximum Sustained Traffic Rate. – UGS packets dropped due to exceeding the Unsolicited Grant Size with a Request/Transmission policy that requires such packets to be dropped. |
docsIetfQosServiceFlowPolicedDelayPkts
|
Counts only the outgoing packets delayed in order to maintain the Maximum Sustained Traffic Rate. |
docsIetfQosUpstreamStatsTable
|
Describes statistics associated with upstream service flows. |
docsIetfQosUpstreamStatsEntry
|
Describes a set of upstream service flow statistics. |
|
Identifies a service ID for an admitted or active upstream service flow. |
docsIetfQosUpstreamFragments
|
Describes the number of fragmentation headers received on an upstream service flow, regardless of whether the fragment was correctly reassembled into a valid packet. |
docsIetfQosUpstreamFragDiscards
|
Describes the number of upstream fragments discarded and not assembled into a valid upstream packet. |
docsIetfQosUpstreamConcatBursts
|
Describes the number of concatenation headers received on an upstream service flow. |
docsIetfQosDynamicServiceStatsTable
|
Describes statistics associated with the Dynamic Service Flows in a managed device. |
docsIetfQosDynamicServiceStatsEntry
|
Describes a set of dynamic service flow statistics. Two entries exist for each DOCSIS MAC layer interface for the upstream and downstream direction. |
|
Describes the direction of interface. |
|
Describes the number of Dynamic Service Addition Requests, including retries. |
|
Describes the number of Dynamic Service Addition Responses, including retries. |
|
Describes the number of Dynamic Service Addition Acknowledgements, including retries. |
|
Describes thenumber of Dynamic Service Change Requests, including retries. |
|
Describes the number of Dynamic Service Change Responses, including retries. |
|
Describes the number of Dynamic Service Change Acknowledgements, including retries. |
|
Describes the number of Dynamic Service Delete Requests, including retries. |
|
Describes the number of Dynamic Service Delete Responses, including retries. |
|
Describes the number of successful Dynamic Service Addition transactions. |
docsIetfQosDynamicAddFails
|
Describes the number of failed Dynamic Service Addition transactions. |
docsIetfQosDynamicChanges
|
Describes the number of successful Dynamic Service Change transactions. |
docsIetfQosDynamicChangeFails
|
Describes the number of failed Dynamic Service Change transactions. |
docsIetfQosDynamicDeletes
|
Describes the number of successful Dynamic Service Delete transactions. |
docsIetfQosDynamicDeleteFails
|
Describes the number of failed Dynamic Service Delete transactions. |
|
Describes the number of Dynamic Channel Change Request messages traversing an interface. |
|
Describes the number of Dynamic Channel Change Response messages traversing an interface. |
|
Describes the number of Dynamic Channel Change Acknowledgement messages traversing an interface. |
|
Describes the number of successful Dynamic Channel Change transactions. |
|
Describes the number of failed Dynamic Channel Change transactions. |
docsIetfQosServiceFlowLogTable
|
Contains a log of the disconnected Service Flows in a managed device. |
docsIetfQosServiceFlowLogEntry
|
Contains information regarding a single disconnected service flow. |
docsIetfQosServiceFlowLogIndex
|
Contains Unique index for a logged service flow. |
docsIetfQosServiceFlowLogIfIndex
|
The ifIndex of ifType docsCableMaclayer(127) on the CMTS where the service flow was present. |
docsIetfQosServiceFlowLogSFID
|
The index assigned to the service flow by the CMTS. |
docsIetfQosServiceFlowLogCmMac
|
Contains the MAC address for the cable modem associated with the service flow. |
docsIetfQosServiceFlowLogPkts
|
Contains the number of packets counted on this service flow after payload header suppression. |
docsIetfQosServiceFlowLogOctets
|
Contains the number of octets counted on this service flow after payload header suppression. |
docsIetfQosServiceFlowLogTimeDeleted
|
Contains the value of sysUpTime when the service flow was deleted. |
docsIetfQosServiceFlowLogTimeCreated
|
The value of sysUpTime when the service flow was created. |
docsIetfQosServiceFlowLogTimeActive
|
The total time that the service flow was active. |
docsIetfQosServiceFlowLogDirection
|
The value of docsIetfQosServiceFlowDirection for the service flow. |
docsIetfQosServiceFlowLogPrimary
|
The value of docsIetfQosServiceFlowPrimary for the service flow. |
docsIetfQosServiceFlowLogServiceClassName
|
The value of docsIetfQosParamSetServiceClassName for the provisioned QOS Parameter Set of the service flow. |
docsIetfQosServiceFlowLogPolicedDropPkts
|
The final value of docsIetfQosServiceFlowPolicedDropPkts for the service flow. |
docsIetfQosServiceFlowLogPolicedDelayPkts
|
The final value of docsIetfQosServiceFlowPolicedDelayPkts for the service flow. |
docsIetfQosServiceFlowLogControl
|
Setting this object to the value destroy(6) removes this entry from the table. |
docsIetfQosServiceClassTable
|
This table describes the set of DOCSIS-QOS Service Classes in a CMTS. |
docsIetfQosServiceClassEntry
|
A provisioned service class on a CMTS. Each entry defines a template for certain DOCSIS QOS Parameter Set values. |
docsIetfQosServiceClassName
|
Service Class Name. DOCSIS specifies that the maximum size is 16 ASCII characters including a terminating zero. |
docsIetfQosServiceClassStatus
|
Used to create or delete rows in this table. |
docsIetfQosServiceClassPriority
|
Contains the template for docsIetfQosParamSetPriority. |
docsIetfQosServiceClassMaxTrafficRate
|
Contains the template for docsIetfQosParamSetMaxTrafficRate. |
docsIetfQosServiceClassMaxTrafficBurst
|
Contains the template for docsIetfQosParamSetMaxTrafficBurst. |
docsIetfQosServiceClassMinReservedRate
|
Template for docsIetfQosParamSEtMinReservedRate. |
docsIetfQosServiceClassMinReservedPkt
|
Template for docsIetfQosParamSetMinReservedPkt. |
docsIetfQosServiceClassMaxConcatBurst
|
Template for docsIetfQosParamSetMaxConcatBurst. |
docsIetfQosServiceClassNomPollInterval
|
Template for docsIetfQosParamSetNomPollInterval. |
docsIetfQosServiceClassTolPollJitter
|
Template for docsIetfQosParamSetTolPollJitter. |
docsIetfQosServiceClassUnsolicitGrantSize
|
Template for docsIetfQosParamSetUnsolicitGrantSize. |
docsIetfQosServiceClassNomGrantInterval
|
Template for docsIetfQosParamSetNomGrantInterval. |
docsIetfQosServiceClassTolGrantJitter
|
Template for docsIetfQosParamSetTolGrantJitter. |
docsIetfQosServiceClassGrantsPerInterval
|
Template for docsIetfQosParamSetGrantsPerInterval. |
docsIetfQosServiceClassMaxLatency
|
Template for docsIetfQosParamSetClassMaxLatency. |
docsIetfQosServiceClassActiveTimeout
|
Contains the template for docsIetfQosParamSetActiveTimeout. |
docsIetfQosServiceClassAdmittedTimeout
|
Contains the template for docsIetfQosParamSetAdmittedTimeout. |
docsIetfQosServiceClassSchedulingType
|
Contains the template for docsIetfQosParamSetSchedulingType. |
docsIetfQosServiceClassRequestPolicy
|
Contains the template for docsIetfQosParamSetRequestPolicyOct. |
docsIetfQosServiceClassTosAndMask
|
Contains the template for docsIetfQosParamSetTosAndMask. |
docsIetfQosServiceClassTosOrMask
|
Contains the template for docsIetfQosParamSetTosOrMask. |
docsIetfQosServiceClassDirection
|
Specifies whether the service class template applies to upstream or downstream service flows. |
docsIetfQosServiceClassStorageType
|
Defines whether this row is kept in volatile storage and lost upon reboot or whether it is backed up by non-volatile or permanent storage. |
docsIetfQosServiceClassDSCPOverwrite
|
Allows the overwrite of the DSCP field per RFC 3260. |
docsIetfQosServiceClassPolicyTable
|
Describes the set of DOCSIS-QOS Service Class Policies. |
docsIetfQosServiceClassPolicyEntry
|
Contains payload service class name policy entry. |
docsIetfQosServiceClassPolicyIndex
|
Index value to identify an entry in this table uniquely. |
docsIetfQosServiceClassPolicyName
|
Service Class Name to identify the name of the service class flow to which the packet should be directed. |
docsIetfQosServiceClassPolicyRulePriority
|
Service Class Policy rule priority for the entry. |
docsIetfQosServiceClassPolicyStatus
|
Used to create or delete rows in this table. |
docsIetfQosServiceClassPolicyStorageType
|
Defines whether this row is kept in volatile storage and lost upon reboot or whether it is backed up by non-volatile or permanent storage. |
|
Describes the set of payload header suppression entries. |
|
Contains payload header suppression entry. |
|
Contains payload header suppression field defines the bytes of the header that must be suppressed/restored by the sending/receiving device. |
|
Contains payloadheader suppression mask defines the bit mask that is used in combination with the docsIetfQosPHSField. |
|
Contains payload header suppression size specifies the number of bytes in the header to be suppressed and restored. |
|
Contains payload header suppression verification value. |
|
Contains payload header suppression index uniquely references the PHS rule for a given service flow. |
docsIetfQosCmtsMacToSrvFlowTable
|
Provides for referencing the service flows associated with a particular cable modem. |
docsIetfQosCmtsMacToSrvFlowEntry
|
An entry is created by CMTS for each service flow connected to this CMTS. |
|
Contains the MAC address for the referenced CM. |
docsIetfQosCmtsServiceFlowId
|
Contains index assigned to a service flow by CMTS. |
|
Contains ifIndex of ifType docsCableMacLayer(127) on the CMTS that is connected to the Cable Modem. |
MIB Constraints
Refer to MIB constraints section under DOCS-QOS-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 4546. 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
Starting with Cisco IOS Release 12.2(33)SCF, the ifIndex object which pointed to the Integrated cable or Modular cable interface SNMP IF Index now points to the RF channel SNMP IF Index in the tables docsIfDownstreamChannelTable, docsIfCmtsChannelUtilizationTable and docsIfCmtsDownChannelCounterTable. Querying of these tables displays the cable interfaces and RF channels of Cisco uBR-MC3GX60V, Cisco UBR-MC20X20V, and Cisco uBR-MC88V line cards, and SPAs.
Note In Cisco IOS Release 12.2(33)SCE and earlier releases, the ifIndex object pointed to the the downstream or upstream channel of the cable interface or the Integrated cable or Modular cable SNMP IF Index.
DOCS-IF-MIB Tables and Objects
Table 3-127 lists DOCS-IF-MIB Tables and Objects.
Table 3-127 DOCS-IF-MIB Tables and Objects
|
|
docsIfDownstreamChannelTable
|
Describes the attributes of downstream channels (frequency bands). |
docsIfUpstreamChannelTable
|
Describes the attributes of attached upstream channels. |
|
Describes the attributes for each class of service. |
|
Describes the PHY signal quality of downstream channels at the cable modem level. This table describes the PHY signal quality of upstream channels at the CMTS level. |
|
Describes the attributes of each CMTS MAC interface, extending the information available from ifEntry. |
|
Describes a number of status objects and counters at the MAC layer. |
|
Contains a set of objects in the CMTS, that is maintained for each cable modem connected to a CMTS. |
docsIfCmtsCmStatusExtTable
|
Contains a set of objects in the CMTS, maintained for each Cable Modem connected to this CMTS. |
|
Describes the attributes of upstream service queues in a CMTS. |
docsIfCmtsModulationTable
|
Describes a modulation profile associated with one or more upstream channels. |
|
Provides a quick access index into the docsIfCmtsCmStatusTable. |
docsIfCmtsChannelUtilizationTable
|
Reports utilization statistics for attached upstream and downstream physical channels. |
docsIfCmtsDownChannelCounterTable
|
Collects downstream channel statistics for utilization calculations for the CMTS. |
docsIfCmtsUpChannelCounterTable
|
Provides upstream channel statistics appropriate for channel utilization calculations for the CMTS. |
MIB Constraints
Table 3-128 lists the constraints that the router places on DOCS-IF-MIB.
.
Table 3-128 DOCS-IF-MIB Constraints
|
|
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. |
|
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. |
|
|
|
Read-only. |
|
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. |
|
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. |
|
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 |
|
Value is Integer32 |
- docsIfCmtsChannelUtUtilization
|
Value is Integer32 |
- docsIfCmtsChannelUtilizationInterval
|
Read, write. |
docsIfUpstreamChannelTable
|
|
- docsIfUpChannelPreEqEnable
|
|
|
|
|
Read-only. Value is 64-bit counter. |
|
Read-only. Value is 64-bit counter. |
- docsIfSigQExtUncorrectables
|
Read-only. Value is 64-bit counter. |
docsIfCmtsDownChannelCounterTable
|
Read-only. |
|
Value is Integer32 |
- docsIfCmtsDownChnlCtrTotalBytes
|
Value is Counter32 |
- docsIfCmtsDownChnlCtrUsedBytes
|
Value is Counter32 |
- docsIfCmtsDownChnlCtrExtTotalBytes
|
Value is Counter64 |
- docsIfCmtsDownChnlCtrExtUsedBytes
|
Value is Counter64 |
docsIfCmtsUpChannelCounterTable
|
Read-only. |
|
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 or the ccwbRFChanUtilInterval attribute.
The value of docsIfCmtsChannelUtilizationInterval ranges from 1 to 86400 seconds. Table 3-129 lists the tables/IPDR schemas affected by docsIfCmtsChannelUtilizationInterval attribute:
Table 3-129 Tables/IPDR Schemas Affected by docsIfCmtsChannelUtilizationInterval Attribute
|
|
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 to 86400 seconds, 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-130 . This object points to the corresponding narrowband channel’s SNMP IF index, or the Modular Cable Interface SNMP IF index.
Table 3-130 docsIfCmtsCmStatusDownChannelIfIndex
|
|
|
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-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:
DOCS-IF3-MIB Tables and Objects
Table 3-131 lists DOCS-IF3-MIB Tables and Objects.
.
Table 3-131 DOCS-IF3-MIB Tables and Objects
|
|
|
Defines attributes of the CM connectivity status.This object provides CM connectivity status information of the CM previously available in the SNMP table docsIfCmStatusTable. |
|
Defines PHY and MAC information about the CM’s upstream channels operating in Multiple Transmit Channel (MTC) mode or in a Pre-3.0 DOSCIS transmit channel mode. This object provides per-CM Upstream channel information previously available in the SNMP table docsIfCmStatusTable. |
docsIf3CmtsCmRegStatusTable
|
Defines attributes that represent the CM’s registration status as tracked by the CMTS. |
docsIf3CmtsCmUsStatusTable
|
Defines status information of the CM currently in use Upstream Logical Channels, as reported by the CMTS. |
|
Configures the association of downstream and upstream channels to a particular MAC Domain (MD) on a CMTS. The creation of channels and MAC domain object interface instances is vendor-specific. In particular, the assignment of the channel interface index is normally vendor-specific. Therefore, this object is intended only for associating channels to a MAC Domain and assumes that those channels were previously configured. The CMTS may have restrictions on which channels can be configured in the same MAC Domain. For example, it could require the upstream channels to be from the same line card. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the ChId attribute to be set. |
|
Identifies the scope of the Receive Channel Configuration (RCC) and provides a top level container for the Receive Module and Receive Channel objects. The CMTS selects an instance of this object to assign to a CM when it registers. This object supports the creation and deletion of multiple instances. |
|
The RCC Status object provides a read-only view of the statically-configured (from the RccCfg object) and dynamically-created RCCs. The CMTS creates an RCC Status instance for each unique MAC Domain Cable Modem Service Group (MD-CM-SG) to which it signals an RCC to the CM. |
|
The Receive Channel Configuration object permits an operator to configure how CMs registered with certain Receive Channel Profiles will configure the Receive Channels within their profile. When a CM registers with an RCP for which all Receive Channel Indices (RcIds) are configured in the Receive Module object and all Receive Channels are configured within this object, the CMTS should use the configuration within these objects to set the Receive Channel Configuration returned to the CM in a REG-RSP message. A CMTS may require configuration of all pertinent Receive Module and Receive Channel instances in order to register a CM that reports a Receive Channel Profile (RCP), including any standard Receive Channel Profiles. If the CM reports multiple RCPs, and Receive Module and Receive Channel objects have instances for more than one RCP, the particular RCP selected by the CMTS is not specified. A CMTS is not restricted to assigning Receive Modules based only on the contents of this object. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the ChIfIndex attribute to be set and a valid reference of a RccCfg instance. |
|
The Receive Channel Status object reports the status of the statically-configured and dynamically-created Receive Channels within an RCC. |
|
The Receive Module Configuration object permits an operator to configure how CMs with certain Receive Channel Profiles (RCPs) will configure the Receive Modules within their profile upon CM registration. When a CM registers with an RCP for which all Receive Module Indices (RmIds) are configured in this object and all Receive Channels are configured within the Receive Channel (ReceiveChannel) object, the CMTS should use the configuration within these objects to set the Receive Channel Configuration assigned to the CM in a REG-RSP message. A CMTS may require configuration of all pertinent Receive Module and Receive Channel instances (i.e., MIB table entries) in order to register a CM that reports a Receive Channel Profile. If the CM reports multiple RCPs, and Receive Module and Receive Channel objects have instances (i.e., MIB table entries) for more than one RCP reported by the CM, the particular RCP selected by the CMTS is not specified. A CMTS is not restricted to assigning Receive Modules based only on the contents of this object. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the reference of a valid RccCfg instance. |
docsIf3RxModuleStatusTable
|
The Receive Module Status object provides a read-only view of the statically configured and dynamically created Receive Modules within an RCC. |
|
Reports 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 reached by the MD-CM-SG. |
|
Returns the list of downstream channel associated with a MAC Domain MD-DS-SG-ID. |
|
Returns the list of upstream channels associated with a MAC Domain MD-US-SG-ID. |
docsIf3MdUsToDsChMappingTable
|
Returns the set of downstream channels that carry UCDs and MAPs for a particular upstream channel in a MAC Domain. |
|
Contains MAC domain level control and configuration attributes. |
docsIf3BondingGrpCfgTable
|
Defines statically configured Downstream Bonding Groups and Upstream Bonding Groups on the CMTS. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the ChList attribute to be set. |
docsIf3DsBondingGrpStatusTable
|
Returns administratively-configured and CMTS defined downstream bonding groups. |
docsIf3UsBondingGrpStatusTable
|
Returns administratively-configured and CMTS-defined upstream bonding groups. |
|
Defines management extensions for upstream channels, in particular SCDMA parameters. |
|
Defines a set of upstream channels. These channel sets may be associated with channel bonding groups, MD-US-SGs, MD-CM-SGs, or any other channel set that the CMTS may derive from other CMTS processes. |
|
Defines 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 may derive from other CMTS processes. |
docsIf3SignalQualityExtTable
|
Provides an in-channel received modulation error ratio metric for CM and CMTS. |
docsIf3CmtsSignalQualityExtTable
|
Provides metrics and parameters associated with received carrier, noise and interference power levels in the upstream channels of the CMTS. |
docsIf3CmtsSpectrumAnalysisMeasTable
|
Configures the logical upstream interfaces to perform the spectrum measurements. This object supports creation and deletion of instances. |
|
Represents the DOCSIS Path Verify Statistics collected in the cable modem device. The CMTS controls the logging of DPV statistics in the cable modem. Therefore the context and nature of the measurements are governed by the CMTS and not self-descriptive when read from the CM. |
|
Represents the control mechanism to enable the dispatching of events based on the event Id. The following rules define the event control behavior: o The CmEventCtrl object has no instances Events are sent to Local Log depending on the settings of the docsDevEvReporting object. Settings in the DocsDevEvReporting for other dispatch mechanisms are treated as disable. o The CmEventCtrl object contains configured instances Only events matching the Event Ids configured in the object are sent according to the settings of the docsDevEvReporting object. o The CmEventCtrl object contains an instance with Event Id 0 All events matching the Local Log settings of docsDevEvReporting are sent to local log. Events matching the Event Ids configured in the docsDevEvReporting and CmEventCtrl objects are delivered to dispatch mechanisms other than Local Log. The CM does not persist instances of CmEventCtrl across reinitializations. |
docsIf3CmtsEventCtrlTable
|
Represents the control mechanism to enable the dispatching of events based on the event Id. The following rules define the event control behavior: o The CmtsEventCtrl object has no instances Events are sent to Local Log depending on the settings of the docsDevEvReporting object. Settings in the DocsDevEvReporting for other dispatch mechanisms are treated as disable. o The CmtsEventCtrl object contains configured instances Only events matching the Event Ids configured in the object are sent according to the settings of the docsDevEvReporting object. o The CmtsEventCtrl object contains an instance with Event Id 0 All events matching the Local Log settings of docsDevEvReporting are sent to local log. Events matching the Event Ids configured in the docsDevEvReporting and CmtsEventCtrl objects are delivered to dispatch mechanisms other than Local Log. The CMTS persists all instances of CmtsEventCtrl across reinitializations. |
MIB Constraints
Table 3-132 lists the constraints that the router places on DOCS-IF3-MIB.
.
Table 3-132 DOCS-IF3-MIB Constraints
|
|
docsIf3CmtsCmRegStatusTable
- docsIf3CmtsCmRegStatusTcsId
|
This docsIf3CmtsCmRegStatusTcsId MIB object is not supported on the Cisco uBR-E-28U line card on the Cisco uBR7225 Series Router. |
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).
DOCS-IF-EXT-MIB Tables and Objects
Table 3-133 lists DOCS-IF-EXT-MIB Tables and Objects.
.
Table 3-133 DOCS-IF-EXT-MIB Tables and Objects
|
|
docsIfCmtsCmStatusExtTable
|
Contains a set of objects in the CMTS, maintained for each Cable Modem connected to this CMTS. |
MIB Constraints
Table 3-134 lists the constraints that the router places on DOCS-IF-EXT-MIB.
.
Table 3-134 DOCS-IF-EXT-TRAP-MIB Constraints
|
|
|
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-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).
DOCS-IFEXT2-MIB Tables and Objects
Table 3-135 lists DOCS-IFEXT2-MIB Tables and Objects.
.
Table 3-135 DOCS-IFEXT2-MIB Tables and Objects
|
|
docsIfExt2CmMscStatusTable
|
Extends the docsIfCmStatusTable to report the CM MSC status. |
docsIfExt2CmtsCmMscStatusTable
|
Extends the docsIfCmtsCmStatusTable to report CM MSC status. |
docsIfExt2CmtsUpChannelMscTable
|
Extends the docsIfUpstreamChannelTable to report CM MSC status. |
docsIfExt2CmtsUpChannelTable
|
Extends the docsIfUpstreamChannelTable to report additional upstream status information. |
MIB Constraints
Table 3-136 lists the constraints that the router places on DOCS-IFEXT2-MIB.
.
Table 3-136 DOCS-IFEXT2-MIB Constraints
|
|
docsIfExt2CmtsUpChannelTable
|
|
- docsIfExt2CmtsUpChannelTotalCMs
|
Read-only. |
DOCS-IF-M-CMTS-MIB
The DOCS-IF-M-CMTS-MIB contains the management objects to configure and manage the Downstream 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).
DOCS-IF-M-CMTS-MIB Tables and Objects
Table 3-137 lists DOCS-IF-M-CMTS-MIB Tables and Objects.
.
Table 3-137 DOCS-IF-M-CMTS-MIB Tables and Objects
|
|
docsIfMCmtsCoreDownstreamTable
|
M-CMTS Core extensions for the DOCSIS RFI Downstream docsIfDownstreamTable. |
docsIfMCmtsEqamDownstreamTable
|
M-CMTS EQAM extensions for the DOCSIS RFI Downstream docsIfDownstreamTable. |
docsIfMCmtsEqamDownstreamCapabilitiesTable
|
Contains the QAM channel capabilities for the M-CMTS Downstream Interface PHY parameters in the EQAM device. |
docsIfMCmtsEqamGroupDependencyTable
|
Describes the rules that identify groups of QAM channels with PHY parameters dependencies. A PHY parameter dependency group means that a set to a QAM channel parameter may affect the value of other QAM Channels in the group. TSID is a broadcast term borrowed by the M-CMTS architecture to represent a unique identifier of QAM channels in the M-CMTS architecture. TSID Group is the DEPI concept of a set of QAM channels with a PHY parameter dependency. This module refers to TSID group as a PHY dependency Group. This table uses the ENTITY-MIB physical component structure to allows the managed system to describe the QAM channels’ PHY parameters dependencies. A management entity can use the information from this table to generate the DEPI TSID Groups. Examples of PHY dependencies could be usage of adjacent frequencies, or QAM channels of RF ports restricted, or same interleaver value, modulation and J.83 Annex value. Additional details and rules to describe the PHY parameter dependency is indicated in docsIfMCmtsEqamGroupDependencyType. Vendors may extend via other MIB modules the usage of docsIfMCmtsEqamGroupDependencyType. |
docsIfMCmtsEqamGlobCfgDownTable
|
For setting multiple parameters of multiple QAM channels. Creating an entry in this table will set automatically all QAM Channels in the containment tree of docsIfMCmtsEqamGlobCfgDownPhysicalIndex in entPhysicalContainsTable to the parameter values specified during the row creation. docsIfMCmtsEqamGlobCfgDownPhysicalIndex MUST be a valid Physical index of entPhysicalTable. The ways to configure QAM channels parameters are: 1) Globally. Using this table, docsIfMCmtsEqamGlobCfgDownTable 2) Directly. Using docsIfMCmtsEqamDownstreamTable and docsIfDownstreamChannelTable to change parameters and lock status of individual QAM channels. In general an entry in this table will set the parameters of QAM channels of the containment tree recursively the same way as doing directly as described in 2)above. It means, potentially there could be rejections based on locked parameters and/or PHY dependencies that prevent the sets. The row creation in this table is not rejected or set in ’inactive’ or ’notInService’ state due individual QAM channels in the group failures due the global set, instead, an error status is reported per entry. The processing of the entries in this table (e.g., at system initialization) is sequential; therefore, it could be overlapping rules based on the containment tree level of the entries. |
docsIfMCmtsChannelBlockTable
|
Configure attributes of block channels and Controls channel Block Tests. A channel block is an ENTITY-MIB containment of PhysicalClass ’module’ that represent an RF connector. |
docsIfMCmtsDepiSessionConfigTable
|
The Control table for the configuration of M-CMTS Downstream Interfaces. The M-CMTS Downstream Interface configuration information is contained in this table. Currently L2TPv3 is the defined tunnel mechanism for DEPI sessions. There may be other DEPI tunnel methods defined in the future. The configuration of entries with docsIfMCmtsDepiSessionConfigMethod equal to ’l2tpControl’ follows the rule below: Only one L2TPv3 Control Plane from a M-CMTS Core IP is established per EQAM IP host destination indicated in docsIfMCmtsDepiSessionConfigRemoteAddr. There may be other L2TPv3 Control Plane connections from different M-CMTSs to the same EQAM IP host. |
docsIfMCmtsDepiSessionInfoTable
|
Provides M-CMTS Downstream Interface with DEPI session information related to the DEPI session configuration process. |
docsIfMCmtsDepiRsrcAllocTable
|
Contains PHBIDs Resources used for DEPI applications. At the M-CMTS core these entries contain information about the mapping of egress traffic to PHIDs and DEPI flow IDs also known as DEPI payload encapsulation. For the M-CMTS Core there are two type of entries: o One set of entries is a preconfigured list of PHBIDs used for M-CMTS requests to EQAM IP Host, e.g., the MIB object docsIfMCmtsDepiSessionConfigRsrcAllocReq references those type of entry sets. In those entries the values of docsIfMCmtsDepiRsrcAllocUdpPort, docsIfMCmtsDepiRsrcAllocFlowId and docsIfMCmtsDepiRsrcAllocPolicyScnTags are ignored by the M-CMTS. o The second set of entries has the responses from the EQAM IP host to the M-CMTS when the DEPI session request is successful. The object docsIfMCmtsDepiSessionConfigPhbIdResp in docsIfMCmtsDepiSessionConfigTable references an entry of this type. The EQAM MAY implement this table to configure the different queue prioritization of the DEPI flow IDs, PHBIDs and UDP ports triplet used in the DEPI Resource allocation response to the M-CMTS. If this table is not implemented by the EQAM device the object docsIfMCmtsDepiSessionInfoRsrcAllocResp is set to zero, and the DEPI session Resource Allocation response is vendor specific. Also the EQAM device MAY implement this table as read-only for the purpose of debugging the DEPI Resource Allocation Responses sent to the M-CMTS core. |
docsIfMCmtsDepiSessionStatsTable
|
Provides DEPI Session statistics for the M-CMTS Downstream Interface. |
docsIfMCmtsDepiSessionCinLatencyPerfTable
|
Provides accumulative measurements of the CIN latency on the network. |
docsIfMCmtsDepiPhbPolicyTable
|
The policy rules that apply to DOCSIS traffic (traffic profiles) of a DEPI session. Traffic Profiles are ways to discriminate specific traffic flows for QOS treatment in the CIN and EQAM device. The main function of this table is to map the DOCSIS SF egress traffic to the Converged Interconnect Network PHB configuration; thus, from the M-CMTS to the EQAM IP host Ingress port, the QOS levels are defined properly. In D-MPT mode this table is only applicable to PHB egress marking for the CIN. In PSP mode this table is referenced PHBID CIN (referenced by docsIfMCmtsDepiSessionConfigCinPhbIdPolicy) The CIN PHBs is operator specific. The CIN per-hub-Behavior of this table accomplishes: o DOCSIS MAPs, DOCSIS MAC messages and PacketCable VoIP PHBID are configured in a reserved policy tag ’ExpediteForwardCIN’ traffic. This policy has a ’permanent’ storage. o Data traffic (per DOCSIS Service Flows) is assigned to PBHIDs based on Admission policies rules, e.g., Service Class Name, DOCSIS specific parameters, etc. This table only deals with policies based with SCN. Other traffic descriptor rules are vendor dependent. |
docsIfMCmtsQosServiceFlowExtTable
|
Contains M-CMTS Extensions of the DOCSIS Service Flow table to describe DEPI QOS associations to Service Flows. DEPI Connection Control Table indicates the policies to apply any time a new DOCSIS Service Flow is added to the M-CMTS Downstream interface. |
MIB Constraints
Table 3-138 lists the constraints that the router places on DOCS-IF-M-CMTS-MIB.
.
Table 3-138 DOCS-IF-M-CMTS-MIB Constraints
|
|
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
DOCS-LOADBAL3-MIB Tables and Objects
Table 3-139 lists DOCS-LOADBAL3-MIB Tables and Objects.
.
Table 3-139 DOCS-LOADBAL3-MIBTables and Objects
|
|
docsLoadbal3ChgOverStatusTable
|
Reports the status of cable modems instructed to move to a new downstream and/or upstream channel or channel sets when commanded either by an operation in the ChgOver object. An instance in this object is created for each change-over operation committed successfully. If the instance value attribute is not final (the change-over operation is still pending completion), this instance is expected to be updated at some point later to reflect the final state of the change-over operation. |
docsLoadbal3CmtsCmParamsTable
|
Represents the autonomous load balancing parameters provisioned for cable modem. The CMTS selects the cable modem Load Balancing Group (GrpId attribute of this object) from multiple sources by following the rules and sequence described below: The CMTS selects the assignment of the CM to a Load Balancing Group by determining first if the CM is in a Restricted Load Balancing Group or in its absence to the General Load Balancing group that corresponds to the MD-CM-SG of the CM. The selection of the Restricted Load Balancing group is achieved by first matching the CM in the RestrictCmCfg Object and if no match is found, by selecting the best match within the ResGrpCfg object. The best match within the ResGrpCfg follows the MULPI requirements on precedences of the CM signaled TLVs: ServiceType ID and Load Balancing Group ID (for backward compatibility of provisioned Group IDs). |
docsLoadbal3GeneralGrpCfgTable
|
Provides the parameters for the General Load Balancing Groups of MD-CM-SGs associated with MAC Domain-Fiber Node pairs. This object allows configuration of load balancing parameters for General Load Balancing Groups by way of MAC Domain-Fiber Node pairs. In many deployments, a MAC Domain-Fiber Node pair will equate to an MD-CM-SG (which always equates to a GLBG). In the case where an MD-CM-SG spans multiple Fiber Nodes, there will be multiple instances of this object that represent the General Load Balancing Group (MD-CM-SG). The CMTS MUST enforce that such instances all have the same attribute values. Any time a fiber node is associated to a MAC Domain an instance of this object is defined by the CMTS and populated with default values from the GeneralGrpDefaults object. Similarly when a fiber node is no longer paired with a MAC Domain the corresponding instance is deleted from the object. |
docsLoadbal3ResGrpCfgTable
|
Represents the configuration of Restricted Load Balancing Groups. |
docsLoadbal3GrpStatusTable
|
Represents the status of all General and Restricted Load Balancing Groups in this CMTS. This object summarizes the load balancing parameters that applies to CMTS system wide Load Balancing Groups. The Load Balancing Groups defined in this object include the configured Restricted Load Balancing Groups and the General Load Balancing Groups derived from the GeneralGrpCfg object. |
docsLoadbal3RestrictCmCfgTable
|
Describes the list of cable modems being statically provisioned at the CMTS to a Restricted Load Balancing Group. |
|
Describes the set of load balancing policies. Instances from this object might be referenced by GrpStatus object. All the rules contained in a load balancing policy apply to an Autonomous Load Balancing operations. Load balancing rules are defined within this specification or can be vendor-defined as well. |
docsLoadbal3BasicRuleTable
|
Represents a basic ruleset applicable to a load balancing policy that references it. |
MIB Constraints
Table 3-140 lists the constraints that the router places on DOCS-LOADBAL3-MIB.
.
Table 3-140 DOCS-LOADBAL3-MIB Constraints
|
|
|
An empty value or a value with all zero bits is not supported. |
|
DBC operation is not be supported. |
docsLoadbal3ChgOverStatusTable
|
Contains up to 100 entries. The table is cleared after PRE switchover. |
|
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. |
|
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).
|
|
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
DOCS-LOADBALANCING-MIB Tables and Objects
Table 3-141 lists DOCS-LOADBALANCING-MIB Tables and Objects.
.
Table 3-141 DOCS-LOADBALANCING-MIB Tables and Objects
|
|
docsLoadBalChgOverStatusTable
|
Contains CMTS operation entries to reports the status of cable modems instructed to move to a new downstream and/or upstream channel. Using the docsLoadBalChgOverGroup objects. An entry in this table is created or updated for the entry with docsIfCmtsCmStatusIndex that correspond to the cable modem MAC address of the Load Balancing operation. docsLoadBalChgOverCommit to true(1). |
|
Contains the attributes of the load balancing groups present in this CMTS. |
|
Lists all upstream and downstream channels associated with load balancing groups. |
|
Contains pairs of upstream channels within a Load Balancing Group. Entries in this table are used to override the initialization techniques defined for the associated Load Balancing Group. |
docsLoadBalRestrictCmTable
|
Lists all cable modems in each Restricted Load Balancing Groups. |
|
Describes the set of Load Balancing policies. Rows in this table might be referenced by rows in docsLoadBalGrpEntry. |
docsLoadBalBasicRuleTable
|
DOCSIS defined basic ruleset for load Balancing Policy. This table enables of disable load balancing for the groups pointing to this ruleset in the policy group. |
docsLoadBalCmtsCmStatusTable
|
Contains the load balancing attributes associated with the cable modem. |
MIB Constraints
Table 3-142 lists the constraints that the router places on DOCS-LOADBALANCING-MIB.
.
Table 3-142 DOCS-LOADBALANCING-MIB Constraints
|
|
|
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. |
|
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).
|
|
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.
DOCS-MCAST-AUTH-MIB Tables and Objects
Table 3-143 lists CISCO-LEC-EXT-MIB Tables and Objects.
.
Table 3-143 DOCS-MCAST-AUTH-MIB Tables and Objects
|
|
docsMcastAuthCmtsCmStatusTable
|
Maintains per-CM status of Multicast Authorization policies to be applied to this CM. The CM acquires these policy parameters through the CM registration process, or in the absence of some or all of those parameters, from the Ctrl Object. This object is meaningful when the Control Enable attribute is set to ’enable’. In the process of authorizing a CM client’s session request the CMTS must check rules defined in StaticSessRule object and then rules defined in ProfileSessRule object. In the case of multiple multicast session matches, the rule priority attribute defines the final selected session rule. The selection of a session rules when multiple matches have the same priority is vendor specific. The CMTS MAY report in the CmtsCmStatus object CMs that do not signal any IP Multicast Authorization Encodings in the registration process. |
docsMcastAuthProfileSessRuleTable
|
Defines Operator configured profiles to be matched during the authorization process. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the following attributes to be set: PrefixAddrType SrcPrefixAddr SrcPrefixLen GrpPrefixAddr GrpPrefixLen. |
docsMcastAuthStaticSessRuleTable
|
Defines the Session authorization Rules based on the CM or group of CMs signaled in IP Multicast Join Authorization Static Session Subtype encoding This object reflects the Static Session rules that were included in the CM registration request message. |
docsMcastAuthProfilesTable
|
Contains the description of the Multicast Authorization profiles for administrative purposes. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the Description attribute to be set. |
MIB Constraints
Table 3-144 lists the constraints that the router places on DOCS-MCAST-AUTH-MIB.
.
Table 3-144 DOCS-MCAST-MIB Constraints
|
|
|
|
|
Not accessible. |
- docsMcastCmtsGrpCfgSrcPrefixAddr
|
Read-only. |
- docsMcastCmtsGrpCfgSrcPrefixLen
|
Read-only. |
- docsMcastCmtsGrpCfgSrcPrefixLen
|
Read-only. |
- docsMcastCmtsGrpCfgGrpPrefixLen
|
Read-only. |
docsMcastCmtsGrpQosCfgTable
|
|
|
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-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 Continuos Concatenation and Fragmentation (CCF).
- docsQos3ServiceFlowTable: Defines the objects to describe the set of DOCSIS-QOS service flows 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.
DOCS-QOS3-MIB Tables and Objects
Table 3-145 lists DOCS-QOS3-MIB Tables and Objects.
.
Table 3-145 DOCS-QOS3-MIB Tables and Objects
|
|
|
Describes the packet classification configured on the CM or CMTS. The model is that a packet either received as input from an interface or transmitted for output on an interface may be compared against an ordered list of rules pertaining to the packet contents. Each rule is an instance of this object. A matching rule provides a Service Flow ID to which the packet is classified. All rules need to match for a packet to match a classifier. The attibutes in this row correspond to a set of Classifier Encoding parameters in a DOCSIS MAC management message. The BitMap attribute indicates which particular parameters were present in the classifier as signaled in the DOCSIS message. If the referenced parameter was not present in the signaled Classifier, the corresponding attribute in this instance reports a value as specified by that attribute description. |
|
Describes the set of QOS parameters defined in a managed device. DOCSIS 1.0 COS service profiles are not represented in this object. Each row corresponds to a DOCSIS QOS Parameter Set as signaled via DOCSIS MAC management messages.Each attribute of an instance of this object corresponds to one or part of oneService Flow Encoding. The BitMap attribute indicates which particular parameters were signaled in the original registration or dynamic service request message that created the QOS Parameter Set. In many cases, even if a QOS Parameter Set parameter was not signaled, the DOCSIS specification calls for a default value to be used. That default value is reported as the value of the corresponding attribute in this object instance. Many attributes are not applicable, depending on the Service Flow direction, upstream scheduling type or Service Flow bonding configuration. The attribute value reported in this case is specified by those attributes descriptions. |
|
Describes the set of DOCSIS-QOS Service Flows in a managed device. |
|
Describes statistics associated with the Service Flows in a managed device. |
|
Describes statistics associated with upstream service flows. All counted frames must be received without a Frame Check Sequence (FCS) error. |
|
Describes statistics associated with the Dynamic Service Flows, Dynamic Channel Changes and Dynamic Bonding Changes in a managed device within a MAC Domain. For each MAC Domain there are two instances for the for the upstream and downstream direction. On the CMTS, the downstream direction instance indicates messages transmitted or transactions originated by the CMTS. The upstream direction intance indicates messages received or transaction originated by the CM. On the CM, the downstream direction instance indicates messages received or transactions originated by the CMTS. The upstream direction instance indicates messages transmitted by the CM or transactions originated by the CM. |
|
Contains a log of the disconnected Service Flows in a managed device. |
|
Describes a provisioned service class on a CMTS. Each object instance defines a template for certain DOCSIS QOS Parameter Set values. When a CM creates or modifies an Admitted QOS Parameter Set for a Service Flow, it may reference a Service Class Name instead of providing explicit QOS Parameter Set values. In this case, the CMTS populates the QOS Parameter Set with the applicable corresponding values from the named Service Class. Subsequent changes to a Service Class row do not affect the QOS Parameter Set values of any service flows already admitted. A service class template applies to only a single direction, as indicated in the ServiceClassDirection attribute. |
|
Describes the set of payload header suppression of Service Flows. |
|
Provides the mapping of unicast service flows with the cable modem the service flows belongs to. |
|
Defines the SID clusters associated with an upstream service flow. |
|
Provides extensions to the service flow information for Group Service Flows (GSFs). |
|
Provides additional packet classification information for Group Classifier References (GCRs) in a Group Service Flow (GSF). |
|
Provides extensions for service flow statistics for fragmentation for channel bonding. |
|
Provides upstream service flow statistics for Continous Concatenation and Fragmentation (CCF). The CMTS MAY not instantate this object for service flows that do not use CCF or return the zero value on individual counter’s statistics. |
|
Defines DOCSIS MAC services primitive statistics of upstream service flows. In pre-3.0 DOCSIS devices this statistics exists per SID for either Cos or Qos services in the SNMP table docsIfCmServiceTable. A 3.0 CM with CoS configuration (DOCSIS 1.0 mode) reports the statistics defined in the SNMP table docsIfCmServiceTable. A 3.0 CM with QoS configuration reports this object regardless of whether Multiple Transmit Channel is enabled or disabled. |
|
Describes DSID information stored in the CMTS. The CMTS reports the current status of existing DSIDs. When a DSID is created during the registration process or a DBC transaction, a corresponding object instance is created. If a DSID is deleted or changed via a DBC message the corresponding object instance is deleted or updated respectively. |
|
The CMTS Debug DSID object contains the control of DSID debug statistics reporting An instance in this object defines the DSID and MAC domain to which the CmtsDebugDsidStats collects statistics for the downstream channel associated with that DSID and MAC Domain. The deletion of an instance stops the reporting of statistics for the specified DSID. This object supports instance creation and deletion. The CMTS MUST support at least one instance of this object. |
|
The CMTS Debug DSID Stats object describes statistics at the CMTS for the forwarding of DSID-labeled downstream packets. The CMTS creates an instance for every combination of MAC Domain, DSID value, and downstream channel on which packets labeled with that DSID are transmitted. The CMTS does not delete such instances while the corresponding CmtsDebug object control instance exists. |
|
When a DSID is created, during the registration process or a DBC transaction,. The CM reports the current status of existing DSID, for example, if a DSID is deleted or changed via DBC messages the corresponding object instance is deleted or updated respectively. |
|
Defines a set of statistics the CM collects per Dsid. |
|
Contains the client MAC addresses that the CMTS requests that the CM uses to replicate Multicast DSIDs during registration or during a DBC transaction. When a DSID is created that includes client MAC addresses, or when client MAC addresses are added to a DSID, new rows are created to indicate the added client MAC addresses. When a Client MAC address is deleted from a DSID, the corresponding row is deleted. When a DSID is deleted, all corresponding rows are deleted, too. |
MIB Constraints
Table 3-146 lists the constraints that the router places on DOCS-QOS3-MIB.
.
Table 3-146 DOCS-QOS3-MIB Constraints
|
|
|
|
- docsQos3PktClassFlowLabel
|
Not supported. |
- docsQos3PktClassCmInterfaceMask
|
Not supported. |
|
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. |
|
Identifies a unique set of QoS parameters. |
|
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. |
|
Not accessible. |
docsQos3CmtsDebugDsidTable
|
|
- docsQos3CmtsDebugDsidRowStatus
|
Valid values are: active(1), createAndGo(4), and destroy(6). |
|
|
|
Not accessible. |
- docsQos3PktClassFlowLabel
|
Not supported. |
docsQos3ParamSetMultiplierContentionReqWindow
|
Default value is eight (8). |
docsQos3GrpServiceFlowTable
|
The GSFs on the wideband interfaces are not supported. |
|
The GCRs in a GSF on the wideband interfaces are not supported. |
|
|
- docsQos3ParamSetServiceFlowId
|
Not accessible. |
docsQos3DynamicServiceStatsTable
|
|
|
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).
DOCS-QOS-MIB Tables and Objects
Table 3-147 lists DOCS-QOS-MIB Tables and Objects.
.
Table 3-147 DOCS-QOS-MIB Tables and Objects
|
|
|
Describes the packet classification configured on the CM or CMTS. |
|
Provides a single packet classifier rule. |
|
Index assigned to packet classifier entry by the CMTS which is unique per service flow. |
|
Indicates the direction to which the classifier is applied. |
|
The value specifies the order of evaluation of the classifiers. |
|
The low value of a range of TOS byte values. |
|
The 8-bit high value of a range of TOS byte values. |
|
The mask value is bitwise ANDed with TOS byte in an IP packet and this value is used check range checking of TosLow and TosHigh. |
docsQosPktClassIpProtocol
|
Indicates the value of the IP Protocol field required for IP packets to match this rule. |
docsQosPktClassIpSourceAddr
|
Deprecated in favor of the object pair docsQosPktClassInetSourceAddrType and docsQosPktClassInetSourceAddr. |
docsQosPktClassIpSourceMask
|
Deprecated in favor of the object pair docsQosPktClassInetSourceMaskType and docsQosPktClassInetSourceMask. |
docsQosPktClassIpDestAddr
|
Deprecated in favor of the object pair docsQosPktClassInetDestAddrType and docsQosPktClassInetDestAddr. |
docsQosPktClassIpDestMask
|
Deprecated in favor of the object pair docsQosPktClassInetDestMaskType and docsQosPktClassInetDestMask. |
docsQosPktClassSourcePortStart
|
Specifies the low end inclusive range of TCP/UDP source port numbers to which a packet is compared. |
docsQosPktClassSourcePortEnd
|
Specifies the high end inclusive range of TCP/UDP source port numbers to which a packet is compared. |
docsQosPktClassDestPortStart
|
Specifies the low end inclusive range of TCP/UDP destination port numbers to which a packet is compared. |
docsQosPktClassDestPortEnd
|
Specifies the high end inclusive range of TCP/UDP destination port numbers to which a packet is compared. |
docsQosPktClassDestMacAddr
|
An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsQosPktClassDestMacMask equals the value of docsQosPktClassDestMacAddr. |
docsQosPktClassDestMacMask
|
An Ethernet packet matches an entry when its destination MAC address bitwise ANDed with docsQosPktClassDestMacMask equals the value of docsQosPktClassDestMacAddr. |
docsQosPktClassSourceMacAddr
|
An Ethernet packet matches this entry when its source MAC address equals the value of this object. |
docsQosPktClassEnetProtocolType
|
Indicates the format of the layer 3 protocol id in the Ethernet packet. A value of none(0) means that the rule does not use the layer 3 protocol type as a matching criteria. |
docsQosPktClassEnetProtocol
|
If docsQosEthPktClassProtocolType is none(0), this object is ignored when considering whether a packet matches the current rule. |
docsQosPktClassUserPriApplies
|
This object is obsolete. |
docsQosPktClassUserPriLow
|
Applies only to Ethernet frames using the 802.1P/Q tag header (indicated with EtherType 0x8100). |
docsQosPktClassUserPriHigh
|
Applies only to Ethernet frames using the 802.1P/Qtag header (indicated with EtherType 0x8100). |
|
Applies only to Ethernet frames using the 802.1P/Q tag header. |
|
Indicates whether or not the classifier is enabled to classify packets to a Service Flow. |
|
Counts the number of packets that have been classified using this entry. |
|
Indicates which parameter encodings were actually present in the DOCSIS packet classifier encoding signaled in the DOCSIS message that created or modified the classifier. |
docsQosPktClassInetSourceAddrType
|
The type of the internet address for docsQosPktClassInetSourceAddr. |
docsQosPktClassInetSourceAddr
|
Specifies the value of the IP Source Address required for packets to match this rule. |
docsQosPktClassInetSourceMaskType
|
The type of the internet address for docsQosPktClassInetSourceMask. |
docsQosPktClassInetSourceMask
|
Specifies which bits of a packet's IP Source Address that are compared to match this rule. |
docsQosPktClassInetDestAddrType
|
The type of the internet address for docsQosPktClassInetDestAddr. |
docsQosPktClassInetDestAddr
|
Specifies the value of the IP Destination Address required for packets to match this rule. |
docsQosPktClassInetDestMaskType
|
The type of the internet address for docsQosPktClassInetDestMask. |
docsQosPktClassInetDestMask
|
Specifies which bits of a packet's IP Destination Address that are compared to match this rule. |
|
Describes the set of DOCSIS 1.1 QOS parameters defined in a managed device. |
|
A unique set of QOS parameters. |
docsQosParamSetServiceClassName
|
Refers to the Service Class Name that the parameter set values were derived. |
|
The relative priority of a service flow, Higher numbers indicate higher priority. |
docsQosParamSetMaxTrafficRate
|
Maximum sustained traffic rate allowed for this service flow in bits/sec. |
docsQosParamSetMaxTrafficBurst
|
Specifies the token bucket size in bytes for this parameter set. |
docsQosParamSetMinReservedRate
|
Specifies the guaranteed minimum rate in bits/sec for this parameter set. |
docsQosParamSetMinReservedPkt
|
Specifies an assumed minimum packet size in bytes for which the docsQosParamSetMinReservedRate will be provided. |
docsQosParamSetActiveTimeout
|
Specifies the maximum duration in seconds that resources remain unused on an active service flow before CMTS signals that both active and admitted parameters set are null. |
docsQosParamSetAdmittedTimeout
|
Specifies the maximum duration in seconds that resources remain in admitted state before resources must be released. |
docsQosParamSetMaxConcatBurst
|
Specifies the maximum concatenated burst in bytes which an upstream service flow is allowed. |
docsQosParamSetSchedulingType
|
Specifies the upstream scheduling service used for upstream service flow. |
docsQosParamSetNomPollInterval
|
Specifies the nominal interval in microseconds between successive unicast request opportunities on an upstream service flow. |
docsQosParamSetTolPollJitter
|
Specifies the maximum amount of time in microseconds that the unicast request interval may be delayed from the nominal periodic schedule on an upstream service flow. |
docsQosParamSetUnsolicitGrantSize
|
Specifies the unsolicited grant size in bytes. |
docsQosParamSetNomGrantInterval
|
Specifies the nominal interval in microseconds between successive data grant opportunities on an upstream service flow. |
docsQosParamSetTolGrantJitter
|
Specifies the maximum amount of time in microseconds that the transmission opportunities may be delayed from the nominal periodic schedule. |
docsQosParamSetGrantsPerInterval
|
Specifies the number of data grants per Nominal Grant Interval (docsQosParamSetNomGrantInterval). |
docsQosParamSetTosAndMask
|
Specifies the AND mask for IP TOS byte for overwriting IP packets TOS value. |
|
Specifies the OR mask for IP TOS byte. See the description of docsQosParamSetTosAndMask for further details. |
docsQosParamSetMaxLatency
|
Specifies the maximum latency between the reception of a packet by the CMTS on its NSI and the forwarding of the packet to the RF interface. |
|
Defines the type of the QOS parameter set defined by this row. |
docsQosParamSetRequestPolicyOct
|
Specifies which transmit interval opportunities the CM omits for upstream transmission requests and packet transmissions. |
|
This object indicates the set of QOS Parameter Set parameters actually signaled in the DOCSIS registration or dynamic service request message that created or modified the QOS Parameter Set. |
|
Describes the set of Docsis-QOS Service Flows in a managed device. |
|
Describes a service flow. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127). |
|
An index assigned to a service flow by CMTS. |
docsQosServiceFlowProvisionedParamSetIndex
|
This object is obsolete. |
docsQosServiceFlowAdmittedParamSetIndex
|
This object is obsolete. |
docsQosServiceFlowActiveParamSetIndex
|
This object is obsolete. |
|
Service Identifier (SID) assigned to an admitted or active service flow. |
docsQosServiceFlowDirection
|
The direction of the service flow. |
docsQosServiceFlowPrimary
|
Object reflects whether service flow is the primary or a secondary service flow. |
docsQosServiceFlowActiveTimeout
|
This object is obsolete. |
docsQosServiceFlowAdmittedTimeout
|
This object is obsolete. |
docsQosServiceFlowSchedulingType
|
This object is obsolete. |
docsQosServiceFlowRequestPolicy
|
This object is obsolete. |
docsQosServiceFlowTosAndMask
|
This object is obsolete. |
docsQosServiceFlowTosOrMask
|
This object is obsolete. |
docsQosServiceFlowStatsTable
|
This table describes statistics associated with the Service Flows in a managed device. |
docsQosServiceFlowStatsEntry
|
Describes a set of service flow statistics. |
|
The number of Packet Data PDUs classified to this service flow. |
|
The number of octets transmitted on the Docsis RF network from the byte after the MAC header HCS to the end of the CRC for all packets counted in the docsQosServiceFlowPkts object for this row. |
docsQosServiceFlowTimeCreated
|
The value of sysUpTime when the service flow was created. |
docsQosServiceFlowTimeActive
|
The total time that service flow has been active. |
docsQosServiceFlowPHSUnknowns
|
The number of packets received on the service flow with an unknown payload header suppression index. |
docsQosServiceFlowPolicedDropPkts
|
The number of packets dropped due to policing of the service flow, especially to limit the maximum rate of the flow. |
docsQosServiceFlowPolicedDelayPkts
|
The number of packet delayed due to policing of the service flow, especially to limit the maximum rate of the flow. |
docsQosUpstreamStatsTable
|
Describes statistics associated with upstream service flows. |
docsQosUpstreamStatsEntry
|
Describes a set of upstream service flow statistics. An entry in the table exists for each upstream Service Flow in a managed device. |
|
Identifies a service id for an admitted or active upstream service flow. |
|
The number of fragmentation headers received on an upstream service flow, regardless of whether the fragment was correctly reassembled into a valid packet. |
docsQosUpstreamFragDiscards
|
The number of upstream fragments discarded and not assembled into a valid upstream packet. |
docsQosUpstreamConcatBursts
|
The number of concatenation headers received on an upstream service flow. |
ocsQosDynamicServiceStatsTable
|
Describes statistics associated with the Dynamic Service Flows in a managed device. |
docsQosDynamicServiceStatsEntry
|
Describes a set of dynamic service flow statistics. |
|
The direction of interface. |
|
The number of Dynamic Service Addition Requests,including retries. |
|
The number of Dynamic Service Addition Responses, including retries. |
|
The number of Dynamic Service Addition Acknowledgements, including retries. |
|
The number of Dynamic Service Change Requests, including retries. |
|
The number of Dynamic Service Change Responses, including retries. |
|
The number of Dynamic Service Change Acknowledgements, including retries. |
|
The number of Dynamic Service Delete Requests, including retries. |
|
The number of Dynamic Service Delete Responses, including retries. |
|
The number of successful Dynamic Service Addition transactions. |
|
The number of failed Dynamic Service Addition transactions. |
|
The number of successful Dynamic Service Change transactions. |
docsQosDynamicChangeFails
|
The number of failed Dynamic Service Change transactions. |
|
The number of successful Dynamic Service Delete transactions. |
docsQosDynamicDeleteFails
|
The number of failed Dynamic Service Delete transactions. |
|
The number of Dynamic Channel Change Request messages traversing an interface. |
|
The number of Dynamic Channel Change Response messages traversing an interface. |
|
The number of Dynamic Channel Change Acknowledgement messages traversing an interface. |
|
The number of successful Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows. |
|
The number of failed Dynamic Channel Change transactions. |
|
The number of Dynamic Channel Change Response (depart) messages traversing an interface. |
|
The number of Dynamic Channel Change Response (arrive) messages traversing an interface. This count is only counted on upstream direction rows. This count should include number of retries. |
docsQosServiceFlowLogTable
|
Contains a log of the disconnected Service Flows in a managed device. |
docsQosServiceFlowLogEntry
|
The information regarding a single disconnected service flow. |
docsQosServiceFlowLogIndex
|
Unique index for a logged service flow. |
docsQosServiceFlowLogIfIndex
|
The ifIndex of ifType docsCableMaclayer(127) on the CMTS where the service flow was present. |
docsQosServiceFlowLogSFID
|
The ifIndex of ifType docsCableMaclayer(127) on the CMTS where the service flow was present. index assigned to the service flow by the CMTS. |
docsQosServiceFlowLogCmMac
|
The MAC address for the cable modem associated with the service flow. |
docsQosServiceFlowLogPkts
|
The number of packets counted on this service flow after payload header suppression. |
docsQosServiceFlowLogOctets
|
The number of octets counted on this service flow after payload header suppression. |
docsQosServiceFlowLogTimeCreated
|
The value of sysUpTime when the service flow was created. |
docsQosServiceFlowLogTimeActive
|
The total time that service flow was active. |
docsQosServiceFlowLogDirection
|
The value of docsQosServiceFlowDirection for the service flow. |
docsQosServiceFlowLogPrimary
|
The value of docsQosServiceFlowPrimary for the service flow. |
docsQosServiceFlowLogServiceClassName
|
The value of docsQosParamSetServiceClassName for the provisioned QOS Parameter Set of the service flow. |
docsQosServiceFlowLogPolicedDropPkts
|
The final value of docsQosServiceFlowPolicedDropPkts for the service flow. |
docsQosServiceFlowLogPolicedDelayPkts
|
The final value of docsQosServiceFlowPolicedDelayPkts for the service flow. |
docsQosServiceFlowLogControl
|
Setting this object to the value destroy(6) removes this entry from the table. |
|
This table describes the set of Docsis-QOS Service Classes in a CMTS. |
|
A provisioned service class on a CMTS. Each entry defines a template for certain DOCSIS QOS Parameter Set values. |
|
Service Class Name. DOCSIS specifies that the maximum size is 15 printable ASCII characters with a terminating zero. |
docsQosServiceClassParamSetIndex
|
This object is obsolete. |
docsQosServiceClassStatus
|
Used to create or delete rows in this table. |
docsQosServiceClassPriority
|
Contains template for docsQosParamSetPriority. |
docsQosServiceClassMaxTrafficRate
|
Contains template for docsQosParamSetMaxTrafficRate. |
docsQosServiceClassMaxTrafficBurst
|
Contains template for docsQosParamSetMaxTrafficBurst. |
docsQosServiceClassMinReservedRate
|
Contains template for docsQosParamSEtMinReservedRate. |
docsQosServiceClassMinReservedPkt
|
Contains template for docsQosParamSetMinReservedPkt. |
docsQosServiceClassMaxConcatBurst
|
Template for docsQosParamSetMaxConcatBurst. |
docsQosServiceClassNomPollInterval
|
Contains template for docsQosParamSetNomPollInterval. |
docsQosServiceClassTolPollJitter
|
Contains templatefor docsQosParamSetTolPollJitter. |
docsQosServiceClassUnsolicitGrantSize
|
Contains template for docsQosParamSetUnsolicitGrantSize. |
docsQosServiceClassNomGrantInterval
|
Contains template for docsQosParamSetNomGrantInterval. |
ocsQosServiceClassTolGrantJitter
|
Contains template for docsQosParamSetTolGrantJitter. |
ocsQosServiceClassGrantsPerInterval
|
Contains template for docsQosParamSetGrantsPerInterval. |
docsQosServiceClassMaxLatency
|
Contains template for docsQosParamSetClassMaxLatency. |
docsQosServiceClassActiveTimeout
|
Contains template for docsQosParamSetActiveTimeout. |
docsQosServiceClassAdmittedTimeout
|
Contains template for docsQosParamSetAdmittedTimeout. |
docsQosServiceClassSchedulingType
|
Contains template for docsQosParamSetSchedulingType. |
docsQosServiceClassRequestPolicy
|
Contains template for docsQosParamSetRequestPolicyOct. |
docsQosServiceClassTosAndMask
|
Contains template for docsQosParamSetTosAndMask. |
docsQosServiceClassTosOrMask
|
Contains template for docsQosParamSetTosOrMask. |
docsQosServiceClassDirection
|
Specifies whether the service class template applies to upstream or downstream service flows. |
docsQosServiceClassPolicyTable
|
Describes the set of Docsis-QOS Service Class Policies. |
docsQosServiceClassPolicyEntry
|
A service class name policy entry. |
ocsQosServiceClassPolicyIndex
|
Index value to uniquely identify an entry in this table. |
docsQosServiceClassPolicyName
|
Service Class Name to identify the name of the service class flow to which the packet should be directed. |
docsQosServiceClassPolicyRulePriority
|
Service Class Policy rule priority for the entry. |
docsQosServiceClassPolicyStatus
|
Used to create or delete rows in this table. |
|
This table describes set of payload header suppression entries. |
|
A payload header suppression entry. The ifIndex is an ifType of docsCableMaclayer(127). The index docsQosServiceFlowId selects one service flow from the cable MAC layer interface. The docsQosPktClassId index matches an index of the docsQosPktClassTable. |
|
Payload header suppression field defines the bytes of the header which must be suppressed/restored by the sending/receiving device. |
|
Payload header suppression mask defines the bit mask which used in combination with the docsQosPHSField defines which bytes in header must be suppressed/restored by the sending or receiving device. |
|
Payload header suppression size specifies the number of bytes in the header to be suppressed and restored. |
|
Payload header suppression verification value of 'true' the sender must verify docsQosPHSField is the same as what is contained in the packet to be suppressed. |
docsQosPHSClassifierIndex
|
This object is obsolete. |
|
Payload header suppression index uniquely references the PHS rule for a given service flow. |
docsQosCmtsMacToSrvFlowTable
|
This table provide for referencing the service flows associated with a particular cable modem. |
docsQosCmtsMacToSrvFlowEntry
|
An entry is created by CMTS for each service flow connected to this CMTS. |
|
Contains MAC address for the referenced CM. |
|
Contains index assigned to a service flow by CMTS. |
|
The ifIndex of ifType docsCableMacLayter(127) on the CMTS that is connected to the Cable Modem. |
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-148 lists the constraints that the router places on DOCS-QOS-MIB.
.
Table 3-148 DOCS-QOS-MIB Constraints
|
|
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. |
|
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. |
|
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)." |
|
This table describes set of payload header suppression entries. |
|
|
|
|
|
An entry in this table that provides a single packet classifier rule. |
|
|
- 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) |
|
Read-only.The number of Dynamic Channel Change Request messages traversing an interface. This count is nonzero only on downstream direction rows. |
|
Read-only. The number of Dynamic Channel Change Response messages traversing an interface. This count is nonzero only on upstream direction rows. |
|
Read-only. The number of Dynamic Channel Change Acknowledgement messages traversing an interface. This count is nonzero only on downstream direction rows. |
|
Read-only. The number of successful Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows. |
|
Read-only. The number of failed Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows. |
**The SNMP query sessions have been improved in these tables. |
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-SEC-MIB Tables and Objects
Table 3-149 lists DOCS-SEC-MIB Tables and Objects.
.
Table 3-149 DOCS-SEC-MIB Tables and Objects
|
|
docsSecCmtsCmEaeExclusionTable
|
Defines a list of CMs or CM groups to exclude from Early Authentication and Encryption (EAE). This object allows overrides to the value of EAE Control for individual CMs or group of CMs for purposes such as debugging. The CMTS supports a minimum of 30 instances of the CmtsCmEaeExclusion object. This object is only applicable when the EarlyAuthEncryptCtrl attribute of the MdCfg object is enabled. This object supports the creation and deletion of multiple instances. |
|
Defines a read-only set of SAV policies associated with a CM that the CMTS will use in addition to the CMTS verification of an operator assigned IP Address being associated with a CM. When the CMTS has not resolved a source address of a CM CPE, the CMTS verifies if the CM CPE is authorized to pass traffic based on this object. These object policies include a list of subnet prefixes (defined in the SavStaticList object) or a SAV Group Name that could reference a CMTS configured list of subnet prefixes (defined in SavCfgList object) or vendor-specific policies. The CMTS populates the attributes of this object for a CM from that CM’s config file. This object is only applicable when the SrcAddrVerificationEnabled attribute of the MdCfg object is ’true’ and the CmAuthEnable attribute of the CmtsSavCtrl object is ’true’. The CMTS is not required to persist instances of this object across reinitializations. |
|
Defines the CMTS configured subnet prefix extension to the SavCmAuth object. This object supports the creation and deletion of multiple instances. Creation of a new instance of this object requires the PrefixAddrType and PrefixAddr attributes to be set. |
docsSecSavStaticListTable
|
Defines a subnet prefix extension to the SavCmAuth object based on CM statically signaled subnet prefixes to the CMTS. When a CM signals to the CMTS static subnet prefixes, the CMTS must create a List Id to be referenced by the CM in the SavCmAuth StaticPrefixListId attribute, or the CMTS may reference an existing List Id associated to previously registered CMs in case of those subnet prefixes associated with the List Id match the ones signaled by the CM. |
docsSecCmtsCmSavStatsTable
|
Provides a read-only list of SAV counters for different service theft indications. |
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 the base 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.
DOCS-SUBMGT3-MIB Tables and Objects
Table 3-150 lists CISCO-LEC-EXT-MIB Tables and Objects.
.
Table 3-150 DOCS-SUBMGT3-MIB Tables and Objects
|
|
docsSubMgtStbFilterUpDefault
|
Maintains per-CM traffic policies enforced by the CMTS. The CMTS acquires the CM traffic policies through the CM registration process, or in the absence of some or all of those parameters, from the Base object. The CM information and controls are meaningful and used by the CMTS, but only after the CM is operational. |
docsSubMgtStbFilterUpDefault
|
Defines the list of IP Addresses behind the CM known by the CMTS. If the Active attribute of the CpeCtrl object associated with a CM is set to ’true’ and the CMTS receives an IP packet from a CM that contains a source IP address that does not match one of the CPE IP addresses associated with this CM, one of two things occurs. If the number of CPE IPs is less than the MaxCpeIp of the CpeCtrl object for that CM, the source IP address is added to this object and the packet is forwarded; otherwise, the packet is dropped. |
docsSubMgtStbFilterUpDefault
|
Defines the set of downstream and upstream filter groups that the CMTS applies to traffic associated with that CM. |
docsSubMgtStbFilterUpDefault
|
Describes a set of filter or classifier criteria. Classifiers are assigned by group to the individual CMs. That assignment is made via the ’Subscriber Management TLVs’ encodings sent upstream from the CM to the CMTS during registration or in their absence, default values configured in the CMTS. A Filter Group ID (GrpId) is a set of rules that correspond to the expansion of a UDC Group ID into UDC individual classification rules. The Filter Group Ids are generated whenever the CMTS is configured to send UDCs during the CM registration process. Implementation of L2 classification criteria is optional for the CMTS; LLC/MAC upstream and downstream filter criteria can be ignored during the packet matching process. |
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.
DOCS-SUBMGT-MIB Tables and Objects
Table 3-151 lists DOCS-SUBMGT-MIB Tables and Objects.
.
Table 3-151 DOCS-SUBMGT-MIB Tables and Objects
|
|
docsSubMgtCpeControlTable
|
Extends the docsIfCmtsCmStatusTable and adds 4 objects which reflect the state of subscriber management on a particular CM. |
|
Contains CPE IP addresses known on a per CM basis. |
|
Contains filter or classifier criteria. Classifiers are assigned by group to the individual CMs. That assignment is made via the configuration objects sent upstream from the CM to the CMTS during registration. |
docsSubMgtTcpUdpFilterTable
|
This is an adjunct to docsSubMgtPktFilterTable. It provides optional filtering based on elements in TCP or UDP headers. This table is separate from docsSubMgtPktFilterTable only because it is expected to be used more rarely. This table is not consulted unless the upper-layer protocol is TCP, UDP, or ’any’. |
|
Identifies for each modem the upstream and downstream filter groups that apply to packets for that modem. Zero is used as a distinguished value to mean no filter group. |
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-152 lists the constraints that the router places on DOCS-SUBMGT-MIB.
.
Table 3-152 DOCS-SUBMGT-MIB Constraints
|
|
|
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).
DOCS-TEST-MIB Tables and Objects
Table 3-153 lists DOCS-TEST-MIB Tables and Objects.
.
Table 3-153 DOCS-TEST-MIB Tables and Objects
|
|
|
Indicates the ability of this device to support the programmable features identified by the TYPE field from the CM/CMTS TLV table in [17]. |
|
Indicates the current operating status of tests initiated through the docsTestSetupObjects. |
|
Corresponds to the TYPE field from the CM/CMTS TLV Table in [17]. |
|
The OCTET STRING length and value correspond to the LENGTH and VALUE fields from the CM/CMTS TLV Table in [17]. |
|
Used to initiate or stop the tests setup through the docsTestType and docsTestData objects. |
MIB Constraints
Table 3-154 lists the constraints that the router places on DOCS-TEST-MIB.
.
Table 3-154 DOCS-TEST-MIB Constraints
|
|
|
|
|
Read-only. |
|
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.
DOCS-L2VPN-MIB Tables and Objects
Table 3-155 lists DOCS-L2VPN-MIB Tables and Objects.
.
Table 3-155 DOCS-L2VPN-MIB Tables and Objects
|
|
docsIfExt2CmtsUpChannelTotalCMs
|
Table indexed by the octet string DocsL2vpnIdentifier that provides the local agent’s internally assigned docsL2vpnIdx value for that DocsL2vpnIdentifier value. The mapping of DocsL2vpnIdentifier to docsL2vpnIdx is 1-1. The agent must instantiate a row in both docsL2vpnIndexToIdTable and docsL2vpnIdToIndexTable for each known L2VPN Identifier. |
docsIfExt2CmtsUpChannelTotalCMs
|
Table indexed by agent’s local docsL2vpnIdx that provides the global L2VPN Identifier. The mapping of docsL2vpnIdx to DocsL2vpnIdentifier is 1-1. The agent must instantiate a row in both docsL2vpnIndexToIdTable and docsL2vpnIdToIndexTable for each known L2VPN. |
docsIfExt2CmtsUpChannelTotalCMs
|
Describes L2VPN per-CM information that is in common with all L2VPNs for the CM, regardless of forwarding mode. |
docsIfExt2CmtsUpChannelTotalCMs
|
Describes the operation of L2VPN forwarding on each CM. |
docsIfExt2CmtsUpChannelTotalCMs
|
Contains statistics for forwarding of packets to and from a CM on each VPN. |
docsIfExt2CmtsUpChannelTotalCMs
|
Displays summary information for the run-time state of each VPN that is currently operating on each bridge port. |
docsIfExt2CmtsUpChannelTotalCMs
|
Displays SF-specific L2VPN forwarding status for each upstream service flow configured with a per-SF L2VPN Encoding. Objects which were signaled in a per-SF L2VPN Encoding but apply for the entire CM are shown in the docsL2vpnVpnCmTable. |
docsIfExt2CmtsUpChannelTotalCMs
|
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. |
docsIfExt2CmtsUpChannelTotalCMs
|
Describes the NSI configuration for a single CM when operating in point-to-point forwarding mode for an L2VPN. |
docsIfExt2CmtsUpChannelTotalCMs
|
Contains a list of CPEs, indexed by the VPNs on a Cable Modem. |
docsIfExt2CmtsUpChannelTotalCMs
|
Contains a list of bridging CPEs, indexed by L2VPN Index and the corresponding CMs on that VPN. |
docsIfExt2CmtsUpChannelTotalCMs
|
Contains packet counters for Unicast MAC Addresses within a VPN. |
docsIfExt2CmtsUpChannelTotalCMs
|
Contains packet counters for Multicast MAC Addresses within a VPN. |
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-156 .
- dtiPathTraceabilityTable—Refer to Table 3-157 .
- entPhysicalTable—Refer to these tables:
– Table 3-163 —entPhysicalTable Entries for the Cisco DTI Card
– Table 3-164 —entPhysicalTable Entries for Cisco DTI Ports
– Table 3-165 —entAliasMappingTable Entries for DTI Interfaces
Table 3-156 dtiProtocolEntityType Entries
|
|
|
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-157 dtiPathTraceabilityTable Entries
|
|
|
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 4133, 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).
ENTITY-MIB Tables and Objects
The following table lists ENTITY-MIB Tables and Objects.
Table 3-158 ENTITY-MIB Tables and Objects
|
|
|
Contains one row per physical entity. There is always at least one row for an ’overall’ physical entity. |
|
Contains one row per logical entity. For agents that implement more than one naming scope, at least one entry must exist. Agents which instantiate all MIB objects within a single naming scope are not required to implement this table. |
|
Contains zero or more rows of logical entity to physical equipment associations. For each logical entity known by this agent, there are zero or more mappings to the physical resources, which are used to realize that logical entity. An agent should limit the number and nature of entries in this table such that only meaningful and non-redundant information is returned. |
|
Contains zero or more rows, representing mappings of logical entity and physical component to external MIB identifiers. Each physical port in the system may be associated with a mapping to an external identifier, which itself is associated with a particular logical entity’s naming scope. A ’wildcard’ mechanism is provided to indicate that an identifier is associated with more than one logical entity. |
|
Exposes the container/’containee’ relationships between physical entities. This table provides all the information found by constructing the virtual containment tree for a given entPhysicalTable, but in a more direct format. |
MIB objects and related constraints introduced in Cisco IOS Release 12.2(33)SCC are included in Table 3-166 .
The MIB attributes for the various physical entities of uBR-MC3GX60V card in Cisco IOS Release 12.2(33)SCE are included in:
- Table 3-159 —entPhysicalTable Entries for the 3Gx60 Line Card
- Table 3-160 —entPhysicalTable Entries for 3Gx60 Ports
- Table 3-161 —entPhysicalTable Entries for 3Gx60 Controller
- Table 3-162 —entPhysicalTable Entries for 3Gx60 SFP
Table 3-159 entPhysicalTable Entries for the 3Gx60 Line Card for Cisco IOS Release 12.2(33)SCE
|
|
|
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 uBR-MC3GX60V 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-160 entPhysicalTable Entries for uBR-MC3Gx60V Port for Cisco IOS Release 12.2(33)SCE
|
|
|
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-161 entPhysicalTable Entries for uBR-MC3GX60V Controller for Cisco IOS Release 12.2(33)SCE
|
|
|
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. |
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-162 entPhysicalTable Entries for UBR-3GX60V SFP for Cisco IOS Release 12.2(33)SCE
|
|
|
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-163 entPhysicalTable Entries for the DTI Line Card in Cisco IOS Release 12.2(33)SCC
|
|
|
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-164 entPhysicalTable Entries for the DTI Ports in Cisco IOS Release 12.2(33)SCC
|
|
|
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 contained in 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-165 entAliasMappingTable Entries for DTI interfaces
|
|
|
entAliasLogicalIndexOrZero |
0 |
Logical index. |
entAliasMappingIdentifier |
ifIndex.<ifIndex#> |
ifindex# is corresponding DTI interface's index. |
Starting with Cisco IOS Release 12.2(33)SCF, the ifIndex object (entAliasMappingIdentifier), in addition to pointing the interfaces, now points to the RF channel SNMP IF Index in table EntAliasMappingTable.
Querying the EntAliasMappingTable displays the cable interfaces and RF channels for the Cisco uBR-MC3GX60V, Cisco UBR-MC20X20V, and Cisco uBR-MC88V line cards and SPAs.
Note In Cisco IOS Release 12.2(33)SCE and earlier releases, the ifIndex object pointed to the Fast Ethernet interface or the Gigabit Ethernet interface, the cable mac-domain interface, the cable downstream or upstream channel of the cable interface or the Integrated cable or Modular cable SNMP IF Index.
MIB Constraints
.
Table 3-166 ENTITY-MIB Constraints Prior to Cisco IOS Release 12.2(33)SCC
|
|
|
This table does not include the NPE on the Cisco uBR7200 series routers until Cisco IOS Release 12.2(8)BC1 and later releases. |
|
Not implemented. |
|
Not implemented. |
|
Not implemented. |
|
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. |
|
- Supports the Cisco Unique Device Identifier (UDI).
- Contains the Version Identifier (VID).
|
|
- Supports the Cisco Unique Device Identifier (UDI).
- Contains the orderable Product Identifier (PID).
|
|
- 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. |
|
- 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.
|
|
This object describes the Cisco uBR10012 router either as UBR10000 or UBR10012, depending on Cisco IOS release. |
|
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. |
|
Not implemented. |
|
- 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”.
|
The entPhysicalTable and entAliasMappingTable objects are automatically updated whenever a card is removed or inserted into a slot or when you enter a command at the CLI prompt that affects the operation of the card. |
Cisco uBR100012 SPA-24XWBD-SFP Shared Port Adapter
Table 3-167 lists physical entities and values for the Cisco uBR100012 CMTS SPA-24XWBD-SFP.
Table 3-167 entPhysicalTable Objects for Cisco Ubr100012 SPA-24XWBD-SFP
|
|
|
|
|
Shared Port Adapter Card Container |
container (5) |
cevContainerSPABay |
slot 1/0/2 |
|
WIDEBAND DOCSIS SPA |
module(9) |
cevSpa24xWbdSfp |
SPA bay 1/2 |
True(1) (represents a field-replaceable unit) |
Copper GigE SFP |
module(9) |
cevSFP1000BaseT |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 1/2/0:1 |
True(1) |
Short wavelength GigE SFP |
module(9) |
cevSFP1000BaseSx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 1/2/0:1 |
True(1) |
Long wavelength GigE SFP |
module(9) |
cevSFP1000BaseLx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 1/2/0:1 |
True(1) |
Extended reach GigE SFP 1000BaseZx |
module(9) |
cevSFP1000BaseZx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 1/2/0:1 |
True(1) |
Cisco Next Generation Wideband SPA Card
Table 3-168 lists physical entities and values for the Cisco Next Generation Wideband SPA card.
Table 3-168 entPhysicalTable Objects for Cisco Next Generation Wideband SPA Card
|
|
|
|
|
Shared Port Adapter Card Container |
container (5) |
cevContainerSPABay |
slot 3/0/3 |
|
DOCSIS HD SPA |
module(9) |
cevSpaHDwbdSfp |
SPA bay 3/3 |
True(1) (represents a field-replaceable unit) |
Copper GigE SFP |
module(9) |
cevSFP1000BaseT |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 3/3/0:0 |
True(1) |
Short wavelength GigE SFP |
module(9) |
cevSFP1000BaseSx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 3/3/0:0 |
True(1) |
Long wavelength GigE SFP |
module(9) |
cevSFP1000BaseLx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 3/3/0:0 |
True(1) |
Extended reach GigE SFP 1000BaseZx |
module(9) |
cevSFP1000BaseZx |
SFP slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP 3/3/0:0 |
True(1) |
10G LR SFP |
module (9) |
cevSFP10GLR |
SFP+ slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP+ 1/1/0:1 |
True (1) |
10G LRM SFP |
module (9) |
cevSFP10GLRM |
SFP+ slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP+ 1/1/0:1 |
True (1) |
10G SR SFP |
module (9) |
cevSFP10GSR |
SFP+ slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP+ 1/1/0:1 |
True (1) |
10G USR SFP |
module (9) |
cevSFP10GUSR |
SFP+ slot/sub-slot/unit:port Where port can be 0 or 1. For example, SFP+ 1/1/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 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-169 provides information about the entities contained in chassis slots on the Cisco uBR10012 router.
Table 3-169 Cisco uBR10012 Router Chassis Slot Contents
|
|
|
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.
ENTITY-SENSOR-MIB Tables and Objects
Table 3-170 lists ENTITY-SENSOR-MIB Tables and Objects.
.
Table 3-170 ENTITY-SENSOR-MIB Tables and Objects
|
|
|
Contains one row per physical sensor represented by an associated row in the entPhysicalTable. |
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).
ETHERLIKE-MIB Tables and Objects
Table 3-171 lists ETHERLIKE-MIBTables and Objects.
.
Table 3-171 ETHERLIKE-MIB Tables and Objects
|
|
|
Contains statistics for a collection of ethernet-like interfaces attached to a particular system. |
|
Statistics for a particular interface to an ethernet-like medium. |
|
Contains an index value that uniquely identifies an interface to an ethernet-like medium. |
|
Contains a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. |
|
Contains a count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
dot3StatsSingleCollisionFrames
|
Contains a count of frames that are involved in a single collision, and are subsequently transmitted successfully. |
dot3StatsMultipleCollisionFrames
|
Contains a count of frames that are involved in more than one collision and are subsequently transmitted successfully. |
|
Contains a count of times that the SQE TEST ERROR is received on a particular interface. |
dot3StatsDeferredTransmissions
|
Contains a count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. |
|
The number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet. |
dot3StatsExcessiveCollisions
|
Contains a count of frames for which transmission on a particular interface fails due to excessive collisions. |
dot3StatsInternalMacTransmitErrors
|
Contains a count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. |
dot3StatsCarrierSenseErrors
|
The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. |
|
Contains a count of frames received on a particular interface that exceed the maximum permitted frame size. |
dot3StatsInternalMacReceiveErrors
|
Contains a count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. |
|
Contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. |
|
For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. |
|
The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. |
dot3StatsRateControlAbility
|
"'true' for interfaces operating at speeds above 1000 Mb/s that support Rate Control through lowering the average data rate of the MAC sublayer, with frame granularity, and 'false' otherwise." |
dot3StatsRateControlStatus
|
Contains the current Rate Control mode of operation of the MAC sublayer of this interface. |
|
Contains a collection of collision histograms for a particular set of interfaces. |
|
Contains a cell in the histogram of per-frame collisions for a particular interface. |
|
Contains number of per-frame media collisions for which a particular collision histogram cell represents the frequency on a particular interface. |
|
Contains a count of individual MAC frames for which the transmission (successful or otherwise) on a particular interface occurs after the frame has experienced exactly the number of collisions in the associated dot3CollCount object. |
|
Contains descriptive and status information about the MAC Control sublayer on the ethernet-like interfaces attached to a particular system. |
|
Contains information about the MAC Control sublayer on a single ethernet-like interface. |
dot3ControlInUnknownOpcodes
|
Contains a count of MAC Control frames received on this interface that contain an opcode that is not supported by this device. |
dot3HCControlInUnknownOpcodes
|
Contains a count of MAC Control frames received on this interface that contain an opcode that is not supported by this device. |
|
Contains descriptive and status information about the MAC Control PAUSE function on the ethernet-like interfaces attached to a particular system. |
|
Containing information about the MAC Control PAUSE function on a single ethernet-like interface. |
|
Used to configure the default administrative PAUSE mode for this interface. |
|
Reflects the PAUSE mode currently in use on this interface. |
|
Contains a count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation. |
|
Contains a count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. |
|
Contains a count of MAC Control frames received on this interface with an opcode indicating the PAUSE operation. |
|
Contains a count of MAC Control frames transmitted on this interface with an opcode indicating the PAUSE operation. |
|
Contains 64-bit versions of error counters from the dot3StatsTable. |
|
An entry containing 64-bit statistics for a single ethernet-like interface. |
dot3HCStatsAlignmentErrors
|
Contains a count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. |
|
Contains a count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
dot3HCStatsInternalMacTransmitErrors
|
Contains a count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. |
|
Contains a count of frames received on a particular interface that exceed the maximum permitted frame size. |
dot3HCStatsInternalMacReceiveErrors
|
Contains a count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. |
|
For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. |
MIB Constraints
Table 3-172 lists the constraints that the router places on ETHERLIKE-MIB.
.
Table 3-172 ETHERLIKE-MIB Constraints
|
|
|
|
- dot3StatsCarrierSenseErrors
|
Implemented starting in Cisco IOS Release 12.2(15)BC2 and later releases. It returns NULL in earlier releases. |
|
Not implemented and is always 0. |
- dot3StatsInternalMacTransmitErrors
|
Not implemented and is always 0. |
|
Deprecated and is always NULL |
|
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. |
|
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).
Table 3-173 lists EVENT-MIB Tables and Objects.
.
Table 3-173 EVENT-MIB Tables and Objects
|
|
mteResourceSampleInstances
|
Contains the number of currently active instance entries as defined for mteResourceSampleInstanceMaximum. |
mteResourceSampleInstancesHigh
|
Contains the highest value of mteResourceSampleInstances that has occurred since initialization of the management system. |
mteResourceSampleInstanceLacks
|
Contains the number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum. |
|
Contains the number of times an attempt to check for a trigger condition has failed. This counts individually for each attempt in a group of targets or each attempt for a wildcarded object. |
|
Contains management event trigger information. |
|
Contains information about a single trigger. |
|
Contains the owner of this entry. The exact semantics of this string are subject to the security policy defined by the security administrator. |
|
Contains the locally-unique, administratively assigned name for the trigger within the scope of mteOwner. |
|
Contains description of the trigger's function and use. |
|
Contains the type of trigger test to perform. |
|
Contains the type of sampling to perform. |
|
Contains the MIB object to sample to see if the trigger should fire. |
mteTriggerValueIDWildcard
|
Control for whether mteTriggerValueID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. |
|
Contains the tag for the target(s) from which to obtain the condition for a trigger check. |
|
Contains the management context from which to obtain mteTriggerValueID. |
mteTriggerContextNameWildcard
|
Controls whether mteTriggerContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. |
|
Contains the number of seconds to wait between trigger samples. |
|
To go with mteTriggerObjects, the mteOwner of a group of objects from mteObjectsTable. |
|
The mteObjectsName of a group of objects from mteObjectsTable. |
|
A control to allow a trigger to be configured but not used. |
|
The control that allows creation and deletion of entries. Once made active an entry may not be modified except to delete it. |
|
Contains management event trigger information for delta sampling. |
|
Contains information about a single trigger's delta sampling. |
mteTriggerDeltaDiscontinuityIDWildcard
|
Control for whether mteTriggerDeltaDiscontinuityID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. Note that the value of this object will be the same as that of the corresponding instance of mteTriggerValueIDWildcard when the corresponding mteTriggerSampleType is 'deltaValue'. |
mteTriggerDeltaDiscontinuityIDType
|
The value 'timeTicks' indicates the mteTriggerDeltaDiscontinuityID of this row is of syntax TimeTicks. |
|
Contains the management event trigger information for existence triggers. |
|
Contains information about a single existence trigger. |
|
The type of existence test to perform. |
mteTriggerExistenceStartup
|
Controls whether an event may be triggered when this entry is first set to 'active' and the test specified by mteTriggerExistenceTest is true. |
mteTriggerExistenceObjectsOwner
|
To go with mteTriggerExistenceObjects, the mteOwner of a group of objects from mteObjectsTable. |
mteTriggerExistenceObjects
|
The mteObjectsName of a group of objects from mteObjectsTable. |
mteTriggerExistenceEventOwner
|
To go with mteTriggerExistenceEvent, the mteOwner of an event entry from the mteEventTable. |
|
The mteEventName of the event to invoke when mteTriggerType is 'existence' and this trigger fires. A length of 0 indicates no event. |
|
Contains the management event trigger information for boolean triggers. |
|
Contains information about a single boolean trigger. |
mteTriggerBooleanComparison
|
Contains the type of boolean comparison to perform. |
|
Containsthe value to use for the test specified by mteTriggerBooleanTest. |
|
Controls whether an event may be triggered when this entry is first set to 'active' or a new instance of the object at mteTriggerValueID is found and the test specified by mteTriggerBooleanComparison is true. |
mteTriggerBooleanObjectsOwner
|
To go with mteTriggerBooleanObjects, the mteOwner of a group of objects from mteObjectsTable. |
|
The mteObjectsName of a group of objects from mteObjectsTable. |
mteTriggerBooleanEventOwner
|
To go with mteTriggerBooleanEvent, the mteOwner of an event entry from mteEventTable. |
|
Contains mteEventName of the event to invoke when mteTriggerType is 'boolean' and this trigger fires. |
|
Contains management event trigger information for threshold triggers. |
|
Information about a single threshold trigger. |
mteTriggerThresholdStartup
|
The event that may be triggered when this entry is first set to 'active' and a new instance of the object at mteTriggerValueID is found. |
mteTriggerThresholdRising
|
Contains a threshold value to check against if mteTriggerType is 'threshold'. |
mteTriggerThresholdFalling
|
Contains a threshold value to check against if mteTriggerType is 'threshold'. |
mteTriggerThresholdDeltaRising
|
Contains a threshold value to check against if mteTriggerType is 'threshold'. |
mteTriggerThresholdDeltaFalling
|
Contains a threshold value to check against if mteTriggerType is 'threshold'. |
mteTriggerThresholdObjectsOwner
|
To go with mteTriggerThresholdObjects, the mteOwner of a group of objects from mteObjectsTable. |
mteTriggerThresholdObjects
|
The mteObjectsName of a group of objects from mteObjectsTable. |
mteTriggerThresholdRisingEventOwner
|
To go with mteTriggerThresholdRisingEvent, the mteOwner of an event entry from mteEventTable. |
mteTriggerThresholdRisingEvent
|
The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdRising. |
mteTriggerThresholdFallingEventOwner
|
To go with mteTriggerThresholdFallingEvent, the mteOwner of an event entry from mteEventTable. |
mteTriggerThresholdFallingEvent
|
The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdFalling. |
mteTriggerThresholdDeltaRisingEventOwner
|
To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an event entry from mteEventTable. |
mteTriggerThresholdDeltaRisingEvent
|
The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaRising. |
mteTriggerThresholdDeltaFallingEventOwner
|
To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an event entry from mteEventTable. |
mteTriggerThresholdDeltaFallingEvent
|
The mteEventName of the event to invoke when mteTriggerType is 'threshold' and this trigger fires based on mteTriggerThresholdDeltaFalling. |
|
Contains table of objects that can be added to notifications based on the trigger, trigger test, or event, as pointed to by entries in those tables. |
|
Applications create and delete entries using mteObjectsEntryStatus. |
|
A locally-unique, administratively assigned name for a group of objects. |
|
Contains anarbitrary integer for the purpose of identifying individual objects within a mteObjectsName group. |
|
The object identifier of a MIB object to add to a Notification that results from the firing of a trigger. |
|
Control for whether mteObjectsID is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard. |
|
Contains control that allows creation and deletion of entries. |
|
Contains number of times an attempt to invoke an event has failed. |
|
Contains table of management event action information. |
|
Applications create and delete entries using mteEventEntryStatus. |
|
Contains locally-unique, administratively assigned name for the event. |
|
A description of the event's function and use. |
|
The actions to perform when this event occurs. |
|
A control to allow an event to be configured but not used. |
|
The control that allows creation and deletion of entries. |
mteEventNotificationTable
|
Contains information about notifications to be sent as a consequence of management events. |
mteEventNotificationEntry
|
Information about a single event's notification. |
|
The object identifier from the NOTIFICATION-TYPE for the notification to use if metEventActions has 'notification' set. |
mteEventNotificationObjectsOwner
|
To go with mteEventNotificationObjects, the mteOwner of a group of objects from mteObjectsTable. |
mteEventNotificationObjects
|
The mteObjectsName of a group of objects from mteObjectsTable if mteEventActions has 'notification' set. |
|
Contains management event action information. |
|
Contains information about a single event's set option. |
|
Contains the object identifier from the MIB object to set if mteEventActions has 'set' set. |
mteEventSetObjectWildcard
|
Control over whether mteEventSetObject is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set. |
|
Contains the value to which to set the object at mteEventSetObject if mteEventActions has 'set' set. |
|
Contains the tag for the target(s) at which to set the object at mteEventSetObject to mteEventSetValue if mteEventActions has 'set' set. |
|
Contains the management context in which to set mteEventObjectID. if mteEventActions has 'set' set. |
mteEventSetContextNameWildcard
|
Control for whether mteEventSetContextName is to be treated as fully-specified or wildcarded, with 'true' indicating wildcard if mteEventActions has 'set' set. |
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).
EXPRESSION-MIB Tables and Objects
Table 3-174 lists EXPRESSION-MIB Tables and Objects.
.
Table 3-174 EXPRESSION-MIB Tables and Objects
|
|
|
Contains expression names, for creating and deleting expressions. |
|
Definitions for each expExpression. Wildcarding instance IDs: It is legal to omit all or part of the instance portion for some or all of the objects in an expression. (See the DESCRIPTION of expObjectID for details. However, note that if more than one object in the same expression is wildcarded in this way, they all must be objects where that portion of the instance is the same. In other words, all objects may be in the same SEQUENCE or in different SEQUENCEs but with the same semantic index value (e.g., a value of ifIndex) for the wildcarded portion. |
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).
HC-RMON-MIB Tables and Objects
Table 3-175 lists HC-RMON-MIB Tables and Objects.
.
Table 3-175 HC-RMON-MIB Tables and Objects
|
|
|
Media independent statistics for promiscious monitoring of any media. The following table defines media independent statistics that provides information for full and/or half-duplex links as well as high capacity links. For half-duplex links, the mediaIndependentOut* objects will not be present. For full-duplex links, the mediaIndependentOut* objects will be present. Whenever possible, the probe should count packets moving away from the closest terminating equipment as output packets. Failing that, the probe should count packets moving away from the DTE as output packets. |
|
Contains the High Capacity RMON extensions to the RMON-1 etherStatsTable. |
|
Contains the High Capacity RMON extensions to the RMON-1 etherHistoryTable. |
|
Contains the High Capacity RMON extensions to the RMON-1 hostTable. |
|
Contains the High Capacity RMON extensions to the RMON-1 hostTimeTable. |
|
Contains the High Capacity RMON extensions to the RMON-1 hostTopNTable when hostTopNRateBase specifies a High Capacity TopN Report. |
|
Contains the High Capacity RMON extensions to the RMON-1 matrixSDTable. |
|
Contains the High Capacity RMON extensions to the RMON-1 matrixDSTable. |
|
Contains the High Capacity RMON extensions to the RMON captureBufferTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 protocolDistStatsTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 nlHostTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 nlMatrixTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 nlMatrixDSTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 nlMatrixTopNTable when nlMatrixTopNControlRateBase specifies a High Capacity TopN Report. |
|
Contains the High Capacity RMON extensions to the RMON-2 alHostTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 alMatrixSDTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 alMatrixDSTable. |
|
Contains the High Capacity RMON extensions to the RMON-2 alMatrixTopNTable when alMatrixTopNControlRateBase specifies a High Capacity TopN Report. |
|
Contains the High Capacity RMON extensions to the RMON-2 usrHistoryTable. |
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 1229, The Interfaces Group MIB Using SMIv2.
In Cisco IOS Release 12.2(33)SCF, attributes are added to point to the RF channel interfaces in the tables ifTable and ifXtable.
In Cisco IOS Release 12.2(33)SCE, ifTable has 15 MAC-domain interfaces and 60 upstream interfaces for an uBR-MC3GX60V 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 Tables and Objects
The following table list IF-MIB Tables and Objects.
Table 3-176 IF-MIB Tables and Objects
|
|
|
Contains a list of interface entries. The number of entries is given by the value of ifNumber. |
|
Contains a list of interface entries and provides additional objects for the interface table. The number of entries is given by the value of ifNumber. |
|
Contains information on the relationships between the multiple sub-layers of network interfaces. |
|
Contains an entry for each address (broadcast, multicast, or unicast) for which the system receives packets or frames on a particular interface. |
|
Contains one entry per interface. It defines objects which allow a network manager to instruct an agent to test an interface for various faults. Tests for an interface are defined in the media-specific MIB for that interface. |
IF-MIB Constraints
Table 3-177 lists the constraints that the router places on IF-MIB.
.
Table 3-177 IF-MIB Constraints
|
|
|
|
|
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. |
|
|
|
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. |
|
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. |
|
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. |
|
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. |
|
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:
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
Note The ifOutMulticastPkts, ifOutBroadcastPkts, ifHCOutMulticastPkts, and ifHCOutBroadcastPkts MIB attributes of the ifXTable are not supported on the Cisco uBR-MC3GX60V, Cisco UBR-MC20X20V, and the Cisco uBR-MC88V line cards.
Table 3-178 lists the ifTable entries for NB channels.
Table 3-178 ifTable Entries for NB channels
|
|
|
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-179 lists the ifXTable entries for NB channels.
Table 3-179 ifXTable Entries for NB channels
|
|
|
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-180 lists the ifStackTable entries for NB channel.
Table 3-180 ifStackTable Entries for NB channel
|
|
|
ifStackHigherLayer |
ifIndex or zero |
ifIndex or zero |
ifStackLowerLayer |
zero |
ifIndex or zero, return always zero |
ifStackStatus |
active |
Read-only, returns always active. |
Table 3-181 lists the ifTable entries for WB channels.
Table 3-181 ifTable Entries for WB channels
|
|
|
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-182 lists the ifXTable entries for WB channels.
Table 3-182 ifXTable Entries for WB channels
|
|
|
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-183 lists the ifStackTable entries for WB channel.
Table 3-183 ifStackTable Entries for WB channel
|
|
|
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).
IGMP-MIB Tables and Objects
Table 3-184 lists IGMP-MIB Tables and Objects.
.
Table 3-184 IGMP-MIB Tables and Objects
|
|
|
The (conceptual) table listing the interfaces on which IGMP is enabled. |
|
The (conceptual) table listing the IP multicast groups for which there are members on a particular interface. |
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).
IGMP-STD-MIB Tables and Objects
Table 3-185 lists IGMP-STD-MIB Tables and Objects.
.
Table 3-185 IGMP-STD-MIB Tables and Objects
|
|
|
The (conceptual) table listing the interfaces on which IGMP is enabled. |
|
The (conceptual) table listing the IP multicast groups for which there are members on a particular interface. |
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).
INT-SERV-MIB Tables and Objects
Table 3-186 lists INT-SERV-MIB Tables and Objects.
.
Table 3-186 INT-SERV-MIB Tables and Objects
|
|
|
The reservable attributes of the system’s in- terfaces. |
|
Information describing the reserved flows us- ing the system’s interfaces. |
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).
IP-MIB Tables and Objects
Table 3-187 lists IP-MIB Tables and Objects.
.
Table 3-187 IP-MIB Tables and Objects
|
|
|
Contains per-interface IPv4-specific information. |
|
Contains per-interface IPv6-specific information. |
|
Contains system wide, IP version specific traffic statistics. This table and the ipIfStatsTable contain similar objects whose difference is in their granularity. Where this table contains system wide traffic statistics, the ipIfStatsTable contains the same statistics but counted on a per-interface basis. |
|
Contains per-interface traffic statistics. This table and the ipSystemStatsTable contain similar objects whose difference is in their granularity. Where this table contains per-interface statistics, the ipSystemStatsTable contains the same statistics, but counted on a system wide basis. |
|
Allows the user to determine the source of an IP address or set of IP addresses, and allows other tables to share the information via pointer rather than by copying. For example, when the node configures both a unicast and anycast address for a prefix, the ipAddressPrefix objects for those addresses will point to a single row in this table. This table primarily provides support for IPv6 prefixes, and several of the objects are less meaningful for IPv4. The table continues to allow IPv4 addresses to allow future flexibility. In order to promote a common configuration, this document includes suggestions for default values for IPv4 prefixes. Each of these values may be overridden if an object is meaningful to the node. All prefixes used by this entity should be included in this table independent of how the entity learned the prefix. (This table isn’t limited to prefixes learned from router advertisements.) |
|
Contains addressing information relevant to the entity’s interfaces. This table does not contain multicast address information. Tables for such information should be contained in multicast specific MIBs, such as RFC 3019. While this table is writable, the user will note that several objects, such as ipAddressOrigin, are not. The intention in allowing a user to write to this table is to allow them to add or remove any entry that isn’t permanent. The user should be allowed to modify objects and entries when that would not cause inconsistencies within the table. Allowing write access to objects, such as ipAddressOrigin, could allow a user to insert an entry and then label it incorrectly. Note well: When including IPv6 link-local addresses in this table, the entry must use an InetAddressType of ’ipv6z’ in order to differentiate between the possible interfaces. |
|
The IP Address Translation table used for mapping from IP addresses to physical addresses. The Address Translation tables contain the IP address to ’physical’ address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. While many protocols may be used to populate this table, ARP and Neighbor Discovery are the most likely options. |
|
Describes IPv6 unicast and multicast scope zones. For those objects that have names rather than numbers, the names were chosen to coincide with the names used in the IPv6 address architecture document. |
|
Describes the default routers known to this entity. |
|
Contains information used to construct router advertisements. |
|
Contains generic system-wide ICMP counters. |
|
Contains system-wide per-version, per-message type ICMP counters. |
|
Contains addressing information relevant to this entity’s IPv4 addresses. This table has been deprecated, as a new IP version-neutral table has been added. It is loosely replaced by the ipAddressTable although several objects that weren’t deemed useful weren’t carried forward while another (ipAdEntReasmMaxSize) was moved to the ipv4InterfaceTable. |
|
The IPv4 Address Translation table used for mapping from IPv4 addresses to physical addresses. This table has been deprecated, as a new IP version-neutral table has been added. It is loosely replaced by the ipNetToPhysicalTable. |
MIB Constraint
The Cisco CMTS routers support the RFC1213-MIB version of this MIB (1.3.6.1.2.1.4).
Note The Cisco CMTS routers partially support the IP-MIB. Hence, the MIB tables and objects may not reflect the correct values or information.
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).
IPMROUTE-MIB Tables and Objects
Table 3-188 lists IPMROUTE-MIB Tables and Objects.
.
Table 3-188 IPMROUTE-MIB Tables and Objects
|
|
|
The (conceptual) table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router. |
|
The (conceptual) table containing information on the next hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next hops on outgoing interfaces for particular sources sending to a particular multicast group address. |
|
The (conceptual) table containing multicast routing information specific to interfaces. |
|
The (conceptual) table listing the router’s scoped multicast address boundaries. |
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).
IPMROUTE-STD-MIB Tables and Objects
Table 3-189 lists IPMROUTE-STD-MIB Tables and Objects.
.
Table 3-189 IPMROUTE-STD-MIB Tables and Objects
|
|
|
The (conceptual) table containing multicast routing information for IP datagrams sent by particular sources to the IP multicast groups known to this router. |
|
The (conceptual) table containing information on the next- hops on outgoing interfaces for routing IP multicast datagrams. Each entry is one of a list of next-hops on outgoing interfaces for particular sources sending to a particular multicast group address. |
|
The (conceptual) table containing multicast routing information specific to interfaces. |
|
The (conceptual) table listing the router’s scoped multicast address boundaries. |
|
The (conceptual) table listing the multicast scope names. |
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).
ISDN-MIB Tables and Objects
Table 3-190 lists ISDN-MIB Tables and Objects.
.
Table 3-190 ISDN-MIB Tables and Objects
|
|
|
Contains configuration and operational parameters for all physical Basic Rate interfaces on this managed device. |
|
Defines port specific operational, statistics and active call data for ISDN B channels. Each entry in this table describes one B (bearer) channel. |
|
Contains configuration and operational parameters for all ISDN signaling channels on this managed device. |
|
ISDN signaling table containing statistics information for all ISDN signaling channels on this managed device. Only statistical information which is not already being counted in the ifTable is being defined in this table. |
|
Table containing configuration and statistics information for all LAPD (D channel Data Link) interfaces on this managed device. Only statistical information which is not already being counted in the ifTable is being defined in this table. |
|
Contains configuration for Terminal Endpoints. |
|
Contains Directory Numbers. |
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)
LAN-EMULATION-CLIENT-MIB Tables and Objects
Table 3-191 lists LAN-EMULATION-CLIENT-MIB Tables and Objects.
.
Table 3-191 CISCO-LEC-EXT-MIB Tables and Objects
|
|
|
Describes all of the LAN Emulation Clients implemented by this host. Each LE Client has a row in the MIB-II/RFC 1573 Interfaces table (describing the emulated packet interface it presents to higher layers). Each LE Client also has a row in this and other LEC MIB tables (describing its interface with other LAN Emulation components). This table contains configuration variables. Three extension tables contain client status, performance statistics, and information about control/multicast VCCs. Unlike hardware ports, LE Clients can be created by management. However, the RFC 1573 Interfaces table does not directly support row creation. Therefore, creating or deleting a row in the lecConfigTable is defined to have the side effect of creating or deleting corresponding rows in - the MIB-II / RFC 1573 Interfaces table, - the ’lecMappingTable’, - the ’lecStatusTable’, - the ’lecServerVccTable’, - the ’lecStatisticsTable’, and - any other dependent tables New Interfaces table rows for LAN Emulation Clients always have ’ifAdminStatus’ set to ’down’. A Note On Indexing: ------------------- Most of the tables in this MIB are indexed in whole or in part by ’lecIndex’ - not by ’ifIndex’. Why is there a separate index? Traditionally, ifIndex values are chosen by agents, and are permitted to change across restarts. Using ifIndex to index lecConfigTable could complicate row creation and/or cause interoperability problems (if each agent had special restrictions on ifIndex). Having a separate index avoids these problems. |
|
A read-only table containing identification, status, and operational information about the LAN Emulation Clients this agent manages. |
|
A table mapping the ’ifIndex’ values of ’aflane8023’ and ’aflane8025’ interfaces to the ’lecIndex’ values of the corresponding LAN Emulation Clients. |
|
An extension table containing traffic statistics for all the LAN Emulation Clients this host implements. |
|
Identifies the Control and Multicast VCCs for each LAN Emulation Client this host implements. |
|
Lists all of the ATM addresses belonging to this host’s LAN Emulation Clients. |
|
Contains entries for all of the registered MAC addresses belonging to this agent’s LE clients. C6 Local Unicast MAC Address(es). Each LE Client has zero or more local unicast MAC addresses. In an operational LE Client, every address in this variable MUST have been registered with the LE Server. Two LE CLients joined to the same emulated LAN MUST NOT have the same local unicast MAC address. A LE Client’s MAC addresses may change during normal operations. When answering a LE_ARP_REQUEST for any address in this list, the ’Remote Address’ bit in the FLAGS field of the LE_ARP_RESPONSE MUST be clear. |
|
This table lists all of the Route Descriptors which are registered by this host’s LAN Emulation Clients. C8 Route Descriptor(s). Route Descriptors exist only for source-routed IEEE 802.5 LE Clients that are Source-Route Bridges. All Route Descriptors in any given emulated LAN MUST be unique. A LE Client MAY have zero or more Route Descriptors and these Route Descriptors MAY change during normal operation. In an operational LE Client, every Local Route Descriptor in C8 MUST have been registered with the LE Server. When answering a LE_ARP_REQUEST for any address in this list, the ’Remote Address’ bit in the FLAGS field of the LE_ARP_RESPONSE MUST be clear. |
|
Provides access to an ATM LAN Emulation Client’s MAC-to-ATM ARP cache. It contains entries for unicast addresses and for the broadcast address, but not for multicast MAC addresses. C16 LE_ARP Cache. A table of entries, each of which establishes a relationship between a LAN Destination external to the LE Client and the ATM address to which data frames for that LAN Destination will be sent. |
|
Provides access to an ATM LAN Emulation Client’s Route Descriptor-to-ATM ARP cache. Implementation of this table is optional for hosts that do not support emulated IEEE 802.5 Token Ring LANs, and mandatory for hosts which do. C16 LE_ARP Cache. A table of entries, each of which establishes a relationship between a LAN Destination external to the LE Client and the ATM address to which data frames for that LAN Destination will be sent. |
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.
MPLS-LSR-MIB Tables and Objects
Table 3-192 lists MPLS-LSR-MIB Tables and Objects.
.
Table 3-192 MPLS-LSR-MIB Tables and Objects
|
|
|
Specifies per-interface MPLS capability and associated information. |
|
Provides MPLS performance information on a per-interface basis. |
|
Contains a collection of incoming segments to an LSR. |
|
Contains statistical information for incoming MPLS segments to an LSR. |
|
Contains a representation of the outgoing segments from an LSR. |
|
Contains statistical information about outgoing segments from an LSR. The counters in this entry should behave in a manner similar to that of the interface. |
|
Specifies information for switching between LSP segments. It supports point-to-point, point-to-multipoint and multipoint-to-point connections. mplsLabelStackTable specifies the label stack information for a cross-connect LSR and is referred to from mplsXCTable. |
|
Specifies the label stack to be pushed onto a packet, beneath the top label. Entries into this table are referred to from mplsXCTable. |
|
Specifies the Traffic Parameter objects for in and out-segments. |
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.
MPLS-LDP-MIB Tables and Objects
Table 3-193 lists MPLS-LDP-MIB Tables and Objects.
.
Table 3-193 MPLS-LSR-MIB Tables and Objects
|
|
|
Contains information about the MPLS Label Distribution Protocol Entities which exist on this Label Switch Router (LSR). |
mplsLdpEntityConfGenericTable
|
Provides a way to configure Generic Labels associated with LDP entities on the LSR. |
mplsLdpEntityAtmParmsTable
|
Contains information about the ATM specific information which could be used in the ’Optional Parameters’ and other ATM specific information. |
mplsLdpEntityConfAtmLabelRangeTable
|
The MPLS LDP Entity Configurable ATM Label Range Table. The purpose of this table is to provide a mechanism for specifying a contiguous range of vpi’s with a contiguous range of vci’s, or a ’label range’ for LDP Entities. LDP Entities which use ATM must have at least one entry in this table. |
mplsLdpEntityFrameRelayParmsTable
|
Contains information about the Optional Parameters to specify what this Entity is going to specify for Frame Relay specific LDP Intialization Messages. |
mplsLdpEntityConfFrLabelRangeTable
|
Contains information about the Optional Parameters to specify what this Entity is going to specify for Frame Relay specific LDP Intialization Messages. |
|
This table is a read-only table which augments the mplsLdpEntityTable. The purpose of this table is to keep statistical information about the LDP Entities on the LSR. |
|
Information about LDP peers known by Entities in the mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer interaction but is not appropriate for the mplsLdpSessionTable. |
mplsLdpHelloAdjacencyTable
|
ContainsHello Adjacencies for Sessions. |
|
Contains Sessions between the LDP Entities and LDP Peers. Each row represents a single session. |
|
A table which relates Sessions in the ’mplsLdpSessionTable’ and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection. NOTE: this table cannot use the ’AUGMENTS’ clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable. |
mplsLdpFrameRelaySessionTable
|
Contains Frame Relay label range intersections between the LDP Entities and LDP Peers. Each row represents a single label range intersection. NOTE: this table cannot use the ’AUGMENTS’ clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable. |
|
Contains statistics for Sessions between LDP Entities and LDP Peers. |
mplsLdpSessionPeerAddressTable
|
This table ’extends’ the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated when Label Withdraw Address Messages are received, i.e. Rows should be deleted as apropriate. NOTE: since more than one address may be contained in a Label Address Message, this table ’extends’, rather than ’AUGMENTS’ the mplsLdpSessionTable’s information. |
|
Represents LIB (Label Information Base) Information. The table is read-only. |
|
Represents the FEC (Forwarding Equivalence Class) Information associated with an LSP. The table is read-only. |
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.
MPLS-TE-MIB Tables and Objects
Table 3-194 lists MPLS-TE-MIB Tables and Objects.
.
Table 3-194 MPLS-TE-MIB Tables and Objects
|
|
|
The mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multi-point-to-point and point- to-multi-point connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. |
|
The mplsTunnelHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, when it is established via signaling, for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelHopListIndex. Each row also has a secondary index mplsTunnelHopIndex corresponding to the next hop that this row corresponds to. The first row in the table is the first hop after the origination point of the tunnel. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelHopTable. |
|
The mplsTunnelResourceTable allows a manager to specify which resources are desired for an MPLS tunnel. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources. |
|
The mplsTunnelARHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as reported by the MPLS signaling protocol, for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelARHopListIndex. Each row also has a secondary index mplsTunnelARHopIndex, corresponding to the next hop that this row corresponds to. The first row in the table is the first hop after the origination point of the tunnel. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelARHopTable. Please note that since the information necessary to build entries within this table are not provided by some MPLS signaling protocols, implementation of this table is optional. Furthermore, since the information in this table is actually provided by the MPLS signaling protocol after the path has been set-up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only. |
|
The mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint- based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, corresponding to the next hop that this row corresponds to. The first row in the table is the first hop after the origination point of the tunnel. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelCHopTable. Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table is actually provided by routing protocol after the path has been computed, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only. |
|
This table provides per-tunnel MPLS performance information. |
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).
MPLS-TE-STD-MIB Tables and Objects
Table 3-195 lists MPLS-TE-STD-MIB Tables and Objects.
.
Table 3-195 MPLS-TE-STD-MIB Tables and Objects
|
|
|
The mplsTunnelTable allows new MPLS tunnels to be created between an LSR and a remote endpoint, and existing tunnels to be reconfigured or removed. Note that only point-to-point tunnel segments are supported, although multipoint-to-point and point- to-multipoint connections are supported by an LSR acting as a cross-connect. Each MPLS tunnel can thus have one out-segment originating at this LSR and/or one in-segment terminating at this LSR. |
|
The mplsTunnelHopTable is used to indicate the hops, strict or loose, for an instance of an MPLS tunnel defined in mplsTunnelTable, when it is established via signalling, for the outgoing direction of the tunnel. Thus at a transit LSR, this table contains the desired path of the tunnel from this LSR onwards. Each row in this table is indexed by mplsTunnelHopListIndex which corresponds to a group of hop lists or path options. Each row also has a secondary index mplsTunnelHopIndex, which indicates a group of hops (also known as a path option). Finally, the third index, mplsTunnelHopIndex indicates the specific hop information for a path option. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelHopTable. |
|
The mplsTunnelResourceTable allows a manager to specify which resources are desired for an MPLS tunnel. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources. |
|
The mplsTunnelARHopTable is used to indicate the hops for an MPLS tunnel defined in mplsTunnelTable, as reported by the MPLS signalling protocol. Thus at a transit LSR, this table (if the table is supported and if the signaling protocol is recording actual route information) contains the actual route of the whole tunnel. If the signaling protocol is not recording the actual route, this table MAY report the information from the mplsTunnelHopTable or the mplsTunnelCHopTable. Each row in this table is indexed by mplsTunnelARHopListIndex. Each row also has a secondary index mplsTunnelARHopIndex, corresponding to the next hop that this row corresponds to. Please note that since the information necessary to build entries within this table is not provided by some MPLS signalling protocols, implementation of this table is optional. Furthermore, since the information in this table is actually provided by the MPLS signalling protocol after the path has been set-up, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read- only. Note also that the contents of this table may change while it is being read because of re-routing activities. A network administrator may verify that the actual route read is consistent by reference to the mplsTunnelLastPathChange object. |
|
The mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint- based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Thus at a transit LSR, this table (if the table is supported) MAY contain the path computed by the CSPF engine on (or on behalf of) this LSR. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, corresponding to the next hop that this row corresponds to. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelCHopTable. Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table describes the path computed by the CSPF engine the entries in this table are read-only. |
|
This table provides per-tunnel instance MPLS performance information. |
|
The mplsTunnelCRLDPResTable allows a manager to specify which CR-LDP-specific resources are desired for an MPLS tunnel if that tunnel is signaled using CR-LDP. Note that these attributes are in addition to those specified in mplsTunnelResourceTable. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources. |
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 additional information about this MIB, see the document MSDP MIB, at the following URL:
http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12s_msdp.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-196 lists the constraints that the router places on MSDP-MIB.
.
Table 3-196 MSDP-MIB Constraints
|
|
|
Not supported. |
|
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).
NOTIFICATION-LOG-MIB Tables and Objects
Table 3-197 lists NOTIFICATION-LOG-MIB Tables and Objects.
.
Table 3-197 NOTIFICATION-LOG-MIB Tables and Objects
|
|
|
Contains logging control entries. |
|
ContainsNotification log statistics entries. |
|
Contains Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0. |
|
Contains variables to go with Notification log entries. |
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-CHASSIS-MIB Tables and Objects
Table 3-198 lists OLD-CISCO-CHASSIS-MIB Tables and Objects.
.
Table 3-198 OLD-CISCO-CHASSIS-MIB Tables and Objects
|
|
|
Chassis card table. |
|
Chassis card table. |
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.
Table 3-199 lists OLD-CISCO-CPU-MIB Tables and Objects.
.
Table 3-199 OLD-CISCO-CPU-MIB Tables and Objects
|
|
|
CPU busy percentage in the last 5 second period. Not the last 5 realtime seconds but the last 5 second period in the scheduler. |
|
1 minute exponentially-decayed moving average of the CPU busy percentage. |
|
5 minute exponentially-decayed moving average of the CPU busy percentage. |
|
cisco internal variable not to be used |
|
cisco internal variable not to be used |
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-INTERFACES-MIB Tables and Objects
Table 3-200 lists OLD-CISCO-CHASSIS-MIB Tables and Objects.
.
Table 3-200 OLD-CISCO-CHASSIS-MIB Tables and Objects
|
|
|
Contains a list of interface entries. |
|
Contains a list of card entries for 4T, HSSI, Mx serial or FSIP. |
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-IP-MIB Tables and Objects
Table 3-201 lists OLD-CISCO-IP-MIB Tables and Objects.
.
Table 3-201 OLD-CISCO-IP-MIB Tables and Objects
|
|
|
Contains a list of IP address entries. |
|
Contains a list of IP routing entries. |
|
Contains a list of accounting entries. |
|
Contains a list of IP checkpoint accounting entries. |
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-MEMORY-MIB Tables and Objects
Table 3-202 lists OLD-CISCO-MEMORY-MIB Tables and Objects.
.
Table 3-202 OLD-CISCO-MEMORY-MIB Tables and Objects
|
|
|
Returns the amount of free memory in bytes. |
|
Contains the number of free buffer elements. |
|
Contains the maximum number of buffer elements. |
|
Contains the number of buffer element hits. |
|
Contains the number of buffer element misses. |
|
Contains the number of buffer element creates. |
|
Contains the size of small buffers. |
|
Contains the total number of small buffers. |
|
Contains the number of free small buffers. |
|
Contains the maximum number of small buffers. |
|
Contains the number of small buffer hits. |
|
Contains the number of small buffer misses. |
|
Contains the number of small buffer trims. |
|
Contains the number of small buffer creates. |
|
Contains the size of medium buffers. |
|
Contains the total number of medium buffers. |
|
Contains the number of free medium buffers. |
|
Contains the maximum number of medium buffers. |
|
Contains the number of medium buffer hits. |
|
Contains the number of medium buffer misses. |
|
Contains the number of medium buffer trims. |
|
Contains the number of medium buffer creates. |
|
Contains the size of big buffers. |
|
Contains the total number of big buffers. |
|
Contains the number of free big buffers. |
|
Contains the maximum number of big buffers. |
|
Contains the number of big buffer hits. |
|
Contains the number of big buffer misses. |
|
Contains the number of big buffer trims. |
|
Contains the number of big buffer creates. |
|
Contains the size of large buffers. |
|
Contains the total number of large buffers. |
|
Contains the number of free large buffers. |
|
Contains the maximum number of large buffers. |
|
Contains the number of large buffer hits. |
|
Contains the number of large buffer misses. |
|
Contains the number of large buffer trims. |
|
Contains the number of large buffer creates. |
|
Count of the number of buffer allocation failures. |
|
Count of the number of buffer create failures due to no free memory. |
|
Contains the size of huge buffers. |
|
Contains the total number of huge buffers. |
|
Contains the number of free huge buffers. |
|
Contains the maximum number of huge buffers. |
|
Contains the number of huge buffer hits. |
|
Contains the number of huge buffer misses. |
|
Contains the number of huge buffer trims. |
|
Contains the number of huge buffer creates. |
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-SYSTEM-MIB Tables and Objects
Table 3-203 lists OLD-CISCO-SYSTEM-MIB Tables and Objects.
.
Table 3-203 OLD-CISCO-SYSTEM-MIB Tables and Objects
|
|
|
Contains a printable octet string which contains the System Bootstrap description and version identification. |
|
Contains a printable octet string which contains the reason why the system was last restarted. |
|
Represents the name of the host in printable ascii characters. |
|
This variable is the domain portion of the domain name of the host. |
|
Contains the last SNMP authorization failure IP address. |
|
Contains the IP address of the host that supplied the currently running software. |
|
Holds the address of the host that supplied the network-confg file. |
|
Holds the name of the network configuration file. |
|
Cause the loading of a new network-config file using TFTP. |
|
Contains the address of the host that provided the host-config file. |
|
Contains the name of the last configured host-confg file. |
|
Causes the loading of a new host-confg file using TFTP. |
|
Writes configuration into non-volatile memory / erase config memory if 0. |
|
Writes configuration to host using TFTP. |
|
cisco's name and address |
|
Holds the protocol that supplied the network-confg file. |
|
Holds the protocol that supplied the host- confg file. |
|
Holds the address of the host that supplied the system boot image. |
|
Holds the name of the system boot image. |
|
Holds the protocol or media that supplied the system boot image. |
|
Performs a clearing of the entire ARP cache and invalidation of route caches. |
|
Clear interface given IfIndex as value. |
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-TCP-MIB Tables and Objects
Table 3-204 lists OLD-CISCO-TCP-MIB Tables and Objects.
.
Table 3-204 OLD-CISCO-TCP-MIB Tables and Objects
|
|
|
Contains a list of TCP connection entries. |
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.
OLD-CISCO-TS-MIB Tables and Objects
Table 3-205 lists OLD-CISCO-TS-MIB Tables and Objects.
.
Table 3-205 OLD-CISCO-TS-MIB Tables and Objects
|
|
|
Contains a list of terminal server line entries. |
|
Contains a list of terminal server line and session entries. |
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).
PIM-MIB Tables and Objects
Table 3-206 lists PIM-MIB Tables and Objects.
.
Table 3-206 PIM-MIB Tables and Objects
|
|
|
The (conceptual) table listing the router’s PIM interfaces. IGMP and PIM are enabled on all interfaces listed in this table. |
|
The (conceptual) table listing the router’s PIM neighbors. |
|
The (conceptual) table listing PIM-specific information on a subset of the rows of the ipMRouteTable defined in the IP Multicast MIB. |
|
The (conceptual) table listing PIM-specific information on a subset of the rows of the ipMRouteNextHopTable defined in the IP Multicast MIB. |
|
The (conceptual) table listing PIM version 1 information for the Rendezvous Points (RPs) for IP multicast groups. This table is deprecated since its function is replaced by the pimRPSetTable for PIM version 2. |
|
The (conceptual) table listing PIM information for candidate Rendezvous Points (RPs) for IP multicast groups. When the local router is the BSR, this information is obtained from received Candidate-RP-Advertisements. When the local router is not the BSR, this information is obtained from received RP-Set messages. |
|
The (conceptual) table listing the IP multicast groups for which the local router is to advertise itself as a Candidate-RP when the value of pimComponentCRPHoldTime is non-zero. If this table is empty, then the local router will advertise itself as a Candidate-RP for all groups (providing the value of pimComponentCRPHoldTime is non- zero). |
|
The (conceptual) table containing objects specific to a PIM domain. One row exists for each domain to which the router is connected. A PIM-SM domain is defined as an area of the network over which Bootstrap messages are forwarded. Typically, a PIM-SM router will be a member of exactly one domain. This table also supports, however, routers which may form a border between two PIM-SM domains and do not forward Bootstrap messages between them. |
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).
RFC1213-MIB Tables and Objects
Table 3-207 lists RFC1213-MIB Tables and Objects.
.
Table 3-207 RFC1213-MIB Tables and Objects
|
|
|
Contains a list of interface entries. The number of entries is given by the value of ifNumber. |
|
The Address Translation tables contain the NetworkAddress to ‘physical’ address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries. |
|
Contains addressing information relevant to this entity’s IP addresses. |
|
This entity’s IP Routing table. |
|
The IP Address Translation table used for mapping from IP addresses to physical addresses. |
|
Contains TCP connection-specific information. |
|
Contains UDP listener information. |
|
The EGP neighbor table. |
MIB Constraints
Table 3-208 lists the constraints that the router places on RFC1213-MIB.
.
Table 3-208 RFC1213-MIB Constraints
|
|
|
|
- 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.
RFC1231-MIB Tables and Objects
Table 3-209 lists RFC1231-MIB Tables and Objects.
.
Table 3-209 RFC1231-MIB Tables and Objects
|
|
|
ContainsToken Ring interface parameters and state variables, one entry per 802.5 interface. |
|
Contains Token Ring statistics, one entry per 802.5 interface. All the statistics are defined using the syntax Counter as 32-bit wrap around counters. Thus, if an interface’s hardware maintains these statistics in 16-bit counters, then the agent must read the hardware’s counters frequently enough to prevent loss of significance, in order to maintain 32-bit counters in software. |
|
Contains Token Ring interface timer values, one entry per 802.5 interface. |
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).
RFC1253-MIB Tables and Objects
Table 3-210 lists CISCO-LEC-EXT-MIB Tables and Objects.
.
Table 3-210 CISCO-LEC-EXT-MIB Tables and Objects
|
|
|
Information describing the configured parameters and cumulative statistics of the router’s attached areas. |
|
The set of metrics that will be advertised by a default Area Border Router into a stub area. |
|
The OSPF Process’s Links State Database. |
|
A range if IP addresses specified by an IP address/IP network mask pair. For example, class B address range of X.X.X.X with a network mask of 255.255.0.0 includes all IP addresses from X.X.0.0 to X.X.255.255 |
|
The list of Hosts, and their metrics, that the router will advertise as host routes. |
|
The OSPF Interface Table describes the interfaces from the viewpoint of OSPF. |
|
The TOS metrics for a non-virtual interface identified by the interface index. |
|
Information about this router’s virtual interfaces. |
|
Contains non-virtual neighbor information. |
|
Contains virtual neighbor information. |
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).
RFC1315-MIB Tables and Objects
Table 3-211 lists RFC1315-MIB Tables and Objects.
.
Table 3-211 RFC1315-MIB Tables and Objects
|
|
|
The Parameters for the Data Link Connection Management Interface for the frame relay service on this interface. |
|
Contains information about specific Data Link Connection Identifiers and corresponding virtual circuits. |
|
Contains information about Errors on the Frame Relay interface. |
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).
RFC1381-MIB Tables and Objects
Table 3-212 lists RFC1381-MIB Tables and Objects.
.
Table 3-212 RFC1381-MIB Tables and Objects
|
|
|
Contains objects that can be changed to manage a LAPB interface. Changing one of these parameters may take effect in the operating LAPB immediately or may wait until the interface is restarted depending on the details of the implementation. Most of the objects in this read-write table have corresponding read-only objects in the lapbOperTable that return the current operating value. The operating values may be different from these configured values if changed by XID negotiation or if a configured parameter was changed after the interface was started. |
|
Contains configuration information about interface parameters currently set in the interface. Many of these objects have corresponding objects in the lapbAdmnTable. |
|
Contains the objects recorded by LAPB to provide information about the traffic flow through the interface. |
|
Defines values to use for XID negotiation that are not found in the lapbAdmnTable. This table is optional for implementations that don’t support XID and mandatory for implementations that do initiate XID negotiation. |
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).
RFC1382-MIB Tables and Objects
Table 3-213 lists RFC1382-MIB Tables and Objects.
.
Table 3-213 RFC1382-MIB Tables and Objects
|
|
|
Contains the administratively set configuration parameters for an X.25 Packet Level Entity (PLE). Most of the objects in this table have corresponding objects in the x25OperTable. This table contains the values as last set by the administrator. The x25OperTable contains the values actually in use by an X.25 PLE. Changing an administrative value may or may not change a current operating value. The operating value may not change until the interface is restarted. Some implementations may change the values immediately upon changing the administrative table. All implementations are required to load the values from the administrative table when initializing a PLE. |
|
The operation parameters in use by the X.25 PLE. |
|
Statistics information about this X.25 PLE. |
|
Contains information about the channel number configuration in an X.25 PLE. These values are the configured values. changes in these values after the interfaces has started may not be reflected in the operating PLE. |
|
Contain general information about a specific circuit of an X.25 PLE. |
|
A table of entries about closed circuits. Entries must be made in this table whenever circuits are closed and the close request or close indication packet contains a clearing cause other than DTE Originated or a Diagnostic code field other than Higher Layer Initiated disconnection-normal. An agent may optionally make entries for normal closes (to record closing facilities or other information). Agents will delete the oldest entry in the table when adding a new entry would exceed agent resources. Agents are required to keep the last entry put in the table and may keep more entries. The object x25OperClearEntriesGranted returns the maximum number of entries kept in the table. |
|
Contains the parameters that can be varied between X.25 calls. The entries in this table are independent of the PLE. There exists only one of these tables for the entire system. The indexes for the entries are independent of any PLE or any circuit. Other tables reference entries in this table. Entries in this table can be used for default PLE parameters, for parameters to use to place/answer a call, for the parameters currently in use for a circuit, or parameters that were used by a circuit. The number of references to a given set of parameters can be found in the x25CallParmRefCount object sharing the same instance identifier with the parameters. The value of this reference count also affects the access of the objects in this table. An object in this table with the same instance identifier as the instance identifier of an x25CallParmRefCount must be consider associated with that reference count. An object with an associated reference count of zero can be written (if its ACCESS clause allows it). An object with an associated reference count greater than zero can not be written (regardless of the ACCESS clause). This ensures that a set of call parameters being referenced from another table can not be modified or changed in a ways inappropriate for continued use by that table. |
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).
RFC1406-MIB Tables and Objects
Table 3-214 lists RFC1406-MIB Tables and Objects.
.
Table 3-214 RFC1406-MIB Tables and Objects
|
|
|
Contains DS1 Configuration. |
|
Contains DS1 Current. |
|
ContainsDS1 Interval. |
|
Contains DS1 Total table. 24 hour interval. |
|
Contains DS1 Far End Current. |
|
Contains DS1 Far End Interval. |
|
Contains DS1 Far End Total. |
|
Contains DS1 Fractional. |
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).
RFC1407-MIB Tables and Objects
Table 3-215 lists RFC1407-MIB Tables and Objects.
.
Table 3-215 RFC1407-MIB Tables and Objects
|
|
|
The DS3/E3 Configuration table. |
|
The DS3/E3 Current table. |
|
The DS3/E3 Interval table. |
|
The DS3/E3 Total table. 24 hour interval. |
|
The DS3 Far End Configuration table. |
|
The DS3 Far End Current table. |
|
The DS3 Far End Interval table. |
|
The DS3 Far End Total table. 24 hour interval. |
|
The DS3 Fractional table. |
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).
RFC1595-MIB Tables and Objects
Table 3-216 lists RFC1595-MIB Tables and Objects.
.
Table 3-216 RFC1595-MIB Tables and Objects
|
|
|
Represents, whether the Cisco Unified Border Element (CUBE) is enabled on the device or not. |
|
Represents the version of Cisco Unified Border Element on the device. |
|
Provides the total number of CUBE session allowed on the device. |
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).
RMON-MIB Tables and Objects
Table 3-217 lists RMON-MIB Tables and Objects.
.
Table 3-217 RMON-MIB Tables and Objects
|
|
|
Contains a list of Ethernet statistics entries. |
|
Contains a list of history control entries. |
|
Contains a list of Ethernet history entries. |
|
Contains a list of alarm entries. |
|
Contains a list of host table control entries. |
|
Contains a list of host entries. |
|
Contains a list of time-ordered host table entries. |
|
Contains a list of top N host control entries. |
|
Contains a list of top N host entries. |
|
Contains a list of information entries for the traffic matrix on each interface. |
|
Contains a list of traffic matrix entries indexed by source and destination MAC address. |
|
Contains a list of traffic matrix entries indexed by destination and source MAC address. |
|
Contains a list of packet filter entries. |
|
Contains a list of packet channel entries. |
|
Contains a list of buffers control entries. |
|
Contains a list of packets captured off of a channel. |
|
Contains a list of events to be generated. |
|
Contains a list of events that have been logged. |
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).
RMON2-MIB Tables and Objects
Table 3-218 lists RMON2-MIB Tables and Objects.
.
Table 3-218 RMON2-MIB Tables and Objects
|
|
|
Lists the protocols that this agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The agent should boot up with this table preconfigured with those protocols that it knows about and wishes to monitor. Implementations are strongly encouraged to support protocols higher than the network layer (at least for the protocol distribution group), even for implementations that don’t support the application layer groups. |
|
Controls the setup of protocol type distribution statistics tables. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of protocol statistics is available. Rationale: This table controls collection of very basic statistics for any or all of the protocols detected on a given interface. An NMS can use this table to quickly determine bandwidth allocation utilized by different protocols. A media-specific statistics collection could also be configured (e.g. etherStats, trPStats) to easily obtain total frame, octet, and droppedEvents for the same interface. |
|
An entry is made in this table for every protocol in the protocolDirTable which has been seen in at least one packet. Counters are updated in this table for every protocol type that is encountered when parsing a packet, but no counters are updated for packets with MAC-layer errors. Note that if a protocolDirEntry is deleted, all associated entries in this table are removed. |
|
Controls the collection of network layer address to physical address to interface mappings. Note that this is not like the typical RMON controlTable and dataTable in which each entry creates its own data table. Each entry in this table enables the discovery of addresses on a new interface and the placement of address mappings into the central addressMapTable. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of address mappings is available. |
|
Contains network layer address to physical address to interface mappings. The probe will add entries to this table based on the source MAC and network addresses seen in packets without MAC-level errors. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirAddressMapConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirAddressMapConfig value of supportedOff(2). |
|
Contains higher layer (i.e. non-MAC) host table control entries. These entries will enable the collection of the network and application level host tables indexed by network addresses. Both the network and application level host tables are controlled by this table is so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore (note that if an implementation stores application layer host records in memory, it can derive network layer host records from them). Entries in the nlHostTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alHostTable, entries in the alHostTable will be created on behalf of each entry in this table. Implementations are encouraged to add an entry per monitored interface upon initialization so that a default collection of host statistics is available. |
|
A collection of statistics for a particular network layer address that has been discovered on an interface of this device. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. |
|
Contains higher layer (i.e. non-MAC) matrix control entries. These entries will enable the collection of the network and application level matrix tables containing conversation statistics indexed by pairs of network addresses. Both the network and application level matrix tables are controlled by this table is so that they will both be created and deleted at the same time, further increasing the ease with which they can be implemented as a single datastore (note that if an implementation stores application layer matrix records in memory, it can derive network layer matrix records from them). Entries in the nlMatrixSDTable and nlMatrixDSTable will be created on behalf of each entry in this table. Additionally, if this probe implements the alMatrix tables, entries in the alMatrix tables will be created on behalf of each entry in this table. |
|
Contains traffic matrix entries which collect statistics for conversations between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all conversations from a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixDSTable with the same source address and destination address. |
|
Contains traffic matrix entries which collect statistics for conversations between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all conversations to a particular address. The probe will populate this table for all network layer protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, this table will only contain entries that have a corresponding entry in the nlMatrixSDTable with the same source address and destination address. |
|
Contains a set of parameters that control the creation of a report of the top N matrix entries according to a selected metric. |
|
Contains a set of statistics for those network layer matrix entries that have counted the highest number of octets or packets. |
|
Contains a collection of statistics for a particular protocol from a particular network address that has been discovered on an interface of this device. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirHostConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirHostConfig value of supportedOff(2). The probe will add to this table all addresses seen as the source or destination address in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address exists in the nlHostTable and will be deleted from this table if their address is deleted from the nlHostTable. |
|
Contains a list of application traffic matrix entries which collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the source address and then by the destination address to make it convenient to collect all statistics from a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixSDTable and will be deleted from this table if the address pair is deleted from the nlMatrixSDTable. |
|
Contains application traffic matrix entries which collect statistics for conversations of a particular protocol between two network-level addresses. This table is indexed first by the destination address and then by the source address to make it convenient to collect all statistics to a particular address. The probe will populate this table for all protocols in the protocol directory table whose value of protocolDirMatrixConfig is equal to supportedOn(3), and will delete any entries whose protocolDirEntry is deleted or has a protocolDirMatrixConfig value of supportedOff(2). The probe will add to this table all pairs of addresses for all protocols seen in all packets with no MAC errors, and will increment octet and packet counts in the table for all packets with no MAC errors. Further, entries will only be added to this table if their address pair exists in the nlMatrixDSTable and will be deleted from this table if the address pair is deleted from the nlMatrixDSTable. |
|
Contains a set of parameters that control the creation of a report of the top N matrix entries according to a selected metric. |
|
Contains a set of statistics for those application layer matrix entries that have counted the highest number of octets or packets. |
|
Contains a list of data-collection configuration entries. |
|
Contains a list of data-collection configuration entries. |
|
Contains a list of user defined history entries. |
|
Contains serial interface configuration entries. This data will be stored in non-volatile memory and preserved across probe resets or power loss. |
|
Contains netConfigEntries. |
|
Contains trap destination entries. |
|
Contains serialConnectionEntries. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Contains the RMON-2 augmentations to RMON-1. |
|
Provides a variable-length packet filter feature to the RMON-1 filter table. |
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).
RS-232-MIB Tables and Objects
Table 3-219 lists RS-232-MIBTables and Objects.
.
Table 3-219 RS-232-MIB Tables and Objects
|
|
|
Contains a list of port entries. The number of entries is given by the value of rs232Number. |
|
Contains a list of asynchronous port entries. Entries need not exist for synchronous ports. |
|
Contains a list of asynchronous port entries. Entries need not exist for synchronous ports. |
|
Contains a list of port input control signal entries implemented and visible to the software on the port, and useful to monitor. |
|
Contains a list of port output control signal entries implemented and visible to the software on the port, and useful to monitor. |
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).
RSVP-MIB Tables and Objects
Table 3-220 lists RSVP-MIB Tables and Objects.
.
Table 3-220 RSVP-MIB Tables and Objects
|
|
|
Contains all sessions seen by a given system. |
|
Contains information describing the state information displayed by senders in PATH messages. |
rsvpSenderOutInterfaceTable
|
List of outgoing interfaces that PATH messages use. The ifIndex is the ifIndex value of the egress interface. |
|
Information describing the state information displayed by receivers in RESV messages. |
|
Information describing the state information displayed upstream in RESV messages. |
|
The RSVP-specific attributes of the system’s interfaces. |
|
Information describing the Neighbors of an RSVP system. |
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).
SMON-MIB Tables and Objects
Table 3-221 lists SMON-MIB Tables and Objects.
.
Table 3-221 SMON-MIB Tables and Objects
|
|
|
Describes RMON data sources and port copy capabilities. An NMS MAY use this table to discover the identity and attributes of the data sources on a given agent implementation. Similar to the probeCapabilities object, actual row-creation operations will succeed or fail based on the resources available and parameter values used in each row-creation operation. Upon restart of the RMON agent, the dataSourceTable, ifTable, and perhaps entPhysicalTable are initialized for the available dataSources. For each dataSourceCapsEntry representing a VLAN or entPhysicalEntry the agent MUST create an associated ifEntry with a ifType value of ’propVirtual(53)’. This ifEntry will be used as the actual value in RMON control table dataSource objects. The assigned ifIndex value is copied into the associated dataSourceCapsIfIndex object. It is understood that dataSources representing VLANs may not always be instantiated immediately upon restart, but rather as VLAN usage is detected by the agent. The agent SHOULD attempt to create dataSource and interface entries for all dataSources as soon as possible. |
smonVlanStatsControlTable
|
Controls the setup of VLAN statistics tables. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection. |
|
Contains the VLAN statistics data. The statistics collected represent a distribution based on the IEEE 802.1Q VLAN-ID (VID), for each good frame attributed to the data source for the collection. This function applies the same rules for attributing frames to VLAN-based collections. RMON VLAN statistics are collected after the Ingress Rules defined in section 3.13 of the VLAN Specification [20] are applied. It is possible that entries in this table will be garbage-collected, based on agent resources, and VLAN configuration. Agents are encouraged to support all 4094 index values and not garbage collect this table. |
smonPrioStatsControlTable
|
Controls the setup of priority statistics tables. The smonPrioStatsControlTable allows configuration of collections based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19],[20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes. |
|
Contains the priority statistics. The collections are based on the value of the 3-bit user priority field encoded in the Tag Control Information (TCI) field according to [19], [20]. Note that this table merely reports priority as encoded in the VLAN headers, not the priority (if any) given to the frame for the actual switching purposes. No garbage collection is designed for this table, as there always are at most eight rows per statistical set, and the low memory requirements do not justify the implementation of such a mechanism. |
|
Port Copy provides the ability to copy all frames from a specified source to specified destination within a switch. Source and destinations MUST be ifEntries, as defined by [22]. One to one, one to many, many to one and many to many source to destination relationships may be configured. Applicable counters on the destination will increment for all packets transiting the port, be it by normal bridging/switching or due to packet copy. Note that this table manages no RMON data collection by itself, and an agent may possibly implement no RMON objects except objects related to the port copy operation defined by the portCopyCompliance conformance macro. That allows for a switch with no other embedded RMON capability to perform port copy operations to a destination port at which a different external RMON probe is connected. One to one, many to one and one to many source to destination relationships may be configured. Each row that exists in this table defines such a relationship. By disabling a row in this table the port copy relationship no longer exists. The number of entries and the types of port copies (1-1, many-1, 1-many) are implementation specific and could possibly be dynamic due to changing resource availability. In order to configure a source to destination portCopy relationship, both source and destination interfaces MUST be present as an ifEntry in the ifTable and their respective ifAdminStatus and ifOperStatus values MUST be equal to ’up(1)’. If the value of any of those two objects changes after the portCopyEntry is activated, portCopyStatus will transition to ’notReady(3)’. The capability of an interface to be source or destination of a port copy operation is described by the ’copySourcePort(0)’ and ’copyDestPort(1)’ bits in dataSourceCopyCaps. Those bits SHOULD be appropriately set by the agent, in order to allow for a portCopyEntry to be created. Applicable counters on the destination will increment for all packets transmitted, be it by normal bridging/switching or due to packet copy. |
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).
SNMP-COMMUNITY-MIB Tables and Objects
Table 3-222 lists SNMP-COMMUNITY-MIB Tables and Objects.
.
Table 3-222 SNMP-COMMUNITY-MIB Tables and Objects
|
|
|
Contains community strings configured in the SNMP engine’s Local Configuration Datastore (LCD). |
|
Contains mask and maximum message size (mms) values associated with the snmpTargetAddrTable. The snmpTargetAddrExtTable augments the snmpTargetAddrTable with a transport address mask value and a maximum message size value. The transport address mask allows entries in the snmpTargetAddrTable to define a set of addresses instead of just a single address. The maximum message size value allows the maximum message size of another SNMP entity to be configured for use in SNMPv1 (and SNMPv2c) transactions, where the message format does not specify a maximum message size. |
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).
Table 3-223 lists SNMP-FRAMEWORK-MIB Tables and Objects.
.
Table 3-223 SNMP-FRAMEWORK-MIB Tables and Objects
|
|
|
An SNMP engine's administratively-unique identifier. This information SHOULD be stored in non-volatile storage so that it remains constant across re-initializations of the SNMP engine. |
|
The number of times that the SNMP engine has (re-)initialized itself since snmpEngineID was last configured. |
|
The number of seconds since the value of the snmpEngineBoots object last changed. When incrementing this object's value would cause it to exceed its maximum, snmpEngineBoots is incremented as if a re-initialization had occurred, and this object's value consequently reverts to zero. |
|
The maximum length in octets of an SNMP message which this SNMP engine can send or receive and process, determined as the minimum of the maximum message size values supported among all of the transports available to and supported by the engine. |
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).
SNMP-MPD-MIB Tables and Objects
Table 3-224 lists SNMP-MPD-MIB Tables and Objects.
.
Table 3-224 SNMP-MPD-MIB Tables and Objects
|
|
snmpUnknownSecurityModels
|
Contains the total number of packets received by the SNMP engine which were dropped because they referenced a securityModel that was not known to or supported by the SNMP engine. |
|
Contains the total number of packets received by the SNMP engine which were dropped because there were invalid or inconsistent components in the SNMP message. |
|
Contains the total number of packets received by the SNMP engine which were dropped because the PDU contained in the packet could not be passed to an application responsible for handling the pduType, e.g. no SNMP application had registered for the proper combination of the contextEngineID and the pduType. |
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).
SNMP-NOTIFICATION-MIB Tables and Objects
Table 3-225 lists SNMP-NOTIFICATION-MIB Tables and Objects.
.
Table 3-225 SNMP-NOTIFICATION-MIB Tables and Objects
|
|
|
Used to select management targets which should receive notifications, as well as the type of notification which should be sent to each selected management target. |
snmpNotifyFilterProfileTable
|
Used to associate a notification filter profile with a particular set of target parameters. |
|
Filter profiles are used to determine whether particular management targets should receive particular notifications. When a notification is generated, it must be compared with the filters associated with each management target which is configured to receive notifications, in order to determine whether it may be sent to each such management target. A more complete discussion of notification filtering can be found in section 6. of [RFC2573]. |
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).
SNMP-PROXY-MIB Tables and Objects
Table 3-226 lists SNMP-PROXY-MIB Tables and Objects.
.
Table 3-226 SNMP-PROXY-MIB Tables and Objects
|
|
|
Contains translation parameters used by proxy forwarder applications for forwarding SNMP messages. |
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).
SNMP-TARGET-MIB Tables and Objects
Table 3-227 lists SNMP-TARGET-MIB Tables and Objects.
.
Table 3-227 SNMP-TARGET-MIBTables and Objects
|
|
|
Contains transport addresses to be used in the generation of SNMP messages. |
|
Contains SNMP target information to be used in the generation of SNMP messages. |
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).
SNMP-USM-MIB Tables and Objects
Table 3-228 lists SNMP-USM-MIB Tables and Objects.
.
Table 3-228 SNMP-USM-MIB Tables and Objects
|
|
|
An advisory lock used to allow several cooperating Command Generator Applications to coordinate their use of facilities to alter secrets in the usmUserTable. |
|
Contains the users configured in the SNMP engine's Local Configuration Datastore (LCD). |
|
Contains the user configured in the SNMP engine's Local Configuration Datastore (LCD) for the User-based Security Model. |
|
Contains SNMP engine's administratively-unique identifier. In a simple agent, this value is always that agent's own snmpEngineID value. |
|
Contains a human readable string representing the name of the user. |
|
Contains a human readable string representing the user in Security Model independent format. |
|
Contains a pointer to another conceptual row in this usmUserTable. The user in this other conceptual row is called the clone-from user. |
|
An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be authenticated, and if so, the type of authentication protocol which is used. |
|
An object, which when modified, causes the secret authentication key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. |
|
Behaves exactly as usmUserAuthKeyChange, with one notable difference: in order for the set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. |
|
An indication of whether messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, can be protected from disclosure, and if so, the type of privacy protocol which is used. |
|
An object, which when modified, causes the secret encryption key used for messages sent on behalf of this user to/from the SNMP engine identified by usmUserEngineID, to be modified via a one-way function. |
|
Behaves exactly as usmUserPrivKeyChange, with one notable difference: in order for the Set operation to succeed, the usmUserName of the operation requester must match the usmUserName that indexes the row which is targeted by this operation. |
|
A publicly-readable value which can be written as part of the procedure for changing a user's secret authentication and/or privacy key, and later read to determine whether the change of the secret was effected. |
|
Contains the storage type for this conceptual row. |
|
Contains the status of this conceptual row. |
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).
SNMP-VACM-MIB Tables and Objects
Table 3-229 lists SNMP-VACM-MIBTables and Objects.
.
Table 3-229 SNMPv2-MIB Tables and Objects
|
|
|
Provides information to SNMP Command Generator applications so that they can properly configure the vacmAccessTable to control access to all contexts at the SNMP entity. |
|
Information about a particular context. |
|
A human readable name identifying a particular context at a particular SNMP entity. |
|
Maps a combination of securityModel and securityName into a groupName which is used to define an access control policy for a group of principals. |
|
An entry in this table maps the combination of a securityModel and securityName into a groupName. |
|
The Security Model, by which the vacmSecurityName referenced by this entry is provided. |
|
The securityName for the principal, represented in a Security Model independent format, which is mapped by this entry to a groupName. |
|
The name of the group to which this entry (e.g., the combination of securityModel and securityName) belongs. |
vacmSecurityToGroupStorageType
|
Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. |
vacmSecurityToGroupStatus
|
The status of this conceptual row. Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the vacmSecurityToGroupStatus column is 'notReady'. In particular, a newly created row cannot be made active until a value has been set for vacmGroupName. |
|
Contains access rights for groups. Each entry is indexed by a groupName, a contextPrefix, a securityModel and a securityLevel. To determine whether access is allowed, one entry from this table needs to be selected and the proper viewName from that entry must be used for access control checking. |
|
Contains access right configured in the Local Configuration Datastore (LCD) authorizing access to an SNMP context.Entries in this table can use an instance value for object vacmGroupName even if no entry in table vacmAccessSecurityToGroupTable has a corresponding value for object vacmGroupName. |
|
In order to gain the access rights allowed by this conceptual row, a contextName must match exactly (if the value of vacmAccessContextMatch is 'exact') or partially (if the value of vacmAccessContextMatch is 'prefix') to the value of the instance of this object. |
|
In order to gain the access rights allowed by this conceptual row, this securityModel must be in use. |
|
Contains the minimum level of security required in order to gain the access rights allowed by this conceptual row. A securityLevel of noAuthNoPriv is less than authNoPriv which in turn is less than authPriv. If multiple entries are equally indexed except for this vacmAccessSecurityLevel index, then the entry which has the highest value for vacmAccessSecurityLevel is selected. |
|
If the value of this object is exact(1), then all rows where the contextName exactly matches vacmAccessContextPrefix are selected.If the value of this object is prefix(2), then all rows where the contextName whose starting octets exactly match vacmAccessContextPrefix are selected. This allows for a simple form of wildcarding. |
|
The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes read access. |
|
The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes write access. |
|
The value of an instance of this object identifies the MIB view of the SNMP context to which this conceptual row authorizes access for notifications. |
|
The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row. |
|
Contains the status of this conceptual row. |
MIB Constraints
There are no constraints on this MIB.
TCP-MIB
TheTCP-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).
TCP-MIB Tables and Objects
Table 3-231 lists TCP-MIB Tables and Objects.
.
Table 3-231 TCP-MIB Tables and Objects
|
|
|
Contains information about existing TCP connections. Note that unlike earlier TCP MIBs, there is a separate table for connections in the LISTEN state. |
|
Contains information about TCP listeners. A listening application can be represented in three possible ways: 1. An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a tcpListenerLocalAddressType of unknown (0) and a tcpListenerLocalAddress of ’’h (a zero-length octet-string). 2. An application that is willing to accept only IPv4 or IPv6 datagrams is represented by a tcpListenerLocalAddressType of the appropriate address type and a tcpListenerLocalAddress of ’0.0.0.0’ or ’::’ respectively. 3. An application that is listening for data destined only to a specific IP address, but from any remote system, is represented by a tcpListenerLocalAddressType of an appropriate address type, with tcpListenerLocalAddress as the specific local address. NOTE: The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 ’sockets’ to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1)). |
|
Contains information about existing IPv4-specific TCP connections or listeners. This table has been deprecated in favor of the version neutral tcpConnectionTable. |
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).
UDP-MIB Tables and Objects
Table 3-232 lists UDP-MIB Tables and Objects.
.
Table 3-232 UDP-MIB Tables and Objects
|
|
|
Contains information about this entity’s UDP endpoints on which a local application is currently accepting or sending datagrams. The address type in this table represents the address type used for the communication, irrespective of the higher-layer abstraction. For example, an application using IPv6 ’sockets’ to communicate via IPv4 between ::ffff:10.0.0.1 and ::ffff:10.0.0.2 would use InetAddressType ipv4(1). Unlike the udpTable in RFC 2013, this table also allows the representation of an application that completely specifies both local and remote addresses and ports. A listening application is represented in three possible ways: 1) An application that is willing to accept both IPv4 and IPv6 datagrams is represented by a udpEndpointLocalAddressType of unknown(0) and a udpEndpointLocalAddress of ’’h (a zero-length octet-string). 2) An application that is willing to accept only IPv4 or only IPv6 datagrams is represented by a udpEndpointLocalAddressType of the appropriate address type and a udpEndpointLocalAddress of ’0.0.0.0’ or ’::’ respectively. 3) An application that is listening for datagrams only for a specific IP address but from any remote system is represented by a udpEndpointLocalAddressType of the appropriate address type, with udpEndpointLocalAddress specifying the local address. In all cases where the remote is a wildcard, the udpEndpointRemoteAddressType is unknown(0), the udpEndpointRemoteAddress is ’’h (a zero-length octet-string), and the udpEndpointRemotePort is 0. If the operating system is demultiplexing UDP packets by remote address and port, or if the application has ’connected’ the socket specifying a default remote address and port, the udpEndpointRemote* values should be used to reflect this. |
|
Contains IPv4-specific UDP listener information. It contains information about all local IPv4 UDP end-points on which an application is currently accepting datagrams. |
MIB Constraints
There are no constraints on this MIB.