Gigabit Ethernet Services

The test suites on this page may be downloaded and used for internal purposes only. The test suites may not be commercialized in any way without express permission of the UNH-IOL.

Table of contents

Introduction     [Top]

The Gigabit Ethernet Consortium currently offers the following Services. These documents are constantly being updated to improve readability and to reflect the current specifications. Please contact us if you would like more information or have questions about the Gigabit Ethernet Consortium

Document Certification     [Top]

When testing based on the following test suites is performed, all reports generated will be digitally signed using an Adobe digital certificate. Upon reception of the report, the recipient can verify its authenticity using the instructions provided at http://www.iol.unh.edu/certifyDoc.

 

IOL     [Top]

Interoperability     [Top]

Ethernet Interoperability Test Suite [Top]
Last Modified: 6/7/2007
Revision: 2.4
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers identify problems that IEEE 802.3 devices may have in establishing link and exchanging packets with each other. The tests do not determine if a product conforms to the IEEE 802.3 standard. Rather, they provide one method to verify that the two devices can exchange packets within the bit error ratio specifications established by the IEEE 802.3 standard when operating over a worst-case compliant channel. The interoperability test suite focuses on two areas of functionality to simulate a real-world environment: the exchange of packets to produce a packet error ratio that is low enough to meet a desired bit error ratio, and the ability to detect and establish a link at the optimal speed between two devices that make up a link segment. A third area covers specific cable testing.
Notes: Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other compliant 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 environments.

Previous versions of this test suite include: v2.3, v2.2, v2.1, v2.0, v2000_08_02, v2000_08_01.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 

Conformance     [Top]

Clause 4 Media Access Control (MAC) Test Suite [Top]
Last Modified: 2/3/2006
Revision: 4.6
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 4 Media Access Control (MAC) based products. The tests do not determine if a product conforms to the IEEE 802.3, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a MAC device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other 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 environments.
Notes: Previous versions of this test suite include: v4.1, v4.2, v4.3, v4.4, v4.5.
1000BASE-X MAC Test Suites: v1.0, v2003_05_20.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 31 Flow Control Test Suite [Top]
Last Modified: 2/3/2006
Revision: 1.3
Status: Fully Documented (Active)
Testing Days Needed: 2 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 31 Flow Control (PAUSE) implementations. The tests do not determine if a product conforms to the IEEE 802.3, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within an implementation. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other 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 environments.
Notes: Previous versions of this test suite include: v1.2, Gigabit Ethernet 1000BASE-X: v1997_JUNE, v1999_JULY, v1.0, v1.1.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 36 1000BASE-X (Fiber) PCS Test Suite [Top]
Last Modified: 2/3/2006
Revision: 2.1
Status: Fully Documented (Active, see notes)
Testing Days Needed: 1 day
Abstract: This suite of tests has been developed to help implementers evaluate the functionality of their Clause 36 Physical Coding Sublayer (PCS) based products. The tests do not determine if a product conforms to IEEE 802.3 standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a PCS device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other 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 environments.
Notes: Test #36.3.1 Under development.

