That generally "fixes" issues where logs are not beign sent at all. > request log-fwd-ctrl device action start-from-lastack If it does not indicate current logs, you can have panorama instruct the firewall to restart log forwarding from teh lack acknowledged message: In panorama, you can verify it is recieving the logs The output should show a message stating that the log forwarding agent is active You should see your panorama appliance serial and IP in the configured list On the firewall you can verify log forwarding is configured and active: Without that they will, of course, log neither locally or to panorama.īefore restarting the services, there are additional troubleshooting steps you can take, again from the CLI I assume this was already the case, but policies must be set to log on session start or end in addition to having a forwarding profile. Yes, the service restarts would be done via CLI, but if you did not have the forwarding profiles with "Panorama" checked for traffic that would explain why they were not being forwarded.
0 kommentar(er)
