Configuring Pbr To Direct Traffic To An Mpls Te Tunnel Or Tunnel Bundle; Configuring Automatic Route Advertisement To Direct Traffic To An Mpls Te Tunnel Or Tunnel Bundle - HP MSR2000 Configuration Manual

Configuring PBR to direct traffic to an MPLS TE tunnel or tunnel
bundle
For more information about the commands in this task, see Layer 3—IP Routing Command Reference.
To configure PBR to direct traffic to an MPLS TE tunnel or tunnel bundle:
Step
1. Enter system view.
2. Create a PBR policy node
and enter policy node view.
Configure an ACL match
3.
criterion.
4. Specify a tunnel interface or a
tunnel bundle interface as the
packet output interface.
5. Return to system view.
6. Apply the PBR policy.
Configuring automatic route advertisement to direct traffic to an
MPLS TE tunnel or tunnel bundle
You can use either IGP shortcut or forwarding adjacency to implement automatic route advertisement.
When you use IGP shortcut, you can specify a metric for the TE tunnel or the tunnel bundle. If you assign
an absolute metric, the metric is directly used as the MPLS TE tunnel's or tunnel bundle's metric. If you
assign a relative metric, the MPLS TE tunnel or tunnel bundle's metric is the assigned metric plus the IGP
link metric.
Before configuring automatic route advertisement, perform the following tasks:
Enable OSPF or IS-IS on the tunnel interface or tunnel bundle interface to advertise the tunnel
•
interface address (or the tunnel bundle interface address) to OSPF or IS-IS.
Enable MPLS TE for an OSPF area or an IS-IS process by executing the mpls te enable command in
•
OSPF area view or IS-IS view.
Follow these restrictions and guidelines when you configure automatic route advertisement:
The destination address of the MPLS TE tunnel or tunnel bundle can be the LSR ID of the egress node
•
or the primary IP address of an interface on the egress node. HP recommends configuring the
destination address of the MPLS TE tunnel or tunnel bundle as the LSR ID of the egress node.
• If you configure the tunnel destination address as the primary IP address of an interface on the
egress node, you must enable MPLS TE, and configure OSPF or IS-IS on that interface. This makes
sure the primary IP address of the interface can be advertised to its peer.
Command
system-view
policy-based-route policy-name [ deny |
permit ] node node-number
if-match acl { acl-number | name acl-name }
apply output-interface { { tunnel
tunnel-number | tunnel-bundle number }
[ track track-entry-number ] }&<1-2>
quit
•
To apply the policy to the local device:
ip local policy-based-route policy-name
•
To apply the policy to an interface:
a. interface interface-type
interface-number
b. ip policy-based-route policy-name
78
Remarks
N/A
By default, no PBR policy
node is created.
By default, no ACL match
criterion is configured.
N/A
N/A
By default, no policy is
applied.