The network admin has told me that the Juniper layer 2 switches (into which the server is plugged) need each of the bonded NICs to have their own unique MAC address, in order to prevent problems with multicast. TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:379085548 (379.0 MB) TX bytes:263658502 (263.6 MB)Įth1 Link encap:Ethernet HWaddr d4:ae:52:ce:32:4e 1 Answer Sorted by: 6 In mode 5, or balance-tlb mode, outgoing traffic uses the MAC address of the slave interface that it's leaving, instead of using the address of the bond interface. TX packets:1991772 errors:0 dropped:0 overruns:0 carrier:0 RX packets:2880650 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 TX packets:1991774 errors:0 dropped:0 overruns:0 carrier:0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 In this way, we increase redundancy or throughput. An available way is to bind together existing connections, so the system recognizes them as one. However, we need appropriate means to use them effectively. Inet6 addr: fe80::d6ae:52ff:fece:324e/64 Scope:Link Overview Modern hardware offers multiple network interfaces. Inet addr:172.26.1.210 Bcast:172.26.1.255 Mask:255.255.255.0 Mode 2 (balance-xor): The source MAC address uses exclusive or (XOR) logic with the destination MAC address. I have a bonded interface: bond0 Link encap:Ethernet HWaddr d4:ae:52:ce:32:4e
0 kommentar(er)
