Forum Discussion

dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Feb 24, 2015

Folders and synchronization

Hi,

 

For some reason my original post just vanished. I would like to figure out real life usage of folders and different Device Group (DG) or Traffic Group (TG) assignment. As far as I understand subject: 1. Device can be member of only one sync-failover DG (SFDG). So only one such group could be assigned to any folder. 2. Device can be member of many sync-only DGs (SODG). So different folders can be assigned to different SODGs 3. Traffic Group (floating) can be only connected to SFDG. There can be many TGF so different folders can be assigned do different TGFs.

 

So far so good, now part I am not sure (hope that above is indeed true :-) 1. If /Common folder is assigned to SFDG and there is App_A folder inside that is assigned to some SODG what will happen. App_A folder will be excluded from syncing performed by SFDG? It will be included but as well synced to another device specified by SODG? 2. If given folder as an attribute has SODG then there is no way to assign any TGF to such folder, only None or traffic-group-local-only is valid? For None objects are replicated to other devices for traffic-group-local-only they are not replicated.

 

Then what are real life scenarios when SODG are used most often. SODG plus None as TG can be used to replicate for example VSs and VIPs to another device but as far as I understand it then IP conflict can occure, if there is no L2 (VLAN) or L3 (router) separation between interfaces of BIG-IP devices where those VIPs are active. I am wondering when using SODG is good idea.

 

Piotr

 

deployment
design
management
TMOS
TMSH

4 Replies

Sort By
  • Brad_Parker's avatar
    Brad_Parker
    Icon for Cirrus rankCirrus
    Feb 25, 2015

    Sync-Only groups are good for syncing non-traffic group objects like you suggested. This could include users if you decided to create a users partition for all your user accounts to live in. It could also include iRules and Datagroups created in the partition assigned to the sync-only group. iRules and datagroups can be used from the partition by any other partition by the way of using the proc command in a different iRule or in the case of datagroups just calling them by /Partition/rulename. Another use case is in the case of DNS-Express in GTM. Its best practice to create all your DNS-Eexpress zones in a sync-only group because that just syncs the DNS-Express configuration amongst you GTMs.

     

  • Brad_Parker_139's avatar
    Brad_Parker_139
    Icon for Nacreous rankNacreous
    Feb 25, 2015

    Sync-Only groups are good for syncing non-traffic group objects like you suggested. This could include users if you decided to create a users partition for all your user accounts to live in. It could also include iRules and Datagroups created in the partition assigned to the sync-only group. iRules and datagroups can be used from the partition by any other partition by the way of using the proc command in a different iRule or in the case of datagroups just calling them by /Partition/rulename. Another use case is in the case of DNS-Express in GTM. Its best practice to create all your DNS-Eexpress zones in a sync-only group because that just syncs the DNS-Express configuration amongst you GTMs.

     

    • dragonflymr's avatar
      dragonflymr
      Icon for Cirrostratus rankCirrostratus
      Feb 25, 2015
      Thanks, I was suspecting something like that. Piotr