<?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 Firewall VM series | interface suddenly goes down in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/548855#M112031</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a PA VM firewall where all working well but firewall interface (eth1/1 and eth1/2) went down suddenly&lt;/P&gt;
&lt;P&gt;No issue with the management interface so we are still able to access the firewall during the incident time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;to brings the interface up, we do reboot on firewall and thus fix the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the system log, we can see "link change" but customers stated that no healthy event was found from Azure.&amp;nbsp; (see attachment)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Firmware: 10.1.9-h1&amp;nbsp; - check for known issue but not sure related with&amp;nbsp;PAN-115816&lt;BR /&gt;(Microsoft Azure only) There is an intermittent issue where an Ethernet (eth1) interface does not come up when you first boot up the firewall.&lt;BR /&gt;Workaround: Reboot the firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here the logs information found&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.097 +0300 Port 1: Down 10Gb/s-full duplex&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.099 +0300 PORT1: board_port_autoneg_enabled -&amp;gt; board_port_autoneg, link: 0, mode: 1&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.102 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 1: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.106 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 1: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.109 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.444 +0300 Port 2: Down 10Gb/s-full duplex&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.447 +0300 PORT2: board_port_autoneg_enabled -&amp;gt; board_port_autoneg, link: 0, mode: 1&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.447 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 2: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.455 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 2: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.456 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:31&lt;BR /&gt;2023-07-11 04:50:31.459 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:31&lt;BR /&gt;2023-07-11 04:50:31.794 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please let me know if we can find out the Root cause why interface down and connection cannot resume until we need to do reboot to get this fix.&lt;/P&gt;</description>
    <pubDate>Tue, 11 Jul 2023 05:07:13 GMT</pubDate>
    <dc:creator>Fariq_Zaidi</dc:creator>
    <dc:date>2023-07-11T05:07:13Z</dc:date>
    <item>
      <title>PA Firewall VM series | interface suddenly goes down</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/548855#M112031</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a PA VM firewall where all working well but firewall interface (eth1/1 and eth1/2) went down suddenly&lt;/P&gt;
&lt;P&gt;No issue with the management interface so we are still able to access the firewall during the incident time.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;to brings the interface up, we do reboot on firewall and thus fix the problem.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the system log, we can see "link change" but customers stated that no healthy event was found from Azure.&amp;nbsp; (see attachment)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Firmware: 10.1.9-h1&amp;nbsp; - check for known issue but not sure related with&amp;nbsp;PAN-115816&lt;BR /&gt;(Microsoft Azure only) There is an intermittent issue where an Ethernet (eth1) interface does not come up when you first boot up the firewall.&lt;BR /&gt;Workaround: Reboot the firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;here the logs information found&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.097 +0300 Port 1: Down 10Gb/s-full duplex&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.099 +0300 PORT1: board_port_autoneg_enabled -&amp;gt; board_port_autoneg, link: 0, mode: 1&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.102 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 1: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.106 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 1: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.109 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.444 +0300 Port 2: Down 10Gb/s-full duplex&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.447 +0300 PORT2: board_port_autoneg_enabled -&amp;gt; board_port_autoneg, link: 0, mode: 1&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.447 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 2: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.455 +0300 port status changed/updated&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;Port 2: mode changed to autoneg&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:29&lt;BR /&gt;2023-07-11 04:50:29.456 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:31&lt;BR /&gt;2023-07-11 04:50:31.459 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;BR /&gt;brdagent.log &lt;BR /&gt;2023-07-11 04:50:31&lt;BR /&gt;2023-07-11 04:50:31.794 +0300 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please let me know if we can find out the Root cause why interface down and connection cannot resume until we need to do reboot to get this fix.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 05:07:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/548855#M112031</guid>
      <dc:creator>Fariq_Zaidi</dc:creator>
      <dc:date>2023-07-11T05:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: PA Firewall VM series | interface suddenly goes down</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/548921#M112039</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/225107"&gt;@Fariq_Zaidi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If you're looking for root cause I'd recommend that you engage TAC so that they can get a technical support dump and actually see all of the associated logs. Given what you have visible in the logs you've shared the firewall detected the interface went down, however that's just based off of a single file entry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'll just toss out there though that troubleshooting a NIC issue on Azure is absolutely horrific, so I'm not sure how your customer could really argue that the interface&amp;nbsp;&lt;EM&gt;didn't&amp;nbsp;&lt;/EM&gt;or&amp;nbsp;&lt;EM&gt;did&amp;nbsp;&lt;/EM&gt;drop momentarily. You simply don't have the logs on an Azure VM at that level to actually say the NIC didn't have an issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jul 2023 13:05:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/548921#M112039</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-07-11T13:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: PA Firewall VM series | interface suddenly goes down</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/551948#M112347</link>
      <description>&lt;P&gt;Update from Palo alto Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;this issue i am facing is related with internal Bug ID and the fix will be in&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;PAN-OS 10.1.11 is expected to be released in the month of September. And no workaround is available.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;hope this help if anyone facing the same issue.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 02:53:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/551948#M112347</guid>
      <dc:creator>Fariq_Zaidi</dc:creator>
      <dc:date>2023-08-01T02:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: PA Firewall VM series | interface suddenly goes down</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/562246#M113878</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/225107"&gt;@Fariq_Zaidi&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;I experienced the same type of issue in PAN-OS 10.1.6.&lt;BR /&gt;May you please let me know what is the bug ID under which PAN TAC identified this issue?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;BR /&gt;Liviu&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2023 10:51:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/562246#M113878</guid>
      <dc:creator>Liviu_Bodeanu</dc:creator>
      <dc:date>2023-10-18T10:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: PA Firewall VM series | interface suddenly goes down</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/562322#M113899</link>
      <description>&lt;P&gt;Hi Liviu,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;PAN-219643 :&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-release-notes/pan-os-10-1-11-known-and-addressed-issues/pan-os-10-1-11-addressed-issues" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/10-1/pan-os-release-notes/pan-os-10-1-11-known-and-addressed-issues/pan-os-10-1-11-addressed-issues&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Fariq&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 01:10:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pa-firewall-vm-series-interface-suddenly-goes-down/m-p/562322#M113899</guid>
      <dc:creator>Fariq_Zaidi</dc:creator>
      <dc:date>2023-10-19T01:10:10Z</dc:date>
    </item>
  </channel>
</rss>

