Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
Configuring basic IP routing ··········································································· 1
Routing table ······················································································································································ 1
Dynamic routing protocols·································································································································· 2
Route preference ··············································································································································· 2
Load sharing ······················································································································································ 3
Route backup ····················································································································································· 3
Route recursion ·················································································································································· 3
Route redistribution ············································································································································ 3
Extension attribute redistribution ························································································································ 3
Setting the maximum lifetime for routes and labels in the RIB··········································································· 4
Setting the maximum lifetime for routes in the FIB ···························································································· 4
Configuring RIB NSR ········································································································································· 5
Controlling RIP reception and advertisement on interfaces ····································································· 27
Configuring a RIP version ························································································································ 27
Configuring RIP route control ··························································································································· 28
Configuring an additional routing metric ··································································································· 28
Configuring the RIP packet sending rate ································································································· 36
Setting the maximum length of RIP packets ···························································································· 37
Setting the DSCP value for outgoing RIP packets ··················································································· 37
Configuring RIP GR ········································································································································· 37
Enabling RIP NSR············································································································································ 38
Configuring BFD for RIP ·································································································································· 38
Configuring an additional metric for a RIP interface················································································· 47
Configuring RIP to advertise a summary route ························································································ 48
Configuring RIP GR ································································································································· 51
OSPF areas ············································································································································· 65
DR and BDR ············································································································································ 69
Protocols and standards ·························································································································· 70
OSPF configuration task list ····························································································································· 70
Enabling OSPF ················································································································································ 72
Enabling OSPF on a network ··················································································································· 73
Enabling OSPF on an interface················································································································ 74
Configuring OSPF areas ·································································································································· 74
Configuring a stub area ···························································································································· 74
Configuring an NSSA area ······················································································································· 75
Configuring a virtual link ··························································································································· 75
Configuring OSPF network types ····················································································································· 76
Configuring the broadcast network type for an interface·········································································· 76
Configuring the NBMA network type for an interface ··············································································· 76
Configuring the P2MP network type for an interface················································································ 77
Configuring the P2P network type for an interface··················································································· 78
Configuring OSPF route control ······················································································································· 78
Advertising a host route ··························································································································· 83
Excluding interfaces in an OSPF area from the base topology································································ 83
Tuning and optimizing OSPF networks ············································································································ 84
Configuration procedure ························································································································· 101
Advertising OSPF link state information to BGP ···························································································· 102
Displaying and maintaining OSPF ················································································································· 102
OSPF configuration examples ······················································································································· 104
Basic OSPF configuration example ······································································································· 104
OSPF route redistribution configuration example ·················································································· 106
OSPF route summarization configuration example ················································································ 108
iii
OSPF stub area configuration example ································································································· 111
OSPF NSSA area configuration example ······························································································ 113
OSPF DR election configuration example ······························································································ 115
OSPF virtual link configuration example ································································································ 119
OSPF GR configuration example ··········································································································· 121
IS-IS address format ······························································································································ 133
NET ························································································································································ 134
IS-IS area ··············································································································································· 135
Setting the IS level and circuit level ······································································································· 141
Configuring P2P network type for an interface ······················································································· 141
Configuring IS-IS route control ······················································································································· 142
Configuring a BGP peer group ··············································································································· 211
Specifying the source address of TCP connections ··············································································· 220
Generating BGP routes ·································································································································· 221
Injecting a local network ························································································································· 221
Redistributing IGP routes ······················································································································· 223
Controlling route distribution and reception ··································································································· 224
Setting a preferred value for routes received ························································································· 239
Configuring preferences for BGP routes ································································································ 241
Configuring the default local preference ································································································ 242
Configuring the MED attribute ················································································································ 244
Configuring the NEXT_HOP attribute ···································································································· 248
Configuring the AS_PATH attribute ······································································································· 250
Ignoring IGP metrics during optimal route selection ·············································································· 255
Configuring the SoO attribute ················································································································· 256
Tuning and optimizing BGP networks ············································································································ 258
Configuring the keepalive interval and hold time ··················································································· 258
Configuring the interval for sending updates for the same route ··························································· 259
Enabling BGP to establish an EBGP session over multiple hops ·························································· 260
v
Enabling immediate re-establishment of direct EBGP connections upon link failure ····························· 261
Enabling 4-byte AS number suppression ······························································································· 262
Enabling MD5 authentication for BGP peers ························································································· 263
Enabling keychain authentication for BGP peers ··················································································· 264
Disabling optimal route selection for labeled routes without tunnel information ····································· 277
Configuring a large-scale BGP network ········································································································· 278
Configuring BGP community ·················································································································· 278
Configuring optional 6PE capabilities····································································································· 293
Configuring BGP LS ······································································································································· 295
Configuring basic BGP LS ····················································································································· 295
Configuring BGP LS route reflection ······································································································ 295
Specifying an AS number and a router ID for BGP LS messages ························································· 296
Displaying and maintaining BGP···················································································································· 296
PBR and Track ······································································································································· 359
PBR configuration task list ····························································································································· 359
Configuring a policy········································································································································ 360
Creating a node ······································································································································ 360
Setting match criteria for a node ············································································································ 360
Configuring actions for a node ··············································································································· 361
Specifying a policy for PBR ···························································································································· 361
Specifying a policy for local PBR ··········································································································· 361
Specifying a policy for interface PBR ····································································································· 362
Specifying a policy for outbound PBR on a VXLAN tunnel interface ····················································· 362
Displaying and maintaining PBR ···················································································································· 363
PBR configuration examples ·························································································································· 363
Packet type-based local PBR configuration example ············································································ 363
Packet type-based interface PBR configuration example ······································································ 365
Configuring the OSPFv3 network type for an interface ·········································································· 404
Configuring an NBMA or P2MP neighbor ······························································································ 404
Configuring OSPFv3 route control ················································································································· 405
Configuring an IP prefix list ···················································································································· 476
Configuring an AS path list ····················································································································· 477
Configuring a community list ·················································································································· 477
Configuring an extended community list ································································································ 477
Configuring a routing policy···························································································································· 478
Remote support ······································································································································ 491
Index ·········································································································· 492
x
Configuring basic IP routing
Criterion
Categories
The destination is a netw ork. T he subnet mask i s les s than 32
Whether the
•
•
•
•
IP routing directs IP packet forwarding on routers based on a routing table. This chapter focuses on
unicast routing protoc ols. For more inf ormation about m ulticast routing protoco ls, see IP Multicast Configuration Guide.
Routing table
A RIB contains the global routing information and related information, including route recursion, route
redistribution, and ro ute extension information. The r outer selects optimal routes f rom the routing
table and puts them into the FIB table. It uses the FIB table to forward packets. For more information
about the FIB table, see Layer 3—IP Services Configuration Guide.
Table 1categorizes routes by different criteria.
Table 1 Route categories
•Network route—
Destination
bits.
•Host route—The destination is a host. The subnet mask is 32 bits.
destination is directly
connected
Origin
• Direct route—The destination is directly connected.
• Indirect route—The destination is indirectly connected.
• Direct route—A direct route is discovered by the data link protocol on an
interface, and is also called an interface route.
• Static route—A static route is manually configured by an administrator.
• Dynamic route—A dynamic route is dynamically discovered by a routing
protocol.
To view brief information about a routing table, use the display ip routing-table command.
<Sysname> display ip routing-table
Destinations : 9 Routes : 9
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
3.3.3.3/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0
127.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
...
A route entry includes the following key items:
Destination—IP address of the destination host or network. Mask—Mask length of the IP address. Proto—Protocol that installed the route. Pre—Preference of the route. Among routes to the same destination, the route with the highest
preference is optimal.
1
•
•
•
Criterion
Categories
RIP and BGP. BGP is also
Route type
Preference
Cost—If multiple routes to a destination have the same preference, the one with the smallest
cost is the optimal route.
NextHop—Next hop. Interface—Output interface.
Dynamic routing protocols
Static routes work well in small, stable networks. They are easy to configure and require fewer
system resources. However, in networks where topology changes occur frequently, a typical practice
is to configure a dynamic routing protocol. Compared with static routing, a dynamic routing protocol
is complicated to configure, requires more router resources, and consumes more network resources.
Dynamic routing protocols dynamically collect and report reachability information to adapt to
topology changes. They are suitable for large networks.
Dynamic routing protocols can be classified by different criteria, as shown in Table 2.
Table 2 Categories of dynamic routing protocols
Operation scope
Routing algorithm
Destination address
type
IP version
• IGPs—Work within an AS. Examples includ e RIP, OSPF, and IS-IS.
• EGPs—Work between ASs. The most popular EGP is BGP.
• Distance-vector protocols—Examples include
considered a path-vector protocol.
• Link-state protocols—Examples include OSPF and IS-IS.
• Unicast routing protocols—Examples include RIP, OSPF, BGP, and IS-IS.
• Multicast routing protocols—Examples include PIM-SM and PIM-DM.
• IPv4 routing protocols—Examples include RIP, OSPF, BGP, and IS-IS.
• IPv6 routing protocols—Examples include RIPng, OSPFv3, IPv6 BGP, and
IPv6 IS-IS.
An AS refers to a group of routers that use the sam e routing policy and work under the same
administration.
Route preference
Routing protocols, includ in g stat ic and direc t r out ing, eac h b y defau lt have a preference. If they find
multiple routes to the sam e dest ination, the router selec ts the r oute with the hig hest pref erence as
the optimal route.
The preference of a direct route is always 0 and cannot be changed. Y ou can configure a preference
for each static route and each dynamic routing protocol. The following table lists the route types and
default preferences. The smaller the value, the higher the preference.
RIP 100
OSPF ASE 150
OSPF NSSA 150
IBGP 255
EBGP 255
Unknown (route from an untrusted source) 256
Load sharing
A routing protocol might find multiple optimal equal-cost routes to the same destination. You can use
these routes to implement equal-cost multi-path (ECMP) load sharing.
Static routing, IPv6 static routing, RIP, RIPng, OSPF, OSPFv3, BGP, IP v6 B GP, IS-IS, and IPv6 IS-IS
support ECMP load sharing.
Route backup
Route backup can im prove network availability. Among m ultiple rout es to the s ame destin ation, the
route with the highest priority is the prim ary route and others are secondary routes.
The router forwards m atching p ackets through the prim ary route. W hen the primar y route fails, the
route with the highest preference among the secondary routes is selected to forward packets. When
the primary route recovers, the router uses it to forward packets.
Route recursion
To use a BGP, s tatic , or R I P route that has an ind irec tl y co nnec t ed nex t ho p, a r o uter must perform
route recursion to find the output interface to reach the next hop.
Link-state routing pro tocols, such as O SPF and IS-IS, do not need route rec ursion, because th ey
obtain directly connected next hops through route calculation.
The RIB records and sa ves route recursion informati on, including brief information abo ut related
routes, recursive paths, and recur sion dep th.
Route redistribution
Route redistribution enables routing protocols to learn routing information from each other. A
dynamic routing pr otocol can redistribute routes from other routing protocols, including direct and
static routing. For more inform ation, see the respective c hapters on those ro uting protocols in this
configuration guide.
The RIB records redistribution relationships of routing protocols.
Extension attribute redistribution
Extension attribute redistribution enables routi ng protocols to learn route extension attri butes from
each other, including BGP extended comm unity attributes , OSPF area IDs , route types, and rout er
IDs.
3
The RIB records extended attributes of each routing protocol and redistribution relationships of
Step
Command
Remarks
rib
y default, no RIB IPv4
y default, the maximum
Step
Command
Remarks
y default, no RIB IPv6
y default, the maximum
Step
Command
Remarks
y default, no RIB IPv4
different routing protocol extended attributes.
Setting the maximum lifetime for routes and labels
in the RIB
Perform this task to prevent rout es of a certain protocol from being aged out due to slo w protocol
convergence resulting from a large number of route entries or long GR period.
The configuration takes effect at the next protocol or RIB process switchover.
To set the maximum lifetime for routes and labels in the RIB (IPv4):
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv4 address
family and enter its view.
4. Set the maximum lifetime for
IPv4 routes and labels in the
RIB.
To set the maximum route lifetime for routes and labels in the RIB (IPv6):
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv6 address
family and enter its view.
4. Set the maximum lifetime for
IPv6 routes and labels in the
RIB.
system-view
address-family ipv4
protocol
instance-name ]
system-view
rib
address-family ipv6
protocol
instance-name ]
protocol [
lifetime
protocol [
lifetime
instance
seconds
instance
seconds
N/A
N/A
B
address family exists.
B
lifetime for routes and labels
in the RIB is 480 seconds.
N/A
N/A
B
address family exists.
B
lifetime for routes and labels
in the RIB is 480 seconds.
Setting the maximum lifetime for routes in the FIB
When GR or NSR is disabled, FIB entries m ust be ret ained for s ome tim e after a protoco l proces s
switchover or RIB proces s switcho ver. When GR or NSR is enab led, FIB entri es m ust be removed
immediately after a protocol or RIB pr oc ess switchover to avoi d routing issues. Pe rf orm this task to
meet such requirements.
To set the maximum lifetime for routes in the FIB (IPv4):
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv4 address
family and enter its view.
system-view
rib
address-family ipv4
4
N/A
N/A
B
address family exists.
Step
Command
Remarks
4. Set the maximum lifetime for
y default, the maximum
lifetime for routes in the FIB
Step
Command
Remarks
y default, no RIB IPv6
y default, the maximum
lifetime for routes in the FIB
IMPORTANT:
Use this feature with protocol GR or NSR to avoid route timeouts and traffic interruption.
Step
Command
Remarks
By default, no RIB IPv4
By default, RIB NSR is
Step
Command
Remarks
RIB IPv6
IPv4 routes in the FIB.
To set the maximum lifetime for routes in the FIB (IPv6):
fib lifetime
seconds
B
is 600 seconds.
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv6 address
family and enter its view.
4. Set the maximum lifetime for
IPv6 routes in the FIB.
system-view
rib
address-family ipv6
fib lifetime
Configuring RIB NSR
When an active/standby switchover occurs, nonstop routing (NSR) backs up routing information
from the active process to the standby process to a void routing flapping and ensure forwarding
continuity.
RIB NSR provides faster route convergence than protocol NSR during an active/standby switchover.
Configuring IP v4 RIB NSR
seconds
N/A
N/A
B
address family exists.
B
is 600 seconds.
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv4 address
family and enter its view.
4. Enable IPv4 RIB NSR.
system-view
rib
address-family ipv4
non-stop-routing
Configuring IP v6 RIB NSR
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv6 address
family and enter its view.
system-view
rib
address-family ipv6
5
N/A
N/A
address family exists.
disabled.
N/A
N/A
By default, no
address family exists.
Step
Command
Remarks
4. Enable IPv6 RIB NSR.
By default, RIB NSR is
CAUTION:
This feature
faulty route, which might cause loops.
Step
Command
Remarks
By default, no RIB IPv4
Enable IPv4 RIB
protocol FRR
is enabled for the public
Step
Command
Remarks
By default, no RIB IPv6
Enable IPv6 RIB
protocol FRR
is enabled for the public
non-stop-routing
Configuring inter-protocol FRR
disabled.
uses the next hop of a route from a different protocol as the backup next hop for the
Inter-protocol fast reroute (FRR) enables fast rerouting between routes of different protocols. A
backup next hop is automatically selected to reduce the service interruption time caused by
unreachable next hops. W hen the next hop of the prim ary link fails, the traffic is redirected to the
backup next hop.
Among the routes to the same destination in the RIB, a router adds the route with the highest
preference to the FIB tab le. For example, if a static route and an O SPF route in the RI B have the
same destination, the router adds the OSPF ro ute to the FIB ta ble by default. The next hop of the
static route is selected as the backup next hop for the OSPF route. When the next hop of the OSPF
route is unreachable, the backup next hop is used.
Configuring IP v4 RIB inter-protoc ol FRR
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv4 address
family and enter its view.
system-view
rib
address-family ipv4
N/A
N/A
address family exists.
4.
inter-protocol FRR.
inter-protocol fast-reroute
vpn-instance
[
vpn-instance-name ]
Configuring IP v6 RIB inter-protoc ol FRR
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv6 address
family and enter its view.
4.
inter-protocol FRR.
system-view
rib
address-family ipv6
inter-protocol fast-reroute
vpn-instance
[
vpn-instance-name ]
By default, inter-protocol
FRR is disabled.
If you do not specify a VPN
instance, inter-
network.
N/A
N/A
address family exists.
By default, inter-protocol
FRR is disabled.
If you do not specify a VPN
instance, internetwork.
6
Step
Command
Remarks
Enable the IPv4 enhanced
By default, the IPv4
enhanced ECMP mode is
Task
Command
information about routes
Display information about routes
routing table
Display next hop information in the
Enabling the IPv4 enhanced ECMP mode
When one or multiple ECMP routes fail, the default ECMP mode enables the device to reallocate all
traffic to the remaining routes.
The IPv4 enhanced ECMP mode enables the device to reallocate only the traffic of the failed routes
to the remaining routes, which ensures forwarding continuity.
This configuration takes effect at reboot. Make sure the reboot does not impact your network.
To enable the IPv4 enhanced ECMP mode:
1. Enter system view.
2.
ECMP mode.
system-view
ecmp mode enhanced
N/A
disabled.
Displaying and maintaining a routing table
Execute display commands in any view and reset commands in user view.
Display the IPv4 ECMP mode.
Display routing table information.
Display information about routes
permitted by an IPv4 basic ACL.
Display information about routes to a
specific destination address.
Display information about routes to a
range of destination addresses.
Display
permitted by an IP prefix list.
display ecmp mode
display ip routing-table
verbose ]
[
display ip routing-table [ vpn-instance
ipv4-acl-number [
display ip routing-table
ip-address [ mask-length | mask ] [
display ip routing-table
ip-address1 to ip-address2 [
display ip routing-table [ vpn-instance
prefix-list
prefix-list-name [
verbose ]
vpn-instance
[
vpn-instance
[
longer-match
vpn-instance
[
verbose ]
verbose ]
vpn-instance-name ]
vpn-instance-name ]
vpn-instance-name ]
vpn-instance-name ]
vpn-instance-name ]
verbose ]
] [
acl
installed by a protocol.
Display IPv4 route statistics.
Display brief IPv4
information.
Display route attribute information in
the RIB.
Display RIB GR state information.
RIB.
Display next hop informatio n for direct
routes.
display ip routing-table
protocol
display ip routing-table
statistics
display ip routing-table
summary
display rib attribute
display rib graceful-restart
display rib nib
display rib nib protocol
display route-direct nib
protocol [
7
self-originated
[
[
inactive
[
[
[ attribute-id ]
protocol [
[ nib-id ] [
vpn-instance
verbose ]
|
vpn-instance
vpn-instance
] [ nib-id ] [
verbose ]
verbose ]
vpn-instance-name ]
vpn-instance-name ]
vpn-instance-name ]
verbose
]
Task
Command
Clear IPv4 route statistics.
isplay information about routes to a
information about routes
information about routes
routing table
attribute information in
Display IPv6 RIB GR state
Display next hop information in the
reset ip routing-table statistics protocol [ vpn-instance
vpn-instance-name ] { protocol |
all }
Display IPv6 routing tab le infor mation.
Display information about rout es to an
IPv6 destination address.
Display information about routes
permitted by an IPv6 basic ACL.
Display next hop information for IPv6
direct routes.
Clear IPv6 route statistics.
display ipv6 route-direct nib
reset ipv6 routing-table statistics protocol
vpn-instance-name ] { protocol |
[ nib-id ] [
all }
verbose ]
vpn-instance
[
8
•
•
•
Step
Command
Remarks
system-view
static route group
(Optional.) Add a
the static route
By default, no static route
figure a static
] |
Configuring static routing
Static routes are m anuall y conf igured. If a net work 's topology is sim ple, you only nee d to co nfigure
static routes for the network to work correctly.
Static routes cannot ada pt t o net wor k topology changes. If a fault or a topological change oc c urs in
the network, the network administrator must modify the static routes manually.
Configuring a static route
Before you configure a static route, complete the following tasks:
Configure the physical parameters for related interfaces.
Configure the link-layer attributes for related interfaces.
Configure the IP addresses for related interfaces.
You can associate Track with a static route to m onitor the reachabil ity of the next hops. For m ore
information about Track, see High Availability Configuration Guide.
To configure a static route:
1. Enter system view.
2. (Optional.) Create a
and enter its view.
3.
static route prefix to
group.
4. (Optional.) Return to
system view.
5. Con
route.
ip route-static-group
prefix
dest-address { mask-length | mask }
quit
•Method 1:
ip route-static { dest-address { mask-length
Enabling BFD for a flapping route could worsen the situation.
•
•
Step
Command
Remarks
Configure BFD
Step
Command
Remarks
6. (Optional.)
ip route-static default-preference
for static routes.
7. (Optional.) Delete all
including the default
route.
default-preference
delete [ vpn-instance
static-routes all
vpn-instance-name ]
Configuring BFD for static routes
The default setting is 60.
use the
route-static
command.
BFD provides a general-purpose, standard, medium-, and protocol-independent fast failure
detection mechanis m. It can uniformly and quickly detec t th e failures of the b id ire c tiona l f orwarding
paths between two routers for protocols, such as routing protocols and MPLS.
For more information about BFD, see High Availability Configuration Guide.
Bidirectional c ontrol mode
To use BFD bidirectional control detection between two devices, enable BFD control mode for each
device's static route destined to the peer.
To configure a static route and enable BFD control mode, use one of the following methods:
Specify an output interface and a direct next hop. Specify an indirect next hop and a specific BFD packet source address for the static route.
To configure BFD control mode for a static route (direct next hop):
1. Enter system view.
2.
control mode for a
static route.
To configure BFD control mode for a static route (indirect next hop):
By default, BFD control
mode for a static route
is not configured.
1. Enter system view.
system-view
N/A
10
Step
Command
Remarks
Configure BFD
By default, BFD control
IMPORTANT:
Do not use BFD for a static route with the output interface in spoofing state.
Step
Command
Remarks
Configure the
source address of
, the source
Availability Command
for a static
for a static route is not
•Method 1:
2.
control mode for a
static route.
•Method 2:
Single-hop echo mode
With BFD echo mode enabled for a static route, the output interface sends BFD echo packets to the
destination device, which loops the packets back to test the link reachability.
interface-number next-hop-address bfd
echo-packet [ preference preference ] [ tag
tag-value ] [ description text ]
ip-address
N/A
By default
address of echo packets is
not configured.
For more information a bout
this command, see High
Reference.
By default, BFD echo mode
configured.
11
•
•
•
•
•
•
Step
Command
Remarks
Configure static route
] ] ]
] ] ]
tag
description
By default, static route FRR
Router A
Router BRouter E
Backup nexthop:
Router C
Nexthop:
Router D
Configuring static route FRR
A link or router failure on a path can cause packet loss and even routing loop. Static route fast reroute
(FRR) enables fast rerouting to minimize the impact of link or node failures.
Figure 1 Network diagram
As shown in Figure 1, upon a link failure, packets are directed to the backup next hop to avoid traffic
interruption. Y ou can either specify a backup next hop for FRR or enable FRR to automatically select
a backup next hop (which must be configured in advance).
Configuration guidelines
Do not use static route FRR and BFD (for a static route) at the same time.Static route does not take effect when the backup output interface is unavailable. Equal-cost routes do not support static route FRR. The backup output interface and next hop must be different from the primary output interface
To change the backup output interface or next hop, you must first remove the current setting. Static route FRR is available only when the state of primary link (with Layer 3 interfaces staying
Configuring static route FRR by specifying a backup next hop
1. Enter system view.
2.
and next hop.
up) changes from bidirectional to unidirectional or down.
Configuring static route FRR to automatically select a backup
next hop
1. Enter system view.
2. Configure static route FRR to
automatically select a
backup next hop.
ip route-static fast-reroute auto
N/A
By default, static route
disabled from automatically
selecting a backup next hop.
Enabling BFD echo packet mode for static route FRR
By default, static route F RR uses ARP to detec t primary link f ailures. Perform this task to enable
static route FRR to use BFD echo packet mode for fast failure detection on the primary link.
To enable BFD echo packet mode for static route FRR:
1. Enter system view.
2.
packets.
system-view
bfd echo-source-ip
ip-address
N/A
By default, the source IP address
of BFD
configured.
The source IP address cannot be
on the same network segment as
any local interface's IP address.
For more information about this
command, see
Command Reference.
As shown in Figure 2, c onf i gure s tat ic routes on th e switches for interc onnections between an y t wo
hosts.
Figure 2 Network diagram
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure static routes:
# Configure a default route on Switch A.
<SwitchA> system-view
[SwitchA] ip route-static 0.0.0.0 0.0.0.0 1.1.4.2
# Configure two static routes on Switch B.
<SwitchB> system-view
[SwitchB] ip route-static 1.1.2.0 255.255.255.0 1.1.4.1
[SwitchB] ip route-static 1.1.3.0 255.255.255.0 1.1.5.6
# Configure a default route on Switch C.
<SwitchC> system-view
[SwitchC] ip route-static 0.0.0.0 0.0.0.0 1.1.5.5
3. Configure the default gateways of Host A, Host B, and Host C as 1.1.2.3, 1.1.6.1, and 1.1.3.1.
(Details not shown.)
Verifying the configuration
# Display static routes on Switch A.
[SwitchA] display ip routing-table protocol static
Summary Coun t : 1
Static Routing table Status : <Ac ti ve>
Summary Coun t : 1
14
Destination/M ask Proto Pre Cost NextHop Interface
0.0.0.0/0 Static 60 0 1.1.4.2 Vlan500
Static Routing ta ble Status : <Inac tive>
Summary Coun t : 0
# Display static routes on Switch B.
[SwitchB] display ip routing-table protocol static
Summary Coun t : 2
Static Routing table Status : <Ac ti ve>
Summary Coun t : 2
Destination/Mask Proto Pre Cost NextHop Interface
1.1.2.0/24 Static 60 0 1.1.4.1 Vlan500
Static Routing table Status : <In ac tive>
Summary Coun t : 0
# Use the ping command on Host B to test the reachability of Host A (Windows XP runs on the two
hosts).
C:\Documents an d Settings\Administrator>ping 1.1.2.2
Pinging 1.1.2.2 with 32 bytes of data :
Reply from 1.1.2.2: bytes=32 time=1ms TTL=126
Reply from 1.1 .2.2: bytes=32 tim e=1ms TTL=126
Reply from 1.1 .2.2: bytes=32 tim e=1ms TTL=126
Reply from 1.1 .2.2: bytes=32 tim e=1ms TTL=126
Ping statist ics for 1.1.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximat e round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
# Use the tracert command on Host B to test the reachability of Host A.
C:\Documents an d Settings\Administrator>tracert 1.1.2.2
Tracing rout e to 1.1.2.2 over a maxi mum of 30 hops
1 <1 ms <1 ms <1 ms 1.1.6.1
2 <1 ms <1 ms <1 ms 1.1.4.1
3 1 ms <1 ms <1 ms 1.1.2.2
Trace complete.
BFD for static routes configuration ex am ple (direct next hop)
Network requirements
Configure the following, as shown in Figure 3:
15
•
•
•
•
Device
Interface
IP address
Switch ASwitch B
Switch C
BFD
L
2
Switch
Vlan-int10
Vlan
-int
11
Vlan-int11
Vlan
-int
13
Vlan-
int13
Vlan-int10
121.
1
.1
.0
/
24
120.1.1.0/24
Configure a static route to subnet 120.1.1.0/24 on Switch A. Configure a static route to subnet 121.1.1.0/ 24 on S wit c h B. Enable BFD for both routes. Configure a static route to subnet 120.1.1.0/24 and a static route to subnet 121.1.1.0/24 on
Switch C.
When the link between Switch A and Switch B throu gh the Layer 2 switch fails, B FD c an det ec t th e
failure immediately. Switch A then communicates with Switch B through Switch C.
Figure 3 Network diagram
Table 4 Interface and IP address assignment
Switch A VLAN-interface 10 12.1.1.1/24
Switch A VLAN-interface 11 10.1.1.102/24
Switch B VLAN-interface 10 12.1.1.2/24
Switch B VLAN-interface 13 13.1.1.1/24
Switch C VLAN-interface 11 10.1.1.100/24
Switch C VLAN-interface 13 13.1.1.2/24
Configuration procedure
1. Configure IP addresses for the interfaces. (Details not shown.)
2. Configure static routes and BFD:
# Configure static routes on Switch A and enable BFD control mode for the static route that
traverses the Layer 2 switch.
<SwitchC> sy stem-view
[SwitchC] ip rout e-static 120.1.1.0 24 13.1.1.1
[SwitchC] ip rout e-static 121.1.1.0 24 10.1.1.102
Verifying the configuration
# Display BFD sessions on Switch A.
<SwitchA> display bfd session
Total Session Nu m: 1 Up Session Num: 1 Init Mode: Ac tive
IPv4 Session Working Under Ctrl Mode:
LD/RD SourceAddr DestAddr State Holdtime Interface
4/7 12.1.1.1 12.1.1.2 Up 2000ms Vlan10
The output shows that the BFD session has been created.
# Display the static routes on Switch A.
<SwitchA> display ip routing-table protocol static
Summary Count : 1
Static Routing table Status : <Ac ti ve>
Summary Coun t : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 60 0 12. 1.1.2 Vlan10
Static Routing ta ble Status : <Inac tive>
Summary Count : 0
The output shows that Swit ch A communicates with Sw itch B thr ough VLAN-interface 10. Then the
link over VLAN-interface 10 fails.
# Display static routes on Switch A.
<SwitchA> display ip routing-table protocol static
Summary Coun t : 1
Static Routing table Status : <Ac ti ve>
Summary Coun t : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 65 0 10. 1.1.100 Vlan11
17
•
•
•
•
•
•
•
Device
Interface
IP address
Switch ASwitch B
Switch C
BFD
Vlan-int10
Vlan
-
int
11
Vlan-int11Vlan-int13
Vlan-
int
13
Vlan-int10
121.1.1.0/24
120.1.1.0/24
Switch D
Vlan-int12
Vlan-int12
Loop1
1.1.1.9/32
Loop1
2.2.2.9/32
Static Routing ta ble Status : <Inac tive>
Summary Coun t : 0
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
BFD for static routes configuration ex am ple (indirect next
hop)
Network requirements
Figure 4 shows the network topology as follows:
Switch A has a route to interface Loopback 1 (2.2.2.9/32) on Switch B, with the output interface
VLAN-interface 10.
Switch B has a route to interface Loopback 1 (1.1.1.9/32) on Switch A, with the output interface
VLAN-interface 12.
Switch D has a route to 1.1.1.9/32, with the output interface VLAN-interface 10, and a route to
2.2.2.9/32, with the output interfac e VLAN-interface 12.
Configure the following:
Configure a static route to subnet 120.1.1.0/24 on Switch A. Configure a static route to subnet 121.1.1.0/24 on Switch B.Enable BFD for both routes. Configure a static route to subnet 120.1.1.0/24 and a static route to subnet 121.1.1.0/24 on both
Switch C and Switch D.
When the link between Switch A and Switch B through Switch D fails, BFD can detect the failure
immediately. Switch A then communicates with Switch B through Switch C.
Figure 4 Network diagram
Table 5 Interface and IP address assignment
Switch A VLAN-interface 10 12.1.1.1/24
Switch A VLAN-interface 11 10.1.1.102/24
Switch A Loopback 1 1.1.1.9/32
Switch B VLAN-interface 12 11.1.1.1/24
Switch B VLAN-interface 13 13.1.1.1/24
Switch B Loopback 1 2.2.2.9/32
18
Loading...
+ 522 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.