Major errors related to Agent running on a Windows 2000 and 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.
"Refresh" the GUI window. The monitoring status of [HOST Property] in the Server node view of the GUI window then becomes normal.
Set the access path that was deleted by mistake.
Communication with Agent is disabled when an access path is connected.
Depending on the particular system environment, Agent may not be able to communicate when an access path is set in the Windows 2000 environment. This is because the simultaneous operation of the access path connection and the plug&play function of Windows 2000 places a temporary heavy load on the system. In such cases, select [Refresh] in the GUI window.
If communication remains disabled, the problem described in Item 3 may have occurred. See Item 3 below.
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.
Anti-virus software "Real Time Scan" is operated
If an anti-virus program performs a real-time scan on a Windows server node, it is possible that the server cannot be detected or that "communication disabled" is displayed. It is because file access processing by agent takes more time than usual and it leads to timeout. Change the setting value of SNMP_HCM_TIMEOUT of sanma.conf to higher value on the side of manager to be able to detect and display the applicable server.
See, "C.2 sanma.conf Parameter" for path of sanma.conf and the procedure for reflecting it.
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 2000 or 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 [Refresh].
For information about driver parameters, see "4.1.2 Windows server node (host)".
