<?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: How we can Scheule TCP connect in ciscoASA IOS 9.* Version in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-we-can-scheule-tcp-connect-in-ciscoasa-ios-9-version/m-p/5273755#M1120202</link>
    <description>&lt;P&gt;For TCP scheduling on Cisco ASA with IOS 9.*, you can't utilize IP SLA or IP MONITOR because they are not supported on ASA appliances, but a decent workaround is to route the traffic to a router that is connected and supports these commands to generate periodic TCP packets. Another alternative is to activate TCP Keepalive on the ASA to keep it open, or utilize a customized script on a separate appliance to generate TCP packets on a periodic interval. Third-party monitoring tools like SolarWinds or PRTG can also be used to generate simulated traffic and keep the tunnel open.-zone traffic with a zone-pair configuration in the Zone-Based Firewall (ZBF). As a workaround, you can use internal DNS to resolve fish.example.com to 10.0.0.107 so that local clients do not require hairpin NAT, or you can use a NAT loopback configuration if your platform supports it. Also, verify and update your ZBF rules to permit intra-zone traffic explicitly.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Mar 2025 04:23:59 GMT</pubDate>
    <dc:creator>sdroy</dc:creator>
    <dc:date>2025-03-21T04:23:59Z</dc:date>
    <item>
      <title>How we can Scheule TCP connect in ciscoASA IOS 9.* Version</title>
      <link>https://community.cisco.com/t5/network-security/how-we-can-scheule-tcp-connect-in-ciscoasa-ios-9-version/m-p/5273686#M1120200</link>
      <description>&lt;P&gt;Hi ALL,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;IP SLA,IP MONITOR these commands are not working in asa firewall,is there any alternate to schedule tcp traffic to bring tunnel up. or else can we&amp;nbsp;send traffic from router through asa firewall to destination to bring tunnel up is this works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 04:21:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-we-can-scheule-tcp-connect-in-ciscoasa-ios-9-version/m-p/5273686#M1120200</guid>
      <dc:creator>srikanth-setty</dc:creator>
      <dc:date>2025-03-21T04:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: How we can Scheule TCP connect in ciscoASA IOS 9.* Version</title>
      <link>https://community.cisco.com/t5/network-security/how-we-can-scheule-tcp-connect-in-ciscoasa-ios-9-version/m-p/5273755#M1120202</link>
      <description>&lt;P&gt;For TCP scheduling on Cisco ASA with IOS 9.*, you can't utilize IP SLA or IP MONITOR because they are not supported on ASA appliances, but a decent workaround is to route the traffic to a router that is connected and supports these commands to generate periodic TCP packets. Another alternative is to activate TCP Keepalive on the ASA to keep it open, or utilize a customized script on a separate appliance to generate TCP packets on a periodic interval. Third-party monitoring tools like SolarWinds or PRTG can also be used to generate simulated traffic and keep the tunnel open.-zone traffic with a zone-pair configuration in the Zone-Based Firewall (ZBF). As a workaround, you can use internal DNS to resolve fish.example.com to 10.0.0.107 so that local clients do not require hairpin NAT, or you can use a NAT loopback configuration if your platform supports it. Also, verify and update your ZBF rules to permit intra-zone traffic explicitly.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 04:23:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-we-can-scheule-tcp-connect-in-ciscoasa-ios-9-version/m-p/5273755#M1120202</guid>
      <dc:creator>sdroy</dc:creator>
      <dc:date>2025-03-21T04:23:59Z</dc:date>
    </item>
  </channel>
</rss>

