Error message of Azure displayed when using VM Series firewall on ESXI server.
3842
Created On 04/26/24 08:51 AM - Last Modified 09/12/24 23:48 PM
Symptom
- Using VM-Series Firewall on an ESXi Server
- When an interface flaps Azure related error message " Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb" is displayed
- brdagent.log (less mp-log brdagent.log) displays the message
513 +0900 Port 3: Down 10Gb/s-full duplex
581 +0900 PORT3: board_port_autoneg_enabled -> board_port_autoneg, link: 0, mode: 1
586 +0900 port status changed/updated
Port 3: mode changed to autoneg
587 +0900 port status changed/updated
Port 3: mode changed to autoneg
588 +0900 rte_eth_dev_set_link_up is not supported on port 3
591 +0900 Error: vm_is_azure_gwlb(vm/vm_ports.c:817): sysd_fetch_obj() failed for cfg.net.azr-gwlb
Environment
- VM-Series on VMware ESXi
- PAN-OS 10.1 branch
Resolution
- This error message is printed when the sysd variable 'cfg.net.azr-gwlb' is searched to find out whether the env is an azure gwlb.
- This cosmetic issue for VM-Series Firewall on an ESXi Server has been addressed in PAN-OS 10.2 or higher branches through an internal Issue ID.