· Payload packet—Original packet. The protocol type of the payload packet is called the passenger protocol. The passenger protocol can be any network layer protocol.

· GRE header—Header that is added to the payload packet to change the payload packet to a GRE packet. A GRE header includes the number of encapsulations, version, passenger protocol type, checksum, and key. GRE is called the encapsulation protocol.

· Delivery header—Header that is added to the GRE packet to deliver it to the tunnel end. The transport protocol (or delivery protocol) is the network layer protocol that transfers GRE packets.

The device supports GRE tunnels with IPv4 and IPv6 as the transport protocols. When the transport protocol is IPv4, the GRE tunnel mode is GRE over IPv4 (GRE/IPv4). When the transport protocol is IPv6, the GRE tunnel mode is GRE over IPv6 (GRE/IPv6).

Figure 1 GRE encapsulation format

‌

GRE tunnel operating principle

As shown in Figure 2, an IPv6 protocol packet traverses an IPv4 network through a GRE tunnel as follows:

1. After receiving an IPv6 packet from the interface connected to IPv6 network 1, Device A processes the packet as follows:

a. Looks up the routing table to identify the outgoing interface for the IPv6 packet.

b. Submits the IPv6 packet to the outgoing interface—the GRE tunnel interface Tunnel 0.

2. Upon receiving the packet, the tunnel interface encapsulates the packet with GRE and then with IPv4. In the IPv4 header:

¡ The source address is the tunnel's source address (the IP address of Interface A of Device A).

¡ The destination address is the tunnel's destination address (the IP address of Interface B of Device B).

3. Device A looks up the routing table according to the destination address in the IPv4 header, and forwards the IPv4 packet out of the physical interface (Interface A) of the GRE tunnel.

4. When the IPv4 arrives at the GRE tunnel destination Device B, Device B checks the destination address. Because the destination is Device B itself and the protocol number in the IP header is 47 (the protocol number for GRE), Device B submits the packet to GRE for de-encapsulation.

5. GRE first removes the IPv4 header, and then checks the GRE key, checksum, and packet sequence number. After GRE finishes the checking, it removes the GRE header, and submits the payload to the IPv6 protocol for forwarding.

Figure 2 IPv6 networks interconnected through a GRE tunnel

‌

GRE security mechanisms

GRE supports the GRE key and GRE checksum security mechanisms.

GRE key

GRE keys ensure packet validity. The sender adds a GRE key into a packet. The receiver compares the GRE key with its own GRE key. If the two keys are the same, the receiver accepts the packet. If the two keys are different, the receiver drops the packet.

GRE checksum

GRE checksums ensure packet integrity. The sender calculates a checksum for the GRE header and payload and sends the packet containing the checksum to the tunnel peer. The receiver calculates a checksum for the received packet and compares it with that carried in the packet. If the checksums are the same, the receiver considers the packet intact and continues to process the packet. If the checksums are different, the receiver discards the packet.

GRE application scenarios

The following shows typical GRE application scenarios:

Connecting networks running different protocols over a single backbone

As shown in Figure 3, IPv6 network 1 and IPv6 network 2 are IPv6 networks, and IPv4 network 1 and IPv4 network 2 are IPv4 networks. Through the GRE tunnel between Device A and Device B, IPv6 network 1 can communicate with IPv6 network 2 and IPv4 network 1 can communicate with IPv4 network 2, without affecting each other.

Figure 3 Network diagram

‌

Enlarging network scope

In an IP network, the maximum TTL value of a packet is 255. If two devices have more than 255 hops in between, they cannot communicate with each other. By using a GRE tunnel, you can hide some hops to enlarge the network scope. As shown in Figure 4, only the tunnel-end devices (Device A and Device D) of the GRE tunnel are counted in hop count calculation. Therefore, there are only three hops between Host A and Host B.

Figure 4 Network diagram

‌

Constructing VPN

As shown in Figure 5, Site 1 and Site 2 both belong to VPN 1 and are located in different cities. Using a GRE tunnel can connect the two VPN sites across the WAN.

Figure 5 Network diagram

‌

Operating with IPsec

As shown in Figure 6, GRE can be used together with IPsec to form a GRE over IPsec tunnel. Packets (for example, routing protocol packets, voice data, and video data) are first encapsulated with GRE and then with IPsec. GRE over IPsec delivers the following benefits:

· Improves transmission security.

· Allows IPsec to protect not only unicast packets. GRE supports encapsulating multicast, broadcast, and non-IP packets. After GRE encapsulation, these packets become common unicast packets, which can be protected by IPsec.

· Simplifies IPsec configuration. Packets are first encapsulated by GRE. You can define the packets to be protected by IPsec according to the GRE tunnel's source and destination addresses, without considering the source and destination addresses of the original packets.

Figure 6 Network diagram

‌

GRE and IPsec can also form IPsec over GRE tunnels. As a best practice, use GRE over IPsec tunnels instead of IPsec over GRE tunnels.

For more information about IPsec, see "Configuring IPsec."

Protocols and standards

· RFC 1701, Generic Routing Encapsulation (GRE)

· RFC 1702, Generic Routing Encapsulation over IPv4 networks

· RFC 2784, Generic Routing Encapsulation (GRE)

· RFC 2890, Key and Sequence Number Extensions to GRE

Restrictions and guidelines: GRE configuration

When you configure a GRE tunnel, follow these restrictions and guidelines:

· You must configure the tunnel source address and destination address at both ends of a tunnel. The tunnel source or destination address at one end must be the tunnel destination or source address at the other end.

· As a best practice, do not configure the same tunnel source and destination addresses for local tunnel interfaces that use the same tunnel mode.

· Do not configure the same tunnel source and destination addresses for a GRE tunnel interface and a GRE P2MP tunnel interface.

· You can enable or disable GRE checksum at each end of a tunnel. If GRE checksum is enabled at a tunnel end, the tunnel end sends packets carrying the checksum to the peer end. A tunnel end checks the GRE checksum of a received packet if the packet carries a GRE checksum, whether or not the tunnel end is enabled with GRE checksum.

· To ensure correct packet forwarding, identify whether the destination network of packets and the IP address of the local tunnel interface are on the same subnet. If they are not, configure a route reaching the destination network through the tunnel interface. You can configure the route by using one of the following methods:

¡ Configure a static route, using the local tunnel interface as the outgoing interface of the route.

¡ Enable a dynamic routing protocol on both the tunnel interface and the interface connecting the private network. This allows the dynamic routing protocol to establish a routing entry with the tunnel interface as the outgoing interface.

· GRE encapsulation and de-encapsulation can decrease the forwarding efficiency of tunnel-end devices.

Configuring a GRE/IPv4 tunnel

Restrictions and guidelines

This task describes only GRE/IPv4 tunnel required tunnel interface commands (the interface tunnel, source, and destination commands). For more tunnel interface commands, see "Configuring tunneling."

Procedure

1. Enter system view.

system-view

2. Create a GRE tunnel interface, and specify the tunnel mode as GRE/IPv4.

interface tunnel number mode gre

You must configure the same tunnel mode on both ends of a tunnel. Otherwise, packet delivery might fail.

3. Configure an IP address for the tunnel interface based on the passenger protocol.

IPv4:

For information about how to assign an IPv4 address to an interface, see IP addressing in Layer 3—IP Services Configuration Guide.

IPv6:

For information about how to assign an IPv6 address to an interface, see basic IPv6 configuration in Layer 3—IP Services Configuration Guide.

By default, no IP address is configured for a tunnel interface.

4. Configure a source address or source interface for the tunnel interface.

source { ip-address | interface-type interface-number }

By default, no source address or interface is configured for a tunnel interface.

If you configure a source address for a tunnel interface, the tunnel interface uses the source address as the source address of the encapsulated packets.

If you configure a source interface for a tunnel interface, the tunnel interface uses the primary IP address of the source interface as the source address of the encapsulated packets.

5. Configure a destination address for the tunnel interface.

destination ip-address

By default, no destination address is configured for a tunnel interface.

The destination address is the address of the physical interface that the tunnel remote end uses to receive packets from the GRE tunnel.

The tunnel local end uses this address as the destination address of the encapsulated packets.

The tunnel destination address and the IP address of the tunnel interface must be in different subnets.

6. (Optional.) Enable GRE keepalive, and set the keepalive interval and keepalive number.

keepalive [ interval [ times ] ]

By default, GRE keepalive is disabled.

7. (Optional.) Configure GRE security mechanisms.

¡ Enable GRE checksum.

gre checksum

By default, GRE checksum is disabled.

¡ Configure a GRE key for the GRE tunnel interface.

gre key key

By default, no GRE key is configured for a GRE tunnel interface.

The two ends of a GRE tunnel must have the same key or both have no key.

8. (Optional.) Set the DF bit for encapsulated packets.

tunnel dfbit enable

By default, the DF bit is not set, allowing encapsulated packets to be fragmented.

Configuring a GRE/IPv6 tunnel

Restrictions and guidelines

This task describes only GRE/IPv6 tunnel required tunnel interface commands (the interface tunnel, source, and destination commands). For more tunnel interface commands, see "Configuring tunneling."

Procedure

1. Enter system view.

system-view

2. Create a GRE tunnel interface, and specify the tunnel mode as GRE/IPv6.

interface tunnel number mode gre ipv6

You must configure the same tunnel mode on both ends of a tunnel. Otherwise, packet delivery might fail.

3. Configure an IP address for the tunnel interface based on the passenger protocol.

IPv4:

For information about how to assign an IPv4 address to an interface, see IP addressing in Layer 3—IP Services Configuration Guide.

IPv6:

For information about how to assign an IPv6 address to an interface, see basic IPv6 configuration in Layer 3—IP Services Configuration Guide.

By default, no IP address is configured for a tunnel interface.

4. Configure a source IPv6 address or source interface for the tunnel interface.

source { ipv6-address | interface-type interface-number }

By default, no source IPv6 address or interface is configured for a tunnel interface.

If you configure a source IPv6 address for a tunnel interface, the tunnel interface uses the source IPv6 address as the source IPv6 address of the encapsulated packets.

If you configure a source interface for a tunnel interface, the tunnel interface uses the IPv6 address of the source interface as the source IPv6 address of the encapsulated packets.

5. Configure a destination IPv6 address for the tunnel interface.

destination ipv6-address

By default, no destination IPv6 address is configured for a tunnel interface.

The destination IPv6 address is the IPv6 address of the physical interface that the tunnel remote end uses to receive packets from the GRE tunnel.

The tunnel local end uses this address as the destination IPv6 address of the encapsulated packets.

The tunnel destination address and the IP address of the tunnel interface must be in different subnets.

6. (Optional.) Configure GRE security mechanisms.

¡ Enable GRE checksum.

gre checksum

By default, GRE checksum is disabled.

¡ (Optional.) Configure a GRE key for the tunnel interface.

gre key key

By default, no GRE key is configured for a GRE tunnel interface.

The two ends of a GRE tunnel must have the same key or both have no key.

Enabling dropping IPv6 packets that use IPv4-compatible IPv6 addresses

About this task

This feature enables the device to check the source and destination IPv6 addresses of the de-encapsulated IPv6 packets from a tunnel. If a packet uses an IPv4-compatible IPv6 address as the source or destination address, the device discards the packet.

Procedure

1. Enter system view.

system-view

2. Configure the device to discard IPv6 packets with IPv4-compatible IPv6 addresses.

tunnel discard ipv4-compatible-packet

By default, the device does not discard such IPv6 packets.

For more information about this command, see tunneling in VPN Command Reference.

Display and maintenance commands for GRE

Execute display commands in any view and reset commands in user view.

Task	Command	Remarks
Display information about tunnel interfaces.	display interface [ tunnel [ number ] ] [ brief [ description \| down ] ]	For more information about the commands, see tunneling in VPN Command Reference.
Display IPv6 information about tunnel interface.	display ipv6 interface [ tunnel [ number ] ] [ brief ]	For more information about this command, see IPv6 basics in Layer 3—IP Services Command Reference.
Clear tunnel interface statistics.	reset counters interface [ tunnel [ number ] ]	For more information about this command, see tunneling in VPN Command Reference.
Clear IPv6 statistics on tunnel interfaces.	reset ipv6 statistics [ slot slot-number ]	For more information about this command, see IPv6 basics in Layer 3—IP Services Command Reference.

‌

GRE configuration examples

