HP VPN Firewall Appliances Network Management Configuration Guide

516
<RouterB> system-view
[RouterB] bgp 65009
[RouterB-bgp] router-id 2.2.2.2
[RouterB-bgp] peer 3.1.1.2 as-number 65008
[RouterB-bgp] peer 3.3.3.3 as-number 65009
[RouterB-bgp] peer 3.3.3.3 connect-interface loopback 0
[RouterB-bgp] network 9.1.1.0 24
[RouterB-bgp] quit
[RouterB] ip route-static 3.3.3.3 32 9.1.1.2
# Configure Router A.
<RouterA> system-view
[RouterA] bgp 65009
[RouterA-bgp] router-id 3.3.3.3
[RouterA-bgp] peer 3.1.2.2 as-number 65008
[RouterA-bgp] peer 2.2.2.2 as-number 65009
[RouterA-bgp] peer 2.2.2.2 connect-interface loopback 0
[RouterA-bgp] network 9.1.1.0 24
[RouterA-bgp] quit
[RouterA] ip route-static 2.2.2.2 32 9.1.1.1
# Display the BGP routing table on Firewall.
[Firewall] 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
{ T h e ou t p u t s h ow s t wo v a l id r o u t e s t o d es t i n a t i on 9.1.1.0 / 24 : t h e ro u t e wi t h n e x t h o p 3.1.1.1 i s
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 output interface GigabitEthernet 0/1.
3. Configure load balancing:
Because Firewall has two routes to reach AS 65009, configuring load balancing over the two BGP
routes on Firewall can improve link utilization.
# Configure Firewall.
[Firewall] bgp 65008
[Firewall-bgp] balance 2
[Firewall-bgp] quit
4. Verify the configuration: