How does the firewall BGP route?

14

When multiple routes are reached at the same destination, BGP adopts the following policy to route:
1. Optimize the route with the highest preferred value (PrefVal);
2. Preferred route with the highest local precedence (Local_Pref);
3. Aggregate routes are preferred (aggregation routes have priority over non-aggregated routes);
4. Local manual aggregation routes have a higher priority than local auto-aggregated routes.
5. Routes imported through the network command take precedence over locally routes imported through the import-route command.
6. Preferred AS path (AS_Path) the shortest route;
7. Compare the Origin attribute, and select the route with the Origin type IGP, EGP, and Incomplete;
8. Preferred route with the lowest MED value;
9. Route learned from EBGP (EBGP route priority is higher than IBGP route);
10. The route with the lowest IGP metric for the AS to reach the BGP next hop is preferred. If load balancing is configured and multiple As_Path identical external routes are configured, multiple routes are selected for load balancing based on the configured number of routes.
11. Optimize the shortest route for Cluster_List;
12. Optimize the route with the smallest Originator_ID;
13. It is preferred that the router with the smallest router ID be advertised;
14. Compare the IP address of the peer, preferably from a peer with a smaller IP Address.

Other related questions:
Monitoring OSPF and BGP status on the firewall
Perform as follows to monitor OSPF and BGP status on the firewall: 1. Choose Network > Route > Dynamic Route Monitoring Table. 2. On the OSPFv2 Route List page, view detailed OSPFv2 route information. 3. On the BGP Route List page, view detailed BGP route information.

Configuring the BGP priority on the firewall
The method for modifying the BGP priority on the USG2000&5000&6000 is as follows: -Modifying the BGP priority: [USG]bgp 25212 [USG-bgp]ipv4-family unicast [USG-bgp-af-ipv4]preference 120

BGP route selection on the firewall
When there are multiple routes to the same destination, BGP selects routes according to the following rules: 1. Prefers the route with the highest PreVal. 2. Prefers the route with the highest Local_Pref. 3. A summarized route is preferred. A summarized route takes precedence over a nonsummarized route. 4. A locally and manually summarized route takes precedence over a locally and automatically summarized route. 5. A route imported using the network command is preferred over a route imported using the import-route command. 6. Prefers the route with the shortest AS_Path. 7. Prefers the route with the highest Origin type. IGP is higher than EGP, and EGP is higher than Incomplete. 8. Prefers the route with the lowest MED. 9. Prefers routes learned from EBGP (EBGP routes have higher priorities than IBGP routes). 10. Prefers routes in an AS with the lowest IGP metric to BGP. If load balancing is configured, and multiple external routes with the same As_Path exist, select multiple routes based on the configured number of routes for load balancing. 11. Prefers the route with the shortest Cluster_List. 12. Prefers the route with the smallest Originator_ID. 13. Prefers the route advertised by the device with the smallest router ID. 14. Prefers the route learned from the peer with the smallest address if the IP addresses of peers are compared in the route selection process.

On S series switches, how long does it take for BGP routes to expire after the static routes imported by BGP expire
If the static routes imported by an S series switch become invalid, the routes imported in the BGP routing table will be invalidated. The route imported through the network command must be active in the local routing table. Otherwise, it cannot be imported in the BGP routing table.

Does an S series switch support BGP
BGP support varies depending on S series switches, which is listed as follows (until V200R008): - S7700/S9700/S12700: supported - S9300: supported - S6720EI: supported - S6700EI: supported - S5720HI: supported - S5710HI: supported - S5700HI: supported - S5720EI: supported - S5710EI: supported - S5700EI: supported - S5720SI/S5720S-SI: supported - S5700SI: not supported - S5710LI: not supported - S5700LI: not supported - S5700S-LI: not supported - S3700HI: supported - S3700EI: supported - S3700SI: not supported - S2750EI: not supported - S2720EI: not supported - S2700EI: not supported - S2710SI: not supported - S2700SI: not supported - S1720: not supported BGP4+ support varies depending on S series switches, which is listed as follows (until V200R008): - S7700/S9700/S12700: supported - S9300: supported - S6720EI: supported - S6700EI: supported (V200R001 and later) - S5720HI: supported - S5710HI: supported - S5700HI: supported (V200R001 and later) - S5720EI: supported - S5710EI: supported - S5700EI: supported (V200R001 and later) - S5720SI/S5720S-SI: supported - S5700SI: not supported - S5710LI: not supported - S5700LI: not supported - S5700S-LI: not supported - S3700HI: supported (V200R001 and later) - S3700EI: not supported - S3700SI: not supported - S2750EI: not supported - S2720EI: not supported - S2700EI: not supported - S2710SI: not supported - S2700SI: not supported - S1720: not supported

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top