Differences between revisions 7 and 8
Revision 7 as of 2006-06-05 03:19:17
Size: 2314
Editor: localhost
Comment:
Revision 8 as of 2008-04-12 17:50:41
Size: 2322
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
iSNS is a protocol to provide discovery, notification, management and configuration of both ["iSCSI"] as well as FibreChannel initiators and targets in an ["IP"] based ["SAN"]. iSNS is a protocol to provide discovery, notification, management and configuration of both [[iSCSI]] as well as FibreChannel initiators and targets in an [[IP]] based [[SAN]].
Line 8: Line 8:
iSNS is supported by many ["iSCSI"] initiator and target implementations but a good management system and interface is still lacking, possibly limiting the full potential of the protocol. iSNS is supported by many [[iSCSI]] initiator and target implementations but a good management system and interface is still lacking, possibly limiting the full potential of the protocol.
Line 12: Line 12:
iSNS is a protocol defined by the [http://www.ietf.org/html.charters/ips-charter.html IPS] (IP Storage) working group of the ["IETF"].[[BR]]
While it is currently still in draft mode and not an ["RFC"] standard, the iSNS protocol has received support from the industry and most/all iSCSI storage vendors today support iSNS.[[BR]]
iSNS is a protocol defined by the [[http://www.ietf.org/html.charters/ips-charter.html|IPS]] (IP Storage) working group of the [[IETF]].<<BR>>
While it is currently still in draft mode and not an [[RFC]] standard, the iSNS protocol has received support from the industry and most/all iSCSI storage vendors today support iSNS.<<BR>>
Line 18: Line 18:
 * ["TCP"] ["UDP"]: iSNS uses either ["TCP"] or ["UDP"] as its transport protocol. The well known port for iSNS traffic is 3205.  * [[TCP]] [[UDP]]: iSNS uses either [[TCP]] or [[UDP]] as its transport protocol. The well known port for iSNS traffic is 3205.
Line 30: Line 30:
See ["iSNS Preferences"] See [[iSNS_Preferences]]
Line 37: Line 37:
A complete list of iSNS display filter fields can be found in the [http://www.wireshark.org/docs/dfref/i/isns.html display filter reference] A complete list of iSNS display filter fields can be found in the [[http://www.wireshark.org/docs/dfref/i/isns.html|display filter reference]]
Line 44: Line 44:
You cannot directly filter iSNS protocols while capturing. However, if you know the ["TCP"]/["UDP"] port used (see above), you can filter on that one. You cannot directly filter iSNS protocols while capturing. However, if you know the [[TCP]]/[[UDP]] port used (see above), you can filter on that one.
Line 48: Line 48:
 * [http://www.ietf.org/internet-drafts/draft-ietf-ips-isns-22.txt iSNS internet draft]
 * [http://www.ietf.org/html.charters/ips-charter.html IPS workgroup homepage] IP storage workgroup of the ["IETF"]
 * [[http://www.ietf.org/internet-drafts/draft-ietf-ips-isns-22.txt|iSNS internet draft]]
 * [[http://www.ietf.org/html.charters/ips-charter.html|IPS workgroup homepage]] IP storage workgroup of the [[IETF]]

Internet Storage Name Server (iSNS)

iSNS is a protocol to provide discovery, notification, management and configuration of both iSCSI as well as FibreChannel initiators and targets in an IP based SAN.

This protocol is a member of the StorageProtocolFamily.

iSNS is supported by many iSCSI initiator and target implementations but a good management system and interface is still lacking, possibly limiting the full potential of the protocol.

History

iSNS is a protocol defined by the IPS (IP Storage) working group of the IETF.
While it is currently still in draft mode and not an RFC standard, the iSNS protocol has received support from the industry and most/all iSCSI storage vendors today support iSNS.
While the protocol as it is now is not yet a ratified standard/RFC it is semi-widely deployed and it is unlikely that the RFC when it will be published will contain any major changes to the protocol.

Protocol dependencies

  • TCP UDP: iSNS uses either TCP or UDP as its transport protocol. The well known port for iSNS traffic is 3205.

Example traffic

XXX - Add example traffic here (as plain text or Wireshark screenshot).

Wireshark

The iSNS dissector is fully functional.

Preference Settings

See iSNS_Preferences

Example capture file

XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Wireshark can open gzipped files automatically.

Display Filter

A complete list of iSNS display filter fields can be found in the display filter reference

  • Show only the iSNS based traffic:

     isns 

Capture Filter

You cannot directly filter iSNS protocols while capturing. However, if you know the TCP/UDP port used (see above), you can filter on that one.

Discussion

Internet_Storage_Name_Server (last edited 2008-04-12 17:50:41 by localhost)