ESM-snmp: View SNMP OID List / Download MIB

Table of managers to which traps must be sent. Up to 10 entries in table

IP address of entity requesting event notification

Community name the receiving entity will expect. When reading the instance of this object the value has no meaning.

Version number supported by destination node

Type of event that should be reported to this address, bit 0 - authentication trap bit 1 - other SNMP traps bit 2 - Error Traps bit 3 - Diagnostic Traps bit 4 - Debug Traps bit 5 - Enterprise Traps other than fmDiagGenericTrap

Determines status of this entry Enumeration: 'active': 1, 'inactive': 2.

If the entry is fixed, it can not be deleted because of aging Enumeration: 'fixed': 0, 'removable': 1.

Aging time of the entry (in sec)

Learn the addresses of the managers automatically. Enumeration: 'enable': 1, 'disable': 0.

Time in sec. until we erase a trap entry

Table of managers to which traps must be sent. Up to 10 entries in table

IP address of entity requesting event notification

Community name the receiving entity will expect. When reading the instance of this object the value has no meaning.

Version number supported by destination node

Type of event that should be reported to this address, bit 0 - authentication trap bit 1 - other SNMP traps bit 2 - Error Traps bit 3 - Diagnostic Traps bit 4 - Debug Traps bit 5 - all Enterprise Traps other than fmDiagGenericTrap

Determines status of this entry Enumeration: 'active': 1, 'inactive': 2.

Learn the addresses of the managers automatically. Enumeration: 'enable': 1, 'disable': 0.

Time in sec. until we erase a trap entry

Resetting the CARD. When reading the instance of this object the value has no meaning. cold reset is performed with selftest , while warm start is performed without selftest Enumeration: 'meaning-less-value': 127, 'cold-reset': 0, 'power-up': 2, 'warm-reset': 1.

Type of self test to be executed upon cold-reset Enumeration: 'none': 0, 'full': 2, 'partial': 1, 'extended': 3.

Version of the station. The version includes station type, hardware version and software version. The string can include CR and LF

IP address of the agent

IP Network Mask

Default Gateway Address

IP address to which a TFTP for boot is sent.

Path and file name that is sent as a TFTP request

Method for booting Enumeration: 'internal-memory': 1, 'bootp': 2.

Downloading the ESM. When reading the instance of this object the value has no meaning. Enumeration: 'download': 1, 'meaning-less-value': 127.

SLIP IP address. This is object is available only when slip interface exist

SLIP IP Network Mask This is object is available only when slip interface exist

SLIP Baud rate This is object is available only when slip interface exist Enumeration: 'baud1200': 0, 'baud19200': 4, 'baud2400': 1, 'baud4800': 2, 'baud9600': 3, 'baud38400': 5.

SLIP Parity This is object is available only when slip interface exist Enumeration: 'even': 2, 'none': 0, 'odd': 1.

SLIP Stop Bits This is object is available only when slip interface exist Enumeration: 'two': 1, 'one': 0.

IP address of the agent

IP Network Mask

Default Gateway Address

IP address to which a TFTP for boot is sent.

Path and file name that is sent as a TFTP request

Method for booting Enumeration: 'internal-memory': 1, 'bootp': 2.

Community string for reading When reading the instance of this object the value has no meaning.

Community string for writing When reading the instance of this object the value has no meaning.

SLIP IP address This is object is available only when slip interface exist

SLIP IP Network Mask This is object is available only when slip interface exist

SLIP Baud rate This is object is available only when slip interface exist Enumeration: 'baud1200': 0, 'baud19200': 4, 'baud2400': 1, 'baud4800': 2, 'baud9600': 3, 'baud38400': 5.

SLIP Parity This is object is available only when slip interface exist Enumeration: 'even': 2, 'none': 0, 'odd': 1.

SLIP Stop Bits This is object is available only when slip interface exist Enumeration: 'two': 1, 'one': 0.

Upon writing, performs a master clear command on all the slots. When reading the instance of this object the value has no meaning.

Slot Number

