About This Documentation (PDF and HTML)
Related Third-Party Web Site References
Introduction to Sun Server Management Agents
Sun Server Management Agents Features
Sun Server Hardware Management Agent
Sun Server Hardware SNMP Plugins
Sun Server Storage Management Agent
Sun SSM Component Manager Overview
(Linux and Solaris Operating Systems) Using Component Manager
(Linux and Solaris Operating Systems) Using Component Manager in Interactive Mode
(Linux and Solaris Operating Systems) Using Component Manager in Unattended Mode
(Windows Operating Systems) Using Component Manager
Configuring Hardware Management Agent and Hardware SNMP Plugins
Hardware Management Agent Configuration File
Configuring the Hardware Management Agent Logging Level
How to Configure the Hardware Management Agent Logging Level:
(Solaris and Linux Operating Systems) Hardware Management Agent Runtime Options
Configuring your Host Operating System's SNMP
(Solaris and Linux Operating Systems) Configuring Net-SNMP/SMA
(Windows Operating Systems) Configuring SNMP
Sun Server Hardware SNMP Plugins
Overview of Sun HW Monitoring MIB
Sun Server Product and Chassis
Sun Server Hardware Monitoring MIB
Sun Server Hardware Management Agent
Sun Server Hardware Monitor Sensor Group
Working With Management Agents
Retrieving and Setting Information Through SNMP
Troubleshooting Management Agents
General Management Agents Troubleshooting
Solaris Operating System Troubleshooting
Windows Component Manager Incorrect Parameter Error
Windows Component Manager Issues Using /I ALL
Storage Management Agent Service Running on Unsupported Platforms
Red Hat Installation Dependencies
Sun X6250 Server Module Wrong Service Processor Version Number
Gaps in sunHwMonInventoryGroup
SunHwMonInventoryTable Shows Incorrect Number of DIMMs
SunHwMonDiscreteHardDriveSensorTable Incorrect Sensors
Enterprise Field is Populated with Incorrect OID
ILOM 3.0 and Windows Server 2003 R2 Extended Data Mode Issue
Sun Blade X6450 with ILOM 2.0 and Windows Server 2003 Issue
Windows Hardware Management Agent snmpwalk on a Sensor Group Issue
Windows Hardware Management Agent SNMP Get Returns Empty String
Adaptec RAID Volumes not Reflected in ILOM CLI using Windows Storage Management Agent
Driver Errors in Windows Application Log
Ordering of Physical and Logical Disks Inconsistent Between Linux and Windows Storage Viewer
The following differences have been found between the SNMP traps sent by Hardware Management Agent and ILOM service processors:
When sunHwTrapProductName is sent from the service processor, it can be empty due to a platform bug. However if the service processor provides it, Hardware Management Agent also provides it.
In the Hardware Management Agent SNMP traps, sunHwTrapSystemIdentifier is empty when using ILOM 2.0 versions.
When sunHwTrapAssocObjectId is sent by Hardware Management Agent it is always SNMPv2-SMI::zeroDotZero, which can differ from the service processor trap.
sunHwTrapComponentName is sent with different formatting.
sunHwTrapThresholdValue and sunHwTrapSensorValue are not the same and sometimes do not provide sufficient information from Hardware Management Agent. This is due to CR 6811841.
On Sun Fire X4200 M2 servers, Hardware Management Agent sends sunHwTrap \Component OK | Error instead of sunHwTrapSlotOr \ Connector Ok | Error, which is sent by the service processor.
On some platforms the disk state information is expressed as sunHwTrapHardDriveError when sent from the service processor and as sunHwTrapHardDriveStatus when sent from Hardware Management Agent. This is due to CR 6811826.
When a power cable is unplugged from a power supply, a sunHwTrapPowerSupplyOk trap is sent. But when the power cable is plugged in to the power supply a sunHwTrapPowerSupplyError trap is sent. This is due to CR 6762982.