CISCO-CONTENT-NETWORK-MIB

        This MIB module defines objects for Content Network devices.
        
A Content Network is a collection of devices that optimizes the
delivery of Internet content (such as HTML documents and MPEG
files) by caching content near clients, by proactively pushing
content into those caches, and by routing each client request to
the best device available at that moment to serve the particular
content requested.
        
Content Network devices include Content Engines (CEs) for
serving content, Content Routers (CRs) for routing client
requests, and Content Distribution Managers (CDMs) for
administering the network.
    
Source file
CISCO-CONTENT-NETWORK-MIB
Last revised
Identity
ciscoContentNetworkMIB
Base OID
1.3.6.1.4.1.9.9.216
Imported Objects
CISCO-SMI ciscoMgmt
RMON2-MIB ZeroBasedCounter32
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Gauge32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-CONTENT-NETWORK-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-CONTENT-NETWORK-MIB::ciscoContentNetworkMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-CONTENT-NETWORK-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-CONTENT-NETWORK-MIB::ciscoContentNetworkMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (17)
.1.3.6.1.4.1.9.9.216
.1.3.6.1.4.1.9.9.216.1
.1.3.6.1.4.1.9.9.216.1.1
.1.3.6.1.4.1.9.9.216.1.1.1
requests-per-secondSNMPv2-SMIGauge32
.1.3.6.1.4.1.9.9.216.1.1.1.1
.1.3.6.1.4.1.9.9.216.1.1.1.2
.1.3.6.1.4.1.9.9.216.1.1.1.3
.1.3.6.1.4.1.9.9.216.1.1.2
.1.3.6.1.4.1.9.9.216.1.1.2.1
.1.3.6.1.4.1.9.9.216.1.1.2.2
objects-per-minuteSNMPv2-SMIGauge32
.1.3.6.1.4.1.9.9.216.1.1.2.3
objects-per-minuteSNMPv2-SMIGauge32
.1.3.6.1.4.1.9.9.216.1.1.2.4
.1.3.6.1.4.1.9.9.216.2
.1.3.6.1.4.1.9.9.216.2.0
.1.3.6.1.4.1.9.9.216.3
.1.3.6.1.4.1.9.9.216.3.1
.1.3.6.1.4.1.9.9.216.3.2
Dependencies (14) 4 direct · 10 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (3)
DNS and Accounting with low capacity Counter32 and Gauge32
objects.
.1.3.6.1.4.1.9.9.216.3.2.1
ccnNotifGroup deprecated
Notifications for the Cisco Content Network.This object is
deprecated by ccnNotifGroupRev1.
.1.3.6.1.4.1.9.9.216.3.2.2
Notifications for the Cisco Content Network.
.1.3.6.1.4.1.9.9.216.3.2.3
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.216.3.1.1
The compliance statement for Cisco Systems entities which
implement the Content Network applications. This object is
deprecated by ccnMIBComplianceRev1.
Required groups

OID .1.3.6.1.4.1.9.9.216.3.1.2
The compliance statement for Cisco Systems entities which
implement the Content Network applications.
Required groups
Notifications / Traps (6)
NameOIDDescription
.1.3.6.1.4.1.9.9.216.2.0.1
The servers on this device are being started. This object is
deprecated by ccnNotifOnline.
.1.3.6.1.4.1.9.9.216.2.0.2
The servers on this device are being stopped. This object is
deprecated by ccnNotifOnline, ccnNotifNeedsAttention and
ccnNotifWaitingForCdm.
.1.3.6.1.4.1.9.9.216.2.0.3
The device is about to disconnect from the network.
.1.3.6.1.4.1.9.9.216.2.0.4
The device is on the network, but is unregistered (not
associated with any CDN) or needs some other adjustment which
cannot be done via the CDM administrator interface (such as
repairing a disk, completing a software upgrade, or configuring
the CDM database).
.1.3.6.1.4.1.9.9.216.2.0.5
The device (CE or CR) is waiting for configuration information
from the CDM. The device is on the network and is either
failing to communicate with the CDM or is being told explictly
by the CDM to continue waiting pending activation by the CDN
administrator.
.1.3.6.1.4.1.9.9.216.2.0.6
The device is operational and ready to participate in the CDN.