iSCSI MIB Team Status 50 th IETF - Minneapolis March 2001 Mark - - PowerPoint PPT Presentation

▶
iscsi mib team status
SMART_READER_LITE
LIVE PREVIEW

iSCSI MIB Team Status 50 th IETF - Minneapolis March 2001 Mark - - PowerPoint PPT Presentation

Sep 09, 2022 653 likes •748 views

iSCSI MIB Team Status 50 th IETF - Minneapolis March 2001 Mark Bakke, Cisco Lawrence Lamers, San Valley Sudhakar Chellam, IBM Satish Mali, StoneFly Networks Kevin Gibbons, Nishan Systems Jim Muchow, Cisco Chad Gregory, Intel Hari Mudalier,

slide-1
SLIDE 1

iSCSI MIB Team Status

50th IETF - Minneapolis March 2001

Mark Bakke, Cisco Sudhakar Chellam, IBM Kevin Gibbons, Nishan Systems Chad Gregory, Intel Jack Harwood, EMC John Hufferd, IBM Marjorie Krueger, HP Lawrence Lamers, San Valley Satish Mali, StoneFly Networks Jim Muchow, Cisco Hari Mudalier, Adaptec Ie Wei Njoo, Agilent William Terrell, Troika Networks

slide-2
SLIDE 2

Status

  • iSCSI Object Model

– Model complete; pending input from WG – Includes iSCSI-visible LU and LUN info

  • iSCSI MIB

– New draft out for review – Would like to make this a WG document

  • SCSI MIB

– Team interested in pursing SCSI MIB

slide-3
SLIDE 3

iSCSI MIB Structure

  • Handles multiple targets and initiators
  • Tracks LUs and LUNs in use

Instance ListenPort Session Target Initiator AccessList Connection Lun LU

slide-4
SLIDE 4

Current Work Items

  • LU and LUN representation
  • SCSI MIB would be beneficial

– Work with T10 or other organization?

  • Access Control representation
  • Working on attributes and descriptions
  • Admin/OperStatus, Sets, Traps
slide-5
SLIDE 5

Proposed Changes

  • Add “last error” UTF8String messages
  • Remove enums for digest & auth
  • Add name service attributes to instance

– Allows navigation to an SNS MIB

  • Add “last LUN” for appropriate errors
  • Make LU and LUN tables optional
slide-6
SLIDE 6

Requirements Questions

  • Move LU/LUN to a SCSI MIB?
  • Error tracking – LUN errors, error strings, logs?
  • Statistics and attributes enough or too much?
  • How long should table entries live?
  • Will anyone attempt sets, and which ones?
  • Will users want RowStatus?

– Delete sessions or connections via SNMP?

  • Any new traps required for iSCSI?
  • Have we overlooked any requirements?
slide-7
SLIDE 7

Issues

  • There is no SCSI MIB

– We are breaking layers somewhat in LU object to compensate

  • Access control model

– We have a simple model; is it appropriate? – Is it worth representing in a standard MIB? – Can use table augmentation is proprietary MIB.

  • Publishing object model with MIB
slide-8
SLIDE 8

Plan

  • April 2001

– Collect input from IPS WG – Solicit any new requirements from WG – Publish new draft as WG document

  • June 2001

– Publish second draft of WG document

  • October 2001

– Submit iSCSI MIB draft to IESG