Extreme Networks BlackDiamond 6800 MPLS, Installation And User Manual

Page: 94 / 176

5-20 MPLS Module Installation and User Guide
Configuring RSVP-TE
follows. Thus, the LSP path follows the configured path of the IP prefix with the order
value from low to high. If the
order
keyword is not specified, the number value for the
LSR defaults to a value 100 higher than the current highest number value.
If the list of IP prefixes, added to the path, does not reflect an actual path through the
network topology, the path message is returned with an error from a downstream LSR
and the LSP is not established.
The order of a configured subobject can not be changed. The ERO subobject must be
deleted and re-added using a different order. If a subobject is added to or deleted from
the ERO while the associated LSP is established, the path is torn down and is resignaled
using the new ERO.
Duplicate ERO subobjects are not allowed. Defining an ERO for the path is optional. If
you do not configure an ERO, the path is signaled along the best-routed path and the
ERO is not included in the path message. When the last subobject in the ERO of the
path message is reached and the egress IP node of the path has not been reached, the
remaining path to the egress node is signaled along the best-routed path. Specification
of an ERO could lead to undesirable routed paths, so you should be careful when
terminating the ERO routed-path definition prior to the configured path egress node.
To delete an RSVP-TE explicit route, use the following command:
config mpls rsvp-te path <path_name> delete ero [all | ipaddress
<ipaddress/masklength> | <host_name> | order <number>]
This command deletes an LSR or subnet from the ERO for the specified path name. The
LSR is specified using the
ipaddress
,
<host_name>
, or
order
parameter. If an LSR is
deleted from an ERO while the associated LSP is established, the path is torn down and
is resignaled using a new ERO. Use the
all
keyword to delete the entire ERO from the
path name. When there is no configured ERO, the path is no longer required to take an
explicit routed path. The path is then signaled along the best-routed path and no ERO is
included in the path message.
Configuring an RSVP-TE Profile
To add an RSVP-TE profile, use the following command:
config mpls rsvp-te add profile <profile_name> {bandwidth <bps>}
{hop-count <number>} {setup-priority <priority>} {hold-priority <priority>}
{retry-timeout <seconds>} {ping-interval <seconds>} {metric [<metric> |
igp-tracking]} {record [enabled | disabled]}