Forum Discussion

balcee's avatar
balcee
Icon for Altocumulus rankAltocumulus
Apr 05, 2024

Traffic not passing through load balancer

A few days ago, inbound traffic stopped passing through to the backend pools. No configuration changes had been made, but the issue appeared to be localised at load balancer level.

Here are the logs:

ltm 03-29 05:00:09 notice F5L-02 tmsh[30629]: private key export: All keys are being exported by user "root" via UCS saving at file "/var/local/ucs/daily_F5L-02.ucs".
ltm 03-29 13:31:46 notice F5L-02 tmm1[17670]: Clock advanced by 313 ticks
ltm 03-29 13:31:46 notice F5L-02 tmm[17670]: Clock advanced by 313 ticks
ltm 03-29 13:42:00 notice F5L-02 tmm[17670]: Clock advanced by 338 ticks
ltm 03-29 13:42:00 notice F5L-02 tmm1[17670]: Clock advanced by 336 ticks
ltm 03-29 19:13:04 info F5L-02 audit_forwarder[12115]: audit_forwarder started.
ltm 03-30 05:00:03 warning F5L-02 tmsh[10374]: [api-status-warning] wom/server-discovery is deprecated
ltm 03-30 05:00:03 warning F5L-02 tmsh[10374]: [api-status-warning] wom/endpoint-discovery is deprecated
ltm 03-30 05:00:03 warning F5L-02 tmsh[10374]: [api-status-warning] wom/deduplication is deprecated
ltm 03-30 05:00:03 warning F5L-02 tmsh[10374]: [api-status-warning] sys/ecm/cloud-provider is deprecated
ltm 03-30 05:00:03 warning F5L-02 tmsh[10374]: [api-status-warning] sys/datastor is deprecated
ltm 03-30 05:00:08 notice F5L-02 tmsh[10369]: private key export: All keys are being exported by user "root" via UCS saving at file "/var/local/ucs/daily_F5L-02.ucs".
ltm 03-30 09:26:06 notice F5L-02 mcpd[5739]: Unable to do incremental sync, reverting to full load for device group /Common/dg_failover device %cmi-mcpd-peer-/Common/F5L-01 from commit id { 846570 7351495955005963346 /Common/F5L-01 } to commit id { 864347 7351496050170958610 /Common/F5L-02 }.
ltm 03-30 09:48:38 notice F5L-02 tmm1[17670]: HA unit 1 state change: from 1 to 0.
ltm 03-30 09:48:38 notice F5L-02 tmm[17670]: HA unit 1 state change: from 1 to 0.
ltm 03-30 09:48:38 notice F5L-02 sod[6673]: Standby
ltm 03-30 09:48:38 notice F5L-02 sod[6673]: Standby for traffic group traffic-group-1.
ltm 03-30 09:48:38 notice F5L-02 sod[6673]: Traffic group traffic-group-1 going standby via targeted failover command.
ltm 03-30 09:48:38 notice F5L-02 sod[6673]: Traffic group traffic-group-1 received a targeted failover command for 10.68.250.81.
ltm 03-30 09:48:38 notice F5L-02 sod[6673]: Command:  go standby /Common/traffic-group-1 /Common/F5L-01 GUI.
ltm 03-30 09:48:39 info F5L-02 sod[6673]: Next active for traffic group traffic-group-1.
ltm 03-30 13:30:40 warning F5L-02 tmm[17670]: Clock has unexpectedly adjusted by 1697 ms
ltm 03-30 13:30:42 warning F5L-02 tmm1[17670]: Clock has unexpectedly adjusted by 1697 ms

 

After forcing a failover of the cluster at 09:48, traffic started passing through again. Is there anything you're able to advise on why this issue may have occurred?

 

Thank you

1 Reply

  • It could be that the configuration was out of sync between the two causing an issue but it's difficult to say without seeing the output of other troubleshooting commands. You might consider making a QKVIEW of the device that had the issue and uploading it to iHealth and see if there are any bugs for your version that would explain the issue you had.