ID of the card in the slot. Special , not-exist, ID identifies a GigaHUB slot that doesn't exist: slot 5, if a HALF MultiHUB installed, or slot 9, if a FULL MultiHUB installed. Enumeration: 'cc044-ID': 65559, 'cc202': 65545, 'lc342': 285278465, 'lc312-129': 131077, 'cc041-ID': 65557, 'lc362p-em364': 302055687, 'cc042-ID': 65558, 'cc432': 65588, 'cc301': 65560, 'lc362p-em364p': 302055690, 'cc303': 65562, 'xm516': 335740929, 'cc308': 65563, 'cc46A': 10, 'lc312': 65578, 'lc303-129': 131075, 'lc362-em364p': 302055685, 'cc260': 65576, 'lc342-nm349': 285409537, 'cc201': 65544, 'cc321': 65552, 'lc362': 302055684, 'cc20': 4, 'unconfig': 0, 'cc832': 65537, 'lc343-nm349': 285409539, 'lc344-nm349': 285409540, 'empty': 1, 'lc362-em365': 302055683, 'lc362-em364': 302055682, 'general-smartcard': 131072, 'lc343': 285278467, 'cc010-ID': 65541, 'cc42': 8, 'cc41': 7, 'cc24X': 65594, 'cc44': 9, 'lc348': 285278466, 'cc421': 65591, 'cc420': 65589, 'cc233': 65568, 'lc362p-em365': 302055688, 'cc427': 65580, 'lc322': 65540, 'lc344': 285278468, 'lc308-129': 131073, 'lc308': 65567, 'sw11X': 65584, 'cc401': 65592, 'lc366': 302055681, 'cc046B': 65553, 'lc303': 65566, 'cc012-ID': 65542, 'cc212': 65551, 'cc211': 65550, 'lc362p': 302055689, 'lc348-nm349': 285409538, 'cc214': 65548, 'cc32': 6, 'cc31': 5, 'cc422': 65590, 'cc020-ID': 65543, 'lc366p': 302055686, 'cc10': 2, 'cc12': 3, 'not-exist': 11.

Ascii string. Description of the card

User general info for the slot. Can be the use of that slot, its location etc...

Status bits of the card in the slot, organized by card channel. Each channel's status occupies 2 bytes. For more information about the meaning of the status, read the specific user manual of each card.

Previous status bits of the card in the slot, organized by card channel. Each channel's status occupies 2 bytes. For more information about the meaning of the status, read the specific user manual of each card. This object id is used mainly for traps (see Card Trap).

Argument: 1 - 4. Perform a RLB set operation on the channel passed as argument. When reading the instance of this object the value has no meaning.

Argument: 1 - 4. Perform a RLB clear operation on the channel passed as argument. When reading the instance of this object the value has no meaning.

