Data Center Bridging Consortium

Transcription

1 Data Center Bridging Consortium 802.1Qaz DCB Capability Exchange Protocol Test Suite Report UNH-IOL 121 Technology Drive, Suite 2 Durham, NH Data Center Bridging Consortium dcblab@iol.unh.edu John Smith March 11, 2011 Company Name Report Rev. 1.0 Street Address City, State, Zip Code Enclosed are the results from the 802.1Qaz DCB Capability Exchange Protocol Conformance testing performed on: Storage Device The test suite referenced in this report is available at the UNH-IOL website: ftp://ftp.iol.unh.edu/pub/dcb/test_suite/802.1qaz_dcb_capability_exchange_protocol_test_suite_(v1.7).pdf Issues Observed While Testing : The DUT was observed to act on a malformed Priority-based Flow Control TLV : The DUT was observed to transmit a malformed FCoE Support TLV : The DUT was observed to respond to multiple LLDP neighbors For specific details regarding issues please see the corresponding test result. Testing Completed 3/11/2011 John Tester John Tester jtester@iol.unh.edu Review Completed 3/11/2011 John Reviewer John Reviewer jreviewer@iol.unh.edu

2 Digital Signature Information This document was created using an Adobe digital signature. A digital signature helps to ensure the authenticity of the document, but only in this digital format. For information on how to verify this document s integrity proceed to the following site: If the document status still indicates Validity of author NOT confirmed, then please contact the UNH-IOL to confirm the document s authenticity. To further validate the certificate integrity, Adobe 6.0 should report the following fingerprint information: MD5 Fingerprint: 4B9E 655C 582A EF 7C0A BCED 1EBF SHA-1 Fingerprint: 02CB 7B8F F1EC 5921 DE3F A21B 6606 B809 12D9 DD0E UNH-IOL DCB Consortium 2 Report Rev. 1.0

3 Table 1: DUT and Test Setup Information DUT Details Manufacturer Acme Corporation Model Prototype Firmware Revision 27B/6 Hardware Revision X300 Driver Version v1.0 Additional Comments/Notes Configuration Commands: runconf.sh Table 2: Result Key The following table contains possible results and their meanings: Result PASS PASS with Comments FAIL Warning Informative Refer to Comments Not Applicable Not Available Borderline Not Tested Interpretation The Device Under Test (DUT) was observed to exhibit conformant behavior. The DUT was observed to exhibit conformant behavior however an additional explanation of the situation is included, such as due to time limitations only a portion of the testing was performed. The DUT was observed to exhibit non-conformant behavior. The DUT was observed to exhibit behavior that is not recommended. Results are for informative purposes only and are not judged on a pass or fail basis. From the observations, a valid pass or fail could not be determined. An additional explanation of the situation is included. The DUT does not support the technology required to perform these tests. Due to testing station or time limitations, the tests could not be performed. The observed values of the specified parameters are valid at one extreme, and invalid at the other. Not tested due to the time constraints of the test period. UNH-IOL DCB Consortium 3 Report Rev. 1.0

4 Table 3: Test Equipment The following test equipment was used in performing 802.1Qaz DCB Capability Exchange Protocol Conformance Testing: Testing Equipment Software Traffic Analyzer Brand and Version Information DCB Testing Tool Wireshark Test Configuration The following configuration was used in performing 802.1Qaz DCB Capability Exchange Protocol Conformance Testing: UNH-IOL DCB Consortium 4 Report Rev. 1.0

5 Test Results: Group 1: ETS Configuration and Recommendation Capability : Transmission of a Well Formed ETS Configuration TLV PASS : Transmission of a Well Formed ETS Recommendation TLV PASS : Validation of the ETS Configuration TLV Willing Bit PASS : Gracefully Ignore Malformed ETS Recommendation TLV PASS UNH-IOL DCB Consortium 5 Report Rev. 1.0

6 Group 2: Priority-based Flow Control Capability : Transmission of a Well Formed Priority-based Flow Control TLV PASS : Validation of the Priority-based Flow Control TLV Willing Bit PASS : Correct Setting of Remote Willing PASS : Gracefully Ignore Malformed Priority-based Flow Control TLV FAIL 1 UNH-IOL DCB Consortium 6 Report Rev. 1.0

7 Group 3: Application Priority Capability : Transmission of a Well Formed Application Priority TLV PASS : Gracefully Ignore Malformed Application Priority TLV PASS : Transmission of FCoE Support TLV FAIL : Transmission of iscsi Support TLV PASS UNH-IOL DCB Consortium 7 Report Rev. 1.0

8 Group 4: Congestion Notification Capability : Transmission of a Well Formed Congestion Notification TLV PASS : Gracefully Ignore Malformed Congestion Notification TLV PASS UNH-IOL DCB Consortium 8 Report Rev. 1.0

9 Group 5: System Configuration : DCBX Enabled by Default PASS : Multiple LLDP Neighbors FAIL 3 Notes: 1. The DUT was observed to act on a malformed Priority-based Flow Control TLV; it is expected that the DUT would not act on any malformed TLV frame. 2. The DUT was observed to transmit a malformed FCoE Support TLV; it is expected that the DUT would send a properly configured FCoE Support TLV, report two Applications in the Application Priority Table, have both Sel fields set to 1, and have one be Ethertype 8914 while the other be Ethertype The DUT was observed to respond to multiple LLDP neighbors; it is expected that the DUT would not react to any of the DCBX frames transmitted. UNH-IOL DCB Consortium 9 Report Rev. 1.0