S5-CHASSIS-MIB: View SNMP OID List / Download MIB

The chassis type. This is 'what kind of box' is being managed. The values are defined under s5ChasTypeVal in the Registration MIB.

A description of the chassis. The value is a zero length string if no information is available.

The physical location of the chassis (e.g., 'fourth floor wiring closet in building A'). The value is a zero length string if no information is available. Note: this object is different from sysLocation in MIB-II. However, an agent may use this value for sysLocation if none is configured in the the agent.

The textual identification of the contact person for the chassis, together with information on how to contact this person. The value is a zero length string if no information is available. Note: this object is different from sysContact in MIB-II. However, an agent may use this value for sysContact if none is configured in the agent.

The version of the chassis in the form 'major.minor.maintenance[letters]'. If the version is unknown or not available then the value should be a zero length string.

The serial number of the chassis. If the serial number is unknown or unavailable then the value should be a zero length string.

The total number of physical changes (i.e., an addition or removal of a component or sub-component) that have been detected in the chassis since cold/warm start of the agent.

The value of sysUpTime when the last physical change (i.e., addition or removal of a module or sub-module) was detected in the chassis. If none have been detected since cold/warm start of the agent, then the value is zero.

The total number of attachment changes across all boards in the chassis that have been detected since cold/warm start of the agent.

The value of sysUpTime when the last attachment change on any board in the chassis was detected. If none have been detected since cold/warm start of the agent, then the value is zero.

The total number of configuration changes (other than attachment changes, or physical additions or removals) across all boards in the chassis that have been detected since cold/warm start of the agent.

The value of sysUpTime when the last configuration change (other than attachment changes, or physical additions or removals) on any board in the chassis was detected. If none have been detected since cold/warm start of the agent, then the value is zero.

A table that contains information about each group that can contain chassis components.

A row in the group table. Rows can not be created or deleted via SNMP requests. The number of entries is determined by the physical construction of the chassis.

The index of the group.

The type of the group. The group type determines the types of items that can be plugged into the positions in the group. The groups are defined under s5ChasGrpTypeVal in the Registration MIB.

The description of the group. If not available, the value is a zero length string.

The maximum number of entries in the group. If not available, a value of -1 is returned.

The current number of entries in the group. If not available, a value of -1 is returned.

The total number of physical changes (i.e., an addition or removal of a component or sub-component) that have been detected in the group since cold/warm start of the agent.

The value of sysUpTime that the last physical change (i.e., addition or removal of a module or sub-module) was detected in the group. If none have been detected since cold/warm start of the agent, then the value is zero.

