SYNOPTICS-COMMON-MIB: View SNMP OID List / Download MIB

The 3000 series agent's Module type. Enumeration: 'm281xSA': 23, 'm3522': 21, 'm2310x': 30, 'm3314-ST': 4, 'm351xSA': 25, 'm271x': 18, 'm3513': 15, 'm3512': 7, 'm2310': 6, 'm3514': 8, 'm281x': 19, 'other': 1, 'm291x': 17, 'm271xSA': 27, 'm810M': 24, 'm3314M-ST': 5, 'm332x': 9, 'm3313': 2, 'm331xSA': 26, 'm2486': 28, 'm332xS': 11, 'm3356': 10, 'm2300x': 29, 'm3313M': 3, 'm331xA': 20, 'm3910S': 12, 'm3395': 13, 'm3394': 14, 'm331xS': 16, 'm2722': 22.

The agent's module firmware version 0=Rev A,1=Rev B,etc.

The agent major software version number. (version is specified as major.minor.maint or 3.0.1). Object is in decimal.

The agent minor software version number (version is specified as major.minor.maint or 3.0.1). Object is in decimal.

Boot protocol used to load the module with its software. On Agents with the Local Load option the value return by this object is valid only if the MIB object s3LocImageLoadMode is remoteBoot(2) or localAsBackup(4). Enumeration: 'proprietary': 5, 'dll-download': 6, 'ieee802-1e': 4, 'tftp-only': 3, 'other': 1, 'bootp-tftp': 2.

The name of the boot file that is sent to the file server during boot time. The actual boot protocol used to retrieve the file is determined by s3AgentBootProtocol. This parameter will not take effect until written into EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) is issued. This parameter is used only if the s3AgentBootMode is set to use EEPROM.

Enable or disable the use of authentication error trap generation. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless the specific NMM configuration file is updated to reflect the change. This object is now deprecated. Managers should use the snmpEnableAuthenTraps object in MIB-II instead. This object is aliased to snmpEnableAuthenTraps. Changing either variable will change the other accordingly. Enumeration: 'enable': 2, 'disable': 1.

This is a informational string that could be used to show the physical location (i.e. area) of the NMM or concentrator. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless the specific NMM configuration file is updated to reflect the change. This object is now deprecated. Managers should use the sysLocation object in MIB-II instead.

Used to determine current MIB release supported by agent. The encoding of this object is of the following form: xyy, where x is the major version number and yy is the minor version number. Thus, version 3.0 would be represented as 300, version 3.01 would be 301 and 3.1 would be 310. Object is in decimal. Values that correspond to each agent type and version are specified in the other SynOptics documentation.

