1 / 8

iSCSI X-key for enhanced supportability

Understand the X-key protocol extension for iSCSI, solving logging issues, supporting large deployments, and enhancing interoperability. Explore potential challenges, next steps, and where to find more information.

robertwinston
Download Presentation

iSCSI X-key for enhanced supportability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. iSCSI X-key for enhanced supportability David Wysochanskidavidw@netapp.com March 20, 2006

  2. Agenda • What is an X-key? • What problems are you solving? • What are the details of the X-key? • What are the new potential problems? • What are the next steps? • Where can I find more info?

  3. What is an X-key? • What is an X-key? • Small protocol extension allowed by iSCSI RFC • Passed during the iSCSI login sequence • Two types • Vendor specific • Starts with “X-” • Anyone can do these easily • Usually viewed as “one-offs” • IETF / IANA blessed • Starts with “X#” • Must be described by an Informational RFC • Will be viewed as more official

  4. What problems are you solving? • Enhanced logging • Easiest to get logs from your own products • Improve support response • “What version of iSCSI is on the other side?” • Eliminating any back/forth is real savings • Hours, days, weeks,… • Validate configurations / confirm interoperability • Large deployments (one to many) • Blade farm of initiators connected to one target • One initiator connected to many targets

  5. What are the details of the X-key? • X#NodeArchitecture • Declarative iSCSI login key • Analogous to "product tokens“ in HTTP 1.1 • "User-Agent" / "Server" headers • Examples: • User-Agent: CERN-LineMode/2.15 libwww/2.17b3 • Server: Apache/0.8.4 • Possible information • iSCSI version (driver, firmware) • OS / kernel version • Hardware Architecture

  6. What are the new potential problems? • iSCSI interoperability • New key involves login sequence • RFC compliant vendors should be ok • Ignore X-keys they don’t support • Security • Software versions transmitted via plaintext • Hackers could use info if intercepted • RFC will address this • Mandate / recommend a disable mechanism • Misuse / Abuse of the key • Historical misuse of User-Agent (browser wars) • RFC will address this

  7. What are the next steps? • Support / confirmation from IPS WG for ID • Consensus that this is useful / net positive? • Rather not proceed with independent submission • Complete Informational RFC • Interested vendors to implement

  8. Where can I find more information? • Current Internet Draft • http://www.ietf.org/internet-drafts/draft-wysochanski-xkey-iscsi-support-00.txt • http://tinyurl.com/hgfjl • Author / Editor • davidw@netapp.com • IETF IP Storage Working group • ips@ietf.org • References RFCs • 3720: iSCSI • 2616: HTTP 1.1 • http://en.wikipedia.org/wiki/Useragent

More Related