"
These are physical boxes, Supermicro 1 HU servers.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
23.1 Legacy Series / Re: Problems with CARP - bug?
February 15, 2023, 01:09:09 PM
That behaviour went on until 12:58:59.
Just counted the multicast messages within 12:58:53: 978 messages sent.
12:58:53.714240 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714250 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714259 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714267 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:59.738948 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:01.743682 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:03.761903 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:05.772651 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
Just counted the multicast messages within 12:58:53: 978 messages sent.
12:58:53.714240 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714250 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714259 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.714267 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:59.738948 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:01.743682 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:03.761903 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:59:05.772651 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
#3
23.1 Legacy Series / Re: Problems with CARP - bug?
February 15, 2023, 01:05:10 PM
Hi mimugmail,
I started a tcpdump at the first box.
I changed the advbase to 2 seconds.
Just spotted now that at 12:58:53 something happened. Instead of the 2-second-interval, the multicast messages are send in about 10 nanosecond intervals.
12:58:31.545214 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:33.554059 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:35.575059 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:37.593496 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:39.601832 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:41.611017 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:43.620565 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:45.664436 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:47.675805 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:49.681860 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:51.692869 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.697689 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.697807 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704257 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704272 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704282 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704294 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704306 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704317 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704329 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704343 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704357 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704374 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704384 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704399 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
I started a tcpdump at the first box.
I changed the advbase to 2 seconds.
Just spotted now that at 12:58:53 something happened. Instead of the 2-second-interval, the multicast messages are send in about 10 nanosecond intervals.
12:58:31.545214 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:33.554059 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:35.575059 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:37.593496 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:39.601832 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:41.611017 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:43.620565 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:45.664436 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:47.675805 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:49.681860 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:51.692869 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.697689 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.697807 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704257 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704272 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704282 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704294 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704306 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704317 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704329 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704343 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704357 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704374 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704384 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
12:58:53.704399 IP 172.16.13.253 > 224.0.0.18: VRRPv2, Advertisement, vrid 12, prio 1, authtype none, intvl 2s, length 36
#4
23.1 Legacy Series / Re: Problems with CARP - bug?
February 15, 2023, 09:31:46 AM
Hi bubbagump,
in my case all four VIP's have a different VHID, they match on both boxes.
At the first box I have an advbase of 1 and an advskew of 1 for all VIP's.
At the second box I have an advbase of 1 and an advskew of 101 for all VIP's.
These four VLAN's are on a trunk interface at the OPNsense.
These trunk interfaces from both boxes go to a switch where also trunks are defined with all four VLAN's enabled as tagged.
The communication via the switch is working well.
I also tried a different switch from another vendor. Also there the communication works, but also the same CARP issues.
in my case all four VIP's have a different VHID, they match on both boxes.
At the first box I have an advbase of 1 and an advskew of 1 for all VIP's.
At the second box I have an advbase of 1 and an advskew of 101 for all VIP's.
These four VLAN's are on a trunk interface at the OPNsense.
These trunk interfaces from both boxes go to a switch where also trunks are defined with all four VLAN's enabled as tagged.
The communication via the switch is working well.
I also tried a different switch from another vendor. Also there the communication works, but also the same CARP issues.
#5
23.1 Legacy Series / Re: Problems with CARP - bug?
February 13, 2023, 10:56:02 AM
Hi Perun,
do you see any ARP issues in your OPNsense terminal ?
I have seen a lot them, looks like no ARP resolution can be performed for some minutes, then it is settling down again to normal.
do you see any ARP issues in your OPNsense terminal ?
I have seen a lot them, looks like no ARP resolution can be performed for some minutes, then it is settling down again to normal.
#6
23.1 Legacy Series / Re: DEC2750 won't update OPNsense
February 07, 2023, 03:41:24 PM
Hello REH,
maybe you had a business license for OPNsense according to the log (.../FILL-IN-YOUR-LICENSE-HERE/...).
Look into System -> Firmware -> Settings -> Type.
When you have the selection "Business", try to change that to "Community".
Then press "Save" and try to update.
Regards
Thomas
maybe you had a business license for OPNsense according to the log (.../FILL-IN-YOUR-LICENSE-HERE/...).
Look into System -> Firmware -> Settings -> Type.
When you have the selection "Business", try to change that to "Community".
Then press "Save" and try to update.
Regards
Thomas
#7
23.1 Legacy Series / Re: Problems with CARP - bug?
February 06, 2023, 03:58:02 PM
In my case the two OPNsense boxes were running for more than one year now, connected to the same switch. No issue at all.
Only after the update to 22.7.11 I'm facing the problem. Nothing changed at the switch.
Only after the update to 22.7.11 I'm facing the problem. Nothing changed at the switch.
#8
23.1 Legacy Series / Re: Problems with CARP - bug?
February 06, 2023, 02:19:44 PM
I have the same issue, came with update to 22.7.11.
I have a lagg0 with four interfaces on it. Three VIP's seem to be OK, one is making problems.
Updated to 23.1_6.
The VIP's are swapping frequently. The lagg0_vlan80 is having problems.
But also all other VIP's are effected, no traffic possible for about 10 minutes.
2023-02-06T14:06:43 Notice configd.py [fa17137f-adfd-4cd1-9cec-d6f691056785] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T14:06:39 Notice configd.py [0f4181cb-d43d-4e8c-b076-d2cfac7f3ec7] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T14:06:38 Notice configd.py [6c0cda9a-238e-426f-8e04-3c29aa86719d] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T14:05:38 Notice configd.py [b287b466-1a9b-42e4-bc23-6c04bcd75188] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:45:23 Notice configd.py [c4eb3166-afec-4386-b8d7-0f129641af6f] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:45:20 Notice configd.py [f9a85c84-eb9a-4a63-9ef2-5e1df97e0327] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:39:53 Notice configd.py [bc11800c-46f6-49b7-82cc-c846a5a5d695] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:39:50 Notice configd.py [1385fd0c-9709-4de2-bce9-31c80f2a1816] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:25:40 Notice configd.py [d050812f-a205-40ae-9f66-2c681383f95d] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:25:36 Notice configd.py [9eca6fd6-8085-49ad-827b-c1c8c3544068] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:18:17 Notice configd.py [bf29afba-6f22-49ef-a55b-823473621420] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:18:14 Notice configd.py [68780d24-4c6f-44e7-8a01-c572ec49bd22] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:18:13 Notice configd.py [2c36a472-cb02-446f-91a2-97440eb897b1] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:17:36 Notice configd.py [2da78693-92a1-4ad1-ba31-c75082c7692e] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:16:43 Notice configd.py [a7f6f843-38a5-4709-95db-d4c5d29dda2e] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:16:40 Notice configd.py [c49bbc96-11c6-4828-bebe-f3ff9c5ffc32] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
I have a lagg0 with four interfaces on it. Three VIP's seem to be OK, one is making problems.
Updated to 23.1_6.
The VIP's are swapping frequently. The lagg0_vlan80 is having problems.
But also all other VIP's are effected, no traffic possible for about 10 minutes.
2023-02-06T14:06:43 Notice configd.py [fa17137f-adfd-4cd1-9cec-d6f691056785] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T14:06:39 Notice configd.py [0f4181cb-d43d-4e8c-b076-d2cfac7f3ec7] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T14:06:38 Notice configd.py [6c0cda9a-238e-426f-8e04-3c29aa86719d] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T14:05:38 Notice configd.py [b287b466-1a9b-42e4-bc23-6c04bcd75188] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:45:23 Notice configd.py [c4eb3166-afec-4386-b8d7-0f129641af6f] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:45:20 Notice configd.py [f9a85c84-eb9a-4a63-9ef2-5e1df97e0327] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:39:53 Notice configd.py [bc11800c-46f6-49b7-82cc-c846a5a5d695] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:39:50 Notice configd.py [1385fd0c-9709-4de2-bce9-31c80f2a1816] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:25:40 Notice configd.py [d050812f-a205-40ae-9f66-2c681383f95d] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:25:36 Notice configd.py [9eca6fd6-8085-49ad-827b-c1c8c3544068] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:18:17 Notice configd.py [bf29afba-6f22-49ef-a55b-823473621420] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:18:14 Notice configd.py [68780d24-4c6f-44e7-8a01-c572ec49bd22] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:18:13 Notice configd.py [2c36a472-cb02-446f-91a2-97440eb897b1] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:17:36 Notice configd.py [2da78693-92a1-4ad1-ba31-c75082c7692e] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
2023-02-06T13:16:43 Notice configd.py [a7f6f843-38a5-4709-95db-d4c5d29dda2e] Carp event on subsystem 12@lagg0_vlan80 for type MASTER
2023-02-06T13:16:40 Notice configd.py [c49bbc96-11c6-4828-bebe-f3ff9c5ffc32] Carp event on subsystem 12@lagg0_vlan80 for type BACKUP
Pages1
