Datasheet

2.3 Outline of Command Processing
C141-C008 2-13
If connections are not established, operation is as follows.
PLOGI is not implemented:
The IDD responds with the LOGO (Extended Link Service) frame.
If PLOGI is already implemented, PRLI is not implemented:
The IDD responds with the PRLO (Extended Link Service) frame.
PRLI is implemented without implementing PLOGI: This combination should
not exist.
Furthermore, this IDD supports connections with a maximum of 32 INITs
(without relation to the port).
As for PLOGI of the 33th and subsequent INITs, the LS_RJT frame is sent as a
response and notification to the effect that there are no internal resources for
establishing connections is sent.
(3) Loop initialization after establishing connections with the INIT and subsequent
processing
After connections between the INIT and IDD are established, if loop initialization
occurs for any reason, SCSI commands which were being executed when loop
initialization was carried out are aborted (however, if a command from a different port
was being executed, it is not aborted).
After loop initialization is terminated, the IDD waits for approximately 2 seconds
for connections with the INIT to be reestablished.
This period of time is for the purpose of confirming any changes that may have
occurred to previously held ALPAs due to loop initialization.
Furthermore, if this time is exceeded, the IDD carries out an implicit logout and
interrupts the connection with the INIT.
If the connection is interrupted, commands waiting in the queue are all aborted
and no response is returned.
Also, the LOGO (Extended Link Service) frame is returned as a response to the
SCSI command from the INIT.