Forum Discussion
Virtual LTM syncing to Physical Viprion 2400
You don't want to use a UCS as that has no merge options; it completely replaces the config on the device. It's also designed to be used more as a backup for the device on which it was created (in the event of a problem or change rollback), and is tied to it in large part. A device group is not the way to go either.
You probably want to use an SCF to replicate configuration data from your BIG-IP VE systems to the VIPRION 2400, without completely replacing the existing VIPRION configuration data either. (Think VLANs, self IPs, etc.) You can take an SCF backup of the running configuration on the VEs, edit them to eliminate the configuration data you don't want on the 2400, then load/merge them onto the 2400.
Check out these articles for more info on replicating configuration data from one BIG-IP system to another:
SOL13408: Overview of single configuration files (11.x - 12.x) - https://support.f5.com/kb/en-us/solutions/public/13000/400/sol13408.html
https://devcentral.f5.com/questions/tmsh-load-sys-config-file
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com