Download presentation

Presentation is loading. Please wait.

Published byDeclan Winston Modified over 2 years ago

1
FC-PI-5, FC-FS-3, and 16GFC bob.nixon@emulex.com T11/09-506v2 - 10/27/20091FC-PI-5, FC-FS-3, and 16GFC

2
Hot Potatoes An earlier version of this presentation described several things for which FC-FS-3 references details or specific values in FC-PI-x. Some have been handled in FC-PI-x for years. Some are new for 16GFC. This presentation attempts to clarify the new ones. It also corrects some names to better match IEEE 802.3:2008 terminology T11/09-506v2 - 10/27/20092FC-PI-5, FC-FS-3, and 16GFC

3
Selection of Transmission Code “An FC-0 standard (e.g., FC-PI-5) may specify the use of the 8B/10B transmission code as its frame transfer transmission code.” (FC-FS-3 5.2.1) “An FC-0 standard (e.g., FC-PI-5) may specify the use of the 64B/66B transmission code as its frame transfer transmission code.” (FC-FS-3 5.3.1) This is new, there was never a choice before. An implementation of a variant shall use 8B/10B if an FC-0 standard (e.g., FC-PI-4) does not specify a frame transfer transmission code for that variant. T11/09-506v2 - 10/27/20093FC-PI-5, FC-FS-3, and 16GFC

4
If Transmission Code is 64B/66B “An FC-0 standard (e.g., FC-PI-5) may specify the use of the Transmitter Training Signal….” (FC-FS-3 5.4.1) FC-PI-5 should select or reject for each 64B/66B physical variant – Transmitter Training Signal Or it may simply say that all 64B/66B variants shall use the Transmitter Training Signal. T11/09-506v2 - 10/27/20094FC-PI-5, FC-FS-3, and 16GFC

5
If Speed Negotiation is supported… “For any variant that does not specify a Transmitter Stabilization Time, including those specified in FC-PI-2, FC-PI- 3, FC-PI-4, 10GFC, the Transmitter Stabilization Time shall be one millisecond.” (FC-FS-3 8.6.6) “For any variant that does not specify a Receiver Stabilization Time, including those specified in FC-PI-2, FC-PI-3, FC-PI-4, 10GFC, the Receiver Stabilization Time shall be one millisecond.” (FC-FS-3 8.6.6) FC-PI-5 should specify for each physical variant that can not stabilize a signal in one millisecond: – Receiver Stabilization Time – Transmitter Stabilization Time T11/09-506v2 - 10/27/20095FC-PI-5, FC-FS-3, and 16GFC

6
If Transmitter Training Signal is supported “Transmitter training negotiates either or both of two capabilities between the transmitters and receivers connected by a link: a) values of transmitter equalizer coefficients that result in most reliable signal reception across the link; and b) use of FEC.” (FC-FS-3 9.2) FC-PI-5 should select, reject, or make optional for each physical variant that supports the Transmitter Training Signal – training of transmitter equalizer coefficients – Forward Error Correction (FEC ) T11/09-506v2 - 10/27/20096FC-PI-5, FC-FS-3, and 16GFC

7
If training of transmitter equalizer coefficients is supported “The use of each coefficient is specified by FC-PI-x for each FC-0 variant that supports transmitter training. Each coefficient in the model has a minimum value, a maximum value, a preset value, an initialize value, and a step size by which it may be adjusted. These values are specified by FC-PI- x for each FC-0 physical variant that supports transmitter training. ” (FC-FS-3 9.2) This author has recently been enlightened: the protocol for 16GFC Transmitter Training was intended to be based on the IEEE 802.3:2008 specification for the Physical Medium Dependent Sublayer and Baseband Medium, Type 10GBASE- KR PMD control function (IEEE 802.3:2008 subclause 72.6.10). T11/09-506v2 - 10/27/20097FC-PI-5, FC-FS-3, and 16GFC

8
If training of transmitter equalizer coefficients is supported FC-PI-5 should specify for each physical variant that supports coefficient training, the following for coefficients 0, 1, and 2: – What it does (if anything) – Its minimum value – Its maximum value – The preset value, to which it will be set for a Preset command – The initialize value, to which it will be set for an Initialize command – Its step size, by which it will be adjusted for an Increment or Decrement command FC-PI-5 may decide how closely these follow IEEE 802.3. FC-PI- 5 may even say some (or all?) of these parameters are vendor specific. T11/09-506v2 - 10/27/20098FC-PI-5, FC-FS-3, and 16GFC

9
Summary T11/09-506v2 - 10/27/2009FC-PI-5, FC-FS-3, and 16GFC9 If:FC-PI-5 should specify for each variant or group of variants: Whether speed negotiation is required, forbidden, or optional If Speed Negotiation is performed and Transmitter Stabilization Time is greater than 1 millisecond Transmitter Stabilization Time (see FC-FS-3 subclause 8.6.6) If Speed Negotiation is performed and Receiver Stabilization Time is greater than 1 millisecond Receiver Stabilization Time (see FC-FS-3 subclause 8.6.6) If transmission code is not 8B/10BTransmission code to use Whether to use Training Signal during link initialization If Training Signal is to be used during link initialization Whether FEC is required, forbidden, or optional Whether training of transmitter coefficients is required, forbidden, or optional If training of transmitter coefficients is performed The effects of coefficients 0, 1, and 2 The maximum values for coefficients 0, 1, and 2 The minimum values for coefficients 0, 1, and 2 The step size for adjusting the values for coefficients 0, 1, and 2 (see IEEE 802.3:2008 subclause 72.6.10.2.3.3 for guidance) The preset values for coefficients 0, 1, and 2 (see IEEE 802.3:2008 subclause 72.6.10.2.3.1 for guidance) The initialize values for coefficients 0, 1, and 2 (see IEEE 802.3:2008 subclause 72.6.10.2.3.2 for guidance)

10
That ought to do it Questions ? T11/09-506v2 - 10/27/200910FC-PI-5, FC-FS-3, and 16GFC

Similar presentations

© 2017 SlidePlayer.com Inc.

All rights reserved.

Ads by Google