<?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 No IPSec-Tunnels after Upgrade from 3.1.7 to 4.01 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/no-ipsec-tunnels-after-upgrade-from-3-1-7-to-4-01/m-p/42901#M31492</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we run 8 PA-500s in 8 Branches. After upgrading them from 3.1.7 to 4.0.1 not all IPSec-Tunnels become active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Tunnels to the branches with the WAN-Interface connected to SDSL with PPPoE (automatic IP/Netmask/Gateway) stayed inactive, even after more than 12h.The WAN-Interface itself was online, pings to a external addresses were answered.&lt;/P&gt;&lt;P&gt;The IPSec-Tunnels to branches with WAN-Interfaces not connected with PPPoE were active immediately after rebooting the new software version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a known bug when upgrading IPSec-Tunnels with PPPoE-WAN-Interfaces from 3.1.7 to 4.0.1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Apr 2011 08:37:03 GMT</pubDate>
    <dc:creator>gratzadmin</dc:creator>
    <dc:date>2011-04-04T08:37:03Z</dc:date>
    <item>
      <title>No IPSec-Tunnels after Upgrade from 3.1.7 to 4.01</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-ipsec-tunnels-after-upgrade-from-3-1-7-to-4-01/m-p/42901#M31492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we run 8 PA-500s in 8 Branches. After upgrading them from 3.1.7 to 4.0.1 not all IPSec-Tunnels become active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Tunnels to the branches with the WAN-Interface connected to SDSL with PPPoE (automatic IP/Netmask/Gateway) stayed inactive, even after more than 12h.The WAN-Interface itself was online, pings to a external addresses were answered.&lt;/P&gt;&lt;P&gt;The IPSec-Tunnels to branches with WAN-Interfaces not connected with PPPoE were active immediately after rebooting the new software version.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a known bug when upgrading IPSec-Tunnels with PPPoE-WAN-Interfaces from 3.1.7 to 4.0.1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Apr 2011 08:37:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-ipsec-tunnels-after-upgrade-from-3-1-7-to-4-01/m-p/42901#M31492</guid>
      <dc:creator>gratzadmin</dc:creator>
      <dc:date>2011-04-04T08:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: No IPSec-Tunnels after Upgrade from 3.1.7 to 4.01</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/no-ipsec-tunnels-after-upgrade-from-3-1-7-to-4-01/m-p/42902#M31493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello again,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the problem was that updating the software from 3.1.7 to 4.0.1 and the necessary reboot/autocommit produced a duplicate line 'ssl-decrypt' in the running (before and after) configuration. After loading the same configuration after the update from the saved file the error was fixed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Apr 2011 05:19:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/no-ipsec-tunnels-after-upgrade-from-3-1-7-to-4-01/m-p/42902#M31493</guid>
      <dc:creator>gratzadmin</dc:creator>
      <dc:date>2011-04-06T05:19:37Z</dc:date>
    </item>
  </channel>
</rss>

