cisco-entity-ext-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-entity-ext-mib and use it to monitor vendor specific OID's.
cisco-entity-ext-mib file content
Object view of cisco-entity-ext-mib:
  
    
      | Scalar Object | 
    
  
  
    
      | ceExtPhysicalProcessorEntry | 
      .1.3.6.1.4.1.9.9.195.1.1.1 | 
    
    
      | 
        A ceExtPhysicalProcessorTable entry extends
        a corresponding entPhysicalTable entry of class
        module(entPhysicalClass = 'module').
        A processor module or line card which
        has a processor will have an entry in
        this table.
        A processor module or line card having
        multiple processors and is a SMP(Symmetric
        multi processor) system will have only
        one entry corresponding to all the processors
        since the resources defined below are shared.
        A processor module or line card having
        multiple processors and is not an SMP system
        would register the processors as separate entities.
        Entries are created by the agent at the system power-up
        or module insertion.
        Entries are removed when the module is reset or removed.
       | 
    
    
      | ceExtConfigRegEntry | 
      .1.3.6.1.4.1.9.9.195.1.2.1 | 
    
    
      | 
        A ceExtConfigRegTable entry extends
        a corresponding entPhysicalTable entry of class
        module which has a configuration register.
        Entries are created by the agent at the system power-up
        or module insertion.
        Entries are removed when the module is reset or
        removed.
       | 
    
    
      | ceExtEntityLEDEntry | 
      .1.3.6.1.4.1.9.9.195.1.3.1 | 
    
    
      | 
        An entry (conceptual row) in the ceExtEntityLEDTable,
        containing information about an LED on an entity, identified by
        entPhysicalIndex. 
       | 
    
    
      | ceExtEntPhysicalEntry | 
      .1.3.6.1.4.1.9.9.195.1.4.1 | 
    
    
      | 
        An entry (conceptual row) in the 'ceExtEntPhysicalTable',
        containing additional information about a physical entity,
        identified by 'entPhysicalIndex'.
       | 
    
  
  
    
      | Tabular Object | 
    
  
  
    
      | ceExtProcessorRam | 
      .1.3.6.1.4.1.9.9.195.1.1.1.1 | 
    
    
      | 
        Total number of bytes of RAM available on the
        Processor.
       | 
    
    
      | ceExtNVRAMSize | 
      .1.3.6.1.4.1.9.9.195.1.1.1.2 | 
    
    
      | 
        Total number of bytes of NVRAM in the entity.
        A value of 0 for this object means the entity
        does not support NVRAM or NVRAM information
        is not available.
       | 
    
    
      | ceExtNVRAMUsed | 
      .1.3.6.1.4.1.9.9.195.1.1.1.3 | 
    
    
      | 
        Number of bytes of NVRAM in use. This object
        is irrelevant if ceExtNVRAMSize is 0.
       | 
    
    
      | ceExtConfigRegister | 
      .1.3.6.1.4.1.9.9.195.1.2.1.1 | 
    
    
      | 
        The value of configuration register with which
        the processor module booted.
       | 
    
    
      | ceExtConfigRegNext | 
      .1.3.6.1.4.1.9.9.195.1.2.1.2 | 
    
    
      | 
        The value of configuration register in the
        processor module at next reboot. Just after
        the reboot this has the same value as
        ceExtConfigRegister.
       | 
    
    
      | ceExtSysBootImageList | 
      .1.3.6.1.4.1.9.9.195.1.2.1.3 | 
    
    
      | 
        The list of system boot images which
        can be used for booting.
       | 
    
    
      | ceExtKickstartImageList | 
      .1.3.6.1.4.1.9.9.195.1.2.1.4 | 
    
    
      | 
        The list of system kickstart images which
        can be used for booting.
       | 
    
    
      | ceExtEntityLEDType | 
      .1.3.6.1.4.1.9.9.195.1.3.1.1 | 
    
    
      | 
        The type of LED on this entity.
        'status' - indicates the entity status.
        'system' - indicates the overall system status.
        'active' - the redundancy status of a module, for e.g.
        supervisor module.
        'power'  - indicates sufficient power availability for all
        modules.
        'battery'- indicates the battery status. 
       | 
    
    
      | ceExtEntityLEDColor | 
      .1.3.6.1.4.1.9.9.195.1.3.1.2 | 
    
    
      | 
        The color of the LED.
       | 
    
    
      | ceEntPhysicalSecondSerialNum | 
      .1.3.6.1.4.1.9.9.195.1.4.1.1 | 
    
    
      | 
        This object represents the vendor-specific second
        serial number string for the physical entity.
        The first serial number string of the physical
        entity is represented in the value of corresponding
        instance of the 'entPhysicalSerialNum' object.
        On the first instantiation of an physical entity, the value
        of this object is the correct vendor-assigned second
        serial number, if this information is available to the agent.
        If the second serial number is unknown or non-existent, then
        the value of this object will be a zero-length string instead.
        Note that implementations which can correctly identify the
        second serial numbers of all installed physical entities do
        not need to provide write access to this object.
        Agents which cannot provide non-volatile storage for the
        second serial number strings are not required to implement
        write access for this object.
        Not every physical component will have a serial number, or
        even need one.  Physical entities for which the associated
        value of the entPhysicalIsFRU object is equal to 'false(2)'
        (e.g., the repeater ports within a repeater module), do not
        need their own unique serial number. An agent does not have
        to provide write access for such entities, and may return a
        zero-length string.
        If write access is implemented for an instance of
        'ceEntPhysicalSecondSerialNum', and a value is written into
        the instance, the agent must retain the supplied value in the
        'ceEntPhysicalSecondSerialNum' instance associated with the
        same physical entity for as long as that entity remains
        instantiated. This includes instantiations across all re-
        initializations/reboots of the network management system,
        including those which result in a change of the physical
        entity's entPhysicalIndex value.
       | 
    
  
  
    
      | Table | 
    
  
  
    
      | ceExtPhysicalProcessorTable | 
      .1.3.6.1.4.1.9.9.195.1.1 | 
    
    
      | 
        The ceExtPhysicalProcessorTable extends
        the ENTITY-MIB entPhysicalTable for modules
        (Non FRUs(Field Replacable Units) or FRUs).
       | 
    
    
      | ceExtConfigRegTable | 
      .1.3.6.1.4.1.9.9.195.1.2 | 
    
    
      | 
        The ceExtConfigRegTable extends
        the ENTITY-MIB entPhysicalTable.
       | 
    
    
      | ceExtEntityLEDTable | 
      .1.3.6.1.4.1.9.9.195.1.3 | 
    
    
      | 
        A table containing information of LED on an entity. 
       | 
    
    
      | ceExtEntPhysicalTable | 
      .1.3.6.1.4.1.9.9.195.1.4 | 
    
    
      | 
        This table contains additional information about
        a particular physical entity.
        This table augments the 'entPhysicalTable'  of
        the ENTITY-MIB.
       | 
    
  
  
    
      | Object Identifier | 
    
  
  
    
      | ciscoEntityExtMIB | 
      .1.3.6.1.4.1.9.9.195 | 
    
    
      | 
        This MIB is an extension of the ENTITY-MIB
        specified in RFC2737.
        This MIB module contains  Cisco-defined  extensions
        to the  entityPhysicalTable to represent information
        related to entities of class module(entPhysicalClass
        = 'module') which have a Processor.
        A processor module is defined as a physical entity
        that has a CPU, RAM and NVRAM  so that
        it can independently
        - load a bootable image
        - save configuration.
        This module is the entry point for external
        applications like SNMP Manager, CLI, FTP etc.
        Line card is an interface card	 with at least a
        Processor and RAM. This might be referred to as
        Service Module in some cisco products.
        A configuration register is  a 16 bit
        software register.
        The configuration register is mainly used to
        check for instructions on where to find the Cisco
        Operating System software.
        Some other functions of configuration register are:
        - To select a boot source and default boot filename.
        - To enable or disable the Break function.
        - To control broadcast addresses.
        - To set the console terminal baud rate.
        - To load operating software from Flash memory.
        - To allow us to manually boot the system using the
        boot command at the bootstrap program prompt.
        Booting is the process of initializing the
        hardware and starting the Operating System.
       | 
    
    
      | ciscoEntityExtMIBObjects | 
      .1.3.6.1.4.1.9.9.195.1 | 
    
    
      | ceExtMIBNotificationPrefix | 
      .1.3.6.1.4.1.9.9.195.2 | 
    
    
      | ciscoEntityExtMIBNotifications | 
      .1.3.6.1.4.1.9.9.195.2.0 | 
    
    
      | ciscoEntityExtMIBConformance | 
      .1.3.6.1.4.1.9.9.195.3 | 
    
    
      | ciscoEntityExtMIBCompliances | 
      .1.3.6.1.4.1.9.9.195.3.1 | 
    
    
      | ciscoEntityExtMIBGroups | 
      .1.3.6.1.4.1.9.9.195.3.2 | 
    
  
  
    
      | Group | 
    
  
  
    
      | ceExtPhysicalProcessorGroup | 
      .1.3.6.1.4.1.9.9.195.3.2.1 | 
    
    
      | 
        The collection of objects which give information about
        the Processor RAM and NVRAM.
       | 
    
    
      | ciscoEntityExtConfigRegGroup | 
      .1.3.6.1.4.1.9.9.195.3.2.2 | 
    
    
      | 
        The collection of objects which give information about
        configuration register.
        Implementation of this group is optional.
       | 
    
    
      | ceExtSysBootImageListGroup | 
      .1.3.6.1.4.1.9.9.195.3.2.3 | 
    
    
      | 
        A group containing an object providing information
        about the system boot images.
        Implementation of this group is optional.
       | 
    
    
      | ciscoEntityExtLEDGroup | 
      .1.3.6.1.4.1.9.9.195.3.2.4 | 
    
    
      | 
        A collection of objects for giving led information.
       | 
    
    
      | ceExtSysBootImageListGroupRev1 | 
      .1.3.6.1.4.1.9.9.195.3.2.5 | 
    
    
      | 
        A group containing an object providing information
        about the system boot images.
        Implementation of this group is optional.
       | 
    
    
      | ciscoExtEntityPhysicalGroup | 
      .1.3.6.1.4.1.9.9.195.3.2.6 | 
    
    
      | 
        The collection of objects for providing additional
        information about the physical entity.
        Implementation of this group is optional.
       |