CHS-MIB: View SNMP OID List / Download MIB

A table that contains information about the slots in the chassis. For those slots that do not contain a physical module, the table will contain a conceptual row with the type of physical module set to 'uchasSlotEmpty'.

A list of information for each slot in the chassis. Conceptual rows may not be created or deleted with SNMP operations, but rather, the Proxy agent running in the Network Management Card will automatically create and delete rows as cards are inserted and removed.

The slot number for which this entry contains management information. NAC slots are numbered from 1 to 16. The Network Management Card (NMC) goes in slot 17. For simplicity's sake, the corresponding NIC slot numbers will be 21 through 37. Rows will not exist in this table for slots 18 through 20.

The type of physical module contained in this slot of the chassis. A value of uchasSlotEmpty indicates an empty slot. A value of uchasSlotUnknown indicates that the type of module is unknown.

The value of MIB-II's sysUpTime (in the agent supporting this chassis MIB) at which a module was last inserted or removed from this slot. If no module has been inserted or removed from this slot since the last time the network management card was re-initialized, then this object has a zero value.

A textual description of the module plugged into the slot.

A textual description of the version/revision level for this module's hardware.

The serial number of the module present in the slot. If the slot is empty, this value will be a zero length string.

The product code of the module present in the slot. For certain entries in the slot table the NMC will not be able to read product codes. In such cases the product code string will be NULL.

This object can be read to determine what options have been enabled in the NACs. It uses individual bits to represent the enable status of the features which are NAC specific.

This object sends the feature key to the appropriate NAC for enabling added cost features. When read, this object returns a null string.

This is a proprietary encoding of a module's view of the chassis NAC configuration as it is stored in the module. For modules not supporting chassis configuration storage, the values will be all 0.

This represents the DIP switch settings on the NAC. It is a bitmapped integer.

This represents the amount of DRAM memory installed on the NAC in Kbytes.

This represents the amount of flash ROM memory installed on the NAC in Kbytes.

A table that contains information about the 'logical' networking devices (entities) in this chassis.

Information concerning an entity in the chassis. Conceptual rows may not be created or deleted with SNMP operations, but rather, will be automatically created and deleted by the proxy agent running on the Network Management Card.

A unique index for the entity for which this entry contains information. For simplicity's sake, entity index values will be assigned according to the formula E=1000*S+I, where E is the entity index, S is the slot index, and I is the index of the entity on the specific card. For example, the third modem on a quad modem card that is in slot 5 has an entity index of 5003.

The specific type of entity. The value of this object is analogous to MIB-II's sysObjectID. In particular, it has the same value as would be returned if the MIB view identified by uchasIpAddress and uchasCommunity, were queried for sysObjectID.

A textual description of the entity. The value of this object is analogous to MIB-II's sysDescr. In particular, it has the same value as would be returned if the MIB view identified by uchasIpAddress and uchasCommunity were queried for sysDescr.

A textual description of the version/revision level for this entity's software.

Provides operational status of the entity for which this row corresponds. Enumeration: 'outOfService': 2, 'loading': 6, 'testing': 3, 'operational': 4, 'failed': 5, 'other': 1.

The value of MIB-II's sysUpTime (in the NMC's proxy agent) at which this entity was last (re-)initialized.

An authoritative identification of the type of chassis. This object provides an easy and unambiguaous means for determining what kind of box is being managed.

A textual description of the specific chassis being managed.

A four digit name given to the chassis. The name will be displayed on the alpha-numeric display on the front panel of the Network Management Card in the given chassis.

The number of physical changes that have occurred in the chassis since the agent was warm/cold started. This includes additions and removal of physical modules.

This object is a proprietarily encoded octet string that is used by USR's management console to retrieve the front panel LED states (attributes) from all of the devices installed in the chassis by getting a single object.

This object is a proprietary encoded octet string used to get the color of every LED from all the devices in the chassis.

This object is a proprietary encoded octet string used to get the status of every NIC in the chassis.

A list of power supply entries, one for each power supply in the chassis. This table is a dense table, so rows appear for all possible power supplies that could be present in the given chassis.

There is one entry in the power supply table for each possible power supply in the chassis.

An index value that uniquely identifies a power supply.

A textual description of the power supply.

Actual status of the power supply represented by this entry in the power supply table. Enumeration: 'unknown': 1, 'bad': 2, 'good': 3, 'empty': 4.

