Thanks for the replies guys. We keep seeing errors like these below when issuing following command: less mp-log l2ctrld.log Maybe this could also be related to a faulty speed/duplex detection? However, we don’t see any errors on the interfaces themselves, also not on the connected switches. 2016-11-29 21:52:04.685 +0100 Got port 33 event, link 1, speed 3, duplex 2 2016-11-29 21:52:04.685 +0100 port 33 is full duplex. Enable lacp 2016-11-29 22:22:05.204 +0100 Error: pan_l2ctrld_read_sysd_port_status(pan_l2ctrld_sysd.c:140): pan_ifhw_link_portstate_to_state for port 30 failed. set to 1Gb/s-full 2016-11-29 22:22:05.257 +0100 Error: pan_l2ctrld_read_sysd_port_status(pan_l2ctrld_sysd.c:140): pan_ifhw_link_portstate_to_state for port 31 failed. set to 1Gb/s-full 2016-11-29 22:22:05.316 +0100 Error: pan_l2ctrld_read_sysd_port_status(pan_l2ctrld_sysd.c:140): pan_ifhw_link_portstate_to_state for port 30 failed. set to 1Gb/s-full 2016-11-29 22:22:05.367 +0100 Error: pan_l2ctrld_read_sysd_port_status(pan_l2ctrld_sysd.c:140): pan_ifhw_link_portstate_to_state for port 32 failed. set to 1Gb/s-full 2016-11-29 22:22:05.422 +0100 Error: pan_l2ctrld_read_sysd_port_status(pan_l2ctrld_sysd.c:140): pan_ifhw_link_portstate_to_state for port 31 failed. set to 1Gb/s-full The link-change events have been there since we configured everything, but they haven't been an issue up to now. There are switches upstream of the Palo before a call server we have in place also. Kind regards Jack
... View more