Commit 206f4158 authored by David Hancock's avatar David Hancock

Fix t10 tee invocation and update debug_approaches

Cloudlab experiment still doesn't work - traffic stops flowing as soon
as VIBRANT encryptors are installed.

The same experiment does work in mininet (as t09).

The debug_approaches file is tracking debugging efforts.  Latest
iteration includes next steps to take.  Recompiling bmv2 to
enable nano output is last because it takes so long and would require
new disk images.
parent a01a1967
......@@ -52,7 +52,7 @@ scp infr_manifest.sh $user@pc${nodes[0]}.emulab.net:~/
ttyecho -n $CONTROLLER sudo cp /users/$user/infr_manifest.sh /opt/hp4-ctrl/tests/t10/
ttyecho -n $CONTROLLER sudo ./tests/update_t10.sh
ttyecho -n $CONTROLLER sudo ./controller --debug | sudo tee -i controller.out
ttyecho -n $CONTROLLER "sudo ./controller --debug | sudo tee -i controller.out"
echo "Next: create/provision slice1 with lease to s1, s2, and s3, slice2 w/ lease to s1, s4, and s5"
$pause
......
Approaches to debugging VIBRANT-CloudLab:
Mininet experiment t09 works (except that xterms no longer automatically launch traffic generating scripts as before - fix is to edit run_t09.sh to send the commands via ttyecho as we do in run_t10_cl.sh).
Next steps:
- Check for assumptions in vib_client.
- Install vib_enc vdev as passthrough, still no traffic?
- Install vib_enc only at s1 and only do h2 -> h4 pings; run tcpdump on
the three interfaces of s1, and view pcap in wireshark to see whether
traffic is being forwarded.
- If yes, repeat for s0, and s2.
- Recompile bmv2 with debugging / nano output enabled. Check nano logs on h2 -> h4 single ping.
Checked each relevant file in tests/t10/. Did not find any errors.
Controller should be using correct json for each device - a d430 version for the d430,
a pc3000 version for the others.
Mininet experiment t09 works (haven't tested that xterms automatically generate traffic as before - implemented fix in run_t09.sh to send the commands via ttyecho as we do in run_t10_cl.sh).
Collect increasingly detailed symptoms until we spot the problem.
Current status: Packets flow until the encryptors are installed. There are no evident errors thrown by encryptor installation.
We have figured out how to use tee with python: python -u forces unbuffered output so that tee will show it on stdout while writing to a file at the same time. Let's run the experiment and see whether there are any errors during encryptor vdev installation.
We have figured out how to use tee with python: python -u forces unbuffered output so that tee will show it on stdout while writing to a file at the same time. Ran the experiment and did not detect any errors during encryptor vdev installation.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment