<?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 PA-220 Login issue in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-220-login-issue/m-p/1260315#M7043</link>
    <description>&lt;P&gt;Hi Everyone&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a load of PA-220's in HA at variuos different sites, after a set period of time the devices stop allowing use to login.&amp;nbsp; Does not matter what method of Auth we try, it just does not work.&amp;nbsp; To compond the problem, if we do not resolve this issue eariler enough both devices at the site go offline taking the whole site down.&amp;nbsp; The issue started around 18 months to 2 years ago.&amp;nbsp; When we first had the issue we opened several support case with Palo Alto and ended up breaking several devices.&amp;nbsp; Those devices then had to be replaced by Palo Alto.&amp;nbsp; Eventually with Palo Alto support we found a workaround.&amp;nbsp; Here are the steps to get the firewalls back online.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Connect with console cable to backup firewall&lt;/P&gt;
&lt;P&gt;2. Power cycle the device&lt;/P&gt;
&lt;P&gt;3. Go into Maintenance Mode&lt;/P&gt;
&lt;P&gt;4. Re-install PANOS.&lt;/P&gt;
&lt;P&gt;5. Reboot&lt;/P&gt;
&lt;P&gt;6. Once the device is back online and the site is reachable again perform the same steps on the primary firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, we do have a workaround but that requires someone to be on site with a laptop that can give us access to the devices, which is not always an easy task.&amp;nbsp; All the PA-220's are located in off site data centers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've only been working with Palo Alto devices for about 2.5 years, but my hunch is that 12 of the drives is filling up and causing the problem.&amp;nbsp; The issue is once we do the reinstall you can see what was the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of our other senior engineers had reported that he had seen on a PA forum they issue could be linked to a memory issue and restarting a process on both PA's before pushing a configuration update out to the devices from Pnaorama.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone suggests anything that we can monitor on the devices like memory or storage to see if the issues are related to either memory or storage?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 29 Jul 2026 11:03:51 GMT</pubDate>
    <dc:creator>R.Moth</dc:creator>
    <dc:date>2026-07-29T11:03:51Z</dc:date>
    <item>
      <title>PA-220 Login issue</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-220-login-issue/m-p/1260315#M7043</link>
      <description>&lt;P&gt;Hi Everyone&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a load of PA-220's in HA at variuos different sites, after a set period of time the devices stop allowing use to login.&amp;nbsp; Does not matter what method of Auth we try, it just does not work.&amp;nbsp; To compond the problem, if we do not resolve this issue eariler enough both devices at the site go offline taking the whole site down.&amp;nbsp; The issue started around 18 months to 2 years ago.&amp;nbsp; When we first had the issue we opened several support case with Palo Alto and ended up breaking several devices.&amp;nbsp; Those devices then had to be replaced by Palo Alto.&amp;nbsp; Eventually with Palo Alto support we found a workaround.&amp;nbsp; Here are the steps to get the firewalls back online.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Connect with console cable to backup firewall&lt;/P&gt;
&lt;P&gt;2. Power cycle the device&lt;/P&gt;
&lt;P&gt;3. Go into Maintenance Mode&lt;/P&gt;
&lt;P&gt;4. Re-install PANOS.&lt;/P&gt;
&lt;P&gt;5. Reboot&lt;/P&gt;
&lt;P&gt;6. Once the device is back online and the site is reachable again perform the same steps on the primary firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, we do have a workaround but that requires someone to be on site with a laptop that can give us access to the devices, which is not always an easy task.&amp;nbsp; All the PA-220's are located in off site data centers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I've only been working with Palo Alto devices for about 2.5 years, but my hunch is that 12 of the drives is filling up and causing the problem.&amp;nbsp; The issue is once we do the reinstall you can see what was the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One of our other senior engineers had reported that he had seen on a PA forum they issue could be linked to a memory issue and restarting a process on both PA's before pushing a configuration update out to the devices from Pnaorama.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone suggests anything that we can monitor on the devices like memory or storage to see if the issues are related to either memory or storage?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Richard&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jul 2026 11:03:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/pa-220-login-issue/m-p/1260315#M7043</guid>
      <dc:creator>R.Moth</dc:creator>
      <dc:date>2026-07-29T11:03:51Z</dc:date>
    </item>
  </channel>
</rss>

