DECHUB900-CHASSIS-MIB-V3-0: View SNMP OID List / Download MIB

The number of slots directly connected to this chassis. For example, a chassis implementation with 8 slots returns 8 when this object is requested.

The number of directly connected slots which are presently occupied.

The maximum number of extended slot numbers supported in this chassis mib.

The total number of extended slots presently attached.

The total number of modules and extended modules which have been inserted and removed from the chassis. This counter is incremented: - when a module is inserted, and - when a module is removed. The goal of this object is to provide a single object which can be polled by an NMS to determine if there have been changes in the chassis population.

A table that contains information about the slots in the chassis.

A list of information for each slot in the chassis. Table rows may not be created or deleted with SNMP operations.

The number of the slot that the module occupies. Note that this index may exceed chasNumSlots if: - extended slots are present in the chassis, or - an integral component such as a management module is present in the chassis.

The sysObjectID of the module which occupies the slot. Besides sysObjectIDs, the value of this object may contain chasSlotUnknown or chasSlotBlocked. chasSlotUnknown (1.3.6.1.4.1.36.2.18.11.1.1.12.1.2) is used to describe a slot which contains a module which is for some reason 'unknown'. chasSlotBlocked (1.3.6.1.4.1.36.2.18.11.1.1.12.1.3) is used to describe a slot which is not usable because a double, triple, etc. width module prevents its use.

The value of MIB-II's sysUpTime (in the agent supporting this chassis MIB) at which a module was last inserted into this slot.

A textual description of the module inserted into the slot. If no description is available, this value is a zero length string. No description may be available if the module reports a chasSlotModuleAdminStaus of fatal-error.

A textual description of the version/revision level for this module's hardware and firmware. If not available, this value is a zero-length string.

The serial number of the module present in the slot. If no serial number is available for a module, this value is a zero length string.

Indicates the size of the module. min(1) modules are decHub90 compatible modules. max(2) modules are full sized DEChub900 modules. The value system(3) is used to denote a module which is neither a min(1) or max(2) module; for example, the integral management module is a system(3) module. Enumeration: 'max': 2, 'system': 3, 'min': 1.

Indicates the operational state of the module. up(1) indicates that the module is performing as expected. disabled(2) indicates that the module has been disabled. insufficient-power(3) indicates that the chassis lacks the power needed by the module. fatal-error(4) indicates that the module encountered an error which prevents its operation. non-fatal-error(5) indicates that the module encountered an error which may inhibit its operation, but does not prevent its operating in a diminished capacity. Enumeration: 'disabled': 2, 'fatal-error': 4, 'up': 1, 'non-fatal-error': 5, 'insufficient-power': 3.

Provides the administratively desired state of the given module. A disabled module is activated by writing a value of enable(2). A slot may be de-activated by writing a value of disable(3). A disabled slot is available for subsequent activation. Writing a value of reset(4) specifies that the model initiate a reset sequence. Writing a value of restore-to-defaults(5) specifies that the module restore all of its non-volatile parameters to their factory default state and reset the module. 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 slots that disabling would compromise the integrity of the chassis. Enumeration: 'disabled': 3, 'unknown': 1, 'restore-to-defaults': 5, 'enabled': 2, 'reset': 4.

A device specific non-fatal error status indication.

This object is used to reset, restore, and test all active modules in the chassis. Modules which are managed by the DECagent90 may only be reset using the DECagent90's MIB. This object may be used to reset, restore, and test all DEChub900 modules and some DEChub90 modules which reside in the DEChub900 chassis. When read, the value 'unknown(1) is returned. Setting this object to 'resetAllModules(2)' has the same affect as setting the chasSlotModuleAdminStatus of each entry in the chasSlotTable, except the entry for the Hub manager itself, to 'reset(4)'. Setting this object to 'resetAllModulesAndMgr(3)' has the same affect as setting the chasSlotModuleAdminStatus of each entry in the chasSlotTable to 'reset(4)'. Since the Hub Manager is reset, no SNMP response is sent when this object is set to resetAllModulesAndMgr(3). Setting this object to 'resetAllModulesToDefaults(2)' has the same affect as setting the chasSlotModuleAdminStatus of each entry in the chasSlotTable, except the entry for the Hub manager itself, to 'restore-to-defaults(5)'. Setting this object to 'resetAllModulesAndMgrToDefaults(3)' has the same affect as setting the chasSlotModuleAdminStatus of each entry in the chasSlotTable to 'restore-to-defaults(5)'. Since the Hub Manager is reset, no SNMP response is sent when this object is set to resetAllModulesAndMgr(3). Enumeration: 'resetAllModulesAndMgrToDefaults': 5, 'unknown': 1, 'resetAllModules': 2, 'resetAllModulesToDefaults': 4, 'resetAllModulesAndMgr': 3.

