CISCO-ENTITY-FRU-CONTROL-MIB

TEXTUAL-CONVENTION

An integer that is in the range of a percent value. A value of -1 means that the percentage is not available.

TEXTUAL-CONVENTION

Operational VM module states. Valid values are : down(1) module is down. up(2) module is operational. unknown(3) module is unknown. goingDown(4) module is goingDown from Up.

TEXTUAL-CONVENTION

The unit for the cooling capacity and requirement. cfm(1) Cubic feet per minute watts(2) Watts

TEXTUAL-CONVENTION

a current measurement, on the system power supply primary output, expressed in cefcPowerUnits. Range is from negative 1 million to positive one million amperes. A negative value expresses current used by the FRU. A positive value expresses current supplied by the FRU.

TEXTUAL-CONVENTION

This is a non-negative integer which represents the time in second between two epochs. Since time is not discrete, it is rounded up to the nearest second. For example, if the elapsed time is greater than zero and less or equal to one second, then one second is returned, etc. When objects are defined which use this type, the description of the object identifies both of the reference epochs.

TEXTUAL-CONVENTION

Administratively desired module states. Valid values are: enabled(1) module is operational. disabled(2) module is not operational. reset(3) module is reset. This value may be specified in a management protocol set operation, it will not be returned in response to a management protocol retrieval operation. outOfServiceAdmin(4) module is powered on but out of service, set by CLI.

TEXTUAL-CONVENTION

Operational module states. Valid values are : unknown(1) Module is not in one of other states normal operational states: ok(2) Module is operational. disabled(3) Module is administratively disabled. okButDiagFailed(4) Module is operational but there is some diagnostic information available. transitional states: boot(5) Module is currently in the process of bringing up image. After boot, it starts its operational software and transitions to the appropriate state. selfTest(6) Module is performing selfTest. failure states: failed(7) Module has failed due to some condition not stated above. missing(8) Module has been provisioned, but it is missing mismatchWithParent(9) Module is not compatible with parent entity. Module has not been provisioned and wrong type of module is plugged in. This state can be cleared by plugging in the appropriate module. mismatchConfig(10) Module is not compatible with the current configuration. Module was correctly provisioned earlier, however the module was replaced by an incompatible module. This state can be resolved by clearing the configuration, or replacing with the appropriate module. diagFailed(11) Module diagnostic test failed due to some hardware failure. dormant(12) Module is waiting for an external or internal event to become operational. outOfServiceAdmin(13) module is administratively set to be powered on but out of service. outOfServiceEnvTemp(14)Module is powered on but out of service, due to environmental temperature problem. An out-o-service module consumes less power thus will cool down the board. poweredDown(15) Module is in powered down state. poweredUp(16) Module is in powered up state. powerDenied(17) System does not have enough power in power budget to power on this module. powerCycled(18) Module is being power cycled. okButPowerOverWarning(19) Module is drawing more power than allocated to this module. The module is still operational but may go into a failure state. This state may be caused by misconfiguration of power requirements (especially for inline power). okButPowerOverCritical(20) Module is drawing more power than this module is designed to handle. The module is still operational but may go into a failure state and could potentially take the system down. This state may be caused by gross misconfi- guration of power requirements (especially for inline power). syncInProgress(21) Synchronization in progress. In a high availability system there will be 2 control modules, active and standby. This transitional state specifies the synchronization of data between the active and standby modules. upgrading(22) Module is upgrading. okButAuthFailed(23) Module is operational but did not pass hardware integrity verification. mdr(24) Module is undergoing a Minimum Disruptive Restart (MDR) upgrade. firmware download states: fwMismatchFound(25) Mistmatch found between current firmware version and the firmware version in the system image. fwDownloadSuccess(26) Module firmware download succeeded. fwDownloadFailure(27) Module firmware download failed.

TEXTUAL-CONVENTION

Describes the reason for the last module reset operation. unknown(1) source of the reset is not identified powerUp(2) system power up operation parityError(3) parity error during system bring up operation clearConfigReset(4) reset due to clear configuration operation manualReset(5) reset due to administrative request watchDogTimeoutReset(6) reset due to watchdog timeout resourceOverflowReset(7) reset due to resource overflow missingTaskReset(8) reset due to missing task lowVoltageReset(9) reset due to low voltage controllerReset(10) reset by controller systemReset(11) system reset switchoverReset(12) reset due to user initiated graceful switchover upgradeReset(13) reset due to upgrade downgradeReset(14) reset due to downgrade cacheErrorReset(15) reset due to cache error deviceDriverReset(16) reset due to device driver error softwareExceptionReset(17) reset due to software exception restoreConfigReset(18) reset due to configuration restoration abortRevReset(19) reset due to revision change abort burnBootReset(20) reset due to boot image change standbyCdHealthierReset(21) reset to switch to healthier standby card nonNativeConfigClearReset(22) reset due clearing of non-native configuration memoryProtectionErrorReset(23) reset due to memory protection violation.

TEXTUAL-CONVENTION

Administratively desired FRU power state types. valid values are: on(1): Turn FRU on. off(2): Turn FRU off. The inline power means that the FRU itself won't cost any power, but the external device connecting to the FRU will drain the power from FRU. For example, the IP phone device. The FRU is a port of a switch with voice ability and IP phone will cost power from the port once it connects to the port. inlineAuto(3): Turn FRU inline power to auto mode. It means that the FRU will try to detect whether the connecting device needs power or not. If it needs power, the FRU will supply power. If it doesn't, the FRU will treat the device as a regular network device. inlineOn(4): Turn FRU inline power to on mode. It means that once the device connects to the FRU, the FRU will always supply power to the device no matter the device needs the power or not. powerCycle(5): Power cycle the FRU. This value may be specified in a management protocol set operation, it will not be returned in response to a management protocol retrieval operation.

TEXTUAL-CONVENTION

Operational FRU Status types. valid values are: offEnvOther(1) FRU is powered off because of a problem not listed below. on(2): FRU is powered on. offAdmin(3): Administratively off. offDenied(4): FRU is powered off because available system power is insufficient. offEnvPower(5): FRU is powered off because of power problem in the FRU. for example, the FRU's power translation (DC-DC converter) or distribution failed. offEnvTemp(6): FRU is powered off because of temperature problem. offEnvFan(7): FRU is powered off because of fan problems. failed(8): FRU is in failed state. onButFanFail(9): FRU is on, but fan has failed. offCooling(10): FRU is powered off because of the system's insufficient cooling capacity. offConnectorRating(11): FRU is powered off because of the system's connector rating exceeded. onButInlinePowerFail(12): The FRU on, but no inline power is being delivered as the data/inline power component of the FRU has failed.

TEXTUAL-CONVENTION

power supply redundancy modes. valid values are: notsupported(1): Read-only operational state, indicates that the requested administrative state (redundant(2), combined(3), psRedundant(5), inPwrSrcRedundant(6) or psRedundantSingleInput(7)) is not supported by the system. redundant(2): A single power supply output can power the entire system, although there are more than one matched supply in the system. In the systems which support multiple level of redundancy, such as input power redundancy, this state indicates that redundancy is enabled on all levels. combined(3): The combined output of the power supplies are available to operate the system when there are more than one matched power supply in the system. In the platforms which support multiple level of redundancy, such as input redundancy, this state indicates that no redundancy on all levels. nonRedundant(4): Read-only operational state, indicates that there is only one power supply or there are unmatched power supplies in the system. psRedundant(5): Only the power output redundancy is enabled in the systems which support multiple levels of redundancy. All other types of redundancy, such as input power redundancy, are disabled. This value is only supported by the systems which support multiple levels of redundancy. inPwrSrcRedundant(6): Only the input power redundancy is enabled in the systems which support multiple levels of redundancy. All other types of redundancy, such as output power redundancy, are disabled. This value is only supported by the systems which support input power redundancy. psRedundantSingleInput(7): Only the power redundancy with single input is enabled in the systems which support multiple levels of redundancy. All other types of redundancy, such as output power redundancy, are disabled. This value is only supported by the systems which support power redundancy with single input.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This table lists the redundancy mode and the operational status of the power supply groups in the system.

