R3721-F3210-F3171-HP High-End Firewalls Network Management Configuration Guide-6PW101

Table Of Contents
465
[FirewallA-bgp] quit
# Configure Firewall B.
<FirewallB> system-view
[FirewallB] bgp 65009
[FirewallB-bgp] router-id 2.2.2.2
[FirewallB-bgp] peer 3.1.1.2 as-number 65008
[FirewallB-bgp] peer 3.3.3.3 as-number 65009
[FirewallB-bgp] peer 3.3.3.3 connect-interface loopback 0
[FirewallB-bgp] network 9.1.1.0 24
[FirewallB-bgp] quit
[FirewallB] ip route-static 3.3.3.3 32 9.1.1.2
# Configure Firewall C.
<FirewallC> system-view
[FirewallC] bgp 65009
[FirewallC-bgp] router-id 3.3.3.3
[FirewallC-bgp] peer 3.1.2.2 as-number 65008
[FirewallC-bgp] peer 2.2.2.2 as-number 65009
[FirewallC-bgp] peer 2.2.2.2 connect-interface loopback 0
[FirewallC-bgp] network 9.1.1.0 24
[FirewallC-bgp] quit
[FirewallC] ip route-static 2.2.2.2 32 9.1.1.1
# Display the BGP routing table on Firewall A.
[FirewallA] display bgp routing-table
Total Number of Routes: 3
BGP Local router ID is 1.1.1.1
Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? – incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 8.1.1.0/24 0.0.0.0 0 0 i
*> 9.1.1.0/24 3.1.1.1 0 0 65009i
* 3.1.2.1 0 0 65009i
{ From the output, you can find two valid routes to destination 9.1.1.0/24: the route with next hop
3.1.1.1 is marked with a greater-than sign (>), indicating it is the best route; the route with next
hop 3.1.2.1 is marked with only an asterisk (*), indicating it is a valid route, but not the best.
{ By using the display ip routing-table command, you can find only one route to 9.1.1.0/24 with
next hop 3.1.1.1 and outgoing interface GE0/2.
3. Configure load balancing:
Since Firewall A has two routes to reach AS 65009, configuring load balancing over the two BGP
routes on Firewall A can improve link utilization.
# Configure Firewall A.
[FirewallA] bgp 65008
[FirewallA-bgp] balance 2