10-Gigabit Ethernet Consortium

Transcription

1 10-Gigabit Ethernet Consortium Proposed modifications to Ethernet Auto-Negotiation Test Suites for 10GBASE-T V0.2 Cover Page Draft Technical Document Last Updated: February 8, :03AM 10 Gigabit Ethernet Consortium InterOperability Laboratory 121 Technology Drive, Suite 2 Research Computing Center Durham, NH University of New Hampshire Phone:

2 MODIFICATION RECORD February 8, 2006 Version 0.2 released for external review September 21, 2005 Version 0.1 released for internal review Please note that the current version of this document is a draft document and is subject to substantial change before it is finalized. Editorial notes, contained within parentheses and italicized, have been placed throughout the document. These notes will be removed prior to the official release of this test suite.

3 ACKNOWLEDGMENTS The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. To be filled in at a later time.

4 INTRODUCTION Overview The University of New Hampshire s InterOperability Laboratory (IOL) is an institution designed to improve the interoperability of standards based products by providing an environment where a product can be tested against other implementations of a standard. This suite of tests has been developed to help implementers evaluate the functioning of the Auto-Negotiation protocol of 10GBASE-T products. The tests do not determine if a product fully conforms to the IEEE Standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within an auto-negotiating device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other auto-negotiating devices. However, combined with satisfactory operation in the IOL s interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function well in most auto-negotiating environments. Organization of Tests The tests contained in this document are organized to simplify the identification of information related to a test and to facilitate in the actual testing process. Each test contains an identification section that describes the test and provides cross-reference information. The discussion section covers background information and specifies why the test is to be performed. Tests are grouped in order to reduce setup time in the lab environment. Each test contains the following information: Test Number The Test Number associated with each test follows a simple grouping structure. Listed first is the Test Group Number followed by the test's number within the group. This allows for the addition of future tests to the appropriate groups of the test suite without requiring the renumbering of the subsequent tests. Purpose The purpose is a brief statement outlining what the test attempts to achieve. The test is written at the functional level. References The references section lists cross-references to the IEEE standards and other documentation that might be helpful in understanding and evaluating the test and results. Resource Requirements The requirements section specifies the hardware, and test equipment that will be needed to perform the test. The items contained in this section are special test devices or other facilities, which may not be available on all devices. Last Modification This specifies the date of the last modification to this test.

5 Discussion The discussion covers the assumptions made in the design or implementation of the test as well as known limitations. Other items specific to the test are covered here. Test Setup The setup section describes the configuration of the test environment. Small changes in the configuration should be included in the test procedure. Procedure The procedure section of the test description contains the step-by-step instructions for carrying out the test. It provides a cookbook approach to testing, and may be interspersed with observable results. Observable Results The observable results section lists observations that can be examined by the tester to verify that the DUT is operating properly. When multiple values are possible for an observable, this section provides a short discussion on how to interpret them. The determination of a pass or fail for a certain test is often based on the successful (or unsuccessful) detection of a certain observable. Possible Problems This section contains a description of known issues with the test procedure, which may affect test results in certain situations.

6 TABLE OF CONTENTS Cover Page... 1 MODIFICATION RECORD... 2 ACKNOWLEDGMENTS... 3 INTRODUCTION... 4 TABLE OF CONTENTS... 6 Proposed modifications to State Machine Base Page Test Suite v Test #28.1.1: FLP Burst spacing... 8 Test #28.1.4: NLP Compliance Test #28.1.6: Link Fail Inhibit Timer Test #28.2.6: Acceptance of Long FLPs Test #28.2.9: Technology Ability Field Bits Test # : Range of NLP Timer Proposed modifications to Next Page Exchange Test Suite Rev Test #28.3.1: Extended Next Page negotiation and usage Test #28.3.2: Extended Message Page format Test #28.3.3: Extended Unformatted Page format Test #28.3.4: Null Message Page Generation for extended Next Pages Proposed modifications to Management System Test Suite v Test #1.2: Base Page Technology Ability Field Test # 1.4: 10GBASE-T Abilities Test #2.1 Speed Resolution and Verification Test #2.5: 10GBASE-T Master-Slave Resolution Proposed modifications to Management Register Test Suite v

7 Proposed modifications to State Machine Base Page Test Suite v5.6 The current test suite may be found here, Note: The modifications proposed in this document will be incorporated into the above test suite upon ratification of IEEE 802.3an-2006.

