This post is more than 5 years old
9 Posts
0
1777
VNX5400 host disappeared
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).
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@10.12.0.51
User system@10.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.
nokogerra
9 Posts
0
January 16th, 2018 20:00
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:
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:
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.
SteveK821
2 Intern
2 Intern
•
137 Posts
0
January 16th, 2018 07:00
The agent.config file on the host is case sensitive. "user" should be all in lower-case, not "User". Found a couple of KB articles about this (326060 and 485372)
Does that host have more than one network adapter?
If so you can try creating a file in the navisphere agent folder (same folder as agent.config).
Filename: agentID.txt
In this text file put the FQDN of the host on the first line. On the second line put the IP Address (the one it should use for talking to the VNX).
Rainer_EMC
8.6K Posts
0
January 17th, 2018 03:00
thanks for the feedback
its really useful for the community when users not just ask questions and leave but return to tell how their issue was solved