Used to determine feature level of the agent. The encoding of this object is of the following form: xyy, where x is the major version number and yy is the minor version number. Thus, feature level version 1.0 would be represented as 100, version 1.01 would be 101 and 1.1 would be 110. Object is in decimal. The current values are the following: 100 - 331x V3.x - Basic Agent 100 - 351x - Basic Agent 100 - 271x V3.x - Basic Agent 101 - 281x V5.0 - Basic Agent - Dual Stack 102 - 331x V4.2.0 - Basic Agent - Non Segmentable Chassis - Ethernet Common board table - Ethernet Command port table - redundant power supply group 103 - 331xA V4.2.0 - Basic Agent - Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - Ethernet plus statistics, 104 - 331xA V4.2.0 - Basic Agent - Non-Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - Ethernet plus statistics, 109 - 331x V4.2.0 - Basic Agent - Segmentable Chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group 112 - 281x V5.1.0 - Basic Agent - Dual Stack - Network to MAC address mapping 113 - 331x V5.1.0 - Basic Agent - Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping 114 - 331x V5.1.0 - Basic Agent - Non-Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping 115 - 331xA V5.1.0 - Basic Agent - Segmentable chassis - Dual Stack - Full Truffle Support - Network to MAC address mapping 116 - 331xA V5.1.0 - Basic Agent - Non-Segmentable chassis - Dual Stack - Full Truffle Support - Network to MAC address mapping 200 - 331x V4.0 & V4.0.1 - Advanced Agent 200 - 271x V4.x - Advanced Agent 200 - 351x V4.x - Advanced Agent 200 - all FDDI Agents 201 - 331x V4.1.0, V4.1.1 - Advanced Agent - redundant power supply group 202 - 331xS V4.1.0, V4.1.1 - Advanced Agent - redundant power supply group - DS/SD traffic tables, - Ethernet plus statistics, - frame type distribution table - frame length distribution table 203 - 281x V4.2.0 - Advanced Agent - Dual Stack 204 - 331x V4.2.0 - Advanced Agent - Non-Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group 205 - 331xS V4.2.0 - Advanced Agent - Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - DS/SD traffic tables, - Ethernet plus statistics, - frame type distribution table - frame length distribution table 206 - 331xS V4.2.0 - Advanced Agent - Non-Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - DS/SD traffic tables, - Ethernet plus statistics, - frame type distribution table - frame length distribution table 207 - 331xA V4.2.0 - Advanced agent - Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - Ethernet plus statistics, 208 - 331xA V4.2.0 - Advanced agent - Non-Segmentable chassis - Ethernet Common board table - Ethernet Common port table - redundant power supply group - Ethernet plus statistics, 209 - 331x V4.2.0 - Advanced agent - Segmentable chassis - Ethernet Common board table - Ethernet Command port table - redundant power supply group 212 - 331x V5.1.0 - Advanced Agent - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups 213 - 281x V5.1.0 - Advanced Agent - Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups 214 - 331x V5.1.0 - Advanced Agent - Non-Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups 215 - 331xA V5.1.0 - Advanced Agent - Segmentable chassis - RMON Ether Stats, History, Alarm, Event Groups - Dual Stack - Full Truffle Support - Network to MAC address mapping 216 - 331xA V5.1.0 - Advanced Agent - Non-Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups 217 - 331xS V5.1.0 - Advanced Agent - Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups - Bulk table retrieval for traffic matrix 218 - 331xS V5.1.0 - Advanced Agent - Non-Segmentable chassis - Full Truffle Support - Dual Stack - Network to MAC address mapping - RMON Ether Stats, History, Alarm, Event Groups - Bulk table retrieval for traffic matrix

Slot where this agent currently resides. If hardware is unable to determine then a 0 should be returned.

This object contains the IP address of the last station that tried to access this agent with an invalid community string. This object is used as a VarBind in an Authentication Trap PDU. A get request will return the last value used, and will return the null address 0.0.0.0 if no authentication traps have been sent.

This object contains the community string of the last unauthenticated attempt to access this agent. This object is used as a VarBind in an Authentication Trap PDU. A get request will return the last value used, and will return the null string (length 0) if no authentication traps have been sent.

The software license code assigned to this agent. This code is required for initializing the agent. The code consists of exactly eight printable characters.

This counts the CPU idle time of the agent in units of 10 microseconds.

The agent software maintenance version number (version is specified as major.minor.maint or 3.0.1). Object is in decimal.

This indicates whether the agent should get configuration data from the network, use the local configuration data, or try the network first and then fall back to local configuration if the network load fails. This object applies only to agents with boot prom support for agent configuration load options. This parameter will not take effect until written into EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) is issued. Enumeration: 'localConfig': 3, 'localAsBackup': 4, 'other': 1, 'remoteConfig': 2.

This indicates whether the agent loaded configuration data from the network or used the local configuration data. Enumeration: 'localConfig': 3, 'other': 1, 'remoteConfig': 2.

This indicates from which network transports over which the agent will accept SNMP requests. This object only applies to agents with IP and IPX dual stack support. This parameter will not take effect until written into EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) or a restart (s3AgentRestart) is issued. Enumeration: 'ip': 2, 'ipx': 3, 'other': 1, 'ipAndIpx': 4.

This indicates which network transports over which the agent will currently accept SNMP requests. Enumeration: 'ip': 2, 'ipx': 3, 'other': 1, 'ipAndIpx': 4.

The name of the agent image file that the NMM loads at boot time. This parameter will not take effect until written to EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) is issued. This parameter is used only if s3AgentBootMode is set to use eeprom(1), s3AgentConfigLoadMode is set to localConfig(3) and s3LocImageLoadMode is not set to localBoot(3).

The Agent's administrative IP address. The current operational IP address can be obtained by the ipAdEntAddr entry in the ipAddrTable. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless it is written into EEPROM (s3AgentWriteEeprom). This parameter is used only if the s3AgentBootMode is set to use EEPROM.