The multiplication factor used in encoding the component index of a component in the group. The component index for any group should be determined in conjunction with this object for that group. A value of 1 indicates 'no encoding'. Stackable platforms: The component index is encoded using the following formula: Component Index = (Unit# * s5ChasGrpEncodeFactor) + Module# Where: Unit# is obtained from s5ChasComIndx for the Unit Group, and Module# is the module number in a unit starting from 1 and increases in a left-to-right and bottom-to-top fashion. NonStackable platforms: These NMMs like 5310, 5510 will always return a value of 1 for this object. Encoding/decoding should not be performed in this case.

A table that contains information about each chassis level component and sub-component.

A row in the component/sub-component table. Rows can not be created or deleted via SNMP requests. Entries are created and deleted when components or sub-components are inserted or removed from the chassis.

The index of the chassis level group which contains this component.

The index of the component in the group. For example, for modules in the 'board' group, this is the slot number.

If this table entry (i.e. table row) describes a component, then the value is zero. Otherwise, this table entry describes a sub-component and this is the index of the sub-component.

The type of component/sub-component. The values are defined under s5ChasComTypeVal in the Registration MIB.

A description of the component/sub-component. If not available, the value is a zero length string.

The version number of the component/sub-component. If not available, the value is a zero length string.

The serial number of the component/sub-component. If not available, the value is a zero length string.

The value of sysUpTime when it was detected that the component/sub-component was added to the chassis. If this has not occurred since the cold/warm start of the agent, then the value is zero.

The desired state of the component/sub-component. The values that are read-only are: other(1)......currently in some other state notAvail(2)...actual value is not available The possible values that can be read and written are: disable(3)...disable operation enable(4)....enable operation reset(5).....reset component test(6)......start self test of component, with the result to be normal(5), warning(8), nonFatalErr(9), or fatalErr(10) in object s5ChasComOperState The allowable (and meaningful) values are determined by the component type. Enumeration: 'reset': 5, 'enable': 4, 'disable': 3, 'other': 1, 'notAvail': 2, 'test': 6.

The current operational state of the component. The possible values are: other(1).........some other state notAvail(2)......state not available removed(3).......component removed disabled(4)......operation disabled normal(5)........normal operation resetInProg(6)...reset in progress testing(7).......doing a self test warning(8).......operating at warning level nonFatalErr(9)...operating at error level fatalErr(10).....error stopped operation notConfig(11)....module needs to be configured obsoleted(12)...module is obsoleted but in the chassis The allowable (and meaningful) values are determined by the component type. Enumeration: 'obsoleted': 12, 'normal': 5, 'testing': 7, 'disabled': 4, 'resetInProg': 6, 'notAvail': 2, 'nonFatalErr': 9, 'fatalErr': 10, 'notConfig': 11, 'removed': 3, 'warning': 8, 'other': 1.

The potential number of sub-components that can be attached to the component. A value of zero means none. A value of -1 indicates that no component information is available. The actual number of installed sub-components is found in s5ChasComNumSubs. If this entry is a sub-component, then this object has a value of zero.

The actual number of sub-components that are attached to the component. A value of zero means none. A value of -1 indicates that no component information is available. The potential number of sub-components that can be installed is found in s5ChasComMaxSubs. If this entry is a sub-component, then this object has the value of zero.

This object describes the position of each component in the unit group relative to each other. Components in the unit group are numbered in the ascending order with the uppermost component being numbered one. The value of this object should never be greater than the value of s5ChasGrpMaxEnts. If not available, a value of zero will be returned. Note: This object is only implemented in agents that support 'virtual' chassis.

This object provides geographic location information of a component in a system modeled as a chassis, but possibly physically implemented with geographically separate devices connected together to exchange managment information. Chassis' modeled in this manner are sometimes refered to as 'virtual chassis'. An example value is: '4th flr wiring closet in blg A'. Notes: 1.) This object is applicable only to components that can be found in either the Board or Unit groups. If the information is unavailable (i.e., not modeling a virtual chassis or component is not in Board or Unit group), the value is a zero length string. 2.) If this object is applicable and is not assigned a value via a SNMP SET PDU when the row is created, the value will default to the value of the object s5ChasComSerNum.

This object describes the group mapping of each component in the chassis. For the components in the unit group, the value of this object should be the backplane number to which the unit is connected. The value of this object should never be greater than the value of s5ChasGrpMaxEnts. If not available, a value of zero should be returned.

This object indicates the number of ports (of any type) contained in a component, not including any sub-components contained within the component.

This object indicates the total number of ports (of any type) contained in a component, including any ports contained in sub-components contained within the component.

The IP address of a component. For components that do not have an IP address/stack, this value should always be 0.0.0.0. Note that for a stackable system in stack mode, this will be the standalone IP address for individual units in the stack.

The version number of the software image running on this component/sub-component. If not available, the value is a zero length string.

The IPv6 address of a component. For components that do not have an IPv6 address/stack, this value should always be 0::0. Note that for a stackable system in stack mode, this will be the standalone IPv6 address for individual units in the stack.

The IPv6 netmask of a component. For components that do not have an IPv6 address/stack, this value should always be 0::0. Note that for a stackable system in stack mode, this will be the standalone IPv6 netmask for individual units in the stack.

The IP address associated with the physical dedicated management port (out of band management port) of a component. For components that do not have an IP address/stack associated with the dedicated management port, this value should always be 0.0.0.0. Note that for a stackable system in stack mode, this IP address always applies to individual units in the stack.

The IP netmask associated with the physical dedicated management port (out of band management port) of a component. For components that do not have an IP address/stack associated with the dedicated management port, this value should always be 0.0.0.0. Note that for a stackable system in stack mode, this netmask always applies to individual units in the stack.

The IP address of the default gateway associated with the physical dedicated management port (out of band management port) of a component. For components that do not have an IP address/stack associated with the dedicated management port, this value should always be 0.0.0.0. Note that for a stackable system in stack mode, this IP address always applies to individual units in the stack.

The IPv6 address associated with the physical dedicated management port (out of band management port) of a component. Note that for a stackable system in stack mode, this IP address always applies to individual units in the stack.

The IPv6 netmask associated with the physical dedicated management port (out of band management port) of a component. Note that for a stackable system in stack mode, this netmask always applies to individual units in the stack.

This object indicates the in-bound packet threshold rate for the management port (out of band management port).

This object indicates the port shutdown period for the management port (out of band management port).

This object is used to control whether the out of band management port is up or down (false for port up and true for port down).

The time (in hundredths of a second) since the unit was initialized.

A table containing information about each board that can be inserted into a slot. These include boards such as Repeater Modules and Network Management Modules.

A row in the board table. Entries can not be created or deleted via SNMP. Entries are created and deleted when boards are inserted or removed from slots in the chassis.

The index of the board. This corresponds to the index of the slot containing the board.

A bit array that contains the value of the front panel LEDs and the annunciator. This is a packed bit string; each LED is encoded into 4 bits (a nibble). The first nibble is stored in the high order bits of the first octet. The second nibble is stored in the low order bits the first octet, etc. However, the current mapping is that the first three nibbles are reserved, the fourth nibble has the value of the 'annunciator', and the 'normal' LEDs start with the fifth nibble. If the LED values are not available, a zero length string is returned. The following shows the meaning of each bit (bit 0 is the least significant bit) when it has a value of one: bit meaning --- ------- 0 green light 1 yellow light 2 blinking 3 reserved

The total number of backplane network attachment points on the board. This may vary based on the mode of the board for FDDI.

The total number of attachment changes for the board that have been detected since cold/warm start of the agent or since the board was inserted.

The value of sysUpTime when the last attachment change on the board has detected. If none have been detected since cold/warm start of the agent, then the value is zero.

The current ASCII character display of the board. The length returned should match the length of the display. Boards with multiple displays should return the values concatenated together. Boards with no display hardware should return a zero length string.

The date of manufacture of the board in ASCII in the format: YYYYmmdd. For example, the value for April 13, 1993 is 19930413. If not available, the value is a zero-length string.

The source of the configuration at the last board reset. The values are: other(1)........unknown or some other value dfltJmpr(2).....default jumpers prmMem(3).......permanent memory on board brdCfg(4).......saved configuration on board sm(5)...........supervisor smDfltJmpr(6)...SM and default jumpers smPrmMem(7).....SM and permanent memory on board smBrdCfg(8).....SM and saved configuration on board Enumeration: 'smDfltJmpr': 6, 'smBrdCfg': 8, 'prmMem': 3, 'smPrmMem': 7, 'other': 1, 'brdCfg': 4, 'sm': 5, 'dfltJmpr': 2.

The total number of configuration changes for the board that have been detected since cold/warm start of the agent or since the board was inserted.

A bit array that contains the value of the front panel LEDs of the fan trays. This is a packed bit string; each LED is encoded into 4 bits (a nibble). The first nibble is stored in the high order bits of the first octet. The second nibble is stored in the low order bits of the first octet etc. The current mapping is that the first four nibbles are reserved, the fifth nibble has the value of the 'annunciator', and the 'normal' LEDs start with the sixth nibble. If the LED values are not available, a zero length string is returned. The following shows the meaning of each bit (bit 0 is the least significant bit) when it has a value of one: bit meaning --- ------- 0 red light 1 blue light 2 purple light 3 blinking 4 reserved

A table containing information about each backplane attachment point on a board. The number of entries for a board is the value of s5ChasBrdNumAtt.

A row in the attachment point table. Entries can not be created or deleted via SNMP. Entries are created and deleted when boards are inserted or removed from slots in the chassis, or the number of attachment points is changed.

The index of the board. This corresponds to the index of the slot containing the board.

The index of the attachment point on the board.

The default setting for the attachment point. An attachment point may be attached to a local channel, not attached to any backplane network, or attached to a media specific backplane network. (The valid choices depend on each specific attachment point.) NOTE: This value will always be valid and may change when the backplane divider switch setting is changed.

The current setting for the attachment point. The slot position of the board, the setting of the backplane divider switch(es), and the mode setting affect which backplane networks are valid values. Also, some boards may put limitations on which backplane network(s) or local channel(s) may be used.

The total number of attachment changes for the attachment point that have been detected since cold/warm start of the agent.

The value of sysUpTime when the last attachment change for the attachment point was detected. If none have been detected since cold/warm start of the agent, then the value is zero.

A bit array that contains the bit map representing all available backplane segment and local segment connections for the cluster. One bit is also reserved to indicate if the cluster has an isolate capability. The first 31 bits of the array represent the backplane numbers, starting from the lower order bit. Bit 32 indicates whether the Cluster has a null connection capability. The bits in the fifth and sixth octets, starting with bits in the lower order octet, represent local segments that the cluster can connect to. A bit with a value of 1 means that the cluster is capable of connecting to the corresponding backplane segment, local segment or null segment.

A table containing information about each 'dual mode' local channel on a board.

A row in the local channel table. Entries can not be created or deleted via SNMP. Entries are added or removed by adding or removing a board that has a 'dual mode' local channel from a slot in the chassis.

The index of the board. This corresponds to the index of the slot containing the board.

The index of the local channel.

Indicates the attachment/isolation mode of a local channel to a backplane channel. The values that are read/write are: connected(2)......connect local chan N to bkpl N notConnected(3)...disconnect local chan N from bkpl The possible values that can be read are: other(1)..........unknown connected(2)......local chan N connected to bkpl N notConnected(3)...local chan N isolated from bkpl N Enumeration: 'notConnected': 3, 'other': 1, 'connected': 2.

A table listing the storage areas on each component/sub-component in the chassis. The number is determined by the components in the chassis which have manageable storage areas. Examples of storage areas include RAM(main memory), FLASH, ROM, EEPROM, etc. This does not include disk drives.

A row in the table of storage areas. The entries can not be created or deleted via SNMP requests. Only those components/sub-components that have storage areas that are installed are present. Storage areas that are on components have a sub-component index value of zero. Storage areas that are on sub-components have a non-zero sub-component index value.

The index of the chassis level group which contains the component or sub-component containing the storage area.

The index of the component or the component which contains the sub-component containing the storage area.

If the storage area is on a component, then the value zero. Otherwise, the storage area is on a sub-component and this is the index of the sub-component.

The index of the storage area on the component or sub-component.

The storage area type on the containing component/sub-component. The values are defined under the .0 branch of the value of s5ChasComType for the component/sub-component containing the storage area in the Registration MIB.

The current size of the storage area in bytes. A value of zero means the storage area is not installed or not usable. A value of -1 indicates that the size is unknown (or unavailable).

The version of the contents (i.e., the code or data) of the storage area in the form 'major.minor.maintenance[letters]'. If not known or not available, then the value is a zero length string. If multiple contents are stored in this container, the the value will contain multiple sub-versions, each separated by a semicolon (;).

Name of the image file to be downloaded or uploaded when the s5AgInfoFileAction object is set to upload or download an image. When the object is not used, the value is a zero-length string.

The current size of the storage area that is currently in use, measured in bytes. A value of zero means the storage area is not in use. A value of -1 means the size is unknown (or unavailable).

A string describing the storage area. When the object is not used, the value is a zero-length string.

A counter of the number of writes performed on this storage area which for areas residing in flash memory is an indication of the flash memory age. This number is the maximum number of writes for any of the access units (e.g. sector) from the storage area. A value of zero means the storage area is not in use. A value of -1 means the age is unknown (or unavailable).

A bit array that contains the value of the supervisor LEDs. (The format of these are the same as the format for object s5ChasBrdLeds.) If not available, a zero length string is returned.

The date of manufacture of the SM module in ASCII in the format: YYYYmmdd. For example, the value for April 13, 1993 is 19930413. If not available, a zero length string is returned

A table that contains temperature sensor values.

A row in the s5ChasTmpSnrTable. Rows in this table will exist for each existing row in the s5ChasComTable which represents a temperature sensor. The values of the indices of the row in this table will be equal to those of the corresponding row in the s5ChasComTable.

The index of the chassis level group which contains this component, corresponds to s5ChasComGrpIndx.

The index of the component in the group. Corresponds to s5ChasComIndx.

Sub-component index. Corresponds to s5ChasComSubIndx.

The current temperature value of the temperature sensor. This is measured in units of a half degree centigrade, e.g. a value of 121 indicates a temperature of 60.5 degrees C. This object is deprecated because it cannot represent temperature values below 0, as Gauge32 is an unsigned type.

The current temperature value of the temperature sensor. This is measured in units of a half degree centigrade, e.g. a value of 121 indicates a temperature of 60.5 degrees C.

A table that contains CPU and memory utilization information.

A row in the s5ChasUtilTable. Rows in this table will exist for each existing row in the s5ChasComTable which represents any chassis component for which CPU and/or memory utilization values are available. The values of the indices of a row in this table will be equal to those of the corresponding row in the s5ChasComTable.

The index of the chassis level group which contains this component, corresponds to s5ChasComGrpIndx.

The index of the component in the group. Corresponds to s5ChasComIndx.

Sub-component index. Corresponds to s5ChasComSubIndx.

This object returns the percentage of time the CPU has been busy since system initialization.

This object returns the percentage of time the CPU has been busy over the last 1 minute.

This object returns the percentage of time the CPU has been busy over the last 10 minutes.

This object returns the percentage of time the CPU has been busy over the last 1 hour.

This object returns the percentage of time the CPU has been busy over the last 24 hours.

This object returns the percentage of dynamic memory that is currently free. This is measured as a percentage of the memory the was available immediately after system initialization.

This object returns the lowest percentage of dynamic memory that has been free since system initialization. This is a 'low-water mark' for memory utilization, and is essentially the lowest value of s5ChasUtilMemoryUsage since system initialization.

This object returns the percentage of time the CPU has been busy over the last 10 seconds.

This object returns the total RAM of unit.

This object returns the available RAM of unit.

A table that contains extended information on RPSU power supply components.

A row in the s5ChasPsRpsuTable. Rows in this table will exist for each existing row in the s5ChasComTable which represents any RPSU power supply. The values of the indices of a row in this table will be equal to those of the corresponding row in the s5ChasComTable.

The index of the chassis level group which contains this component, corresponds to s5ChasComGrpIndx.

The index of the component in the group. Corresponds to s5ChasComIndx.

Sub-component index. Corresponds to s5ChasComSubIndx.

This object returns the specific type of RPSU. It can be set to indicate to the system the type of installed RPSU in cases where the RPSU type cannot be automatically detected. Enumeration: 'bayStack15': 3, 'bayStack10': 1, 'nes': 2.

This object is used to specify how a particular RPSU should be used by the system, as follows: ups(1) Indicates that the RPSU should be used only as an uninterruptible power source for devices attached to powered ethernet ports. rpsu(2) Indicates that the RPSU should be used only as a source of backup power for the device itself. powerSharing(3) Indicates that the RPSU should be used both as a source of backup power for the device, and as a UPS for devices attached to powered ethernet ports. Enumeration: 'powerSharing': 3, 'rps': 2, 'ups': 1.

5000 Chassis MIB Copyright 1995-2012 Nortel Networks, Inc. All rights reserved. This Nortel Networks SNMP Management Information Base Specification (Specification) embodies Nortel Networks' confidential and proprietary intellectual property. Nortel Networks retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS', and Nortel Networks makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

This object is used in the s5CtrFanDirectionError notification to indicate fan direction. Enumeration: 'right': 2, 'left': 1.

A table that contains information about pluggable ports.

A row in the s5ChasGbicInfoTable.

A unique value, greater than zero, for each interface.

The type of pluggable part.

The wavelength value measured in nanometers for the pluggable part.

The name of the vendor of the pluggable part.

The Organizationally Unique Identifier (OUI) of the pluggable part.

The vendor part number of the pluggable part.

The vendor revision of the pluggable part.

The vendor serial number for the pluggable part.

The hardware options supported by the pluggable part. Bits: 'rxLoss': 0, 'txDisable': 2, 'txFault': 1.

The manufacturing date of the pluggable part.

The Common Language Equipment Identification Code of the pluggable part.

The product code of the pluggable part.