8 Test #28.1.1: FLP Burst spacing Purpose: To verify proper separation of consecutive fast link pulse (FLP) bursts. References: [1] IEEE P802.3an D3.1: subclause , , Table 28-1, Table 28-9, Figure 28-6, Figure Resource Requirements: Line Monitor: A system capable of detecting, time stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Last Modification: February 8, 2006 Discussion: A station capable of Auto-Negotiation must transmit fast link pulse (FLP) bursts. Not only are the content and composition of these bursts important, but also the timing of the bursts. This test is designed to verify that the timing of the device under test s consecutive FLP bursts fall within the specified ranges. For devices that are not using extended Next Pages, the allowable range from the beginning of one FLP Burst to the beginning of the next FLP Burst is 8 ms to 24 ms. The range from the end of one FLP Burst to the beginning of the next FLP Burst is 5.7 ms to 22.3 ms. For devices that are using extended Next Pages, the allowable range from the beginning of one FLP Burst to the beginning of the next FLP Burst is 8 ms to 8.5 ms. The range from the end of one FLP Burst to the beginning of the next FLP Burst is 1.3 ms to 3.2 ms when the page_size is 48, and is 5.7 ms to 6.8 ms when the page_size is 16. Test Setup: Using a Cat 5 cord, connect the DUT s transmitter to the Line Monitor. Terminate the DUT s transmit channel with a 100 Ω line termination. Procedure:The DUT is configured to send FLP bursts. 1. Monitor the transmitted bursts. 2. The separation of each burst is measured from the last NLP sent in an FLP to the first NLP sent in the next FLP and from the first NLP sent in an FLP to the first NLP sent in the next FLP. 3. Repeat steps 1 3, configuring the DUT to send FLP bursts consisting of extended Next Pages. Observable Results: a. The separation of FLP bursts from the last NLP in an FLP to the first NLP in the next FLP must be within the range of 5.7 ms to 22.3 ms. b. The separation of FLP bursts from the first NLP in an FLP to the first NLP in the next FLP must be within the range of 8 ms to 16 ms.

9 c. The separation of FLP bursts from the last NLP in an FLP to the fist NLP in the next FLP, with a device supporting extended Next Pages when page_size is 16 is 5.7 ms to 6.8 ms. d. The separation of FLP bursts from the last NLP in an FLP to the fist NLP in the next FLP, when in an extended Next Page, must be within the range of 1.3 ms to 3.2 ms. e. The separation of FLP bursts from the first NLP in an FLP to the fist NLP in the next FLP, when in an extended Next Page, must be within the range of 8 ms to 8.5 ms. Possible Problems: None.

10 Test #28.1.4: NLP Compliance Purpose: To verify the DUT s link pulse waveforms meet specification. References: [1] IEEE Std : subclauses , , , 28.4, Figure [2] IEEE P802.3an D3.1: subclause 28.2, Resource Requirements: Oscilloscope: A digitizing signal analyzer, which meets or exceeds the specifications for an oscilloscope, as defined in IEEE Std d-1993 Section Differential Voltage Probes: Meets or exceeds specifications defined in IEEE Std d-1993 Section TP Test Card: A testing card with an RJ-45 interface, cable termination of Test Load 1, or Test Load 2 (as defined in IEEE Section and Figure 14-11, Start-of- TP_IDLE test load), and an Unshielded twisted pair model (as defined in IEEE Std Section ) that can be inserted inline. Last Modification: February 8, 2006 Discussion: All link pulses need to conform to the transmitter waveform specifications for Link Test Pulses defined in IEEE Std 802.3, 2005 Ed. Figure 14-12, Transmitter waveform for link test pulse, including those contained in an FLP burst, when measured across each of the test loads defined in Figure 14-11; both with the load connected directly to the TD circuit and with the load connected through all of the cable types and distances supported by the advertised capabilities. This test is designed to verify that the device under test produces link pulses within specification. [Add table showing different capabilities and cable types that need to be tested.] Test Setup: [Text to be added at a later time.] Procedure: 1. The DUT is configured to send FLP bursts. 2. Monitor the transmitted bursts. 3. Observe the link pulse waveforms across each test load defined in Figure 14-11, Start-of- TP_IDLE test load. 4. Repeat procedure with loads connected through applicable cable types, as shown in the above table [Note, table doesn t exist yet]. Observable Results: a. Under each test setup, the FLP s link pulses should fit within the NLP template defined in Figure After the differential output voltage drops below -50 mv, it shall remain below +50 mv. Possible Problems: None.

