Data Center Bridging Consortium
Total Page:16
File Type:pdf, Size:1020Kb
Data Center Bridging Consortium 802.1Qaz DCB Exchange Protocol Test Suite Version 1.9 Technical Document Last Updated: April 10, 2012 Data Center Bridging Consortium HTTP://WWW.IOL.UNH.EDU/CONSORTIUMS/DCB InterOperability Laboratory 121 Technology Drive, Suite 2 University of New Hampshire Durham, NH 03824 Phone: +1-603-862-0701 © 2012 University of New Hampshire InterOperability Laboratory Table of Contents Table of Contents...........................................................................................................................2 Modification Record......................................................................................................................3 Acknowledgments..........................................................................................................................4 Introduction....................................................................................................................................5 References.......................................................................................................................................7 Test Setup.......................................................................................................................................8 Group 1: ETS Configuration and Recommendation Capability...............................................9 TEST #38.1.1: TRANSMISSION OF A WELL FORMED ETS CONFIGURATION TLV.............................10 TEST #38.1.2: TRANSMISSION OF A WELL FORMED ETS RECOMMENDATION TLV.........................11 TEST #38.1.3: VALIDATION OF THE ETS CONFIGURATION TLV WILLING BIT................................12 TEST #38.1.4: GRACEFULLY IGNORE MALFORMED ETS RECOMMENDATION TLV..........................14 Group 2: Priority-based Flow Control Capability...................................................................16 TEST #38.2.1: TRANSMISSION OF A WELL FORMED PRIORITY-BASED FLOW CONTROL TLV............17 TEST #38.2.2: VALIDATION OF THE PRIORITY-BASED FLOW CONTROL TLV WILLING BIT...............18 TEST #38.2.3: CORRECT SETTING OF REMOTE WILLING.................................................................20 TEST #38.2.4: GRACEFULLY IGNORE MALFORMED PRIORITY-BASED FLOW CONTROL TLV.............21 Group 3: Application Priority Capability.................................................................................22 TEST #38.3.1: TRANSMISSION OF A WELL FORMED APPLICATION PRIORITY TLV...........................23 TEST #38.3.2: GRACEFULLY IGNORE MALFORMED APPLICATION PRIORITY TLV............................24 TEST #38.3.3: TRANSMISSION OF FCOE SUPPORT TLV................................................................25 TEST #38.3.4: TRANSMISSION OF ISCSI SUPPORT TLV................................................................26 Group 4: Congestion Notification Capability...........................................................................27 TEST #38.4.1: TRANSMISSION OF A WELL FORMED CONGESTION NOTIFICATION TLV.....................28 TEST #38.4.2: GRACEFULLY IGNORE MALFORMED CONGESTION NOTIFICATION TLV......................29 Group 5: System Configuration.................................................................................................30 TEST #38.5.1: DCBX ENABLED BY DEFAULT...............................................................................31 TEST #38.5.2: MULTIPLE LLDP NEIGHBORS................................................................................32 © 2012 University of New Hampshire InterOperability Laboratory Modification Record 1. January 4, 2009 Initial Version (mhagen, rzarick) 2. March 5, 2010 Updated to latest standards, added Congestion NotificationTLV (mhagen) 3. October 8, 2010 Updated to draft 2.0 standard (mhagen) 4. December 15, 2010 Fixed ETS Configuration and PFC Configuration tests (mhagen) 5. January 6, 2011 Fixed a mistake in Test 38.3.2 (mhagen) 6. January 6, 2011 Rev 1.5 – cleaned up ETS Recommendation and Configurations (mhagen) 7. January 7, 2011 Fixed a mistake in Test 38.1.4 (dshea) 8. January 31, 2011 Fixed Malformed TLV tests (dshea) 9. March 18, 2011 Updated to draft 2.4 standard (mhagen) 10. April 10, 2012 Updated to the final version of the standard (mhagen) © 2012 University of New Hampshire InterOperability Laboratory Acknowledgments The University of New Hampshire would like to acknowledge the efforts of the following individuals in the development of this test suite. Mikkel Hagen University of New Hampshire Daniel Shea University of New Hampshire Ryan Zarick University of New Hampshire © 2012 University of New Hampshire InterOperability Laboratory 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. These tests are designed to determine if a DCB product conforms to specifications defined in IEEE Std 802.1Qaz-2011 Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks – Amendment 18: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic Classes (hereafter referred to as “DCBX”). This suite of tests has been developed to help implementers evaluate the functioning of their Data Center Bridging based products. The tests do not determine if a product conforms to the IEEE standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a Data Center Bridging device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other Data Center Bridging devices. However, combined with satisfactory operation in the IOL’s semi-production environment, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function well in most multi-vendor Data Center Bridging 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 detailed section discusses the background information and specifies how 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 Clause followed by 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 short statement describing 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 software, hardware, and test equipment that will be needed to perform the test. The items contained in this section are special test devices, software that must reside on the DUT, or other facilities, which may not be available on all devices. Last Modification This specifies the date of the last modification to this test. 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. © 2012 University of New Hampshire InterOperability Laboratory Test Setup The setup section describes in detail the configuration of the test environment and includes a block diagram for clarification as well as information such as the interconnection of devices, what monitoring equipment should capture, what the generation equipment should send, and any other configuration information vital to carrying out the test. 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 will often be interspersed with observable results. Observable Results The observable results section lists observables 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. Note that complete delineation between the observables in the Procedure and Observable Results is virtually impossible. As such a careful note should be made of the requirements in both sections. In certain cases, it may be necessary to modify certain steps in the Procedure section while doing the actual tests so as to be able to perform the tests. In such cases, the modifications will be noted in the summary report. Possible Problems This section provides some clues to look for if the test does not yield the expected results. Legend For reasons of brevity, the following abbreviation has been used in the Test Suite: DCBX Data Center Bridging Capability Exchange DUT Device Under Test ETS Enhanced Transmission Selection PFC Priority-based Flow Control TS Testing Station © 2012 University of New Hampshire InterOperability Laboratory References The following documents are referenced