Try opening Connectivity Status and then click on the Serve (right most) column to sort by host name. Find the paths for the host in question and and select one path and then click on the INFO button - that should give you the information about the hostname and IP address - make sure that the IP address listed matches the host's. If it does not then see Knowledgebase article emc66921 on PowerLink.

glen

I verified the info an each path is correct.

Generally there are four reasons that the hosts appear unmanaged:

1. The IP address that is registered on the array for the host is incorrect - the array can't talk to the host using the IP address

2. There is a firewall between the host and the array - if so, open port 6389

3. The Navipshere Host Agent program on the host is not working correctly or not running. Try un-installing, installing Agent again

4. The switch port configuration on the port that the array's Management Ports are connected to are set to 100/FULL - the array's Management Ports are by default set to auto/auto. Check the switch ports for the correct configuration

glen

Hi,

does the server running the agent is attached to different networks or has more than one NIC installed and configured? If so, you have to create a file called agendID.txt and save it to the agent directory.

A multihomed host machine has multiple IP addresses connected to networks; it is physically connected to multiple data links that can be on the same or different networks. When you install Navisphere Host Agent on a multihomed host, the host agent, by default, binds to the first NIC in the host. If your host is multihomed, for the host agent to successfully register with the desired CLARiiON storage system, you need to configure the host agent to bind to a specific NIC. You do this by setting up an

agentID.txt file.

Example:

host28.mydomain.com

192.111.222.3

The

agentID.txt file should contain only these two lines, without any formatting. The first line should contain the hostname and the second line should contain the IP address of the HBA/NIC port as described above. Both lines should end with a carriage return. As a result, the cursor will be on a third line but this line should not contain any text.

Jim,

I highly doubt that moving the LUNs between hosts caused this. It is most likely the communication problem with the agents already existed and moving the LUNs helped to reveal it since that action involves communication with the hosts. The Navisphere agent is not very active on the hosts once a host is masked to the array and LUNs have been assigned to the host.

Have you tried uninstalling and reinstalling the agent. I would also install the latest agent and cli supported by the FLARE code of you array. The Navisphere Agent/CLI uninstall/install is non-disruptive to the host and will not affect the LUN masking or host access to the LUNs. So this can be done during the middle of production hours without any impact to the host.

Aran

Thank you for your input - unfortunately, it did not have any affect. I have tried recycling the agent service after making this addition as well with no luck. There is a second nic on this server, but it is disconnected and only there in the event the current nic fails. Could this have been caused or have anything to do with moving luns between storage groups/possibly how they were moved?

Jim

Thank you all for your feedback - I have been able to isolate the cause to be network related. It appears some change to the configuration of the network switch is preventing network connectivity between the SAN and host servers in a specific subnet. Unfortunately, our network backbone is managed by another agency, so modifications/updates/configurations are rarely communicated to me in many instances...