FIBRE CHANNEL - T11

TR-xx-1998 Fibre Channel Tape Rev 1.07 August 7, 1998
5 FC-2 feature sets
The tables in this clause list features described in FC-PH, FC-PH-2, and FC-PH-3. These tables indicate
whether the feature is Required, Prohibited, Allowable, or Invokable for compliance with this
specification. Features that are not listed do not affect interoperability of Private NL_Ports.
Reserved FC-PH, FC-PH-2, and FC-PH-3 fields are processed in accordance with the applicable
standard or standards. Validity bits set to zero remove any requirement to check the corresponding
field for zeroes and make the associated field meaningless (e.g., if F_CTL bit 3=0 in an FCP_DATA
Sequence at a receiving NL_Port, the Relative Offset in the parameter field of the Frame header shall
not be used in any way when reassembling the Sequence at the recipient).
5.1 Node and port naming
All SCSI Targets and Initiators complying with this profile shall have a unique Node_Name (WWN).
Each FC-TAPE compliant NL_Port associated with these nodes shall also have a unique Port_Name
(WWN). To ensure uniqueness of these names, all names shall use one of the registered name formats
such as the IEEE or IEEE extended formats defined by FC-PH-3.
All NL_Ports must acquire a valid AL_PA and Native Address Identifier before performing PLOGI with
other NL_Ports.
NL_Ports must retain the Node_Name and Port_Name of the other port from each PLOGI and associate
that information with the Native Address Identifier of that NL_Port. This information shall be retained
for as long as the PLOGI with the other port is active.
SCSI Targets and SCSI Initiators shall validate current NL_Port logins following every Loop Initialization
by comparing the Port Name, Node Name, and N_Port ID received during the PLOGI with those
reported by the PDISC or ADISC that follows the Loop Initialization. All three identifiers reported during
the PDISC or ADISC shall match the values reported during PLOGI or a configuration change has
occurred and LOGO is required and all open Exchanges with that SCSI Initiator or SCSI Target will
be terminated.
Consider two examples os a DISC or ADISC request arriving at a SCSI Target, or ACC arriving at a
SCSI Initiator in response to a PDISC or ADISC.
Table 3 – PDISC, ADISC, ACC Examples
Example Identifier PLOGI Data ADISC, PDISC, or ACC
Data
1
2
N_Port ID (24 bits) 00 00 AA 00 00 AB
Node Name (64 bits) 1000 ABCD EF12 3456 1000 ABCD EF12 3456
Port Name (64 bits) 1000 ABCD EF12 3457 1000 ABCD EF12 3457
N_Port ID (24 bits) 0000AA 0000AA
Node Name (64 bits) 1000 ABCD EF12 3456 1000 ABCD EF12 3456
Port Name (64 bits) 1000 ABCD EF12 3456 1000 ABCD EF98 7654
Response
LOGO
LOGO
Example 1 may occur if a node with no Hard Address has been removed and reinserted into a reconfigured
loop, and takes a different soft address.
11