11 Test #28.1.6: Link Fail Inhibit Timer Purpose: To verify that the DUT will defer for the proper amount of time before attempting to verify the status of the link determined by the Auto-Negotiation process. References: [1] IEEE Std : Sections , 28.3 [2] IEEE P802.3an D3.1: subclause , Table 28-9 Resource Requirements: Line Monitor: A system capable of detecting, time stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: Once a device has entered the FLP LINK GOOD CHECK state, it must receive a link_status=ok message from its link partner within a specified amount of time. If this message is not received, it will enter the TRANSMIT DISABLE state and wait for the duration of its break_link_timer before starting a re-negotiation. This time is defined by the device s link_fail_inhibit_timer, and is required to be between 750 and 1000 ms for devices not operating at 10Gb/s, and ms for devices operating at 10Gb/s. This test is designed to verify that the device under test enters the TRANSMIT DISABLE state from the FLP LINK GOOD CHECK state when a link_status=ok message is not received from its link partner in the acceptable range of time. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the DUT s receiver will see the Traffic Generator s signaling. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: Part a: for devices with a 10BASE-T PMA: 1. Establish a connection (not a link) to the DUT. 2. Use the Traffic Generator to put the device into the FLP LINK GOOD CHECK state and resolve a 10BASE-T link by sending enough FLPs that advertise only 10BASE-T abilities 3. Verify that the DUT restarts Auto-Negotiation. 4. Measure the amount of time NLPs are sent from the DUT and verify it is link_fail_inhibit_timer. Part b: for devices with a 100BASE-TX PMA: 5. Repeat steps 1-3 above, changing the advertised abilities to include 100BASE-TX abilities. 6. Measure the amount of time the DUT was observed to source 100BASE-TX link signaling.

12 Part c: for devices with a 1000BASE-T PMA: 7. Repeat steps 1-3 above, changing the advertised abilities, by means of a Next Page exchange, to include 1000BASE-T abilities. 8. Measure the amount of time the DUT was observed to source 1000BASE-T link signaling. Part d: for devices with a 10GBASE-T PMA: 9. Repeat steps 1-3 above, changing the advertised abilities, by means of a Next Page exchange, to include 10GBASE-T abilities. It may be necessary to force the DUT to be MASTER. 10. Measure the amount of time the DUT was observed to source 10GBASE-T link signaling. Observable Results: a. For devices with a 10BASE-T PMA, observation of the interval between FLP cessation and 10BASE-T link signaling cessation + transmit_link_burst_timer should be in the range of 750 to 1000 ms. b. For devices with a 100BASE-TX PMA, observation of the interval between FLP cessation and 100BASE-TX link signaling cessation should be in the range of 750 to 1000 ms. c. For devices with a 1000BASE-T PMA, observation of the interval between FLP cessation and 1000BASE-T link signaling cessation should be in the range of 750 to 1000 ms. d. For devices with a 10GBASE-T PMA, observation of the interval between FLP cessation and 10GBASE-T link signaling cessation should be in the range of 2000 to 2250 ms. Possible Problems: None.

13 Test #28.2.6: Acceptance of Long FLPs Purpose: To verify that the DUT properly accepts FLPs with more than 16 (or 48) data positions by ignoring all but the first 16 (or 48) data bits. References: [1] IEEE Std Edition: subclauses , , , Figure Resource Requirements: Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: September 21, 2005 Discussion: An FLP burst normally consists of 17 to 33 pulses, with normally 16 data bits. An extended Next Page FLP Burst normally consists of 49 to 97 pulses, with normally 48 data bits. However, if a device receives an FLP with more than 16 (or 48) data positions, it should still accept the burst. The first 16 (or 48) data bits should be kept and any additional should be ignored. This test is designed to determine whether the Device Under Test properly accepts FLPs with more than 16 (or 48) data bits. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the DUT s receiver will see the Traffic Generator s signaling. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: Part a: 1. Use a Traffic Generator to send enough valid FLPs with 1 extra data position corresponding to a logic one (1 extra clock pulse and 1 data pulses) attached to the end to put the DUT into the Acknowledge Detect state. 2. Observe whether the DUT enters the ACKNOWLEDGE DETECT state. 3. Repeat steps 1 and 2, using extended Next Pages, if necessary. Part b: 4. Repeat steps 1 and 2 above, sending 5 additional data bits corresponding to Repeat step 3, using extended Next pages, if necessary. Observable Results: a. The DUT should enter the ACKNOWLEDGE DETECT state. b. The DUT should enter the ACKNOWLEDGE DETECT state. Possible Problems: None.

