Re: [Testbed-admins] TMCC exited with status 256! *** WARNING: Could not get bossinfo from tmcc!

[Leigh Stoller <stoller@flux.utah.edu>]

> On FreeBSD, the control interface is bce1 and the experimental
> interfaces are em0-3.
>
> On Fedora we can only see two interfaces, eth0 and eth1. After
> manually running ifcfg-eth99, the control interface is resolved with
> an IP address on eth0.  Running eth99 on startup causes problems
> logging on as previously mentioned, and this might be a domain
> issue.

Hmm, good point. First off, I assume that you have only a single DHCP
server (boss) on the network, right.

Next, make sure that pc1.hwdown.emulab-ops.emulab.naresky resolves
on boss (ping it and see it resolves to an IP). If not, then run
named_setup on boss.

> There seems to be an inconsistency between FreeBSD and Fedora, as
> the control interface is bce1 on FreeBSD (making it the second
> interface) and is eth0 on Fedora (making it the first interface).

This is okay; we do not rely on the ordering the OS assigns.

> Fedora will boot as long at the eth99 script is not started on boot.
>
> FreeBSD and Fedora (after manually running eth99) will resolve an IP
> address for the control network with no troubles. FreeBSD can load the
> experimental interfaces, but Fedora is unable to see the experimental
> interfaces. Could this be a driver issue (or lack of a driver) for the
> experimental NICs in Fedora?

Almost certainly a driver issue ... you might need to add to that
modprobe line in ifcfg-eth99 and then recreate the image. I'll point
you to the wiki page that describes how to do that, if you have not
seen it already.

> can we setup the DHCP setting on the experimental PC's to use a
> different NIC for the DHCP?

Not sure what you mean here; you want only the control interface (the
thing wired to the control switch) to get a DHCP response.

Lbs