Mike,
Windows 2008 is better than 2003 so that means everything is harder to find and more difficult to configure

The Advanced menu is still there, you just have to unhide it first. Go to Network and Sharing Center, and select Manage Network Connections on the left. Click on the Organize drop down box, select Layout and then select Menu Bar. Then the usual menu list appears and you can go into Advanced and adjust your binding order as needed.

This may not resolve the problem though. With Windows 2008 I have found the binding order does not always resolve the issue and that the firewall can interfere the naviagent. First try creating an agentID.txt file in the Navisphere Agent (with all the usual parameters) directory and restart the Navisphere Agent service. If that doesn't resolve it disable the firewall temporarily and see if that resolves it. If that resolves it them check out the firewall rules for the naviagent service.

Aran

No, the agentID.txt file is created in the Navisphere directory. If the Navisphere Agent service finds the file on startup, it uses the host name and IP address parameters in the file for regisitering with the array.

So just create a text file in the Navisphere Agent directory and name it agentID.txt. The format of the file is:

Line 1: fqdn of host
Line 2: ip address of host

Example:
host1.domain.com
10.1.2.3

Restart Navisphere Agent after the creation of the file.

Well you got me to the advanced settings but you were right that wasnt it. You mention an agentID.txt file? Do you mean the agent.config file?

Windows Firewall is off.

Thanks,

Mike

It's not weird, it is normal for 2008. I have experienced the same thing with just about every 2008 server in our environment.

Also disabling UAC is one of the first things I do as that tends to cause problems with some installed agents.

Ok I will give that a try. The weird thing is that Naviagent registered with the array once before but now its Unmanaged. I dont know why it would register with the array and then become unmanaged. I installed Naviagent today so there hasnt been any changes really to the host itself.

Thanks,

Mike

Hi Guys,

I have faced the same problem. I did the order binding for the networks and also I have created the agentID file under the Naviagent directory. It became managed for few minutes then back to Big U on the hosts.

best regards

osama

I've found that the problem is with a new adapter called "Microsoft Failover Cluster Virtual Adaper" - for some reason this has a higher priority than the other NIC's -  do an ipconfig /all - you should see it there. I have seen this as the IP address for the the two hosts in a cluster. Then do a netstat -rn - the Interface List will list all the adapters - there is a number in the left most column - that is suppose to indicate the priority for each NIC - in Windows 2008 the lowest number is suppose to be the first bound NIC - which Agent uses to communication with the Clariion. Note that the Failover NIC is higher than the NIC you chose in Advanced Settings.

The agentID.txt is suppose to override this and force Agent to use the address you put into agentID.txt - for some reason it does not appear to do this.

What version of Agent are you using? If using version 6.29 try 6.28 and see if that works.

I've also seen that when you shutdown one of the hosts (for a two node cluster) that the IP address on the remaining host will suddenly start displaying the correct IP address in Navisphere - when the second host is started, it reverts back to the Failover NIC IP address - these seem to be in the 169.254.1.x range.

glen

It was some firewall issue, it is now working fine.

thanx for all

Can you provide more detailed information on what you needed to do to fix the problem?

What Firewall - Windows or external? What about the Microsoft Failover Cluster Virtual Adapter - did this cause you any issues?

Did you need to set the binding order or did you use the agentID.txt?

Any information would be greatly appreciated.

glen

I did set the binding oreder for the local networks and create the agentID file under the naviagent directory.

Also there was a firewall on the windows hosts it self, so I opened the port 6389 for naviagent at the local firewall. After that the hosts appears with normal view without any problem.

osama