It is most likely your binding order of your nic's. if your heartbeat nic is set as the top one and it is on a different network then the storage processors, it cant communicate and that is why you get that message.
I have seen many 2003 cluster configs in which the heartbeat did not have to be the first entry in the bind order. maybe it is different in W2008?
Ken is correct - when the top NIC is not the local LAN NIC, then Agent will be pushing up the incorrect IP address. You can force Agent to use a particular IP address by using the "agentID.txt" file - see Primus emc66921 for information about unstalling and using agentID.txt.
For other Agent related questions, also see emc254967
kenn2347
3 Apprentice
•
542 Posts
0
January 6th, 2011 06:00
It is most likely your binding order of your nic's. if your heartbeat nic is set as the top one and it is on a different network then the storage processors, it cant communicate and that is why you get that message.
I have seen many 2003 cluster configs in which the heartbeat did not have to be the first entry in the bind order. maybe it is different in W2008?
srketi
3 Posts
0
January 6th, 2011 06:00
Host agent is not reachable if the Windows firewall is enabled.
See emc239655
kelleg
4 Operator
•
4.5K Posts
0
January 6th, 2011 10:00
Ken is correct - when the top NIC is not the local LAN NIC, then Agent will be pushing up the incorrect IP address. You can force Agent to use a particular IP address by using the "agentID.txt" file - see Primus emc66921 for information about unstalling and using agentID.txt.
For other Agent related questions, also see emc254967
glen