Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

JardineJoe

10 Posts

1520

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?

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 12th, 2007 16:00

JardineJoe

10 Posts

July 13th, 2007 20:00

To even be able to add the host to the storage group I have to manually register the initiators. Having done that and then adding the host to the desired storage group the connectivity status shows the appropraite storage group but still no joy. I reconnected them anyway. That didn't do anything.

Have rebooted and still nothing.

Thinking about it though... the QLogic card was a spare one we had from a system that was decommissioned last year (compaq/intel/windows). Is it possible the array is hanging on to some old info?

Message was edited by:
JardineJoe

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 14th, 2007 05:00

when you manually registered the host ..what did you select for Failover mode ? Since you are running PowerPath it should be 1. The qlogic driver you are using ..is it the leadville driver or did you downloaded it from Qlogic. The reason i ask is because with Qlogic drivers you have to manually modify sd.conf enumerate your luns , modify qla.conf and set your targets ...where with leadville it does it for you. When you are rebooting you are typing: reboot -- -r ?

JardineJoe

10 Posts

July 15th, 2007 14:00

Failover mode was set to 1. I'm using the qlogic driver and as per the procedure generator I've added:

to system:

set sd:sd_max_throttle=20
set sd:sd_io_time=0x3C

and changed the appropriate settings in qla2300.conf according to the procedure.

The installation of the driver automatically put the following into sd.conf:

name="sd" parent="qla2300" target=2048;

I've compared these files to hosts that are working properly and they are the same.

Yes... rebooting with reboot -- -r

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 15th, 2007 18:00

do you have these type of entries in your /kernel/drv/qla2x00.conf

hbax-SCSI-target-id-y-fibre-channel-port-name="PPPP";

i am surprised you only have one entry in your sd.conf ..i would expect to see somthing like this:

name="sd" class="scsi" target=125 lun=0;
name="sd" class="scsi" target=125 lun=1;
name="sd" class="scsi" target=125 lun=2;

..etc

JardineJoe

10 Posts

July 15th, 2007 20:00

Sorry I just showed the bit of sd.conf that the QLA2300 driver added. The whole file is:

# cd /kernel/drv
# more sd.conf
#
# Copyright 2006 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
#
#ident "@(#)sd.conf 1.10 06/02/08 SMI"

name="sd" class="scsi" class_prop="atapi"
target=0 lun=0;

name="sd" class="scsi" class_prop="atapi"
target=1 lun=0;

name="sd" class="scsi" class_prop="atapi"
target=2 lun=0;

name="sd" class="scsi" class_prop="atapi"
target=3 lun=0;

name="sd" class="scsi"
target=4 lun=0;

name="sd" class="scsi"
target=5 lun=0;

name="sd" class="scsi"
target=6 lun=0;

name="sd" class="scsi"
target=8 lun=0;

name="sd" class="scsi"
target=9 lun=0;

name="sd" class="scsi"
target=10 lun=0;

name="sd" class="scsi"
target=11 lun=0;

name="sd" class="scsi"
target=12 lun=0;

name="sd" class="scsi"
target=13 lun=0;

name="sd" class="scsi"
target=14 lun=0;

name="sd" class="scsi"
target=15 lun=0;
#
# Enable Target 7 for the mpt SCSI/SAS/SATA driver. Target 7 has
# traditionally been reserved for legacy SCSI HBAs, but SAS controllers
# supported by the mpt driver do not use target 7 for that purpose.
# Enabling Target 7 allows the use of 8 disks on those controllers.
#
name="sd" parent="mpt"
target=7 lun=0;
name="sd" parent="qla2300" target=2048;


Mind you the system I'm comparing to is Solaris 8 and the system I'm having trouble with is Solaris 10.

And as far as:

hbax-SCSI-target-id-y-fibre-channel-port-name="PPPP";

goes, not there isn't an entry for that. But then the systems that work don't have it either.

Message was edited by:
JardineJoe

Message was edited by:
JardineJoe

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 16th, 2007 08:00

can you look in /var/adm/messages ...see anything like this:

