cc/td/doc/product/wanbu/mgx8850/20x
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

CISCO ENTITY FRU CONTROL MIB File

CISCO ENTITY FRU CONTROL MIB File

This chapter describes the individual MIB objects that comprise the PXM45-specific MIB files. The CISCO ENTITY Field Replaceable Unit (FRU) Control MIB resides in the ENTITY-MIB.my file. The CISCO ENTITY FRU CONTROL MIB is used to monitor and configure the operational FRU of the system listed in the ENTITY MIB (RFC 2037) entPhysicalTable.

The FRUs include assemblies such as power supplies, fans, processor modules, interface modules, and so forth.

Contents of this chapter include:

CISCO ENTITY FRU CONTROL MIB Textual Conventions

The names of the textual conventions are specified in the object syntax.

Table 4-1 lists the textual conventions MIB objects.


Note   Textual conventions do not have object identifiers.


Table 4-1: Textual Conventions MIB Objects
Name Syntax Description Default Value

PowerRedundancy
Type

Integer {notsupported (1), redundant (2), combined (3)}

Contains the valid values of the power supply redundancy modes. The following is the values:

  • notsupported(1)—Indicates only that the requested administrative state [redundant (2) or combined (3)] is not supported by the system. This is the operational state.

  • redundant(2)—Signifies a single power supply output that powers the entire system, although there is more than one supply in the system. For example, a system with one 1000-watt supply and one 1300-watt supply can be rated to power 1000-watts of FRUs.

  • combined(3)—Specifies the combined output of the power supplies that are available to operate the system. For example, two 1000-watt supplies a combined-mode supply of 2000 watts to the system.

Status: current

none

PowerAdminType

Integer {on(1), off(2)}

Sets the administratively desired FRU power state types. Valid values are the following:

  • on (1)

  • Turn FRU on and off (2)

  • Turn FRU off

Status: current

none

PowerOperType

Integer {offEnvOther(1), on(2), offAdmin(3), offDenied(4), offEnvPower(5), offEnvTemp(6), offEnvFan(7)}

Sets the operational FRU status types. The following are the values:

  • offEnvOther(1)—Specifies that FRU is powered off because of a problem not listed below.

  • on(2)—Specifies that FRU is powered on.

  • offAdmin(3)—Turns administratively off.

  • offDenied(4)—Specifies that FRU is powered off because the available system power is insufficient.

  • offEnvPower(5)—Turns the FRU ipower off because of a power problem. For example, the FRU power translation (DC-DC converter) or distribution failed.

  • offEnvTemp(6)—Turns the FRU power off because of a temperature problem.

  • offEnvFan(7)—Turns the FRU power off because of fan problems.

Status: current

none

FRUCurrentType

Integer
( -1000000000..1000000000 )

Shows a current measurement on the system power supply primary output in cefcPowerUnits. Range is from negative
1 million to positive one million amperes.

A negative value expresses the current used by the FRU. A positive value expresses the current supplied by the FRU.

Status: current

none

ModuleAdminType

Integer {enabled (1), disabled (2), reset (3), outOfServiceAdmin (4)}

Sets the administratively desired module states. The following are the values:

  • enabled (1)—Determines the module is operational.

  • disabled (2)—Determines the module is not operational.

  • reset (3)—Resets the module.

  • outOfServiceAdmin (4)—Turns the module power on but it is out of service. This is set by Command Line Interface (CLI).

Status: current

none

ModuleOperType

Integer {unknown(1), ok(2), disabled(3), okButDiagFailed(4), boot(5), selfTest(6), failed(7), missing(8), mismatchWithParent(9), mismatchConfig(10), diagFailed(11), dormant(12), outOfServiceAdmin(13), outOfServiceEnvTemp(14)}

Displays the operational module states. The following are the values:

  • unknown(1)—Specifies the module is not in one of the other recognized operational states.

  • ok(2)—States the module is operational.

  • disabled(3)—Disables the module administratively.

  • okButDiagFailed(4)—Specifies the module is operational but there is some diagnostic information available. This is a transitional state.

  • boot(5)—Brings up the image of the module. After boot, it starts its operational software and transitions to the appropriate state. This is a transitional state.

  • selfTest(6)—Performs a self test of the module. This is a transitional state.

  • failed(7)—Specifies the module has failed due to some condition not stated above. This is a failure state.

  • missing(8)—Specifies the module is provisioned, but it is missing. This is a failure state.

  • mismatchWithParent(9)—Indicates the module is not compatible with parent entity. Module is not provisioned; the wrong type of module is plugged in. This state is cleared by plugging in the appropriate module. This is a failure state.

none

ModuleOperType