Example: Configuring an IPv4 over IPv4 GRE tunnel

Network configuration

As shown in Figure 7, Group 1 and Group 2 are two private IPv4 networks. The two networks both use private network addresses and belong to the same VPN. Establish a GRE tunnel between Device A and Device B to interconnect the two private IPv4 networks Group 1 and Group 2.

Figure 7 Network diagram

‌

Procedure

1. Assign IP addresses to interfaces and configure routes, security zones, zone pairs, and interzone policies. Make sure the network connections are available. (Details not shown.)

2. Configure Device A:

# Create tunnel interface Tunnel 0, and specify the tunnel mode as GRE/IPv4.

<DeviceA> system-view

[DeviceA] interface tunnel 0 mode gre

# Configure an IP address for the tunnel interface.

[DeviceA-Tunnel0] ip address 10.1.2.1 255.255.255.0

# Configure the source address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device A.

[DeviceA-Tunnel0] source 1.1.1.1

# Configure the destination address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device B.

[DeviceA-Tunnel0] destination 2.2.2.2

[DeviceA-Tunnel0] quit

# Configure a static route from Device A through the tunnel interface to Group 2.

[DeviceA] ip route-static 10.1.3.0 255.255.255.0 tunnel 0

# Add tunnel interface Tunnel 0 to security zone Untrust.

[DeviceA] security-zone name Untrust

[DeviceA-security-zone-Untrust] import interface Tunnel 0

[DeviceA-security-zone-Untrust] quit

# Allow bidirectional traffic communication between security zones Untrust and Local.

[DeviceA] security-policy ip

[DeviceA-security-policy-ip] rule name tunnel

[DeviceA-security-policy-ip-13-tunnel] source-zone untrust

[DeviceA-security-policy-ip-13-tunnel] source-zone local

[DeviceA-security-policy-ip-13-tunnel] destination-zone local

[DeviceA-security-policy-ip-13-tunnel] destination-zone untrust

[DeviceA-security-policy-ip-13-tunnel] quit

[DeviceA-security-policy-ip] quit

3. Configure Device B:

# Create tunnel interface Tunnel 0 and specify the tunnel mode as GRE/IPv4.

<DeviceB> system-view

[DeviceB] interface tunnel 0 mode gre

# Configure an IP address for the tunnel interface.

[DeviceB-Tunnel0] ip address 10.1.2.2 255.255.255.0

# Configure the source address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device B.

[DeviceB-Tunnel0] source 2.2.2.2

# Configure the destination address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device A.

[DeviceB-Tunnel0] destination 1.1.1.1

[DeviceB-Tunnel0] quit

# Configure a static route from Device B through the tunnel interface to Group 1.

[DeviceB] ip route-static 10.1.1.0 255.255.255.0 tunnel 0

# Add tunnel interface Tunnel 0 to security zone Untrust.

[DeviceB] security-zone name Untrust

[DeviceB-security-zone-Untrust] import interface Tunnel 0

[DeviceB-security-zone-Untrust] quit

# Allow bidirectional traffic communication between security zones Untrust and Local.

[DeviceB] security-policy ip

[DeviceB-security-policy-ip] rule name tunnel

[DeviceB-security-policy-ip-13-tunnel] source-zone untrust

[DeviceB-security-policy-ip-13-tunnel] source-zone local

[DeviceB-security-policy-ip-13-tunnel] destination-zone local

[DeviceB-security-policy-ip-13-tunnel] destination-zone untrust

[DeviceB-security-policy-ip-13-tunnel] quit

[DeviceB-security-policy-ip] quit

Verifying the configuration

# Display tunnel interface information on Device A.

[DeviceA] display interface tunnel 0

Tunnel0

Current state: UP

Line protocol state: UP

Description: Tunnel0 Interface

Bandwidth: 64kbps

Maximum transmission unit: 1476

Internet address: 10.1.2.1/24 (primary)

Tunnel source 1.1.1.1, destination 2.2.2.2

Tunnel keepalive disabled

Tunnel TTL 255

Tunnel protocol/transport GRE/IP

GRE key disabled

Checksumming of GRE packets disabled

Last clearing of counters: Never

Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Input: 0 packets, 0 bytes, 0 drops

Output: 0 packets, 0 bytes, 0 drops

# Display tunnel interface information on Device B.

[DeviceB] display interface tunnel 0

Tunnel0

Current state: UP

Line protocol state: UP

Description: Tunnel0 Interface

Bandwidth: 64kbps

Maximum transmission unit: 1476

Internet address: 10.1.2.2/24 (primary)

Tunnel source 2.2.2.2, destination 1.1.1.1

Tunnel keepalive disabled

Tunnel TTL 255

Tunnel protocol/transport GRE/IP

GRE key disabled

Checksumming of GRE packets disabled

Last clearing of counters: Never

Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec

Input: 0 packets, 0 bytes, 0 drops

Output: 0 packets, 0 bytes, 0 drops

# From Device B, ping the IP address of GigabitEthernet 1/0/1 on Device A.

[DeviceB] ping -a 10.1.3.1 10.1.1.1

Ping 10.1.1.1 (10.1.1.1) from 10.1.3.1: 56 data bytes, press CTRL_C to break

56 bytes from 10.1.1.1: icmp_seq=0 ttl=255 time=11.000 ms

56 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=0.000 ms

56 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=0.000 ms

56 bytes from 10.1.1.1: icmp_seq=4 ttl=255 time=0.000 ms

--- Ping statistics for 10.1.1.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/2.400/11.000/4.317 ms

The output shows that Device B can successfully ping Device A.

Example: Configuring an IPv4 over IPv6 GRE tunnel

Network configuration

As shown in Figure 8, two IPv4 subnets Group 1 and Group 2 are connected to an IPv6 network. Create a GRE/IPv6 tunnel between Device A and Device B, so the two IPv4 subnets can communicate with each other through the GRE tunnel over the IPv6 network.

Figure 8 Network diagram

‌

Procedure

1. Assign IP addresses to interfaces and configure routes, security zones, zone pairs, and interzone policies. Make sure the network connections are available. (Details not shown.)

2. Configure Device A:

# Create tunnel interface Tunnel 0, and specify the tunnel mode as GRE/IPv6.

<DeviceA> system-view

[DeviceA] interface tunnel 0 mode gre ipv6

# Configure an IP address for the tunnel interface.

[DeviceA-Tunnel0] ip address 10.1.2.1 255.255.255.0

# Configure the source address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device A.

[DeviceA-Tunnel0] source 2002::1:1

# Configure the destination address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device B.

[DeviceA-Tunnel0] destination 2001::2:1

[DeviceA-Tunnel0] quit

# Configure a static route from Device A through the tunnel interface to Group 2.

[DeviceA] ip route-static 10.1.3.0 255.255.255.0 tunnel 0

# Add tunnel interface Tunnel 0 to security zone Untrust.

[DeviceA] security-zone name Untrust

[DeviceA-security-zone-Untrust] import interface Tunnel 0

[DeviceA-security-zone-Untrust] quit

# Allow bidirectional traffic communication between security zones Untrust and Local.

[DeviceA] security-policy ip

[DeviceA-security-policy-ip] rule name tunnel

[DeviceA-security-policy-ip-13-tunnel] source-zone untrust

[DeviceA-security-policy-ip-13-tunnel] source-zone local

[DeviceA-security-policy-ip-13-tunnel] destination-zone local

[DeviceA-security-policy-ip-13-tunnel] destination-zone untrust

[DeviceA-security-policy-ip-13-tunnel] quit

[DeviceA-security-policy-ip] quit

3. Configure Device B:

# Create tunnel interface Tunnel 0, and specify the tunnel mode as GRE/IPv6.

<DeviceB> system-view

[DeviceB] interface tunnel 0 mode gre ipv6

# Configure an IP address for the tunnel interface.

[DeviceB-Tunnel0] ip address 10.1.2.2 255.255.255.0

# Configure the source address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device B.

[DeviceB-Tunnel0] source 2001::2:1

# Configure the destination address of the tunnel interface as the IP address of GigabitEthernet 1/0/2 on Device A.

[DeviceB-Tunnel0] destination 2002::1:1

[DeviceB-Tunnel0] quit

# Configure a static route from Device B through the tunnel interface to Group 1.

[DeviceB] ip route-static 10.1.1.0 255.255.255.0 tunnel 0

# Add tunnel interface Tunnel 0 to security zone Untrust.

[DeviceB] security-zone name Untrust

[DeviceB-security-zone-Untrust] import interface Tunnel 0

[DeviceB-security-zone-Untrust] quit

# Allow bidirectional traffic communication between security zones Untrust and Local.

[DeviceB] security-policy ip

[DeviceB-security-policy-ip] rule name tunnel

[DeviceB-security-policy-ip-13-tunnel] source-zone untrust

[DeviceB-security-policy-ip-13-tunnel] source-zone local

[DeviceB-security-policy-ip-13-tunnel] destination-zone local

[DeviceB-security-policy-ip-13-tunnel] destination-zone untrust

[DeviceB-security-policy-ip-13-tunnel] quit

[DeviceB-security-policy-ip] quit

Verifying the configuration

# Display tunnel interface information on Device A.

[DeviceA] display interface tunnel 0

Tunnel0

Current state: UP

Line protocol state: UP

Description: Tunnel0 Interface

Bandwidth: 64kbps

Maximum transmission unit: 1456

Internet address: 10.1.2.1/24 (primary)

Tunnel source 2002::1:1, destination 2001::2:1

Tunnel TTL 255

Tunnel protocol/transport GRE/IPv6

GRE key disabled

Checksumming of GRE packets disabled

Last clearing of counters: Never

Last 300 seconds input rate: 1 bytes/sec, 8 bits/sec, 0 packets/sec

Last 300 seconds output rate: 1 bytes/sec, 8 bits/sec, 0 packets/sec

Input: 10 packets, 840 bytes, 0 drops

Output: 10 packets, 840 bytes, 0 drops

# Display tunnel interface information on Device B.

[DeviceB] display interface tunnel 0

Tunnel0

Current state: UP

Line protocol state: UP

Description: Tunnel0 Interface

Bandwidth: 64kbps

Maximum transmission unit: 1456

Internet address: 10.1.2.2/24 (primary)

Tunnel source 2001::2:1, destination 2002::1:1

Tunnel TTL 255

Tunnel protocol/transport GRE/IPv6

GRE key disabled

Checksumming of GRE packets disabled

Last clearing of counters: Never

Last 300 seconds input rate: 1 bytes/sec, 8 bits/sec, 0 packets/sec

Last 300 seconds output rate: 1 bytes/sec, 8 bits/sec, 0 packets/sec

Input: 10 packets, 840 bytes, 0 drops

Output: 10 packets, 840 bytes, 0 drops

# From Device B, ping the IP address of GigabitEthernet 1/0/1 on Device A.

[DeviceB] ping -a 10.1.3.1 10.1.1.1

Ping 10.1.1.1 (10.1.1.1) from 10.1.3.1: 56 data bytes, press CTRL_C to break

56 bytes from 10.1.1.1: icmp_seq=0 ttl=255 time=2.000 ms

56 bytes from 10.1.1.1: icmp_seq=1 ttl=255 time=1.000 ms

56 bytes from 10.1.1.1: icmp_seq=2 ttl=255 time=1.000 ms

56 bytes from 10.1.1.1: icmp_seq=3 ttl=255 time=0.000 ms

56 bytes from 10.1.1.1: icmp_seq=4 ttl=255 time=1.000 ms

--- Ping statistics for 10.1.1.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.000/1.000/2.000/0.632 ms

The output shows that Device B can successfully ping Device A.

Troubleshooting GRE

The key to configuring GRE is to keep the configuration consistent. Most faults can be located by using the debugging gre or debugging tunnel command. This section analyzes one type of fault for illustration, with the scenario shown in Figure 9.

Figure 9 Network diagram

‌

Hosts at both ends of a GRE tunnel cannot ping each other

Symptom

The interfaces at both ends of the tunnel are configured correctly and can ping each other, but Host A and Host B cannot ping each other.

Solution

To resolve the issue:

1. Execute the display ip routing-table command on Device A and Device C to view whether Device A has a route over tunnel 0 to 10.2.0.0/16 and whether Device C has a route over tunnel 0 to 10.1.0.0/16.

2. If such a route does not exist, execute the ip route-static command in system view to add the route. Take Device A as an example:

[DeviceA] ip route-static 10.2.0.0 255.255.0.0 tunnel 0

3. If the issue persists, contact H3C Support.

Configuring GRE P2MP tunnels

About GRE P2MP tunnels

The GRE point-to-multipoint (P2MP) tunnel technology allows the device to use a GRE P2MP tunnel interface to establish a tunnel with multiple destinations.

Application scenario

As shown in Figure 10, an enterprise has multiple branches. For the headquarters to communicate with the branches through tunnels, you can deploy GRE P2MP.

Configure a GRE P2MP tunnel interface on the gateway of the headquarters. Configure GRE/IPv4 or GRE/IPv6 tunnel interfaces (also called point-to-point GRE tunnel interfaces) on the gateways of the branch networks. Use the GRE P2MP tunnel interface on the headquarters gateway to set up a point-to-multipoint tunnel with the point-to-point GRE tunnel interfaces on the branch gateways.

Figure 10 GRE P2MP tunnel application

‌

Benefits

Compared with GRE point-to-point tunnels and other dynamic VPN technologies, GRE P2MP has the following benefits:

· Simplified configuration—One GRE P2MP tunnel interface can set up a point-to-multipoint tunnel with multiple point-to-point GRE tunnel interfaces. You do not need to create multiple GRE tunnel interfaces for the headquarters gateway to establish point-to-point tunnels with each branch.

· Good interoperability and decreased TCO—The device implements GRE P2MP based on the standard GRE protocol. It does not require other proprietary protocols. GRE P2MP does not have special requirements for the branch gateways. You can use any devices that support GRE as branch gateways.

Working mechanisms

GRE uses the same packet encapsulation and de-encapsulation processes for point-to-multipoint and point-to-point tunnels.

When the device uses a GRE P2MP tunnel to forward traffic, it searches the tunnel entries for the tunnel destination address based on the packet destination IP address. GRE encapsulates the tunnel destination address as the destination IP address in the GRE transport protocol header.

Restrictions: Hardware compatibility with GRE P2MP tunnels

Hardware	GRE P2MP tunnel compatibility
F1000-A-G3, F1000-C-G3, F1000-E-G3, F1000-S-G3	Yes
F100-A-G3, F100-E-G3	Yes
F100-C-G3, F100-M-G3, F100-S-G3	No
F1000-E-VG	Yes
F1000-S-VG	No
F1000-A-G2, F1000-C-G2, F1000-E-G2, F1000-S-G2	Yes
F100-A-G2, F100-E-G2	Yes
F100-C-G2, F100-M-G2, F100-S-G2	No
F1000-C-EI, F100-A-EI, F100-A-SI, F100-E-EI	Yes
F100-C-EI	No
F100-A80-WiNet	Yes
F100-C80-WiNet, F100-C60-WiNet, F100-C50-WiNet, F100-S80-WiNet	No
F1000-C8180, F1000-C8170, F1000-C8160	Yes
F1000-C8150, F1000-C8130, F1000-C8120, F1000-C8110	No
F100-C-A6, F100-C-A5, F100-C-A3	No
F100-C-A6-WL, F100-C-A5-W, F100-C-A3-W	No
F1000-C-HI, F100-A-HI	Yes
F100-C-HI, F100-S-HI	No
F1000-990-AI, F1000-980-AI, F1000-970-AI, F1000-960-AI, F1000-950-AI, F1000-930-AI, F1000-920-AI	Yes
LSPM6FWD8, LSQM2FWDSC8	No

‌

Restrictions and guidelines: GRE P2MP tunnel configuration

For more information about the interface tunnel, source, and tunnel discard ipv4-compatible-packet commands and additional configuration commands on a tunnel interface, see "Configuring tunneling" and tunneling commands in VPN Command Reference.

Restrictions and guidelines for the headquarters end of a P2MP tunnel

When you configure the headquarters end of a P2MP tunnel, follow these restrictions and guidelines:

· Do not configure the same tunnel source address for multiple P2MP tunnel interfaces on the gateway.

· Do not configure the same tunnel source and destination addresses for a GRE P2MP tunnel interface and a GRE tunnel interface.

· Do not configure a GRE key on a GRE P2MP tunnel interface.