The Agent's administrative subnet mask. The current operational subnet mask can be obtained by the ipAdEntNetMask entry in the ipAddrTable. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless it is written into EEPROM (s3AgentWriteEeprom). This parameter is used only if the agentBootMode is set to use EEPROM. NOTE: The Model 331x (3313, 3313M, 3314-ST, 3314M-ST) Ethernet NMM agents do not store this parameter in EEPROM, so for these agents the subnet mask configuration must be downloaded in the configuration file.

The Agent's administrative default gateway IP address. The current operational default gateway's IP address can be obtained from the ipRoutingTable. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless it is written into EEPROM (s3AgentWriteEeprom). This parameter is used only if the agentBootMode is set to use EEPROM.

The IP address to which the requests for boot files are sent. The protocol used to retrieve the boot files is determined by object s3AgentBootProtocol. This parameter will not take effect until until written into EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) is issued. This parameter is used only if the s3AgentBootMode is set to use EEPROM.

The agent's administrative secondary default gateway IP address. This default gateway's IP address will be used when the primary default gateway (s3AgentDefaultGateway) is determined unreachable. This parameter will not survive a reset (s3AgentReset) unless it is written into EEPROM (s3AgentWriteEeprom).

Controls whether the agent will periodically send out the icmp echos (pings) to the default router(s). The values are: other(1)...unknown or other on(2)......agent will periodically send out pings to the default router(s). off(3).....agent won't send out the pings to the default router(s). Enumeration: 'on': 2, 'other': 1, 'off': 3.

The time interval that the agent uses to send out the pings periodically to the default router(s) to check if the router(s) are still reachable.

The default route IP address used at boot time to download the NMM's agent configuration and image files from the TFTP server. This parameter will not survive a reset (s3AgentReset) unless it is written into EEPROM (s3AgentWriteEeprom).

Table containing list of NMS's that are to receive traps generated by this NMM.

A destination address and community string to a particular trap server, along with a trap filter and entry aging capability.

Setting this object to the value invalid(3) has the effect of invalidating the corresponding entry in the s3AgentTrapReceiverTable. That is, it effectively disassociates the address identified with the entry by removing the entry from the table. On a read the value of valid(2) should be returned if the entry contains a valid record, or invalid(3) should be returned if the entry contains an invalid record. Enumeration: 'other': 1, 'valid': 2, 'invalid': 3.

IP address for trap server that is to receive the trap.

Community string used for traps sent to this trap receiver.

This is the time interval used to age entries out of the trap receiver table. The default value if not specified will be 0, or infinite, never to be aged out.

This indicates whether the NMM is online(2) and operating, or offline(1) (ie: not connected to the concentrator backplane). Enumeration: 'offline': 1, 'online': 2.

The network management module's MDA hardware version number (0=Rev. A, 1=Rev. B, etc.).

This indicates whether the NMM is operating in primary(1) or secondary(2) mode. Enumeration: 'other': 3, 'primary': 1, 'secondary': 2.

Network management module reset status. Writing a reset(2) to this object will reset the NMM and perform a download and restart. Enumeration: 'reset': 2, 'noReset': 1.

Network management module restart status. Writing a restart(2) to this object will restart the NMM. This initializes all the counters, re-reads the EEPROM data structure and starts executing from the beginning of the code. Enumeration: 'noRestart': 1, 'restart': 2.

The method for obtaining boot parameter information. The possible values are: eeprom(1)......get boot info from eeprom net(2).........get boot info from remote server otherCase(3)...not eeprom or net This parameter will not take effect until written into EEPROM (s3AgentWriteEeprom) and a reset (s3AgentReset) is issued. Note: In previous versions of this MIB the name associated with the value '2' was 'other', which implied the same meaning as it does now. Thus to prevent confusion, the name for value '3' was chosen to be 'otherCase'. Enumeration: 'net': 2, 'otherCase': 3, 'eeprom': 1.

Network management module EEPROM write status. Writing a (2) to this object will write the contents of current EEPROM data structure in the EEPROM. Enumeration: 'writeEeprom': 2, 'noWriteEeprom': 1.

