cisco-content-network-mib.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file cisco-content-network-mib and use it to monitor vendor specific OID's.
cisco-content-network-mib file content
Object view of cisco-content-network-mib:
  
    
      | Scalar Object | 
    
  
  
    
      | ccnReportDnsRequestRate | 
      .1.3.6.1.4.1.9.9.216.1.1.1.1 | 
    
    
      | 
        Number of DNS requests per second.
       | 
    
    
      | ccnReportDnsClientCount | 
      .1.3.6.1.4.1.9.9.216.1.1.1.2 | 
    
    
      | 
        Total number of DNS clients that have contacted this device
        since the DNS server last started.
       | 
    
    
      | ccnReportDnsRequests | 
      .1.3.6.1.4.1.9.9.216.1.1.1.3 | 
    
    
      | 
        Total number of DNS requests since the DNS server
        last started.
       | 
    
    
      | ccnReportAcctBytesServed | 
      .1.3.6.1.4.1.9.9.216.1.1.2.1 | 
    
    
      | 
        Total number of bytes of content served to clients
        from this device since the servers on this device last
        started.
       | 
    
    
      | ccnReportAcctObjectsCached | 
      .1.3.6.1.4.1.9.9.216.1.1.2.2 | 
    
    
      | 
        Total number of objects in the content cache.
       | 
    
    
      | ccnReportAcctCacheHitRate | 
      .1.3.6.1.4.1.9.9.216.1.1.2.3 | 
    
    
      | 
        Number of cache hits per minute.
       | 
    
    
      | ccnReportAcctCacheMissRate | 
      .1.3.6.1.4.1.9.9.216.1.1.2.4 | 
    
    
      | 
        Number of cache misses per minute.
       | 
    
  
  
    
      | Trap | 
    
  
  
    
      | ccnNotifServerStart | 
      .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.
       | 
    
    
      | ccnNotifServerStop | 
      .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.
       | 
    
    
      | ccnNotifOffline | 
      .1.3.6.1.4.1.9.9.216.2.0.3 | 
    
    
      | 
        The device is about to disconnect from the network.
       | 
    
    
      | ccnNotifNeedsAttention | 
      .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).
       | 
    
    
      | ccnNotifWaitingForCdm | 
      .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.
       | 
    
    
      | ccnNotifOnline | 
      .1.3.6.1.4.1.9.9.216.2.0.6 | 
    
    
      | 
        The device is operational and ready to participate in the CDN.
       | 
    
  
  
    
      | Object Identifier | 
    
  
  
    
      | ciscoContentNetworkMIB | 
      .1.3.6.1.4.1.9.9.216 | 
    
    
      | 
        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.
       | 
    
    
      | ciscoContentNetworkMIBObjects | 
      .1.3.6.1.4.1.9.9.216.1 | 
    
    
      | ccnReport | 
      .1.3.6.1.4.1.9.9.216.1.1 | 
    
    
      | ccnReportDns | 
      .1.3.6.1.4.1.9.9.216.1.1.1 | 
    
    
      | ccnReportAcct | 
      .1.3.6.1.4.1.9.9.216.1.1.2 | 
    
    
      | ciscoContentNetworkMIBNotif | 
      .1.3.6.1.4.1.9.9.216.2 | 
    
    
      | ccnNotifications | 
      .1.3.6.1.4.1.9.9.216.2.0 | 
    
    
      | ccnMIBConformance | 
      .1.3.6.1.4.1.9.9.216.3 | 
    
    
      | ccnMIBCompliances | 
      .1.3.6.1.4.1.9.9.216.3.1 | 
    
    
      | ccnMIBGroups | 
      .1.3.6.1.4.1.9.9.216.3.2 | 
    
  
  
    
      | Group | 
    
  
  
    
      | ccnReportingGroup | 
      .1.3.6.1.4.1.9.9.216.3.2.1 | 
    
    
      | 
        DNS and Accounting with low capacity Counter32 and Gauge32
        objects.
       | 
    
    
      | ccnNotifGroup | 
      .1.3.6.1.4.1.9.9.216.3.2.2 | 
    
    
      | 
        Notifications for the Cisco Content Network.This object is
        deprecated by ccnNotifGroupRev1.
       | 
    
    
      | ccnNotifGroupRev1 | 
      .1.3.6.1.4.1.9.9.216.3.2.3 | 
    
    
      | 
        Notifications for the Cisco Content Network.
       |