... | ... | @@ -16,22 +16,26 @@ people at Utah. |
|
|
|
|
|
This software makes some assumptions about the environment in which it is run. Some of the most basic are listed below. We don't have the resources to adapt it to every possible environment. So, you will need to either work out a way to match the environment outlined below, or be willing to invest substantial work in adapting the software.
|
|
|
|
|
|
* Emulab assumes a minimum of two dedicated server machines, known hereafter as 'boss' and 'ops', for Emulab setup. We encourage use of the 'ops' server to host the Emulab shared filesystems, but we also (loosely) support the use of a separate, dedicated filesystem server, hereafter referred to as 'fs'. People have set up the Emulab servers as VMs under VMWare and as of the FreeBSD 10 based release, these servers can be instantiated as VMs under Xen as well.
|
|
|
* Emulab assumes a minimum of two dedicated server machines, known hereafter as 'boss' and 'ops', for Emulab setup. In the past we have supported use of a separate, dedicated filesystem server, 'fs', but we now encourage use of the 'ops' server to host the Emulab shared filesystems. People have set up the Emulab servers as VMs under VMWare and as of the FreeBSD 10 based release, these servers can be instantiated as VMs under Xen (4.9 or 4.11) as well.
|
|
|
|
|
|
* You will need at least two network interfaces on each experimental node: one for the control network and one for the experimental network. The experimental network needs to be one on which you can make VLANs with SNMP. Currently, Emulab supports:
|
|
|
|
|
|
* Cisco 6500/6500-E and 4000 series switches (though not all switches in these lines have been tested - the 6513, 6509, 6506, 4006, and 4506 are known to work, running either CatOS or IOS). Cisco 3750's probably work but have not been tested. The 2950, 2960 and 2980 switches are known to work, although they are limited to a small number (64) of VLANs. (In general, it's the supervisor module, rather than the chassis, that matters, and Emulab supports all supervisor modules for the 6500s that we know about.)
|
|
|
* Dell 'S' and 'Z' series switches running OS9 and OS10. We use these extensively, including S3048, S3148, S4048, S5248, Z9100, Z9264, and Z9500. We do not support the 'N' series switches.
|
|
|
|
|
|
* HP Procurve. The 5400zl line has seen heavy production use on two Emulab sites. Other models may be easy to support, but this has not been tested.
|
|
|
* Select Mellanox switches including MSN2400 switches running MLNX-OS.
|
|
|
|
|
|
* HP Comware switches including the Moonshot 45XGc switch cartridges and the HP 12900 series chassis switch.
|
|
|
|
|
|
* Dell Force10 switches, running either OS9 or OS10. We use Dell 'S' series switches extensively including the 3048, 4048, 5248, 9100, and 9500. We do not support the more basic 'N' series switches.
|
|
|
* HP Procurve. The 5400zl line has seen heavy production use on two Emulab sites. Other models may be easy to support, but this has not been tested.
|
|
|
|
|
|
* Some Mellanox switches.
|
|
|
* Cisco 6500/6500-E and 4000 series switches (though not all switches in these lines have been tested - the 6513, 6509, 6506, 4006, and 4506 are known to work, running either CatOS or IOS). Cisco 3750's probably work but have not been tested. The 2950, 2960 and 2980 switches are known to work, although they are limited to a small number (64) of VLANs. (In general, it's the supervisor module, rather than the chassis, that matters, and Emulab supports all supervisor modules for the 6500s that we know about.)
|
|
|
|
|
|
* Some Arista switches.
|
|
|
|
|
|
* Some Foundry switches.
|
|
|
|
|
|
* NETSCOUT nGenius 3900 series layer-1 switch.
|
|
|
|
|
|
* The control network must have full multicast support, including IGMP snooping. Nodes' control network interfaces must support PXE booting.
|
|
|
|
|
|
* We highly, highly recommend that boss, ops, fs, and all the nodes be in publicly-routed IP space. If this is not possible, then boss, ops, and fs should be given two interfaces: One in the nodes' control network, and one in public IP space. If you must use private IP space for the nodes' control network, we suggest using the 192.168/16 subnet, which leaves the larger 10/8 subnet available for the experimental network. The defs-example-privatecnet file shows an example configuration like this.
|
... | ... | |