231 | | The following snippet shows how the exercise runs the mfperf application and also changes the block size dynamically |
| 231 | The following snippet shows how the exercise runs. As indicated above first we will run mfping between the hosts as described in exercise 1: |
| 232 | [[CollapsibleStart(If not coming from the previous exercise follow these instructions to run mfping)]] |
| 233 | Once the host and router components are up, you can log in to the sender (host identified by GUID 101) and receiver (host identified by GUID 102) host nodes (two separate terminals) and run the 'mfping' application. |
| 234 | |
| 235 | Run the mfping 'server' specifying the application GUID: |
| 236 | |
| 237 | {{{ |
| 238 | #!sh |
| 239 | mfping -s -m 102 -o 101 |
| 240 | }}} |
| 241 | |
| 242 | where "-s" specifies that the host is running as server, "-m" specifies the source guid and "-o" the destination one |
| 243 | |
| 244 | To run the mfping 'client' |
| 245 | |
| 246 | {{{ |
| 247 | #!sh |
| 248 | mfping -c -m 101 -o 102 -n 10 |
| 249 | }}} |
| 250 | |
| 251 | Where "-c" specifies the client is running and "-n" specifies the number of pings between the two nodes. |
| 252 | If successfully executed, the client will display some information similar to the following snippet |
| 253 | |
| 254 | {{{ |
| 255 | #!sh |
| 256 | |
| 257 | root@node1-1:~# mfping -c -m 101 -o 102 -n 10 |
| 258 | 64 bytes received: seq_n=0, time=25.1470 msec |
| 259 | 64 bytes received: seq_n=1, time=23.7070 msec |
| 260 | 64 bytes received: seq_n=2, time=20.0559 msec |
| 261 | 64 bytes received: seq_n=3, time=24.0371 msec |
| 262 | 64 bytes received: seq_n=4, time=23.1831 msec |
| 263 | 64 bytes received: seq_n=5, time=20.3069 msec |
| 264 | 64 bytes received: seq_n=6, time=24.1379 msec |
| 265 | 64 bytes received: seq_n=7, time=19.6230 msec |
| 266 | 64 bytes received: seq_n=8, time=20.3931 msec |
| 267 | 64 bytes received: seq_n=9, time=20.2239 msec |
| 268 | }}} |
| 269 | |
| 270 | [[CollapsibleEnd]] |
| 271 | |