I thought I would add this tidbit:
/etc/init.d/network stop and then /etc/init.d/network start brings the bond0 interface down and up as expected. Could there be an issue with when the aliases are available from /etc/modprobe.conf? There is nothing in dmesg or /var/log/messages that show the system even trying to start this interface on boot. However, when done manually:
Ethernet Channel Bonding Driver: v3.5.0 (November 4, 2008)
bonding: MII link monitoring set to 100 ms
bonding: bond0: Setting MII monitoring interval to 100.
bonding: bond0: setting mode to 802.3ad (4).
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0: Adding slave eth0.
e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
bonding: bond0: enslaving eth0 as a backup interface with an up link.
bonding: bond0: Adding slave eth1.
e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
bonding: bond0: enslaving eth1 as a backup interface with an up link.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
bond0: no IPv6 routers present
As always, any help would be appreciated.
---
Will Y.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
