<?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 Re: flexconfig deployment issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3902819#M926929</link>
    <description>&lt;P&gt;I have the same exact problem too, did anyone else gets to resolve this officially Instead of a workaround of re-deploying the same pbr flexconfig every single time, an ACL change is made?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 05 Aug 2019 03:37:36 GMT</pubDate>
    <dc:creator>J_Vansen_S</dc:creator>
    <dc:date>2019-08-05T03:37:36Z</dc:date>
    <item>
      <title>flexconfig deployment issue</title>
      <link>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3210134#M926927</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello Experts,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I have 2 x FTD2110 configured in HA and they managed by FMCv. Both FMC and FTD are running on code 6.2.2.&lt;/P&gt;
&lt;P&gt;I have configured a PBR with 'match list' and a 'set next-hop' command&amp;nbsp;and was able push the flexconfig to FTD successfully and PBR was working fine. later, i have made some other modifications to the config such as ACL, etc and push the new config to the FTD. Once the config deployment is completed, I have noticed the "Set next-hop' command has been removed from the FTD interface configuration. During the config deployment, I have&amp;nbsp; made sure that "flexconfig" has green tick next to it for the config deployment. Hence, no command from flexconfig should have been deployed. The flexconfig is set to "once" and "Append". Anyone has experienced the same issue?&lt;/P&gt;
&lt;P&gt;The work around I have is to push the flex config again&amp;nbsp;to push "Set interface"&amp;nbsp;command.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Nimalraj&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:37:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3210134#M926927</guid>
      <dc:creator>nimalrajphilips</dc:creator>
      <dc:date>2020-02-21T14:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: flexconfig deployment issue</title>
      <link>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3742202#M926928</link>
      <description>Hi! I found a workaroud that seem to do the trick. Made a FlexConfig just with the route-map and next-hop statement and run this every time.</description>
      <pubDate>Thu, 08 Nov 2018 15:58:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3742202#M926928</guid>
      <dc:creator>kwalderhaug</dc:creator>
      <dc:date>2018-11-08T15:58:54Z</dc:date>
    </item>
    <item>
      <title>Re: flexconfig deployment issue</title>
      <link>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3902819#M926929</link>
      <description>&lt;P&gt;I have the same exact problem too, did anyone else gets to resolve this officially Instead of a workaround of re-deploying the same pbr flexconfig every single time, an ACL change is made?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2019 03:37:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/flexconfig-deployment-issue/m-p/3902819#M926929</guid>
      <dc:creator>J_Vansen_S</dc:creator>
      <dc:date>2019-08-05T03:37:36Z</dc:date>
    </item>
  </channel>
</rss>

