Hello, Stephen. Thank you for your reply. agent.config file was created by host agent installer, so letter "U" was capitalized by the installer. However, I had change it and now agent.config looks like this: clarDescr clarContact poll 60 baud 9600 eventlog 2048 user system[NAME].12.0.51 user system[NAME].12.0.52  This host have 2 NICs indeed, but they are bonded by LACP, so there is only one logical NIC and only one IP address. But I had created the file "agentID.txt" and put it into the host agent folder. agentID.txt content looks like this: DirectSANProxy.uitisk.local 10.12.0.95 Now I guess the problem was in the firewall. If it is disabled the host looks OK in Unisphere. Can't find firewall requirements for unisphere host agent though. update: wireshark says that TCP 6389 needs to be open, but in windows you can actually make firewall rules for specific program, not fot L4 port. Now the problem is solved.
Good day. VNX 5400; 05.33.008.5.119, Windows 2012 R2 with qlogic hba. I got some problem with Windows host: sometimes it is not displayed in the host list in the Unisphere. However there are no real problem with storage access, this Winddows host works fine as veeam backup direct SAN access proxy (backing up VMs directly from VMFS volumes that reside on VNX LUNs). [IMAGE] Unisphere host agent is installed on this Windows host (7.33.9.1.84), here is the config: clarDescr  clarContact poll 60 baud 9600 eventlog 2048 User system[NAME].12.0.51 User system[NAME].12.0.52 10.12.0.51 and 10.12.0.52 are the real IPs of VNX SPs.  I`ve tried to launch the agent and to reboot this host, but it seems that the problem occures randomly.
VNX5400 host disappeared