WWN for SCSI adapters?

[mag007]

Is there a unique name/id/number for SCSI adapters? I am trying to draw SCSI and VSCSI adapters, and would like to know if its possible.

TIA

 

[FrankieAIX]

What do you mean you are trying to "draw"?

 

[mrn]

No WWID

try

lsdev -C | grep scsi

lsattr -E -l scsi0

or

lsattr -D -l scsi0

man lsattr

Mike

"Whenever I dwell for any length of time on my own shortcomings, they gradually begin to seem mild, harmless, rather engaging little things, not at all like the staring defects in other people's characters."

 

[p5wizard]

SCSI adapters, being bus-oriented only have a SCSI-ID, which is mostly 7 (default) and only needs to be unique to a SCSI bus, so you can have multiple SCSI adapters in a server all having the same SCSI-ID, as long as they are on separate buses, that is fine.

see: lsattr -E -l scsi0 output

I've come across twin-tailed buses for shared SCSI storage where you have two SCSI adapters of two servers on the same bus and one would have a SCSI-ID 7 the other would be 6 or so.

SAN adapters being designed to operate in a network / fabric need a more elaborate/unique way of identifying themselves - hence the WWNN.


HTH,

p5wizard

 

[mag007]

When I say draw, create a diagram. I want a picture (hardcopy).

Managing this APV env can get tricky, and tough to visualize the virtulization portion without a pic.

 

[p5wizard]

Well, for vhost and vscsi adapters, I'd show the lpar ID and virtual slot number, that pretty much identifies which adapter is which.

on VIOS, you can use lsdev -slots info
on client LPARs, user lscfg|grep -i 'virtual scsi'

if I'm not mistaken.

HTH,

p5wizard

 

[mag007]

I will try that. Basically I want all dual paths on different adapters for redudancy...

thanks
if you are right, a star will be awarded

 

[p5wizard]

on VIOS:

lsmap -all

will give you the mapping between vhost adapters and the client LPARs including slot numbers, also the devices that are served on the vhost adapters


HTH,

p5wizard

 

[p5wizard]

I checked - mapping between Virtual SCSI vhost on VIOS and vscsi on client can only be seen on HMC. That is why I use the same virtual slot number for vhost adapter and vscsi adapter when creating the adapter pair.


HTH,

p5wizard