Troubleshooting Tip: FortiPortal scalable cluster send out 10.43.0.0/16 and 10.42.0.0/16 logs and these logs captured inside FortiGate

[WinterSnowYap]

Description	This article describes that FortiPortal's scalable cluster sends out 10.43.0.0/16 and 10.42.0.0/16 logs, and these logs are captured inside FortiGate.
Scope	FortiPortal.
Solution	Device information for FortiPortal scalable cluster: FortiPortal-A (Primary). FortiPortal-B (Secondary). FortiPortal-C (Secondary). FortiGate acts as the default gateway for FortiPortal. Scenario 1: When the FortiPortal scalable cluster performs a reboot, all FortiPortal will send out 10.43.0.0/16 and 10.42.0.0/16 logs, it will be captured by FortiGate, which is the expected behavior. Once all FortiPortals are rebooted and come back online, all FortiPortals will stop sending out 10.43.0.0/16 and 10.42.0.0/16 logs. Scenario 2: When a FortiPortal scalable cluster has a cluster issue, all FortiPortals will send out 10.43.0.0/16 and 10.42.0.0/16 logs, which will be captured by FortiGate, which is the expected behavior. After the FortiPortal scalable cluster resolves the cluster issue, all FortiPortal instances will stop sending out 10.43.0.0/16 and 10.42.0.0/16 logs. Ignore 10.43.0.0/16 and 10.42.0.0/16 logs that show inside FortiGate, as these 2 subnet logs are related to FortiPortal system internal use.