Cascading Configs Tool for F5 Distributed Cloud Managed Service Provider (MSP) and Delegated Access Customers
A new tool has been released that enables F5 Distributed Cloud Managed Service Provider customers or customers with Delegated Access to push and maintain shared configurations to any of their Child Tenants.
BigDB.dat: Configsync.PeerIpaddr : No longer used in v11.6?
I have just found that the "[Configsync.PeerIpaddr]" section in the BigDB.dat contains an IP address that is different from what I get from: tmsh list /cm device my_device_name configsync-ip , and it does not get overwritten by changes done via the Configuration Utility. It seems that this variable is no longer used in v11.6.x. Can anybody confirm this?Problem with config-sync all of a sudden. Cannot create archive as well.
I am getting errors when I try to run config-sync on my two 1600 LTMs. Config sync was working before but all of a sudden I cannot do it anymore. Primary: 10.10.10.12 Secondary: 10.10.10.13 Floating: 10.10.10.14 Running on Primary. Synchronizing to peer. Checking configuration on local system and peer system... Peer's IP address: 10.10.10.13 Synchronizing Master Keys... Saving active configuration... /home/admin/20140507-1914: (at /home/admin/20140507-1914) does not exist /home/admin/20140507-1913: (at /home/admin/20140507-1913) does not exist Errors during file attribute collection Operation aborted. /tmp/configsync.spec: Error creating package Error creating package Error running config sync all. BIGpipe parsing error: 01110001:3: Error running config sync all Running on secondary. Synchronizing from peer. Configsync Mode: Pull Saving temporary UCS on peer... OperationFailed exception: Primary error : 16908289 Secondary error: 0 Error text : Error saving configuration Error saving temporary UCS on peer. Checking configuration on local system and peer system... Peer's IP address: 10.10.10.12 Transport and install failed Error running config sync pull. BIGpipe parsing error: 01110001:3: Error running config sync pull Running on primary. Creating an archive. Saving active configuration... /home/admin/20140507-1914: (at /home/admin/20140507-1914) does not exist /home/admin/20140507-1913: (at /home/admin/20140507-1913) does not exist Errors during file attribute collection Operation aborted. /tmp/configsync.spec: Error creating package WARNING:There are error(s) during saving. Not everything was saved. Be very careful when using this saved file! Error creating package Error during config save. BIGpipe parsing error: 01020001:3: The requested operation failed. What is weird is that files do exist in that folder. Both files have 600 level permissions.
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
Caught configuration exception (0), Can't find monitor rule
I've been playing around with device trusts and sync-only groups, trying to figure out a way to keep my access policies in sync across multiple devices (while other configurations remain different, as this is not an HA pair or active-standby situation). I had some trouble with getting things to work, and finally removed the trusts altogether. But now I'm getting this error message ever 30 seconds or so... err mcpd[6455]: 01070712:3: Caught configuration exception (0), Can't find monitor rule: . (where is one of a variety of different numbers). Anyone have an idea of how to get rid of this issue. Can't seem to find anything helpful on my own. Thanks!Can we pull the config sync from Active to standby when you are in standby device ?
Hi Experts !!! say we have 2 f5 in cluster , 1.BIGIP-TEST-1 (Active) 2.BIGIP-TEST-2 (Standby) Now someone has done a change in Standby device . Since BIGIP-TEST-1 is Active device . I would like to pull the latest config from Standby to Active .( I do not want to login to Standby and do the sync ) In this case, 1.How can I pull the config sync from standby device ? 2.Do we have any cli command to pull the config sync from other device ? 3.Do we have a command to know which device in the cluster has the recent changes made ?How to sync the config in CLI when we have multiple traffic-group ( Active-Active)
Hi Experts !!! How to sync the config via cli in Active-Active setup . Example : We have 2 f5 named BIGIP-A and BIGIP-B and 2 traffic-group-1 is active in BIGIP-A and traffic-group-2 is Active in BIGIP-2 . On BIGIP-A I configure a VIP which is Active in traffic-group-2 , in this case how do I sync the config in CLI . I need CLI command to sync the config when the F5 HA status are in Acive-Active setup .
GTM Sync config Save
Just a basic (may sound Silly as well ) GTM Question regarding Sync - If I have 4 GTMs in a sync grp (GTMA,GTMB, GTMC, GTMD) , none of them have autosave option enabled and I did a latest change on GTMA followed by "save sys config" in TMSH. So, will the rest of the GTMs get the updated bigip_gtm.conf file or do I need to type "save sys config" in TMSH of all the other GTMs ?
Config sync for ASM module not impacting other modules
Hello experts, Need an advice how to properly sync ASM policy/configuration between different devices. I have an environment with a sync-failover cluster consisting of 2 F5 devices in each data centre so in total - 4 devices. Each cluster runs APM, LTM and ASM. What I want is to configure sync only between clusters for ASM module not impacting other modules. So if I make ASM change on a cluster in 1st DC the change is synced to 2nd DC cluster. All other changes for LTM/APM are synced between devices in the particular DC cluster only - not propagated between clusters in different DCs. Would this be possible? Is there any guide / KB to implement this? Thanks, Roman
