Forum Discussion

Doran_Lum_13484's avatar
Doran_Lum_13484
Icon for Nimbostratus rankNimbostratus
Sep 18, 2014

How do I move a Pool from Common partition to another partition ?

Hi all, how do I move a pool from one partition(Common) to another partition in my F5 version 11.4 ?

 

I notice the partition field is fixed and no option available to move it. What about the nodes , do i also need to move it toegther with the pool over to the other partition ?

 

under the link below it says "you cannot move an object in Common to one of the new partitions. Instead, you must delete the object from Common and recreate it in the new partition."

 

http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos_management_guide_10_1/tmos_partitions.html?sr=40389350

 

  • you pretty much answered your own question. you can't move objects between partitions via the GUI. delete and create is the way to go.

     

    you could try to do it in the config files and reload them. but you need to be very sure what you are doing there else the config might not load causing issues.

     

  • THi's avatar
    THi
    Icon for Nimbostratus rankNimbostratus

    We have done this a couple of times when moving lots of/multiple objects, but one has to be pretty careful. If you need to move only a small number of objects, then do it via GUI.

    If you really want to play with the config files, you can copy the ltm pool (and possibly ltm node) parts from the source partition’s bigip.conf file into a text file, modify it and verify the syntax and merge to target partition’s bigip.conf file, finally saving the running config (make sure you have made backup copies..). Remember to remove the objects from the source partition, too.

    Something like:

    my_file:

    ltm node /Common/10.10.1.10 {
        address 10.10.1.10
    }
    ltm node /Common/10.10.1.11 {
        address 10.10.1.11
    }
    ltm pool /Common/test_pool {
        members {
            /Common/10.10.1.10:80 {
                address 10.10.1.10
            }
            /Common/10.10.1.11:80 {
                address 10.10.1.11
            }
        }
    }
    

    In this case the source partition is /Common. Then edit the file to reflect the correct target partition path (find/replace). If the nodes are also used elsewhere, then do not copy them here, they may remain in the /Common.

    Edited my_file:

    ltm node /target/10.10.1.10 {
        address 10.10.1.10
    }
    ltm node /target/10.10.1.11 {
        address 10.10.1.11
    }
    ltm pool /target/test_pool {
        members {
            /target/10.10.1.10:80 {
                address 10.10.1.10
            }
            /target/10.10.1.11:80 {
                address 10.10.1.11
            }
        }
    }
    

    Doublecheck that only the paths are changed. You can check the syntax by comparing with existing bigip.conf file. Then move to the target partition (ie. cd /config/partitions/target folder, check with pwd) and do verify merge command:

    tmsh sys load config verify merge file my_file
    

    This validates the specified configuration in my_file to see whether it is valid to be merged into the running configuration. The running configuration will not be changed when using verify.

    If all is ok, then you can try to merge (while being in target partition, check with pwd)

    tmsh sys load config merge file my_file
    

    And finally if everything works, you need to save the running config while being in target partition.

    tmsh sys save config current-partition
    

    This saves the running configuration in your current partition by overwriting the system configuration files. You need remove the source partition’s original objects and save the config, too.

    be careful, test first in test unit if you have one - or rather do it via GUI

  • shaggy's avatar
    shaggy
    Icon for Nimbostratus rankNimbostratus

    The feature allowing movement of objects appears to be on its way - the release notes for 11.6 show an early access feature giving the ability to move/rename objects:

     

    Object move and rename (early access) This release provides early access to the feature that enables move/rename of specific BIG-IP object types, such as virtual servers, virtual addresses, pools (implicitly moves pool members), nodes, monitors, profiles, iRules, iApps, device names, self IP addresses, iCall, and folders. Note that this functionality is not provided for VLANs or Partitions.

     

    http://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/product/relnote-ltm-11-6-0.html