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

14
Encapsulation is TUNNEL, service-loopback-group ID not set.
Tunnel source 2002::2:1, destination 2002::1:1
Tunnel protocol/transport GRE/IPv6
GRE key disabled
Checksumming of GRE packets disabled
Output queue : (Urgent queuing : Size/Length/Discards) 0/100/0
Output queue : (Protocol queuing : Size/Length/Discards) 0/500/0
Output queue : (FIFO queuing : Size/Length/Discards) 0/75/0
Last clearing of counters: Never
Last 300 seconds input: 0 bytes/sec, 0 packets/sec
Last 300 seconds output: 0 bytes/sec, 0 packets/sec
10 packets input, 840 bytes
0 input error
10 packets output, 840 bytes
0 output error
# From Device B, you can ping the IP address of GigabitEthernet 1/1 on Device A.
[DeviceB] ping 10.1.1.1
PING 10.1.1.1: 56 data bytes, press CTRL_C to break
Reply from 10.1.1.1: bytes=56 Sequence=1 ttl=255 time=3 ms
Reply from 10.1.1.1: bytes=56 Sequence=2 ttl=255 time=2 ms
Reply from 10.1.1.1: bytes=56 Sequence=3 ttl=255 time=2 ms
Reply from 10.1.1.1: bytes=56 Sequence=4 ttl=255 time=2 ms
Reply from 10.1.1.1: bytes=56 Sequence=5 ttl=255 time=3 ms
--- 10.1.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 2/2/3 ms
Troubleshooting GRE
The key to configuring GRE is to keep the configurations 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 10 .
Figure 10 Troubleshoot GRE
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.