CheckList

These are site requirements for setting up your InstaGeni rack. Before we can proceed, each of the items in this checklist needs to completed.

• Have you read through the rack deployment page: ____ (Y/y)
• Does the back of your rack look like this diagram? ____ (Y/y) If the answer is NO, then contact us immediately!

Pay special attention to slot U38; Make sure the line card is on the left side of U38.

• Physical location (address) of your rack (for latitude/longitude): ______________________________
• Domain for your rack: ________________________________

This should look something like instageni.foo.bar.edu.

• IP subnet (public,routable) and netmask for your rack: ________________________

This should be a static subnet and at least a /26 (64 hosts);

Emulab must serve as the DNS server and DHCP server for the subnet.

• Your uplink router does NOT route either the 192.168 or the 10. subnets on/off the rack subnet: _____ (Y/y)
• Your uplink switch has been configured to NOT pass DHCP packets through, and does NOT have proxy arp enabled: ____ (Y/y)
• IP for the default router on your rack subnet: __________________________
• IP for your DNS forwarder(s). There can be several of these of course: _______________________
• Delegation of the forward DNS zone has been done: ____ (Y/y)

Once you tell us the subnet and mask, we can assign  IPs to the nodes in the rack, in particular the name server. For example, on a /24 network the name server would be XXX.YYY.ZZZ.4, while on a /25 network it would XXX.YYY.ZZZ.4 or XXX.YYY.ZZZ.132 (if the subnet is the upper half).  On a /26 it would be one of XXX.YYY.ZZZ.4, XXX.YYY.ZZZ.68, XXX.YYY.ZZZ.132, or XXX.YYY.ZZZ.196 (depending on which quadrant of the subnet).

Your campus network people will need to place (something like) this in their zone file:

	ns.instageni        IN      A       XXX.YYY.ZZZ.4
	instageni           IN      NS      ns.instageni
	instageni           IN      NS      ns.emulab.net.

As you can see, Utah will serve as a backup name server for the rack.

• Your rack is outside your campus firewall: ___ (Y/N)

This is the simplest solution since a number of ports are required for the rack to operate properly. 

• If you answered No to the previous question, are the following ports are allowed through your campus/network firewall, to the entire rack subnet: ____ (Y/y)
  • 22         - ssh
  • 25         - smtp (outbound connections only, from boss/ops)
  • 80         - http (must also allow outbound connections from boss/ops)
  • 443       - https (must also allow outbound connections from boss/ops)
  • 12369   - InstaGeni XMLRPC
  • 17990   - iLo remote console
  • 17988   - iLo remote media
  • 30000+ - Ports used by software.
  • GRE       - Not a port, but an IP protocol, required for constructing tunnels between racks.
• Full name and phone number of the local administrator: name: ________________________, phone: _____________________
• Preferred login id (username) for the local administrator: _____________________

The local administrator will have accounts on the various infrastructure nodes (control,boss,ops).

• Email address for the local administrator: ____________________________
• Version 2 SSH public key for the local administrator. Please attach.

This should be a real person, not a pseudo user. An administrator account will be built on the control node, from which other admin accounts can be added. See the RackAdminAccounts page for more details on adding local admin accounts, and for instructions on how to get an admin account on the Emulab infrastructure nodes.

• Optional, but recommended, local email lists for Emulab's status and logging messages:

The local administrator starts out as the sole receiver of these email messages, but if you provide alternate addresses (say, exploders) we can send the email there instead. Just let us know. You really want separate lists (exploders), not a single list!

• External network information:

1. We need a pool of at least 20 VLANs to extend from the rack to AL2S on your primary layer2 network uplink. 
2. Specify the port that the VLANs will connect to on the dataplane switch. If you have the all-copper module, we suggest that you use port 24 for the upwire to the switch providing that vlan. If you use a different port, be sure to tell us!
3. Specify other ports used for any other layer2 dataplane network connections.   For each of these connections, specify the port, the network provider (e.g. metro, campus or regional provider name), VLAN numbers available to configure for GENI data plane use on that network, and the switch name and port number for the non-GENI rack VLAN endpoints. 

• One-word ID for where the machines are (e.g. GPOLab, Utah, etc.):__________________

For monitoring purposes (reporting to GMOC), we need a one-word ID. This should be unique among all InstaGENI sites, so something related to your organization or location is best.

• Canonical organization name, may contain spaces (e.g. University of Utah, BBN Technologies):_____________________