While troubleshooting a new implementation with axdebug captures, I see dozens of messages pairs like this:
@279485663 i( 3, 101, b4795)> ip 10.95.100.44 > 10.42.101.225 tcp 6310 > 443 PA 9b8c5dba:ee9455c7(37)
@279485663 i( 3, 101, b4795)> Rerouting failure for forward traffic match
And the page is ‘waiting to load’.
What does the re-routing failure mean and what could be causing it?
Not the virtual-server is on vlan-A and the back-end servers are on vlan-B
Hi
It looks like AX doesn’t have enough resources to process the traffic.
is this only affecting 1 VIP?
I worked with A10 support on this - it was a strange situation where the A10 was not learning the address for one vlan in a vrrp instance. They were quite surprised by that state. A fail-over to the secondary unit resolve the issue, and when we failed back all was good. A10 captured logs/backup and will review to see how it could have gotten into that state