Forwarding Traffic Along Mpls Te Tunnels Through Automatic Route Advertisement - HP HSR6800 Configuration Manual

Step
1. Enter system view.
2. Create and enter the view
of an advanced IPv4 ACL.
3. Define an ACL rule.
4. Return to system view.
5. Create a policy node and
enter policy-based-route
view.
6. Reference the ACL that
target traffic should match.
7. Specify the output
interface to be the tunnel
interface.
8. Return to system view.
9. Enable policy based
routing.
For more information about configuring policy routing, see ACL and QoS Command Reference and
the Layer 3—IP Routing Command Reference.
Forwarding traffic along MPLS TE tunnels through automatic
route advertisement
Two methods, IGP shortcut and forwarding adjacency, are available to automatically advertise MPLS
TE tunnel interface routes to IGPs, allowing traffic to be routed down MPLS TE tunnels.
You can assign a metric, either absolute or relative, to TE tunnels for the purpose of path calculation
in either methods. If it is absolute, the metric is directly used for path calculation. If it is relative, the
cost of the corresponding IGP path must be added to the metric before it can be used for path
calculation.
Enable OSPF or IS-IS on the tunnel interface of the MPLS TE tunnel before configuring automatic
route advertisement.
To use automatic route advertisement, specify the destination address of the TE tunnel as the LSR
ID of the peer and advertise the tunnel interface address to IGPs, such as OSPF and ISIS.
Configuring an IGP shortcut
Command
system-view
acl number acl-number [ match-order { auto |
config } ]
rule [ rule-id ] { deny | permit } protocol
[ destination { dest-addr dest-wildcard | any } |
destination-port operator port1 [ port2 ] | dscp
dscp | established | fragment | icmp-type
{ icmp-type icmp-code | icmp-message } |
logging | precedence precedence | reflective |
source { sour-addr sour-wildcard | any } |
source-port operator port1 [ port2 ] |
time-range time-name | tos tos | vpn-instance
vpn-instance-name ] *
quit
policy-based-route policy-name { permit |
deny } node node-number
if-match acl acl-number
apply output-interface tunnel number1
[ tunnel number2 ]
quit
•
Enable local policy based routing:
ip local policy-based-route policy-name
•
Enable policy based routing for an
interface:
a. interface interface-type
interface-number
b. ip policy-based-route policy-name
68
Remarks
N/A
The default ACL rule
match order is
config.
N/A
N/A
You can create
multiple policy nodes
in one policy.
N/A
N/A
N/A
Use one of the
methods.