Major errors related to Agent running on a Windows Server 2003 server node and the corrective action to be taken are explained below. In the Event viewer or the GUI window, confirm the occurrence of the errors described below.
If all access paths under multipath control have been deleted by mistake, follow the recovery procedure given below.
Restart the Windows server node.
After an access path is deleted, multipath control no longer controls the path, and the related device is not recognized.
For the respective devices deleted by mistake on the access path, execute [Reload Conf.].
Set the access path that was deleted by mistake.
Too many devices are connected to the Windows server node.
If too many devices are recognized by the Windows server node, Agent cannot perform processing within the response time, leading to a communication failure. In this event, check the connection configuration, and reduce the number of devices recognized by the Windows server node.
Access paths can be set for approximately 100 devices per one Windows server node, but the number of devices varies depending on the server node environment.
An access path from an Emulex HBA cannot be drawn.
The Topology value in a driver parameter in the registry may be incorrect.
This caused by values in the registry being reset to default values, which occurs at either of the times: when a driver is re-installed; and when a driver is automatically re-installed because of the installation a new HBA having a different model number from that of a HBA already installed in a Windows Server 2003 machine (e.g., LP9802 and LP1050).
Using the registry editor, check the driver parameters of the HBA, correct any incorrect value that you find, and then select [Reload Conf.].
For information about driver parameters, see "4.1.2 Windows server node (host)".
