Error: failed to bring up eth1

1,051 views
Skip to first unread message

Pavitra Shetty

unread,
Jan 10, 2012, 3:15:50 AM1/10/12
to cof...@googlegroups.com
Hi,
we are installing UEC (ubuntu enterprise cloud) which requires 2 machines to be connected as below :
A cloud controller (one system) connected to public network through eth0.
A node controller (another system) connected to the cloud controller through its eth0 on cloud controller's eth1.

For this configuration we added foll lines to /etc/network/interfaces file on cloud controller :

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
address 192.168.20.1
netmask 255.255.255.0
network 192.168.20.0
broadcast 192.168.20.255

However, on restarting the network it shows the error-

SIOCSIFADDR: No such device
eth1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
eth1: ERROR while getting interface flags: No such device
eth1: ERROR while getting interface flags: No such device
Failed to bring up eth1.

It fails to connect on eth1. Please guide.
     
--
Have a nice day ahead,
Pavitra.

Sankarshan Mukhopadhyay

unread,
Jan 10, 2012, 3:24:01 AM1/10/12
to cof...@googlegroups.com
On Tue, Jan 10, 2012 at 1:45 PM, Pavitra Shetty
<pavitras...@gmail.com> wrote:

> SIOCSIFADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> SIOCSIFNETMASK: No such device
> SIOCSIFBRDADDR: No such device
> eth1: ERROR while getting interface flags: No such device
> eth1: ERROR while getting interface flags: No such device
> Failed to bring up eth1.

It might be an issue with the persistent files under
/etc/udev/rules.d/ On a side note, isn't NetworkManager supposed to
handle the IP and related assignments ?

--
sankarshan mukhopadhyay
<http://sankarshan.randomink.org/blog/>

Gaurav Jain

unread,
Jan 10, 2012, 3:25:21 AM1/10/12
to cof...@googlegroups.com
Just to make sure, you have two ethernet ports right? or one ethernet one wlan?

On Tue, Jan 10, 2012 at 1:45 PM, Pavitra Shetty <pavitras...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "CoFSUG" group.
To post to this group, send an email to cof...@googlegroups.com.
To unsubscribe from this group, send email to cofsug+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cofsug?hl=en-GB.

shravan aras

unread,
Jan 10, 2012, 3:42:30 AM1/10/12
to cof...@googlegroups.com
Could you please confirm that eth1 is indeed present with a ifconfig
-a | grep eth

Thank You,

--
Shravan Aras.
(http://www.kushraho.com)

Pavitra Shetty

unread,
Jan 10, 2012, 6:09:47 AM1/10/12
to cof...@googlegroups.com
@ Shravan: ifconfig -a gives only eth0.
@ Gaurav: we have one ethernet port.

shravan aras

unread,
Jan 10, 2012, 6:14:31 AM1/10/12
to cof...@googlegroups.com
Interpreting what you have quoted -

"A node controller (another system) connected to the cloud controller
through its eth0 on cloud controller's eth1"
you will need 2 lan / ethernet cards on your "cloud controller"
machine. Once you have installed the second Ethernet card you should
be able to see the eth1 interface.
There can be no interface without its respective hardware :)

On Tue, Jan 10, 2012 at 4:39 PM, Pavitra Shetty

Gaurav Jain

unread,
Jan 10, 2012, 6:44:08 AM1/10/12
to cof...@googlegroups.com
I second Shravan and/or what you can do is, use wlan0 (Wireless Card) in replacement to eth1 if you have that.

Cheers!

Pavitra Shetty

unread,
Jan 12, 2012, 3:59:32 AM1/12/12
to cof...@googlegroups.com
We got the solution. To establish the second interface, in the interfaces file,
instead of eth1 write eth0:1 This creates a new eth1 type interface and that we can configure in interfaces file as needed earlier.
Thanks.
Reply all
Reply to author
Forward
0 new messages