Sun Oracle Storage Tek T10000, Справочное руководство

Страница: 74 / 296

Public Loop SCSI Target Discovery
56 T10000: Interface Reference Manual • January 2011 • E20425-01
■
Public Loop SCSI Target Discovery
The following private loop discovery is used except that discovery of SCSI
Targets will be performed via the Simple Name Server or RSCN and the
function performed by ADISC/PDISC will be replaced by FAN.
■
Private Loop SCSI Target Discovery
When the possibility of a configuration change exists, a SCSI Initiator may
want to rediscover the new configuration. The SCSI Target Discovery
procedure for a SCSI Initiator is:
For all valid AL_PAs:
In order to determine if an OPN was successful, the NL_Port must be able to:
1. Detect when an OPN has not been intercepted by the designated AL_PA.
2. Detect that an R_RDY or CLS has not been received from the AL_PA
specified in an OPN within E_D_TOV of sending that OPN.
3. Detect that a CLS was received in response to the OPN.

In this case, the Target Discovery procedure should be retried at a later
time.
4. Detect that the OPN or frame Extended Link Service failed.
If the SCSI Target Discovery procedure revealed a Hard Address conflict
(such as an NL_Port was unable to acquire its hard address), then the
application may choose to operate in spite of that conflict.
OPN(AL_PA)
IF OPN is successful, then
Send ADISC or PDISC to D_ID = hex ’0000’ || AL_PA
IF LOGO is returned or the Node Name or Port Name has changed, then
Send PLOGI to D_ID = hex ’0000’ || AL_PA
IF PLOGI is successful, then
IF no hard address conflicts or application tolerant of hard
address conflicts
Send PRLI to D_ID = hex ’0000’ || AL_PA
IF PRLI is successful, then
Send FCP_CMND with INQUIRY CDB to D_ID = hex ’0000’
||AL_PA(LUN_0)
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
NEXT AL_PA