- Products
- Learn
- Local User Groups
- Partners
- More
Check Point Jump-Start Online Training
Now Available on CheckMates for Beginners!
Why do Hackers Love IoT Devices so Much?
Join our TechTalk on Aug 17, at 5PM CET | 11AM EST
Welcome to Maestro Masters!
Talk to Masters, Engage with Masters, Be a Maestro Master!
ZTNA Buyer’s Guide
Zero Trust essentials for your most valuable assets
The SMB Cyber Master
Boost your knowledge on Quantum Spark SMB gateways!
As YOU DESERVE THE BEST SECURITY
Upgrade to our latest GA Jumbo
CheckFlix!
All Videos In One Space
Hi Team,
We had an issue where one of the route prefix advertisement was suddenly stopped from AWS Transit Gateway to Checkpoint Firewalls and we are investigating the root cause. Can any one help me where we can see the logs for the advertised and received route prefixes to/from a specific BGP peers. We have verified in routed.log and routed_messages files but we cannot find it.
Are trace options enabled in the BGP config?
Otherwise I doubt that such things are logged in a non debug state (see sk101399), rather such information is usually visible (point in time) by the applicable CLI commands.
There were no trace options enabled. So without BGP debug we cannot have this kind of logs, correct?. Will the debug procedure described in sk101399 help to get the logs during the issue time?.
Recommend working with TAC on an action plan to capture relevant information should the issue reoccur.
About CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY