Unable to Discover a UNIX Host Because of DNS or Routing Issues

If the management server is unable to discover a UNIX host because of a DNS or routing issues, you will need increase the amount of time that passes before the management server times out for that CIM Extension. By default, the management server waits 1,000 ms before it times out. It is recommended you increasing the time before the management server times out to 200000 ms (3.33 minutes), as described in the following steps. If you continue to see time out issues, you can still increase the time before the management server times out, but keep in mind that it will lengthen discovery.

To increase the time out period:

1.Select Options > Storage Essentials > Manage Product Health. Then, click Advanced in the Disk Space tree in the management server.

2.Paste the following text into the Custom Properties field. How you paste the text depends on your Web browser. If you are using Microsoft Explorer or Netscape Navigator, right-click the field and select Paste.

cimom.cxws.agency.firstwait=200000

cimom.cxws.agency.timeout=200000

where

•cimom.cxws.agency.firstwait - The firstwait property controls the amount of time required for the management server to wait after it first contacts the CIM Extension on the host before the management server attempts to proceed with a username and password. The default value is 1,000 ms. You are modifying it to wait 20,000 ms or 3.33 minutes.

•cimom.cxws.agency.timeout - The timeout property controls the allowable interval of silence before either the CIM Extension or the management server start to question whether its partner is still alive. If an entity (management server or extension) has not received a message from the other during the interval set by the timeout property, it will send an “are you there” message. If that message is not acknowledged during the interval set by the timeout property, the entity will conclude that the connection is no longer functioning. The CIM Extension will stop attempting to make a connection. When this occurs on the side of the management server, the management server will attempt to re-connect (and it will keep re-attempting until the host becomes available). The default value is 1,000 ms. You are modifying it to wait 20,000 ms or 3.33 minutes.

3.Click Save.

4.Restart the service for the management server for your changes to take effect.

While AppStorManager is restarting, users are not able to access the management server. The AppStorManager service must be running for the management server to monitor elements.

Troubleshooting the Java Plug-in

This section describes the following:

•”Java Applet Has Data from a Different Version of Management Server Software” on page 626

•”OutOfMemoryException Messages” on page 626

•”Improving Reload Performance in System Manager” on page 626

Storage Essentials 5.00.01 User Guide 625