The number of times that uchasPowerSupplyOperStatus has gone to bad(4).

A list of power supply output entries, one for each output of each power supply in the chassis.

There is one row in this table for each power supply output for each power supply in the chassis.

An index which specifies the power supply to which this output relates. The value of this index corresponds directly to values of the index for the power supply table.

An index that, together with uchasPowerSupplyOutPSIndex, uniquely defines an output for the specified power supply.

Actual status of the supply output. One of unknown(1), warning(2), or good(3). Enumeration: 'unknown': 1, 'good': 3, 'warning': 2.

In hundredths of a volt, the voltage the output is supposed to supply, such as -5V, which would be represented by the value -500, or +12V, which would correspond to a value of +1200.

In hundredths of a volt, the voltage actually offered by the output. If uchasPowerSupplyOutStatus is good(4), the value 0 means offered voltage is not available.

The number of times uchasPowerSupplyOutputStatus has gone to warning(3).

A list of environmental entries, one for each environmental sensor in the chassis.

Values for an environmental sensor in the chassis.

A index that uniquely identifies an environmental sensor.

The identification of the type of environmental sensor to which this entry applies.

Actual status indicated by the sensor. Enumeration: 'unknown': 1, 'bad': 2, 'warning': 3, 'good': 4.

The number of times uchasEnvironStatus has gone to warning(3).

The number of times uchasEnvironStatus has gone to bad(2).

The Chassis Command table contains an entry for each of the NIC and NAC slots in the chassis. It provides a means through which to take specific actions on one or more devices in the chassis at a card level. Device specific commands are not included here, but rather in the specific MIB used to manage the device.

There is one entry in this table for each row in uchasSlotTable.

This index uniquely identifies the slot to which the command being written is to take place. Values of uchasCmdSlotIndex correspond to values used to index uchasSlotTable.

This object is a generic read-write variable that a Management Station (MS) can use to guarantee that the results from a given command are the results of a command issued by that specific MS. Each MS must SET a unique value to this object when doing commands and GET the value of this object together with uchasCmdReqId and uchasCmdResult to detect interference from other MSs.

Ths object contains the value of the request-id field in the SNMP PDU which invoked the current or most recent command on the device in the specified slot of the chassis. If the request-id is unknown or undefined, this value contains the value zero.

A control variable used to start and stop operator-initiated commands. A command is initiated by setting this object to a value other than noCommand(1). When the value noCommand(1) is written to this object, no action is taken, unless a command is in progress, in which case the command is aborted. Enumeration: 'removeFromService': 2, 'hardwareReset': 4, 'softwareDownload': 5, 'noCommand': 1, 'restoreToService': 3.

In some cases, the devices in the chassis may be in a state such that certain commands could adversely affect connections or other device specific operations. In such cases, a command with uchasCmdForce set to noForce will result in a warning. If the operator elects to ignore such warnings, uchasCmdForce can be set to force in the command request and the command will be carried out regardless of its potentially hazzardous effects. Enumeration: 'noForce': 2, 'force': 1.

This object contains parameters that are specific to the particular command being issued. In some cases, there will be no additional parameters required.

This object contains the result of the most recently requested test, or the value none(1) if not commands have been requested since the last reset. Note that this facility provides no provision for saving the results of one command when starting another, as could be required if used by multiple managers concurrently. Enumeration: 'none': 1, 'success': 2, 'failed': 7, 'unAbleToRun': 5, 'aborted': 6, 'inProgress': 3, 'notSupported': 4.

The value of this object upon command completion indicates a further description of what went wrong if the command was unsuccessful. This object is also used as an indication of the in progress status of the software download command. Enumeration: 'pendingSoftwareDownload': 73, 'crcTestingSdlFile': 78, 'invalidRomId': 75, 'nonManagedDevice': 21, 'userInterfaceActive': 58, 'flashEraseTimeout': 87, 'invalidFileHeader': 88, 'eraseSequenceError': 64, 'slotEmpty': 8, 'badFlashRomID': 61, 'eraseExecutionError': 65, 'badProgramVoltage': 68, 'deviceDisabled': 22, 'unrecognizedCommand': 6, 'ramCrcBad': 74, 'noError': 1, 'unable': 2, 'noResponse': 12, 'unsupportedCommand': 20, 'downloadingSdlFile': 77, 'programmingDataError': 69, 'executeLoadedProgram': 80, 'sdlTrigger': 76, 'flashEraseError': 63, 'connected': 14, 'badAddressInData': 67, 'tftpTimeout': 86, 'downloadingNacFile': 82, 'cardIdUnknown': 85, 'badFlashVoltage': 62, 'erasingFlash': 81, 'queryWorkSpaceSize': 79, 'cardIdMismatch': 84, 'resetingNac': 83, 'invalidCodeError': 71, 'programCodeError': 70, 'romCrcBad': 72, 'receiveBufferOverflow': 66.

