Forum Discussion
CirrostratusMgmt monitor issue
Hello,
There are two different routing table son the F5, one for the TMM interface which the self IPs used, and another one for the management one.
in the default cases with respect to the default routes, the tmm take presedence over the management default route, but in your case, the back end server IP is "10.20.54.2/24" which is located in the same subnet of the management.
i think you can make a specific route for this IP/32 and add the gateway of your self IP and check.
*network > route > Add (10.20.54.2/32)
In general, you should start considering changing the management IP to a management subnet only, or change the backend server IP.
BR,
Hello,
There are two different routing table son the F5, one for the TMM interface which the self IPs used, and another one for the management one.
in the default cases with respect to the default routes, the tmm take presedence over the management default route, but in your case, the back end server IP is "10.20.54.2/24" which is located in the same subnet of the management.
i think you can make a specific route for this IP/32 and add the gateway of your self IP and check.
*network > route > Add (10.20.54.2/32)
In general, you should start considering changing the management IP to a management subnet only, or change the backend server IP.
BR,
- Michaelyang
Hi Mohamed_Salah,
Thanks for your reply.
I make a specific route for this IP/32 and add the gateway of my self IP and check.
Successfully solved the problem !I would like to ask F5 if there is a relevant document to explain this situation.
Any help is appreciated.
