Today we were alerted by CheckMK about some port errors on one of our 18.5 MR3 HA Clusters.
The issue happened on the dedicated HA Port Port10 on which both machines are connected with 1m CAT6 cable.
Of course, we could change the cable.
But I'd like to know if there is something special to check elsewere, not just the port statistics.
This special cluster is causing some kind of issues from the beginning on. It did not survive the Update 18.5 MR2 to MR3 and the HA Link was broken at that time, like it never existed.
PRI NODE:
XGS136_XN01_SFOS 18.5.3 MR-3-Build408# ifconfig Port10
Port10 Link encap:Ethernet HWaddr 7C:5A:1C:B1:9D:19
inet addr:10.1.178.5 Bcast:10.1.178.7 Mask:255.255.255.252
inet6 addr: fe80::7e5a:1cff:feb1:9d19/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11213596 errors:3 dropped:15 overruns:0 frame:0
TX packets:12169366 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4360491474 (4.0 GiB) TX bytes:5172758242 (4.8 GiB)
AUX NODE:
XGS136_XN01_SFOS 18.5.3 MR-3-Build408# ssh -F /static/ha/hauser.conf hauser@10.1.178.6
Jun 10 13:30:12 Warning: Permanently added '10.1.178.6' (ED25519) to the list of known hosts.
XGS136_XN01_SFOS 18.5.3 MR-3-Build408# ifconfig Port10
Port10 Link encap:Ethernet HWaddr 7C:5A:1C:B1:B1:59
inet addr:10.1.178.6 Bcast:10.1.178.7 Mask:255.255.255.252
inet6 addr: fe80::7e5a:1cff:feb1:b159/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12168635 errors:0 dropped:52 overruns:0 frame:0
TX packets:11212931 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5172503717 (4.8 GiB) TX bytes:4360261073 (4.0 GiB)
This thread was automatically locked due to age.