Perform an expanded command on the slot. For expanded codes, see specific card user manual. When reading the instance of this object the value has no meaning. Extended command codes for NDS cards ------------------------------------ 1. CC892.303 (Ethernet) Code (Dec/Hex) Command ----------------------------------- 02/02 Detach Port 13 03/03 Attach Port 13 04/04 Detach Port 01 05/05 Attach Port 01 06/06 Detach Port 02 07/07 Attach Port 02 08/08 Detach Port 03 09/09 Attach Port 03 10/0A Detach Port 04 11/0B Attach Port 04 12/0C Detach Port 05 13/0D Attach Port 05 14/0E Detach Port 06 15/0F Attach Port 06 16/10 Detach Port 07 17/11 Attach Port 07 18/12 Detach Port 08 19/13 Attach Port 08 20/14 Detach Port 09 21/15 Attach Port 09 22/16 Detach Port 10 23/17 Attach Port 10 24/18 Detach Port 11 25/19 Attach Port 11 26/1A Detach Port 12 27/1B Attach Port 12 28/1C Detach All Ports 29/1D Attach All Ports 30/1E Reset Card 31/1F Link Select ====================================================== 2. CC892.308 (Ethernet) Code (Dec/Hex) Command ----------------------------------- 02/02 Detach Port 01 03/03 Attach Port 01 04/04 Detach Port 02 05/05 Attach Port 02 06/06 Detach Port 03 07/07 Attach Port 03 08/08 Detach Port 04 09/09 Attach Port 04 10/0A Detach Port 05 11/0B Attach Port 05 12/0C Detach Port 06 13/0D Attach Port 06 14/0E Detach Port 07 15/0F Attach Port 07 16/10 Detach Port 08 17/11 Attach Port 08 ... 28/1C Detach All Ports 29/1D Attach All Ports 30/1E Reset Card 31/1F Link Select ================================================ 3. CC892.322 (Token-ring) Module 323 ---------- Code (Dec/Hex) Command ----------------------------------- 02/02 Detach Port 01 03/03 Attach Port 01 04/04 Detach Port 02 05/05 Attach Port 02 06/06 Detach Port 03 07/07 Attach Port 03 08/08 Detach Port 04 09/09 Attach Port 04 10/0A Detach Port 05 11/0B Attach Port 05 12/0C Detach Port 06 13/0D Attach Port 06 18/12 Detach Port 07 19/13 Attach Port 07 20/14 Detach Port 08 21/15 Attach Port 08 22/16 Detach Port 19 23/17 Attach Port 19 24/18 Detach Port 10 25/19 Attach Port 10 26/1A Detach Port 11 27/1B Attach Port 11 28/1C Detach Port 12 29/1D Attach Port 12 30/1E Reset Card 34/22 Detach Port 13 35/23 Attach Port 13 36/24 Detach Port 14 37/25 Attach Port 14 38/26 Detach Port 15 39/27 Attach Port 15 40/28 Detach Port 16 41/29 Attach Port 16 42/2A Detach Port 17 43/2B Attach Port 17 44/2C Detach Port 18 45/2D Attach Port 18 50/32 Detach Port 19 51/33 Attach Port 19 52/34 Detach Port 20 53/35 Attach Port 20 54/36 Detach Port 21 55/37 Attach Port 21 56/38 Detach Port 22 57/39 Attach Port 22 58/3A Detach Port 23 59/3B Attach Port 23 60/3C Detach Port 24 61/3D Attach Port 24 77/4D Detach All Ports 79/4F Attach All Ports ======================================================== Module 325 ---------- 30/1E Reset Card 80/50 Detach Local Port 1 (channel 1) 81/51 Attach Local Port 1 (channel 1) 82/52 Detach Local Port 2 (channel 1) 83/53 Attach Local Port 2 (channel 1) 88/58 Detach Local Port 1 (channel 3) 89/59 Attach Local Port 1 (channel 3) 90/5A Detach Local Port 2 (channel 3) 91/5B Attach Local Port 2 (channel 3) 77/4D Detach All Ports 79/4F Attach All Ports 4. CC892.427 (Voice) Code (Dec/Hex) Command ----------------------------------- 04/04 Loopback OFF on Port 1 05/05 Loopback ON on Port 1 06/06 Loopback OFF on Port 2 07/07 Loopback ON on Port 2 08/08 Loopback OFF on Port 3 09/09 Loopback ON on Port 3 10/0A Loopback OFF on Port 4 11/0B Loopback ON on Port 4 12/0C Loopback OFF on Port 5 13/0D Loopback ON on Port 5 14/0E Loopback OFF on Port 6 15/0F Loopback ON on Port 6 16/10 Loopback OFF on Port 7 17/11 Loopback ON on Port 7 18/12 Loopback OFF on Port 8 19/13 Loopback ON on Port 8 20/14 Loopback OFF on Port 9 21/15 Loopback ON on Port 9 22/16 Loopback OFF on Port 10 23/17 Loopback ON on Port 10 24/18 Loopback OFF on Port 11 25/19 Loopback ON on Port 11 26/1A Loopback OFF on Port 12 27/1B Loopback ON on Port 12 28/1C Loopback OFF on Port 13 29/1D Loopback ON on Port 13 30/1E Loopback OFF on Port 14 31/1F Loopback ON on Port 14 32/20 Loopback OFF on Port 15 33/21 Loopback ON on Port 15 34/22 Loopback OFF on Port 16 35/23 Loopback ON on Port 16 37/25 Loopback ALL on Ports 1-8 39/27 Loopback ALL on Ports 9-16 40/28 Alternate Mode on Channel Module #1 41/29 Normal Mode on Channel Module #1 42/2A Alternate Mode on Channel Module #2 43/2B Normal Mode on Channel Module #2 45/2D Configuration Load Module #1 47/2F Configuration Load Module #2 ======================================================

When the value is 1, no more traps from that slot are sent, until next reset. (temporary mask) Enumeration: 'mask': 1, 'no-mask': 0.

