H3C Technologies H3C SecPath F1000-E - Manual (Page 65)

53
# Configure a static route to the headquarters network with the outgoing interface being Tunnel 0.
[RouterB] ip route-static 192.168.11.0 255.255.255.0 tunnel 0
Verifying the configuration
# After the configurations, view the tunnel entry information on Router A. No tunnel entry exists.
[RouterA] display gre p2mp tunnel-table interface tunnel 0
Dest Addr Mask Tunnel Dest Addr Gre Key
# Ping Host A from Host B. The operation succeeds.
# View tunnel entry information on Router A again. As the branch has initiated the establishment
of the tunnel by sending packets to the headquarters, a tunnel entry should be installed, as shown
in the following output information:
[RouterA] display gre p2mp tunnel-table interface tunnel 0
Dest Addr Mask Tunnel Dest Addr Gre Key
192.168.12.0 255.255.255.0 11.1.1.2
Configuration example for P2MP GRE tunnel backup at the
headquarters
Network requirements
As shown in Figure 30 , the headquarters uses two gateways at the egress of the internal network, with
SecPath B for backup. Two GRE tunnels are created on SecPath C, the gateway at the branch, one for
connecting SecPath A and the other for connecting SecPath B. Normally, packets are forwarded along
the tunnel between SecPath A and SecPath C. When a failure occurs along this path, the tunnel between
SecPath B and SecPath C is used to transmit packets.
To meet the requirements, establish a P2MP GRE tunnel with the branch on both SecPath A and SecPath
B, establish a GRE over IPv4 tunnel between SecPath A and SecPath B, and on SecPath A configure the
tunnel interface of the GRE over IPv4 tunnel as the backup interface of the P2MP GRE tunnel interface.
Thus, when SecPath A cannot find the corresponding tunnel entry for a packet, it delivers the packet to
SecPath B, which then forwards the packet to SecPath C.
NOTE:
To avoid looping, do not configure the tunnel interface of the GRE over IPv4 tunnel as the backup interface
of the P2MP GRE tunnel interface on SecPath B.