cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Who Me Too'd this topic

PA Firewall VM series | interface suddenly goes down

L3 Networker

Hi Team,

 

We have a PA VM firewall where all working well but firewall interface (eth1/1 and eth1/2) went down suddenly

No issue with the management interface so we are still able to access the firewall during the incident time. 

to brings the interface up, we do reboot on firewall and thus fix the problem.

 

From the system log, we can see "link change" but customers stated that no healthy event was found from Azure.  (see attachment) 

 

Firmware: 10.1.9-h1  - check for known issue but not sure related with PAN-115816
(Microsoft Azure only) There is an intermittent issue where an Ethernet (eth1) interface does not come up when you first boot up the firewall.
Workaround: Reboot the firewall.

 

here the logs information found

 

brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.097 +0300 Port 1: Down 10Gb/s-full duplex
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.099 +0300 PORT1: board_port_autoneg_enabled -> board_port_autoneg, link: 0, mode: 1
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.102 +0300 port status changed/updated
brdagent.log
2023-07-11 04:50:29
Port 1: mode changed to autoneg
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.106 +0300 port status changed/updated
brdagent.log
2023-07-11 04:50:29
Port 1: mode changed to autoneg
brdagent.log
2023-07-11 04:50:29
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
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.444 +0300 Port 2: Down 10Gb/s-full duplex
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.447 +0300 PORT2: board_port_autoneg_enabled -> board_port_autoneg, link: 0, mode: 1
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.447 +0300 port status changed/updated
brdagent.log
2023-07-11 04:50:29
Port 2: mode changed to autoneg
brdagent.log
2023-07-11 04:50:29
2023-07-11 04:50:29.455 +0300 port status changed/updated
brdagent.log
2023-07-11 04:50:29
Port 2: mode changed to autoneg
brdagent.log
2023-07-11 04:50:29
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
brdagent.log
2023-07-11 04:50:31
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
brdagent.log
2023-07-11 04:50:31
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

 

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.

Who Me Too'd this topic