When the value is 1, no more traps for that slot will be sent, starting after next reset (permanent mask) Enumeration: 'mask': 1, 'no-mask': 0.

IP address of a channel card.

This run-time object determines through which interface the SNMP management will be permitted. The default is through the managment bus, via the ESM. This object value is reinitialized to its permanent value after system reset. Setting the object is permitted only for slots containing active SNMP managers. Such cards will change management access immediately according to the specified value. Set values must be either Management-Bus or LAN and the target slot must contain an active SNMP agent. Enumeration: 'lan': 2, 'no-SNMP-management': 1, 'management-bus': 3.

This permanent object determines through which interface the SNMP management will be permitted. The default is through the managment bus, via the ESM. This object has no effect on slots not containing SNMP agents. The run-time object will receive this value after system reset only if the value is permitted. Setting the object is permitted only for slots containing active SNMP managers. Such cards will change management access only the next time the card is initialized. Set values must be either Management-Bus or LAN and the target slot must contain an active SNMP agent. Enumeration: 'lan': 2, 'no-SNMP-management': 1, 'management-bus': 3.

This object determines the Entity index which the card is a memeber in.

This object determines the Entity Community which the card is a memeber in.

This object determines if the card is an SNMP-manageable Entity Manager. Enumeration: 'sNMP-entity-manager': 2, 'no-entity-manager': 1.

Logic unit ID Enumeration: 'none': 1, 'lu104': 6, 'lu107': 9, 'lu106': 8, 'lu105': 7, 'unconfig': 0, 'lu103': 5, 'lu102': 4, 'lu101': 3, 'lu100': 2, 'lu108': 10.

Ascii string. Description of the logic unit

One byte of LU status

Setup LU link. Enumeration: 'sec-link': 1, 'main-link': 0.

Upon writing, performs LLB command. When reading the instance of this object the value has no meaning.

Upon writing, clear LLB command. When reading the instance of this object the value has no meaning.

When the value is 1, no more traps from the LU are sent, until next reset. (temporary mask) Enumeration: 'mask': 1, 'no-mask': 0.

When the value is 1, no more traps for the LU will be sent, starting after next reset (permanent mask) Enumeration: 'mask': 1, 'no-mask': 0.

Version of the station. The version includes station type, hardware version and software version. The string can include CR and LF

Used for generic traps. The first word is the trap code. The rest of the string is the extra information. Contains CR and LF char.

Table of fault reports from the agent

The fault index in the fault table

Get the faults detected by the agent

This object is for factory use only. Users must not write into this variable or improper operation can occur. Enumeration: 'normal-mode': 0, 'debug-mode': 1.

Issued when the Logic unit goes out of synchronization

Issues as soon as the logic unit returns to synchronization

Issues as soon as the logic unit pass to main link

Issues as soon as the logic unit pass to second link

When primary link of the logic unit fails this trap is issued

When primary link of the logic unit fails this trap is issued

When second link of the logic unit fails this trap is issued

When second link of the logic unit fails this trap is issued

When the logic unit enters LLB mode

When the logic unit exits LLB mode

Issues when a change in the LU configuration is done

Generated when a significant status has changed in a slot. By xoring the 2 statuses, the NMS can identify the cause of the trap.

Issued when the system detects changes in its slots configuration

Generic Trap information

This trap message is generated as soon as one of the power supply has changed its operational status.

This trap message is generated when there is a change in enviromental sensor status.

This trap is generated when an unauthorized host attempts to perform an SNMP SET operation.

This trap message is generated when there is a change in module operational status

This trap is generated when a module is removed from a modular slot.

This trap is generated when a module is inserted in a modular slot.

This trap is generated when physical module resource is changed it's segment/ring attachment.

This trap is generated when there is a global change in physical module resources configuration.

This trap message is generated as soon as one of the EBM cards has changed its operational status.

This trap is generated when IP Address is changed in a slot.

This table maps resources to backplane segments/ring numbers

This table maps resources to backplane segments/ring numbers

A unique integer representing the location type index

A unique integer representing the location type instance

A unique integer representing the resource instance at this location

The type of resource.

A unique integer representing the resource capability for attachment to the serial busses. Enumeration: 'eb2-four': 23, 'tr-4M': 33, 'tr-16M': 34, 'eb2-three': 22, 'eb2-one': 20, 'fddi-100M': 49, 'esb': 17, 'eb2': 19, 'eb2-two': 21, 'no-bus': 1.