Previous versions of this test suite include: v1997_SEP, v1997_OCT, v1.8, v1.9, v2.0.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 37 1000BASE-X (Fiber) Auto-Negotiation Test Suite [Top]
Last Modified: 1/3/2007
Revision: 1.4.4
Status: Fully Documented (Active, see notes)
Testing Days Needed: 2 Days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 37 Auto-Negotiation based products. The tests do not determine if a product conforms to the IEEE 802.3 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.
Notes: Previous versions of this test suite include: v1.0, v1.0a, v1.0b, v1.1, v1.3, v1.4, v1.4.1, v1.4.2, v1.4.3.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 28 Auto-Negotiation State Machine Test Suite [Top]
Last Modified: 1/4/2007
Revision: 5.9
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 28 Auto-Negotiation based products. The tests do not determine if a product conforms to the IEEE 802.3 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.
Notes: Previous versions of this test suite include: v0.5, v1.0, v1.1, v2.0, v3.01, v3.10, v4.0.2, v4.0.3, v5.0, v5.1, v5.2, v5.3, v5.4, v5.5, v5.6, v5.7, v5.8.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 28 Auto-Negotiation Next Page Test Suite [Top]
Last Modified: 2/3/2006
Revision: 2.3
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 28 Auto-Negotiation based products. The tests do not determine if a product conforms to the IEEE 802.3 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 capable 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.
Notes: Previous versions of this test suite include: v1.0, v2.0, v2.1, v2.2.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 28 Auto-Negotiation Management System Test Suite [Top]
Last Modified: 2/3/2006
Revision: 2.6
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 28 Auto-Negotiation based products. Though the IOL's Fast Ethernet Consortium has long been performing a Clause 28 Auto-Negotiation test suite targeting the functionality of the Auto-Negotiation state machines specified in clause 28 of IEEE 802.3, that "state machine" test suite rarely focused on system level device issues. System level issues in this context refer to interoperability problems which occur between an auto-negotiating end-user device and its link partner even though the device's Auto-Negotiation state machines and associated registers may be functioning properly. These issues typically occur as a result of a problem with the device's management, whereby the underlying Auto-Negotiation mechanism may perform properly, but then the device's management acts or reacts inappropriately. While many end-user devices utilize the same underlying Auto-Negotiation mechanism (typically embedded in a PHY), most devices have very different management and user level control. The focus of the tests within this Auto-Negotiation Management System Test Suite is to examine the functionality of the Auto- Negotiation management entity of a device.
Notes: Previous versions of this test suite include: v1.0, v2.0, v2.1, v2.3, v2.4, v2.5.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 28 Auto-Negotiation Management Register Test Suite [Top]
Last Modified: 7/20/2006
Revision: 3.0
Status: Fully Documented (Active)
Testing Days Needed: 3 days
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 22, Clause 28, and Clause 40 Auto- Negotiation based products. The tests do not determine if a product conforms to the IEEE 802.3, 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.
Notes: Previous versions of this test suite include: v1.0.5, v1.04, v2.0, v2.1, v2.2, v2.3, v2.4, v2.5, v2.6, v2.7, v2.8, v2.9.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 38 1000BASE-X Optical PMD [Top]
Last Modified: 8/22/2008
Revision: .7
Status: Draft (Active)
Testing Days Needed: 2 days
Abstract: This suite of tests pertains to the operation of the transmitter and the determination of various parametric values as defined in Std. IEEE 802.3 – 2005 Clause 38 for 1000 Base-X optical devices.
Notes: Previous versions of this test suite include: v.6
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 39 1000BASE-CX PMD Test Suite [Top]
Last Modified: 7/8/2009
Revision: .2
Status: Draft (Active)
Testing Days Needed: 1 week
Abstract: This suite of tests pertains to the operation of the transmitter and the determination of various parametric values as defined in Std. IEEE 802.3 – 2008 Clause 38 for 1000 Base-CX devices.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 40 Auto-Crossover Test Suite [Top]
Last Modified: 3/24/2009
Revision: 2.2
Status: Fully Documented (Active)
Testing Days Needed: 1 day
Abstract: This suite of tests has been developed to help implementers evaluate the functioning of their Clause 22, Clause 28, and Clause 40 Auto-Negotiation based products. The tests do not determine if a product conforms to the IEEE 802.3, 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.
Notes: Previous versions of this test suite include: v1.0, v1.1, v1.2, v1.3, v1.4, v1.5, v1.6, v1.7, v1.8, v2.0, v2.1.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 
Clause 40 PMA Test Suite [Top]
Last Modified: 5/20/2008
Revision: 2.5
Status: Fully Documented (Active)
Testing Days Needed: 2 days
Abstract: These tests are designed to determine if a product conforms to specifications defined in the IEEE 802.3 standard. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other 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 properly in many 1000BASE-T environments.
Notes: Tests in section 1 of the PMA Test Suite require the ability to enable Transmitter test modes as defined in clause 40.6 of the IEEE 802.3-2005 Standard (see our What are the 1000-T PMA Test Modes? Tutorial). Additionally, access to the TX_TCLK is required for a full Transmitter Timing Jitter test (see our What is the TX_TCLK? tutorial). A modified version can be performed without TX_TCLK access, but the results may be inconclusive.

Previous versions of this test suite include: v1.0, v1.1, v1.2, v2.0, v2.1, v2.2, v2.3. v2.4.
Test Suite: PDF Click to download PDF
Sample Report: PDF Click to download PDF
 

 


Testing Programs