Alcatel-Lucent 7450 Configuration Manual page 130

Router Global Commands
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference]
[metric metric] [tag tag] [community comm-id] [enable | disable] black-hole [mcast-
family] {prefix-list prefix-list-name [all | none]}
Context config>router
Description This command creates static route entries for both the network and access routes.
When configuring a static route, either next-hop, indirect or black-hole must be configured.
The no form of the command deletes the static route entry. If a static route needs to be removed when
multiple static routes exist to the same destination, then as many parameters to uniquely identify the
static route must be entered.
If a CPE connectivity check target address is already being used as the target address in a different
static route, then cpe-check parameters must match. If they do not, the new configuration command
will be rejected.
If a static-route command is issued with no cpe-check target but the destination prefix/netmask and
next-hop matches a static route that did have an associated cpe-check, the cpe-check test will be
removed from the associated static route.
Default No static routes are defined.
Parameters ip-prefix/prefix-length — The destination address of the static route.
ip-address — The IP address of the IP interface. The ip-addr portion of the address command
netmask — The subnet mask in dotted decimal notation.
community comm-id — This configuration option associates a BGP community with the static
ldp-sync — Extends the LDP synchronization feature to a static route. When an interface comes
Page 130
Values ipv4-prefix
ipv4-prefix-length
specifies the IP host address that will be used by the IP interface within the subnet. This address
must be unique within the subnet and specified in dotted decimal notation.
Values ipv4-address
Values 0.0.0.0 — 255.255.255.255 (network bits all 1 and host bits all 0)
route. The community can be matched in route policies and is automatically added to BGP routes
exported from the static route.
Values comm-id
asn
comm-val
well-known-comm
back up, it is possible that a preferred static route using the interface as next-hop for a given
prefix is enabled before the LDP adjacency to the peer LSR comes up on this interface. In this
case, traffic on an SDP that uses the static route for the far-end address would be black-holed
until the LDP session comes up and the FECs exchanged.
This option when enabled delays the activation of the static route until the LDP session comes up
over the interface and the ldp-sync-timer configured on that interface has expired.
a.b.c.d (host bits must be 0)
0 — 32
a.b.c.d (host bits must be 0)
asn:comm-val | well-known-comm
0 — 65535
0 — 65535
no-advertise, no-export, no-export-subconfed
7450 ESS Router Configuration Guide