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

Table Of Contents
468
Firewall C has learned the route to the destination 9.1.1.0/24 from Firewall B.
3. Configure BGP community attribute:
# Configure a routing policy.
[FirewallA] route-policy comm_policy permit node 0
[FirewallA-route-policy] apply community no-export
[FirewallA-route-policy] quit
# Apply the routing policy.
[FirewallA] bgp 10
[FirewallA-bgp] peer 200.1.2.2 route-policy comm_policy export
[FirewallA-bgp] peer 200.1.2.2 advertise-community
# Display BGP routing table information on Firewall B.
[FirewallB] display bgp routing-table 9.1.1.0
BGP local router ID : 2.2.2.2
Local AS number : 20
Paths: 1 available, 1 best
BGP routing table entry information of 9.1.1.0/24:
From : 200.1.2.1 (1.1.1.1)
Original nexthop: 200.1.2.1
Community : No-Export
AS-path : 10
Origin : igp
Attribute value : MED 0, pref-val 0, pre 255
State : valid, external, best,
Not advertised to any peers yet
You can find the No-export community attribute in the output information. In this case, the route of
9.1.1.0/24 is not available in the routing table of Firewall C.
BGP route reflector configuration at the CLI
Network requirements
In Figure 288, all firewalls run BGP.
Between Firewall A and Firewall B is an EBGP connection, and between Firewall C and Firewall B,
and between Firewall C and Firewall D are IBGP connections.
Firewall C is a route reflector with clients Firewall B and D.
Firewall D can learn route 1.0.0.0/8 from Firewall C.