< draft-ietf-imss-fc-zs-mib-02.txt		draft-ietf-imss-fc-zs-mib-03.txt >
	Internet Draft C. DeSanti		Internet Draft C. DeSanti
	H.K. Vivek		H.K. Vivek
	K. McCloghrie		K. McCloghrie
	Cisco Systems		Cisco Systems
	S. Gai		S. Gai
	8 January 2007		24 January 2007
	Fibre-Channel Zone Server MIB		Fibre-Channel Zone Server MIB
	draft-ietf-imss-fc-zs-mib-02.txt		draft-ietf-imss-fc-zs-mib-03.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 2, line 11 ¶		skipping to change at page 2, line 11 ¶
	for use with network management protocols in the Internet community.		for use with network management protocols in the Internet community.
	In particular, it describes managed objects for information related		In particular, it describes managed objects for information related
	to a Fibre Channel Zone Server.		to a Fibre Channel Zone Server.
	Table of Contents		Table of Contents
	1 Introduction ................................................. 3		1 Introduction ................................................. 3
	1.1 Change Log ................................................. 3		1.1 Change Log ................................................. 3
	2 The Internet-Standard Management Framework ................... 7		2 The Internet-Standard Management Framework ................... 7
	3 Overview of Fibre Channel .................................... 7		3 Overview of Fibre Channel .................................... 7
	3.1 General Overview ........................................... 7		3.1 General Overview ........................................... 8
	3.2 Zoning ..................................................... 8		3.2 Zoning ..................................................... 8
	3.3 Zoning Configuration and Management ........................ 9		3.3 Zoning Configuration and Management ........................ 9
	4 Relationship to Other MIBs ................................... 11		4 Relationship to Other MIBs ................................... 12
	5 MIB Overview ................................................. 12		5 MIB Overview ................................................. 12
	5.1 Fibre Channel management instance .......................... 12		5.1 Fibre Channel management instance .......................... 12
	5.2 Switch Index ............................................... 13		5.2 Switch Index ............................................... 13
	5.3 Fabric Index ............................................... 13		5.3 Fabric Index ............................................... 13
	5.4 Locking the Fabric ......................................... 13		5.4 Locking the Fabric ......................................... 13
	5.5 Basic and Enhanced Modes ................................... 14		5.5 Basic and Enhanced Modes ................................... 14
	5.6 Persistent Storage ......................................... 15		5.6 Persistent Storage ......................................... 15
	5.7 The Active Zone Set and the Zone Set Database .............. 15		5.7 The Active Zone Set and the Zone Set Database .............. 15
	5.8 Conformance Groups ......................................... 16		5.8 Conformance Groups ......................................... 16
	6 The T11-FC-FABRIC-LOCK-MIB Module ............................ 18		6 The T11-FC-FABRIC-LOCK-MIB Module ............................ 18
	skipping to change at page 6, line 44 ¶		skipping to change at page 6, line 44 ¶
	t11ZsZoneMemberTable and t11ZsAttribBlockTable explaining their		t11ZsZoneMemberTable and t11ZsAttribBlockTable explaining their
	fate-sharing relationships with other tables.		fate-sharing relationships with other tables.
	- Fixed several typos.		- Fixed several typos.
	1.1.6. 8 January 2007 version		1.1.6. 8 January 2007 version
	The following changes were made for the version was submitted to the		The following changes were made for the version was submitted to the
	IETF as: draft-ietf-imss-fc-zs-mib-02.txt.		IETF as: draft-ietf-imss-fc-zs-mib-02.txt.
	- Inserted references to [FC-SW-5] to replace the "TBD" for the		- Inserted references to FC-SW-5 to replace the "TBD" for the
	reference to the assignment of an Application_ID value for the		reference to the assignment of an Application_ID value for the
	benefit of this MIB module.		benefit of this MIB module.
	- fixed typos.		- fixed typos.
	- added IETF IMSS WG to the ORGANIZATION clause.		- added IETF IMSS WG to the ORGANIZATION clause.
	- Changed year in copyright dates to 2007.		- Changed year in copyright dates to 2007.
	- Included a reference to RFC 3584.		- Included a reference to RFC 3584.
	skipping to change at page 7, line 21 ¶		skipping to change at page 7, line 21 ¶
	- Updated the SIZE clause of t11ZsActiveAttribValue.		- Updated the SIZE clause of t11ZsActiveAttribValue.
	- Included a statement in t11ZsNotifyControlEntry on the persistency		- Included a statement in t11ZsNotifyControlEntry on the persistency
	of read-write data in rows of the t11ZsNotifyControlTable.		of read-write data in rows of the t11ZsNotifyControlTable.
	- Removed the statement specifying the meaning of non-instantiated		- Removed the statement specifying the meaning of non-instantiated
	instances of t11FLockInitiatorIpAddrType & t11FLockInitiatorIpAddr,		instances of t11FLockInitiatorIpAddrType & t11FLockInitiatorIpAddr,
	and clarified the meaning of "request" in the DESCRIPTION of		and clarified the meaning of "request" in the DESCRIPTION of
	t11FLockInitiatorIpAddr.		t11FLockInitiatorIpAddr.
			1.1.7. 24 January 2007 version
			The following changes were made for the version was submitted to the
			IETF as: draft-ietf-imss-fc-zs-mib-03.txt.
			- Removed all references to the incomplete FC-SW-5 specification so
			that this document can proceed without delay.
	2. The Internet-Standard Management Framework		2. The Internet-Standard Management Framework
	For a detailed overview of the documents that describe the current		For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of		Internet-Standard Management Framework, please refer to section 7 of
	RFC 3410 [RFC3410].		RFC 3410 [RFC3410].
	Managed objects are accessed via a virtual information store, termed		Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally		the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).		accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the		Objects in the MIB are defined using the mechanisms defined in the
	skipping to change at page 11, line 14 ¶		skipping to change at page 11, line 26 ¶
	session can be established. The subsequent SSE request causes a		session can be established. The subsequent SSE request causes a
	Release Change Authorization (RCA) request to all other switches, and		Release Change Authorization (RCA) request to all other switches, and
	thus, the fabric to be unlocked.		thus, the fabric to be unlocked.
	For at least one application other than Zoning, the managing switch		For at least one application other than Zoning, the managing switch
	uses a different type of request to lock the fabric, i.e., it sends		uses a different type of request to lock the fabric, i.e., it sends
	an Enhanced Acquire Change Authorization (EACA) request to all other		an Enhanced Acquire Change Authorization (EACA) request to all other
	switches in the fabric. An EACA reserves local resources associated		switches in the fabric. An EACA reserves local resources associated
	with a designated application to ensure the consistency of that		with a designated application to ensure the consistency of that
	application's data. The application is identified in the EACA using		application's data. The application is identified in the EACA using
	an Application_ID (see Table 116 in [FC-SW-5]). A lock which was		an Application_ID (see Table 116 in [FC-SW-4]). A lock which was
	established via an EACA is released using an Enhanced Release Change		established via an EACA is released using an Enhanced Release Change
	Authorization (ERCA) request.		Authorization (ERCA) request.
	Changes requested in a Zoning Database by Enhanced Zoning commands		Changes requested in a Zoning Database by Enhanced Zoning commands
	persist after the end of the Zoning (server) session only if the		persist after the end of the Zoning (server) session only if the
	commands are followed, within the same server session, by a Commit		commands are followed, within the same server session, by a Commit
	Zone Changes (CMIT) request. On receipt of a CMIT request, the Zone		Zone Changes (CMIT) request. On receipt of a CMIT request, the Zone
	Server checks that the Zoning Database as modified by the outstanding		Server checks that the Zoning Database as modified by the outstanding
	changes will pass the applicable consistency checks, and then		changes will pass the applicable consistency checks, and then
	distributes it to all other switches in the fabric using a Stage		distributes it to all other switches in the fabric using a Stage
	skipping to change at page 21, line 28 ¶		skipping to change at page 21, line 28 ¶
	the 'managing' switch, sending Acquire Change Authorization		the 'managing' switch, sending Acquire Change Authorization
	(ACA) requests to all other switches in the fabric.		(ACA) requests to all other switches in the fabric.
	For other applications, a fabric lock is established by the		For other applications, a fabric lock is established by the
	'managing' switch sending Enhanced Acquire Change		'managing' switch sending Enhanced Acquire Change
	Authorization (EACA) requests to other switches in the		Authorization (EACA) requests to other switches in the
	fabric. Each EACA request includes an Application_ID		fabric. Each EACA request includes an Application_ID
	value to identify the application requesting the lock.		value to identify the application requesting the lock.
	For the benefit of this MIB module, a distinct value of		For the benefit of this MIB module, a distinct value of
	Application_ID has also been assigned/reserved (see FC-SW-5)		Application_ID has also been assigned/reserved (see
	as a means of distinguishing locks established via Acquire		ANSI INCITS T11/06-679v0, entitiled 'FC-SW-5 Letter to
	Change Authorization (ACA) requests. This additional		T11.5') as a means of distinguishing locks established via
	assignment allows an Application_ID to be used to uniquely		Acquire Change Authorization (ACA) requests. This
	identify any active lock amongst all those established		additional assignment allows an Application_ID to be used to
	either by an EACA or by an ACA.		uniquely identify any active lock amongst all those
			established either by an EACA or by an ACA.
	Whenever a fabric is locked, by the sending of either an ACA		Whenever a fabric is locked, by the sending of either an ACA
	or an EACA, a row gets created in the representation of this		or an EACA, a row gets created in the representation of this
	table for the 'managing' switch.		table for the 'managing' switch.
	In order to process SNMP SetRequests which make parameter		In order to process SNMP SetRequests which make parameter
	changes for the relevant types of servers (e.g., to the		changes for the relevant types of servers (e.g., to the
	Zoning Database), the SNMP agent must get serialized access		Zoning Database), the SNMP agent must get serialized access
	to the fabric (for the relevant type of management data),		to the fabric (for the relevant type of management data),
	i.e., the fabric must be locked by creating an entry in		i.e., the fabric must be locked by creating an entry in
	skipping to change at page 22, line 28 ¶		skipping to change at page 22, line 29 ¶
	FC-GS-5 mentions various error situations in which a		FC-GS-5 mentions various error situations in which a
	fabric lock is released so as to avoid a deadlock. In		fabric lock is released so as to avoid a deadlock. In
	such situations, the agent removes the corresponding row		such situations, the agent removes the corresponding row
	in this table as and when the lock is released. This can		in this table as and when the lock is released. This can
	happen for all values of t11FLockInitiatorType."		happen for all values of t11FLockInitiatorType."
	REFERENCE		REFERENCE
	"Fibre Channel - Generic Services-5 (FC-GS-5),		"Fibre Channel - Generic Services-5 (FC-GS-5),
	ANSI INCITS 427-2006, sections 4.9.5.5 and 6.4.7.1.		ANSI INCITS 427-2006, sections 4.9.5.5 and 6.4.7.1.
	Fibre Channel - Switch Fabric-4 (FC-SW-4),		Fibre Channel - Switch Fabric-4 (FC-SW-4),
	ANSI INCITS 418-2006, sections 6.1.17, 10.6.6 and 13.2.		ANSI INCITS 418-2006, sections 6.1.17, 10.6.6 and 13.2,
			and table 116.
	'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,		'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,
	http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,		http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,
	21 September, 2006.		21 September, 2006."
	Fibre Channel - Switch Fabric-5 (FC-SW-5),
	T11/Project 1674-D/Rev 8.0, table 116."
	INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FLockFabricIndex,		INDEX { fcmInstanceIndex, fcmSwitchIndex, t11FLockFabricIndex,
	t11FLockApplicationID }		t11FLockApplicationID }
	::= { t11FLockTable 1 }		::= { t11FLockTable 1 }
	T11FLockEntry ::= SEQUENCE {		T11FLockEntry ::= SEQUENCE {
	t11FLockFabricIndex T11FabricIndex,		t11FLockFabricIndex T11FabricIndex,
	t11FLockApplicationID OCTET STRING,		t11FLockApplicationID OCTET STRING,
	t11FLockInitiatorType INTEGER,		t11FLockInitiatorType INTEGER,
	t11FLockInitiator OCTET STRING,		t11FLockInitiator OCTET STRING,
	t11FLockInitiatorIpAddrType InetAddressType,		t11FLockInitiatorIpAddrType InetAddressType,
	skipping to change at page 23, line 41 ¶		skipping to change at page 23, line 41 ¶
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The Application_ID value which identifies the type of		"The Application_ID value which identifies the type of
	application for which the fabric is locked.		application for which the fabric is locked.
	A lock established via Acquire Change Authorization (ACA)		A lock established via Acquire Change Authorization (ACA)
	does not, strictly speaking, have an Application_ID value.		does not, strictly speaking, have an Application_ID value.
	However, the value 'FF'h (255 decimal) has been reserved		However, the value 'FF'h (255 decimal) has been reserved
	by T11 to be used as the value of this MIB object as and		by T11 to be used as the value of this MIB object as and
	when a lock is established by an ACA. This value was		when a lock is established by an ACA. This value was
	initially documented in an approved letter from the FC-SW-5		initially documented in a letter from the FC-SW-5 Editor
	Editor to T11.5, and subsequently in FC-SW-5."		to T11.5, which was approved by the T11 and T11.5 plenary
			meetings on October 5, 2006."
	REFERENCE		REFERENCE
	"Fibre Channel - Switch Fabric-4 (FC-SW-4),		"Fibre Channel - Switch Fabric-4 (FC-SW-4),
	ANSI INCITS 418-2006, April 2006, table 116.		ANSI INCITS 418-2006, April 2006, table 116.
	'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,		'FC-SW-5 Letter to T11.5' ANSI INCITS T11/06-679v0,
	http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,		http://www.t11.org/ftp/t11/pub/fc/sw-5/06-679v0.pdf,
	21 September, 2006.		21 September, 2006."
	Fibre Channel - Switch Fabric-5 (FC-SW-5),
	T11/Project 1674-D/Rev 8.0, table 116."
	::= { t11FLockEntry 2 }		::= { t11FLockEntry 2 }
	t11FLockInitiatorType OBJECT-TYPE		t11FLockInitiatorType OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	other(1),		other(1),
	ssb(2),		ssb(2),
	cli(3),		cli(3),
	snmp(4)		snmp(4)
	}		}
	MAX-ACCESS read-only		MAX-ACCESS read-only
	skipping to change at page 89, line 25 ¶		skipping to change at page 89, line 25 ¶
	[FC-GS-4]		[FC-GS-4]
	"Fibre Channel - Generic Services - 4 (FC-GS-4)", ANSI INCITS		"Fibre Channel - Generic Services - 4 (FC-GS-4)", ANSI INCITS
	387-2004, http://www.t11.org/t11/stat.nsf/upnum/1505-d, February		387-2004, http://www.t11.org/t11/stat.nsf/upnum/1505-d, February
	2004.		2004.
	[FC-SW-4]		[FC-SW-4]
	"Fibre Channel - Switch Fabric - 4 (FC-SW-4)", ANSI INCITS		"Fibre Channel - Switch Fabric - 4 (FC-SW-4)", ANSI INCITS
	418-2006, http://www.t11.org/ftp/t11/pub/fc/sw-4/06-296v0.pdf 4		418-2006, http://www.t11.org/ftp/t11/pub/fc/sw-4/06-296v0.pdf 4
	April 2006.		April 2006.
	[FC-SW-5]
	"Fibre Channel - Switch Fabric - 5 (FC-SW-5)", T11/Project
	1674-D/Rev 8.0, http://www.t11.org/t11/stat.nsf/upnum/06-804v0.pdf,
	22 November 2006.
	[FC-FS]		[FC-FS]
	"Fibre Channel - Framing and Signaling (FC-FS)", ANSI INCITS		"Fibre Channel - Framing and Signaling (FC-FS)", ANSI INCITS
	373-2003, April 2003.		373-2003, April 2003.
	[RFC4001]		[RFC4001]
	Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder,		Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder,
	"Textual Conventions for Internet Network Addresses", RFC 4001,		"Textual Conventions for Internet Network Addresses", RFC 4001,
	February 2005.		February 2005.
	[RFC4044]		[RFC4044]
	skipping to change at page 92, line 39 ¶		skipping to change at page 92, line 39 ¶
	Retired		Retired
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007). This document is subject to the		Copyright (C) The IETF Trust (2007). This document is subject to the
	rights, licenses and restrictions contained in BCP 78, and except as		rights, licenses and restrictions contained in BCP 78, and except as
	set forth therein, the authors retain all their rights.		set forth therein, the authors retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES,		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	PURPOSE.
	Disclaimer of validity		Disclaimer of validity
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
End of changes. 14 change blocks.
	34 lines changed or deleted		33 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/