Limitations of the Solaris Volume Manager SNMP Agent

The Solaris Volume Manager SNMP agent has certain limitations, and will not issue traps for all Solaris Volume Manager problems that system administrators will likely need to know about. Specifically, the agent issues traps only in the following instances:

• A RAID 1 or RAID 5 subcomponent goes into “needs maintenance” state

• A hot spare is swapped into service

• A hot spare starts to resynchronize

• A hot spare completes resynchronization

• A mirror is taken offline

• A disk set is taken by another host and the current host panics

Many problematic situations, such as an unavailable disk with RAID 0 volumes or soft partitions on it, do not result in SNMP traps, even when reads and writes to the device are attempted. SCSI or IDE errors are generally reported in these cases, but other SNMP agents must issue traps for those errors to be reported to a monitoring console.