<?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: Requirement to shutdown FTD inside interface via SLA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839713#M1100611</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our issue is that we cannot use static route as we are already running ospf in the FTD, and we need to remove some subnets from getting advertised to ospf when the upstream internet link goes down.&lt;/P&gt;</description>
    <pubDate>Sun, 21 May 2023 12:20:45 GMT</pubDate>
    <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
    <dc:date>2023-05-21T12:20:45Z</dc:date>
    <item>
      <title>Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839544#M1100594</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;We have a requirement to shutdown the inside interface of our FTD once the internet link on the upstream ISP router goes down. The logical connectivity is as follows.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Core Switch&lt;/STRONG&gt;----&amp;gt;&lt;FONT color="#FF0000"&gt;(inside)&lt;/FONT&gt;&lt;STRONG&gt;FTD&lt;/STRONG&gt;&lt;FONT color="#FF0000"&gt;(outside)&lt;/FONT&gt;-----&amp;gt;&lt;FONT color="#FF0000"&gt;(inside)&lt;/FONT&gt;&lt;STRONG&gt;ISP Router&lt;/STRONG&gt;&lt;FONT color="#FF0000"&gt;(outside)&lt;/FONT&gt;-----&amp;gt;&lt;STRONG&gt;Internet&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Initially I planning to use an sla monitor (ping to 8.8.8.8)and use it in an EEM script to shutdown the interface. But I found that FTD/ASA does not support event track command. Please advise if there is any other way to achieve my requirement.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2023 18:00:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839544#M1100594</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-20T18:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839546#M1100595</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/316042"&gt;@SHABEEB KUNHIPOCKER&lt;/a&gt; you can use the ASA EEM syntax with FlexConfig on the FTD.&lt;/P&gt;
&lt;P&gt;What is your scenario to shutdown the FTD interface?...there might be a more elegant solution.&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2023 18:07:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839546#M1100595</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-05-20T18:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839549#M1100596</link>
      <description>&lt;P&gt;From first view you can use flexconfig to config eem in ftd.&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2023 18:07:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839549#M1100596</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-20T18:07:48Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839551#M1100597</link>
      <description>&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-management/cisco-ftd-6-7-0-1-eem-quot-event-track-quot/td-p/4401894" target="_blank"&gt;https://community.cisco.com/t5/network-management/cisco-ftd-6-7-0-1-eem-quot-event-track-quot/td-p/4401894&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Check this link&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2023 18:10:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839551#M1100597</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-20T18:10:32Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839617#M1100601</link>
      <description>&lt;P&gt;Hi Rob,&lt;/P&gt;
&lt;P&gt;The issue that the FTD is running ospf with core switch. The FTD has DMZ interface where they have an ESA. The customer has two data centers and when we do failover to the DC2, we need these DC1 DMZ routes to be removed from the routing table. My plan was to track an internet IP and shutdown the inside interface of FTD so that the ospf will be down from FTD to core and the DMZ route will be removed from the downstream devices.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 04:36:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839617#M1100601</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-21T04:36:44Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839618#M1100602</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I have seen this link. But as stated there is no option to configure event track. In my case I need to monitor an internet IP and when it is unreachable I need to run EEM. So I don’t think I can use the solution in the link.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 04:38:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839618#M1100602</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-21T04:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839667#M1100605</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/316042"&gt;@SHABEEB KUNHIPOCKER&lt;/a&gt; event track is not supported on ASA and FTD. I just had a thought why dont you use the syslog ID "&lt;SPAN&gt;718063&amp;nbsp;&amp;nbsp;&amp;nbsp; Error Message %ASA-5-718063: Interface interface_name is down&lt;/SPAN&gt;" and "&lt;SPAN&gt;718064&lt;/SPAN&gt;&amp;nbsp; &lt;SPAN&gt;Error Message&lt;/SPAN&gt; &lt;SPAN&gt;%ASA-5-718064: Admin. interface&lt;/SPAN&gt; &lt;SPAN&gt;interface_name&lt;/SPAN&gt; &lt;SPAN&gt;is down&lt;/SPAN&gt;". as &lt;STRONG&gt;syslog &lt;/STRONG&gt;are supported on EEM applet&lt;/P&gt;
&lt;P&gt;on based of these log ID you can create the EEM applet and run it.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 09:37:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839667#M1100605</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-21T09:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839668#M1100606</link>
      <description>&lt;P&gt;Yes you correct&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even track not support'&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can use syslog' but syslog for what&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here the Q&lt;/P&gt;
&lt;P&gt;The answer you can use static route with track and use syslog for add remove this route to rib and config eem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 09:51:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839668#M1100606</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-21T09:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839670#M1100607</link>
      <description>&lt;P&gt;syslog can be use against the &lt;STRONG&gt;"name if"&lt;/STRONG&gt; here is the log id and description " "&lt;STRONG&gt;718063&lt;/STRONG&gt; Error Message %ASA-5-&lt;STRONG&gt;718063: Interface interface_name is down&lt;/STRONG&gt;"&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 09:59:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839670#M1100607</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-21T09:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839671#M1100608</link>
      <description>&lt;P&gt;He use IP SLA because the FTD side not down when ISP interface down'&lt;/P&gt;
