... | @@ -16,7 +16,7 @@ people at Utah. |
... | @@ -16,7 +16,7 @@ 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.
|
|
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. While the 'ops' server normally hosts the Emulab shared filesystems, we also 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.0 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. 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.
|
|
|
|
|
|
* 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:
|
|
* 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:
|
|
|
|
|
... | @@ -24,14 +24,14 @@ This software makes some assumptions about the environment in which it is run. S |
... | @@ -24,14 +24,14 @@ This software makes some assumptions about the environment in which it is run. S |
|
|
|
|
|
* 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.
|
|
* 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 Foundry switches.
|
|
* 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.
|
|
|
|
|
|
* Some Force10 (Dell) switches.
|
|
|
|
|
|
|
|
* Some Mellanox switches.
|
|
* Some Mellanox switches.
|
|
|
|
|
|
* Some Arista switches.
|
|
* Some Arista switches.
|
|
|
|
|
|
|
|
* Some Foundry switches.
|
|
|
|
|
|
* The control network must have full multicast support, including IGMP snooping. Nodes' control network interfaces must support PXE booting.
|
|
* 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.
|
|
* 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.
|
... | | ... | |