Changes between Version 22 and Version 23 of WARPLab/QuickStart
- Timestamp:
- Mar 29, 2013, 1:23:31 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WARPLab/QuickStart
v22 v23 72 72 73 73 {{{ 74 >ping -l 9000 10.0.0.174 >ping -l 8000 10.0.0.1 75 75 }}} 76 76 77 This will send 9000 byte pings to the boards. If the board responds, Windows will tell you how many bytes were actually returned. For example, we receive the following using one of our PCs:77 This will send 8000 byte pings to the board. If the board responds, Windows will tell you how many bytes were actually returned. For example, we receive the following using one of our PCs: 78 78 79 79 {{{ 80 Pinging 10.0.0.1 with 9000 bytes of data:81 Reply from 10.0.0.1: bytes=8 984 (sent 9000) time=3ms TTL=3282 Reply from 10.0.0.1: bytes=8 984 (sent 9000) time=3ms TTL=3283 Reply from 10.0.0.1: bytes=8 984 (sent 9000) time=3ms TTL=3284 Reply from 10.0.0.1: bytes=8 984 (sent 9000) time=3ms TTL=3280 Pinging 10.0.0.1 with 8000 bytes of data: 81 Reply from 10.0.0.1: bytes=8000 time=2ms TTL=32 82 Reply from 10.0.0.1: bytes=8000 time=2ms TTL=32 83 Reply from 10.0.0.1: bytes=8000 time=2ms TTL=32 84 Reply from 10.0.0.1: bytes=8000 time=2ms TTL=32 85 85 }}} 86 86 87 This shows the 8984 bytes were returned. 87 This shows that the 8000 byte ping packet was returned, and you computer and switch appear to support communicating with a WARP board with jumbo frames. If, however, you receive ping responses that look like this: 88 89 {{{ 90 Pinging 10.0.0.1 with 8000 bytes of data: 91 Reply from 10.0.0.1: bytes=1472 (sent 8000) time<1ms TTL=32 92 Reply from 10.0.0.1: bytes=1472 (sent 8000) time<1ms TTL=32 93 Reply from 10.0.0.1: bytes=1472 (sent 8000) time<1ms TTL=32 94 Reply from 10.0.0.1: bytes=1472 (sent 8000) time<1ms TTL=32 95 }}} 96 97 Then only 1472 bytes were returned of the sent 8000. This means that the packets were fragmented and that the MTU was not set high enough to support the 8000 byte ping packet. 88 98 89 99 '''Linux/OSX:''' Open a terminal and type the following: 90 100 101 {{{ 102 > ping -s 8000 10.0.0.1 103 }}} 104 105 This will send 8000 byte pings to the board. The board should respond to these pings and return something similar to the following: 106 107 {{{ 108 PING 10.0.0.1 (10.0.0.1): 8000 data bytes 109 5976 bytes from 10.0.0.1: icmp_seq=1 ttl=32 time=2.356 ms 110 wrong total length 5996 instead of 8028 111 }}} 112 113 If, however, the MTU is not set high enough to support the 8000 byte pings, then the board may respond with a smaller reply: 114 115 {{{ 116 PING 10.0.0.1 (10.0.0.1): 8000 data bytes 117 8008 bytes from 10.0.0.1: icmp_seq=0 ttl=32 time=2.928 ms 118 8008 bytes from 10.0.0.1: icmp_seq=1 ttl=32 time=3.071 ms 119 }}} 120 91 121 ==== WARPLab Test ==== 122 If the ping test indicates that your PC and your Ethernet switch support jumbo frames, the next step is to see if WARPLab works with jumbo frames. When node objects are first set up in a WARPLab script, they run a test with their associated boards to see what maximum payload size can be supported. First, re-run the [wiki:WARPLab7/Reference/Utility#wl_setup 'wl_setup'] function in {{{M_Code_Reference}}} and select that you would like to enable jumbo frame support. Next, ensure one WARP board is programmed with the WARPLab bitstream and configured with DIP switch '0'. Then, copy and paste the following lines to the MATLAB command line: 92 123 93 ==== Known Compatible Hardware ==== 124 {{{ 125 clear; 126 node = wl_initNodes(1); 127 disp(node.transport.maxPayload) 128 }}} 94 129 95 ==== Known Partially Compatible Hardware ==== 130 This will display the payload size the WARPLab has configured itself to use. For one of our PCs, this value returns as {{{8960}}}, showing the jumbo frame support is correctly working. 96 131 97 ==== Known Incompatible Hardware ==== 132 ==== Known Hardware Compatibility ==== 133 It is impossible to form a definitive list of hardware that is compatible with jumbo frame support, but we will maintain a list of observed setups and their compatibility. If you try jumbo frames and have a hardware setup that does or does not work with them, please post to [http://warpproject.org/forums/ the WARP forums] so we can add them to the list. 134 135 '''Known Compatible:''' 136 137 '''Known Partially Compatible:''' 138 139 '''Known Incompatible:''' 140 141 142 143 98 144 99 145 === pnet Toolbox ===