Forum Discussion

zaephod_10490's avatar
zaephod_10490
Icon for Nimbostratus rankNimbostratus
Nov 11, 2013

Anyone actually use ace2tmshv1.2.pl to migrate ACE AS (3.4) config to tmsh 11.4?

I have two questions, first is there a way on the ACE system to get a complete running-config of all contexts?

 

 

Second has anyone successfully gotten the ace2tmshv1.2 script to convert some of the basic information like vlan configs, ip addresses, and node names? I grabed the running config from one context and tried to run the script against it but half the nodes didn't convert over, none of the vlans were identified, and IP addresses assigned to the VLANs were not migrated.

 

 

Just curious if anyone was successful or if I should be just going straight manual conversion.

 

 

Thank you

 

7 Replies

  • The only thing you can do, is go to the flash of the ACE and get all of the separate config files from there. TFTP of something like that. One the ACE there is one per context. I done ACE to LTM quite a few times now, and I think it is better to do it manually as it allows for a bit of a tidy up, and also there are things you can enable of the LTM, that just don't exist of the ACE. I think even if there was a tool, I would still do it manually
  • Thats what I thought in regards to the ACE config. I ran a backup all which produced a tgz file of all the running-configs then FTP'd that off but I was hoping for one big config with all the data. Guess I can always cat * > ciscoace.txt. I was looking to use the script more to get all the nodes and pools ported over since that seems to be the bulk of data. But you are right with a lot of the config, it is quite different between ACE and F5. I was just hoping there was a trick to using the script or that I had missed a step.
  • You could just take all the node in a text file and use "find and replace" The TMSH code to create a node is "create node 10.10.10.1 { screen test } " The ACE code to create a real server is rserver host xxxxxxx_RS ip address 172.17.94.48 inservice This is not exactly going to work, but for example you could do find / replace "ip address" with "create node" find / replace "rserver host" with "{" find / replace "_RS" with "}" - (Assumming you have _RS at the end of your real servers) or write a bit more of a clever script or use Excel
  • Thanks for the followup and that is probably the route I will end up taking. I was just really curious if anyone had success with the script.
  • can just add a no on succesfully using the script, too much it misses.
  • Thanks for the input. I found the same thing regarding the script and gave up on it. I went with GreeceMonkey's suggestion of search and destroy
  • Robin_Mordasie1's avatar
    Robin_Mordasie1
    Historic F5 Account

    To make a long story short, no the scripts themselves are not the silver bullet to take care of the migration. Any way you look at it you will need to put in a considerable effort and time to make sure you end up with a decent bigip.conf. Either you will need to extend the logic in those scripts to produce a bigip.conf that you are happy with, or you will need to massage the output of those scripts to get to the point where you have a decent bigip.conf.