A unique integer representing the ring or segment number in which the resource is attached to.

A list of EBM cards entries, one for each EBM card in the chassis.

Values for a EBM card.

An index value that uniquely identifies a EBM card

A textual description of the EBM card.

Actual status of the EBM card: - unknown(1) - don't have the information - empty(2) - no EBM card installed in slot - bad(3) - unable to work due to failure - good(4) - the card is good - active(5) - the card is good and active Enumeration: 'active': 5, 'unknown': 1, 'bad': 3, 'good': 4, 'empty': 2.

An authoritative identification of the type of hub-based or standalone chassis. By convention this value is allocated within the SMI enterprises subtree(1.3.6.1.4.1), and provides an easy and unambiguous means for determining `what kind of box' is being managed. If this information is not present or unknown, its value should be set to the value: chasTypeUnknown.

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

The serial number of the chassis. If no serial number is available then this object should be the zero length string.

Which type of MultiHUB is installed in the chassis. Enumeration: 'unknown': 1, 'none': 2, 'full': 4, 'half': 3.

This table summarises the different classes of and types of modular physical locations in the chassis. This includes but is not limited to slot within a chassis, power supply bay.

An entry in the phyLocationTable

This uniquely identifies the physical location type within the chassis.

This defines the number of physical locations of this type exist within the chassis.

Uniquely identifies the 'type' of the physical location within the chassis.

Each type of physical location within the chassis is given a textual name.

This table defines the physical modules within a chassis. This is done by defining the type physical modules and the physical location where it resides. This table also provides a mapping between physical modules and their location within the chassis.

An entry in this table that describes a physical module that resides at a given physcial location within the chassis.

An instance of a module is identified by the physical location in which it resides. The physical location is identified by location type index and location index (instance of that location type). This object defines an instance of the chasPhyLocationType.

An instance of a module is identified by the physical location which it resides. The physical location is identified by location type index and location index (instance of that location type). This object defines the instance of a particular location type. It must be within the bounds defined by chasPhyLocationCount.

An authoritative identification of the type of physcial module in this physical location. A value of chasModuleUnknown indicates that the type of physical module is unknown.

A textual description of the version/revision level for this module's software. If not realized this value should be set to the zero-length string.

A textual description of the version/revision level for this module's firmware. If not realized this value should be set to the zero-length string.

The serial number of the physical module present in this physical location. If the physical location table is implemented as dense and the slot is empty this value will be the zero length string. If no serial number is available for a physical module this value should set to a zero length string.

A textual description of the physical module plugged that resides in this physical location. If not available this value should be set to a zero length string.

The value of MIB-II's sysUpTime (in the agent supporting this chassis MIB) at which a module was last inserted or initialized. If the module has not changed since the last network managment system reinitialized then this object has a zero value.

Provides desired state of the given physical module. Notice that not all values may be supported by the specified physical module. In this case and SNMP error will be returned when the set is attempted. A physical module maybe activated by writing a value of enable(2). A physical module may be de-activated by writing a value of disable(3). In a disabled state a physical module is present in the chassis but is benign. Writing a value of sw-reset(4) initiates a software reset sequence. Writing a value of hw-reset(7) initiates a hardware reset sequence. A value of programLoad(5) initiates a software load sequence. Writing a value of test(6) should start a self test sequence within the physical module. Enumeration: 'enable': 2, 'unknown': 1, 'hw-reset': 7, 'test': 6, 'disable': 3, 'sw-reset': 4, 'programLoad': 5.

Provides operational status of the module. The following are possible definitions of the values. The exact definition of the values is implementation specific. A value of other(1) implies some undetermined state, possibly as a result of setting phyAdminStatus to a value of disable(3). A value of invalid(2) could have the possible meaning that the module exists but the chassis manager has no direct control over the module. A value of testing(3) may be a diagnostic state. A value of operational(4) implies that the entity is running with no errors or warnings. State resetInProgress(5) implies equivalent of setting phyAdminStatus to reset(4). The states of warning(6), nonFatalError(7), fatalError(8) reflect conditions detected during operation. The entity may or may not be still functional. For example if a modules value of phyAdminStatus is disable(3) and is set to enable(2) then phyOperStatus may enter a state of testing(3) then change to a value of operational(4). Enumeration: 'nonFatalError': 7, 'resetInProgress': 5, 'invalid': 2, 'operational': 4, 'other': 1, 'fatalError': 8, 'test': 3, 'programLoad': 9, 'warning': 6.

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.

A unique index for the entity for which this entry contains information.

The specific type of entity. The value of this object is analagous to MIB-II's sysObjectId. In particular, it has the same value as would be returned if the SNMP Party (identified by chasEntityParty) and/or the community (identified by chasIpAddress and chasCommunity), were queried for sysObjectId.

A textual description of the entity. The value of this object is analagous to MIB-II's sysDescr. In particular, it has the same value as would be returned if the SNMP Party (identified by chasEntityParty) and/or the community (identified by chasIpAddress and chasCommunity), were queried for sysDescr.

Provides the administratively desired state of the given entity. An entity is activated by writing a value of enable(2). An entity may be de-activated by writing a value of disable(3). In a disabled state, a entity does exist within the given chassis, but is benign. A disabled entity is available for subsequent activation. Writing a value of reset(4) specifies an entity should initiate a reset sequence. Writing a value of programload(5) specifies an entity should initiate a program load sequence. Writing a value of test(6) specifies an entity should initiate a testing sequence. Agent support of the writing of any of the values of this object is implementation-specific. For example, this object might be read only for entities that disabling would compromise the integrity of the chassis. Enumeration: 'reset': 4, 'enable': 2, 'unknown': 1, 'disable': 3, 'test': 6, 'programload': 5.

Provides operational status of the entity. The following are possible definitions of the values. The exact definition of the values is implementation specific. A value of other(1) implies some undetermined state, possibly as a result of setting chasEntityAdminStatus to a value of disable(3). A value of invalid(2) could have the possible meaning that the entity exists but the chassis manager has no direct control of the entity. A value of testing(3) may be a diagnostic state. A value of operational(4) implies that the entity is running with no errors or warnings. State resetInProgress(5) implies equivalent of setting chasEntityAdminStatus to reset(4). The states of warning(6), nonFatalError(7), fatalError(8) reflect conditions detected during operation. The entity may or may not be still functional. State loading(10) is a result of asserting programload(5) in chasEntityAdminStatus. For example if an entities value of chasEntityAdminStatus is disable(3) and is set to enable(2) then chasEntityOperStatus may enter a state of testing(3) then change to a value of operational(4). Enumeration: 'nonFatalError': 7, 'loading': 10, 'resetInProgress': 5, 'testing': 3, 'invalid': 2, 'operational': 4, 'warning': 6, 'fatalError': 8, 'other': 1.

The value of MIB-II's sysUpTime (in the agent supporting this MIB) at which this entity was last (re-)initialized. If the entity has not been initialized then this object has a zero value.

The SNMP Party which provides access to the detailed management information for this entity. Note that the definition of a SNMP Party includes the location at which it executes, the authentication and privacy algorithms and parameters required to access the management entity. In order for a SNMP manager to be able to access the Party, that manager must have prior knowledge of the Party. A party is named by a 'Party'. For a entity which is not managed through access to a SNMP Party, the value of this object is 0.0

The SNMPv2 Context indentifier the chasEntityContext in conjunction with chasEntityParty defines access to the MIB view for this entity.

The SNMP Community which executes at the address chasEntityIpAddress, and provides access to the detailed management information for this entity. For a entity which is not managed through access to a SNMP Community, the value of this object is the zero-length string.

The address of the SNMP agent which responds to messages for the SNMP Community identified by chasEntityCommunity. When access is via proxy, this variable contains the address of the proxy agent. For a entity which is not managed through access to a SNMP Community, the value of this object is 0.0.0.0.

This table defines a physical relationship between physical modules and resources. A resource is a building block. A resource defines the type of relationship between entities. This may be a back plane connection between physical modules sharing the same entity. It may be a network segment that connects multiple entities. This table then defines the physical mapping of resources and physical modules onto entities.

Defines a particular physical configuration relationship.

A resource exists on a particular module. A module is identified by it's physical location. Physical location is defined by location type and an instance of that physical location type. This object defines the location type. This object can be used in conjunction with chasPhyResLocation to index the module table.

A resource exists on a particular module. A module is identified by it's physical location. Physical location is defined by location type and an instance of that physical location type. This object defines a particular instance of the physical location.

A unique index for the chassis resource on this particular physical module.

The type of resource.

The physical module resource is assigned to a specific entity. This object defines the entity to which this resource is currently assigned. Notice, not all implementations may support this object as read-write. If read-write is supported assignment may still fail due to a number of reasons such as insufficient resources, invalid configuration.

Provides a unique index that can be used to identify the relationship in terms of the entity.

Defines a logical configuration relationship which is a relationship between entities and resources and the physical module that the relationship exists on.

Defines a single logical relationship.

The entity ID for which this logical configuration relationship exists.

The entity sub index for which this logical configuration relationship exists. The logical relationship is identified by a resource assignment to an entity. The sub index defines a particular instance of the mapping of physical configuration onto an entity.

A module is defined by it's physical location type and an instance of that physical location. This object defines the physical location type portion of the physical module identifier that this logical configuration exists for.

A module is defined by it's physical location type and an instance of that physical location. This object defines the instance physical location (location index) portion of the physical module identifier that this logical configuration exists for.

The value of this object refers to a particular instance of a resource, as defined by chasResourceIndex, for which this relationship is defined. This together with chasLogResLocationType and chasLogResLocation completes the mapping of the logical configuration on to the physical module and resource combination.

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

Values for a power supply.

An index value that uniquely identifies a power supply. This may correspond to a hardware power supply slot, which may or may not be the same as a network device slot (chasSlotIndex).

A textual description of the power supply, including the vendor's name and version.

Desired status of the power supply. Enumeration: 'unknown': 1, 'enable': 2, 'disable': 3.

Actual status of the power supply: - unknown(1) - status not known. - empty(2) - no power supply installed in slot - disabled(3) - unable to supply power due to chasPowerSupplyAdminStatus - bad(4) - unable to supply power due to failure - warning(5) - supplying power but an output or sensor is bad or warning - standby(6) - believed usable but not supplying power - engaged(7) - supplying power - redundant(8) - supplying power but not needed It is an implementation specific matter whether the agent keeps entries with status unknown(1) or empty(2) in the table. Enumeration: 'standby': 6, 'unknown': 1, 'engaged': 7, 'redundant': 8, 'disabled': 3, 'bad': 4, 'warning': 5, 'empty': 2.

A textual description of the power supply's operational status. Agents may use this string to provide detailed information on current failures, including how they were detected, and/or instructions for problem resolution. The contents are agent-specific.

The number of times chasPowerSupplyOperStatus has gone to warning(5).

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

This defines the instance of a physical location type of the power supply. Location Type together with location index completely defines the location of a power supply.

Defines a particular instance of a physical location type.

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

Values for a power supply output.

An index value that uniquely identifies a power supply. This may correspond to a hardware power supply slot, which may or may not be the same as a network device slot (chasSlotIndex).

An index value that uniquely identifies an output for the power supply.

Actual status of the power supply: - unknown(1) status not known - bad(2) unable to supply power due to failure - warning(3) supplying power but marginally - good(4) supplying power It is an implementation specific matter whether the agent keeps entries with status unknown(1) in the table. If unknown(1), offered values and counters are meaningless. Enumeration: 'unknown': 1, 'bad': 2, 'warning': 3, 'good': 4.

In hundredths of a volt, the voltage the output is supposed to supply, such as -5, +5, +12, -15, etc.

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

In hundredths of a watt, the wattage actually offered by the output. If chasPowerSupplyOutputStatus is good(4), the value 0 means offered wattage is not available.

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

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

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

Values for a environmental sensor.

The identification of an environmental sensor. Other AutonomousType values may be defined elsewhere, in association with specific protocols. However, this document assigns those of known interest as of this writing.

Actual status indicated by the sensor. It is an implementation specific matter whether the agent keeps entries with status unknown(1) in the table. If unknown(1), counters are meaningless. Enumeration: 'unknown': 1, 'bad': 2, 'warning': 3, 'good': 4.

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

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

Defines the actual type of physical location that this environmental sensor occupies.

This defines the particular instance of a physical location type which this environmental sensor occupies.

An index value that uniquely identifies an environmental sensor.