Wiki code for NIC Driver Test Suite

Hide Line numbers
1: == NIC Driver Test Suite ==
2: 
3: ==== Announcements ====
4: 
5: See [[Driver News>>Community Group device_drivers.drivernews]] for announcements about NIC drivers.
6: 
7: ==== Related Information ====
8: 
9: * [[MAXQ NIC test>>Community Group device_drivers.maxq]] is a test suite based on ##netperf##
10: * [[WIFI test checklist>>Community Group device_drivers.wifi_test]] is a self-test guide for WiFi driver development
11: 
12: === NICDRV Introduction ===
13: 
14: This project is for the NIC test suites development. You can download the NIC driver test suite and learn about nic driver testing from this link. Everyone’s contribution and feedback is important to this project.
15: 
16: NICDRV is a testsuite developed by us for NIC drivers testing. It is used to qualify the NIC’s functionalities working on Solaris and supports both SPARC and X86 platforms. We analyzed the functionalities of all kinds of NICs and refined the testing criteria.
17: 
18: NICDRV contains necessary network applications to verify the working of NIC drivers, including network data transmission at IPv4/IPv6, transmission at promiscuous mode, transmission based on all kinds of packet length, data corruption verifying, multicast transmission, ndd-parameters setting, working-mode testing, Statistics, vlan, link aggregation, loading/unloading drivers and etc.NICDRV also include stress testing
19: 
20: NICDRV is implemented based on our existing Solaris Test Framework (STF), so it can be configured and executed automatically instead of running every test case manually. Test report will also be produced automatically after the test ends.
21: 
22: NICDRV uses code coverage analysis to evaluate test effectiveness. While the test is running, all functions of the under test NIC driver are called can be recorded by a Dtrace script. At the end of the test, the code coverage rate will be shown. Testers can know which functions of the NIC driver routine are passed and which functions aren’t called. This feature of the NICDRV framework is also used in developing new test cases for NIC.
23: 
24: We designed NICDRV as an open test platform. The test criteria can be adjusted based on the different models of NIC. If it is a high-end NIC, like 10Gb/s NIC, used on transmitting huge network data, testers can select a set of parameters with high level to test. If the NIC is just for low-end usage, a little data being transmitted (like 10Mb/s NIC), testers can adjust the parameters to a lower level. A new set of parameters can be added into NICDRV platform for the new model of NIC as the new test criteria. And also, new test cases can be added into NICDRV easily.
25: 
26: === What Is the Meaning of Each Test Case? ===
27: 
28: |=Case Name|=Type|=Runtime (full)|=Description|=Possible Causes for Failure
29: |test00|functional|2 hours|Data transmitting/receiving
30: Ftp ipv4/ipv6|A wrong root password in config.vars file
31: Big size files cannot be transmitted by the tested driver
32: Disk free space (/var > 2G)
33: IPv6 doesn’t work
34: Hardware chipset error
35: |test01|functional|3 hours|Receiving/transmitting under promiscuous mode
36: Netperf+snoop on/off|Driver cannot support the promiscuous mode
37: Driver cannot work stably with repeatedly promiscuous mode on/off
38: Sessions/connection can not be established
39: Timeout:performance issue to make the driver cost too much time for transmission.
40: Timeout: system or interface hang.
41: |test02|functional|1 hour|Packets lost and zero length data pending
42: ping all packet size|Failed to transfer one or several packets with particular length
43: Driver works unstably
44: Timeout: too slow to ping every packet
45: |test03|functional|2 hours|Data corruption
46: nfs corrupt|Found data corruption
47: An NFS environment mistake (e.g. S10 is different from Snv)
48: |test04|functional|1 hour|Multicast
49: IPmulticast|Failed to join multiple multicast groups
50: |test05|functional|5 minutes|ndd interface
51: ndd read/write command|Some parameters of driver cannot be set by ndd
52: There are some new private parameters that the current NICDRV cannot support in the under test driver
53: |test06|functional|3 hours|Receiving/transmitting on different duplex/speed mode
54: netperf on 10/100/1000Mbps duplex/speed mode|Driver cannot work stably on 10/100/1000Mbps duplex/speed mode
55: Failed to transfer UDP traffic
56: Check the failures of MAXQ
57: |test07|functional|20 minutes|Statistic
58: kstat and netstat counter check|Found statistics errors
59: |test08|functional|2 hours|VLAN
60: VLAN plumb/FTP/nfs corrupt/MAXQ|Failed to create VLAN interface
61: Failed to access by rsh
62: Check the switch configuration if the under test interfaces are connected by a switch.
63: The failures of test00 test01 test02 and test03 could cause test08 to fail
64: Failed to create the maximum number of VLAN interface.
65: |test09|functional|1 hour|Trunking
66: nfs corrupt on trunking interface|Failed to create link aggregation
67: Failed to cleanup after test00-test08
68: The driver cannot support link aggregation, The driver based on GLDv3 is supposed to support link aggregation.
69: |test10|functional|1 hour|load,unload driver
70: Test driver load unload functionality|Driver cannot be attach/detach or plumb/unplumb
71: Driver cost too many memories for one interface
72: |test11|functional|1 hour|DR (dynamic reconfiguration) test
73: Test NIC driver dynamic reconfiguration support|UNSUPPORTED means the under test system cannot support the DR feature, so the test doesn’t run. It’s not a failure.
74: The main platforms that support DR: (TBD)
75: |test12|functional|1 hour|VNIC|The VNIC works unstably if the failure is only in MAXQ
76: Failed to create multiple VNIC interfaces
77: |test13|functional|1.5 hours|dladm (Brussels and Jumbo)|dladm operations on the tested driver failed
78: Changing parameters failed
79: Cannot support jumbo frame feature
80: Driver works unstably in half-duplex mode.
81: |test14|functional|1.5 hours|IPMI (Intelligent Platform Management Interface)|IPMI configuration incorrectly
82: Test machine not support IPMI
83: |netstress|stress|15 hours|netperf (TCP/UDP)|Driver cannot work stably for a long time, like a half day.
84: The under test system cannot support a certain large number of sessions.
85: System or interface hang could cause the test case timeout.
86: |loadunload|stress|6 hours|load/unload with netperf|Found memory leaks after repeatedly loading/unloading driver
87: System or interface hang could cause the test case timeout.
88: |total| |41 hours| | 
89: 
90: === Quick Start ===
91: 
92: [[auto_nicdrv readme>>attach:autonicdrvreadme.txt]]
93: 
94: Install wrapper for nicdrv: [[auto_nicdrv_1109.tar.bz2>>attach:autonicdrv1109.tar.bz2]]
95: 
96: === Source Code, Binary and Package ===
97: 
98: Community Group device_drivers: Projects > NIC Driver Test Suite  
99: 
100: The NICDRV i386 binary is: [[SUNWstc-nicdrv-20090924.i386.tar.bz2>>attach:SUNWstc-nicdrv-20090924.i386.tar.bz2]]
101: 
102: The NICDRV SPARC binary is: [[SUNWstc-nicdrv-20090924.sparc.tar.bz2>>attach:SUNWstc-nicdrv-20090924.sparc.tar.bz2]]
103: 
104: The test suite source is: [[source/xref/test/ontest-stc2/src/suites/net/nicdrv>>http://cvs.opensolaris.org/source/xref/test/ontest-stc2/src/suites/net/nicdrv]]
105: 
106: The test suite source is: [[stcnv-nicdrv-src-20090629.tar.bz2>>attach:stcnv-nicdrv-src-20090629.tar.bz2]]
107: 
108: === How to Build and Use ===
109: 
110: [[nicdrv readme>>attach:nicdrvreadme.txt]]
111: 
112: === NICDRV Baseline Report ===
113: 
114: |=nicdrv Version|=Solaris Build|=x86|=SPARC
115: |2.0|Opensolaris 0906|Function: [[e1000g test report>>attach:journal.soe-x4200m2-13.20090624020656.execute.amd64.txt]]
116: Stress: [[e1000g test report>>attach:journal.soe-x4200m2-13.20090623200626.execute.amd64.txt]]| 
117: |2.0|Solaris nv114|Function: [[e1000g test report>>attach:journal.sol-x4200-4.20090619145110.execute.amd64.txt]]
118: Stress: [[e1000g test report>>attach:journal.sol-x4200-4.20090618153104.execute.amd64.txt]]| 
119: |2.0|Solaris nv116|Function: [[bge test report>>attach:journal.sol-x4200-4.20090618153104.execute.amd64.html]]|Function: [[bge test report>>attach:journal.sol-x4200-4.20090619145110.execute.amd64.txt]]
120: Stress: [[bge test report>>attach:journal.sol-t1000-15.20090623161034.execute.sparcv9.txt]]
121: 
122: === Bugs ===
123: 
124: View the [[nicdrv bug list>>http://bugs.opensolaris.org/search.do?process=1&type=&sortBy=relevance&bugStatus=&perPage=10&bugId=&keyword=&textSearch=&category=driver&subcategory=nic-nicdrv&since=]].
125: 
126: [[Report a bug>>http://defect.opensolaris.org/bz/]] or request a feature for NICDRV.
127: 
128: === How to Participate ===
129: 
130: Join the discussion at NICDRV-interest at sun dot com. Hear from the experts, review archives, and post your questions.
OpenSolaris

Top Menu

Wiki code for NIC Driver Test Suite

Search

Collectives

Community Group

Project

User Group

Subsites

Community Group device_drivers Pages
