Commit c5e1110c authored by Russ Fish's avatar Russ Fish

Add a faq about no Win2k support. Knit Windows XP in wherever FreeBSD and Linux are mentioned.

parent 903b890d
......@@ -18,8 +18,10 @@
<li> <a href="#Differences">Differences from FreeBSD and Linux in Emulab </a></li>
<ul>
<li> <a href="#Windows_Passwords"> Windows Passwords </a></li>
<li> <a href="#Experiment_setup"> Experiment setup for Windows nodes. </a></li>
<li> <a href="#Login_connections"> Login connections to Windows. </a></li>
<li> <a href="#Experiment_setup"> Experiment setup for Windows nodes </a></li>
<li> <a href="#Routing"> Routing </a></li>
<li> <a href="#Boots_twice"> Windows nodes boot twice </a></li>
<li> <a href="#Login_connections"> Login connections to Windows </a></li>
<li> <a href="#RDP_details"> RDP details </a></li>
</ul>
<li> <a href="#Cygwin"> Cygwin </a> </li>
......@@ -37,6 +39,7 @@
Microsoft <i>Windows XP</i> is now supported as one of the operating system
types for experiment nodes in Emulab, in addition to FreeBSD and Linux.
<a href="../faq.php3?#SWS-WIN2K">Windows 2000</a> is not supported. <p>
Before booting the node at swap-in time, Emulab loads a fresh image of Windows
XP onto the experiment nodes in parallel, using our Frisbee service. Emulab
......@@ -101,41 +104,66 @@ password, the account information including passwords will be updated at the
next Emulab watchdog daemon isalive interval. This should be in 3 to 6
minutes. <p>
<h4><a name="Experiment_setup"> </a> Experiment setup for Windows nodes. </h4>
<h4><a name="Experiment_setup"> </a> Experiment setup for Windows nodes </h4>
All you have to do is put a line specifying a WINXP OS image in your
experiment .ns file, like this: <br>
<pre> tb-set-node-os $node WINXP-02-16</pre>
<pre> tb-set-node-os $node WINXP-UPDATE</pre>
Currently available images are:
Currently available Windows XP images are:
<ul>
<li><b>WINXP-02-11</b> - Windows XP-SP1, pc600 and pc850, release
candidate.</li>
<li><b>WINXP-UPDATE</b> - Windows XP-SP2+, pc600 and pc850. This will be
updated periodically from Windows Update with critical and security fixes up
through the date we pull the image file. <p>
<li><b>WINXP-02-16</b> - Windows XP-SP2+, pc600 and pc850, release
candidate. This incorporates SP2, as well as all "critical" and "security"
updates as of the date of the image. </li>
The Windows Firewall is disabled by default (as it will inform you
repeatedly!) <p>
This image fixes the problem that was causing Windows experiments created
with Netbuild to fail. Netbuild creates all experiments with "Static"
routing enabled, and that form of route is now supported. <p>
There was also a problem with Windows not finding all the interfaces when it
booted. Hopefully that is fixed as well.
</li>
<li><b>WINXP-02-16</b> - Windows XP-SP2+, pc600 and pc850, first release.
This incorporates SP2, as well as all "critical" and "security" updates as
of the date of the image. <p>
If you use WINXP-02-16 and built your experiment .ns file with the
<i>NetBuild</i> GUI, be aware that it puts in a <code>rtproto Static</code>
statement, which you will need to modify to <code>rtproto Static-old</code>.
</li>
<li><b>WINXP-02-11</b> - Windows XP-SP1, pc600 and pc850, early release
candidate.
</li>
</ul>
<div style="margin-left: 40px;"> <b>NOTE:</b> Router nodes can not run Windows
at present. The only form of routing that is currently supported on Windows
is <b><code>rtproto Static-old</code></b>. <code>rtproto Manual</code> should
work too. Don't put any other <code>rtproto</code> statements in your .ns
file. <p>
<h4><a name="Routing"> </a> Routing </h4>
Router nodes can not run Windows, i.e. <b><code>rtproto Session</code></b> is
not supported.<p>
If you built your experiment .ns file with the <i>NetBuild</i> GUI, be aware
that it puts in a <code>rtproto Static</code> statement, which you will need
to modify to <code>rtproto Static-old</code>. <p>
<b><code>rtproto Static</code></b> is supported in WINXP-UPDATE, but not in
WINXP-02-16 or before. <p>
<b><code>rtproto Static-old</code></b> or <b><code>rtproto Manual</code></b>
will work in any image.<p>
There is more information on routing in the <a
href="http://www.emulab.net/tutorial/docwrapper.php3?docname=tutorial.html#Routing">
Routing Section of the Emulab Tutorial. </a><p> </div>
Routing Section of the Emulab Tutorial. </a><p>
<h4><a name="Boots_twice"> </a> Windows nodes boot twice </h4>
Notice that Windows reboots an extra time after first swap-in on a node, after
changing the node name, to set up the network stack properly. <p>
changing the node name, to set up the network stack properly.
Be patient, Windows doesn't boot fast. <p>
<div style="margin-left: 40px;"> <b>NOTE:</b> Sometimes we have seen Windows
XP fail to do the second reboot. We're working on it. If you try to login
......@@ -146,7 +174,7 @@ If you are able to log in but your remote home directory isn't mounted, you
have the additional option of executing this command on
the node itself: <pre> /sbin/reboot</pre> </div>
<h4><a name="Login_connections"> </a> Login connections to Windows. </h4>
<h4><a name="Login_connections"> </a> Login connections to Windows </h4>
You can manually start up SSH or RDP client programs to connect and log in to
nodes in your experiment, using your Windows password. <p>
......
......@@ -79,6 +79,7 @@
<ul>
<li> <a href="#SWS-1">What OS do the nodes run?</a>
<li> <a href="#SWS-2">How do I select which OS to run on each node?</a>
<li> <a href="#SWS-WIN2K">Is Windows 2000 supported as well as Windows XP?</a>
<li> <a href="#SWS-3">Can I load my own software (RPMs/Tarballs)
on my nodes?</a>
<li> <a href="#SWS-4">Can I schedule programs to run
......@@ -1077,12 +1078,27 @@
</p>
<p>
Please see the
<a href="tutorial/docwrapper.php3?docname=nscommands.html">Extensions</a>
<a href="tutorial/docwrapper.php3?docname=nscommands.html#OS">Extensions</a>
page for a summary of all Emulab NS extensions, and the
<a href = "tutorial/tutorial.php3">Emulab Tutorial</a> for an
<a href = "tutorial/tutorial.php3#OsChoices">Emulab Tutorial</a> for an
example.
</p>
<li><a NAME="SWS-WIN2K"></a>
<font size='+1'><b>Is Windows 2000 supported as well as Windows XP?</b></font>
<p>
We have no existing support for Win2k. Given our experience in bringing
Windows XP into the Emulab fold, it could easily be an enormous
undertaking to get Win2k going.
</p>
<p>
We suggest switching to XP if at all possible.
</p>
<p>
Please see the <a href="doc/docwrapper.php3?docname=windows.html">
Windows&nbsp;XP</a> page for more information.
</p>
<li><a NAME="SWS-3"></a>
<font size='+1'><b>Can I load my own software (RPMs/Tarballs) on
my nodes?</b></font>
......@@ -1475,11 +1491,11 @@
<code>tb-set-node-os</code>, then make sure you have specified
a valid image (e.g., did you spell the OS identifier correctly?)
Again, the log output should include an error if the OSID was
invalid. Try:
<pre>
os_load -l
</pre>
on users.emulab.net to get a list of OSIDs that you can use.
invalid.
<p>
Click <a href="https://www.emulab.net/showosid_list.php3">List ImageIDs and
OSIDs</a> in the Emulab web interface "Interaction" pane to see the
current list of Emulab-supplied OSs.
<p>
If the OSID is correct, but the log contains messages of the form:
<pre>
......
......@@ -57,9 +57,22 @@
<p>
<li><b>pc[1-40].emulab.net</b>: <a href="hardware.html#tbpc600">pc600</a> testbed PC nodes
<p>
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 testbed nodes can boot any operating system image that has been
captured into an Emulab imagezip file. FreeBSD,
RedHat Linux, and
<a href="doc/docwrapper.php3?docname=windows.html"> Windows&nbsp;XP</a>
are fully supported.
Click <a href="https://www.emulab.net/showosid_list.php3">List ImageIDs and
OSIDs</a> in the Emulab web interface "Interaction" pane to see the
current list of Emulab-supplied OSs,
and see the <a href="faq.php3#SWS-2">FAQ</a> and
<a href = "tutorial/tutorial.php3#OsChoices">Tutorial</a>
for more information.
<p>
You may also boot your own OSKit kernels on them. You
can run whatever OS you like by loading
<a href="tutorial/tutorial.php3#CustomOS">your own OS image</a> onto the
the 4th DOS slice using the Testbed configuration software.
<p>
......@@ -81,8 +94,9 @@
<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.5 and RedHat Linux 7.1, or capable of running
custom OSKit kernels.
booting FreeBSD, RedHat Linux,
<a href="doc/docwrapper.php3?docname=windows.html"> Windows&nbsp;XP</a>,
OSKit or custom 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.
......
......@@ -318,10 +318,18 @@ tb-set-node-os $node1 MY_OS
a custom OSID, created via the web interface.
<li>If no OS is specified for a node a default OS is chosen based on
the nodes type. This is currently RHL-STD for PCs.
<li>The currently available standard OS types are: FBSD-STD,
RHL-STD, NBSD14-STD (should not be used on PC nodes), and
<li>The currently available standard OS types are: FBSD-STD, RHL-STD,
<a href="../doc/docwrapper.php3?docname=windows.html">WINXP-UPDATE</a>,
NBSD14-STD (should not be used on PC nodes), and
NETBOOT-STD (oskit netboot kernel for loading other
operating systems over the network).
operating systems over the network). <p>
<a href="../faq.php3?#SWS-WIN2K">Windows 2000</a> is not supported. <p>
Click <a href="https://www.emulab.net/showosid_list.php3">List ImageIDs and
OSIDs</a> in the Emulab web interface "Interaction" pane to see the
current list of Emulab-supplied OSs.
</ul>
......
......@@ -34,8 +34,8 @@
How do I know when all my nodes are ready?</a>
<li> <a href="#Routing">
Setting up IP routing between nodes</a>
<li> <a href="../doc/docwrapper.php3?docname=windows_in_emulab_user.html">
Using Windows XP on test nodes</a>
<li> <a href="../doc/docwrapper.php3?docname=windows.html">
Using Windows XP on experiment nodes</a>
<img src="../new.gif" alt="&lt;NEW&gt;">
<li> <a href="docwrapper.php3?docname=nse.html">
Hybrid Experiments with Simulation and Emulation</a>
......@@ -186,17 +186,28 @@ node A to B.
In addition to the standard NS syntax above, a number of
<a href="docwrapper.php3?docname=nscommands.html">
extensions</a> have been added that allow you
to better control your experiment. For example, you may specify what
to better control your experiment. <p>
<a NAME="OsChoices"></a>
For example, you may specify what
Operating System is booted on your nodes. We currently support FreeBSD
4.10, Linux RedHat 9.0, and Windows&nbsp;XP. Fedora Core 2 (Linux 2.6)
4.10, Linux RedHat 9.0, and
<a href="../doc/docwrapper.php3?docname=windows.html"> Windows&nbsp;XP</a>.
<a href="../faq.php3?#SWS-WIN2K">Windows 2000</a> is not supported.
Fedora Core 2 (Linux 2.6)
is available but unsupported. We also support
<a href="http://www.cs.utah.edu/flux/oskit/">OSKit</a> kernels on the
Emulab PCs.
By default, our most recent Linux image is selected.
Emulab PCs. <p>
Click <a href="https://www.emulab.net/showosid_list.php3">List ImageIDs and
OSIDs</a> in the Emulab web interface "Interaction" pane to see the current
list of Emulab-supplied OS. By default, our most recent Linux image is
selected.<p>
<code><pre>
tb-set-node-os $nodeA FBSD-STD
tb-set-node-os $nodeC RHL-STD</code></pre>
tb-set-node-os $nodeC RHL-STD
tb-set-node-os $nodeC WINXP-UPDATE</code></pre>
<p>
In a topology like this, you will likely want to communicate between
......@@ -385,7 +396,8 @@ here</a>.)
By the time you receive the email message listing your nodes, the
Emulab configuration system will have ensured that your nodes are
fully configured and ready to use. If you have selected one of the
Emulab-supported operating system images (FreeBSD or Linux),
Emulab-supported operating system images (FreeBSD, Linux, or
<a href="../doc/docwrapper.php3?docname=windows.html">Windows&nbsp;XP</a>),
this configuration process includes:
<p>
......@@ -442,7 +454,10 @@ Testbed Ops</a> for help or more information.
<p>
If you need to customize the configuration, or perhaps reboot nodes,
you can use the "sudo" command, located in <code>/usr/local/bin</code>
on FreeBSD and Linux, and <code>/usr/pkg/bin</code> on NetBSD. Our
on FreeBSD and Linux, and <code>/usr/pkg/bin</code> on NetBSD.
All users are added to the Administrators group on
<a href="../doc/docwrapper.php3?docname=windows.html">Windows&nbsp;XP</a>
nodes. Our
policy is very liberal; you can customize the configuration in any way
you like, provided it does not violate Emulab's
<a href="../docwrapper.php3?docname=policies.html">
......@@ -580,9 +595,9 @@ Again, please feel free to contact us.
<li> <a href="#Startupcmd">Starting your application automatically</a>
<li> <a href="#SyncServer">How do I know when all my nodes are ready?</a>
<li> <a href="#Routing">Setting up IP routing between nodes</a>
<li> <a href="../doc/docwrapper.php3?docname=windows_in_emulab_user.html">
Using Windows XP on test nodes</a>
<img src="../new.gif" alt="&lt;NEW&gt;">
<li> <a href="../doc/docwrapper.php3?docname=windows.html">
Using Windows XP on test nodes</a>
<img src="../new.gif" alt="&lt;NEW&gt;">
<li> <a href="docwrapper.php3?docname=nse.html">Hybrid Experiments with Simulation and Emulation</a>
<li> <a href="docwrapper.php3?docname=vnodes.html">Multiplexed Virtual Nodes</a>
<li> <a href="docwrapper.php3?docname=ixp.html">Using IXP network processors</a>
......@@ -741,11 +756,13 @@ nodes when it boots:
<code><pre>
tb-set-node-rpms $nodeA /proj/myproj/rpms/silly-freebsd.rpm
tb-set-node-rpms $nodeB /proj/myproj/rpms/silly-linux.rpm </code></pre>
tb-set-node-rpms $nodeB /proj/myproj/rpms/silly-linux.rpm
tb-set-node-rpms $nodeC /proj/myproj/rpms/silly-windows.rpm </code></pre>
The above NS code says to install the <tt>silly-freebsd.rpm</tt> file
on <tt>nodeA</tt>, and the <tt>silly-linux.rpm</tt> on <tt>nodeB</tt>.
RPMs are installed as root, must reside in either the project's
on <tt>nodeA</tt>, the <tt>silly-linux.rpm</tt> on <tt>nodeB</tt>,
and the <tt>silly-windows.rpm</tt> on <tt>nodeC</tt>.
RPMs are installed as root, and must reside in either the project's
<tt>/proj</tt> directory, or if the experiment has been created in a
subgroup, in the <tt>/groups</tt> directory. You may not place your
rpms in your home directory.
......@@ -919,7 +936,8 @@ by default.
However, many users are more interested in end-to-end aspects and don't
want to be bothered with setting up routes. For those users we provide
an option to automatically set up routes on nodes which run one of our
provided FreeBSD or Linux disk images.
provided FreeBSD, Linux or <a href="../doc/docwrapper.php3?docname=windows.html">
Windows&nbsp;XP</a> disk images.
<p>
You can use the NS <tt>rtproto</tt> syntax in your NS file to enable
......@@ -933,7 +951,9 @@ or <code>Manual</code>. <p>
<code>Session</code> routing provides fully automated routing support,
and is implemented by enabling <code>gated</code> running the OSPF protocol
on all nodes in the experiment. <p>
on all nodes in the experiment. This is not supported on
<a href="../doc/docwrapper.php3?docname=windows.html#Routing">
Windows&nbsp;XP</a> nodes. <p>
<code>Static</code> routing also provides automatic routing support, but
rather than computing the routes dynamically, the routes are precomputed by a
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment