203 | | The extractClickConfig script produces router configurations for your experiment. It also creates a diagram of your experiment. Copy it back to the '''click-example''' directory on your local host so you can view it. There's a copy on each of your router hosts. I've chosen pc336.emulab.net, which is the top router, but it doesn't matter. You'll need to find the host name in the script output above, and then run this command ''on your local machine''. |
204 | | |
205 | | {{{ |
206 | | scp pc336.emulab.net:myslice.png . |
207 | | }}} |
208 | | |
209 | | Once you have '''myslice.png''' on your local machine, open it in a browser or other viewer program. Your slice will look something like the one below (see [attachment:myslice.png]). The overall configuration should be the same, with two end hosts, named hostA and hostB, and four routers (top, left, right, bottom) in a diamond configuration. The host names, interface names, and MAC addresses will be different, depending on the actual resources assigned to your slice. |
| 203 | i. The extractClickConfig script produces router configurations for your experiment. It also creates a diagram of your experiment. Get a copy locally from one of the routers, by typing in a local terminal: |
| 204 | {{{ |
| 205 | scp top:myslice.png |
| 206 | }}} |
| 207 | i. View the diagram by typing : |
| 208 | {{{ |
| 209 | eog myslice.png & |
| 210 | }}} |
| 211 | Your slice will look something like the one below (see [attachment:myslice.png]). The overall configuration should be the same, with two end hosts, named hostA and hostB, and four routers (top, left, right, bottom) in a diamond configuration. The host names, interface names, and MAC addresses will be different, depending on the actual resources assigned to your slice. |