43
11. (Optional.) Configure a GRE
key for the tunnel interface.
gre key
key
By default, no GRE key is configured
for an mGRE tunnel interface.
You must configure the same GRE
key or configure no key on both ends
of a tunnel.
On the device, you must configure
different GRE keys for mGRE tunnel
interfaces that have the same source
address or source interface.
For more information about the GRE
key, see GRE in Layer 3—IP
Services Configuration Guide.
12. (Optional.) Set the DF bit for
tunneled packets.
tunnel dfbit enable
By default, the DF bit is not set.
Tunneled packets can be
fragmented for forwarding.
Configuring routing
mGRE clients support dynamic routing protocols of OSPF, RIP, and BGP.
When you configure routing for mGRE client, following these restrictions and guidelines:
When OSPF is used, specify the OSPF interface network type as broadcast in a full-mesh
network and as p2mp in a NHS-NHC network.
Full-mesh networks do not support RIP. NHS-NHC networks must use the RIP-2 multicast
mode and disable the split horizon feature for NHS nodes.
When BGP is used, configure routing polices to ensure the following:
In a full-mesh network, ensure that the local NHC learns a route to the remote private
network, and the route's next hop address is the address of the remote NHC.
In an NHS-NHC network, ensure that the local NHC learns a route to the remote private
network, and the route's next hop address is the address of the NHS.
For more information about OSPF, RIP, BGP, and routing policy configuration, see Layer 3—IP
Routing Configuration Guide.
Configuring IPsec for an mGRE tunnel
The device supports protecting mGRE tunnel data and control packets by using IPsec profiles.
To configure IPsec for an mGRE tunnel:
1. Configure an IPsec transform set to specify the security protocol, authentication and encryption
algorithms, and encapsulation type.
2. Configure an IKE-based IPsec profile.
3. Apply the IKE-based IPsec profile to the mGRE tunnel interface.
To Next Page
Loading...
