Troubleshooting, Changing log levels, Removing non-storage mirroring nodes – HP Storage Mirroring Software User Manual

Page 61: Chapter 7 troubleshooting -1

Advertising
background image

7 - 1

Troubleshooting

Troubleshooting Storage Mirroring Reporting Center consists of:

z

Changing log levels

z

Removing non-Storage Mirroring nodes

z

Viewing collector reports

z

Verifying Storage Mirroring server connectivity

z

Verifying WMI connectivity

The following files may need to be gathered to troubleshoot Storage Mirroring issues.

z

For install and setup information, see

C:\windows\temp\dtrc_setup.log

z

For configuration information, look for

controller.xml

in the Storage Mirroring install path,

and all .xml files in the install subfolder in the Storage Mirroring path.

The following log files should be in the log folder under the install path for Storage Mirroring:

z

analysisengine.log—Check the analysisengine log file if you are having problems with Storage

Mirroring generating alerts.

z

collector.log—This log file is written to by the Storage Mirroring Collector service. Check this log

file if you are having problems with the Storage Mirroring Collector service or with the data that

should be being gathered.

z

controller.log—The log written to by the Storage Mirroring Controller service. This process is a

critical component for system stability and should contain no errors. If the Storage Mirroring

Controller service cannot start or is crashing, then check the contents of this file for any errors.

z

listener.log—This log is written to by the Storage Mirroring Listener service that receives data

from the Storage Mirroring Collector and logs it to the database. This process is a critical

component in the data gathering process. If you are not seeing data being displayed when running

reports, check the listener log file for any errors.

z

publisher.log—This log is written to by the Storage Mirroring Reporting Center Publisher service.

Check this log if email reports are not being sent.

z

reporter.log—This log is written to by the Storage Mirroring Reporter service. If you are having

problems with reports being run in the GUI, then check this log file for any errors.

z

dtrc_gui.log

Changing log levels

By default, all processes log only errors and warnings. This may not be enough information to

troubleshoot difficult problems. You can change the log levels for the Server, Collector, and GUI to

capture additional information to help you identify any problems.
For more information about changing log levels, see

Configuring system settings

on page 3-2.

Removing non-Storage Mirroring nodes

Storage Mirroring Reporting Center is designed to monitor Storage Mirroring servers. There is no limit

set on the number of Storage Mirroring servers that can be monitored.
Storage Mirroring Reporting Center can only monitor up to 10 non-Storage Mirroring servers. If you

attempt to monitor more than 10 non-Storage Mirroring servers, the following message will appear:

“Report not generated: product monitoring more elements than licenses allow. [Number] servers

without Storage Mirroring monitored.”
To remedy this situation, you must remove some of the non-Storage Mirroring servers you are

monitoring from the navigation tree.
If you are getting host information data returned on a node but do not get any data when running

Storage Mirroring reports, ensure that Storage Mirroring is installed on the server you are monitoring.

If Storage Mirroring isn't installed, you can still gather host information from that machine; however,

you won't be able to gather data specific to Storage Mirroring.

Advertising
This manual is related to the following products: