Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[ScreenOS] The firewall fails to announce the BGP network prefix if the same is configured as a BGP aggregate route

0

0

Article ID: KB13012 KB Last Updated: 03 Oct 2012Version: 3.0
Summary:
This article describes the issue of the aggregate route not being advertised to its BGP peer, if the BGP route prefix is exactly the same as it's BGP aggregate route.
Symptoms:
The BGP aggregate can be used to announce a supernet to minimize BGP flapping with its peers. For example, the 192.168.1.0/24, 192.168.2.0/24, and 192.168.3.0/24 networks can be supernetted and announced as:
   set vrouter trust-vr
       set protocol bgp
          set aggregate ip 192.168.0.0/22 summary-only
But, if the aggregate prefix is 192.168.0.0/22 and the network (whether learned via OSPF, static route, and so on) is also 192.168.0.0/22, then this prefix is no longer announced to the BGP peer.


Cause:

Solution:
The workaround is to announce the prefix with the no-check statement:
      set vrouter trust-vr
      set protocol bgp
         set network 192.168.0.0/22 no-check
This issue is fixed in ScreenOS 6.1.0r5, 6.2.0r2, and 6.3.0r1 or later.
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search