Citrix Netscaler to F5 BIG-IP
Problem this snippet solves: This scripts is built to convert Citrix Netscaler text based configuration files to BIG-IP commands. This scripts aim to reduce the largest burden of entering object names, IP addresses and other parameters, as well as logically linking these objects to each other. This script is not meant to perform a totally automated and unattended migration. For the objects that the script migrates, not all parameters may be converted. For the parameters that are converted, some are mapped to the closest matching BIG-IP feature. If there are any non-ASCII characters or line-breaks in the source file, this will need to be manually fixed first (some screen captures may wrap lines so copying the file directly is preferred). All Netscaler commands are on a single line. Note that this script will produce a comprehensive list of errors, warnings, notes, etc, at the bottom of the output file. You should look through these first, starting with the errors and working your way down to less critical messages. You may need to correct problems in the input file or in the Perl script and re-run the conversion. Once you have reviewed the warnings and notes, you should look through the configuration that was generated. The original Netscaler commands are provided for each portion of the BIG-IP configuration and you should compare the "before and after" for each object. How to use this snippet: To get command line config execute the following command on Netscaler: more /nsconfig/ns.conf (Or you can secure copy it to your PC using something like winscp/pscp.) Input restrictions: Probably only supports Netscaler v7, v8, and v9 Output restrictions: Outputs BIG-IP 9.4.x format (which v10 appears to read fine) Output file contains warnings errors, base config, and main bigip.conf It is best to have Active Perl on you PC to perform the conversions. You can also use the Perl installation on the BIG-IP command line. Once the file is converted you can import the configuration into the BigIP using (b load, or b merge). You can also copy/paste into bpsh. Read the header of each of the scripts files, they have addition information on the usage of the scripts. Usage: perl nsv8_to_f5.pl netscalerconfigfile /var/tmp/bigipoutputfileCisco CSM to F5 BIG-IP
Problem this snippet solves: This script will convert Cisco CSM configuration files to F5 BIG-IP configuration. It is not intended to do a complete migration, but should help do the heavy lifting. How to use this snippet: The script dumps to stdout, to capture in a file, use: perl csm2f5.pl csmconfigfile > /var/tmp/bigipconf.txtCisco CSS to F5 BIG-IP
Problem this snippet solves: This script will convert Cisco CSS Configuration Files to F5 BIG-IP configuration. It is not intended to do a complete migration, but should help do the heavy lifting. How to use this snippet: The script dumps to stdout, to capture in a file, use: perl css2f5.pl cssconfigfile > /var/tmp/bigipconf.txtCisco ACE to F5 BIG-IP
Problem this snippet solves: This script will convert Cisco ACE Configuration Files to F5 BIG-IP configuration. It is not intended to do a complete migration, but should help do the heavy lifting. How to use this snippet: The script dumps to stdout, to capture in a file, use: perl ace2f5.pl aceconfigfile > /var/tmp/bigipconf.txtCisco ACE to F5 BIG-IP via tmsh
Problem this snippet solves: This script will convert Cisco ACE Configuration Files to F5 BIG-IP configuration. It is not intended to do a complete migration, but should help do the heavy lifting How to use this snippet: The script dumps to stdout, to capture in a file, use: perl ace2tmsh_v1.2.pl aceconfigfile > /var/tmp/bigip-tmsh.confCisco CSS to F5 BIG-IP via tmsh
Problem this snippet solves: This script will convert Cisco CSS Configuration Files to F5 BIG-IP configuration. It is not intended to do a complete migration, but should help do the heavy lifting. How to use this snippet: The script dumps to stdout, to capture in a file, use: perl css2f5-tmsh.pl cssconfigfile > /var/tmp/bigipconf.txtRadware to F5 BIG-IP via tmsh
Problem this snippet solves: This script only converts WSD text file. It does not convert ".ber" files. We may add AppDirector support at some point. Here is an explanation of the different file from one of our radware experts "Harry Kleinbourg": For some years, wsd has been replaced by AppDirector product. WSD config files could be saved in a specific format .ber. Then with an external tool, the ber file could be transform into an ascii file. Now, with AppDirector, there's only one format which is a text file. The system config-immediate isn't a config file. It's a command which shows the running config but it doesn't replace the config file. An easy way to check if you have a wsd or an appdirector is to run the command system device-info or to look into the system config-immediate : if the lines begin with "wsd" then it is a wsd, if the lines begin with appdirector then it's an appdirector. Obvious, isn't it ? How to use this snippet: The script dumps to stdout, to capture in a file, use: perl rad2f5.pl radwareconfigfile > /var/tmp/bigipconf.txt