qla2300-hbax-SCSI-target-id-0-fibre-channel-port name=" 50060482c464abec";
qla2300-hbax-SCSI-target-id-0-fibre-channel-port-name=" 50060482c464abec";

JardineJoe

10 Posts

July 16th, 2007 14:00

No. A grep of messages for qla2300 has:

# grep qla2300 messages
Jul 11 15:45:29 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 11 15:45:30 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 11 15:45:30 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 11 15:45:30 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 11 15:45:30 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 11 15:45:30 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 11 15:45:30 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 11 15:45:30 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 11 15:45:30 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 11 15:55:51 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 11 15:55:52 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 11 15:55:52 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 11 15:55:52 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 11 15:55:52 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 11 15:55:52 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 11 15:55:52 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 11 15:55:52 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 11 15:55:52 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 11 16:40:11 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 11 16:40:12 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 11 16:40:12 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 11 16:40:12 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 11 16:40:12 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 11 16:40:12 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 11 16:40:12 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 11 16:40:12 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 11 16:40:12 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 11 16:53:18 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 11 16:53:19 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 11 16:53:19 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 11 16:53:19 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 11 16:53:19 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 11 16:53:19 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 11 16:53:19 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 11 16:53:19 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 11 16:53:19 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 12 08:27:34 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 12 08:27:35 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 12 08:27:35 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 12 08:27:35 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 12 08:27:35 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 12 08:27:35 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 12 08:27:35 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 12 08:27:35 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 12 08:27:35 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 14 11:26:43 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 14 11:26:44 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 14 11:26:44 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 14 11:26:44 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 14 11:26:44 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 14 11:26:44 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 14 11:26:44 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 14 11:26:44 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 14 11:26:44 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 16 09:59:36 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 16 09:59:36 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 16 09:59:36 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 16 09:59:37 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 16 09:59:37 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 16 09:59:37 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 16 09:59:37 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 16 09:59:37 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 16 09:59:37 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 16 10:09:59 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 16 10:10:00 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 16 10:10:00 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 16 10:10:00 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 16 10:10:00 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 16 10:10:00 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 16 10:10:00 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 16 10:10:00 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 16 10:10:00 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 16 11:47:56 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 16 11:47:57 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 16 11:47:57 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 16 11:47:57 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 16 11:47:57 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 16 11:47:57 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 16 11:47:57 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 16 11:47:57 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 16 11:47:57 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3
Jul 16 16:44:38 jltaperux4 qla2300: [ID 818750 kern.notice] QLogic Fibre Channel Driver v4.22 Instance: 3
Jul 16 16:44:39 jltaperux4 qla2300: [ID 920500 kern.info] hba3: Fibre Channel Loop is Down (8030)
Jul 16 16:44:39 jltaperux4 qla2300: [ID 736385 kern.info] hba3: Fibre Channel Loop is Up (8014)
Jul 16 16:44:39 jltaperux4 qla2300: [ID 491635 kern.notice] hba3: Firmware v3.3.12 (ipx)
Jul 16 16:44:39 jltaperux4 qla2300: [ID 568177 kern.info] hba3-adapter-node-name="200000e08b0f9cc0";
Jul 16 16:44:39 jltaperux4 qla2300: [ID 562076 kern.info] hba3-adapter-port-name="210000e08b0f9cc0";
Jul 16 16:44:39 jltaperux4 qla2300: [ID 720712 kern.info] hba3-adapter-port-id="610f13";
Jul 16 16:44:39 jltaperux4 pcisch: [ID 370704 kern.info] PCI-device: fibre-channel@3, qla23003
Jul 16 16:44:39 jltaperux4 genunix: [ID 936769 kern.info] qla23003 is /pci@1e,600000/fibre-channel@3

I've also noticed different devices in /dev/rdsk than I'm used to seeing. Our other Solaris hosts have the usual devices you'd expect plus the emcpower devices. On this host however there are devices with the WWN of the CX600 SP's in them and no emcpower devices:

c4t5006016010601122d0s0
c4t5006016010601122d0s1
c4t5006016010601122d0s2
....

I also noticed that on the hosts that work there are additional entries in sd.conf like you suggest:

name="sd" class="scsi" target=0 lun=1;
name="sd" class="scsi" target=0 lun=2;
name="sd" class="scsi" target=0 lun=3;
name="sd" class="scsi" target=0 lun=4;
...

I've added these entries to sd.conf and rebooted with no luck. I also added:

hbax-SCSI-target-id-y-fibre-channel-port-name="PPPP";

to qla2300.conf and rebooted and again no luck.

All reboots were with reboot -- -r

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 16th, 2007 19:00

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 16th, 2007 19:00

take a look at this document ..make sure you are putting things in the right file. Unfortunately i use emulex in my box otherwise i would show you what it looks like on my system.

http://download.qlogic.com/drivers/5419/QLogic_Solaris.pdf

JardineJoe

10 Posts

July 16th, 2007 20:00

With the Leaderville drivers it does appear these are installed but again they are also on the systems that are working so I'm not sure how that was handled.

On the functioning system (Solaris 8):

system SUNWqlc Qlogic ISP 2200/2202 Fibre Channel Device Driver
system SUNWqlcx Qlogic ISP 2200/2202 Fibre Channel Device Driver (64 bit)

On the disfunctional system (Solaris 10):
system SUNWqlc Qlogic ISP 2200/2202 Fibre Channel Device Driver
system SUNWqlcu Qlogic Fibre Channel Adapter Utilities (usr)

Yet the Solaris 8 host doesn't have any of the ctXWWN.... devices.

I am also having trouble getting rid of the manual registration of the host on the cx600. I've de-regitered it but there are now two entries under the hosts tab:

20:00:00:E0:8B:0F:9C:C0:21:00:00:E0:8B:0F:9C:C0 [UNKNOWN]
jltaperux4.jlta.com.au [10.0.60.39; Manually Registered]

If I block the port via the switch then the top one disappears (as you'd expect). But the bottom one (which is no longer associated with any HBAa) just won't go.

JardineJoe

10 Posts

July 16th, 2007 22:00

I've got it registering now properly. I'll have to refine it a bit to see which entried made the difference but it was the target entries in the qla2300.conf that did it. I used scli to automatically set the targets and it put a bunch of stuff in qla2300.conf.

Should I get rid of the SUNWqlc packages since I'm not really using them?

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 17th, 2007 06:00

what is scli ? Sansurfer cli ?

If your luns appear ok now ..then i would leave SUNWqlc alone.

JardineJoe

10 Posts

July 17th, 2007 14:00

Yep. Sansurfer cli. This is what it added to qla2300.conf:

QL_CONFIGURE="Tue Jul 17 11:53:29 2007";
scsi-qla3-target-1-device-1-control="00";
scsi-qla3-target-1-device-1-port-id="610413";
scsi-qla3-target-1-device-1-port="5006016010601122";
scsi-qla3-target-1-device-1-node="5006016090601122";
scsi-qla3-target-0-device-0-control="00";
scsi-qla3-target-0-device-0-port-id="610813";
qla-mp-config-required=1;
scsi-qla3-adapter-model="QLA2340";
scsi-qla3-adapter-node="200000E08B0F9CC0";
scsi-qla3-adapter-port="210000E08B0F9CC0";
scsi-qla3-target-0-device-0-node="5006016090601122";
scsi-qla3-target-0-device-0-port="5006016910601122";
scsi-qla3-target-0-device-0-preferred="FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF";
scsi-qla3-target-0-device-0-lun-disabled="0000000000000000000000000000000000000000000000000000000000000000";
scsi-qla3-target-1-device-0-node="5006016090601122";
scsi-qla3-target-1-device-0-port="5006016010601122";
scsi-qla3-target-1-device-0-preferred="8000000000000000000000000000000000000000000000000000000000000000";
scsi-qla3-target-1-device-0-lun-disabled="0000000000000000000000000000000000000000000000000000000000000000";


Not exactly what I was expecting... but it works.

dynamox

11 Legend

 • 

20.4K Posts

 • 

87.4K Points

July 17th, 2007 19:00

yeah ..looks interesting ..especially the lines with disabled and preferred.

Was this post helpful?

View All

No Events found!

Top