4 Operator

 • 

2.8K Posts

March 21st, 2008 02:00

Hi Marco.

Machine n.1 where it all works fine:
# cat /proc/scsi/qla2xxx/0

...
SCSI Device Information:
scsi-qla0-adapter-node=50014380011c51bd;
scsi-qla0-adapter-port=50014380011c51bc;
scsi-qla0-target-0=5006016141e00fa9;
scsi-qla0-target-1=5006016941e00fa9;

...
#cat /proc/scsi/qla2xxx/1
SCSI Device Information:
scsi-qla1-adapter-node=50014380011c51bf;
scsi-qla1-adapter-port=50014380011c51be;
scsi-qla1-target-0=5006016041e00fa9;
scsi-qla1-target-1=5006016841e00fa9;


This host have 2 HBA and every HBA can see two different WWN (two different targets). The wwns belong to two ports of the same Clariion. So an HBA can see SPA0 and SPB0 while the other HBA can see SPA1 and SPB1.

Machine n.2 where it doesn't works:
cat /proc/scsi/qla2xxx/0

...
SCSI Device Information:
scsi-qla0-adapter-node=5001438000beaf21;
scsi-qla0-adapter-port=5001438000beaf20;
scsi-qla0-target-0=5006016141e00fa9;

...
cat /proc/scsi/qla2xxx/1
SCSI Device Information:
scsi-qla1-adapter-node=5001438000beaf23;
scsi-qla1-adapter-port=5001438000beaf22;


This host have again 2 HBA but while HBA0 can see only a single target (only a single SPXy) the other HBA can see ANY target.

Can you please explain what do you mean by "it doesn't works" ?? :D

How can I correct those errors?


If the "error" is that your Machine n.2 can't see all the luns, please check zoning for Machine n.2. Maybe you have also to check masking (I think it's called Access Logix in CX world). Also check that your hba logs in correctly on the Storage Processors before going on. Use Navisphere to check connectivity between your hosts and the CX.

-s-

4 Operator

 • 

5.7K Posts

March 21st, 2008 05:00

Also check if in the connectivity status all paths are the same color (black) and if there are no blue-ish icons.

341 Posts

March 24th, 2008 21:00

Might also be worth checking from Navisphere Manager that all paths to storage are enabled for this host.

Refer to EMC knowledgebase article emc111684 for instructions on how to do this, and if you have any questions about this procedure contact the EMC Customer Support center or your local EMC representative and quote this article ID.

Let us know if any of these suggestions have progressed the issue reported.

Message was edited by:
Mark Foreman (moderator)

341 Posts

March 25th, 2008 00:00

Sorry, I was using emc111684 to troubleshoot which is "customer-viewable", and publicly displays the p/w... I didn't realise it was secret!
I can't seem to edit my previous post.

Marc/Stefano, you can delete as you see fit... sorry.

4 Operator

 • 

5.7K Posts

March 25th, 2008 00:00

Please remove the engineering mode password from your post. It's supposed to be secret.

By the way: the checking of the color in connectivity status is leading towards your solving that particular problem.

4 Operator

 • 

5.7K Posts

March 25th, 2008 01:00

AFAIK mentioning passwords or serial numbers are not best practice here ;)

4 Operator

 • 

5.7K Posts

March 25th, 2008 03:00

Oh well, just thought it would be better not to mention too much of those details here ;)

9 Legend

 • 

20.4K Posts

March 25th, 2008 03:00

this password is mentioned in many solutions on PP ..what's the big deal.

4 Operator

 • 

2.8K Posts

March 25th, 2008 13:00

I missed the opportunity to trim a thread !!! :D

However I suppose the password you are talking about is the Navisphere "expert" password. Even if widely known it's still a "secret" .. ]:)

9 Legend

 • 

20.4K Posts

March 25th, 2008 16:00

I missed the opportunity to trim a thread !!! :D


i would say something but then what's the point ..enjoy your power trip my friend.

9 Legend

 • 

20.4K Posts

March 26th, 2008 05:00

oh ..so you disabled Qlogic native failover. If you typically download drivers from the OEM section on Qlogic/Emulex website and for OEM vendor select EMC, their rpm's are usually modified to set failover to 0.

10 Posts

March 26th, 2008 05:00

Hi Stefano,
the problem was solved installing qla2xxx-v8.02.08-dist.tgz, adding the following line to /etc/modprob.conf
options qla2xxx ConfigRequired=0 ql2xfailover=0
and following the guidelines provided by the README.qla2xxx file.

Now I've another problem... I'll post it asap :)


Thanks,
Marco
No Events found!

Top