OBJECT-TYPE

An cefcFRUPowerSupplyGroupTable entry lists the desired redundancy mode, the units of the power outputs and the available and drawn current for the power supply group. Entries are created by the agent when a power supply group is added to the entPhysicalTable. Entries are deleted by the agent at power supply group removal.

OBJECT-TYPE

The administratively desired power supply redundancy mode.

OBJECT-TYPE

The units of primary supply to interpret cefcTotalAvailableCurrent and cefcTotalDrawnCurrent as power. For example, one 1000-watt power supply could deliver 100 amperes at 10 volts DC. So the value of cefcPowerUnits would be 'at 10 volts DC'. cefcPowerUnits is for display purposes only.

OBJECT-TYPE

Total current available for FRU usage.

OBJECT-TYPE

Total current drawn by powered-on FRUs.

OBJECT-TYPE

The power supply redundancy operational mode.

OBJECT-TYPE

This object has the value of notApplicable(1) when cefcPowerRedundancyOperMode of the instance does not have the value of nonRedundant(4). The other values explain the reason why cefcPowerRedundancyOperMode is nonRedundant(4), e.g. unknown(2) the reason is not identified. singleSupply(3) There is only one power supply in the group. mismatchedSupplies(4) There are more than one power supplies in the groups. However they are mismatched and can not work redundantly. supplyError(5) Some power supply or supplies does or do not working properly.

OBJECT-TYPE

Total inline current drawn for inline operation.

OBJECT-TYPE

This table lists the power-related administrative status and operational status of the manageable components in the system.

OBJECT-TYPE

An cefcFRUPowerStatusTable entry lists the desired administrative status, the operational status of the power manageable component, and the current required by the component for operation. Entries are created by the agent at system power-up or the insertion of the component. Entries are deleted by the agent at the removal of the component. Only components with power control are listed in the table.

OBJECT-TYPE

Administratively desired FRU power state.

OBJECT-TYPE

Operational FRU power state.

OBJECT-TYPE

Current supplied by the FRU (positive values) or current required to operate the FRU (negative values).

OBJECT-TYPE

This object indicates the set of supported power capabilities of the FRU. realTimeCurrent(0) - cefcFRURealTimeCurrent is supported by the FRU.

OBJECT-TYPE

This object indicates the realtime value of current supplied by the FRU (positive values) or the realtime value of current drawn by the FRU (negative values).

OBJECT-TYPE

The system will provide power to the device connecting to the FRU if the device needs power, like an IP Phone. We call the providing power inline power. This MIB object controls the maximum default inline power for the device connecting to the FRU in the system. If the maximum default inline power of the device is greater than the maximum value reportable by this object, then this object should report its maximum reportable value (12500) and cefcMaxDefaultHighInLinePower must be used to report the actual maximum default inline power.

OBJECT-TYPE

This table lists the power capacity of a power FRU in the system if it provides variable power. Power supplies usually provide either system or inline power. They cannot be controlled by software to dictate how they distribute power. We can also have what are known as variable power supplies. They can provide both system and inline power and can be varied within hardware defined ranges for system and inline limited by a total maximum combined output. They could be configured by the user via CLI or SNMP or be controlled by software internally. This table supplements the information in the cefcFRUPowerStatusTable for power supply FRUs. The cefcFRUCurrent attribute in that table provides the overall current the power supply FRU can provide while this table gives us the individual contribution towards system and inline power.

OBJECT-TYPE

An cefcFRUPowerSupplyValueTable entry lists the current provided by the FRU for operation. Entries are created by the agent at system power-up or FRU insertion. Entries are deleted by the agent at FRU removal. Only power supply FRUs are listed in the table.

OBJECT-TYPE

Total current that could be supplied by the FRU (positive values) for system operations.

OBJECT-TYPE

Amount of current drawn by the FRU's in the system towards system operations from this FRU

OBJECT-TYPE

Total current supplied by the FRU (positive values) for inline operations.

OBJECT-TYPE

Amount of current that is being drawn from this FRU for inline operation.

OBJECT-TYPE

Amount of actual input current of this power supply.

OBJECT-TYPE

Amount of actual output current of this power supply.

OBJECT-TYPE

The system will provide power to the device connecting to the FRU if the device needs power, like an IP Phone. We call the providing power inline power. This MIB object controls the maximum default inline power for the device connecting to the FRU in the system.

OBJECT-IDENTITY

OBJECT-TYPE

A cefcModuleTable entry lists the operational and administrative status information for ENTITY-MIB entPhysicalTable entries for manageable components of type PhysicalClass module(9).

OBJECT-TYPE

A cefcModuleStatusTable entry lists the operational and administrative status information for ENTITY-MIB entPhysicalTable entries for manageable components of type PhysicalClass module(9). Entries are created by the agent at the system power-up or module insertion. Entries are deleted by the agent upon module removal.

OBJECT-TYPE

This object provides administrative control of the module.

OBJECT-TYPE

This object shows the module's operational state.

OBJECT-TYPE

This object identifies the reason for the last reset performed on the module.

OBJECT-TYPE

The value of sysUpTime at the time the cefcModuleOperStatus is changed.

OBJECT-TYPE

The value of sysUpTime when the configuration was most recently cleared.

OBJECT-TYPE

A description qualifying the module reset reason specified in cefcModuleResetReason. Examples: command xyz missing task switch over watchdog timeout etc. cefcModuleResetReasonDescription is for display purposes only. NMS applications must not parse.

OBJECT-TYPE

This object displays human-readable textual string which describes the cause of the last state change of the module. This object contains zero length string if no meaningful reason could be provided. Examples: 'Invalid software version' 'Software download failed' 'Software version mismatch' 'Module is in standby state' etc. This object is for display purposes only. NMS applications must not parse this object and take any decision based on its value.

OBJECT-TYPE

This object provides the up time for the module since it was last re-initialized. This object is not persistent; if a module reset, restart, power off, the up time starts from zero.

OBJECT-TYPE

This object indicates the VM module's operational state.

OBJECT-TYPE

The value of sysUpTime at the time the cefcVmModuleOperStatus is changed.

OBJECT-TYPE

This table sparsely augments the cefcModuleTable (i.e., every row in this table corresponds to a row in the cefcModuleTable but not necessarily vice-versa). A cefcIntelliModuleTable entry lists the information specific to intelligent modules which cannot be provided by the cefcModuleTable.

OBJECT-TYPE

A cefcIntelliModuleTable entry lists the information specific to an intelligent module which cannot be provided by this module's corresponding instance in the cefcModuleTable. Only an intelligent module with Internet address configured has its entry here. An entry of this table is created if an intelligent module is detected by the managed system and its management Internet address is configured on the intelligent module. An entry of this table is deleted if the removal of Internet address configuration of this module or the module itself.

OBJECT-TYPE

The type of Internet address by which the intelligent module is reachable.

OBJECT-TYPE

The Internet address configured for the intelligent module. The type of this address is determined by the value of the object cefcIntelliModuleIPAddrType.

OBJECT-TYPE

This table sparsely augments the cefcModuleTable (i.e., every row in this table corresponds to a row in the cefcModuleTable but not necessarily vice-versa). A cefcModuleLocalSwitchingTable entry lists the information specific to local switching capable modules which cannot be provided by the cefcModuleTable.

OBJECT-TYPE

A cefcModuleLocalSwitchingTable entry lists the information specific to a local switching capable module which cannot be provided by this module's corresponding instance in the cefcModuleTable. Only a module which is capable of local switching has its entry here. An entry of this table is created if a module which is capable of local switching is detected by the managed system. An entry of this table is deleted if the removal of this module.

OBJECT-TYPE

This object specifies the mode of local switching. enabled(1) - local switching is enabled. disabled(2) - local switching is disabled.

OBJECT-IDENTITY

OBJECT-TYPE

This variable indicates whether the system produces the following notifications: cefcModuleStatusChange, cefcPowerStatusChange, cefcFRUInserted, cefcFRURemoved, cefcUnrecognizedFRU, cefcFanTrayStatusChange and cefcVmModuleStatusChangeNotif. A false value will prevent these notifications from being generated.

OBJECT-TYPE

This variable indicates whether the system produces the cefcPowerSupplyOutputChange notifications when the output capacity of a power supply has changed. A false value will prevent this notification to generated.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains the operational status information for all ENTITY-MIB entPhysicalTable entries which have an entPhysicalClass of 'fan'; specifically, all entPhysicalTable entries which represent either: one physical fan, or a single physical 'fan tray' which is a manufactured (inseparable in the field) combination of multiple fans.

OBJECT-TYPE

An cefcFanTrayStatusTable entry lists the operational status information for the ENTITY-MIB entPhysicalTable entry which is identified by the value of entPhysicalIndex. The value of entPhysicalClass for the identified entry will be 'fan', and the represented physical entity will be either: one physical fan, or a single physical 'fan tray' which is a manufactured (inseparable in the field) combination of multiple fans. Entries are created by the agent at system power-up or fan or fan tray insertion. Entries are deleted by the agent at the fan or fan tray removal.

OBJECT-TYPE

The operational state of the fan or fan tray. unknown(1) - unknown. up(2) - powered on. down(3) - powered down. warning(4) - partial failure, needs replacement as soon as possible.

OBJECT-TYPE

The air flow direction of the fan or fan tray. unknown(1) - unknown. frontToBack(2) - air flow from front to back backToFront(3) - air flow from back to front

OBJECT-TYPE

This table contains a list of fan information for all the fans that have entPhysicalTable entries with 'fan' in the entPhysicalClass and capable of providing management information defined in this table.

OBJECT-TYPE

An entry containing management information applicable to a particular fan unit. Entries are created by the agent at system power-up or fan or fan tray insertion. Entries are deleted by the agent at the fan or fan tray removal.

OBJECT-TYPE

The speed of the fan.

OBJECT-TYPE

The percent of speed relative to the maximum speed of the fan.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains one row per physical entity.

OBJECT-TYPE

Information about a particular physical entity.

OBJECT-TYPE

The status of this physical entity. other(1) - the status is not any of the listed below. supported(2) - this entity is supported. unsupported(3) - this entity is unsupported. incompatible(4) - this entity is incompatible. It would be unsupported(3), if the ID read from Serial EPROM is not supported. It would be incompatible(4), if in the present configuration this FRU is not supported.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains the power input information for all the power supplies that have entPhysicalTable entries with 'powerSupply' in the entPhysicalClass. The entries are created by the agent at the system power-up or power supply insertion. Entries are deleted by the agent upon power supply removal. The number of entries is determined by the number of power supplies and number of power inputs on the power supply.

OBJECT-TYPE

An entry containing power input management information applicable to a particular power supply and input.

OBJECT-TYPE

A unique value, greater than zero, for each input on a power supply.

OBJECT-TYPE

The type of an input power detected on the power supply. unknown(1): No input power is detected. acLow(2): Lower rating AC input power is detected. acHigh(3): Higher rating AC input power is detected. dcLow(4): Lower rating DC input power is detected. dcHigh(5): Higher rating DC input power is detected.

OBJECT-TYPE

This table contains a list of possible output mode for the power supplies, whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of 'powerSupply'. It also indicate which mode is the operational mode within the system.

OBJECT-TYPE

A cefcPowerSupplyOutputTable entry lists the power output capacity and its operational status for manageable components of type PhysicalClass 'powerSupply'. Entries are created by the agent at the system power-up or power supply insertion. Entries are deleted by the agent upon power supply removal. The number of entries of a power supply is determined by the power supply.

OBJECT-TYPE

A unique value, greater than zero, for each possible output mode on a power supply.

OBJECT-TYPE

The output capacity of the power supply.

OBJECT-TYPE

A value of 'true' indicates that this mode is the operational mode of the power supply output capacity. A value of 'false' indicates that this mode is not the operational mode of the power supply output capacity. For a given power supply's entPhysicalIndex, at most one instance of this object can have the value of true(1).

OBJECT-IDENTITY

OBJECT-TYPE

This table contains the cooling capacity information of the chassis whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of 'chassis'.

