For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Eric_Hartwell_1's avatar
Eric_Hartwell_1
Icon for Nimbostratus rankNimbostratus
Feb 13, 2014

Partitions and moving objects between them

Does anyone know if this https://devcentral.f5.com/wiki/AdvDesignConfig.Migrate-objects-to-a-new-partition-and-route-domain.ashx is relevant for 11.4.1? We want to segment our VIPs into different partitions for easy viewing/management. We've created some pools and VIPs and would prefer to move existing rather than recreating.

 

thanks,

 

eah

 

8 Replies

  • Robin_Mordasie1's avatar
    Robin_Mordasie1
    Historic F5 Account

    I had a look through the guide and it looks like it hasn't been updated for version 11. In version 11 you no longer have partitions defined in the same bigip.conf file, and partitions now have their own bigip.conf in subfolders under /config/partitions. You will still need to use a text editor like vi to remove the sections from your /config/bigip.conf to /config/partitions/tenant1/bigip.conf

     

    • Eric_Hartwell_1's avatar
      Eric_Hartwell_1
      Icon for Nimbostratus rankNimbostratus
      let me make sure I have this. In order to move objects, I cut them from bigip.conf, change any reference to /common, and paste the edited entries into the new partitions bigip.conf.
    • Eric_Hartwell_1's avatar
      Eric_Hartwell_1
      Icon for Nimbostratus rankNimbostratus
      if pools and nodes created on /common are accessible to VIPs created on another partition, is there a reason to move those pools/nodes?
  • Robin_Mordasie1's avatar
    Robin_Mordasie1
    Historic F5 Account

    If your nodes or pools are common objects that might be referenced by vips/pools in other partitions then you will want them to remain in /Common. I might suggest that you define all your shared nodes in /Common, and then create partition specific pools which reference the nodes in /Common. This will allow you to create users that can administratively disable pool members in their own partitions without affecting other partitions.

     

  • Hamish's avatar
    Hamish
    Icon for Cirrocumulus rankCirrocumulus

    You could write a script that reads the config, builds an object dependency tree and then deletes and re-creates the affected objects...

     

    Interesting piece of work.... If only I had more time :)

     

    H

     

  • Hi Eric,

     

    take a look at this one link

     

    this guy wrote an iapp that allows you to copy objects.

     

    you may found it useful in case you want to make a new iapp that meets your requirements.

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    You might have a problem sharing some objects if you want to have your partitions on different route domains.