<?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: Monitor Traffic Shows Sess Still Active over Tunnel Even After Int Fail in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/monitor-traffic-shows-sess-still-active-over-tunnel-even-after/m-p/346802#M86550</link>
    <description>&lt;P&gt;I feel confident a coworker has figured out what we were seeing: We have the rules set to log on session-end. We were most likely seeing the log entry (over the dead link) of the session summary as it timed-out (30 minute timer I believe we have for SSL) and therefore creating the log entry. Makes sense.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Sep 2020 22:12:53 GMT</pubDate>
    <dc:creator>michaelmertens</dc:creator>
    <dc:date>2020-09-03T22:12:53Z</dc:date>
    <item>
      <title>Monitor Traffic Shows Sess Still Active over Tunnel Even After Int Failed</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/monitor-traffic-shows-sess-still-active-over-tunnel-even-after/m-p/346529#M86523</link>
      <description>&lt;P&gt;We're provisioning and testing a dedicate wave circuit and an Internet-IPSEC backup between two PANs. (We are also running IPSEC over the wave circuit). We noticed a phenomena of sorts and was wondering if anyone has experienced this: We purposely failed the upstream PAN's WAVE circuit's ethernet interface to test failover to the internet-IPSEC. The wave-IPSEC tunnel went red for IKE and Tunnel Info on both head-end and remote-office. The odd thing was that we had a PAN Traffic Monitor going on the head and watching session traffic going over the wave-IPSEC; when the traffic was failed over to internet-IPSEC we still saw session traffic with new time stamps over the downed wave-IPSEC tunnel interface...We KNOW that circuit was down, unavailable and even the PAN knew it from the tunnel status. We are running OS 9.0.9.&lt;BR /&gt;&lt;BR /&gt;Does anyone have any guesses, thoughts, etc?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks!!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2020 23:40:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/monitor-traffic-shows-sess-still-active-over-tunnel-even-after/m-p/346529#M86523</guid>
      <dc:creator>michaelmertens</dc:creator>
      <dc:date>2020-09-02T23:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Traffic Shows Sess Still Active over Tunnel Even After Int Fail</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/monitor-traffic-shows-sess-still-active-over-tunnel-even-after/m-p/346802#M86550</link>
      <description>&lt;P&gt;I feel confident a coworker has figured out what we were seeing: We have the rules set to log on session-end. We were most likely seeing the log entry (over the dead link) of the session summary as it timed-out (30 minute timer I believe we have for SSL) and therefore creating the log entry. Makes sense.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Sep 2020 22:12:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/monitor-traffic-shows-sess-still-active-over-tunnel-even-after/m-p/346802#M86550</guid>
      <dc:creator>michaelmertens</dc:creator>
      <dc:date>2020-09-03T22:12:53Z</dc:date>
    </item>
  </channel>
</rss>

