IPS Working Group INTERNET-DRAFT Ravi Natarajan Lightsand Communications Expires April 2005 Anil Rijhsinghani Accton Technology Corporation October 2004 Definitions of Managed Objects for FCIP Status of this Memo: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt . The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html . This Internet-Draft will expire on Aril 2005. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. 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 FCIP entities, as defined in [FCIP] and used in FC fabrics as described in [FCBB2]. FCIP MIB Expires April 2005 [Page 1] Internet Draft FCIP MIB October 2004 Table of Contents Status of this Memo...............................................1 Copyright Notice..................................................1 Abstract..........................................................1 Table of Contents.................................................2 1. The Internet-Standard Management Framework....................3 2. Overview of FCIP management model.............................3 3. Relationship to other MIBs....................................5 4. Changes from draft-ietf-ips-fcip-mib-05.txt...................6 5. MIB Definitions...............................................8 6. Security Considerations......................................29 7. Intellectual Property........................................29 8. Acknowledgements.............................................30 9. Normative References.........................................30 10. Informative References.......................................31 11. Authors' Addresses...........................................31 12. Disclaimer of Validity.......................................31 13. Copyright Statement..........................................32 FCIP MIB Expires April 2005 [Page 2] Internet Draft FCIP MIB October 2004 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. Overview of FCIP management model Note that the FCIP Entity is fully described in [FCIP] from a functional point of view. A collection of multiple instances of FCIP Entities and the corresponding FC Entities, described in [FCBB2], within an SNMP Context is referred to as an FCIP device here. This section describes FCIP from a management point of view. +------------------------------------------+ | FCIP Device | | | | +-----------+ +-----------+ | | |FCIP Entity| |FCIP Entity| | | | | | | | | | | | | | | +--+--+--+--+ +--+--+--+--+ | | | | | | | | | | | | | | | | | | FCIP Links FCIP Links | | | +------------------------------------------+ The FCIP device provides IP-based interconnection model to interconnect FC fabric elements. In this model, the FCIP devices along with the IP network on which they are running provide a new FCIP transport network. This IP-based FCIP Interconnection Model supports the following topology: o The FCIP-based transport network is formed by interconnecting the FCIP-devices. o Each FCIP device has one or more FCIP Entities or Instances. FCIP MIB Expires April 2005 [Page 3] Internet Draft FCIP MIB October 2004 o Peer FCIP Entities are connected by FCIP Links, attached to VE_ports/B_Access. o Each FCIP Link Endpoint contains one or more Data Engines. o The FCIP device can work as a standalone box or as part of a FC fabric element. Each FCIP Entity managed by this MIB is referred to as a FCIP Instance. The MIB is broken up as follows: 2.1 FCIP Entity Instances Table The FCIP Entity table contains information about this entity's existing instances of FCIP entities. 2.2 FCIP Link Table The FCIP link table contains information about this FCIP device's existing FCIP links. 2.3 FCIP TCP Connection Table The FCIP TCP Connection table contains information about existing TCP connections. Each FCIP link within a FCIP entity contains one or more TCP connections. The FCIP entity employs a Data Engine for each TCP connection for handling FC frame encapsulation, de-encapsulation and transmission of FCIP frames on the connection. 2.4 FCIP Dynamic Route Table The FCIP dynamic route table contains routing information that is dynamically discovered by this FCIP device. The FCIP device may use the SLPv2 protocol in conjunction with other protocols, such as FSPF, to dynamically discover other FCIP entities, and populate this table to map destination domains to FCIP Links. 2.5 FCIP Static Route Table The FCIP static route table contains routing information that is statically configured into this FCIP device by Network Admin. In the absence of dynamic discovery of remote FCIP entities, the Network Manager can configure remote domains and FCIP Entities that are reachable by this device into this table. At any point of time, both the static and dynamic routing tables can be active. If a DID is present in both tables, information in the static route table will take precedence over the entry in the dynamic route table for the same DID. 2.6 FCIP Discovery Domain Table The FCIP Discovery Domain Table maps this device's FCIP Entities into FCIP Discovery Domains. FCIP MIB Expires April 2005 [Page 4] Internet Draft FCIP MIB October 2004 2.7 FCIP Link Error Table The FCIP Link Errors Table contains counters that indicate error conditions on an FCIP Link. 3. Relationship to other MIBs Objects accessible from other MIBs applicable to FCIP devices have not been included in this MIB. The following lists all applicable MIB modules/objects that should be present with FCIP-MGMT-MIB. 3.1 Relationship to the 'TCP' group of MIB-II This group is mandatory for all systems which implement TCP. Objects relevant to TCP must be obtained from this group. 3.2 Relationship to the 'interfaces' MIB The 'interfaces' group is defined as being mandatory for all systems and contains information on an entity's interfaces. Each logical/virtual interface created as an FCIP Link should be represented as a row in the ifTable with a unique ifIndex value and a value of ifType 'fcipLink' (224) for each such interface. For a complete list of interface types, refer to the IANA registry at "ftp://ftp.isi.edu/mib/iana.mib/ianaiftype.mib". These are the only ifIndex values of relevance to an FCIP Entity because FCIP runs on top of TCP/IP. When an FCIP entity has data to transmit to a peer FCIP entity, it gives it to TCP, and TCP formats the data into segments and gives them to IP; IP puts the data into datagrams which it sends on whatever one or more physical interfaces IP has available. Therefore, only IP, not an FCIP Entity, has knowledge of the ifIndex values for physical interfaces. 3.3 Relationship to the Fibre Channel Management MIB The Fibre Channel Management MIB [FCMGMT] is assumed for FC functionality managed objects. 3.4 Specific Interface Group MIB Objects The following table provides specific implementation guidelines for applying the objects defined in the Interfaces Group MIB to FCIP Links. For those objects not listed here, refer to their generic definitions in [RFC2863]. Object Guidelines ifType 'fcipLink' (224) FCIP MIB Expires April 2005 [Page 5] Internet Draft FCIP MIB October 2004 ifSpeed The ifSpeed for the physical interface(s) over which the FCIP Link runs. ifPhysAddress There is no physical address corresponding to an FCIP Link (only WWN). Reported as 0. ifAdminStatus Write access is not required, and support for 'testing' is not required. ifOperStatus Support for 'testing' is not required. The value 'dormant' has no meaning for FCIP Links. ifInOctets The number of octets of FCIP information ifHCInOctets contained in received frames in TCP streams, starting with FCIP header. ifInUcastPkts The number of FCIP frames received ifHCInUcastPkts on this FCIP Link. ifOutOctets The number of octets of FCIP information ifHCOutOctets contained in transmitted frames in TCP streams, starting with FCIP header. ifOutUcastPkts The number of FCIP frames transmitted ifHCOutUcastPkts on this FCIP Link. ifInMulticastPkts These counters are not incremented. ifInBroadcastPkts ifOutMulticastPkts ifOutBroadcastPkts ifHCInMulticastPkts ifHCInBroadcastPkts ifHCOutMulticastPkts ifHCOutBroadcastPkts ifLinkUpDownTrapEnable Default is 'disabled'. ifPromiscuousMode This will be 'false' ifConnectorPresent This will be 'false'. 4. Changes from draft-ietf-ips-fcip-mib-05.txt o Added ASCII picture depicting FCIP Device/Entity/Link. o Added 'fcipLink' value and IANA URL for ifType MIB. FCIP MIB Expires April 2005 [Page 6] Internet Draft FCIP MIB October 2004 o Clarification of Static and Dynamic table conflict resolution. o Syntax for fcipEntityName and fcipDiscoveryDomainName changed from DisplayString to SnmpAdminString. o Several boilerplate and typo corrections. o Description of fcipEntityRowStatus, fcipLinkStatus and fcipStaticRouteStatus updated to describe behavior when status is set to active(1) and destroy(6). FCIP MIB Expires April 2005 [Page 7] Internet Draft FCIP MIB October 2004 5. FCIP-MGMT-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, MODULE-IDENTITY, Unsigned32, Counter32, mib-2 FROM SNMPv2-SMI TEXTUAL-CONVENTION, TruthValue, RowStatus FROM SNMPv2-TC InetAddressType, InetAddress FROM INET-ADDRESS-MIB FcNameIdOrZero FROM FC-MGMT-MIB InterfaceIndex FROM IF-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF SnmpAdminString FROM SNMP-FRAMEWORK-MIB; fcipMIB MODULE-IDENTITY LAST-UPDATED "200410180000Z" ORGANIZATION "IETF IPFC Working Group" CONTACT-INFO "Anil Rijhsinghani Accton Technology Corporation 5 Mount Royal Ave Marlboro, MA 01752 USA. Ravi Natarajan LightSand Communications Inc, 279 Sinclair Frontage Road Milpitas, CA 95035 USA. Email: ravin@lightsand.com" DESCRIPTION "The module defines management information specific to FCIP devices. Copyright (C) The Internet Society (2004). This version of this MIB module is part of RFC xxxx; see the RFC itself for full legal notices." REVISION "200410180000Z" DESCRIPTION "Initial version of the FCIP MIB module." ::= { mib-2 XXX } -- TO BE ASSIGNED by IANA fcipObjects OBJECT IDENTIFIER ::= { fcipMIB 1 } fcipConformance OBJECT IDENTIFIER ::= { fcipMIB 2 } fcipConfig OBJECT IDENTIFIER ::= { fcipObjects 1 } FCIP MIB Expires April 2005 [Page 8] Internet Draft FCIP MIB October 2004 -- ****************************************************************** -- Textual conventions -- FcDomainId ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The Domain ID of a FC entity." SYNTAX OCTET STRING (SIZE(1)) FcEntityMode ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of port mode provided by an FCIP Entity for a FCIP Link. An FCIP Entity can be an E-Port mode for one of its FCIP Link Endpoints, an B-Port mode for another of its FCIP Link Endpoints." SYNTAX INTEGER { ePortMode(1), bPortMode(2) } -- ****************************************************************** -- The FCIP group -- -- This group defines the global scalar objects applicable to FCIP -- devices only 9. Normative References: [FCIP] Rajagopal, M., et al "Fibre Channel Over TCP/IP (FCIP)", , August 2002. [FCBB2] Fibre Channel Backbone -2 v6 (FC-BB-2), T11/03-078v0, February 2003. [FCMGMT] McCloghrie, K., "Fibre Channel Management MIB", , February 2003. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. FCIP MIB Expires April 2005 [Page 30] Internet Draft FCIP MIB October 2004 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC1323] Jacobson, V., Braden, R. and D. Borman, "TCP Extensions for High Performance", RFC 1323, May 1992. [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the DS Field in the IPv4 Headers", RFC 2474, December 1998. 10. Informative References [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet- Standard Management Framework", RFC 3410, December 2002. 11. Authors' Addresses Anil Rijhsinghani Accton Technology Corporation 5 Mount Royal Ave Marlboro, MA 01752 USA Ravi Natarajan LightSand Communications, Inc. 279 Sinclair Frontage Road Milpitas, CA 95035 USA E-mail: ravin@lightsand.com 12. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE FCIP MIB Expires April 2005 [Page 31] Internet Draft FCIP MIB October 2004 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 13. Copyright Statement Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. FCIP MIB Expires April 2005 [Page 32]