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

461
i 2.2.2.2/32 2.2.2.2 0 100 0 ?
*>i 3.1.1.0/24 2.2.2.2 0 100 0 ?
*>i 8.1.1.0/24 3.1.1.2 0 100 0 65008i
* i 9.1.1.0/24 2.2.2.2 0 100 0 ?
The output shows that the route 8.1.1.0 becomes valid with the next hop as Firewall A.
5. Verify the configuration:
# Ping 8.1.1.1 on Firewall C.
[FirewallC] ping 8.1.1.1
PING 8.1.1.1: 56 data bytes, press CTRL_C to break
Reply from 8.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms
Reply from 8.1.1.1: bytes=56 Sequence=2 ttl=254 time=2 ms
Reply from 8.1.1.1: bytes=56 Sequence=3 ttl=254 time=2 ms
Reply from 8.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms
Reply from 8.1.1.1: bytes=56 Sequence=5 ttl=254 time=2 ms
--- 8.1.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/2/2 ms
BGP and IGP synchronization configuration at the CLI
Network requirements
As shown in Figure 285, all devices of company A belong to AS 65008 while all devices of company B
belong to AS 65009. AS 65008 and AS 65009 are connected through Firewall A and Firewall B. It is
required that Firewall A can access network 9.1.2.0/24 in AS 65009, and Firewall C can access network
8.1.1.0/24 in AS 65008.
Figure 285 Network diagram
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown)
2. Configure OSPF:
Enable OSPF in AS 65009, so that Firewall B can obtain the route to 9.1.2.0/24.
# Configure Firewall B.
<FirewallB> system-view
[FirewallB] ospf 1
[FirewallB-ospf-1] area 0
[FirewallB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[FirewallB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255