| | 1 | * This page provides general guidance to the networking team at any future GENI event venue for GENI network requirements |
| | 2 | |
| | 3 | = Network requirements = |
| | 4 | |
| | 5 | GPO event coordinator will provide the total number of attendees for the event. The event could be |
| | 6 | |
| | 7 | * a tutorial at a conference |
| | 8 | * a workshop |
| | 9 | * GENI summer camp |
| | 10 | * GENI engineering conference. |
| | 11 | |
| | 12 | == How will attendees connect to your network == |
| | 13 | |
| | 14 | * Wired or wireless |
| | 15 | * Think about the number of wireless AP's in the location of the event. |
| | 16 | * Rule of thumb is 2-3 AP's per 50 attendees |
| | 17 | * DHCP ; ideally provide sufficient subnet and lease times based on attendees. ( For GENI conferences, we require a /24 network ) |
| | 18 | * Some locations prefer to handout static addresses. Please plan in advance how to distribute these temp accounts. |
| | 19 | * Please specify requirement of any Captive portal login or rebooting an attendees machine to log onto the network |
| | 20 | |
| | 21 | == How is your campus network setup == |
| | 22 | |
| | 23 | * What is the total capacity of the network |
| | 24 | * Since most of the tutorials offered at GENI events are focused on new networking paradigms,traffic patterns from our locations might look suspicious to your network monitoring tools. |
| | 25 | * Please ,if possible, disable traffic shaping algorithms running on the network. |
| | 26 | * One of the tools used has all attendees reach out using the same IP address to a remote host and your network monitoring tools might want to drop these packets. |
| | 27 | * Please think about how you can help avoid these false positives. |
| | 28 | * Please also provide a hands on person/hotline/email for the day of the event for any last minute emergencies |
| | 29 | |
| | 30 | == How to check if the required GENI ports are open on your network == |
| | 31 | |
| | 32 | GENI tutorials use non-standard ports in addition to standard TCP,UDP ports. Most of these ports are usually blocked by universities. |
| | 33 | To test your network, there is a very nice tool developed by the folks at iMinds in Belgium. The tool is a Java applet and is available at |
| | 34 | [http://jfed.iminds.be]. |
| | 35 | |
| | 36 | Test from a laptop that is: |
| | 37 | * Connected only to the wireless network that will be used by the attendees i.e. it should not be connected to any other network |
| | 38 | * Is a laptop that has not previously been registered on the campus wireless network i.e. test as if it is somebody connecting to the network for the 1st time. |
| | 39 | * If providing credentials (guest/temporary) to attendees, please use those credentials to test. |
| | 40 | |
| | 41 | To test: |
| | 42 | * Point browser to http://jfed.iminds.be |
| | 43 | * On that page, click on "Quickstart jFed Experimenter Tool". A window that looks like this will pop up: |
| | 44 | |
| | 45 | [[Image(login.jpg, 30%)]] |
| | 46 | * At the bottom left, of that window, click on the "Connectivity Tester" button. |
| | 47 | * A new window will pop up: |
| | 48 | |
| | 49 | [[Image(TestResults.jpg, 30%)]] |
| | 50 | * Tests that succeed will get green check boxes and those that fail get red 'x's. You can click on a test result to get details. |
| | 51 | * To save test results to a text file, click on the "Save test results" button at the top of the window. |
