H3C S9500 Series Operation Manual page 168

Operation Manual – Tunneling
H3C S9500 Series Routing Switches
To do...
Define a ACL rule
Define a class and
enter class view
Define the packet
matching rule
Define a traffic
behavior and enter
traffic behavior view
Configure the traffic
redirection action for
the traffic behavior
Configure a service
loopback group ID to
be referenced by the
tunnel interface
Enable the expedite
termination function
Caution:
If the tunnel interface addresses at the two ends of a tunnel are not in the same
network segment, a forwarding route through the tunnel to the peer must be
configured so that the encapsulated packet can be forwarded. You can configure
static or dynamic routes. A forwarding route needs to be configured at both ends of
the tunnel. For the detailed configuration, refer to the IP Routing Volume.
Two or more tunnel interfaces using the same encapsulation protocol must have
different source and destination addresses.
If the tunnel interface is the source interface, the tunnel source address is the
primary IP address of the source interface.
Use the command...
rule [ rule-id ] { permit | deny }
protocol [ rule-string ]
traffic classifier tcl-name
[ operator { and | or } ]
if-match [ not ] match-criteria
traffic behavior behavior-name
redirect { cpu | interface
interface-type interface-number |
link-aggregation group
aggregation-group-id | next-hop
{ ipv4-add [ ipv4-add ] | ipv6-add
[ interface-type interface-number ]
[ ipv6-add [ interface-type
interface-number ] ] } }
aggregation-group
aggregation-group-id
expediting enable
1-37
Chapter 1 Tunneling Configuration
Remarks
Required
Required
Required
Required
Required
Required
Optional
By default, the
expedite termination
function is disabled.