Configure Mpls Rsvp-Te Add Ero - Extreme Networks ExtremeWare Command Reference Manual

MPLS Commands—BlackDiamond Switch Only

configure mpls rsvp-te add ero

configure mpls rsvp-te path <path_name> add ero [ipaddress
<ipaddress/masklength> | <host_name>] {strict | loose} {order <number>}
Description
Adds an RSVP-TE explicit route.
Syntax Description
path_name Specifies the path name.
ipaddress/masklength Specifies an LSR using either a /32 address, which may represent an LSR router ID,
loopback address, or direct router interface, or an IP prefix, which represents a directly
connected subnet.
strict Specifies a strict subobject.
loose Specifies a loose subobject.
order <number> Specifies the LSR path order.
Default
N/A
Usage Guidelines
This command adds an IP address to the explicit route object (ERO) for the specified path name. The
RSVP-TE routed path may be described by a configured sequence of the LSRs and/or subnets traversed
by the path. Each defined LSR or subnet represents an ERO subobject. Up to 64 subobjects can be added
to each path name.
When specifying an LSR using the
configured so that the
<host_name>
identifies an LSR using either a /32 address, which may represent an LSR router ID, loopback address,
or direct router interface, or an IP prefix, which represents a directly connected subnet. Each IP address
or prefix is included in the ERO as an IPv4 subobject. Each specified subobject must be topologically
adjacent to the next subobject, as listed in the ERO. If the subobject matches a direct router interface or a
directly attached subnet, the switch verifies that the path message is received on the matching router
interface. If the LSR specified matches the OSPF router ID or a configured loopback IP address, the
router interface on which the packet is received is ignored.
If the IP address is specified as
previous subobject as listed in the ERO. If the IP address is specified as
required to be topologically adjacent to the previous subobject as listed in the ERO. If omitted, the
default subobject attribute is
subobject.
If the subobject matches a direct router interface or a directly attached subnet, the switch verifies that
the path message is received on the matching router interface. If the LSR specified matches the OSPF
1. The LSP next hop matches either the interface IP address or the OSPF router-id of the immediate neighbor
LSR.
2544
parameter, the DNS client on the switch must be
<host_name>
can first be resolved to an IP address. The
, the strict subobject must be topologically
strict
. Each IP address or prefix is included in the ERO as an IPv4
strict
keyword
ipaddress
1
adjacent to the
, the loose subobject is not
loose
ExtremeWare 7.7 Command Reference Guide