14 Test #28.2.9: Technology Ability Field Bits Purpose: To verify that the DUT accepts FLPs with different combinations of the Technology Ability Field bits set to logic one. References: [1] IEEE Std : subclauses , , , Annex 28B.2 [2] IEEE P802.3an D3.1: subclause Resource Requirements: Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: The technology ability field contains eight bits that indicate supported technologies specific to the Selector Field value. Bits A0:A7 are encoded as 10BASE-T half duplex, 10BASE-T full duplex, 100BASE-TX half duplex, 100BASE-TX full duplex, 100BASE-T4, PAUSE, Asymmetric PAUSE operation, and extended Next Page, respectively. Regardless of what abilities a device advertises, it is supposed to be able to receive any of the technology ability field bits set to a one without affecting normal operation. This test is designed to verify that the device under test will accept a Link Code Word with various combinations of the technology ability field set to logic one. Test Setup: Using a Cat 5 cord, connect the DUT s transmitter to the Line Monitor. Terminate the DUT s transmit channel with a 100Ω line termination. Using a Cat 5 cord, connect the DUT s receiver to the Traffic Generator using a 100Ω line termination. Procedure: Part a: 1. Establish a connection (not a link) to the DUT. 2. Use the Traffic Generator to send (n) FLPs with the Acknowledge bit not set and bit A0 set to logic one to put it into the ACKNOWLEDGE DETECT state. 3. Verify that the DUT enters the ACKNOWLEDGE DETECT state. 4. Repeat steps 1-3 but send FLPs encoded with bit combinations set to logic one including A1, A2, A3, A4, A5, A6, and A7. Part b: 5. Use the Traffic Generator to send (n) FLPs with the Acknowledge bit not set, and (m) FLPs with the Acknowledge bit set to put the DUT into the COMPLETE ACKNOWLEDGE state. 6. Verify that the DUT enters the COMPLETE ACKNOWLEDGE state. 7. Repeat step 5 but send FLPs encoded with all possible one bit differences.

15 Observable Results: a. The DUT should enter the ACKNOWLEDGE DETECT state regardless of the received FLPs encoded with varying Technology Ability Field bits. b. The DUT should enter the COMPLETE ACKNOWLEDGE state regardless of the received FLPs encoded with varying Technology Ability Field bits. Possible Problems: None.

16 Test # : Range of NLP Timer Purpose: To verify that the DUT accepts FLP bursts with proper spacing, and refuses those with spacing outside of the acceptable range. References: [1] IEEE Std : subclauses , [2] IEEE P802.3an D3.1: subclause Resource Requirements Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: As well as characteristic requirements, FLP bursts have requirements for the delay between consecutive bursts. In order to be accepted as valid, received FLP bursts must have a delay between them between nlp_test_min_timer and nlp_test_max_timer. The nonoptimized value for nlp_test_min_timer must be between 5 and 7 ms. The optimized value for nlp_test_min_timer must be between 6.75 and 7.25 ms. The value for nlp_test_max_timer must be between 50 and 150 ms. This test is to verify that the device under test accepts FLP bursts with spacing within these ranges, and refuses FLP bursts with spacing outside of these ranges. Note, nlp_test_min_timer is measured from the beginning of an FLP to the beginning of the next FLP, whereas nlp_test_max_timer is measured from the end of an FLP to the beginning of the next FLP. Test Setup: Using a Cat 5 cord, connect the DUT s transmitter to the Line Monitor. Terminate the DUT s transmit channel with a 100Ω line termination. Using a Cat 5 cord, connect the DUT s receiver to the Traffic Generator using a 100Ω line termination. Procedure: Part a: nlp_test_min_timer 1. Establish a connection (not a link) to the DUT. 2. Use a Traffic Generator to send the DUT (n) FLPs with the Acknowledge bit not set spaced between 2 ms and 10 ms to put it into the ACKNOWLEDGE DETECT state. 3. Observe whether the DUT entered the ACKNOWLEDGE DETECT state. 4. Repeat steps 1-3 varying the spacing of the FLPs until the range at which the DUT enters the ACKNOWLEDGE DETECT state and does not enter the ACKNOWLEDGE DETECT state is found.

