Unsolved
This post is more than 5 years old
5 Posts
0
3516
vSphere with cx3-30 host registration
I've recently installed a vSphere 4.0 setup connected to a cx3-20 with flare 3.26.20.5.019. As per the Host Connectivity guide, I did not install the naviagent on the ESX consoles. I've got two problems that I'm running into
- Navisphere shows 3/4 of the hosts as "Host Agent not Reachable". I've read through the forums that vsphere 4 will auto-register when the system boots. Is this to be expected?
- One of the hosts was previously manually registered, and the hosts screen still shows it as manually registered. I'm not sure how to remove the manual registration so I can see the OS etc. I've tried rebooting, deleting the hostidfile.txt file, rebooting again, to no avail.
Any help would be appreciated.
Thanks
SJHiker
RRR
2 Intern
2 Intern
•
5.7K Posts
0
April 1st, 2010 02:00
You'll need ip connectivity between the storage processors and the hosts: is that working ok ?
SJHiker
5 Posts
0
April 1st, 2010 09:00
I have IP connectivity. Previously with navisphere, I had to open up ports in the ESX firewall, however, I haven't seen any instructions that require that this be done with vsphere.
kelleg
4.5K Posts
0
April 1st, 2010 13:00
Once a host is manually registered to change back you need to shut down the host, remove the host from the Storage Group, de-register the host in Connectivity Status (all paths listed), then turn on the host.
The issue with NaviAgent use to be finding the correct NIC to use to communicate with the array, EMC agent uses the first bound NIC, so for example, on a Windows host if you have 4 NICs and the one that you use to communicate with the array is the second NIC bound, Agent will push to the array the first NIC bound and Agent on the array will attempt to talk to the host using the wrong NIC. It might be the same for the agent in V4.
glen
SJHiker
5 Posts
0
April 1st, 2010 16:00
So I followed your procedure. I shut down the vsphere system, removed the host from all storage groups, went into Connectivity status and deregistered the host. Then I powered the host back on. The host has only one nic in it that is connected to the network and configured with an IP address. When the host came back on, I received the expected event that two unregistered hbas logged into the fabric. However, when I went to the hosts tab, I saw once again the host and it was listed as Manually registered.
Is it also expected that you cannot do things like "Server Update now" since there's no agent on the vsphere?
kelleg
4.5K Posts
0
April 2nd, 2010 07:00
The Agent on the host that's included in V4 is suppose to act the same way that the Navisphere host Agent works - the array contacts the host agent using TCP port 6389 (check that these ports are open and no firewall), and the host agent is suppise to respond.
You may need to open a case with VMware to see what's going on if the TCP port is open and still not working.
glen
LCS2
20 Posts
0
April 7th, 2010 05:00
I have read that the vsphere registration is a "push" from the ESX kernel to the Clariion. I can not find any documentation indicating TCP port 6389 must be open for the ESX 4.0 registration process, only for Navisphere agent(which we do not install on ESX4.0 per EMC recommendation), and or Navisphere CLI which at this point we do not install on ESX 4.0.
We are having issue with the auto-registratioin of ESX4.0 to our CX4-480 array's(Flare v29). We did open port 6389 on one ESX 4.0 host to asist in troubleshooing the issue. Still no auto-registration. We have also verified within the ESX configuration/advanced settings/disk, the Disk.EnableNaviReg setting was set to "1" to allow the auto registration.
It seems we are missing some small piece to this puzzle, any ideas would be appreciated.
thanks
SJHiker
5 Posts
0
April 8th, 2010 16:00
Ok.. so I hooked up a brand new server today with HBAs that have never been seen by the clarrion and made an interesting observation.
The new host (2 hbas) automatically appeared as "manually registered".
The other hosts which were upgraded from ESX3.5 to vsphere4, which previously had automatic registration via the agent, all show "U" icons for agent not reachable. Seems that the clariion thinks that an agent should be there where there isn't an agent anymore and that the clarrion can't switch from agent to no agent when you upgrade from esx3.5 to 4.
Odd behavior.
wolf591
1 Message
0
May 25th, 2010 06:00
I've been looking at this issue on and off for a while and I found a Primus article from November 2009 (can't remember the ID - sorry) stating that with vSphere 4, the kernel will auto-register with the Clariion array but that on FLARE revisions 28 or less, the host will display "Manually registered; Host agent not reachable" in the Navisphere storage management GUI - on FLARE 29 it should read as fully registered.
Regards,
George.
toddjam10
30 Posts
0
May 25th, 2010 06:00
Take a look at EMC Knowledgebase solution emc228353, this related to release28 but may also be needed for release29. If this is the case, I would suggest you notify EMC via a service request that the article needs to be updated for R29 if still affected or an alternate registration process is needed.
kelleg
4.5K Posts
0
May 25th, 2010 11:00
Please see Primus emc241869 for a list of all Primus articles about ESX4 and registering on the array.
Also Primus emc220412 or emc229699 - both copied below - may be what you're seeing
The following is a Primus(R) eServer solution:
ID: emc220412
Domain: EMC1
Solution Class: 3.X Compatibility
Goal Do you need to install Navisphere host agent on ESX4.0 VSphere hosts?
Fact Product: CLARiiON CX4 Series
Fact Product: CLARiiON CX3 Series
Fact OS: VMware VSphere ESX 4.0
Fact EMC SW: Navisphere Host Agent
Symptom ESX 4.0 Hosts are shown as unmanaged in Navisphere Manager for a CX4 Series array with FLARE Release 28.
Fix For ESX4, the ESX kernel will perform an auto registration to a CLARiiON array of all releases. Navisphere Agent or Navisphere server utility will not push registration from ESX4 Console to all releases of CLARiiON arrays. Navisphere Host Agent is NOT supported on ESX4i or ESX4.x.
If you are using Release 28 or earlier Navisphere on the array, Navisphere will display unmanaged for the ESX server (ESX3i, ESX4) which uses ESX kernel auto push/registration. But actually Navisphere does show the device mappings for the ESX server. This behavior is changed in Navisphere Release 29, where they are shown as managed now.
Release 29 Navisphere Display
So regardless of the revision of Navisphere that you are using on the array, Navisphere agent should not be installed on the ESX4 console.
Note Navisphere host agent should not be installed on ESX 4.0 hosts and is not supported.
The following is a Primus(R) eServer solution:
ID: emc229699
Domain: EMC1
Solution Class: 3.X Compatibility
Fact Product: CLARiiON CX4 series
Fact Product: CLARiiON CX3 series
Fact Product: CLARiiON CX series
Fact System: VMware ESX 4
Fact System: VMware ESXi 4
Fact EMC Firmware: FLARE Release 26 Patch 005
Symptom Navisphere GUI shows the operating system of the ESX host as 'unknown' and no LUN Status information.
Symptom ESX Server operating system is shown as "unknown".
Symptom No LUN mappings shown for ESX server LUNs
Cause The customer installed a new ESX4 server. The array was running FLARE Release 26 Patch 005. When viewing host properties from Navisphere Manager, the customer saw that the operating system was listed as "unknown" and the LUN Status did not show host/LUN mappings. Navisphere Host Agent on the ESX4 hosts is not supported.
Fix FLARE Release 29 has improved functionality with ESX4 servers. These functions have been back-ported to other versions of FLARE. In this case, upgrading the array to FLARE Release 26 Patch 016 resolved the issue.
Note This same functionality has been back-ported to these FLARE releases as well:
See solutions emc220412 and emc241869 for additional information.
glen
AranH1
2.2K Posts
0
May 25th, 2010 12:00
Glen,
The article ID emc241869 does not return a valide primus article.