Forum Discussion
Virtual address from address list is down after assignment to VS
- Oct 30, 2023
Here is an update after I opened a case.
- this is actually a known behavior, and it is documented here Route Domain ID specified in traffic matching criteria address list doesn't take effect on Virtual Server IP (f5.com)
- so after you assign your address list to the VS, its create a traffic-matching-criteria object that is by default attached to the default domain
- you can change the route domain from CLI
- then the virtual IP is finally UP, and answering ARP requests
In my case, I also have this other issue since I'm also using ASM policy on the VS: Security log profile cannot be assigned to a virtual servers using address list, traffic matching criteria, TMC (f5.com)
- it is NOT recommended to use address list on VS if you intend to use ASM on the VS as well
- there is a workaround to use it anyway, but only for experimental purpose
I've tried the following :
in partition A : create address list, and assign to VS in partition A as well => virtual addresses are down
in common partition : create address list, and assign to VS in partition common as well => virtual addresses are UP!
mix : create address list in common partition, and assign it to VS in partition A => virtual addresses are down
=> I do need to assign address lists to my partition A VS, I can't create them in /common, due to different route domains.
How to achieve that ?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com