Host agent not reachable can be a number of things - Windows firewall - open port 6389, multiple NICs - Agent wants to use the first bound NIC - see Primus emc208222 and emc234729  Symptom    Windows 2008 host shows as  unreachable/unmanaged from Navisphere Manager GUI.  Cause    Fix  Follow these steps:  Note: This will require downtime if host is in  production!  You can use a different method found in emc66921 - you create a text file called agentID.txt and put the name and IP address to force Agent to use what is in this file.  Be careful about the name of the file, in Windows 2003 you name the file  agentID.txt, in Windows 2008, name the file agentID and save as file type "Text"  otherwise the filename becomes agentID.txt.txt and will not worik.  glen
Hi  I'm trying to set up host agent on Windows Server 2008 R2 for connection to CX4, but after installation and basic configuration such as adding privileged user, agent logs in system event monitor the following message: "No  entries in the device list. This is normal if the host is attached only to  FC4700 arrays.". What is the "device list" and how can I add some devices to it?.. I've seen no information about it in installation and administration guides... Also agent changed registered host name at CLARiiON side
Windows Host agent device list definition desired