| 1 | == Pre-Purchase == |
| 2 | |
| 3 | Connection between OpenFlow switches should ideally appear like layer 1 connections to the experimenters. This can be accomplished in various ways including using dedicated fiber, existing pseudo-wire technologies, OF switches to pass traffic, or applying special configurations to traditional layer 2 VLANs such as disabling mac learning and STP. |
| 4 | |
| 5 | * Does your site require any additional hardware or support in preparing your network environment for hosting a GENI rack? |
| 6 | * Do you need an additional transceiver to connect the 10Gb uplink connection from the rack to your network? |
| 7 | |
| 8 | |
| 9 | == Post-Purchase == |
| 10 | |
| 11 | **Important: If the following information is not or cannot be provided prior to the rack being sent to your site, you will receive the hardware with only a bare OS installed on all servers and the switch un-configured. In order to have your rack delivered as a ready to be deployed product, you MUST provide the following: |
| 12 | |
| 13 | |
| 14 | === OS Installation === |
| 15 | |
| 16 | ==== Hostname ==== |
| 17 | |
| 18 | * What is a unique name for your location? (Example: USC-Spartburg; USC-Columbia)[[BR]] |
| 19 | * How do we check conflicts?[[BR]] |
| 20 | * Use this information to generate a unique identifier for GENI.[[BR]] |
| 21 | * Ie: <company>-<location>-<function>-<number> |
| 22 | * Clemson-main-ctrl-1, Clemson-main-comp-1,etc |
| 23 | * Generated by integrator based on customer. Information given to customer after they purchase the unit.[[BR]] |
| 24 | * Tracked by integrator so if 2nd order is placed we know which number to start off on.[[BR]] |
| 25 | |
| 26 | DNS server |
| 27 | |
| 28 | === GRAM software === |
| 29 | |
| 30 | Range and subnet of public IP addresses for virtual machines: |
| 31 | * Define a range of contiguous IP addresses to be assigned to the Virtual Machines. |
| 32 | * Start_ip to end_ip must be a contiguous block of ip addresses not in use. There must be at least one, e.g.. 130.127.39.130 - 130.127.39.131. |
| 33 | |
| 34 | VLAN information for external plane: |
| 35 | * Provide the external plane VLAN number for your site. |
| 36 | * Needed for switch configuration |
| 37 | |
| 38 | |
| 39 | External network configuration on control nodes and compute nodes[[BR]] |
| 40 | |
| 41 | Assign the following for the control node attached to the system. (DHCP is not recommended as a change in IP address can disrupt the software utilized by GENI)[[BR]] |
| 42 | * Static IP address: |
| 43 | * Subnet: |
| 44 | * Gateway: |
| 45 | * DNS Server: |
| 46 | |
| 47 | Will the following ports be allowed through your campus/network firewall, to the entire rack subnet: |
| 48 | * 22 - ssh |
| 49 | * 25 - smtp (outbound connections only, from control node) |
| 50 | * 80 - http (must also allow outbound connections from control node) |
| 51 | * 443 - https (must also allow outbound connections from control node) |
| 52 | * 843 - Flash Policy Server |
| 53 | * 5001 - GRAM |
| 54 | * 5002 - GRAM |
| 55 | * 30000-65535 - Ports used by software. |
| 56 | * GRE - Not a port, but an IP protocol, required for constructing tunnels between racks. |
| 57 | * ICMP - ping |
| 58 | |
| 59 | |
| 60 | === iDRAC network configuration Static IP address === |
| 61 | * Subnet |
| 62 | * Gateway |
| 63 | |
| 64 | |
| 65 | === Force10 switch network configuration === |
| 66 | Assign the following: |
| 67 | * Static IP address |
| 68 | * Subnet |
| 69 | * Gateway |
| 70 | |
| 71 | === PT7048 switch network configuration === |
| 72 | Assign the following: |
| 73 | * Static IP address |
| 74 | * Subnet |
| 75 | * Gateway |