OBJECT-TYPE

A cefcChassisCoolingEntry lists the maximum cooling capacity that could be provided for one slot on the manageable components of type PhysicalClass 'chassis'. Entries are created by the agent if the corresponding entry is created in ENTITY-MIB entPhysicalTable. Entries are deleted by the agent if the corresponding entry is deleted in ENTITY-MIB entPhysicalTable.

OBJECT-TYPE

The maximum cooling capacity that could be provided for any slot in this chassis. The default unit of the cooling capacity is 'cfm', if cefcChassisPerSlotCoolingUnit is not supported.

OBJECT-TYPE

The unit of the maximum cooling capacity for any slot in this chassis.

OBJECT-TYPE

This table contains the cooling capacity information of the fans whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of 'fan'.

OBJECT-TYPE

A cefcFanCoolingEntry lists the cooling capacity that is provided by the manageable components of type PhysicalClass 'fan'. Entries are created by the agent if the corresponding entry is created in ENTITY-MIB entPhysicalTable. Entries are deleted by the agent if the corresponding entry is deleted in ENTITY-MIB entPhysicalTable.

OBJECT-TYPE

The cooling capacity that is provided by this fan. The default unit of the fan cooling capacity is 'cfm', if cefcFanCoolingCapacityUnit is not supported.

OBJECT-TYPE

The unit of the fan cooling capacity.

OBJECT-TYPE

This table contains the cooling requirement for all the manageable components of type entPhysicalClass 'module'.

OBJECT-TYPE

A cefcModuleCoolingEntry lists the cooling requirement for a manageable components of type entPhysicalClass 'module'. Entries are created by the agent at the system power-up or module insertion. Entries are deleted by the agent upon module removal.

OBJECT-TYPE

The cooling requirement of the module and its daughter cards. The default unit of the module cooling requirement is 'cfm', if cefcModuleCoolingUnit is not supported.

OBJECT-TYPE

The unit of the cooling requirement of the module and its daughter cards.

OBJECT-TYPE

This table contains a list of the possible cooling capacity modes and properties of the fans, whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of 'fan'.

OBJECT-TYPE

A cefcFanCoolingCapacityEntry lists the cooling capacity mode of a manageable components of type entPhysicalClass 'fan'. It also lists the corresponding cooling capacity provided and the power consumed by the fan on this mode. Entries are created by the agent if the corresponding entry is created in ENTITY-MIB entPhysicalTable. Entries are deleted by the agent if the corresponding entry is deleted in ENTITY-MIB entPhysicalTable.

OBJECT-TYPE

An arbitrary value that uniquely identifies a cooling capacity mode for a fan.

OBJECT-TYPE

A textual description of the cooling capacity mode of the fan.

OBJECT-TYPE

The cooling capacity that could be provided when the fan is operating in this mode. The default unit of the cooling capacity is 'cfm', if cefcFanCoolingCapCapacityUnit is not supported.

OBJECT-TYPE

The power consumption of the fan when operating in in this mode.

OBJECT-TYPE

The unit of the fan cooling capacity when operating in this mode.

OBJECT-IDENTITY

OBJECT-TYPE

This table contains the connector power ratings of FRUs. Only components with power connector rating management are listed in this table.

OBJECT-TYPE

A cefcConnectorRatingEntry lists the power connector rating information of a component in the system. An entry or entries are created by the agent when an physical entity with connector rating management is added to the ENTITY-MIB entPhysicalTable. An entry is deleted by the agent at the entity removal.

OBJECT-TYPE

The maximum power that the component's connector can withdraw.

OBJECT-TYPE

This table contains the total power consumption information for modules whose ENTITY-MIB entPhysicalTable entries have an entPhysicalClass of 'module'.

OBJECT-TYPE

A cefcModulePowerConsumptionEntry lists the total power consumption of a manageable components of type entPhysicalClass 'module'. Entries are created by the agent at the system power-up or module insertion. Entries are deleted by the agent upon module removal.

OBJECT-TYPE

The combined power consumption to operate the module and its submodule(s) and inline-power device(s).

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY