0002404: duplicate ip address on bonded interface restart

Notes
(0006817) lacika (reporter) 2008-02-05 14:32	I have got the same problem on Sun Fire X4200, but the bonding working fine. #uname -a Linux lolka.answare.hu 2.6.18-53.1.6.el5 0000001 SMP Wed Jan 23 11:28:47 EST 2008 x86_64 x86_64 x86_64 GNU/Linux [root@lolka ~]# lspci 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 13) 00:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) 00:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 13) 00:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) 00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) 00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) 00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) 01:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) 01:02.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) 01:02.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet Controller (Copper) (rev 03) 02:03.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064 PCI-X Fusion-MPT SAS (rev 02) 03:00.0 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:00.1 USB Controller: Advanced Micro Devices [AMD] AMD-8111 USB (rev 0b) 03:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) 04:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 13) 04:01.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01) 04:02.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 13) 04:02.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X IOAPIC (rev 01)

(0006881) Azrael (reporter) 2008-02-13 13:22	Maybe not related, but I thought it might be worth a mention... I experienced a similar issue on an HP BL460C blade server running CentOS 5.1 x86_64 with the Xen hypervisor. When the machine first booted, the network connection appears to be brought up (Starting interface bond0: [ OK ]), but no communication to or from the system seems possible. I tried disabling iptables, but this didn't seem to have any affect either. However, if I issued a "service network restart" to the machine, network communication became possible. After a bit of thought, I wondered if Xen itself might be causing the issue - I remembered seeing messages relating to peth0 in the log files. I then forced the network device used for the network-bridge script definition in /etc/xen/xend-config.sxp: (network-script 'network-bridge netdev=bond0') This seems to have fixed the issue!

Issue History
Date Modified	Username	Field	Change
2007-10-23 16:56	abhatnagar	New Issue
2007-10-23 16:56	abhatnagar	Status	new => assigned
2007-10-23 16:56	abhatnagar	Assigned To	=> kbsingh@karan.org
2008-02-05 14:32	lacika	Note Added: 0006817
2008-02-13 13:22	Azrael	Note Added: 0006881

Relationships