I am going to post the coolest little piece of information that most people in the CX world either don't know about or don't care to read about.
To fix this issue on Windows do this:
1. Create a file called "AgentID.txt" in the C:\Program Files\EMC\NaviAgent dir.
2. In the file put the following: WHAT_YOU_WANT_TO_CALL_THE_HOST UNIQUE_IP_OF_HOST (Example "AgentID.txt" file) web1.whatever.com 34.56.78.90
3. Save the file, restart NaviAgent and then refresh your connectivetly status.
The reason I say "UNIQUE_IP_OF_HOST" is Navisphere will do some funky "Ghosting" when you have more than one host that has the same IP. For example don't allow a host to be connected to the array that both have 192.168.1.1. If you have a Lab enviroment and want to see what it does then go for it
This documented trick works great for anyone that wants to identify there host by another name, IP or both.
If you want to do this for Linux then follow the same above steps. But instead of the "AgentID.txt" file, you creat a file called "agentID.txt" and put it in the (root) / directory on your Linux server. Unfortunately, I have not checked the doc's lately, this Linux one is not documented to well.
This problem is typically seen when there is a config mismatch or the driver/FW versions are incorrectly set.
Cross the "t"s and dot the "i"s as far a the HBA driver and FW your running. Ensure all HBA settings are as per the documentation. Ensure that all necessary items in the EMC Powerpath Release Notes are meet. Ensure that your host falls in line with the EMC Support Matrix www.emc.com/interoperability. On the Clariion Side of things, ensure that the "Failover" modes and "Array Commpath" settings are correct.
GlenH
141 Posts
0
November 15th, 2006 00:00
Do the HBA WWN's appear in the Connectivity status list in Navisphere ?
I think you'll need to post a little more info regarding the configuration and where you are up to for us to help you.
Glen.
csmykay1
59 Posts
0
November 15th, 2006 11:00
I am going to post the coolest little piece of information that most people in the CX world either don't know about or don't care to read about.
To fix this issue on Windows do this:
1. Create a file called "AgentID.txt" in the C:\Program Files\EMC\NaviAgent dir.
2. In the file put the following:
WHAT_YOU_WANT_TO_CALL_THE_HOST
UNIQUE_IP_OF_HOST
(Example "AgentID.txt" file)
web1.whatever.com
34.56.78.90
3. Save the file, restart NaviAgent and then refresh your connectivetly status.
The reason I say "UNIQUE_IP_OF_HOST" is Navisphere will do some funky "Ghosting" when you have more than one host that has the same IP. For example don't allow a host to be connected to the array that both have 192.168.1.1. If you have a Lab enviroment and want to see what it does then go for it
This documented trick works great for anyone that wants to identify there host by another name, IP or both.
If you want to do this for Linux then follow the same above steps. But instead of the "AgentID.txt" file, you creat a file called "agentID.txt" and put it in the (root) / directory on your Linux server. Unfortunately, I have not checked the doc's lately, this Linux one is not documented to well.
If you would like more information on this check out the NaviSphere Administartion guide at:
https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/Offering_Technical/Technical_Documentation/300-002-038_A07_elccnt_0.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tDb250ZW50RXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwMWE4NTc4LG5hdmVOb2RlPVNvZndhcmVEb3dubG9hZHM_
Hope this helps,
Shmac
Joe-tzlGj
1 Message
0
December 1st, 2006 11:00
I do have the latest supported Qlogic drivers, I do have AgentID.txt file. I can connect to my Clariion but Powerpath does not see my HBAs.
I tried different PowerPath version but no luck.
Thanks
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 26th, 2006 20:00
Cross the "t"s and dot the "i"s as far a the HBA driver and FW your running. Ensure all HBA settings are as per the documentation.
Ensure that all necessary items in the EMC Powerpath Release Notes are meet.
Ensure that your host falls in line with the EMC Support Matrix www.emc.com/interoperability.
On the Clariion Side of things, ensure that the "Failover" modes and "Array Commpath" settings are correct.
g