Opened 16 months ago
Last modified 3 months ago
#5586 new Defekt
"invalid new link" im Journal von gluster1
| Reported by: | Rüdiger Kupper | Owned by: | bau |
|---|---|---|---|
| Priority: | bald erledigen | Milestone: | Schuljahr 2024/25 |
| Component: | Hardware: Netzwerktechnik | Severity: | beeinträchtigt den Unterricht einiger Lehrer |
| Keywords: | Cc: |
Description
Auch nach eine Reboot stehen Meldungen dieser Art im Journal:
Jul 09 11:57:23 gluster1 kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond Jul 09 11:57:23 gluster1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f0): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f1): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f0): link status up, enabling it in 0 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f1): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f0): link status definitely up, 1000 Mbps full duplex Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f1): invalid new link 3 on slave Jul 09 11:57:23 gluster1 kernel: bond0: active interface up! Jul 09 11:57:23 gluster1 kernel: igb 0000:01:00.2 enp1s0f2: igb: enp1s0f2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f2): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f2): invalid new link 3 on slave Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f1): link status definitely up, 1000 Mbps full duplex Jul 09 11:57:23 gluster1 kernel: igb 0000:04:00.2 enp4s0f2: igb: enp4s0f2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp4s0f2): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp1s0f2): link status definitely up, 1000 Mbps full duplex Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp4s0f2): invalid new link 3 on slave Jul 09 11:57:23 gluster1 kernel: igb 0000:04:00.3 enp4s0f3: igb: enp4s0f3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp4s0f3): link status up, enabling it in 200 ms Jul 09 11:57:23 gluster1 kernel: bond0: (slave enp4s0f3): invalid new link 3 on slave
Change History (3)
comment:1 by , 16 months ago
comment:2 by , 16 months ago
den Status von bond0 erhält man mit
cat /proc/net/bonding/bond0
auf gluster1 ist das:
Ethernet Channel Bonding Driver: v6.1.0-35-amd64
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 200
Down Delay (ms): 200
Peer Notification Delay (ms): 0
802.3ad info
LACP active: on
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 00:1b:21:bb:ad:04
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 7
Actor Key: 9
Partner Key: 2
Partner Mac Address: 00:59:dc:29:80:00
Slave Interface: enp1s0f0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:bb:ad:04
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 1
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 527
port state: 61
Slave Interface: enp1s0f1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:bb:ad:05
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 2
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 526
port state: 61
Slave Interface: enp1s0f2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:bb:ad:06
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 3
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 515
port state: 61
Slave Interface: enp1s0f3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:bb:ad:07
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 4
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 514
port state: 61
Slave Interface: enp4s0f0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 3
Permanent HW addr: 00:1b:21:ca:ef:94
Slave queue ID: 0
Aggregator ID: 1
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: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 5
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 551
port state: 61
Slave Interface: enp4s0f1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:ca:ef:95
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 6
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 550
port state: 61
Slave Interface: enp4s0f2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:ca:ef:96
Slave queue ID: 0
Aggregator ID: 3
Actor Churn State: churned
Partner Churn State: churned
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 7
port state: 69
details partner lacp pdu:
system priority: 65535
system mac address: 00:00:00:00:00:00
oper key: 1
port priority: 255
port number: 1
port state: 1
Slave Interface: enp4s0f3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 1
Permanent HW addr: 00:1b:21:ca:ef:97
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:1b:21:bb:ad:04
port key: 9
port priority: 255
port number: 8
port state: 61
details partner lacp pdu:
system priority: 32768
system mac address: 00:59:dc:29:80:00
oper key: 2
port priority: 32768
port number: 538
port state: 61
comment:3 by , 3 months ago
Inzwischen haben doch alle gluster Glasfaser, oder?
Dann kann dieses Ticket geschlossen werden.
Note:
See TracTickets
for help on using tickets.
das steht auch immer auf dem ersten Screen - ist anscheinend aber unbedenklich.
ToDo: Alle Gluster-Server mit den 10GE-Glasfaserkarten ausstatten - bond0 ersetzen