(continued)

  • mismatchConfig(10)—Indicates the module is not compatible with the current configuration. The module was provisioned correctly earlier; however, the module was replaced by an incompatible module. This state is resolved by clearing the configuration or by replacing the appropriate module. This is a failure state.

  • diagFailed(11)—Specifies the module diagnostic test failed due to a hardware failure. This is a failure state.

  • dormant(12)—Specifies the module is waiting for an external or internal event to become operational.

  • outOfServiceAdmin(13)—Turns on the module administratively; however, it is out of service.

  • outOfServiceEnvTemp(14)—Turns on the module administratively; however, it is out of service due to an environmental temperature problem. An out-of-service module consumes less power and can consequently cool down.

Status: current

ModuleResetReasonType

Integer {unknown(1), powerUp(2), parityError(3), clearConfigReset(4), manualReset(5)}

Describes the reason for the last module reset operation. The following are the values:

  • unknown(1)—Source of the reset is not identified.

  • powerUp(2)—Indicates a system powerup operation.

  • parityError(3)—Indicates a parity error that occurred during the system bring up operation.

  • clearConfigReset(4)—Resets due to clear configuration operation.

  • manualReset(5)—Resets due to an administrative request.

Status: current

none

cefc Module Table

The object identifier for each MIB object is listed in Table 4-2.


Table 4-2: cefc Module Table Object Identifiers
Name Object Identifier

cefcModuleTable

::= { cefcModule 1 }

cefcModuleEntry

::= { cefcModuleTable 1 }

cefcModuleAdminStatus

::= { cefcModuleEntry 1 }

cefcModuleOperStatus

::= { cefcModuleEntry 2 }

cefcModuleResetReason

::= { cefcModuleEntry 3 }

cefcModuleStatusLastChangeTime

::= { cefcModuleEntry 4 }

The MIB objects are listed in Table 4-3.


Table 4-3: cefc Module Table MIB Objects
Name Syntax Description Default Value

cefcModuleTable

Sequence of cefcModuleEntry

Lists the operation and administrative status information for ENTITY MIB entPhysicalTable entries for the FRUs of type PhysicalClass module(9).

Max-Access: not-accessible

Status: current

none

cefcModuleEntry

cefcModuleEntry

Lists the operation and administrative status information for ENTITY MIB entPhysicalTable entries for FRUs 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.

Max-Access: not-accessible

Status: current

The index contains entPhysicalIndex.

none

cefcModuleAdminStatus

ModuleAdminType

Provides administrative control of the module.

Max-Access: read-write

Status: current

none

cefcModuleOperStatus

ModuleOperType

Shows the operational state of the module.

Max-Access: read-only

Status: current

none

cefcModuleResetReason

ModuleResetReasonType

Identifies the reason for the last reset performed on the module.

Max-Access: read-only

Status: current

none

cefcModuleStatusLast
ChangeTime

TimeStamp

Displays the value of sysUpTime when the cefcModuleOperStatus is changed.

Max-Access: read-only

Status: current

none

CISCO ENTITY FRU CONTROL MIB Notification

According to RFC 2578, a notification is used to describe unsolicited transmissions of management information. NOTIFICATION-TYPE conveys the syntax and semantics of a notication.

The object identifier for the MIB object is listed in Table 4-4.


Table 4-4: CISCO ENTITY FRU CONTROL MIB Notification Object Identifier
Name Object Identifier

cefcModuleStatusChange

::= { cefcMIBNotifications 1 }

One MIB object is listed in Table 4-5.


Table 4-5: CISCO ENTITY FRU CONTROL MIB Notification MIB Object
Name Objects Description Default Value

cefcModuleStatusChange

cefcModuleOperStatus, cefcModuleStatusLast
ChangeTime

Generates the value of cefcModuleOperStatus changes. It is utilized by a NMS to update the status of the module it is managing.

Status: current

none

CISCO ENTITY FRU CONTROL MIB Conformance Information

The information on conformance is specific to SNMPv2 as listed in Table 4-6 and Table 4-7.


Table 4-6: CISCO ENTITY FRU CONTROL MIB Units of Conformance
Name Object Identifier

cefcMIBModuleGroup

::= { cefcMIBGroups 3 }


Table 4-7: CISCO ENTITY FRU CONTROL MIB Units of Conformance Object
Name Objects Description Default Value

cefcMIBModuleGroup

cefcModuleAdminStatus, cefcModuleOperStatus, cefcModuleResetReason, cefcModuleStatusLast
ChangeTime

Provides a collection of objects that is used to obtain the operational state and redundancy state of the modules.

Status: current

none


hometocprevnextglossaryfeedbacksearchhelp
Posted: Fri Sep 15 11:53:15 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.