SUMMARY: fabric attached device question
2007-12-25 0:48:00
You might try using iostat -En and see if the LUNid's are referenced as
part of the serial number.
result is:
Illegal Request: 0 Predictive Failure Analysis: 0
c1t3d2 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: IBM Product: 2105F20 Revision: 2.91 Serial No:
30218872
Size: 5.00GB <4998758400 bytes>
the LUNid is 302
wow.
-----Original Message-----
From: Jeff Barratt [mailto:jbarratt at compsat.com]
Sent: March 14, 2003 1:52 PM
To: codeprof at codeprof.com
Subject: fabric attached device question
managers,
I am not a solaris expert, so please excuse my infamiliarity in this.
I have an ultra 60 with approved HBAs attached to a fabric that is being
presented LUNs from an IBM shark. I am able to use the LUNs as expected,
but
I am having difficulty mapping the device back to the shark's LUNid. I
can
do this through a GUI (like ezfibre) but how do I do this natively
through
solaris(9)?
the reason I ask is this:
if I present 4 25GB LUNs to a single HBA, and put data onto 3 of the
drives
and then decide I want to remove the unused 4th drive, I can find the
LUN ID
via ezfibre(serial# drive paramater), but how do I find that number via
a
shell? The reason this is important is, dependant upon the HBA, I don't
want
to use a specific tool. I understand the nature of fibre channel, and
that I
am only presenting the LUN to the HBA, and the shark(or any other
appliance)
has no idea what machine the HBA is in, nor how it(the HBA) will present
drives to the host. In AIX I can do it through the drive
attributes(lsattr),
but format doesn't give me the info I need (or does it?)
_______________________________________________
codeprof mailing list
codeprof at codeprof.com
http://www.codeprof.com/execute/ask/?codeinfoid=21313
Comments
Got something to say?
You must be logged in to post a comment.
