FC-LS-4 Login Revisited
Table of Contents The Diagnostic Goal Atomic Solution Options T11 June 2016 2
The Diagnostic Goal Low overhead Objective Minimize the activity surrounding diagnostic operations Observations RDP is a diagnostic operation Bulk RDP operations are possible Especially outward from the fabric (i.e. Domain Controller) Concern Login requirement can create a session-like behavior Function of login, in this case, is to determine the maximum payload size T11 June 2016 3
Atomic Solution Single Frame / No Login Login Modify Table 9 to indicate RDP does not require login Request Requestor assumes the responsibility of accepting the maximum payload in a single frame upon issuing the RDP ELS Response Responder packages descriptors of response into a single frame (with respect to clause 4.3.48.4) T11 June 2016 4
Option 1 I asked for it, I can take it! Modify the RDP ELS entry in Table 9 of FC- LS-3 as shown: Table 9 ELS_Command codes Valule (Bits 31-24) Description Abbr. Reference 18h Read Diagnostic Parameters RDP 4.3.48 No b... Login Required b An Nx_Port may require login to complete the response. Receiving an ELS without login assumes the requestor is capable of accepting the maximum size response in a single payload. T11 June 2016 5
Option 2 Let the ELS decide Modify the RDP ELS entry in Table 9 of FC- LS-3 as shown: Table 9 ELS_Command codes Valule (Bits 31-24) Description Abbr. Reference Login Required 18h Read Diagnostic Parameters RDP 4.3.48 No b... b See the ELS command description for the appropriate response. T11 June 2016 6
RDP ELS Let the ELS decide Add clause to RDP definition under Reply Sequence 4.3.48.4.1 Response to Received ELS If the Nx_Port receiving an RDP ELS request is logged in with the source, it shall respond as appropriate for the ELS and the current state of the Nx_Port. If the Nx_Port receiving an RDP ELS request is not logged in with the source, it may respond with LS_RJT with a reason code of Login Required or it shall respond with a single frame sequence. Reference Table 10 - Responses to Received ELSs Login Required No responses Respond as appropriate for the ELS and the current state of the Nx_Port. Same response for both Yes and No of Logged in with Source? designation T11 June 2016 7
End of Frame Thank You
References Notes from April Meeting T11 June 2016 9
Diagnostic ELSs Evolving Behavior RLS Read Link Error Status Block (0x0F) ECHO Echo (0x10) TEST Test (0x11) RDP Read Diagnostic Parameters (0x18) RNID Read Node Identifier (0x78) RPSC Read Port Speed Capabilities (0x7D) LCB Link Cable Beacon (0x81) T11 June 2016 10
Requests Login Required? My F_Port (F_Port Controller) My A B V 20 W X U 10 30 C Y Z Your (_ID) D 40 F E Your Your F_Port (Domain Controller) T11 June 2016 11
Domain Controller Requests Login Required? My (Domain Controller) My A B V 20 W X U 10 30 C Y Z D 40 F E Your Your (Domain Controller) T11 June 2016 12
Questions/Suggestions Login when already logged in? ELS from Nx_Port to F_Port Controller/Domain Controller Login occurred with FLOGI Does it make sense to PLOGI? ELS from F_Port Controller/Domain Controller to Nx_Port FLOGI preceeds ELS Is it redundant to PLOGI? Would clarifying Login Required help? T11 June 2016 13
Notes on Sizes Payloads Buffer-to-Buffer Receive Data_Field Size Default == 128-bytes Command RLS Maximum Payload 28-bytes ECHO Login or default 4 TEST Login or default 4 RDP RNID RPSC LCB 112/140-bytes 236/264-bytes 276-bytes 8-bytes 12-bytes Descriptor Preamble and Link Services Port Speed LESB Port Names SFP QSFP FEC Buffer Credit Optical Element Optical Data Size 20-bytes 12-bytes 36-bytes 24-bytes 20-bytes 48-bytes 16-bytes 20-bytes 20-bytes 68-bytes T11 June 2016 14
Thank You! This slide intentionally left blank