[imss] Changes to draft-ietf-imss-fc-fam-mib-00.txt

Keith McCloghrie <kzm@cisco.com> Sun, 05 December 2004 17:27 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23539 for <imss-web-archive@ietf.org>; Sun, 5 Dec 2004 12:27:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cb0GL-0003YH-H6 for imss-web-archive@ietf.org; Sun, 05 Dec 2004 12:33:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cb01D-00008n-7N; Sun, 05 Dec 2004 12:17:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CazyE-000788-QK for imss@megatron.ietf.org; Sun, 05 Dec 2004 12:14:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22594 for <imss@ietf.org>; Sun, 5 Dec 2004 12:14:48 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cb04P-0003ID-K3 for imss@ietf.org; Sun, 05 Dec 2004 12:21:14 -0500
Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 05 Dec 2004 10:22:24 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from cisco.com (cypher.cisco.com [171.69.11.142]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB5HEDD9027712; Sun, 5 Dec 2004 09:14:13 -0800 (PST)
Received: (from kzm@localhost) by cisco.com (8.8.8-Cisco List Logging/8.8.8) id JAA09001; Sun, 5 Dec 2004 09:14:15 -0800 (PST)
From: Keith McCloghrie <kzm@cisco.com>
Message-Id: <200412051714.JAA09001@cisco.com>
To: imss@ietf.org, t11_5@mail.t11.org (T11.5)
Date: Sun, 5 Dec 2004 09:14:15 -0800 (PST)
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: Keith McCloghrie <kzm@cisco.com>
Subject: [imss] Changes to draft-ietf-imss-fc-fam-mib-00.txt
X-BeenThere: imss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet and Management Support for Storage Working Group <imss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:imss@ietf.org>
List-Help: <mailto:imss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/imss>, <mailto:imss-request@ietf.org?subject=subscribe>
Sender: imss-bounces@ietf.org
Errors-To: imss-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit

Hi,

One of the items raised in the IMSS WG at the last IETF meeting in
Washington was that of updating draft-ietf-imss-fc-fam-mib-00.txt in
accordance with the latest agreements in T11.  An earlier revision of
the I-D (draft-desanti-fc-domain-manager-00.txt, dated January 2004)
contained two extra objects and an extra enumerated value for the
T11FamState TC.  At that earlier date, T11.5 decided that it was
"premature" to define these, and they were deleted from subsequent
revisions.

The following text was recently added to FC-SW-4 (in section 7.1):

   Domain_IDs may be assigned statically or dynamically. When
   Domain_IDs are assigned statically, the administrator shall
   configure a Domain_ID and a Fabric_Name on each Switch of the
   Fabric, and the operations described in 7.3 and 7.4 shall not be
   performed by a Switch. When Domain_IDs are assigned dynamically, the
   operations described in 7.3 and 7.4 shall be performed by a Switch.

Based on this addition to FC-SW-4, it is proposed that having the
extra objects/enumeration is no longer "premature", and thus, that they
should now be added.  Here are the specific objects and enumeration:

- additional enumeration to T11FamState:

                       disabled(11),

- two additional objects in the t11FamTable:

  t11FamEnable OBJECT-TYPE
      SYNTAX      TruthValue
      MAX-ACCESS  read-write
      STATUS      current
      DESCRIPTION
             "Enables the Fabric Address Manager on this switch
             on this Fabric.

             If enabled on a Fabric, the switch will participate
             in principal switch selection.  If disabled, the
             switch will participate in neither the principal
             switch selection nor domain allocation.  Thus, the
             corresponding value of t11FamConfigDomainIdType
             needs to be 'static'."
      DEFVAL  { true }
      ::= { t11FamEntry 26 }

  t11FamFabricName  OBJECT-TYPE
      SYNTAX      FcNameIdOrZero
      MAX-ACCESS  read-write
      STATUS      current
      DESCRIPTION
             "The WWN that is configured on this switch to be
             used as the name of this Fabric when the value of
             t11FamEnable is 'false'.

             If the value of t11FamEnable is 'true', this value
             is not used."
      ::= { t11FamEntry 27 }

Are we agreed on this ?

Keith.

_______________________________________________
imss mailing list
imss@ietf.org
https://www1.ietf.org/mailman/listinfo/imss