Definitions of Managed Objects for the Internet Fibre Channel Protocol (iFCP)
obsoletes
- rfc-4369 — Definitions of Managed Objects for Internet Fibre Channel Protocol (iFCP)
Extracted elements (25)
Both Counter64-based (ifcpSessionStatsTable) and Counter32-based (ifcpSessionLcStatsTable) statistics are provided because at 1-Gbps rates a Counter32 can wrap as often as every 34 seconds, yet Counter32 objects are needed for backward compatibility with systems lacking Counter64 support or running SNMPv1.
The iFCP address translation mode is deprecated as of RFC 6172. This MIB revision obsoletes RFC 4369 specifically to reflect that deprecation, with the new compliance statement (ifcpGatewayComplianceNoTranslation) requiring only addressTransparent(1) mode.
The session table uses an opaque integer index (ifcpSessionIndex) rather than the local and remote N_Port identifiers, because using N_Port information would create a complex index that would be difficult to implement.
Shortly after an iFCP session entry is created, it corresponds to an entry in the TCP-MIB tcpConnectionTable (RFC 4022), and optionally to RFC 2012's tcpConnTable for IPv4. The address type fields in both tables must match to simplify cross-table lookups.
When a TCP connection for an iFCP session terminates, both the tcpConnectionTable entry and the ifcpSessionAttributesTable entry are deleted simultaneously. TCP port fields may temporarily hold value 0 during initial session setup before port numbers are known.
Both compliance statements restrict ifcpSessionLclPrtlAddrType and ifcpSessionRmtPrtlIfAddrType to global IPv4 and IPv6 address types only; other InetAddressType values need not be supported.
Deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Implementers are RECOMMENDED to use SNMPv3 with full cryptographic mechanisms for authentication and privacy, and to restrict object access to principals with legitimate rights.
Implementers are RECOMMENDED to use the high-capacity Counter64 statistics in ifcpSessionStatsTable when possible, rather than the Counter32-based ifcpSessionLcStatsTable.
The ifcpGatewayComplianceNoTranslation compliance statement requires support only for addressTransparent(1) in ifcpLclGtwyInstAddrTransMode, reflecting the deprecation of address translation mode.
The IfcpAddressMode textual convention defines two address operating modes: addressTransparent(1) and addressTranslation(2). Address translation mode is deprecated per RFC 6172.
The IfcpIpTOVorZero textual convention represents the maximum IP propagation delay in seconds (range 0..3600). A value of 0 means Fibre Channel frame lifetime limits will not be enforced.
The ifcpLclGtwyInstTable contains an entry per managed local iFCP gateway instance, providing per-gateway parameters including default IP_TOV (default 6 seconds), default LTI (default 10 seconds), address translation mode, and FC broadcast support.
The IfcpLTIorZero textual convention represents the Liveness Test Interval (LTI) in seconds (range 0..65535). A value of 0 means no liveness testing will be performed.
The ifcpSessionAttributesTable provides session management information indexed by local gateway instance and session index, capturing local and remote portal IP addresses, TCP ports, N_Port WWNs, FC identifiers, IP_TOV, and LTI values per session.
The ifcpSessionBound object indicates whether a session is bound to specific local and remote N_Ports. Sessions are unbound by default and ready for future assignment.
The ifcpSessionDiscontinuityTime object records the sysUpTime value at the most recent counter discontinuity for the session stats table. It is zero if no discontinuities have occurred since last reinitialization.
The ifcpSessionLcStatsTable augments the session attributes table with low-capacity Counter32-based equivalents of the same statistics, provided for backward compatibility with systems that do not support Counter64 or need SNMPv1 support.
The ifcpSessionRmtNpFcidAlias object holds the Fibre Channel Identifier alias assigned by the local gateway for the remote N_Port, relevant only in address translation mode.
The IfcpSessionStates textual convention defines three session states: down(1), openPending(2), and open(3).
The ifcpSessionStatsTable augments the session attributes table with high-capacity Counter64-based statistics per session: TxOctets, RxOctets, TxFrames, RxFrames, StaleFrames, HeaderCRCErrors, FcPayloadCRCErrors, OtherErrors, and a discontinuity timestamp.
This document registers the OBJECT IDENTIFIER value { transmission 230 } for the ifcpMgmtMIB module in the SMI Numbers registry.
Five read-write MIB objects can disrupt storage traffic if modified without authorization: ifcpLclGtwyInstAddrTransMode, ifcpLclGtwyInstFcBrdcstSupport, ifcpLclGtwyInstDefaultIpTOV, ifcpLclGtwyInstDefaultLTInterval, and ifcpSessionIpTOV. SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
SNMP versions prior to SNMPv3 lack adequate security. Even on a network secured by IPsec, earlier SNMP versions provide no access control over who on the secure network may GET or SET MIB objects.
The ifcpLclGtwyInstTable and ifcpSessionAttributesTable expose sensitive information about storage session participants and traffic patterns; even GET and NOTIFY access to these objects should be controlled and values may need encryption in transit.
An iFCP session transitions through states down(1), openPending(2), and open(3). The session duration counter resets to 0 when a session returns to the down state.