Forum Discussion
Nimbostratusnew partition and common partition have same VIPs
Hi Guys,
I have created a new patition on F5 LTM but it is having the same VIP config as common. As per my understanding it should be blank so that I can create some new VIP but it not blank.
Please let me know if there any setting which needs to changed.
Thanks,
wlopez_98779All objects created under the default 'Common' partition are automatically:
-associated to the default routed domain '0'
-viewable/usable from all other non-default partitions
If you want to isolate objects on the new partition from the ones on the default 'Common' partition then you'll need to create the vlans and a new route domain under the non-default partition. You'll also need to enable the new route domain (Ex. '1') to be the partition default route domain and select the strict isolation option. Then you can create your self and floating IPs, default route, pools, virtual servers, etc. isolated from the default partition 'Common' and route domain '0'.
Nilesh_Dubey_36Hi Wlopez
Thanks for suggestion. Can you please let me know what would be impact of new route domain on current environment. As I read in an article, more than one route-domain in same environment create unnecessary routing issues.
Please correct me if i am wrong.
Thanks,
- wlopez_98779
Adding a route domain has no impact on current services. If you're not familiar with that setup I would suggest you try it on a non-production environment. It's basically the same as everything else you configure under the default partition/route domain, except for the initial setup.
You first create the new partition.
Then you move to the new partition.
You create the vlans for the new partition.
You create a new route domain with a new ID (Ex. 1), selecting the new vlans created under the new partition, selecting strict isolation and setting the new route domain as the default route domain for that partition.
You create the new local/non-floating IP addresses for the new vlans.
You create the new floating IP addresses for the new vlans.
You create your routes for the new route domain.
After that you start creating your pools, profiles, virtual servers, etc. the same way you currently do.
wlopezCirrocumulus
All objects created under the default 'Common' partition are automatically:
-associated to the default routed domain '0'
-viewable/usable from all other non-default partitions
If you want to isolate objects on the new partition from the ones on the default 'Common' partition then you'll need to create the vlans and a new route domain under the non-default partition. You'll also need to enable the new route domain (Ex. '1') to be the partition default route domain and select the strict isolation option. Then you can create your self and floating IPs, default route, pools, virtual servers, etc. isolated from the default partition 'Common' and route domain '0'.
- Nilesh_Dubey_36
Hi Wlopez
Thanks for suggestion. Can you please let me know what would be impact of new route domain on current environment. As I read in an article, more than one route-domain in same environment create unnecessary routing issues.
Please correct me if i am wrong.
Thanks,
- wlopez
Adding a route domain has no impact on current services. If you're not familiar with that setup I would suggest you try it on a non-production environment. It's basically the same as everything else you configure under the default partition/route domain, except for the initial setup.
You first create the new partition.
Then you move to the new partition.
You create the vlans for the new partition.
You create a new route domain with a new ID (Ex. 1), selecting the new vlans created under the new partition, selecting strict isolation and setting the new route domain as the default route domain for that partition.
You create the new local/non-floating IP addresses for the new vlans.
You create the new floating IP addresses for the new vlans.
You create your routes for the new route domain.
After that you start creating your pools, profiles, virtual servers, etc. the same way you currently do.
RaghavendraSYAltostratus
Which version you are running?
In versions prior to BIG-IP 11.0.0, the BIG-IP configuration files ( bigip.conf file and bigip_base.conf file) reside only in the /config directory.
- Nilesh_Dubey_36
Current version is 12.1.2
Thanks,
- RaghavendraSY_7
Cumulonimbus
Which version you are running?
In versions prior to BIG-IP 11.0.0, the BIG-IP configuration files ( bigip.conf file and bigip_base.conf file) reside only in the /config directory.
- Nilesh_Dubey_36
Current version is 12.1.2
Thanks,