SUSECON
Results 1 to 5 of 5

Thread: Why could not use ifup bring up a device in bonding?

Threaded View

  1. #1
    Join Date
    Dec 2012
    Location
    Shanghai, China
    Posts
    8

    Question Why could not use ifup bring up a device in bonding?

    Hi,

    Please excuse me, this is my first thread here.

    Issue description: I setup a bond interface (bond0), which include two slave devices (eth0 and eth2). Then I executed command "ifdown" to bring down one of slave device, then I want to use "ifup" to bring up it again, it do not works.
    Then I tried to use "ifconfig <device> up", it works.

    System information:
    HTML Code:
    Linux linux-vm1 3.0.58-0.6.6-default #1 SMP Tue Feb 19 11:07:00 UTC 2013 (1576ecd) x86_64 x86_64 x86_64 GNU/Linux
    linux-vm1:~ # cat /etc/SuSE-release
    SUSE Linux Enterprise Server 11 (x86_64)
    VERSION = 11
    PATCHLEVEL = 2
    Commons record:
    HTML Code:
    linux-vm1:~ # ifstatus eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
        eth2      is up
    3: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
        link/ether 08:00:27:2e:54:9d brd ff:ff:ff:ff:ff:ff
    linux-vm1:~ # ifdown eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
    linux-vm1:~ # ifstatus eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
        eth2      is down
    linux-vm1:~ # ifup eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
    linux-vm1:~ # ifstatus eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
        eth2      is down
    linux-vm1:~ # ifconfig eth2 up
    linux-vm1:~ # ifstatus eth2
        eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
        eth2      is up
    3: eth2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bond0 state UP qlen 1000
        link/ether 08:00:27:2e:54:9d brd ff:ff:ff:ff:ff:ff
    Message log:
    HTML Code:
    Mar 15 16:08:48 linux-vm1 ifdown:     eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
    Mar 15 16:08:48 linux-vm1 kernel: [ 4025.861271] bonding: bond0: link status definitely down for interface eth2, disabling it
    Mar 15 16:08:48 linux-vm1 kernel: [ 4025.861299] bonding: bond0: making interface eth0 the new active one.
    Mar 15 16:09:31 linux-vm1 ifup:     eth2      device: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) (rev 02)
    Mar 15 16:10:24 linux-vm1 kernel: [ 4121.409163] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
    Mar 15 16:10:24 linux-vm1 kernel: [ 4121.476075] bonding: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex.
    So, my questions are :
    What is difference between "ifup <device>" and "ifconfig <device> up"?

    Why do not work with "ifup" when the device is a bonding slave?

    Thanks!

    ================================================== ============================
    Best Regards!

    Mengz You
    Last edited by mzyou; 15-Mar-2013 at 09:57. Reason: Format

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •