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
Limitations of the Solaris Volume Manager SNMP Agent
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 agents is not enabled by default. Use the following procedure to enable SNMP traps.
Whenever you upgrade your Solaris operating system, you will probably need to edit the/etc/snmp/conf/enterprises.oid file and append the line in Step 6 again, then restart the Solaris Enterprise Agents server.
After you have completed this procedure, your system will issue SNMP traps to the host or hosts that you specified. You will need to use an appropriate SNMP monitor, such as Solstice Enterprise Agents software, to view the traps as they are issued.
Set the mdmonitord command to probe your system regularly to help ensure that you receive traps if problems arise. See Configuring the mdmonitord Command for Periodic Error Checking. Also, refer to Monitoring Solaris Volume Manager With a cron Job for additional error-checking options.
# mv /etc/snmp/conf/mdlogd.rsrc- /etc/snmp/conf/mdlogd.rsrc
trap = { { trap-community = SNMP-trap hosts = corsair { enterprise = "Solaris Volume Manager" trap-num = 1, 2, 3 }
Change the line that contains hosts = corsair to specify the host name that you want to receive Solaris Volume Manager SNMP traps. For example, to send SNMP traps to lexicon, you would change the line to hosts = lexicon. If you want to include multiple hosts, provide a comma-delimited list of host names, as in hosts = lexicon, idiom.
Find the block that begins with trap = and add the same list of hosts that you added in the previous step. This section might be commented out with #'s. If so, you must remove the # at the beginning of the required lines in this section. Additional lines in the trap section are also commented out. However, you can leave those lines alone or delete them for clarity. After uncommenting the required lines and updating the hosts line, this section could look similar to the following:
################### # trap parameters # ################### trap = { { trap-community = SNMP-trap hosts =lexicon { enterprise = "sun" trap-num = 0, 1, 2-5, 6-16 } # { # enterprise = "3Com" # trap-num = 4 # } # { # enterprise = "snmp" # trap-num = 0, 2, 5 # } # } # { # trap-community = jerry-trap # hosts = jerry, nanak, hubble # { # enterprise = "sun" # trap-num = 1, 3 # } # { # enterprise = "snmp" # trap-num = 1-3 # } } }
Note - Make sure that you have the same number of opening and closing brackets in the /etc/snmp/conf/snmpdx.acl file.
trap-community = SNMP-trap hosts = lexicon { enterprise = "sun" trap-num = 0, 1, 2-5, 6-16 } { enterprise = "Solaris Volume Manager" trap-num = 1, 2, 3 }
Note that the added four lines are placed immediately after the enterprise = “sun” block.
"Solaris Volume Manager" "1.3.6.1.4.1.42.104"
# /etc/init.d/init.snmpdx stop # /etc/init.d/init.snmpdx start