<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ASAtoVSX - Translate your Cisco running config to VSX and more! in API / CLI Discussion</title>
    <link>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72909#M4316</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I wanted to share with you a tool that we developed to help us automate a big part of a project.&lt;/P&gt;&lt;P&gt;Long story short, we needed to migrate many virtual context from ASA to VSX. As you may know adding static routes and interfaces to a VS can be cumbersome. Especially if you have firewalls with +100 interfaces and +300 routes &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The tool was developed in Golang and is open source.&lt;/P&gt;&lt;P&gt;Keep in mind that this tool was developed for our use case, maybe you need to tinker around a bit regarding interfaces names. For example, you may need to replace "bond" with "eth"&lt;/P&gt;&lt;P&gt;Feel free to fork it if you need.&lt;/P&gt;&lt;P&gt;Download: &lt;A href="https://github.com/MoltenMinds/ASAtoVSXParser/releases" target="_self"&gt;ASAtoVSX Parser - Molten Minds Github&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF99CC"&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Current features (Tested with ASA&lt;/FONT&gt; &lt;FONT size="5"&gt;Version 9.4(4)5 and Check Point R80.30)&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Translates interfaces to vsx_provisioning_tool language&lt;/LI&gt;&lt;LI&gt;Translates static routes to vsx_provisioning_tool language&lt;/LI&gt;&lt;LI&gt;Marks with # when an interface is down&lt;/LI&gt;&lt;LI&gt;Generates a vsx_provisioning_tool output with interfaces and static routes&lt;/LI&gt;&lt;LI&gt;Generates a JSON file containing all the interfaces&lt;/LI&gt;&lt;LI&gt;Generates a JSON file containing all the routes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Translation examples&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="9.975369458128078%" height="25px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="40.02463054187193%" height="25px"&gt;ASA&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;Check Point (vsx_provisioning_tool)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="9.975369458128078%" height="145px"&gt;Interface&lt;/TD&gt;&lt;TD width="40.02463054187193%" height="145px"&gt;interface Port-channelY.XX&lt;BR /&gt;description ***&lt;BR /&gt;nameif IFNAME&lt;BR /&gt;security-level 30&lt;BR /&gt;ip address 172.**.**.** 255.255.128.0&lt;BR /&gt;!&lt;/TD&gt;&lt;TD width="50%" height="145px"&gt;add interface name bondY.XX ip 172.**.**.** netmask 255.255.128.0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="179px"&gt;Interface (Shutdown)&lt;/TD&gt;&lt;TD height="179px"&gt;Caso interfaz down&lt;BR /&gt;interface Port-channelY.XX&lt;BR /&gt;description IFNAME&lt;BR /&gt;shutdown&lt;BR /&gt;nameif IFNAME&lt;BR /&gt;security-level 30&lt;BR /&gt;ip address 10.**.**.** 255.255.255.248&lt;BR /&gt;!&lt;/TD&gt;&lt;TD height="179px"&gt;#add interface name bondY.XX ip 10.**.**.** netmask 255.255.255.248&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="47px"&gt;Static route&lt;/TD&gt;&lt;TD height="47px"&gt;route IFNAME 10.**.**.** 255.255.255.255 10.**.**.** 1&lt;/TD&gt;&lt;TD height="47px"&gt;add route destination 10.**.**.** netmask 255.255.255.255 next_hop 10.**.**.**&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="25px"&gt;Default route&lt;/TD&gt;&lt;TD height="25px"&gt;route OUTSIDE 0.0.0.0 0.0.0.0 181.**.**.** 1&lt;/TD&gt;&lt;TD height="25px"&gt;add route destination default next_hop 186.**.**.**&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF00FF"&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Usage&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Usage is really simple.&lt;/P&gt;&lt;P&gt;1) Download the executable file from Github or compile the code yourself&lt;/P&gt;&lt;P&gt;2) Extract running config and save it as a text file with &lt;STRONG&gt;UTF-8 format&lt;/STRONG&gt; . At the moment the tool only allow inputs in this format.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser1.png" style="width: 123px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4070iB7006ACCAFC483F7/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser1.png" alt="parser1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;3) Using PowerShell execute the program command with the desired input file.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser2.png" style="width: 505px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4071iF619FBA4B7E09422/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser2.png" alt="parser2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;4) Check the output files&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser3.png" style="width: 270px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4072iD9B9F72CF627A577/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser3.png" alt="parser3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;vsx_provisioning_tool sample output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser4.png" style="width: 740px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4073i3E903E5F74A14194/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser4.png" alt="parser4.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Interfaces JSON output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser5.png" style="width: 379px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4074iF5FB25DBA3364C7D/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser5.png" alt="parser5.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Routes JSON output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser6.png" style="width: 430px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4075i14574159CE955379/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser6.png" alt="parser6.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;5) Add the desired header on the VSX output for vsx_provisioning_tool to create de VS. Example: &lt;EM&gt;add vd name VS-Name &lt;SPAN class="markqiq64qm19"&gt;vsx&lt;/SPAN&gt; &lt;SPAN class="markqiq64qm19"&gt;VSX&lt;/SPAN&gt;-FW instances 1 main_ip 172.1.2.3&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;6) Put the script in the management server that manages the involved VSX and use vsx_provisioning_tool to execute it&lt;/P&gt;&lt;P&gt;7) Verify the new VS and push policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;L&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;ab&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Sample VSX Lab prior script&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Example1.png" style="width: 774px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4076i559AA6B8BB9C3F3A/image-size/large?v=v2&amp;amp;px=999" role="button" title="Example1.png" alt="Example1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;After we move the generated script to the management server we execute it.&lt;/P&gt;&lt;P&gt;If any of the commands fail then the transaction will be canceled and reversed.&lt;/P&gt;&lt;P&gt;User and passwords are for demonstration purposes only &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="example2.png" style="width: 789px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4077i86CF75C6DE128E3E/image-size/large?v=v2&amp;amp;px=999" role="button" title="example2.png" alt="example2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Now check your VS and push policy&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="example3.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4078iEC85B41C9F971881/image-size/large?v=v2&amp;amp;px=999" role="button" title="example3.png" alt="example3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2020 13:04:15 GMT</pubDate>
    <dc:creator>FedericoMeiners</dc:creator>
    <dc:date>2020-01-22T13:04:15Z</dc:date>
    <item>
      <title>ASAtoVSX - Translate your Cisco running config to VSX and more!</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72909#M4316</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I wanted to share with you a tool that we developed to help us automate a big part of a project.&lt;/P&gt;&lt;P&gt;Long story short, we needed to migrate many virtual context from ASA to VSX. As you may know adding static routes and interfaces to a VS can be cumbersome. Especially if you have firewalls with +100 interfaces and +300 routes &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The tool was developed in Golang and is open source.&lt;/P&gt;&lt;P&gt;Keep in mind that this tool was developed for our use case, maybe you need to tinker around a bit regarding interfaces names. For example, you may need to replace "bond" with "eth"&lt;/P&gt;&lt;P&gt;Feel free to fork it if you need.&lt;/P&gt;&lt;P&gt;Download: &lt;A href="https://github.com/MoltenMinds/ASAtoVSXParser/releases" target="_self"&gt;ASAtoVSX Parser - Molten Minds Github&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF99CC"&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Current features (Tested with ASA&lt;/FONT&gt; &lt;FONT size="5"&gt;Version 9.4(4)5 and Check Point R80.30)&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Translates interfaces to vsx_provisioning_tool language&lt;/LI&gt;&lt;LI&gt;Translates static routes to vsx_provisioning_tool language&lt;/LI&gt;&lt;LI&gt;Marks with # when an interface is down&lt;/LI&gt;&lt;LI&gt;Generates a vsx_provisioning_tool output with interfaces and static routes&lt;/LI&gt;&lt;LI&gt;Generates a JSON file containing all the interfaces&lt;/LI&gt;&lt;LI&gt;Generates a JSON file containing all the routes&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Translation examples&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="9.975369458128078%" height="25px"&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD width="40.02463054187193%" height="25px"&gt;ASA&lt;/TD&gt;&lt;TD width="50%" height="25px"&gt;Check Point (vsx_provisioning_tool)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD width="9.975369458128078%" height="145px"&gt;Interface&lt;/TD&gt;&lt;TD width="40.02463054187193%" height="145px"&gt;interface Port-channelY.XX&lt;BR /&gt;description ***&lt;BR /&gt;nameif IFNAME&lt;BR /&gt;security-level 30&lt;BR /&gt;ip address 172.**.**.** 255.255.128.0&lt;BR /&gt;!&lt;/TD&gt;&lt;TD width="50%" height="145px"&gt;add interface name bondY.XX ip 172.**.**.** netmask 255.255.128.0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="179px"&gt;Interface (Shutdown)&lt;/TD&gt;&lt;TD height="179px"&gt;Caso interfaz down&lt;BR /&gt;interface Port-channelY.XX&lt;BR /&gt;description IFNAME&lt;BR /&gt;shutdown&lt;BR /&gt;nameif IFNAME&lt;BR /&gt;security-level 30&lt;BR /&gt;ip address 10.**.**.** 255.255.255.248&lt;BR /&gt;!&lt;/TD&gt;&lt;TD height="179px"&gt;#add interface name bondY.XX ip 10.**.**.** netmask 255.255.255.248&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="47px"&gt;Static route&lt;/TD&gt;&lt;TD height="47px"&gt;route IFNAME 10.**.**.** 255.255.255.255 10.**.**.** 1&lt;/TD&gt;&lt;TD height="47px"&gt;add route destination 10.**.**.** netmask 255.255.255.255 next_hop 10.**.**.**&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="25px"&gt;Default route&lt;/TD&gt;&lt;TD height="25px"&gt;route OUTSIDE 0.0.0.0 0.0.0.0 181.**.**.** 1&lt;/TD&gt;&lt;TD height="25px"&gt;add route destination default next_hop 186.**.**.**&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT color="#FF00FF"&gt;&lt;STRONG&gt;&lt;FONT size="5"&gt;Usage&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;Usage is really simple.&lt;/P&gt;&lt;P&gt;1) Download the executable file from Github or compile the code yourself&lt;/P&gt;&lt;P&gt;2) Extract running config and save it as a text file with &lt;STRONG&gt;UTF-8 format&lt;/STRONG&gt; . At the moment the tool only allow inputs in this format.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser1.png" style="width: 123px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4070iB7006ACCAFC483F7/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser1.png" alt="parser1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;3) Using PowerShell execute the program command with the desired input file.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser2.png" style="width: 505px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4071iF619FBA4B7E09422/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser2.png" alt="parser2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;4) Check the output files&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser3.png" style="width: 270px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4072iD9B9F72CF627A577/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser3.png" alt="parser3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;vsx_provisioning_tool sample output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser4.png" style="width: 740px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4073i3E903E5F74A14194/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser4.png" alt="parser4.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Interfaces JSON output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser5.png" style="width: 379px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4074iF5FB25DBA3364C7D/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser5.png" alt="parser5.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Routes JSON output&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="parser6.png" style="width: 430px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4075i14574159CE955379/image-size/large?v=v2&amp;amp;px=999" role="button" title="parser6.png" alt="parser6.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;5) Add the desired header on the VSX output for vsx_provisioning_tool to create de VS. Example: &lt;EM&gt;add vd name VS-Name &lt;SPAN class="markqiq64qm19"&gt;vsx&lt;/SPAN&gt; &lt;SPAN class="markqiq64qm19"&gt;VSX&lt;/SPAN&gt;-FW instances 1 main_ip 172.1.2.3&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;6) Put the script in the management server that manages the involved VSX and use vsx_provisioning_tool to execute it&lt;/P&gt;&lt;P&gt;7) Verify the new VS and push policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;L&lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT size="5"&gt;&lt;STRONG&gt;ab&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Sample VSX Lab prior script&lt;BR /&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Example1.png" style="width: 774px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4076i559AA6B8BB9C3F3A/image-size/large?v=v2&amp;amp;px=999" role="button" title="Example1.png" alt="Example1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;After we move the generated script to the management server we execute it.&lt;/P&gt;&lt;P&gt;If any of the commands fail then the transaction will be canceled and reversed.&lt;/P&gt;&lt;P&gt;User and passwords are for demonstration purposes only &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="example2.png" style="width: 789px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4077i86CF75C6DE128E3E/image-size/large?v=v2&amp;amp;px=999" role="button" title="example2.png" alt="example2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Now check your VS and push policy&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="example3.png" style="width: 999px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/4078iEC85B41C9F971881/image-size/large?v=v2&amp;amp;px=999" role="button" title="example3.png" alt="example3.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 13:04:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72909#M4316</guid>
      <dc:creator>FedericoMeiners</dc:creator>
      <dc:date>2020-01-22T13:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: ASAtoVSX - Translate your Cisco running config to vsx_util and more!</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72921#M4317</link>
      <description>Well done!</description>
      <pubDate>Tue, 21 Jan 2020 22:00:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72921#M4317</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-01-21T22:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASAtoVSX - Translate your Cisco running config to VSX and more!</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72970#M4318</link>
      <description>&lt;P&gt;This post requires a correction. You are using vsx_profisioning_tool and not vsx_util. These are two different tools, and the latter is for maitenance of VSX clusters and not for provisioning.&lt;BR /&gt;&lt;BR /&gt;Please change the text of the post to reflect this.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 10:45:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72970#M4318</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2020-01-22T10:45:32Z</dc:date>
    </item>
    <item>
      <title>Re: ASAtoVSX - Translate your Cisco running config to VSX and more!</title>
      <link>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72995#M4319</link>
      <description>&lt;P&gt;I've made the corrections, thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 13:05:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/API-CLI-Discussion/ASAtoVSX-Translate-your-Cisco-running-config-to-VSX-and-more/m-p/72995#M4319</guid>
      <dc:creator>FedericoMeiners</dc:creator>
      <dc:date>2020-01-22T13:05:19Z</dc:date>
    </item>
  </channel>
</rss>

