VPD Page 83 for virtual luns or logical volumes

[George Ericson]

* From the T10 Reflector (t10 at t10.org), posted by:
* "George Ericson" <GEricson at TownISP.com>
*
Using IEEE Registered Extended Names to form a 128 bit Device ID is
recommended practice.

This from of Section 8.8.4 in SPC2.

NOTE 62 In the case of virtual logical units (e.g., volume sets as defined
by SCC), the Identifier field (see table 111)should be an IEEE Registered
Extended name. The IEEE Registered Extended name has a code of 3h in the
Identifier type field and an NAA value of 0110b as defined in FC-PH, FC-PH-3
or FC-FS.

George

-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org]On Behalf Of John
Tyndall
Sent: Wednesday, November 21, 2001 10:30 AM
To: t10 at t10.org
Subject: VPD Page 83 for virtual luns or logical volumes


* From the T10 Reflector (t10 at t10.org), posted by:
* "John Tyndall" <jtyndall at Crossroads.com>
*

I am trying to gather information on how logical (vs. physical) devices
are expected to respond to a request for the inquiry page 0x83 vpd page.
Bridges and raid controllers have to come up with some way of returning
a guaranteed unique name for a logical volume or an internally
configured logical unit. We have kicked around the idea of reserving
extra WWN type names, but it can be somewhat difficult to predict how
many are needed. We have also considered using an extended form such as
IEEE Registered Extended Name (Format 6), but the larger size may cause
difficulties. Is there any consensus on the proper way to deal with
this?

John Tyndall
Architect
Crossroads Systems Inc.
Email  : jtyndall at crossroads.com
Phone : 512-928-7282

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org 

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org