Specifies the baud rate in bits per second of either the internal modem or the RS-232 port. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless the specific NMM configuration file is updated to reflect the change.

This is the initialization string used to establish the out-of-band connection. (i.e. could contain the string ATDT,415-960-1100 for an internal or external modem). This is used as a hint for the network manager since this string is not used by the agent to initiate a connection to a management station. This parameter will take effect only after a restart (s3AgentRestart) is issued. This parameter will not survive a reset (s3AgentReset) unless the specific NMM configuration file is updated to reflect the change.

The size of the EEPROM of the agent in units of bytes.

The size of the EPROM of the agent in units of bytes.

The size of the DRAM of the agent in units of bytes.

The current 4 ASCII character display of the agent. Agents with no hex display hardware should return a zero length string.

This indicates the operational status of the flash device of the agent. A fail(3) indicates that either the flash device configuration on board is not valid or the flash EEPROMs on the board have failed. Enumeration: 'fail': 3, 'other': 1, 'ok': 2.

This indicates whether the agent has a valid local code image on board. An EPROM checksum failure would cause the agent to return localImageInvalid(3). Enumeration: 'localImageInvalid': 3, 'localImageValid': 2, 'other': 1.

The major software version number of the locally-stored image. This object applies only to agents with valid local image. Other agents should return zero.

The minor software version number of the locally-stored image. This object applies only to agents with valid local image. Other agents should return zero.

This indicates whether the agent should get code from the network, use a local image, or try the network first and then fall back to local image if the network boot fails. The localBoot(3) and localAsBackup(4) values apply only to agents with local load option. Note: on agents that have no local storage, either remoteBoot(2), or remoteNoUpdate(5) may be specified, however the value remoteBoot(2) is prefered due to backwards compatibility Enumeration: 'localBoot': 3, 'remoteBoot': 2, 'remoteNoUpdate': 5, 'localAsBackup': 4, 'other': 1, 'localAutoUpdate': 7, 'remoteNewUpdate': 6.

This indicates whether the agent loaded code from the network or used a local image. When the the ImageLoadMode is localAsBackup, this variable indicates whether the network load was successful. Enumeration: 'remoteImage': 2, 'other': 1, 'localImage': 3.

The maintenance software version number of the locally-stored image. This object applies only to agents with valid local image. Other agents should return zero.

The chassis type.

The chassis backplane type.

The chassis backplane revision.

The chassis power supply type. This value is valid only when the backplane type is not other(1). If the chassis has a redundant backplane, the agent returns redundantCapable(5), even if only one power supply is installed. The objects s3RedPsPrimaryConfig and s3RedPsSecondaryConfig should be consulted to determine the installed power supply type(s) with redundant backplanes.

The chassis power supply status. Enumeration: 'primaryFail': 2, 'secondaryFail': 3, 'ok': 1, 'bothFail': 4.

The status of the chassis cooling fan. Enumeration: 'fail': 2, 'other': 3, 'ok': 1.

The chassis slot configuration table.

What type of module is in each slot of the chassis.

The 3000 Chassis slot number. Valid entries are 1-12.

ID for the module. Values are specified in SynOptics technical documents.

The type of module this entry represents. Values are specified in SynOptics technical documents.

Module description. Values are specified in SynOptics technical documents.

Status of the module LEDs. Format is specified in SynOptics technical documents. NOTE: the 291x FDDI workgroup concentrators actually return a string with size of 10.

ID of the medium-dependent part of the board. The value is board dependent. Values are specified in SynOptics technical documents.

A table containing information about the boards currently plugged into the 3000 Chassis. This board table contains an entry for each non-empty slot in the s3SlotConfigTable, EXCEPT for those slots containing Retiming Modules. All of the information in this board table is retrievable using the NMI commands that are common to all boards integrated into the SynOptics Series 3000 Concentrators.

A table entry containing information about a single Board currently plugged into the 3000 Chassis. These values can be retrieved using the common board NMI commands.

A unique value for each board. Its value ranges between 1 and 12. The value for each board must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.

