Configure Naviagent to use specific NIC

taken from Primus - emc70909

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The agentID.txt file can be used to specify what IP address is used for the host. Create a file with the following:

1st line Fully-qualified host name
2nd line IP address to be used

Example:
pss22102. .com
10.14.9.102

Note: The IP address in this file can be any IP address. It does not have to be an IP address that is actually being used by the host so care should be taken to ensure that the address is accurate.

The location of the file can be set using the environment variable EV_AGENTID_DIRECTORY. Otherwise, the file will be assumed to be in the / directory.

For the file to take effect, remove the old HostIdFile.txt file and then stop and start the Agent:

mv /etc/log/HostIdFile.txt /etc/log/HostIdFile.txt.o

For HP-UX:

/sbin/init.d/agent stop
/sbin/init.d/agent start

For AIX:

rc.agent stop
rc.agent start

For Solaris:

/etc/init.d/agent stop
/etc/init.d/agent start

To verify that Navisphere Agent has picked up the new IP address, look at the contents of the /etc/log/HostIdFile.txt file and compare it to the original contents in the /etc/log/HostIdFile.txt.o file

For VMWARE ESX Server 2.5.0 and later follow the procedure below. Before installing Navisphere agent confirm that it is supported according to the EMC Support Matrix.

Note: The HostIdFile.txt is located in the /var/log directory.

Confirm that Navisphere agent is not installed.
If the HostIdFile.txt file is present, either delete it or rename as mentioned above.
Create the agentID.txt (case sensitive) and place it in the / directory as mentioned above.
Reboot the VMWARE ESX server.
Install Navisphere agent and confirm the agent has started.
Check the HostIdFile.txt and confirm that the correct IP address is displayed.
Navisphere should automatically update with the correct IP address found in the HostIdFile.txt.

Ok that process was straight forward but I am still having some issues.

The SAN recognizes the initiator name (but not the alias). The initiator is logged in but the agent has not registered itself.

When I check the hosts under the hosts tab, I see the new initiator but its properties says the agent cannot be reached.

I also see a reference to the hostname of that server but it must be an old one as its pointing to old IP.

How do I get rid of entries under the hosts tab? This server has no connections under connectivity status

cheers

I got a bit further but issue has not been resolved. Now I have two entries for my host. One reflects the old ip and the other one reflects the new ip as configured in the agentID file.
I suppose the latter is what we want to see but both entries appeared to have marked with the red U and cannot connect to agent on host.

I still cannot seem to get rid of the old entries under hosts tab and there are no old paths listed under connectivity status

I have made a wee bit more progress.
I forgot to open one port in the firewall. SAN and agent are seeing each other now but still not able to add storage to my esx box

Message was edited by:
AllBlack

do you see the host in navisphere if you expand the host branch?
in the connectivity status, all the HBAs of the host must be "registered"= yes and "logged in"=yes.
if not, you can manually register each record.
after that the host will be visible in navisphere. then you can create a storage group and add the host and luns in that storage group.

Starting Fresh,

I install the naviagentcli.rpm on my esx 3.5 box and ensure it has started.

I enable the ISCSI initiator and add the IPs of two storage ports. I perform a rescan and my two targets are discovered. I restart and stop agent.

In navisphere the host shows up and is logged in and registered. It takes quite a while to reflect this!! Why is that?

Under my hosts tab shows up and is talking to agent on IP configured in agentID file. However, I still have old entry for same host here (marked U )

Now I create storage group, add host and bind a LUN to it.

Back in ESX I add storage. I select Disk/LUN and my LUNS do not appear. This is where I keep getting stuck. Do I need to add priviliges for user somewhere as this is going over a dedicated network? Our SCSI network is all setup correctly, none of our windows boxes have issues talking to SAN over ISCSI

cheers

it wont appear in a flash...but is it taking more than few minutes?


that will go once you restart the management server.


its better to shut down the host at this moment, remove the host from storage group, register all paths related to this server from connectivity status, restart the management server on array and then power up the host back on.

this may sound a long thing to do but can resolve this quick. and restarting management wont affect access to other hosts and luns.