17 Part b: nlp_test_max_timer 5. Repeat steps 1-3 varying the spacing of the FLPs starting between 30 ms and 200 ms, until the range at which DUT enters the ACKNOWLEDGE DETECT state and does not enter the ACKNOWLEDGE DETECT state is found. Observable Results: a. The nlp_test_min_timer should lay between 5 ms and 7 ms for devices using nonoptimized timing. The nlp_test_min_timer should lay between 6.75 ms and 7.25 ms for devices using optimized timing. b. The nlp_test_max_timer should lay between 50 ms and 150 ms. Possible Problems: None.

18 Proposed modifications to Next Page Exchange Test Suite Rev 2.3 The current test suite may be found here, Note: The modifications proposed in this document will be incorporated into the above test suite upon ratification of IEEE 802.3an Tests are added into a new group 3 (Extended Next Page functionality)

19 Test #28.3.1: Extended Next Page negotiation and usage Purpose: To verify that the DUT can properly handle the negotiation of extended Next Pages. References: [1] IEEE P802.3an D3.1: subclause , Resource Requirements: Line Monitor: A system capable of detecting, time stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: When two devices are connected to each other, they will negotiate the usage of extended Next Pages. Extended Next Page capability is advertised in Technology Ability Field bit A7 of the Base Page. When both devices indicate support of extended Next Page capability, then both devices will only transmit extended Next Pages. If only one device supports extended Next page capability, or if neither device supports extended Next Page capability, then extended Next Pages will not be used. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the DUT s receiver will see the Traffic Generator s signaling. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: Part a (DUT supports extended Next Page): 1. Establish a connection (not a link) to the DUT. 2. Use the Traffic Generator to send (n) FLPs with the Acknowledge bit not set, and (m) FLPs with the Acknowledge bit set, all with the extended Next Page bit and Next Page bit set to logic one to put it into the NEXT PAGE WAIT state. 3. Verify that the DUT enters the NEXT PAGE WAIT state and observe all Next Page transmissions from the DUT. 4. Repeat steps 1 3, setting the extended Next Page bit to logic zero. Observable Results: a. The device should enter the NEXT PAGE WAIT state and begin sending extended Next Pages when both link partners indicate extended Next Page support. The device should enter the NEXT PAGE WAIT state and begin sending Next Pages when both devices to not indicate extended Next Page support. Possible Problems: None.

20 Test #28.3.2: Extended Message Page format Purpose: To verify that the DUT transmits a properly formatted extended Message Page. References: [1] IEEE P802.3an D3.1: subclause , , Figure Resource Requirements: Line Monitor: A system capable of detecting, time stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: Once extended Next Page has been negotiated, the link partners will transmit extended Next Pages following the completion of the Base Page exchange. The extended Next Pages are similar to traditional Next Pages, with the exception that they contain 48 data bits instead of 16. Extended Message Pages have identical first 16 data bits as the Message Pages. The following 32 data bits are part of the 32-bit Unformatted Code Field. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the DUT s receiver will see the Traffic Generator s signaling. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: 1. Establish a connection (not a link) to the DUT. 2. Use the Traffic Generator to send (n) FLPs with the Acknowledge bit not set, and (m) FLPs with the Acknowledge bit set, all with the extended Next Page bit and Next Page bit set to logic one to put it into the NEXT PAGE WAIT state. 3. Verify that the DUT enters the NEXT PAGE WAIT state and observe all Next Page transmissions from the DUT. Observable Results: a. The DUT should transmit properly formatted extended Message Pages immediately after the Base Page exchange. Possible Problems: None.

21 Test #28.3.3: Extended Unformatted Page format Purpose: To verify that the DUT transmits a properly formatted extended Unformatted Page. References: [1] IEEE P802.3an D3.1: subclauses , , Figure Resource Requirements: Line Monitor: A system capable of detecting, time stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the Line Monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: Once extended Next Page has been negotiated, the link partners will transmit extended Next Pages following the completion of the Base Page exchange. The extended Next Pages are similar to traditional Next Pages, with the exception that they contain 48 data bits instead of 16. Extended Unformatted Pages have identical flag bits as the Unformatted Pages. The remaining 42 data bits are part of the 42-bit Unformatted Code Field. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the DUT s receiver will see the Traffic Generator s signaling. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: 1. Establish a connection (not a link) to the DUT. 2. Use the Traffic Generator to send FLPs such that the DUT will be forced to transmit extended Unformatted Pages. 3. Observe all Next Page transmissions from the DUT. Observable Results: a. The DUT should transmit properly formatted extended Unformatted Pages. Possible Problems: None.

