Skip Navigation Links | |
Exit Print View | |
Solaris Volume Manager Administration Guide Oracle Solaris 10 1/13 Information Library |
1. Getting Started With Solaris Volume Manager
2. Storage Management Concepts
3. Solaris Volume Manager Overview
4. Solaris Volume Manager for Sun Cluster (Overview)
5. Configuring and Using Solaris Volume Manager (Scenario)
8. RAID-0 (Stripe and Concatenation) Volumes (Overview)
9. RAID-0 (Stripe and Concatenation) Volumes (Tasks)
10. RAID-1 (Mirror) Volumes (Overview)
11. RAID-1 (Mirror) Volumes (Tasks)
12. Soft Partitions (Overview)
16. Hot Spare Pools (Overview)
20. Maintaining Solaris Volume Manager (Tasks)
21. Best Practices for Solaris Volume Manager
22. Top-Down Volume Creation (Overview)
23. Top-Down Volume Creation (Tasks)
24. Monitoring and Error Reporting (Tasks)
Solaris Volume Manager Monitoring and Reporting (Task Map)
Configuring the mdmonitord Command for Periodic Error Checking
How to Configure the mdmonitord Command for Periodic Error Checking
Solaris Volume Manager SNMP Agents Overview
Configuring the Solaris Volume Manager SNMP Agents
How to Configure the Solaris Volume Manager SNMP Agents
Monitoring Solaris Volume Manager With a cron Job
How to Automate Checking for Errors in Volumes
25. Troubleshooting Solaris Volume Manager (Tasks)
A. Important Solaris Volume Manager Files
B. Solaris Volume Manager Quick Reference
The Solaris Volume Manager SNMP agent does not issue traps for all of the Solaris Volume Manager problems that system administrators need to be aware oft. Specifically, the agent issues traps only in the following instances:
A RAID-1 or RAID-5 subcomponent goes into a “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 problems, 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. However, other SNMP agents must issue traps for those errors to be reported to a monitoring console.