Forum Discussion
Change Partition of Virtual Address
When we rolled out our first APM build, we put most of the objects in a partition specific to the service and this has worked out quite well. The first partition has a couple virtuals that have a destination of 0.0.0.0/0 and the associated 0.0.0.0 virtual address was also created in the partition.
We are now rolling out another service and are using a second partition. This second partition also has a virtual which uses 0.0.0.0 and even though the virtuals in both partitions listen on distinct VLANs, I cannot create a virtual that references a virtual address created in another partition.
My question is if there is any issue moving the virtual address from the first partition into /Common? I presume there is no problem doing this but having never done this before I just wanted to ask the experts.
Thanks.
APM 11.5.1
1 Reply
- Brad_Parker
Cirrus
You will have to delete it and recreate it. You can however use route domains and assign the unique route domains to the partitions. If you create a route domain for both your VLANs and assign the route domains as the default for each corresponding partition you can create a 0.0.0.0/0 VIP in both partitions.
changes the default route domain for a partition.tmsh modify auth partition default-route-domain
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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