CISCO-ENTITY-FRU-CONTROL-MIB

The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other...

Typedef Base type Abstract
FRUCoolingUnit enumeration The unit for the cooling capacity and requirement. cfm(1) Cubic feet per minute watts(2) Watts
FRUCurrentType int32 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.
FRUTimeSeconds uint32 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.
ModuleAdminType enumeration 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.
ModuleOperType enumeration 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.
ModuleResetReasonType enumeration 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.
PowerAdminType enumeration 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.
PowerOperType enumeration 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.
PowerRedundancyType enumeration 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.

© 2023 YumaWorks, Inc. All rights reserved.