CISCO-ENTITY-EXT-MIB: View SNMP OID List / Download MIB

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.

The ceExtPhysicalProcessorTable extends the ENTITY-MIB entPhysicalTable for modules (Non FRUs(Field Replacable Units) or FRUs).

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.

Total number of bytes of RAM available on the Processor.

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.

Number of bytes of NVRAM in use. This object is irrelevant if ceExtNVRAMSize is 0.

This object represents the upper 32-bit of ceExtProcessorRam. This object needs to be supported only if the available RAM bytes exceeds 32-bit, otherwise this object value would be set to 0.

This object represents the total number of bytes of RAM available on the Processor. This object is a 64-bit version of ceExtProcessorRam.

The ceExtConfigRegTable extends the ENTITY-MIB entPhysicalTable.

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.

The value of configuration register with which the processor module booted.

The value of configuration register in the processor module at next reboot. Just after the reboot this has the same value as ceExtConfigRegister.

The list of system boot images which can be used for booting.

The list of system kickstart images which can be used for booting.

A table containing information of LED on an entity.

An entry (conceptual row) in the ceExtEntityLEDTable, containing information about an LED on an entity, identified by entPhysicalIndex.

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. Enumeration: 'status': 1, 'active': 3, 'battery': 5, 'system': 2, 'power': 4.

The color of the LED. Enumeration: 'amber': 3, 'green': 2, 'off': 1, 'red': 4.

This table contains additional information about a particular physical entity. This table augments the 'entPhysicalTable' of the ENTITY-MIB.

An entry (conceptual row) in the 'ceExtEntPhysicalTable', containing additional information about a physical entity, identified by 'entPhysicalIndex'.

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.

This object controls the generation of ceExtEntDoorCloseNotif and ceExtEntDoorOpenNotif notifications as follows: 'true(1)' - the generation of ceExtEntDoorCloseNotif and ceExtEntDoorOpenNotif notifications are enabled. 'false(2)' - the generation of ceExtEntDoorCloseNotif and ceExtEntDoorOpenNotif notifications are disabled.

This object controls the generation of ceExtBreakOutPortInserted and ceExtBreakOutPortRemoved as follows: 'true(1)' - the generation of ceExtBreakOutPortInserted and ceExtBreakOutPortRemoved notifications is enabled. 'false(2)' - the generation of ceExtBreakOutPortInserted and ceExtBreakOutPortRemoved notifications is disabled.

This object controls the generation of ceExtUSBModemPlugInNotif and ceExtUSBModemPlugOutNotif as follows: 'true(1)' - the generation of ceExtUSBModemPlugInNotif and ceExtUSBModemPlugOutNotif notifications is enabled. 'false(2)' - the generation of ceExtUSBModemPlugOutNotif and ceExtUSBModemPlugOutNotif notifications is disabled.

A table containing information of USB MODEMs on an entity.

An entry (conceptual row) in the ceExtUSBModemTable, containing information about an USB MODEM on an entity, identified by entPhysicalIndex.

The International Mobile Equipment Identifier (IMEI) of the USB-MODEM

The International Mobile Subscriber Identifier(IMSI) - for a GSM USB MODEM.

The Service Provider name for a USB MODEM.

The signal strength of the USB MODEM.

A ceExtEntDoorCloseNotif is generated if the door of an entity has been closed.

A ceExtEntDoorOpenNotif is generated if the door of an entity has been opened.

The ceExtBreakOutPortInserted notification indicates that a Breakout port was inserted. The varbind for this notification indicates the entPhysicalIndex of the inserted Breakout port, and the entPhysicalIndex of the BreakOut Port module that contains this port.

The ceExtBreakOutPortRemoved notification indicates that a Breakout Port was removed. The varbind for this notification indicates the entPhysicalIndex of the removed Breakout port, and the entPhysicalIndex of the BreakOut Port module that contains this port.

The ceExtUSBModemPlugInNotif notification indicates that a USB MODEM was inserted. The varbind for this notification indicates the entPhysicalDescr of the inserted USB MODEM, and the entPhysicalIndex of the USB MODEM's container.

The ceExtUSBModemPlugOutNotif notification indicates that a USB MODEM was removed. The varbind for this notification indicates the entPhysicalDescr of the removed USB MODEM, and the entPhysicalIndex of the USB MODEM's container.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

Compliance for SNMP Entities which support modules with CPU, NVRAM and configuration register.

The collection of objects which give information about the Processor RAM and NVRAM.

The collection of objects which give information about configuration register. Implementation of this group is optional.

A group containing an object providing information about the system boot images. Implementation of this group is optional.

A collection of objects for giving led information.

A group containing an object providing information about the system boot images. Implementation of this group is optional.

The collection of objects for providing additional information about the physical entity. Implementation of this group is optional.

The collection of Overflow (upper 32-bit) objects which provides information about physical processor, when the entity runs on 64-bit Operating System (OS). This group is optional for the entities which run on 32-bit OS.

The collection of High Capacity (HC) objects which provides information about physical processor, when the entity runs on 64-bit Operating System (OS). This group is optional for the entities which run on 32-bit OS.

A collection of objects providing the notification information for door entitites.

A collection of objects providing control for entity door notifications.

A collection of objects providing the notification information for supporting Breakout port feature.

A collection of objects providing control for Breakout Port notifications.

A collection of objects for giving USB MODEM config information.

A collection of notifications for USB MODEM removal and insertion.

A collection of objects providing control for USB MODEM notifications.