Restrictions and guidelines for the branch ends of a P2MP tunnel

The branch networks cannot communicate with one another. They do not have tunnels to reach one another.

When you configure the branch ends of a P2MP tunnel, follow these restrictions and guidelines:

· The tunnel destination address at each branch end must be the tunnel source address of the P2MP tunnel interface on the headquarters.

· On each gateway, the IP address of the tunnel interface and the tunnel destination address configured on the tunnel interface must be in different subnets.

Restrictions and guidelines for all ends of a P2MP tunnel

The following restrictions and guidelines apply to all ends of a P2MP tunnel:

· Configure routes reaching the destination networks through the local tunnel interface. You can configure the routes by using one of the following methods:

¡ Configure static routes, using the local tunnel interface as the outgoing interface of the routes.

¡ Enable a dynamic routing protocol on both the tunnel interface and the interface connecting the private network. This allows the dynamic routing protocol to establish routing entries with the tunnel interface as the outgoing interface.

Configuring a GRE P2MP tunnel interface

1. Enter system view.

system-view

2. Create a GRE P2MP tunnel template and enter its view.

gre p2mp-template template-name

3. Configure a tunnel mapping entry.

map [ vpn-instance vpn-instance-name ] branch-network-address branch-network-address { mask | mask-length } tunnel-destination tunnel-dest-address [ checksum-fill checksum-value ]

By default, no tunnel mapping entries are configured for a GRE P2MP tunnel template.

Specify the checksum-fill checksum-value option depending on your network. The option might cause GRE checksum failures.

4. Return to system view.

quit

5. Create a GRE P2MP tunnel interface and enter its view.

interface tunnel interface-number mode gre-p2mp

The other end of a GRE P2MP tunnel interface must be a GRE/IPv4 tunnel interface.

6. Configure an IPv4 address for the tunnel interface.

For information about how to assign an IPv4 address to an interface, see IP addressing in Layer 3—IP Services Configuration Guide.

By default, no IPv4 address is configured for a tunnel interface.

7. Configure a source IP address or source interface for the tunnel interface.

source { ipv4-address | interface-type interface-number }

By default, no source IP address or interface is configured for a tunnel interface.

If you configure a source IP address for a tunnel interface, the tunnel interface uses the source IP address as the source IP address of the encapsulated packets.

If you configure a source interface for a tunnel interface, the tunnel interface uses the primary IP address of the source interface as the source IP address of the encapsulated packets.

8. Apply the GRE P2MP tunnel template to the tunnel interface.

gre p2mp-template template-name

By default, no GRE P2MP tunnel template is applied to a GRE P2MP tunnel interface.

You must specify an existing GRE P2MP tunnel template for this command.

9. (Optional.) Enable GRE checksum.

gre checksum

By default, GRE checksum is disabled.

10. (Optional.) Configure the preference of static routes issued by the tunnel mapping entries in the GRE P2MP tunnel template.

tunnel route-static [ preference preference-value ]

By default, the preference is 60.

Display and maintenance commands for GRE P2MP tunnels

Execute display commands in any view and reset commands in user view.

Task	Command
Display packet statistics of static tunnel entries for a GRE P2MP tunnel interface.	display gre p2mp tunnel-table statistics interface tunnel number [ vpn-instance vpn-instance-name ] [ branch-network-address branch-network-address { mask \| mask-length } ]
Clear packet statistics of static tunnel entries for a GRE P2MP tunnel interface.	reset gre p2mp tunnel-table statistics interface tunnel number [ vpn-instance vpn-instance-name ] [ branch-network-address branch-network-address { mask \| mask-length } ]

06-VPN Configuration Guide

Configuring GRE

About GRE

GRE key

GRE checksum

Enlarging network scope

Constructing VPN

Operating with IPsec

Protocols and standards

Configuring a GRE/IPv4 tunnel

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

About this task

Procedure

Display and maintenance commands for GRE

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Troubleshooting GRE

Symptom

Solution

Restrictions and guidelines: GRE P2MP tunnel configuration

Restrictions and guidelines for the headquarters end of a P2MP tunnel

Restrictions and guidelines for the branch ends of a P2MP tunnel

Restrictions and guidelines for all ends of a P2MP tunnel

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us