Tech-invite3GPPspaceIETF RFCsSIP
93929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 4939

Definitions of Managed Objects for iSNS (Internet Storage Name Service)

Pages: 80
Proposed Standard
Errata
Part 1 of 4 – Pages 1 to 7
None   None   Next

Top   ToC   RFC4939 - Page 1
Network Working Group                                         K. Gibbons
Request for Comments: 4939                                   2Wire, Inc.
Category: Standards Track                                    G. Ramkumar
                                                          SnapTell, Inc.
                                                                 S. Kipp
                                                           Brocade, Inc.
                                                               July 2007


                Definitions of Managed Objects for iSNS
                    (Internet Storage Name Service)

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 IETF Trust (2007).

Abstract

The iSNS (Internet Storage Name Service) protocol provides storage name service functionality on an IP network that is being used for iSCSI (Internet Small Computer System Interface) or iFCP (Internet Fibre Channel Protocol) storage. This document provides a mechanism to monitor multiple iSNS Servers, including information about registered objects in an iSNS Server.
Top   ToC   RFC4939 - Page 2

Table of Contents

1. The Internet-Standard Management Framework ......................3 2. Introduction ....................................................3 2.1. Requirement Levels .........................................3 3. Technical Description ...........................................4 3.1. iSNS Registered Objects ....................................4 3.2. iSNS MIB Structure .........................................5 3.3. iSNS Server Info ...........................................5 3.3.1. Control Node Information ............................6 3.3.2. Discovery Domain Set (DDS) ..........................6 3.3.3. Discovery Domain (DD) ...............................6 3.3.4. Registered Storage Objects ..........................6 3.3.4.1. Registered Entities ........................6 3.3.4.2. Registered Portals .........................6 3.3.4.3. Registered Portal Groups ...................7 3.3.4.4. Registered iSCSI Nodes .....................7 3.3.4.5. Registered FC Ports ........................7 3.3.4.6. Registered FC Nodes ........................7 3.4. Multiple Server Instances ..................................7 3.5. iSNS Notifications .........................................7 4. MIB References ..................................................7 5. MIB Module ......................................................8 6. IANA Considerations ............................................75 7. Security Considerations ........................................76 8. Normative References ...........................................77 9. Informative References .........................................78 10. Acknowledgements ..............................................78
Top   ToC   RFC4939 - Page 3

1. 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 2580 [RFC2580].

2. Introduction

The iSNS protocol, as described in RFC 4171 [RFC4171], can be used by IP-based storage devices for dynamic registration and discovery of other storage devices in the network. It has the capability to group devices into storage Discovery Domains, and Discovery Domains into Discovery Domain Sets. The iSNS MIB is designed to allow Simple Network Management Protocol (SNMP) to be used to monitor iSNS servers supporting iSCSI [RFC3720] and iFCP [RFC4172].

2.1. Requirement Levels

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 [RFC2119].
Top   ToC   RFC4939 - Page 4

3. Technical Description

3.1. iSNS Registered Objects

The following entity relationship figure indicates the objects that can be registered in the iSNS, and their relationship to each other. +--------------+ +-----------+ | NETWORK |1 *| | | ENTITY |----| PORTAL | | | | | +--------------+ +-----------+ |1 |1 |* | | | | |* | | +----------+ | | | PORTAL | | | | GROUP | | | +----------+ | | |* | | | | |* |1 |* +----------+ +-------------+ +----------+ +-----------+ | FC |1 *| STORAGE |* *| DISCOVERY|* *| DISCOVERY | | DEVICE |----| NODE |----| DOMAIN |----| DOMAIN | | | | | | | | SET | +----------+ +-------------+ +----------+ +-----------+ * represents 0 to many possible relationships
Top   ToC   RFC4939 - Page 5

3.2. iSNS MIB Structure

The MIB is divided into sections for iSNS server information, iSNS server registered objects information, and iSNS notifications. +--------------+ +--------------+ | MANAGED iSNS |1 *| CONTROL NODE | | SERVER |----| INFO | | INFO | +--------------+ +--------------+ |1 |1 | | +--------------+ | | *| DDS AND DD | | +------| INFO | | | | | +--------------+ | | +-------------+ | *| REGISTERED | +------------| ENTITIES | | INFO | +-------------+ +-----------------+ | iSNS | | NOTIFICATION | | INFO | +-----------------+ The sections that are required to implement are for iSNS Server management and notification.

3.3. iSNS Server Info

The isnsServerInfo section provides the ability to monitor multiple iSNS Server instances. The isnsServerTable table provides information on each server instance. This table is indexed by the variable isnsServerIndex. The table indicates current settings for each iSNS server being managed. The network address, TCP and UDP ports being used by a server for iSNSP registrations and queries can be determined from this table. The count of objects registered in each iSNS server instance is shown in the table isnsNumObjectsTable. The provides a summary of the number Discovery Domain Sets, Discovery Domains, Entities, Portals, Portal Groups, iSCSI Nodes, and iFCP FC Nodes and Ports.
Top   ToC   RFC4939 - Page 6

3.3.1. Control Node Information

As defined in the iSNS specification, Control Nodes are objects that have been registered with the server and are allowed to manage the iSNS server. These Control Nodes are identified by their iSCSI Node Name or iFCP FC Port Name. The isnsControlNodeInfo section of the MIB provides the ability to view the currently registered set of iSCSI and iFCP control nodes.

3.3.2. Discovery Domain Set (DDS)

The isnsDdsInfo section provides information on each registered DDS, the Discovery Domain members of each DDS, for each iSNS Server instance being managed. DDSs provide a method to group multiple Discovery Domains for easier control. As described in the iSNS Specification [RFC4171], a DDS can be enabled or disabled, which in turn enables or disables the member Discovery Domains. Discovery Domains that are contained in an enabled DDS are then enforced by an iSNS Server.

3.3.3. Discovery Domain (DD)

The isnsDdInfo section provides information on each registered DD, and the DD members, for each iSNS Server instance being managed. DDs are collections of storage nodes and portals that are allowed to discover one another. DD members can be iSCSI nodes, Entity Portals, or iFCP nodes.

3.3.4. Registered Storage Objects

The isnsReg section provides information on the registered storage objects for a specific iSNS Server instance. This section is divided into subsections for Entities, Portals, and iSCSI Nodes, as well as iFCP Port and Node information.
3.3.4.1. Registered Entities
The isnsRegEntityInfo section provides information on the registered entities. Entities are collections of storage nodes and portals.
3.3.4.2. Registered Portals
The isnsRegPortalInfo section provides information on the registered portals for a specific iSNS Server instance. Portals are logical IP-Address, TCP/UDP Port pairs that provide access to storage nodes contained in the associated Entity.
Top   ToC   RFC4939 - Page 7
3.3.4.3. Registered Portal Groups
The isnsRegPortalGroupInfo section provides information on the registered portal groups for a specific iSNS Server instance. As described in iSCSI [RFC3720], Portal Groups provide a mapping between Portals and iSCSI Storage Nodes contained in an Entity.
3.3.4.4. Registered iSCSI Nodes
The isnsRegIscsiNodeInfo section provides information on the registered iSCSI Nodes for a specific iSNS Server instance. The iSCSI nodes are individual storage targets or initiators.
3.3.4.5. Registered FC Ports
The isnsRegFcPortInfo section provides information on the registered FC Ports for a specific iSNS Server instance. The FC Ports are ports associated with an iFCP gateway.
3.3.4.6. Registered FC Nodes
The isnsRegFcNodeInfo section provides information on the registered FC Nodes for a specific iSNS Server instance. The FC nodes are individual storage devices associated with an iFCP gateway.

3.4. Multiple Server Instances

The management of multiple instances of iSNS servers by the agent is supported. As described in Section 3.3, each managed iSNS server instance has an entry in the table isnsServerTable.

3.5. iSNS Notifications

The isnsNotification section provides SNMP notifications for iSNS Server state changes.

4. MIB References

The following MIB module has IMPORTS from [RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC4001], [RFC4044], and [RFC4133]. In REFERENCE clauses, it also refers to [RFC3720], [RFC4171], and [RFC4172].


(next page on part 2)

Next Section