Config-sync only certain BIG-IP folders
Hey guys - We have F5 platforms at each datacenter using a OTV link to extend Layer 2 services. We would like to be able to synchronize everything in the /Common folder/partition. But create a site specific folder or partition that does not get synchronized. Reading the snippet below, it seems like this is doable using folders. But it is not clear to me how to actually assign a folder to a specific traffic-group, and then to a specific sync-only device group? Any help on the configuration steps to accomplish this? (BIG-IP 12.1.2) Folders A folder is a container for BIG-IP configuration objects. You can use folders to set up synchronization and failover of configuration data in a device group. You can sync all configuration data on a BIG-IP device, or you can sync and fail over objects within a specific folder only. https://support.f5.com/csp/article/K13946
How to link the VIP subnet with traffic-group ?
Hi team , We have 2 subnets for configuring VIP and we have 2 f5's in cluster nd 2 traffic-groups ..So I just wanted to know how we configure specific subnet to be part of one traffic group ? 10.10.100.0/24 = trafic-group-1 10.10.200.0/24 = traffic group-2
F5-SDK : How to update Virtual Address Traffic Group
I have an Active-Active LTM Deployment. Virtual Servers ( and Virtual Addresses ) are split between two units. I am trying to use F5-SDK to update traffic group so that VS/VA will move between two units. Vars BigIP_IP = "10.10.100.100" V_IP = "172.31.13.151:80" New_TG = "/Common/traffic-group-2" Connect new_mgmt = ManagementRoot(BigIP_IP, username, password) Load v_a_info = new_mgmt.tm.ltm.virtual_address_s.load(name=V_IP, partition='Common') Assign new TG v_a_info.trafficGroup = New_TG Update Virtual Address v_a_info.modify(v_a_info.trafficGroup) But getting this Error : Traceback (most recent call last): File "update-virtual-address-traffic-group.py", line 13, in v_a_info = new_mgmt.tm.ltm.virtual_address_s.load(name=V_IP, partition='Common') File "/usr/lib/python3.6/site-packages/f5/bigip/resource.py", line 655, in load raise InvalidResource(error_message) f5.sdk_exception.InvalidResource: Only Resources support 'load'. Then found out that "Virtual Addresses" are "Collections" and I able to read them fine using below command and loop through all attributes of a Virtual Address: v_a_info = new_mgmt.tm.ltm.virtual_address_s.get_collection() But then questions comes up how to update an Attribute of a "Virtual Address" in a Collection and push it back to the LTM to implement the change Versions F5-SDK : 3.0.20 LTM : 12.1.2 HF2 I highly appreciate any help or link to resolve this issue -Muhammad
List of traffic-group objects using TMSH?
(Referring to versions 11.5 or greater) The GUI provides a means for listing all failover objects in a traffic group by navigating to Device Management > Traffic Groups > [select traffic group] > Failover Objects I have been unable to find a similar means to list the failover objects in TMSH, other than iterating through all object classes that can fail over and sorting based on the 'traffic group' parameter of the object. Is there a single TMSH command that provides a listing of failover objects for each traffic group? Thanks! -EdRename a Traffic Group
Is it possible to rename a traffic group? I have two older BIG-IP devices that I would like to place in an active/active configuration, however, they each already have a traffic group configured with the same name. Is it possible to rename the traffic group on one of the systems? Units are running 11.6.1
Traffic-Group Behaviour
I have been testing traffic-group on my vLabs and I still do not quite understand the behaviour during failover times. The vLab I am working on has the following configuration: BIGIP_A - Traffic-Group-A BIGIP_A - Traffic-Group-B BIGIP_B - Traffic-Group-C BIGIP_B - Traffic-Group-D This configuration makes both devices become an Active-Active pair, which is fine. I expected that. I have added virtual addresses objects on all traffic-groups for testing purposes and enabled SNAT auto-map as well. The question I have is regarding the failover between them. When I simply unplug the network cable, the traffic-groups are not floating to the other device; however, if I power the device off, the traffic-group floats right away. The only situation, which I managed to make the traffic-group to failover after unplugging the network cable is by enabling the VLAN-Failsafe feature, which then automatically failover the traffic group to the other device. Can someone explain the reason for such behaviour or if it is just he way it supposed to be? Thanks
Single iApps, two traffic-groups
Is it possible to create multiple virtual-addresses on differents traffic-groups using iApps? I have two traffic-groups, and I want to create a virtual-server on each. VS_A -> VIP_A -> TG_A VS_B -> VIP_B -> TG_B With a single iApp. Do you know if it is possible and how to do that ? Best regards,
traffic-group has failover object that doesn't exist in "Virtual Servers" tab
Hi, I noticed that there is a failover object in the traffic group that doesn't exist in the "virtual servers" tab. I went to tmsh and ran the following. list ltm virtual-address x.x.x.145 ltm virtual-address x.x.x.145 { address x.x.x.145 mask 255.255.255.255 traffic-group traffic-group-1 } Can someone explain why I'm seeing this VS? Is there away to get the name of it to see if it should be there or not?
Replacing float-ip on default traffic group
Sorry for the long post. I have an active/standby HA pair of 6900's running 11.6.1. I am using the default traffic group with float-ip's for each server vlan and the float-ip's (.1) are the DG for each server vlan. We are now preparing to move that DG role off of the F5's and over to the core switch. This means I will need to give up that .1 float-ip for each server vlan and create a new float-ip that will be used for only automap source nat's for load-balance pool traffic. The plan is to... 1. Move the .1 float-ip DG for a couple of vlans at a time over a few weeks. 2. For each migration, on the standby unit, I will create a new float-ip (say .4) and assign it to the same default traffic group that the existing .1 float is part of. 3. Delete the .1 float-ip, leaving the new .4 float-ip in the default traffic group. 4. Failover to the standby, have the .1 go live on the core switches, clear arps and fingers crossed. If successful, then do the other F5. I'm know any existing pool connection using the old .1 automap source nat will be torn down after the failover, but that is to be expected. I know that's kind of a simplified high level approach but is that basically the steps I will need to do? Any unseen "gotcha's" I need to consider? Thanks!