Network Router User Manual

A-2

Cisco 7304 Router MIB Specifications Guide

OL-4925-02

Appendix A Using MIBs

Managing Router Physical Entities

• Provides firmware and software information for chassis components

The entPhysicalTable enumerates the physical entities contained by the system. In addition, it classifies

each physical entity into a vendor type and class.

Note The sample outputs and values that appear throughout this chapter are only examples of what you can

view when using MIBs.

Physical Entity Management MIBs

The following MIBs are used to manage physical entities on the Cisco 7304:

• CISCO-ENTITY-ASSET-MIB—Contains asset tracking information (ID PROM contents) for the

physical entities listed in the entPhysicalTable of the ENTITY-MIB. The MIB provides

device-specific information for physical entities, including orderable part number, serial number,

manufacturing assembly number, and hardware, software, and firmware information.

• CISCO-ENTITY-FRU-CONTROL-MIB—Contains objects used to monitor and configure the

administrative and operational status of field replaceable units (FRUs), such as power supplies and

line cards, that are listed in the entPhysicalTable of the ENTITY-MIB.

• CISCO-ENTITY-VENDORTYPE-OID-MIB—Contains the object identifiers (OIDs) for all

physical entities in the router in the entPhysicalTable.

• CISCO-ENVMON-MIB—Contains information about the status of environmental sensors. For

example, the MIB reports the chassis core inlet temperatures.

• ENTITY-MIB—Contains information for managing physical entities on the router. It also organizes

the physical entities contained by a system into a tree, referred to as a containment tree. This tree

describes the relationship of each physical entity to all others. The ENTITY-MIB contains the

following tables:

–

The entPhysicalTable describes each physical component (entity) in the router. The table contains

an entry for the top-level entity (the chassis) and for each entity in the chassis. Each entry provides

information about that entity: its name, type, vendor, and a description, and describes how the

entity fits into the hierarchy of chassis entities. Each entity is identified by a unique index

(entPhysicalIndex) that is used to access information about the entity in this and other MIBs.

The entPhysicalTable which contains two managed objects that describe a physical entity’s

relationship to its parent:

• entPhysicalContainedIn – this object specifies the entPhysicalIndex of the physical entity

representing this physical entity’s parent; that is, the physical entity that contains this physical

entity. For example, a physical entity representing a slot (within a chassis) typically contains a

physical entity representing a line card. The slot is the parent of the line card.

• entPhysicalParentRelPos – this object specifies an integer value that represents this physical

entity’s relationship relative to its parent. For example, a physical entity representing a slot will

have an entPhysicalParentRelPos equal to the slot number of the physical slot it represents.

–

The entPhysicalContainsTable, which lists the children of each physical entity contained by the

system. This table provides the management client with another view of the parent-child

relationship between physical entities.