A counter which is incremented whenever entity table entries are added or deleted, and when one of the following fields of an existing chasEntityTable is modified: o chasEntityCommunity, o chasEntityIpAddress, or o chasEntityAccessMethod Entity changes occur when the IP address or one of the community strings of a device is changed. This counter is also incremented: o when modules are inserted, o when modules are removed, and o when chasEntityCommunity, chasEntityIpAddress, or chasEntityAccessMethod of an existing entry changes. (This does not count in chasEntityOperStatus of an existing entry.)

A table containing information about the 'logical' networking devices (entity) in this chassis.

Information concerning an entity in the chassis. Table rows may not be created or deleted with SNMP operations.

A unique index for the table entry.

The generic function of the entity. The value is a sum. Starting from zero, for each type of generic function that the entity performs, 2 raised to a power is added to the sum. The powers are according to the following table: Function Power -------- ------ repeater 0 -- e.g. Ethernet repeater, -- e.g. FDDI concentrator bridge 1 router 2 terminalServer 3 agent 4 -- entity that defines chassis MIB services 5 -- e.g. MIB Walk tools manager etc mau 6 power 7 networkMonitor 8 -- e.g. RMON device other 15 -- e.g. None of the above For example, an entity performing both bridging and routing functions would have a value of 6 (2^1 + 2^2). *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

