This post is more than 5 years old
24 Posts
0
4114
NaviSphere ESX 3.0 Unable to retrieve remote agent configuration
Gents,
I'm running a CX500. I've installed a ESX 3.0 server and connected it to the CX500
installed the .rpm using this command:
rpm -ivh naviagentcli-6.19.4.7.0-1.noarch.rpm
restarted my esx server but still got the message in NaviSphere manager that the host is unmanaged although i can add it to storage group and assign lun's to it...
(also created a vmfs partition, so it works properly)
anyone got an idea to get this host managed?!?!
Do i have to add naviagent to a startup file or something?
Thanx in advance!
regards.
I'm running a CX500. I've installed a ESX 3.0 server and connected it to the CX500
installed the .rpm using this command:
rpm -ivh naviagentcli-6.19.4.7.0-1.noarch.rpm
restarted my esx server but still got the message in NaviSphere manager that the host is unmanaged although i can add it to storage group and assign lun's to it...
(also created a vmfs partition, so it works properly)
anyone got an idea to get this host managed?!?!
Do i have to add naviagent to a startup file or something?
Thanx in advance!
regards.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 23rd, 2007 06:00
Spud4
24 Posts
0
January 23rd, 2007 06:00
user system@
user system@
stupid me, i did a start instead of a restart.
all working now!
Spud4
24 Posts
0
January 23rd, 2007 06:00
http://www.vmware.com/community/thread.jspa?messageID=544745
still without succes tho.
when i want to start the naviagent (/etc/init.d/naviagent start) i get a failed everytime.
still think you are right dynamox that i should modify the agent.config file somewhere..
Spud4
24 Posts
0
January 23rd, 2007 07:00
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 23rd, 2007 07:00
EKellerman
76 Posts
0
January 23rd, 2007 11:00
Question: Resolving VMware ESX server that shows as host unreachable from Navisphere
Environment: OS: VMware ESX server 3.0
Environment: EMC Software: Navisphere Host agent 6.16.0.4.81 and 6.19.x.x
Problem: Navisphere Manager displays the VMware host as unreachable.
Problem: CLARiiON SP error logs shows: 4740 '11.93.16.11' cannot be managed. Client non-data stream error. 11.93.16.11 Err: RWSockErr: in RWSocket::connect: TIMEDOUT
Notes: Although the site's network had the required ports open for Navisphere CLI and Agent, VMware ESX has a built-in firewall.
Fix: Open the Naviagent, CLI, and Storage System Initialization Utility port from the ESX service console:
# esxcfg-firewall ¿o ¿openPort
For example:
esxcfg-firewall ¿o 6389,tcp,in,naviagent
Spud4
24 Posts
0
January 24th, 2007 00:00
and EKellerman, i've put this command : esxcfg-firewall ¿o 6389,tcp,in,naviagent
(restarted naviagent)
but no luck also...
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 24th, 2007 05:00
Spud4
24 Posts
0
January 24th, 2007 06:00
it's configurered with a 10.x network...
it's still in test, so no users or any servers are connected..except a few windows, netware, esx hosts for testing purposes
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
January 24th, 2007 07:00
kelleg
4.5K Posts
0
January 24th, 2007 09:00
In addition to installing the RPM, the EMC_Install.sh script opens some ports on the ESX 3 firewall. This is only necessary on ESX v3.0.x.
The procedure to do this is in the document:
EMC CLARiiON Server Support Products for Linux and ESX Server Installation Guide
P/N 300-002-041
Rev A08
However, this document is incorrect in a couple of places (I have submitted changes) and actually provides the command to close (-c) the ports instead of opening (-o) them in a couple of places.
The commands that I used from within the ESX3 (ESX3 ONLY) service console (as root) are as follows:
/usr/sbin/esxcfg-firewall -o 443,tcp,out,navisphere
/usr/sbin/esxcfg-firewall -o 2163,tcp,out,navisphere
/usr/sbin/esxcfg-firewall -o 6389,tcp,in,navisphere
/usr/sbin/esxcfg-firewall -o 6389,tcp,out,navisphere
/usr/sbin/esxcfg-firewall -o 6390,tcp,in,navisphere
/usr/sbin/esxcfg-firewall -o 6391,tcp,in,navisphere
/usr/sbin/esxcfg-firewall -o 6392,tcp,in,navisphere
After this you will need to either restart the firewall service or reboot the system to have the changes take effect.
Hope this helps,
glenk
george-medlabce
1 Message
0
March 5th, 2007 20:00
http://www.vmware.com/vmtn/resources/cat/91,100,126