22 Test #28.3.4: Null Message Page Generation for extended Next Pages Purpose: To verify that the device under test transmits proper Null Message pages if it completes sending extended Message Pages and extended Unformatted Pages before its link partner. References: [1] IEEE Std : subclauses , , , , , Annex 28C, 28C.2 [2] IEEE P802.3an D3.1: Annex 28C Resource Requirements: Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the line monitor with minimal distortion. Traffic Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: Once a device has finished sending extended Message Pages and extended Unformatted Pages, it is required to send Null Message Pages until its link partner is done as well. An extended Null Message Page is defined as an extended Message Page that contains the Message Code Field (bits M[10:0]). This test is designed to verify that once the device under test completes its transmission of extended Message and extended Unformatted Pages, it sends out valid extended Null Message Pages until its link partner is done as well. Alternatively, a device may solely transmit extended Next Pages containing extended Null Message codes. This would allow a device with no extended Next Page data to transmit and still receive extended Next Page information from its link partner. Note that extended Null Message Pages contain a single Message Code Field, as described above. All other bits within the Unformatted Code Field of the extended Message Page are to be transmitted as zero. Test Setup: Using Cat 5 cords, connect the DUT and the Traffic Generator to the Line Monitor such that the traffic generator s signaling will be seen by the DUT s receiver. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: Part a: Send More Next Pages than DUT has to transmit 1. Use the Traffic Generator to send the DUT validly formed Base Pages and extended Next Pages with NP=1 and proper Toggle bit values. 2. Continue sending extended Next pages until the DUT writes a 0 to the NP bit in its extended Next Page.

23 3. Monitor the extended Next Pages transmitted by the DUT. Count the number (n) of extended Next Pages (not FLPs) sent by the DUT. Part b: Send same number of Next Pages as DUT has to transmit 4. Repeat step 1 above, but send 'n' extended Next Pages to the DUT (where 'n' is the value found in part a, the number of pages the DUT transmits), setting NP=0 in the final extended Next Page sent to the DUT. 5. Monitor the next pages transmitted by the DUT. Observable Results: a. The DUT's last two Next Pages should contain validly formed extended Null Message Pages. b. INFORMATIVE: When both devices exchange the same number of Next Pages, there is no need to transmit extended Null Message Pages. However, if a device did do this, it would be considered acceptable (though wasteful) as long as the page sent by the DUT before the extended Null Message Page still had NP=1. Possible Problems: None

24 Proposed modifications to Management System Test Suite v2.6 The current test suite may be found here, Note: The modifications proposed in this document will be incorporated into the above test suite upon ratification of IEEE 802.3an-2006.

25 Test #1.2: Base Page Technology Ability Field Purpose: To verify that the DUT s management advertises valid technology ability field codes. References: [1] IEEE Std : subclauses , , , , , , , Annex 28A, Annex 28B, Annex 28B.1, Annex 28B.2 [2] IEEE P802.3an D3.1: subclause Resource Requirements: Line Monitor: A system capable of detecting and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The monitor should allow the NLPs to pass through while minimally impacting the channel. Last Modification: February 8, 2006 Discussion: This test is designed to verify that the DUT transmits Link Code Words whose technology ability field accurately reflects the capabilities of the device and the current management settings. The technology ability field reflects speed capabilities of the physical layer, duplex capabilities of the MAC layer, and flow control capabilities of the MAC control layer. A device must never advertise capabilities that it does not possess. Through management, the user often has the ability to specify which capabilities are desired which may further restrict the abilities advertised. In this test, the technology ability field advertised by the device is verified to be within the capability set of the device, and reflects the desired mode set in management. Test Setup: Using a Cat 5 cord, connect the DUT s transmitter to the Line Monitor. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: 1. Configure the DUT to send FLP bursts. 2. Monitor the transmitted bursts. 3. Observe the data present in several bursts. 4. If available via the DUT s management, modify the desired (advertised) ability. This may include turning on/off: 10BASE-T half duplex, 10BASE-T full duplex, 100BASE-TX half duplex, 100BASE-TX full duplex, PAUSE, ASYM_DIR PAUSE, and extended Next Page. For each modifiable ability, repeat steps 1-3. Observable Results: a. The technology ability field should advertise the proper abilities as indicated in Table for the device s capability and current management setting. b. The DUT should not advertise any abilities that it does not possess Possible Problems: None.

