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.
GlenH
141 Posts
350
0
Posted 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.