bernardodemarco commented on PR #13001: URL: https://github.com/apache/cloudstack/pull/13001#issuecomment-4263708572
Hello, @weizhouapache > can you grep "arping" in the /var/log/cloud.log in the backup VR (now it should be primary VR) ? Sure, here are the `arping` logs emitted by the old backup VR: <details> <summary><code>grep 'arping' /var/log/cloud.log</code></summary> ``` root@r-20-VM:~# grep 'arping' /var/log/cloud.log 2026-04-16 21:15:20,217 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:21,563 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:21,712 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:22,195 INFO Copied /opt/cloud/templates/arping_gateways.sh.templ to /ramdisk/rrouter/arping_gateways.sh 2026-04-16 21:15:23,403 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:23,490 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:24,429 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:24,543 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:24,628 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:24,942 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:24,998 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:25,039 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:25,594 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:25,676 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:25,749 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:26,275 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:26,341 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:26,419 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:27,449 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:27,545 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:27,616 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 2026-04-16 21:15:27,975 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.15 192.168.122.1 2026-04-16 21:15:28,039 INFO Executing2: arping -c 1 -I eth1 -A -U -s 192.168.122.13 192.168.122.1 2026-04-16 21:15:28,090 INFO Executing2: arping -c 1 -I eth2 -A -U -s 10.0.0.128 10.0.0.1 ``` </details> > can you test also port forwarding and load balancing rules, other than static nat ? Yes, I have performed the tests with static NAT, port forwarding and load balancing rules. It is working fine for all of them. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
