R3303-HP HSR6800 Routers MPLS Configuration Guide

ManualsBrandsHP ManualsNetwork HardwareHP HSR6804 Router Chassis

the MTU of each IS-IS enabled interface to be equal to or greater than 512 bytes to guarantee that IS-IS

LSPs can be flooded on the network.

IS-IS TE does not support secondary IP address advertisement. With IS-IS TE enabled on an interface

configured with multiple IP addresses, IS-IS TE advertises only the primary IP address of the interface

through the sub-TLV of IS reachability TLV (type 22). HP recommends that you avoid enabling IS-IS TE on

an interface configured with secondary IP addresses.

For more information about IS-IS, see Layer 3—IP Routing Configuration Guide.

To configure IS-IS TE:

Ste

Command

Remarks

1. Enter system view.

system-view N/A

2. Enter IS-IS view.

isis [ process-id ] N/A

3. Configure the wide metric

attribute of IS-IS.

cost-style { narrow | wide |

wide-compatible | { compatible |

narrow-compatible }

[ relax-spf-limit ] }

By default, IS-IS uses narrow metric

style.

4. Enable IS-IS TE.

traffic-eng [ level-1 | level-2 |

level-1-2 ]

Disabled by default.

5. Configure the TLV type of the

sub-TLV carrying DS-TE

parameters.

te-set-subtlv { bw-constraint value

| lo-multiplier value |

unreserved-bw-sub-pool value }

Optional.

By default, the bw-constraint

parameter is carried in sub-TLV

252, the lo-multiplier parameter in

sub-TLV 253, and the

unreserved-bw-sub-pool

parameter in sub-TLV 251.

Configuring an MPLS TE explicit path

An explicit path is a set of nodes. The relationship between any two neighboring nodes on an explicit

path can be either strict or loose.

• Strict—The two nodes are directly connected.

• Loose—The two nodes have devices in between.

When inserting nodes to an explicit path or modifying nodes on it, you can configure the include

keyword to have the established LSP traverse the specified nodes or the exclude keyword to have the

established LSP bypass the specified nodes.

When establishing an MPLS TE tunnel between areas or ASs, use a loose explicit route, specify the ABR

or ASBR as the next hop of the route, and make sure the tunnel's ingress node and the ABR or ASBR can

reach each other.

To configure an MPLS TE explicit path:

Ste

Command

Remarks

1. Enter system view.

system-view N/A

2. Create an explicit path for

MPLS TE tunneling and enter

its view.

explicit-path path-name [ disable |

enable ]

N/A