Enterprise Volume Manager (Multi-OS) Version 2.0D Network Administration Guide

Enterprise Volume Manager (Multi-OS) Network Administration Guide 6–7
Troubleshooting
EVM GUI Takes a Long Time to Load
The EVM GUI makes extensive use of Java applets. When a new Web browser session
is established, applets may take a minute or more to download, depending on current
network conditions. After the applets are downloaded, they remain stored in the Web
browser cache until a new browser session is established.
30-Minute Spawn Process Timeout
By default, the EVM host agent is configured to time out and report an error if a
process spawned by a suspend, resume, or launch operation does not complete within
30 minutes. In some cases, the spawned process may require more than 30 minutes to
complete. For this situation, do the following:
1. Modify the PIPE_READ_TIMEOUT value in the sb.ini file, on the appropriate
EVM host agent computer, to reflect the desired value (in seconds).
2. Restart the EVM service on the EVM host agent computer to make the changes
take effect.
Accuracy of Step-Percent-Complete Bar
Sometimes the step-percent-complete bar on the Job Monitor page may drop from a
larger percentage to a smaller one. This does not necessarily indicate a problem.
For example, a clone normalization step may reach 100% and then drop down when
two jobs that normalize the same unit are both running. Because EVM displays the
average percent complete of all mirror members, the percent-complete bar in one job
may drop to a smaller percentage when the second job begins its normalization.
EVM Host Agent Connectivity Troubleshooting
The bidirectional communication between the EVM server and the individual EVM
host agent computers is accomplished through an encrypted TCP socket interface. For
this communication interface to work properly, the following must be true:
• Each EVM host agent computer must be able to resolve the network name of the
Management Appliance (EVM server).
• The Management Appliance (EVM server) must be able to resolve the network
names for each of the EVM host agent computers.