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

slowpoke115_145's avatar
slowpoke115_145
Icon for Nimbostratus rankNimbostratus
Apr 03, 2014

Cloning virtual F5's and relicensing

If I were to setup a pair of F5's and clone them (for redeployment multiple times in multiple platforms). What would happen with the base registration keys? Are there any methods of resetting the keys and using a new license?

 

Ideally I'm looking at deploying F5's as quickly as possible and whilst this seems like a decent method, I'm not sure how the licensing will work. The other method would be to script the bigip_base.conf which is so complex and "unique" this seems much more troublesome.

 

application delivery
deployment
license
LTM
virtualization

1 Reply

  • What_Lies_Bene1's avatar
    What_Lies_Bene1
    Icon for Cirrostratus rankCirrostratus
    Apr 03, 2014

    I think as long as you re-license with a new key then you should be OK. Refer to http://support.f5.com/kb/en-us/solutions/public/13000/500/sol13570. It suggests you need to contact F5 support but I take this to mean when you want to move the license, not clone and use a new one.

     

    Regarding the VNICs and MAC addresses (that may be mixed up after a clone to a new host), refer to these if you have any issues;

     

    • http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-ve-setup-vmware-vcloud-11-2-0/5.html
    • http://support.f5.com/kb/en-us/solutions/public/12000/100/sol12149.html

    Also note (as I never knew this): FastL4 virtual servers affected will have very low throughput. "The customer should enable TCP Segmentation Offload (TSO) by modifying 'sys db tm.tcpsegmentationoffload'. The customer may also resolve this issue by disabling large Receive Offload (LRO) on any hypervisor they plan on running Virtual Edition."