No they do not show up in the list of hosts if i select 'Include connected'

They all show up as blue so they are not in storage group.

And i did not manually register, they showed up automatically.

If your ESX hosts will be in a cluster then make sure that you assign the same hlu number to each host for the same LUN. This has to be identical for ESX cluster LUN access.

What were the initiator settings in Connectivity Status?

If you select on one of the initiator records in connetivity status what are the settings? They should be set to Failover 1, CLARiiON Open, Array CommPath Enabled, and the Storage Group should list ~management since they are not assigned to a storage group.

If all of that looks good then it may be a Navisphere GUI issue. Have you tried restarting the management server? To do so go to http:// /setup the select 'Restart Management Server'. Wait until you can login to SPA again with navisphere and then do the same think with SPB. After that is complete try to add the host to the storage group again.

You can also test to see if this is a Navisphere GUI issue by adding the hosts to the Storage Group via the CLI:

naviseccli -h storagegroup -addhlu -gname -hlu -alu

Initiator type: clariion open

HBA type: host

Array Commpath: Enabled

Failover mode: 1

Unit serial Number: array

Storage Group: ~management

Are they already assigned to another Storage Group? When you go to add hosts to a Storage Group the default selection from the drop-down menu is hosts that are 'Not Connected', if you change that to 'Include connected' do the ESX hosts appear in the list?

Also if you look in Connectivity Status what color are the entries? If they are green they are already assigned to a Storage Group, blue they are not assigned to a Storage Group.

Did you manually register the hosts? Have you double checked their registration settings?

were you adding the host to an existing storage group or did you create a new storage group?

Hosts will not show up in the Host list until you add to a storage group.

Also, check emc99467 - see note 17 -maybe you need to set to failover 4 instead of 1?

17. For VMware native failover, failovermode settings are as follows:
• CX and CX3 series arrays: failovermode MUST be set to 1
• CX4 arrays operating with FLARE revisions prior to 04.28.000.5.704: failovermode MUST be set to 1
• CX4 arrays operating with FLARE 04.28.000.5.704 or later:
     - ESX 2.x or 3.x: Failovermode MUST be set to 1
     - ESX 4.0 or above:
          Failovermode is recommended to be set to 4 for ALUA behavior or
          Failovermode may be set to 1 for active/passive behavior

glen

peterborghard wrote: How can I add them to a storage group, if They are not in the list when i select "connect hosts'?

I think Glen was referring to the Hosts container in Navisphere. A host won't show up in that container until it has been added to a storage group.

Were you able to add the host to the storage group and mask a LUN to the host using the CLI?

peterborghard wrote: No do not think i need to change the failover mode. There are two hosts that work, older setup exact same version of Esxi and they have failover mode set as 1.

Yes, the failover mode should only be changed to 4 if you want to enable ALUA on a Cx4 running FLARE 4.28....704 and a host running ESX 4.

Are these two hosts that work on this array?

glen

So the hlu number is user defined. You specify which host lun number you want to assign the LUN being masked to the host. If you have not assigned a LUN to the hosts yet then start at 0.

I forgot to put in my previous post the command for adding the host to the storage group. You will have to do this before you can use the command to assign the lun to the storage group.

So do this one first:

naviseccli -h storagegroup -connecthost -o -host -gname

Then issue this command. As stated previously, since this is the first LUN assigned to your ESX host use 0 for the hlu. The next LUN masked to that host will be assigned the hlu 1.

naviseccli -h storagegroup -addhlu -gname -hlu -alu

I am not too familair with command line and was having problems finding the -hlu number.