Also known as www.netbed.org. Runs FreeBSD. This is the master machine for the testbed software. Runs all the critical software components and thus is not directly accessible by testbed users. Mediates (via the database) access to node power cycling and disk-image loading as well as providing DNS and web services.
Also known as ops.emulab.net and fs.emulab.net.
Currently runs FreeBSD 4.5-RELEASE. This is the main server machine for users
of the testbed and is where shared home directories and all project files
live. While most of the testbed configuration process is done via
the Web interface, a few things must be done while logged into
users.emulab.net. These testbed specific commands and programs are
contained in /usr/testbed/bin. Your skeleton login
files already have this directory in your path.
This is also one of Emulab's "serial-line console" servers. Experimenters can access
the console of any testbed node (using the console program) from here.
Console output of all nodes is also logged here.
Runs FreeBSD 4.5-RELEASE. Provides physical serial line ports for additional testbed nodes. Not directly accessible by testbed users, hosted serial lines are accessed by users via a proxy agent on users.emulab.net.
The testbed nodes can dual boot FreeBSD 4.5 and RedHat Linux 7.1. You may also boot your own OSKit kernels on them. Alternatively, you can run whatever OS you like by loading your own OS image onto the the 4th DOS slice using the Testbed configuration software.
Each node has 5 100/MBbps ethernet cards. The first four
interfaces are connected to the "experimental network," and are
used to "wire up" your specific network topology. The last
interface is connected to the "control network," and is used
for configuration and for login access from users.emulab.net.
In FreeBSD this card is named fxp4,
and in Linux and OSKit kernels it is eth4
All of these nodes have their COM1 serial interface (console
port) connected to users.emulab.net. The port is configured to run
at 115K baud, and are accessible from users.emulab.net via
console using the appropriate "pc" names; e.g., "pc6."
Same as "pc600" nodes from a software perspective:
dual booting FreeBSD 4.5 and RedHat Linux 7.1, or capable of running
custom OSKit kernels.
However, due to differences in the hardware configuration,
the "control" interface is fxp0 under FreeBSD,
eth2 under Linux, and eth0 under OSKit kernels.
As these testbed nodes support true console redirection, BIOS interaction, as well as OS kernel interaction, is possible via the console serial lines. However, the BIOS is password-protected and only read-only access is allowed without the password.
The Sharks run NetBSD by default, with the filesystems provided via NFS. You may also boot your own OSKit kernels. At this time, no support is provided for running your own operating system on the Sharks.
Each Shark has a single 10Mbps ethernet which serves as both the control and experimental interface. This is done with IP "aliasing", and causes experimental traffic to be routed to the experimental network instead of the control network.
All nodes use the serial port as their console, but due to the
limited number of serial ports on the control node, only the last
Shark on each shelf is connected to the control node. These
designated Shark console lines are accessible from
users.emulab.net (via the console command) using the appropriate
"tbsh" shelf names; e.g., "sh16."