26 Test # 1.4: 10GBASE-T Abilities Purpose: To verify that the management of a 10GBASE-T DUT advertises valid capabilities. References: [1] IEEE P802.3an D3.1: section , subclause Resource Requirements: Line Monitor: A system capable of detecting and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The monitor should allow the NLPs to pass through while minimally impacting the channel. NLP Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs). Last Modification: February 8, 2006 Discussion: This test is designed to verify that the 10GBASE-T DUT transmits capabilities that accurately reflect the capabilities of the device and the current management settings. A device must never advertise capabilities that it does not possess. Through management, the user may have the ability to specify which capabilities are desired which further restricts the abilities advertised. In this test, the 10GBASE-T capabilities advertised by the device in the extended Message Page are verified to be within the capability set of the device, and reflect the desired mode set in management. Test Setup: Using Cat 5 cords, connect the DUT and the NLP Generator to the Line Monitor such that the Traffic Generator s signaling will be seen by the DUT s receiver. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: 1. Use the NLP Generator to complete the exchange of the Base Page sent by the DUT during Auto-Negotiation. 2. Monitor the second page, which should be the first extended Message Page sent by the DUT. 3. If available via the DUT s management, modify the desired (advertised) ability. This may include turning on/off: 1000BASE-T half duplex, 1000BASE-T full duplex, Loop Timing, Manual Master, Manual Slave, LD THP Setting, and LD PMA Training. For each modifiable ability, repeat steps 1-3. Observable Results: a. The page should advertise the proper abilities as indicated in Table XX for the device s capability and current management setting. The DUT should not advertise any abilities that it does not possess. [Probably should add some more text here about the other settings (loop timing, THP startup, PMA training )] Possible Problems: None.

27 Test #2.1 Speed Resolution and Verification Purpose: To verify that the DUT resolves a link to the highest speed possible. References: [1] IEEE Std : subclause , Annex 28B.3 [2] IEEE P802.3an D3.1: section , subclause , Annex 28B.3 Resource Requirements: Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the line monitor with minimal distortion. NLP Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: When a device has completed the Auto-Negotiation process, before a link can be established, the device must resolve the link in a certain way. This link resolution depends upon the abilities of the two devices connected and the priority of these abilities. With regards to speed, the order of priority (highest to lowest) is as follows: 10GBASE-T full duplex, 1000BASE-T full duplex, 1000BASE-T half duplex, 100BASE-T2 full duplex, 100BASE-TX full duplex, 100BASE-T2 half duplex, 100BASE-T4, 100BASE-TX half duplex, 10BASE-T full duplex, and 10BASE-T half duplex. Two devices should resolve a link to the highest common speed between the devices. Test Setup: Using Cat 5 cords, connect the DUT and the NLP Generator to the Line Monitor such that the Traffic Generator s signaling will be seen by the DUT s receiver. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: 1. If necessary, configure the DUT to advertise all supported technology speeds. 2. Provide a series of FLPs to the DUT advertising a single speed, such that the DUT will enter the FLP LINK GOOD CHECK state. To advertise some technologies, a Next Page exchange may be required, this would require the DUT to support Next Page exchange and the Base Page sent to the DUT would have to be followed by the appropriate Message Page and Unformatted Pages required by the technology. 3. Observe transmissions from the DUT. Part a: 4. Repeat steps 2&3 varying the abilities to be received by the DUT to the abilities: 10BASE-T (full duplex & half duplex), 100BASE-TX (full duplex & half duplex), 100BASE-T4, 100BASE-T2(full duplex & half duplex), 1000BASE-T(full duplex & half duplex), and 10GBASE-T full duplex. Part b: 5. Repeat steps 2 and 3 but modify step 2 such that all abilities that the DUT supports are advertised in the FLPs received by the DUT.

