Submit comments about this document at: http://www.sun.com/hwdocs/feedback
Copyright 2004Sun Microsystems,Inc., 4150 NetworkCircle, SantaClara, California95054, U.S.A. Allrights reserved.
Sun Microsystems,Inc. hasintellectual propertyrights relating to technology thatis described in this document.In particular, and without
limitation, theseintellectual propertyrights may includeone ormore ofthe U.S. patentslisted athttp://www.sun.com/patentsand one or
more additionalpatents orpending patent applicationsin theU.S. and inother countries.
This documentand the product to whichit pertainsare distributedunder licenses restricting theiruse, copying, distribution, and
decompilation. Nopart of the product orof thisdocument may bereproduced in any formby any means without priorwritten authorization of
Sun andits licensors, if any.
Third-party software, including font technology,is copyrighted and licensed fromSun suppliers.
Parts ofthe productmay be derivedfrom BerkeleyBSD systems,licensed from the University ofCalifornia. UNIX is a registered trademark in
the U.S.and in other countries, exclusivelylicensed throughX/Open Company, Ltd.
Sun, Sun Microsystems,the Sunlogo, AnswerBook2, docs.sun.com,Sun Fire,OpenBoot, Netra,and Solaris are trademarksor registered
trademarks ofSun Microsystems,Inc. in theU.S. andin other countries.
All SPARC trademarks are used underlicense andare trademarksor registeredtrademarks of SPARC International,Inc. in theU.S. andin other
countries. Productsbearing SPARC trademarks are based uponan architecturedeveloped by SunMicrosystems, Inc.
The OPENLOOK and Sun™ Graphical UserInterface was developed by SunMicrosystems, Inc.for its users and licensees. Sun acknowledges
the pioneeringefforts ofXerox inresearching anddeveloping the conceptof visualor graphical userinterfaces forthe computer industry. Sun
holds anon-exclusive license from Xeroxto the Xerox GraphicalUser Interface, which license alsocovers Sun’s licensees who implementOPEN
LOOK GUIsand otherwise comply with Sun’swritten license agreements.
U.S. GovernmentRights—Commercial use.Government users are subject tothe Sun Microsystems, Inc.standard licenseagreement and
applicable provisionsof theFAR and its supplements.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANYIMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2004Sun Microsystems,Inc., 4150 NetworkCircle, SantaClara, Californie95054, Etats-Unis. Tous droitsréservés.
Sun Microsystems,Inc. ales droits de propriété intellectuels relatants àla technologiequi est décritdans cedocument. En particulier, et sans la
limitation, cesdroits depropriété intellectuels peuvent inclure un ou plusdes brevetsaméricains énumérés àhttp://www.sun.com/patentset
un oules brevetsplus supplémentaires ou les applicationsde breveten attente dans les Etats-Uniset dans les autres pays.
Ce produitou documentest protégépar un copyrightet distribuéavec des licencesqui enrestreignent l’utilisation,la copie, ladistribution, etla
décompilation. Aucunepartie de ce produit oudocument nepeut êtrereproduite sousaucune forme, parquelque moyenque ce soit,sans
l’autorisation préalableet écrite de Sun etde ses bailleurs de licence,s’il y ena.
Le logicieldétenu par des tiers, etqui comprendla technologie relative aux policesde caractères, est protégé parun copyrightet licencié pardes
fournisseurs deSun.
Des partiesde ce produit pourront être dérivées des systèmes BerkeleyBSD licenciés par l’Université deCalifornie. UNIX est une marque
déposée auxEtats-Unis et dans d’autres payset licenciéeexclusivement par X/OpenCompany, Ltd.
Sun, SunMicrosystems, lelogo Sun, AnswerBook2,docs.sun.com, SunFire, OpenBoot,Netra, et Solarissont desmarques de fabrique ou des
marques déposéesde SunMicrosystems, Inc.aux Etats-Unis etdans d’autrespays.
Toutes lesmarques SPARC sont utiliséessous licenceet sont desmarques defabrique oudes marques déposées de SPARC International, Inc.
aux Etats-Uniset dans d’autres pays. Lesproduits portantles marquesSPARCsont basés sur une architecture développée parSun
Microsystems, Inc.
L’interfaced’utilisation graphiqueOPEN LOOK etSun™ aété développée parSun Microsystems,Inc. pourses utilisateurs etlicenciés. Sun
reconnaît lesefforts depionniers de Xerox pour la recherche et le développementdu concept des interfaces d’utilisationvisuelle ougraphique
pour l’industriede l’informatique. Sun détient unelicense non exclusive de Xeroxsur l’interfaced’utilisation graphique Xerox, cette licence
couvrant égalementles licenciées de Sun quimettent en place l’interface d’utilisation graphique OPEN LOOK etqui enoutre se conforment
aux licencesécrites de Sun.
LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES
OU TACITES SONT FORMELLEMENTEXCLUES, DANSLA MESURE AUTORISEE PAR LA LOIAPPLICABLE, Y COMPRIS NOTAMMENT
TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A
L’ABSENCE DE CONTREFAÇON.
Contents
Sun SNMP Management Agent Addendum for the Netra 440 Server1
Sun SNMP Management Agent2
Netra 440 Server SNMP Containment Model2
Component and Indicator Identification10
Fans and Fan Trays14
Fan Failures14
Detecting Fan Status17
Power Supplies17
Power Supply Failures18
Detecting Power Supply Status21
Dry Contact Alarm Relays and LED Indicators21
Alarm State Changes22
i
iiSun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
Sun SNMP Management Agent
Addendum for the Netra 440 Server
This document describes how the Netra™ 440 server fans, power supplies, and LED
indicators are represented in the Sun™ Simple Network Management Protocol
(SNMP) Agent for Sun Fire™ and Netra Systems. This document contains the
following sections:
■ “Sun SNMP Management Agent” on page 2
■ “Netra 440 Server SNMP Containment Model” on page 2
■ “Component and Indicator Identification” on page 10
■ “Fans and Fan Trays” on page 14
■ “Power Supplies” on page 17
■ “Dry Contact Alarm Relays and LED Indicators” on page 21
Note – For instructions on installing and using the Sun SNMP Management Agent,
refer to the Sun SNMP Management Agent for Sun Fire and Netra Systems (817-2559-xx)
manual. See “Sun SNMP Management Agent” on page 2 for more information.
1
Sun SNMP Management Agent
The Sun SNMP Management Agent for Sun Fire and Netra Systems provides the
management of supported systems using the Simple Network Management Protocol
(SNMP). Using the Sun SNMP Management Agent, you can monitor inventory,
configuration, and service indicators, as well as environmental and fault reports.
You can download the Sun SNMP Management Agent for Sun Fire and Netra
Systems software and documentation at the following web site:
For instructions on installing and configuring the software, refer to the Sun SNMP
Management Agent for Sun Fire and Netra Systems (817-2559-xx). The SNMP
management agent manual contains a detailed overview of the agent software,
including an introduction to the SNMP environment and a description of how the
agent models hardware platforms using the Sun Platform SNMP model (SunPSM).
The manual also describes how the SNMP interface presents managed objects and
their relationships using the ENTITY-MIB and SUN-PLATFORM-MIB management
information bases (MIB).
This document supplements the Sun SNMP Management Agent for Sun Fire and NetraSystems manual by documenting how the agent represents the Netra 440 server fans,
power supplies, and certain LED indicators. This document provides Netra 440
server-specific information only. For complete descriptions of the SNMP agent
terminology, management models, and trap properties, refer to the Sun SNMPManagement Agent for Sun Fire and Netra Systems manual.
For additional information about the Netra 440 server, refer to the server’s
documentation at the following web site:
TABLE 1 presents an example of how the Sun SNMP agent models the Netra 440
server component hierarchy. Because this component hierarchy may vary depending
on your server and the SNMP agent software version, query the SNMP agent to
identify your server’s hierarchy. To locate these server components, see the figures in
“Component and Indicator Identification” on page 10.
2Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
TABLE 1Netra 440 Server Containment Model (Hierarchy)
Model DescriptionFor Location, See:
Netra 440 Chassis
➥ Alarm Board
Critical Alarm Relay
Major Alarm Relay
Minor Alarm Relay
User Alarm Relay
➥ System Board
OpenBoot PROM
➥ Battery
Battery Voltage Monitor
➥ CPU/Memory Slot 0 (far left - viewed from front)FIGURE 4 – item 2
➥ System Configuration Card ReaderFIGURE 1 – item 4
➥ System Configuration CardFIGURE 1 – item 4
➥ DVD Drive BayFIGURE 1 – item 6
➥ DVD DriveFIGURE 1 – item 6
➥ Power Distribution Module BayFIGURE 1 – item 7
➥ Power Distribution ModuleFIGURE 1 – item 7
Ethernet Port 0 (left - viewed from rear)
Ethernet Port 1 (right - viewed from rear)
* The SNMP model mayshow frequency valuesfor slots 1- 4 that are differentfrom those shownin this table;if that isthe case, ignore
the frequency values shown inthe SNMP model, and use the frequencyvalues shown in this table and theregular Netra 440 server
labels and documents instead. Refer to the Netra 440 Server Release Notes for more information.
† While the service-required indicator is represented in the containment model, it is not supported.
FIGURE 3 – item 19
FIGURE 3 – item 18
Sun SNMP Management Agent Addendum for the Netra 440 Server9
Component and Indicator Identification
The following figures show the location of the Netra 440 server components. TABLE 1
lists of how the agent models these components in an SNMP hierarchy.
1
23
4
8
9
10
11
7
FIGURE 1Front Panel Indicators and Components
Indicators:
1. System locator
2. System service-required
3. System active
5
6
SCC
4. System configuration card reader
5. System control keyswitch
6. DVD drive bay/DVD drive
7. Power distribution module bay
8. Critical alarm
9. Major alarm
10. Minor alarm
11. User alarm
10Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
9
8
7
6
5
10
11
12
13
4
3
2
1
SCC
Components and indicators:
1. Hard disk drive (HDD) 0
2. Fan tray 0
3. HDD 1
4. HDD0 okay to remove
5. Fan tray 0 service required
6. Fan tray 0 active
7. HDD1 okay to remove
8. Fan tray 1 service required
9. Fan tray 1 active
FIGURE 2Hard Disk Drive and Fan Tray Components and Indicators
14
15
16
17
10. HDD2 okay to remove
11. Fan tray 2 service required
12. Fan tray 2 active
13. HDD3 okay to remove
14. Fan tray 1
15. HDD 2
16. Fan tray 2
17. HDD 3
Sun SNMP Management Agent Addendum for the Netra 440 Server11
25
1
23
4
6
5
7
8
910
11
12
13
14
24
23
22
21
20
Components and indicators:
1. System locator
2. System service-required
3. System active
4. Network management port
5. Serial management port
6. PCI card slot 5
7. PCI card slot 4
8. PCI card slot 3
9. PCI card slot 2
10. PCI card slot 1
11. PCI card slot 0
12. Power supply (PS) active
13. PS service-required
14. PS okay-to-remove
FIGURE 3Rear Panel Components and Indicators
1819
17
15. PS 0
16. PS 1
17. SCSI port
18. NET 1 ethernet port
19. NET 0 ethernet port
20. PS 2
21. USB 2 and 3 ports
22. USB 0 and 1 ports
23. PS 3
24. Serial port
25. Alarm port
1516
12Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
1
FIGURE 4Internal Components
2
3
4
Internal components:
1. Fan Tray 3/Fan 3
2. CPU/memory module 0
5
3. CPU/memory module 1
4. CPU/memory module 2
5. CPU/memory module 3
6. SCSI disk backplane
6
Memory banks and DIMMs
1. Memory bank 0 DIMM 0
2. Memory bank 0 DIMM 1
3. Memory bank 1 DIMM 0
4. Memory bank 1 DIMM 1
5. Memory bank 0
4123
6. Memory bank 1
5
FIGURE 5Memory Banks and DIMMs
Sun SNMP Management Agent Addendum for the Netra 440 Server13
6
Fans and Fan Trays
The Netra 440 server fans in the fan trays are identified in the ENTITYMIB::entPhysicalTable by the entPhysicalDescr of Fan number, where number is a
number in the range from 0 to 3. The fans are represented in the following tables that
extend the entPhysicalTable:
■ SUN-PLATFORM-MIB::sunPlatEquipmentTable
■ SUN-PLATFORM-MIB::sunPlatFanTable
Note – The fans in fan trays 0-2 have certain sensors that give status and failure
information, whereas the fan in fan tray 3 does not; therefore, the information in the
remainder of this section will apply only to the fans in fan trays 0-2, not the fan in
fan tray 3. Also, if the fan in fan tray 3 fails, the Netra 440 server automatically shuts
down and no SNMP traps are generated.
The fans in fan trays 0-2 contain a tachometer used to indicate the current speed of
the fan expressed in revolutions per minute (RPM). The tachometers are identified
by their entPhysicalDescr of Fan number Tachometer, where number is a number in
the range from 0 to 2 corresponding to the fan tray being monitored. The fan
tachometers are represented in the following tables that extend the entPhysicalTable:
■ SUN-PLATFORM-MIB::sunPlatEquipmentTable
■ SUN-PLATFORM-MIB::sunPlatSensorTable
■ SUN-PLATFORM-MIB::sunPlatNumericSensorTable
Fan Failures
If the speed of a fan falls below the threshold indicated by its tachometer's
sunPlatNumericSensorLowerThresholdNonCritical value, the fan is considered to
have failed and the following will occur:
■ The sunPlatEquipmentOperationalState value for the fan will change from
enabled(2) to disabled(1) and a sunPlatStateChange trap will be generated
with the form shown in
■ A sunPlatEnvironmentalAlarm trap with a sunPlatNotificationPerceivedSeverity
value of warning(5) will be generated for the fan with the form shown in
TABLE 3.
■ The sunPlatEquipmentAlarmStatus value for the fan will change from
cleared(7) to warning(5) and a sunPlatAttributeChangeInteger trap will be
generated with the form shown in
14Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
TABLE 2.
TABLE 4.
■ The sunPlatAlarmState values for the status LEDs will change and
sunPlatAttributeChangeInteger traps will be generated with the form shown in
TABLE 5.
If the fan recovers from the failure, the following changes will occur:
■ The sunPlatEquipmentOperationalState value for the fan will change from
disabled(1) to enabled(2) and a sunPlatStateChange trap will be generated
with the form shown in
■ A sunPlatEnvironmentalAlarm trap with a sunPlatNotificationPerceivedSeverity
TABLE 2.
value of cleared(6) will be generated for the fan with the form shown in
TABLE 3.
■ The sunPlatEquipmentAlarmStatus value for the fan will change from
warning(5) to cleared(7) and a sunPlatAttributeChangeInteger trap will be
generated with the form shown in
■ The sunPlatAlarmState values for the status LEDs will change and
TABLE 4.
sunPlatAttributeChangeInteger traps will be generated with the form shown in
TABLE 5.
TABLE 2sunPlatStateChange Trap for a Fan Failure or Recovery
* LED instance indicates the row in the entPhysicalTable associated with the LED.
16Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
Detecting Fan Status
You can detect fan status using the following mechanisms:
■ Polling sunPlatNumericSensorCurrent and
sunPlatNumericSensorLowerThresholdNonCritical for the fan's tachometer and
comparing their values.
■ Polling the sunPlatEquipmentOperationalState of the fan.
■ Receiving a sunPlatStateChange trap corresponding to the change of the
sunPlatEquipmentOperationalState of the fan.
■ Receiving a sunPlatEnvironmentalAlarm trap with a
sunPlatNotificationProbableCause of coolingFanFailure(107).
Power Supplies
The power supplies are identified in the ENTITY-MIB::entPhysicalTable by the
entPhysicalDescr of Power Supply number where number is 0, 1 2 or 3. The power
supplies are represented in the SUN-PLATFORM-MIB::sunPlatEquipmentTable.
Each power supply contains the following sensors:
■ Power Inlet Presence Monitor
■ Fan Under-Speed Fault Monitor
■ Over-Voltage Fault Monitor
■ Under-Voltage Fault Monitor
■ Over-Temperature Fault Monitor
■ Over-Current Fault Monitor
These sensors are represented in the following tables:
■ SUN-PLATFORM-MIB::sunPlatEquipmentTable
■ SUN-PLATFORM-MIB::sunPlatSensorTable
■ SUN-PLATFORM-MIB::sunPlatBinarySensorTable
Sun SNMP Management Agent Addendum for the Netra 440 Server17
Power Supply Failures
If any of the power supply sensors detect a fault the following changes will occur:
■ The sunPlatBinarySensorCurrent value for the sensor that detected the fault will
change from true(1) to false(2) and a sunPlatAttributeChangeInteger trap
will be generated with the form shown in
■ The sunPlatEquipmentOperationalState for the power supply will change from
enabled(2) to disabled(1) and a sunPlatStateChange trap will be generated
with the form shown in
■ A sunPlatEquipmentAlarm trap for the power supply will be generated with the
form shown in
■ The sunPlatEquipmentAlarmStatus value for the power supply will change from
TABLE 8.
TABLE 7.
cleared(7) to major(2) and a sunPlatAttributeChangeInteger trap will be
generated with the form shown in
■ The sunPlatAlarmState values for the status LEDs will change and
TABLE 9.
sunPlatAttributeChangeInteger traps will be generated with the form shown in
TABLE 10.
Recovery from the power supply fault will result in the following changes:
■ The sunPlatBinarySensorCurrent value for the sensor that detected the fault will
change from false(2) to true(1) and a sunPlatAttributeChangeInteger trap
will be generated with the form shown in
■ The sunPlatEquipmentOperationalState for the power supply will change from
disabled(1) to enabled(2) and a sunPlatStateChange trap will be generated
with the form shown in
■ A sunPlatEquipmentAlarm trap with a sunPlatNotificationPerceivedSeverity
TABLE 7.
value of cleared(6) will be generated for the power supply with the form
shown in
■ The sunPlatEquipmentAlarmStatus value for the power supply will change from
TABLE 8.
major(2) to cleared(7) and a sunPlatAttributeChangeInteger trap will be
generated with the form shown in
■ The sunPlatAlarmState values for the status LEDs will change and
TABLE 9.
sunPlatAttributeChangeInteger traps will be generated with the form shown in
TABLE 10.
TABLE 6.
TABLE 6.
18Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
TABLE 6sunPlatAttributeChangeInteger Trap for a Power Supply Sensor
* LED instance indicates the row in the entPhysicalTable associated with the LED.
20Sun SNMP Management Agent Addendum for the Netra 440 Server • April 2004
Detecting Power Supply Status
You can use the following mechanisms to detect power supply status:
■ Poll the value of sunPlatBinarySensorCurrent for each of the power supply
sensors.
■ Poll the value of sunPlatEquipmentOperationalState for the power supply.
■ Receiving a sunPlatAttributeChangeInteger trap corresponding to a change in the
sunPlatBinarySensorCurrent value for one of the power supply sensors.
■ Receiving a sunPlatStateChange trap corresponding to a change in the
sunPlatEquipmentOperationalState for the power supply.
■ Receiving a sunPlatEquipmentAlarm trap with a
sunPlatNotificationProbableCause value of powerProblem(58).
Dry Contact Alarm Relays and LED
Indicators
The Netra 440 server has four dry contact alarm relays and four corresponding LED
indicators. The alarm relays are identified in the ENTITY-MIB::entPhysicalTable by
the following entPhysicalDescr values:
■ Critical Alarm Relay
■ Major Alarm Relay
■ Minor Alarm Relay
■ User Alarm Relay
The alarm LED indicators are identified in the ENTITY-MIB::entPhysicalTable by the
following entPhysicalDescr values:
■ Critical Alarm Indicator (front)
■ Major Alarm Indicator (front)
■ Minor Alarm Indicator (front)
■ User Alarm Indicator (front)
The alarm relays and the alarm LED indicators are represented in the
SUN-PLATFORM-MIB::sunPlatAlarmTable which extends the
ENTITY-MIB::entPhysicalTable.
Sun SNMP Management Agent Addendum for the Netra 440 Server21
Alarm State Changes
The alarm relay state cannot be changed using SNMP set commands. However, the
alarm relay state can be changed using the Sun Advanced Lights Out Manager
(ALOM) setalarm command. For more information about ALOM commands, refer
to the Sun Advanced Lights Out Manager Software User's Guide for the Netra 440 Server
(817-5481-xx).
The alarm relay states can also be changed using the alarm relay output application
programming interface (API). For information about this API, refer to the Netra 440Server System Administration Guide (817-3884-xx).
If one of the alarm relays changes its state, the sunPlatAlarmState values associated
with the relay and its corresponding indicator change state, and
sunPlatAttributeChangeInteger traps will be generated in the format shown in
TABLE 11.
TABLE 11 sunPlatAttributeChangeInteger Trap for a Change in the sunPlatAlarmState of an Alarm Relay