The date is required by the spec: (RFC 3720, section 3.2.6.3.1)
Since a domain name can expire, be acquired by another entity, or may
be used to generate iSCSI names by both owners, the domain name must
be additionally qualified by a date during which the naming authority
owned the domain name. For this reason, a date code is provided as
part of the "iqn." format.
The iSCSI qualified name string consists of:
- The string "iqn.", used to distinguish these names from "eui."
formatted names.
- A date code, in yyyy-mm format. This date MUST be a date
during which the naming authority owned the domain name used in
this format, and SHOULD be the first month in which the domain
name was owned by this naming authority at 00:01 GMT of the
first day of the month. This date code uses the Gregorian
calendar. All four digits in the year must be present. Both
digits of the month must be present, with January == "01" and
December == "12". The dash must be included.
- A dot "."
- The reversed domain name of the naming authority (person or
organization) creating this iSCSI name.
- An optional, colon (:) prefixed, string within the character
set and length boundaries that the owner of the domain name
deems appropriate. This may contain product types, serial
numbers, host identifiers, or software keys (e.g., it may
include colons to separate organization boundaries). With the
exception of the colon prefix, the owner of the domain name can
assign everything after the reversed domain name as desired.
It is the responsibility of the entity that is the naming
authority to ensure that the iSCSI names it assigns are
worldwide unique. For example, "Example Storage Arrays, Inc.",
might own the domain name "example.com".
There is no way to force Solaris not to adopt to these controls.
Jeff
Gabriele Bulfon wrote:
Hello,
I'm testing an Adaptec Snap Server 520 with a Sparc Solaris 10 server.
If I work with just one network card (1Gbit) and use dynamic mode, the
discovery runs succesfully and I can mount and use the partition.
Knowing about a previously discussed bug, I was prepared that I had to switch
to static mode, to be able to run round-robin mode over two different LANs
(2Gb).
So I removed any previous dynamic config, and started issuing the static config
commands.
With my surprise, Solaris did not like the iqn format as suggested by the Snap
server.
Infact, the Snap iqn is something like "iqn.snap747174.v250", where the "snap"
portion is the server name defined in the Snap server.
Solaris seems to look for a date after "iqn." and I found no way to let the
Snap server set the iqn that way.
What looks very strange, is that the iqn was accepted by Solaris in dynamic
mode (automatic discovery), but is refused if used manually (static config).
Is there any way to force Solaris to NOT adopt the strict control of the iqn
format?
At the same time I am working with Adaptec to see if they have some way to let
me change the automatic iqn from the machine...
Thanx for any help.
Gabriele.
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
