Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)
RFC 4544
Document | Type |
RFC - Proposed Standard
(May 2006; Errata)
Obsoleted by RFC 7147
|
|
---|---|---|---|
Authors | Tom McSweeney , Marjorie Krueger , James Muchow , Mark Bakke | ||
Last updated | 2020-01-21 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 4544 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Allison Mankin | ||
Send notices to | bwijnen@lucent.com |
Network Working Group M. Bakke Request for Comments: 4544 Cisco Systems Category: Standards Track M. Krueger Hewlett-Packard T. McSweeney IBM J. Muchow Qlogic Corp. May 2006 Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing a client using the Internet Small Computer System Interface (iSCSI) protocol (SCSI over TCP). Bakke, et al. Standards Track [Page 1] RFC 4544 iSCSI MIB May 2006 Table of Contents 1. Introduction ....................................................3 2. Specification of Requirements ...................................3 3. The Internet-Standard Management Framework ......................3 4. Relationship to Other MIB Modules ...............................3 5. Relationship to SNMP Contexts ...................................4 6. Discussion ......................................................4 6.1. iSCSI MIB Object Model .....................................5 6.2. iSCSI MIB Table Structure ..................................6 6.3. iscsiInstance ..............................................7 6.4. iscsiPortal ................................................7 6.5. iscsiTargetPortal ..........................................9 6.6. iscsiInitiatorPortal .......................................9 6.7. iscsiNode .................................................10 6.8. iscsiTarget ...............................................10 6.9. iscsiTgtAuthorization .....................................11 6.10. iscsiInitiator ...........................................11 6.11. iscsiIntrAuthorization ...................................11 6.12. iscsiSession .............................................11 6.13. iscsiConnection ..........................................12 6.14. IP Addresses and TCP Port Numbers ........................12 6.15. Descriptors: Using OIDs in Place of Enumerated Types .....13 6.16. Notifications ............................................13 7. MIB Definitions ................................................14 8. Security Considerations ........................................79 9. IANA Considerations ............................................80 10. Normative References ..........................................80 11. Informative References ........................................81 12. Acknowledgements ..............................................81 Bakke, et al. Standards Track [Page 2] RFC 4544 iSCSI MIB May 2006 1. Introduction This document defines a MIB module for iSCSI [RFC3720], used to manage devices that implement the iSCSI protocol. 2. Specification of Requirements The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 3. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580Show full document text