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

[Ben Burnett <bburnett@atcorp.com>]

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.

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

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?

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


Ben Burnett
  R&D Software Engineer: wired, wireless, ad hoc, mesh networking,
    network monitoring and data visualization
  ATC (Architecture Technology Corporation)   http://www.atcorp.com/
  bburnett@atcorp.com                         (952) 829-5864 x167
  --------Views expressed are mine and not those of ATC--------
  Personal:
    ben@burnett.ws                            http://www.burnett.ws/
http://ben.burnett.ws/
http://www.linkedin.com/in/benburnett



On Wed, Jul 15, 2009 at 10:16 AM, Leigh Stoller<stoller@flux.utah.edu> wrote:
>> in both Linux and FreeBSD we are getting problems with the node
>> and/or image finding boss.  The nodes look for boss on eth99 and
>> since we don't have an eth99 this obviously fails.
>
> Hi Ben. Is the problem intermittent, or does it always fail on
> both Linux and FreeBSD?
>
>> 2. Nodes can't find boss on bootup (the boot up sequence looks for
>> boss on eth99) how/where do we configure this?  is this supposed to
>> come over pxe?  is this a custom configuration step that we missed, or
>> was it left out of the docs?
>
> Lets concentrate on this one, since I think (hope) this is the basis
> of your problems. eth99 is a pseudo device we use to deal with dhcp
> issues on linux. Look at /etc/sysconfig/network-scripts/ifcfg-eth99,
> at the modprobe line. Are the proper network drivers getting loaded
> for your hardware?
>
> If so, which interface is your control network interface, and is it
> active after you log in on the console.
>
> Lbs
>
>
>