Enables the generation of a trap when a card is inserted into the chassis. This parameter is effective across all slots in the chassis. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when a card is removed from the chassis. This parameter is effective across all slots in the chassis. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when a power supply enters a warning state, such as one or more output voltages being out of range. This parameter is effective across all PSUs in the chassis. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when a power supply fails and has been automatically shut down due to overvoltage, overcurrent, etc. This parameter is effective across all PSUs in the chassis. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when the temperature in the chassis, as detected by the NMC, becomes excessive. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when the fan in the chassis is not rotating with sufficient speed to cool the power supplies. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when a logical networking entity in the chassis undergoes a watchdog timeout event, indicating software failure. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

Enables the generation of a trap when the SNMP proxy agent in the NMC is unable to communicate properly with a logical networking entity in the chassis. Enumeration: 'enableTrap': 1, 'enableAll': 4, 'enableLog': 3, 'disableAll': 2.

This script is triggered when the NMC detects that voltage levels, for at least one power supply on the mid plane, are outside the normal operating range.

This script is triggered when the NMC detects an over-voltage or over-current condition present in the PSU.

This script is triggered when the fan speed becomes dangerously slow as to risk damage to inadequate cooling of the chassis.

This script is triggered when the chassis temperature is outside the specified normal operating range.

This script is triggered when the first general purpose timer expires.

This script is triggered when the second general purpose timer expires.

This script is triggered when the third general purpose timer expires.

This script is triggered when the fourth general purpose timer expires.

A table that contains auto response scripts, in the chassis, that act on a particular slot.

A list of auto response scripts, in the chassis, that act on a slot.

The slot number for which this entry contains an auto response script. NAC slots are numbered from 1 to 16. The Network Management Card (NMC) goes into slot 17. To keep things simple, the corresponding NIC slot numbers are from 21 to 37. Rows for slots 18 to 20 do not exist.

This script is triggered when a module is inserted in the chassis.

This script is triggered when the following occur: chassis power transitions from off to on; a module is inserted in the chassis; software download has just been completed to a module; a module is restored to service; or a module is reset (hardware).

This script is triggered when a module is physically removed from the chassis.

This script is triggered when the following occur: software download to a module has just been started; a module is removed from service; or a module has failed (i.e. all entities on that module have failed).

This script is triggered when one or more module entities experience a watchdog time-out.

A table that contains general purpose global timer parameters. These timers act on an entire chassis.

A list of parameters for general purpose global timers.

The number of general purpose global timers.

Enable or disable the specified global timer. Enumeration: 'enable': 2, 'disable': 1.

This object determines the date on which the timer becomes active. This date is compared against the system date, time and time zone defined in management entity. Default=01/01/95

This object determines the time on which the timer becomes active. This time is compared against the system date, time and time zone defined in management entity. Default=00:00:00

This object specifies the date on which this timer becomes passive. This date is compared against the system date, time and time zone defined in management entity. The timer will not be active if the timer stop date and time is less than system date and time. Default = 01/01/95

This object specifies the time on which this timer becomes passive. This time is compared against the system date, time and time zone defined in management entity. The timer will not be active if the timer stop date and time is less than system date and time. Default = 00:00:00

The interval in seconds between each timer firing. The firings will happen at each interval after the timer starts until the date/time specified if the following 2 conditions are met. First, TimerInterval must be less than or equal to the timer active period. Second, The start date/time is less than the stop date/time. The timer will fire only once at stop date/time if a zero value has been assigned to this object. Default = 0. Max 259000 sec = 30 days.

This object indicates the current state of the global timer. Enumeration: 'passive': 2, 'active': 3, 'init': 1.

This object indicates the number of times that a global timer has triggered since the last system boot time.