This is the ID of the board, which is 'hard-coded' in the board, and identifies the board's basic functionality. Some boards have the capability to change aspects of their functionality, such as media type, interface types, or power supply wattages, by plugging in different daughter cards. Other boards may identify the type of cable plugged into them. The boards that have these capabilities use different values for the object s3SlotModuleMda to identify the changable portion of the functionality currently used. Boards that do not support these capabilities typically set the object s3SlotModuleMda to 255 or zero. The combination of the value of this object and the s3SlotModuleMda object are then mapped by software to determine the type of module (i.e., s3SlotModuleType). Notes: 1.) The object s3SlotModuleType is marked as deprecated. 2.) Agents do not implement a complete mapping of s3CommonBoardId and s3SlotModuleMda to s3SlotModuleType. The mapping that is performed pertains to the media type of the agent. The possible values for this object are: m331x(1)...................331x Ethernet NMM m3302(2)...................3302 Ethernet STP Host m332x(3)...................332x Ethernet Local Bridge m3304ST(4).................3304 Ethernet FOIRL-ST Host m3305(5)...................3305 Ethernet UTP Host m333x(6)...................333x Ethernet Repeater/Retiming m3307(7)...................3307 Ethernet 50 Pin UTP Host m3308(8)...................3308 10BaseT UTP Host m3301(9)...................3301 10Base2 Thin Net Host m3904(10)..................3904 FDDI Multimode Fiber Host m3902(11)..................3902 FDDI STP Host m3910S(12).................3910S FDDI NMM m331xS(14).................331xS Ethernet NMM m3100R(15).................3100R Power Supply Summing m3502(16)..................3502 Token Ring Passive STP Host m3502A(17).................3502A Token Ring Passive STP/UTP Host m353x(18)..................353x Token Ring RI/RO Repeater m3040(19)..................3040 Network Control Engine (NCE) m3505(20)..................3505 Token Ring Active UTP Host m3505A(21).................3505A Token Ring Active UTP Host m355x(22)..................355x Token Ring FOIRL RI/RO Repeater m3040S(23).................3040S Network Control Engine m351x(24)..................351x Token Ring NMM m332xS(25).................332xS Ethernet High Speed Local Bridge m338x(26)..................338x Ethernet Remote Router m3328(27)..................3328 Ethernet Switching Engine (ESE) m3395(28)..................3395 Terminal Server m3394(29)..................3394 LattisTalk Router/Repeater m3522(30)..................3522 Token Ring Local Bridge m3395A(31).................3395A Terminal Server m3800(32)..................3800 Multimedia Router m3368(36)..................3368 Ethernet LattisSecure Host m3308A(38).................3308A 10BaseT Host m2810nmm(39)...............2810 Ethernet NMM m2810hm(40)................2810 Ethernet Host m3301ohms75(41)............3301-75 Ethernet Thin Net Host (75-ohm) m3301ohms93(42)............3301-93 Ethernet Thin Net Host (93-ohm) m2912(43)..................2912 FDDI STP Concentrator m2914(44)..................2914 FDDI Fiber Concentrator m3502B(45).................3502B Token Ring Passive STP/UTP Host m3505B(46).................3505B Token Ring Active STP/UTP Host m3307HD(47)................3307HD Ethernet 100 Pin UTP Host m2702Fhm(48)...............2702F Token Ring Passive Host m2712Fhm(49)...............2712F Token Ring Passive Host m2712hm(50)................2712 Token Ring Passive Host m2702hm(51)................2702 Token Ring Passive Host m2813nmm(52)...............2813 Ethernet NMM m2813hm(53)................2813 Ethernet Host m2814hm(54)................2814 Ethernet Host m2803hm(55)................2803 Ethernet Host m3356(56)..................3356 Ethernet Remote Bridge m2814nmm(57)...............2814 Ethernet NMM m2804hm(58)................2804 Ethernet Host m2702Chm(59)...............2702C Token Ring Passive Host m2715Fhm(60)...............2715F Token Ring Active Host m2705Fhm(61)...............2705F Token Ring Active Host m2705Chm(62)...............2705C Token Ring Active Host m3902A(63).................3902A FDDI STP Host m2912A(64).................2912A FDDI STP Concentrator m271xnmm(65)...............271x Token Ring NMM m2715hm(66)................2715 Token Ring Active Host m3910SSD(67)...............3910S-SD FDDI NMM m3313A(68).................3313A Ethernet NMM m3314A(69).................3314A Ethernet NMM m3304A(70).................3304A Ethernet 10BaseF Host m3910SA(71)................3910SA FDDI NMM m2705hm(72)................2705 Token Ring Active Host m3905(73)..................3905 FDDI UTP Host m2915(74)..................2915 FDDI UTP Concentrator m2715Bhm(75)...............2715B Token Ring Active Host m2705Bhm(76)...............2505B Token Ring Active Host m2715BFhm(77)..............2715B-F Token Ring Active Host m2712Bhm(78)...............2712B Token Ring Passive Host m2712BFhm(79)..............2712B-F Token Ring Passive Host m2702BChm(80)..............2702B-C Token Ring Passive Host m3486(82)..................3486 LattisEngine/486 m810m(88)..................810M Ethernet Concentrator m3517SA(101)...............3517SA Token Ring NMM m3308B(102)................3308B 10BaseT Host m2813SAnmm(103)............2813SA Ethernet NMM m2814SAnmm(104)............2814SA Ethernet NMM m3313SA(105)...............3313SA Ethernet NMM m3314SA(106)...............3314SA Ethernet NMM m3174(107).................3174 Workstation Controller m3522A(108)................3522A Token Ring Local Bridge m3513SA(109)...............3513SA Token Ring NMM m271xSAnmm(110)............271xSA Token Ring NMM m2300x(114)................2300x Product m2310x(115)................2310x Product m3299C(116)................3299-C Terminal Multiplexor Adapter m3299U(117)................3299-U TTP Terminal Multiplexor Adapter m3299F(119)................3299-F Fiber Optic Terminal Adapter m3410(120).................3410 Fast Ethernet Network Management Module m3405(121).................3405 Fast Ethernet Host Module with 12 100BASE-TX ports m3475(122).................3475 Fast Ethernet Host Module with 11 100BASE-TX ports and 1 100BASE-FX port mAlcatelEthConcnmm(250)....Alcatel Ethernet NMM mAlcatelEthConchm(251).....Alcatel Ethernet Host mAlcatelEthExpConchm(252)..Alcatel Ethernet Expansion Host Enumeration: 'm3314A': 69, 'm271xnmm': 65, 'm3313SA': 105, 'mAlcatelEthConcnmm': 250, 'mAlcatelEthExpConchm': 252, 'm2705hm': 72, 'm3305': 5, 'm3910SSD': 67, 'm2715BFhm': 77, 'm2715Bhm': 75, 'm3902A': 63, 'm3313A': 68, 'm3174': 107, 'm353x': 18, 'm2813SAnmm': 103, 'm3522': 30, 'm2712Fhm': 49, 'm3513SA': 109, 'm331x': 1, 'm3368': 36, 'm2702hm': 51, 'm3308B': 102, 'm3308A': 38, 'm271xSAnmm': 110, 'm3475': 122, 'm3040S': 23, 'm3395A': 31, 'm2810hm': 40, 'm3314SA': 106, 'm3505': 20, 'm2813hm': 53, 'm3502': 16, 'm2705Fhm': 61, 'm332xS': 25, 'm2814SAnmm': 104, 'm351x': 24, 'm2814hm': 54, 'm3395': 28, 'm3394': 29, 'm331xS': 14, 'm3502A': 17, 'm2914': 44, 'm2915': 74, 'm2803hm': 55, 'm3302': 2, 'm3301': 9, 'm3307': 7, 'm333x': 6, 'm3308': 8, 'm2712hm': 50, 'm810m': 88, 'm3304ST': 4, 'm3301ohms75': 41, 'm2702Fhm': 48, 'm3902': 11, 'm3100R': 15, 'm3904': 10, 'm3905': 73, 'm2310x': 115, 'm3505B': 46, 'm3505A': 21, 'm3522A': 108, 'm3301ohms93': 42, 'm2705Chm': 62, 'm2810nmm': 39, 'm2705Bhm': 76, 'm2814nmm': 57, 'mAlcatelEthConchm': 251, 'm338x': 26, 'm3405': 121, 'm3910S': 12, 'm3486': 82, 'm3502B': 45, 'm3517SA': 101, 'm3328': 27, 'm2715Fhm': 60, 'm2715hm': 66, 'm3304A': 70, 'm2813nmm': 52, 'm3307HD': 47, 'm3800': 32, 'm3040': 19, 'm2712BFhm': 79, 'm2712Bhm': 78, 'm3410': 120, 'm2300x': 114, 'm332x': 3, 'm3910SA': 71, 'm2702BChm': 80, 'm355x': 22, 'm3356': 56, 'm3299F': 119, 'm2804hm': 58, 'm3299C': 116, 'm3299U': 117, 'm2912': 43, 'm2912A': 64, 'm2702Chm': 59.

