software.html 4.54 KB
Newer Older
1 2
<html>
<head>
3 4
	<title>Emulab.Net - Software Overview</title>
	<link rel='stylesheet' href='tbstyle-plain.css' type='text/css'>
5 6 7 8 9 10 11 12 13 14
</head>
<body>

<center>
<h1>
    Software Overview
</h1>
</center>

<ul>
Mike Hibler's avatar
Mike Hibler committed
15
<li><b>boss.emulab.net</b>: Master node, database, web server, name server, trusted disk-image server
16
    <p>
Mike Hibler's avatar
Mike Hibler committed
17 18 19 20 21 22 23 24 25 26 27 28 29 30
    Also known as <b>www.emulab.net</b>.
    Runs FreeBSD 4.3-RELEASE.  This is the master machine for the testbed
    software.  Runs all the critical software components and thus is not
    directly accessible by testbed users.  Moderates (via the database)
    access to node power cycling and disk-image loading as well as providing
    DNS and web services.

<p>
<li><b>users.emulab.net</b>: Control node, NFS server, test node serial line server and console access point
    <p>
    Also known as <b>ops.emulab.net</b>.
    Runs FreeBSD 4.3-RELEASE.  This is the main server machine for users
    of the testbed and is where home directories and all project files
    live. While most of the testbed configuration process is done via
31
    the Web interface, a few things must be done while logged into
Mike Hibler's avatar
Mike Hibler committed
32
    users.emulab.net.  These testbed specific commands and programs are
33 34 35 36
    contained in <code>/usr/testbed/bin</code>. Your skeleton login
    files will already have this directory in your path.
    
    <p>
Mike Hibler's avatar
Mike Hibler committed
37 38 39 40 41 42 43 44 45 46 47
    This is also our "serial-line console" server.  Experimenters can access
    the console of any testbed node (using <code>tip</code>) from here.
    Console output of all nodes is also logged here.

<p>
<li><b>tipserv1.emulab.net</b>: additional test node serial line server
    <p>
    Runs FreeBSD 4.3-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.
48 49

<p>
Mike Hibler's avatar
Mike Hibler committed
50
<li><b>pc[1-40].emulab.net</b>: <a href="hardware.html#tbpc600">pc600</a> testbed PC nodes
51
    <p>
Mike Hibler's avatar
Mike Hibler committed
52 53
    The testbed nodes can dual boot FreeBSD 4.3 and RedHat Linux 7.1.
    You may also boot your own OSKit kernels on them. Alternatively, you
54 55 56 57
    can run whatever OS you like by loading your own OS image onto the
    the 4th DOS slice using the Testbed configuration software.

    <p>
58
    Each node has 5 100/MBbps ethernet cards. The first four
59 60 61
    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
Mike Hibler's avatar
Mike Hibler committed
62 63 64
    for configuration and for login access from users.emulab.net.
    In FreeBSD this card is named <code>fxp4</code>,
    and in Linux and OSKit kernels it is <code>eth4</code>
65 66

    <p>
Mike Hibler's avatar
Mike Hibler committed
67
    All of these nodes have their COM1 serial interface (console
68
    port) connected to users.emulab.net. The port is configured to run
Mike Hibler's avatar
Mike Hibler committed
69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86
    at 115K baud, and are accessible from users.emulab.net via
    <code>tip</code> using the appropriate "pc" names; e.g., "pc6."

<p>
<li><b>pc[41-168].emulab.net</b>: <a href="hardware.html#tbpc850">pc850</a> testbed PC nodes
    <p>
    Same as "pc600" nodes from a software perspective:
    dual booting FreeBSD 4.3 and RedHat Linux 7.1, or capable of running
    custom OSKit kernels.
    However, due to differences in the hardware configuration,
    the "control" interface is <code>fxp0</code> under FreeBSD,
    <code>eth2</code> under Linux, and <code>eth0</code> under OSKit kernels.

    <p>
    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.
87 88

<p>
Mike Hibler's avatar
Mike Hibler committed
89
<li><b>sh[1-20]-[1-8].emulab.net</b>: testbed <a href="hardware.html#tbshark">Shark</a> nodes
90
    <p>
Mike Hibler's avatar
Mike Hibler committed
91
    The Sharks run NetBSD by default, with the filesystems provided via
92 93
    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.
94 95 96 97 98 99 100 101 102 103 104 105 106

    <p>
    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.

    <p>
    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 tip command) using the appropriate
Leigh B. Stoller's avatar
Leigh B. Stoller committed
107
    "tbsh" shelf names; e.g., "sh16."
108 109

</ul>