1) Yes, as alluded to in the iSNS draft. You understood it well.
2) You are welcome to write a paper or RFC if you desire. I am
willing to help you out.
From: dan yo
Sent: Sunday, September 28, 2003
Subject: [Ips] iSNS: question on
exporting FC Zone DB to iSNS DB
I would like to get
some opinions and thoughts on mapping FC Zone Server DB
to iSNS DB in a
single or multiple fabrics, mixed protocol SAN switches
Based on my understanding
of the FC-GS, FC-SW, and the iSNS draft, FC zone
objects are mapped to
iSNS objects as follow:
FC zone maps
to iSNS DD (Discovery Domain).
FC zone set maps
to iSNS DD Set.
FC fabric maps to
iSNS Network Entity.
Assume we have a
multi-fabric SAN with mixed FC and iSCSI switches,
We want to create a
central iSNS database to store all the devices,
where some of the devices
are exported from the FC zone DBs, and some
are registered from
the iSNS capable clients (most likely iSCSI devices).
With the central iSNS
server, iSNS capable management stations now
have a full view of the
whole multi-fabric SAN.
1. Would iSNS serve
well for the above application?
2. When FC Zone DBs are
merged or segmented, how the FC Zone DBs
synchronized with the iSNS DB is an implementation issue, but
anybody written any guideline or paper on this?
not, would this subject be a good ietf draft/rfc candidate?
3. Is there any such
product on the market from the major SAN switch
manufacturers (that exports and maps FC Zone DB to iSNS server)?
Do you Yahoo!?
New Yahoo! Shopping - with improved product search
All information transmitted hereby is intended only for the use of the
addressee(s) named above and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
of confidential and privileged information is prohibited. If the reader
of this message is not the intended recipient(s) or the employee or agent
responsible for delivering the message to the intended recipient, you are
herby notified that you must not read this transmission and that disclosure,
copying, printing, distribution or use of any of the information contained
in or attached to this transmission is STRICTLY PROHIBITED.
Anyone who receives confidential and privileged information in error should
notify us immediately by telephone and mail the original message to us at
the above address and destroy all copies. To the extent any portion of this
communication contains public information, no such restrictions apply to that