UNSOLVED
B
Bomb_29390e
2 Intern
•
193 Posts
0
5000
November 16th, 2009 11:00
Host agent not reachable
I am getting an error for each of my ESX host in my cx4120 saying "host not reachbale". how can i verify navi agent is running on the esx - i tried under /etc/init.d to run naviagent stop and start and get commnad not found?
1658
1
Posted November 16th, 2009 12:00
First check if it is installed:
/bin/rpm -qa | grep -i navi
If you don't see it, then download the agent and unzip it on your esx server. That has an install script you can run. If I recall correctly, the script is named as ESX_install.sh. You can run that to install the agent.
1658
0
Posted November 16th, 2009 12:00
i run the/bin/rpm -qa | grep -i navi
and no massage just go back to prompt with no error
1659
1
Posted November 16th, 2009 12:00
Same as in Linux, do
ps -ef| grep agent
is the agent installed? The start/stop should be /etc/init.d/naviagent start or stop.
1658
0
Posted November 16th, 2009 12:00
when running naviagent stop start i am getting command not found. what the easy way to reinstall the naviagent ?
1658
1
Posted November 17th, 2009 07:00
I recall reading the the naviagent was not needed for ESX4, that the hosts are supposed to self-register with the CLARiiON arrays. I will dig around a little and see if I can find the documentation on this.1658
0
Posted November 17th, 2009 07:00
Found the primus article:
http://knowledgebase.emc.com/emcice/documentDisplay.do?docType=1006&clusterName=DefaultCluster&resultType=5002&groupId=1&page=&docProp=$solution_id&docPropValue=emc220412&passedTitle=null
"VMware ESX server shows manually registered after using the ESX_install.sh script to install Navisphere Host Agent." ID: emc209061 Usage: 5 Date Created: 03/10/2009 Last Modified: 07/02/2009 STATUS: Approved Audience: Customer Knowledgebase Solution Environment: EMC SW: Navisphere Agent Environment: Product: CLARiiON CX4 Series Environment: Product: CLARiiON CX3 Series Environment: System: VMware ESX Environment: Fibre Channel Problem: VMware ESX server shows manually registered after using the ESX_install.sh script to install Navisphere Host Agent, even rebooting the ESX server did not resolve the issue. Change: VMware ESX server was initially manually registered, then the site installed Navisphere Host Agent on server. Fix: After Navisphere Agent is installed, it is necessary to rescan the HBAs using VMware vCenter for VMware ESX 3.x and then restart the agent on VMware ESX server so that it communicates with the storage system and sends updated information. Run service naviagent restart on the ESX service console to restart the agent, or run the following command to restart the agent:
/etc/init.d/naviagent stop
/etc/init.d/naviagent startNotes: The Navisphere Host Agent is not required vSphere 4.0 (also referred to as ESX 4.0). With these versions of VMware the native multipathing driver performs a registration "push" down all paths at each boot. With this functionality, no host agent or manual registration is required. Please refer to emc217063. 1658
0
Posted November 17th, 2009 08:00
i fixed the problem with all of my ESX's. i talk to vmware and not sure why, but they said i do need to reinstalll the navi agent on vsphere - esx 4. i thought it is already embededd into the system. i am ok now thanks for all1658
0
Posted November 17th, 2009 08:00
Did they say why? I am curious what the reasons were if you could share them with us. According to the primus article we shouldn't have to install the agent.206
0
Posted November 17th, 2009 09:00
the story is that about two month ago i upgraded my VMware environment from 3.5 U3 to VSphere (ESX 4.0), and probably i did not check inside my Navisphere manager to make sure all hosts are communicating with VMware. last week i had to change few of my LUN's due to a new LUN structure i am building for VMware, and i found that all my ESX host in Navisphere manager are reporting "Host not reachable - cannot find host agent", even though all LUN's are still visible on VMware, what made me think something is going on with the Navigant. When I run /bin/rpm -qa | grep -i navi it showed no agent installed. i assume during VMware upgrade to vSphere the installation removed the agent or the system can no longer access the old esx3 folder. so long story short i reinstalled the navi agent version 6.29.0.6. on all host and issues resolved. as we mention here before i also know that with vSphere u should not install the agent, so i am not sure what the deal here... - also not sure but when i try to start and stop naviaent under /etc/init.d i am getting - command not found, not sure where exactly the service/daemon is reside
Bomb_29390e
2 Intern
•
193 Posts
1658
0
Posted November 16th, 2009 12:00
also i am on emc for downloading the agent but not sure which to pickfor ESX 4.0 (Vsphere) see list
or from here