The value of this object is analogous to the MIB-II sysObjectID object. As stated in MIB-II, `It provides an easy and unambiguous means for determining what kind of box is being managed.' *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

A textual description of the entity. *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

A textual description of the version/revision level for this entity's hardware, ROM, and software. *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

This object 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 exists within the chassis, but is benign. A disabled entity is available for subsequent activation. (The table entry remains, but the entity for which it refers is disabled. The entity will perform no SNMP, except the operation to this object.) Writing a value of reset(4) specifies an entity initiate a reset sequence. Writing a value of programload(5) specifies an entity initiate a program load sequence. Writing a value of test(6) specifies an entity 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. Or, devices which do not support downline load may reject sets to programLoad(5). *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. *************************************************************** Enumeration: 'reset': 4, 'enable': 2, 'unknown': 1, 'disable': 3, 'test': 6, 'programload': 5.

This object provides operational status of the entity. other - A value of other(1) implies some undetermined state, possibly as a result of setting chasEntityAdminStatus to a value of disable(3). invalid - A value of invalid(2) indicates that the entity exists but the chassis manager has no direct control of the entity. testing - A value of testing(3) is in a diagnostic state. operational - A value of operational(4) implies that the entity is running with no errors or warnings. resetInProgress - State resetInProgress(5) implies equivalent of setting chasEntityAdminStatus to reset(4). warning, nonFatalError, and fatalError - The states warning(6), nonFatalError(7), fatalError(8) reflect conditions detected during operation. The entity is functioning is a diminished capacity when warning or nonFatalError are indicated. When fatalError is indicated the device may or may not be functional. loading - State loading(10) is a result of asserting programload(5) in chasEntityAdminStatus. *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. *************************************************************** 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. *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

The SNMP Version 2 Party which provides access to the detailed management information for this entity. An entity which is not managed through SNMP Version 2 returns a zero-length object-identifier. An entity which is not managed through SNMP returns chasEntityNoParty. *************************************************************** This object has been deprecated. Devices no longer have to support it. It's OID may not be reused. For devices which already support it, it may *not* be used for any purpose other than its original indended purpose described above. ***************************************************************

The SNMP Community which when paired with chasEntityIpAddress 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 IP address which when paired with chasEntityCommunity provides access to the detailed management information for this entity. When access is via proxy, this object contains the IP address of the proxy agent. For a entity which is not managed through access through a community name, internet address pair the value of this object is 0.0.0.0.

The access rights associated with the community name, internet address pair. Note: Just because a user directs a message to the community name, internet address pair does not imply that the user is authorized on that pair. Additional security mechanisms may be employed such that only messages from particular internet addresses are authorized. THIS OBJECT IS ONLY HERE FOR BACKWARDS COMPATIBILITY WITH OLDER VERSION OF HUBWATCH THAT DO NOT SUPPORT chasEntityAccessCharacteristics. THIS OBJECT SHOULD BE DEPRECATED WHEN ALL VERSIONS OF HUBWATCH, THAT ARE IN THE FIELD, ARE SUPPORTING THE NEW INTERFACE. Enumeration: 'readWrite': 2, 'readOnly': 1, 'other': 4, 'traps': 3.

This object contains methods of access for a given module. If the entity is accessed by SNMP the value of this object is a zero length string, or a host IP address used for 'security' purposes. If access to the entity is by a means other than SNMP, this object contains the protocol and address used to access the Entity. This object is an opaque type. It contains a Type-Length-Value encoding where: octet 1 Type The type of protocol address specified in the value portion of this encoding. The type has the form: dh90Module(1), mgmtSet(2), telnet(3) octet 2 Length The length of the value. This length may contain a value from 1 to 30. octet 3..Length The value, which may be up to 30 octets. The dh90Module(1) type indicates that the entity is a DEChub90 module. The eight octet value portion contains a 2 octet DEChub90 module type, followed by a 6 octet hardware address. The mgmtSet(2) type indicates that the value of this object was derived from the chasEntityAccessLoadTable. The value portion is 'opaque'. It will take on any value which was set in the corresponding entry of the chasEntityAccessLoadTable. The telnet(3) type indicates that the module is accessible via telnet. The six octet value portion contains a 4 octet IP address, and a 2 octet TCP port number.

The slot number used to communicate with this agent. For entities which occupy more than one slot this value is the lowest slot number that this entity occupies.

This object is used to provide HOST IP ADDRESS AUTHENTICATION. Host IP address authentication can be performed two different ways, depending on whether there is a subnet mask provided in chasEntitySrcSubnetMask. If chasEntitySrcSubnetMask is not defined, then the host IP address (source IP address in the SNMP command PDU) must be equal to this object. If chasEntitySrcSubnetMask is defined, then the host IP address (source IP address in the SNMP command PDU) is ANDed with the chasEntitySrcSubnetMask, and the value must be equal to this object. If the values are equal, then that SNMP command is authorized the community access rights for the associated chasEntityCommunity, chasEntityIpAddress pair. NOTE 1: This is assuming that the community profile has been authorized. NOTE 2: Multiple source IP addresses can be defined for the same community name, internet address pair. See example at the begining of the chasEntityTable. For an entity which is not supporting host IP address authentication scheme, the value of this object is 0.0.0.0.

This object is used in conjunction with the chasEntitySrcIpAddress to provide HOST IP ADDRESS AUTHENTICATION. Refer to chasEntitySrcIpAddress for a description For an entity that does not support the subnet mask, this value is 0.0.0.0.

This object is used to provide access characteristics pertaining to other objects in the given entity row. The characteristics are divided into categories. Each category uses a set of predefined bits to encode data. The following categories are currently supported: Category Bits -------- ---- Community Access Rights 1..4 Network Interface 5..6 UNUSED 7..15 The categories are orthogonal to each other, so it is not necessary to perform 'inter-category' bounds checking. The object value is a concatentation of encodings from each category, and can be considered a sum. The actual encoding mechanism is defined on a per category basis. Categories ========== Community Access Rights ----------------------- Community access rights are associated with the community name, internet address pair. More than one access right can be defined for a given community name, internet address pair. The encoding works as follows: Starting from zero, for each access right supported, 2 raised to a power is added to the sum. The powers are according to the following table: Type Power ---- ----- readOnly 0 readWrite 1 trap 2 other 3 For example, a community name, internet address pair with readOnly and readWrite access rights, would have a value of 3 (2^0 + 2^1). An access right of other(3) defines the entity row as non-SNMP manageable. Management information is provided in the chasEntityAccessMethod and the Network Interface (defined below). Note: Just because a user directs a message to the community name, internet address pair does not imply that the user is authorized on that pair. Additional security mechanisms may be employed such that only messages from particular internet addresses are authorized. Network Interface ----------------- The network interface is associated with the internet address and defines the route for management traffic. A network interface can be one of the following: none(0), obm(1), ibm(2), and port(3). The value is placed in the 2-bits reserved for network interfaces. Note: ibm(2) and port(3) are both in-band management. The difference is ibm(2) is a module wide ip address, and port(3) is associated with a particular port/interface.

A table that contain manually entered entity access information.

A list of information about how to access entities.

The number of the slot in which the chasEntityAccessLoadMethod information applies.

A value which is loaded into chasEntityAccessMethod if the slot is occupied by a module for which no better information about how to access the entity exists.

A table that contains change counters for each module in the chassis.

Information concerning module change counters.

The slot number in which the chasEntityChangeCounter applies.

A counter which is incremented whenever entity table entries, for a particular slot, are added, deleted, or changed. Adds and deletes occur when: o IP addresses are added, o IP addresses are deleted, o modules are inserted, and o modules are removed. Entity changes occur when one of the following fields of an existing chasEntityTable is modified: o chasEntityCommunity, o chasEntityIpAddress, or o chasEntityAccessMethod. (This does not count in chasEntityOperStatus of an existing entry.) NOTE: The chasEntityChanges counter is incremented when ever an instance of the chasEntityChangeCounter is incremented.

A table that contains information about the backplane(s) present in the chassis.

A list of information of the backplane(s) in the chassis.

A unique index for the table entry.

A textual description of the backplane.

A textual description of the revision level of the backplane.

The number of slots this backplane supports.

A table that contains information about the network segments contained within the chassis, and used to interconnect the chassis' logical networking devices.

A list of information for a particular segment in the chassis.

A unique index for the network segment for which this entry contains information.

An administratively assigned segment name.

A segment's media type. Enumeration: 'atm': 4, 'tr': 3, 'pebus': 6, 'async': 5, 'ethernet': 2, 'fddi': 1.

The index of specific media type a segment is selected to serve, from the chasSegSubtypeTable.

Status of a segment table entry. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

A table that contains information about the subtype of a network segment, contains additional information about the segment. The speed of a token ring may be specified, for example.

A list of information of subtypes for segment in the chassis.

A unique index for the table entry.

The specific media type a segment is selected to serve. Enumeration: 'default': 1, 'thinwire': 2, 'imb': 3, 'imb2': 4.

The speed of the segment expressed in thousands of bits per second.

Status of a segment table entry. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

The default VNbus state. While enabled(1), a VNbus segment will be created automatically when a line card containing a VNbus port awakens, and the port will be connected to the segment. The segment will be removed when the last line card containing a VNbus port is removed. No automatic segment/connection creation/removal takes place while this is disabled(2). Enabling the default VNbus causes any unconnected VNbus ports that have not been explicitly disconnected to be connected to the VNbus segment (which will be created automatically if necessary). Disabling it has no effect on existing VNbus port connections. Enumeration: 'disabled': 2, 'enabled': 1.

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

The number of physical changes that have occurred in the chassis backplane configuration since the agent was warm/cold started. Specifically, this object is incremented: 1) whenever chasConnEntryStatus for any object becomes 'valid', 2) whenever chasConnEntryStatus transitions from 'valid' to any other state, and 3) whenever the chasConnSegment or chasConnPort of a 'valid' chasConnEntry is modified.

A list of Tx port to backplane connections. At cold boot, MAM initializes the table for a populated hub based on default configuration. MAM has the ownership of this table. The creation of an entry in this table by NMS causes Management Agent to set the interface status of a corresponding icomBpConnTable port to 'connected'.

Backplane connection definition.

Index into the table.

An index value of the chasSegmentTable.

An index value of the chasPortTable.

A downstream neighbor's backplane port index in the chasPortTable. It is only used by ring segments. This object has the value 65535 when not using a ring segment, or no downstream neighbor exists.

Status of a connection table entry. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

The value of MIB-II's sysUpTime (in the agent supporting this chassis MIB) at which a port had its chasPortOperStatus change.

A list of backplane ports on installed line cards. MAM initializes the table based on what is learned from the icomBpIfTables and has the ownership of this table.

Line card backplane port definition.

Index into the table.

Slot ID of a line card. If a line card has more than one backplane port, same slot ID may appear multiple times in this table.

An administratively assigned path name. A Default value will be assigned by the management agent module. Users may overwrite the default value. This object in non-volatile. The default value is based on the values of chasPortType and chasPortSubtypeSelect. Recommended defaults are: Default chasPortType chasPortSubtypeSelect ================= =============== ===================== Ethernet ethernet 0 (Nothing selected) Ethernet ethernet default Thinwire Ethernet ethernet thinwire Repeater Bus ethernet imb FDDI fddi 0 (Nothing selected) FDDI fddi default FDDI-A fddi fddiA FDDI-B fddi fddiB FDDI-M fddi fddiM FDDI-S fddi fddiS Token Ring tr 0 (Nothing selected) Token Ring tr default ATM atm 0 (Nothing selected) ATM atm default Asynchronous asynch 0 (Nothing selected) Asynchronous asynch default

A port's media type. Ethernet type consists of IMB and ThinWire subtypes. TrMatrix and TrDH90 are not managed by the matrix manager for BL2 (reserved types). Enumeration: 'atm': 4, 'tr': 3, 'pebus': 6, 'async': 5, 'ethernet': 2, 'fddi': 1.

The index in chasPortSubtypeTable that has been selected for this port. The 0 value for this index is only legal as a place holder for an unconfigured port.

Status of a port. Enumeration: 'broken': 1, 'configured': 3, 'testing': 4, 'connected': 5, 'unconfigured': 2.

A list of backplane port description for installed line cards. MAM initializes the table based on what is learned from the icomBpIfTables and has the ownership of this table.

Line card backplane port descriptive text.

Index in the Port Table of the port described by this entry

Text that describes the function of the port. This text is read from the line card.

A table that contains information about the subtype of a port, contains additional information about the port. The speed of a token ring port may be specified, for example.

A list of information of subtypes for port in the port table.

Index into the table.

The index of a port in the chasPortTable that can support the specified chasPortSubtypeFlavor and chasPortSubtypeSpeed. A value of '-1' occurs in the first table row indicating a port which will not be reconnected on a hub power cycle.

The specific media type a port is selected to support. A value of zero (0), though not allowed as an enumerated value, occurs in conjunction with the occurrance of a chasPortSubtypePortIndex of '-1' (see above). Enumeration: 'thinwireEndStation': 2, 'atmMaster': 13, 'fddiB': 7, 'imbRepeater': 5, 'default': 1, 'thinwireFlexRepeater': 10, 'imb2Repeater': 15, 'fddiS': 9, 'imbEndStation': 4, 'imb2FlexRepeater': 16, 'fddiA': 6, 'thinwireRepeater': 3, 'fddiM': 8, 'imbFlexRepeater': 11, 'imb2EndStation': 12, 'atmSlave': 14.

The speed of the port expressed in hundreds of bits per second.

The maximum number of power supplies which may be installed within this chassis.

The current number of power supplies which are installed within this chassis.

A count of the total number of times a chasPowerConfigOperStatus value in the chasPowerConfigTable has changed. This does not include changes that occur when entries are created and deleted due to module insertion and deletion. This counter may not equal the sum of the chasPowerConfig- Warnings and chasPowerConfigFailures counters because modules which have undergone environmental changes could have been removed from the chassis. The purpose of this object is to provide a single object which can be polled by an NMS to determine if anything in the chasPowerConfigTable has changed.

This indicates whether the present configuration can continue to operate if any one of the power supplies fail or is removed. In certain configurations, the hub may need one, two or three power supply modules. The addition of an extra power supply module will allow for the failure of any one of the power supply modules. A power system such as this which allows for the failure of any one of the power supplies is referred to as a 'redundant power system'. Some redundant power systems provide standby power supplies which engages only when a primary supply fails. Unlike this type of system, the DEChub900 power system employs load sharing. Each power supply provides a portion of the power necessary to power the system. When redundant power is available in the system, the failure of one supply causes the load of the remaining supplies to increase sufficiently to make up for the failed supply. Enumeration: 'redundantPowerAvailable': 1, 'redundantPowerNotAvailable': 2.

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.

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: o unknown(1) - status not known. o empty(2) - no power supply installed in slot o disabled(3) - unable to supply power due to chasPowerConfigAdminStatus o bad(4) - unable to supply power due to failure o warning(5) - supplying power but an output or sensor is bad or warning o standby(6) - believed usable but not supplying power o engaged(7) - supplying power o 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 chasPowerConfigOperStatus has gone to warning(5).

The number of times chasPowerConfigOperStatus has become bad(4).

The total amount of power available within the chassis. This value is expressed in milli-watts. This value will not go below zero if there are unpowered modules in the chassis. This value is based on the maximum rating of the power supply. Therefore, this value will not equal the sum of the chasPowerSourceTable's chasPowerSourcePower objects. The chasPowerSourcePower object specifies power available at a specific voltage.

The total amount of current available within the chassis. This value is expressed in milli-amperes. This value will not go below zero if there are unpowered modules in the chassis.

A list of power supply source capabilities.

Values for a power supply output.

An index value that identifies the power supply. This value corresponds to chasPowerConfigIndex.

An index value that uniquely identifies an output for the power supply. A value of zero indicates that no power supply is installed.

The nominal voltage available thru this supply. The value of this object is expressed in milli-volts.

The total power available at the nominal voltage of this supply. The value of this object is expressed is milli-watts.

A list of slot power requirements.

A Slot's power requirement definition.

An index into the table which corresponds to chasSlotIndex.

An index per chasPowerSinkVoltage.

The voltage, in milli-volts used by the power sink.

The amount of power, in milli-watts, needed by the power sink.

Indicates if the slot is drawing power. It is an implementation specific matter whether the agent keeps entries with status unknown(1) in the table. Enumeration: 'unknown': 1, 'notInUse': 3, 'inUse': 2.

A count of the total number of changes to existing entries in the chasEnvironOperStatus have occurred. This does not include changes that occur when entries are created and deleted due to module insertion and deletion. This counter may not equal the sum of the chasEnviron- Warnings and chasEnvironFailures counters because modules which have undergone environmental changes could have been removed from the chassis. The purpose of this object is to provide a single object which can be polled by an NMS to determine if anything in the chasEnvironTable has changed.

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

Values for an environmental sensor.

An index value that uniquely identifies the slot in which the sensor is sensing stuff.

An index value that uniquely identifies one of possibly many sensors within a slot.

The type of the sensor. Enumeration: 'dc-power': 5, 'other': 1, 'fan': 3, 'temperature': 2, 'humidity': 4.

The desired state of the sensor. When sensors are 'disabled' their chasEnvironWarnings and chasEnvironFailures counters do not change. Moreover, chasEnvironChanges will not change as a result of a 'disabled' sensor. Enumeration: 'unknown': 1, 'enable': 2, 'disable': 3.

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. If 'disabled', counters freeze. Enumeration: 'disabled': 5, '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).

A list of boot/load information for the slots.

Slot boot/load information.

Slot ID of the owner of the boot information.

This object is used to control the program load process of a device. When read, the value other(1) is returned. When set to start-read(2) the device initiates a TFTP read operation to read a new program image. When set to start-write(3) the device is placed in such a state as to accept a new program image via a TFTP write operation. Once initiated, the status of the load attempt is reflected in chasLoadOperStatus. A device shall always reset upon completion of a successful load attempt. It may reset upon unsuccessful completion of the load attempt. When set to cancel(4) the device will attempt to cancel an ongoing load. Enumeration: 'cancel': 4, 'start-write': 3, 'other': 1, 'start-read': 2.

The final state of the last load attempt. none(1) indicates that no load has been attempted, ever. Enumeration: 'failure': 3, 'none': 1, 'success': 2.

The name of the file in which to load. When the device is reading, this is the name of the file to be read. When the device is being written, this is the only name of the file in which writes will be accepted - provided the device can check the file name. If the device can not check the file name then this object is ignored. It is the duty of the NMS triggering the device to load this object. This object is non-volatile for a mam Load. The initial value of this object is a zero-lengthed string. In the case of multi-file loads (aka segmented loads) this object contains the name of the first file in which to load. It is an application specific issue as to how to get subsequent load files.

The IP address of the host from which to load. When the device is reading, this is the IP address of the host in which the read will be directed. When the device is being written, this is the IP address of the only host in which writes will be accepted. This object is non-volatile for slotId corresponding to the management agent module. The initial value of this object is 0.0.0.0. Sets of this object to 0.0.0.0 and 255.255.255.255 are rejected with a badValue error.

A device specific parameter which may be used to indicate detailed error information about the last attempted load. A value of zero indicates that no load has been attempted, or that there is nothing interesting to report of the last load.

Used to create and delete rows in the load table. Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.

The number of entries in the Ligo table.

A list of LIGOs (building blocks).

A LIGO entry containing objects which describe the building block.

A unique value for each LIGO. The value of this object ranges between 1 and n where n is the total number of building blocks supported by the device.

Slot number associated with this building block.

A building block's type. Enumeration: 'ethernet': 3, 'other': 1, 'atm': 4, 'fddi': 2.

The chasLigoSubtypeIndex into the chasLigoSubtypeTable which describes the specific LIGO type a building block is selected to support. The value of this object must be a valid index in the chasLigoTable. A value of 0 indicates that no subtype has been selected.

The number of entries in the chasLigoSubtypeTable.

A list of LIGO (building blocks) subtypes.

An entry containing objects which describe the building block's specific type.

A unique value for each LIGO subtype.

The value of the LigoIndex in the chasLigoTable that can use this subtype.

This object specifies the ports that are used by this LigoSubtype. It is a bit map of port indexes from the chasPortTable with bit 0 corresponding to port index 1. Bits set to 1 indicate the ports which are used by the LigoSubtype.

This object specifies the labels that are used by this LigoSubtype. It is a bit map of if indexes from the chasLigoLabelTable with bit 0 corresponding to if index 1. Bits set to 1 indicate the labels which are used by the LigoSubtype.

A building block's type. Enumeration: 'fddiRoot-Secondary': 2, 'fddiTrunk-B-Primary': 6, 'fddiTrunk-A-Primary': 4, 'atm-front': 17, 'fddiTrunk-A-Secondary': 5, 'fddiStump-Secondary': 11, 'fddiStump-Primary': 10, 'fddiNonroot-S': 15, 'ethernet-back': 13, 'fddiRoot-Primary': 1, 'fddiNonroot-SM': 16, 'ethernet-front': 12, 'fddiTrunk-AB-Secondary': 9, 'fddiNonroot-M': 14, 'atm-back': 18, 'fddiNonroot': 3, 'fddiTrunk-AB-Primary': 8, 'fddiTrunk-B-Secondary': 7.

This object specifies the ports that are used by this LigoSubtype. It is a bit map of port indexes from the chasPortTable with bit 0 corresponding to port index 1. This object supports twice as many ports in the hub as chasLigoSubtypePortMask. Bits set to 1 indicate the ports which are used by the LigoSubtype.

This object specifies the labels that are used by this LigoSubtype. It is a bit map of if indexes from the chasLigoLabelTable with bit 0 corresponding to if index 1. This object supports twice as many ligos in the hub as chasLigoSubtypeLabelIndexMask. Bits set to 1 indicate the labels which are used by the LigoSubtype.

The number of entries in the chasLigo label table.

A list of Labels (for ports).

An entry containing objects which describe the label of the port affected by the LIGO this module supports.

A unique value for each Label. The value of this object ranges between 1 and n where n is the total number of Labels supported by the device.

A textual description of the port number associated with a LIGO. If the device is bridge then bridge port number should be used for the ethernet and fddi. If the device is a wire concentrator then concentrator port numbers should be used.

Provides the means to enable and disable Backplane Auto Healing. When enabled, the Management Agent Module updates the chasRingMemberTable with the current backplane configuration, and takes action to repair FDDI rings and performs whatever steps are necessary for all other backplane technologies when a module is out of service. When disabled, all entries of the chasRingMember table are deleted and the Management Agent Module will not perform any Backplane Auto Healing. Enumeration: 'disabled': 2, 'enabled': 1.

A list of slots and their status.

An entry containing the objects which describe the slots and their patching status.

The backplane slot ID for this entry. Only slots that are currently eligible for patching will appear in the table.

The FDDI network segment for which this entry contains information, from chasSegmentIndex. This object is superceded by the chasRingMemberSegmentMask, but is left here for backwards compatibility.

The current patch status of the slot. in(1) means that the linecard is an active part of the hub. out(2) means the linecard has been patched around if necessary, and is not currently attached to its backplane LAN(s). Enumeration: 'out': 2, 'in': 1.

This object specifies the segments that are used by this slot module. It is a bit map of segment indexes from the chasSegmentTable with bit 0 corresponding to segment index 1. Bits set to 1 indicate the segments which are used by the slot module.