Internet2: E2Epi | BWCTL AES Request

[an error occurred while processing this directive]

Using BWCTL to Test Into the Middle

One of the driving reasons to implement BWCTL was to allow the Abilene regularly-scheduled bandwidth test systems to be used by end-users, as well. This enables end users to do path decomposition to help isolate problem portions of the path.

We are now ready to start allowing users to do tests into the middle. That said, our policies are still in a state of flux. It is still unclear to us how popular this service will be, so we have not determined exactly how to set the priorities. We are attempting to be as "liberal" as we can for now, but we may need to become more strict over time.

If you are interested in doing tests into the middle (i.e. tests from your institution to abilene routers) these are the basic steps:

Locally install and test bwctl.

Determine local policy issues (who are you willing to test with, and how many resources are you willing to allow them to use.
If possible, install on two local hosts and run tests between them to trouble-shoot problems locally before dealing with tests across multiple network domains. (Keep this part simple - don't use AES keys yet...)
Add AES authentication to the local tests and make sure you can get that to work locally. Instructions on creating a key can be found at http://e2epi.internet2.edu/bwctl/aespasswd.man.html. Instructions on getting bwctld to use that key can be found at http://e2epi.internet2.edu/bwctl/bwctld.limits.man.html

Register your key with Abilene to enable testing between Abilene hosts and your hosts by filling in the following form and submitting it.

Obtaining an AES Key


The E2E piPEs team invites you to try out the system; to do this you will need an AES key. To register a key to do testing to Abilene measurement hosts fill in the form below. You will create your own key by using aespasswd and pasting it and the keyid name into the form. You may be contacted to verify your registration before the key is made active on Abilene. The key may be used by multiple measurement hosts and multiple people within an organization, but please do not share the key with people outside of your working relationship (remember you will be the responsible party for any tests using this key). Use the key in the config files of the test programs. The key will only enable you to do testing to Abilene measurement hosts. If you want to testing to other measurement hosts you must do a key exchange with the operators of those hosts. Responsible Party: Email: Phone: Locations of Measurement Hosts — Institution: Domain Name: Who will have access to use your measurement host(s) and how do you control access? Your Key: Your KeyID Name:

Run your tests. The current measurement points within Abilene are:

Los Angeles	nms1-losa.abilene.ucaid.edu
Sunnyvale	nms1-snva.abilene.ucaid.edu
Seattle	nms1-sttl.abilene.ucaid.edu
Denver	nms1-dnvr.abilene.ucaid.edu
Kansas City	nms1-kscy.abilene.ucaid.edu
Houston	nms1-hstn.abilene.ucaid.edu
Indianapolis	nms1-ipls.abilene.ucaid.edu
Chicago	nms1-chin.abilene.ucaid.edu
Atlanta	nms1-atla.abilene.ucaid.edu
Washington	nms1-wash.abilene.ucaid.edu
New York	nms1-nycm.abilene.ucaid.edu