rfc-4369

Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)

K. Gibbons, C. Monia, J. Tseng, F. Travostino
date2006-01 streamIETF areatsv wgips statusPROPOSED STANDARD pages29 canonicalhttps://www.rfc-editor.org/rfc/rfc4369 doi10.17487/RFC4369
The iFCP protocol (RFC 4172) provides Fibre Channel fabric functionality on an IP network in which TCP/IP switching and routing elements replace Fibre Channel components. The iFCP protocol is used between iFCP Gateways. This document provides a mechanism to monitor and control iFCP Gateway instances, and their associated sessions, using SNMP. [STANDARDS-TRACK]

obsoleted by

Extracted elements (20)

design-rationale §4

A simple integer (ifcpSessionIndex) is used as the session table index rather than a composite of local and remote N_PORT identifiers, because the N_PORT-based index would be complex and difficult to implement.

snmp

design-rationale §4

Low-capacity 32-bit statistics (ifcpSessionLcStatsTable) are provided alongside 64-bit counters because at 1 Gbps a Counter32 wraps approximately every 34 seconds, making Counter32 sufficient only in limited scenarios. The 64-bit table is preferred when supported.

snmp

interoperability-note §4

Each ifcpSessionAttributesTable entry should correspond to an entry in the TCP-MIB tcpConnectionTable (RFC 4022). The InetAddressType values for local and remote portals in the iFCP session table and the TCP-MIB index must match to simplify cross-table lookups. IPv4 sessions may also appear in the legacy tcpConnTable of RFC 2012.

snmp, tcp

normative-requirement §4 REQUIRED

For ifcpSessionLclPrtlAddrType and ifcpSessionRmtPrtlIfAddrType, compliance only requires support for global IPv4 (ipv4(1)) and IPv6 (ipv6(2)) address types.

snmp, ip

normative-requirement §6 RECOMMENDED

Implementers are RECOMMENDED to support SNMPv3 with full cryptographic mechanisms for authentication and privacy. Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED.

snmp, security

normative-requirement §4 REQUIRED

The MODULE-COMPLIANCE statement ifcpGatewayCompliance mandates all four OBJECT-GROUPs: ifcpLclGatewayGroup, ifcpLclGatewaySessionGroup, ifcpLclGatewaySessionStatsGroup, and ifcpLclGatewaySessionLcStatsGroup.

snmp

protocol-element §4

ifcpLclGtwyInstTable provides configuration and status for each local iFCP gateway instance, including version range, address translation mode, FC broadcast support, default IP_TOV, default LTI, and active session count. A single management entity may monitor multiple local gateway instances.

snmp

protocol-element §4

ifcpSessionAttributesTable represents each iFCP session as a pair of N_PORTs joined by a single TCP/IP connection. Fields include local and remote portal IP address/port, local and remote N_Port WWN and FCID, FCID alias, IP_TOV, LTI values, and a bound flag indicating assignment to specific N_PORTs.

snmp

protocol-element §4

ifcpSessionDiscontinuityTime records the sysUpTime value at the most recent counter discontinuity across all eight Counter64 objects in ifcpSessionStatsTable; it is zero if no discontinuity has occurred since last reinitialization.

snmp

protocol-element §4

ifcpSessionLclPrtlTcpPort and ifcpSessionRmtPrtlTcpPort may hold a value of zero during initial session setup before TCP port numbers are determined; a zero value must not be used to locate a session in the TCP-MIB.

snmp, tcp

protocol-element §4

ifcpSessionLcStatsTable augments ifcpSessionAttributesEntry with the same eight traffic counters as ifcpSessionStatsTable but using ZeroBasedCounter32 for backward compatibility with SNMPv1 and systems lacking Counter64 support.

snmp

protocol-element §4

ifcpSessionRmtNpFcidAlias carries the Fibre Channel Identifier Alias assigned by the local gateway for the remote N_Port in address translation mode; it is a zero-length string for unbound sessions.

snmp

protocol-element §4

ifcpSessionStatsTable augments ifcpSessionAttributesEntry with 64-bit ZeroBasedCounter64 counters for TxOctets, RxOctets, TxFrames, RxFrames, StaleFrames, HeaderCRCErrors, FcPayloadCRCErrors, OtherErrors, and a DiscontinuityTime timestamp.

snmp

registry §5

IANA assigned a unique OID for IFCP-MGMT-MIB under the transmission branch at { transmission 230 }.

registry, snmp

security-consideration §6

Five read-write objects — ifcpLclGtwyInstAddrTransMode, ifcpLclGtwyInstFcBrdcstSupport, ifcpLclGtwyInstDefaultIpTOV, ifcpLclGtwyInstDefaultLTInterval, and ifcpSessionIpTOV — can disrupt active storage traffic if modified without proper authorization. SET operations in non-secure environments pose a negative risk to network operations.

snmp, security

security-consideration §6

ifcpLclGtwyInstTable and ifcpSessionAttributesTable expose information about which nodes are communicating and exchanging storage data; even read (GET/NOTIFY) access to these tables should be controlled and values should potentially be encrypted in transit.

snmp, security, privacy

state-machine §4

IfcpSessionStates defines three iFCP session states: down(1), openPending(2), and open(3). The ifcpSessionDuration counter resets to 0 when a session enters the down state.

snmp

wire-format §4

IfcpAddressMode is an INTEGER with two values: addressTransparent(1) and addressTranslation(2), indicating the iFCP gateway's address handling mode. The default for ifcpLclGtwyInstAddrTransMode is addressTranslation.

snmp

wire-format §4

IfcpIpTOVorZero is an Unsigned32 (0..3600) representing the maximum IP propagation delay in seconds for an encapsulated FC frame. A value of 0 disables Fibre Channel frame lifetime enforcement.

snmp

wire-format §4

IfcpLTIorZero is an Unsigned32 (0..65535) representing the Liveness Test Interval in seconds. A value of 0 means no liveness testing will be performed on the session.

snmp