Ubuntu a bonding - Mode 4, 802.3ad - nefunguje jak by mel?
Pokousim se prinutit Ubuntu server 16.04 LTS k bondingu dvou sitovek jako 802.3ad, a tak neak se uplne nedari. Mate nekdo s timto osobni zkusenost?
Interfaces mam takhle:
bond-slaves eth1, eth2
bond-mode 4
bond-miimon 100
bond-lacp-rate 1
plus standardni nezbytnosti, sam bond a sitovky jsou "up" a nejak to bezi:
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
802.3ad info
LACP rate: fast
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 9c:69:b4:61:ae:ae
Active Aggregator Info:
Aggregator ID: 2
Number of ports: 2
Actor Key: 13
Partner Key: 20030
Partner Mac Address: 60:9c:9f:22:a3:00
Slave Interface: eth1
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 9c:69:b4:61:ae:ae
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 9c:69:b4:61:ae:ae
port key: 13
port priority: 255
port number: 1
port state: 63
details partner lacp pdu:
system priority: 1
system mac address: 60:9c:9f:22:a3:00
oper key: 20030
port priority: 1
port number: 15
port state: 61
Slave Interface: eth2
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 9c:69:b4:61:ae:af
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 9c:69:b4:61:ae:ae
port key: 13
port priority: 255
port number: 2
port state: 63
details partner lacp pdu:
system priority: 1
system mac address: 60:9c:9f:22:a3:00
oper key: 20030
port priority: 1
port number: 16
port state: 61
- jenze odchozi provoz se nedeli na oba slaves, ale tece vse jednim. Jen prichozi traffic se dle vseho deli na eth1 a eth2.
Napada nekoho, co delam spatne?