The hardware revision of the board. 0=Rev. A, 1=Rev. B, etc.

This indicates the operational status of the board. Enumeration: 'fail': 2, 'ok': 1.

This indicates the reset state of the board. Writing with the value reset (2) will reset the board. Enumeration: 'reset': 2, 'noReset': 1.

Tells whether the board is partitioned or enabled. Writing with the value partition(2) will partition the board indefinitely and writing with the value enabled(1) will enable the board. If a timed partition is desired, then this object must be written with timedPartition(3) and in the same PDU a partition duration must be supplied in s3CommonBoardPartTime. Timed partitions will not survive across a reset. In this case the port will go to the partition(2) state. Boards cannot be partitioned in the 2810 concentrator and other workgroup concentrators. These agents will implement this object as read-only. Enumeration: 'partition': 2, 'enabled': 1, 'timedPartition': 3.

Tells whether the board is under network management control. The value nmControl(2) indicates that the board or one or more ports are being controlled by network management. This means that the board or one or more ports are partitioned via a network manager. Enumeration: 'notNmControl': 1, 'nmControl': 2.

This indicates the operational status of the board power supply. A fail(2) indicates that one of the power supplies on the board has failed. Enumeration: 'fail': 2, 'ok': 1.

When partitioning the board for a specified time, s3CommonBoardPartStatus must be set with timedPartition(3) and this object must be supplied with the duration value. If a PDU sets s3CommonBoardPartStatus and not this object, the board will not be partitioned. This value is decremented while the board is partitioned until the value reaches zero at which time the board is enabled.

Packed octet string for the slot configuration table. Format is specified in SynOptics technical documents. NOTE: the 291x FDDI workgroup concentrators actually return a string with size a multiple of 14.

This gauge is measured in amperes.

This gauge is measured in amperes.

This status indicates whether the ambient temperature is normal, i.e., below 40 degree C. Enumeration: 'aboveNormalTemp': 3, 'other': 1, 'normalTemperature': 2.

This gauge is measured in Celsius.

This indicates the primary power supply type (PS 1). Note that value redundantCapable(5) should not be returned for this object.

This indicates the secondary power supply type (PS 2). Note that value redundantCapable(5) should not be returned for this object.

This gives the status of the summing diode on the 3100R associated with the indicated power supply. Enumeration: 'primaryFail': 3, 'other': 1, 'bothFail': 5, 'bothOk': 2, 'secondaryFail': 4.

This tells whether the indicated power supply is sensing voltage on the backplane. Enumeration: 'primaryFail': 3, 'other': 1, 'bothFail': 5, 'bothOk': 2, 'secondaryFail': 4.

A value that describes the divisions of the segmentable ethernet channel. For those devices that do not implement a backplane with this feature, they still need to implement this object and return a value (i.e., zero) to indicate that no divisions are enabled. The value is a sum (i.e., integer bit string). This value initially takes the value of zero, then for each division that is enabled on the channel, 2 raised to a power is added to the sum. The powers are according to the following table: Division between Power Slots 4 and 5 0 Slots 6 and 7 1 Slots 8 and 9 2 For example, a channel with no divisions enabled (i.e., not segmented) would have a value of 0. A channel with divisions between slots 6 and 7, and slots 8 and 9 enabled (i.e., having three segments) would have a value of 6 (2**1 + 2**2).

The agent will return aSegmentable(2) for the 3000N, 3000NT, 3000S, 3000SR, and any other backplanes in which Ethernet channel A can be divided into multiple segments. The value aNotSegmentable(3) indicates that the Ethernet backplane channel A cannot be segmented. For Token Ring or FDDI workgroup concentrators, or other devices in which there is no Ethernet channel, the agent will return other(1). Enumeration: 'aSegmentable': 2, 'aNotSegmentable': 3, 'other': 1.