28 Part c: 6. Repeat steps 2 and 3, but advertise no speed. Observable Results: a. In step 4, the DUT should attempt to establish a link only when a supported technology is advertised, and should refuse a link when an unsupported technology is advertised. b. In step 5, the DUT should attempt to establish a link at the highest common speed. c. In step 6, the DUT should not establish a link with a device that does not advertise any abilities. Possible Problems: If the DUT does not support Next Page exchange, then the 100BASE-T2, 1000BASE-T, and 10GBASE-T abilities cannot be tested.

29 Test #2.5: 10GBASE-T Master-Slave Resolution Purpose: To verify that the MASTER-SLAVE configuration for 10GBASE-T links is resolved properly according to Table XX References: [1] [References need to be added and checked.] Resource Requirements: Line Monitor: A system capable of detecting, time-stamping, and recording normal link pulses (NLPs) on both the receive and transmit channels of the DUT. The channel signaling should pass through the line monitor with minimal distortion. NLP Generator: A system capable of generating and transmitting normal link pulses (NLPs) and fast link pulses (FLPs) while connected to the receiver of the DUT. Last Modification: February 8, 2006 Discussion: Before a 10GBASE-T link can be established between two devices, one device must resolve to be the MASTER, and the other device must resolve to be the SLAVE. During the extended Next Page exchange, one extended Message Page is transmitted that is used to decide the MASTER-SLAVE resolution. Bit U13 of the extended Unformatted Code Field shows whether the device is a single-port or multiport device, and bits U11 and U12 of this page hold the manual configuration values for MASTER-SLAVE resolution. Loop timing support is indicated in bit U17. Bits U1:U10 contain a random MASTER-SLAVE seed, which is used when devices of the same type are connected together. When both devices support loop timing, or when both devices do not support loop timing, the following resolution table will be used. When only one of the two devices supports loop timing, that device will be forced to SLAVE and its link partner to MASTER. Local Device Type Remote Device Type Local Device Resolution Remote Device Resolution single-port device multiport device SLAVE MASTER single-port device manual_master SLAVE MASTER manual_slave manual_master SLAVE MASTER manual_slave multiport device SLAVE MASTER multiport device manual_master SLAVE MASTER manual_slave single-port device SLAVE MASTER multiport device single-port device MASTER SLAVE multiport device manual_slave MASTER SLAVE manual_master manual_slave MASTER SLAVE manual_master single-port device MASTER SLAVE single-port device manual_slave MASTER SLAVE manual_master multiport device MASTER SLAVE

30 multiport device multiport device single-port device single-port device manual_slave manual_slave The device with the higher SEED value is configured as MASTER, otherwise SLAVE. The device with the higher SEED value is configured as MASTER, otherwise SLAVE. MASTER-SLAVE configuration fault manual_master manual_master MASTER-SLAVE configuration fault The device with the higher SEED value is configured as MASTER, otherwise SLAVE. The device with the higher SEED value is configured as MASTER, otherwise SLAVE. MASTER-SLAVE configuration fault MASTER-SLAVE configuration fault Test Setup: Using Cat 5 cords, connect the DUT and the NLP Generator to the Line Monitor such that the Traffic Generator s signaling will be seen by the DUT s receiver. Terminate the DUT s transmit channel with a 100Ω line termination. Procedure: Part a (both devices support loop timing or both devices do not support loop timing)): 1. Send a series of FLPs to proceed through the Auto-Negotiation process with the first extended Message Page containing U11:U13 set to 100, and U1:U10 set to a random value, and with U17 set to match that of the DUT. 2. Check whether the DUT has resolved the link to be MASTER or SLAVE by observing if 10GBASE-T Idle signaling is transmitted. 3. Repeat steps 1 and 2, changing the contents of the extended Message Pages such that the different resolutions, shown in Table XX are tested. 4. Repeat steps 1 3, using the same random seed value as the DUT. Part b (only one device supports loop timing): 5. Repeat steps 1 4, setting the value of bit U17 opposite that of the DUT. Observable Results: a. The DUT should resolve the link according to Table XX, and should restart Auto- Negotiation after receiving an extended Message Page with an identical random seed value to its own. b. The DUT should resolve to SLAVE if it does support loop timing, and to MASTER if it does not support loop timing. Possible Problems: None

31 Proposed modifications to Management Register Test Suite v2.7 The current test suite may be found here, Note: The modifications proposed in this document will be incorporated into the above test suite upon ratification of IEEE 802.3an As of February 8, 2006, these additional tests are still under development. They will be added to this document as soon as possible.