UNSOLVED

JardineJoe

updated

19 years ago

J

JardineJoe

10 Posts

0

1564

July 12th, 2007 15:00

Solaris host will not register with CX600

We are having a problem with getting a solaris 10 host to register with our CX600. Connectivity status says it is logged in but not registered. I've been through the EMC knowledgebase, forums and other forums and still can't find a resolution.

Our setup:

Sunfire V240
SunOS 5.10 Generic_125100-10
Qlogic 2340 with driver 4.22
Navisphere Agent 6.19.4.7.0
Navisphere Admsnap 2.9.0.0.7
PowerPath 4.5.0_b169
CX600 array with flare 2.19.600.5.034 with AccessLogix, NavisphereManager and SnapView
Connected through EMC DS24-M2 with firmware 9.0.0 76

I've checked E-Lab Navigator and all the above is deemed compatible. We've installed all the requisit OS patches.

There was one EMC article that said the host and the array should be on the same subnet. That's obviously not true as all of our hosts are on a different subnet and can communicate just fine. The are other solaris hosts on the same subnet as this one and they have no problem registering. Certainly IP connectivity between the host and the array is working. There are no firewalls separating them.

I've looked at HostIdFile.txt and that is correct. The host only has a single NIC so there are not multihoming issues to worry about. But I created an agentID.txt file with the correct details in it just in case. Made no difference. The hosts file has the correct information for the IP of the NIC and the hostname (and FQDN).

The agent.config file is setup correctly and is the correct location:
LastSave 3265501581
clarDescr Navisphere Agent
clarContact xxxx, xxxxxxx

device auto auto

user root
user system@10.0.102.102
user system@10.0.102.103

poll 60
eventlog 100
baud 9600

Though I shouldn't have to, I've manually registered the host on the CX600. I am then able to assign the host to a storage group but the LUNs don't appear on the host even after a few "Update Now"s, restarting the agent and rebooting the host.

There is nothing in the agent log on the hosts the provides any clues and the storage processor event logs don't reveal anything either.

I've used the procedure generator to make sure we haven't missed any steps with the install process and we haven't.

Help?