&lt;P&gt;So we will use static route only for eem and detect it add remove.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 10:03:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839671#M1100608</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-21T10:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839676#M1100609</link>
      <description>&lt;P&gt;In that case there are the syslog id need to be configured.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;609001 &lt;BR /&gt;302020&lt;BR /&gt;302021&lt;BR /&gt;609002&lt;BR /&gt;622001&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I get these syslog id from &lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/118962-configure-asa-00.html" target="_self"&gt;Cisco Document&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="syslog.PNG" style="width: 904px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/185149iE6D419162A01C624/image-size/large?v=v2&amp;amp;px=999" role="button" title="syslog.PNG" alt="syslog.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/syslog/b_syslog.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/syslog/b_syslog.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 10:17:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839676#M1100609</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-21T10:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839686#M1100610</link>
      <description>&lt;P&gt;I am far from my PC I already run lab using this syslog, hope share this lab tonight&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 10:33:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839686#M1100610</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-21T10:33:49Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839713#M1100611</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Our issue is that we cannot use static route as we are already running ospf in the FTD, and we need to remove some subnets from getting advertised to ospf when the upstream internet link goes down.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 12:20:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839713#M1100611</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-21T12:20:45Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839740#M1100613</link>
      <description>&lt;P&gt;you detect the 8.8.8.8 use static route to 8.8.4.4, we talk here about any static route not specific one&amp;nbsp;&lt;BR /&gt;route OUT 8.8.4.4 255.255.255.255 &amp;lt;ISP&amp;gt; track x&amp;nbsp;&lt;BR /&gt;then use EEM and shut down or remove net under OSPF&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 13:46:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839740#M1100613</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-21T13:46:02Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839785#M1100617</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/316042"&gt;@SHABEEB KUNHIPOCKER&lt;/a&gt; you can configure the Interface syslog id as mentioned in my earlier post and run the EEM applet aganist it. If this is production network which I assume it is. There is a less chance of false positive as you or some one else from network team will shutting the any interface of the firewall. so syslog id 718063 and 718064 is your best bet. unless otherwise, you get the syslog id of the ospf adjacency syslog id and run against the EEM applet.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am afraid you only have these options with EEM applet.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 16:38:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839785#M1100617</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-21T16:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839824#M1100618</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I tried it in my lab with syslog id 622001 in the em script. But unfortunately it did not work. Do I need to enable console logging in the FTD for this to work?.&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 18:57:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839824#M1100618</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-21T18:57:20Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839826#M1100619</link>
      <description>&lt;P&gt;Did you config log level for this message?&lt;/P&gt;
&lt;P&gt;If you want push the log message to other log level if you want&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 19:02:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839826#M1100619</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-05-21T19:02:26Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839837#M1100620</link>
      <description>&lt;P&gt;First of all please rate the post as we are taking our personal time and helping you here. secnond share your em script.&lt;/P&gt;
&lt;P&gt;Third. I have give a sample test it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;event manager applet Auto_Action
 description "ShutDown Interfaces"
 event syslog id 622001
 action 1 cli command "enable"
 action 2 cli command "config t"
 action 3 cli command "interface Ethernet1/1"
 action 4 cli command "shutdown"
 output none
&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 May 2023 19:52:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4839837#M1100620</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-21T19:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4840039#M1100636</link>
      <description>&lt;P&gt;Hello Sheraz/MHM,&lt;/P&gt;
&lt;P&gt;I managed to shut the interface down with the syslog ID 622001. The issue was with logging and I created an event list in the platform settings and deployed it in FTD. But now the issue is that the interface will go down once the tracker is down. But when the internet link comes back up it is not enabled automatically. I believe I need to write another script to bring it up, but I am wondering what would be the parameter I should use in that script as the syslog ID 622001 is for both removal and addition of the tracked route.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SHABEEBKUNHIPOCKER_0-1684740013752.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/185220i74E5410579EEF83F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SHABEEBKUNHIPOCKER_0-1684740013752.png" alt="SHABEEBKUNHIPOCKER_0-1684740013752.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The script I am running is shown below&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;event&amp;nbsp;manager&amp;nbsp;applet&amp;nbsp;Internet-Down&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;description&amp;nbsp;Wan&amp;nbsp;Disconnected&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;event&amp;nbsp;syslog&amp;nbsp;id&amp;nbsp;622001&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;action&amp;nbsp;1&amp;nbsp;cli&amp;nbsp;command&amp;nbsp;"en"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;action&amp;nbsp;2&amp;nbsp;cli&amp;nbsp;command&amp;nbsp;"config&amp;nbsp;t"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;action&amp;nbsp;3&amp;nbsp;cli&amp;nbsp;command&amp;nbsp;"interface&amp;nbsp;GigabitEthernet0/1"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;action&amp;nbsp;4&amp;nbsp;cli&amp;nbsp;command&amp;nbsp;"shutdown"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;action&amp;nbsp;5&amp;nbsp;cli&amp;nbsp;command&amp;nbsp;"wr&amp;nbsp;mem"&lt;/EM&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT color="#3366FF"&gt;&lt;EM&gt;&amp;nbsp;output&amp;nbsp;none&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 07:27:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4840039#M1100636</guid>
      <dc:creator>SHABEEB KUNHIPOCKER</dc:creator>
      <dc:date>2023-05-22T07:27:51Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement to shutdown FTD inside interface via SLA</title>
      <link>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4840068#M1100640</link>
      <description>&lt;P&gt;your understand is correct. you can use this sys ID 622001 again and put the interface/s as no shut. as according to the documentation log ID 622001 is for removal and same ID for adding it back.&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 08:30:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/requirement-to-shutdown-ftd-inside-interface-via-sla/m-p/4840068#M1100640</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2023-05-22T08:30:25Z</dc:date>
    </item>
  </channel>
</rss>

