Configure Mpls Rsvp-Te Profile - Extreme Networks ExtremeWare Command Reference Manual

MPLS Commands—BlackDiamond Switch Only

configure mpls rsvp-te profile

configure mpls rsvp-te profile <profile_name> {bandwidth <bps>}
{setup-priority <priority>} {hold-priority <priority>} {retry-timeout
<seconds>} {hop-count <number>} {ping-interval <seconds>} {metric [<metric>
| igp-tracking} {record [enabled | disabled]} {mtu <number>}
Description
Configures an existing RSVP-TE profile.
Syntax Description
profile_name Specifies the profile name.
bandwidth Specifies the reserved bandwidth for the LSP.
setup-priority A value that is compared to the hold-priority of existing LSPs to determine if any of the existing
LSPs need to be preempted to allow a higher priority LSP to be established.
hold-priority A value that is compared to the setup-priority of existing LSPs to determine if any of the
existing LSPs need to be preempted to allow a higher priority LSP to be established.
retry-timeout Specifies the maximum number of seconds the switch allows for LSP setup.
ping-interval Specifies how frequently an ICMP echo request is transmitted to the egress LSR IP address on
the established LSP.
metric Specifies a route metric used to determine if an established RSVP-TE LSP will actually be
used to send data.
record Specifies hop-by-hop path recording.
mtu Specifies the MTU value transport payload packet (customer packet).
Default
N/A
Usage Guidelines
This command configures RSVP-TE attributes for the specified profile. The
been previously added. All of the LSP profile values are updated dynamically. For LSPs configured with
this profile, the LSP parameters are updated automatically with the sending of the next refresh path
message. If the metric is changed, all LSPs using this profile are rechecked against the calculated IGP
metric. In some cases, the LSP may be torn down because of a profile configuration change. For
example, if the bandwidth value is increased, the LSRs along the existing path may not be able to
accommodate the additional reserved bandwidth. In this scenario, the LSP is torn down and signaled
again.
The mtu keyword optionally specifies the MTU value transport payload packet (customer packet). The
mtu value is exchanged with vpls configured peer nodes. All VPLS peer nodes must be configured with
the same mtu value. If the mtu values do not match, VC-LSPs cannot be established between VPLS
peers. By default the VPLS mtu is set to 1500. The configurable mtu range is 1492 through 9216.
Changing the mtu setting will cause established VC-LSPs to terminate. VPLS payload packets may be
dropped if the VPLS MTU setting is greater than the MPLS MTU setting for the VC-LSP interface. The
vplsping command may be used to verify end-to-end path connectivity for specific payload packet
sizes.
2474
must have
<profile_name>
ExtremeWare 7.5 Command Reference Guide