Administrator's Guide

5 Monitoring and troubleshooting the messaging system
The messaging system provides several monitoring and troubleshooting options. You can access
troubleshooting alerts and solutions to maintain the health of the messaging system from the
following:
Notification alerts, which you sign up to receive during the initial configuration of the storage
solution
HP E5000 System Manager
System Management Homepage (SMH)
Hardware component LEDs
EMU CLI SHOW commands
HP and Microsoft support websites
HP Insight Remote Support software
Microsoft Systems Center Operations Manager (SCOM) and Microsoft websites
HP SIM. HP SIM 6.3 or later is required for proper messaging system/HP SIM integration.
NOTE: Integration with HP SIM is only supported using the WBEM/WMI interfaces. Do not
attempt to configure HP SIM to use the ProLiant SNMP agents, because the configuration is
untested and unsupported. The ProLiant SNMP agents are enabled on the messaging system
by default and should not be disabled as they are used for internal management functions. If
they are enabled for external client consumption, HP SIM must be configured so it does not
attempt to communicate with these agents.
If you are unable to resolve a messaging system operation issue after using the various options,
contact HP Support. You need to provide your Service Agreement ID (SAID) and your warranty
and entitlement labels. See “Obtaining the Service Agreement ID (SAID)” (page 61) and “Locating
the messaging system warranty entitlement labels” (page 62).
Using notification alerts
When you receive an alert, open the HP E5000 System Manager (described in “Using the E5000
System Manager” (page 43)) to view a high-level description of the issue. You may then choose
to open the System Management Homepage or HP SIM to obtain more detailed information.
IMPORTANT: While the notification alerts report issues as they arise, it is still important to monitor
the messaging system regularly to ensure optimal operation.
For more information on receiving notification alerts, see “Using notification alerts” (page 37).
Examples of error messages
Table 1 (page 37) lists examples of possible error messages and describes the needed action to
resolve the issue.
Table 1 Examples of possible error messages
ResolutionIssueMessage appears
Enter the correct Exchange license key.Entered an incorrect Exchange license
key
Not a valid license
Enter the correct Administrator
password.
Adding the wrong information for a
domain controller
You cannot reach the domain
controller
Using notification alerts 37