Aruba JC611A HPE FlexNetwork Switch Installation Guide
Advertisement
Advertisement
HPE FlexNetwork 10500 Switch Series
Layer 3—IP Routing Configuration Guide
Part number: 5200-1898a
Software version: 10500-CMW710-R7557P01
Document version: 6W101-20171020
© Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
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
Configuring static routing ············································································· 10
Configuring a default route ··········································································· 24
Configuring RIP ··························································································· 25
i
Configuring OSPF························································································ 65
ii
iii
Configuring IS-IS ······················································································· 135
iv
Configuring BGP ························································································ 195
v
vi
Configuring PBR ························································································ 386
Configuring IPv6 static routing ··································································· 401
Configuring an IPv6 default route······························································· 411
Configuring RIPng ····················································································· 412
vii
Configuring OSPFv3 ·················································································· 437
viii
Configuring IPv6 IS-IS ··············································································· 489
Configuring IPv6 PBR ················································································ 509
ix
Configuring routing policies ········································································ 517
Configuring DCN ······················································································· 530
Document conventions and icons ······························································ 540
Support and other resources ····································································· 542
Index ·········································································································· 545
x
Configuring basic IP routing
IP routing directs IP packet forwarding on routers based on a routing table. This chapter focuses on unicast routing protocols. For more information about multicast routing protocols, see IP Multicast
Configuration Guide .
Routing table
A RIB contains the global routing information and related information, including route recursion, route redistribution, and route extension information. The router selects optimal routes from 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 1 categorizes routes by different criteria.
Table 1 Route categories
Criterion
Destination
Categories
•
Network route —The destination is a network. The subnet mask is less than 32 bits.
•
Host route —The destination is a host. The subnet mask is 32 bits.
Whether the destination is directly connected
•
Direct route —The destination is directly connected.
•
Indirect route —The destination is indirectly connected.
Origin
•
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
•
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
Criterion
Operation scope
Routing algorithm
Destination address type
IP version
Categories
•
IGPs —Work within an AS. Examples include RIP, OSPF, and IS-IS.
•
EGPs —Work between ASs. The most popular EGP is BGP.
•
Distance-vector protocols —Examples include RIP and BGP. BGP is also 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 same routing policy and work under the same administration.
Route preference
Routing protocols, including static and direct routing, each by default have a preference. If they find multiple routes to the same destination, the router selects the route with the highest preference as the optimal route.
The preference of a direct route is always 0 and cannot be changed. You 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.
Table 3 Route types and default route preferences
Route type
Direct route
Multicast static route
OSPF
IS-IS
Unicast static route
Preference
0
1
10
15
60
2
Route type
RIP
OSPF ASE
OSPF NSSA
IBGP
EBGP
Unknown (route from an untrusted source)
Preference
100
150
150
255
255
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, IPv6 BGP, IS-IS, and IPv6 IS-IS support ECMP load sharing.
Route backup
Route backup can improve network availability. Among multiple routes to the same destination, the route with the highest priority is the primary route and others are secondary routes.
The router forwards matching packets through the primary route. When the primary 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, static, or RIP route that has an indirectly connected next hop, a router must perform route recursion to find the output interface to reach the next hop.
Link-state routing protocols, such as OSPF and IS-IS, do not need route recursion, because they obtain directly connected next hops through route calculation.
The RIB records and saves route recursion information, including brief information about related routes, recursive paths, and recursion depth.
Route redistribution
Route redistribution enables routing protocols to learn routing information from each other. A dynamic routing protocol can redistribute routes from other routing protocols, including direct and static routing. For more information, see the respective chapters on those routing protocols in this configuration guide.
The RIB records redistribution relationships of routing protocols.
Extension attribute redistribution
Extension attribute redistribution enables routing protocols to learn route extension attributes from each other, including BGP extended community attributes, OSPF area IDs, route types, and router
IDs.
3
The RIB records extended attributes of each routing protocol and redistribution relationships of different routing protocol extended attributes.
Setting the maximum lifetime for routes and labels in the RIB
Perform this task to prevent routes of a certain protocol from being aged out due to slow 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):
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter RIB view. rib N/A
3. Create the RIB IPv4 address family and enter its view. address-family ipv4
By default, no RIB IPv4 address family exists.
4. Set the maximum lifetime for
IPv4 routes and labels in the
RIB.
protocol protocol [ instance instance-name ] lifetime seconds
To set the maximum route lifetime for routes and labels in the RIB (IPv6):
By default, the maximum lifetime for routes and labels in the RIB is 480 seconds.
Step
1. Enter system view.
Command system-view rib 2. Enter RIB view.
3. Create the RIB IPv6 address family and enter its view. address-family ipv6
4. Set the maximum lifetime for
IPv6 routes and labels in the
RIB.
protocol protocol [ instance instance-name ] lifetime seconds
Remarks
N/A
N/A
By default, no RIB IPv6 address family exists.
By default, the maximum 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 must be retained for some time after a protocol process switchover or RIB process switchover. When GR or NSR is enabled, FIB entries must be removed immediately after a protocol or RIB process switchover to avoid routing issues. Perform this task to meet such requirements.
To set the maximum lifetime for routes in the FIB (IPv4):
Step
1. Enter system view.
Command system-view rib 2. Enter RIB view.
3. Create the RIB IPv4 address family and enter its view. address-family ipv4
Remarks
N/A
N/A
By default, no RIB IPv4 address family exists.
4
Step Command
4. Set the maximum lifetime for
IPv4 routes in the FIB.
fib lifetime seconds
To set the maximum lifetime for routes in the FIB (IPv6):
Step
1. Enter system view.
2. Enter RIB view.
Command system-view rib
3. Create the RIB IPv6 address family and enter its view. address-family ipv6
4. Set the maximum lifetime for
IPv6 routes in the FIB.
fib lifetime seconds
Remarks
By default, the maximum lifetime for routes in the FIB is 600 seconds.
Remarks
N/A
N/A
By default, no RIB IPv6 address family exists.
By default, the maximum lifetime for routes in the FIB is 600 seconds.
Enabling the RIB to flush route attribute information to the FIB
This feature is available only for BGP routes in the current software version. You can configure this feature when using sFlow to monitor BGP traffic. For more information about BGP path attributes and sFlow, see Layer 3
—
IP Routing Configuration Guide and Network Management and Monitoring
Configuration Guide .
To enable RIB to flush route attribute information to the FIB:
Step
1. Enter system view.
Command system-view
2. Enter RIB view.
3. Create the RIB IPv4 address family and enter its view. rib address-family ipv4
4. Enable the RIB to flush route attribute information to the
FIB. flush route-attribute protocol
Remarks
N/A
N/A
By default, no RIB IPv4 address family exists.
By default, the RIB does not flush route attribute information to the FIB.
Setting the maximum number of ECMP routes
This configuration takes effect at reboot. Make sure the reboot does not impact your network.
To set the maximum number of ECMP routes:
Step
1. Enter system view.
Command system-view
2. Set the maximum number of
ECMP routes. max-ecmp-num number
Remarks
N/A
By default, the maximum number of ECMP routes is not set.
5
Configuring RIB NSR
IMPORTANT:
Use this feature with protocol GR or NSR to avoid route timeouts and traffic interruption.
When an active/standby switchover occurs, nonstop routing (NSR) backs up routing information from the active process to the standby process to avoid routing flapping and ensure forwarding continuity.
RIB NSR provides faster route convergence than protocol NSR during an active/standby switchover.
Configuring IPv4 RIB NSR
Step
1. Enter system view.
Command system-view rib 2. Enter RIB view.
3. Create the RIB IPv4 address family and enter its view. address-family ipv4
4. Enable IPv4 RIB NSR. non-stop-routing
Configuring IPv6 RIB NSR
Remarks
N/A
N/A
By default, no RIB IPv4 address family exists.
By default, RIB NSR is disabled.
Step
1. Enter system view.
Command system-view rib 2. Enter RIB view.
3. Create the RIB IPv6 address family and enter its view. address-family ipv6
4. Enable IPv6 RIB NSR. non-stop-routing
Configuring inter-protocol FRR
Remarks
N/A
N/A
By default, no RIB IPv6 address family exists.
By default, RIB NSR is disabled.
CAUTION:
This feature uses the next hop of a route from a different protocol as the backup next hop for the faulty route, which might cause loops.
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. When the next hop of the primary 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 table. For example, if a static route and an OSPF route in the RIB have the same destination, the router adds the OSPF route to the FIB table 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.
6
Configuring IPv4 RIB inter-protocol FRR
Step
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv4 address family and enter its view.
4. Enable IPv4 RIB inter-protocol FRR.
Command system-view rib address-family ipv4 inter-protocol fast-reroute
[ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
By default, no RIB IPv4 address family exists.
By default, inter-protocol
FRR is disabled.
If you do not specify a VPN instance, inter-protocol FRR is enabled for the public network.
Configuring IPv6 RIB inter-protocol FRR
Step
1. Enter system view.
2. Enter RIB view.
3. Create the RIB IPv6 address family and enter its view.
4. Enable IPv6 RIB inter-protocol FRR.
Command system-view rib address-family ipv6 inter-protocol fast-reroute
[ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
By default, no RIB IPv6 address family exists.
By default, inter-protocol
FRR is disabled.
If you do not specify a VPN instance, inter-protocol FRR is enabled for the public network.
Configuring routing policy-based recursive lookup
When a route changes, the routing protocol has to perform a route recursion if the next hop is indirectly connected. The routing protocol might select an incorrect path, which can cause traffic loss.
To prevent this problem, you can use a routing policy to verify the recursive route. If the recursive route fails to match the routing policy, the routing protocol invalidates the route and marks it as unreachable.
For the device to use exact routes to forward the traffic, make sure all desired routes can match the routing policy.
To configure routing policy-based recursive lookup:
Step
1. Enter system view.
Command system-view
2. Enter RIB view. rib
3. Create the RIB IPv4 address family and enter its view. address-family ipv4
Remarks
N/A
N/A
By default, no RIB IPv4 address family exists.
7
Step
4. Configure routing policy-based recursive lookup.
Command
protocol protocol nexthop
recursive-lookup route-policy route-policy-name
Remarks
By default, routing policy-based recursive lookup is not configured.
Displaying and maintaining a routing table
Execute display commands in any view and reset commands in user view.
Task
Display routing table information.
Command display ip routing-table [ vpn-instance vpn-instance-name ]
[ verbose ]
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 information about routes permitted by an IP prefix list.
Display information about routes installed by a protocol.
Display IPv4 route statistics. display ip routing-table ipv4-acl-number display ip routing-table ip-address [ display ip routing-table ip-address1 mask-length to
[
[ verbose
[
|
[ ip-address2
vpn-instance vpn-instance-name
]
vpn-instance vpn-instance-name mask ] [ longer-match ] [ verbose
vpn-instance vpn-instance-name
[ verbose ]
]
]
]
] display ip routing-table [ vpn-instance vpn-instance-name ] prefix-list prefix-list-name [ verbose ] display ip routing-table [ vpn-instance vpn-instance-name ] protocol protocol [ inactive | verbose ] display ip routing-table [ vpn-instance vpn-instance-name ] statistics display ip routing-table [ vpn-instance vpn-instance-name ] summary
acl
Display brief IPv4 routing table information.
Display the maximum number of
ECMP routes.
Display route attribute information in the RIB.
Display RIB GR state information. display max-ecmp-num display rib attribute [ attribute-id ]
Display next hop information in the
RIB. display rib graceful-restart display rib nib [ self-originated ] [ nib-id ] [ verbose ] display rib nib protocol protocol [ verbose ]
Display next hop information for direct routes. display route-direct nib [ nib-id ] [ verbose ]
Clear IPv4 route statistics. reset ip routing-table statistics protocol [ vpn-instance vpn-instance-name ] { protocol | all }
Display IPv6 routing table information. display ipv6 routing-table [ vpn-instance vpn-instance-name ]
[ verbose ]
Display information about routes to an
IPv6 destination address. display ipv6 routing-table [ vpn-instance vpn-instance-name ] ipv6-address [ prefix-length ] [ longer-match ] [ verbose ]
Display information about routes permitted by an IPv6 basic ACL.
Display information about routes to a range of IPv6 destination addresses.
Display information about routes permitted by an IPv6 prefix list. display ipv6 routing-table acl ipv6-acl-number [ verbose display ipv6 routing-table [ vpn-instance vpn-instance-name ]
ipv6-address1 to ipv6-address2 [ verbose ] display ipv6 routing-table prefix-list prefix-list-name
[
[
[ vpn-instance
] vpn-instance-name
vpn-instance vpn-instance-name verbose ]
]
]
8
Task
Display information about routes installed by an IPv6 protocol.
Display IPv6 route statistics.
Command display ipv6 routing-table [ vpn-instance vpn-instance-name ]
protocol protocol [ inactive | verbose ] display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics display ipv6 routing-table [ vpn-instance vpn-instance-name ] summary
Display brief IPv6 routing table information.
Display route attribute information in the IPv6 RIB.
Display IPv6 RIB GR state information. display ipv6 rib attribute [ attribute-id display ipv6 rib graceful-restart
]
Display next hop information in the
IPv6 RIB.
Display next hop information for IPv6 direct routes. display ipv6 rib nib [ self-originated display ipv6 rib nib protocol
] [ protocol [ nib-id ] [ verbose verbose
] display ipv6 route-direct nib [ nib-id ] [ verbose ]
]
Clear IPv6 route statistics. reset ipv6 routing-table statistics protocol [ vpn-instance vpn-instance-name ] { protocol | all }
9
Configuring static routing
Static routes are manually configured. If a network's topology is simple, you only need to configure static routes for the network to work correctly.
Static routes cannot adapt to network topology changes. If a fault or a topological change occurs 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 monitor the reachability of the next hops. For more information about Track, see High Availability Configuration Guide .
To configure a static route:
Step Command
1. Enter system view. system-view
2. (Optional.) Create a static route group and enter its view.
3. (Optional.) Add a static route prefix to the static route group.
4. (Optional.) Return to system view. ip route-static-group group-name prefix dest-address { mask-length | mask } quit
5. Configure a static route.
Remarks
N/A
By default, no static route group is configured.
By default, no static route prefix is added to the static route group.
N/A
•
Method 1: ip route-static { dest-address { mask-length
| mask } | group group-name }
{ interface-type interface-number
[ next-hop-address ] | next-hop-address
[ recursive-lookup host-route ] [ track track-entry-number ] | vpn-instance d-vpn-instance-name next-hop-address
[ recursive-lookup host-route ] [ track track-entry-number ] } [ permanent ]
[ preference preference ] [ tag tag-value ]
[ description text ]
•
Method 2: ip route-static vpn-instance s-vpn-instance-name { dest-address
{ mask-length | mask } | group group-name }
{ interface-type interface-number
[ next-hop-address ] | next-hop-address
[ recursive-lookup host-route ] [ public ]
[ track track-entry-number ] | vpn-instance d-vpn-instance-name next-hop-address
[ recursive-lookup host-route ] [ track track-entry-number ] } [ permanent ]
[ preference preference ] [ tag tag-value ]
[ description text ]
By default, no static route is configured.
10
Step
6. (Optional.) Enable periodic sending of
ARP requests to the next hops of static routes.
7. (Optional.)
Configure the default preference for static routes.
8. (Optional.) Delete all static routes, including the default route.
Command ip route-static arp-request interval interval ip route-static default-preference
default-preference delete [ vpn-instance vpn-instance-name ] static-routes all
Configuring BFD for static routes
Remarks
By default, the device does not send ARP requests to the next hops of static routes.
The default setting is 60.
To delete one static route, use the undo ip route-static command.
IMPORTANT:
Enabling BFD for a flapping route could worsen the situation.
BFD provides a general-purpose, standard, medium-, and protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols and MPLS.
For more information about BFD, see High Availability Configuration Guide .
Bidirectional control 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):
Step Command
1. Enter system view.
system-view
2. Configure BFD control mode for a static route.
•
Method 1:
ip route-static dest-address { mask-length | mask } interface-type interface-number next-hop-address bfd control-packet
[ preference preference ] [ tag tag-value ]
[ description text ]
•
Method 2: ip route-static vpn-instance
s-vpn-instance-name dest-address
{ mask-length | mask } interface-type interface-number next-hop-address bfd control-packet [ preference preference ] [ tag tag-value ] [ description text ]
To configure BFD control mode for a static route (indirect next hop):
Remarks
N/A
By default, BFD control mode for a static route is not configured.
11
Step Command
1. Enter system view.
system-view
2. Configure BFD control mode for a static route.
•
Method 1: ip route-static dest-address { mask-length | mask } { next-hop-address bfd control-packet
bfd-source ip-address | vpn-instance d-vpn-instance-name next-hop-address bfd control-packet bfd-source ip-address }
[ preference preference ] [ tag tag-value ]
[ description text ]
•
Method 2: ip route-static vpn-instance
s-vpn-instance-name dest-address
{ mask-length | mask } { next-hop-address bfd control-packet bfd-source ip-address | vpn-instance d-vpn-instance-name next-hop-address bfd control-packet bfd-source ip-address } [ preference preference ] [ tag tag-value ] [ description
text ]
Remarks
N/A
By default, BFD control mode for a static route is not configured.
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.
IMPORTANT:
Do not use BFD for a static route with the output interface in spoofing state.
To configure BFD echo mode for a static route:
Step Command
1. Enter system view. system-view
Remarks
N/A
2. Configure the source address of echo packets. bfd echo-source-ip ip-address
By default, the source address of echo packets is not configured.
For more information about this command, see High
Availability Command
Reference .
3. Configure BFD echo mode for a static route.
•
Method 1: ip route-static dest-address { mask-length | mask } interface-type interface-number next-hop-address bfd echo-packet
[ preference preference ] [ tag tag-value ]
[ description text ]
•
Method 2: ip route-static vpn-instance s-vpn-instance-name dest-address
{ mask-length | mask } interface-type interface-number next-hop-address bfd echo-packet [ preference preference ] [ tag tag-value ] [ description text ]
By default, BFD echo mode for a static route is not configured.
12
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
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
interruption. You 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 and next hop.
•
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 up) changes from bidirectional to unidirectional or down.
Configuring static route FRR by specifying a backup next hop
Step
1. Enter system view.
2. Configure static route
FRR.
Command system-view
•
Method 1: ip route-static dest-address
{ mask-length | mask } interface-type interface-number [ next-hop-address
[ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] ] ]
[ permanent ] [ preference preference ]
[ tag tag-value ] [ description text ]
•
Method 2: ip route-static vpn-instance s-vpn-instance-name dest-address
{ mask-length | mask } interface-type interface-number [ next-hop-address
[ backup-interface interface-type interface-number [ backup-nexthop backup-nexthop-address ] ] ]
[ permanent ] [ preference preference ]
[ tag tag-value ] [ description text ]
Remarks
N/A
By default, static route FRR is disabled.
13
Configuring static route FRR to automatically select a backup next hop
Step
1. Enter system view.
Command system-view
2. Configure static route FRR to automatically select a backup next hop. ip route-static fast-reroute auto
Remarks
N/A
By default, static route FRR is disabled from automatically selecting a backup next hop.
Enabling BFD echo packet mode for static route FRR
By default, static route FRR uses ARP to detect primary link failures. 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:
Step
1. Enter system view.
2. Configure the source IP address of BFD echo packets.
Command system-view
bfd echo-source-ip ip-address
3. Enable BFD echo packet mode for static route FRR. ip route-static primary-path-detect bfd echo
Remarks
N/A
By default, the source IP address of BFD echo packets is not 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 High Availability
Command Reference .
By default, BFD echo mode for static route FRR is disabled.
Displaying and maintaining static routes
Execute display commands in any view.
Task
Display static route information.
Display static route next hop information.
Display static routing table information.
Command display ip routing-table protocol static [ inactive | verbose ] display route-static nib [ nib-id ] [ verbose ] display route-static routing-table [ vpn-instance vpn-instance-name ] [ ip-address { mask-length | mask } ]
14
Static route configuration examples
Basic static route configuration example
Network requirements
As shown in Figure 2 , configure static routes on the switches for interconnections between any two
hosts.
Figure 2 Network diagram
Host B
1.1.6.2/24
Vlan-int100
1.1.6.1/24
Vlan-int500
1.1.4.2/30
Switch B
Vlan-int600
1.1.5.5/30
Vlan-int500
1.1.4.1/30
Vlan-int600
1.1.5.6/30
Vlan-int300
1.1.2.3/24
Switch A Host A
1.1.2.2/24
Configuration procedure
Vlan-int900
Switch C
1.1.3.1/24
Host C
1.1.3.2/24
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 Count : 1
Static Routing table Status : <Active>
Summary Count : 1
15
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/0 Static 60 0 1.1.4.2 Vlan500
Static Routing table Status : <Inactive>
Summary Count : 0
# Display static routes on Switch B.
[SwitchB] display ip routing-table protocol static
Summary Count : 2
Static Routing table Status : <Active>
Summary Count : 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 : <Inactive>
Summary Count : 0
# Use the ping command on Host B to test the reachability of Host A (Windows XP runs on the two hosts).
C:\Documents and 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 time=1ms TTL=126
Reply from 1.1.2.2: bytes=32 time=1ms TTL=126
Reply from 1.1.2.2: bytes=32 time=1ms TTL=126
Ping statistics for 1.1.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate 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 and Settings\Administrator>tracert 1.1.2.2
Tracing route to 1.1.2.2 over a maximum 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 example (direct next hop)
Network requirements
Configure the following, as shown in Figure 3 :
16
•
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
Switch C.
When the link between Switch A and Switch B through the Layer 2 switch fails, BFD can detect the failure immediately. Switch A then communicates with Switch B through Switch C.
Figure 3 Network diagram
121.1.1.0/24 120.1.1.0/24
Switch A
Vlan-int10
L2 Switch
Vlan-int10
Switch B
Vlan-int11 Vlan-int13
BFD
Vlan-int11 Vlan-int13
Switch C
Table 4 Interface and IP address assignment
Device
Switch A
Switch A
Switch B
Switch B
Switch C
Interface
VLAN-interface 10
VLAN-interface 11
VLAN-interface 10
VLAN-interface 13
VLAN-interface 11
IP address
12.1.1.1/24
10.1.1.102/24
12.1.1.2/24
13.1.1.1/24
10.1.1.100/24
Switch C
Configuration procedure
VLAN-interface 13 13.1.1.2/24
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.
<SwitchA> system-view
[SwitchA] interface vlan-interface 10
[SwitchA-vlan-interface10] bfd min-transmit-interval 500
[SwitchA-vlan-interface10] bfd min-receive-interval 500
[SwitchA-vlan-interface10] bfd detect-multiplier 9
[SwitchA-vlan-interface10] quit
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 10 12.1.1.2 bfd control-packet
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 preference 65
[SwitchA] quit
# Configure static routes on Switch B and enable BFD control mode for the static route that traverses the Layer 2 switch.
<SwitchB> system-view
[SwitchB] interface vlan-interface 10
17
[SwitchB-vlan-interface10] bfd min-transmit-interval 500
[SwitchB-vlan-interface10] bfd min-receive-interval 500
[SwitchB-vlan-interface10] bfd detect-multiplier 9
[SwitchB-vlan-interface10] quit
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 10 12.1.1.1 bfd control-packet
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 preference 65
[SwitchB] quit
# Configure static routes on Switch C.
<SwitchC> system-view
[SwitchC] ip route-static 120.1.1.0 24 13.1.1.1
[SwitchC] ip route-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 Num: 1 Up Session Num: 1 Init Mode: Active
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 : <Active>
Summary Count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 60 0 12.1.1.2 Vlan10
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through 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 Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 65 0 10.1.1.100 Vlan11
18
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
BFD for static routes configuration example (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 interface 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
121.1.1.0/24
Loop1
1.1.1.9/32
Loop1
2.2.2.9/32
Switch D
Vlan-int10
Switch A
Vlan
-int
11
Vlan-int10
BFD
Vlan-int12
Vlan-int12
Vlan
-int
13
Switch B
120.1.1.0/24
Vlan-int11 Vlan-int13
Switch C
Table 5 Interface and IP address assignment
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Interface
VLAN-interface 10
VLAN-interface 11
Loopback 1
VLAN-interface 12
VLAN-interface 13
Loopback 1
19
IP address
12.1.1.1/24
10.1.1.102/24
1.1.1.9/32
11.1.1.1/24
13.1.1.1/24
2.2.2.9/32
Device
Switch C
Switch C
Interface
VLAN-interface 11
VLAN-interface 13
IP address
10.1.1.100/24
13.1.1.2/24
Switch D VLAN-interface 10 12.1.1.2/24
Switch D
Configuration procedure
VLAN-interface 12 11.1.1.2/24
1. Configure IP addresses for 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 Switch D.
<SwitchA> system-view
[SwitchA] bfd multi-hop min-transmit-interval 500
[SwitchA] bfd multi-hop min-receive-interval 500
[SwitchA] bfd multi-hop detect-multiplier 9
[SwitchA] ip route-static 120.1.1.0 24 2.2.2.9 bfd control-packet bfd-source 1.1.1.9
[SwitchA] ip route-static 120.1.1.0 24 vlan-interface 11 10.1.1.100 preference 65
[SwitchA] quit
# Configure static routes on Switch B and enable BFD control mode for the static route that traverses Switch D.
<SwitchB> system-view
[SwitchB] bfd multi-hop min-transmit-interval 500
[SwitchB] bfd multi-hop min-receive-interval 500
[SwitchB] bfd multi-hop detect-multiplier 9
[SwitchB] ip route-static 121.1.1.0 24 1.1.1.9 bfd control-packet bfd-source 2.2.2.9
[SwitchB] ip route-static 121.1.1.0 24 vlan-interface 13 13.1.1.2 preference 65
[SwitchB] quit
# Configure static routes on Switch C.
<SwitchC> system-view
[SwitchC] ip route-static 120.1.1.0 24 13.1.1.1
[SwitchC] ip route-static 121.1.1.0 24 10.1.1.102
# Configure static routes on Switch D.
<SwitchD> system-view
[SwitchD] ip route-static 120.1.1.0 24 11.1.1.1
[SwitchD] ip route-static 121.1.1.0 24 12.1.1.1
Verifying the configuration
# Display BFD sessions on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 Session Working Under Ctrl Mode:
LD/RD SourceAddr DestAddr State Holdtime Interface
4/7 1.1.1.9 2.2.2.9 Up 2000ms N/A
The output shows that the BFD session has been created.
20
# Display the static routes on Switch A.
<SwitchA> display ip routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 60 0 12.1.1.2 Vlan10
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through 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 Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 Static 65 0 10.1.1.100 Vlan11
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
Static route FRR configuration example
Network requirements
As shown in Figure 5 , configure static routes on Switch A, Switch B, and Switch C, and configure
static route FRR. When Link A becomes unidirectional, traffic can be switched to Link B immediately.
Figure 5 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
100
Link B
Vlan
-int
101
Link A
Vlan
-int
101
Loop0 Loop0
Switch A
Vlan-int200 Vlan-int200
Switch B
21
Table 6 Interface and IP address assignment
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Interface
VLAN-interface 100
VLAN-interface 200
Loopback 0
VLAN-interface 101
VLAN-interface 200
Loopback 0
VLAN-interface 100
IP address
12.12.12.1/24
13.13.13.1/24
1.1.1.1/32
24.24.24.4/24
13.13.13.2/24
4.4.4.4/32
12.12.12.2/24
Switch C
Configuration procedure
VLAN-interface 101 24.24.24.2/24
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure static route FRR on link A by using one of the following methods:
(Method 1.) Specify a backup next hop for static route FRR:
# Configure a static route on Switch A, and specify VLAN-interface 100 as the backup output interface and 12.12.12.2 as the backup next hop.
<SwitchA> system-view
[SwitchA] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2 backup-interface vlan-interface 100 backup-nexthop 12.12.12.2
# Configure a static route on Switch B, and specify VLAN-interface 101 as the backup output interface and 24.24.24.2 as the backup next hop.
<SwitchB> system-view
[SwitchB] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1 backup-interface vlan-interface 101 backup-nexthop 24.24.24.2
(Method 2.) Configure static route FRR to automatically select a backup next hop:
# Configure static routes on Switch A, and enable static route FRR.
<SwitchA> system-view
[SwitchA] ip route-static 4.4.4.4 32 vlan-interface 200 13.13.13.2
[SwitchA] ip route-static 4.4.4.4 32 vlan-interface 100 12.12.12.2 preference 70
[SwitchA] ip route-static fast-reroute auto
# Configure static routes on Switch B, and enable static route FRR.
<SwitchB> system-view
[SwitchB] ip route-static 1.1.1.1 32 vlan-interface 200 13.13.13.1
[SwitchB] ip route-static 1.1.1.1 32 vlan-interface 101 24.24.24.2 preference 70
[SwitchB] ip route-static fast-reroute auto
3. Configure static routes on Switch C.
<SwitchC> system-view
[SwitchC] ip route-static 4.4.4.4 32 vlan-interface 101 24.24.24.4
[SwitchC] ip route-static 1.1.1.1 32 vlan-interface 100 12.12.12.1
Verifying the configuration
# Display route 4.4.4.4/32 on Switch A to view the backup next hop information.
[SwitchA] display ip routing-table 4.4.4.4 verbose
Summary Count : 1
22
Destination: 4.4.4.4/32
Protocol: Static
Process ID: 0
SubProtID: 0x0 Age: 04h20m37s
Cost: 0 Preference: 60
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.2
Label: NULL RealNextHop: 13.13.13.2
BkLabel: NULL BkNextHop: 12.12.12.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display route 1.1.1.1/32 on Switch B to view the backup next hop information.
[SwitchB] display ip routing-table 1.1.1.1 verbose
Summary Count : 1
Destination: 1.1.1.1/32
Protocol: Static
Process ID: 0
SubProtID: 0x0 Age: 04h20m37s
Cost: 0 Preference: 60
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.1
Label: NULL RealNextHop: 13.13.13.1
BkLabel: NULL BkNextHop: 24.24.24.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
23
Configuring a default route
A default route is used to forward packets that do not match any specific routing entry in the routing table. Without a default route, packets that do not match any routing entries are discarded and an
ICMP destination-unreachable packet is sent to the source.
A default route can be configured in either of the following ways:
•
The network administrator can configure a default route with both destination and mask being
0.0.0.0. For more information, see " Configuring static routing ."
•
Some dynamic routing protocols, such as OSPF, RIP, and IS-IS, can generate a default route.
For example, an upstream router running OSPF can generate a default route and advertise it to other routers. These routers install the default route with the next hop being the upstream router.
For more information, see the respective chapters on these routing protocols in this configuration guide.
24
Configuring RIP
Overview
Routing Information Protocol (RIP) is a distance-vector IGP suited to small-sized networks. It employs UDP to exchange route information through port 520.
RIP uses a hop count to measure the distance to a destination. The hop count from a router to a directly connected network is 0. The hop count from a router to a directly connected router is 1. To limit convergence time, RIP restricts the value range of the metric from 0 to 15. A destination with a metric value of 16 (or greater) is considered unreachable. For this reason, RIP is not suitable for large-sized networks.
RIP route entries
RIP stores routing entries in a database. Each routing entry contains the following elements:
•
Destination address —IP address of a destination host or a network.
•
Next hop —IP address of the next hop.
•
Egress interface —Egress interface of the route.
•
Metric —Cost from the local router to the destination.
•
Route time —Time elapsed since the last update. The time is reset to 0 when the routing entry is updated.
•
Route tag
—Used for route control. For more information, see " Configuring routing policies ."
Routing loop prevention
RIP uses the following mechanisms to prevent routing loops:
•
Counting to infinity —A destination with a metric value of 16 is considered unreachable. When a routing loop occurs, the metric value of a route will increment to 16 to avoid endless looping.
•
Triggered updates —RIP immediately advertises triggered updates for topology changes to reduce the possibility of routing loops and to speed up convergence.
•
Split horizon —Disables RIP from sending routes through the interface where the routes were learned to prevent routing loops and save bandwidth.
•
Poison reverse —Enables RIP to set the metric of routes received from a neighbor to 16 and sends these routes back to the neighbor. The neighbor can delete such information from its routing table to prevent routing loops.
RIP operation
RIP works as follows:
1. RIP sends request messages to neighboring routers. Neighboring routers return response messages that contain their routing tables.
2. RIP uses the received responses to update the local routing table and sends triggered update messages to its neighbors. All RIP routers on the network do this to learn latest routing information.
3. RIP periodically sends the local routing table to its neighbors. After a RIP neighbor receives the message, it updates its routing table, selects optimal routes, and sends an update to other neighbors. RIP ages routes to keep only valid routes.
25
RIP versions
There are two RIP versions, RIPv1 and RIPv2.
RIPv1 is a classful routing protocol. It advertises messages only through broadcast. RIPv1 messages do not carry mask information, so RIPv1 can only recognize natural networks such as
Class A, B, and C. For this reason, RIPv1 does not support discontiguous subnets.
RIPv2 is a classless routing protocol. It has the following advantages over RIPv1:
•
Supports route tags to implement flexible route control through routing policies.
•
Supports masks, route summarization, and CIDR.
•
Supports designated next hops to select the best ones on broadcast networks.
•
Supports multicasting route updates so only RIPv2 routers can receive these updates to reduce resource consumption.
•
Supports plain text authentication and MD5 authentication to enhance security.
RIPv2 supports two transmission modes: broadcast and multicast. Multicast is the default mode using 224.0.0.9 as the multicast address. An interface operating in RIPv2 broadcast mode can also receive RIPv1 messages.
Protocols and standards
•
RFC 1058, Routing Information Protocol
•
RFC 1723, RIP Version 2 - Carrying Additional Information
•
RFC 1721, RIP Version 2 Protocol Analysis
•
RFC 1722, RIP Version 2 Protocol Applicability Statement
•
RFC 1724, RIP Version 2 MIB Extension
•
RFC 2082, RIPv2 MD5 Authentication
•
RFC 2453, RIP Version 2
RIP configuration task list
Tasks at a glance
•
•
(Optional.) Controlling RIP reception and advertisement on interfaces
•
(Optional.) Configuring a RIP version
(Optional.) Configuring RIP route control :
•
Configuring an additional routing metric
•
Configuring RIPv2 route summarization
•
Disabling host route reception
•
•
Configuring received/redistributed route filtering
•
•
Configuring RIP route redistribution
26
Tasks at a glance
(Optional.) Tuning and optimizing RIP networks :
•
•
Enabling split horizon and poison reverse
•
Setting the maximum number of RIP ECMP routes
•
Enabling zero field check on incoming RIPv1 messages
•
Enabling source IP address check on incoming RIP updates
•
Configuring RIPv2 message authentication
•
Setting the RIP triggered update interval
•
•
Configuring RIP network management
•
Configuring the RIP packet sending rate
•
Setting the maximum length of RIP packets
•
Setting the DSCP value for outgoing RIP packets
(Optional.) Configuring RIP GR
(Optional.) Configuring BFD for RIP
(Optional.) Configuring RIP FRR
Configuring basic RIP
Before you configure basic RIP settings, complete the following tasks:
•
Configure the link layer protocol.
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring routers.
Enabling RIP
Follow these guidelines when you enable RIP:
•
To enable multiple RIP processes on a router, you must specify an ID for each process. A RIP process ID has only local significance. Two RIP routers having different process IDs can also exchange RIP packets.
•
If you configure RIP settings in interface view before enabling RIP, the settings do not take effect until RIP is enabled.
•
If a physical interface is attached to multiple networks, you cannot advertise these networks in different RIP processes.
•
You cannot enable multiple RIP processes on a physical interface.
•
The rip enable command takes precedence over the network command.
Enabling RIP on a network
You can enable RIP on a network and specify a wildcard mask for the network. After that, only the interface attached to the network runs RIP.
To enable RIP on a network:
Step
1. Enter system view.
Command system-view
Remarks
N/A
27
Step
2. Enable RIP and enter RIP view.
3. Enable RIP on a network.
Command rip [ process-id ] [ vpn-instance vpn-instance-name ]
network network-address
[ wildcard-mask ]
Remarks
By default, RIP is disabled.
By default, RIP is disabled on a network.
The network 0.0.0.0 command can enable RIP on all interfaces in a single process, but does not apply to multiple RIP processes.
Enabling RIP on an interface
Step
1. Enter system view.
2. Enable RIP and enter RIP view.
3. Return to system view.
4. Enter interface view.
5. Enable RIP on the interface.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ] quit interface interface-type
interface-number rip process-id enable
[ exclude-subip ]
Remarks
N/A
By default, RIP is disabled.
N/A
N/A
By default, RIP is disabled on an interface.
Controlling RIP reception and advertisement on interfaces
Step
1. Enter system view.
2. Enter RIP view.
3. Disable an interface from sending RIP messages.
4. Return to system view.
5. Enter interface view.
6. Enable an interface to receive RIP messages.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A silent-interface { interface-type interface-number | all }
By default, all RIP-enabled interfaces can send RIP messages.
The disabled interface can still receive RIP messages and respond to unicast requests containing unknown ports.
N/A quit interface interface-type interface-number rip input
7. Enable an interface to send
RIP messages. rip output
N/A
By default, a RIP-enabled interface can receive RIP messages.
By default, a RIP-enabled interface can send RIP messages.
28
Configuring a RIP version
You can configure a global RIP version in RIP view or an interface-specific RIP version in interface view.
An interface preferentially uses the interface-specific RIP version. If no interface-specific version is specified, the interface uses the global RIP version. If neither a global nor interface-specific RIP version is configured, the interface sends RIPv1 broadcasts and can receive the following:
•
RIPv1 broadcasts and unicasts.
•
RIPv2 broadcasts, multicasts, and unicasts.
To configure a RIP version:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Specify a global RIP version. version { 1 | 2 }
4. Return to system view.
By default, no global version is specified. An interface sends
RIPv1 broadcasts, and can receive RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts.
N/A
5. Enter interface view. quit interface interface-type interface-number
N/A
6. Specify a RIP version for the interface. rip version { 1 | 2 [ broadcast | multicast ] }
By default, no interface-specific
RIP version is specified. The interface sends RIPv1 broadcasts, and can receive
RIPv1 broadcasts and unicasts, and RIPv2 broadcasts, multicasts, and unicasts.
Configuring RIP route control
Before you configure RIP route control, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring routers.
•
Configure basic RIP.
Configuring an additional routing metric
An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIP route.
An outbound additional metric is added to the metric of a sent route, and it does not change the route's metric in the routing table.
An inbound additional metric is added to the metric of a received route before the route is added into the routing table, and the route's metric is changed. If the sum of the additional metric and the original metric is greater than 16, the metric of the route is 16.
To configure additional routing metrics:
29
Step
1. Enter system view.
2. Enter interface view.
3. Specify an inbound additional routing metric.
4. Specify an outbound additional routing metric.
Command system-view interface interface-type interface-number rip metricin [ route-policy route-policy-name ] value rip metricout [ route-policy route-policy-name ] value
Remarks
N/A
N/A
The default setting is 0.
The default setting is 1.
Configuring RIPv2 route summarization
Perform this task to summarize contiguous subnets into a summary network and sends the network to neighbors. The smallest metric among all summarized routes is used as the metric of the summary route.
Enabling RIPv2 automatic route summarization
Automatic summarization enables RIPv2 to generate a natural network for contiguous subnets. For example, suppose there are three subnet routes 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24.
Automatic summarization automatically creates and advertises a summary route 10.0.0.0/8 instead of the more specific routes.
To enable RIPv2 automatic route summarization:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. (Optional.) Enable RIPv2 automatic route summarization. summary
By default, RIPv2 automatic route summarization is enabled.
If subnets in the routing table are not contiguous, disable automatic route summarization to advertise more specific routes.
Advertising a summary route
Perform this task to manually configure a summary route.
For example, suppose contiguous subnets routes 10.1.1.0/24, 10.1.2.0/24, and 10.1.3.0/24 exist in the routing table. You can create a summary route 10.1.0.0/16 on GigabitEthernet 1/0/1 to advertise the summary route instead of the more specific routes.
To configure a summary route:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Disable RIPv2 automatic route summarization.
4. Return to system view. undo summary quit
By default, RIPv2 automatic route summarization is enabled.
N/A
30
Step
5. Enter interface view.
6. Configure a summary route.
Command
interface interface-type interface-number
Remarks
N/A
rip summary-address
ip-address { mask-length | mask }
By default, no summary route is configured.
Disabling host route reception
Perform this task to disable RIPv2 from receiving host routes from the same network to save network resources. This feature does not apply to RIPv1.
To disable RIP from receiving host routes:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Disable RIP from receiving host routes. undo host-route
By default, RIP receives host routes.
Advertising a default route
You can advertise a default route on all RIP interfaces in RIP view or on a specific RIP interface in interface view. The interface view setting takes precedence over the RIP view settings.
To disable an interface from advertising a default route, use the rip default-route no-originate command on the interface.
To configure RIP to advertise a default route:
Step
1. Enter system view.
2. Enter RIP view.
3. Enable RIP to advertise a default route.
4. Return to system view.
5. Enter interface view.
6. Configure the RIP interface to advertise a default route.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ] default-route { only | originate }
[ cost cost-value | route-policy route-policy-name ] * quit interface interface-type interface-number rip default-route { { only | originate } [ cost cost-value |
route-policy route-policy-name ]
* | no-originate }
Remarks
N/A
N/A
By default, RIP does not advertise a default route.
N/A
N/A
By default, a RIP interface can advertise a default route if the RIP process is enabled to advertise a default route.
NOTE:
The router enabled to advertise a default route does not accept default routes from RIP neighbors.
31
Configuring received/redistributed route filtering
Perform this task to filter received and redistributed routes by using a filtering policy.
To configure route filtering:
Step
1. Enter system view.
2. Enter RIP view.
3. Configure the filtering of received routes.
4. Configure the filtering of redistributed routes.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A filter-policy { ipv4 acl-number | gateway prefix-list-name | prefix-list prefix-list-name [ gateway prefix-list-name ] } import
[ interface-type interface-number ]
By default, the filtering of received routes is not configured.
This command filters received routes. Filtered routes are not installed into the routing table or advertised to neighbors. filter-policy { ipv4 acl-number | prefix-list prefix-list-name } export
[ protocol [ process-id ] | interface-type interface-number ]
By default, the filtering of redistributed routes is not configured.
This command filters redistributed routes, including routes redistributed with the import-route command.
Setting a preference for RIP
If multiple IGPs find routes to the same destination, the route found by the IGP that has the highest priority is selected as the optimal route. Perform this task to assign a preference to RIP. The smaller the preference value, the higher the priority.
To set a preference for RIP:
Step
1. Enter system view.
Remarks
N/A
2. Enter RIP view.
3. Set a preference for RIP.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ] preference { preference | route-policy route-policy-name }
*
N/A
The default setting is 100.
Configuring RIP route redistribution
Perform this task to configure RIP to redistribute routes from other routing protocols, including OSPF,
IS-IS, BGP, static, and direct.
To configure RIP route redistribution:
Step
1. Enter system view.
Command system-view
Remarks
N/A
32
Step
2. Enter RIP view.
Command rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
3. Redistribute routes from another routing protocol.
import-route protocol
[ as-number ] [ process-id | all-processes | allow-ibgp ]
[ allow-direct | cost cost-value |
route-policy route-policy-name |
tag tag ] *
By default, RIP route redistribution is disabled.
This command can redistribute only active routes. To view active routes, use the display ip routing-table protocol command.
4. (Optional.) Set a default cost for redistributed routes.
default cost cost-value The default setting is 0.
Tuning and optimizing RIP networks
Configuration prerequisites
Before you tune and optimize RIP networks, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Configure basic RIP.
Setting RIP timers
You can change the RIP network convergence speed by adjusting the following RIP timers:
•
Update timer —Specifies the interval between route updates.
•
Timeout timer —Specifies the route aging time. If no update for a route is received within the aging time, the metric of the route is set to 16.
•
Suppress timer —Specifies how long a RIP route stays in suppressed state. When the metric of a route is 16, the route enters the suppressed state. A suppressed route can be replaced by an updated route that is received from the same neighbor before the suppress timer expires and has a metric less than 16.
•
Garbage-collect timer —Specifies the interval from when the metric of a route becomes 16 to when it is deleted from the routing table. RIP advertises the route with a metric of 16. If no update is announced for that route before the garbage-collect timer expires, the route is deleted from the routing table.
IMPORTANT:
To avoid unnecessary traffic or route flapping, configure identical RIP timer settings on RIP routers.
To set RIP timers:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
33
Step
3. Set RIP timers.
Command timers { garbage-collect garbage-collect-value | suppress suppress-value | timeout timeout-value | update update-value } *
Remarks
By default:
•
The garbage-collect timer is 120 seconds.
•
The suppress timer is 120 seconds.
•
The timeout timer is 180 seconds.
•
The update timer is 30 seconds.
Enabling split horizon and poison reverse
The split horizon and poison reverse functions can prevent routing loops.
If both split horizon and poison reverse are configured, only the poison reverse function takes effect.
Enabling split horizon
Split horizon disables RIP from sending routes through the interface where the routes were learned to prevent routing loops between adjacent routers.
To enable split horizon:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable split horizon. rip split-horizon
By default, split horizon is enabled.
Enabling poison reverse
Poison reverse allows RIP to send routes through the interface where the routes were learned. The metric of these routes is always set to 16 (unreachable) to avoid routing loops between neighbors.
To enable poison reverse:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable poison reverse. rip poison-reverse
By default, poison reverse is disabled.
Setting the maximum number of RIP ECMP routes
Perform this task to implement load sharing over ECMP routes.
To set the maximum number of RIP ECMP routes:
Step
1. Enter system view.
Command system-view
Remarks
N/A
34
Step
2. Enter RIP view.
Command rip [ process-id ] [ vpn-instance vpn-instance-name ]
3. Set the maximum number of
RIP ECMP routes. maximum load-balancing number
Remarks
N/A
By default, the maximum number of RIP ECMP routes equals the maximum number of ECMP routes supported by the system.
Enabling zero field check on incoming RIPv1 messages
Some fields in the RIPv1 message must be set to zero. These fields are called "zero fields." You can enable zero field check on incoming RIPv1 messages. If a zero field of a message contains a non-zero value, RIP does not process the message. If you are certain that all messages are trustworthy, disable zero field check to save CPU resources.
This feature does not apply to RIPv2 packets, because they have no zero fields.
To enable zero field check on incoming RIPv1 messages:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable zero field check on incoming RIPv1 messages. checkzero The default setting is enabled.
Enabling source IP address check on incoming RIP updates
Perform this task to enable source IP address check on incoming RIP updates.
Upon receiving a message, RIP compares the source IP address of the message with the IP address of the receiving interface. If they are not in the same network segment, RIP discards the message.
To enable source IP address check on incoming RIP updates:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable source IP address check on incoming RIP messages. validate-source-address
By default, this function is enabled.
Configuring RIPv2 message authentication
Perform this task to enable authentication on RIPv2 messages. This feature does not apply to RIPv1 because RIPv1 does not support authentication. Although you can specify an authentication mode for RIPv1 in interface view, the configuration does not take effect.
RIPv2 supports two authentication modes: simple authentication and MD5 authentication.
To configure RIPv2 message authentication:
35
Step
1. Enter system view.
2. Enter interface view.
3. Configure RIPv2 authentication.
Command system-view interface interface-type interface-number rip authentication-mode { md5 { rfc2082
{ cipher | plain } string key-id | rfc2453
{ cipher | plain } string } | simple { cipher | plain } string }
Remarks
N/A
N/A
By default, RIPv2 authentication is not configured.
Setting the RIP triggered update interval
Perform this task to avoid network overhead and reduce system resource consumption caused by frequent RIP triggered updates.
You can use the timer triggered command to set the maximum interval, minimum interval, and incremental interval for sending RIP triggered updates.
•
For a stable network, the minimum-interval is used.
•
If network changes become frequent, the incremental interval incremental-interval is used to extend the triggered update sending interval until the maximum-interval is reached.
To set the triggered update interval:
Step
1. Enter system view.
2. Enter RIP view.
3. Set the RIP triggered update interval.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
timer triggered maximum-interval
[ minimum-interval [ incremental-interval ] ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is
50 milliseconds.
•
The incremental interval is 200 milliseconds.
Specifying a RIP neighbor
Typically RIP messages are sent in broadcast or multicast. To enable RIP on a link that does not support broadcast or multicast, you must manually specify RIP neighbors.
Follow these guidelines when you specify a RIP neighbor:
•
Do not use the peer ip-address command when the neighbor is directly connected. Otherwise, the neighbor might receive both unicast and multicast (or broadcast) messages of the same routing information.
•
If the specified neighbor is not directly connected, disable source address check on incoming updates.
To specify a RIP neighbor:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
36
Step
3. Specify a RIP neighbor. peer ip-address
4. Disable source IP address check on inbound RIP updates
Command undo validate-source-address
Remarks
By default, RIP does not unicast updates to any peer.
By default, source IP address check on inbound
RIP updates is enabled.
Configuring RIP network management
You can use network management software to manage the RIP process to which MIB is bound.
To configure RIP network management:
Step Command
1. Enter system view.
system-view
2. Bind MIB to a RIP process. rip mib-binding process-id
Remarks
N/A
By default, MIB is bound to the
RIP process with the smallest process ID.
Configuring the RIP packet sending rate
Perform this task to set the interval for sending RIP packets and the maximum number of RIP packets that can be sent at each interval. This feature can avoid excessive RIP packets from affecting system performance and consuming too much bandwidth.
To configure the RIP packet sending rate:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Set the interval for sending
RIP packets and the maximum number of RIP packets that can be sent at each interval.
4. Return to system view.
output-delay time count count
By default, an interface sends up to three RIP packets every 20 milliseconds.
N/A
5. Enter interface view. quit interface interface-type
interface-number
N/A
6. Set the interval for sending
RIP packets and the maximum number of RIP packets that can be sent at each interval.
rip output-delay time count
count
By default, the interface uses the
RIP packet sending rate configured for the RIP process that the interface runs.
37
Setting the maximum length of RIP packets
CAUTION:
The supported maximum length of RIP packets varies by vendor. Use this feature with caution to avoid compatibility issues.
The packet length of RIP packets determines how many routes can be carried in a RIP packet. Set the maximum length of RIP packets to make good use of link bandwidth.
When authentication is enabled, follow these guidelines to ensure packet forwarding:
•
For simple authentication, the maximum length of RIP packets must be no less than 52 bytes.
•
For MD5 authentication (with packet format defined in RFC 2453), the maximum length of RIP packets must be no less than 56 bytes.
•
For MD5 authentication (with packet format defined in RFC 2082), the maximum length of RIP packets must be no less than 72 bytes.
To set the maximum length of RIP packets:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Set the maximum length of
RIP packets. rip max-packet-length value
By default, the maximum length of
RIP packets is 512 bytes.
Setting the DSCP value for outgoing RIP packets
The DSCP value specifies the precedence of outgoing packets.
To set the DSCP value for outgoing RIP packets:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
3. Set the DSCP value for outgoing RIP packets.
dscp dscp-value
Remarks
N/A
N/A
By default, the DSCP value for outgoing RIP packets is 48.
Configuring RIP GR
GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Two routers are required to complete a GR process. The following are router roles in a GR process:
•
GR restarter —Graceful restarting router. It must have GR capability.
•
GR helper —A neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
After RIP restarts on a router, the router must learn RIP routes again and update its FIB table, which causes network disconnections and route reconvergence.
38
With the GR feature, the restarting router (known as the GR restarter) can notify the event to its GR capable neighbors. GR capable neighbors (known as GR helpers) maintain their adjacencies with the router within a GR interval. During this process, the FIB table of the router does not change. After the restart, the router contacts its neighbors to retrieve its FIB.
By default, a RIP-enabled device acts as the GR helper. Perform this task on the GR restarter.
IMPORTANT:
You cannot enable RIP NSR on a device that acts as GR restarter.
To configure GR on the GR restarter:
Step
1. Enter system view.
2. Enter RIP view.
3. Enable GR for RIP.
4. (Optional.) Set the GR interval.
Command system-view
Remarks
N/A rip [ process-id ] [ vpn-instance vpn-instance-name ] graceful-restart
N/A
By default, RIP GR is disabled. graceful-restart interval interval
By default, the GR interval is 60 seconds.
Enabling RIP NSR
Nonstop Routing (NSR) allows the device to back up the routing information from the active RIP process to the standby RIP process. After an active/standby switchover, NSR can complete route regeneration without tearing down adjacencies or impacting forwarding services.
NSR does not require the cooperation of neighboring devices to recover routing information, and it is typically used more often than GR.
IMPORTANT:
A device that has RIP NSR enabled cannot act as GR restarter.
To enable RIP NSR:
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable RIP NSR. non-stop-routing
By default, RIP NSR is disabled.
RIP NSR enabled for a RIP process takes effect only on that process. As a best practice, enable RIP NSR for each process if multiple RIP processes exist.
Configuring BFD for RIP
RIP detects route failures by periodically sending requests. If it receives no response for a route within a certain time, RIP considers the route unreachable. To speed up convergence, perform this
39
task to enable BFD for RIP. For more information about BFD, see High Availability Configuration
Guide .
RIP supports the following BFD detection modes:
•
Single-hop echo detection —Detection mode for a direct neighbor. In this mode, a BFD session is established only when the directly connected neighbor has route information to send.
•
Single-hop echo detection for a specific destination —In this mode, a BFD session is established to the specified RIP neighbor when RIP is enabled on the local interface.
•
Bidirectional control detection —Detection mode for an indirect neighbor. In this mode, a
BFD session is established only when both ends have routes to send and BFD is enabled on the receiving interface.
Configuring single-hop echo detection (for a directly connected RIP neighbor)
Step
1. Enter system view.
2. Configure the source IP address of BFD echo packets.
3. Enter interface view.
Command system-view
bfd echo-source-ip ip-address interface interface-type interface-number rip bfd enable
Remarks
N/A
By default, the source IP address of BFD echo packets is not configured.
N/A
By default, BFD for RIP is disabled.
4. Enable BFD for RIP.
Configuring single-hop echo detection (for a specific destination)
When a unidirectional link occurs between the local device and a specific neighbor, BFD can detect the failure. The local device will not receive or send any RIP packets through the interface connected to the neighbor to improve convergence speed. When the link recovers, the interface can send RIP packets again.
This feature applies to RIP neighbors that are directly connected.
To configure BFD for RIP (single hop echo detection for a specific destination):
Step
1. Enter system view.
2. Configure the source IP address of BFD echo packets.
Command system-view
bfd echo-source-ip ip-address
Remarks
N/A
By default, no source IP address is configured for BFD echo packets.
3. Enter interface view.
4. Enable BFD for RIP. interface interface-type interface-number rip bfd enable destination
ip-address
N/A
By default, BFD for RIP is disabled.
40
Configuring bidirectional control detection
Step
1. Enter system view.
2. Enter RIP view.
3. Specify a RIP neighbor.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
peer ip-address interface interface-type interface-number rip bfd enable
N/A
By default, RIP does not unicast updates to any peer.
Because the undo peer command does not remove the neighbor relationship immediately, executing the command cannot bring down the
BFD session immediately.
N/A
By default, BFD is disabled on a
RIP interface.
4. Enter interface view.
5. Enable BFD on the RIP interface.
Configuring RIP FRR
A link or router failure on a path can cause packet loss and even routing loop until RIP completes routing convergence based on the new network topology. FRR enables fast rerouting to minimize the impact of link or node failures.
Figure 6 Network diagram for RIP FRR
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
As shown in Figure 6 , configure FRR on Router B by using a routing policy to specify a backup next
hop. When the primary link fails, RIP directs packets to the backup next hop. At the same time, RIP calculates the shortest path based on the new network topology, and forwards packets over that path after network convergence.
Configuration restrictions and guidelines
•
RIP FRR takes effect only for RIP routes learned from directly connected neighbors.
•
RIP FRR is available only when the state of primary link (with Layer 3 interfaces staying up) changes from bidirectional to unidirectional or down.
•
Equal-cost routes do not support RIP FRR.
41
Configuration prerequisites
You must specify a next hop by using the apply fast-reroute backup-interface command in a routing policy and reference the routing policy for FRR. For more information about routing policy
configuration, see " Configuring routing policies ."
Configuring RIP FRR
Step
1. Enter system view.
2. Enter RIP view.
Command system-view rip [ process-id ] [ vpn-instance vpn-instance-name ] fast-reroute route-policy route-policy-name
Remarks
N/A
N/A
By default, RIP FRR is disabled. 3. Configure RIP FRR.
Enabling BFD for RIP FRR
By default, RIP FRR does not use BFD to detect primary link failures. To speed up RIP convergence, enable BFD single-hop echo detection for RIP FRR to detect primary link failures.
To configure BFD for RIP FRR:
Step
1. Enter system view.
2. Configure the source IP address of BFD echo packets.
Command system-view
bfd echo-source-ip ip-address
Remarks
N/A
By default, the source IP address of BFD echo packets is not 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 High Availability
Command Reference .
3. Enter interface view.
4. Enable BFD for RIP FRR. interface interface-type interface-number rip primary-path-detect bfd echo
N/A
By default, BFD for RIP FRR is disabled.
Displaying and maintaining RIP
Execute display commands in any view and execute reset commands in user view.
Command Task
Display RIP current status and configuration information. display rip [ process-id ]
Display active routes in the RIP database.
Display RIP GR information.
display rip process-id database [ ip-address
{ mask-length | mask } ] display rip [ process-id ] graceful-restart
42
Task
Display RIP interface information.
Display neighbor information for a RIP process.
Display RIP NSR information.
Display routing information for a RIP process.
Command
display rip process-id interface [ interface-type interface-number ] display rip process-id neighbor [ interface-type interface-number ] display rip [ process-id ] non-stop-routing
display rip process-id route [ ip-address
{ mask-length | mask } [ verbose ] | peer ip-address | statistics ]
reset rip process-id process
reset rip process-id statistics
Reset a RIP process.
Clear the statistics for a RIP process.
RIP configuration examples
Configuring basic RIP
Network requirements
As shown in Figure 7 , enable RIPv2 on all interfaces on Switch A and Switch B. Configure Switch B
to not advertise route 10.2.1.0/24 to Switch A, and to accept only route 2.1.1.0/24 from Switch A.
Figure 7 Network diagram
Vlan-int101
3.1.1.1/24
Vlan-int102
2.1.1.1/24
Switch A
Vlan-int100
1.1.1.1/24
Configuration procedure
Vlan-int101
10.2.1.1/24
Vlan-int100
1.1.1.2/24
Switch B
Vlan-int102
10.1.1.2/24
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP by using either of the following methods:
(Method 1) # Enable RIP on the specified networks on Switch A.
<SwitchA> system-view
[SwitchA] rip
[SwitchA-rip-1] network 1.0.0.0
[SwitchA-rip-1] network 2.0.0.0
[SwitchA-rip-1] network 3.0.0.0
[SwitchA-rip-1] quit
(Method 2) # Enable RIP on the specified interfaces on Switch B.
<SwitchB> system-view
[SwitchB] rip
[SwitchB-rip-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] rip 1 enable
[SwitchB-Vlan-interface100] quit
[SwitchB] interface vlan-interface 101
43
[SwitchB-Vlan-interface101] rip 1 enable
[SwitchB-Vlan-interface101] quit
[SwitchB] interface vlan-interface 102
[SwitchB-Vlan-interface102] rip 1 enable
[SwitchB-Vlan-interface102] quit
# Display the RIP routing table of Switch A.
[SwitchA] display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 1.1.1.2 on Vlan-interface100
Destination/Mask Nexthop Cost Tag Flags Sec
10.0.0.0/8 1.1.1.2 1 0 RAOF 11
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
1.1.1.0/24 0.0.0.0 0 0 RDOF -
2.1.1.0/24 0.0.0.0 0 0 RDOF -
3.1.1.0/24 0.0.0.0 0 0 RDOF -
The output shows that RIPv1 uses a natural mask.
3. Configure a RIP version:
# Configure RIPv2 on Switch A.
[SwitchA] rip
[SwitchA-rip-1] version 2
[SwitchA-rip-1] undo summary
[SwitchA-rip-1] quit
# Configure RIPv2 on Switch B.
[SwitchB] rip
[SwitchB-rip-1] version 2
[SwitchB-rip-1] undo summary
[SwitchB-rip-1] quit
# Display the RIP routing table on Switch A.
[SwitchA] display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 1.1.1.2 on Vlan-interface100
Destination/Mask Nexthop Cost Tag Flags Sec
10.0.0.0/8 1.1.1.2 1 0 RAOF 50
10.2.1.0/24 1.1.1.2 1 0 RAOF 16
10.1.1.0/24 1.1.1.2 1 0 RAOF 16
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
1.1.1.0/24 0.0.0.0 0 0 RDOF -
2.1.1.0/24 0.0.0.0 0 0 RDOF -
3.1.1.0/24 0.0.0.0 0 0 RDOF -
44
The output shows that RIPv2 uses classless subnet masks.
NOTE:
After RIPv2 is configured, RIPv1 routes might still exist in the routing table until they are aged out.
# Display the RIP routing table on Switch B.
[SwitchB] display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 1.1.1.1 on Vlan-interface100
Destination/Mask Nexthop Cost Tag Flags Sec
2.1.1.0/24 192.168.1.3 1 0 RAOF 19
3.1.1.0/24 192.168.1.3 1 0 RAOF 19
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
1.1.1.0/24 0.0.0.0 0 0 RDOF -
10.1.1.0/24 0.0.0.0 0 0 RDOF -
10.2.1.0/24 0.0.0.0 0 0 RDOF -
4. Configure route filtering:
# Reference IP prefix lists on Switch B to filter received and redistributed routes.
[SwitchB] ip prefix-list aaa index 10 permit 2.1.1.0 24
[SwitchB] ip prefix-list bbb index 10 deny 10.2.1.0 24
[SwitchB] ip prefix-list bbb index 11 permit 0.0.0.0 0 less-equal 32
[SwitchB] rip 1
[SwitchB-rip-1] filter-policy prefix-list aaa import
[SwitchB-rip-1] filter-policy prefix-list bbb export
[SwitchB-rip-1] quit
# Display the RIP routing table on Switch A.
[SwitchA] display rip 100 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
----------------------------------------------------------------------------
Peer 1.1.1.2 on Vlan-interface100
Destination/Mask Nexthop Cost Tag Flags Sec
10.1.1.0/24 1.1.1.2 1 0 RAOF 19
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
1.1.1.0/24 0.0.0.0 0 0 RDOF -
2.1.1.0/24 0.0.0.0 0 0 RDOF -
3.1.1.0/24 0.0.0.0 0 0 RDOF -
# Display the RIP routing table on Switch B.
[SwitchB] display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
45
Peer 1.1.1.1 on Vlan-interface100
Destination/Mask Nexthop Cost Tag Flags Sec
2.1.1.0/24 1.1.1.3 1 0 RAOF 19
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
1.1.1.0/24 0.0.0.0 0 0 RDOF -
10.1.1.0/24 0.0.0.0 0 0 RDOF -
10.2.1.0/24 0.0.0.0 0 0 RDOF -
Configuring RIP route redistribution
Network requirements
As shown in Figure 8 , Switch B communicates with Switch A through RIP 100 and with Switch C
through RIP 200.
Configure RIP 200 to redistribute direct routes and routes from RIP 100 on Switch B so Switch C can learn routes destined for 10.2.1.0/24 and 11.1.1.0/24. Switch A cannot learn routes destined for
12.3.1.0/24 and 16.4.1.0/24.
Figure 8 Network diagram
RIP 100
Vlan-int101
10.2.1.1/24
Switch A
Vlan-int100
11.1.1.1/24
Eth1/1 Vlan-int100
11.1.1.2/24
Switch B
Vlan-int200
12.3.1.1/24
RIP 200
Vlan-int200
12.3.1.2/24
Switch C
Vlan-int400
16.4.1.1/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP:
# Enable RIP 100, and configure RIPv2 on Switch A.
<SwitchA> system-view
[SwitchA] rip 100
[SwitchA-rip-100] network 10.0.0.0
[SwitchA-rip-100] network 11.0.0.0
[SwitchA-rip-100] version 2
[SwitchA-rip-100] undo summary
[SwitchA-rip-100] quit
# Enable RIP 100 and RIP 200, and configure RIPv2 on Switch B.
<SwitchB> system-view
[SwitchB] rip 100
[SwitchB-rip-100] network 11.0.0.0
[SwitchB-rip-100] version 2
[SwitchB-rip-100] undo summary
[SwitchB-rip-100] quit
[SwitchB] rip 200
[SwitchB-rip-200] network 12.0.0.0
[SwitchB-rip-200] version 2
[SwitchB-rip-200] undo summary
46
[SwitchB-rip-200] quit
# Enable RIP 200, and configure RIPv2 on Switch C.
<SwitchC> system-view
[SwitchC] rip 200
[SwitchC-rip-200] network 12.0.0.0
[SwitchC-rip-200] network 16.0.0.0
[SwitchC-rip-200] version 2
[SwitchC-rip-200] undo summary
[SwitchC-rip-200] quit
# Display the IP routing table on Switch C.
[SwitchC] display ip routing-table
Destinations : 13 Routes : 13
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
12.3.1.0/24 Direct 0 0 12.3.1.2 Vlan200
12.3.1.0/32 Direct 0 0 12.3.1.2 Vlan200
12.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0
12.3.1.255/32 Direct 0 0 12.3.1.2 Vlan200
16.4.1.0/24 Direct 0 0 16.4.1.1 Vlan400
16.4.1.0/32 Direct 0 0 16.4.1.1 Vlan400
16.4.1.1/32 Direct 0 0 127.0.0.1 InLoop0
16.4.1.255/32 Direct 0 0 16.4.1.1 Vlan400
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
3. Configure route redistribution:
# Configure RIP 200 to redistribute routes from RIP 100 and direct routes on Switch B.
[SwitchB] rip 200
[SwitchB-rip-200] import-route rip 100
[SwitchB-rip-200] import-route direct
[SwitchB-rip-200] quit
# Display the IP routing table on Switch C.
[SwitchC] display ip routing-table
Destinations : 15 Routes : 15
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.2.1.0/24 RIP 100 1 12.3.1.1 Vlan200
11.1.1.0/24 RIP 100 1 12.3.1.1 Vlan200
12.3.1.0/24 Direct 0 0 12.3.1.2 Vlan200
12.3.1.0/32 Direct 0 0 12.3.1.2 Vlan200
12.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0
12.3.1.255/32 Direct 0 0 12.3.1.2 Vlan200
16.4.1.0/24 Direct 0 0 16.4.1.1 Vlan400
47
16.4.1.0/32 Direct 0 0 16.4.1.1 Vlan400
16.4.1.1/32 Direct 0 0 127.0.0.1 InLoop0
16.4.1.255/32 Direct 0 0 16.4.1.1 Vlan400
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
Configuring an additional metric for a RIP interface
Network requirements
Switch E.
Switch A has two links to Switch D. The link from Switch B to Switch D is more stable than that from
Switch C to Switch D. Configure an additional metric for RIP routes received from VLAN-interface
200 on Switch A so Switch A prefers route 1.1.5.0/24 learned from Switch B.
Figure 9 Network diagram
Switch A
Vlan-int100
1.1.1.1/24
Vlan-int100
1.1.1.2/24
Vlan-int200
1.1.2.1/24
Vlan-int200
1.1.2.2/24
Switch B
Vlan-int400
1.1.3.1/24
Vlan-int300
1.1.4.2/24
Vlan-int400
1.1.3.2/24
Vlan-int500
Switch D
1.1.5.1/24
Vlan-int500
1.1.5.2/24
Vlan-int300
1.1.4.1/24
Switch C
Switch E
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] rip 1
[SwitchA-rip-1] network 1.0.0.0
[SwitchA-rip-1] version 2
[SwitchA-rip-1] undo summary
[SwitchA-rip-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] rip 1
[SwitchB-rip-1] network 1.0.0.0
[SwitchB-rip-1] version 2
[SwitchB-rip-1] undo summary
# Configure Switch C.
<SwitchC> system-view
[SwitchB] rip 1
[SwitchC-rip-1] network 1.0.0.0
[SwitchC-rip-1] version 2
48
[SwitchC-rip-1] undo summary
# Configure Switch D.
<SwitchD> system-view
[SwitchD] rip 1
[SwitchD-rip-1] network 1.0.0.0
[SwitchD-rip-1] version 2
[SwitchD-rip-1] undo summary
# Configure Switch E.
<SwitchE> system-view
[SwitchE] rip 1
[SwitchE-rip-1] network 1.0.0.0
[SwitchE-rip-1] version 2
[SwitchE-rip-1] undo summary
# Display all active routes in the RIP database on Switch A.
[SwitchA] display rip 1 database
1.0.0.0/8, auto-summary
1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface
1.1.2.0/24, cost 0, nexthop 1.1.2.1, RIP-interface
1.1.3.0/24, cost 1, nexthop 1.1.1.2
1.1.4.0/24, cost 1, nexthop 1.1.2.2
1.1.5.0/24, cost 2, nexthop 1.1.1.2
1.1.5.0/24, cost 2, nexthop 1.1.2.2
The output shows two RIP routes destined for network 1.1.5.0/24, with the next hops as Switch
B (1.1.1.2) and Switch C (1.1.2.2), and with the same cost of 2.
3. Configure an additional metric for a RIP interface:
# Configure an inbound additional metric of 3 for RIP-enabled interface VLAN-interface 200 on
Switch A.
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] rip metricin 3
# Display all active routes in the RIP database on Switch A.
[SwitchA-Vlan-interface200] display rip 1 database
1.0.0.0/8, auto-summary
1.1.1.0/24, cost 0, nexthop 1.1.1.1, RIP-interface
1.1.2.0/24, cost 0, nexthop 1.1.2.1, RIP-interface
1.1.3.0/24, cost 1, nexthop 1.1.1.2
1.1.4.0/24, cost 2, nexthop 1.1.1.2
1.1.5.0/24, cost 2, nexthop 1.1.1.2
The output shows that only one RIP route reaches network 1.1.5.0/24, with the next hop as
Switch B (1.1.1.2) and a cost of 2.
Configuring RIP to advertise a summary route
Network requirements
As shown in Figure 10 , Switch A and Switch B run OSPF, Switch D runs RIP, and Switch C runs
OSPF and RIP. Configure RIP to redistribute OSPF routes on Switch C so Switch D can learn routes destined for networks 10.1.1.0/24, 10.2.1.0/24, 10.5.1.0/24, and 10.6.1.0/24.
To reduce the routing table size of Switch D, configure route summarization on Switch C to advertise only the summary route 10.0.0.0/8 to Switch D.
49
Figure 10 Network diagram
Vlan-int200
10.1.1.1/24
Vlan-int500
10.6.1.2/24
Vlan-int300
11.3.1.1/24
Vlan-int200
10.1.1.2/24
Switch C
Vlan-int100
10.2.1.2/24
Vlan-int100
10.2.1.1/24
Switch B
Switch A
Vlan-int600
10.5.1.2/24
OSPF
RIP
Vlan-int400
11.4.1.2/24
Switch D
Vlan-int300
11.3.1.2/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 10.5.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 10.6.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
3. Configure basic RIP:
# Configure Switch C.
[SwitchC] rip 1
[SwitchC-rip-1] network 11.3.1.0
[SwitchC-rip-1] version 2
[SwitchC-rip-1] undo summary
# Configure Switch D.
<SwitchD> system-view
[SwitchD] rip 1
50
[SwitchD-rip-1] network 11.0.0.0
[SwitchD-rip-1] version 2
[SwitchD-rip-1] undo summary
[SwitchD-rip-1] quit
# Configure RIP to redistribute routes from OSPF process 1 and direct routes on Switch C.
[SwitchC-rip-1] import-route direct
[SwitchC-rip-1] import-route ospf 1
[SwitchC-rip-1] quit
# Display the IP routing table on Switch D.
[SwitchD] display ip routing-table
Destinations : 15 Routes : 15
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.1.1.0/24 RIP 100 1 11.3.1.1 Vlan300
10.2.1.0/24 RIP 100 1 11.3.1.1 Vlan300
10.5.1.0/24 RIP 100 1 11.3.1.1 Vlan300
10.6.1.0/24 RIP 100 1 11.3.1.1 Vlan300
11.3.1.0/24 Direct 0 0 11.3.1.2 Vlan300
11.3.1.0/32 Direct 0 0 11.3.1.2 Vlan300
11.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0
11.4.1.0/24 Direct 0 0 11.4.1.2 Vlan400
11.4.1.0/32 Direct 0 0 11.4.1.2 Vlan400
11.4.1.2/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
4. Configure route summarization:
# Configure route summarization on Switch C and advertise only the summary route 10.0.0.0/8.
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] rip summary-address 10.0.0.0 8
# Display the IP routing table on Switch D.
[SwitchD] display ip routing-table
Destinations : 12 Routes : 12
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.0.0.0/8 RIP 100 1 11.3.1.1 Vlan300
11.3.1.0/24 Direct 0 0 11.3.1.2 Vlan300
11.3.1.0/32 Direct 0 0 11.3.1.2 Vlan300
11.3.1.2/32 Direct 0 0 127.0.0.1 InLoop0
11.4.1.0/24 Direct 0 0 11.4.1.2 Vlan400
11.4.1.0/32 Direct 0 0 11.4.1.2 Vlan400
11.4.1.2/32 Direct 0 0 127.0.0.1 InLoop0
127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0
51
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
Configuring RIP GR
Network requirements
As shown in Figure 11 , Switch A, Switch B, and Switch C all run RIPv2.
•
Enable GR on Switch A. Switch A acts as the GR restarter.
•
Switch B and Switch C act as GR helpers to synchronize their routing tables with Switch A by using GR.
Figure 11 Network diagram
Router ID: 1.1.1.1
GR restarter
Switch A
Vlan-int100
192.1.1.1/24
Vlan-int100
192.1.1.2/24
Switch B
Vlan-int100
192.1.1.3/24
Switch C
GR helper
Router ID: 2.2.2.2
GR helper
Router ID: 3.3.3.3
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure RIPv2 on the switches to ensure the following: (Details not shown.)
Switch A, Switch B, and Switch C can communicate with each other at Layer 3.
Dynamic route update can be implemented among them with RIPv2.
3. Enable RIP GR on Switch A.
<SwitchA> system-view
[SwitchA] rip
[SwitchA-rip-1] graceful-restart
Verifying the configuration
# Trigger a routing protocol restart or active/standby switchover and display GR status on Switch A.
<SwitchA> display rip graceful-restart
RIP process: 1
Graceful Restart capability : Enabled
Current GR state : Normal
Graceful Restart period : 60 seconds
Graceful Restart remaining time : 0 seconds
Configuring RIP NSR
Network requirements
As shown in Figure 12 , Switch A, Switch B, and Switch S all run RIPv2.
52
Enable RIP NSR on Switch S to ensure correct routing when an active/standby switchover occurs on
Switch S.
Figure 12 Network diagram
Loop 0
22.22.22.22/32
Switch A
Vlan-int100
12.12.12.1/24
Vlan-int100
12.12.12.2/24
Switch S
Vlan-int200
14.14.14.1/24
Vlan-int200
14.14.14.2/24
Switch B
Loop 0
44.44.44.44/32
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure RIPv2 on the switches to ensure the following: (Details not shown.)
Switch A, Switch B, and Switch S can communicate with each other at Layer 3.
Dynamic route update can be implemented among them with RIPv2.
3. Enable RIP NSR on Switch S.
<SwitchS> system-view
[SwitchS] rip 100
[SwitchS-rip-100] non-stop-routing
[SwitchS-rip-100] quit
Verifying the configuration
# Perform an active/standby switchover on Switch S.
[SwitchS] placement reoptimize
Predicted changes to the placement
Program Current location New location
--------------------------------------------------------------------- lb 0/0 0/0 lsm 0/0 0/0 slsp 0/0 0/0 rib6 0/0 0/0 routepolicy 0/0 0/0 rib 0/0 0/0 staticroute6 0/0 0/0 staticroute 0/0 0/0 eviisis 0/0 0/0 ospf 0/0 1/0
Continue? [y/n]:y
Re-optimization of the placement start. You will be notified on completion
Re-optimization of the placement complete. Use 'display placement' to view the new placement
# Display neighbor information and route information on Switch A.
[SwitchA] display rip 1 neighbor
Neighbor Address: 12.12.12.2
Interface : Vlan-interface200
Version : RIPv2 Last update: 00h00m13s
Relay nbr : No BFD session: None
Bad packets: 0 Bad routes : 0
[SwitchA] display rip 1 route
53
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 12.12.12.2 on Vlan-interface200
Destination/Mask Nexthop Cost Tag Flags Sec
14.0.0.0/8 12.12.12.2 1 0 RAOF 16
44.0.0.0/8 12.12.12.2 2 0 RAOF 16
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
12.12.12.0/24 0.0.0.0 0 0 RDOF -
22.22.22.22/32 0.0.0.0 0 0 RDOF -
# Display neighbor information and route information on Switch B.
[SwitchB] display rip 1 neighbor
Neighbor Address: 14.14.14.2
Interface : Vlan-interface200
Version : RIPv2 Last update: 00h00m32s
Relay nbr : No BFD session: None
Bad packets: 0 Bad routes : 0
[SwitchB] display rip 1 route
Route Flags: R - RIP, T - TRIP
P - Permanent, A - Aging, S - Suppressed, G - Garbage-collect
D - Direct, O - Optimal, F - Flush to RIB
----------------------------------------------------------------------------
Peer 14.14.14.2 on Vlan-interface200
Destination/Mask Nexthop Cost Tag Flags Sec
12.0.0.0/8 14.14.14.2 1 0 RAOF 1
22.0.0.0/8 14.14.14.2 2 0 RAOF 1
Local route
Destination/Mask Nexthop Cost Tag Flags Sec
44.44.44.44/32 0.0.0.0 0 0 RDOF -
14.14.14.0/24 0.0.0.0 0 0 RDOF -
The output shows that the neighbor and route information on Switch A and Switch B keep unchanged during the active/standby switchover on Switch S. The traffic from Switch A to Switch B has not been impacted.
Configuring BFD for RIP (single-hop echo detection for a directly connected neighbor)
Network requirements
As shown in
Figure 13 , VLAN-interface 100 of Switch A and Switch C runs RIP process 1.
VLAN-interface 200 of Switch A runs RIP process 2. VLAN-interface 300 of Switch C and
VLAN-interface 200 and VLAN-interface 300 of Switch B run RIP process 1.
•
Configure a static route destined for 100.1.1.1/24 and enable static route redistribution into RIP on Switch C. This allows Switch A to learn two routes destined for 100.1.1.1/24 through
VLAN-interface 100 and VLAN-interface 200 respectively, and uses the one through
VLAN-interface 100.
54
•
Enable BFD for RIP on VLAN-interface 100 of Switch A. When the link over VLAN-interface 100 fails, BFD can quickly detect the failure and notify RIP. RIP deletes the neighbor relationship and route information learned on VLAN-interface 100, and uses the route destined for 100.1.1.1
24 through VLAN-interface 200.
Figure 13 Network diagram
Switch B
Vlan-int200
192.168.2.2/24
Vlan-int300
192.168.3.1/24
Vlan-int200
192.168.2.1/24
Vlan-int300
192.168.3.2/24
L2 switch
Switch A
Vlan-int100
192.168.1.1/24
Vlan-int100
192.168.1.2/24
Switch C
BFD
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] rip 1
[SwitchA-rip-1] version 2
[SwitchA-rip-1] undo summary
[SwitchA-rip-1] network 192.168.1.0
[SwitchA-rip-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] rip bfd enable
[SwitchA-Vlan-interface100] quit
[SwitchA] rip 2
[SwitchA-rip-2] version 2
[SwitchA-rip-2] undo summary
[SwitchA-rip-2] network 192.168.2.0
[SwitchA-rip-2] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] rip 1
[SwitchB-rip-1] version 2
[SwitchB-rip-1] undo summary
[SwitchB-rip-1] network 192.168.2.0
[SwitchB-rip-1] network 192.168.3.0
[SwitchB-rip-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] rip 1
55
[SwitchC-rip-1] version 2
[SwitchC-rip-1] undo summary
[SwitchC-rip-1] network 192.168.1.0
[SwitchC-rip-1] network 192.168.3.0
[SwitchC-rip-1] import-route static
[SwitchC-rip-1] quit
3. Configure BFD parameters on VLAN-interface 100 of Switch A.
[SwitchA] bfd echo-source-ip 11.11.11.11
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] bfd min-transmit-interval 500
[SwitchA-Vlan-interface100] bfd min-receive-interval 500
[SwitchA-Vlan-interface100] bfd detect-multiplier 7
[SwitchA-Vlan-interface100] quit
[SwitchA] quit
4. Configure a static route on Switch C.
[SwitchC] ip route-static 120.1.1.1 24 null 0
Verifying the configuration
# Display the BFD session information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 Session Working Under Echo Mode:
LD SourceAddr DestAddr State Holdtime Interface
4 192.168.1.1 192.168.1.2 Up 2000ms Vlan100
# Display RIP routes destined for 120.1.1.0/24 on Switch A.
<SwitchA> display ip routing-table 120.1.1.0 24
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 RIP 100 1 192.168.1.2 Vlan-interface100
The output shows that Switch A communicates with Switch C through VLAN-interface 100. Then the link over VLAN-interface 100 fails.
# Display RIP routes destined for 120.1.1.0/24 on Switch A.
<SwitchA> display ip routing-table 120.1.1.0 24
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
120.1.1.0/24 RIP 100 1 192.168.2.2 Vlan-interface200
The output shows that Switch A communicates with Switch C through VLAN-interface 200.
56
Configuring BFD for RIP (single hop echo detection for a specific destination)
Network requirements
As shown in Figure 14 , VLAN-interface 100 of Switch A and Switch B runs RIP process 1.
VLAN-interface 200 of Switch B and Switch C runs RIP process 1.
•
Configure a static route destined for 100.1.1.0/24 and enable static route redistribution into RIP on both Switch A and Switch C. This allows Switch B to learn two routes destined for
100.1.1.0/24 through VLAN-interface 100 and VLAN-interface 200. The route redistributed from
Switch A has a smaller cost than that redistributed from Switch C, so Switch B uses the route through VLAN-interface 200.
•
Enable BFD for RIP on VLAN-interface 100 of Switch A, and specify VLAN-interface 100 of
Switch B as the destination. When a unidirectional link occurs between Switch A and Switch B,
BFD can quickly detect the link failure and notify RIP. Switch B then deletes the neighbor relationship and the route information learned on VLAN-interface 100. It does not receive or send any packets from VLAN-interface 100. When the route learned from Switch A ages out,
Switch B uses the route destined for 100.1.1.1 24 through VLAN-interface 200.
Figure 14 Network diagram
Switch B
Vlan-int100
192.168.2.2/24
Vlan-int200
192.168.3.1/24
Vlan-int100
192.168.2.1/24
Vlan-int200
192.168.3.2/24
Switch A Switch C
RIP packets
BFD session
Fault
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP and enable BFD on the interfaces:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] rip 1
[SwitchA-rip-1] network 192.168.2.0
[SwitchA-rip-1] import-route static
[SwitchA-rip-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] rip bfd enable destination 192.168.2.2
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] rip 1
[SwitchB-rip-1] network 192.168.2.0
57
[SwitchB-rip-1] network 192.168.3.0
[SwitchB-rip-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] rip 1
[SwitchC-rip-1] network 192.168.3.0
[SwitchC-rip-1] import-route static cost 3
[SwitchC-rip-1] quit
3. Configure BFD parameters on VLAN-interface 100 of Switch A.
[SwitchA] bfd echo-source-ip 11.11.11.11
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] bfd min-echo-receive-interval 500
[SwitchA-Vlan-interface100] return
4. Configure static routes:
# Configure a static route on Switch A.
[SwitchA] ip route-static 100.1.1.0 24 null 0
# Configure a static route on Switch C.
[SwitchA] ip route-static 100.1.1.0 24 null 0
Verifying the configuration
# Display BFD session information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 session working under Echo mode:
LD SourceAddr DestAddr State Holdtime Interface
3 192.168.2.1 192.168.2.2 Up 2000ms vlan100
# Display routes destined for 100.1.1.0/24 on Switch B.
<SwitchB> display ip routing-table 100.1.1.0 24 verbose
Summary Count : 1
Destination: 100.1.1.0/24
Protocol: RIP
Process ID: 1
SubProtID: 0x1 Age: 00h02m47s
Cost: 1 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x12000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 192.168.2.1
Flags: 0x1008c OrigNextHop: 192.168.2.1
Label: NULL RealNextHop: 192.168.2.1
BkLabel: NULL BkNextHop: N/A
58
Tunnel ID: Invalid Interface: vlan-interface 100
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display routes destined for 100.1.1.0/24 on Switch B when the link between Switch A and Switch B fails.
<SwitchB> display ip routing-table 100.1.1.0 24 verbose
Summary Count : 1
Destination: 100.1.1.0/24
Protocol: RIP
Process ID: 1
SubProtID: 0x1 Age: 00h21m23s
Cost: 4 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x12000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 192.168.3.2
Flags: 0x1008c OrigNextHop: 192.168.3.2
Label: NULL RealNextHop: 192.168.3.2
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: vlan-interface 200
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
Configuring BFD for RIP (bidirectional detection in BFD control packet mode)
Network requirements
As shown in Figure 15 , VLAN-interface 100 of Switch A and VLAN-interface 200 of Switch C run RIP
process 1.
VLAN-interface 300 of Switch A runs RIP process 2. VLAN-interface 400 of Switch C, and
VLAN-interface 300 and VLAN-interface 400 of Switch D run RIP process 1.
•
Configure a static route destined for 100.1.1.0/24 on Switch A.
•
Configure a static route destined for 101.1.1.0/24 on Switch C.
•
Enable static route redistribution into RIP on Switch A and Switch C. This allows Switch A to learn two routes destined for 100.1.1.0/24 through VLAN-interface 100 and VLAN-interface 300.
It uses the route through VLAN-interface 100.
•
Enable BFD on VLAN-interface 100 of Switch A and VLAN-interface 200 of Switch C.
When the link over VLAN-interface 100 fails, BFD can quickly detect the link failure and notify RIP.
RIP deletes the neighbor relationship and the route information received learned on VLAN-interface
100. It uses the route destined for 100.1.1.0/24 through VLAN-interface 300.
59
Figure 15 Network diagram
Vlan-int300
Switch D
Vlan-int400
101.1.1.0/24
Vlan-int300
Vlan-int400
Vlan-int100
Vlan-int100
Switch B
Vlan-int200
Vlan-int200
Switch A Switch C
BFD
100.1.1.0/24
Table 7 Interface and IP address assignment
Device
Switch A
Switch A
Switch B
Switch B
Switch C
Switch C
Switch D
Interface
VLAN-interface 300
VLAN-interface 100
VLAN-interface 100
VLAN-interface 200
VLAN-interface 200
VLAN-interface 400
VLAN-interface 300
IP address
192.168.3.1/24
192.168.1.1/24
192.168.1.2/24
192.168.2.1/24
192.168.2.2/24
192.168.4.2/24
192.168.3.2/24
Switch D VLAN-interface 400 192.168.4.1/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic RIP and enable static route redistribution into RIP so Switch A and Switch C have routes to send to each other:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] rip 1
[SwitchA-rip-1] version 2
[SwitchA-rip-1] undo summary
[SwitchA-rip-1] network 192.168.1.0
[SwitchA-rip-1] network 101.1.1.0
[SwitchA-rip-1] peer 192.168.2.2
[SwitchA-rip-1] undo validate-source-address
[SwitchA-rip-1] import-route static
[SwitchA-rip-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] rip bfd enable
[SwitchA-Vlan-interface100] quit
[SwitchA] rip 2
[SwitchA-rip-2] version 2
60
[SwitchA-rip-2] undo summary
[SwitchA-rip-2] network 192.168.3.0
[SwitchA-rip-2] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] rip 1
[SwitchC-rip-1] version 2
[SwitchC-rip-1] undo summary
[SwitchC-rip-1] network 192.168.2.0
[SwitchC-rip-1] network 192.168.4.0
[SwitchC-rip-1] network 100.1.1.0
[SwitchC-rip-1] peer 192.168.1.1
[SwitchC-rip-1] undo validate-source-address
[SwitchC-rip-1] import-route static
[SwitchC-rip-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] rip bfd enable
[SwitchC-Vlan-interface200] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] rip 1
[SwitchD-rip-1] version 2
[SwitchD-rip-1] undo summary
[SwitchD-rip-1] network 192.168.3.0
[SwitchD-rip-1] network 192.168.4.0
3. Configure BFD parameters:
# Configure Switch A.
[SwitchA] bfd session init-mode active
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] bfd min-transmit-interval 500
[SwitchA-Vlan-interface100] bfd min-receive-interval 500
[SwitchA-Vlan-interface100] bfd detect-multiplier 7
[SwitchA-Vlan-interface100] quit
# Configure Switch C.
[SwitchC] bfd session init-mode active
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] bfd min-transmit-interval 500
[SwitchC-Vlan-interface200] bfd min-receive-interval 500
[SwitchC-Vlan-interface200] bfd detect-multiplier 7
[SwitchC-Vlan-interface200] quit
4. Configure static routes:
# Configure a static route to Switch C on Switch A.
[SwitchA] ip route-static 192.168.2.0 24 vlan-interface 100 192.168.1.2
[SwitchA] quit
# Configure a static route to Switch A on Switch C.
[SwitchC] ip route-static 192.168.1.0 24 vlan-interface 200 192.168.2.1
61
Verifying the configuration
# Display the BFD session information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 session working under Ctrl mode:
LD/RD SourceAddr DestAddr State Holdtime Interface
513/513 192.168.1.1 192.168.2.2 Up 1700ms vlan100
# Display RIP routes destined for 100.1.1.0/24 on Switch A.
<SwitchA> display ip routing-table 100.1.1.0 24
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
100.1.1.0/24 RIP 100 1 192.168.2.2 vlan-interface 100
The output shows that Switch A communicates with Switch C through VLAN-interface 100. Then the link over VLAN-interface 100 fails.
# Display RIP routes destined for 100.1.1.0/24 on Switch A.
<SwitchA> display ip routing-table 100.1.1.0 24
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
100.1.1.0/24 RIP 100 2 192.168.3.2 vlan-interface 300
The output shows that Switch A communicates with Switch C through VLAN-interface 300.
Configuring RIP FRR
Network requirements
As shown in Figure 16 , Switch A, Switch B, and Switch C run RIPv2. Configure RIP FRR so that
when Link A becomes unidirectional, services can be switched to Link B immediately.
Figure 16 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
101
Link B
Vlan
-int
100
Link A
Loop0
Switch A
Vlan-int200
Table 8 Interface and IP address assignment
Vlan
-int
101
Vlan-int200
Switch B
Loop0
Device
Switch A
Interface
VLAN-interface 100
IP address
12.12.12.1/24
62
Device
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Interface
VLAN-interface 200
Loopback 0
VLAN-interface 101
VLAN-interface 200
Loopback 0
VLAN-interface 100
IP address
13.13.13.1/24
1.1.1.1/32
24.24.24.4/24
13.13.13.2/24
4.4.4.4/32
12.12.12.2/24
Switch C VLAN-interface 101 24.24.24.2/24
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure RIPv2 on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3. (Details not shown.)
3. Configure RIP FRR:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ip prefix-list abc index 10 permit 4.4.4.4 32
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ip address prefix-list abc
[SwitchA-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
100 backup-nexthop 12.12.12.2
[SwitchA-route-policy-frr-10] quit
[SwitchA] rip 1
[SwitchA-rip-1] fast-reroute route-policy frr
[SwitchA-rip-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ip prefix-list abc index 10 permit 1.1.1.1 32
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ip address prefix-list abc
[SwitchB-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
101 backup-nexthop 24.24.24.2
[SwitchB-route-policy-frr-10] quit
[SwitchB] rip 1
[SwitchB-rip-1] fast-reroute route-policy frr
[SwitchB-rip-1] quit
Verifying the configuration
# Display route 4.4.4.4/32 on Switch A to view the backup next hop information.
[SwitchA] display ip routing-table 4.4.4.4 verbose
Summary Count : 1
Destination: 4.4.4.4/32
Protocol: RIP
Process ID: 1
63
SubProtID: 0x1 Age: 04h20m37s
Cost: 1 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 13.13.13.2
Flags: 0x1008c OrigNextHop: 13.13.13.2
Label: NULL RealNextHop: 13.13.13.2
BkLabel: NULL BkNextHop: 12.12.12.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display route 1.1.1.1/32 on Switch B to view the backup next hop information.
[SwitchB] display ip routing-table 1.1.1.1 verbose
Summary Count : 1
Destination: 1.1.1.1/32
Protocol: RIP
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 1 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 13.13.13.1
Flags: 0x1008c OrigNextHop: 13.13.13.1
Label: NULL RealNextHop: 13.13.13.1
BkLabel: NULL BkNextHop: 24.24.24.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
64
Configuring OSPF
Overview
Open Shortest Path First (OSPF) is a link-state IGP developed by the OSPF working group of the
IETF. OSPF version 2 is used for IPv4. OSPF refers to OSPFv2 throughout this chapter.
OSPF has the following features:
•
Wide scope —Supports multiple network sizes and several hundred routers in an OSPF routing domain.
•
Fast convergence —Advertises routing updates instantly upon network topology changes.
•
Loop free —Computes routes with the SPF algorithm to avoid routing loops.
•
Area-based network partition —Splits an AS into multiple areas to facilitate management.
This feature reduces the LSDB size on routers to save memory and CPU resources, and reduces route updates transmitted between areas to save bandwidth.
•
ECMP routing —Supports multiple equal-cost routes to a destination.
•
Routing hierarchy —Supports a 4-level routing hierarchy that prioritizes routes into intra-area, inter-area, external Type-1, and external Type-2 routes.
•
Authentication —Supports area- and interface-based packet authentication to ensure secure packet exchange.
•
Support for multicasting —Multicasts protocol packets on some types of links to avoid impacting other devices.
OSPF packets
OSPF messages are carried directly over IP. The protocol number is 89.
OSPF uses the following packet types:
•
Hello —Periodically sent to find and maintain neighbors, containing timer values, information about the DR, BDR, and known neighbors.
•
Database description (DD) —Describes the digest of each LSA in the LSDB, exchanged between two routers for data synchronization.
•
Link state request (LSR) —Requests needed LSAs from a neighbor. After exchanging the DD packets, the two routers know which LSAs of the neighbor are missing from their LSDBs. They then exchange LSR packets requesting the missing LSAs. LSR packets contain the digest of the missing LSAs.
•
Link state update (LSU) —Transmits the requested LSAs to the neighbor.
•
Link state acknowledgment (LSAck) —Acknowledges received LSU packets. It contains the headers of received LSAs (an LSAck packet can acknowledge multiple LSAs).
LSA types
OSPF advertises routing information in Link State Advertisements (LSAs). The following LSAs are commonly used:
•
Router LSA —Type-1 LSA, originated by all routers and flooded throughout a single area only.
This LSA describes the collected states of the router's interfaces to an area.
65
•
Network LSA —Type-2 LSA, originated for broadcast and NBMA networks by the designated router, and flooded throughout a single area only. This LSA contains the list of routers connected to the network.
•
Network Summary LSA —Type-3 LSA, originated by Area Border Routers (ABRs), and flooded throughout the LSA's associated area. Each summary-LSA describes a route to a destination outside the area, yet still inside the AS (an inter-area route).
•
ASBR Summary LSA —Type-4 LSA, originated by ABRs and flooded throughout the LSA's associated area. Type 4 summary-LSAs describe routes to Autonomous System Boundary
Router (ASBR).
•
AS External LSA —Type-5 LSA, originated by ASBRs, and flooded throughout the AS (except stub and NSSA areas). Each AS-external-LSA describes a route to another AS.
•
NSSA LSA —Type-7 LSA, as defined in RFC 1587, originated by ASBRs in NSSAs and flooded throughout a single NSSA. NSSA LSAs describe routes to other ASs.
•
Opaque LSA —A proposed type of LSA. Its format consists of a standard LSA header and application specific information. Opaque LSAs are used by the OSPF protocol or by some applications to distribute information into the OSPF routing domain. The opaque LSA includes
Type 9, Type 10, and Type 11. The Type 9 opaque LSA is flooded into the local subnet, the Type
10 is flooded into the local area, and the Type 11 is flooded throughout the AS.
OSPF areas
In large OSPF routing domains, SPF route computations consume too many storage and CPU resources, and enormous OSPF packets generated for route synchronization occupy excessive bandwidth.
To resolve these issues, OSPF splits an AS into multiple areas. Each area is identified by an area ID.
The boundaries between areas are routers rather than links. A network segment (or a link) can only
reside in one area as shown in Figure 17 .
You can configure route summarization on ABRs to reduce the number of LSAs advertised to other areas and minimize the effect of topology changes.
Figure 17 Area-based OSPF network partition
Area 4
Area 1
Area 0
Area 2
Area 3
66
Backbone area and virtual links
Each AS has a backbone area that distributes routing information between non-backbone areas.
Routing information between non-backbone areas must be forwarded by the backbone area. OSPF has the following requirements:
•
All non-backbone areas must maintain connectivity to the backbone area.
•
The backbone area must maintain connectivity within itself.
In practice, these requirements might not be met due to lack of physical links. OSPF virtual links can solve this issue.
A virtual link is established between two ABRs through a non-backbone area. It must be configured on both ABRs to take effect. The non-backbone area is called a transit area.
As shown in Figure 18 , Area 2 has no direct physical link to the backbone Area 0. You can configure
a virtual link between the two ABRs to connect Area 2 to the backbone area.
Figure 18 Virtual link application 1
Transit area
Virtual link
Area 0
ABR ABR
Area 2
Area 1
Virtual links can also be used as redundant links. If a physical link failure breaks the internal connectivity of the backbone area, you can configure a virtual link to replace the failed physical link,
Figure 19 Virtual link application 2
Area 1
Virtual link
R1 R2
Area 0
The virtual link between the two ABRs acts as a point-to-point connection. You can configure interface parameters, such as hello interval, on the virtual link as they are configured on a physical interface.
The two ABRs on the virtual link unicast OSPF packets to each other, and the OSPF routers in between convey these OSPF packets as normal IP packets.
Stub area and totally stub area
A stub area does not distribute Type-5 LSAs to reduce the routing table size and LSAs advertised within the area. The ABR of the stub area advertises a default route in a Type-3 LSA so that the routers in the area can reach external networks through the default route.
To further reduce the routing table size and advertised LSAs, you can configure the stub area as a totally stub area. The ABR of a totally stub area does not advertise inter-area routes or external
67
routes. It advertises a default route in a Type-3 LSA so that the routers in the area can reach external networks through the default route.
NSSA area and totally NSSA area
An NSSA area does not import AS external LSAs (Type-5 LSAs) but can import Type-7 LSAs generated by the NSSA ASBR. The NSSA ABR translates Type-7 LSAs into Type-5 LSAs and advertises the Type-5 LSAs to other areas.
As shown in Figure 20 , the OSPF AS contains Area 1, Area 2, and Area 0. The other two ASs run RIP.
Area 1 is an NSSA area where the ASBR redistributes RIP routes in Type-7 LSAs into Area 1. Upon receiving the Type-7 LSAs, the NSSA ABR translates them to Type-5 LSAs, and advertises the
Type-5 LSAs to Area 0.
The ASBR of Area 2 redistributes RIP routes in Type-5 LSAs into the OSPF routing domain.
However, Area 1 does not receive Type-5 LSAs because it is an NSSA area.
Figure 20 NSSA area
RIP
RIP
NSSA
ASBR
Type 5
Type 5
Area 2 ABR
Type 5
Type 5
Area 0 NSSA
ABR
Type 7
Area 1 NSSA
ASBR
Router types
OSPF routers are classified into the following types based on their positions in the AS:
•
Internal router —All interfaces on an internal router belong to one OSPF area.
•
ABR —Belongs to more than two areas, one of which must be the backbone area. ABR connects the backbone area to a non-backbone area. An ABR and the backbone area can be connected through a physical or logical link.
•
Backbone router —No less than one interface of a backbone router must reside in the backbone area. All ABRs and internal routers in Area 0 are backbone routers.
•
ASBR —Exchanges routing information with another AS is an ASBR. An ASBR might not reside on the border of the AS. It can be an internal router or an ABR.
68
Figure 21 OSPF router types
RIP
IS-IS
ASBR
Area 1
Area 4
Backbone router
Internal router
Area 0
ABR
Area 2
Area 3
Route types
OSPF prioritizes routes into the following route levels:
•
Intra-area route.
•
Inter-area route.
•
Type-1 external route.
•
Type-2 external route.
The intra-area and inter-area routes describe the network topology of the AS. The external routes describe routes to external ASs.
A Type-1 external route has high credibility. The cost of a Type-1 external route = the cost from the router to the corresponding ASBR + the cost from the ASBR to the destination of the external route.
A Type-2 external route has low credibility. OSPF considers that the cost from the ASBR to the destination of a Type-2 external route is much greater than the cost from the ASBR to an OSPF internal router. The cost of a Type-2 external route = the cost from the ASBR to the destination of the
Type-2 external route. If two Type-2 routes to the same destination have the same cost, OSPF takes the cost from the router to the ASBR into consideration to determine the best route.
Route calculation
OSPF computes routes in an area as follows:
•
Each router generates LSAs based on the network topology around itself, and sends them to other routers in update packets.
•
Each OSPF router collects LSAs from other routers to compose an LSDB. An LSA describes the network topology around a router, and the LSDB describes the entire network topology of the area.
69
•
Each router transforms the LSDB to a weighted directed graph that shows the topology of the area. All the routers within the area have the same graph.
•
Each router uses the SPF algorithm to compute a shortest path tree that shows the routes to the nodes in the area. The router itself is the root of the tree.
OSPF network types
OSPF classifies networks into the following types, depending on different link layer protocols:
•
Broadcast —By default, OSPF considers the network type as broadcast. On a broadcast network, hello, LSU, and LSAck packets are multicast to 224.0.0.5 that identifies all OSPF routers or to 224.0.0.6 that identifies the DR and BDR. DD packets and LSR packets are unicast.
•
NBMA —OSPF packets are unicast on an NBMA network.
•
P2MP —No link is P2MP type by default. P2MP must be a conversion from other network types such as NBMA. On a P2MP network, OSPF packets are multicast to 224.0.0.5.
•
P2P —On a P2P network, OSPF packets are multicast to 224.0.0.5.
The following are the differences between NBMA and P2MP networks:
•
NBMA networks are fully meshed. P2MP networks are not required to be fully meshed.
•
NBMA networks require DR and BDR election. P2MP networks do not have DR or BDR.
•
On an NBMA network, OSPF packets are unicast, and neighbors are manually configured. On a
P2MP network, OSPF packets are multicast by default, and you can configure OSPF to unicast protocol packets.
DR and BDR
DR and BDR mechanism
On a broadcast or NBMA network, any two routers must establish an adjacency to exchange routing information with each other. If n routers are present on the network, n(n-1)/2 adjacencies are established. Any topology change on the network results in an increase in traffic for route synchronization, which consumes a large amount of system and bandwidth resources.
Using the DR and BDR mechanisms can solve this problem.
•
DR —Elected to advertise routing information among other routers. If the DR fails, routers on the network must elect another DR and synchronize information with the new DR. Using this mechanism without BDR is time-consuming and is prone to route calculation errors.
•
BDR —Elected along with the DR to establish adjacencies with all other routers. If the DR fails, the BDR immediately becomes the new DR, and other routers elect a new BDR.
Routers other than the DR and BDR are called DR Others. They do not establish adjacencies with one another, so the number of adjacencies is reduced.
The role of a router is subnet (or interface) specific. It might be a DR on one interface and a BDR or
DR Other on another interface.
As shown in Figure 22 , solid lines are Ethernet physical links, and dashed lines represent OSPF
adjacencies. With the DR and BDR, only seven adjacencies are established.
70
Figure 22 DR and BDR in a network
DR BDR
DR other DR other DR other
Physical links Adjacencies
NOTE:
In OSPF, neighbor and adjacency are different concepts. After startup, OSPF sends a hello packet on each OSPF interface. A receiving router checks parameters in the packet. If the parameters match its own, the receiving router considers the sending router an OSPF neighbor. Two OSPF neighbors establish an adjacency relationship after they synchronize their LSDBs through exchange of DD packets and LSAs.
DR and BDR election
DR election is performed on broadcast or NBMA networks but not on P2P and P2MP networks.
Routers in a broadcast or NBMA network elect the DR and BDR by router priority and ID. Routers with a router priority value higher than 0 are candidates for DR and BDR election.
The election votes are hello packets. Each router sends the DR elected by itself in a hello packet to all the other routers. If two routers on the network declare themselves as the DR, the router with the higher router priority wins. If router priorities are the same, the router with the higher router ID wins.
If a router with a higher router priority becomes active after DR and BDR election, the router cannot replace the DR or BDR until a new election is performed. Therefore, the DR of a network might not be the router with the highest priority, and the BDR might not be the router with the second highest priority.
Protocols and standards
•
RFC 1765, OSPF Database Overflow
•
RFC 2328, OSPF Version 2
•
RFC 3101, OSPF Not-So-Stubby Area (NSSA) Option
•
RFC 3137, OSPF Stub Router Advertisement
•
RFC 4811, OSPF Out-of-Band LSDB Resynchronization
•
RFC 4812, OSPF Restart Signaling
•
RFC 4813, OSPF Link-Local Signaling
OSPF configuration task list
To run OSPF, you must first enable OSPF on the router. Make a proper configuration plan to avoid incorrect settings that can result in route blocking and routing loops.
To configure OSPF, perform the following tasks:
71
Tasks at a glance
(Optional.) Configuring OSPF areas :
•
•
•
(Optional.) Configuring OSPF network types :
•
Configuring the broadcast network type for an interface
•
Configuring the NBMA network type for an interface
•
Configuring the P2MP network type for an interface
•
Configuring the P2P network type for an interface
(Optional.) Configuring OSPF route control :
•
Configuring OSPF route summarization
Configuring route summarization on an ABR
Configuring route summarization on an ASBR
•
Configuring received OSPF route filtering
•
Configuring Type-3 LSA filtering
•
Setting an OSPF cost for an interface
•
Setting the maximum number of ECMP routes
•
•
Configuring discard routes for summary networks
•
Configuring OSPF route redistribution
Redistributing routes from another routing protocol
Redistributing a default route
Configuring default parameters for redistributed routes
•
•
Excluding interfaces in an OSPF area from the base topology
72
Tasks at a glance
(Optional.) Tuning and optimizing OSPF networks :
•
•
Setting LSA transmission delay
•
Setting SPF calculation interval
•
Setting the LSA arrival interval
•
Setting the LSA generation interval
•
Disabling interfaces from receiving and sending OSPF packets
•
•
Configuring OSPF authentication
•
Adding the interface MTU into DD packets
•
Setting a DSCP value for OSPF packets
•
Setting the maximum number of external LSAs in LSDB
•
Setting OSPF exit overflow interval
•
Enabling compatibility with RFC 1583
•
Logging neighbor state changes
•
Configuring OSPF network management
•
•
•
Configuring prefix suppression
•
Configuring prefix prioritization
•
•
Setting the number of OSPF logs
•
Filtering outbound LSAs on an interface
•
Filtering LSAs for the specified neighbor
•
(Optional.) Configuring OSPF GR
•
•
•
(Optional.) Configuring OSPF NSR
(Optional.) Configuring BFD for OSPF
(Optional.) Configuring OSPF FRR
(Optional.) Advertising OSPF link state information to BGP
Enabling OSPF
Enable OSPF before you perform other OSPF configuration tasks.
Configuration prerequisites
Configure the link layer protocol and IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
Configuration guidelines
To enable OSPF on an interface, you can enable OSPF on the network where the interface resides or directly enable OSPF on that interface. If you configure both, the latter takes precedence.
73
You can specify a global router ID, or specify a router ID when you create an OSPF process.
•
If you specify a router ID when you create an OSPF process, any two routers in an AS must have different router IDs. A common practice is to specify the IP address of an interface as the router ID.
•
If you specify no router ID when you create the OSPF process, the global router ID is used. As a best practice, specify a router ID when you create the OSPF process.
OSPF supports multiple processes and VPNs.
•
To run multiple OSPF processes, you must specify an ID for each process. The process IDs take effect locally and has no influence on packet exchange between routers. Two routers with different process IDs can exchange packets.
•
You can configure an OSPF process to run in a specified VPN instance. For more information about VPN, see MPLS Configuration Guide .
Enabling OSPF on a network
Step
1. Enter system view.
2. (Optional.) Configure a global router ID.
Command system-view
router id router-id
Remarks
N/A
By default, no global router ID is configured.
If no global router ID is configured, the highest loopback interface IP address, if any, is used as the router ID. If no loopback interface IP address is available, the highest physical interface IP address is used, regardless of the interface status (up or down).
3. Enable an OSPF process and enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
4. (Optional.) Configure a description for the OSPF process.
description text
5. Create an OSPF area and enter OSPF area view.
area area-id
6. (Optional.) Configure a description for the area.
description text
By default, OSPF is disabled.
By default, no description is configured for the OSPF process.
As a best practice, configure a description for each OSPF process.
By default, no OSPF areas exist.
By default, no description is configured for the area.
As a best practice, configure a description for each OSPF area.
7. Specify a network to enable the interface attached to the network to run the OSPF process in the area.
network ip-address wildcard-mask
Enabling OSPF on an interface
Step
1. Enter system view.
Command system-view
By default, no network is specified.
A network can be added to only one area.
Remarks
N/A
74
Step
2. Enter interface view.
Command interface interface-type
interface-number
Remarks
N/A
3. Enable an OSPF process on the interface.
ospf process-id area area-id [ exclude-subip ]
By default, OSPF is disabled on an interface.
If the specified OSPF process and area do not exist, the command creates the OSPF process and area. Disabling an OSPF process on an interface does not delete the
OSPF process or the area.
Configuring OSPF areas
Before you configure an OSPF area, perform the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable OSPF.
Configuring a stub area
You can configure a non-backbone area at an AS edge as a stub area. To do so, execute the stub command on all routers attached to the area. The routing table size is reduced because Type-5 LSAs will not be flooded within the stub area. The ABR generates a default route into the stub area so all packets destined outside of the AS are sent through the default route.
To further reduce the routing table size and routing information exchanged in the stub area, configure a totally stub area by using the stub no-summary command on the ABR. AS external routes and inter-area routes will not be distributed into the area. All the packets destined outside of the AS or area will be sent to the ABR for forwarding.
A stub or totally stub area cannot have an ASBR because external routes cannot be distributed into the area.
To configure an OSPF stub area:
Step
1. Enter system view.
Remarks
N/A
2. Enter OSPF view.
3. Enter area view.
4. Configure the area as a stub area.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * area area-id stub
[ default-route-advertise-alwa ys | no-summary ] *
N/A
N/A
By default, no stub area is configured.
5. (Optional.) Set a cost for the default route advertised to the stub area. default-cost cost-value
The default setting is 1.
The default-cost cost command takes effect only on the ABR of a stub area or totally stub area.
75
Configuring an NSSA area
A stub area cannot import external routes, but an NSSA area can import external routes into the
OSPF routing domain while retaining other stub area characteristics.
Do not configure the backbone area as an NSSA area or totally NSSA area.
To configure an NSSA area, configure the nssa command on all the routers attached to the area.
To configure a totally NSSA area, configure the nssa command on all the routers attached to the area and configure the nssa no-summary command on the ABR. The ABR of a totally NSSA area does not advertise inter-area routes into the area.
To configure an NSSA area:
Step
1. Enter system view.
2. Enter OSPF view.
3. Enter area view.
4. Configure the area as an
NSSA area.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * area area-id nssa [ default-route-advertise
[ cost cost-value | nssa-only |
route-policy route-policy-name |
type type ] * | no-import-route | no-summary | suppress-fa |
[ [ [ translate-always ]
[ translate-ignore-checking-bac kbone ] ] | translate-never ] | translator-stability-interval value ] *
Remarks
N/A
N/A
N/A
By default, no area is configured as an NSSA area.
5. (Optional.) Set a cost for the default route advertised to the NSSA area. default-cost cost-value
The default setting is 1.
This command takes effect only on the ABR/ASBR of an NSSA or totally NSSA area.
Configuring a virtual link
Virtual links are configured for connecting backbone area routers that have no direct physical links.
To configure a virtual link:
Step
1. Enter system view.
2. Enter OSPF view.
3. Enter area view.
4. Configure a virtual link.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A area area-id N/A vlink-peer router-id [ dead seconds | hello seconds |
{ { hmac-md5 | md5 } key-id
{ cipher | plain } string | keychain keychain-name | simple { cipher
| plain } string } | retransmit seconds | trans-delay seconds ] *
By default, no virtual links exist.
Configure this command on both ends of a virtual link. The hello and dead intervals must be identical on both ends of the virtual link.
76
Configuring OSPF network types
OSPF classifies networks into four types, including broadcast, NBMA, P2MP, and P2P. The default network type of an interface on the device is broadcast.
When you change the network type of an interface, follow these guidelines:
•
When an NBMA network becomes fully meshed, change the network type to broadcast to avoid manual configuration of neighbors.
•
If any routers in a broadcast network do not support multicasting, change the network type to
NBMA.
•
An NBMA network must be fully meshed. OSPF requires that an NBMA network be fully meshed. If a network is partially meshed, change the network type to P2MP.
•
If a router on an NBMA network has only one neighbor, you can change the network type to P2P to save costs.
Two broadcast-, NBMA-, and P2MP-interfaces can establish a neighbor relationship only when they are on the same network segment.
Configuration prerequisites
Before you configure OSPF network types, perform the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable OSPF.
Configuring the broadcast network type for an interface
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type interface-number
3. Configure the OSPF network type for the interface as broadcast. ospf network-type broadcast
Remarks
N/A
N/A
By default, the network type of an interface is broadcast.
Configuring the NBMA network type for an interface
After you configure the network type as NBMA, you must specify neighbors and their router priorities because NBMA interfaces cannot find neighbors by broadcasting hello packets.
To configure the NBMA network type for an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Configure the OSPF network type for the interface as NBMA. ospf network-type nbma
By default, the network type of an interface is broadcast.
77
Step
4. (Optional.) Set a router priority for the interface.
Command ospf dr-priority priority
Remarks
The default setting is 1.
The router priority configured with this command is for DR election.
N/A 5. Return to system view.
6. Enter OSPF view. quit ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
7. Specify a neighbor and set its router priority. peer ip-address [ dr-priority priority ]
By default, no neighbor is specified.
The priority configured with this command indicates whether a neighbor has the election right or not.
If you configure the router priority for a neighbor as 0, the local router determines the neighbor has no election right, and does not send hello packets to this neighbor. However, if the local router is the DR or BDR, it still sends hello packets to the neighbor for neighbor relationship establishment.
Configuring the P2MP network type for an interface
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
3. Configure the OSPF network type for the interface as P2MP. ospf network-type p2mp
[ unicast ]
4.
5.
Return to system view.
Enter OSPF view. quit ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
6. (Optional.) Specify a neighbor and set its router priority. peer ip-address [ cost cost-value ]
Remarks
N/A
N/A
By default, the network type of an interface is broadcast.
After you configure the OSPF network type for an interface as
P2MP unicast, all packets are unicast over the interface. The interface cannot broadcast hello packets to discover neighbors, so you must manually specify the neighbors.
N/A
N/A
By default, no neighbor is specified.
This step must be performed if the network type is P2MP unicast, and is optional if the network type is
P2MP.
78
Configuring the P2P network type for an interface
Step
1. Enter system view.
2. Enter interface view.
3. Configure the OSPF network type for the interface as P2P.
Command system-view interface interface-type interface-number ospf network-type p2p
[ peer-address-check ]
Remarks
N/A
N/A
By default, the network type of an interface is broadcast.
Configuring OSPF route control
This section describes how to control the advertisement and reception of OSPF routing information, as well as route redistribution from other protocols.
Configuration prerequisites
Before you configure OSPF route control, perform the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable OSPF.
•
Configure filters if routing information filtering is needed.
Configuring OSPF route summarization
Route summarization enables an ABR or ASBR to summarize contiguous networks into a single network and advertise the network to other areas.
Route summarization reduces the routing information exchanged between areas and the size of routing tables, and improves routing performance. For example, three internal networks 19.1.1.0/24,
19.1.2.0/24, and 19.1.3.0/24 are available within an area. You can summarize the three networks into network 19.1.0.0/16, and advertise the summary network to other areas.
Configuring route summarization on an ABR
After you configure a summary route on an ABR, the ABR generates a summary LSA instead of specific LSAs. The scale of LSDBs on routers in other areas and the influence of topology changes are reduced.
To configure route summarization on an ABR:
Step
1. Enter system view.
2. Enter OSPF view.
3. Enter OSPF area view.
4. Configure ABR route summarization.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * area area-id abr-summary ip-address
{ mask-length | mask } [ advertise | not-advertise ] [ cost cost-value ]
Remarks
N/A
N/A
N/A
By default, route summarization is not configured on an ABR.
79
Configuring route summarization on an ASBR
Perform this task to enable an ASBR to summarize external routes within the specified address range into a single route. The ASBR advertises only the summary route to reduce the number of
LSAs in the LSDB.
An ASBR can summarize routes in the following LSAs:
•
Type-5 LSAs.
•
Type-7 LSAs in an NSSA area.
•
Type-5 LSAs translated by the ASBR (also an ABR) from Type-7 LSAs in an NSSA area.
If the ASBR (ABR) is not a translator, it cannot summarize routes in Type-5 LSAs translated from Type-7 LSAs.
To configure route summarization on an ASBR:
Step
1. Enter system view.
2. Enter OSPF view.
3. Configure ASBR route summarization.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A asbr-summary ip-address
{ mask-length | mask } [ cost cost-value | not-advertise | nssa-only | tag tag ] *
By default, route summarization is not configured on an ASBR.
Configuring received OSPF route filtering
Perform this task to filter routes calculated using received LSAs.
The following filtering methods are available:
•
Use an ACL or IP prefix list to filter routing information by destination address.
•
Use the gateway keyword to filter routing information by next hop.
•
Use an ACL or IP prefix list to filter routing information by destination address. At the same time use the gateway keyword to filter routing information by next hop.
•
Use a routing policy to filter routing information.
To configure OSPF to filter routes calculated using received LSAs:
Step
1. Enter system view.
2. Enter OSPF view.
3. Configure OSPF to filter routes calculated using received LSAs.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A filter-policy { ipv4-acl-number [ gateway prefix-list-name ] | gateway prefix-list-name
| prefix-list prefix-list-name [ gateway prefix-list-name ] | route-policy route-policy-name } import
By default, OSPF accepts all routes calculated using received
LSAs.
Configuring Type-3 LSA filtering
Perform this task to filter Type-3 LSAs advertised to an area on an ABR.
80
To configure Type-3 LSA filtering:
Step
1. Enter system view.
2. Enter OSPF view.
3. Enter area view.
4. Configure Type-3 LSA filtering.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A area area-id N/A filter { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } { export | import }
By default, the ABR does not filter Type-3 LSAs.
Setting an OSPF cost for an interface
Set an OSPF cost for an interface by using either of the following methods:
•
Set the cost value in interface view.
•
Set a bandwidth reference value for the interface. OSPF computes the cost with this formula:
Interface OSPF cost = Bandwidth reference value (100 Mbps) / Expected interface bandwidth
(Mbps). The expected bandwidth of an interface is configured with the bandwidth command
(see Interface Command Reference ).
If the calculated cost is greater than 65535, the value of 65535 is used. If the calculated cost is less than 1, the value of 1 is used.
If no cost or bandwidth reference value is configured for an interface, OSPF computes the interface cost based on the interface bandwidth and default bandwidth reference value.
To set an OSPF cost for an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Set an OSPF cost for the interface. ospf cost cost value
By default, the OSPF cost is calculated according to the interface bandwidth.
For a loopback interface, the OSPF cost is 0 by default.
To set a bandwidth reference value:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Set a bandwidth reference value. bandwidth-reference value
Remarks
N/A
N/A
The default setting is 100 Mbps.
81
Setting the maximum number of ECMP routes
Perform this task to implement load sharing over ECMP routes.
To set the maximum number of ECMP routes:
Step
1. Enter system view.
2. Enter OSPF view.
3. Set the maximum number of
ECMP routes.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A maximum load-balancing number
By default, the maximum number of ECMP routes equals the maximum number of ECMP routes supported by the system.
Setting OSPF preference
A router can run multiple routing protocols, and each protocol is assigned a preference. If multiple routes are available to the same destination, the one with the highest protocol preference is selected as the best route.
To set OSPF preference:
Step
2. Enter OSPF view.
Command
1. Enter system view. system-view
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A
3. Set a preference for
OSPF. preference [ ase ] { preference | route-policy route-policy-name } *
By default, the preference of OSPF internal routes is 10 and the preference of OSPF external routes is 150.
Configuring discard routes for summary networks
Perform this task on an ABR or ASBR to specify whether to generate discard routes for summary networks. You can also specify a preference for the discard routes.
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Configure discard routes for summary networks. discard-route { external
{ preference | suppression } | internal { preference | suppression } } *
By default:
•
The ABR or ASBR generates discard routes for summary networks.
•
The preference of discard routes is 255.
82
Configuring OSPF route redistribution
On a router running OSPF and other routing protocols, you can configure OSPF to redistribute static routes, direct routes, or routes from other protocols, such as RIP, IS-IS, and BGP. OSPF advertises the routes in Type-5 LSAs or Type-7 LSAs. In addition, you can configure OSPF to filter redistributed routes so that OSPF advertises only permitted routes.
IMPORTANT:
The import-route bgp command redistributes only EBGP routes. Because the import-route bgp allow-ibgp command redistributes both EBGP and IBGP routes, and might cause routing loops, use it with caution.
Redistributing routes from another routing protocol
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Configure OSPF to redistribute routes from another routing protocol. import-route protocol [ as-number ]
[ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ]
*
By default, no route redistribution is configured.
This command redistributes only active routes. To view information about active routes, use the display ip routing-table protocol command.
4. (Optional.) Configure
OSPF to filter redistributed routes.
Redistributing a default route filter-policy { ipv4-acl-number | prefix-list prefix-list-name } export
[ protocol [ process-id ] ]
By default, OSPF accepts all redistributed routes.
The import-route command cannot redistribute a default external route. Perform this task to redistribute a default route.
To redistribute a default route:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
3. Redistribute a default route. default-route-advertise [ [ always | permit-calculate-other ] | cost cost-value | route-policy
route-policy-name | type type ] * default-route-advertise [ summary cost cost-value ]
Configuring default parameters for redistributed routes
By default, no default route is redistributed.
This command is applicable only to VPNs. The PE router advertises a default route in a
Type-3 LSA to a CE router.
Perform this task to configure default parameters for redistributed routes, including cost, tag, and type. Tags identify information about protocols. For example, when redistributing BGP routes, OSPF uses tags to identify AS IDs.
To configure the default parameters for redistributed routes:
83
Step
1. Enter system view.
2. Enter OSPF view.
3. Configure the default parameters for redistributed routes
(cost, upper limit, tag, and type).
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A default { cost cost-value | tag tag | type type } *
By default, the cost is 1, the tag is 1, and the type is Type-2.
Advertising a host route
Step
1. Enter system view.
2. Enter OSPF view.
3. Enter area view.
4. Advertise a host route.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * area area-id host-advertise ip-address cost
Remarks
N/A
N/A
N/A
By default, no host route is advertised.
Excluding interfaces in an OSPF area from the base topology
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] * area area-id 3. Enter area view.
4. Exclude interfaces from the base topology. capability default-exclusion
Remarks
N/A
N/A
N/A
By default, interfaces in an OSPF area belong to the base topology.
Tuning and optimizing OSPF networks
You can use one of the following methods to optimize an OSPF network:
•
Change OSPF packet timers to adjust the convergence speed and network load. On low-speed links, consider the delay time for sending LSAs.
•
Change the SPF calculation interval to reduce resource consumption caused by frequent network changes.
•
Configure OSPF authentication to improve security.
Configuration prerequisites
Before you configure OSPF network optimization, perform the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
84
•
Enable OSPF.
Setting OSPF timers
An OSPF interface includes the following timers:
•
Hello timer — Interval for sending hello packets. It must be identical on OSPF neighbors.
•
Poll timer — Interval for sending hello packets to a neighbor that is down on the NBMA network.
•
Dead timer — Interval within which if the interface does not receive any hello packet from the neighbor, it declares the neighbor is down.
•
LSA retransmission timer — Interval within which if the interface does not receive any acknowledgment packets after sending an LSA to the neighbor, it retransmits the LSA.
To set OSPF timers:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Set the hello interval.
4. Set the poll interval.
5. Set the dead interval.
6. Set the retransmission interval. ospf timer hello seconds ospf timer poll seconds ospf timer dead seconds ospf timer retransmit interval
By default:
•
The hello interval on P2P and broadcast interfaces is 10 seconds.
•
The hello interval on P2MP and
NBMA interfaces is 30 seconds.
The default hello interval is restored when the network type for an interface is changed.
The default setting is 120 seconds.
The poll interval is a minimum of four times the hello interval.
By default:
•
The dead interval on P2P and broadcast interfaces is 40 seconds.
•
The dead interval on P2MP and
NBMA interfaces is 120 seconds.
The dead interval must be a minimum of four times the hello interval on an interface.
The default dead interval is restored when the network type for an interface is changed.
The default setting is 5 seconds.
A retransmission interval setting that is too small can cause unnecessary LSA retransmissions. This interval is typically set bigger than the round-trip time of a packet between two neighbors.
85
Setting LSA transmission delay
To avoid LSAs from aging out during transmission, set an LSA retransmission delay especially for low speed links.
To set the LSA transmission delay on an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Set the LSA transmission delay. ospf trans-delay seconds The default setting is 1 second.
Setting SPF calculation interval
LSDB changes result in SPF calculations. When the topology changes frequently, a large amount of network and router resources are occupied by SPF calculation. You can adjust the SPF calculation interval to reduce the impact.
For a stable network, the minimum interval is used. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval × 2 n-2
for each calculation until the maximum interval is reached. The value n is the number of calculation times.
To set the SPF calculation interval:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Set the SPF calculation interval. spf-schedule-interval maximum-interval
[ minimum-interval
[ incremental-interval ] ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is 50 milliseconds.
•
The incremental interval is 200 milliseconds.
Setting the LSA arrival interval
If OSPF receives an LSA that has the same LSA type, LS ID, and router ID as the previously received
LSA within the LSA arrival interval, OSPF discards the LSA to save bandwidth and route resources.
To set the LSA arrival interval:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
86
Step Command
3. Set the LSA arrival interval. lsa-arrival-interval interval
Remarks
The default setting is 1000 milliseconds.
Make sure this interval is smaller than or equal to the interval set with the lsa-generation-interva l command.
Setting the LSA generation interval
Adjust the LSA generation interval to protect network resources and routers from being overwhelmed by LSAs at the time of frequent network changes.
For a stable network, the minimum interval is used. If network changes become frequent, the LSA generation interval is incremented by the incremental interval × 2 n-2
for each generation until the maximum interval is reached. The value n is the number of generation times.
To set the LSA generation interval:
Step
1. Enter system view.
2. Enter OSPF view.
3. Set the LSA generation interval.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A lsa-generation-interval maximum-interval [ minimum-interval
[ incremental-interval ] ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is 50 milliseconds.
•
The incremental interval is 200 milliseconds.
Disabling interfaces from receiving and sending OSPF packets
To enhance OSPF adaptability and reduce resource consumption, you can set an OSPF interface to
"silent." A silent OSPF interface blocks OSPF packets and cannot establish any OSPF neighbor relationship. However, other interfaces on the router can still advertise direct routes of the interface in
Router LSAs.
To disable interfaces from receiving and sending routing information:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
87
Step
3. Disable interfaces from receiving and sending
OSPF packets.
Command silent-interface { interface-type
interface-number | all }
Remarks
By default, an OSPF interface can receive and send OSPF packets.
The silent-interface command disables only the interfaces associated with the current process rather than other processes. Multiple OSPF processes can disable the same interface from receiving and sending OSPF packets.
Configuring stub routers
A stub router is used for traffic control. It reports its status as a stub router to neighboring OSPF routers. The neighboring routers can have a route to the stub router, but they do not use the stub router to forward data.
Router LSAs from the stub router might contain different link type values. A value of 3 means a link to a stub network, and the cost of the link will not be changed by default. To set the cost of the link to
65535, specify the include-stub keyword in the stub-router command. A value of 1, 2 or 4 means a point-to-point link, a link to a transit network, or a virtual link. On such links, a maximum cost value of
65535 is used. Neighbors do not send packets to the stub router as long as they have a route with a smaller cost.
To configure a router as a stub router:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
3. Configure the router as a stub router. stub-router [ external-lsa
[ max-metric-value ] | include-stub | on-startup { seconds | wait-for-bgp
[ seconds ] } | summary-lsa
[ max-metric-value ] ] *
By default, the router is not configured as a stub router.
A stub router is not related to a stub area.
Configuring OSPF authentication
Perform this task to configure OSPF area and interface authentication.
OSPF adds the configured key into sent packets, and uses the key to authenticate received packets.
Only packets that pass the authentication can be received. If a packet fails the authentication, the
OSPF neighbor relationship cannot be established.
If you configure OSPF authentication for both an area and an interface in that area, the interface uses the OSPF authentication configured on it.
Configuring OSPF area authentication
You must configure the same authentication mode and key on all the routers in an area.
To configure OSPF area authentication:
Step
1. Enter system view.
Command system-view
Remarks
N/A
88
Step
2. Enter OSPF view.
Command ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
3. Enter area view.
4. Configure area authentication mode. area area-id
•
Configure MD5 authentication: authentication-mode { hmac-md5 | md5 } key-id { cipher | plain } string
•
Configure simple authentication:
authentication-mode simple
{ cipher | plain } string
•
Configure keychain authentication: authentication-mode keychain keychain-name
Configuring OSPF interface authentication
N/A
By default, no authentication is configured.
For information about keychains, see Security
Configuration Guide .
You must configure the same authentication mode and key on both the local interface and its peer interface.
To configure OSPF interface authentication:
Step
1. Enter system view.
2. Enter interface view.
3. Configure interface authentication mode.
Command system-view
Remarks
N/A interface interface-type interface-number N/A
•
Configure simple authentication: ospf authentication-mode simple
{ cipher | plain } string
•
Configure MD5 authentication: ospf authentication-mode
{ hmac-md5 | md5 } key-id { cipher | plain } string
•
Configure keychain authentication: ospf authentication-mode keychain keychain-name
By default, no authentication is configured.
For information about keychain, see Security
Configuration Guide .
Adding the interface MTU into DD packets
By default, an OSPF interface adds a value of 0 into the interface MTU field of a DD packet rather than the actual interface MTU. You can enable an interface to add its MTU into DD packets.
To add the interface MTU into DD packets:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable the interface to add its MTU into DD packets. ospf mtu-enable
By default, the interface adds an
MTU value of 0 into DD packets.
89
Setting a DSCP value for OSPF packets
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Set a DSCP value for OSPF packets. dscp dscp-value
Remarks
N/A
N/A
By default, the DSCP value for OSPF packets is 48.
Setting the maximum number of external LSAs in LSDB
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Set the maximum number of external LSAs in the LSDB. lsdb-overflow-limit number
Remarks
N/A
N/A
By default, the maximum number of external LSAs in the
LSDB is not limited.
Setting OSPF exit overflow interval
When the number of LSAs in the LSDB exceeds the upper limit, the LSDB is in an overflow state. To save resources, OSPF does not receive any external LSAs and deletes the external LSAs generated by itself when in this state.
Perform this task to configure the interval that OSPF exits overflow state.
To set the OSPF exit overflow interval:
Step
1. Enter system view.
2. Enter OSPF view.
3. Set the OSPF exit overflow interval.
Command system-view
Remarks
N/A ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
lsdb-overflow-interval interval
The default setting is 300 seconds.
The value of 0 indicates that
OSPF does not exit overflow state.
Enabling compatibility with RFC 1583
RFC 1583 specifies a different method than RFC 2328 for selecting the optimal route to a destination in another AS. When multiple routes are available to the ASBR, OSPF selects the optimal route by using the following procedure:
1. Selects the route with the highest preference.
If RFC 2328 is compatible with RFC 1583, all these routes have equal preference.
90
If RFC 2328 is not compatible with RFC 1583, the intra-area route in a non-backbone area is preferred to reduce the burden of the backbone area. The inter-area route and intra-area route in the backbone area have equal preference.
2. Selects the route with the lower cost if two routes have equal preference.
3. Selects the route with the larger originating area ID if two routes have equal cost.
To avoid routing loops, set identical RFC 1583-compatibility on all routers in a routing domain.
To enable compatibility with RFC 1583:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable compatibility with RFC 1583. rfc1583 compatible
By default, compatibility with RFC
1583 is enabled.
Logging neighbor state changes
Perform this task to enable output of neighbor state change logs to the information center. The information center processes the logs according to user-defined output rules (whether and where to output logs). For more information about the information center, see Network Management and
Monitoring Configuration Guide .
To enable the logging of neighbor state changes:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable the logging of neighbor state changes. log-peer-change
By default, this feature is enabled.
Configuring OSPF network management
This task involves the following configurations:
•
Bind an OSPF process to MIB so that you can use network management software to manage the specified OSPF process.
•
Enable SNMP notifications for OSPF to report important events.
•
Configure the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval.
SNMP notifications are sent to the SNMP module, which outputs SNMP notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide .
To configure OSPF network management:
Step
1. Enter system view.
Command system-view
Remarks
N/A
91
Step
2. Bind OSPF MIB to an
OSPF process.
3. Enable SNMP notifications for OSPF.
4. Enter OSPF view.
Command
ospf mib-binding process-id
Remarks
By default, OSPF MIB is bound to the process with the smallest process ID. snmp-agent trap enable ospf
[ authentication-failure | bad-packet | config-error | grhelper-status-change
| grrestarter-status-change | if-state-change | lsa-maxage | lsa-originate | lsdb-approaching-overflow | lsdb-overflow | neighbor-state-change | nssatranslator-status-change | retransmit | virt-authentication-failure
| virt-bad-packet | virt-config-error | virt-retransmit | virtgrhelper-status-change | virtif-state-change | virtneighbor-state-change ] *
By default, SNMP notifications for OSPF are enabled. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
5. Configure the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval. snmp trap rate-limit interval
trap-interval count trap-number
By default, OSPF outputs a maximum of seven SNMP notifications within 10 seconds.
Setting the LSU transmit rate
During LSDB synchronization, if the local router has multiple neighbors, it must send many LSUs to each neighbor. When a neighbor receives excessive LSUs within a short time period, the following events might occur:
•
The performance of the neighbor is degraded because too much system resources are used to process the received LSU packets.
•
The neighbor drops hello packets used for maintaining the neighbor relationship because it is busy dealing with the LSUs. As a result, the neighbor relationship is torn down. To reestablish a relationship to the neighbor, the local router must send more LSUs to the neighbor. This exacerbates the performance degradation.
This task allows you to limit the global LSU transmit rate by setting the LSU transmit interval and the maximum number of LSUs that can be sent at each interval.
To set the LSU transmit rate:
Step Command
1. Enter system view. system-view
2. Enable OSPF to limit the LSU transmit rate. ospf lsu-flood-control [ interval count ]
Remarks
N/A
By default, OSPF does not limit the LSU transmit rate.
Inappropriate use of this command might cause abnormal routing. As a best practice, execute this command with the default values.
92
Step
3. Enter OSPF view.
Command ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
4. (Optional.) Set the
LSU transmit interval and the maximum number of LSUs that can be sent at each interval. transmit-pacing interval interval count count
Remarks
N/A
By default, an OSPF interface sends a maximum of three
LSU packets every 20 milliseconds.
Enabling OSPF ISPF
When the topology changes, Incremental Shortest Path First (ISPF) computes only the affected part of the SPT, instead of the entire SPT.
To enable OSPF ISPF:
Step Command
1. Enter system view. system-view
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable OSPF ISPF. ispf enable
By default, OSPF ISPF is enabled.
Configuring prefix suppression
By default, an OSPF interface advertises all of its prefixes in LSAs. To speed up OSPF convergence, you can suppress interfaces from advertising all of their prefixes. This feature helps improve network security by preventing IP routing to the suppressed networks.
When prefix suppression is enabled:
•
On P2P and P2MP networks, OSPF does not advertise Type-3 links in Type-1 LSAs. Other routing information can still be advertised to ensure traffic forwarding.
•
On broadcast and NBMA networks, the DR generates Type-2 LSAs with a mask length of 32 to suppress network routes. Other routing information can still be advertised to ensure traffic forwarding. If no neighbors exist, the DR does not advertise the primary IP addresses of interfaces in Type-1 LSAs.
IMPORTANT:
As a best practice, configure prefix suppression on all OSPF routers if you want to use prefix suppression.
Configuring prefix suppression for an OSPF process
Enabling prefix suppression for an OSPF process does not suppress the prefixes of secondary IP addresses, loopback interfaces, and passive interfaces. To suppress the prefixes of loopback interfaces and passive interfaces, enable prefix suppression on the interfaces.
To configure prefix suppression for an OSPF process:
93
Step Command
1. Enter system view. system-view
Remarks
N/A
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enable prefix suppression for the
OSPF process. prefix-suppression
Configuring prefix suppression for an interface
N/A
By default, prefix suppression is disabled for an OSPF process.
Interface prefix suppression does not suppress prefixes of secondary IP addresses.
To configure interface prefix suppression:
Step Command
1. Enter system view. system-view
2. Enter interface view.
3. Enable prefix suppression for the interface. interface interface-type interface-number ospf prefix-suppression [ disable ]
Remarks
N/A
N/A
By default, prefix suppression is disabled on an interface.
Configuring prefix prioritization
This feature enables the device to install prefixes in descending priority order: critical, high, medium, and low. The prefix priorities are assigned through routing policies. When a route is assigned multiple prefix priorities, the route uses the highest priority.
By default, the 32-bit OSPF host routes have a medium priority and other routes a low priority.
To configure prefix prioritization:
Step Command
1. Enter system view. system-view
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enable prefix prioritization.
Remarks
N/A
N/A
prefix-priority route-policy route-policy-name
By default, prefix prioritization is disabled.
Configuring OSPF PIC
Prefix Independent Convergence (PIC) enables the device to speed up network convergence by ignoring the number of prefixes.
When both OSPF PIC and OSPF FRR are configured, OSPF FRR takes effect.
OSPF PIC applies only to inter-area routes and external routes.
Enabling OSPF PIC
Step Command
1. Enter system view. system-view
Remarks
N/A
94
Step
2. Enter OSPF view.
Command ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
3. Enable PIC for
OSPF.
Configuring BFD for OSPF PIC pic [ additional-path-always ]
By default, OSPF PIC is enabled.
By default, OSPF PIC does not use BFD to detect primary link failures. To speed up OSPF convergence, enable BFD for OSPF PIC to detect the primary link failures.
To configure BFD control packet mode for OSPF PIC:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type
interface-number
3. Enable BFD control packet mode for OSPF PIC. ospf primary-path-detect bfd ctrl
To configure BFD echo packet mode for OSPF PIC:
Step
1. Enter system view.
Command system-view
N/A
By default, BFD control packet mode for OSPF PIC is disabled.
2. Configure the source IP address of BFD echo packets. bfd echo-source-ip ip-address
Remarks
N/A
By default, the source IP address of BFD echo packets is not 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 High Availability
Command Reference .
3. Enter interface view.
4. Enable BFD echo packet mode for OSPF PIC. interface interface-type
interface-number ospf primary-path-detect bfd echo
N/A
By default, BFD echo packet mode for OSPF PIC is disabled.
Setting the number of OSPF logs
OSPF logs include LSA aging logs, route calculation logs, and neighbor logs.
To set the number of OSPF logs:
Step Command
1. Enter system view. system-view
2. Enter OSPF view.
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A
95
Step Command
3. Set the number of
OSPF logs. event-log { lsa-flush | peer | spf } size count
Remarks
By default, the number of OSPF logs is
10 for each type, including LSA aging logs, route calculation logs, and neighbor logs.
Filtering outbound LSAs on an interface
To reduce the LSDB size for the neighbor and save bandwidth, you can perform this task on an interface to filter LSAs to be sent to the neighbor.
To filter outbound LSAs on an interface:
Step Command
1. Enter system view. system-view
2. Enter interface view. interface interface-type
interface-number
3. Filter outbound
LSAs on the interface.
Remarks
N/A
N/A ospf database-filter { all | { ase [ acl ipv4-acl-number ] | nssa [ acl ipv4-acl-number ] | summary [ acl ipv4-acl-number ] } * }
By default, the outbound LSAs are not filtered on the interface.
Filtering LSAs for the specified neighbor
On an P2MP network, a router might have multiple OSPF neighbors with the P2MP type. Perform this task to prevent the router from sending LSAs to the specified neighbor.
To filter LSAs for the specified neighbor:
Step
2. Enter OSPF view.
Command
1. Enter system view. system-view
Remarks
N/A ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A
3. Filter LSAs for the specified neighbor.
database-filter peer ip-address { all
| { ase [ acl ipv4-acl-number ] | nssa
[ acl ipv4-acl-number ] | summary
[ acl ipv4-acl-number ] } * }
By default, the LSAs for the specified neighbor are not filtered.
Configuring GTSM for OSPF
The Generalized TTL Security Mechanism (GTSM) protects the device by comparing the TTL value in the IP header of incoming OSPF packets against a valid TTL range. If the TTL value is within the valid TTL range, the packet is accepted. If not, the packet is discarded.
The valid TTL range is from 255 – the configured hop count + 1 to 255.
When GTSM is configured, the OSPF packets sent by the device have a TTL of 255.
GTSM checks OSPF packets from common neighbors and virtual link neighbors. It does not check
OSPF packets from sham link neighbors. For information about GTSM for OSPF sham links, see
MPLS Configuration Guide .
96
You can configure GTSM in OSPF area view or interface view.
•
The configuration in OSPF area view applies to all OSPF interfaces in the area.
•
The configuration in interface view takes precedence over OSPF area view.
IMPORTANT:
To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.
To configure GTSM in OSPF area view:
Step
1. Enter system view.
Command system-view
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enter OSPF area view. area area-id
4. Enable GTSM for the OSPF area. ttl-security [ hops hop-count ]
To configure GTSM in interface view:
Step
1. Enter system view.
2. Enter interface view.
3. Enable GTSM for the interface.
Remarks
N/A
N/A
N/A
By default, GTSM is disabled for the OSPF area.
Command system-view
Remarks
N/A interface interface-type
interface-number
N/A ospf ttl-security [ hops hop-count
| disable ]
By default, GTSM is disabled for the interface.
Configuring OSPF GR
GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Two routers are required to complete a GR process. The following are router roles in a GR process:
•
GR restarter —Graceful restarting router. It must have GR capability.
•
GR helper —A neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
OSPF GR has the following types:
•
IETF GR —Uses Opaque LSAs to implement GR.
•
Non-IETF GR —Uses link local signaling (LLS) to advertise GR capability and uses out of band synchronization to synchronize the LSDB.
A device can act as a GR restarter and GR helper at the same time.
Configuring OSPF GR restarter
You can configure the IETF or non-IETF OSPF GR restarter.
97
IMPORTANT:
You cannot enable OSPF NSR on a device that acts as GR restarter.
Configuring the IETF OSPF GR restarter
Step
1. Enter system view.
2. Enable OSPF and enter its view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enable opaque LSA reception and advertisement capability. opaque-capability enable
4. Enable the IETF GR. graceful-restart ietf [ global | planned-only ] *
5. (Optional.) Set the GR interval. graceful-restart interval interval
Configuring the non-IETF OSPF GR restarter
Remarks
N/A
N/A
By default, opaque LSA reception and advertisement capability is enabled.
By default, the IETF GR capability is disabled.
By default, the GR interval is 120 seconds.
Step
1. Enter system view.
2. Enable OSPF and enter its view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3.
4. Enable the out-of-band re-synchronization capability.
5.
6.
Enable the link-local signaling capability.
Enable non-IETF GR.
(Optional.) Set the GR interval. enable link-local-signaling enable out-of-band-resynchronization graceful-restart [ nonstandard ]
[ global | planned-only ] * graceful-restart interval interval
By default, the link-local signaling capability is disabled.
By default, the out-of-band re-synchronization capability is disabled.
By default, non-IETF GR capability is disabled.
By default, the GR interval is 120 seconds.
Configuring OSPF GR helper
You can configure the IETF or non-IETF OSPF GR helper.
Configuring the IETF OSPF GR helper
Step
1. Enter system view.
2. Enable OSPF and enter its view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enable opaque LSA reception and advertisement capability. opaque capability enable
Remarks
N/A
N/A
By default, opaque LSA reception and advertisement capability is enabled.
98
Step
4. (Optional.) Enable GR helper capability.
Command graceful-restart helper enable
[ planned-only ]
5. (Optional.) Enable strict LSA checking for the GR helper. graceful-restart helper strict-lsa-checking
Configuring the non-IETF OSPF GR helper
Remarks
By default, GR helper capability is enabled.
By default, strict LSA checking for the GR helper is disabled.
Step
1. Enter system view.
2. Enable OSPF and enter its view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable the link-local signaling capability. enable link-local-signaling
4. Enable the out-of-band re-synchronization capability. enable out-of-band-resynchronization
By default, the link-local signaling capability is disabled.
By default, the out-of-band re-synchronization capability is disabled.
5. (Optional.) Enable GR helper.
6. (Optional.) Enable strict LSA checking for the GR helper. graceful-restart helper enable graceful-restart helper strict-lsa-checking
By default, GR helper is enabled.
By default, strict LSA checking for the GR helper is disabled.
Triggering OSPF GR
OSPF GR is triggered by an active/standby switchover or when the following command is executed.
To trigger OSPF GR, perform the following command in user view:
Task
Trigger OSPF GR.
Command reset ospf [ process id ] process graceful-restart
Configuring OSPF NSR
Nonstop routing (NSR) backs up OSPF link state information from the active process to the standby process. After an active/standby switchover, NSR can complete link state recovery and route regeneration without tearing down adjacencies or impacting forwarding services.
NSR does not require the cooperation of neighboring devices to recover routing information, and it is typically used more often than GR.
IMPORTANT:
A device that has OSPF NSR enabled cannot act as GR restarter.
To enable OSPF NSR:
Step Command
1. Enter system view. system-view
Remarks
N/A
99
Step
2. Enter OSPF view.
Command Remarks ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ]
*
N/A
3. Enable OSPF NSR. non-stop-routing
By default, OSPF NSR is disabled.
This command takes effect only for the current process. As a best practice, enable OSPF NSR for each process if multiple OSPF processes exist.
Configuring BFD for OSPF
BFD provides a single mechanism to quickly detect and monitor the connectivity of links between
OSPF neighbors, which improves the network convergence speed. For more information about BFD, see High Availability Configuration Guide .
OSPF supports the following BFD detection modes:
•
Bidirectional control detection —Requires BFD configuration to be made on both OSPF routers on the link.
•
Single-hop echo detection —Requires BFD configuration to be made on one OSPF router on the link.
Configuring bidirectional control detection
Step
1. Enter system view.
2. Enter interface view.
3. Enable BFD bidirectional control detection.
Command system-view interface interface-type interface-number ospf bfd enable
Remarks
N/A
N/A
By default, BFD bidirectional control detection is disabled.
Both ends of a BFD session must be on the same network segment and in the same area.
Configuring single-hop echo detection
Step
1. Enter system view.
2. Configure the source address of echo packets.
Command system-view bfd echo-source-ip ip-address
3. Enter interface view. interface interface-type interface-number
4. Enable BFD single-hop echo detection. ospf bfd enable echo
Remarks
N/A
By default, the source address of echo packets is not configured.
N/A
By default, BFD single-hop echo detection is disabled.
100
Configuring OSPF FRR
A link or router failure on a path can cause packet loss and even routing loop until OSPF completes routing convergence based on the new network topology. FRR enables fast rerouting to minimize the impact of link or node failures.
Figure 23 Network diagram for OSPF FRR
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
As shown in Figure 23 , configure FRR on Router B by using a routing policy to specify a backup next
hop. When the primary link fails, OSPF directs packets to the backup next hop. At the same time,
OSPF calculates the shortest path based on the new network topology. It forwards packets over the path after network convergence.
You can configure OSPF FRR to calculate a backup next hop by using the loop free alternate (LFA) algorithm, or specify a backup next hop by using a routing policy.
Configuration prerequisites
Before you configure OSPF FRR, perform the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable OSPF.
Configuration guidelines
•
Do not use the fast-reroute lfa command together with the vlink-peer command.
•
When both OSPF PIC and OSPF FRR are configured, OSPF FRR takes effect.
Configuration procedure
Configuring OSPF FRR to calculate a backup next hop using the LFA algorithm
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type
interface-number
Remarks
N/A
N/A
3. (Optional.) Enable LFA on an interface. ospf fast-reroute lfa-backup
By default, the interface is enabled with LFA and it can be selected as a backup interface.
4. Return to system view. N/A
5. Enter OSPF view. quit ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
N/A
101
Step
6. Enable OSPF FRR to calculate a backup next hop by using the LFA algorithm.
Command fast-reroute lfa [ abr-only ]
Remarks
By default, OSPF FRR is disabled.
If abr-only is specified, the route to the ABR is selected as the backup path.
Configuring OSPF FRR to specify a backup next hop using a routing policy
Before you perform this task, use the apply fast-reroute backup-interface command to specify a backup next hop in the routing policy to be used. For more information about the apply fast-reroute backup-interface
command and routing policy configuration, see " Configuring routing policies ."
To configure OSPF FRR to specify a backup next hop using a routing policy:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPF view. ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
3. Enable OSPF FRR to specify a backup next hop by using a routing policy. fast-reroute route-policy route-policy-name
Configuring BFD for OSPF FRR
N/A
By default, OSPF FRR is disabled.
By default, OSPF FRR does not use BFD to detect primary link failures. To speed up OSPF convergence, enable BFD for OSPF FRR to detect primary link failures.
To configure BFD control packet mode for OSPF FRR:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type
interface-number
Remarks
N/A
N/A
3. Enable BFD control packet mode for OSPF FRR. ospf primary-path-detect bfd ctrl
To configure BFD echo packet mode for OSPF FRR:
By default, BFD control packet mode for OSPF FRR is disabled.
Step
1. Enter system view.
2. Configure the source
IP address of BFD echo packets.
Command system-view bfd echo-source-ip ip-address
Remarks
N/A
By default, the source IP address of
BFD echo packets is not 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 High Availability
Command Reference .
3. Enter interface view. interface interface-type
interface-number
N/A
102
Step
4. Enable BFD echo packet mode for
OSPF FRR.
Command Remarks ospf primary-path-detect bfd echo
By default, BFD echo packet mode for
OSPF FRR is disabled.
Advertising OSPF link state information to BGP
After the device advertises OSPF link state information to BGP, BGP can advertise the information
for intended applications. For more information about BGP LS, see " Configuring BGP ."
To advertise OSPF link state information to BGP:
Step
1. Enter system view.
2. Enter OSPF view.
Command system-view ospf [ process-id | router-id router-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Advertise OSPF link state information to BGP. distribute bgp-ls
By default, the device does not advertise OSPF link state information to
BGP.
Displaying and maintaining OSPF
Execute display commands in any view and reset commands in user view.
Task Command
Display OSPF process information. display ospf [ process-id ] [ verbose ]
Display OSPF GR information. display ospf [ process-id ] graceful-restart [ verbose ]
Display OSPF FRR backup next hop information. display ospf [ process-id ] [ area area-id ] fast-reroute lfa-candidate [ topology topo-name ]
Display OSPF LSDB information. display ospf [ process-id ] lsdb [ brief | originate-router advertising-router-id | self-originate ] display ospf [ process-id ] lsdb { opaque-as | ase } [ link-state-id ]
[ originate-router advertising-router-id | self-originate ] display ospf [ process-id ] [ area area-id ] lsdb { asbr | network | nssa | opaque-area | opaque-link | router | summary }
[ link-state-id ] [ originate-router advertising-router-id | self-originate ]
Display OSPF next hop information. display ospf [ process-id ] nexthop
Display OSPF NSR information. display ospf [ process-id ] non-stop-routing status
Display OSPF neighbor information. display ospf [ process-id ] peer [ verbose ] [ interface-type interface-number ] [ neighbor-id ]
Display neighbor statistics for OSPF areas. display ospf [ process-id ] peer statistics
Display OSPF routing table information.
Display SPF tree information. display ospf [ process-id ] routing [ ip-address { mask-length | mask } ] [ interface interface-type interface-number ] [ nexthop nexthop-address ] [ verbose ] display ospf [ process-id ] [ area area-id ] spf-tree [ verbose ]
103
Task
Display OSPF statistics.
Command display ospf [ process-id ] statistics [ error | packet [ interface-type interface-number ] ]
Display OSPF virtual link information.
Display OSPF request queue information. display ospf [ process-id ] vlink display ospf [ process-id ] request-queue [ interface-type interface-number ] [ neighbor-id ]
Display OSPF retransmission queue information. display ospf [ process-id ] retrans-queue [ interface-type interface-number ] [ neighbor-id ]
Display OSPF ABR and ASBR information.
Display summary route information on the OSPF ABR.
Display OSPF interface information. display ospf [ process-id ] abr-asbr [ verbose ] display ospf [ process-id ] [ area area-id ] abr-summary
[ ip-address { mask-length | mask } ] [ verbose ] display ospf [ process-id ] interface [ interface-type interface-number | verbose ]
Display OSPF log information.
Display OSPF ASBR route summarization information.
Display the global route ID.
Clear OSPF statistics. display ospf [ process-id ] event-log { lsa-flush | peer | spf } display ospf [ process-id ] asbr-summary [ ip-address
{ mask-length | mask } ] display router id
Clear OSPF log information.
Restart an OSPF process.
Re-enable OSPF route redistribution. reset ospf [ process-id ] statistics reset ospf [ process-id ] event-log [ lsa-flush | peer | spf ] reset ospf [ process-id ] process [ graceful-restart ] reset ospf [ process-id ] redistribution
OSPF configuration examples
Basic OSPF configuration example
Network requirements
•
Enable OSPF on all switches, and split the AS into three areas.
•
Configure Switch A and Switch B as ABRs.
104
Figure 24 Network diagram
Switch A
Vlan-int100
Area 0
10.1.1.1/24
Vlan-int200
10.2.1.1/24
Vlan-int100
10.1.1.2/24
Switch B
Vlan-int200
10.3.1.1/24
Area 2
Vlan-int200
10.3.1.2/24
Area 1
Vlan-int200
10.2.1.2/24
Switch C
Vlan-int300
10.4.1.1/24
Vlan-int300
10.5.1.1/24 Switch D
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] router id 10.2.1.1
[SwitchA] ospf
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] area 1
[SwitchA-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.1] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] router id 10.3.1.1
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] area 2
[SwitchB-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.2] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] router id 10.4.1.1
[SwitchC] ospf
[SwitchC-ospf-1] area 1
[SwitchC-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.1] network 10.4.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.1] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
105
<SwitchD> system-view
[SwitchD] router id 10.5.1.1
[SwitchD] ospf
[SwitchD-ospf-1] area 2
[SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.2] network 10.5.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.2] quit
[SwitchD-ospf-1] quit
Verifying the configuration
# Display information about neighbors on Switch A.
[SwitchA] display ospf peer verbose
OSPF Process 1 with Router ID 10.2.1.1
Neighbors
Area 0.0.0.0 interface 10.1.1.1(Vlan-interface100)'s neighbors
Router ID: 10.3.1.1 Address: 10.1.1.2 GR State: Normal
State: Full Mode: Nbr is master Priority: 1
DR: 10.1.1.1 BDR: 10.1.1.2 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 37 sec
Neighbor is up for 06:03:59
Authentication Sequence: [ 0 ]
Neighbor state change count: 5
Area 0.0.0.1 interface 10.2.1.1(Vlan-interface200)'s neighbors
Router ID: 10.4.1.1 Address: 10.2.1.2 GR State: Normal
State: Full Mode: Nbr is master Priority: 1
DR: 10.2.1.1 BDR: 10.2.1.2 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 32 sec
Neighbor is up for 06:03:12
Authentication Sequence: [ 0 ]
Neighbor state change count: 5
# Display OSPF routing information on Switch A.
[SwitchA] display ospf routing
OSPF Process 1 with Router ID 10.2.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 1 Transit 10.2.1.1 10.2.1.1 0.0.0.1
10.3.1.0/24 2 Inter 10.1.1.2 10.3.1.1 0.0.0.0
10.4.1.0/24 2 Stub 10.2.1.2 10.4.1.1 0.0.0.1
10.5.1.0/24 3 Inter 10.1.1.2 10.3.1.1 0.0.0.0
106
10.1.1.0/24 1 Transit 10.1.1.1 10.2.1.1 0.0.0.0
Total nets: 5
Intra area: 3 Inter area: 2 ASE: 0 NSSA: 0
# Display OSPF routing information on Switch D.
[SwitchD] display ospf routing
OSPF Process 1 with Router ID 10.5.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 3 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.3.1.0/24 1 Transit 10.3.1.2 10.3.1.1 0.0.0.2
10.4.1.0/24 4 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.5.1.0/24 1 Stub 10.5.1.1 10.5.1.1 0.0.0.2
10.1.1.0/24 2 Inter 10.3.1.1 10.3.1.1 0.0.0.2
Total nets: 5
Intra area: 2 Inter area: 3 ASE: 0 NSSA: 0
# On Switch D, ping the IP address 10.4.1.1 to test reachability.
[SwitchD] ping 10.4.1.1
Ping 10.4.1.1 (10.4.1.1): 56 data bytes, press CTRL_C to break
56 bytes from 10.4.1.1: icmp_seq=0 ttl=253 time=1.549 ms
56 bytes from 10.4.1.1: icmp_seq=1 ttl=253 time=1.539 ms
56 bytes from 10.4.1.1: icmp_seq=2 ttl=253 time=0.779 ms
56 bytes from 10.4.1.1: icmp_seq=3 ttl=253 time=1.702 ms
56 bytes from 10.4.1.1: icmp_seq=4 ttl=253 time=1.471 ms
--- Ping statistics for 10.4.1.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.779/1.408/1.702/0.323 ms
OSPF route redistribution configuration example
Network requirements
•
Enable OSPF on all the switches.
•
Split the AS into three areas.
•
Configure Switch A and Switch B as ABRs.
•
Configure Switch C as an ASBR to redistribute external routes (static routes).
107
Figure 25 Network diagram
Area 1
Switch A
Vlan-int100
10.1.1.1/24
Area 0
Vlan-int100
10.1.1.2/24
Vlan-int200
10.2.1.1/24
Switch B
Vlan-int200
10.3.1.1/24
Vlan-int200
10.2.1.2/24
Area 2
Vlan-int200
10.3.1.2/24
Switch C
Vlan-int300
10.4.1.1/24
Vlan-int500
10.5.1.1/24 Switch D
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2.
Enable OSPF (see " Basic OSPF configuration example ").
3. Configure OSPF to redistribute routes:
# On Switch C, configure a static route destined for network 3.1.2.0/24.
<SwitchC> system-view
[SwitchC] ip route-static 3.1.2.1 24 10.4.1.2
# On Switch C, configure OSPF to redistribute static routes.
[SwitchC] ospf 1
[SwitchC-ospf-1] import-route static
Verifying the configuration
# Display the ABR/ASBR information on Switch D.
<SwitchD> display ospf abr-asbr
OSPF Process 1 with Router ID 10.5.1.1
Routing Table to ABR and ASBR
Topology base (MTID 0)
Type Destination Area Cost Nexthop RtType
Intra 10.3.1.1 0.0.0.2 10 10.3.1.1 ABR
Inter 10.4.1.1 0.0.0.2 22 10.3.1.1 ASBR
# Display the OSPF routing table on Switch D.
<SwitchD> display ospf routing
OSPF Process 1 with Router ID 10.5.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 22 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.3.1.0/24 10 Transit 10.3.1.2 10.3.1.1 0.0.0.2
108
10.4.1.0/24 25 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.5.1.0/24 10 Stub 10.5.1.1 10.5.1.1 0.0.0.2
10.1.1.0/24 12 Inter 10.3.1.1 10.3.1.1 0.0.0.2
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
3.1.2.0/24 1 Type2 1 10.3.1.1 10.4.1.1
Total nets: 6
Intra area: 2 Inter area: 3 ASE: 1 NSSA: 0
OSPF route summarization configuration example
Network requirements
•
Configure OSPF on Switch A and Switch B in AS 200.
•
Configure OSPF on Switch C, Switch D, and Switch E in AS 100.
•
Configure an EBGP connection between Switch B and Switch C. Configure Switch B and
Switch C to redistribute OSPF routes and direct routes into BGP and BGP routes into OSPF.
•
Configure Switch B to advertise only summary route 10.0.0.0/8 to Switch A.
Figure 26 Network diagram
Vlan-int500
10.3.1.1/24
Switch D
Vlan-int400
10.1.1.1/24
Vlan-int300
10.2.1.2/24
Switch E
Vlan-int600
10.4.1.1/24
AS 100
Vlan-int400
10.1.1.2/24
Vlan-int300
10.2.1.1/24
Switch C
Vlan-int200
11.1.1.2/24
EBGP
Vlan-int200
11.1.1.1/24
Switch B
Vlan-int100
11.2.1.2/24
Vlan-int100
11.2.1.1/24
AS 200
Switch A
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] router id 11.2.1.2
[SwitchA] ospf
[SwitchA-ospf-1] area 0
109
[SwitchA-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] router id 11.2.1.1
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 11.2.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] router id 11.1.1.2
[SwitchC] ospf
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] router id 10.3.1.1
[SwitchD] ospf
[SwitchD-ospf-1] area 0
[SwitchD-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.0] network 10.3.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.0] quit
[SwitchD-ospf-1] quit
# Configure Switch E.
<SwitchE> system-view
[SwitchE] router id 10.4.1.1
[SwitchE] ospf
[SwitchE-ospf-1] area 0
[SwitchE-ospf-1-area-0.0.0.0] network 10.2.1.0 0.0.0.255
[SwitchE-ospf-1-area-0.0.0.0] network 10.4.1.0 0.0.0.255
[SwitchE-ospf-1-area-0.0.0.0] quit
[SwitchE-ospf-1] quit
3. Configure BGP to redistribute OSPF routes and direct routes:
# Configure Switch B.
[SwitchB] bgp 200
[SwitchB-bgp] peer 11.1.1.2 as 100
[SwitchB-bgp] address-family ipv4 unicast
[SwitchB-bgp-ipv4] import-route ospf
[SwitchB-bgp-ipv4] import-route direct
[SwitchB-bgp ipv4] quit
[SwitchB-bgp] quit
# Configure Switch C.
110
[SwitchC] bgp 100
[SwitchC-bgp] peer 11.1.1.1 as 200
[SwitchC-bgp] address-family ipv4 unicast
[SwitchC-bgp-ipv4] import-route ospf
[SwitchC-bgp-ipv4]import-route direct
[SwitchC-bgp-ipv4] quit
[SwitchC-bgp] quit
4. Configure Switch B and Switch C to redistribute BGP routes into OSPF:
# Configure OSPF to redistribute routes from BGP on Switch B.
[SwitchB] ospf
[SwitchB-ospf-1] import-route bgp
# Configure OSPF to redistribute routes from BGP on Switch C.
[SwitchC] ospf
[SwitchC-ospf-1] import-route bgp
# Display the OSPF routing table on Switch A.
[SwitchA] display ip routing-table
Destinations : 16 Routes : 16
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.1.1.0/24 O_ASE2 150 1 11.2.1.1 Vlan100
10.2.1.0/24 O_ASE2 150 1 11.2.1.1 Vlan100
10.3.1.0/24 O_ASE2 150 1 11.2.1.1 Vlan100
10.4.1.0/24 O_ASE2 150 1 11.2.1.1 Vlan100
11.2.1.0/24 Direct 0 0 11.2.1.2 Vlan100
11.2.1.0/32 Direct 0 0 11.2.1.2 Vlan100
11.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0
11.2.1.255/32 Direct 0 0 11.2.1.2 Vlan100
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
224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0
224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
5. Configure route summarization:
# Configure route summarization on Switch B to advertise a summary route 10.0.0.0/8.
[SwitchB-ospf-1] asbr-summary 10.0.0.0 8
# Display the IP routing table on Switch A.
[SwitchA] display ip routing-table
Destinations : 13 Routes : 13
Destination/Mask Proto Pre Cost NextHop Interface
0.0.0.0/32 Direct 0 0 127.0.0.1 InLoop0
10.0.0.0/8 O_ASE2 150 2 11.2.1.1 Vlan100
111
11.2.1.0/24 Direct 0 0 11.2.1.2 Vlan100
11.2.1.0/32 Direct 0 0 11.2.1.2 Vlan100
11.2.1.2/32 Direct 0 0 127.0.0.1 InLoop0
11.2.1.255/32 Direct 0 0 11.2.1.2 Vlan100
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
224.0.0.0/4 Direct 0 0 0.0.0.0 NULL0
224.0.0.0/24 Direct 0 0 0.0.0.0 NULL0
255.255.255.255/32 Direct 0 0 127.0.0.1 InLoop0
The output shows that routes 10.1.1.0/24, 10.2.1.0/24, 10.3.1.0/24 and 10.4.1.0/24 are summarized into a single route 10.0.0.0/8.
OSPF stub area configuration example
Network requirements
•
Enable OSPF on all switches, and split the AS into three areas.
•
Configure Switch A and Switch B as ABRs to forward routing information between areas.
•
Configure Switch D as the ASBR to redistribute static routes.
•
Configure Area 1 as a stub area to reduce advertised LSAs without influencing reachability.
Figure 27 Network diagram
Switch A
Vlan-int100
Area 0
10.1.1.1/24
Vlan-int200
10.2.1.1/24
Vlan-int100
10.1.1.2/24
Switch B
Vlan-int200
10.3.1.1/24
Area 1
Stub
Vlan-int200
10.2.1.2/24
Switch C
Vlan-int300
10.4.1.1/24
Area 2
Vlan-int200
10.3.1.2/24
Vlan-int300
10.5.1.1/24
Switch D
ASBR
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2.
Enable OSPF (see " Basic OSPF configuration example ").
3. Configure route redistribution:
# Configure Switch D to redistribute static routes.
<SwitchD> system-view
[SwitchD] ip route-static 3.1.2.1 24 10.5.1.2
[SwitchD] ospf
[SwitchD-ospf-1] import-route static
[SwitchD-ospf-1] quit
# Display ABR/ASBR information on Switch C.
<SwitchC> display ospf abr-asbr
112
OSPF Process 1 with Router ID 10.4.1.1
Routing Table to ABR and ASBR
Topology base (MTID 0)
Type Destination Area Cost Nexthop RtType
Intra 10.2.1.1 0.0.0.1 3 10.2.1.1 ABR
Inter 10.5.1.1 0.0.0.1 7 10.2.1.1 ASBR
# Display OSPF routing table on Switch C.
<SwitchC> display ospf routing
OSPF Process 1 with Router ID 10.4.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 3 Transit 0.0.0.0 10.2.1.1 0.0.0.1
10.3.1.0/24 7 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.4.1.0/24 3 Stub 10.4.1.1 10.4.1.1 0.0.0.1
10.5.1.0/24 17 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.1.1.0/24 5 Inter 10.2.1.1 10.2.1.1 0.0.0.1
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
3.1.2.0/24 1 Type2 1 10.2.1.1 10.5.1.1
Total nets: 6
Intra area: 2 Inter area: 3 ASE: 1 NSSA: 0
The output shows that Switch C's routing table contains an AS external route.
4. Configure Area 1 as a stub area:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf
[SwitchA-ospf-1] area 1
[SwitchA-ospf-1-area-0.0.0.1] stub
[SwitchA-ospf-1-area-0.0.0.1] quit
[SwitchA-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf
[SwitchC-ospf-1] area 1
[SwitchC-ospf-1-area-0.0.0.1] stub
[SwitchC-ospf-1-area-0.0.0.1] quit
[SwitchC-ospf-1] quit
# Display OSPF routing information on Switch C
113
[SwitchC] display ospf routing
OSPF Process 1 with Router ID 10.4.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
0.0.0.0/0 4 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.2.1.0/24 3 Transit 0.0.0.0 10.2.1.1 0.0.0.1
10.3.1.0/24 7 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.4.1.0/24 3 Stub 10.4.1.1 10.4.1.1 0.0.0.1
10.5.1.0/24 17 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.1.1.0/24 5 Inter 10.2.1.1 10.2.1.1 0.0.0.1
Total nets: 6
Intra area: 2 Inter area: 4 ASE: 0 NSSA: 0
The output shows that a default route replaces the AS external route.
# Configure Area 1 as a totally stub area.
[SwitchA] ospf
[SwitchA-ospf-1] area 1
[SwitchA-ospf-1-area-0.0.0.1] stub no-summary
[SwitchA-ospf-1-area-0.0.0.1] quit
[SwitchA-ospf-1] quit
# Display OSPF routing information on Switch C.
[SwitchC] display ospf routing
OSPF Process 1 with Router ID 10.4.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
0.0.0.0/0 4 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.2.1.0/24 3 Transit 0.0.0.0 10.4.1.1 0.0.0.1
10.4.1.0/24 3 Stub 10.4.1.1 10.4.1.1 0.0.0.1
Total nets: 3
Intra area: 2 Inter area: 1 ASE: 0 NSSA: 0
The output shows that inter-area routes are removed, and only one external route (a default route) exists on Switch C.
OSPF NSSA area configuration example
Network requirements
114
•
Configure OSPF on all switches and split AS into three areas.
•
Configure Switch A and Switch B as ABRs to forward routing information between areas.
•
Configure Area 1 as an NSSA area and configure Switch C as an ASBR to redistribute static routes into the AS.
Figure 28 Network diagram
Switch A
Vlan-int100
10.1.1.1/24
Area 0
Vlan-int100
10.1.1.2/24
Vlan-int200
10.2.1.1/24
Switch B
Vlan-int200
10.3.1.1/24
Area 1
NSSA
Vlan-int200
10.2.1.2/24
ASBR
Switch C
Vlan-int300
10.4.1.1/24
Area 2
Vlan-int300
10.5.1.1/24
Vlan-int200
10.3.1.2/24
Switch D
Configuration procedure
1. Configure IP addresses for interfaces.
2.
Enable OSPF (see " Basic OSPF configuration example ").
3. Configure Area 1 as an NSSA area:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf
[SwitchA-ospf-1] area 1
[SwitchA-ospf-1-area-0.0.0.1] nssa
[SwitchA-ospf-1-area-0.0.0.1] quit
[SwitchA-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf
[SwitchC-ospf-1] area 1
[SwitchC-ospf-1-area-0.0.0.1] nssa
[SwitchC-ospf-1-area-0.0.0.1] quit
[SwitchC-ospf-1] quit
# Display OSPF routing information on Switch C.
[SwitchC] display ospf routing
OSPF Process 1 with Router ID 10.4.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 3 Transit 10.2.1.2 10.4.1.1 0.0.0.1
10.3.1.0/24 7 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.4.1.0/24 3 Stub 10.4.1.1 10.4.1.1 0.0.0.1
115
10.5.1.0/24 17 Inter 10.2.1.1 10.2.1.1 0.0.0.1
10.1.1.0/24 5 Inter 10.2.1.1 10.2.1.1 0.0.0.1
Total nets: 5
Intra area: 2 Inter area: 3 ASE: 0 NSSA: 0
4. Configure route redistribution:
# Configure Switch C to redistribute static routes.
[SwitchC] ip route-static 3.1.3.1 24 10.4.1.2
[SwitchC] ospf
[SwitchC-ospf-1] import-route static
[SwitchC-ospf-1] quit
# Display OSPF routing information on Switch D.
<SwitchD> display ospf routing
OSPF Process 1 with Router ID 10.5.1.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 22 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.3.1.0/24 10 Transit 10.3.1.2 10.3.1.1 0.0.0.2
10.4.1.0/24 25 Inter 10.3.1.1 10.3.1.1 0.0.0.2
10.5.1.0/24 10 Stub 10.5.1.1 10.5.1.1 0.0.0.2
10.1.1.0/24 12 Inter 10.3.1.1 10.3.1.1 0.0.0.2
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
3.1.3.0/24 1 Type2 1 10.3.1.1 10.2.1.1
Total nets: 6
Intra area: 2 Inter area: 3 ASE: 1 NSSA: 0
The output shows that an external route imported from the NSSA area exists on Switch D.
OSPF DR election configuration example
Network requirements
•
Enable OSPF on Switches A, B, C, and D on the same network.
•
Configure Switch A as the DR, and configure Switch C as the BDR.
116
Figure 29 Network diagram
Switch A Switch B
DR
Vlan-int1
192.168.1.1/24
Vlan-int1
192.168.1.2/24
Vlan-int1
192.168.1.3/24
Vlan-int1
192.168.1.4/24
BDR
Switch D
Switch C
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] router id 1.1.1.1
[SwitchA] ospf
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] router id 2.2.2.2
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] router id 3.3.3.3
[SwitchC] ospf
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] router id 4.4.4.4
[SwitchD] ospf
[SwitchD-ospf-1] area 0
[SwitchD-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.0] quit
[SwitchD-ospf-1] quit
117
# Display OSPF neighbor information on Switch A.
[SwitchA] display ospf peer verbose
OSPF Process 1 with Router ID 1.1.1.1
Neighbors
Area 0.0.0.0 interface 192.168.1.1(Vlan-interface1)'s neighbors
Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal
State: 2-Way Mode: None Priority: 1
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 38 sec
Neighbor is up for 00:01:31
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 3.3.3.3 Address: 192.168.1.3 GR State: Normal
State: Full Mode: Nbr is master Priority: 1
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 31 sec
Neighbor is up for 00:01:28
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 4.4.4.4 Address: 192.168.1.4 GR State: Normal
State: Full Mode: Nbr is master Priority: 1
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 31 sec
Neighbor is up for 00:01:28
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
The output shows that Switch D is the DR and Switch C is the BDR.
3. Configure router priorities on interfaces:
# Configure Switch A.
[SwitchA] interface vlan-interface 1
[SwitchA-Vlan-interface1] ospf dr-priority 100
[SwitchA-Vlan-interface1] quit
# Configure Switch B.
[SwitchB] interface vlan-interface 1
[SwitchB-Vlan-interface1] ospf dr-priority 0
[SwitchB-Vlan-interface1] quit
# Configure Switch C.
[SwitchC] interface vlan-interface 1
118
[SwitchC-Vlan-interface1] ospf dr-priority 2
[SwitchC-Vlan-interface1] quit
# Display neighbor information on Switch D.
<SwitchD> display ospf peer verbose
OSPF Process 1 with Router ID 4.4.4.4
Neighbors
Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors
Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal
State: Full Mode:Nbr is slave Priority: 100
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 31 sec
Neighbor is up for 00:11:17
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal
State: Full Mode:Nbr is slave Priority: 0
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 35 sec
Neighbor is up for 00:11:19
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 3.3.3.3 Address: 192.168.1.3 GR State: Normal
State: Full Mode:Nbr is slave Priority: 2
DR: 192.168.1.4 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 33 sec
Neighbor is up for 00:11:15
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
The output shows that the DR and BDR are not changed, because the priority settings do not take effect immediately.
4. Restart OSPF process:
# Restart the OSPF process of Switch D.
<SwitchD> reset ospf 1 process
Warning : Reset OSPF process? [Y/N]:y
# Display neighbor information on Switch D.
<SwitchD> display ospf peer verbose
OSPF Process 1 with Router ID 4.4.4.4
119
Neighbors
Area 0.0.0.0 interface 192.168.1.4(Vlan-interface1)'s neighbors
Router ID: 1.1.1.1 Address: 192.168.1.1 GR State: Normal
State: Full Mode: Nbr is slave Priority: 100
DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 39 sec
Neighbor is up for 00:01:40
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 2.2.2.2 Address: 192.168.1.2 GR State: Normal
State: 2-Way Mode: None Priority: 0
DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 35 sec
Neighbor is up for 00:01:44
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
Router ID: 3.3.3.3 Address: 192.168.1.3 GR State: Normal
State: Full Mode: Nbr is slave Priority: 2
DR: 192.168.1.1 BDR: 192.168.1.3 MTU: 0
Options is 0x02 (-|-|-|-|-|-|E|-)
Dead timer due in 39 sec
Neighbor is up for 00:01:41
Authentication Sequence: [ 0 ]
Neighbor state change count: 6
BFD status: Disabled
The output shows that Switch A becomes the DR and Switch C becomes the BDR.
If the neighbor state is full, Switch D has established an adjacency with the neighbor. If the neighbor state is 2-way , the two switches are not the DR or the BDR, and they do not exchange
LSAs.
# Display OSPF interface information.
[SwitchA] display ospf interface
OSPF Process 1 with Router ID 1.1.1.1
Interfaces
Area: 0.0.0.0
IP Address Type State Cost Pri DR BDR
192.168.1.1 Broadcast DR 1 100 192.168.1.1 192.168.1.3
[SwitchB] display ospf interface
120
OSPF Process 1 with Router ID 2.2.2.2
Interfaces
Area: 0.0.0.0
IP Address Type State Cost Pri DR BDR
192.168.1.2 Broadcast DROther 1 0 192.168.1.1 192.168.1.3
The interface state DROther means the interface is not the DR or BDR.
OSPF virtual link configuration example
Network requirements
As shown in Figure 30 , configure a virtual link between Switch B and Switch C to connect Area 2 to
the backbone area. After configuration, Switch B can learn routes to Area 2.
Figure 30 Network diagram
Area 1
Virtual link
Switch B
Vlan-int200
10.2.1.1/24
Area 0
Vlan-int300
10.1.1.2/24
Vlan-int300
10.1.1.1/24
Switch D
Vlan-int100
10.3.1.1/24
Vlan-int100
10.3.1.2/24
Area 2
Switch C
Vlan-int200
10.2.1.2/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf 1 router-id 1.1.1.1
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf 1 router-id 2.2.2.2
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] area 1
[SwitchB–ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255
[SwitchB–ospf-1-area-0.0.0.1] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf 1 router-id 3.3.3.3
Switch A
121
[SwitchC-ospf-1] area 1
[SwitchC-ospf-1-area-0.0.0.1] network 10.2.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.1] quit
[SwitchC-ospf-1] area 2
[SwitchC–ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255
[SwitchC–ospf-1-area-0.0.0.2] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] ospf 1 router-id 4.4.4.4
[SwitchD-ospf-1] area 2
[SwitchD-ospf-1-area-0.0.0.2] network 10.3.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.2] quit
[SwitchD-ospf-1] quit
# Display the OSPF routing table on Switch B.
[SwitchB] display ospf routing
OSPF Process 1 with Router ID 2.2.2.2
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 2 Transit 10.2.1.1 3.3.3.3 0.0.0.1
10.1.1.0/24 2 Transit 10.1.1.2 2.2.2.2 0.0.0.0
Total nets: 2
Intra area: 2 Inter area: 0 ASE: 0 NSSA: 0
The output shows that Switch B does not have routes to Area 2 because Area 0 is not directly connected to Area 2.
3. Configure a virtual link:
# Configure Switch B.
[SwitchB] ospf
[SwitchB-ospf-1] area 1
[SwitchB-ospf-1-area-0.0.0.1] vlink-peer 3.3.3.3
[SwitchB-ospf-1-area-0.0.0.1] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
[SwitchC] ospf 1
[SwitchC-ospf-1] area 1
[SwitchC-ospf-1-area-0.0.0.1] vlink-peer 2.2.2.2
[SwitchC-ospf-1-area-0.0.0.1] quit
[SwitchC-ospf-1] quit
# Display the OSPF routing table on Switch B.
[SwitchB] display ospf routing
OSPF Process 1 with Router ID 2.2.2.2
Routing Table
122
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
10.2.1.0/24 2 Transit 10.2.1.1 3.3.3.3 0.0.0.1
10.3.1.0/24 5 Inter 10.2.1.2 3.3.3.3 0.0.0.0
10.1.1.0/24 2 Transit 10.1.1.2 2.2.2.2 0.0.0.0
Total nets: 3
Intra area: 2 Inter area: 1 ASE: 0 NSSA: 0
The output shows that Switch B has learned the route 10.3.1.0/24 to Area 2.
OSPF GR configuration example
Network requirements
•
Switch A, Switch B, and Switch C that belong to the same AS and the same OSPF routing domain are GR capable.
•
Switch A acts as the non-IETF GR restarter. Switch B and Switch C are the GR helpers, and synchronize their LSDBs with Switch A through OOB communication of GR.
Figure 31 Network diagram
Router ID: 1.1.1.1
GR restarter
Switch A
Vlan-int100
192.1.1.1/24
Vlan-int100
192.1.1.2/24
Switch B
Vlan-int100
192.1.1.3/24
Switch C
GR helper
Router ID: 2.2.2.2
Configuration procedure
GR helper
Router ID: 3.3.3.3
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
SwitchA> system-view
[SwitchA] router id 1.1.1.1
[SwitchA] ospf 100
[SwitchA-ospf-100] area 0
[SwitchA-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255
[SwitchA-ospf-100-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] router id 2.2.2.2
123
[SwitchB] ospf 100
[SwitchB-ospf-100] area 0
[SwitchB-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255
[SwitchB-ospf-100-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] router id 3.3.3.3
[SwitchC] ospf 100
[SwitchC-ospf-100] area 0
[SwitchC-ospf-100-area-0.0.0.0] network 192.1.1.0 0.0.0.255
[SwitchC-ospf-100-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
3. Configure OSPF GR:
# Configure Switch A as the non-IETF OSPF GR restarter: enable the link-local signaling capability, the out-of-band re-synchronization capability, and non-IETF GR capability for OSPF process 100.
[SwitchA-ospf-100] enable link-local-signaling
[SwitchA-ospf-100] enable out-of-band-resynchronization
[SwitchA-ospf-100] graceful-restart
[SwitchA-ospf-100] quit
# Configure Switch B as the GR helper: enable the link-local signaling capability and the out-of-band re-synchronization capability for OSPF process 100.
[SwitchB-ospf-100] enable link-local-signaling
[SwitchB-ospf-100] enable out-of-band-resynchronization
# Configure Switch C as the GR helper: enable the link-local signaling capability and the out-of-band re-synchronization capability for OSPF process 100.
[SwitchC-ospf-100] enable link-local-signaling
[SwitchC-ospf-100] enable out-of-band-resynchronization
Verifying the configuration
# Enable OSPF GR event debugging and restart the OSPF process by using GR on Switch A.
<SwitchA> debugging ospf event graceful-restart
<SwitchA> terminal monitor
<SwitchA> terminal logging level 7
<SwitchA> reset ospf 100 process graceful-restart
Reset OSPF process? [Y/N]:y
%Oct 21 15:29:28:727 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.2(Vlan-interface100) from Full to Down.
%Oct 21 15:29:28:729 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.3(Vlan-interface100) from Full to Down.
*Oct 21 15:29:28:735 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 nonstandard GR Started for OSPF Router
*Oct 21 15:29:28:735 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 created GR wait timer,timeout interval is 40(s).
*Oct 21 15:29:28:735 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 created GR Interval timer,timeout interval is 120(s).
*Oct 21 15:29:28:758 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 created OOB Progress timer for neighbor 192.1.1.3.
124
*Oct 21 15:29:28:766 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 created OOB Progress timer for neighbor 192.1.1.2.
%Oct 21 15:29:29:902 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.2(Vlan-interface100) from Loading to Full.
*Oct 21 15:29:29:902 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.2.
%Oct 21 15:29:30:897 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.3(Vlan-interface100) from Loading to Full.
*Oct 21 15:29:30:897 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 deleted OOB Progress timer for neighbor 192.1.1.3.
*Oct 21 15:29:30:911 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF GR: Process 100 Exit Restart,Reason : DR or BDR change,for neighbor : 192.1.1.3.
*Oct 21 15:29:30:911 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 deleted GR Interval timer.
*Oct 21 15:29:30:912 2011 SwitchA OSPF/7/DEBUG: -MDC=1;
OSPF 100 deleted GR wait timer.
%Oct 21 15:29:30:920 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.2(Vlan-interface100) from Full to Down.
%Oct 21 15:29:30:921 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.3(Vlan-interface100) from Full to Down.
%Oct 21 15:29:33:815 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.3(Vlan-interface100) from Loading to Full.
%Oct 21 15:29:35:578 2011 SwitchA OSPF/5/OSPF_NBR_CHG: -MDC=1; OSPF 100 Neighbor
192.1.1.2(Vlan-interface100) from Loading to Full.
The output shows that Switch A completes GR.
OSPF NSR configuration example
Network requirements
As shown in Figure 32 , Switch S, Switch A, and Switch B belong to the same OSPF routing domain.
Enable OSPF NSR on Switch S to ensure correct routing when an active/standby switchover occurs on Switch S.
Figure 32 Network diagram
Loop 0
22.22.22.22/32
Switch A
Vlan-int100
12.12.12.1/24
Vlan-int100
12.12.12.2/24
Switch S
Vlan-int200
14.14.14.1/24
Vlan-int200
14.14.14.2/24
Switch B
Loop 0
44.44.44.44/32
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure OSPF on the switches to ensure the following: (Details not shown.)
Switch S, Switch A, and Switch B can communicate with each other at Layer 3.
Dynamic route update can be implemented among them with OSPF.
3. Enable OSPF NSR on Switch S.
<SwitchS> system-view
[SwitchS] ospf 100
[SwitchS-ospf-100] non-stop-routing
125
[SwitchS-ospf-100] quit
Verifying the configuration
# Perform an active/standby switchover on Switch S.
[SwitchS] placement reoptimize
Predicted changes to the placement
Program Current location New location
--------------------------------------------------------------------- lb 0/0 0/0 lsm 0/0 0/0 slsp 0/0 0/0 rib6 0/0 0/0 routepolicy 0/0 0/0 rib 0/0 0/0 staticroute6 0/0 0/0 staticroute 0/0 0/0 eviisis 0/0 0/0 ospf 0/0 1/0
Continue? [y/n]:y
Re-optimization of the placement start. You will be notified on completion
Re-optimization of the placement complete. Use 'display placement' to view the new placement
# During the switchover period, display OSPF neighbors on Switch A to verify the neighbor relationship between Switch A and Switch S.
<SwitchA> display ospf peer
OSPF Process 1 with Router ID 2.2.2.1
Neighbor Brief Information
Area: 0.0.0.0
Router ID Address Pri Dead-Time State Interface
3.3.3.1 12.12.12.2 1 37 Full/BDR Vlan100
# Display OSPF routes on Switch A to verify if Switch A has a route to the loopback interface on
Switch B.
<SwitchA> display ospf routing
OSPF Process 1 with Router ID 2.2.2.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
44.44.44.44/32 2 Stub 12.12.12.2 4.4.4.1 0.0.0.0
14.14.14.0/24 2 Transit 12.12.12.2 4.4.4.1 0.0.0.0
22.22.22.22/32 0 Stub 22.22.22.22 2.2.2.1 0.0.0.0
12.12.12.0/24 1 Transit 12.12.12.1 2.2.2.1 0.0.0.0
Total nets: 4
126
Intra area: 4 Inter area: 0 ASE: 0 NSSA: 0
# Display OSPF neighbors on Switch B to verify the neighbor relationship between Switch B and
Switch S.
<SwitchB> display ospf peer
OSPF Process 1 with Router ID 4.4.4.1
Neighbor Brief Information
Area: 0.0.0.0
Router ID Address Pri Dead-Time State Interface
3.3.3.1 14.14.14.2 1 39 Full/BDR Vlan200
# Display OSPF routes on Switch B to verify if Switch B has a route to the loopback interface on
Switch A.
<SwitchB> display ospf routing
OSPF Process 1 with Router ID 4.4.4.1
Routing Table
Topology base (MTID 0)
Routing for network
Destination Cost Type NextHop AdvRouter Area
44.44.44.44/32 0 Stub 44.44.44.44 4.4.4.1 0.0.0.0
14.14.14.0/24 1 Transit 14.14.14.1 4.4.4.1 0.0.0.0
22.22.22.22/32 2 Stub 14.14.14.2 2.2.2.1 0.0.0.0
12.12.12.0/24 2 Transit 14.14.14.2 2.2.2.1 0.0.0.0
Total nets: 4
Intra area: 4 Inter area: 0 ASE: 0 NSSA: 0
The output shows the following when an active/standby switchover occurs on Switch S:
•
The neighbor relationships and routing information on Switch A and Switch B have not changed.
•
The traffic from Switch A to Switch B has not been impacted.
BFD for OSPF configuration example
Network requirements
As shown in Figure 33 , run OSPF on Switch A, Switch B, and Switch C so that they are reachable to
each other at the network layer.
•
When the link over which Switch A and Switch B communicate through a Layer 2 switch fails,
BFD can quickly detect the failure and notify OSPF of the failure.
•
Switch A and Switch B then communicate through Switch C.
127
Figure 33 Network diagram
Loop0
Switch A
Vlan-int10
Vlan-int11
BFD
L2 Switch
Vlan-int10
Switch B
Vlan-int13
Loop0
Area 0
Vlan-int11 Vlan-int13
Switch C
Table 9 Interface and IP address assignment
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Interface
Vlan-int10
Vlan-int11
Loop0
Vlan-int10
Vlan-int13
Loop0
Vlan-int11
IP address
192.168.0.102/24
10.1.1.102/24
121.1.1.1/32
192.168.0.100/24
13.1.1.1/24
120.1.1.1/32
10.1.1.100/24
Switch C
Configuration procedure
Vlan-int13 13.1.1.2/24
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable OSPF:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] network 121.1.1.1 0.0.0.0
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 120.1.1.1 0.0.0.0
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
128
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] network 13.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
3. Configure BFD:
# Enable BFD on Switch A and configure BFD parameters.
[SwitchA] bfd session init-mode active
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ospf bfd enable
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500
[SwitchA-Vlan-interface10] bfd min-receive-interval 500
[SwitchA-Vlan-interface10] bfd detect-multiplier 7
[SwitchA-Vlan-interface10] quit
# Enable BFD on Switch B and configure BFD parameters.
[SwitchB] bfd session init-mode active
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ospf bfd enable
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500
[SwitchB-Vlan-interface10] bfd min-receive-interval 500
[SwitchB-Vlan-interface10] bfd detect-multiplier 6
[SwitchB-Vlan-interface10] quit
Verifying the configuration
# Display the BFD information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 Session Working Under Ctrl Mode:
LD/RD SourceAddr DestAddr State Holdtime Interface
3/1 192.168.0.102 192.168.0.100 Up 1700ms Vlan10
# Display routes destined for 120.1.1.1/32 on Switch A.
<SwitchA> display ip routing-table 120.1.1.1 verbose
Summary Count : 1
Destination: 120.1.1.1/32
Protocol: O_INTRA
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 1 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
129
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 192.168.0.100
Label: NULL RealNextHop: 192.168.0.100
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface10
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
The output shows that Switch A communicates with Switch B through VLAN-interface 10. Then the link over VLAN-interface 10 fails.
# Display routes destined for 120.1.1.1/32 on Switch A.
<SwitchA> display ip routing-table 120.1.1.1 verbose
Summary Count : 1
Destination: 120.1.1.1/32
Protocol: O_INTRA
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 2 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 10.1.1.100
Label: NULL RealNextHop: 10.1.1.100
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface11
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
OSPF FRR configuration example
Network requirements
As shown in Figure 34 , Switch A, Switch B, and Switch C reside in the same OSPF domain.
Configure OSPF FRR so that when the link between Switch A and Switch B fails, traffic is immediately switched to Link B.
130
Figure 34 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
101
Link B
Vlan
-int
100
Link A
Loop0
Switch A
Vlan-int200
Table 10 Interface and IP address assignment
Vlan
-int
101
Vlan-int200
Switch B
Loop0
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Interface
Vlan-int100
Vlan-int200
Loop0
Vlan-int101
Vlan-int200
Loop0
Vlan-int100
IP address
12.12.12.1/24
13.13.13.1/24
1.1.1.1/32
24.24.24.4/24
13.13.13.2/24
4.4.4.4/32
12.12.12.2/24
Switch C
Configuration procedure
Vlan-int101 24.24.24.2/24
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure OSPF on the switches to ensure that Switch A, Switch B, and Switch C can communicate with each other at the network layer. (Details not shown.)
3. Configure OSPF FRR to automatically calculate the backup next hop:
You can enable OSPF FRR to either calculate a backup next hop by using the LFA algorithm, or specify a backup next hop by using a routing policy.
(Method 1.) Enable OSPF FRR to calculate the backup next hop by using the LFA algorithm:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospf 1
[SwitchA-ospf-1] fast-reroute lfa
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf 1
[SwitchB-ospf-1] fast-reroute lfa
[SwitchB-ospf-1] quit
(Method 2.) Enable OSPF FRR to designate a backup next hop by using a routing policy.
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ip prefix-list abc index 10 permit 4.4.4.4 32
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ip address prefix-list abc
131
[SwitchA-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
100 backup-nexthop 12.12.12.2
[SwitchA-route-policy-frr-10] quit
[SwitchA] ospf 1
[SwitchA-ospf-1] fast-reroute route-policy frr
[SwitchA-ospf-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ip prefix-list abc index 10 permit 1.1.1.1 32
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ip address prefix-list abc
[SwitchB-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
101 backup-nexthop 24.24.24.2
[SwitchB-route-policy-frr-10] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] fast-reroute route-policy frr
[SwitchB-ospf-1] quit
Verifying the configuration
# Display route 4.4.4.4/32 on Switch A to view the backup next hop information.
[SwitchA] display ip routing-table 4.4.4.4 verbose
Summary Count : 1
Destination: 4.4.4.4/32
Protocol: O_INTRA
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 1 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.2
Label: NULL RealNextHop: 13.13.13.2
BkLabel: NULL BkNextHop: 12.12.12.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display route 1.1.1.1/32 on Switch B to view the backup next hop information.
[SwitchB] display ip routing-table 1.1.1.1 verbose
Summary Count : 1
Destination: 1.1.1.1/32
Protocol: O_INTRA
132
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 1 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.1
Label: NULL RealNextHop: 13.13.13.1
BkLabel: NULL BkNextHop: 24.24.24.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
Troubleshooting OSPF configuration
No OSPF neighbor relationship established
Symptom
No OSPF neighbor relationship can be established.
Analysis
If the physical link and lower layer protocols work correctly, verify OSPF parameters configured on interfaces. Two neighbors must have the same parameters, such as the area ID, network segment, and mask. (A P2P or virtual link can have different network segments and masks.)
Solution
To resolve the problem:
1. Use the display ospf peer command to verify OSPF neighbor information.
2. Use the display ospf interface command to verify OSPF interface information.
3. Ping the neighbor router's IP address to verify that the connectivity is normal.
4. Verify OSPF timers. The dead interval on an interface must be a minimum of four times the hello interval.
5. On an NBMA network, use the peer ip-address command to manually specify the neighbor.
6. A minimum of one interface must have a router priority higher than 0 on an NBMA or a broadcast network.
7. If the problem persists, contact Hewlett Packard Enterprise Support.
Incorrect routing information
Symptom
OSPF cannot find routes to other areas.
133
Analysis
Solution
The backbone area must maintain connectivity to all other areas. If a router connects to more than one area, a minimum of one area must be connected to the backbone. The backbone cannot be configured as a stub area.
In a stub area, all routers cannot receive external routes, and all interfaces connected to the stub area must belong to the stub area.
To resolve the problem:
1. Use the display ospf peer command to verify neighbor information.
2. Use the display ospf interface command to verify OSPF interface information.
3. Use the display ospf lsdb command to verify the LSDB.
4. Use the display current-configuration configuration ospf command to verify area configuration. If more than two areas are configured, a minimum of one area is connected to the backbone.
5. In a stub area, all routers attached are configured with the stub command. In an NSSA area, all routers attached are configured with the nssa command.
6. If a virtual link is configured, use the display ospf vlink command to verify the state of the virtual link.
7. If the problem persists, contact Hewlett Packard Enterprise Support.
134
Configuring IS-IS
Overview
Intermediate System-to-Intermediate System (IS-IS) is a dynamic routing protocol designed by the
ISO to operate on the connectionless network protocol (CLNP).
IS-IS was modified and extended in RFC 1195 by the IETF for application in both TCP/IP and OSI reference models, called "Integrated IS-IS" or "Dual IS-IS."
IS-IS is an IGP used within an AS. It uses the SPF algorithm for route calculation.
Terminology
•
Intermediate system —Similar to a router in TCP/IP, IS is the basic unit used in an IS-IS routing domain to generate and propagate routing information. Throughout this chapter, an IS refers to a router.
•
End system —Similar to a host in TCP/IP, an ES does not run IS-IS. ISO defines the ES-IS protocol for communication between an ES and an IS.
•
Routing domain —An RD comprises a group of ISs that exchange routing information with each other by using the same routing protocol.
•
Area —An IS-IS routing domain can be split into multiple areas.
•
Link State Database —All link states in the network form the LSDB. Each IS has a minimum of one LSDB. An IS uses the SPF algorithm and LSDB to generate IS-IS routes.
•
Link State Protocol Data Unit or Link State Packet —An IS advertises link state information in an LSP.
•
Network Protocol Data Unit —An NPDU is a network layer protocol packet in OSI, similar to an IP packet in TCP/IP.
•
Designated IS —A DIS is elected on a broadcast network.
•
Network service access point —An NSAP is an OSI network layer address. The NSAP identifies an abstract network service access point and describes the network address format in the OSI reference model.
IS-IS address format
NSAP
As shown in Figure 35 , an NSAP address comprises the Initial Domain Part (IDP) and the Domain
Specific Part (DSP). The IDP is analogous to the network ID of an IP address, and the DSP is analogous to the subnet and host ID.
The IDP includes the Authority and Format Identifier (AFI) and the Initial Domain Identifier (IDI).
The DSP includes:
•
High Order Part of DSP (HO-DSP) — Identifies the area.
•
System ID —Identifies the host.
•
SEL —Identifies the type of service.
The IDP and DSP are variable in length. The length of an NSAP address is in the range of 8 to 20 bytes.
135
Figure 35 NSAP address format
IDP DSP
System ID (6 octet) AFI IDI HO-DSP SEL (1 octet)
Area address
Area address
The area address comprises the IDP and the HO-DSP of the DSP, which identify the area and the routing domain. Different routing domains cannot have the same area address.
Typically, a router only needs one area address, and all nodes in the same area must have the same area address. To support smooth area merging, partitioning, and switching, a router can have a maximum of three area addresses.
System ID
A system ID uniquely identifies a host or router. It has a fixed length of 48 bits (6 bytes).
The system ID of a device can be generated from the router ID. For example, suppose a router uses the IP address 168.10.1.1 of Loopback 0 as the router ID. The system ID can be obtained in the following steps:
1. Extend each decimal number of the IP address to three digits by adding 0s from the left, such as
168.010.001.001.
2. Divide the extended IP address into three sections that each has four digits to get the system ID
1680.1000.1001.
If you use other methods to define a system ID, make sure that it can uniquely identify the host or router.
SEL
The N-SEL, or the NSAP selector (SEL), is similar to the protocol identifier in IP. Different transport layer protocols correspond to different SELs. All SELs in IP are 00.
Routing method
The IS-IS address format identifies the area, so a Level-1 router can easily identify packets destined to other areas. IS-IS routers perform routing as follows:
•
A Level-1 router performs intra-area routing according to the system ID. If the destination address of a packet does not belong to the local area, the Level-1 router forwards it to the nearest Level-1-2 router.
•
A Level-2 router performs inter-area routing according to the area address.
NET
A network entity title (NET) identifies the network layer information of an IS. It does not include transport layer information. A NET is a special NSAP address with the SEL being 0. The length of a
NET is in the range of 8 to 20 bytes, same as a NSAP address.
A NET includes the following parts:
•
Area ID —Has a length of 1 to 13 bytes.
•
System ID —A system ID uniquely identifies a host or router in the area and has a fixed length of 6 bytes.
•
SEL —Has a value of 0 and a fixed length of 1 byte.
For example, for a NET ab.cdef.1234.5678.9abc.00, the area ID is ab.cdef, the system ID is
1234.5678.9abc, and the SEL is 00.
136
Typically, a router only needs one NET, but it can have a maximum of three NETs for smooth area merging and partitioning. When you configure multiple NETs, make sure the system IDs are the same.
IS-IS area
IS-IS has a 2-level hierarchy to support large-scale networks. A large-scale routing domain is divided into multiple areas. Typically, a Level-1 router is deployed within an area. A Level-2 router is deployed between areas. A Level-1-2 router is deployed between Level-1 and Level-2 routers.
Level-1 and Level-2
•
Level-1 router —A Level-1 router establishes neighbor relationships with Level-1 and Level-1-2 routers in the same area. It maintains an LSDB comprising intra-area routing information. A
Level-1 router forwards packets destined for external areas to the nearest Level-1-2 router.
Level-1 routers in different areas cannot establish neighbor relationships.
•
Level-2 router —A Level-2 router establishes neighbor relationships with Level-2 and Level-1-2 routers in the same area or in different areas. It maintains a Level-2 LSDB containing inter-area routing information. All the Level-2 and Level-1-2 routers must be contiguous to form the backbone of the IS-IS routing domain. Level-2 routers can establish neighbor relationships even if they are in different areas.
•
Level-1-2 router —A router with both Level-1 and Level-2 router functions is a Level-1-2 router.
It can establish Level-1 neighbor relationships with Level-1 and Level-1-2 routers in the same area. It can establish Level-2 neighbor relationships with Level-2 and Level-1-2 routers in different areas. A Level-1 router can reach other areas only through a Level-1-2 router. The
Level-1-2 router maintains two LSDBs, a Level-1 LSDB for intra-area routing and a Level-2
LSDB for inter-area routing.
Figure 36 shows one IS-IS network topology. Area 1 is the backbone that comprises a set of Level-2
routers. The other four areas are non-backbone areas connected to the backbone through Level-1-2 routers.
Figure 36 IS-IS topology 1
Area 3
Area 2
L1/L2
L1 L2
Area 4
L2
L1/L2
L2
Area 1
L2
L1/L2
Area 5
L1/L2 L1
L1 L1
L1 L1
Figure 37 shows another IS-IS topology. The Level-1-2 routers connect to the Level-1 and Level-2
routers, and form the IS-IS backbone together with the Level-2 routers. No area is defined as the
137
backbone in this topology. The backbone comprises all contiguous Level-2 and Level-1-2 routers in different areas. The IS-IS backbone does not need to be a specific area.
Figure 37 IS-IS topology 2
Area 1
L2
Area 2
L1
Area 4
L1/L2
L1 L1/L2 L1
Area 3
L2
Both the Level-1 and Level-2 routers use the SPF algorithm to generate the shortest path tree.
Route leaking
Level-2 and Level-1-2 routers form a Level-2 area. An IS-IS routing domain comprises only one
Level-2 area and multiple Level-1 areas. A Level-1 area must connect to the Level-2 area rather than another Level-1 area.
Level-1-2 routers send the routing information of Level-1 areas to the Level-2 area. Level-2 routers know the routing information of the entire IS-IS routing domain. By default, a Level-2 router does not advertise the routing information of other areas to a Level-1 area. A Level-1 router simply sends packets destined for other areas to the nearest Level-1-2 router. The path passing through the
Level-1-2 router might not be the best. To solve this problem, IS-IS provides the route leaking feature.
Route leaking enables a Level-1-2 router to advertise the routes of other areas to the connected
Level-1 area so that the Level-1 routers can select the optimal routes.
IS-IS network types
Network types
IS-IS supports only broadcast networks (for example, Ethernet and Token Ring).
DIS and pseudonodes
IS-IS routers on a broadcast network must elect a DIS.
The Level-1 and Level-2 DISs are elected separately. You can assign different priorities to a router for different level DIS elections. The higher the router priority, the more likely the router becomes the
DIS. If multiple routers with the same highest DIS priority exist, the one with the highest Subnetwork
Point of Attachment (SNPA) address will be elected. On a broadcast network, the SNPA address is the MAC address. A router can be the DIS for different levels.
IS-IS DIS election differs from OSPF DIS election in the following ways:
•
A router with priority 0 can also participate in the DIS election.
•
When a router with a higher priority is added to the network, an LSP flooding process is performed to elect the router as the new DIS.
As shown in Figure 38 , the same level routers on a network, including non-DIS routers, establish
adjacency with each other.
138
Figure 38 DIS in the IS-IS broadcast network
L1/L2 L1/L2
L2 adjacencies
L1 adjacencies
L1
DIS
L2
DIS
The DIS creates and updates pseudonodes, and generates LSPs for the pseudonodes, to describe all routers on the network.
A pseudonode represents a virtual node on the broadcast network. It is not a real router. In IS-IS, it is identified by the system ID of the DIS and a 1-byte Circuit ID (a non-zero value).
Using pseudonodes simplifies network topology and can reduce the amount of resources consumed by SPF.
NOTE:
On an IS-IS broadcast network, all routers establish adjacency relationships, but they synchronize their LSDBs through the DIS.
IS-IS PDUs
PDU
IS-IS PDUs are encapsulated into link layer frames. An IS-IS PDU has two parts, the headers and the variable length fields. The headers comprise the PDU common header and the PDU specific header. All PDUs have the same PDU common header. The specific headers vary by PDU type.
Figure 39 PDU format
PDU common header PDU specific header Variable length fields (CLV)
Table 11 PDU types
25
26
27
17
18
20
24
Type
15
16
PDU Type
Level-1 LAN IS-IS hello PDU
Level-2 LAN IS-IS hello PDU
Point-to-Point IS-IS hello PDU
Level-1 Link State PDU
Level-2 Link State PDU
Level-1 Complete Sequence Numbers PDU
Level-2 Complete Sequence Numbers PDU
Level-1 Partial Sequence Numbers PDU
Level-2 Partial Sequence Numbers PDU
Acronym
L1 LAN IIH
L2 LAN IIH
P2P IIH
L1 LSP
L2 LSP
L1 CSNP
L2 CSNP
L1 PSNP
L2 PSNP
139
Hello PDU
IS-to-IS hello (IIH) PDUs are used by routers to establish and maintain neighbor relationships. On broadcast networks, Level-1 routers use Level-1 LAN IIHs, and Level-2 routers use Level-2 LAN IIHs.
The P2P IIHs are used on point-to-point networks.
LSP
The LSPs carry link state information. LSPs include Level-1 LSPs and Level-2 LSPs. The Level-2
LSPs are sent by the Level-2 routers, and the Level-1 LSPs are sent by the Level-1 routers. The
Level-1-2 router can send both types of LSPs.
SNP
A sequence number PDU (SNP) describes the complete or partial LSPs for LSDB synchronization.
SNPs include CSNP and PSNP, which are further divided into Level-1 CSNP, Level-2 CSNP, Level-1
PSNP, and Level-2 PSNP.
A CSNP describes the summary of all LSPs for LSDB synchronization between neighboring routers.
On broadcast networks, CSNPs are sent by the DIS periodically (every 10 seconds by default).
A PSNP only contains the sequence numbers of one or multiple latest received LSPs. It can acknowledge multiple LSPs at one time. When LSDBs are not synchronized, a PSNP is used to request missing LSPs from a neighbor.
CLV
The variable fields of PDU comprise multiple Code-Length-Value (CLV) triplets.
Figure 40 CLV format
Code
No. of Octets
1
Length 1
Value Length
Table 12 shows that different PDUs contain different CLVs. Codes 1 through 10 are defined in ISO
10589 (code 3 and 5 are not shown in the table). Codes 128 through 132 are defined in RFC 1195.
Codes 222 through 237 are defined in RFC 5120.
Table 12 CLV codes and PDU types
CLV Code
1
9
10
128
129
130
2
4
6
7
8
Name
Area Addresses
IS Neighbors (LSP)
Partition Designated Level 2 IS
IS Neighbors (MAC Address)
IS Neighbors (SNPA Address)
Padding
LSP Entries
Authentication Information
IP Internal Reachability Information
Protocols Supported
IP External Reachability Information
PDU Type
IIH, LSP
LSP
L2 LSP
LAN IIH
LAN IIH
IIH
SNP
IIH, LSP, SNP
LSP
IIH, LSP
L2 LSP
140
CLV Code
131
132
222
229
235
237
Name
Inter-Domain Routing Protocol Information
IP Interface Address
MT-ISN
M-Topologies
MT IP. Reach
MT IPv6 IP. Reach
PDU Type
L2 LSP
IIH, LSP
LSP
IIH, LSP
LSP
LSP
Protocols and standards
•
ISO 10589 ISO IS-IS Routing Protocol
•
ISO 9542 ES-IS Routing Protocol
•
ISO 8348/Ad2 Network Services Access Points
•
RFC 1195, Use of OSI IS-IS for Routing in TCP/IP and Dual Environments
•
RFC 2763, Dynamic Hostname Exchange Mechanism for IS-IS
•
RFC 2966, Domain-wide Prefix Distribution with Two-Level IS-IS
•
RFC 2973, IS-IS Mesh Groups
•
RFC 3277, IS-IS Transient Blackhole Avoidance
•
RFC 3358, Optional Checksums in ISIS
•
RFC 3373, Three-Way Handshake for IS-IS Point-to-Point Adjacencies
•
RFC 3567, Intermediate System to Intermediate System (IS-IS) Cryptographic Authentication
•
RFC 3719, Recommendations for Interoperable Networks using IS-IS
•
RFC 3786, Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit
•
RFC 3787, Recommendations for Interoperable IP Networks using IS-IS
•
RFC 3847, Restart Signaling for IS-IS
•
RFC 4444, Management Information Base for Intermediate System to Intermediate System
(IS-IS)
•
RFC 5303, Three-Way Handshake for IS-IS Point-to-Point Adjacencies
•
RFC 5310, IS-IS Generic Cryptographic Authentication
IS-IS configuration task list
Tasks at a glance
•
•
(Optional.) Setting the IS level and circuit level
•
(Optional.) Configuring P2P network type for an interface
141
Tasks at a glance
(Optional.) Configuring IS-IS route control :
•
•
Specifying a preference for IS-IS
•
Configuring the maximum number of ECMP routes
•
Configuring IS-IS route summarization
•
•
Configuring IS-IS route redistribution
•
Configuring IS-IS route filtering
•
Configuring IS-IS route leaking
•
Advertising IS-IS link state information to BGP
(Optional.) Tuning and optimizing IS-IS networks :
•
Specifying the interval for sending IS-IS hello packets
•
Specifying the IS-IS hello multiplier
•
Specifying the interval for sending IS-IS CSNP packets
•
Configuring a DIS priority for an interface
•
Disabling an interface from sending/receiving IS-IS packets
•
Enabling an interface to send small hello packets
•
•
Controlling SPF calculation interval
•
Configuring convergence priorities for specific routes
•
•
•
Configuring the tag value for an interface
•
Configuring system ID to host name mappings
•
Enabling the logging of neighbor state changes
•
•
•
Configuring IS-IS network management
•
(Optional.) Enhancing IS-IS network security :
•
Configuring neighbor relationship authentication
•
Configuring area authentication
•
Configuring routing domain authentication
(Optional.) Configuring IS-IS GR
(Optional.) Configuring IS-IS NSR
(Optional.) Configuring BFD for IS-IS
(Optional.) Configuring IS-IS FRR
Configuring basic IS-IS
Configuration prerequisites
Before the configuration, complete the following tasks:
•
Configure the link layer protocol.
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
142
Enabling IS-IS
Step
1. Enter system view.
2. Enable IS-IS and enter IS-IS view.
3. Assign a NET.
4. Return to system view.
5. Enter interface view.
6. Enable IS-IS on the interface.
Command system-view isis [ process-id ]
[ vpn-instance vpn-instance-name ] network-entity net quit interface interface-type interface-number isis enable [ process-id ]
Remarks
N/A
By default, IS-IS is disabled.
By default, NET is not assigned.
N/A
N/A
By default, IS-IS is disabled.
Setting the IS level and circuit level
Follow these guidelines when you configure the IS level for routers in only one area:
•
Set the IS level of all routers to Level-1 or Level-2 rather than different levels because the routers do not need to maintain two identical LSDBs.
•
Set the IS level to Level-2 on all routers in an IP network for good scalability.
For an interface of a Level-1 or Level-2 router, the circuit level can only be Level-1 or Level-2. For an interface of a Level-1-2 router, the default circuit level is Level-1-2. If the router only needs to form
Level-1 or Level-2 neighbor relationships, set the circuit level for its interfaces to Level-1 or Level-2.
This will limit neighbor relationship establishment.
To configure the IS level and circuit level:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Specify the IS level.
4. Return to system view.
5. Enter interface view.
6. Specify the circuit level.
Command system-view
Remarks
N/A isis [ process-id ] [ vpn-instance vpn-instance-name ] is-level { level-1 | level-1-2 | level-2 }
N/A
By default, the IS level is Level-1-2. quit interface interface-type
interface-number
N/A
N/A isis circuit-level [ level-1 | level-1-2 | level-2 ]
By default, an interface can establish either the Level-1 or
Level-2 adjacency.
Configuring P2P network type for an interface
Perform this task only for a broadcast network that has up to two attached routers.
Interfaces with different network types operate differently. For example, broadcast interfaces on a network must elect the DIS and flood CSNP packets to synchronize the LSDBs. However, P2P interfaces on a network do not need to elect the DIS, and have a different LSDB synchronization mechanism.
143
If only two routers exist on a broadcast network, set the network type of attached interfaces to P2P.
This avoids DIS election and CSNP flooding, saving network bandwidth and speeding up network convergence.
To configure P2P network type for an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Configure P2P network type for an interface. isis circuit-type p2p
By default, the network type of an interface varies by physical media. The network type of a
VLAN interface is broadcast.
Configuring IS-IS route control
Configuration prerequisites
Before the configuration, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable IS-IS.
Configuring IS-IS link cost
The IS-IS cost of an interface is determined in the following order:
1. IS-IS cost specified in interface view.
2. IS-IS cost specified in system view.
The cost is applied to the interfaces associated with the IS-IS process.
3. Automatically calculated cost.
If the cost style is wide or wide-compatible , IS-IS automatically calculates the cost using the formula: Interface cost = (Bandwidth reference value / Expected interface bandwidth) × 10, in
the range of 1 to 16777214. For other cost styles, Table 13 applies.
Configure the expected bandwidth of an interface with the bandwidth command. For more information, see Interface Command Reference .
Table 13 Automatic cost calculation scheme for cost styles other than wide and wide-compatible
Interface bandwidth
≤ 10 Mbps
≤ 100 Mbps
≤ 155 Mbps
≤ 622 Mbps
≤ 2500 Mbps
Interface cost
60
50
40
30
20
> 2500 Mbps 10
4. If none of the above costs is used, a default cost of 10 applies.
144
Configuring an IS-IS cost for an interface
Step
1. Enter system view.
2. Enter IS-IS view.
3. (Optional.) Specify an
IS-IS cost style.
4. Return to system view.
5. Enter interface view.
6. Specify a cost for the
IS-IS interface.
Configuring a global IS-IS cost
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] } quit interface interface-type interface-number isis cost cost-value [ level-1 | level-2 ]
Remarks
N/A
N/A
By default, the IS-IS cost type is narrow .
N/A
N/A
By default, no cost for the interface is specified.
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. (Optional.) Specify an
IS-IS cost style. cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] }
4. Specify a global IS-IS cost. circuit-cost cost-value [ level-1 | level-2 ]
Enabling automatic IS-IS cost calculation
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Enable automatic IS-IS cost calculation.
4. (Optional.) Configure a bandwidth reference value for automatic IS-IS cost calculation. auto-cost enable bandwidth-reference value
Remarks
N/A
N/A
By default, the IS-IS cost type is narrow .
By default, no global cost is specified.
Remarks
N/A
N/A
By default, automatic IS-IS cost calculation is disabled.
The default setting is 100
Mbps.
Specifying a preference for IS-IS
If multiple routing protocols find routes to the same destination, the route found by the routing protocol that has the highest preference is selected as the optimal route.
Perform this task to assign a preference to IS-IS directly or by using a routing policy. For more
information about the routing policy, see " Configuring routing policies ."
To configure a preference for IS-IS:
145
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
Command system-view a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ] preference { preference | route-policy route-policy-name } *
Remarks
N/A
N/A
The default setting is 15.
3. Configure a preference for
IS-IS.
Configuring the maximum number of ECMP routes
Perform this task to implement load sharing over ECMP routes.
To configure the maximum number of ECMP routes:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
Command system-view a isis [ process-id ] [ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4 [ unicast ]
Remarks
N/A
N/A
3. Specify the maximum number of ECMP routes.
maximum load-balancing number
By default, the maximum number of ECMP routes supported by IS-IS equals the maximum number of
ECMP routes supported by the system.
Configuring IS-IS route summarization
Perform this task to summarize specific routes, including IS-IS routes and redistributed routes, into a single route. Route summarization can reduce the routing table size and the LSDB scale.
Route summarization applies only to locally generated LSPs. The cost of the summary route is the lowest one among the costs of the more-specific routes.
To configure route summarization:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
Command system-view a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ]
Remarks
N/A
N/A
146
Step
3. Configure IS-IS route summarization.
Command summary ip-address { mask-length
| mask } [ avoid-feedback | generate_null0_route | [ level-1 | level-1-2 | level-2 ] | tag tag ] *
Remarks
By default, route summarization is not configured.
Advertising a default route
IS-IS cannot redistribute a default route to its neighbors. This task enables IS-IS to advertise a default route of 0.0.0.0/0 in an LSP to the same-level neighbors. Upon receiving the default route, the neighbors add it into their routing table.
To advertise a default route:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
3. Advertise a Level-1 or
Level-2 default route.
Command system-view a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ]
Remarks
N/A
N/A default-route-advertise [ [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name ] *
By default, IS-IS does not advertise a Level-1 or Level-2 default route.
Configuring IS-IS route redistribution
Perform this task to redistribute routes from other routing protocols into IS-IS. You can specify a cost for redistributed routes and specify the maximum number of redistributed routes.
To configure IS-IS route redistribution from other routing protocols:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
Command system-view a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ]
Remarks
N/A
N/A
147
Step
3. Redistribute routes from other routing protocols or other IS-IS processes.
Command import-route protocol [ as-number ]
[ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
4. (Optional.) Configure the maximum number of redistributed Level 1/Level 2
IPv4 routes.
import-route limit number
Remarks
By default, no route is redistributed.
By default, if no level is specified, this command redistributes routes into the
Level-2 routing table.
This command redistributes only active routes. To display active routes, use the display ip routing-table protocol command.
By default, the maximum number of redistributed Level
1/Level 2 IPv4 routes is not configured.
Configuring IS-IS route filtering
You can use an ACL, IP prefix list, or routing policy to filter routes calculated using received LSPs and routes redistributed from other routing protocols.
Filtering routes calculated from received LSPs
IS-IS saves LSPs received from neighbors in the LSDB, and uses the SPF algorithm to calculate the shortest path tree with itself as the root. IS-IS installs the calculated routes to the IS-IS routing table and the optimal routes to the IP routing table.
Perform this task to filter calculated routes. Only routes that are not filtered can be added to the IP routing table. The filtered routes retain in the IS-IS routing table and can be advertised to neighbors.
To filter routes calculated using received LSPs:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
Command system-view a isis [ process-id ] [ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4 [ unicast ]
Remarks
N/A
N/A
3. Filter routes calculated using received LSPs. filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } import
By default, IS-IS route filtering is not configured.
Filtering redistributed routes
IS-IS can redistribute routes from other routing protocols or other IS-IS processes, add them to the
IS-IS routing table, and advertise them in LSPs.
Perform this task to filter redistributed routes. Only routes that are not filtered can be added to the
IS-IS routing table and advertised to neighbors.
To filter redistributed routes:
Step
1. Enter system view.
Command system-view
Remarks
N/A
148
Step
2. Enter IS-IS IPv4 unicast address family view.
3. Filter routes redistributed from other routing protocols or IS-IS processes.
Command a isis [ process-id ] [ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4 [ unicast ] filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } export [ protocol [ process-id ] ]
Remarks
N/A
By default, IS-IS route filtering is not configured.
Configuring IS-IS route leaking
Perform this task to control route advertisement (route leaking) between Level-1 and Level-2.
You can configure IS-IS to advertise routes from Level-2 to Level-1, and to not advertise routes from
Level-1 to Level-2.
To configure IS-IS route leaking:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
3. Configure route leaking from
Level-1 to Level-2.
4. Configure route leaking from
Level-2 to Level-1.
Command system-view
Remarks
N/A a isis [ process-id ] [ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4 [ unicast ]
N/A import-route isis level-1 into level-2
[ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
By default, IS-IS advertises routes from Level-1 to
Level-2. import-route isis level-2 into level-1
[ filter-policy { ipv4-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
By default, IS-IS does not advertise routes from
Level-2 to Level-1.
Advertising IS-IS link state information to BGP
After the device advertises IS-IS link state information to BGP, BGP can advertise the information for
intended applications. For more information about BGP LS, see " Configuring BGP ."
To advertise IS-IS link state information to BGP:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Advertise IS-IS link state information to BGP.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A distribute bgp-ls [ instance-id id ]
[ level-1 | level-2 ]
By default, the device does not advertise IS-IS link state information to BGP.
149
Tuning and optimizing IS-IS networks
Configuration prerequisites
Before you tune and optimize IS-IS networks, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable IS-IS.
Specifying the interval for sending IS-IS hello packets
If a neighbor does not receive any hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
To specify the interval for sending hello packets:
Step
1. Enter system view.
2. Enter interface view.
3. Specify the interval for sending hello packets.
Command system-view
Remarks
N/A interface interface-type interface-number
N/A
isis timer hello seconds [ level-1
| level-2 ]
The default setting is 10 seconds.
The interval between hello packets sent by the DIS is 1/3 the hello interval set with the isis timer hello command.
Specifying the IS-IS hello multiplier
The hello multiplier is the number of hello packets a neighbor must miss before it declares that the router is down.
If a neighbor receives no hello packets from the router within the advertised hold time, it considers the router down and recalculates the routes. The hold time is the hello multiplier multiplied by the hello interval.
On a broadcast link, Level-1 and Level-2 hello packets are advertised separately. You must set a hello multiplier for each level.
On a P2P link, Level-1 and Level-2 hello packets are advertised in P2P hello packets. You do not need to specify Level-1 or Level-2.
To specify the IS-IS hello multiplier:
Step
1. Enter system view.
2. Enter interface view.
3. Specify the hello multiplier.
Command system-view interface interface-type interface-number isis timer holding-multiplier value
[ level-1 | level-2 ]
Remarks
N/A
N/A
The default setting is 3.
150
Specifying the interval for sending IS-IS CSNP packets
On a broadcast network, perform this task on the DIS that uses CSNP packets to synchronize
LSDBs.
To specify the interval for sending IS-IS CSNP packets:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Specify the interval for sending CSNP packets on the DIS of a broadcast network.
isis timer csnp seconds [ level-1
| level-2 ]
The default setting is 10 seconds.
Configuring a DIS priority for an interface
On a broadcast network, IS-IS must elect a router as the DIS at a routing level. You can specify a DIS priority at a level for an interface. The greater the interface's priority, the more likely it becomes the
DIS. If multiple routers in the broadcast network have the same highest DIS priority, the router with the highest MAC address becomes the DIS.
To configure a DIS priority for an interface:
Step
1. Enter system view.
2. Enter interface view.
3. Configure a DIS priority for the interface.
Command system-view
Remarks
N/A interface interface-type interface-number
N/A
isis dis-priority priority [ level-1 | level-2 ]
The default setting is 64.
Disabling an interface from sending/receiving IS-IS packets
After being disabled from sending and receiving hello packets, an interface cannot form any neighbor relationship, but can advertise directly connected networks in LSPs through other interfaces. This can save bandwidth and CPU resources, and ensures that other routers know networks directly connected to the interface.
To disable an interface from sending and receiving IS-IS packets:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Disable the interface from sending and receiving IS-IS packets. isis silent
By default, the interface can send and receive IS-IS packets.
151
Enabling an interface to send small hello packets
IS-IS messages cannot be fragmented at the IP layer because they are directly encapsulated in frames. Any two IS-IS neighboring routers must negotiate a common MTU. To avoid sending big hellos to save bandwidth, enable the interface to send small hello packets without CLVs.
To enable an interface to send small hello packets:
Remarks
N/A
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
3. Enable the interface to send small hello packets without
CLVs. isis small-hello
N/A
By default, the interface can send standard hello packets.
Configuring LSP parameters
Configuring LSP timers
1. Specify the maximum age of LSPs.
Each LSP has an age that decreases in the LSDB. Any LSP with an age of 0 is deleted from the
LSDB. You can adjust the age value based on the scale of a network.
To specify the maximum age of LSPs:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter IS-IS view. isis [ process-id ]
[ vpn-instance vpn-instance-name ]
N/A
3. Specify the maximum LSP age.
timer lsp-max-age seconds
The default setting is 1200 seconds.
2. Specify the LSP refresh interval and generation interval.
Each router needs to refresh its LSPs at a configurable interval and send them to other routers to prevent valid routes from aging out. A smaller refresh interval speeds up network convergence but consumes more bandwidth.
When network topology changes such as neighbor state, interface metric, system ID, or area ID changes occur, the router generates an LSP after a configurable interval. If such a change occurs frequently, excessive LSPs are generated, consuming a large amount of router resources and bandwidth. To solve the problem, you can adjust the LSP generation interval.
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the LSP generation interval increases by incremental-interval × 2 n-2
(n is the number of calculation times) each time a generation occurs until the maximum-interval is reached.
To specify the LSP refresh interval and generation interval:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
152
Step
3. Specify the LSP refresh interval.
Command
timer lsp-refresh seconds
Remarks
By default, the LSP refresh interval is 900 seconds.
4. Specify the LSP generation interval. timer lsp-generation maximum-interval
[ minimum-interval
[ incremental-interval ] ] [ level-1 |
level-2 ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is 50 milliseconds.
•
The incremental interval is 200 milliseconds.
3. Specify LSP sending intervals.
If a change occurs in the LSDB, IS-IS advertises the changed LSP to neighbors. You can specify the minimum interval for sending these LSPs to control the amount of LSPs on the network.
On a P2P link, IS-IS requires an advertised LSP be acknowledged. If no acknowledgment is received within a configurable interval, IS-IS will retransmit the LSP.
To configure LSP sending intervals:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter interface view. interface interface-type interface-number
3. Specify the minimum interval for sending LSPs and the maximum LSP number that can be sent at a time.
isis timer lsp time [ count count ]
N/A
By default, the minimum interval is 33 milliseconds, and the maximum LSP number that can be sent at a time is 5.
4. Specify the LSP retransmission interval on a P2P link.
Specifying LSP lengths
isis timer retransmit seconds
By default, the LSP retransmission interval on a
P2P link is 5 seconds.
IS-IS messages cannot be fragmented at the IP layer because they are directly encapsulated in frames. IS-IS routers in an area must send LSPs smaller than the smallest interface MTU in the area.
If the IS-IS routers have different interface MTUs, configure the maximum size of generated LSP packets to be smaller than the smallest interface MTU in the area. Without the configuration, the routers must dynamically adjust the LSP packet size to fit the smallest interface MTU, which takes time and affects other services.
To specify LSP lengths:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Specify the maximum length of generated Level-1 LSPs or
Level-2 LSPs.
lsp-length originate size [ level-1 | level-2 ]
By default, the maximum length of generated Level-1
LSPs or Level-2 LSPs is 1497 bytes.
153
Step
4. Specify the maximum length of received LSPs.
Command
lsp-length receive size
Remarks
By default, the maximum length of received LSPs is
1497 bytes.
Enabling LSP flash flooding
Changed LSPs can trigger SPF recalculation. To advertise the changed LSPs before the router recalculates routes for faster network convergence, enable LSP flash flooding.
To enable LSP flash flooding:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
N/A
3. Enable LSP flash flooding. flash-flood [ flood-count flooding-count
| max-timer-interval flooding-interval |
[ level-1 | level-2 ] ] *
By default, LSP flash flooding is disabled.
Enabling LSP fragment extension
Perform this task to enable IS-IS fragment extension for an IS-IS process. The MTUs of all interfaces running the IS-IS process must not be less than 512. Otherwise, LSP fragment extension does not take effect.
To enable LSP fragment extension:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Enable LSP fragment extension.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] lsp-fragments-extend [ level-1 | level-1-2 | level-2 ]
Remarks
N/A
N/A
By default, this feature is disabled.
4. Configure a virtual system ID. virtual-system virtual-system-id
By default, no virtual system ID is configured.
Configure a minimum of one virtual system to generate extended LSP fragments.
Limiting LSP flooding
In some networks, many P2P links exist. As shown in Figure 41 , Routers A, B, C and D run IS-IS.
When Router A generates an LSP, it floods the LSP out of GigabitEthernet 1/0/1, GigabitEthernet
1/0/2, and GigabitEthernet 1/0/3. After Router D receives the LSP from GigabitEthernet 1/0/3, it floods it out of GigabitEthernet 1/0/2 and GigabitEthernet 1/0/1 to Router B and Router C. However,
Router B and Router C have already received the LSP from Router A. Repeated LSP flooding consumes extra bandwidth.
154
Figure 41 Network diagram of a fully meshed network
Router D Router A
GE1/0/1
GE1/0/2
GE1/0/3
GE1/0/3
GE1/0/2
GE1/0/1
GE1/0/1
GE1/0/2 GE1/0/2
GE1/0/1
GE1/0/3 GE1/0/3
Router B Router C
To avoid this problem, you can add interfaces to a mesh group or block some interfaces.
•
An interface in a mesh group floods a received LSP only to interfaces not in the mesh group.
•
A blocked interface sends LSPs only after receiving LSP requests.
Before you configure this task, you must consider redundancy for interfaces in case LSP packets cannot be flooded because of link failures.
To add an interface to a mesh group or block an interface:
Remarks
N/A
Step
1. Enter system view.
2. Enter interface view.
3. Add the interface to a mesh group or block the interface.
Command system-view interface interface-type interface-number
•
Add the interface to a mesh group: isis mesh-group mesh-group-number
•
Block the interface: isis mesh-group mesh-blocked
N/A
By default, the interface does not belong to any mesh group and is not blocked.
The mesh group feature takes effect only on P2P interfaces.
Controlling SPF calculation interval
Based on the LSDB, an IS-IS router uses the SPF algorithm to calculate the shortest path tree with itself being the root, and uses the shortest path tree to determine the next hop to a destination network. By adjusting the SPF calculation interval, you can prevent bandwidth and router resources from being over consumed due to frequent topology changes.
When network changes are not frequent, the minimum-interval is adopted. If network changes become frequent, the SPF calculation interval increases by incremental-interval × 2 n-2
(n is the number of calculation times) each time a calculation occurs until the maximum-interval is reached.
To control SPF calculation interval:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
155
Step
3. Configure the SPF calculation interval.
Command
timer spf maximum-interval
[ minimum-interval
[ incremental-interval ] ]
Remarks
By default:
•
The maximum interval is
5 seconds.
•
The minimum interval is
50 milliseconds.
•
The incremental interval is 200 milliseconds.
Configuring convergence priorities for specific routes
A topology change causes IS-IS routing convergence. To improve convergence speed, you can assign convergence priorities to IS-IS routes. Convergence priority levels are critical, high, medium, and low. The higher the convergence priority, the faster the convergence speed.
By default, IS-IS host routes have medium convergence priority, and other IS-IS routes have low convergence priority.
To assign convergence priorities to specific IS-IS routes:
Step
1. Enter system view.
2. Enter IS-IS IPv4 unicast address family view.
3. Assign convergence priorities to specific IS-IS routes.
Command system-view a isis [ process-id ] [ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4 [ unicast ]
•
Method 1: prefix-priority { critical | high | medium } { prefix-list prefix-list-name | tag tag-value }
•
Method 2
: prefix-priority route-policy route-policy-name
Remarks
N/A
N/A
By default, IS-IS routes, except IS-IS host routes, have the low convergence priority.
Setting the LSDB overload bit
By setting the overload bit in sent LSPs, a router informs other routers of failures that make it unable to select routes and forward packets.
When an IS-IS router cannot record the complete LSDB, for example, because of memory insufficiency, it will calculate wrong routes. To make troubleshooting easier, temporarily isolate the router from the IS-IS network by setting the overload bit.
To set the LSDB overload bit:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
156
Step
3. Set the overload bit.
Command set-overload [ on-startup
[ [ start-from-nbr system-id [ timeout1
[ nbr-timeout ] ] ] | timeout2 | wait-for-bgp [ timeout3 ] ] ] [ allow
{ external | interlevel } * ]
Remarks
By default, the overload bit is not set.
Configuring the ATT bit
A Level-1-2 router sends Level-1 LSPs with an ATT bit to inform the Level-1 routers that it can reach other areas.
Configuring IS-IS not to calculate the default route through the ATT bit
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
3. Configure IS-IS not to calculate the default route through the ATT bit.
Setting the ATT bit of Level-1 LSPs ignore-att
N/A
By default, IS-IS uses the ATT bit to calculate the default route.
Step
1. Enter system view.
2. Enter IS-IS view
3. Set the ATT bit of Level-1
LSPs.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] set-att { always | never }
Remarks
N/A
N/A
By default, the ATT bit is not set for Level-1 LSPs.
Configuring the tag value for an interface
Perform this task when the link cost style is wide , wide-compatible , or compatible .
When IS-IS advertises a prefix with a tag value, IS-IS adds the tag to the IP reachability information
TLV of the prefix.
To configure the tag value for an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Configure the tag value for the interface.
isis tag tag
By default, the tag value of the interface is not configured.
157
Configuring system ID to host name mappings
A 6-byte system ID in hexadecimal notation uniquely identifies a router or host in an IS-IS network.
To make a system ID easy to read, the system allows you to use host names to identify devices. It also provides mappings between system IDs and host names.
The mappings can be configured manually or dynamically. Follow these guidelines when you configure the mappings:
•
To view host names rather than system IDs by using the display isis lsdb command, you must enable dynamic system ID to host name mapping.
•
If you configure both dynamic mapping and static mapping on a router, the host name specified for dynamic mapping applies.
Configuring a static system ID to host name mapping
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Configure a system ID to host name mapping for a remote IS. is-name map sys-id map-sys-name
By default, no system ID to host name mapping is configured for a remote IS.
A system ID can correspond to only one host name.
Configuring dynamic system ID to host name mapping
Static system ID to host name mapping requires you to manually configure a mapping for each router in the network. When a new router is added to the network or a mapping must be modified, you must configure all routers manually.
When you use dynamic system ID to host name mapping, you only need to configure a host name for each router in the network. Each router advertises the host name in a dynamic host name CLV to other routers so all routers in the network can have all mappings.
To help check the origin of LSPs in the LSDB, you can configure a name for the DIS in a broadcast network.
To configure dynamic system ID to host name mapping:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Specify a host name for the
IS and enable dynamic system ID to host name mapping.
4. Return to system view.
is-name sys-name
5. Enter interface view. quit interface interface-type interface-number
Remarks
N/A
N/A
By default, no host name is specified for the router.
N/A
N/A
158
Step
6. Configure a DIS name.
Command
isis dis-name symbolic-name
Remarks
By default, no DIS name is configured.
This command takes effect only on a router enabled with dynamic system ID to host name mapping.
This command is not available on
P2P interfaces.
Enabling the logging of neighbor state changes
With this feature enabled, the router delivers logs about neighbor state changes to its information center. The information center processes the logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see Network
Management and Monitoring Configuration Guide .
To enable the logging of neighbor state changes:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable the logging of neighbor state changes. log-peer-change
By default, the logging of neighbor state changes is enabled.
Enabling IS-IS ISPF
When the network topology changes, Incremental Shortest Path First (ISPF) computes only the affected part of the SPT, instead of the entire SPT.
To enable IS-IS ISPF:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Enable IS-IS ISPF.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] ispf enable
Remarks
N/A
N/A
By default, IS-IS is disabled.
Enabling prefix suppression
Perform this task to disable an interface from advertising its prefix in LSPs. This enhances network security by preventing IP routing to the interval nodes and speeds up network convergence.
To enable prefix suppression:
Step
1. Enter system view.
Command system-view
Remarks
N/A
159
Step
2. Enter interface view.
Command interface interface-type interface-number
3. Enable prefix suppression on the interface. isis prefix-suppression
Remarks
N/A
By default, prefix suppression is disabled on the interface.
This command is also applicable to the secondary IP address of the interface.
Configuring IS-IS network management
This task includes the following configurations:
•
Bind an IS-IS process to MIB so that you can use network management software to manage the specified IS-IS process.
•
Enable IS-IS notifications to report important events.
Notifications are delivered to the SNMP module, which outputs the notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide .
TRILL uses the IS-IS MIB to provide the TRILL object management function for NMS. Because the
MIB objects defined in the IS-IS MIB are single-instance management objects, NMS cannot manage
IS-IS and TRILL at the same time. According to the management for multiple OSPF instances defined in RFC 4750, you can set a context name for the SNMP object for managing TRILL. In this way, the SNMP requests for managing IS-IS and the SNMP requests for managing TRILL from NMS can be distinguished. Because the context name is a concept specific to SNMPv3, the community names are mapped to context names for distinguishing different protocols in SNMPv1/v2c.
To configure IS-IS network management:
Step
1. Enter system view.
2. Bind MIB to an IS-IS process.
3. Enable IS-IS notification sending.
4. Enter IS-IS view.
Command system-view
Remarks
N/A
isis mib-binding process-id
By default, MIB is bound to the
IS-IS process with the smallest process ID. snmp-agent trap enable isis
[ adjacency-state-change | area-mismatch | authentication | authentication-type | buffsize-mismatch | id-length-mismatch | lsdboverload-state-change | lsp-corrupt | lsp-parse-error | lsp-size-exceeded | manual-address-drop | max-seq-exceeded | maxarea-mismatch | own-lsp-purge | protocol-support | rejected-adjacency | skip-sequence-number | version-skew ] *
By default, IS-IS notification sending is enabled. isis [ process-id ] [ vpn-instance vpn-instance-name ]
N/A
160
Step
5. Configure the context name for the SNMP object for managing IS-IS.
Command snmp context-name context-name
Remarks
By default, no context name is set for the SNMP object for managing IS-IS.
Configuring IS-IS PIC
Prefix Independent Convergence (PIC) enables the device to speed up network convergence by ignoring the number of prefixes.
When both IS-IS PIC and IS-IS FRR are configured, IS-IS FRR takes effect.
IS-IS PIC applies only to LSPs sent by neighbors.
Enabling IS-IS PIC
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable PIC for IS-IS. pic [ additional-path-always ]
By default, IS-IS PIC is enabled.
Enabling BFD for IS-IS PIC
By default, IS-IS PIC does not use BFD to detect primary link failures. To speed up IS-IS convergence, enable BFD for IS-IS PIC to detect primary link failures.
To enable BFD control packet mode for IS-IS PIC:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type interface-number
3. Enable BFD control packet mode for IS-IS PIC. isis primary-path-detect bfd ctrl
To configure BFD echo packet mode for IS-IS PIC:
Step
1. Enter system view.
Command system-view
N/A
By default, BFD control packet mode is disabled for IS-IS PIC.
2. Configure the source IP address of BFD echo packets.
bfd echo-source-ip ip-address
Remarks
N/A
By default, the source IP address of BFD echo packets is not configured.
The source IP address cannot be on the same network segment as any local interface's
IP address.
For more information, see High
Availability Command
Reference .
3. Enter interface view. interface interface-type interface-number
N/A
161
Step
4. Enable BFD echo packet mode for IS-IS PIC.
Command isis primary-path-detect bfd echo
Remarks
By default, BFD echo packet mode is disabled for IS-IS PIC.
Enhancing IS-IS network security
To enhance the security of an IS-IS network, you can configure IS-IS authentication. IS-IS authentication involves neighbor relationship authentication, area authentication, and routing domain authentication.
Configuration prerequisites
Before the configuration, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable IS-IS.
Configuring neighbor relationship authentication
With neighbor relationship authentication configured, an interface adds the key in the specified mode into hello packets to the peer and checks the key in the received hello packets. If the authentication succeeds, it forms the neighbor relationship with the peer.
The authentication mode and key at both ends must be identical.
To prevent packet exchange failure in case of an authentication key change, configure the interface not to check the authentication information in the received packets.
To configure neighbor relationship authentication:
Step
1. Enter system view.
2. Enter interface view.
3. Specify the authentication mode and key.
4. (Optional.) Configure the interface not to check the authentication information in the received hello packets.
Command system-view
Remarks
N/A interface interface-type interface-number
N/A isis authentication-mode { { gca key-id
{ hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string | keychain keychain-name } [ level-1 | level-2 ] [ ip | osi ]
By default, no authentication is configured. isis authentication send-only [ level-1
| level-2 ]
When the authentication mode and key are configured, the interface checks the authentication information in the received packets by default.
Configuring area authentication
Area authentication prevents the router from installing routing information from untrusted routers into the Level-1 LSDB. The router encapsulates the authentication key in the specified mode in Level-1 packets (LSP, CSNP, and PSNP). It also checks the key in received Level-1 packets.
162
Routers in a common area must have the same authentication mode and key.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
To configure area authentication:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
N/A
3. Specify the area authentication mode and key. area-authentication-mode { { gca key-id { hmac-sha-1 | hmac-sha-224
| hmac-sha-256 | hmac-sha-384 | hmac-sha-512 } [ nonstandard ] | md5 | simple } { cipher | plain } string
| keychain keychain-name } [ ip | osi ]
By default, no area authentication is configured.
4. (Optional.) Configure the interface not to check the authentication information in the received Level-1 packets, including LSPs,
CSNPs, and PSNPs. area-authentication send-only
When the authentication mode and key are configured, the interface checks the authentication information in the received packets by default.
Configuring routing domain authentication
Routing domain authentication prevents untrusted routing information from entering into a routing domain. A router with the authentication configured encapsulates the key in the specified mode into
Level-2 packets (LSP, CSNP, and PSNP) and check the key in received Level-2 packets.
All the routers in the backbone must have the same authentication mode and key.
To prevent packet exchange failure in case of an authentication key change, configure IS-IS not to check the authentication information in the received packets.
To configure routing domain authentication:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Specify the routing domain authentication mode and key.
Command system-view
Remarks
N/A isis [ process-id ] [ vpn-instance vpn-instance-name ]
N/A domain-authentication-mode
{ { gca key-id { hmac-sha-1 | hmac-sha-224 | hmac-sha-256 | hmac-sha-384 | hmac-sha-512 }
[ nonstandard ] | md5 | simple }
{ cipher | plain } string | keychain keychain-name } [ ip | osi ]
By default, no routing domain authentication is configured.
4. (Optional.) Configure the interface not to check the authentication information in the received Level-2 packets, including LSPs,
CSNPs, and PSNPs. domain-authentication send-only
When the authentication mode and key are configured, the interface checks the authentication information in the received packets by default.
163
Configuring IS-IS GR
GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Two routers are required to complete a GR process. The following are router roles in a GR process.
•
GR restarter —Graceful restarting router. It must have GR capability.
•
GR helper —A neighbor of the GR restarter. It assists the GR restarter to complete the GR process. By default, the device acts as the GR helper.
Configure IS-IS GR on the GR restarter.
GR restarter uses the following timers:
•
T1 timer —Specifies the times that GR restarter can send a Restart TLV with the RR bit set.
When rebooted, the GR restarter sends a Restart TLV with the RR bit set to its neighbor. If the
GR restarter receives a Restart TLV with the RA set from its neighbor before the T1 timer expires, the GR process starts. Otherwise, the GR process fails.
•
T2 timer —Specifies the LSDB synchronization interval. Each LSDB has a T2 timer. The
Level-1-2 router has a Level-1 timer and a Level-2 timer. If the LSDBs have not synchronized before the two timers expire, the GR process fails.
•
T3 timer —Specifies the GR interval. The GR interval is set as the holdtime in hello PDUs.
Within the interval, the neighbors maintain their adjacency with the GR restarter. If the GR process has not completed within the holdtime, the neighbors tear down the neighbor relationship and the GR process fails.
IMPORTANT:
IS-IS GR and IS-IS NSR are mutually exclusive. Do not configure them at the same time.
To configure GR on the GR restarter:
Step
1. Enter system view.
Command system-view
2. Enable IS-IS and enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable IS-IS GR. graceful-restart
4. (Optional.) Suppress the SA bit during restart. graceful-restart suppress-sa
5. (Optional.) Configure the T1 timer. graceful-restart t1 seconds count
count
6. (Optional.) Configure the T2 timer. graceful-restart t2 seconds
7. (Optional.) Configure the T3 timer.
graceful-restart t3 seconds
By default, the GR capability for
IS-IS is disabled.
By default, the SA bit is not suppressed.
By enabling the GR restarter to suppress the
Suppress-Advertisement (SA) bit in the hello PDUs, the neighbors will still advertise their adjacency with the GR restarter.
By default, the T1 timer is 3 seconds and can expire 10 times.
By default, the T2 timer is 60 seconds.
By default, the T2 timer is 300 seconds.
164
Configuring IS-IS NSR
After an active/standby switchover, the GR restarter obtains routing information from its neighbors, and the IS-IS process must learn all the routes. If the network topology changes during the switchover, removed routes cannot be updated to the device, which can result in blackhole routes.
NSR solves the problem by backing up IS-IS link state information from the active process to the standby process. After an active/standby switchover, NSR can complete link state recovery and route regeneration without requiring the cooperation of other devices.
IMPORTANT:
IS-IS NSR and IS-IS GR are mutually exclusive. Do not configure them at the same time.
To configure IS-IS NSR:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ]
[ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable IS-IS NSR. non-stop-routing
By default, IS-IS NSR is disabled.
IS-IS NSR takes effect on a per-process basis. As a best practice, enable NSR for each IS-IS process.
Configuring BFD for IS-IS
BFD provides a single mechanism to quickly detect and monitor the connectivity of links between
IS-IS neighbors, reducing network convergence time. For more information about BFD, see High
Availability Configuration Guide .
To configure BFD for IS-IS:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type interface-number
3. Enable IS-IS on an interface. isis enable [ process-id ]
4. Enable BFD on an IS-IS interface. isis bfd enable
N/A
N/A
By default, an IS-IS interface is not enabled with BFD.
Configuring IS-IS FRR
A link or router failure on a path can cause packet loss and routing loop. IS-IS FRR enables fast rerouting to minimize the failover time.
165
Figure 42 Network diagram for IS-IS FRR
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
In Figure 42 , after you enable FRR on Router B, IS-IS automatically calculates or designates a
backup next hop when a link failure is detected. In this way, packets are directed to the backup next hop to reduce traffic recovery time. Meanwhile, IS-IS calculates the shortest path based on the new network topology, and forwards packets over the path after network convergence.
You can assign a backup next hop for IS-IS FRR through the following ways:
•
Enable IS-IS FRR to calculate a backup next hop through Loop Free Alternate (LFA) calculation.
•
Designate a backup next hop with a routing policy for routes matching specific criteria.
Configuration prerequisites
Before you configure IS-IS FRR, complete the following tasks:
•
Configure IP addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable IS-IS.
Configuration guidelines
The LFA calculation of FRR and that of TE are mutually exclusive.
Configuration procedure
Configuring IS-IS FRR to calculate a backup next hop through LFA calculation
Step
1. Enter system view.
2. Enter interface view.
4. Return to system view.
5. Enter IS-IS IPv4 unicast address family view.
Command system-view interface interface-type interface-number
3. (Optional.) Disable LFA calculation on the interface. isis fast-reroute lfa-backup exclude quit a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ]
Remarks
N/A
N/A
By default, the interface participates in LFA calculation, and can be elected as a backup interface.
N/A
N/A
166
Step
6. Enable IS-IS FRR to calculate a backup next hop through LFA calculation.
Command fast-reroute lfa
Configuring IS-IS FRR using a routing policy
Remarks
By default, IS-IS FRR is disabled.
You can use the apply fast-reroute backup-interface command to specify a backup next hop in a routing policy for routes matching specific criteria. You can also perform this task to reference the routing policy for IS-IS FRR. For more information about the apply fast-reroute backup-interface
command and routing policy configurations, see " Configuring routing policies ."
To configure IS-IS FRR using a routing policy:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. (Optional.) Disable LFA calculation on the interface. isis fast-reroute lfa-backup exclude
By default, the interface participates in LFA calculation, and can be elected as a backup interface.
4. Return to system view.
5. Enter IS-IS IPv4 unicast address family view. quit a isis [ process-id ]
[ vpn-instance vpn-instance-name ] b cost-style { wide | wide-compatible } c address-family ipv4
[ unicast ]
N/A
N/A
6. Enable IS-IS FRR using a routing policy.
Enabling BFD for IS-IS FRR fast-reroute route-policy route-policy-name
By default, this feature is not enabled.
By default, IS-IS FRR does not use BFD to detect primary link failures. To speed up IS-IS convergence, enable BFD for IS-IS FRR to detect primary link failures.
To enable BFD control packet mode for IS-IS FRR:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter interface view.
interface interface-type interface-number
3. Enable BFD control packet mode for IS-IS FRR. isis primary-path-detect bfd ctrl
To enable BFD echo packet mode for IS-IS FRR:
Step
1. Enter system view.
Command system-view
N/A
By default, BFD control packet mode is disabled for IS-IS FRR.
Remarks
N/A
167
Step Command
2. Configure the source IP address of BFD echo packets.
bfd echo-source-ip ip-address
Remarks
By default, the source IP address of BFD echo packets is not configured.
The source IP address cannot be on the same network segment as any local interface's IP address.
For more information, see High
Availability Command Reference .
3. Enter interface view.
4. Enable BFD echo packet mode for IS-IS FRR. interface interface-type interface-number isis primary-path-detect bfd echo
N/A
By default, BFD echo packet mode is disabled for IS-IS FRR.
Displaying and maintaining IS-IS
Execute display commands in any view and the reset command in user view.
Task
Display IS-IS process information.
Command display isis [ process-id ]
(In standalone mode.) Display IS-IS
GR log information.
(In IRF mode.) Display IS-IS GR log information.
Display the IS-IS GR status. display isis graceful-restart event-log slot slot-number display isis graceful-restart event-log chassis slot slot-number chassis-number display isis graceful-restart status [ level-1 | level-2 ] [ process-id ]
Display IS-IS interface information.
Display IS-IS LSDB information.
Display IS-IS LSDB statistics. display isis interface [ [ i nterface-type interface-number ]
[ verbose ] | statistics ] [ process-id ] display isis lsdb [ [ level-1 | level-2 ] | local | lsp-id lspid |
[ lsp-name lspname ] | verbose ] * [ process-id ] display isis lsdb statistics [ level-1 | level-2 ] [ process-id ]
Display IS-IS mesh group information.
Display the host name to system ID mapping table. display isis mesh-group display isis name-table [
[ process-id process-id ]
]
(In standalone mode.) Display IS-IS
NSR log information. display isis non-stop-routing event-log slot slot-number
(In IRF mode.) Display IS-IS NSR log information. display isis non-stop-routing event-log chassis chassis-number slot slot-number
Display the IS-IS NSR status.
Display IS-IS packet statistics. display isis non-stop-routing status display isis packet { csnp | hello | lsp | psnp } [ verbose ]
[ interface-type interface-number ] [ process-id ]
Display IS-IS neighbor information. display isis peer [ statistics | verbose ] [ process-id ]
Display IS-IS redistributed route information.
Display IS-IS IPv4 routing information.
| display isis redistribute
level-2 ] [ process-id ]
[ ipv4 [ ip-address mask-length ] ] [ level-1 display isis route [ ipv4 [ ip-address mask-length ] ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
168
Task
Display IS-IS IPv4 topology information.
Display IS-IS statistics.
Command display isis spf-tree [ ipv4 ] [ [ level-1 | level-2 ] | verbose ] *
[ process-id ] display isis statistics [ ipv4 ] [ level-1 | level-1-2 | level-2 ]
[ process-id ]
(In standalone mode.) Display OSI connection information.
(In IRF mode.) Display OSI connection information.
(In standalone mode.) Display OSI connection statistics.
(In IRF mode.) Display OSI connection statistics.
Clear IS-IS process data structure information.
(In standalone mode.) Clear IS-IS
GR log information.
(In IRF mode.) Clear IS-IS GR log information.
(In standalone mode.) Clear IS-IS
NSR log information.
(In IRF mode.) Clear IS-IS NSR log information.
Clear IS-IS LSP log information. display osi display osi
[
[ chassis chassis-number display osi statistics display osi statistics reset isis all [ slot slot-number
[
[ slot slot-number
chassis chassis-number
process-id ] [
] slot slot-number ] graceful-restart reset isis graceful-restart event-log slot
] slot slot-number
slot-number reset isis graceful-restart event-log chassis
slot-number reset isis non-stop-routing event-log slot
] chassis-number
slot-number
] slot
Clear IS-IS packet statistics. reset isis non-stop-routing event-log chassis chassis-number slot slot-number reset isis event-log lsp [ process-id ] reset isis packet [ csnp | hello | lsp | psnp ] by-interface
[ interface-type interface-number ] [ process-id ]
Clear the data structure information of an IS-IS neighbor.
Clear OSI connection statistics. reset isis peer system-id [ process-id ] reset osi statistics
IS-IS configuration examples
Basic IS-IS configuration example
Network requirements
As shown in Figure 43 , Switch A, Switch B, Switch C, and Switch D reside in an IS-IS AS.
Switch A and B are Level-1 switches, Switch D is a Level-2 switch, and Switch C is a Level-1-2 switch.
Switch A, Switch B, and Switch C are in Area 10, and Switch D is in Area 20.
169
Figure 43 Network diagram
Vlan-int100
10.1.1.2/24
Switch A
L1
Vlan-int100
10.1.1.1/24
Vlan-int200
10.1.2.1/24
Vlan-int300
192.168.0.1/24
Vlan-int300
192.168.0.2/24
Switch C
L1/L2
Switch D
L2
Vlan-int100
172.16.1.1/16
Vlan-int200
10.1.2.2/24
Area 20
Switch B
L1
Area 10
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] is-level level-1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis enable 1
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] is-level level-1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] isis enable 1
[SwitchB-Vlan-interface200] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] isis enable 1
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis enable 1
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 300
170
[SwitchC-Vlan-interface300] isis enable 1
[SwitchC-Vlan-interface300] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] isis 1
[SwitchD-isis-1] is-level level-2
[SwitchD-isis-1] network-entity 20.0000.0000.0004.00
[SwitchD-isis-1] quit
[SwitchD] interface vlan-interface 100
[SwitchD-Vlan-interface100] isis enable 1
[SwitchD-Vlan-interface100] quit
[SwitchD] interface vlan-interface 300
[SwitchD-Vlan-interface300] isis enable 1
[SwitchD-Vlan-interface300] quit
Verifying the configuration
# Display the IS-IS LSDB on each switch to verify the LSPs.
[SwitchA] display isis lsdb
Database information for IS-IS(1)
---------------------------------
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
0000.0000.0001.00-00* 0x00000004 0xdf5e 1096 68 0/0/0
0000.0000.0002.00-00 0x00000004 0xee4d 1102 68 0/0/0
0000.0000.0002.01-00 0x00000001 0xdaaf 1102 55 0/0/0
0000.0000.0003.00-00 0x00000009 0xcaa3 1161 111 1/0/0
0000.0000.0003.01-00 0x00000001 0xadda 1112 55 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
[SwitchB] display isis lsdb
Database information for IS-IS(1)
---------------------------------
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
0000.0000.0001.00-00 0x00000006 0xdb60 988 68 0/0/0
0000.0000.0002.00-00* 0x00000008 0xe651 1189 68 0/0/0
0000.0000.0002.01-00* 0x00000005 0xd2b3 1188 55 0/0/0
0000.0000.0003.00-00 0x00000014 0x194a 1190 111 1/0/0
0000.0000.0003.01-00 0x00000002 0xabdb 995 55 0/0/0
171
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
[SwitchC] display isis lsdb
Database information for IS-IS(1)
---------------------------------
Level-1 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
0000.0000.0001.00-00 0x00000006 0xdb60 847 68 0/0/0
0000.0000.0002.00-00 0x00000008 0xe651 1053 68 0/0/0
0000.0000.0002.01-00 0x00000005 0xd2b3 1052 55 0/0/0
0000.0000.0003.00-00* 0x00000014 0x194a 1051 111 1/0/0
0000.0000.0003.01-00* 0x00000002 0xabdb 854 55 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
Level-2 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
--------------------------------------------------------------------------
0000.0000.0003.00-00* 0x00000012 0xc93c 842 100 0/0/0
0000.0000.0004.00-00 0x00000026 0x331 1173 84 0/0/0
0000.0000.0004.01-00 0x00000001 0xee95 668 55 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
[SwitchD] display isis lsdb
Database information for IS-IS(1)
---------------------------------
Level-2 Link State Database
---------------------------
LSPID Seq Num Checksum Holdtime Length ATT/P/OL
-------------------------------------------------------------------------------
0000.0000.0003.00-00 0x00000013 0xc73d 1003 100 0/0/0
0000.0000.0004.00-00* 0x0000003c 0xd647 1194 84 0/0/0
0000.0000.0004.01-00* 0x00000002 0xec96 1007 55 0/0/0
*-Self LSP, +-Self LSP(Extended), ATT-Attached, P-Partition, OL-Overload
# Display the IS-IS routing information on each switch.
[SwitchA] display isis route
172
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL Vlan100 Direct D/L/-
10.1.2.0/24 20 NULL Vlan100 10.1.1.1 R/-/-
192.168.0.0/24 20 NULL Vlan100 10.1.1.1 R/-/-
0.0.0.0/0 10 NULL Vlan100 10.1.1.1 R/-/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
[SwitchC] display isis route
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
192.168.0.0/24 10 NULL Vlan300 Direct D/L/-
10.1.1.0/24 10 NULL Vlan100 Direct D/L/-
10.1.2.0/24 10 NULL Vlan200 Direct D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
192.168.0.0/24 10 NULL D/L/-
10.1.1.0/24 10 NULL D/L/-
10.1.2.0/24 10 NULL D/L/-
172.16.0.0/16 20 NULL Vlan300 192.168.0.2 R/-/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
[SwitchD] display isis route
Route information for IS-IS(1)
------------------------------
Level-2 IPv4 Forwarding Table
-----------------------------
173
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
192.168.0.0/24 10 NULL Vlan300 Direct D/L/-
10.1.1.0/24 20 NULL Vlan300 192.168.0.1 R/-/-
10.1.2.0/24 20 NULL Vlan300 192.168.0.1 R/-/-
172.16.0.0/16 10 NULL Vlan100 Direct D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
The output shows that the routing table of Level-1 switches contains a default route with the next hop as the Level-1-2 switch. The routing table of Level-2 switch contains both routing information of
Level-1 and Level-2.
DIS election configuration example
Network requirements
As shown in Figure 44 , Switches A, B, C, and D reside in IS-IS area 10 on a broadcast network
(Ethernet). Switch A and Switch B are Level-1-2 switches, Switch C is a Level-1 switch, and Switch D is a Level-2 switch.
Change the DIS priority of Switch A to make it elected as the Level-1-2 DIS router.
Figure 44 Network diagram
Switch A
L1/L2
Switch B
L1/L2
Vlan-int100
10.1.1.1/24
Vlan-int100
10.1.1.2/24
Vlan-int100
10.1.1.3/24
Vlan-int100
10.1.1.4/24
Switch C
L1
Configuration procedure
Switch D
L2
1. Configure IP addresses for interfaces. (Details not shown.)
2. Enable IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis enable 1
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
174
[SwitchB] isis 1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] isis enable 1
[SwitchB-Vlan-interface100] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] is-level level-1
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] isis enable 1
[SwitchC-Vlan-interface100] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] isis 1
[SwitchD-isis-1] network-entity 10.0000.0000.0004.00
[SwitchD-isis-1] is-level level-2
[SwitchD-isis-1] quit
[SwitchD] interface vlan-interface 100
[SwitchD-Vlan-interface100] isis enable 1
[SwitchD-Vlan-interface100] quit
# Display information about IS-IS neighbors on Switch A.
[SwitchA] display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0003.01
State: Up HoldTime: 21s Type: L1(L1L2) PRI: 64
System Id: 0000.0000.0003
Interface: Vlan-interface100 Circuit Id: 0000.0000.0003.01
State: Up HoldTime: 27s Type: L1 PRI: 64
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0004.01
State: Up HoldTime: 28s Type: L2(L1L2) PRI: 64
System Id: 0000.0000.0004
Interface: Vlan-interface100 Circuit Id: 0000.0000.0004.01
State: Up HoldTime: 30s Type: L2 PRI: 64
# Display information about IS-IS interfaces on Switch A.
[SwitchA] display isis interface
Interface information for IS-IS(1)
175
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
# Display information about IS-IS interfaces on Switch C.
[SwitchC] display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 Yes/No
# Display information about IS-IS interfaces on Switch D.
[SwitchD] display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/Yes
The output shows that when the default DIS priority is used, Switch C is the DIS for Level-1, and
Switch D is the DIS for Level-2. The pseudonodes of Level-1 and Level-2 are
0000.0000.0003.01 and 0000.0000.0004.01.
#Configure the DIS priority of Switch A.
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis dis-priority 100
[SwitchA-Vlan-interface100] quit
# Display IS-IS neighbors on Switch A.
[SwitchA] display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 21s Type: L1(L1L2) PRI: 64
System Id: 0000.0000.0003
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L1 PRI: 64
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 28s Type: L2(L1L2) PRI: 64
176
System Id: 0000.0000.0004
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 30s Type: L2 PRI: 64
# Display information about IS-IS interfaces on Switch A.
[SwitchA] display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 Yes/Yes
The output shows that after the DIS priority configuration, Switch A becomes the DIS for
Level-1-2, and the pseudonode is 0000.0000.0001.01.
# Display information about IS-IS neighbors and interfaces on Switch C.
[SwitchC] display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 25s Type: L1 PRI: 64
System Id: 0000.0000.0001
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 7s Type: L1 PRI: 100
[SwitchC] display isis interface
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
# Display information about IS-IS neighbors and interfaces on Switch D.
[SwitchD] display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0001
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 9s Type: L2 PRI: 100
System Id: 0000.0000.0002
Interface: Vlan-interface100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 28s Type: L2 PRI: 64
[SwitchD] display isis interface
177
Interface information for IS-IS(1)
----------------------------------
Interface: Vlan-interface100
Index IPv4.State IPv6.State CircuitID MTU Type DIS
00001 Up Down 1 1497 L1/L2 No/No
IS-IS route redistribution configuration example
Network requirements
As shown in Figure 45 , Switch A, Switch B, Switch C, and Switch D reside in the same AS. They use
IS-IS to interconnect. Switch A and Switch B are Level-1 routers, Switch D is a Level-2 router, and
Switch C is a Level-1-2 router.
Redistribute RIP routes into IS-IS on Switch D.
Figure 45 Network diagram
Switch A
L1
Vlan-int100
10.1.1.2/24
Vlan-int100
10.1.1.1/24
Vlan-int200
10.1.2.1/24
Vlan-int500
10.1.5.1/24
Vlan-int300
192.168.0.1/24
Switch C
L1/L2
Vlan-int300
192.168.0.2/24
RIP
Switch D
L2
Vlan-int400
10.1.4.1/24
Vlan-int400
10.1.4.2/24
Switch E
Vlan-int600
10.1.6.1/24
Vlan-int200
10.1.2.2/24 Area 20
Switch B
L1
Area 10
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] is-level level-1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis enable 1
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] is-level level-1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 200
178
[SwitchB-Vlan-interface200] isis enable 1
[SwitchB-Vlan-interface200] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis enable 1
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] isis enable 1
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] isis enable 1
[SwitchC-Vlan-interface300] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] isis 1
[SwitchD-isis-1] is-level level-2
[SwitchD-isis-1] network-entity 20.0000.0000.0004.00
[SwitchD-isis-1] quit
[SwitchD] interface interface vlan-interface 300
[SwitchD-Vlan-interface300] isis enable 1
[SwitchD-Vlan-interface300] quit
[SwitchD] interface interface vlan-interface 400
[SwitchD-Vlan-interface400] isis enable 1
[SwitchD-Vlan-interface400] quit
# Display IS-IS routing information on each switch.
[SwitchA] display isis route
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL VLAN100 Direct D/L/-
10.1.2.0/24 20 NULL VLAN100 10.1.1.1 R/-/-
192.168.0.0/24 20 NULL VLAN100 10.1.1.1 R/-/-
0.0.0.0/0 10 NULL VLAN100 10.1.1.1 R/-/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
[SwitchC] display isis route
Route information for IS-IS(1)
179
------------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL VLAN100 Direct D/L/-
10.1.2.0/24 10 NULL VLAN200 Direct D/L/-
192.168.0.0/24 10 NULL VLAN300 Direct D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL D/L/-
10.1.2.0/24 10 NULL D/L/-
192.168.0.0/24 10 NULL D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
[SwitchD] display isis route
Route information for IS-IS(1)
------------------------------
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
192.168.0.0/24 10 NULL VLAN300 Direct D/L/-
10.1.1.0/24 20 NULL VLAN300 192.168.0.1 R/-/-
10.1.2.0/24 20 NULL VLAN300 192.168.0.1 R/-/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
3. Run RIPv2 between Switch D and Switch E, and configure IS-IS to redistribute RIP routes on
Switch D:
# Configure RIPv2 on Switch D.
[SwitchD] rip 1
[SwitchD-rip-1] network 10.0.0.0
[SwitchD-rip-1] version 2
[SwitchD-rip-1] undo summary
# Configure RIPv2 on Switch E.
[SwitchE] rip 1
[SwitchE-rip-1] network 10.0.0.0
180
[SwitchE-rip-1] version 2
[SwitchE-rip-1] undo summary
# Configure IS-IS to redistribute RIP routes on Switch D.
[SwitchD-rip-1] quit
[SwitchD] isis 1
[SwitchD–isis-1] address-family ipv4
[SwitchD–isis-1-ipv4] import-route rip level-2
# Display IS-IS routing information on Switch C.
[SwitchC] display isis route
Route information for IS-IS(1)
------------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL VLAN100 Direct D/L/-
10.1.2.0/24 10 NULL VLAN200 Direct D/L/-
192.168.0.0/24 10 NULL VLAN300 Direct D/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
10.1.1.0/24 10 NULL D/L/-
10.1.2.0/24 10 NULL D/L/-
192.168.0.0/24 10 NULL D/L/-
10.1.4.0/24 20 NULL VLAN300 192.168.0.2 R/L/-
10.1.5.0/24 10 0 VLAN300 192.168.0.2 R/L/-
10.1.6.0/24 10 0 VLAN300 192.168.0.2 R/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
IS-IS authentication configuration example
Network requirements
As shown in Figure 46 , Switch A, Switch B, Switch C, and Switch D reside in the same IS-IS routing
domain. Run IS-IS among them.
Switch A, Switch B, and Switch C belong to Area 10, and Switch D belongs to Area 20.
•
Configure neighbor relationship authentication between neighbors.
•
Configure area authentication in Area 10 to prevent untrusted routes from entering into the area.
181
•
Configure routing domain authentication on Switch C and Switch D to prevent untrusted routes from entering the routing domain.
Figure 46 Network diagram
Vlan-int100
10.1.1.2/24
Switch A
L1
Vlan-int100
10.1.1.1/24
Vlan-int300
10.1.3.1/24
Vlan-int200
10.1.2.1/24 Switch C
L1/L2
Vlan-int200
10.1.2.2/24
Vlan-int300
10.1.3.2/24
Switch D
L2
Area 20
Switch B
L1
Configuration procedure
Area 10
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis enable 1
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] isis enable 1
[SwitchB-Vlan-interface200] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis enable 1
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] isis enable 1
[SwitchC-Vlan-interface300] quit
[SwitchC] interface vlan-interface 300
182
[SwitchC-Vlan-interface300] isis enable 1
[SwitchC-Vlan-interface300] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] isis 1
[SwitchD-isis-1] network-entity 20.0000.0000.0001.00
[SwitchD-isis-1] quit
[SwitchD] interface vlan-interface 300
[SwitchD-Vlan-interface300] isis enable 1
[SwitchD-Vlan-interface300] quit
3. Configure neighbor relationship authentication between neighbors:
# Set the authentication mode to MD5 and set the plaintext key to eRq on VLAN-interface 100 of Switch A and on VLAN-interface 100 of Switch C.
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis authentication-mode md5 plain eRg
[SwitchA-Vlan-interface100] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] isis authentication-mode md5 plain eRg
[SwitchC-Vlan-interface100] quit
# Set the authentication mode to MD5 and set the plaintext key to t5Hr on VLAN-interface 200 of Switch B and on VLAN-interface 200 of Switch C.
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] isis authentication-mode md5 plain t5Hr
[SwitchB-Vlan-interface200] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis authentication-mode md5 plain t5Hr
[SwitchC-Vlan-interface200] quit
# Set the authentication mode to MD5 and set the plaintext key to hSec on VLAN-interface 300 of Switch D and on VLAN-interface 300 of Switch C.
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] isis authentication-mode md5 plain hSec
[SwitchC-Vlan-interface300] quit
[SwitchD] interface vlan-interface 300
[SwitchD-Vlan-interface300] isis authentication-mode md5 plain hSec
[SwitchD-Vlan-interface300] quit
4. Set the area authentication mode to MD5 and set the plaintext key to 10Sec on Switch A,
Switch B, and Switch C.
[SwitchA] isis 1
[SwitchA-isis-1] area-authentication-mode md5 plain 10Sec
[SwitchA-isis-1] quit
[SwitchB] isis 1
[SwitchB-isis-1] area-authentication-mode md5 plain 10Sec
[SwitchB-isis-1] quit
[SwitchC] isis 1
[SwitchC-isis-1] area-authentication-mode md5 plain 10Sec
[SwitchC-isis-1] quit
5. Set routing domain authentication mode to MD5 and set the plaintext key to 1020Sec on Switch
C and Switch D.
[SwitchC] isis 1
183
[SwitchC-isis-1] domain-authentication-mode md5 plain 1020Sec
[SwitchC-isis-1] quit
[SwitchD] isis 1
[SwitchD-isis-1] domain-authentication-mode md5 plain 1020Sec
IS-IS GR configuration example
Network requirements
As shown in Figure 47 , Switch A, Switch B, and Switch C belong to the same IS-IS routing domain.
Figure 47 Network diagram
GR restarter
Switch A
Vlan-int100
10.0.0.1/24
Vlan-int100
10.0.0.2/24
Switch B
Vlan-int100
10.0.0.3/24
Switch C
GR helper GR helper
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces. (Details not shown.)
2. Configure IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at layer 3 and dynamic route update can be implemented among them with IS-IS. (Details not shown.)
3. Enable IS-IS GR on Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] graceful-restart
[SwitchA-isis-1] return
Verifying the configuration
# Restart the IS-IS process on Switch A.
<SwitchA> reset isis all 1 graceful-restart
Reset IS-IS process? [Y/N]:y
# Check the GR state of the IS-IS process on Switch A.
<SwitchA> display isis graceful-restart status
Restart information for IS-IS(1)
--------------------------------
Restart status: COMPLETE
Restart phase: Finish
Restart t1: 3, count 10; Restart t2: 60; Restart t3: 300
SA Bit: supported
Level-1 restart information
---------------------------
Total number of interfaces: 1
184
Number of waiting LSPs: 0
Level-2 restart information
---------------------------
Total number of interfaces: 1
Number of waiting LSPs: 0
IS-IS NSR configuration example
Network requirements
As shown in Figure 48 , Switch S, Switch A, and Switch B belong to the same IS-IS routing domain.
•
Run IS-IS on all the switches to interconnect them with each other.
•
Enable IS-IS NSR on Switch S to ensure forwarding continuity between Switch A and Switch B when an active/standby switchover occurs on Switch S.
Figure 48 Network diagram
Loop 0
22.22.22.22/32
Switch A
Vlan-int100
12.12.12.1/24
Vlan-int100
12.12.12.2/24
Switch S
Vlan-int200
14.14.14.1/24
Vlan-int200
14.14.14.2/24
Switch B
Loop 0
44.44.44.44/32
Configuration procedure
1. Configure the IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure IS-IS on the switches to make sure Switch S, Switch A, and Switch B can communicate with each other at Layer 3 and dynamic route update can be implemented among them with IS-IS. (Details not shown.)
3. Enable IS-IS NSR on Switch S.
<SwitchS> system-view
[SwitchS] isis 1
[SwitchS-isis-1] non-stop-routing
[SwitchS-isis-1] return
Verifying the configuration
# Reoptimize process placement on Switch S to trigger an active/standby switchover.
<SwitchS> system-view
[SwitchS] placement reoptimize
Predicted changes to the placement
Program Current location New location
--------------------------------------------------------------------- syslog 0/0 0/0 diagusageratio 0/0 0/0 l3vpn 0/0 0/0 fc 0/0 0/0 dns 0/0 0/0 lauth 0/0 0/0 aaa 0/0 0/0 lsm 0/0 0/0
185
rm 0/0 0/0 rm6 0/0 0/0 track 0/0 0/0 ip6addr 0/0 0/0 ipaddr 0/0 0/0 rpm 0/0 0/0 trange 0/0 0/0 tunnel 0/0 0/0 lagg 0/0 0/0 bfd 0/0 0/0 acl 0/0 0/0 slsp 0/0 0/0 usr6 0/0 0/0 usr 0/0 0/0 qos 0/0 0/0 fczone 0/0 0/0 ethbase 0/0 0/0 ipcim 0/0 0/0 ip6base 0/0 0/0 ipbase 0/0 0/0 eth 0/0 0/0 eviisis 0/0 0/0 ifnet NA NA isis 0/0 1/0
Continue? [y/n]:y
Re-optimization of the placement start. You will be notified on completion
Re-optimization of the placement complete. Use 'display placement' to view the new placement
# During the switchover period, display IS-IS neighbor information on Switch A to verify the neighborship between Switch A and Switch S.
<SwitchA> display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0001
Interface: vlan100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 25s Type: L1(L1L2) PRI: 64
System Id: 0000.0000.0001
Interface: vlan100 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L2(L1L2) PRI: 64
# Display IS-IS routing information on Switch A to verify that Switch A has a route to the loopback interface of Switch B.
<SwitchA> display isis route
Route information for IS-IS(1)
-----------------------------
186
Level-1 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
12.12.12.0/24 10 NULL vlan100 Direct D/L/-
22.22.22.22/32 10 NULL Loop0 Direct D/-/-
14.14.14.0/32 10 NULL vlan100 12.12.12.2 R/L/-
44.44.44.44/32 10 NULL vlan100 12.12.12.2 R/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
12.12.12.0/24 10 NULL vlan100 Direct D/L/-
22.22.22.22/32 10 NULL Loop0 Direct D/-/-
14.14.14.0/32 10 NULL
44.44.44.44/32 10 NULL
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
# Display IS-IS neighbor information on Switch B to verify the neighborship between Switch B and
Switch S.
<SwitchB> display isis peer
Peer information for IS-IS(1)
----------------------------
System Id: 0000.0000.0001
Interface: vlan200 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 25s Type: L1(L1L2) PRI: 64
System Id: 0000.0000.0001
Interface: vlan200 Circuit Id: 0000.0000.0001.01
State: Up HoldTime: 27s Type: L2(L1L2) PRI: 64
# Display IS-IS routing information on Switch B to verify that Switch B has a route to the loopback interface of Switch A.
<SwitchB> display isis route
Route information for IS-IS(1)
-----------------------------
Level-1 IPv4 Forwarding Table
-----------------------------
187
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
14.14.14.0/24 10 NULL vlan200 Direct D/L/-
44.44.44.44/32 10 NULL Loop0 Direct D/-/-
12.12.12.0/32 10 NULL vlan200 14.14.14.4 R/L/-
22.22.22.22/32 10 NULL vlan200 14.14.14.4 R/L/-
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv4 Forwarding Table
-----------------------------
IPv4 Destination IntCost ExtCost ExitInterface NextHop Flags
-------------------------------------------------------------------------------
14.14.14.0/24 10 NULL vlan200 Direct D/L/-
44.44.44.44/32 10 NULL Loop0 Direct D/-/-
12.12.12.0/32 10 NULL
22.22.22.22/32 10 NULL
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
The output shows that the neighbor information and routing information on Switch A and Switch B have not changed during the active/standby switchover on Switch S. The neighbors are unaware of the switchover.
BFD for IS-IS configuration example
Network requirements
•
As shown in Figure 49 , run IS-IS on Switch A, Switch B and Switch C so that can reach each
other at the network layer.
•
After the link over which Switch A and Switch B communicate through the Layer-2 switch fails,
BFD can quickly detect the failure and notify IS-IS of the failure. Switch A and Switch B then communicate through Switch C.
Figure 49 Network diagram
Loop0
Switch A
Vlan-int10
Vlan-int11
BFD
L2 Switch
Vlan-int10
Switch B
Vlan-int13
Loop0
Area 0
Vlan-int11 Vlan-int13
Switch C
Table 14 Interface and IP address assignment
Device
Switch A
Interface IP address
Vlan-int10 10.1.0.102/24
Device
Switch B
188
Interface IP address
Vlan-int10 10.1.0.100/24
Device
Switch C
Interface IP address
Vlan-int11
Loop0
Vlan-int11
11.1.1.1/24
121.1.1.1/32
11.1.1.2/24
Vlan-int13 13.1.1.2/24
Configuration procedure
Device
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure basic IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] quit
[SwitchA] interface loopback 0
[SwitchA-LoopBack0] isis enable
[SwitchA-LoopBack0] quit
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] isis enable
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] isis enable
[SwitchA-Vlan-interface11] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface loopback 0
[SwitchB-LoopBack0] isis enable
[SwitchB-LoopBack0] quit
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] isis enable
[SwitchB-Vlan-interface10] quit
[SwitchB] interface vlan-interface 13
[SwitchB-Vlan-interface13] isis enable
[SwitchB-Vlan-interface13] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 11
[SwitchC-Vlan-interface11] isis enable
[SwitchC-Vlan-interface11] quit
[SwitchC] interface vlan-interface 13
[SwitchC-Vlan-interface13] isis enable
Interface IP address
Vlan-int13
Loop0
13.1.1.1/24
120.1.1.1/32
189
[SwitchC-Vlan-interface13] quit
3. Configure BFD functions:
# Enable BFD and configure BFD parameters on Switch A.
[SwitchA] bfd session init-mode passive
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] isis bfd enable
[SwitchA-Vlan-interface10] bfd min-receive-interval 500
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500
[SwitchA-Vlan-interface10] bfd detect-multiplier 7
# Enable BFD and configure BFD parameters on Switch B.
[SwitchB] bfd session init-mode active
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] isis bfd enable
[SwitchB-Vlan-interface10] bfd min-receive-interval 500
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500
[SwitchB-Vlan-interface10] bfd detect-multiplier 8
[SwitchB-Vlan-interface10] return
Verifying the configuration
# Display the BFD session information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 Session Working Under Ctrl Mode:
LD/RD SourceAddr DestAddr State Holdtime Interface
3/1 192.168.0.102 192.168.0.100 Up 1700ms Vlan10
# Display routes destined for 120.1.1.1/32 on Switch A.
<SwitchA> display ip routing-table 120.1.1.1 verbose
Summary Count : 1
Destination: 120.1.1.1/32
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 10 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 192.168.0.100
Label: NULL RealNextHop: 192.168.0.100
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface10
190
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
The output shows that Switch A and Switch B communicate through VLAN-interface 10. Then the link over VLAN-interface 10 fails.
# Display routes destined for 120.1.1.1/32 on Switch A.
<SwitchA> display ip routing-table 120.1.1.1 verbose
Summary Count : 1
Destination: 120.1.1.1/32
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 20 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 10.1.1.100
Label: NULL RealNextHop: 10.1.1.100
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface11
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
The output shows that Switch A and Switch B communicate through VLAN-interface 11.
IS-IS FRR configuration example
Network requirements
As shown in Figure 50 , Switch A, Switch B, and Switch C belong to the same IS-IS routing domain.
Configure IS-IS FRR so that when the Link A fails, traffic can be switched to Link B immediately.
Figure 50 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
100
Link B
Vlan
-int
101
Link A
Vlan
-int
101
Loop0 Loop0
Switch A
Vlan-int200 Vlan-int200
Switch B
191
Table 15 Interface and IP address assignment
Device
Switch A
Switch C
Interface IP address
Vlan-int100 12.12.12.1/24
Vlan-int200 13.13.13.1/24
Loop0 1.1.1.1/32
Vlan-int100 12.12.12.2/24
Vlan-int101 24.24.24.2/24
Device
Switch B
Interface IP address
Vlan-int101 24.24.24.4/24
Vlan-int200 13.13.13.2/24
Loop0 4.4.4.4/32
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3. (Details not shown.)
3. Configure IS-IS FRR:
Enable IS-IS FRR to calculate a backup next hop through LFA calculation, or designate a backup next hop by using a referenced routing policy.
(Method 1.) Enable IS-IS FRR to calculate a backup next hop through LFA calculation:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] address-family ipv4
[SwitchA-isis-1-ipv4] fast-reroute lfa
[SwitchA-isis-1-ipv4] quit
[SwitchA-isis-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] address-family ipv4
[SwitchB-isis-1-ipv4] fast-reroute lfa
[SwitchB-isis-1-ipv4] quit
[SwitchB-isis-1] quit
(Method 2.) Enable IS-IS FRR to designate a backup next hop by using a referenced routing policy:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ip prefix-list abc index 10 permit 4.4.4.4 32
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ip address prefix-list abc
[SwitchA-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
100 backup-nexthop 12.12.12.2
[SwitchA-route-policy-frr-10] quit
[SwitchA] isis 1
[SwitchA-isis-1] address-family ipv4
[SwitchA-isis-1-ipv4] fast-reroute route-policy frr
[SwitchA-isis-1-ipv4] quit
[SwitchA-isis-1] quit
# Configure Switch B.
<SwitchB> system-view
192
[SwitchB] ip prefix-list abc index 10 permit 1.1.1.1 32
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ip address prefix-list abc
[SwitchB-route-policy-frr-10] apply fast-reroute backup-interface vlan-interface
101 backup-nexthop 24.24.24.2
[SwitchB-route-policy-frr-10] quit
[SwitchB] isis 1
[SwitchB-isis-1] address-family ipv4
[SwitchB-isis-1-ipv4] fast-reroute route-policy frr
[SwitchB-isis-1-ipv4] quit
[SwitchB-isis-1] quit
Verifying the configuration
# Display route 4.4.4.4/32 on Switch A to view the backup next hop information.
[SwitchA] display ip routing-table 4.4.4.4 verbose
Summary Count : 1
Destination: 4.4.4.4/32
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 10 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.2
Label: NULL RealNextHop: 13.13.13.2
BkLabel: NULL BkNextHop: 12.12.12.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display route 1.1.1.1/32 on Switch B to view the backup next hop information.
[SwitchB] display ip routing-table 1.1.1.1 verbose
Summary Count : 1
Destination: 1.1.1.1/32
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 04h20m37s
Cost: 10 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
193
TableID: 0x2 OrigAs: 0
NibID: 0x26000002 LastAs: 0
AttrID: 0xffffffff Neighbor: 0.0.0.0
Flags: 0x1008c OrigNextHop: 13.13.13.1
Label: NULL RealNextHop: 13.13.13.1
BkLabel: NULL BkNextHop: 24.24.24.2
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
194
Configuring BGP
Overview
Border Gateway Protocol (BGP) is an exterior gateway protocol (EGP). It is called internal BGP
(IBGP) when it runs within an AS and called external BGP (EBGP) when it runs between ASs.
The current version in use is BGP-4 (RFC 4271).
BGP has the following characteristics:
•
Focuses on route control and selection rather than route discovery and calculation.
•
Uses TCP to enhance reliability.
•
Measures the distance of a route by using a list of ASs that the route must travel through to reach the destination. BGP is also called a path-vector protocol.
•
Supports CIDR.
•
Reduces bandwidth consumption by advertising only incremental updates. BGP is very suitable to advertise large numbers of routes on the Internet.
•
Eliminates routing loops by adding AS path information to BGP route updates.
•
Uses policies to implement flexible route filtering and selection.
•
Has good scalability.
BGP speaker and BGP peer
A router running BGP is a BGP speaker. A BGP speaker establishes peer relationships with other
BGP speakers to exchange routing information over TCP connections.
BGP peers include the following types:
•
IBGP peers —Reside in the same AS as the local router.
•
EBGP peers —Reside in different ASs from the local router.
BGP message types
BGP uses the following message types:
•
Open —After establishing a TCP connection, BGP sends an Open message to establish a session to the peer.
•
Update —BGP sends update messages to exchange routing information between peers. Each update message can advertise a group of feasible routes with identical attributes and multiple withdrawn routes.
•
Keepalive —BGP sends Keepalive messages between peers to maintain connectivity.
•
Route-refresh —BGP sends a Route-refresh message to request the routing information for a specific address family from a peer.
•
Notification —BGP sends a Notification message upon detecting an error and immediately closes the connection.
BGP path attributes
BGP uses the following path attributes in update messages for route filtering and selection:
•
ORIGIN
195
The ORIGIN attribute specifies the origin of BGP routes. This attribute has the following types:
IGP —Has the highest priority. Routes generated in the local AS have the IGP attribute.
EGP —Has the second highest priority. Routes obtained through EGP have the EGP attribute.
INCOMPLETE —Has the lowest priority. The source of routes with this attribute is unknown.
Routes redistributed from other routing protocols have the INCOMPLETE attribute.
•
AS_PATH
The AS_PATH attribute identifies the ASs through which a route has passed. Before advertising a route to another AS, BGP adds the local AS number into the AS_PATH attribute, so the receiver can determine ASs to route the message back.
The AS_PATH attribute has the following types:
AS_SEQUENCE
—Arranges AS numbers in sequence. As shown in Figure 51 , the number
of the AS closest to the receiver's AS is leftmost.
AS_SET —Arranges AS numbers randomly.
Figure 51 AS_PATH attribute
D = 8.0.0.0
AS_PATH = 10
AS 20
8.0.0.0
AS 10
D = 8.0.0.0
AS_PATH = 10
AS 40
D = 8.0.0.0
AS_PATH = 20, 10
D = 8.0.0.0
AS_PATH = 30, 20, 10
D = 8.0.0.0
AS_PATH = 40, 10
AS 30 AS 50
BGP uses the AS_PATH attribute to implement the following functions:
Avoid routing loops —A BGP router does not receive routes containing the local AS number to avoid routing loops.
Affect route selection —BGP gives priority to the route with the shortest AS_PATH length if
other factors are the same. As shown in Figure 51 , the BGP router in AS 50 gives priority to
the route passing AS 40 for sending data to the destination 8.0.0.0. In some applications, you can apply a routing policy to control BGP route selection by modifying the AS_PATH
length. For more information about routing policy, see " Configuring routing policies ."
Filter routes —By using an AS path list, you can filter routes based on AS numbers contained in the AS_PATH attribute. For more information about AS path list, see
" Configuring routing policies ."
•
NEXT_HOP
The NEXT_HOP attribute may not be the IP address of a directly connected router. Its value is determined as follows:
When a BGP speaker advertises a self-originated route to a BGP peer, it sets the address of the sending interface as the NEXT_HOP.
196
When a BGP speaker sends a received route to an EBGP peer, it sets the address of the sending interface as the NEXT_HOP.
When a BGP speaker sends a route received from an EBGP peer to an IBGP peer, it does not modify the NEXT_HOP attribute. If load balancing is configured, BGP modifies the
Figure 52 NEXT_HOP attribute
D = 8.0.0.0
Next_hop = 1.1.1.1
AS 200
AS 100
1.1.2.1/24 EBGP
1.1.1.1/24
8.0.0.0
EBGP
D = 8.0.0.0
Next_hop = 1.1.2.1
AS 300
IBGP
D = 8.0.0.0
Next_hop = 1.1.2.1
•
MED (MULTI_EXIT_DISC)
BGP advertises the MED attribute between two neighboring ASs, each of which does not advertise the attribute to any other AS.
Similar to metrics used by IGPs, MED is used to determine the optimal route for traffic going into an AS. When a BGP router obtains multiple routes to the same destination but with different next hops, it considers the route with the smallest MED value as the optimal route. As shown in
Figure 53 , traffic from AS 10 to AS 20 travels through Router B that is selected according to
MED.
Figure 53 MED attribute
2.1.1.1
MED = 0
Router B
D = 9.0.0.0
Next_hop = 2.1.1.1
MED = 0
EBGP
Router A IBGP
IBGP
9.0.0.0
Router D
D = 9.0.0.0
Next_hop = 3.1.1.1
MED = 100
AS 10
EBGP IBGP
3.1.1.1
MED = 100
Router C
AS 20
197
Generally BGP only compares MEDs of routes received from the same AS. You can also use the compare-different-as-med command to force BGP to compare MED values of routes received from different ASs.
•
LOCAL_PREF
The LOCAL_PREF attribute is exchanged between IBGP peers only, and is not advertised to any other AS. It indicates the priority of a BGP router.
BGP uses LOCAL_PREF to determine the optimal route for traffic leaving the local AS. When a
BGP router obtains multiple routes to the same destination but with different next hops, it considers the route with the highest LOCAL_PREF value as the optimal route. As shown in
Figure 54 , traffic from AS 20 to AS 10 travels through Router C that is selected according to
LOCAL_PREF.
Figure 54 LOCAL_PREF attribute
Local_pref = 100
Router B
8.0.0.0
2.1.1.1
Router A
3.1.1.1
EBGP
EBGP
IBGP
IBGP
IBGP
D = 8.0.0.0
Next_hop = 2.1.1.1
Local_pref = 100
Router D
D = 8.0.0.0
Next_hop = 3.1.1.1
Local_pref = 200
AS 10
Router C
Local_pref = 200
AS 20
•
COMMUNITY
The COMMUNITY attribute identifies the community of BGP routes. A BGP community is a group of routes with the same characteristics. It has no geographical boundaries. Routes of different ASs can belong to the same community.
A route can carry one or more COMMUNITY attribute values (each of which is represented by a
4-byte integer). A router uses the COMMUNITY attribute to determine whether to advertise the route and the advertising scope without using complex filters such as ACLs. This mechanism simplifies routing policy configuration, management, and maintenance.
Well-known COMMUNITY attributes involve the following:
INTERNET —By default, all routes belong to the Internet community. Routes with this attribute can be advertised to all BGP peers.
NO_EXPORT —Routes with this attribute cannot be advertised out of the local AS or out of the local confederation, but can be advertised to other sub-ASs in the confederation. For
confederation information, see " Settlements for problems in large-scale BGP networks ."
No_ADVERTISE —Routes with this attribute cannot be advertised to other BGP peers.
No_EXPORT_SUBCONFED —Routes with this attribute cannot be advertised out of the local AS or other sub-ASs in the local confederation.
You can configure BGP community lists to filter BGP routes based on the BGP COMMUNITY attribute.
198
•
Extended community attribute
To meet new demands, BGP defines the extended community attribute. The extended community attribute has the following advantages over the COMMUNITY attribute:
Provides more attribute values by extending the attribute length to eight bytes.
Allows for using different types of extended community attributes in different scenarios to enhance route filtering and control and simplify configuration and management.
The device supports the route target and Site of Origin (SoO) extended community attributes.
For information about route target, see MPLS Configuration Guide .
The SoO attribute specifies the site where the route originated. It prevents advertising a route back to the originating site. If the AS-path attribute is lost, the router can use the SoO attribute to avoid routing loops.
The SoO attribute has the following formats:
16-bit AS number:32-bit user-defined number. For example, 100:3.
32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.
32-bit AS number:16-bit user-defined number , where the minimum value of the AS number is 65536. For example, 65536:1.
BGP route selection
BGP discards routes with unreachable NEXT_HOPs. If multiple routes to the same destination are available, BGP selects the optimal route in the following sequence:
1. The route with the highest Preferred_value.
2. The route with the highest LOCAL_PREF.
3. The route generated by the network command, the route redistributed by the import-route command, or the summary route in turn.
4. The route with the shortest AS_PATH.
5. The IGP, EGP, or INCOMPLETE route in turn.
6. The route with the lowest MED value.
7. The route learned from EBGP, confederation EBGP, confederation IBGP, or IBGP in turn.
8. The route with the smallest IGP metric.
9. The route with the smallest recursion depth.
10. If all routes are received from EBGP peers and the peers have different router IDs, the route that used to be an optimal route becomes the optimal route.
11. The route advertised by the router with the smallest router ID.
If one of the routes is advertised by a route reflector, BGP compares the ORIGINATOR_ID of the route with the router IDs of other routers. Then, BGP selects the route with the smallest ID as the optimal route.
12. The route with the shortest CLUSTER_LIST.
13. The route advertised by the peer with the lowest IP address.
The CLUSTER_IDs of route reflectors form a CLUSTER_LIST. If a route reflector receives a route that contains its own CLUSTER ID in the CLUSTER_LIST, the router discards the route to avoid routing loops.
If load balancing is configured, the system selects available routes to implement load balancing.
BGP route advertisement rules
BGP follows these rules for route advertisement:
199
•
When multiple feasible routes to a destination exist, BGP advertises only the optimal route to its peers. If the advertise-rib-active command is configured, BGP advertises the optimal route in the IP routing table. If not, BGP advertises the optimal route in the BGP routing table.
•
BGP advertises only routes that it uses.
•
BGP advertises routes learned from an EBGP peer to all BGP peers, including both EBGP and
IBGP peers.
•
BGP advertises routes learned from an IBGP peer to EBGP peers, rather than other IBGP peers.
•
After establishing a session to a new BGP peer, BGP advertises all the routes matching the above rules to the peer. After that, BGP advertises only incremental updates to the peer.
BGP load balancing
BGP load balancing is applicable between EBGP peers, between IBGP peers, and between confederations.
BGP implements load balancing through route recursion and route selection.
BGP load balancing through route recursion
The next hop of a BGP route might not be directly connected. One of the reasons is that the next hop information exchanged between IBGP peers is not modified. The BGP router must find the directly connected next hop through IGP. The matching route with the direct next hop is called the recursive route. The process of finding a recursive route is route recursion.
If multiple recursive routes to the same destination are load balanced, BGP generates the same number of next hops to forward packets.
BGP load balancing based on route recursion is always enabled in the system.
BGP load balancing through route selection
IGP routing protocols, such as RIP and OSPF, can use route metrics as criteria to load balance between routes that have the same metric. BGP cannot load balance between routes by route metrics as an IGP protocol does, because BGP does not have a route computation algorithm.
BGP uses the following load balancing criteria to determine load balanced routes:
•
The routes have the same ORIGIN, LOCAL_PREF, and MED attributes. If the balance as-path-neglect command is not configured, the routes must also have the same AS_PATH attribute.
•
The routes have the same MPLS label assignment status (labeled or not labeled).
BGP does not use the route selection rules described in " BGP route selection " for load balancing.
As shown in Figure 55 , Router A and Router B are IBGP peers of Router C. Router C allows a
maximum number of two ECMP routes for load balancing.
Router D and Router E both advertise a route 9.0.0.0 to Router C. Router C installs the two routes to its routing table for load balancing if the routes meet the BGP load balancing criteria. After that,
Router C forwards to Router A and Router B a single route whose attributes are changed as follows:
•
AS_PATH attribute:
If the balance as-path-neglect command is not configured, the AS_PATH attribute does not change.
If the balance as-path-neglect command is configured, the AS_PATH attribute is changed to the attribute of the optimal route.
•
The NEXT_HOP attribute is changed to the IP address of Router C.
•
Other attributes are changed to be the same as the optimal route.
200
Figure 55 Network diagram
Router A Router D
Router C
AS 200 AS 100
9.0.0.0/24
Router B Router E
Settlements for problems in large-scale BGP networks
You can use the following methods to facilitate management and improve route distribution efficiency on a large-scale BGP network.
•
Route summarization
Route summarization can reduce the BGP routing table size by advertising summary routes rather than more specific routes.
The system supports both manual and automatic route summarization. Manual route summarization allows you to determine the attribute of a summary route and whether to advertise more specific routes.
•
Route dampening
Route flapping (a route comes up and disappears in the routing table frequently) causes BGP to send many routing updates. It can consume too many resources and affect other operations.
In most cases, BGP runs in complex networks where route changes are more frequent. To solve the problem caused by route flapping, you can use BGP route dampening to suppress unstable routes.
BGP route dampening uses a penalty value to judge the stability of a route. The bigger the value, the less stable the route. Each time a route state changes from reachable to unreachable, or a reachable route's attribute changes, BGP adds a penalty value of 1000 to the route. When the penalty value of the route exceeds the suppress value, the route is suppressed and cannot become the optimal route. When the penalty value reaches the upper limit, no penalty value is added.
If the suppressed route does not flap, its penalty value gradually decreases to half of the suppress value after a period of time. This period is called "Half-life." When the value decreases to the reusable threshold value, the route is usable again.
201
Figure 56 BGP route dampening
Penalty value
Suppress threshold
Reusable threshold
Suppression time
Time
Half-life
•
Peer group
You can organize BGP peers with the same attributes into a group to simplify their configurations.
When a peer joins the peer group, the peer obtains the same configuration as the peer group. If the configuration of the peer group is changed, the configuration of group members is changed.
•
Community
You can apply a community list or an extended community list to a routing policy for route
control. For more information, see " BGP path attributes ."
•
Route reflector
IBGP peers must be fully meshed to maintain connectivity. If n routers exist in an AS, the number of IBGP connections is n(n-1)/2. If a large number of IBGP peers exist, large amounts of network and CPU resources are consumed to maintain sessions.
Using route reflectors can solve this issue. In an AS, a router acts as a route reflector, and other routers act as clients connecting to the route reflector. The route reflector forwards routing information received from a client to other clients. In this way, all clients can receive routing information from one another without establishing BGP sessions.
must establish BGP sessions to the route reflector and other non-clients.
Figure 57 Network diagram for a route reflector
IBGP
Route reflector
IBGP
Non-client
Cluster
Client
IBGP
IBGP
IBGP
IBGP
Client Client
202
Non-client
AS 65000
The route reflector and clients form a cluster. Typically a cluster has one route reflector. The ID of the route reflector is the Cluster_ID. You can configure more than one route reflector in a
cluster to improve availability, as shown in Figure 58 . The configured route reflectors must have
the same Cluster_ID to avoid routing loops.
Figure 58 Network diagram for route reflectors
Route reflector1
IBGP
Route reflector2
Cluster
IBGP IBGP IBGP
Client Client
Client
AS 65000
When the BGP routers in an AS are fully meshed, route reflection is unnecessary because it consumes more bandwidth resources. You can use commands to disable route reflection instead of modifying network configuration or changing network topology.
After route reflection is disabled between clients, routes can still be reflected between a client and a non-client.
•
Confederation
Confederation is another method to manage growing IBGP connections in an AS. It splits an AS
into multiple sub-ASs. In each sub-AS, IBGP peers are fully meshed. As shown in Figure 59 ,
intra-confederation EBGP connections are established between sub-ASs in AS 200.
Figure 59 Confederation network diagram
AS 65002 AS 65003
EBGP EBGP
AS 100
EBGP
AS 200
IBGP
IBGP
IBGP
AS 65004
203
A non-confederation BGP speaker does not need to know sub-ASs in the confederation. It considers the confederation as one AS, and the confederation ID as the AS number. In the above figure, AS 200 is the confederation ID.
Confederation has a deficiency. When you change an AS into a confederation, you must reconfigure the routers, and the topology will be changed.
In large-scale BGP networks, you can use both route reflector and confederation.
MP-BGP
BGP-4 can only advertise IPv4 unicast routing information. Multiprotocol Extensions for BGP-4
(MP-BGP) can advertise routing information for the following address families:
•
IPv6 unicast address family.
•
IPv4 multicast and IPv6 multicast address families.
PIM uses static and dynamic unicast routes to perform RPF check before creating multicast routing entries. When the multicast and unicast topologies are different, you can use MP-BGP to advertise the routes for RPF check. MP-BGP stores the routes in the BGP multicast routing table. For more information about PIM and RPF check, see IP Multicast Configuration Guide .
•
VPNv4 and VPNv6 address families.
For more information about VPNv4 and VPNv6, see MPLS Configuration Guide .
•
Labeled IPv4 unicast and IPv6 unicast address families.
MP-BGP advertises IPv4 unicast/IPv6 unicast routes and MPLS labels assigned for the routes.
Labeled IPv4 unicast routes apply to inter-AS Option C for MPLS L3VPN. Labeled IPv6 unicast routes apply to 6PE and inter-AS Option C for MPLS L3VPN. For more information about inter-AS Option C, see MPLS Configuration Guide .
•
L2VPN address family.
L2VPN information includes label block information and remote peer information. For more information about L2VPN and VPLS, see MPLS Configuration Guide .
•
EVPN address family.
MP-BGP advertises EVPN routes to implement automatic VTEP discovery, VXLAN tunnel establishment and assignment, and MAC and ARP information advertisement. For more information about EVPN, see EVPN Configuration Guide .
•
IPv4 MDT address family.
MP-BGP advertises MDT information including the PE address and default group so that multicast VPN can create a default MDT that uses the PE as the root on the public network. For more information about multicast VPN, see IP Multicast Configuration Guide .
MP-BGP extended attributes
Prefixes and next hops are key routing information. BGP-4 uses update messages to carry the following information:
•
Feasible route prefixes in the Network Layer Reachability Information (NLRI) field.
•
Unfeasible route prefixes in the withdrawn routes field.
•
Next hops in the NEXT_HOP attribute.
BGP-4 cannot carry routing information for multiple network layer protocols.
To support multiple network layer protocols, MP-BGP defines the following path attributes:
•
MP_REACH_NLRI —Carries feasible route prefixes and next hops for multiple network layer protocols.
•
MP_UNREACH_NLRI —Carries unfeasible route prefixes for multiple network layer protocols.
204
MP-BGP uses these two attributes to advertise feasible and unfeasible routes for different network layer protocols. BGP speakers not supporting MP-BGP ignore updates containing these attributes and do not forward them to its peers.
Address family
MP-BGP uses address families and subsequent address families to identify different network layer protocols for routes contained in the MP_REACH_NLRI and MP_UNREACH_NLRI attributes. For example, an Address Family Identifier (AFI) of 2 and a Subsequent Address Family Identifier (SAFI) of 1 identify IPv6 unicast routing information carried in the MP_REACH_NLRI attribute. For address family values, see RFC 1700.
BGP multi-instance
A BGP router can run multiple BGP processes. Each BGP process corresponds to a BGP instance.
BGP maintains an independent routing table for each BGP instance.
You can create multiple public address families for a BGP instance. However, each public address family (except for public IPv4 unicast, public IPv6 unicast, public VPNv4, and public VPNv6 address families) can belong to only one BGP instance.
You can create multiple VPN instances for a BGP instance, and each VPN instance can have multiple address families. A VPN instance can belong to only one BGP instance.
Different BGP instances can have the same AS number but cannot have the same name.
BGP configuration views
BGP uses different views to manage routing information for different BGP instances, address families, and VPN instances. Most BGP commands are available in all BGP views. BGP supports multiple VPN instances by establishing a separate routing table for each VPN instance.
Table 16 describes different BGP configuration views.
Table 16 BGP configuration views
View names
BGP instance view
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
Ways to enter the views Remarks
You can create a BGP instance and enter its view by specifying the instance keyword in the bgp command.
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc]
Configurations in this view apply to all public address families for the specified BGP instance and all VPN instances (such as confederation,
GR, and logging configurations), or apply to all public address families for the specified BGP instance.
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv4 unicast
Configurations in this view apply to public IPv4 unicast routes and peers of the specified BGP instance.
[Sysname-bgp-abc-ipv4]
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv6 unicast
Configurations in this view apply to public IPv6 unicast routes and peers of the specified BGP instance.
[Sysname-bgp-abc-ipv6]
205
View names
BGP IPv4 multicast address family view
BGP IPv6 multicast address family view
BGP VPNv4 address family view
BGP VPNv6 address family view
BGP L2VPN address family view
BGP EVPN address family view
BGP-VPN instance view
BGP-VPN IPv4 unicast address family view
Ways to enter the views Remarks
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv4 multicast
Configurations in this view apply to
IPv4 multicast routes and peers of the specified BGP instance.
[Sysname-bgp-abc-mul-ipv4]
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv6 multicast
Configurations in this view apply to
IPv6 multicast routes and peers of the specified BGP instance.
[Sysname-bgp-abc-mul-ipv6]
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
VPNv4 routes and peers of the specified BGP instance.
[Sysname-bgp-abc] address-family vpnv4
[Sysname-bgp-abc-vpnv4]
For more information about BGP
VPNv4 address family view, see
MPLS Configuration Guide .
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
VPNv6 routes and peers of the specified BGP instance.
[Sysname-bgp-abc] address-family vpnv6
[Sysname-bgp-abc-vpnv6]
For more information about BGP
VPNv6 address family view, see
MPLS Configuration Guide .
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
L2VPN information and L2VPN peers of the specified BGP instance.
[Sysname-bgp-abc] address-family l2vpn
[Sysname-bgp-abc-l2vpn]
For more information about BGP
L2VPN address family view, see
MPLS Configuration Guide .
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
EVPN routes and peers of the specified BGP instance.
[Sysname-bgp-abc] address-family l2vpn evpn
[Sysname-bgp-abc-evpn]
For more information about BGP
EVPN address family view, see
EVPN Configuration Guide .
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] ip vpn-instance vpn1
Configurations in this view apply to all address families in the specified
VPN instance of the specified BGP instance.
[Sysname-bgp-abc-vpn1]
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] ip vpn-instance vpn1
[Sysname-bgp-abc-vpn1] address-family ipv4 unicast
Configurations in this view apply to
IPv4 unicast routes and peers in the specified VPN instance of the specified BGP instance.
[Sysname-bgp-abc-ipv4-vpn1]
206
View names
BGP-VPN IPv6 unicast address family view
BGP-VPN VPNv4 address family view
Ways to enter the views Remarks
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] ip vpn-instance vpn1
[Sysname-bgp-abc-vpn1] address-family ipv6 unicast
Configurations in this view apply to
IPv6 unicast routes and peers in the specified VPN instance of the specified BGP instance.
[Sysname-bgp-abc-ipv6-vpn1]
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] ip vpn-instance vpn1
Configurations in this view apply to
VPNv4 routes and peers in the specified VPN instance of the specified BGP instance.
[Sysname-bgp-abc-vpn1] address-family vpnv4
[Sysname-bgp-abc-vpnv4-vpn1]
For more information about
BGP-VPN VPNv4 address family view, see MPLS Configuration
Guide .
BGP MDT address family view
BGP LS address family view
BGP IPv4 RT filter address family view
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
MDT routes and peers of the specified BGP instance.
[Sysname-bgp-abc] address-family ipv4 mdt
[Sysname-bgp-abc-mdt]
For more information about BGP
MDT address family view, see IP
Multicast Configuration Guide .
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family link-state
Configurations in this view apply to
LS messages and peers of the specified BGP instance.
[Sysname-bgp-abc-ls]
<Sysname> system-view
[Sysname] bgp 100 instance abc
Configurations in this view apply to
IPv4 RT filter routes and peers of the specified BGP instance.
[Sysname-bgp-abc] address-family ipv4 rtfilter
[Sysname-bgp-abc-rtf-ipv4]
For more information about BGP
IPv4 RT filter address family view, see MPLS Configuration Guide .
Protocols and standards
•
RFC 1700, ASSIGNED NUMBERS
•
RFC 1771, A Border Gateway Protocol 4 (BGP-4)
•
RFC 1997, BGP Communities Attribute
•
RFC 2439, BGP Route Flap Damping
•
RFC 2796, BGP Route Reflection
•
RFC 2858, Multiprotocol Extensions for BGP-4
•
RFC 2918, Route Refresh Capability for BGP-4
•
RFC 3065, Autonomous System Confederations for BGP
•
RFC 3392, Capabilities Advertisement with BGP-4
•
RFC 4271, A Border Gateway Protocol 4 (BGP-4)
•
RFC 4360, BGP Extended Communities Attribute
•
RFC 4724, Graceful Restart Mechanism for BGP
•
RFC 4760, Multiprotocol Extensions for BGP-4
207
•
RFC 5082, The Generalized TTL Security Mechanism (GTSM)
•
RFC 6037, Cisco Systems' Solution for Multicast in BGP MPLS IP VPNs
BGP configuration task list
On a basic BGP network, perform the following configuration tasks:
•
Enable BGP.
•
Configure BGP peers or peer groups. If you configure a BGP setting at both the peer group and the peer level, the most recent configuration takes effect on the peer.
•
Control BGP route generation.
To control BGP route distribution and path selection, you must perform additional configuration tasks.
To configure BGP, perform the following tasks (IPv4 unicast/IPv4 multicast):
Remarks Tasks at a glance
•
•
(Required.) Perform one of the following tasks:
•
(Optional.) Specifying the source address of TCP connections
Perform at least one of the following tasks to generate BGP routes:
•
•
(Optional.) Controlling route distribution and reception :
•
Configuring BGP route summarization
•
Advertising optimal routes in the IP routing table
•
Advertising a default route to a peer or peer group
•
Configuring BGP to first send updates of the default route
•
Limiting routes received from a peer or peer group
•
Configuring BGP route filtering policies
•
Setting the BGP route sending rate
•
Configuring BGP route update delay
•
Configuring a startup policy for BGP route updates
•
Configuring BGP route dampening
(Optional.) Controlling BGP path selection :
•
Setting a preferred value for routes received
•
Configuring preferences for BGP routes
•
Configuring the default local preference
•
•
Configuring the NEXT_HOP attribute
•
Configuring the AS_PATH attribute
•
Ignoring IGP metrics during optimal route selection
•
As a best practice, configure BGP peer groups on large scale
BGP networks for easy configuration and maintenance.
N/A
BGP cannot advertise optimal routes in the IP routing table for IPv4 multicast address family.
N/A
208
Tasks at a glance Remarks
(Optional.) Tuning and optimizing BGP networks :
•
Configuring the keepalive interval and hold time
•
Setting the session retry timer
•
Configuring the interval for sending updates for the same route
•
Enabling BGP to establish an EBGP session over multiple hops
Enabling immediate re-establishment of direct EBGP connections upon link failure
•
•
Enabling 4-byte AS number suppression
•
Enabling MD5 authentication for BGP peers
•
Enabling keychain authentication for BGP peers
•
Configuring BGP load balancing
•
Configuring IPsec for IPv6 BGP
•
Disabling BGP to establish a session to a peer or peer group
•
•
•
Protecting an EBGP peer when memory usage reaches level 2 threshold
•
Configuring an update delay for local MPLS labels
•
Flushing the suboptimal BGP route to the RIB
•
Setting a DSCP value for outgoing BGP packets
Disabling route recursion policy control for routes received from a peer or peer group
•
Enabling per-prefix label allocation
•
Disabling optimal route selection for labeled routes without tunnel information
N/A
(Optional.) Configuring a large-scale BGP network :
•
•
Configuring BGP route reflection
•
Configuring a BGP confederation
(Optional.) Configuring BGP GR
N/A
N/A
(Optional.) Configuring BGP NSR
(Optional.) Enabling SNMP notifications for BGP
(Optional.) Enabling logging for session state changes
(Optional.) Enabling logging for BGP route flapping
(Optional.) Configuring BFD for BGP
(Optional.) Configuring BGP FRR
(Optional.) Configuring BGP LS
To configure BGP, perform the following tasks (IPv6 unicast/IPv6 multicast):
N/A
N/A
N/A
N/A
N/A
N/A
BGP does not support
FRR for IPv4 multicast routes.
N/A
N/A
209
Tasks at a glance
•
•
(Required.) Perform one of the following tasks:
•
(Optional.) Specifying the source address of TCP connections
Perform at least one of the following tasks to generate BGP routes:
•
•
(Optional.) Controlling route distribution and reception :
•
Configuring BGP route summarization
•
Advertising optimal routes in the IP routing table
•
Advertising a default route to a peer or peer group
•
Configuring BGP to first send updates of the default route
•
Limiting routes received from a peer or peer group
•
Configuring BGP route filtering policies
•
Setting the BGP route sending rate
•
Configuring BGP route update delay
•
Configuring a startup policy for BGP route updates
•
Configuring BGP route dampening
(Optional.) Controlling BGP path selection :
•
Setting a preferred value for routes received
•
Configuring preferences for BGP routes
•
Configuring the default local preference
•
•
Configuring the NEXT_HOP attribute
•
Configuring the AS_PATH attribute
•
Remarks
As a best practice, configure BGP peer groups on large scale
BGP networks for easy configuration and maintenance.
N/A
BGP cannot advertise optimal routes in the IP routing table for IPv6 multicast address family.
N/A
210
Tasks at a glance Remarks
(Optional.) Tuning and optimizing BGP networks :
•
Configuring the keepalive interval and hold time
•
Setting the session retry timer
•
Configuring the interval for sending updates for the same route
•
Enabling BGP to establish an EBGP session over multiple hops
Enabling immediate re-establishment of direct EBGP connections upon link failure
•
•
Enabling 4-byte AS number suppression
•
Enabling MD5 authentication for BGP peers
•
Enabling keychain authentication for BGP peers
•
Configuring BGP load balancing
•
Configuring IPsec for IPv6 BGP
•
Disabling BGP to establish a session to a peer or peer group
•
•
•
Protecting an EBGP peer when memory usage reaches level 2 threshold
•
Configuring an update delay for local MPLS labels
•
Flushing the suboptimal BGP route to the RIB
•
Setting a DSCP value for outgoing BGP packets
Disabling route recursion policy control for routes received from a peer or peer group
•
Enabling per-prefix label allocation
•
Disabling optimal route selection for labeled routes without tunnel information
N/A
(Optional.) Configuring a large-scale BGP network :
•
•
Configuring BGP route reflection
•
Configuring a BGP confederation
(Optional.) Configuring BGP GR
N/A
N/A
(Optional.) Configuring BGP NSR
(Optional.) Enabling SNMP notifications for BGP
(Optional.) Enabling logging for session state changes
(Optional.) Enabling logging for BGP route flapping
(Optional.) Configuring BFD for BGP
(Optional.) Configuring BGP FRR
(Optional.) Configuring BGP LS
N/A
N/A
N/A
N/A
N/A
BGP does not support
FRR for IPv6 multicast routes.
IPv6 multicast does not support 6PE.
N/A
Configuring basic BGP
This section describes the basic settings required for a BGP network to run.
211
Enabling BGP
A router ID is the unique identifier of a BGP router in an AS.
•
To ensure the uniqueness of a router ID and enhance availability, specify in BGP instance view the IP address of a local loopback interface as the router ID. Different BGP instances can have the same router ID.
•
If no router ID is specified in BGP instance view, the global router ID is used.
•
To modify a non-zero router ID of a BGP instance , use the router-id command in BGP instance view, rather than the router id command in system view.
•
If you specify a router ID in BGP instance view and then remove the interface that owns the router ID, the router does not select a new router ID. To select a new router ID, use the undo router-id command in BGP instance view.
To enable BGP:
Step
1. Enter system view.
Command system-view
2. Configure a global router ID.
router id router-id
3. Enable BGP and enter BGP instance view.
4. (Optional.) Configure an
SNMP context for the BGP instance.
bgp as-number [ instance instance-name ] snmp context-name
context-name
Remarks
N/A
By default, no global router ID is configured, and BGP uses the highest loopback interface IP address—if any—as the router ID. If no loopback interface IP address is available, BGP uses the highest physical interface IP address as the route ID regardless of the interface status.
By default, BGP is disabled and no
BGP instances exist.
By default, no SNMP context is configured for a BGP instance.
5. (Optional.) Configure a router ID for the BGP instance.
6. (Optional.) Enter BGP-VPN instance view.
7. (Optional.) Configure a router ID for the BGP VPN instance.
router-id router-id ip vpn-instance
vpn-instance-name
router-id { router-id | auto-select }
By default, no router ID is configured for a BGP instance, and the BGP instance uses the global router ID configured by the router-id command in system view.
The specified VPN instance must have been created and have an RD.
For more information about VPN instances, see MPLS Configuration
Guide .
By default, no router ID is configured for a BGP VPN instance, and the BGP VPN instance uses the router ID configured in BGP instance view. If no router ID is configured in BGP instance view, the BGP VPN instance uses the global router ID configured in system view.
212
Configuring a BGP peer
Configuring a BGP peer (IPv4 unicast address family)
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Create an IPv4 BGP peer and specify its AS number.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
peer ipv4-address as-number as-number
4. (Optional.) Configure a description for a peer.
peer ipv4-address description
text
5. Create the BGP IPv4 unicast address family or BGP-VPN
IPv4 unicast address family and enter its view.
6. Enable the router to exchange IPv4 unicast routing information with the specified peer.
address-family ipv4 [ unicast ]
peer ipv4-address enable
Configuring a BGP peer (IPv6 unicast address family)
Remarks
N/A
N/A
By default, no IPv4 BGP peers exist.
By default, no description is configured for a peer.
By default, no BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information with the peer.
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Create an IPv6 BGP peer and specify its AS number.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
peer ipv6-address as-number as-number
4. (Optional.) Configure a description for a peer.
peer ipv6-address description
text
5. Create the BGP IPv6 unicast address family or BGP-VPN
IPv6 unicast address family and enter its view.
address-family ipv6 [ unicast ]
Remarks
N/A
N/A
By default, no IPv6 BGP peers exist.
By default, no description is configured for a peer.
By default, no BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family exists.
213
Step
6. Enable the router to exchange IPv6 unicast routing information with the specified peer.
Command
peer ipv6-address enable
Configuring a BGP peer (IPv4 multicast address family)
Step
1. Enter system view.
2. Enter BGP instance view
Command system-view bgp as-number [ instance instance-name ]
3. Create an IPv4 BGP peer and specify its AS number.
peer ipv4-address as-number as-number
4. (Optional.) Configure a description for the peer.
peer ipv4-address description
text
5. Create the BGP IPv4 multicast address family and enter its view.
6. Enable the router to exchange IPv4 unicast routing information used for
RPF check with the specified peer.
address-family ipv4 multicast
peer ipv4-address enable
Configuring a BGP peer (IPv6 multicast address family)
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Create an IPv6 BGP peer and specify its AS number.
peer ipv6-address as-number as-number
4. (Optional.) Configure a description for the peer.
peer ipv6-address description
text
5. Create the BGP IPv6 multicast address family and enter its view.
6. Enable the router to exchange IPv6 unicast routing information used for
RPF check with the specified peer.
address-family ipv6 multicast
peer ipv6-address enable
Remarks
By default, the router cannot exchange IPv6 unicast routing information with the peer.
Remarks
N/A
N/A
By default, no IPv4 BGP peers exist.
By default, no description is configured for a peer.
By default, no BGP IPv4 multicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information used for RPF check with the peer.
Remarks
N/A
N/A
By default, no IPv6 BGP peers exist.
By default, no description is configured for a peer.
By default, no BGP IPv6 multicast address family exist.
By default, the router cannot exchange IPv6 unicast routing information used for RPF check with the peer.
Configuring dynamic BGP peers
This feature enables BGP to establish dynamic BGP peer relationships with devices in a network.
BGP accepts connection requests from the network but it does not initiate connection requests to the network.
After a device in the network initiates a connection request, BGP establishes a dynamic peer relationship with the device.
214
If multiple BGP peers reside in the same network, you can use this feature to simplify BGP peer configuration.
For a remote device to establish a peer relationship with the local device, you must specify the IP address of the local device on the remote device.
Configuring dynamic BGP peers (IPv4 unicast address family)
Step
1. Enter system view.
2. Enter BGP instance view or BGP-VPN instance view.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Specify devices in a network as dynamic BGP peers and specify an AS number for the peers.
4. (Optional.) Configure a description for dynamic
BGP peers.
peer ipv4-address mask-length
as-number as-number peer ipv4-address mask-length description text
5. Create the BGP IPv4 unicast address family or
BGP-VPN IPv4 unicast address family and enter its view.
6. Enable BGP to exchange
IPv4 unicast routing information with dynamic
BGP peers in the specified network.
address-family ipv4 [ unicast ]
peer ipv4-address mask-length enable
Configuring dynamic BGP peers (IPv6 unicast address family)
Remarks
N/A
N/A
By default, no dynamic BGP peers exist.
By default, no description is configured for dynamic BGP peers.
By default, no BGP IPv4 unicast address family or
BGP-VPN IPv4 unicast address family exists.
By default, BGP cannot exchange IPv4 unicast routing information with dynamic BGP peers.
Step
1. Enter system view.
2. Enter BGP instance view or BGP-VPN instance view.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Specify devices in a network as dynamic BGP peers and specify an AS number for the peers.
peer ipv6-address prefix-length as-number as-number
4. (Optional.) Configure a description for dynamic
BGP peers.
peer ipv6-address prefix-length description text
Remarks
N/A
N/A
By default, no dynamic BGP peers exist.
By default, no description is configured for dynamic BGP peers.
215
Step
5. Create the BGP IPv6 unicast address family or
BGP-VPN IPv6 unicast address family and enter its view.
6. Enable BGP to exchange
IPv6 unicast routing information with dynamic
BGP peers in the specified network.
Command address-family ipv6 [ unicast ]
peer ipv6-address prefix-length enable
Configuring dynamic BGP peers (IPv4 multicast address family)
Remarks
By default, no BGP IPv6 unicast address family or
BGP-VPN IPv6 unicast address family exists.
By default, BGP cannot exchange IPv6 unicast routing information with dynamic BGP peers.
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Specify devices in a network as dynamic BGP peers and specify an AS number for the peers.
peer ipv4-address mask-length
as-number as-number
4. (Optional.) Configure a description for dynamic
BGP peers.
peer ipv4-address mask-length description text
5. Create the BGP IPv4 multicast address family and enter its view.
6. Enable BGP to exchange
IPv4 unicast routing information used for RPF check with dynamic BGP peers in the specified network.
address-family ipv4 multicast
peer ipv4-address mask-length enable
Configuring dynamic BGP peers (IPv6 multicast address family)
Remarks
N/A
N/A
By default, no dynamic BGP peers exist.
By default, no description is configured for dynamic BGP peers.
By default, no BGP IPv4 multicast address family exists.
By default, BGP cannot exchange IPv4 unicast routing information used for RPF check with dynamic BGP peers.
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Specify devices in a network as dynamic BGP peers and specify an AS number for the peers.
4. (Optional.) Configure a description for dynamic BGP peers.
peer ipv6-address prefix-length as-number as-number peer ipv6-address prefix-length description text
5. Create the BGP IPv6 multicast address family and enter its view.
address-family ipv6 multicast
Remarks
N/A
N/A
By default, no dynamic BGP peers exist.
By default, no description is configured for dynamic BGP peers.
By default, no BGP IPv6 multicast address family exists.
216
Step
6. Enable BGP to exchange
IPv6 unicast routing information used for RPF check with dynamic BGP peers in the specified network.
Command
peer ipv6-address prefix-length enable
Remarks
By default, BGP cannot exchange IPv6 unicast routing information used for RPF check with dynamic BGP peers.
Configuring a BGP peer group
The peers in a peer group use the same route selection policy.
In a large-scale network, many peers can use the same route selection policy. You can configure a peer group and add these peers into this group. When you change the policy for the group, the modification also applies to the peers in the group.
A peer group is an IBGP peer group if peers in it belong to the local AS, and is an EBGP peer group if peers in it belong to different ASs.
Configuring an IBGP peer group
After you create an IBGP peer group and then add a peer into it, the system creates the peer in BGP instance view and specifies the local AS number for the peer.
To configure an IBGP peer group (IPv4 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Create an IBGP peer group.
group group-name [ internal ]
By default, no IBGP peer groups exist.
4. Add a peer into the IBGP peer group.
peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peer exists in the peer group.
The as-number as-number option must specify the local AS number.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv4 unicast address family or BGP-VPN
IPv4 unicast address family and enter its view.
7. Enable the router to exchange IPv4 unicast routing information with peers in the specified peer group.
peer group-name description
text address-family ipv4 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information with the peers.
217
To configure an IBGP peer group (IPv6 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Create an IBGP peer group.
group group-name [ internal ]
By default, no IBGP peer groups exist.
4. Add a peer into the IBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peer exists in the peer group.
The as-number as-number option must specify the local AS number.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv6 unicast address family or BGP-VPN
IPv6 unicast address family and enter its view.
7. Enable the router to exchange IPv6 unicast routing information with peers in the specified peer group.
peer group-name description
text address-family ipv6 [ unicast ]
peer group-name enable
To configure an IBGP peer group (IPv4 multicast address family):
By default, no description is configured for the peer group.
By default, no BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information with the peers.
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
N/A
3.
4.
Create an IBGP peer group.
Add an IPv4 peer into the
IBGP peer group.
group group-name [ internal ]
By default, no IBGP peer groups exist. peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peer exists in the peer group.
The as-number as-number option must specify the local AS number.
5. (Optional.) Configure a description for the peer group.
peer
text group-name description By default, no description is configured for the peer group.
218
Step
6. Create the BGP IPv4 multicast address family and enter its view.
Command address-family ipv4 multicast
Remarks
By default, no BGP IPv4 multicast address family exists.
7. Enable the router to exchange IPv4 unicast routing information used for
RPF check with peers in the specified peer group.
peer group-name enable
To configure an IBGP peer group (IPv6 multicast address family):
By default, the router cannot exchange IPv4 unicast routing information used for RPF check with the peers in the peer group.
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Create an IBGP peer group.
group group-name [ internal ]
By default, no IBGP peer groups exist.
4. Add a peer into the IBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peer exists in the peer group.
The as-number as-number option must specify the local AS number.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv6 multicast address family and enter its view.
7. Enable the router to exchange IPv6 unicast routing information used for
RPF check with peers in the specified peer group.
Configuring an EBGP peer group peer group-name description
text address-family ipv6 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 multicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information used for RPF check with the peers in the peer group.
If peers in an EBGP group belong to the same external AS, the EBGP peer group is a pure EBGP peer group. If not, it is a mixed EBGP peer group.
Use one of the following methods to configure an EBGP peer group:
•
Method 1 —Create an EBGP peer group, specify its AS number, and add peers into it. All the added peers have the same AS number. All peers in the peer group have the same AS number as the peer group. You can specify an AS number for a peer before adding it into the peer group.
The AS number must be the same as that of the peer group.
•
Method 2 —Create an EBGP peer group, specify an AS number for a peer, and add the peer into the peer group. Peers added in the group can have different AS numbers.
•
Method 3 —Create an EBGP peer group and add a peer with an AS number into it. Peers added in the group can have different AS numbers.
To configure an EBGP peer group by using Method 1 (IPv4 unicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
219
Step
2. Enter BGP instance view or
BGP-VPN instance view.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
3. Create an EBGP peer group.
group group-name external
By default, no EBGP peer groups exist.
4. Specify the AS number of the group.
peer group-name as-number as-number
By default, no AS number is specified.
If a peer group contains peers, you cannot remove or change its
AS number.
5. Add a peer into the EBGP peer group.
peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer
group-name as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv4 unicast address family or BGP-VPN
IPv4 unicast address family and enter its view.
8. Enable the router to exchange IPv4 unicast routing information with peers in the specified peer group.
peer group-name description
text address-family ipv4 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information with the peers.
To configure an EBGP peer group by using Method 1 (IPv6 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Create an EBGP peer group.
group group-name external
By default, no EBGP peer groups exist.
220
Step Command
4. Specify the AS number of the group.
peer group-name as-number as-number
Remarks
By default, no AS number is specified.
If a peer group contains peers, you cannot remove or change its
AS number.
5. Add a peer into the EBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer
group-name as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv6 unicast address family or BGP-VPN
IPv6 unicast address family and enter its view.
8. Enable the router to exchange IPv6 unicast routing information with peers in the specified peer group.
peer group-name description
text address-family ipv6 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information with the peers.
To configure an EBGP peer group by using Method 1 (IPv4 multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
N/A
3. Create an EBGP peer group.
group group-name external
By default, no EBGP peer groups exist.
4. Specify the AS number of the group.
5. Add an IPv4 BGP peer into the EBGP peer group.
peer group-name as-number as-number
By default, no AS number is specified.
If a peer group contains peers, you cannot remove or change its
AS number. peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer
group-name as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv4 multicast address family and enter its view.
peer
text group-name description address-family ipv4 multicast
By default, no description is configured for the peer group.
By default, no BGP IPv4 multicast address family exists.
221
Step
8. Enable the router to exchange IPv4 unicast routing information used for
RPF check with peers in the specified peer group.
Command
peer group-name enable
Remarks
By default, the router cannot exchange IPv4 unicast routing information used for RPF check with the peers in the group.
To configure an EBGP peer group by using Method 1 (IPv6 multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Create an EBGP peer group.
group group-name external
By default, no EBGP peer groups exist.
4. Specify the AS number of the group.
peer group-name as-number as-number
By default, no AS number is specified.
If a peer group contains peers, you cannot remove or change its
AS number.
5. Add an IPv6 BGP peer into the EBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer
group-name as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv6 multicast address family and enter its view.
8. Enable the router to exchange IPv6 unicast routing information used for
RPF check with peers in the specified peer group.
peer group-name description
text address-family ipv6 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 multicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information used for RPF check with the peers in the group.
To configure an EBGP peer group by using Method 2 (IPv4 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
222
Step
4. Create an IPv4 BGP peer and specify its AS number.
Command
3. Create an EBGP peer group.
group group-name external
Remarks
By default, no EBGP peer groups exist. peer ipv4-address [ mask-length ]
as-number as-number
By default, no IPv4 BGP peers exist.
5. Add the peer into the EBGP peer group.
peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer ipv4-address [ mask-length ]
as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv4 unicast address family or BGP-VPN
IPv4 unicast address family and enter its view.
8. Enable the router to exchange IPv4 unicast routing information with peers in the specified peer group.
peer group-name description
text address-family ipv4 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information with the peers.
To configure an EBGP peer group by using Method 2 (IPv6 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3.
4.
Create an EBGP peer group.
Create an IPv6 BGP peer and specify its AS number.
group group-name external
By default, no EBGP peer groups exist. peer ipv6-address [ prefix-length ]
as-number as-number
By default, no IPv6 BGP peers exist.
5. Add the peer into the EBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer ipv4-address [ prefix-length ]
as-number as-number command.
223
Step
6. (Optional.) Configure a description for the peer group.
Command peer group-name description
text
Remarks
By default, no description is configured for the peer group.
7. Create the BGP IPv6 unicast address family or BGP-VPN
IPv6 unicast address family and enter its view.
8. Enable the router to exchange IPv6 unicast routing information with peers in the specified peer group.
address-family ipv6 [ unicast ]
peer group-name enable
By default, no BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information with the peers.
To configure an EBGP peer group by using Method 2 (IPv4 multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3.
4.
Create an EBGP peer group.
Create an IPv4 BGP peer and specify its AS number.
group group-name external
By default, no EBGP peer groups exist. peer ipv4-address [ mask-length ]
as-number as-number
By default, no IPv4 BGP peers exist.
5. Add the peer into the EBGP peer group.
peer ipv4-address [ mask-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer ipv4-address [ mask-length ]
as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv4 multicast address family and enter its view.
8. Enable the router to exchange IPv4 unicast routing information used for
RPF check with peers in the specified peer group.
peer group-name description
text address-family ipv4 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 multicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information used for RPF check with the peers in the group.
To configure an EBGP peer group by using Method 2 (IPv6 multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Create an EBGP peer group.
group group-name external
By default, no EBGP peer groups exist.
224
Step
4. Create an IPv6 BGP peer and specify its AS number.
Command peer ipv6-address [ prefix-length ]
as-number as-number
Remarks
By default, no IPv6 BGP peers exist.
5. Add the peer into the EBGP peer group.
peer ipv6-address [ prefix-length ] group group-name [ as-number as-number ]
By default, no peers exist in the peer group.
The as-number as-number option, if used, must specify the same AS number as the peer ipv6-address [ prefix-length ]
as-number as-number command.
6. (Optional.) Configure a description for the peer group.
7. Create the BGP IPv6 multicast address family and enter its view.
8. Enable the router to exchange IPv6 unicast routing information used for
RPF check with peers in the specified peer group.
peer group-name description
text address-family ipv6 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 multicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information used for RPF check with the peers in the group.
To configure an EBGP peer group by using Method 3 (IPv4 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Create an EBGP peer group. group group-name external
By default, no EBGP peer groups exist.
4. Add a peer into the EBGP peer group. peer ipv4-address [ mask-length ] group group-name as-number as-number
By default, no peers exist in the peer group.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv4 unicast address family or BGP-VPN
IPv4 unicast address family and enter its view.
7. Enable the router to exchange IPv4 unicast routing information with peers in the specified peer group. peer group-name description
text address-family ipv4 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 unicast address family or BGP-VPN IPv4 unicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information with the peers.
225
To configure an EBGP peer group by using Method 3 (IPv6 unicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Create an EBGP peer group. group group-name external
By default, no EBGP peer groups exist.
4. Add a peer into the EBGP peer group. peer ipv6-address [ prefix-length ] group group-name as-number as-number
By default, no peers exist in the peer group.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv6 unicast address family or BGP-VPN
IPv6 unicast address family and enter its view.
7. Enable the router to exchange IPv6 unicast routing information with peers in the specified peer group. peer group-name description
text address-family ipv6 [ unicast ]
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 unicast address family or BGP-VPN IPv6 unicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information with the peers.
To configure an EBGP peer group by using Method 3 (IPv4 multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
N/A
3.
4.
Create an EBGP peer group.
Add an IPv4 BGP peer into the EBGP peer group.
group group-name external
By default, no EBGP peer groups exist. peer ipv4-address [ mask-length ] group group-name as-number as-number
By default, no peers exist in the peer group.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv4 multicast address family and enter its view.
7. Enable the router to exchange IPv4 unicast routing information used for
RPF check with peers in the specified peer group. peer
text group-name description address-family ipv4 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv4 multicast address family exists.
By default, the router cannot exchange IPv4 unicast routing information used for RPF check with the peers.
226
To configure an EBGP peer group by using Method 3 (IPv6 multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
N/A
3. Create an EBGP peer group. group group-name external
By default, no EBGP peer groups exist.
4. Add an IPv6 BGP peer into the EBGP peer group. peer ipv6-address [ prefix-length ] group group-name as-number as-number
By default, no peers exist in the peer group.
5. (Optional.) Configure a description for the peer group.
6. Create the BGP IPv6 multicast address family and enter its view.
7. Enable the router to exchange IPv6 unicast routing information used for
RPF check with peers in the specified peer group. peer group-name description
text address-family ipv6 multicast
peer group-name enable
By default, no description is configured for the peer group.
By default, no BGP IPv6 multicast address family exists.
By default, the router cannot exchange IPv6 unicast routing information used for RPF check with the peers in the group.
Specifying the source address of TCP connections
By default, BGP uses the primary IPv4/IPv6 address of the output interface in the optimal route to a peer or peer group as the source address of TCP connections to the peer or peer group. You can change the source address in the following scenarios:
•
If the peer's IPv4/IPv6 address belongs to an interface indirectly connected to the local router, specify that interface as the source interface for TCP connections on the peer. For example, interface A on the local end is directly connected to interface B on the peer. If you use the peer x.x.x.x as-number as-number command on the local end, and x.x.x.x is not the IPv4 address of interface B, you must do the following: a. Use the peer connect-interface command on the peer. b. Specify the interface whose IPv4 address is x.x.x.x as the source interface.
•
If the source interface fails on a BGP router that has multiple links to a peer, BGP must re-establish TCP connections. To avoid this problem, use a loopback interface as the source interface or use the IP address of a loopback interface as the source address.
•
If the BGP sessions use the IP addresses of different interfaces, specify a source address or source interface for each peer to establish multiple BGP sessions to a router. Specify a source address for each peer if the BGP sessions use the different addresses of the same interface.
Otherwise, the local BGP router might fail to establish a TCP connection to a peer when it uses the optimal route to determine the source address.
To specify the source address of TCP connections (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
227
Step
2. Enter BGP instance view or
BGP-VPN instance view.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Specify the source address of TCP connections to a peer or peer group. peer { group-name | ipv4-address
[ mask-length ] } source-address source-ipv4-address
Remarks
N/A
4. Specify the source interface of TCP connections to a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } connect-interface interface-type interface-number
By default, BGP uses the primary
IPv4 address of the output interface in the optimal route to a peer or peer group as the source address of TCP connections to the peer or peer group.
To specify the source address of TCP connections (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Specify the source IPv6 address of TCP connections to a peer or peer group.
4. Specify the source interface of TCP connections to a peer or peer group.
peer { group-name | ipv6-address
[ prefix-length ] } source-address source-ipv6-address peer { group-name interface-number
| ipv6-address
[ prefix-length ] } connect-interface interface-type
By default, BGP uses the IPv6 address of the output interface in the optimal route to the BGP peer or peer group as the source address of TCP connections to the peer or peer group.
Generating BGP routes
BGP can generate routes in the following ways:
•
Advertise local networks.
•
Redistribute IGP routes.
Injecting a local network
Perform this task to inject a network in the local routing table to the BGP routing table, so BGP can advertise the network to BGP peers. The ORIGIN attribute of BGP routes advertised in this way is
IGP. You can also use a routing policy to control route advertisement.
228
The specified network must be available and active in the local IP routing table.
To inject a local network (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Configure BGP to advertise a local network.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast network ipv4-address
[ mask-length | mask ]
[ route-policy route-policy-name ]
To inject a local network (IPv6 unicast/multicast address family):
Remarks
N/A
N/A
By default, BGP does not advertise local networks.
Step
1. Enter system view.
Command system-view
Remarks
N/A
229
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure BGP to advertise a local network.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast network ipv6-address prefix-length [ route-policy route-policy-name ]
Remarks
N/A
By default, BGP does not advertise local networks.
Redistributing IGP routes
Perform this task to configure route redistribution from an IGP to BGP.
By default, BGP does not redistribute default IGP routes. You can use the default-route imported command to redistribute default IGP routes into the BGP routing table.
Only active routes can be redistributed. To view route state information, use the display ip routing-table protocol or display ipv6 routing-table protocol command.
The ORIGIN attribute of BGP routes redistributed from IGPs is INCOMPLETE.
To configure BGP to redistribute IGP routes (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
230
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Enable route redistribution from the specified IGP into
BGP.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast import-route protocol
[ { process-id | all-processes }
[ allow-direct | med med-value |
route-policy route-policy-name ]
* ]
Remarks
N/A
By default, BGP does not redistribute IGP routes.
4. (Optional.) Enable default route redistribution into BGP.
default-route imported
By default, BGP does not redistribute default routes.
To configure BGP to redistribute IGP routes (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
231
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Enable route redistribution from the specified IGP into
BGP.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast import-route protocol
[ { process-id | all-processes }
[ allow-direct | med med-value |
route-policy route-policy-name ]
* ]
Remarks
N/A
By default, BGP does not redistribute IGP routes.
4. (Optional.) Enable default route redistribution into BGP.
default-route imported
By default, BGP does not redistribute default routes.
Controlling route distribution and reception
This section describes how to control route distribution and reception.
Configuring BGP route summarization
Route summarization can reduce the number of redistributed routes and the routing table size. IPv4
BGP supports automatic route summarization and manual route summarization. Manual summarization takes precedence over automatic summarization. IPv6 BGP supports only manual route summarization.
The output interface of a BGP summary route is Null 0 on the originating router. Therefore, a summary route must not be an optimal route on the originating router. Otherwise, BGP will fail to forward packets matching the route. If a summarized specific route has the same mask as the summary route, but has a lower priority, the summary route becomes the optimal route. To ensure correct packet forwarding, change the priority of the summary or specific route to make the specific route the optimal route.
Configuring automatic route summarization
Automatic route summarization enables BGP to summarize IGP subnet routes redistributed by the import-route command so BGP advertises only natural network routes.
To configure automatic route summarization (IPv4 unicast/multicast address family):
232
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
3. Configure automatic route summarization.
summary automatic
By default, automatic route summarization is not configured.
Configuring manual route summarization
By configuring manual route summarization, you can do the following:
•
Summarize both redistributed routes and routes injected using the network command.
•
Determine the mask length for a summary route.
To configure BGP manual route summarization (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
233
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Create a summary route in the BGP routing table.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast aggregate ipv4-address
{ mask-length | mask } [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
Remarks
N/A
By default, no summary routes are configured.
To configure BGP manual route summarization (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
234
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Create a summary route in the IPv6 BGP routing table.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
Remarks
N/A
By default, no summary routes are configured.
Advertising optimal routes in the IP routing table
By default, BGP advertises optimal routes in the BGP routing table, which may not be optimal in the
IP routing table. This task allows you to advertise BGP routes that are optimal in the IP routing table.
To enable BGP to advertise optimal routes in the IP routing table (IPv4 unicast):
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enable BGP to advertise optimal routes in the IP routing table.
advertise-rib-active
By default, BGP advertises optimal routes in the BGP routing table.
235
Step
4. Enter BGP IPv4 unicast address family view or
BGP-VPN IPv4 unicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: a. ip vpn-instance vpn-instance-name b. address-family ipv4
[ unicast ]
Remarks
N/A
5. Enable BGP to advertise optimal routes in the IP routing table of the address family in the VPN instance.
advertise-rib-active
By default, the setting is the same as that in BGP instance view.
To enable BGP to advertise optimal routes in the IPv6 routing table (IPv6 unicast):
Step
1. Enter system view.
2. Enter BGP instance view.
3. Enable BGP to advertise optimal routes in the IPv6 routing table.
4. Enter BGP IPv6 unicast address family view or
BGP-VPN IPv6 unicast address family view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A advertise-rib-active
By default, BGP advertises optimal routes in the BGP routing table.
•
Enter BGP IPv6 unicast address family view: address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: a. ip vpn-instance vpn-instance-name b. address-family ipv6
[ unicast ]
N/A
5. Enable BGP to advertise optimal routes in the IPv6 routing table of the address family in the VPN instance.
advertise-rib-active
By default, the setting is the same as that in BGP instance view.
Advertising a default route to a peer or peer group
Perform this task to advertise a default BGP route with the next hop being the advertising router to a peer or peer group.
To advertise a default route to a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
236
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
3. Advertise a default route to a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } default-route-advertise
[ route-policy route-policy-name ]
Remarks
N/A
By default, no default route is advertised.
To advertise a default route to a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
237
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
3. Advertise a default route to a peer or peer group.
peer { group-name | ipv6-address
[ prefix-length ] } default-route-advertise
[ route-policy route-policy-name ]
Remarks
N/A
By default, no default route is advertised.
Configuring BGP to first send updates of the default route
About configuring BGP to first send updates of the default route
Typically a BGP router does not first send update messages of the default route to its peers. If the peer relationship is down, the default route cannot be withdrawn first. Traffic interruption might occur.
Perform this task to configure BGP to first send the update message of the default route. This can reduce the traffic interruption time when the peer relationship is down.
As shown in
Figure 60 , Device A and Device B send a default route and large numbers of external
routes to the internal network. After optimal route selection, Device E selects Device A as the egress router to reach the external network. If the peer relationship between Device A and Device C is down,
Device C sends route withdrawal messages to Device E. If the withdrawal message of the default route is not sent first, traffic forwarded through the default route will be interrupted. After you configure this task, traffic can be immediately switched to Device D to reduce traffic interruption time.
238
Figure 60 Network diagram
Internet
Device A Device B
Device C Device D
Device E
Procedure
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Configure BGP to first send updates of the default route. default-route update-first
Remarks
N/A
N/A
By default, BGP does not first send updates of the default route.
Limiting routes received from a peer or peer group
This feature can prevent attacks that send a large number of BGP routes to the router.
If the number of routes received from a peer or peer group exceeds the upper limit, the router takes one of the following actions based on your configuration:
•
Tears down the BGP session to the peer or peer group and does not attempt to re-establish the session.
•
Continues to receive routes from the peer or peer group and generates a log message.
•
Retains the session to the peer or peer group, but it discards excess routes and generates a log message.
•
Tears down the BGP session to the peer or peer group and, after a specific period of time, re-establishes a BGP session to the peer or peer group.
You can specify a percentage threshold for the router to generate a log message. When the ratio of the number of received routes to the maximum number reaches the percentage value, the router generates a log message.
To limit routes that a router can receive from a peer or peer group (IPv4 unicast/multicast address family):
239
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Specify the maximum number of routes that a router can receive from a peer or peer group.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast peer { group-name | ipv4-address
[ mask-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *
Remarks
N/A
N/A
By default, the number of routes that a router can receive from a peer or peer group is not limited.
To limit routes that a router can receive from a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
240
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Specify the maximum number of routes that a router can receive from a peer or peer group.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast peer { group-name | ipv6-address
[ prefix-length ] } route-limit prefix-number [ { alert-only | discard | reconnect reconnect-time } | percentage-value ] *
Remarks
N/A
By default, the number of routes that a router can receive from a peer or peer group is not limited.
Configuring BGP route filtering policies
Configuration prerequisites
Before you configure BGP routing filtering policies, configure the following filters used for route filtering as needed:
•
ACL (see ACL and QoS Configuration Guide ).
•
Prefix list (see " Configuring routing policies ").
•
Routing policy (see " Configuring routing policies ").
•
AS path list (see " Configuring routing policies ").
Configuring BGP route distribution filtering policies
To configure BGP route distribution filtering policies, use the following methods:
•
Use an ACL or prefix list to filter routing information advertised to all peers.
•
Use a routing policy, ACL, AS path list, or prefix list to filter routing information advertised to a peer or peer group.
If you configure multiple filtering policies, apply them in the following sequence:
1. filter-policy export
2. peer filter-policy export
3. peer as-path-acl export
4. peer prefix-list export
241
5. peer route-policy export
Only routes passing all the configured policies can be advertised.
To configure BGP route distribution filtering policies (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
242
Step
3. Configure BGP route distribution filtering policies.
Command
•
Reference an ACL or IP prefix list to filter advertised
BGP routes: filter-policy
{ ipv4-acl-number | prefix-list prefix-list-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ]
•
Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } route-policy route-policy-name export
•
Reference an ACL to filter
BGP routes advertised to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } filter-policy ipv4-acl-number export
•
Reference an AS path list to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } as-path-acl as-path-acl-number export
•
Reference an IPv4 prefix list to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } prefix-list prefix-list-name export
Remarks
Use at least one method.
By default, no BGP distribution filtering policy is configured.
To configure BGP route distribution filtering policies (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
243
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
244
Step
3. Configure BGP route distribution filtering policies.
Command
•
Reference an ACL or IPv6 prefix list to filter advertised
BGP routes: filter-policy
{ ipv6-acl-number | prefix-list ipv6-prefix-name } export [ direct | isisv6 process-id | ospfv3 process-id | ripng process-id
| static ]
•
Reference a routing policy to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } route-policy route-policy-name export
•
Reference an ACL to filter
BGP routes advertised to a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } filter-policy ipv6-acl-number export
•
Reference an AS path list to filter BGP routes advertised to a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } as-path-acl as-path-acl-number export
•
Reference an IPv6 prefix list to filter BGP routes advertised to a peer or peer group peer { group-name | ipv6-address
[ prefix-length ] } prefix-list ipv6-prefix-name export
Configuring BGP route reception filtering policies
Remarks
Use at least one method.
By default, no BGP distribution filtering policy is configured.
You can use the following methods to configure BGP route reception filtering policies:
•
Use an ACL or prefix list to filter routing information received from all peers.
•
Use a routing policy, ACL, AS path list, or prefix list to filter routing information received from a peer or peer group.
If you configure multiple filtering policies, apply them in the following sequence:
1. filter-policy import
2. peer filter-policy import
3. peer as-path-acl import
4. peer prefix-list import
5. peer route-policy import
Only routes passing all the configured policies can be received.
To configure BGP route reception filtering policies (IPv4 unicast/multicast address family):
245
Step
1. Enter system view.
Command Remarks
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Configure BGP route reception filtering policies.
system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number [ instance instance-name ] g. address-family ipv4 multicast
•
Reference an ACL or IP prefix list to filter BGP routes received from all peers: filter-policy { ipv4-acl-number |
prefix-list prefix-list-name } import
•
Reference a routing policy to filter
BGP routes received from a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } route-policy route-policy-name import
•
Reference an ACL to filter BGP routes received from a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } filter-policy
ipv4-acl-number import
•
Reference an AS path list to filter
BGP routes received from a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } as-path-acl
as-path-acl-number import
•
Reference an IPv4 prefix list to filter BGP routes received from a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } prefix-list
prefix-list-name import
N/A
N/A
Use at least one method.
By default, no route reception filtering is configured.
To configure BGP route reception filtering policies (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
246
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure BGP route reception filtering policies.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number [ instance instance-name ] g. address-family ipv6 multicast
•
Reference ACL or IPv6 prefix list to filter BGP routes received from all peers: filter-policy { ipv6-acl-number |
prefix-list ipv6-prefix-name } import
•
Reference a routing policy to filter
BGP routes received from a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } route-policy route-policy-name import
•
Reference an ACL to filter BGP routes received from a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } filter-policy
ipv6-acl-number import
•
Reference an AS path list to filter
BGP routes received from a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } as-path-acl as-path-acl-number import
•
Reference an IPv6 prefix list to filter BGP routes received from a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } prefix-list ipv6-prefix-name import
Remarks
N/A
Use at least one method.
By default, no route reception filtering is configured.
Setting the BGP route sending rate
If a device sends many new routes within a short time period, it might be unable to add the routes to the FIB before the peer device adds them. This might result in traffic forwarding failure. To avoid this problem, you can perform this task to set an appropriate route sending rate for the device.
247
For a device with high performance, you can set a high BGP route sending rate as needed. For a device without high performance, set a relatively low BGP route sending rate as a best practice.
This task applies only to IPv4 unicast routes and IPv6 unicast routes.
To set the BGP route sending rate:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Set the BGP route sending rate.
route-rate-limit rate
N/A
By default, the BGP route sending rate is not set.
Configuring BGP route update delay
Perform this task to configure BGP to delay sending route updates on reboot to reduce traffic loss.
With this feature enabled, BGP redistributes all routes from other neighbors on reboot, selects the optimal route, and then advertises it.
To configure BGP route update delay:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view
bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Configure BGP to delay sending route updates on reboot.
bgp update-delay on-startup seconds
By default, BGP immediately sends route updates on reboot.
4. (Optional.) Configure BGP to immediately send route updates for routes that match a prefix list.
bgp update-delay on-startup
prefix-list prefix-list-name
By default, no prefix list is specified to filter routes.
Use this command when the updates for the specified routes must be sent immediately.
This command is available only to IPv4 prefix lists.
Configuring a startup policy for BGP route updates
About startup policy for BGP route updates
Perform this task to configure BGP to send route updates with the specified attributes within the specified period after reboot.
if Router B restarts and sends route updates before route convergence completes, traffic sent from Router A through Router B might be lost. This feature enables Router B to send route updates with the specified attribute values within the specified period after reboot, so that Router A can forward traffic through Router C.
248
Figure 61 Network diagram
Router B
IP network
Router A
Router C
Procedure
To configure a startup policy for BGP route updates:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view
bgp as-number [ instance instance-name ]
3. Specify the period after reboot within which the startup policy takes effect. bgp apply-policy on-startup
duration seconds
4. Specify a MED attribute. bgp policy on-startup med med-value
Remarks
N/A
N/A
By default, the startup policy does not take effect.
By default, the MED attribute is
4294967295.
Configuring BGP route dampening
Route dampening enables BGP to not select unstable routes as optimal routes. This feature applies to EBGP routes but not to IBGP routes.
If an EBGP peer goes down after you configure this feature, routes coming from the peer are not deleted and they are dampened.
To configure BGP route dampening (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
249
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number [ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Configure BGP route dampening.
dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] *
By default, BGP route dampening is not configured.
To configure BGP route dampening (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure IPv6 BGP route dampening.
Command system-view
•
Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number [ instance instance-name ] g. address-family ipv6 multicast dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling | route-policy route-policy-name ] *
Remarks
N/A
N/A
By default, IPv6 BGP route dampening is not configured.
250
Controlling BGP path selection
By configuring BGP path attributes, you can control BGP path selection.
Setting a preferred value for routes received
Perform this task to set a preferred value for specific routes to control BGP path selection.
Among multiple routes that have the same destination/mask and are learned from different peers, the one with the greatest preferred value is selected as the optimal route.
To set a preferred value for routes from a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Set a preferred value for routes received from a peer or peer group.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast peer { group-name | ipv4-address
[ mask-length ] } preferred-value value
Remarks
N/A
N/A
The default preferred value is 0.
To set a preferred value for routes from a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
251
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Set a preferred value for routes received from a peer or peer group.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast peer { group-name | ipv6-address
[ prefix-length ] } preferred-value value
Remarks
N/A
The default preferred value is 0.
Configuring preferences for BGP routes
Routing protocols each have a default preference. If they find multiple routes destined for the same network, the route found by the routing protocol with the highest preference is selected as the optimal route.
You can use the preference command to modify preferences for EBGP, IBGP, and local BGP routes, or use a routing policy to set a preference for matching routes. For routes not matching the routing policy, the default preference applies.
If a device has an EBGP route and a local BGP route to reach the same destination, it does not select the EBGP route because the EBGP route has a lower preference than the local BGP route by default.
You can use the network short-cut command to configure the EBGP route as a shortcut route that has the same preference as the local BGP route. The EBGP route will more likely become the optimal route.
To configure preferences for BGP routes (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
252
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Configure preferences for
EBGP, IBGP, and local BGP routes.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast preference { external-preference internal-preference local-preference | route-policy route-policy-name }
Remarks
N/A
The default preferences for
EBGP, IBGP, and local BGP routes are 255, 255, and 130.
4. Configure an EBGP route as a shortcut route.
network ipv4-address
[ mask-length | mask ] short-cut
By default, an EBGP route has a preference of 255.
To configure preferences for BGP routes (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
253
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure preferences for
EBGP, IBGP, and local BGP routes.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast preference { external-preference internal-preference local-preference | route-policy route-policy-name }
Remarks
N/A
The default preferences for
EBGP, IBGP, and local BGP routes are 255, 255, and 130.
4. Configure an EBGP route as a shortcut route.
network ipv6-address
prefix-length short-cut
By default, an EBGP route has a preference of 255.
Configuring the default local preference
The local preference is used to determine the optimal route for traffic leaving the local AS. When a
BGP router obtains from several IBGP peers multiple routes to the same destination, but with different next hops, it considers the route with the highest local preference as the optimal route.
This task allows you to specify the default local preference for routes sent to IBGP peers.
To specify the default local preference (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
254
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Configure the default local preference.
default local-preference value
The default local preference is
100.
To specify the default local preference (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
255
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
3. Configure the default local preference.
default local-preference value
The default local preference is
100.
Configuring the MED attribute
BGP uses MED to determine the optimal route for traffic going into an AS. When a BGP router obtains multiple routes with the same destination but with different next hops, it considers the route with the smallest MED value as the optimal route if other conditions are the same.
Configuring the default MED value
To configure the default MED value (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
256
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Configure the default MED value.
default med med-value The default MED value is 0.
To configure the default MED value (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
257
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
3. Configure the default MED value.
default med med-value The default MED value is 0.
Enabling MED comparison for routes from different ASs
This task enables BGP to compare the MEDs of routes from different ASs.
To enable MED comparison for routes from different ASs:
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Enable MED comparison for routes from different ASs.
compare-different-as-med
Enabling MED comparison for routes on a per-AS basis
This task enables BGP to compare the MEDs of routes from an AS.
By default, MED comparison for routes from different ASs is disabled.
258
Figure 62 Route selection based on MED (in an IPv4 network)
AS 400
Router E
10.0.0.0
AS 200
Loop0
3.3.3.3/32
Router A
GE1/0/1
13.1.1.2/24
Router C
Loop0
1.1.1.1/32
GE1/0/1
11.1.1.2/24
GE1/0/1
GE1/0/3 GE1/0/2
AS 300
Router B
GE1/0/1
12.1.1.2/24
Loop0
2.2.2.2/32
AS 100
Router D
As shown in Figure 62 , Router D establishes indirect EBGP peer relationships with Router A, Router
B, and Router C, and learns addresses 1.1.1.1/32, 2.2.2.2/32, and 3.3.3.3/32 through OSPF. The following output shows the routing information on Router D.
Destination/Mask Proto Pre Cost NextHop Interface
1.1.1.1/32 O_INTRA 10 10 11.1.1.2 GE1/0/1
2.2.2.2/32 O_INTRA 10 20 12.1.1.2 GE1/0/2
3.3.3.3/32 O_INTRA 10 30 13.1.1.2 GE1/0/3
Router D learns network 10.0.0.0 from both Router A and Router B. Because the route learned from
Router B has a smaller IGP metric, the route is optimal. The following output shows the BGP routing table on Router D.
Network NextHop MED LocPrf PrefVal Path/Ogn
*>e 10.0.0.0 2.2.2.2 50 0 300 400e
* e 3.3.3.3 50 0 200 400e
When Router D learns network 10.0.0.0 from Router C, it compares the route with the optimal route in its routing table. Because Router C and Router B reside in different ASs, BGP does not compare the MEDs of the two routes. The route from Router C has a smaller IGP metric than the route from
Router B, so the route from Router C becomes optimal. The following output shows the BGP routing table on Router D.
Network NextHop MED LocPrf PrefVal Path/Ogn
*>e 10.0.0.0 1.1.1.1 60 0 200 400e
* e 10.0.0.0 2.2.2.2 50 0 300 400e
* e 3.3.3.3 50 0 200 400e
However, Router C and Router A reside in the same AS, and Router C has a greater MED, so network 10.0.0.0 learned from Router C should not be optimal.
To avoid this problem, you can configure the bestroute compare-med command to enable MED comparison for routes from the same AS on Router D. After that, Router D puts the routes received from each AS into a group, selects the route with the lowest MED from each group, and compares routes from different groups. Network 10.0.0.0 learned from Router B is the optimal route. The following output shows the BGP routing table on Router D.
Network NextHop MED LocPrf PrefVal Path/Ogn
*>e 10.0.0.0 2.2.2.2 50 0 300 400e
* e 3.3.3.3 50 0 200 400e
259
* e 1.1.1.1 60 0 200 400e
To enable MED comparison for routes on a per-AS basis:
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Enable MED comparison for routes on a per-AS basis. bestroute compare-med
By default, MED comparison for routes on a per-AS basis is disabled.
Enabling MED comparison for routes from confederation peers
This task enables BGP to compare the MEDs of routes received from confederation peers. However, if a route received from a confederation peer has an AS number that does not belong to the confederation, BGP does not compare the route with other routes. For example, a confederation has three AS numbers 65006, 65007, and 65009. BGP receives three routes from different confederation peers. The AS_PATH attributes of these routes are 65006 65009, 65007 65009, and 65008 65009, and the MED values of them are 2, 3, and 1. Because the third route's AS_PATH attribute contains
AS number 65008 that does not belong to the confederation, BGP does not compare it with other routes. As a result, the first route becomes the optimal route.
To enable MED comparison for routes from confederation peers:
Remarks
N/A
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Enable MED comparison for routes from confederation peers.
bestroute med-confederation
N/A
By default, MED comparison for routes from confederation peers is disabled.
Configuring the NEXT_HOP attribute
By default, a BGP router does not set itself as the next hop for routes advertised to an IBGP peer or peer group. In some cases, however, you must configure the advertising router as the next hop to ensure that the BGP peer can find the correct next hop.
260
For example, as shown in Figure 63 , Router A and Router B establish an EBGP neighbor
relationship, and Router B and Router C establish an IBGP neighbor relationship. If Router C has no route destined for IP address 1.1.1.1/24, you must configure Router B to set itself 3.1.1.1/24 as the next hop for the network 2.1.1.1/24 advertised to Router C.
Figure 63 NEXT_HOP attribute configuration
AS 100 AS 200
2.1.1.1/24
Router A
1.1.1.1/24 1.1.1.2/24
EBGP
Router B
3.1.1.1/24 3.1.1.2/24
IBGP
Router C
If a BGP router has two peers on a broadcast network, it does not set itself as the next hop for routes
sent to an EBGP peer by default. As shown in Figure 64 , Router A and Router B establish an EBGP
neighbor relationship, and Router B and Router C establish an IBGP neighbor relationship. They are on the same broadcast network 1.1.1.0/24. When Router B sends EBGP routes to Router A, it does not set itself as the next hop by default. However, you can configure Router B to set it (1.1.1.2/24) as the next hop for routes sent to Router A by using the peer next-hop-local command as needed.
Figure 64 NEXT_HOP attribute configuration
AS 100
Router A
1.1.1.1/24
1.1.1.2/24
1.1.1.3/24
Router B
Router C
AS 200
IMPORTANT:
If you have configured BGP load balancing, the router sets itself as the next hop for routes sent to an
IBGP peer or peer group regardless of whether the peer next-hop-local command is configured.
To configure the NEXT_HOP attribute (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
261
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Specify the router as the next hop for routes sent to a peer or peer group. peer { group-name | ipv4-address
[ mask-length ] } next-hop-local
By default, the router sets itself as the next hop for routes sent to an
EBGP peer or peer group.
However, it does not set itself as the next hop for routes sent to an
IBGP peer or peer group.
To configure the NEXT_HOP attribute (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
262
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
3. Specify the router as the next hop for routes sent to a peer or peer group. peer { group-name | ipv6-address
[ prefix-length ] } next-hop-local
By default, the router sets itself as the next hop for routes sent to an
EBGP peer or peer group.
However, it does not set itself as the next hop for routes sent to an
IBGP peer or peer group.
Configuring the AS_PATH attribute
Permitting local AS number to appear in routes from a peer or peer group
In general, BGP checks whether the AS_PATH attribute of a route from a peer contains the local AS number. If yes, it discards the route to avoid routing loops.
In certain network environments (for example, a Hub&Spoke network in MPLS L3VPN), however, the AS_PATH attribute of a route from a peer must be allowed to contain the local AS number.
Otherwise, the route cannot be advertised correctly.
To permit the local AS number to appear in routes from a peer or peer group and specify the appearance times (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
263
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Permit the local AS number to appear in routes from a peer or peer group and set the appearance times.
peer { group-name | ipv4-address
[ mask-length ] } allow-as-loop
[ number ]
By default, the local AS number is not allowed in routes from a peer or peer group.
To permit the local AS number to appear in routes from a peer or peer group and specify the appearance times (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
264
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
3. Permit the local AS number to appear in routes from a peer or peer group and set the appearance times.
peer { group-name | ipv6-address
[ prefix-length ] } allow-as-loop
[ number ]
By default, the local AS number is not allowed in routes from a peer or peer group.
Ignoring the AS_PATH attribute during optimal route selection
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Configure BGP to ignore the
AS_PATH attribute during optimal route selection bestroute as-path-neglect
Advertising a fake AS number to a peer or peer group
Remarks
N/A
N/A
By default, BGP considers
AS_PATH during optimal route selection.
After you move a BGP router from an AS to another AS (from AS 2 to AS 3 for example), you have to modify the AS number of the router on all its EBGP peers. To avoid such modifications, you can configure the router to advertise a fake AS number 2 to its EBGP peers so that the EBGP peers still think that Router A is in AS 2.
To advertise a fake AS number to a peer or peer group (IPv4 unicast/multicast address family):
265
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Advertise a fake AS number to a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } fake-as
as-number
By default, no fake AS number is advertised to a peer or peer group.
This command applies only to
EBGP peers or EBGP peer groups.
To advertise a fake AS number to a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Advertise a fake AS number to a peer or peer group.
Configuring AS number substitution peer { group-name | ipv6-address
[ prefix-length ] } fake-as
as-number
By default, no fake AS number is advertised to a peer or peer group.
This command applies only to
EBGP peers or EBGP peer groups.
IMPORTANT:
Do not configure AS number substitution in normal circumstances. Otherwise, routing loops might occur.
To use EBGP between PE and CE in MPLS L3VPN, VPN sites in different geographical areas should have different AS numbers. Otherwise, BGP discards route updates containing the local AS number.
If two CEs connected to different PEs use the same AS number, you must configure AS number substitution on each PE. This substitution can replace the AS number in route updates originated by the remote CE as its own AS number before advertising them to the connected CE.
266
Figure 65 AS number substitution configuration (in an IPv4 network)
PE 1
AS 100
MPLS backbone
PE 2
EBGP_Update: 10.1.0.0/16
AS_PATH: 800
CE 1
VPNv4_Update: 10.1.0.0/16
RD: 100:1
AS_PATH: 800
CE 2
EBGP_Update: 10.1.0.0/16
AS_PATH: 100, 100
AS 800 AS 800
As shown in Figure 65 , CE 1 and CE 2 use the same AS number 800. To ensure bidirectional
communication between the two sites, configure AS number substitution on PE 2. PE 2 replaces AS
800 with AS 100 for the BGP route update originated from CE 1 before advertising it to CE 2. Perform the same configuration on PE 1.
To configure AS number substitution for a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure AS number substitution for a peer or peer group. peer { group-name | ipv4-address
[ mask-length ] } substitute-as
By default, AS number substitution is not configured.
To configure AS number substitution for a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure AS number substitution for a peer or peer group. peer { group-name | ipv6-address
[ prefix-length ] } substitute-as
By default, AS number substitution is not configured.
267
Removing private AS numbers from updates sent to an EBGP peer or peer group
Private AS numbers are typically used in test networks, and should not be transmitted in public networks. The range of private AS numbers is from 64512 to 65535.
To remove private AS numbers from updates sent to an EBGP peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Configure BGP to remove private AS numbers from the
AS_PATH attribute of updates sent to an EBGP peer or peer group.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A peer { group-name | ipv4-address
[ mask-length ] } public-as-only
By default, BGP updates sent to an EBGP peer or peer group can carry both public and private AS numbers.
This command is applicable only to EBGP peers or peer groups.
To remove private AS numbers from updates sent to an EBGP peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
268
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure BGP to remove private AS numbers from the
AS_PATH attribute of updates sent to an EBGP peer or peer group.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A peer { group-name | ipv6-address
[ prefix-length ] } public-as-only
By default, BGP updates sent to an EBGP peer or peer group can carry both public and private AS numbers.
This command is applicable only to EBGP peers or peer groups.
Ignoring the first AS number of EBGP route updates
By default, BGP checks the first AS number of a received EBGP route update. If the first AS number is neither the AS number of the BGP peer nor a private AS number, the BGP router disconnects the
BGP session to the peer.
To ignore the first AS number of EBGP route updates:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Configure BGP to ignore the first AS number of EBGP route updates.
ignore-first-as
By default, BGP checks the first AS number of EBGP route updates.
Ignoring IGP metrics during optimal route selection
Step
1. Enter system view.
Command system-view
Remarks
N/A
269
Step
2. Enter BGP instance view or
BGP-VPN instance view.
Command
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
3. Configure BGP to ignore
IGP metrics during optimal route selection.
bestroute igp-metric-ignore
By default, BGP considers IGP metrics during optimal route selection. If multiple routes to the same destination are available, BGP selects the route with the smallest IGP metric as the optimal route.
Configuring the SoO attribute
After you configure the SoO attribute for a BGP peer or peer group, BGP adds the SoO attribute into the route updates received from the BGP peer or peer group. In addition, before advertising route updates to the peer or peer group, BGP checks the SoO attribute of the route update against the configured SoO attribute. If they are the same, BGP does not advertise the route updates to the BGP peer or peer group.
To configure the SoO attribute (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
270
Step Command Remarks
3. Configure the SoO attribute for a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } soo site-of-origin
By default, no SoO attribute is configured for a peer or peer group.
To configure the SoO attribute (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Configure the SoO attribute for a peer or peer group.
Command system-view
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } soo site-of-origin
By default, no SoO attribute is configured for a peer or peer group.
Tuning and optimizing BGP networks
This section describes how to tune and optimize BGP networks.
Configuring the keepalive interval and hold time
BGP sends keepalive messages regularly to keep the BGP session between two routers.
If a router receives no keepalive or update message from a peer within the hold time, it tears down the session.
You can configure the keepalive interval and hold time globally or for a peer or peer group. The individual settings take precedence over the global settings.
The actual keepalive interval and hold time are determined as follows:
•
If the hold time settings on the local and peer routers are different, the smaller setting is used. If the hold time is 0, BGP does not send keepalive messages to its peers and never tears down the session.
271
•
If the keepalive interval is not 0, the actual keepalive interval is the smaller one between 1/3 of the hold time and the keepalive interval.
To configure the keepalive interval and hold time (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure the keepalive interval and hold time.
•
Configure the global keepalive interval and hold time:
timer keepalive keepalive hold holdtime
•
Configure the keepalive interval and hold time for a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } timer keepalive keepalive hold
holdtime
Use at least one method.
By default, the keepalive interval is 60 seconds, and hold time is
180 seconds.
The timer command takes effect for new BGP sessions and does not affect existing sessions.
The timers configured with the timer and peer timer commands do not take effect until a session is re-established (for example, a session is reset).
The hold time must be at least three times the keepalive interval.
To configure the keepalive interval and hold time (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
272
Step
3. Configure the keepalive interval and hold time.
Command
•
Configure the global keepalive interval and hold time:
timer keepalive keepalive hold holdtime
•
Configure the keepalive interval and hold time for a peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } timer keepalive keepalive hold
holdtime
Remarks
Use at least one method.
By default, the keepalive interval is 60 seconds, and hold time is
180 seconds.
The timer command takes effect for new BGP sessions and does not affect existing sessions.
The timers configured with the timer and peer timer commands do not take effect until a session is re-established (for example, a session is reset).
The hold time must be at least three times the keepalive interval.
Setting the session retry timer
About setting the session retry timer
To speed up session establishment to a peer or peer group, set a small session retry timer. If the
BGP session flaps, you can set a large session retry timer to reduce the impact and speed up route convergence.
Restrictions and guidelines
The timer set by the peer timer connect-retry command takes precedence over the timer set by the timer connect-retry command.
Procedure
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Set the session retry timer.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name
•
Set the session retry timer for all peers or peer groups:
timer connect-retry retry-time
•
Set the session retry timer for a peer or peer group: peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } timer connect-retry retry-time
Remarks
N/A
N/A
By default, the session retry timer is 32 seconds for a peer or peer group.
273
Configuring the interval for sending updates for the same route
A BGP router sends an update message to its peers when a route is changed. If the route changes frequently, the BGP router keeps sending updates for the same route, resulting route flapping. To prevent this situation, perform this task to configure the interval for sending updates for the same route to a peer or peer group.
To configure the interval for sending the same update to a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure the interval for sending updates for the same route to a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } route-update-interval interval
By default, the interval is 15 seconds for an IBGP peer and 30 seconds for an EBGP peer.
To configure the interval for sending the same update to a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure the interval for sending updates for the same route to a peer or peer group.
peer { group-name | ipv6-address
[ prefix-length ] } route-update-interval interval
By default, the interval is 15 seconds for an IBGP peer and 30 seconds for an EBGP peer.
274
Enabling BGP to establish an EBGP session over multiple hops
To establish an EBGP session, two routers must have a direct physical link and use directly connected interfaces. If no direct link is available, you must use the peer ebgp-max-hop command to enable BGP to establish an EBGP session over multiple hops and specify the maximum hops.
When the BGP GTSM feature is enabled, two peers can establish an EBGP session after passing
GTSM check, regardless of whether the maximum number of hops is reached.
To enable BGP to establish an indirect EBGP session (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Enable BGP to establish an
EBGP session to an indirectly connected peer or peer group and specify the maximum hop count.
peer { group-name | ipv4-address
[ mask-length ] } ebgp-max-hop
[ hop-count ]
By default, BGP cannot establish an EBGP session to an indirectly connected peer or peer group.
To enable BGP to establish an indirect EBGP session (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Enable BGP to establish an
EBGP session to an indirectly connected peer or peer group and specify the maximum hop count.
peer { group-name | ipv6-address
[ prefix-length ] } ebgp-max-hop
[ hop-count ]
By default, BGP cannot establish an EBGP session to an indirectly connected peer or peer group.
275
Enabling immediate re-establishment of direct EBGP connections upon link failure
When the link to a directly connected EBGP peer goes down, the router does not re-establish a session to the peer until the hold time timer expires. This feature enables BGP to immediately recreate the session in that situation. When this feature is disabled, route flapping does not affect
EBGP session state.
To enable immediate re-establishment of direct EBGP connections:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enable immediate re-establishment of direct
EBGP connections upon link failure.
ebgp-interface-sensitive
By default, immediate re-establishment of direct EBGP connections is enabled.
Enabling BGP ORF capabilities
About BGP ORF
BGP Outbound Route Filtering (ORF) saves the system resources by reducing the route updates that are sent between BGP peers.
The BGP peers negotiate the ORF capabilities through Open messages. After completing the negotiation process, the BGP peers can exchange ORF information (local route reception filtering policy) through route refresh messages. Then, only routes that pass both the local route distribution filtering policy and the received route reception filtering policy can be advertised.
Restrictions and guidelines
You can enable the ORF information sending, receiving, or both sending and receiving capabilities on a BGP router. For two BGP peers to successfully negotiate the ORF capabilities, make sure one end has the sending capability and the other end has the receiving capability.
Enabling BGP ORF capabilities
To enable BGP ORF capabilities (IPv4 unicast/IPv4 multicast):
Step
1. Enter system view.
Command system-view
Remarks
N/A
276
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view:
a. bgp as-number [ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view:
c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view:
f. bgp as-number [ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Enable BGP ORF capabilities. peer { group-name | ipv4-address
[ mask-length ] } capability-advertise orf prefix-list { both | receive | send }
By default, BGP ORF capabilities are disabled.
To enable BGP ORF capabilities (IPv6 unicast/IPv6 multicast):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Enable BGP ORF capabilities.
Command system-view
•
Enter BGP IPv6 unicast address family view:
a. bgp as-number [ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number [ instance instance-name ] d. ip vpn-instance
vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view:
f. bgp as-number [ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise orf prefix-list { both | receive | send }
By default, BGP ORF capabilities are disabled.
277
Enabling nonstandard BGP ORF capabilities
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
N/A
3. Enable nonstandard BGP
ORF capabilities. peer { group-name | ip-address
[ mask-length ] | ipv6-address
[ prefix-length ] } capability-advertise orf non-standard
By default, nonstandard BGP ORF capabilities are disabled.
To enable the BGP peers to exchange nonstandard ORF information, you must configure this command together with the peer capability-advertise orf prefix-list command.
Enabling 4-byte AS number suppression
BGP supports 4-byte AS numbers. The 4-byte AS number occupies four bytes, in the range of 1 to
4294967295. By default, a device sends an Open message to the peer device for session establishment. The Open message indicates that the device supports 4-byte AS numbers. If the peer device supports 2-byte AS numbers instead of 4-byte AS numbers, the session cannot be established. To resolve this issue, enable the 4-byte AS number suppression feature. The device then sends an Open message to inform the peer that it does not support 4-byte AS numbers, so the
BGP session can be established.
If the peer device supports 4-byte AS numbers, do not enable the 4-byte AS number suppression feature. Otherwise, the BGP session cannot be established.
To enable 4-byte AS number suppression (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable 4-byte AS number suppression.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv4-address
[ mask-length ] } capability-advertise suppress-4-byte-as
Remarks
N/A
N/A
By default, 4-byte AS number suppression is disabled.
To enable 4-byte AS number suppression (IPv6 unicast/multicast address family):
278
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable 4-byte AS number suppression.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise suppress-4-byte-as
Remarks
N/A
N/A
By default, 4-byte AS number suppression is disabled.
Enabling MD5 authentication for BGP peers
MD5 authentication provides the following benefits:
•
Peer authentication ensures that only BGP peers that have the same password can establish
TCP connections.
•
Integrity check ensures that BGP packets exchanged between peers are intact.
To enable MD5 authentication for BGP peers (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable MD5 authentication for a BGP peer group or peer.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv4-address
[ mask-length ] } password
{ cipher | simple } password
Remarks
N/A
N/A
By default, MD5 authentication is disabled.
To enable MD5 authentication for BGP peers (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
279
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable MD5 authentication for a BGP peer group or peer.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv6-address
[ prefix-length ] } password
{ cipher | simple } password
Remarks
N/A
By default, MD5 authentication is disabled.
Enabling keychain authentication for BGP peers
Keychain authentication enhances the security of TCP connection establishment between BGP peers. It allows BGP peers to establish TCP connections only when the following conditions are met:
•
Keychain authentication is enabled on both BGP peers.
•
The keys used by the BGP peers have the same authentication algorithm and key string.
Before configuring keychain authentication, make sure the specified keychain has been created.
For more information about keychains, see Security Configuration Guide .
To enable keychain authentication for BGP peers (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view of
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
N/A
3. Enable keychain authentication for a BGP peer or peer group. peer { group-name | ip-address
[ mask-length ] } keychain keychain-name
By default, keychain authentication is disabled.
To enable keychain authentication for BGP peers (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
280
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable keychain authentication for a BGP peer or peer group.
Command
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv6-address
[ prefix-length ] } keychain keychain-name
Remarks
N/A
By default, keychain authentication is disabled.
Configuring BGP load balancing
Perform this task to specify the maximum number of BGP ECMP routes for load balancing.
To specify the maximum number of BGP ECMP routes for load balancing (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
3. Specify the maximum number of BGP ECMP routes for load balancing.
4. (Optional.) Enable BGP to ignore the AS_PATH attribute when it implements load balancing.
balance [ ebgp | eibgp | ibgp ]
number balance as-path-neglect
By default, load balancing is disabled.
By default, BGP does not ignore the AS_PATH attribute when it implements load balancing.
281
Step
5. (Optional.) Enable load balancing for routes that have different AS_PATH attributes of the same length.
Command balance as-path-relax
Remarks
By default, BGP cannot perform load balancing for routes that have different AS_PATH attributes of the same length.
To specify the maximum number of BGP ECMP routes for load balancing (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command system-view
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
3. Specify the maximum number of BGP ECMP routes for load balancing.
4. (Optional.) Enable BGP to ignore the AS_PATH attribute when it implements load balancing.
balance
number
[ ebgp | eibgp
5. (Optional.) Enable load balancing for routes that have different AS_PATH attributes of the same length. balance as-path-relax
| ibgp balance as-path-neglect
]
Remarks
N/A
N/A
By default, load balancing is disabled.
By default, BGP does not ignore the AS_PATH attribute when it implements load balancing.
By default, BGP cannot perform load balancing for routes that have different AS_PATH attributes of the same length.
Configuring IPsec for IPv6 BGP
Perform this task to configure IPsec for IPv6 BGP. IPsec can provide privacy, integrity, and authentication for IPv6 BGP packets exchanged between BGP peers.
When two IPv6 BGP peers are configured with IPsec (for example, Device A and Device B), Device
A encapsulates an IPv6 BGP packet with IPsec before sending it to Device B. If Device B successfully receives and de-encapsulates the packet, it establishes an IPv6 BGP peer relationship
282
with Device A and learns IPv6 BGP routes from Device A. If Device B receives but fails to de-encapsulate the packet, or receives a packet not protected by IPsec, it discards the packet.
To configure IPsec for IPv6 BGP packets (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Configure an IPsec transform set and a manual
IPsec profile.
3. Enter BGP instance view or
BGP-VPN instance view.
4. Apply the IPsec profile to an
IPv6 BGP peer or peer group.
Command system-view
Remarks
N/A
See Security Configuration Guide.
By default, no IPsec transform set or manual IPsec profile exists.
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
N/A peer { group-name | ipv6-address
[ prefix-length ] } ipsec-profile profile-name
By default, no IPsec profile is configured for any IPv6 BGP peer or peer group.
This command supports only
IPsec profiles in manual mode.
Disabling BGP to establish a session to a peer or peer group
This task enables you to temporarily tear down the BGP session to a peer or peer group. Then you can perform network upgrade and maintenance without needing to delete and reconfigure the peer or peer group. To recover the session, execute the undo peer ignore command.
To disable BGP to establish a session to a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Disable BGP to establish a session to a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } ignore
By default, BGP can establish a session to a peer or peer group.
To disable BGP to establish a session to a peer or peer group (IPv6 unicast/multicast address family):
283
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Disable BGP to establish a session to a peer or peer group.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } ignore
By default, BGP can establish a session to a peer.
Configuring GTSM for BGP
The Generalized TTL Security Mechanism (GTSM) protects a BGP session by comparing the TTL value in the IP header of incoming BGP packets against a valid TTL range. If the TTL value is within the valid TTL range, the packet is accepted. If not, the packet is discarded.
The valid TTL range is from 255 – the configured hop count + 1 to 255.
When GTSM is configured, the BGP packets sent by the device have a TTL of 255.
GTSM provides best protection for directly connected EBGP sessions, but not for multihop EBGP or
IBGP sessions because the TTL of packets might be modified by intermediate devices.
IMPORTANT:
•
When GTSM is configured, the local device can establish an EBGP session to the peer after both devices pass GTSM check, regardless of whether the maximum number of hops is reached.
•
To use GTSM, you must configure GTSM on both the local and peer devices. You can specify different hop-count values for them.
To configure GTSM for BGP (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
3. Configure GTSM for the specified BGP peer or peer group. peer { group-name | ipv4-address
[ mask-length ] } ttl-security hops hop-count
To configure GTSM for BGP (IPv6 unicast/multicast address family):
By default, GTSM is disabled.
284
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Configure GTSM for the specified BGP peer or peer group.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name peer { group-name | ipv6-address
[ prefix-length ] } ttl-security hops hop-count
Remarks
N/A
N/A
By default, GTSM is disabled.
Configuring BGP soft-reset
After you modify the route selection policy, for example, modify the preferred value, you must reset
BGP sessions to apply the new policy. The reset operation tears down and re-establishes BGP sessions.
To avoid tearing down BGP sessions, you can use one of the following soft-reset methods to apply the new policy:
•
Enabling route-refresh —The BGP router advertises a route-refresh message to the specified peer, and the peer resends its routing information to the router. After receiving the routing information, the router filters the routing information by using the new policy.
This method requires that both the local router and the peer support route refresh.
•
Saving updates —Use the peer keep-all-routes command to save all route updates from the specified peer. After modifying the route selection policy, filter routing information by using the new policy.
This method does not require that the local router and the peer support route refresh but it uses more memory resources to save routes.
•
Manual soft-reset —Use the refresh bgp command to enable BGP to send local routing information or advertise a route-refresh message to the specified peer. The peer then resends its routing information. After receiving the routing information, the router filters the routing information by using the new policy.
This method requires that both the local router and the peer support route refresh.
Enabling route-refresh
To enable BGP route refresh for a peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
285
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable BGP route refresh for a peer or peer group.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
•
Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } capability-advertise route-refresh
•
Enable the BGP route refresh, multi-protocol extension, and 4-byte AS number features for the specified peer or peer group: undo peer { group-name | ipv4-address
[ mask-length ] } capability-advertise conventional
Remarks
N/A
By default, the BGP route refresh, multi-protocol extension, and
4-byte AS number features are enabled.
To enable BGP route refresh for a peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
286
Step
3. Enable BGP route refresh for a peer or peer group.
Command
•
Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise route-refresh
•
Enable the BGP route refresh, multi-protocol extension, and 4-byte AS number features for the specified peer or peer group: undo peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise conventional
Remarks
By default, the BGP route refresh, multi-protocol extension, and
4-byte AS number features are enabled.
Saving updates
To save all route updates from the specified peer or peer group (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
3. Save all route updates from the peer or peer group.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A peer { group-name | ipv4-address
[ mask-length ] } keep-all-routes
By default, the routes are not saved.
This command takes effect only for the routes received after this command is executed.
287
To save all route updates from the specified peer or peer group (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Save all route updates from the peer or peer group.
Command system-view
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } keep-all-routes
By default, the routes are not saved.
This command takes effect only for the routes received after this command is executed.
Configuring manual soft-reset
To configure manual soft-reset (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
288
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable BGP route refresh for a peer or peer group.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
•
Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } capability-advertise route-refresh
•
Enable the BGP route refresh, multi-protocol extension, and 4-byte AS number features for the specified peer or peer group: undo peer { group-name | ipv4-address
[ mask-length ] } capability-advertise conventional
Remarks
N/A
By default, the BGP route refresh, multi-protocol extension, and
4-byte AS number features are enabled.
4. Return to user view.
return N/A
5. Perform manual soft-reset.
refresh bgp [ instance instance-name ] { ipv4-address
[ mask-length ] | all | external |
group group-name | internal }
{ export | import } ipv4
{ multicast | [ unicast ]
[ vpn-instance vpn-instance-name ] }
N/A
To configure manual soft-reset (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
289
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable BGP route refresh for a peer or peer group.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
•
Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise route-refresh
•
Enable the BGP route refresh, multi-protocol extension, and 4-byte AS number features for the specified peer or peer group: undo peer { group-name | ipv6-address
[ prefix-length ] } capability-advertise conventional
Remarks
N/A
By default, the BGP route refresh, multi-protocol extension, and
4-byte AS number features are enabled.
4. Return to user view.
return N/A
5. Perform manual soft-reset.
refresh bgp [ instance instance-name ] { ipv6-address
[ prefix-length ] | all | external |
group group-name | internal }
{ export | import } ipv6
{ multicast | [ unicast ]
[ vpn-instance vpn-instance-name ] }
To configure manual soft-reset (LS address family):
N/A
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
N/A
290
Step
3. Enable BGP route refresh for a peer or peer group.
Command
•
Enable BGP route refresh for the specified peer or peer group: peer { group-name | ipv4-address [ mask-length ] | ipv6-address
[ prefix-length ] } capability-advertise route-refresh
•
Enable the BGP route refresh, multi-protocol extension, and 4-byte AS number features for the specified peer or peer group: undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address
[ prefix-length ] } capability-advertise conventional
Remarks
By default, the BGP route refresh, multi-protocol extension, and
4-byte AS number features are enabled.
4. Return to user view. return N/A
5. Perform manual soft-reset. refresh bgp [ instance instance-name ] { ipv4-address
[ mask-length ] | ipv6-address
[ prefix-length ] | all | external | group group-name | internal }
{ export | import } link-state
N/A
Protecting an EBGP peer when memory usage reaches level
2 threshold
Memory usage includes the following threshold levels: normal, level 1, level 2, and level 3. When the level 2 threshold is reached, BGP periodically tears down an EBGP session to release memory resources until the memory usage falls below the level 2 threshold. You can configure this feature to avoid tearing down the EBGP session to an EBGP peer when the memory usage reaches the level 2 threshold.
For more information about memory usage thresholds, see Fundamentals Configuration Guide .
To configure BGP to protect an EBGP peer or peer group when the memory usage reaches level 2 threshold (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A
291
Step
3. Configure BGP to protect an
EBGP peer or peer group when the memory usage reaches level 2 threshold.
Command peer { group-name | ipv4-address
[ mask-length ] } low-memory-exempt
Remarks
By default, BGP periodically tears down an EBGP session to release memory resources when level 2 threshold is reached.
To configure BGP to protect an EBGP peer or peer group when the memory usage reaches level 2 threshold (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Configure BGP to protect an
EBGP peer or peer group when the memory usage reaches level 2 threshold.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } low-memory-exempt
By default, BGP tears down an
EBGP session to release memory resources periodically when level
2 threshold is reached.
Configuring an update delay for local MPLS labels
BGP includes local MPLS labels in advertised VPNv4 routes, VPNv6 routes, labeled IPv4 unicast routes, and labeled IPv6 unicast routes.
When a local label is changed, BGP removes the old label and advertises the new label. Traffic interruption occurs if BGP peers use the old label to forward packets before they learn the new label.
To resolve this issue, configure an update delay for local MPLS labels. BGP does not remove the old label before the update delay timer expires.
To configure an update delay for local MPLS labels:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Configure an update delay for local MPLS labels.
retain local-label retain-time
N/A
By default, the update delay is 60 seconds.
Flushing the suboptimal BGP route to the RIB
This feature flushes the suboptimal BGP route to the RIB when the following conditions are met:
•
The optimal route is generated by the network command or is redistributed by the import-route command.
•
The suboptimal route is received from a BGP peer.
292
After the suboptimal route is flushed to the RIB on a network, BGP immediately switches traffic to the suboptimal route when the optimal route fails.
For example, the device has a static route to the subnet 1.1.1.0/24 that has a higher priority than a
BGP route. BGP redistributes the static route and receives a route to 1.1.1.0/24 from a peer. After the flush suboptimal-route command is executed, BGP flushes the received BGP route to the RIB as the suboptimal route. When the static route fails, BGP immediately switches traffic to the suboptimal route if inter-protocol FRR is enabled. For more information about inter-protocol FRR, see
" Configuring basic IP routing ."
To flush the suboptimal BGP route to the RIB:
Step
1. Enter system view.
2. Enter BGP view.
Command system-view
bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Flush the suboptimal BGP route to the RIB.
flush suboptimal-route
By default, BGP is disabled from flushing the suboptimal BGP route to the RIB, and only the optimal route is flushed to the RIB.
Setting a DSCP value for outgoing BGP packets
The DSCP value of an IP packet specifies the priority level of the packet and affects the transmission priority of the packet.
To set a DSCP value for outgoing BGP packets:
Step
1. Enter system view.
2. Enter BGP instance view or BGP-VPN instance view.
3. Set a DSCP value for outgoing BGP packets.
Command system-view
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv4-address
[ mask-length ] | ipv6-address
[ prefix-length ] } dscp dscp-value
Remarks
N/A
N/A
By default, the DSCP value for outgoing BGP packets is 48.
Disabling route recursion policy control for routes received from a peer or peer group
If you configure routing policy-based recursive lookup for BGP routes, this route recursion policy applies to BGP routes learned from all peers. This task allows you to disable route recursion policy control for routes learned from certain peers, for example, direct EBGP peers.
To disable route recursion policy control for routes received from a peer or peer group:
Step
1. Enter system view.
Command system-view
Remarks
N/A
293
Step
2. Enter BGP instance view or
BGP-VPN instance view.
3. Disable route recursion policy control for routes received from the specified peer or peer group.
Command
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ip-address
[ mask-length ] | ipv6-address
[ prefix-length ] } nexthop-recursive-policy disable
Enabling per-prefix label allocation
Remarks
N/A
By default, the route recursion policy applies to routes received from the peer or peer group.
CAUTION:
A change to the label allocation mode enables BGP to re-advertise all routes, which will cause service interruption. Use this command with caution.
Perform this task to enable BGP to allocate a label to each route prefix.
To enable per-prefix label allocation:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Enable per-prefix label allocation. label-allocation-mode per-prefix
N/A
By default, BGP allocates labels on a per-next-hop basis.
Disabling optimal route selection for labeled routes without tunnel information
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Disable optimal route selection for labeled routes without tunnel information. labeled-route ignore-no-tunnel
Remarks
N/A
N/A
By default, labeled routes without tunnel information can participate in optimal route selection.
Configuring a large-scale BGP network
In a large network, the number of BGP connections is huge and BGP configuration and maintenance are complicated. To simply BGP configuration, you can use the peer group, community, route
294
reflector, and confederation features as needed. For more information about configuring peer groups,
see " Configuring a BGP peer group ."
Configuring BGP community
By default, a router does not advertise the COMMUNITY or extended community attribute to its peers or peer groups. When the router receives a route carrying the COMMUNITY or extended community attribute, it removes the attribute before advertising the route to other peers or peer groups.
Perform this task to enable a router to advertise the COMMUNITY or extended community attribute to its peers for route filtering and control. You can also use a routing policy to add or modify the
COMMUNITY or extended community attribute for specific routes. For more information about
routing policy, see " Configuring routing policies ."
To configure BGP community (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
295
Step
3. Advertise the COMMUNITY or extended community attribute to a peer or peer group.
Command
•
Advertise the COMMUNITY attribute to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } advertise-community
•
Advertise the extended community attribute to a peer or peer group: peer { group-name | ipv4-address
[ mask-length ] } advertise-ext-community
Remarks
By default, the COMMUNITY or extended community attribute is not advertised.
4. (Optional.) Apply a routing policy to routes advertised to a peer or peer group. peer { group-name | ipv4-address
[ mask-length ] } route-policy route-policy-name export
By default, no routing policy is applied.
To configure BGP community (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command system-view
•
Enter BGP IPv6 unicast address family view: a. bgp as-number [ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number [ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: f. bgp as-number [ instance instance-name ] g. address-family ipv6 multicast
Remarks
N/A
N/A
296
Step
3. Advertise the COMMUNITY or extended community attribute to a peer or peer group.
Command
•
Advertise the COMMUNITY attribute to a peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } advertise-community
•
Advertise the extended community attribute to a peer or peer group: peer { group-name | ipv6-address [ prefix-length ] } advertise-ext-community
4. (Optional.) Apply a routing policy to routes advertised to a peer or peer group. peer { group-name | ipv6-address
[ prefix-length ] } route-policy route-policy-name export
Remarks
By default, the COMMUNITY or extended community attribute is not advertised.
By default, no routing policy is applied.
Configuring BGP route reflection
Configuring a BGP route reflector
Perform this task to configure a BGP route reflector and its clients. The route reflector and its clients automatically form a cluster identified by the router ID of the route reflector. The route reflector forwards route updates among its clients.
To improve availability, you can specify multiple route reflectors for a cluster. The route reflectors in the cluster must have the same cluster ID to avoid routing loops.
To configure a BGP route reflector (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
297
Step
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command
•
Enter BGP IPv4 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view: c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view: f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
3. Configure the router as a route reflector and specify a peer or peer group as its client.
peer { group-name | ipv4-address
[ mask-length ] } reflect-client
By default, no route reflector or client is configured.
4. Enable route reflection between clients.
reflect between-clients
By default, route reflection between clients is enabled.
5. (Optional.) Configure the cluster ID of the route reflector.
reflector cluster-id { cluster-id | ipv4-address }
By default, a route reflector uses its own router ID as the cluster ID.
To configure a BGP route reflector (IPv6 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
298
Step
2. Enter BGP IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
Command
•
Enter BGP IPv6 unicast address family view: a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view: c. bgp as-number
[ instance instance-name ] d. address-family ipv6 multicast
3. Configure the router as a route reflector and specify a peer or peer group as its client.
4. Enable route reflection between clients.
reflect between-clients
Remarks
N/A peer { group-name | ipv6-address
[ prefix-length ] } reflect-client
By default, no route reflector or client is configured.
By default, route reflection between clients is enabled.
5. (Optional.) Configure the cluster ID of the route reflector.
reflector cluster-id { cluster-id | ipv4-address }
Ignoring the ORIGINATOR_ID attribute
By default, a route reflector uses its own router ID as the cluster ID.
By default, BGP drops incoming route updates whose ORIGINATOR_ID attribute is the same as the local router ID. Some special networks require BGP to accept such route updates. To meet the requirement, you must configure BGP to ignore the ORIGINATOR_ID attribute.
To ignore the ORIGINATOR_ID attribute (IPv4 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
N/A
3. Ignore the ORIGINATOR_ID attribute.
peer { group-name | ipv4-address
[ mask-length ] } ignore-originatorid
By default, BGP does not ignore the ORIGINATOR_ID attribute.
Make sure this command does not result in a routing loop.
After you execute this command,
BGP also ignores the
CLUSTER_LIST attribute.
To ignore the ORIGINATOR_ID attribute (IPv6 unicast/multicast address family):
299
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Ignore the ORIGINATOR_ID attribute.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance vpn-instance-name
Remarks
N/A
N/A peer { group-name | ipv6-address
[ prefix-length ] } ignore-originatorid
By default, BGP does not ignore the ORIGINATOR_ID attribute.
Make sure this command does not result in a routing loop.
After you execute this command,
BGP also ignores the
CLUSTER_LIST attribute.
Configuring a BGP confederation
BGP confederation provides another way to reduce IBGP connections in an AS.
A confederation contains sub-ASs. In each sub-AS, IBGP peers are fully meshed. Sub-ASs establish
EBGP connections in between.
Configuring a BGP confederation
After you split an AS into multiple sub-ASs, configure a router in a sub-AS as follows:
1.
Enable BGP and specify the AS number of the router. For more information, see " Enabling
2. Specify the confederation ID. From an outsider's perspective, the sub-ASs of the confederation is a single AS, which is identified by the confederation ID.
3. If the router needs to establish EBGP connections to other sub-ASs, you must specify the peering sub-ASs in the confederation.
A confederation can contain a maximum of 32 sub-ASs. The AS number of a sub-AS is effective only in the confederation.
To configure a BGP confederation:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Configure a confederation
ID.
4. Specify confederation peer sub-ASs in the confederation.
confederation id as-number confederation peer-as as-number-list
By default, no confederation ID is configured.
By default, no confederation peer sub-ASs are specified.
300
Configuring confederation compatibility
If any routers in the confederation do not comply with RFC 3065, enable confederation compatibility to allow the router to work with those routers.
To configure confederation compatibility:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enable confederation compatibility.
confederation nonstandard
By default, confederation compatibility is disabled.
Configuring BGP GR
Graceful Restart (GR) ensures forwarding continuous when a routing protocol restarts or an active/standby switchover occurs. Two routers are required to complete a GR process. The following are router roles in a GR process:
•
GR restarter —Performs GR upon a BGP restart or active/standby switchover.
•
GR helper —Helps the GR restarter to complete the GR process.
A device can act as a GR restarter and GR helper at the same time.
BGP GR works as follows:
1. The BGP GR restarter and helper exchange Open messages for GR capability negotiation. If both parties have the GR capability, they establish a GR-capable session. The GR restarter sends the GR timer set by the graceful-restart timer restart command to the GR helper in an
Open message.
2. When an active/standby switchover occurs or BGP restarts, the GR restarter does not remove existing BGP routes from Routing Information Base (RIB) and Forwarding Information Base
(FIB). It still uses these routes for packet forwarding, and it starts the RIB purge timer (set by the graceful-restart timer purge-time command). The GR helper marks all routes learned from the GR restarter as stale instead of deleting them. It continues to use these routes for packet forwarding. During the GR process, packet forwarding is not interrupted.
3. After the active/standby switchover or BGP restart completes, the GR restarter re-establishes a
BGP session to the GR helper. If the BGP session fails to be established within the GR timer advertised by the GR restarter, the GR helper removes the stale routes.
4. If the BGP session is established, routing information is exchanged for the GR restarter to retrieve route entries and for the GR helper to recover stale routes.
5. Both the GR restarter and the GR helper start the End-Of-RIB marker waiting timer.
The End-Of-RIB marker waiting time is set by the graceful-restart timer wait-for-rib command. If routing information exchange is not completed within the time, the GR restarter does not receive new routes. The GR restarter updates the RIB with the BGP routes already learned, and removes the aged routes from the RIB. The GR helper removes the stale routes.
6. The GR restarter quits the GR process if routing information exchange is not completed within the RIB purge timer. It updates the RIB with the BGP routes already learned, and removes the aged routes.
Follow these guidelines when you configure BGP GR:
•
The End-Of-RIB indicates the end of route updates.
•
The maximum time to wait for the End-of-RIB marker configured on the local end is not advertised to the peer. It controls the time for the local end to receive updates from the peer.
301
As a best practice, perform the following configuration on the GR restarter and GR helper.
To configure BGP GR:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enable GR capability for BGP.
graceful-restart
4. Configure the GR timer.
graceful-restart timer restart timer
5. Configure the maximum time to wait for the End-of-RIB marker.
graceful-restart timer wait-for-rib timer
6. Configure the RIB purge timer.
graceful-restart timer purge-time timer
By default, GR capability is disabled for BGP.
The default setting is 150 seconds.
The time that a peer waits to re-establish a session must be less than the hold time.
The default setting is 180 seconds.
The default setting is 480 seconds.
Configuring BGP NSR
To use BGP nonstop routing (NSR), the system must have a minimum of two MPUs.
NSR ensures nonstop services when BGP has redundant processes on multiple MPUs. In contrast to GR, NSR does not require a neighbor device to recover routing information.
BGP NSR backs up BGP state and data information from the active BGP process to the standby
BGP process. The standby BGP process takes over when any of the following events occurs:
•
The active BGP process restarts.
•
The MPU that runs the active BGP process fails.
•
An ISSU starts on the MPU that runs the active BGP process.
When both GR and NSR are configured for BGP, NSR has a higher priority than GR. The device will not act as the GR restarter. If the device acts as a GR helper, it cannot help the restarter to complete
GR.
To use BGP NSR in MPLS L3VPN, you must enable RIB NSR. For information about RIB NSR, see
" Configuring basic IP routing ."
To configure BGP NSR:
Step
1. Enter system view.
2. Enter BGP instance view.
3. Enable BGP NSR.
Command system-view bgp as-number [ instance instance-name ] non-stop-routing
Remarks
N/A
N/A
By default, BGP NSR is disabled.
302
Enabling SNMP notifications for BGP
After you enable SNMP notifications for BGP, the device generates a notification when a BGP neighbor state change occurs. The notification includes the neighbor address, the error code and subcode of the most recent error, and the current neighbor state.
For BGP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.
To enable SNMP notifications for BGP:
Step
1. Enter system view.
2. Enable SNMP notifications for BGP.
Command system-view snmp-agent trap enable bgp
[ instance instance-name ]
Remarks
N/A
By default, SNMP notifications for
BGP are enabled.
Enabling logging for session state changes
Perform this task to enable BGP to log BGP session establishment and disconnection events. To display the log information, use the display bgp peer ipv4 unicast log-info command or the display bgp peer ipv6 unicast log-info command. The logs are sent to the information center. The output rules of the logs (whether to output the logs and where to output) are determined by the information center configuration.
For more information about information center configuration, see Network Management and
Monitoring Configuration Guide .
To enable logging for session state changes (IPv4 unicast/IPv4 multicast):
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
N/A
3. Enable logging for session state changes globally.
log-peer-change
By default, logging for session state changes is enabled globally.
4. (Optional.) Enter BGP-VPN instance view.
ip vpn-instance
vpn-instance-name
N/A
5. Enable logging for session state changes for a peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } log-change
By default, logging for session state changes is enabled for all peers or peer groups.
To enable logging for session state changes (IPv6 unicast/IPv6 multicast):
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enable logging for session state changes globally.
log-peer-change
By default, logging for session state changes is enabled globally.
303
Step
4. (Optional.) Enter BGP-VPN instance view.
5. Enable logging for session state changes for a peer or peer group.
Command ip vpn-instance
vpn-instance-name
Remarks
N/A peer { group-name | ipv6-address
[ prefix-length ] } log-change
By default, logging for session state changes is enabled for all peers or peer groups.
Enabling logging for BGP route flapping
This feature enables BGP to generate logs for BGP route flappings that trigger log generation. The generated logs are sent to the information center. For the logs to be output correctly, you must also configure information center on the device. For more information about the information center, see
Network Management and Monitoring Configuration Guide .
To enable logging for BGP route flapping (IPv4 unicast/IPv4 multicast):
Step
1. Enter system view.
2. Enter BGP IPv4 unicast address family view,
BGP-VPN IPv4 unicast address family view, or BGP
IPv4 multicast address family view.
Command system-view
•
Enter BGP IPv4 unicast address family view:
a. bgp as-number
[ instance instance-name ] b. address-family ipv4
[ unicast ]
•
Enter BGP-VPN IPv4 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv4
[ unicast ]
•
Enter BGP IPv4 multicast address family view:
f. bgp as-number
[ instance instance-name ] g. address-family ipv4 multicast
Remarks
N/A
N/A
3. Enable logging for BGP route flapping.
log-route-flap monitor-time monitor-count [ log-count-limit | route-policy route-policy-name ]
*
By default, logging for BGP route flapping is disabled.
To enable logging for BGP route flapping (IPv6 unicast/IPv6 multicast):
Step
1. Enter system view.
Command system-view
Remarks
N/A
304
Step
2. Enter BGP IPv6 unicast address family view,
BGP-VPN IPv6 unicast address family view, or BGP
IPv6 multicast address family view.
3. Enable logging for BGP route flapping.
Command
•
Enter BGP IPv6 unicast address family view:
a. bgp as-number
[ instance instance-name ] b. address-family ipv6
[ unicast ]
•
Enter BGP-VPN IPv6 unicast address family view:
c. bgp as-number
[ instance instance-name ] d. ip vpn-instance vpn-instance-name e. address-family ipv6
[ unicast ]
•
Enter BGP IPv6 multicast address family view:
f. bgp as-number
[ instance instance-name ] g. address-family ipv6 multicast log-route-flap monitor-time monitor-count [ log-count-limit | route-policy route-policy-name ] *
Remarks
N/A
By default, logging for BGP route flapping is disabled.
Configuring BFD for BGP
IMPORTANT:
If you have enabled GR, use BFD with caution because BFD might detect a failure before the system performs GR, which will result in GR failure. If you have enabled both BFD and GR for BGP, do not disable BFD during a GR process to avoid GR failure.
BGP maintains neighbor relationships based on the keepalive timer and hold timer in seconds. It requires that the hold time must be at least three times the keepalive interval. This mechanism slows down link failure detection. Once a failure occurs on a high-speed link, a large quantity of packets will be dropped before routing convergence completes. BFD for BGP can solve this problem by fast detecting link failures to reduce convergence time.
Before you enable BFD for a BGP peer or peer group, you must establish a BGP session between the local router and the peer or peer group.
For more information about BFD, see High Availability Configuration Guide .
To enable BFD for a BGP peer (IPv4 unicast/multicast address family):
Step
1. Enter system view.
Command system-view
Remarks
N/A
305
Step
2. Enter BGP instance view or
BGP-VPN instance view.
Command
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name
3. Enable BFD to detect the link to the specified BGP peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } bfd [ multi-hop | single-hop ]
To enable BFD for a BGP peer (IPv6 unicast/multicast address family):
Step
1. Enter system view.
2. Enter BGP instance view or
BGP-VPN instance view.
3. Enable BFD to detect the link to the specified IPv6 BGP peer or peer group.
Command system-view
•
Enter BGP instance view: bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number [ instance instance-name ] b. ip vpn-instance
vpn-instance-name peer { group-name | ipv6-address
[ prefix-length ] } bfd [ multi-hop | single-hop ]
Remarks
N/A
By default, BFD is disabled.
Remarks
N/A
N/A
By default, BFD is disabled.
Configuring BGP FRR
When a link fails, the packets on the link are discarded, and a routing loop might occur until BGP completes routing convergence based on the new network topology.
You can enable BGP fast reroute (FRR) to resolve this issue.
Figure 66 Network diagram for BGP FRR
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
After you configure FRR on Router B as shown in Figure 66 , BGP generates a backup next hop
Router C for the primary route. BGP uses ARP (for IPv4), echo-mode BFD (for IPv4), or ND (for IPv6) to detect the connectivity to Router D. When the link to Router D fails, BGP directs packets to the backup next hop. At the same time, BGP calculates a new optimal route, and forwards packets over the optimal route.
You can use the following methods to configure BGP FRR:
306
•
Method 1 —Execute the pic command in BGP address family view. BGP calculates a backup next hop for each BGP route in the address family if there are two or more unequal-cost routes that reach the destination.
•
Method 2 —Execute the fast-reroute route-policy command to use a routing policy in which a backup next hop is specified by using the command apply [ ipv6 ] fast-reroute backup-nexthop . The backup next hop calculated by BGP must be the same as the specified backup next hop. Otherwise, BGP does not generate a backup next hop for the primary route.
You can also configure if-match clauses in the routing policy to identify the routes protected by
FRR.
If both methods are configured, Method 2 takes precedence over Method 1.
BGP supports FRR for IPv4 and IPv6 unicast routes, but not for IPv4 and IPv6 multicast routes.
To configure BGP FRR (IPv4 unicast address family):
Step
1. Enter system view.
Command system-view
2. Configure the source address of echo packets.
3. Create a routing policy and enter routing policy view.
4. Set the backup next hop for
FRR.
5. Return to system view.
bfd echo-source-ip ipv4-address
route-policy route-policy-name
permit node node-number apply fast-reroute
backup-nexthop ipv4-address
Remarks
N/A
By default, no source address is specified for echo packets.
This step is required when echo-mode BFD is used to detect the connectivity to the next hop of the primary route.
Specify a source IP address that does not belong to any local network.
For more information about this command, see High Availability
Command Reference .
By default, no routing policies exist.
This step is required when
Method 2 is used to enable BGP
FRR.
For more information about this command, see Layer 3—IP
Routing Command Reference .
By default, no backup next hop is set.
This step is required when
Method 2 is used to enable BGP
FRR.
For more information about this command, see Layer 3—IP
Routing Command Reference .
N/A
6. Enter BGP instance view. quit bgp as-number [ instance instance-name ]
N/A
7. (Optional.) Use echo-mode
BFD to detect the connectivity to the next hop of the primary route.
8. (Optional.) Enter BGP-VPN instance view. primary-path-detect bfd echo ip vpn-instance
vpn-instance-name
By default, ARP is used to detect the connectivity to the next hop.
N/A
307
Step
9. Enter BGP IPv4 unicast address family view or
BGP-VPN IPv4 unicast address family view.
Command address-family ipv4 [ unicast ]
Remarks
N/A
10. Enable BGP FRR.
•
(Method 1) Enable BGP FRR for the address family: pic
•
(Method 2) Apply a routing policy to FRR for the address family: fast-reroute route-policy
route-policy-name
By default, BGP FRR is disabled.
Method 1 might result in routing loops. Use it with caution.
By default, no routing policy is applied.
The apply fast-reroute backup-nexthop and apply ipv6 fast-reroute backup-nexthop commands can take effect in the applied routing policy. Other apply commands do not take effect.
To configure BGP FRR (IPv6 unicast address family):
Step
1. Enter system view.
2. Create a routing policy and enter routing policy view.
3. Set the backup next hop for
FRR.
4. Return to system view.
5. Enter BGP instance view or
BGP-VPN instance view.
Command system-view
Remarks
N/A route-policy
route-policy-name permit
node node-number apply ipv6 fast-reroute backup-nexthop
ipv6-address quit
•
Enter BGP instance view: bgp as-number
[ instance instance-name ]
•
Enter BGP-VPN instance view: a. bgp as-number
[ instance instance-name ] b. ip vpn-instance
vpn-instance-name
N/A
N/A
By default, no routing policies exist.
This step is required when Method 2 is used to enable BGP FRR.
For more information about this command, see Layer 3—IP Routing
Command Reference .
By default, no backup next hop is set.
This step is required when Method 2 is used to enable BGP FRR.
For more information about this command, see Layer 3—IP Routing
Command Reference .
6. Enter BGP IPv6 unicast address family view or
BGP-VPN IPv6 unicast address family view. address-family ipv6
[ unicast ]
N/A
308
Step
7. Enable BGP FRR.
Command
•
(Method 1) Enable BGP
FRR for the address family: pic
•
(Method 2) Apply a routing policy to FRR for the address family: fast-reroute route-policy
route-policy-name
Remarks
By default, BGP FRR is disabled.
Method 1 might result in routing loops.
Use it with caution.
By default, no routing policy is applied.
The apply fast-reroute backup-nexthop and apply ipv6 fast-reroute backup-nexthop commands can take effect in the applied routing policy. Other apply commands do not take effect.
Configuring 6PE
IPv6 provider edge (6PE) is a transition technology that uses MPLS to connect sparsely populated
IPv6 networks through an existing IPv4 backbone network. It is an efficient solution for ISP
IPv4/MPLS networks to provide IPv6 traffic switching capability.
Figure 67 Network diagram for 6PE
CE
IPv4/MPLS network
CE
IBGP
IPv6 network
Customer site
6PE 6PE IPv6 network
Customer site
P
6PE mainly performs the following operations:
•
6PE assigns a label to IPv6 routing information received from a CE router, and sends the labeled IPv6 routing information to the peer 6PE device through an MP-BGP session. The peer
6PE device then forwards the IPv6 routing information to the attached customer site.
•
6PE provides tunnels over the IPv4 backbone so the IPv4 backbone can forward packets for
IPv6 networks. The tunnels can be GRE tunnels, MPLS LSPs, or MPLS TE tunnels.
•
Upon receiving an IPv6 packet, 6PE adds an inner tag (corresponding to the IPv6 packet) and then an outer tag (corresponding to the public network tunnel) to the IPv6 packet. Devices in the
IPv4 backbone network forwards the packet based on the outer tag. When the peer 6PE device receives the packet, it removes the outer and inner tags and forwards the original IPv6 packet to the attached customer site.
To implement exchange of IPv6 routing information, you can configure IPv6 static routing, an IPv6
IGP protocol, or IPv6 BGP between CE and 6PE devices.
For more information about MPLS, MPLS TE, CE, and P, see MPLS Configuration Guide . For more information about GRE, see Layer 3—IP Services Configuration Guide .
Configuring basic 6PE
Before you configure 6PE, perform the following tasks:
•
Establish tunnels in the IPv4 backbone network (see Layer 3—IP Services Configuration
Guide ).
•
Configure basic MPLS on 6PE devices (see MPLS Configuration Guide ).
309
•
Configure BGP on 6PE devices so that they can advertise tagged IPv6 routing information through BGP sessions. The following describes only BGP configurations on 6PE devices.
To configure basic 6PE:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Specify a 6PE peer or peer group and its AS number.
peer { group-name | ipv4-address
[ mask-length ] } as-number as-number
4. Enter BGP IPv6 unicast address family view.
5. Enable BGP to exchange
IPv6 unicast routing information with the 6PE peer or peer group.
6. Enable BGP to exchange labeled IPv6 routes with the 6PE peer or peer group.
address-family ipv6 peer
[ mask-length peer
{
{
group-name
] } group-name
[ mask-length ] }
|
|
[ ipv4-address label-route-capability unicast ] ipv4-address enable
N/A
No 6PE peer is specified by default.
N/A
This feature is disabled by default.
This feature is disabled by default.
Configuring optional 6PE capabilities
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view.
bgp as-number [ instance instance-name ]
3. Enter BGP IPv6 unicast address family view.
address-family ipv6 [ unicast ]
4. Advertise COMMUNITY attribute to the 6PE peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } advertise-community
5. Advertise extended community attribute to the
6PE peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } advertise-ext-community
6. Allow the local AS number to appear in routes from the
6PE peer or peer group and specify the repeat times.
peer { group-name | ipv4-address
[ mask-length ] } allow-as-loop
[ number ]
7. Specify an AS path list to filter routes advertised to or received from the 6PE peer or peer group.
8. Specify an IPv6 ACL to filter routes advertised to or received from the 6PE peer or peer group.
peer
[ mask-length as-path-acl as-path-acl-number import peer
{
{ group-name
}
] } group-name
|
{
| ipv4-address
export | ipv4-address
[ mask-length ] } filter-policy ipv6-acl-number { export | import }
Remarks
N/A
N/A
N/A
By default, the COMMUNITY attribute is not advertised.
By default, the extended community attribute is not advertised.
By default, the local AS number is not allowed to appear in routes from the 6PE peer or peer group.
By default, no AS path list is specified.
By default, no ACL is specified.
310
Step
9. Specify an IPv6 prefix list to filter routes advertised to or received from the 6PE peer or peer group.
10. Specify a routing policy to filter routes advertised to or received from the 6PE peer or peer group.
Command peer { group-name | ipv4-address
[ mask-length ] } prefix-list ipv6-prefix-name { export | import }
Remarks
By default, no IPv6 prefix list is specified. peer { group-name | ipv4-address
[ mask-length ] } route-policy route-policy-name { export | import }
By default, no routing policy is specified.
11. Advertise a default route to the 6PE peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } default-route-advertise
[ route-policy route-policy-name ]
12. Save all routes from the 6PE peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } keep-all-routes
13. Configure BGP updates sent to the 6PE peer or peer group to carry only public AS numbers.
14. Specify the maximum number of routes that BGP can receive from the 6PE peer or peer group.
peer
[
{ group-name mask-length ] }
| ipv4-address public-as-only
By default, BGP updates sent to a 6PE peer or peer group can carry both public and private AS numbers. peer { group-name | ipv4-address
[ mask-length ] } route-limit prefix-number [ { alert-only discard | reconnect reconnect-time } | percentage-value ] *
By default, the number of routes that a router can receive from the 6PE peer or peer group is not limited.
15. Specify a preferred value for routes received from the 6PE peer or peer group.
peer { group-name | ipv4-address
[ mask-length ] } preferred-value
value
16. Configure the device as a route reflector and the 6PE peer or peer group as a client.
peer
[
{ group-name mask-length ] }
| ipv4-address reflect-client
By default, no default route is advertised.
By default, routes from a peer or peer group are not saved.
By default, the preferred value is 0.
By default, no route reflector or client is configured.
17. Configure the SoO attribute for a peer or peer group.
peer
[
{ group-name mask-length ] }
| soo ipv4-address
site-of-origin
By default, no SoO attribute is configured for a peer or peer group.
18.
20.
Return to user view.
Display routing information advertised to or received from the 6PE peer or peer group.
return display bgp [ instance instance-name ] routing-table ipv6
[ unicast ] peer ipv4-address
{ advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ]
N/A
19. Display information about the
6PE peer or peer group.
display bgp [ instance instance-name ] peer ipv6 [ unicast ]
[ ipv4-address mask-length |
{ ipv4-address | group-name group-name } log-info |
[ ipv4-address ] verbose ]
Available in any view.
Available in any view.
21.
22.
Soft-reset a BGP 6PE connection.
Reset a BGP 6PE connection.
refresh bgp [ instance instance-name ] ipv4-address
[ mask-length ] { export | import } ipv6 [ unicast ] reset bgp [ instance instance-name ] ipv4-address
[ mask-length ] ipv6 [ unicast ]
Available in user view.
Available in user view.
311
Configuring BGP LS
The BGP Link State (LS) feature implements inter-domain and inter-AS advertisement of link state database (LSDB) and TE database (TEDB) information.
The device sends the collected link state information to the controller, which implements end-to-end traffic management and scheduling, and meets the requirements of intended applications.
Configuring basic BGP LS
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
3. Specify an AS number for an LS peer or peer group. peer { ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } as-number as-number
peer group-name as-number as-number
4. Create the BGP LS address family and enter its view. address-family link-state
5. Enable the device to exchange LS information with the peer or peer group. peer { group-name | ipv4-address
[ mask-length ] | ipv6-address
[ prefix-length ] } enable
Remarks
N/A
N/A
By default, no AS number is specified.
N/A
By default, the device cannot exchange LS information with the peer or peer group.
Configuring BGP LS route reflection
Perform this task to configure a BGP route reflector and its clients. The route reflector and its clients automatically form a cluster identified by the router ID of the route reflector. The route reflector forwards route updates among its clients.
To configure BGP LS route reflection:
Step
1. Enter system view.
2. Enter BGP instance view.
Command system-view bgp as-number [ instance instance-name ]
Remarks
N/A
N/A
3. Enter BGP LS address family view.
4. Configure the device as a route reflector and specify a peer or peer group as its client.
5. Enable route reflection between clients.
6. (Optional.) Configure the cluster ID of the route reflector. address-family link-state peer
[
[
{ group-name mask-length prefix-length
] |
] }
| ipv4-address ipv6-address reflect between-clients reflect-client reflector cluster-id { cluster-id | ipv4-address }
N/A
By default, no route reflector or client is configured.
By default, route reflection between clients is enabled.
By default, a route reflector uses its own router ID as the cluster ID.
312
Specifying an AS number and a router ID for BGP LS messages
Perform this task to ensure that LS messages sent by devices in the same AS have the same AS number and router ID.
To specify an AS number and a router ID for BGP LS messages:
Step
1. Enter system view.
Command system-view
2. Enter BGP instance view. bgp as-number [ instance instance-name ]
3. Enter BGP LS address family view. address-family link-state
4. Specify an AS number and a router ID for BGP LS messages. domain-distinguisher as-number:router-id
Remarks
N/A
N/A
N/A
By default, the AS number and router ID of the current BGP process are used.
Configuring BMP
The BGP monitoring protocol (BMP) enables a BGP router (BMP client) to send session status information of the specified peers to BMP servers for monitoring. The session status information includes peer relationship establishment and termination as well as routing information. The BMP client communicates with the BMP servers through TCP connections.
To configure BMP:
Step
1. Enter system view.
Command system-view
2. Create a BMP server and enter BMP server view. bmp server server-number
3. Configure an IP address and port number for the BMP server. server address ipv4-address port
port-number
Remarks
N/A
By default, no BMP servers exist.
By default, no IP address and port number are configured for the BMP server.
4. Set the interval at which BGP sends statistics information to the BMP server.
statistics-interval value
5.
6.
Return to system view.
Enter BGP instance view or
BGP-VPN instance view.
7. Specify a peer or peer group to be monitored. quit
•
Enter BGP instance view:
bgp as-number [ instance instance-name ]
•
Enter BGP-VPN instance view:
a. bgp as-number [ instance instance-name ] b. ip vpn-instance vpn-instance-name peer { group-name | ipv4-address
[ mask-length ] | ipv6-address
[ prefix-length ] } bmp server server-number-list
By default, BGP does not send statistics information to the
BMP server.
N/A
N/A
By default, no peer or peer group is specified.
313
Displaying and maintaining BGP
Displaying BGP
Execute display commands in any view (IPv4 unicast address family).
Task
Display BGP NSR status information.
Command display bgp [ instance instance-name ] non-stop-routing status
Display BGP IPv4 unicast peer group information.
Display BGP IPv4 unicast peer or peer group information.
Display BGP IPv4 unicast routing information.
Display dampened BGP IPv4 unicast routing information. display bgp [ instance instance-name ] group ipv4 [ unicast ]
[ vpn-instance vpn-instance-name ] [ group-name group-name ] display bgp [ instance instance-name ] peer ipv4 [ unicast ]
[ vpn-instance vpn-instance-name ] [ ipv4-address mask-length
| { ipv4-address | group-name group-name } log-info |
[ ipv4-address ] verbose ] display bgp [ instance instance-name ] peer ipv4 [ unicast ] vpn-instance-all [ verbose ] display bgp [ instance instance-name ] routing-table ipv4
[ unicast ] [ vpn-instance vpn-instance-name ] [ ipv4-address
[ { mask-length | mask } [ longest-match ] ] | ipv4-address
[ mask-length | mask ] advertise-info | as-path-acl as-path-acl-number | community-list
{ { basic-community-list-number | comm-list-name }
[ whole-match ] | adv-community-list-number } | peer ipv4-address { advertised-routes | received-routes }
[ ipv4-address [ mask-length | mask ] | statistics ] | statistics ] display bgp [ instance instance-name ] routing-table dampened ipv4 [ unicast ] [ vpn-instance vpn-instance-name ]
Display BGP dampening parameter information.
Display BGP IPv4 unicast routing flap statistics. display bgp [ instance instance-name ] dampening parameter ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] display bgp [ instance instance-name ] routing-table flap-info ipv4 [ unicast ] [ vpn-instance vpn-instance-name ]
[ ipv4-address [ { mask-length | mask } [ longest-match ] ] | as-path-acl as-path-acl-number ]
Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp [ instance instance-name ] network ipv4
[ unicast ] [ vpn-instance vpn-instance-name ]
Display BGP path attribute information.
Display information about all BGP instances. display bgp [ instance instance-name ] paths
[ as-regular-expression ]
Display BGP IPv4 unicast address family update group information. display bgp [ instance instance-name ] update-group ipv4
[ unicast ] [ vpn-instance vpn-instance-name ] [ ipv4-address ] display bgp instance-info
Display BMP server information.
Display ORF prefix information received by a peer. display bgp [ instance instance-name ] bmp server
server-number display bgp [ instance instance-name ] peer ipv4 [ unicast ]
[ vpn-instance vpn-instance-name ] ipv4-address received prefix-list
314
Execute display commands in any view (IPv6 unicast address family).
Task
Display BGP NSR status information.
Command display bgp [ instance instance-name ] non-stop-routing status
Display BGP IPv6 unicast peer group information.
Display BGP IPv6 unicast peer or peer group information. display bgp [ instance instance-name ] group ipv6 [ unicast ]
[ vpn-instance vpn-instance-name ] [ group-name group-name ] display bgp [ instance instance-name ] peer ipv6 [ unicast ]
[ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length | { ipv6-address | group-name group-name } log-info | [ ipv6-address ] verbose ] display bgp [ instance instance-name ] peer ipv6 [ unicast ]
[ ipv4-address mask-length | ipv4-address log-info |
[ ipv4-address ] verbose ] display bgp [ instance instance-name ] peer ipv6 [ unicast ] vpn-instance-all [ verbose ]
Display BGP IPv6 unicast routing information.
Display dampened BGP IPv6 unicast routing information.
Display BGP dampening parameter information.
Display BGP IPv6 unicast routing flap statistics.
display bgp [ instance instance-name ] routing-table ipv6
[ unicast ] [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length [ advertise-info ] | as-path-acl as-path-acl-number | community-list
{ { basic-community-list-number | comm-list-name }
[ whole-match ] | adv-community-list-number } | peer ipv6-address { advertised-routes | received-routes }
[ ipv6-address prefix-length | statistics ] | statistics ] display bgp [ instance instance-name ] routing-table ipv6
[ unicast ] peer ipv4-address { advertised-routes | received-routes } [ ipv6-address prefix-length | statistics ] display bgp [ instance instance-name ] routing-table dampened ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] display bgp [ instance instance-name ] dampening parameter ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] display bgp [ instance instance-name ] routing-table flap-info ipv6 [ unicast ] [ vpn-instance vpn-instance-name ]
[ ipv6-address prefix-length | as-path-acl as-path-acl-number ] display bgp [ instance instance-name ] routing-table ipv6
[ unicast ] inlabel
Display incoming labels for BGP IPv6 unicast routes.
Display outgoing labels of BGP IPv6 unicast routes. display bgp [ instance instance-name ] routing-table ipv6
[ unicast ] outlabel
Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp [ instance instance-name ] network ipv6
[ unicast ] [ vpn-instance vpn-instance-name ]
Display BGP path attribute information. display bgp [ instance instance-name ] paths
[ as-regular-expression ]
Display BGP IPv6 unicast address family update group information. display bgp [ instance instance-name ] update-group ipv6
[ unicast ] [ ipv4-address | ipv6-address ] display bgp [ instance instance-name ] update-group ipv6
[ unicast ] vpn-instance vpn-instance-name [ ipv6-address ]
Display information about all BGP instances. display bgp instance-info
315
Task Command
Display ORF prefix information received by a peer. display bgp [ instance instance-name ] peer ipv6 [ unicast ]
[ vpn-instance vpn-instance-name ] ipv6-address received prefix-list display bgp [ instance instance-name ] peer ipv6 [ unicast ]
ipv4-address received prefix-list
Execute display commands in any view (IPv4 multicast address family).
Task
Display BGP NSR status information.
Command display bgp [ instance instance-name ] non-stop-routing status
Display BGP IPv4 multicast peer group information.
Display BGP IPv4 multicast peer or peer group information.
Display BGP IPv4 multicast routing information.
Display dampened BGP IPv4 multicast routing information.
Display BGP dampening parameter information. display bgp [ instance instance-name ] group ipv4 multicast
[ group-name group-name ] display bgp [ instance instance-name ] peer ipv4 multicast
[ ipv4-address mask-length | { ipv4-address | group-name group-name } log-info | [ ipv4-address ] verbose ] display bgp [ instance instance-name ] routing-table ipv4 multicast [ ipv4-address [ { mask-length | mask }
[ longest-match ] ] | ipv4-address [ mask-length | mask ] advertise-info | as-path-acl as-path-acl-number | community-list { { basic-community-list-number | comm-list-name } [ whole-match ] | adv-community-list-number } | peer ipv4-address
{ advertised-routes | received-routes } [ ipv4-address
[ mask-length | mask ] | statistics ] | statistics ] display bgp [ instance instance-name ] routing-table dampened ipv4 multicast display bgp [ instance instance-name ] dampening parameter ipv4 multicast
Display BGP IPv4 multicast routing flap statistics. display bgp [ instance instance-name ] routing-table flap-info ipv4 multicast [ ipv4-address [ { mask-length | mask }
[ longest-match ] ] | as-path-acl as-path-acl-number ]
Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp [ instance instance-name ] network ipv4 multicast
Display BGP path attribute information.
Display BGP IPv4 multicast address family update group information.
Display information about all BGP instances. display bgp [ instance instance-name ] paths
[ as-regular-expression ] display bgp [ instance instance-name ] update-group ipv4 multicast [ ipv4-address ] display bgp instance-info
Display BMP server information. display bgp [ instance instance-name ] bmp server
server-number
Display ORF prefix information received by a peer. display bgp [ instance instance-name ] peer ipv4 multicast
ipv4-address received prefix-list
Execute display commands in any view (IPv6 multicast address family).
316
Task
Display BGP NSR status information.
Command display bgp [ instance instance-name ] non-stop-routing status
Display BGP IPv6 multicast peer group information.
Display BGP IPv6 multicast peer or peer group information.
Display BGP IPv6 multicast routing information. display bgp [ instance instance-name ] group ipv6 multicast
[ group-name group-name ] display bgp [ instance instance-name ] peer ipv6 multicast
[ ipv6-address prefix-length | { ipv6-address | group-name group-name } log-info | [ ipv6-address ] verbose ] display bgp [ instance instance-name ] routing-table ipv6 multicast [ ipv6-address prefix-length [ advertise-info ] |
as-path-acl as-path-acl-number | community-list
{ { basic-community-list-number | comm-list-name }
[ whole-match ] | adv-community-list-number } | peer ipv6-address { advertised-routes | received-routes }
[ ipv6-address prefix-length | statistics ] | statistics ]
Display dampened BGP IPv6 multicast routing information.
Display BGP dampening parameter information.
Display BGP IPv6 multicast routing flap statistics. display bgp [ instance instance-name ] routing-table flap-info ipv6 multicast [ ipv6-address prefix-length |
as-path-acl as-path-acl-number ]
Display information about routes advertised by the network command and shortcut routes configured by the network short-cut command. display bgp [ instance instance-name ] network ipv6 multicast
Display BGP path attribute information.
Display BGP IPv6 multicast address family update group information.
Display information about all BGP instances. display bgp [ instance instance-name ] routing-table dampened ipv6 multicast display bgp [ instance instance-name ] dampening parameter ipv6 multicast display bgp [ instance instance-name ] paths
[ as-regular-expression ] display bgp [ instance instance-name ] update-group ipv6
multicast [ ipv6-address ] display bgp instance-info
Display ORF prefix information received by a peer. display bgp [ instance instance-name ] peer ipv6 multicast ipv6-address received prefix-list
Execute display commands in any view (LS address family).
Task
Display BGP LS peer group information.
Display BGP LS information.
Display BGP LS peer or peer group information.
Command display bgp [ instance instance-name ] group link-state
[ group-name group-name ] display bgp [ instance instance-name ] link-state [ ls-prefix | peer { ipv4-address | ipv6-address } { advertised | received }
[ statistics ] | statistics ] display bgp [ instance instance-name ] peer link-state
[ ipv4-address mask-length | ipv6-address prefix-length |
{ ipv4-address | ipv6-address | group-name group-name } log-info | [ ipv4-address | ipv6-address ] verbose ]
Display BGP LS address family update group information. display bgp [ instance instance-name ] update-group link-state [ ipv4-address | ipv6-address ]
Execute display commands in any view (IPv4 RT filter address family).
317
Task
Display BGP IPv4 RT filter routing information.
Command display bgp [ instance instance-name ] routing-table ipv4 rtfilter [ default-rt [ advertise-info ] | [ origin-as as-number ]
[ route-target [ advertise-info ] ] | peer ipv4-address
{ advertised-routes | received-routes } [ default-rt |
[ origin-as as-number ] [ route-target ] | statistics ] | statistics ]
Resetting BGP sessions
Execute reset commands in user view.
Task
Reset all BGP sessions.
Reset BGP sessions for IPv4 unicast address family.
Reset BGP sessions for IPv6 unicast address family.
Reset BGP sessions for LS address family.
Reset BGP sessions for IPv4 multicast address family.
Reset BGP sessions for IPv6 multicast address family.
Command reset bgp [ instance instance-name ] all reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name
| internal } ipv4 [ unicast ] [ vpn-instance vpn-instance-name ] reset bgp [ instance instance-name ] { as-number | ipv6-address [ prefix-length ] | all | external | group group-name
| internal } ipv6 [ unicast ] [ vpn-instance vpn-instance-name ] reset bgp [ instance instance-name ] ipv4-address
[ mask-length ] ipv6 [ unicast ] reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] | all | external | group group-name | internal } { export | import } link-state reset bgp [ instance instance-name ] { as-number | ipv4-address [ mask-length ] | all | external | group group-name
| internal } ipv4 multicast reset bgp [ instance instance-name ] { as-number | ipv6-address [ prefix-length ] | all | external | group group-name
| internal } ipv6 multicast
Clearing BGP information
Execute reset commands in user view.
Task
Clear dampening information for BGP
IPv4 unicast routes and release suppressed BGP IPv4 unicast routes.
Clear flap information for BGP IPv4 unicast routes.
Clear dampening information for BGP
IPv6 unicast routes and release suppressed BGP IPv6 unicast routes.
Command reset bgp [ instance instance-name ] dampening ipv4
[ unicast ] [ vpn-instance vpn-instance-name ] [ ipv4-address
[ mask-length | mask ] ] reset bgp [ instance instance-name ] flap-info ipv4 [ unicast ]
[ vpn-instance vpn-instance-name ] [ ipv4-address
[ mask-length | mask ] | as-path-acl as-path-acl-number | peer ipv4-address [ mask-length ] ] reset bgp [ instance instance-name ] dampening ipv6
[ unicast ] [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length ]
318
Task
Clear flap information for BGP IPv6 unicast routes.
Clear dampening information for BGP
IPv4 multicast routes and release suppressed BGP IPv4 multicast routes.
Clear flap information for BGP IPv4 multicast routes.
Clear dampening information for BGP
IPv6 multicast routes and release suppressed BGP IPv6 multicast routes.
Clear flap information for BGP IPv6 multicast routes.
Clear BMP server statistics.
Command reset bgp [ instance instance-name ] flap-info ipv6 [ unicast ]
[ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length | as-path-acl as-path-acl-number | peer ipv6-address [ prefix-length ] ] reset bgp [ instance instance-name ] dampening ipv4 multicast [ ipv4-address [ mask-length | mask ] ] reset bgp [ instance instance-name ] flap-info ipv4 multicast
[ ipv4-address [ mask-length | mask ] | as-path-acl as-path-acl-number | peer ipv4-address [ mask-length ] ] reset bgp [ instance instance-name ] dampening ipv6 multicast [ ipv6-address prefix-length ] reset bgp [ instance instance-name ] flap-info ipv6 multicast
[ ipv6-address prefix-length | as-path-acl as-path-acl-number | peer ipv6-address [ prefix-length ] ] reset bgp [ instance instance-name ] bmp server
server-number statistics
IPv4 BGP configuration examples
Basic BGP configuration example
Network requirements
As shown in Figure 68 , all switches run BGP. Run EBGP between Switch A and Switch B, and run
IBGP between Switch B and Switch C to allow Switch C to access network 8.1.1.0/24 connected to
Switch A.
Figure 68 Network diagram
Loop0
1.1.1.1/32
AS 65008 AS 65009
Loop0
2.2.2.2/32
Loop0
3.3.3.3/32
Vlan-int100
8.1.1.1/24
Vlan-int200
Switch A
3.1.1.2/24
EBGP
Vlan-int200
3.1.1.1/24
Switch B
Vlan-int300
9.1.1.1/24
IBGP
Vlan-int300
9.1.1.2/24
Switch C
Requirements analysis
To prevent route flapping caused by port state changes, this example uses loopback interfaces to establish IBGP connections. Loopback interfaces are virtual interfaces. Therefore, use the peer connect-interface command to specify the loopback interface as the source interface for establishing BGP connections. Enable OSPF in AS 65009 to ensure that Switch B can communicate with Switch C through loopback interfaces.
The EBGP peers, Switch A and Switch B (usually belong to different carriers), are located in different
ASs. Typically, their loopback interfaces are not reachable to each other, so directly connected interfaces are used for establishing EBGP sessions. To enable Switch C to access the network
8.1.1.0/24 connected directly to Switch A, inject network 8.1.1.0/24 to the BGP routing table of
Switch A.
319
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure IBGP:
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 3.3.3.3 as-number 65009
[SwitchB-bgp-default] peer 3.3.3.3 connect-interface loopback 0
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 3.3.3.3 enable
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 2.2.2.2 as-number 65009
[SwitchC-bgp-default] peer 2.2.2.2 connect-interface loopback 0
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 2.2.2.2 enable
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
[SwitchC] ospf 1
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
[SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
[SwitchC] display bgp peer ipv4
BGP local router ID : 3.3.3.3
Local AS number : 65009
Total number of peers : 1 Peers in established state : 1
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2.2.2.2 65009 2 2 0 0 00:00:13 Established
The output shows that Switch C has established an IBGP peer relationship with Switch B.
3. Configure EBGP:
# Configure Switch A.
320
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 3.1.1.1 as-number 65009
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 3.1.1.1 enable
[SwitchA-bgp-default-ipv4] network 8.1.1.0 24
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
[SwitchB] bgp 65009
[SwitchB-bgp-default] peer 3.1.1.2 as-number 65008
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 3.1.1.2 enable
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Display BGP peer information on Switch B.
[SwitchB] display bgp peer ipv4
BGP local router ID : 2.2.2.2
Local AS number : 65009
Total number of peers : 2 Peers in established state : 2
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
3.3.3.3 65009 4 4 0 0 00:02:49 Established
3.1.1.2 65008 2 2 0 0 00:00:05 Established
The output shows that Switch B has established an IBGP peer relationship with Switch C and an EBGP peer relationship with Switch A.
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 8.1.1.0/24 8.1.1.1 0 32768 i
# Display the BGP routing table on Switch B.
[SwitchB] display bgp routing-table ipv4
Total number of routes: 1
321
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 8.1.1.0/24 3.1.1.2 0 0 65008i
# Display the BGP routing table on Switch C.
[SwitchC] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
i 8.1.1.0/24 3.1.1.2 0 100 0 65008i
The outputs show that Switch A has learned no route to AS 65009, and Switch C has learned network 8.1.1.0, but the next hop 3.1.1.2 is unreachable. As a result, the route is invalid.
4. Redistribute direct routes:
Configure BGP to redistribute direct routes on Switch B, so that Switch A can obtain the route to
9.1.1.0/24, and Switch C can obtain the route to 3.1.1.0/24.
# Configure Switch B.
[SwitchB] bgp 65009
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] import-route direct
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 4
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 2.2.2.2/32 3.1.1.1 0 0 65009?
* >e 3.1.1.0/24 3.1.1.1 0 0 65009?
* > 8.1.1.0/24 8.1.1.1 0 32768 i
* >e 9.1.1.0/24 3.1.1.1 0 0 65009?
322
Two routes, 2.2.2.2/32 and 9.1.1.0/24, have been added in Switch A's routing table.
# Display the BGP routing table on Switch C.
[SwitchC] display bgp routing-table ipv4
Total number of routes: 4
BGP local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 2.2.2.2/32 2.2.2.2 0 100 0 ?
* >i 3.1.1.0/24 2.2.2.2 0 100 0 ?
* >i 8.1.1.0/24 3.1.1.2 0 100 0 65008i
* >i 9.1.1.0/24 2.2.2.2 0 100 0 ?
The output shows that the route 8.1.1.0 becomes valid with the next hop as Switch A.
Verifying the configuration
# Verify that Switch C can ping 8.1.1.1.
[SwitchC] ping 8.1.1.1
Ping 8.1.1.1 (8.1.1.1): 56 data bytes, press CTRL_C to break
56 bytes from 8.1.1.1: icmp_seq=0 ttl=254 time=10.000 ms
56 bytes from 8.1.1.1: icmp_seq=1 ttl=254 time=4.000 ms
56 bytes from 8.1.1.1: icmp_seq=2 ttl=254 time=4.000 ms
56 bytes from 8.1.1.1: icmp_seq=3 ttl=254 time=3.000 ms
56 bytes from 8.1.1.1: icmp_seq=4 ttl=254 time=3.000 ms
--- Ping statistics for 8.1.1.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 3.000/4.800/10.000/2.638 ms
BGP and IGP route redistribution configuration example
Network requirements
As shown in Figure 69 , all devices of company A belong to AS 65008, and all devices of company B
belong to AS 65009.
Configure BGP and IGP route redistribution to allow Switch A to access network 9.1.2.0/24 in AS
65009, and Switch C to access network 8.1.1.0/24 in AS 65008.
Figure 69 Network diagram
Loop0
1.1.1.1/32
AS 65008 AS 65009
Loop0
2.2.2.2/32
Loop0
3.3.3.3/32
Vlan-int100
8.1.1.1/24
Vlan-int200
Switch A
3.1.1.2/24
EBGP
Vlan-int200
3.1.1.1/24
Switch B
Vlan-int300
9.1.1.1/24
OSPF
Vlan-int300
9.1.1.2/24
Switch C
Vlan-int400
9.1.2.1/24
323
Configuration considerations
Configure BGP to redistribute routes from OSPF on Switch B, so Switch A can obtain the route to
9.1.2.0/24. Configure OSPF to redistribute routes from BGP on Switch B, so Switch C can obtain the route to 8.1.1.0/24.
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure OSPF:
Enable OSPF in AS 65009, so Switch B can obtain the route to 9.1.2.0/24.
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf 1
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[SwitchB-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf 1
[SwitchC-ospf-1] import-route direct
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 9.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
3. Configure the EBGP connection:
Configure the EBGP connection and inject network 8.1.1.0/24 to the BGP routing table of
Switch A, so that Switch B can obtain the route to 8.1.1.0/24.
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 3.1.1.1 as-number 65009
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 3.1.1.1 enable
[SwitchA-bgp-default-ipv4] network 8.1.1.0 24
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
[SwitchB] bgp 65009
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 3.1.1.2 as-number 65008
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 3.1.1.2 enable
4. Configure BGP and IGP route redistribution:
# Configure route redistribution between BGP and OSPF on Switch B.
[SwitchB-bgp-default-ipv4] import-route ospf 1
[SwitchB-bgp-default-ipv4] quit
324
[SwitchB-bgp-default] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] import-route bgp
[SwitchB-ospf-1] quit
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 3
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 3.3.3.3/32 3.1.1.1 1 0 65009?
* > 8.1.1.0/24 8.1.1.1 0 32768 i
* >e 9.1.2.0/24 3.1.1.1 1 0 65009?
# Display the OSPF routing table on Switch C.
[SwitchC] display ospf routing
OSPF Process 1 with Router ID 3.3.3.3
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
9.1.1.0/24 1 Transit 9.1.1.2 3.3.3.3 0.0.0.0
2.2.2.2/32 1 Stub 9.1.1.1 2.2.2.2 0.0.0.0
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
8.1.1.0/24 1 Type2 1 9.1.1.1 2.2.2.2
Total Nets: 3
Intra Area: 2 Inter Area: 0 ASE: 1 NSSA: 0
Verifying the configuration
# Use ping for verification.
[SwitchA] ping -a 8.1.1.1 9.1.2.1
Ping 9.1.2.1 (9.1.2.1) from 8.1.1.1: 56 data bytes, press CTRL_C to break
56 bytes from 9.1.2.1: icmp_seq=0 ttl=254 time=10.000 ms
56 bytes from 9.1.2.1: icmp_seq=1 ttl=254 time=12.000 ms
56 bytes from 9.1.2.1: icmp_seq=2 ttl=254 time=2.000 ms
56 bytes from 9.1.2.1: icmp_seq=3 ttl=254 time=7.000 ms
56 bytes from 9.1.2.1: icmp_seq=4 ttl=254 time=9.000 ms
--- Ping statistics for 9.1.2.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
325
round-trip min/avg/max/std-dev = 2.000/8.000/12.000/3.406 ms
[SwitchC] ping -a 9.1.2.1 8.1.1.1
Ping 8.1.1.1 (8.1.1.1) from 9.1.2.1: 56 data bytes, press CTRL_C to break
56 bytes from 8.1.1.1: icmp_seq=0 ttl=254 time=9.000 ms
56 bytes from 8.1.1.1: icmp_seq=1 ttl=254 time=4.000 ms
56 bytes from 8.1.1.1: icmp_seq=2 ttl=254 time=3.000 ms
56 bytes from 8.1.1.1: icmp_seq=3 ttl=254 time=3.000 ms
56 bytes from 8.1.1.1: icmp_seq=4 ttl=254 time=3.000 ms
--- Ping statistics for 8.1.1.1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 3.000/4.400/9.000/2.332 ms
BGP route summarization configuration example
Network requirements
As shown in Figure 70 , run EBGP between Switch C and Switch D, so the internal network and
external network can communicate with each other.
•
In AS 65106, perform the following configurations so the devices in the internal network can communicate:
Configure static routing between Switch A and Switch B.
Configure OSPF between Switch B and Switch C.
Configure OSPF to redistribute static routes.
•
Configure route summarization on Switch C so BGP advertises a summary route instead of advertising routes to the 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 networks to
Switch D.
Figure 70 Network diagram
Internal network
AS 65106
Switch B
Core layer device
Vlan-int110
192.168.212.1/24
Vlan-int100
172.17.100.1/24
External network
AS 64631
Switch A
Distribution layer device
Loop0
1.1.1.1/32
Loop0
2.2.2.2/32
Vlan-int110
192.168.212.161/24
Vlan-int100
172.17.100.2/24
Loop0
3.3.3.3/32
Vlan-int200
10.220.2.16/24
Switch C
Boundary device
Loop0
4.4.4.4/32
Vlan-int200
10.220.2.217/24
Switch D
External network device
192.168.64.0/24 192.168.74.0/24 192.168.99.0/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure static routing between Switch A and Switch B:
# Configure a default route with the next hop 192.168.212.1 on Switch A.
<SwitchA> system-view
[SwitchA] ip route-static 0.0.0.0 0 192.168.212.1
326
# Configure static routes to 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 with the same next hop 192.168.212.161 on Switch B.
<SwitchB> system-view
[SwitchB] ip route-static 192.168.64.0 24 192.168.212.161
[SwitchB] ip route-static 192.168.74.0 24 192.168.212.161
[SwitchB] ip route-static 192.168.99.0 24 192.168.212.161
3. Configure OSPF between Switch B and Switch C and configure OSPF on Switch B to redistribute static routes:
# Configure OSPF to advertise the local network and enable OSPF to redistribute static routes on Switch B.
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 172.17.100.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] import-route static
[SwitchB-ospf-1] quit
# Configure OSPF to advertise the local networks on Switch C.
[SwitchC] ospf
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 172.17.100.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] network 10.220.2.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Display the IP routing table on Switch C.
[SwitchC] display ip routing-table protocol ospf
Summary count : 5
OSPF Routing table Status : <Active>
Summary count : 3
Destination/Mask Proto Pre Cost NextHop Interface
192.168.64.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.74.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.99.0/24 OSPF 150 1 172.17.100.1 Vlan100
OSPF Routing table Status : <Inactive>
Summary count : 2
Destination/Mask Proto Pre Cost NextHop Interface
10.220.2.0/24 OSPF 10 1 10.220.2.16 Vlan200
172.17.100.0/24 OSPF 10 1 172.17.100.2 Vlan100
The output shows that Switch C has learned routes to 192.168.64.0/24, 192.168.99.0/24, and
192.168.64.0/18 through OSPF.
4. Configure BGP between Switch C and Switch D and configure BGP on Switch C to redistribute
OSPF routes:
# On Switch C, enable BGP, specify Switch D as an EBGP peer, and configure BGP to redistribute OSPF routes.
[SwitchC] bgp 65106
327
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 10.220.2.217 as-number 64631
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 10.220.2.217 enable
[SwitchC-bgp-default-ipv4] import-route ospf
# Enable BGP, and configure Switch C as an EBGP peer on Switch D.
[SwitchD] bgp 64631
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] peer 10.220.2.16 as-number 65106
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] peer 10.220.2.16 enable
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
# Display the IP routing table on Switch D.
[SwitchD] display ip routing-table protocol bgp
Summary count : 3
BGP Routing table Status : <Active>
Summary count : 3
Destination/Mask Proto Pre Cost NextHop Interface
192.168.64.0/24 BGP 255 1 10.220.2.16 Vlan200
192.168.74.0/24 BGP 255 1 10.220.2.16 Vlan200
192.168.99.0/24 BGP 255 1 10.220.2.16 Vlan200
BGP Routing table Status : <Inactive>
Summary count : 0
The output shows that Switch D has learned routes to 192.168.64.0/24, 192.168.74.0/24, and
192.168.99.0/24 through BGP.
# Verify that Switch D can ping hosts on networks 192.168.74.0/24, 192.168.99.0/24, and
192.168.64.0/18. (Details not shown.)
5. Configure route summarization on Switch C to summarize 192.168.64.0/24, 192.168.74.0/24, and 192.168.99.0/24 into a single route 192.168.64.0/18, and disable advertisement of specific routes.
[SwitchC-bgp-default-ipv4] aggregate 192.168.64.0 18 detail-suppressed
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
Verifying the configuration
# Display IP routing table on Switch C.
[SwitchC] display ip routing-table | include 192.168
192.168.64.0/18 BGP 130 0 127.0.0.1 NULL0
192.168.64.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.74.0/24 OSPF 150 1 172.17.100.1 Vlan100
192.168.99.0/24 OSPF 150 1 172.17.100.1 Vlan100
The output shows that Switch C has a summary route 192.168.64.0/18 with the output interface
Null0.
# Display IP routing table on Switch D.
328
[SwitchD] display ip routing-table protocol bgp
Summary count : 1
BGP Routing table Status : <Active>
Summary count : 1
Destination/Mask Proto Pre Cost NextHop Interface
192.168.64.0/18 BGP 255 0 10.220.2.16 Vlan200
BGP Routing table Status : <Inactive>
Summary count : 0
The output shows that Switch D has only one route 192.168.64.0/18 to AS 65106.
# Verify that Switch D can ping the hosts on networks 192.168.64.0/24, 192.168.74.0/24, and
192.168.99.0/24. (Details not shown.)
BGP load balancing configuration example
Network requirements
As shown in Figure 71 , run EBGP between Switch A and Switch B, and between Switch A and Switch
C. Run IBGP between Switch B and Switch C. Configure load balancing over the two EBGP links on
Switch A.
Figure 71 Network diagram
AS 65009
Loop0
2.2.2.2/32
AS 65008
Loop0
1.1.1.1/32
Vlan-int200
3.1.1.2/24
EBGP
Switch A
Vlan-int300
3.1.2.2/24 EBGP
Vlan-int200
3.1.1.1/24
Switch B
IBGP
Vlan-int400
9.1.1.1/24
Vlan-int400
9.1.1.2/24
Vlan-int300
3.1.2.1/24
Switch C
Intranet
Loop0
3.3.3.3/32
Configuration considerations
On Switch A:
•
Establish EBGP connections with Switch B and Switch C.
•
Configure BGP to advertise network 8.1.1.0/24 to Switch B and Switch C, so that Switch B and
Switch C can access the internal network connected to Switch A.
On Switch B:
•
Establish an EBGP connection with Switch A and an IBGP connection with Switch C.
•
Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet through Switch B.
329
•
Configure a static route to interface loopback 0 on Switch C (or use a routing protocol like OSPF) to establish the IBGP connection.
On Switch C:
•
Establish an EBGP connection with Switch A and an IBGP connection with Switch B.
•
Configure BGP to advertise network 9.1.1.0/24 to Switch A, so that Switch A can access the intranet through Switch C.
•
Configure a static route to interface loopback 0 on Switch B (or use another protocol like OSPF) to establish the IBGP connection.
Configure load balancing on Switch A.
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure BGP connections:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 3.1.1.1 as-number 65009
[SwitchA-bgp-default] peer 3.1.2.1 as-number 65009
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 3.1.1.1 enable
[SwitchA-bgp-default-ipv4] peer 3.1.2.1 enable
[SwitchA-bgp-default-ipv4] network 8.1.1.0 24
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 3.1.1.2 as-number 65008
[SwitchB-bgp-default] peer 3.3.3.3 as-number 65009
[SwitchB-bgp-default] peer 3.3.3.3 connect-interface loopback 0
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 3.1.1.2 enable
[SwitchB-bgp-default-ipv4] peer 3.3.3.3 enable
[SwitchB-bgp-default-ipv4] network 9.1.1.0 24
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
[SwitchB] ip route-static 3.3.3.3 32 9.1.1.2
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 3.1.2.2 as-number 65008
[SwitchC-bgp-default] peer 2.2.2.2 as-number 65009
[SwitchC-bgp-default] peer 2.2.2.2 connect-interface loopback 0
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 3.1.2.2 enable
330
[SwitchC-bgp-default-ipv4] peer 2.2.2.2 enable
[SwitchC-bgp-default-ipv4] network 9.1.1.0 24
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
[SwitchC] ip route-static 2.2.2.2 32 9.1.1.1
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 3
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 8.1.1.0/24 8.1.1.1 0 32768 i
* >e 9.1.1.0/24 3.1.1.1 0 0 65009i
* e 3.1.2.1 0 0 65009i
The output shows two valid routes to destination 9.1.1.0/24. The route with next hop 3.1.1.1 is marked with a greater-than sign (>), indicating that it is the optimal route (because the ID of Switch B is smaller). The route with next hop 3.1.2.1 is marked with an asterisk (*), indicating that it is a valid route, but not the optimal route.
By using the display ip routing-table command, you can find only one route to 9.1.1.0/24 with next hop 3.1.1.1 and output interface VLAN-interface 200.
3. Configure loading balancing:
Because Switch A has two routes to reach AS 65009, configuring load balancing over the two
BGP routes on Switch A can improve link usage.
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] balance 2
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
Verifying the configuration
# Display the BGP routing table on Switch A.
[SwitchA] display bgp routing-table ipv4
Total number of routes: 3
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
331
* > 8.1.1.0/24 8.1.1.1 0 32768 i
* >e 9.1.1.0/24 3.1.1.1 0 0 65009i
* >e 3.1.2.1 0 0 65009i
•
The route 9.1.1.0/24 has two next hops, 3.1.1.1 and 3.1.2.1, both of which are marked with a greater-than sign (>), indicating that they are the optimal routes.
•
By using the display ip routing-table command, you can find two routes to 9.1.1.0/24. One has next hop 3.1.1.1 and output interface VLAN-interface 200, and the other has next hop
3.1.2.1 and output interface VLAN-interface 300.
BGP community configuration example
Network requirements
As shown in Figure 72 , Switch B establishes EBGP connections with Switch A and Switch C.
Configure NO_EXPORT community attribute on Switch A to make routes from AS 10 not advertised by AS 20 to any other AS.
Figure 72 Network diagram
Loop0
1.1.1.1/32
Vlan-int100
9.1.1.1/24
Vlan-int200
200.1.2.1/24
Switch A
AS 10
EBGP
Loop0
2.2.2.2/32
Vlan-int200
200.1.2.2/24
AS 20
Vlan-int300
Switch B
200.1.3.1/24
EBGP
Vlan-int300
Loop0
3.3.3.3/32
200.1.3.2/24
Switch C
AS 30
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure EBGP connections:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 10
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 200.1.2.2 as-number 20
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 200.1.2.2 enable
[SwitchA-bgp-default-ipv4] network 9.1.1.0 255.255.255.0
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 20
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 200.1.2.1 as-number 10
[SwitchB-bgp-default] peer 200.1.3.2 as-number 30
[SwitchB-bgp-default] address-family ipv4 unicast
332
[SwitchB-bgp-default-ipv4] peer 200.1.2.1 enable
[SwitchB-bgp-default-ipv4] peer 200.1.3.2 enable
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 30
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 200.1.3.1 as-number 20
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 200.1.3.1 enable
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
# Display the BGP routing table on Switch B.
[SwitchB] display bgp routing-table ipv4 9.1.1.0
BGP local router ID: 2.2.2.2
Local AS number: 20
Paths: 1 available, 1 best
BGP routing table information of 9.1.1.0/24:
From : 200.1.2.1 (1.1.1.1)
Rely nexthop : 200.1.2.1
Original nexthop: 200.1.2.1
OutLabel : NULL
AS-path : 10
Origin : igp
Attribute value : pref-val 0
State : valid, external, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
# Display advertisement information of network 9.1.1.0 on Switch B.
[SwitchB] display bgp routing-table ipv4 9.1.1.0 advertise-info
BGP local router ID: 2.2.2.2
Local AS number: 20
Paths: 1 best
BGP routing table information of 9.1.1.0/24:
Advertised to peers (1 in total):
200.1.3.2
The output shows that Switch B can advertise the route with the destination 9.1.1.0/24 to other
ASs through BGP.
# Display the BGP routing table on Switch C.
[SwitchC] display bgp routing-table ipv4
333
Total number of routes: 1
BGP local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 9.1.1.0/24 200.1.3.1 0 20 10i
The output shows that Switch C has learned route 9.1.1.0/24 from Switch B.
3. Configure BGP community:
# Configure a routing policy.
[SwitchA] route-policy comm_policy permit node 0
[SwitchA-route-policy-comm_policy-0] apply community no-export
[SwitchA-route-policy-comm_policy-0] quit
# Apply the routing policy.
[SwitchA] bgp 10
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 200.1.2.2 route-policy comm_policy export
[SwitchA-bgp-default-ipv4] peer 200.1.2.2 advertise-community
Verifying the configuration
# Display the routing table on Switch B.
[SwitchB] display bgp routing-table ipv4 9.1.1.0
BGP local router ID: 2.2.2.2
Local AS number: 20
Paths: 1 available, 1 best
BGP routing table information of 9.1.1.0/24:
From : 200.1.2.1 (1.1.1.1)
Rely nexthop : 200.1.2.1
Original nexthop: 200.1.2.1
OutLabel : NULL
Community : No-Export
AS-path : 10
Origin : igp
Attribute value : pref-val 0
State : valid, external, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
# Display advertisement information for the route 9.1.1.0 on Switch B.
[SwitchB] display bgp routing-table ipv4 9.1.1.0 advertise-info
334
BGP local router ID: 2.2.2.2
Local AS number: 20
Paths: 1 best
BGP routing table information of 9.1.1.0/24:
Not advertised to any peers yet
# Display the BGP routing table on Switch C.
[SwitchC] display bgp routing-table ipv4
Total number of routes: 0
The output shows that BGP has not learned any route.
BGP route reflector configuration example
Network requirements
As shown in Figure 73 , all switches run BGP. Run EBGP between Switch A and Switch B, and run
IBGP between Switch C and Switch B, and between Switch C and Switch D.
Configure Switch C as a route reflector with clients Switch B and Switch D to allow Switch D to learn route 20.0.0.0/8 from Switch C.
Figure 73 Network diagram
Vlan-int100
20.1.1.1/8
Loop0
1.1.1.1/32
Switch A
Vlan-int200
192.1.1.1/24
Loop0
3.3.3.3/32
Vlan-int300
193.1.1.1/24
Switch C
Route reflector
Vlan-int400
194.1.1.1/24
Vlan-int200
192.1.1.2/24
Loop0
2.2.2.2/32
Vlan-int300
193.1.1.2/24
Vlan-int400
194.1.1.2/24
Loop0
4.4.4.4/32
AS 100 Switch B AS 200 Switch D
Configuration procedure
1. Configure IP addresses for interfaces and configure OSPF in AS 200. (Details not shown.)
2. Configure BGP connections:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 192.1.1.2 as-number 200
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 192.1.1.2 enable
# Inject network 20.0.0.0/8 to the BGP routing table.
[SwitchA-bgp-default-ipv4] network 20.0.0.0
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
335
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 192.1.1.1 as-number 100
[SwitchB-bgp-default] peer 193.1.1.1 as-number 200
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 192.1.1.1 enable
[SwitchB-bgp-default-ipv4] peer 193.1.1.1 enable
[SwitchB-bgp-default-ipv4] peer 193.1.1.1 next-hop-local
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 193.1.1.2 as-number 200
[SwitchC-bgp-default] peer 194.1.1.2 as-number 200
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 193.1.1.2 enable
[SwitchC-bgp-default-ipv4] peer 194.1.1.2 enable
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] bgp 200
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] peer 194.1.1.1 as-number 200
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] peer 194.1.1.1 enable
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
3. Configure Switch C as the route reflector.
[SwitchC] bgp 200
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 193.1.1.2 reflect-client
[SwitchC-bgp-default-ipv4] peer 194.1.1.2 reflect-client
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
Verifying the configuration
# Display the BGP routing table on Switch B.
[SwitchB] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
336
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 20.0.0.0 192.1.1.1 0 0 100i
# Display the BGP routing table on Switch D.
[SwitchD] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 4.4.4.4
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 20.0.0.0 193.1.1.2 0 100 0 100i
The output shows that Switch D has learned route 20.0.0.0/8 from Switch C.
BGP confederation configuration example
Network requirements
As shown in Figure 74 , split AS 200 into three sub-ASs (AS 65001, AS 65002, and AS 65003) to
reduce IBGP connections. Switches in AS 65001 are fully meshed.
Figure 74 Network diagram
Switch F Switch B
Switch C
Vlan-int600
Vlan-int200
Vlan-int300
AS 65002
AS 65003
Vlan-int100
AS 100
-int
300
Switch D
Vlan-int100
Switch A
Vlan-int500
Vlan-int500
Vlan-int400
Vlan-int200
AS 65001
Vlan-int200
Switch E
AS 200
Table 17 Interface and IP address assignment
Device
Switch A
Interface
Vlan-int100
Vlan-int200
Vlan-int300
Vlan-int400
IP address
200.1.1.1/24
10.1.1.1/24
10.1.2.1/24
10.1.3.1/24
Device
Switch D
Switch E
337
Interface
Vlan-int200
Vlan-int400
Vlan-int200
Vlan-int500
IP address
10.1.5.1/24
10.1.3.2/24
10.1.5.2/24
10.1.4.2/24
Device
Switch B
Interface
Vlan-int500
Vlan-int200
IP address
10.1.4.1/24
10.1.1.2/24
Device
Switch F
Switch C Vlan-int300 10.1.2.2/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure BGP confederation:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65001
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] confederation id 200
[SwitchA-bgp-default] confederation peer-as 65002 65003
[SwitchA-bgp-default] peer 10.1.1.2 as-number 65002
[SwitchA-bgp-default] peer 10.1.2.2 as-number 65003
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 10.1.1.2 enable
[SwitchA-bgp-default-ipv4] peer 10.1.2.2 enable
[SwitchA-bgp-default-ipv4] peer 10.1.1.2 next-hop-local
[SwitchA-bgp-default-ipv4] peer 10.1.2.2 next-hop-local
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65002
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] confederation id 200
[SwitchB-bgp-default] confederation peer-as 65001 65003
[SwitchB-bgp-default] peer 10.1.1.1 as-number 65001
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 10.1.1.1 enable
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65003
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] confederation id 200
[SwitchC-bgp-default] confederation peer-as 65001 65002
[SwitchC-bgp-default] peer 10.1.2.1 as-number 65001
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 10.1.2.1 enable
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
3. Configure IBGP connections in AS 65001:
Interface
Vlan-int100
Vlan-int600
338
IP address
200.1.1.2/24
9.1.1.1/24
# Configure Switch A.
[SwitchA] bgp 65001
[SwitchA-bgp-default] peer 10.1.3.2 as-number 65001
[SwitchA-bgp-default] peer 10.1.4.2 as-number 65001
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 10.1.3.2 enable
[SwitchA-bgp-default-ipv4] peer 10.1.4.2 enable
[SwitchA-bgp-default-ipv4] peer 10.1.3.2 next-hop-local
[SwitchA-bgp-default-ipv4] peer 10.1.4.2 next-hop-local
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] bgp 65001
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] confederation id 200
[SwitchD-bgp-default] peer 10.1.3.1 as-number 65001
[SwitchD-bgp-default] peer 10.1.5.2 as-number 65001
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] peer 10.1.3.1 enable
[SwitchD-bgp-default-ipv4] peer 10.1.5.2 enable
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
# Configure Switch E.
<SwitchE> system-view
[SwitchE] bgp 65001
[SwitchE-bgp-default] router-id 5.5.5.5
[SwitchE-bgp-default] confederation id 200
[SwitchE-bgp-default] peer 10.1.4.1 as-number 65001
[SwitchE-bgp-default] peer 10.1.5.1 as-number 65001
[SwitchE-bgp-default] address-family ipv4 unicast
[SwitchE-bgp-default-ipv4] peer 10.1.4.1 enable
[SwitchE-bgp-default-ipv4] peer 10.1.5.1 enable
[SwitchE-bgp-default-ipv4] quit
[SwitchE-bgp-default] quit
4. Configure the EBGP connection between AS 100 and AS 200:
# Configure Switch A.
[SwitchA] bgp 65001
[SwitchA-bgp-default] peer 200.1.1.2 as-number 100
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 200.1.1.2 enable
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch F.
<SwitchF> system-view
[SwitchF] bgp 100
[SwitchF-bgp-default] router-id 6.6.6.6
[SwitchF-bgp-default] peer 200.1.1.1 as-number 200
339
[SwitchF-bgp-default] address-family ipv4 unicast
[SwitchF-bgp-default-ipv4] peer 200.1.1.1 enable
[SwitchF-bgp-default-ipv4] network 9.1.1.0 255.255.255.0
[SwitchF-bgp-default-ipv4] quit
[SwitchF-bgp-default] quit
Verifying the configuration
# Display the routing table on Switch B.
[SwitchB] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 9.1.1.0/24 10.1.1.1 0 100 0 (65001)
100i
[SwitchB] display bgp routing-table ipv4 9.1.1.0
BGP local router ID: 2.2.2.2
Local AS number: 65002
Paths: 1 available, 1 best
BGP routing table information of 9.1.1.0/24:
From : 10.1.1.1 (1.1.1.1)
Rely nexthop : 10.1.1.1
Original nexthop: 10.1.1.1
OutLabel : NULL
AS-path : (65001) 100
Origin : igp
Attribute value : MED 0, localpref 100, pref-val 0, pre 255
State : valid, external-confed, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
# Display the BGP routing table on Switch D.
[SwitchD] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 4.4.4.4
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
340
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 9.1.1.0/24 10.1.3.1 0 100 0 100i
[SwitchD] display bgp routing-table ipv4 9.1.1.0
BGP local router ID: 4.4.4.4
Local AS number: 65001
Paths: 1 available, 1 best
BGP routing table information of 9.1.1.0/24:
From : 10.1.3.1 (1.1.1.1)
Rely nexthop : 10.1.3.1
Original nexthop: 10.1.3.1
OutLabel : NULL
AS-path : 100
Origin : igp
Attribute value : MED 0, localpref 100, pref-val 0, pre 255
State : valid, internal-confed, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
The output shows the following:
•
Switch F can send route information to Switch B and Switch C through the confederation by establishing only an EBGP connection with Switch A.
•
Switch B and Switch D are in the same confederation, but belong to different sub-ASs. They obtain external route information from Switch A, and generate identical BGP route entries although they have no direct connection in between.
BGP path selection configuration example
Network requirements
As shown in Figure 75 , all switches run BGP.
•
EBGP runs between Switch A and Switch B, and between Switch A and Switch C.
•
IBGP runs between Switch B and Switch D, and between Switch D and Switch C. OSPF is the
IGP protocol in AS 200.
Configure routing policies, making Switch D use the route 1.0.0.0/8 from Switch C as the optimal.
341
Figure 75 Network diagram
AS 200
AS 100 Vlan-int100 Vlan-int300
Vlan-int101
Switch B
Vlan-int300
Vlan-int100
Vlan-int200
Switch A Vlan-int200
Switch C
Table 18 Interface and IP address assignment
Vlan-int400
Switch D
Vlan-int400
Device
Switch A
Switch B
Interface
Vlan-int101
Vlan-int100
Vlan-int200
Vlan-int100
IP address
1.0.0.1/8
192.1.1.1/24
193.1.1.1/24
192.1.1.2/24
Device
Switch D
Switch C
Vlan-int300 194.1.1.2/24
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure OSPF on Switch B, Switch C, and Switch D:
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospf
[SwitchB-ospf] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 192.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ospf
[SwitchC-ospf] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 193.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] ospf
[SwitchD-ospf] area 0
[SwitchD-ospf-1-area-0.0.0.0] network 194.1.1.0 0.0.0.255
[SwitchD-ospf-1-area-0.0.0.0] network 195.1.1.0 0.0.0.255
Interface
Vlan-int400
Vlan-int300
Vlan-int400
Vlan-int200
342
IP address
195.1.1.1/24
194.1.1.1/24
195.1.1.2/24
193.1.1.2/24
[SwitchD-ospf-1-area-0.0.0.0] quit
[SwitchD-ospf-1] quit
3. Configure BGP connections:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA-bgp-default] peer 192.1.1.2 as-number 200
[SwitchA-bgp-default] peer 193.1.1.2 as-number 200
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 192.1.1.2 enable
[SwitchA-bgp-default-ipv4] peer 193.1.1.2 enable
# Inject network 1.0.0.0/8 to the BGP routing table on Switch A.
[SwitchA-bgp-default-ipv4] network 1.0.0.0 8
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
[SwitchB] bgp 200
[SwitchB-bgp-default] peer 192.1.1.1 as-number 100
[SwitchB-bgp-default] peer 194.1.1.1 as-number 200
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 192.1.1.1 enable
[SwitchB-bgp-default-ipv4] peer 194.1.1.1 enable
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
[SwitchC] bgp 200
[SwitchC-bgp-default] peer 193.1.1.1 as-number 100
[SwitchC-bgp-default] peer 195.1.1.1 as-number 200
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 193.1.1.1 enable
[SwitchC-bgp-default-ipv4] peer 195.1.1.1 enable
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
# Configure Switch D.
[SwitchD] bgp 200
[SwitchD-bgp-default] peer 194.1.1.2 as-number 200
[SwitchD-bgp-default] peer 195.1.1.2 as-number 200
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] peer 194.1.1.2 enable
[SwitchD-bgp-default-ipv4] peer 195.1.1.2 enable
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
4. Configure local preference for route 1.0.0.0/8, making Switch D give priority to the route learned from Switch C:
# Define IPv4 basic ACL 2000 on Switch C to permit route 1.0.0.0/8.
[SwitchC] acl basic 2000
[SwitchC-acl-ipv4-basic-2000] rule permit source 1.0.0.0 0.255.255.255
[SwitchC-acl-ipv4-basic-2000] quit
343
# Configure a routing policy named localpref on Switch C, setting the local preference of route
1.0.0.0/8 to 200 (the default is 100).
[SwitchC] route-policy localpref permit node 10
[SwitchC-route-policy-localpref-10] if-match ip address acl 2000
[SwitchC-route-policy-localpref-10] apply local-preference 200
[SwitchC-route-policy-localpref-10] quit
# Apply routing policy localpref to routes from peer 193.1.1.1.
[SwitchC] bgp 200
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 193.1.1.1 route-policy localpref import
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
# Display the BGP routing table on Switch D.
[SwitchD] display bgp routing-table ipv4
Total number of routes: 2
BGP local router ID is 195.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >i 1.0.0.0 193.1.1.1 200 0 100i
* i 192.1.1.1 100 0 100i
Route 1.0.0.0/8 learned from Switch C is the optimal.
BGP GR configuration example
Network requirements
As shown in Figure 76 , all switches run BGP. EBGP runs between Switch A and Switch B. IBGP runs
between Switch B and Switch C.
Enable GR capability for BGP so that the communication between Switch A and Switch C is not affected when an active/standby switchover occurs on Switch B.
Figure 76 Network diagram
AS 65008 AS 65009
Vlan-int100
8.1.1.1/8
Switch A
( GR helper )
Vlan-int200
200.1.1.2/24
Vlan-int200
200.1.1.1/24
Vlan-int400
9.1.1.1/24
Switch B
( GR restarter )
Vlan-int400
9.1.1.2/24
Switch C
( GR helper )
Configuration procedure
1. Configure Switch A:
# Configure IP addresses for interfaces. (Details not shown.)
# Configure the EBGP connection.
344
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 200.1.1.1 as-number 65009
# Enable GR capability for BGP.
[SwitchA-bgp-default] graceful-restart
# Inject network 8.0.0.0/8 to the BGP routing table.
[SwitchA-bgp-default] address-family ipv4
[SwitchA-bgp-default-ipv4] network 8.0.0.0
# Enable Switch A to exchange IPv4 unicast routing information with Switch B.
[SwitchA-bgp-default-ipv4] peer 200.1.1.1 enable
2. Configure Switch B:
# Configure IP addresses for interfaces. (Details not shown.)
# Configure the EBGP connection.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 200.1.1.2 as-number 65008
# Configure the IBGP connection.
[SwitchB-bgp-default] peer 9.1.1.2 as-number 65009
# Enable GR capability for BGP.
[SwitchB-bgp-default] graceful-restart
# Inject networks 200.1.1.0/24 and 9.1.1.0/24 to the BGP routing table.
[SwitchB-bgp-default] address-family ipv4
[SwitchB-bgp-default-ipv4] network 200.1.1.0 24
[SwitchB-bgp-default-ipv4] network 9.1.1.0 24
# Enable Switch B to exchange IPv4 unicast routing information with Switch A and Switch C.
[SwitchB-bgp-default-ipv4] peer 200.1.1.2 enable
[SwitchB-bgp-default-ipv4] peer 9.1.1.2 enable
3. Configure Switch C:
# Configure IP addresses for interfaces. (Details not shown.)
# Configure the IBGP connection.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 9.1.1.1 as-number 65009
# Enable GR capability for BGP.
[SwitchC-bgp-default] graceful-restart
# Enable Switch C to exchange IPv4 unicast routing information with Switch B.
[SwitchC-bgp-default-ipv4] peer 9.1.1.1 enable
Verifying the configuration
Ping Switch C on Switch A. Meanwhile, perform an active/standby switchover on Switch B. The ping operation is successful during the whole switchover process. (Details not shown.)
345
BFD for BGP configuration example
Network requirements
As shown in Figure 77 , configure OSPF as the IGP in AS 200.
•
Establish two IBGP connections between Switch A and Switch C. When both paths operate correctly, Switch C uses the path Switch A<—>Switch B<—>Switch C to exchange packets with network 1.1.1.0/24.
•
Configure BFD over the path. When the path fails, BFD can quickly detect the failure and notify it to BGP. Then, the path Switch A<—>Switch D<—>Switch C takes effect immediately.
Figure 77 Network diagram
AS 100 1.1.1.0/24
Switch B
Vlan-int100 Vlan-int101
Vlan-int100 Vlan-int101
Switch A
Vlan-int200
AS 200
Vlan-int201
Switch C
AS 300
Vlan-int200
Switch D
Vlan-int201
Table 19 Interface and IP address assignment
Device
Switch A
Switch B
Interface
Vlan-int100
Vlan-int200
Vlan-int100
IP address
3.0.1.1/24
2.0.1.1/24
3.0.1.2/24
Device
Switch C
Switch D
Interface
Vlan-int101
Vlan-int201
Vlan-int200
IP address
3.0.2.2/24
2.0.2.2/24
2.0.1.2/24
Vlan-int101
Configuration procedure
3.0.2.1/24 Vlan-int201 2.0.2.1/24
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure OSPF to ensure that Switch A and Switch C are reachable to each other. (Details not shown.)
3. Configure BGP on Switch A:
# Establish two IBGP connections to Switch C.
<SwitchA> system-view
[SwitchA] bgp 200
[SwitchA-bgp-default] peer 3.0.2.2 as-number 200
[SwitchA-bgp-default] peer 2.0.2.2 as-number 200
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 3.0.2.2 enable
346
[SwitchA-bgp-default-ipv4] peer 2.0.2.2 enable
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Create IPv4 basic ACL 2000 to permit 1.1.1.0/24 to pass.
[SwitchA] acl basic 2000
[SwitchA-acl-ipv4-basic-2000] rule permit source 1.1.1.0 0.0.0.255
[SwitchA-acl-ipv4-basic-2000] quit
# Create two routing policies to set the MED for route 1.1.1.0/24. The policy apply_med_50 sets the MED to 50, and the policy apply_med_100 sets the MED to 100.
[SwitchA] route-policy apply_med_50 permit node 10
[SwitchA-route-policy-apply_med_50-10] if-match ip address acl 2000
[SwitchA-route-policy-apply_med_50-10] apply cost 50
[SwitchA-route-policy-apply_med_50-10] quit
[SwitchA] route-policy apply_med_100 permit node 10
[SwitchA-route-policy-apply_med_100-10] if-match ip address acl 2000
[SwitchA-route-policy-apply_med_100-10] apply cost 100
[SwitchA-route-policy-apply_med_100-10] quit
# Apply routing policy apply_med_50 to routes outgoing to peer 3.0.2.2, and apply routing policy apply_med_100 to routes outgoing to peer 2.0.2.2.
[SwitchA] bgp 200
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 3.0.2.2 route-policy apply_med_50 export
[SwitchA-bgp-default-ipv4] peer 2.0.2.2 route-policy apply_med_100 export
[SwitchA-bgp-default-ipv4] quit
# Enable BFD for peer 3.0.2.2.
[SwitchA-bgp-default] peer 3.0.2.2 bfd
[SwitchA-bgp-default] quit
4. Configure BGP on Switch C:
# Establish two IBGP connections to Switch A.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] peer 3.0.1.1 as-number 200
[SwitchC-bgp-default] peer 2.0.1.1 as-number 200
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 3.0.1.1 enable
[SwitchC-bgp-default-ipv4] peer 2.0.1.1 enable
[SwitchC-bgp-default-ipv4] quit
# Enable BFD for peer 3.0.1.1.
[SwitchC-bgp-default] peer 3.0.1.1 bfd
[SwitchC-bgp-default] quit
[SwitchC] quit
Verifying the configuration
# Display detailed BFD session information on Switch C.
<SwitchC> display bfd session verbose
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv4 Session Working Under Ctrl Mode:
347
Local Discr: 513 Remote Discr: 513
Source IP: 3.0.2.2 Destination IP: 3.0.1.1
Session State: Up Interface: N/A
Min Tx Inter: 500ms Act Tx Inter: 500ms
Min Rx Inter: 500ms Detect Inter: 2500ms
Rx Count: 135 Tx Count: 135
Connect Type: Indirect Running Up for: 00:00:58
Hold Time: 2457ms Auth mode: None
Detect Mode: Async Slot: 0
Protocol: BGP
Version: 1
Diag Info: No Diagnostic
The output shows that a BFD session has been established between Switch A and Switch C.
# Display BGP peer information on Switch C.
<SwitchC> display bgp peer ipv4
BGP local router ID: 3.3.3.3
Local AS number: 200
Total number of peers: 2 Peers in established state: 2
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2.0.1.1 200 4 5 0 0 00:01:55 Established
3.0.1.1 200 4 5 0 0 00:01:52 Established
The output shows that Switch C has established two BGP connections with Switch A, and both connections are in Established state.
# Display route 1.1.1.0/24 on Switch C.
<SwitchC> display ip routing-table 1.1.1.0 24 verbose
Summary count : 1
Destination: 1.1.1.0/24
Protocol: BGP Process ID: 0
SubProtID: 0x1 Age: 00h00m09s
Cost: 50 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x15000001 LastAs: 0
AttrID: 0x1 Neighbor: 3.0.1.1
Flags: 0x10060 OrigNextHop: 3.0.1.1
Label: NULL RealNextHop: 3.0.2.1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface101
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
348
Connector: N/A
The output shows that Switch C communicates with network 1.1.1.0/24 through the path Switch
C<—>Switch B<—>Switch A.
# Break down the path Switch C<—>Switch B<—>Switch A and then display route 1.1.1.0/24 on
Switch C.
<SwitchC> display ip routing-table 1.1.1.0 24 verbose
Summary count : 1
Destination: 1.1.1.0/24
Protocol: BGP Process ID: 0
SubProtID: 0x1 Age: 00h03m08s
Cost: 100 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 0
NibID: 0x15000000 LastAs: 0
AttrID: 0x0 Neighbor: 2.0.1.1
Flags: 0x10060 OrigNextHop: 2.0.1.1
Label: NULL RealNextHop: 2.0.2.1
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface201
BkTunnel ID: Invalid BkInterface: N/A
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
The output shows that Switch C communicates with network 1.1.1.0/24 through the path Switch
C<—>Switch D<—>Switch A.
BGP FRR configuration example
Network requirements
As shown in Figure 78 , configure BGP FRR so that when Link B fails, BGP uses Link A to forward
traffic.
349
Figure 78 Network diagram
Switch A
Vlan-int 100
10.1.1.1/24
Loop0
2.2.2.2/32
Vlan-int 100
10.1.1.2/24
Switch B
Link B
Vlan-int 101
20.1.1.2/24
AS 200
Vlan-int 101
20.1.1.4/24
Switch D
AS 100 Vlan-int 200
30.1.1.1/24
Vlan-int 200
30.1.1.3/24
Link A
Switch C
Vlan-int 201
40.1.1.3/24
Vlan-int 201
40.1.1.4/24
Loop0
3.3.3.3/32
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure OSPF in AS 200 to ensure connectivity among Switch B, Switch C, and Switch D.
(Details not shown.)
3. Configure BGP connections:
# Configure Switch A to establish EBGP sessions to Switch B and Switch C, and advertise network 1.1.1.1/32.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 10.1.1.2 as-number 200
[SwitchA-bgp-default] peer 30.1.1.3 as-number 200
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] peer 10.1.1.2 enable
[SwitchA-bgp-default-ipv4] peer 30.1.1.3 enable
[SwitchA-bgp-default-ipv4] network 1.1.1.1 32
# Configure Switch B to establish an EBGP session to Switch A, and an IBGP session to Switch
D.
<SwitchB> system-view
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 10.1.1.1 as-number 100
[SwitchB-bgp-default] peer 4.4.4.4 as-number 200
[SwitchB-bgp-default] peer 4.4.4.4 connect-interface loopback 0
[SwitchB-bgp-default] address-family ipv4 unicast
[SwitchB-bgp-default-ipv4] peer 10.1.1.1 enable
[SwitchB-bgp-default-ipv4] peer 4.4.4.4 enable
[SwitchB-bgp-default-ipv4] peer 4.4.4.4 next-hop-local
[SwitchB-bgp-default-ipv4] quit
[SwitchB-bgp-default] quit
350
# Configure Switch C to establish an EBGP session to Switch A, and an IBGP session to Switch
D.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 30.1.1.1 as-number 100
[SwitchC-bgp-default] peer 4.4.4.4 as-number 200
[SwitchC-bgp-default] peer 4.4.4.4 connect-interface loopback 0
[SwitchC-bgp-default] address-family ipv4 unicast
[SwitchC-bgp-default-ipv4] peer 30.1.1.1 enable
[SwitchC-bgp-default-ipv4] peer 4.4.4.4 enable
[SwitchC-bgp-default-ipv4] peer 4.4.4.4 next-hop-local
[SwitchC-bgp-default-ipv4] quit
[SwitchC-bgp-default] quit
# Configure Switch D to establish IBGP sessions to Switch B and Switch C, and advertise network 4.4.4.4/32.
<SwitchD> system-view
[SwitchD] bgp 200
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] peer 2.2.2.2 as-number 200
[SwitchD-bgp-default] peer 2.2.2.2 connect-interface loopback 0
[SwitchD-bgp-default] peer 3.3.3.3 as-number 200
[SwitchD-bgp-default] peer 3.3.3.3 connect-interface loopback 0
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] peer 2.2.2.2 enable
[SwitchD-bgp-default-ipv4] peer 3.3.3.3 enable
[SwitchD-bgp-default-ipv4] network 4.4.4.4 32
4. Configure preferred values so Link B is used to forward traffic between Switch A and Switch D:
# Configure Switch A to set the preferred value to 100 for routes received from Switch B.
[SwitchA-bgp-default-ipv4] peer 10.1.1.2 preferred-value 100
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# Configure Switch D to set the preferred value to 100 for routes received from Switch B.
[SwitchD-bgp-default-ipv4] peer 2.2.2.2 preferred-value 100
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
5. Configure BGP FRR:
# On Switch A, set the source address of BFD echo packets to 11.1.1.1.
[SwitchA] bfd echo-source-ip 11.1.1.1
# Create routing policy frr to set a backup next hop 30.1.1.3 (Switch C) for the route destined for
4.4.4.4/32.
[SwitchA] ip prefix-list abc index 10 permit 4.4.4.4 32
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy] if-match ip address prefix-list abc
[SwitchA-route-policy] apply fast-reroute backup-nexthop 30.1.1.3
[SwitchA-route-policy] quit
# Use echo-mode BFD to detect the connectivity to Switch D.
[SwitchA] bgp 100
351
[SwitchA-bgp-default] primary-path-detect bfd echo
# Apply the routing policy to BGP FRR for BGP IPv4 unicast address family.
[SwitchA-bgp-default] address-family ipv4 unicast
[SwitchA-bgp-default-ipv4] fast-reroute route-policy frr
[SwitchA-bgp-default-ipv4] quit
[SwitchA-bgp-default] quit
# On Switch D, set the source address of BFD echo packets to 44.1.1.1.
[SwitchD] bfd echo-source-ip 44.1.1.1
# Create routing policy frr to set a backup next hop 3.3.3.3 (Switch C) for the route destined for
1.1.1.1/32.
[SwitchD] ip prefix-list abc index 10 permit 1.1.1.1 32
[SwitchD] route-policy frr permit node 10
[SwitchD-route-policy] if-match ip address prefix-list abc
[SwitchD-route-policy] apply fast-reroute backup-nexthop 3.3.3.3
[SwitchD-route-policy] quit
# Use echo-mode BFD to detect the connectivity to Switch A.
[SwitchD] bgp 200
[SwitchD-bgp-default] primary-path-detect bfd echo
# Apply the routing policy to BGP FRR for BGP IPv4 unicast address family.
[SwitchD-bgp-default] address-family ipv4 unicast
[SwitchD-bgp-default-ipv4] fast-reroute route-policy frr
[SwitchD-bgp-default-ipv4] quit
[SwitchD-bgp-default] quit
Verifying the configuration
# Display detailed information about the route to 4.4.4.4/32 on Switch A. The output shows the backup next hop for the route.
[SwitchA] display ip routing-table 4.4.4.4 32 verbose
Summary count : 1
Destination: 4.4.4.4/32
Protocol: BGP Process ID: 0
SubProtID: 0x2 Age: 00h01m52s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 200
NibID: 0x15000003 LastAs: 200
AttrID: 0x5 Neighbor: 10.1.1.2
Flags: 0x10060 OrigNextHop: 10.1.1.2
Label: NULL RealNextHop: 10.1.1.2
BkLabel: NULL BkNextHop: 30.1.1.3
Tunnel ID: Invalid Interface: Vlan-interface 100
BkTunnel ID: Invalid BkInterface: Vlan-interface 200
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
352
# Display detailed information about the route to 1.1.1.1/32 on Switch D. The output shows the backup next hop for the route.
[SwitchD] display ip routing-table 1.1.1.1 32 verbose
Summary count : 1
Destination: 1.1.1.1/32
Protocol: BGP Process ID: 0
SubProtID: 0x1 Age: 00h00m36s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0x2 OrigAs: 100
NibID: 0x15000003 LastAs: 100
AttrID: 0x1 Neighbor: 2.2.2.2
Flags: 0x10060 OrigNextHop: 2.2.2.2
Label: NULL RealNextHop: 20.1.1.2
BkLabel: NULL BkNextHop: 40.1.1.3
Tunnel ID: Invalid Interface: Vlan-interface 101
BkTunnel ID: Invalid BkInterface: Vlan-interface 201
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
Multicast BGP configuration example
Network requirements
As shown in Figure 79 , OSPF runs within AS 100 and AS 200 to ensure intra-AS connectivity. MBGP
runs between the two ASs to exchange IPv4 unicast routes used for RPF check.
•
Configure the Loopback 0 interface of Switch A and Switch B as the C-BSR and C-RP.
•
Configure Switch A and Switch B to establish a Multicast Source Discovery Protocol (MSDP) peer relationship through MBGP, so that the receiver can receive multicast traffic from the source.
353
Figure 79 Network diagram
AS 100
Loop0
AS 200
Vlan-int101
Switch A
Vlan-int100
Source
Switch D
Vlan-int101 Switch B
Vlan
-int
102
Receiver
Vlan
-int
103
Vlan
-int
103
Vlan-int104
Vlan
-int
102
Vlan-int104
-int
200
Vlan
Switch C
PIM-SM 1
Loop0
MBGP peers
Table 20 Interface and IP address assignment
PIM-SM 2
Loop0
Device Interface IP address
Source N/A 10.110.1.100/24
Switch A Vlan-int100 10.110.1.1/24
Vlan-int101 192.168.1.1/24
Loop0 1.1.1.1/32
Switch B Vlan-int101 192.168.1.2/24
Vlan-int102 192.168.2.1/24
Vlan-int103 192.168.3.1/24
Device
Switch C
Switch D
Interface
Vlan-int200
Vlan-int102
Vlan-int104
Loop0
Vlan-int103
Vlan-int104
Loop0
IP address
10.110.2.1/24
192.168.2.2/24
192.168.4.1/24
3.3.3.3/32
192.168.3.2/24
192.168.4.2/24
4.4.4.4/32
Loop0 2.2.2.2/32
Configuration procedure
1. Configure IP addresses for interfaces and configure OSPF (this example uses OSPF process 1) in AS 200 to ensure intra-AS connectivity. (Details not shown.)
2. Enable IP multicast routing, PIM-SM, and IGMP, and configure BSR boundaries:
# On Switch A, enable multicast routing globally, and enable PIM-SM on interfaces.
<SwitchA> system-view
[SwitchA] multicast routing
[SwitchA-mrib] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] pim sm
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] pim sm
[SwitchA-Vlan-interface101] quit
# Configure Switch B and Switch D in the same way that Switch A was configured.
# On Switch C, enable multicast routing globally.
<SwitchC> system-view
354
Loop0
[SwitchC] multicast routing
[SwitchA-mrib] quit
# Enable PIM-SM on interfaces, and enable IGMP on VLAN-interface 200.
[SwitchC] interface vlan-interface 102
[SwitchC-Vlan-interface102] pim sm
[SwitchC-Vlan-interface102] quit
[SwitchC] interface vlan-interface 104
[SwitchC-Vlan-interface104] pim sm
[SwitchC-Vlan-interface104] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] pim sm
[SwitchC-Vlan-interface200] igmp enable
[SwitchC-Vlan-interface200] quit
# Configure the BSR boundary on Switch A.
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] pim bsr-boundary
[SwitchA-Vlan-interface101] quit
# Configure the BSR boundary on Switch B.
[SwitchB] interface vlan-interface 101
[SwitchB-Vlan-interface101] pim bsr-boundary
[SwitchB-Vlan-interface101] quit
3. Configure Loopback 0, C-BSR, and C-RP:
# Configure the Loopback 0 interface and specify it as the C-BSR and C-RP on Switch A.
[SwitchA] interface loopback 0
[SwitchA-LoopBack0] ip address 1.1.1.1 32
[SwitchA-LoopBack0] pim sm
[SwitchA-LoopBack0] quit
[SwitchA] pim
[SwitchA-pim] c-bsr 1.1.1.1
[SwitchA-pim] c-rp 1.1.1.1
[SwitchA-pim] quit
# Configure the Loopback 0 interface and specify it as the C-BSR and C-RP on Switch B.
[SwitchB] interface loopback 0
[SwitchB-LoopBack0] ip address 2.2.2.2 32
[SwitchB-LoopBack0] pim sm
[SwitchB-LoopBack0] quit
[SwitchB] pim
[SwitchB-pim] c-bsr 2.2.2.2
[SwitchB-pim] c-rp 2.2.2.2
[SwitchB-pim] quit
4. Configure BGP to establish BGP IPv4 multicast peers and redistribute routes:
# On Switch A, establish an EBGP session to Switch B.
[SwitchA] bgp 100
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 192.168.1.2 as-number 200
# Enable exchange of IPv4 unicast routes used for RPF check with Switch B.
[SwitchA-bgp-default] address-family ipv4 multicast
355
[SwitchA-bgp-default-mul-ipv4] peer 192.168.1.2 enable
# Redistribute direct routes into BGP.
[SwitchA-bgp-default-mul-ipv4] import-route direct
[SwitchA-bgp-default-mul-ipv4] quit
[SwitchA-bgp-default] quit
# On Switch B, establish an EBGP session to Switch A.
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 192.168.1.1 as-number 100
# Enable exchange of IPv4 unicast routes used for RPF check with Switch B.
[SwitchB-bgp-default] address-family ipv4 multicast
[SwitchB-bgp-default-mul-ipv4] peer 192.168.1.1 enable
# Redistribute OSPF routes into BGP.
[SwitchB-bgp-default-mul-ipv4] import-route ospf 1
[SwitchB-bgp-default-mul-ipv4] quit
[SwitchB-bgp-default] quit
5. Configure MSDP peers:
# Configure an MSDP peer on Switch A.
[SwitchA] msdp
[SwitchA-msdp] peer 192.168.1.2 connect-interface vlan-interface 101
[SwitchA-msdp] quit
# Configure an MSDP peer on Switch B.
[SwitchB] msdp
[SwitchB-msdp] peer 192.168.1.1 connect-interface vlan-interface 101
[SwitchB-msdp] quit
Verifying the configuration
# Verify the BGP IPv4 multicast peer information on Switch B.
[SwitchB] display bgp peer ipv4 multicast
BGP local router ID : 2.2.2.2
Local AS number : 200
Total number of peers : 3 Peers in established state : 3
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
192.168.1.1 100 56 56 0 0 00:40:54 Established
# Verify the MSDP peer information on Switch B.
[SwitchB] display msdp brief
Configured Established Listen Connect Shutdown Disabled
1 1 0 0 0 0
Peer address State Up/Down time AS SA count Reset count
192.168.1.1 Established 00:07:17 100 1 0
356
Dynamic BGP peer configuration example
Network requirements
As shown in Figure 80 , Switch A needs to establish IBGP peer relationships with Switch B, Switch C,
and Switch D in network 10.1.0.0/16. Configure dynamic BGP peers to simplify the configuration.
Configure Switch A as the route reflector, and configure Switch B, Switch C, and Switch D as its clients.
Figure 80 Network diagram
AS 200
Vlan-int10
10.1.1.2/24
Switch B
Vlan-int10
10.1.1.1/24
Switch A
Vlan-int30
10.1.3.1/24
Vlan-int20
10.1.2.1/24
Vlan-int20
10.1.2.2/24
S2/1
Switch C
Vlan-int9
9.1.1.1
Vlan-int30
10.1.3.2/24
Switch D
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure IBGP peer relationship:
# Configure Switch A to establish dynamic BGP peer relationships with switches in network
10.1.0.0/16.
<SwitchA> system-view
[SwitchA] bgp 200
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 10.1.0.0 16 as-number 200
[SwitchA-bgp-default] address-family ipv4
[SwitchA-bgp-default-ipv4] peer 10.1.0.0 16 enable
# Configure Switch B to establish an IBGP peer relationship with Switch A.
<SwitchB> system-view
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 10.1.1.1 as-number 200
[SwitchB-bgp-default] address-family ipv4
[SwitchB-bgp-default-ipv4] peer 10.1.1.1 enable
# Configure Switch C to establish an IBGP peer relationship with Switch A.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] router-id 3.3.3.3
357
[SwitchC-bgp-default] peer 10.1.2.1 as-number 200
[SwitchC-bgp-default] address-family ipv4
[SwitchC-bgp-default-ipv4] peer 10.1.2.1 enable
# Configure Switch D to establish an IBGP peer relationship with Switch A.
<SwitchD> system-view
[SwitchD] bgp 200
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] peer 10.1.3.1 as-number 200
[SwitchD-bgp-default] address-family ipv4
[SwitchD-bgp-default-ipv4] peer 10.1.3.1 enable
# Display BGP peer information on Switch A. The output shows that Switch A has established
IBGP peer relationships with Switch B, Switch C, and Switch D.
[SwitchA] display bgp peer ipv4
BGP local router ID : 1.1.1.1
Local AS number : 200
Total number of peers : 3 Peers in established state : 3
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
*10.1.1.2 200 7 10 0 0 00:06:09 Established
*10.1.2.2 200 7 10 0 0 00:06:09 Established
*10.1.3.2 200 7 10 0 0 00:06:09 Established
3. Configure Switch A as the route reflector, and configure peers in network 10.1.0.0/16 as its clients.
[SwitchA-bgp-default-ipv4] peer 10.1.0.0 16 reflect-client
4. Configure Switch C to advertise network 9.1.1.0/24.
[SwitchC-bgp-default-ipv4] network 9.1.1.0 24
Verifying the configuration
# Verify that route 9.1.1.0/24 exists in the BGP routing table on Switch A, Switch B, and Switch D.
This example uses Switch A.
[SwitchA-bgp-default] display bgp routing-table ipv4
Total Number of Routes: 1
BGP Local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* i 9.1.1.0/24 10.1.2.2 0 100 0 ?
358
BGP LS configuration example
Network requirements
As shown in Figure 81 , all switches run BGP. Run IBGP between Switch A and Switch B, between
Switch B and Switch C, and between Switch B and Switch D.
Configure Switch B as a route reflector with client Switch A to allow Switch A to learn LS information advertised by Switch C and Switch D.
Figure 81 Network diagram
Switch C
Switch A
Vlan-int11
192.1.1.1/24
Vlan
-int12
/24
193.
1.1.1
Vlan-int11
192.1.1.2/24
Switch B
Vlan
-int12
/24
193.
1.1.2
Vlan
-int13
194.1.1
.2/24
Vlan
194.1.1
-int13
.1/24
Switch D
Configuration procedure
1. Configure IP addresses for interfaces and configure OSPF on Switch C and Switch D. (Details not shown.)
2. Configure BGP connections:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA-bgp-default] peer 192.1.1.2 as-number 100
[SwitchA-bgp-default] address-family link-state
[SwitchA-bgp-default-ls] peer 192.1.1.2 enable
[SwitchA-bgp-default-ls] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 100
[SwitchB-bgp-default] peer 192.1.1.1 as-number 100
[SwitchB-bgp-default] peer 193.1.1.1 as-number 100
[SwitchB-bgp-default] peer 194.1.1.1 as-number 100
[SwitchB-bgp-default] address-family link-state
[SwitchB-bgp-default-ls] peer 192.1.1.1 enable
[SwitchB-bgp-default-ls] peer 193.1.1.1 enable
[SwitchB-bgp-default-ls] peer 194.1.1.1 enable
[SwitchB-bgp-default-ls] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 100
[SwitchC-bgp-default] peer 193.1.1.2 as-number 100
[SwitchC-bgp-default] address-family link-state
359
[SwitchC-bgp-default-ls] peer 193.1.1.2 enable
[SwitchC-bgp-default-ls] quit
[SwitchC-bgp-default] quit
[SwitchC] ospf
[SwitchC-ospf-1] distribute bgp-ls
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 0.0.0.0 0.0.0.0
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] bgp 100
[SwitchD-bgp-default] peer 194.1.1.2 as-number 100
[SwitchD-bgp-default] address-family link-state
[SwitchD-bgp-default-ls] peer 194.1.1.2 enable
[SwitchD-bgp-default-ls] quit
[SwitchD-bgp-default] quit
[SwitchD] ospf
[SwitchD-ospf-1] distribute bgp-ls
[SwitchD-ospf-1] area 0
[SwitchD-ospf-1-area-0.0.0.0] network 0.0.0.0 0.0.0.0
[SwitchD-ospf-1-area-0.0.0.0] quit
[SwitchD-ospf-1] quit
3. Configure Switch B as the route reflector.
[SwitchB] bgp 100
[SwitchB-bgp-default] address-family link-state
[SwitchB-bgp-default-ls] peer 192.1.1.1 reflect-client
[SwitchB-bgp-default-ls] quit
[SwitchB-bgp-default] quit
Verifying the configuration
# Verify that Switch A has learned LS information advertised by Switch C and Switch D.
[SwitchA] display bgp link-state
Total number of routes: 4
BGP local Switch ID is 192.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Prefix codes: E link, V node, T IP reacheable route, u/U unknown,
I Identifier, N local node, R remote node, L link, P prefix,
L1/L2 ISIS level-1/level-2, O OSPF, D direct, S static,
a area-ID, , l link-ID, t topology-ID, s ISO-ID,
c confed-ID/ASN, b bgp-identifier, r Switch-ID,
i if-address, n nbr-address, o OSPF Route-type, p IP-prefix
d designated Switch address i Network : [V][O][I0x0][N[c100][b193.1.1.1][a0.0.0.0][r193.1.1.1]]/376
NextHop : 193.1.1.1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED :
360
Path/Ogn: i i Network : [V][O][I0x0][N[c100][b194.1.1.1][a0.0.0.0][r194.1.1.1]]/376
NextHop : 194.1.1.1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: i i Network :
[T][O][I0x0][N[c100][b193.1.1.1][a0.0.0.0][r193.1.1.1]][P[o0x1][p193.1.1.0/24]]/480
NextHop : 193.1.1.1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: i i Network :
[T][O][I0x0][N[c100][b194.1.1.1][a0.0.0.0][r194.1.1.1]][P[o0x1][p194.1.1.0/24]]/480
NextHop : 194.1.1.1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED :
Path/Ogn: i
IPv6 BGP configuration examples
IPv6 BGP basic configuration example
Network requirements
As shown in Figure 82 , all switches run BGP. Run EBGP between Switch A and Switch B, and run
IBGP between Switch B and Switch C to allow Switch C to access network 50::/64 connected to
Switch A.
Figure 82 Network diagram
Vlan-int50
50::1/64
Loop0
1.1.1.1/32
AS 65008
EBGP
AS 65009
Loop0
2.2.2.2/32
Vlan-int10
Switch A
10::2/64
Vlan-int10
10::1/64
Switch B
Vlan-int9
9::1/64
IBGP
Loop0
3.3.3.3/32
Vlan-int9
9::2/64
Switch C
Configuration procedure
1. Configure IP addresses for interfaces. (Details not shown.)
2. Configure IBGP:
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65009
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 9::2 as-number 65009
[SwitchB-bgp-default] address-family ipv6
[SwitchB-bgp-default-ipv6] peer 9::2 enable
[SwitchB-bgp-default-ipv6] quit
361
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 9::1 as-number 65009
[SwitchC-bgp-default] address-family ipv6
[SwitchC-bgp-default-ipv6] peer 9::1 enable
3. Configure EBGP:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 10::1 as-number 65009
[SwitchA-bgp-default] address-family ipv6
[SwitchA-bgp-default-ipv6] peer 10::1 enable
# Configure Switch B.
[SwitchB-bgp-default] peer 10::2 as-number 65008
[SwitchB-bgp-default] address-family ipv6
[SwitchB-bgp-default-ipv6] peer 10::2 enable
4. Inject network routes to the BGP routing table:
# Configure Switch A.
[SwitchA-bgp-default-ipv6] network 10:: 64
[SwitchA-bgp-default-ipv6] network 50:: 64
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
[SwitchB-bgp-default-ipv6] network 10:: 64
[SwitchB-bgp-default-ipv6] network 9:: 64
[SwitchB-bgp-default-ipv6] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
[SwitchC-bgp-default-ipv6] network 9:: 64
[SwitchC-bgp-default-ipv6] quit
[SwitchC-bgp-default] quit
Verifying the configuration
# Display IPv6 BGP peer information on Switch B.
[SwitchB] display bgp peer ipv6
BGP local router ID: 2.2.2.2
Local AS number: 65009
Total number of peers: 2 Peers in established state: 2
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
9::2 65009 41 43 0 1 00:29:00 Established
10::2 65008 38 38 0 2 00:27:20 Established
362
The output shows that Switch A and Switch B have established an EBGP connection, and Switch B and Switch C have established an IBGP connection.
# Display IPv6 BGP routing table information on Switch A.
[SwitchA] display bgp routing-table ipv6
Total number of routes: 4
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* >e Network : 9:: PrefixLen : 64
NextHop : 10::1 LocPrf :
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: 65009i
* > Network : 10:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: i
* e Network : 10:: PrefixLen : 64
NextHop : 10::1 LocPrf :
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: 65009i
* > Network : 50:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: i
The output shows that Switch A has learned routing information of AS 65009.
# Display IPv6 BGP routing table information on Switch C.
[SwitchC] display bgp routing-table ipv6
Total number of routes: 4
BGP local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 9:: PrefixLen : 64
NextHop : :: LocPrf :
363
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: i
* i Network : 9:: PrefixLen : 64
NextHop : 9::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
* >i Network : 10:: PrefixLen : 64
NextHop : 9::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
* >i Network : 50:: PrefixLen : 64
NextHop : 10::2 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: 65008i
The output shows that Switch C has learned the route 50::/64.
# Verify that Switch C can ping hosts on network 50::/64. (Details not shown.)
IPv6 BGP route reflector configuration example
Network requirements
As shown in Figure 83 , run EBGP between Switch A and Switch B, run IBGP between Switch C and
Switch B, and between Switch C and Switch D.
Configure Switch C as a route reflector with clients Switch B and Switch D.
Figure 83 Network diagram
Loop0
1.1.1.1/32
Vlan-int10
1::1/64
Switch A
Vlan-int100
100::1/96
AS 100
Vlan-int101
101::1/96
Vlan-int100
100::2/96
Loop0
2.2.2.2/32
Vlan-int101
101::2/96
Loop0
3.3.3.3/32
Switch C
Vlan-int102
102::1/96
Vlan-int102
102::2/96
AS 200
Loop0
4.4.4.4/32
Switch B Switch D
Configuration procedure
1. Configure IPv6 addresses for interfaces and IPv4 addresses for loopback interfaces. (Details not shown.)
2. Configure IBGP and EBGP connections and advertise network routes through IPv6 BGP:
364
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 100::2 as-number 200
[SwitchA-bgp-default] address-family ipv6
[SwitchA-bgp-default-ipv6] peer 100::2 enable
[SwitchA-bgp-default-ipv6] network 1:: 64
[SwitchA-bgp-default-ipv6] network 100:: 96
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 100::1 as-number 100
[SwitchB-bgp-default] peer 101::1 as-number 200
[SwitchB-bgp-default] address-family ipv6
[SwitchB-bgp-default-ipv6] peer 100::1 enable
[SwitchB-bgp-default-ipv6] peer 101::1 enable
[SwitchB-bgp-default-ipv6] peer 101::1 next-hop-local
[SwitchB-bgp-default-ipv6] network 100:: 96
[SwitchB-bgp-default-ipv6] network 101:: 96
[SwitchB-bgp-default-ipv6] quit
[SwitchB-bgp-default] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 101::2 as-number 200
[SwitchC-bgp-default] peer 102::2 as-number 200
[SwitchC-bgp-default] address-family ipv6
[SwitchC-bgp-default-ipv6] peer 101::2 enable
[SwitchC-bgp-default-ipv6] peer 102::2 enable
[SwitchC-bgp-default-ipv6] network 101:: 96
[SwitchC-bgp-default-ipv6] network 102:: 96
# Configure Switch D.
<SwitchD> system-view
[SwitchD] bgp 200
[SwitchD-bgp-default] router-id 4.4.4.4
[SwitchD-bgp-default] peer 102::1 as-number 200
[SwitchD-bgp-default] address-family ipv6
[SwitchD-bgp-default-ipv6] peer 102::1 enable
[SwitchD-bgp-default-ipv6] network 102:: 96
3. Configure Switch C as a route reflector, and configure Switch B and Switch D as its clients.
[SwitchC-bgp-default-ipv6] peer 101::2 reflect-client
[SwitchC-bgp-default-ipv6] peer 102::2 reflect-client
[SwitchC-bgp-default-ipv6] quit
365
[SwitchC-bgp-default] quit
Verifying the configuration
# Execute the display bgp routing-table ipv6 command on Switch D.
[SwitchD] display bgp routing-table ipv6
Total number of routes: 5
BGP local router ID is 4.4.4.4
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* >i Network : 1:: PrefixLen : 64
NextHop : 101::2 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: 100i
* >i Network : 100:: PrefixLen : 96
NextHop : 101::2 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
* >i Network : 101:: PrefixLen : 96
NextHop : 102::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
* > Network : 102:: PrefixLen : 96
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: i
* i Network : 102:: PrefixLen : 96
NextHop : 102::1 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
The output shows that Switch D has learned the network 1::/64 from Switch C through route reflection.
366
6PE configuration example
Network requirements
As shown in Figure 84 , use 6PE to connect two isolated IPv6 networks over an IPv4/MPLS network.
•
The ISP uses OSPF as the IGP.
•
PE 1 and PE 2 are edge devices of the ISP, and establish an IPv4 IBGP connection between them.
•
CE 1 and CE 2 are edge devices of the IPv6 networks, and they connect the IPv6 networks to the ISP.
•
A CE and a PE exchange IPv6 packets through IPv6 static routing.
Figure 84 Network diagram
Loop0
1::1/128
Vlan-int10
10::2/64
PE 1
Vlan-int10
10::1/64
CE 1
Loop0
2.2.2.2/32
Vlan-int30
1.1.1.1/16
AS 65100
Vlan-int30
1.1.1.2/16
Loop0
3.3.3.3/32
IBGP
IPv4/MPLS network
PE 2
Vlan-int20
20::2/64
Loop0
4::4/128
Vlan-int20
20::1/64
CE 2
IPv6 network IPv6 network
Configuration procedure
1. Configure IPv6 addresses and IPv4 addresses for interfaces. (Details not shown.)
2. Configure PE 1:
# Enable LDP globally, and configure the LSP generation policy.
<PE1> system-view
[PE1] mpls lsr-id 2.2.2.2
[PE1] mpls ldp
[PE1-ldp] lsp-trigger all
[PE1-ldp] quit
# Enable MPLS and LDP on VLAN-interface 30.
[PE1] interface vlan-interface 30
[PE1-Vlan-interface30] mpls enable
[PE1-Vlan-interface30] mpls ldp enable
[PE1-Vlan-interface30] quit
# Configure IBGP, enable the peer's 6PE capabilities, and redistribute IPv6 direct and static routes.
[PE1] bgp 65100
[PE1-bgp-default] router-id 2.2.2.2
[PE1-bgp-default] peer 3.3.3.3 as-number 65100
[PE1-bgp-default] peer 3.3.3.3 connect-interface loopback 0
[PE1-bgp-default] address-family ipv6
[PE1-bgp-default-ipv6] import-route direct
[PE1-bgp-default-ipv6] import-route static
367
[PE1-bgp-default-ipv6] peer 3.3.3.3 enable
[PE1-bgp-default-ipv6] peer 3.3.3.3 label-route-capability
[PE1-bgp-default-ipv6] quit
[PE1-bgp-default] quit
# Configure a static route to CE 1.
[PE1] ipv6 route-static 1::1 128 10::1
# Configure OSPF for the ISP.
[PE1] ospf
[PE1-ospf-1] area 0
[PE1-ospf-1-area-0.0.0.0] network 2.2.2.2 0.0.0.0
[PE1-ospf-1-area-0.0.0.0] network 1.1.0.0 0.0.255.255
[PE1-ospf-1-area-0.0.0.0] quit
[PE1-ospf-1] quit
3. Configure PE 2:
# Enable LDP globally, and configure the LSP generation policy.
<PE2> system-view
[PE2] mpls lsr-id 3.3.3.3
[PE2] mpls ldp
[PE2-mpls-ldp] lsp-trigger all
[PE2-mpls-ldp] quit
# Enable MPLS and LDP on VLAN-interface 30.
[PE2] interface vlan-interface 30
[PE2-Vlan-interface30] mpls enable
[PE2-Vlan-interface30] mpls ldp enable
[PE2-Vlan-interface30] quit
# Configure IBGP, enable the peer's 6PE capabilities, and redistribute IPv6 direct and static routes.
[PE2] bgp 65100
[PE2-bgp-default] router-id 3.3.3.3
[PE2-bgp-default] peer 2.2.2.2 as-number 65100
[PE2-bgp-default] peer 2.2.2.2 connect-interface loopback 0
[PE2-bgp-default] address-family ipv6
[PE2-bgp-default-ipv6] import-route direct
[PE2-bgp-default-ipv6] import-route static
[PE2-bgp-default-ipv6] peer 2.2.2.2 enable
[PE2-bgp-default-ipv6] peer 2.2.2.2 label-route-capability
[PE2-bgp-default-ipv6] quit
[PE2-bgp-default] quit
# Configure the static route to CE 2.
[PE2] ipv6 route-static 4::4 128 20::1
# Configure OSPF for the ISP.
[PE2] ospf
[PE2-ospf-1] area 0
[PE2-ospf-1-area-0.0.0.0] network 3.3.3.3 0.0.0.0
[PE2-ospf-1-area-0.0.0.0] network 1.1.0.0 0.0.255.255
[PE2-ospf-1-area-0.0.0.0] quit
[PE2-ospf-1] quit
4. Configure a static route on CE 1, with PE 1 as the default next hop.
368
<CE1> system-view
[CE1] ipv6 route-static :: 0 10::2
5. Configure a static route on CE 2, with PE 2 as the default next hop.
<CE2> system-view
[CE2] ipv6 route-static :: 0 20::2
Verifying the configuration
# Display the IPv6 BGP routing tables on PE 1 and PE 2. The output shows that each of them has two IPv6 network routes. The following shows the output on PE 1:
[PE1] display bgp routing-table ipv6
Total number of routes: 5
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
* > Network : 1::1 PrefixLen : 128
NextHop : 10::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 4::4 PrefixLen : 128
NextHop : ::FFFF:3.3.3.3 LocPrf : 100
PrefVal : 0 OutLabel : 1279
MED : 0
Path/Ogn: ?
* > Network : 10:: PrefixLen : 64
NextHop : :: LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* > Network : 10::2 PrefixLen : 128
NextHop : ::1 LocPrf :
PrefVal : 32768 OutLabel : NULL
MED : 0
Path/Ogn: ?
* >i Network : 20:: PrefixLen : 64
NextHop : ::FFFF:3.3.3.3 LocPrf : 100
PrefVal : 0 OutLabel : 1278
MED : 0
Path/Ogn: ?
# Verify that CE 1 can ping the IPv6 address 4::4 (loopback interface address) of CE 2. (Details not shown.)
369
BFD for IPv6 BGP configuration example
Network requirements
As shown in Figure 85 , configure OSPFv3 as the IGP in AS 200.
•
Establish two IBGP connections between Switch A and Switch C. When both paths operate correctly, Switch C uses the path Switch A<—>Switch B<—>Switch C to exchange packets with network 1200::0/64.
•
Configure BFD over the path. When the path fails, BFD can quickly detect the failure and notify it to IPv6 BGP. Then, the path Switch A<—>Switch D<—>Switch C takes effect immediately.
Figure 85 Network diagram
AS 100 1200::0/64
Switch B
Vlan-int100 Vlan-int101
Vlan-int100
Vlan-int101
Switch A
Vlan-int200
AS 200
Vlan-int201
Switch C
AS 300
Vlan-int200
Switch D
Vlan-int201
Table 21 Interface and IP address assignment
Device
Switch A
Switch B
Interface
Vlan-int100
Vlan-int200
Vlan-int100
IP address
3000::1/64
2000::1/64
3000::2/64
Device
Switch C
Switch D
Interface
Vlan-int101
Vlan-int201
Vlan-int200
IP address
3001::3/64
2001::3/64
2000::2/64
Vlan-int101 3001::2/64 Vlan-int201 2001::2/64
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure OSPFv3 so that Switch A and Switch C can reach each other. (Details not shown.)
3. Configure IPv6 BGP on Switch A:
# Establish two IBGP connections to Switch C.
<SwitchA> system-view
[SwitchA] bgp 200
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 3001::3 as-number 200
[SwitchA-bgp-default] peer 2001::3 as-number 200
[SwitchA-bgp-default] address-family ipv6
[SwitchA-bgp-default-ipv6] peer 3001::3 enable
370
[SwitchA-bgp-default-ipv6] peer 2001::3 enable
[SwitchA-bgp-default-ipv6] quit
# Create IPv6 basic ACL 2000 to permit 1200::0/64 to pass.
[SwitchA] acl ipv6 basic 2000
[SwitchA-acl-ipv6-basic-2000] rule permit source 1200:: 64
[SwitchA-acl-ipv6-basic-2000] quit
# Create two routing policies to set the MED for route 1200::0/64. The policy apply_med_50 sets the MED to 50, and the policy apply_med_100 sets the MED to 100.
[SwitchA] route-policy apply_med_50 permit node 10
[SwitchA-route-policy-apply_med_50-10] if-match ipv6 address acl 2000
[SwitchA-route-policy-apply_med_50-10] apply cost 50
[SwitchA-route-policy-apply_med_50-10] quit
[SwitchA] route-policy apply_med_100 permit node 10
[SwitchA-route-policy-apply_med_100-10] if-match ipv6 address acl 2000
[SwitchA-route-policy-apply_med_100-10] apply cost 100
[SwitchA-route-policy-apply_med_100-10] quit
# Apply routing policy apply_med_50 to routes outgoing to peer 3001::3, and apply routing policy apply_med_100 to routes outgoing to peer 2001::3.
[SwitchA] bgp 200
[SwitchA-bgp-default] address-family ipv6 unicast
[SwitchA-bgp-default-ipv6] peer 3001::3 route-policy apply_med_50 export
[SwitchA-bgp-default-ipv6] peer 2001::3 route-policy apply_med_100 export
[SwitchA-bgp-default-ipv6] quit
# Enable BFD for peer 3001::3.
[SwitchA-bgp-default] peer 3001::3 bfd
[SwitchA-bgp-default] quit
4. Configure IPv6 BGP on Switch C:
# Establish two IBGP connections to Switch A.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] peer 3000::1 as-number 200
[SwitchC-bgp-default] peer 2000::1 as-number 200
[SwitchC-bgp-default] address-family ipv6
[SwitchC-bgp-default-ipv6] peer 3000::1 enable
[SwitchC-bgp-default-ipv6] peer 2000::1 enable
[SwitchC-bgp-default-ipv6] quit
# Enable BFD for peer 3001::1.
[SwitchC-bgp-default] peer 3000::1 bfd
[SwitchC-bgp-default] quit
[SwitchC] quit
Verifying the configuration
# Display detailed BFD session information on Switch C.
<SwitchC> display bfd session verbose
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv6 Session Working Under Ctrl Mode:
371
Local Discr: 513 Remote Discr: 513
Source IP: 3001::3
Destination IP: 3000::1
Session State: Up Interface: N/A
Min Tx Inter: 500ms Act Tx Inter: 500ms
Min Rx Inter: 500ms Detect Inter: 2500ms
Rx Count: 13 Tx Count: 14
Connect Type: Indirect Running Up for: 00:00:05
Hold Time: 2243ms Auth mode: None
Detect Mode: Async Slot: 0
Protocol: BGP4+
Version:1
Diag Info: No Diagnostic
The output shows that a BFD session has been established between Switch A and Switch C.
# Display BGP peer information on Switch C.
<SwitchC> display bgp peer ipv6
BGP local router ID: 3.3.3.3
Local AS number: 200
Total number of peers: 2 Peers in established state: 2
* - Dynamically created peer
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2000::1 200 8 8 0 0 00:04:45 Established
3000::1 200 5 4 0 0 00:01:53 Established
The output shows that Switch C has established two BGP connections with Switch A, and both connections are in Established state.
# Display route 1200::0/64 on Switch C.
<SwitchC> display ipv6 routing-table 1200::0 64 verbose
Summary count : 1
Destination: 1200::/64
Protocol: BGP4+ Process ID: 0
SubProtID: 0x1 Age: 00h01m07s
Cost: 50 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x25000001 LastAs: 0
AttrID: 0x1 Neighbor: 3000::1
Flags: 0x10060 OrigNextHop: 3000::1
Label: NULL RealNextHop: FE80::20C:29FF:FE4A:3873
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface101
BkTunnel ID: Invalid BkInterface: N/A
372
The output shows that Switch C communicates with network 1200::0/64 through the path Switch
C<—>Switch B<—>Switch A.
# Break down the path Switch C<—>Switch B<—>Switch A and then display route 1200::0/64 on
Switch C.
<SwitchC> display ipv6 routing-table 1200::0 64 verbose
Summary count : 1
Destination: 1200::/64
Protocol: BGP4+ Process ID: 0
SubProtID: 0x1 Age: 00h00m57s
Cost: 100 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x1 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x25000000 LastAs: 0
AttrID: 0x0 Neighbor: 2000::1
Flags: 0x10060 OrigNextHop: 2000::1
Label: NULL RealNextHop: FE80::20C:29FF:FE40:715
BkLabel: NULL BkNextHop: N/A
Tunnel ID: Invalid Interface: Vlan-interface201
BkTunnel ID: Invalid BkInterface: N/A
The output shows that Switch C communicates with network 1200::0/64 through the path Switch
C<—>Switch D<—>Switch A.
IPsec for IPv6 BGP packets configuration example
Network requirements
As shown in Figure 86 , all switches run IPv6 BGP. Establish an IBGP connection between Switch A
and Switch B, and establish an EBGP connection between Switch B and Switch C.
To enhance security, configure IPsec to protect IPv6 BGP packets.
Figure 86 Network diagram
AS 65008
Switch A
Vlan-int100
1::1/64
Vlan-int100
1::2/64
Switch B
Vlan-int200
3::1/64
AS 65009
Vlan-int200
3::2/64
Switch C
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Establish an IBGP connection between Switch A and Switch B:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] group ibgp internal
373
[SwitchA-bgp-default] peer 1::2 group ibgp
[SwitchA-bgp-default] address-family ipv6 unicast
[SwitchA-bgp-default-ipv6] peer ibgp enable
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] bgp 65008
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] group ibgp internal
[SwitchB-bgp-default] peer 1::1 group ibgp
[SwitchB-bgp-default] address-family ipv6 unicast
[SwitchB-bgp-default-ipv6] peer ibgp enable
[SwitchB-bgp-default-ipv6] quit
3. Establish an EBGP connection between Switch B and Switch C:
# Configure Switch C.
<SwitchC> system-view
[SwitchC] bgp 65009
[SwitchC-bgp-default] router-id 3.3.3.3
[SwitchC-bgp-default] group ebgp external
[SwitchC-bgp-default] peer 3::1 as-number 65008
[SwitchC-bgp-default] peer 3::1 group ebgp
[SwitchC-bgp-default] address-family ipv6 unicast
[SwitchC-bgp-default-ipv6] peer ebgp enable
[SwitchC-bgp-default-ipv6] quit
[SwitchC-bgp-default] quit
# Configure Switch B.
[SwitchB-bgp-default] group ebgp external
[SwitchB-bgp-default] peer 3::2 as-number 65009
[SwitchB-bgp-default] peer 3::2 group ebgp
[SwitchB-bgp-default] address-family ipv6 unicast
[SwitchB-bgp-default-ipv6] peer ebgp enable
[SwitchB-bgp-default-ipv6] quit
[SwitchB-bgp-default] quit
4. Configure IPsec transform sets and IPsec profiles:
# On Switch A, create an IPsec transform set named tran1 .
[SwitchA] ipsec transform-set tran1
# Set the encapsulation mode to transport mode.
[SwitchA-ipsec-transform-set-tran1] encapsulation-mode transport
# Set the security protocol to ESP, the encryption algorithm to DES, and authentication algorithm to SHA1.
[SwitchA-ipsec-transform-set-tran1] esp encryption-algorithm des
[SwitchA-ipsec-transform-set-tran1] esp authentication-algorithm sha1
[SwitchA-ipsec-transform-set-tran1] quit
# Create an IPsec profile named policy001 , and specify the manual mode for it.
[SwitchA] ipsec profile policy001 manual
# Use IPsec transform set tran1 .
[SwitchA-ipsec-profile-policy001-manual] transform-set tran1
374
# Set the SPIs of the inbound and outbound SAs to 12345 .
[SwitchA-ipsec-profile-policy001-manual] sa spi outbound esp 12345
[SwitchA-ipsec-profile-policy001-manual] sa spi inbound esp 12345
# Set the keys for the inbound and outbound SAs using ESP to abcdefg .
[SwitchA-ipsec-profile-policy001-manual] sa string-key outbound esp simple abcdefg
[SwitchA-ipsec-profile-policy001-manual] sa string-key inbound esp simple abcdefg
[SwitchA-ipsec-profile-policy001-manual] quit
# On Switch B, create an IPsec transform set named tran1 .
[SwitchB] ipsec transform-set tran1
# Set the encapsulation mode to transport mode.
[SwitchB-ipsec-transform-set-tran1] encapsulation-mode transport
# Set the security protocol to ESP, the encryption algorithm to DES, and authentication algorithm to SHA1.
[SwitchB-ipsec-transform-set-tran1] esp encryption-algorithm des
[SwitchB-ipsec-transform-set-tran1] esp authentication-algorithm sha1
[SwitchB-ipsec-transform-set-tran1] quit
# Create IPsec profile named policy001 , and specify the manual mode for it.
[SwitchB] ipsec profile policy001 manual
# Use IPsec transform set tran1 .
[SwitchB-ipsec-profile-policy001-manual] transform-set tran1
# Set the SPIs of the inbound and outbound SAs to 12345 .
[SwitchB-ipsec-profile-policy001-manual] sa spi outbound esp 12345
[SwitchB-ipsec-profile-policy001-manual] sa spi inbound esp 12345
# Set the keys for the inbound and outbound SAs using ESP to abcdefg .
[SwitchB-ipsec-profile-policy001-manual] sa string-key outbound esp simple abcdefg
[SwitchB-ipsec-profile-policy001-manual] sa string-key inbound esp simple abcdefg
[SwitchB-ipsec-profile-policy001-manual] quit
# Create an IPsec transform set named tran2 .
[SwitchB] ipsec transform-set tran2
# Set the encapsulation mode to transport mode.
[SwitchB-ipsec-transform-set-tran2] encapsulation-mode transport
# Set the security protocol to ESP, the encryption algorithm to DES, and authentication algorithm to SHA1.
[SwitchB-ipsec-transform-set-tran2] esp encryption-algorithm des
[SwitchB-ipsec-transform-set-tran2] esp authentication-algorithm sha1
[SwitchB-ipsec-transform-set-tran2] quit
# Create IPsec profile named policy002 , and specify the manual mode for it.
[SwitchB] ipsec profile policy002 manual
# Use IPsec transform set tran2 .
[SwitchB-ipsec-profile-policy002-manual] transform-set tran2
# Set the SPIs of the inbound and outbound SAs to 54321 .
[SwitchB-ipsec-profile-policy002-manual] sa spi outbound esp 54321
[SwitchB-ipsec-profile-policy002-manual] sa spi inbound esp 54321
# Set the keys for the inbound and outbound SAs using ESP to gfedcba .
[SwitchB-ipsec-profile-policy002-manual] sa string-key outbound esp simple gfedcba
[SwitchB-ipsec-profile-policy002-manual] sa string-key inbound esp simple gfedcba
[SwitchB-ipsec-profile-policy002-manual] quit
375
# On Switch C, create an IPsec transform set named tran2 .
[SwitchC] ipsec transform-set tran2
# Set the encapsulation mode to transport mode.
[SwitchC-ipsec-transform-set-tran2] encapsulation-mode transport
# Set the security protocol to ESP, the encryption algorithm to DES, and authentication algorithm to SHA1.
[SwitchC-ipsec-transform-set-tran2] esp encryption-algorithm des
[SwitchC-ipsec-transform-set-tran2] esp authentication-algorithm sha1
[SwitchC-ipsec-transform-set-tran2] quit
# Create IPsec profile named policy002 , and specify the manual mode for it.
[SwitchC] ipsec profile policy002 manual
# Use IPsec transform set tran2 .
[SwitchC-ipsec-profile-policy002-manual] transform-set tran2
# Set the SPIs of the inbound and outbound SAs to 54321 .
[SwitchC-ipsec-profile-policy002-manual] sa spi outbound esp 54321
[SwitchC-ipsec-profile-policy002-manual] sa spi inbound esp 54321
# Set the keys for the inbound and outbound SAs using ESP to gfedcba .
[SwitchC-ipsec-profile-policy002-manual] sa string-key outbound esp simple gfedcba
[SwitchC-ipsec-profile-policy002-manual] sa string-key inbound esp simple gfedcba
[SwitchC-ipsec-profile-policy002-manual] quit
5. Configure IPsec to protect IPv6 BGP packets between Switch A and Switch B:
# Configure Switch A.
[SwitchA] bgp 65008
[SwitchA-bgp-default] peer 1::2 ipsec-profile policy001
[SwitchA-bgp-default] quit
# Configure Switch B.
[SwitchB] bgp 65008
[SwitchB-bgp-default] peer 1::1 ipsec-profile policy001
[SwitchB-bgp-default] quit
6. Configure IPsec to protect IPv6 BGP packets between Router B and Switch C:
# Configure Switch C.
[SwitchC] bgp 65009
[SwitchC-bgp-default] peer ebgp ipsec-profile policy002
[SwitchC-bgp-default] quit
# Configure Switch B.
[SwitchB] bgp 65008
[SwitchB-bgp-default] peer ebgp ipsec-profile policy002
[SwitchB-bgp-default] quit
Verifying the configuration
# Display detailed information about IPv6 BGP peers on Switch B.
[SwitchB] display bgp peer ipv6 verbose
Peer: 1::1 Local: 2.2.2.2
Type: IBGP link
BGP version 4, remote router ID 1.1.1.1
BGP current state: Established, Up for 00h05m54s
BGP current event: KATimerExpired
376
BGP last state: OpenConfirm
Port: Local - 24896 Remote - 179
Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time: 60 sec
Peer optional capabilities:
Peer support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support BGP route AS4 capability
Address family IPv6 Unicast: advertised and received
InQ updates: 0, OutQ updates: 0
NLRI statistics:
Rcvd: UnReach NLRI 0, Reach NLRI 0
Sent: UnReach NLRI 0, Reach NLRI 3
Message statistics:
Msg type Last rcvd time/ Current rcvd count/ History rcvd count/
Last sent time Current sent count History sent count
Open 18:59:15-2013.4.24 1 1
18:59:15-2013.4.24 1 2
Update - 0 0
18:59:16-2013.4.24 1 1
Notification - 0 0
18:59:15-2013.4.24 0 1
Keepalive 18:59:15-2013.4.24 1 1
18:59:15-2013.4.24 1 1
RouteRefresh - 0 0
- 0 0
Total - 2 2
- 3 5
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 15 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Peer preferred value: 0
IPsec profile name: policy001
Routing policy configured:
No routing policy is configured
Peer: 3::2 Local: 2.2.2.2
Type: EBGP link
BGP version 4, remote router ID 3.3.3.3
BGP current state: Established, Up for 00h05m00s
377
BGP current event: KATimerExpired
BGP last state: OpenConfirm
Port: Local - 24897 Remote - 179
Configured: Active Hold Time: 180 sec Keepalive Time: 60 sec
Received : Active Hold Time: 180 sec
Negotiated: Active Hold Time: 180 sec Keepalive Time: 60 sec
Peer optional capabilities:
Peer support BGP multi-protocol extended
Peer support BGP route refresh capability
Peer support BGP route AS4 capability
Address family IPv6 Unicast: advertised and received
Received: Total 8 messages, Update messages 1
Sent: Total 8 messages, Update messages 1
Maximum allowed prefix number: 4294967295
Threshold: 75%
Minimum time between advertisements is 30 seconds
Optional capabilities:
Multi-protocol extended capability has been enabled
Route refresh capability has been enabled
Peer preferred value: 0
IPsec profile name: policy002
Routing policy configured:
No routing policy is configured
IPv6 BGP FRR configuration example
Network requirements
As shown in Figure 87 , configure BGP FRR so that when Link B fails, BGP uses Link A to forward
traffic.
Figure 87 Network diagram
Loop0
2.2.2.2/32
Vlan-int100
3001::2/64
Vlan-int101
3002::1/64
AS 200
Switch A
Vlan-int100
3001::1/64
Switch B
Link B
Vlan-int101
3002::2/64
Switch D
Vlan-int201
2002::2/64
AS 100 Vlan-int200
2001::1/64
Vlan-int200
2001::2/64
Link A
Switch C
Vlan-int201
2002::1/64
Loop0
3.3.3.3/32
378
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure OSPFv3 in AS 200 to ensure connectivity among Switch B, Switch C, and Switch D.
(Details not shown.)
3. Configure BGP connections:
# Configure Switch A to establish EBGP sessions to Switch B and Switch C, and advertise network 1::/64.
<SwitchA> system-view
[SwitchA] bgp 100
[SwitchA] router-id 1.1.1.1
[SwitchA-bgp-default] peer 3001::2 as-number 200
[SwitchA-bgp-default] peer 2001::2 as-number 200
[SwitchA-bgp-default] address-family ipv6 unicast
[SwitchA-bgp-default-ipv6] peer 3001::2 enable
[SwitchA-bgp-default-ipv6] peer 2001::2 enable
[SwitchA-bgp-default-ipv6] network 1:: 64
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# Configure Switch B to establish an EBGP session to Switch A, and an IBGP session to Switch
D.
<SwitchB> system-view
[SwitchB] bgp 200
[SwitchB] router-id 2.2.2.2
[SwitchB-bgp-default] peer 3001::1 as-number 100
[SwitchB-bgp-default] peer 3002::2 as-number 200
[SwitchB-bgp-default] address-family ipv6 unicast
[SwitchB-bgp-default-ipv6] peer 3001::1 enable
[SwitchB-bgp-default-ipv6] peer 3002::2 enable
[SwitchB-bgp-default-ipv6] peer 3002::2 next-hop-local
[SwitchB-bgp-default-ipv6] quit
[SwitchB-bgp-default] quit
# Configure Switch C to establish an EBGP session to Switch A, and an IBGP session to Switch
D.
<SwitchC> system-view
[SwitchC] bgp 200
[SwitchC] router-id 3.3.3.3
[SwitchC-bgp-default] peer 2001::1 as-number 100
[SwitchC-bgp-default] peer 2002::2 as-number 200
[SwitchC-bgp-default] address-family ipv6 unicast
[SwitchC-bgp-default-ipv6] peer 2001::1 enable
[SwitchC-bgp-default-ipv6] peer 2002::2 enable
[SwitchC-bgp-default-ipv6] peer 2002::2 next-hop-local
[SwitchC-bgp-default-ipv6] quit
[SwitchC-bgp-default] quit
# Configure Switch D to establish IBGP sessions to Switch B and Switch C, and advertise network 4::/64.
<SwitchD> system-view
[SwitchD] bgp 200
379
[SwitchD-bgp-default] peer 3002::1 as-number 200
[SwitchD-bgp-default] peer 2002::1 as-number 200
[SwitchD-bgp-default] address-family ipv6 unicast
[SwitchD-bgp-default-ipv6] peer 3002::1 enable
[SwitchD-bgp-default-ipv6] peer 2002::1 enable
[SwitchD-bgp-default-ipv6] network 4:: 64
[SwitchD-bgp-default-ipv6] quit
[SwitchD-bgp-default] quit
4. Configure preferred values so Link B is used to forward traffic between Switch A and Switch D:
# Configure Switch A to set the preferred value to 100 for routes received from Switch B.
[SwitchA-bgp-default-ipv6] peer 3001::2 preferred-value 100
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# Configure Switch D to set the preferred value to 100 for routes received from Switch B.
[SwitchD-bgp-default-ipv6] peer 3002::1 preferred-value 100
[SwitchD-bgp-default-ipv6] quit
[SwitchD-bgp-default] quit
5. Configure BGP FRR:
# On Switch A, create routing policy frr to set a backup next hop 2001::2 (Switch C) for the route destined for 4::/64.
<SwitchA> system-view
[SwitchA] ipv6 prefix-list abc index 10 permit 4:: 64
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy] if-match ipv6 address prefix-list abc
[SwitchA-route-policy] apply ipv6 fast-reroute backup-nexthop 2001::2
[SwitchA-route-policy] quit
# Apply the routing policy to BGP FRR for BGP IPv6 unicast address family.
[SwitchA] bgp 100
[SwitchA-bgp-default] address-family ipv6 unicast
[SwitchA-bgp-default-ipv6] fast-reroute route-policy frr
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# On Switch D, create routing policy frr to set a backup next hop 2002::1 (Switch C) for the route destined for 1::/64.
<SwitchD> system-view
[SwitchD] ipv6 prefix-list abc index 10 permit 1:: 64
[SwitchD] route-policy frr permit node 10
[SwitchD-route-policy] if-match ipv6 address prefix-list abc
[SwitchD-route-policy] apply ipv6 fast-reroute backup-nexthop 2002::1
[SwitchD-route-policy] quit
# Apply the routing policy to BGP FRR for BGP IPv6 unicast address family.
[SwitchD] bgp 200
[SwitchD-bgp-default] address-family ipv6 unicast
[SwitchD-bgp-default-ipv6] fast-reroute route-policy frr
[SwitchD-bgp-default-ipv6] quit
[SwitchD-bgp-default] quit
380
Verifying the configuration
# Display detailed information about the route to 4::/64 on Switch A. The output shows the backup next hop for the route.
[SwitchA] display ipv6 routing-table 4:: 64 verbose
Summary count : 1
Destination: 4::/64
Protocol: BGP4+ Process ID: 0
SubProtID: 0x2 Age: 00h00m58s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 200
NibID: 0x25000003 LastAs: 200
AttrID: 0x3 Neighbor: 3001::2
Flags: 0x10060 OrigNextHop: 3001::2
Label: NULL RealNextHop: 3001::2
BkLabel: NULL BkNextHop: 2001::2
Tunnel ID: Invalid Interface: Vlan-interface 100
BkTunnel ID: Invalid BkInterface: Vlan-interface 200
FtnIndex: 0x0
# Display detailed information about the route to 1::/64 on Switch D. The output shows the backup next hop for the route.
[SwitchD] display ipv6 routing-table 1:: 64 verbose
Summary count : 1
Destination: 1::/64
Protocol: BGP4+ Process ID: 0
SubProtID: 0x1 Age: 00h03m24s
Cost: 0 Preference: 255
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 100
NibID: 0x25000003 LastAs: 100
AttrID: 0x4 Neighbor: 3002::1
Flags: 0x10060 OrigNextHop: 3002::1
Label: NULL RealNextHop: 3002::1
BkLabel: NULL BkNextHop: 2002::1
Tunnel ID: Invalid Interface: Vlan-interface 101
BkTunnel ID: Invalid BkInterface: Vlan-interface 201
FtnIndex: 0x0
381
IPv6 multicast BGP configuration example
Network requirements
As shown in Figure 88 , OSPFv3 runs within AS 100 and AS 200 to ensure intra-AS connectivity. IPv6
MBGP runs between the two ASs to exchange IPv6 unicast routes used for RPF check.
Enable Anycast RP on Switch A and Switch B.
Figure 88 Network diagram
AS 100
Loop0 Loop1
Vlan-int101
Switch A Vlan-int100
Source
IPv6 PIM-SM 1
AS 200
Loop0 Loop1
Vlan-int101
Vlan
-int
103
Vlan
-int
103
Vlan-int104
Switch D
Vlan
Switch B
Receiver
-int
102
Vlan
-int
102
Vlan-int104
Switch C
Vlan
-int
200
IPv6 MBGP peers
Table 22 Interface and IP address assignment
IPv6 PIM-SM 2
Device Interface IP address
Source - 1002::100/64
Switch A Vlan-int100 1002::1/64
Vlan-int101 1001::1/64
Loop0
Loop1
1:1::1/128
1:1::2/128
Switch C Vlan-int200 3002::1/64
Vlan-int102 2001::2/64
Device
Switch B
Switch D
Interface
Vlan-int101
Vlan-int102
Vlan-int103
Loop0
Loop1
Vlan-int103
Vlan-int104
IP address
1001::2/64
2001::1/64
2002::1/64
1:1::1/128
2:2::2/128
2002::2/64
3001::2/64
Vlan-int104 3001::1/64
Configuration procedure
1. Configure IPv6 addresses for interfaces and configure OSPFv3 (this example uses OSPFv3 process 1) in AS 200 to ensure intra-AS connectivity. (Details not shown.)
2. Enable IPv6 multicast routing, IPv6 PIM-SM, and MLD, and configure BSR boundaries:
# On Switch A, enable IPv6 multicast routing globally, and enable IPv6 PIM-SM on interfaces.
<SwitchA> system-view
[SwitchA] ipv6 multicast routing
[SwitchA-mrib6] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ipv6 pim sm
[SwitchA-Vlan-interface100] quit
382
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] ipv6 pim sm
[SwitchA-Vlan-interface101] quit
[SwitchA] interface loopback 0
[SwitchA-LoopBack0] ipv6 pim sm
[SwitchA-LoopBack0] quit
# Configure Switch B and Switch D in the same way that Switch A was configured.
# On Switch C, enable IPv6 multicast routing globally.
<SwitchC> system-view
[SwitchC] ipv6 multicast routing
[SwitchC-mrib6] quit
# Enable IPv6 PIM-SM on interfaces, and enable MLD on VLAN-interface 200.
[SwitchC] interface vlan-interface 102
[SwitchC-Vlan-interface102] ipv6 pim sm
[SwitchC-Vlan-interface102] quit
[SwitchC] interface vlan-interface 104
[SwitchC-Vlan-interface104] ipv6 pim sm
[SwitchC-Vlan-interface104] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] ipv6 pim sm
[SwitchC-Vlan-interface200] mld enable
[SwitchC-Vlan-interface200] quit
# Configure the BSR boundary on Switch A.
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] ipv6 pim bsr-boundary
[SwitchA-Vlan-interface101] quit
# Configure the BSR boundary on Switch B.
[SwitchB] interface vlan-interface 101
[SwitchB-Vlan-interface101] ipv6 pim bsr-boundary
[SwitchB-Vlan-interface101] quit
3. Enable Anycast RP, and specify C-BSR and C-RP:
# Configure Switch A.
[SwitchA] ipv6 pim
[SwitchA-pim6] anycast-rp 1:1::1 1:1::2
[SwitchA-pim6] anycast-rp 1:1::1 2:2::2
[SwitchA-pim6] c-bsr 1:1::1
[SwitchA-pim6] c-rp 1:1::1
[SwitchA-pim6] quit
# Configure Switch B.
[SwitchB] ipv6 pim
[SwitchB-pim6] anycast-rp 1:1::1 1:1::2
[SwitchB-pim6] anycast-rp 1:1::1 2:2::2
[SwitchB-pim6] c-bsr 1:1::1
[SwitchB-pim6] c-rp 1:1::1
[SwitchB-pim6] quit
4. Configure BGP to establish BGP IPv6 multicast peers and redistribute routes:
# On Switch A, establish an EBGP session to Switch B.
383
[SwitchA] bgp 100
[SwitchA-bgp-default] router-id 1.1.1.1
[SwitchA-bgp-default] peer 1001::2 as-number 200
# Enable exchange of IPv6 unicast routes used for RPF check with Switch B.
[SwitchA-bgp-default] address-family ipv6 multicast
[SwitchA-bgp-default-mul-ipv6] peer 1001::2 enable
# Redistribute direct routes into BGP.
[SwitchA-bgp-default-mul-ipv6] import-route direct
[SwitchA-bgp-default-mul-ipv6] quit
# On Switch B, establish an EBGP session to Switch A.
[SwitchB] bgp 200
[SwitchB-bgp-default] router-id 2.2.2.2
[SwitchB-bgp-default] peer 1001::1 as-number 100
# Enable exchange of IPv6 unicast routes used for RPF check with Switch B.
[SwitchB-bgp-default] address-family ipv6 multicast
[SwitchB-bgp-default-mul-ipv6] peer 1001::1 enable
# Redistribute OSPFv3 routes into BGP.
[SwitchB-bgp-default-mul-ipv6] import-route ospfv3 1
[SwitchB-bgp-default-mul-ipv6] quit
5. Establish BGP IPv6 unicast peer relationships between Switch A and Switch B and redistribute routes:
# On Switch A, enable BGP to exchange IPv6 unicast routes with Switch B, and redistribute direct routes into BGP.
[SwitchA-bgp-default] address-family ipv6 unicast
[SwitchA-bgp-default-ipv6] peer 1001::2 enable
[SwitchA-bgp-default-ipv6] import-route direct
[SwitchA-bgp-default-ipv6] quit
[SwitchA-bgp-default] quit
# On Switch B, enable BGP to exchange IPv6 unicast routes with Switch A, and redistribute direct routes into BGP.
[SwitchB-bgp-default] address-family ipv6 unicast
[SwitchB-bgp-default-ipv6] peer 1001::1 enable
[SwitchB-bgp-default-ipv6] import-route direct
[SwitchB-bgp-default-ipv6] quit
[SwitchB-bgp-default] quit
Verifying the configuration
# Verify the BGP IPv6 multicast peer information on Switch B.
[SwitchB] display bgp peer ipv6 multicast
BGP local router ID : 2.2.2.2
Local AS number : 200
Total number of peers : 3 Peers in established state : 3
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
1001::1 100 56 56 0 0 00:40:54 Established
# Verify the RPF information for the multicast source on Switch B.
384
[SwitchB] display ipv6 multicast rpf-info 1002::1
RPF information about source 1002::1:
RPF interface: Vlan-interface101, RPF neighbor: 1001::1
Referenced prefix/prefix length: 1002::/64
Referenced route type: mbgp
Route selection rule: preference-preferred
Load splitting rule: disable
Troubleshooting BGP
Symptom
The display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command output shows that the state of the connection to a peer cannot become established.
Analysis
To become BGP peers, any two routers must establish a TCP connection using port 179 and exchange Open messages successfully.
Solution
1. To resolve the problem: a. Use the display current-configuration command to verify the current configuration, and verify that the peer's AS number is correct. b. Use the display bgp peer ipv4 unicast or display bgp peer ipv6 unicast command to verify that the peer's IP/IPv6 address is correct. c. If a loopback interface is used, verify that the loopback interface is specified with the peer connect-interface command. d. If the peer is a non-direct EBGP peer, verify that the peer ebgp-max-hop command is configured. e. If the peer ttl-security hops command is configured, verify that the command is configured on the peer. Verify that the hop-count values configured on them are greater than the number of hops between them. f. Verify that a valid route to the peer is available. g. Use the ping command to verify the connectivity to the peer. h. Use the display tcp verbose or display ipv6 tcp verbose command to verify the TCP connection. i. Verify that no ACL rule is applied to disable TCP port 179.
2. If the problem persists, contact Hewlett Packard Enterprise Support.
385
Configuring PBR
Overview
Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop and default next hop for packets that match specific criteria such as ACLs.
A device forwards received packets using the following process:
1. The device uses PBR to forward matching packets.
2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets.
3. If the routing table-based forwarding fails, the device uses the default next hop defined in PBR to forward packets.
4. If the default next hop-based forwarding fails, the device uses the default route to forward packets.
PBR includes local PBR and interface PBR.
•
Local PBR guides the forwarding of locally generated packets, such as the ICMP packets generated by using the ping command.
•
Interface PBR guides the forwarding of packets received on an interface only.
Policy
A policy includes match criteria and actions to be taken on the matching packets. A policy can have one or multiple nodes as follows:
•
Each node is identified by a node number. A smaller node number has a higher priority.
•
A node contains if-match and apply clauses. An if-match clause specifies a match criterion, and an apply clause specifies an action.
•
A node has a match mode of permit or deny .
A policy compares packets with nodes in priority order. If a packet matches the criteria on a node, it is processed by the action on the node. Otherwise, it goes to the next node for a match. If the packet does not match the criteria on any node, it is forwarded according to the routing table. if-match clause
PBR supports the following types of if-match clauses:
• if-match acl —Sets an ACL match criterion.
• if-match service-chain —Sets a service chain match criterion. For more information about service chain, see Service Chain Configuration Guide .
On a node, you can specify multiple types of if-match clauses, but only one if-match clause for each type.
To match a node, a packet must match all types of the if-match clauses for the node but only one if-match clause for each type. apply clause
PBR supports the types of apply
clauses shown in Table 23 . You can specify multiple
apply clauses for a node, but some of them might not be executed. The following apply clauses determine the packet forwarding paths in a descending order:
• apply next-hop
• apply output-interface
386
• apply default-next-hop
Table 23 Priorities and meanings of apply clauses
Clause apply precedence apply next-hop and apply output-interface apply service-chain
Meaning Priority
Sets an IP precedence. This clause is always executed.
Sets next hops and sets output interfaces.
Sets the service chain information.
Only the apply next-hop clause is executed when both are configured.
For this clause to take effect, make sure you have specified a reachable next hop in the apply next-hop clause. apply default-next-hop
Sets the default next hop.
This clause takes effect only when no next hop is set or the next hop is invalid, and the packet does not match any route in the routing table.
Relationship between the match mode and clauses on the node
Does a packet match all the if-match clauses on the node?
Yes.
Match mode
Permit
•
If the node is configured with apply clauses, PBR executes the apply clauses on the node.
If the PBR-based forwarding succeeds, PBR does not compare the packet with the next node.
If the PBR-based forwarding fails, PBR does not compare the packet with the next node.
•
If the node is configured with no apply clauses, the packet is forwarded according to the routing table.
Deny
The packet is forwarded according to the routing table.
No.
PBR compares the packet with the next node.
PBR compares the packet with the next node.
A node that has no if-match clauses matches any packet.
PBR and Track
PBR can work with the Track feature to dynamically adapt the availability status of an apply clause to the link status of a tracked next hop or default next hop.
•
When the track entry associated with an object changes to Negative , the apply clause is invalid.
•
When the track entry changes to Positive or NotReady , the apply clause is valid.
For more information about Track-PBR collaboration, see High Availability Configuration Guide .
387
PBR configuration task list
Tasks at a glance
(Required.) Configuring a policy :
•
•
Setting match criteria for a node
•
Configuring actions for a node
•
•
Configuring a policy
Creating a node
Step
1. Enter system view.
2. Create a node for a policy, and enter policy node view.
Command system-view policy-based-route policy-name
[ deny | permit ] node node-number
Setting match criteria for a node
Remarks
N/A
By default, no policy node is created.
Step
1. Enter system view.
2. Enter policy node view.
3. Set an ACL match criterion.
Command system-view policy-based-route policy-name [ deny | permit ] node node-number
Remarks
N/A
N/A
4. Set a service chain match criterion. if-match acl { acl-number | name acl-name } if-match service-chain { path-id service-path-id
[ path-index service-patch-index ] }
By default, no ACL match criterion is set.
By default, no service chain match criterion is set.
A policy that contains this clause is not supported on Layer 3
Ethernet subinterfaces.
NOTE:
If an ACL match criterion is defined, packets are compared with the ACL rules, and the permit or deny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no packet is matched.
388
Configuring actions for a node
Step
1. Enter system view.
2. Enter policy node view.
3. Set an IP precedence.
5.
6.
Set output interfaces.
Set default next hops.
Command system-view policy-based-route policy-name [ deny | permit ] node node-number apply precedence { type | value }
4. Set next hops. apply next-hop [ vpn-instance
vpn-instance-name ] { ip-address [ direct ]
[ track track-entry-number ] }&<1-2> apply output-interface interface-number [ track track-entry-number ] }
{ interface-type apply default-next-hop [ vpn-instance vpn-instance-name ] { ip-address [ direct ]
[ track track-entry-number ] }&<1-2>
Remarks
N/A
N/A
By default, no IP precedence is specified.
By default, no next hop is specified.
You can specify two next hops for backup in one command line or by executing this command twice.
You can specify a maximum of two next hops for a node.
By default, no output interface is specified.
By default, no default next hop is specified.
You can specify two default next hops for backup in one command line or by executing this command twice.
You can specify a maximum of two default next hops for a node.
The vpn-instance vpn-instance-name option does not take effect.
This command is not supported on the following modules:
•
EA interface modules.
•
EB interface modules.
•
SE interface modules:
LSU1GP24TXSE0 (JC617A,
JG376A).
LSU1GT48SE0 (JC618A,
JG377A).
LSU1GP48SE0 (JC619A,
JG378A).
LSU1TGX4SE0 (JC620A,
JG379A).
LSU1TGS8SE0 (JC631A,
JG389A).
LSU1GP24TSE0 (JC763A,
JG347A).
•
SC interface module:
LSU1TGS16SC0 (JC628A).
389
Step
7. Set the service chain information.
Command
apply service-chain path-id service-path-id
[ path-index service-patch-index ]
Remarks
By default, no service chain information is set.
A policy that contains this clause is not supported on Layer 3 Ethernet subinterfaces.
This clause does not apply to software forwarded packets.
Configuring PBR
Configuring local PBR
Configure PBR by applying a policy locally. PBR uses the policy to guide the forwarding of locally generated packets. The specified policy must already exist. Otherwise, the local PBR configuration fails.
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
Local PBR might affect local services, such as ping and Telnet. Do not configure local PBR unless doing so is required.
To configure local PBR:
Step
1. Enter system view.
2. Apply a policy locally.
Command system-view ip local policy-based-route policy-name
Remarks
N/A
By default, no policy is locally applied.
Configuring interface PBR
Configure PBR by applying a policy to an interface. PBR uses the policy to guide the forwarding of packets received on the interface. The specified policy must already exist. Otherwise, the interface
PBR configuration fails.
You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.
You can apply a policy to multiple interfaces.
To configure interface PBR:
Step
1. Enter system view.
2. Enter interface view.
Command system-view
3. Apply a policy to the interface. ip policy-based-route policy-name
Remarks
N/A interface interface-type interface-number N/A
By default, no policy is applied to the interface.
390
Displaying and maintaining PBR
Execute display commands in any view and reset commands in user view.
Task
Display PBR policy information.
Display PBR configuration.
(In standalone mode.) Display local PBR configuration and statistics.
(In IRF mode.) Display local PBR configuration and statistics.
(In standalone mode.) Display interface PBR configuration and statistics.
(In IRF mode.) Display interface PBR configuration and statistics.
Clear PBR statistics.
Command display ip policy-based-route [ policy policy-name ] display ip policy-based-route setup display ip policy-based-route local [ slot slot-number ] display ip policy-based-route local [ chassis chassis-number slot slot-number ] display ip policy-based-route interface interface-type interface-number [ slot slot-number ] display ip policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ] reset ip policy-based-route statistics [ policy policy-name ]
PBR configuration examples
Packet type-based local PBR configuration example
Network requirements
Switch A forwards other packets according to the routing table.
Figure 89 Network diagram
Switch A
Vlan-int10
1.1.2.1/24
Vlan-int10
1.1.2.2/24
Switch B
Vlan-int20
1.1.3.1/24
Vlan-int20
1.1.3.2/24
Switch C
Configuration procedure
1. Configure Switch A:
# Create VLAN 10 and VLAN 20.
<SwitchA> system-view
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchA] vlan 20
[SwitchA-vlan20] quit
# Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20.
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ip address 1.1.2.1 24
391
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 20
[SwitchA-Vlan-interface20] ip address 1.1.3.1 24
[SwitchA-Vlan-interface20] quit
# Configure ACL 3101 to match TCP packets.
[SwitchA] acl advanced 3101
[SwitchA-acl-adv-3101] rule permit tcp
[SwitchA-acl-adv-3101] quit
# Configure Node 5 for policy aaa to forward TCP packets to next hop 1.1.2.2.
[SwitchA] policy-based-route aaa permit node 5
[SwitchA-pbr-aaa-5] if-match acl 3101
[SwitchA-pbr-aaa-5] apply next-hop 1.1.2.2
[SwitchA-pbr-aaa-5] quit
# Configure local PBR by applying policy aaa to Switch A.
[SwitchA] ip local policy-based-route aaa
2. Configure Switch B:
# Create VLAN 10.
<SwitchB> system-view
[SwitchB] vlan 10
[SwitchB-vlan10] quit
# Configure the IP address of VLAN-interface 10.
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ip address 1.1.2.2 24
3. Configure Switch C:
# Create VLAN 20.
<SwitchC> system-view
[SwitchC] vlan 20
[SwitchC-vlan20] quit
# Configure the IP address of VLAN-interface 20.
[SwitchC] interface vlan-interface 20
[SwitchC-Vlan-interface20] ip address 1.1.3.2 24
Verifying the configuration
# Telnet to Switch B on Switch A. The operation succeeds.
# Telnet to Switch C on Switch A. The operation fails.
# Ping Switch C from Switch A. The operation succeeds.
Telnet uses TCP, and ping uses ICMP. The results show the following:
•
All TCP packets sent from Switch A are forwarded to the next hop 1.1.2.2.
•
Other packets are forwarded through VLAN-interface 20.
•
The local PBR configuration is effective.
Packet type-based interface PBR configuration example
Network requirements
As shown in Figure 90 , configure PBR on Switch A to forward all TCP packets received on
VLAN-interface 11 to the next hop 1.1.2.2. Switch A forwards other packets according to the routing table.
392
Figure 90 Network diagram
Switch B Switch C
Vlan-int10
1.1.2.2/24
Vlan-int20
1.1.3.2/24
Vlan-int10
1.1.2.1/24
Vlan-int20
1.1.3.1/24
Switch A
Vlan-int11
10.110.0.10/24
Subnet
10.110.0.0/24
Host A
10.110.0.20/24
Gateway: 10.110.0.10
Host B
Configuration procedure
1. Configure Switch A:
# Create VLAN 10 and VLAN 20.
<SwitchA> system-view
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchA] vlan 20
[SwitchA-vlan20] quit
# Configure the IP addresses of VLAN-interface 10 and VLAN-interface 20.
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ip address 1.1.2.1 24
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 20
[SwitchA-Vlan-interface20] ip address 1.1.3.1 24
[SwitchA-Vlan-interface20] quit
# Configure ACL 3101 to match TCP packets.
[SwitchA] acl advanced 3101
[SwitchA-acl-adv-3101] rule permit tcp
[SwitchA-acl-adv-3101] quit
# Configure Node 5 for policy aaa to forward TCP packets to next hop 1.1.2.2.
[SwitchA] policy-based-route aaa permit node 5
[SwitchA-pbr-aaa-5] if-match acl 3101
[SwitchA-pbr-aaa-5] apply next-hop 1.1.2.2
[SwitchA-pbr-aaa-5] quit
# Configure interface PBR by applying policy aaa to VLAN-interface 11.
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] ip address 10.110.0.10 24
393
[SwitchA-Vlan-interface11] ip policy-based-route aaa
[SwitchA-Vlan-interface11] quit
2. Configure Switch B:
# Create VLAN 10.
<SwitchB> system-view
[SwitchB] vlan 10
[SwitchB-vlan10] quit
# Configure the IP address of VLAN-interface 10.
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ip address 1.1.2.2 24
[SwitchB-Vlan-interface10] quit
# Configure a static route to subnet 10.110.0.0/24.
[SwitchB] ip route-static 10.110.0.0 24 1.1.2.1
3. Configure Switch C:
# Create VLAN 20.
<SwitchC> system-view
[SwitchC] vlan 20
[SwitchC-vlan20] quit
# Configure the IP address of VLAN-interface 20.
[SwitchC] interface vlan-interface 20
[SwitchC-Vlan-interface20] ip address 1.1.3.2 24
[SwitchC-Vlan-interface20] quit
# Configure a static route to subnet 10.110.0.0/24.
[SwitchC] ip route-static 10.110.0.0 24 1.1.3.1
Verifying the configuration
# Configure the IP address 10.110.0.20/24 for Host A, and specify its gateway address as
10.110.0.10.
# On Host A, Telnet to Switch B that is directly connected to Switch A. The operation succeeds.
# On Host A, Telnet to Switch C that is directly connected to Switch A. The operation fails.
# Ping Switch C from Host A. The operation succeeds.
Telnet uses TCP, and ping uses ICMP. The results show the following:
•
All TCP packets arriving on VLAN-interface 11 of Switch A are forwarded to next hop 1.1.2.2.
•
Other packets are forwarded through VLAN-interface 20.
•
The interface PBR configuration is effective.
EVPN-based service chain PBR configuration example
Network requirements
As shown in
Figure 91 , Switch A, Switch B, and Switch C are distributed EVPN gateway devices.
Switch D acts as a route reflector to reflect BGP routes for the other switches.
Configure PBR to direct packets sent by Server 1 to Service node 1. After being processed, the packets are forwarded to Server 2.
394
Figure 91 Network diagram
Loop0
4.4.4.4/32
IP transport network
Switch D
Vlan-int11
11.1.1.4/24
Vlan-int12
12.1.1.4/24
Vlan-int13
13.1.1.4/24
Loop0
1.1.1.1/32
Switch A
GE1/0/1
Vlan-int11
11.1.1.1/24
Vlan-int12
12.1.1.2/24
VSI-int1
10.1.1.1/24
Switch B
GE1/0/1
Loop0
2.2.2.2/32
Switch C
Vlan-int13
13.1.1.3/24
Loop0
3.3.3.3/32
VSI-int1
10.1.1.1/24
VSI-int1
10.1.1.1/24
V
M
1
10.1.1.10
Server 1
V
M
2
10.1.1.20
Server 2
Service node 1
10.1.1.11/24
Configuration procedure
1.
Configure IP addresses and subnet masks for interfaces, as shown in Figure 91 . (Details not
shown.)
2. Configure Switch A:
# Enable L2VPN.
<SwitchA> system-view
[SwitchA] l2vpn enable
# Disable remote-MAC address learning and remote ARP learning.
[SwitchA] vxlan tunnel mac-learning disable
[SwitchA] vxlan tunnel arp-learning disable
# Create an EVPN instance in VSI instance view, and configure the system to automatically generate an RT and RD.
[SwitchA] vsi vpna
[SwitchA-vsi-vpna] evpn encapsulation vxlan
[SwitchA-vsi-vpna-evpn-vxlan] route-distinguisher auto
[SwitchA-vsi-vpna-evpn-vxlan] vpn-target auto
[SwitchA-vsi-vpna-evpn-vxlan] quit
# Create VXLAN 10.
[SwitchA-vsi-vpna] vxlan 10
[SwitchA-vsi-vpna-vxlan-10] quit
[SwitchA-vsi-vpna] quit
# Configure BGP to advertise EVPN routes.
[SwitchA] bgp 200
[SwitchA-bgp-default] peer 4.4.4.4 as-number 200
395
[SwitchA-bgp-default] peer 4.4.4.4 connect-interface loopback 0
[SwitchA-bgp-default] address-family l2vpn evpn
[SwitchA-bgp-default-evpn] peer 4.4.4.4 enable
[SwitchA-bgp-default-evpn] quit
[SwitchA-bgp-default] quit
# Create VPN instance vpna .
[SwitchA] ip vpn-instance vpna
[SwitchA-vpn-instance-vpna] route-distinguisher 1:1
[SwitchA-vpn-instance-vpna] address-family ipv4
[SwitchA-vpn-ipv4-vpna] vpn-target 2:2
[SwitchA-vpn-ipv4-vpna] quit
[SwitchA-vpn-instance-vpna] address-family evpn
[SwitchA-vpn-evpn-vpna] vpn-target 1:1
# Configure VSI-interface 1.
[SwitchA] interface vsi-interface 1
[SwitchA-Vsi-interface1] ip binding vpn-instance vpna
[SwitchA-Vsi-interface1] ip address 10.1.1.1 255.255.255.0
[SwitchA-Vsi-interface1] mac-address 0001-0001-0001
[SwitchA-Vsi-interface1] local-proxy-arp enable
[SwitchA-Vsi-interface1] distributed-gateway local
[SwitchA-Vsi-interface1] quit
# Configure VSI-interface 3, associate the interface with VPN instance vpna , and set the L3
VXLAN ID to 1000.
[SwitchA] interface vsi-interface 3
[SwitchA-Vsi-interface3] ip binding vpn-instance vpna
[SwitchA-Vsi-interface3] l3-vni 1000
[SwitchA-Vsi-interface3] quit
# Associate VSI instance vpna with VSI-interface 1.
[SwitchA] vsi vpna
[SwitchA-vsi-vpna] gateway vsi-interface 1
[SwitchA-vsi-vpna] quit
# Configure VLAN-interface 11.
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] ip address 11.1.1.1 255.255.255.0
[SwitchA-Vlan-interface11] ospf 1 area 0.0.0.0
[SwitchA-Vlan-interface11] quit
# Associate Ethernet service instance 1000 with VSI instance vpna .
[SwitchA] interface gigabitethernet 1/0/1
[SwitchA-GigabitEthernet1/0/1] port link-mode bridge
[SwitchA-GigabitEthernet1/0/1] service-instance 1000
[SwitchA-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 2
[SwitchA-GigabitEthernet1/0/1-srv1000] xconnect vsi vpna
# Create ACL 3000 to permit packets with source IP address 10.1.1.10 and destination IP address 10.1.1.20.
<SwitchA> system-view
[SwitchA] acl advanced 3000
[SwitchA-acl-ipv4-adv-3000] rule 0 permit ip source 10.1.1.10 0 destination 10.1.1.20 0
396
# Create node 0, use ACL 3000 to match packets with source IP address 10.1.1.1 and destination IP address 10.1.1.20. Apply next hop 10.1.1.11 and service chain path ID 1 to matching packets.
[SwitchA] policy-based-route aa permit node 0
[SwitchA-pbr-aa-0] if-match acl 3000
[SwitchA-pbr-aa-0] apply service-chain path-id 1
[SwitchA-pbr-aa-0] apply next-hop vpn-instance vpna 10.1.1.11
# Apply policy aa to VSI-interface 3.
[SwitchA] interface vsi-interface 1
[SwitchA-Vsi-interface1] ip policy-based-route aa
[SwitchA-Vsi-interface1] quit
3. Configure Switch B:
# Enable L2VPN.
<SwitchB> system-view
[SwitchB] l2vpn enable
# Disable remote-MAC address learning and remote ARP learning.
[SwitchB] vxlan tunnel mac-learning disable
[SwitchB] vxlan tunnel arp-learning disable
# Create an EVPN instance in VSI instance view, and configure the system to automatically generate an RT and RD.
[SwitchB] vsi vpna
[SwitchB-vsi-vpna] evpn encapsulation vxlan
[SwitchB-vsi-vpna-evpn-vxlan] route-distinguisher auto
[SwitchB-vsi-vpna-evpn-vxlan] vpn-target auto
[SwitchB-vsi-vpna-evpn-vxlan] quit
# Configure VXLAN 10.
[SwitchB-vsi-vpna] vxlan 10
[SwitchB-vsi-vpna-vxlan-10] quit
[SwitchB-vsi-vpna] quit
# Configure BGP to advertise EVPN routes.
[SwitchB] bgp 200
[SwitchB-bgp-default] peer 4.4.4.4 as-number 200
[SwitchB-bgp-default] peer 4.4.4.4 connect-interface loopback0
[SwitchB-bgp-default] address-family l2vpn evpn
[SwitchB-bgp-default-evpn] peer 4.4.4.4 enable
# Create VPN instance vpna .
[SwitchB] ip vpn-instance vpna
[SwitchB-vpn-instance-vpna] route-distinguisher 1:1
[SwitchB-vpn-instance-vpna] address-family ipv4
[SwitchB-vpn-ipv4-vpna] vpn-target 2:2
[SwitchB-vpn-ipv4-vpna] quit
[SwitchB-vpn-instance-vpna] address-family evpn
[SwitchB-vpn-evpn-vpna] vpn-target 1:1
[SwitchB-vpn-evpn-vpna] quit
# Configure VSI-interface 1.
[SwitchB] interface vsi-interface 1
[SwitchB-Vsi-interface1] ip binding vpn-instance vpna
[SwitchB-Vsi-interface1] ip address 10.1.1.1 255.255.255.0
397
[SwitchB-Vsi-interface1] mac-address 0001-0001-0001
[SwitchB-Vsi-interface1] local-proxy-arp enable
[SwitchB-Vsi-interface1] distributed-gateway local
[SwitchB-Vsi-interface1] quit
# Associate VSI instance vpna with VSI-interface 1.
[SwitchB] vsi vpna
[SwitchB-vsi-vpna] gateway vsi-interface 1
[SwitchB-vsi-vpna] quit
# Configure VSI-interface 3.
[SwitchB] interface vsi-interface 3
[SwitchB-Vsi-interface3] ip binding vpn-instance vpna
[SwitchB-Vsi-interface3] l3-vni 1000
[SwitchB-Vsi-interface3] quit
# Configure GigabitEthernet 1/0/1 as an AC interface.
[SwitchB] interface gigabitethernet 1/0/1
[SwitchB-GigabitEthernet1/0/1] port link-mode bridge
[SwitchB-GigabitEthernet1/0/1] service-instance 1000
[SwitchB-GigabitEthernet1/0/1-srv1000] encapsulation s-vid 2
[SwitchB-GigabitEthernet1/0/1-srv1000] xconnect vsi vpna
[SwitchB-GigabitEthernet1/0/1-srv1000] quit
[SwitchB-GigabitEthernet1/0/1] quit
# Create node 0 and apply next hop 10.1.1.11 to packets with service chain path ID 1.
[SwitchB] policy-based-route aa permit node 0
[SwitchB-pbr-aa-0] if-match service-chain path-id 1
[SwitchB-pbr-aa-0] apply next-hop vpn-instance vpna 10.1.1.11
[SwitchB-pbr-aa-0] quit
# Apply policy aa to VSI-interface 3.
[SwitchB] interface vsi-interface 3
[SwitchB-Vsi-interface3] ip policy-based-route aa
[SwitchB-Vsi-interface3] quit
4. Configure Switch C:
# Enable L2VPN.
<SwitchC> system-view
[SwitchC] l2vpn enable
# Disable remote-MAC address learning and remote ARP learning.
[SwitchC] vxlan tunnel mac-learning disable
[SwitchC] vxlan tunnel arp-learning disable
# Create an EVPN instance in VSI instance view, and configure the system to automatically generate an RT and RD.
[SwitchC] vsi vpna
[SwitchC-vsi-vpna] evpn encapsulation vxlan
[SwitchC-vsi-vpna-evpn-vxlan] route-distinguisher auto
[SwitchC-vsi-vpna-evpn-vxlan] vpn-target auto
[SwitchC-vsi-vpna-evpn-vxlan] quit
# Configure VXLAN 10.
[SwitchC-vsi-vpna] vxlan 10
[SwitchC-vsi-vpna-vxlan-10] quit
[SwitchC-vsi-vpna] quit
398
# Configure BGP to advertise EVPN routes.
[SwitchC] bgp 200
[SwitchC-bgp-default] peer 4.4.4.4 as-number 200
[SwitchC-bgp-default] peer 4.4.4.4 connect-interface loopback 0
[SwitchC-bgp-default] address-family l2vpn evpn
[SwitchC-bgp-default-evpn] peer 4.4.4.4 enable
[SwitchC-bgp-default-evpn] quit
[SwitchC-bgp-default] quit
# Create VPN instance vpna .
[SwitchC] ip vpn-instance vpna
[SwitchC-vpn-instance-vpna] route-distinguisher 1:1
[SwitchC-vpn-instance-vpna] address-family ipv4
[SwitchC-vpn-ipv4-vpna] vpn-target 2:2
[SwitchC-vpn-ipv4-vpna] quit
[SwitchC-vpn-instance-vpna] address-family evpn
[SwitchC-vpn-evpn-vpna] vpn-target 1:1
[SwitchC-vpn-evpn-vpna] quit
# Create VSI-interface 1, assign an IP address to it, and specify the interface as a distributed gateway in VXLAN 10.
[SwitchC] interface vsi-interface 1
[SwitchC-Vsi-interface1] ip binding vpn-instance vpna
[SwitchC-Vsi-interface1] ip address 10.1.1.1 255.255.255.0
[SwitchC-Vsi-interface1] mac-address 0001-0001-0001
[SwitchC-Vsi-interface1] local-proxy-arp enable
[SwitchC-Vsi-interface1] distributed-gateway local
[SwitchC-Vsi-interface1] quit
# Associate VSI instance vpna with VSI-interface 1.
[SwitchC] vsi vpna
[SwitchC-vsi-vpna] gateway vsi-interface 1
[SwitchC-vsi-vpna] quit
# Bind VSI instance vpna to GigabitEthernet 1/0/1.
[SwitchC] interface gigabitethernet 1/0/1
[SwitchC-GigabitEthernet1/0/1] port link-mode bridge
[SwitchC-GigabitEthernet1/0/1] service-instance 2000
[SwitchC-GigabitEthernet1/0/1-srv2000] encapsulation s-vid 2
[SwitchC-GigabitEthernet1/0/1] xconnect vsi vpna
[SwitchC-GigabitEthernet1/0/1] quit
5. Configure Switch D:
# Configure Switch D to establish BGP connections with the other switches.
<SwitchD> system-view
[SwitchD] bgp 200
[SwitchD-bgp-default] group evpn
[SwitchD-bgp-default] peer 1.1.1.1 group evpn
[SwitchD-bgp-default] peer 2.2.2.2 group evpn
[SwitchD-bgp-default] peer 3.3.3.3 group evpn
[SwitchD-bgp-default] peer evpn as-number 200
[SwitchD-bgp-default] peer evpn connect-interface loopback 0
399
# Configure BGP to advertise EVPN routes, and disable route target filtering for BGP EVPN routes.
[SwitchD-bgp-default] address-family l2vpn evpn
[SwitchD-bgp-default-evpn] peer evpn enable
[SwitchD-bgp-default-evpn] undo policy vpn-target
# Configure Switch D as a route reflector.
[SwitchD-bgp-default-evpn] peer evpn reflect-client
[SwitchD-bgp-default-evpn] quit
[SwitchD-bgp-default] quit
# Configure VLAN-interface 11.
[SwitchD] interface vlan-interface 11
[SwitchD-Vlan-interface11] ip address 11.1.1.4 255.255.255.0
[SwitchD-Vlan-interface11] ospf 1 area 0.0.0.0
[SwitchD-Vlan-interface11] quit
# Configure VLAN-interface 12.
[SwitchD] interface vlan-interface 12
[SwitchD-Vlan-interface12] ip address 12.1.1.4 255.255.255.0
[SwitchD-Vlan-interface12] ospf 1 area 0.0.0.0
[SwitchD-Vlan-interface12] quit
# Configure VLAN-interface 13.
[SwitchD] interface Vlan-interface 13
[SwitchD-Vlan-interface13] ip address 13.1.1.4 255.255.255.0
[SwitchD-Vlan-interface13] ospf 1 area 0.0.0.0
[SwitchD-Vlan-interface13] quit
Verifying the configuration
# Capture packets sent from Server 1 to Server 2 in Ethernet service instance 1000. (Details not shown.)
The packets are processed by Service node 1 before they are delivered to Server 2.
400
Configuring IPv6 static routing
Static routes are manually configured and cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the network administrator must modify the static routes manually. IPv6 static routing works well in a simple IPv6 network.
Configuring an IPv6 static route
Before you configure an IPv6 static route, complete the following tasks:
•
Configure parameters for the related interfaces.
•
Configure link layer attributes for the related interfaces.
•
Make sure the neighboring nodes can reach each other.
To configure an IPv6 static route:
Step
1. Enter system view.
2. Configure an IPv6 static route.
Command system-view
•
Method 1: ipv6 route-static ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] | next-hop-address | vpn-instance d-vpn-instance-name next-hop-address }
[ permanent ] [ preference preference ]
[ tag tag-value ] [ description text ]
•
Method 2: ipv6 route-static vpn-instance s-vpn-instance-name ipv6-address prefix-length { interface-type interface-number [ next-hop-address ] | next-hop-address [ public ] | vpn-instance d-vpn-instance-name next-hop-address } [ permanent ]
[ preference preference ] [ tag tag-value ]
[ description text ]
3. (Optional.) Set the default preference for IPv6 static routes. ipv6 route-static default-preference
default-preference
Remarks
N/A
By default, no IPv6 static route is configured.
The default setting is
60.
4. (Optional.) Delete all IPv6 static routes, including the default route. delete ipv6 [ vpn-instance vpn-instance-name ] static-routes all
The undo ipv6 route-static command deletes one IPv6 static route.
Configuring BFD for IPv6 static routes
BFD provides a general purpose, standard, and medium- and protocol-independent fast failure detection mechanism. It can uniformly and quickly detect the failures of the bidirectional forwarding paths between two routers for protocols, such as routing protocols and MPLS. For more information about BFD, see High Availability Configuration Guide .
IMPORTANT:
Enabling BFD for a flapping route could worsen the situation.
401
Bidirectional control 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 BFD packet source address for the static route.
To configure BFD control mode for an IPv6 static route (direct next hop):
Step Command
1. Enter system view. system-view
Remarks
N/A
2. Configure BFD control mode for an
IPv6 static route. ipv6 route-static [ vpn-instance s-vpn-instance-name ] ipv6-address prefix-length interface-type interface-number next-hop-address bfd control-packet
[ bfd-source ipv6-address ] [ preference preference ] [ tag tag-value ] [ description text ]
By default, BFD control mode for an IPv6 static route is not configured.
To configure BFD control mode for an IPv6 static route (indirect next hop):
Step Command
1. Enter system view. system-view
Remarks
N/A
2. Configure BFD control mode for an
IPv6 static route. ipv6 route-static [ vpn-instance s-vpn-instance-name ] ipv6-address prefix-length [ vpn-instance d-vpn-instance-name ] { next-hop-address bfd control-packet bfd-source ipv6-address }
[ preference preference ] [ tag tag-value ]
[ description text ]
By default, BFD control mode for an IPv6 static route is not configured.
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.
IMPORTANT:
Do not use BFD for a static route with the output interface in spoofing state.
To configure BFD echo mode for an IPv6 static route:
Step Command
1. Enter system view. system-view
Remarks
N/A
402
Step
2. Configure the source address of echo packets.
Command
bfd echo-source-ipv6 ipv6-address
Remarks
By default, the source address of echo packets is not configured.
The source address of echo packets must be a global unicast address.
For more information about this command, see High
Availability Command
Reference .
3. Configure BFD echo mode for an IPv6 static route. ipv6 route-static [ vpn-instance s-vpn-instance-name ] ipv6-address prefix-length interface-type interface-number next-hop-address bfd echo-packet
[ bfd-source ipv6-address ] [ preference preference ] [ tag tag-value ] [ description text ]
By default, BFD echo mode for an IPv6 static route is not configured.
The next hop IPv6 address must be a global unicast address.
Displaying and maintaining IPv6 static routes
Execute display commands in any view.
Task
Display IPv6 static route information.
Command display ipv6 routing-table protocol static [ inactive | verbose ]
Display IPv6 static route next hop information. display ipv6 route-static nib [ nib-id ] [ verbose ]
Display IPv6 static routing table information. display ipv6 route-static routing-table [ vpn-instance vpn-instance-name ] [ ipv6-address prefix-length ]
IPv6 static routing configuration examples
Basic IPv6 static route configuration example
Network requirements
As shown in Figure 92 , configure IPv6 static routes so that hosts can reach one another.
403
Figure 92 Network diagram
Host B 2::2/64
Vlan-int400
2::1/64
Vlan-int200
4::2/64
Switch B
Vlan-int300
5::2/64
Vlan-int200
4::1/64
Vlan-int300
5::1/64
Host A 1::2/64
Vlan-int100
1::1/64
Switch A
Vlan-int500
Switch C
3::1/64
Host C 3::2/64
Configuration procedure
1. Configure the IPv6 addresses for all VLAN interfaces. (Details not shown.)
2. Configure IPv6 static routes:
# Configure a default IPv6 static route on Switch A.
<SwitchA> system-view
[SwitchA] ipv6 route-static :: 0 4::2
# Configure two IPv6 static routes on Switch B.
<SwitchB> system-view
[SwitchB] ipv6 route-static 1:: 64 4::1
[SwitchB] ipv6 route-static 3:: 64 5::1
# Configure a default IPv6 static route on Switch C.
<SwitchC> system-view
[SwitchC] ipv6 route-static :: 0 5::2
3. Configure the IPv6 addresses for all the hosts and configure the default gateway of Host A,
Host B, and Host C as 1::1, 2::1, and 3::1.
Verifying the configuration
# Display the IPv6 static route information on Switch A.
[SwitchA] display ipv6 routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination: :: Protocol : Static
NextHop : 4::2 Preference: 60
Interface : Vlan-interface200 Cost : 0
Static Routing table Status : <Inactive>
Summary Count : 0
# Display the IPv6 static route information on Switch B.
[SwitchB] display ipv6 routing-table protocol static
404
Summary Count : 2
Static Routing table Status : <Active>
Summary Count : 2
Destination: 1::/64 Protocol : Static
NextHop : 4::1 Preference: 60
Interface : Vlan-interface200 Cost : 0
Destination: 3::/64 Protocol : Static
NextHop : 5::1 Preference: 60
Interface : Vlan-interface300 Cost : 0
Static Routing table Status : <Inactive>
Summary Count : 0
# Use the ping command to test the reachability.
[SwitchA] ping ipv6 3::1
Ping6(56 data bytes) 4::1 --> 3::1, press CTRL_C to break
56 bytes from 3::1, icmp_seq=0 hlim=62 time=0.700 ms
56 bytes from 3::1, icmp_seq=1 hlim=62 time=0.351 ms
56 bytes from 3::1, icmp_seq=2 hlim=62 time=0.338 ms
56 bytes from 3::1, icmp_seq=3 hlim=62 time=0.373 ms
56 bytes from 3::1, icmp_seq=4 hlim=62 time=0.316 ms
--- Ping6 statistics for 3::1 ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss round-trip min/avg/max/std-dev = 0.316/0.416/0.700/0.143 ms
BFD for IPv6 static routes configuration example (direct next hop)
Network requirements
•
Configure an IPv6 static route to subnet 120::/64 on Switch A.
•
Configure an IPv6 static route to subnet 121::/64 on Switch B.
•
Enable BFD for both routes.
•
Configure an IPv6 static route to subnet 120::/64 and an IPv6 static route to subnet 121::/64 on
Switch C.
When the link between Switch A and Switch B through the Layer 2 switch fails, BFD can detect the failure immediately, and Switch A and Switch B can communicate through Switch C.
405
Figure 93 Network diagram
121::/64
Switch A L2 Switch
Vlan-int10 Vlan-int10
Switch B
120::/64
Vlan-int11 Vlan-int13
BFD
Vlan-int11 Vlan-int13
Switch C
Table 24 Interface and IP address assignment
Device
Switch A
Switch A
Switch B
Switch B
Switch C
Interface
Vlan-int10
Vlan-int11
Vlan-int10
Vlan-int13
Vlan-int11
IPv6 address
12::1/64
10::102/64
12::2/64
13::1/64
10::100/64
Switch C
Configuration procedure
Vlan-int13 13::2/64
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure IPv6 static routes and BFD:
# Configure IPv6 static routes on Switch A and enable BFD control mode for the static route that traverses the Layer 2 switch.
<SwitchA> system-view
[SwitchA] interface vlan-interface 10
[SwitchA-vlan-interface10] bfd min-transmit-interval 500
[SwitchA-vlan-interface10] bfd min-receive-interval 500
[SwitchA-vlan-interface10] bfd detect-multiplier 9
[SwitchA-vlan-interface10] quit
[SwitchA] ipv6 route-static 120:: 64 vlan-interface 10 12::2 bfd control-packet
[SwitchA] ipv6 route-static 120:: 64 10::100 preference 65
[SwitchA] quit
# Configure IPv6 static routes on Switch B and enable BFD control mode for the static route that traverses the Layer 2 switch.
<SwitchB> system-view
[SwitchB] interface vlan-interface 10
[SwitchB-vlan-interface10] bfd min-transmit-interval 500
[SwitchB-vlan-interface10] bfd min-receive-interval 500
[SwitchB-vlan-interface10] bfd detect-multiplier 9
[SwitchB-vlan-interface10] quit
[SwitchB] ipv6 route-static 121:: 64 vlan-interface 10 12::1 bfd control-packet
[SwitchB] ipv6 route-static 121:: 64 vlan-interface 13 13::2 preference 65
[SwitchB] quit
# Configure IPv6 static routes on Switch C.
406
<SwitchC> system-view
[SwitchC] ipv6 route-static 120:: 64 13::1
[SwitchC] ipv6 route-static 121:: 64 10::102
Verifying the configuration
# Display the BFD sessions on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv6 Session Working Under Ctrl Mode:
Local Discr: 513 Remote Discr: 33
Source IP: 12::1
Destination IP: 12::2
Session State: Up Interface: Vlan10
Hold Time: 2012ms
The output shows that the BFD session has been created.
# Display IPv6 static routes on Switch A.
<SwitchA> display ipv6 routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination: 120::/64 Protocol : Static
NextHop : 12::2 Preference: 60
Interface : Vlan10 Cost : 0
Direct Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through VLAN-interface 10. The link over VLAN-interface 10 fails.
# Display IPv6 static routes on Switch A again.
<SwitchA> display ipv6 routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination: 120::/64 Protocol : Static
NextHop : 10::100 Preference: 65
Interface : Vlan11 Cost : 0
Static Routing table Status : < Inactive>
Summary Count : 0
407
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
BFD for IPv6 static routes configuration example (indirect next hop)
Network requirements
•
Switch A has a route to interface Loopback 1 (2::9/128) on Switch B, and the output interface is
VLAN-interface 10.
•
Switch B has a route to interface Loopback 1 (1::9/128) on Switch A, and the output interface is
VLAN-interface 12.
•
Switch D has a route to 1::9/128, and the output interface is VLAN-interface 10. It also has a route to 2::9/128, and the output interface is VLAN-interface 12.
Configure the following:
•
Configure an IPv6 static route to subnet 120::/64 on Switch A.
•
Configure an IPv6 static route to subnet 121::/64 on Switch B.
•
Enable BFD for both routes.
•
Configure an IPv6 static route to subnet 120::/64 and an IPv6 static route to subnet 121::/64 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 and Switch A and Switch B can communicate through Switch C.
Figure 94 Network diagram
121::/64
Loop1
1::9/128
Loop1
2::9/128
Switch D
Vlan-int10
Switch A
Vlan
-int
11
Vlan-int10
BFD
Vlan-int12
Vlan-int12
Vlan
-int
13
Switch B
120::/64
Vlan-int11 Vlan-int13
Switch C
Table 25 Interface and IP address assignment
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Switch C
Interface
Vlan-int10
Vlan-int11
Loop1
Vlan-int12
Vlan-int13
Loop1
Vlan-int11
Vlan-int13
IPv6 address
12::1/64
10::102/64
1::9/128
11::2/64
13::1/64
2::9/128
10::100/64
13::2/64
408
Device
Switch D
Interface
Vlan-int10
IPv6 address
12::2/64
Switch D Vlan-int12 11::1/64
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure IPv6 static routes and BFD:
# Configure IPv6 static routes on Switch A and enable BFD control packet mode for the IPv6 static route that traverses Switch D.
<SwitchA> system-view
[SwitchA] bfd multi-hop min-transmit-interval 500
[SwitchA] bfd multi-hop min-receive-interval 500
[SwitchA] bfd multi-hop detect-multiplier 9
[SwitchA] ipv6 route-static 120:: 64 2::9 bfd control-packet bfd-source 1::9
[SwitchA] ipv6 route-static 120:: 64 10::100 preference 65
[SwitchA] ipv6 route-static 2::9 128 12::2
[SwitchA] quit
# Configure IPv6 static routes on Switch B and enable BFD control packet mode for the static route that traverses Switch D.
<SwitchB> system-view
[SwitchB] bfd multi-hop min-transmit-interval 500
[SwitchB] bfd multi-hop min-receive-interval 500
[SwitchB] bfd multi-hop detect-multiplier 9
[SwitchB] ipv6 route-static 121:: 64 1::9 bfd control-packet bfd-source 2::9
[SwitchB] ipv6 route-static 121:: 64 13::2 preference 65
[SwitchB] ipv6 route-static 1::9 128 11::1
[SwitchB] quit
# Configure IPv6 static routes on Switch C.
<SwitchC> system-view
[SwitchC] ipv6 route-static 120:: 64 13::1
[SwitchC] ipv6 route-static 121:: 64 10::102
# Configure IPv6 static routes on Switch D.
<SwitchD> system-view
[SwitchD] ipv6 route-static 120:: 64 11::2
[SwitchD] ipv6 route-static 121:: 64 12::1
[SwitchD] ipv6 route-static 2::9 128 11::2
[SwitchD] ipv6 route-static 1::9 128 12::1
Verifying the configuration
# Display the BFD sessions on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Up Session Num: 1 Init Mode: Active
IPv6 Session Working Under Ctrl Mode:
Local Discr: 513 Remote Discr: 33
Source IP: 1::9
409
Destination IP: 2::9
Session State: Up Interface: N/A
Hold Time: 2012ms
The output shows that the BFD session has been created.
# Display the IPv6 static routes on Switch A.
<SwitchA> display ipv6 routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination: 120::/64 Protocol : Static
NextHop : 2::9 Preference: 60
Interface : Vlan10 Cost : 0
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates Switch B through VLAN-interface 10. The link over
VLAN-interface 10 fails.
# Display IPv6 static routes on Switch A again.
<SwitchA> display ipv6 routing-table protocol static
Summary Count : 1
Static Routing table Status : <Active>
Summary Count : 1
Destination: 120::/64 Protocol : Static
NextHop : 10::100 Preference: 65
Interface : Vlan11 Cost : 0
Static Routing table Status : <Inactive>
Summary Count : 0
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
410
Configuring an IPv6 default route
A default IPv6 route is used to forward packets that match no entry in the routing table.
A default IPv6 route can be configured in either of the following ways:
•
The network administrator can configure a default route with a destination prefix of ::/0 . For
more information, see " Configuring IPv6 static routing ."
•
Some dynamic routing protocols, such as OSPFv3, IPv6 IS-IS, and RIPng, can generate a default IPv6 route. For example, an upstream router running OSPFv3 can generate a default
IPv6 route and advertise it to other routers. These routers install the default IPv6 route with the next hop being the upstream router. For more information, see the respective chapters on those routing protocols in this configuration guide.
411
Configuring RIPng
Overview
RIP next generation (RIPng) is an extension of RIP-2 for support of IPv6. Most RIP concepts are applicable to RIPng.
RIPng is a distance vector routing protocol. It employs UDP to exchange route information through port 521. RIPng uses a hop count to measure the distance to a destination. The hop count is the metric or cost. The hop count from a router to a directly connected network is 0. The hop count between two directly connected routers is 1. When the hop count is greater than or equal to 16, the destination network or host is unreachable.
By default, the routing update is sent every 30 seconds. If the router receives no routing updates from a neighbor within 180 seconds, the routes learned from the neighbor are considered unreachable. If no routing update is received within another 240 seconds, the router removes these routes from the routing table.
RIPng for IPv6 has the following differences from RIP:
•
UDP port number —RIPng uses UDP port 521 to send and receive routing information.
•
Multicast address —RIPng uses FF02::9 as the link-local-router multicast address.
•
Destination Prefix —128-bit destination address prefix.
•
Next hop —128-bit IPv6 address.
•
Source address —RIPng uses FE80::/10 as the link-local source address.
RIPng route entries
RIPng stores route entries in a database. Each route entry contains the following elements:
•
Destination address —IPv6 address of a destination host or a network.
•
Next hop address —IPv6 address of the next hop.
•
Egress interface —Egress interface of the route.
•
Metric —Cost from the local router to the destination.
•
Route time —Time elapsed since the most recent update. The time is reset to 0 every time the route entry is updated.
•
Route tag
—Used for route control. For more information, see " Configuring routing policies ."
RIPng packets
RIPng uses request and response packets to exchange routing information as follows:
1. When RIPng starts or needs to update some route entries, it sends a multicast request packet to neighbors.
2. When a RIPng neighbor receives the request packet, it sends back a response packet that contains the local routing table. RIPng can also advertise route updates in response packets periodically or advertise a triggered update caused by a route change.
3. After RIPng receives the response, it checks the validity of the response before adding routes to its routing table, including the following details:
Whether the source IPv6 address is the link-local address.
Whether the port number is correct.
412
4. A response packet that fails the check is discarded.
Protocols and standards
•
RFC 2080, RIPng for IPv6
•
RFC 2081, RIPng Protocol Applicability Statement
RIPng configuration task list
Tasks at a glance
(Required.) Configuring basic RIPng
(Optional.) Configuring RIPng route control :
•
Configuring an additional routing metric
•
Configuring RIPng route summarization
•
•
Configuring received/redistributed route filtering
•
Setting a preference for RIPng
•
Configuring RIPng route redistribution
(Optional.) Tuning and optimizing the RIPng network :
•
•
Configuring split horizon and poison reverse
•
Configuring zero field check on RIPng packets
•
Setting the maximum number of ECMP routes
•
Configuring the RIPng packet sending rate
•
Setting the interval for sending triggered updates
(Optional.) Configuring RIPng GR
(Optional.) Configuring RIPng NSR
(Optional.) Configuring RIPng FRR
(Optional.) Applying an IPsec profile
Configuring basic RIPng
Before you configure basic RIPng, configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
To configure basic RIPng:
Step
1. Enter system view.
2. Enable RIPng and enter its view.
3. Return to system view.
4. Enter interface view.
Command system-view ripng [ process-id ]
[ vpn-instance vpn-instance-name ] quit interface interface-type interface-number
Remarks
N/A
By default, RIPng is disabled.
N/A
N/A
413
Step
5. Enable RIPng on the interface.
Command
ripng process-id enable
Remarks
By default, RIPng is disabled.
If RIPng is not enabled on an interface, the interface does not send or receive any RIPng route.
Configuring RIPng route control
Before you configure RIPng, complete the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
•
Configure basic RIPng.
Configuring an additional routing metric
An additional routing metric (hop count) can be added to the metric of an inbound or outbound RIPng route.
An outbound additional metric is added to the metric of a sent route, and it does not change the route's metric in the routing table.
An inbound additional metric is added to the metric of a received route before the route is added into the routing table, and the route's metric is changed.
To configure an inbound or outbound additional routing metric:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Specify an inbound additional routing metric.
4. Specify an outbound additional routing metric.
ripng metricin value ripng metricout value
The default setting is 0.
The default setting is 1.
Configuring RIPng route summarization
Configure route summarization on an interface, so RIPng advertises a summary route based on the longest match.
RIPng route summarization improves network scalability, reduces routing table size, and increases routing table lookup efficiency.
RIPng advertises a summary route with the smallest metric of all the specific routes.
For example, RIPng has two specific routes to be advertised through an interface: 1:11:11::24 with a metric of a 2 and 1:11:12::34 with a metric of 3. Configure route summarization on the interface, so
RIPng advertises a single route 11::0/16 with a metric of 2.
To configure RIPng route summarization:
Step
1. Enter system view.
Command system-view
Remarks
N/A
414
Step
2. Enter interface view.
3. Advertise a summary IPv6 prefix.
Command interface interface-type interface-number
ripng summary-address ipv6-address prefix-length
Remarks
N/A
By default, the summary IPv6 prefix is not configured.
Advertising a default route
You can configure RIPng to advertise a default route with the specified cost to its neighbors.
To configure RIPng to advertise a default route:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter interface view. interface interface-type interface-number
N/A
3. Configure RIPng to advertise a default route. ripng default-route { only | originate } [ cost cost-value | route-policy route-policy-name ] *
By default, RIPng does not advertise a default route.
This command advertises a default route on the current interface regardless of whether the default route exists in the local IPv6 routing table.
Configuring received/redistributed route filtering
Perform this task to filter received or redistributed routes by using an IPv6 ACL or IPv6 prefix list. You can also configure RIPng to filter routes redistributed from other routing protocols and routes from a specified neighbor.
To configure a RIPng route filtering policy:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter RIPng view.
3. Configure a filter policy to filter received routes.
4. Configure a filter policy to filter redistributed routes. ripng [ process-id ] [ vpn-instance vpn-instance-name ] filter-policy { ipv6-acl-number | prefix-list prefix-list-name } import filter-policy { ipv6-acl-number | prefix-list prefix-list-name } export
[ protocol [ process-id ] ]
N/A
By default, RIPng does not filter received routes.
By default, RIPng does not filter redistributed routes.
Setting a preference for RIPng
Routing protocols each have a preference. When they find routes to the same destination, the route found by the routing protocol with the highest preference is selected as the optimal route. You can manually set a preference for RIPng. The smaller the value, the higher the preference.
To set a preference for RIPng:
415
Step
1. Enter system view.
2. Enter RIPng view.
3. Set a preference for RIPng.
Command system-view ripng [ process-id ]
[ vpn-instance vpn-instance-name ] preference { preference | route-policy route-policy-name }
*
Remarks
N/A
N/A
By default, the preference of
RIPng is 100.
Configuring RIPng route redistribution
Step
1. Enter system view.
2. Enter RIPng view.
3. Redistribute routes from other routing protocols.
Command system-view
Remarks
N/A ripng [ process-id ]
[ vpn-instance vpn-instance-name ]
N/A import-route protocol
[ as-number | process-id ]
[ allow-ibgp ] [ allow-direct | cost cost-value | route-policy route-policy-name ] *
By default, RIPng does not redistribute routes from other routing protocols.
default cost cost-value
The default metric of redistributed routes is 0.
4. (Optional.) Set a default routing metric for redistributed routes.
Tuning and optimizing the RIPng network
This section describes how to tune and optimize the performance of the RIPng network as well as applications under special network environments.
Before you tune and optimize the RIPng network, complete the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
•
Configure basic RIPng.
Setting RIPng timers
You can adjust RIPng timers to optimize the performance of the RIPng network.
When you adjust RIPng timers, consider the network performance, and perform unified configurations on routers running RIPng to avoid unnecessary network traffic or route oscillation.
To set RIPng timers:
Step Command
1. Enter system view.
system-view
2. Enter RIPng view. ripng [ process-id ]
[ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
416
Step
3. Set RIPng timers.
Command timers { garbage-collect garbage-collect-value |
suppress suppress-value |
timeout timeout-value | update update-value } *
Remarks
By default:
•
The update timer is 30 seconds.
•
The timeout timer is 180 seconds.
•
The suppress timer is 120 seconds.
•
The garbage-collect timer is 120 seconds.
Configuring split horizon and poison reverse
If both split horizon and poison reverse are configured, only the poison reverse function takes effect.
Configuring split horizon
Split horizon disables RIPng from sending routes through the interface where the routes were learned to prevent routing loops between neighbors.
As a best practice, enable split horizon to prevent routing loops in normal cases.
To configure split horizon:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable split horizon. ripng split-horizon
By default, split horizon is enabled.
Configuring poison reverse
Poison reverse enables a route learned from an interface to be advertised through the interface.
However, the metric of the route is set to 16, which means the route is unreachable.
To configure poison reverse:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable poison reverse. ripng poison-reverse
By default, poison reverse is disabled.
Configuring zero field check on RIPng packets
Some fields in the RIPng packet header must be zero. These fields are called zero fields. You can enable zero field check on incoming RIPng packets. If a zero field of a packet contains a non-zero value, RIPng does not process the packets. If you are certain that all packets are trustworthy, disable the zero field check to save CPU resources.
To configure RIPng zero field check:
Step
1. Enter system view.
Command system-view
Remarks
N/A
417
Step
2. Enter RIPng view.
Command ripng [ process-id ]
[ vpn-instance vpn-instance-name ]
3. Enable the zero field check on incoming RIPng packets. checkzero
Remarks
N/A
By default, zero field check is enabled for incoming RIPng packets.
Setting the maximum number of ECMP routes
Step
1. Enter system view.
2. Enter RIPng view.
3. Set the maximum number of ECMP routes.
Command system-view
Remarks
N/A ripng [ process-id ] [ vpn-instance vpn-instance-name ]
N/A maximum load-balancing number
By default, the maximum number of ECMP routes equals the maximum number of ECMP routes supported by the system.
Configuring the RIPng packet sending rate
Perform this task to specify the interval for sending RIPng packets and the maximum number of
RIPng packets that can be sent at each interval. This feature can avoid excessive RIPng packets from affecting system performance and consuming too much bandwidth.
To configure the RIPng packet sending rate:
Step
1. Enter system view.
2. Enter RIPng view.
Command system-view ripng [ process-id ]
[ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Set the interval for sending
RIPng packets and the maximum number of RIPng packets that can be sent at each interval.
4. Return to system view.
output-delay time count count
By default, a RIPng process sends a maximum of three RIPng packets every 20 milliseconds.
N/A
5. Enter interface view. quit interface interface-type
interface-number
N/A
6. Set the interval for sending
RIPng packets and the maximum number of RIPng packets that can be sent at each interval. ripng output-delay time count
count
By default, an interface uses the
RIPng packet sending rate configured for the RIPng process that the interface runs.
418
Setting the interval for sending triggered updates
Perform this task to avoid network overhead and reduce system resource consumption caused by frequent RIPng triggered updates.
You can use the timer triggered command to set the maximum interval, minimum interval, and incremental interval for sending RIPng triggered updates.
For a stable network, the minimum interval is used. If network changes become frequent, the triggered update sending interval is incremented by the incremental interval × 2 n-2
for each triggered update until the maximum interval is reached. The value n is the number of triggered update times.
To set the interval for sending triggered updates:
Step
1. Enter system view.
2. Enter RIPng view.
Command system-view ripng [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Set the interval for sending triggered updates.
timer triggered maximum-interval
[ minimum-interval
[ incremental-interval ] ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is 50 milliseconds.
•
The incremental interval is 200 milliseconds.
Configuring RIPng GR
GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Two routers are required to complete a GR process. The following are router roles in a GR process:
•
GR restarter —Graceful restarting router. It must have GR capability.
•
GR helper —A neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
After RIPng restarts on a router, the router must learn RIPng routes again and updates its FIB table, which causes network disconnections and route reconvergence.
With the GR feature, the restarting router (known as the GR restarter) can notify the event to its GR capable neighbors. GR capable neighbors (known as GR helpers) maintain their adjacencies with the router within a configurable GR interval. During this process, the FIB table of the router does not change. After the restart, the router contacts its neighbors to retrieve its FIB.
By default, a RIPng-enabled device acts as the GR helper. Perform this task on the GR restarter.
IMPORTANT:
You cannot enable RIPng NSR on a device that acts as GR restarter.
To configure GR on the GR restarter:
Step
1. Enter system view.
Command system-view
Remarks
N/A
419
Step
2. Enable RIPng and enter
RIPng view.
Command ripng [ process-id ]
[ vpn-instance vpn-instance-name ]
Remarks
N/A
3. Enable the GR capability for
RIPng.
4. (Optional.) Set the GR interval. graceful-restart graceful-restart interval interval
By default, RIPng GR is disabled.
By default, the GR interval is 60 seconds.
Configuring RIPng NSR
Nonstop routing (NSR) backs up RIPng routing information from the active process to the standby process. After an active/standby switchover, NSR can complete route regeneration without tearing down adjacencies or impacting forwarding services.
NSR does not require the cooperation of neighboring devices to recover routing information, and it is typically used more often than GR.
IMPORTANT:
A device that has RIPng NSR enabled cannot act as GR restarter.
To enable RIPng NSR:
Step Command
1. Enter system view. system-view
2. Enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enable RIPng NSR. non-stop-routing
By default, RIPng NSR is disabled.
RIPng NSR enabled for a RIPng process takes effect only on that process. If multiple RIPng processes exist, enable RIPng NSR for each process as a best practice.
Configuring RIPng FRR
A link or router failure on a path can cause packet loss and even routing loop until RIPng completes routing convergence based on the new network topology. FRR enables fast rerouting to minimize the impact of link or node failures.
Figure 95 Network diagram for RIPng FRR
Backup next hop: Router C
Router A Router B Next hop: Router D Router E
420
As shown in Figure 95 , configure FRR on Router B by using a routing policy to specify a backup next
hop. When the primary link fails, RIPng directs packets to the backup next hop. At the same time,
RIPng calculates the shortest path based on the new network topology. Then, the device forwards packets over that path after network convergence.
Configuration restrictions and guidelines
•
RIPng FRR is available only when the state of the primary link (with Layer 3 interfaces staying up) changes from bidirectional to unidirectional or down.
•
RIPng FRR is only effective for RIPng routes that are learned from directly connected neighbors.
•
Equal-cost routes do not support RIPng FRR.
Configuration prerequisites
You must specify a next hop by using the apply ipv6 fast-reroute backup-interface command in a routing policy and reference the routing policy for FRR. For more information about routing policy
configuration, see " Configuring routing policies ."
Configuring RIPng FRR
Step
1. Enter system view.
2. Enter RIPng view.
Command system-view
Remarks
N/A ripng [ process-id ] [ vpn-instance vpn-instance-name ]
N/A fast-reroute route-policy route-policy-name
By default, RIPng FRR is disabled.
3. Configure RIPng FRR.
Enabling BFD for RIPng FRR
By default, RIPng FRR does not use BFD to detect primary link failures. To speed up RIPng convergence, enable BFD single-hop echo detection for RIPng FRR to detect primary link failures.
To configure BFD for RIPng FRR:
Step
1. Enter system view.
2. Configure the source IP address of BFD echo packets.
Command system-view
bfd echo-source-ipv6 ipv6-address
Remarks
N/A
By default, the source IP address of BFD echo packets is not 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 High Availability
Command Reference .
3. Enter interface view.
4. Enable BFD for RIPng FRR. interface interface-type interface-number ripng primary-path-detect bfd echo
N/A
By default, BFD for RIPng FRR is disabled.
421
Applying an IPsec profile
To protect routing information and prevent attacks, RIPng supports using an IPsec profile to authenticate protocol packets. For more information about IPsec profiles, see Security Configuration
Guide .
Outbound RIPng packets carry the Security Parameter Index (SPI) defined in the relevant IPsec profile. A device compares the SPI carried in a received packet with the configured IPsec profile. If they match, the device accepts the packet. If they do not match, the device discards the packet and does not establish a neighbor relationship with the sending device.
You can configure an IPsec profile for a RIPng process or interface. The IPsec profile configured for a process applies to all packets in the process. The IPsec profile configured for an interface applies to packets on the interface. If an interface and its process each have an IPsec profile configured, the interface uses its own IPsec profile.
To apply an IPsec profile to a process:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter RIPng view. ripng [ process-id ] [ vpn-instance vpn-instance-name ]
N/A
3. Apply an IPsec profile to the process. enable ipsec-profile profile-name
To apply an IPsec profile to an interface:
By default, no IPsec profile is applied.
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Apply an IPsec profile to the interface. ripng ipsec-profile profile-name
By default, no IPsec profile is applied.
Displaying and maintaining RIPng
Execute display commands in any view and reset commands in user view.
Command Task
Display configuration information for a
RIPng process. display ripng [ process-id ]
Display routes in the RIPng database.
Display RIPng GR information.
Display interface information for a RIPng process.
Display neighbor information for a RIPng process. display ripng process-id database [ ipv6-address prefix-length ] display ripng [ process-id ] graceful-restart display ripng process-id interface [ interface-type interface-number ] display ripng process-id neighbor [ interface-type interface-number ]
422
Task
Display RIPng NSR information.
Display the routing information for a RIPng process.
Restart a RIPng process.
Clear statistics for a RIPng process.
Command display ripng [ process-id ] non-stop-routing display ripng process-id route [ ipv6-address prefix-length
[ verbose ] | peer ipv6-address | statistics ] reset ripng process-id process reset ripng process-id statistics
RIPng configuration examples
Basic RIPng configuration example
Network requirements
As shown in Figure 96 , Switch A, Switch B, and Switch C run RIPng. Configure Switch B to filter the
route 2::/64 learned from Switch A and to forward only the route 4::/64 to Switch A.
Figure 96 Network diagram
Vlan-int400
2::1/64
Switch A
Vlan-int100
1::1/64
Vlan-int100
1::2/64
Switch B
Vlan-int200
3::1/64
Vlan-int600
4::1/64
Vlan-int500
5::1/64
Vlan-int200
3::2/64
Switch C
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic RIPng:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ripng 1
[SwitchA-ripng-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ripng 1 enable
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 400
[SwitchA-Vlan-interface400] ripng 1 enable
[SwitchA-Vlan-interface400] quit
# Configure Switch B.
<SwitchA> system-view
[SwitchA] ripng 1
[SwitchA-ripng-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ripng 1 enable
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 400
[SwitchA-Vlan-interface400] ripng 1 enable
[SwitchA-Vlan-interface400] quit
# Configure Switch C.
423
<SwitchC> system-view
[SwitchC] ripng 1
[SwitchC-ripng-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] ripng 1 enable
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 500
[SwitchC-Vlan-interface500] ripng 1 enable
[SwitchC-Vlan-interface500] quit
[SwitchC] interface vlan-interface 600
[SwitchC-Vlan-interface600] ripng 1 enable
[SwitchC-Vlan-interface600] quit
# Display the RIPng routing table on Switch B.
[SwitchB] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::20F:E2FF:FE23:82F5 on Vlan-interface100
Destination 2::/64,
via FE80::20F:E2FF:FE23:82F5, cost 1, tag 0, AOF, 6 secs
Peer FE80::20F:E2FF:FE00:100 on Vlan-interface200
Destination 4::/64,
via FE80::20F:E2FF:FE00:100, cost 1, tag 0, AOF, 11 secs
Destination 5::/64,
via FE80::20F:E2FF:FE00:100, cost 1, tag 0, AOF, 11
Local route
Destination 1::/64,
via ::, cost 0, tag 0, DOF
Destination 3::/64,
via ::, cost 0, tag 0, DOF
# Display the RIPng routing table on Switch A.
[SwitchA] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::200:2FF:FE64:8904 on Vlan-interface100
Destination 3::/64,
via FE80::200:2FF:FE64:8904, cost 1, tag 0, AOF, 31 secs
Destination 4::/64,
via FE80::200:2FF:FE64:8904, cost 2, tag 0, AOF, 31 secs
Destination 5::/64,
via FE80::200:2FF:FE64:8904, cost 2, tag 0, AOF, 31 secs
Local route
Destination 2::/64,
via ::, cost 0, tag 0, DOF
Destination 1::/64,
424
via ::, cost 0, tag 0, DOF
3. Configure route filtering:
# Use IPv6 prefix lists on Switch B to filter received and redistributed routes.
[SwitchB] ipv6 prefix-list aaa permit 4:: 64
[SwitchB] ipv6 prefix-list bbb deny 2:: 64
[SwitchB] ipv6 prefix-list bbb permit :: 0 less-equal 128
[SwitchB] ripng 1
[SwitchB-ripng-1] filter-policy prefix-list aaa export
[SwitchB-ripng-1] filter-policy prefix-list bbb import
[SwitchB-ripng-1] quit
# Display RIPng routing tables on Switch B and Switch A.
[SwitchB] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::1:100 on Vlan-interface100
Peer FE80::3:200 on Vlan-interface200
Destination 4::/64,
via FE80::2:200, cost 1, tag 0, AOF, 11 secs
Destination 5::/64,
via FE80::2:200, cost 1, tag 0, AOF, 11 secs
Local route
Destination 1::/64,
via ::, cost 0, tag 0, DOF
Destination 3::/64,
via ::, cost 0, tag 0, DOF
[SwitchA] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D – Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::2:100 on Vlan-interface100
Destination 4::/64,
via FE80::1:100, cost 2, tag 0, AOF, 2 secs
RIPng route redistribution configuration example
Network requirements
As shown in Figure 97 , Switch B communicates with Switch A through RIPng 100 and with Switch C
through RIPng 200.
Configure route redistribution on Switch B, so the two RIPng processes can redistribute routes from each other.
425
Figure 97 Network diagram
RIPng 100 RIPng 200
Vlan-int200
2::1/64
Switch A
Vlan-int100
1::1/64
Vlan-int100
1::2/64
Switch B
Vlan-int300
3::1/64
Vlan-int300
3::2/64
Switch C
Vlan-int400
4::1/64
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic RIPng:
# Enable RIPng 100 on Switch A.
<SwitchA> system-view
[SwitchA] ripng 100
[SwitchA-ripng-100] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ripng 100 enable
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ripng 100 enable
[SwitchA-Vlan-interface200] quit
# Enable RIPng 100 and RIPng 200 on Switch B.
<SwitchB> system-view
[SwitchB] ripng 100
[SwitchB-ripng-100] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ripng 100 enable
[SwitchB-Vlan-interface100] quit
[SwitchB] ripng 200
[SwitchB-ripng-200] quit
[SwitchB] interface vlan-interface 300
[SwitchB-Vlan-interface300] ripng 200 enable
[SwitchB-Vlan-interface300] quit
# Enable RIPng 200 on Switch C.
<SwitchC> system-view
[SwitchC] ripng 200
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] ripng 200 enable
[SwitchC-Vlan-interface300] quit
[SwitchC] interface vlan-interface 400
[SwitchC-Vlan-interface400] ripng 200 enable
[SwitchC-Vlan-interface400] quit
# Display the routing table on Switch A.
[SwitchA] display ipv6 routing-table
Destinations : 7 Routes : 7
426
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 1::/64 Protocol : Direct
NextHop : 1::1 Preference: 0
Interface : Vlan100 Cost : 0
Destination: 1::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2::/64 Protocol : Direct
NextHop : 2::1 Preference: 0
Interface : Vlan200 Cost : 0
Destination: 2::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
3. Configure RIPng route redistribution:
# Configure route redistribution between the two RIPng processes on Switch B.
[SwitchB] ripng 100
[SwitchB-ripng-100] import-route ripng 200
[SwitchB-ripng-100] quit
[SwitchB] ripng 200
[SwitchB-ripng-200] import-route ripng 100
[SwitchB-ripng-200] quit
# Display the routing table on Switch A.
[SwitchA] display ipv6 routing-table
Destinations : 8 Routes : 8
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 1::/64 Protocol : Direct
NextHop : 1::1 Preference: 0
Interface : Vlan100 Cost : 0
427
Destination: 1::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 2::/64 Protocol : Direct
NextHop : 2::1 Preference: 0
Interface : Vlan200 Cost : 0
Destination: 2::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 4::/64 Protocol : RIPng
NextHop : FE80::200:BFF:FE01:1C02 Preference: 100
Interface : Vlan100 Cost : 1
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
RIPng GR configuration example
Network requirements
As shown in Figure 98 , Switch A, Switch B, and Switch C learn IPv6 routing information through
RIPng.
Configure Switch A as the GR restarter. Configure Switch B and Switch C as the GR helpers to synchronize their routing tables with Switch A by using GR.
Figure 98 Network diagram
Router ID: 1.1.1.1
GR restarter
Switch A
Vlan-int100
2000::1/24
Vlan-int100
2000::2/24
Switch B
Vlan-int100
2000::3/24
Switch C
GR helper
Router ID: 2.2.2.2
Configuration procedure
GR helper
Router ID: 3.3.3.3
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure RIPng on the switches to ensure the following: (Details not shown.)
Switch A, Switch B, and Switch C can communicate with each other at Layer 3.
428
Dynamic route update can be implemented among them with RIPng.
3. Enable RIPng GR on Switch A.
<SwitchA> system-view
[SwitchA] ripng 1
[SwitchA-ripng-1] graceful-restart
Verifying the configuration
# Restart RIPng process 1 on Switch A.
[SwitchA-ripng-1] return
<SwitchA> reset ripng 1 process
Reset RIPng process? [Y/N]:y
# Display GR information on Switch A.
<SwitchA> display ripng 1 graceful-restart
RIPng process: 1
Graceful Restart capability : Enabled
Current GR state : Normal
Graceful Restart period : 60 seconds
Graceful Restart remaining time: 0 seconds
RIPng NSR configuration example
Network requirements
As shown in Figure 99 , Switch S, Switch A, and Switch B learn IPv6 routing information through
RIPng.
Enable RIPng NSR on Switch S to ensure correct routing when an active/standby switchover occurs on Switch S.
Figure 99 Network diagram
Loop 0
2002::2/128
Switch A
Vlan-int100
1200:1::1/64
Vlan-int100
1200:1::2/64
Switch S
Vlan-int200
1400:1::2/64
Vlan-int200
1400:1::1/64
Switch B
Loop 0
4004::4/128
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure RIPng on the switches to ensure the following: (Details not shown.)
Switch S, Switch A, and Switch B can communicate with each other at Layer 3.
Dynamic route update can be implemented among them with RIPng.
3. Enable RIPng NSR on Switch S.
<SwitchS> system-view
[SwitchS] ripng 1
[SwitchS-ripng-1] non-stop-routing
[SwitchS-ripng-1] quit
Verifying the configuration
# Perform an active/standby switchover on Switch S.
[SwitchS] placement reoptimize
Predicted changes to the placement
429
Program Current location New location
--------------------------------------------------------------------- lb 0/0 0/0 lsm 0/0 0/0 slsp 0/0 0/0 rib6 0/0 0/0 routepolicy 0/0 0/0 rib 0/0 0/0 staticroute6 0/0 0/0 staticroute 0/0 0/0 eviisis 0/0 0/0 ospf 0/0 1/0
Continue? [y/n]:y
Re-optimization of the placement start. You will be notified on completion
Re-optimization of the placement complete. Use 'display placement' to view the new placement
# During the switchover period, display RIPng neighbors on Switch A to verify the neighbor relationship between Switch A and Switch S.
[SwitchA] display ripng 1 neighbor
Neighbor Address: FE80::AE45:5CE7:422E:2867
Interface : Vlan-interface100
Version : RIPng version 1 Last update: 00h00m23s
Bad packets: 0 Bad routes : 0
# Display RIPng routes on Switch A to verify if Switch A has a route to the loopback interface on
Switch B.
[SwitchA] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D - Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::AE45:5CE7:422E:2867 on Vlan-interface100
Destination 1400:1::/64,
via FE80::AE45:5CE7:422E:2867, cost 1, tag 0, AOF, 1 secs
Destination 4004::4/128,
via FE80::AE45:5CE7:422E:2867, cost 2, tag 0, AOF, 1 secs
Local route
Destination 2002::2/128,
via ::, cost 0, tag 0, DOF
Destination 1200:1::/64,
via ::, cost 0, tag 0, DOF
# Display RIPng neighbors on Switch B to verify the neighbor relationship between Switch B and
Switch S.
[SwitchB] display ripng 1 neighbor
Neighbor Address: FE80::20C:29FF:FECE:6277
Interface : Vlan-interface200
Version : RIPng version 1 Last update: 00h00m18s
Bad packets: 0 Bad routes : 0
# Display RIPng routes on Switch B to verify if Switch B has a route to the loopback interface on
Switch A.
430
[SwitchB] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect, D - Direct
O - Optimal, F - Flush to RIB
----------------------------------------------------------------
Peer FE80::20C:29FF:FECE:6277 on Vlan-interface200
Destination 2002::2/128,
via FE80::20C:29FF:FECE:6277, cost 2, tag 0, AOF, 24 secs
Destination 1200:1::/64,
via FE80::20C:29FF:FECE:6277, cost 1, tag 0, AOF, 24 secs
Local route
Destination 4004::4/128,
via ::, cost 0, tag 0, DOF
Destination 1400:1::/64,
via ::, cost 0, tag 0, DOF
The output shows the following when an active/standby switchover occurs on Switch S:
•
The neighbor relationships and routing information on Switch A and Switch B have not changed.
•
The traffic from Switch A to Switch B has not been impacted.
Configuring RIPng FRR
Network requirements
As shown in Figure 100 , Switch A, Switch B, and Switch C run RIPng. Configure RIPng FRR so that
when Link A becomes unidirectional, traffic can be switched to Link B immediately.
Figure 100 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
100
Link B
Vlan
-int
101
Link A
Vlan
-int
101
Loop0 Loop0
Switch A
Vlan-int200 Vlan-int200
Switch B
Device
Switch A
Switch A
Switch A
Switch B
Switch B
Switch B
Switch C
Switch C
Interface
VLAN-interface 100
VLAN-interface 200
Loopback 0
VLAN-interface 101
VLAN-interface 200
Loopback 0
VLAN-interface 100
VLAN-interface 101
IP address
1::1/64
2::1/64
10::1/128
3::1/64
2::2/64
20::1/128
1::2/64
3::2/64
431
Configuration procedure
1. Configure IPv6 addresses for interfaces on the switches. (Details not shown.)
2. Configure RIPng on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3. (Details not shown.)
3. Configure RIPng FRR:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ipv6 prefix-list abc index 10 permit 20:: 128
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchA-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 100 backup-nexthop 1::2
[SwitchA-route-policy-frr-10] quit
[SwitchA] ripng 1
[SwitchA-ripng-1] fast-reroute route-policy frr
[SwitchA-ripng-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ipv6 prefix-list abc index 10 permit 10:: 128
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 101 backup-nexthop 3::2
[SwitchB-route-policy-frr-10] quit
[SwitchB] ripng 1
[SwitchB-ripng-1] fast-reroute route-policy frr
[SwitchB-ripng-1] quit
Verifying the configuration
# Display the route 20::1/128 on Switch A to view the backup next hop information.
[SwitchA] display ipv6 routing-table 20::1 128 verbose
Summary count : 1
Destination: 20::1/128
Protocol: RIPng
Process ID: 1
SubProtID: 0x0 Age: 00h17m42s
Cost: 1 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Inactive Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x22000003 LastAs: 0
AttrID: 0xffffffff Neighbor: FE80::34CD:9FF:FE2F:D02
Flags: 0x41 OrigNextHop: FE80::34CD:9FF:FE2F:D02
Label: NULL RealNextHop: FE80::34CD:9FF:FE2F:D02
BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102
Tunnel ID: Invalid Interface: Vlan-interface200
432
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display the route 10::1/128 on Switch B to view the backup next hop information.
[SwitchB] display ipv6 routing-table 10::1 128 verbose
Summary count : 1
Destination: 10::1/128
Protocol: RIPng
Process ID: 1
SubProtID: 0x0 Age: 00h22m34s
Cost: 1 Preference: 100
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Inactive Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x22000001 LastAs: 0
AttrID: 0xffffffff Neighbor: FE80::34CC:E8FF:FE5B:C02
Flags: 0x41 OrigNextHop: FE80::34CC:E8FF:FE5B:C02
Label: NULL RealNextHop: FE80::34CC:E8FF:FE5B:C02
BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
RIPng IPsec profile configuration example
Network requirements
As shown in Figure 101 , configure RIPng on the switches, and configure IPsec profiles on the
switches to authenticate and encrypt protocol packets.
Figure 101 Network diagram
Switch A
Vlan-int100
1::1/64
Vlan-int100
1::2/64
Switch B
Vlan-int200
3::1/64
Vlan-int200
3::2/64
Switch C
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure RIPng basic functions:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ripng 1
[SwitchA-ripng-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ripng 1 enable
433
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ripng 1
[SwitchB-ripng-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ripng 1 enable
[SwitchB-Vlan-interface200] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ripng 1 enable
[SwitchB-Vlan-interface100] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] ripng 1
[SwitchC-ripng-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] ripng 1 enable
[SwitchC-Vlan-interface200] quit
3. Configure RIPng IPsec profiles:
On Switch A:
# Create an IPsec transform set named protrf1 .
[SwitchA] ipsec transform-set protrf1
# Specify the ESP encryption and authentication algorithms.
[SwitchA-ipsec-transform-set-protrf1] esp encryption-algorithm 3des-cbc
[SwitchA-ipsec-transform-set-protrf1] esp authentication-algorithm md5
# Specify the encapsulation mode as transport .
[SwitchA-ipsec-transform-set-protrf1] encapsulation-mode transport
[SwitchA-ipsec-transform-set-protrf1] quit
# Create a manual IPsec profile named profile001 .
[SwitchA] ipsec profile profile001 manual
# Reference IPsec transform set protrf1 .
[SwitchA-ipsec-profile-profile001-manual] transform-set protrf1
# Configure the inbound and outbound SPIs for ESP.
[SwitchA-ipsec-profile-profile001-manual] sa spi inbound esp 256
[SwitchA-ipsec-profile-profile001-manual] sa spi outbound esp 256
# Configure the inbound and outbound SA keys for ESP.
[SwitchA-ipsec-profile-profile001-manual] sa string-key inbound esp simple abc
[SwitchA-ipsec-profile-profile001-manual] sa string-key outbound esp simple abc
[SwitchA-ipsec-profile-profile001-manual] quit
On Switch B:
# Create an IPsec transform set named protrf1 .
[SwitchB] ipsec transform-set protrf1
# Specify the ESP encryption and authentication algorithms.
[SwitchB-ipsec-transform-set-protrf1] esp encryption-algorithm 3des-cbc
[SwitchB-ipsec-transform-set-protrf1] esp authentication-algorithm md5
# Specify the encapsulation mode as transport .
[SwitchB-ipsec-transform-set-protrf1] encapsulation-mode transport
434
[SwitchB-ipsec-transform-set-protrf1] quit
# Create a manual IPsec profile named profile001 .
[SwitchB] ipsec profile profile001 manual
# Reference IPsec transform set protrf1 .
[SwitchB-ipsec-profile-profile001-manual] transform-set protrf1
# Configure the inbound and outbound SPIs for ESP.
[SwitchB-ipsec-profile-profile001-manual] sa spi inbound esp 256
[SwitchB-ipsec-profile-profile001-manual] sa spi outbound esp 256
# Configure the inbound and outbound SA keys for ESP.
[SwitchB-ipsec-profile-profile001-manual] sa string-key inbound esp simple abc
[SwitchB-ipsec-profile-profile001-manual] sa string-key outbound esp simple abc
[SwitchB-ipsec-profile-profile001-manual] quit
On Switch C:
# Create an IPsec transform set named protrf1 .
[SwitchC] ipsec transform-set protrf1
# Specify the ESP encryption and authentication algorithms.
[SwitchC-ipsec-transform-set-protrf1] esp encryption-algorithm 3des-cbc
[SwitchC-ipsec-transform-set-protrf1] esp authentication-algorithm md5
# Specify the encapsulation mode as transport .
[SwitchC-ipsec-transform-set-protrf1] encapsulation-mode transport
[SwitchC-ipsec-transform-set-protrf1] quit
# Create a manual IPsec profile named profile001 .
[SwitchC] ipsec profile profile001 manual
# Reference IPsec transform set protrf1 .
[SwitchC-ipsec-profile-profile001-manual] transform-set protrf1
# Configure the inbound and outbound SPIs for ESP.
[SwitchC-ipsec-profile-profile001-manual] sa spi inbound esp 256
[SwitchC-ipsec-profile-profile001-manual] sa spi outbound esp 256
# Configure the inbound and outbound SA keys for ESP.
[SwitchC-ipsec-profile-profile001-manual] sa string-key inbound esp simple abc
[SwitchC-ipsec-profile-profile001-manual] sa string-key outbound esp simple abc
[SwitchC-ipsec-profile-profile001-manual] quit
4. Apply the IPsec profiles to the RIPng process:
# Configure Switch A.
[SwitchA] ripng 1
[SwitchA-ripng-1] enable ipsec-profile profile001
[SwitchA-ripng-1] quit
# Configure Switch B.
[SwitchB] ripng 1
[SwitchB-ripng-1] enable ipsec-profile profile001
[SwitchB-ripng-1] quit
# Configure Switch C.
[SwitchC] ripng 1
[SwitchC-ripng-1] enable ipsec-profile profile001
[SwitchC-ripng-1] quit
435
Verifying the configuration
# Verify that RIPng packets between Switches A, B and C are protected by IPsec. (Details not shown.)
436
Configuring OSPFv3
This chapter describes how to configure RFC 2740-compliant Open Shortest Path First version 3
(OSPFv3) for an IPv6 network. For more information about OSPFv2, see " Configuring OSPF ."
Overview
OSPFv3 and OSPFv2 have the following in common:
•
32-bit router ID and area ID.
•
Hello, Database Description (DD), Link State Request (LSR), Link State Update (LSU), Link
State Acknowledgment (LSAck).
•
Mechanisms for finding neighbors and establishing adjacencies.
•
Mechanisms for advertising and aging LSAs.
OSPFv3 and OSPFv2 have the following differences:
•
OSPFv3 runs on a per-link basis. OSPFv2 runs on a per-IP-subnet basis.
•
OSPFv3 supports running multiple processes on an interface, but OSPFv2 does not support.
•
OSPFv3 identifies neighbors by router ID. OSPFv2 identifies neighbors by IP address.
OSPFv3 packets
OSPFv3 uses the following packet types:
•
Hello —Periodically sent to find and maintain neighbors, containing timer values, information about the DR, BDR, and known neighbors.
•
DD —Describes the digest of each LSA in the LSDB, exchanged between two routers for data synchronization.
•
LSR —Requests needed LSAs from the neighbor. After exchanging the DD packets, the two routers know which LSAs of the neighbor are missing from their LSDBs. They then send an
LSR packet to each other, requesting the missing LSAs. The LSA packet contains the digest of the missing LSAs.
•
LSU —Transmits the requested LSAs to the neighbor.
•
LSAck —Acknowledges received LSU packets.
OSPFv3 LSA types
OSPFv3 sends routing information in LSAs. The following LSAs are commonly used:
•
Router LSA —Type-1 LSA, originated by all routers. This LSA describes the collected states of the router's interfaces to an area, and is flooded throughout a single area only.
•
Network LSA —Type-2 LSA, originated for broadcast and NBMA networks by the DR. This LSA contains the list of routers connected to the network, and is flooded throughout a single area only.
•
Inter-Area-Prefix LSA —Type-3 LSA, originated by ABRs and flooded throughout the LSA's associated area. Each Inter-Area-Prefix LSA describes a route with IPv6 address prefix to a destination outside the area, yet still inside the AS.
•
Inter-Area-Router LSA —Type-4 LSA, originated by ABRs and flooded throughout the LSA's associated area. Each Inter-Area-Router LSA describes a route to ASBR.
437
•
AS External LSA —Type-5 LSA, originated by ASBRs, and flooded throughout the AS, except stub areas and Not-So-Stubby Areas (NSSAs). Each AS External LSA describes a route to another AS. A default route can be described by an AS External LSA.
•
NSSA LSA —Type-7 LSA, originated by ASBRs in NSSAs and flooded throughout a single
NSSA. NSSA LSAs describe routes to other ASs.
•
Link LSA —Type-8 LSA. A router originates a separate Link LSA for each attached link. Link
LSAs have link-local flooding scope. Each Link LSA describes the IPv6 address prefix of the link and Link-local address of the router.
•
Intra-Area-Prefix LSA —Type-9 LSA. Each Intra-Area-Prefix LSA contains IPv6 prefix information on a router, stub area, or transit area information, and has area flooding scope. It was introduced because Router LSAs and Network LSAs contain no address information.
•
Grace LSA —Type-11 LSA, generated by a GR restarter at reboot and transmitted on the local link. The GR restarter describes the cause and interval of the reboot in the Grace LSA to notify its neighbors that it performs a GR operation.
Protocols and standards
•
RFC 5340, OSPF for IPv6
•
RFC 2328, OSPF Version 2
•
RFC 3101, OSPF Not-So-Stubby Area (NSSA) Option
•
RFC 5187, OSPFv3 Graceful Restart
OSPFv3 configuration task list
Tasks at a glance
(Optional.) Configuring OSPFv3 area parameters :
•
•
•
Configuring an OSPFv3 virtual link
(Optional.) Configuring OSPFv3 network types :
•
Configuring the OSPFv3 network type for an interface
•
Configuring an NBMA or P2MP neighbor
(Optional.) Configuring OSPFv3 route control :
•
Configuring OSPFv3 route summarization
•
Configuring OSPFv3 received route filtering
•
Configuring Inter-Area-Prefix LSA filtering
•
Setting an OSPFv3 cost for an interface
•
Setting the maximum number of OSPFv3 ECMP routes
•
Setting a preference for OSPFv3
•
Configuring OSPFv3 route redistribution
438
Tasks at a glance
(Optional.) Tuning and optimizing OSPFv3 networks :
•
•
Setting LSA transmission delay
•
Setting SPF calculation interval
•
Setting the LSA generation interval
•
Setting a DR priority for an interface
•
Ignoring MTU check for DD packets
•
Disabling interfaces from receiving and sending OSPFv3 packets
•
Enabling logging for neighbor state changes
•
Configuring OSPFv3 network management
•
•
•
Configuring prefix suppression
•
Configuring OSPFv3 authentication
(Optional.) Configuring OSPFv3 GR :
•
•
•
(Optional.) Configuring OSPFv3 NSR
(Optional.) Configuring BFD for OSPFv3
(Optional.) Configuring OSPFv3 FRR
(Optional.) Applying an IPsec profile
Enabling OSPFv3
Before you enable OSPFv3, configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
To enable an OSPFv3 process on a router:
•
Enable the OSPFv3 process globally.
•
Assign the OSPFv3 process a router ID.
•
Enable the OSPFv3 process on related interfaces.
The router ID uniquely identifies the router within an AS. If a router runs multiple OSPFv3 processes, you must specify a unique router ID for each process.
An OSPFv3 process ID has only local significance. Process 1 on a router can exchange packets with process 2 on another router.
To enable OSPFv3:
Step
1. Enter system view.
2. Enable an OSPFv3 process and enter its view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
By default, no OSPFv3 processes are enabled.
3. Specify a router ID. router-id router-id
By default, no router ID is configured.
439
Step
4. Enter interface view.
5. Enable an OSPFv3 process on the interface.
Command interface interface-type interface-number
ospfv3 process-id area area-id
[ instance instance-id ]
Remarks
N/A
By default, no OSPFv3 processes are enabled on an interface.
Configuring OSPFv3 area parameters
OSPFv3 has the same stub area, NSSA area, and virtual link features as OSPFv2.
After you split an OSPFv3 AS into multiple areas, the LSA number is reduced and OSPFv3 applications are extended. To further reduce the size of routing tables and the number of LSAs, configure the non-backbone areas at an AS edge as stub areas.
A stub area cannot import external routes, but an NSSA area can import external routes into the
OSPFv3 routing domain while retaining other stub area characteristics.
Non-backbone areas exchange routing information through the backbone area, so the backbone and non-backbone areas (including the backbone itself) must be fully meshed. If no connectivity can be achieved, configure virtual links.
Configuration prerequisites
Before you configure OSPFv3 area parameters, enable OSPFv3.
Configuring a stub area
All the routers attached to a stub area must be configured with the stub command. The no-summary keyword is only available on the ABR of the stub area.
If you use the stub command with the no-summary keyword on an ABR, the ABR advertises a default route in an Inter-Area-Prefix LSA into the stub area. No AS External LSA, Inter-Area-Prefix
LSA, or other Inter-Area-Router LSA is advertised in the area. The stub area of this kind is called a totally stub area.
To configure an OSPFv3 stub area:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
N/A
3. Enter OSPFv3 area view.
4. Configure the area as a stub area.
area area-id N/A stub
[ default-route-advertise-always
| no-summary ] *
By default, no area is configured as a stub area.
5. (Optional.) Set a cost for the default route advertised to the stub area. default-cost cost value The default setting is 1.
440
Configuring an NSSA area
To configure an NSSA area, configure the nssa command on all the routers attached to the area.
To configure a totally NSSA area, configure the nssa no-summary command on the ABR. The ABR of a totally NSSA area does not advertise inter-area routes into the area.
To configure an NSSA area:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] * area area-id
N/A
3.
4.
Enter OSPFv3 area view.
Configure the area as an
NSSA area.
5. (Optional.) Set a cost for the default route advertised to the NSSA area. default-cost cost-value
N/A nssa [ default-route-advertise
[ cost cost-value | nssa-only |
route-policy route-policy-name |
tag tag | type type ] * | no-import-route | no-summary |
[ translate-always | translate-never ] | suppress-fa | translator-stability-interval value ] *
By default, no area is configured as an NSSA area.
The default setting is 1.
This command takes effect only on the ABR/ASBR of an NSSA or totally NSSA area.
Configuring an OSPFv3 virtual link
You can configure a virtual link to maintain connectivity between a non-backbone area and the backbone, or in the backbone itself.
IMPORTANT:
•
Both ends of a virtual link are ABRs that must be configured with the vlink-peer command.
•
Do not configure virtual links in the areas of a GR-capable process.
To configure a virtual link:
Step
1. Enter system view.
2. Enter OSPFv3 view.
3. Enter OSPFv3 area view.
4. Configure a virtual link.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
area area-id
vlink-peer router-id [ dead seconds |
hello seconds | instance instance-id |
ipsec-profile profile-name | keychain keychain-name | retransmit seconds |
trans-delay seconds ] *
Remarks
N/A
N/A
N/A
By default, no virtual links exist.
441
Configuring OSPFv3 network types
By the link layer protocol, OSPFv3 classifies networks into different types, including broadcast,
NBMA, P2MP, and P2P. By default, OSPFv3 considers the network type as broadcast.
Follow these guidelines when you change the network type of an OSPFv3 interface:
•
An NBMA network must be fully connected. Any two routers in the network must be directly reachable to each other through a virtual circuit. If no such direct link is available, you must change the network type through a command.
•
If direct connections are not available between some routers in an NBMA network, the type of interfaces associated must be configured as P2MP, or as P2P for interfaces with only one neighbor.
Configuration prerequisites
Before you configure OSPFv3 network types, enable OSPFv3.
Configuring the OSPFv3 network type for an interface
Step
1. Enter system view.
2. Enter interface view.
3. Configure a network type for the OSPFv3 interface.
Command system-view interface interface-type interface-number ospfv3 network-type
{ broadcast | nbma | p2mp
[ unicast ] | p2p } [ instance instance-id ]
Remarks
N/A
N/A
By default, the network type of an
OSPFv3 interface is broadcast.
Configuring an NBMA or P2MP neighbor
For NBMA and P2MP interfaces (only when in unicast mode), you must specify the link-local IP addresses of their neighbors because these interfaces cannot find neighbors through broadcasting hello packets. For NBMA interfaces, you can also specify DR priorities for neighbors.
To configure an NBMA or P2MP (unicast) neighbor and its DR priority:
Step
1. Enter system view.
Remarks
N/A
2. Enter interface view.
3. Specify an NBMA or P2MP
(unicast) neighbor and its DR priority.
Command system-view interface interface-type interface-number ospfv3 peer ipv6-address [ cost cost value | dr-priority priority ]
[ instance instance-id ]
N/A
By default, no link-local address is specified for the neighbor interface.
442
Configuring OSPFv3 route control
Configuration prerequisites
Before you configure OSPFv3 route control, perform the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
•
Enable OSPFv3.
Configuring OSPFv3 route summarization
Route summarization enables an ABR or ASBR to summarize contiguous networks into a single network and advertise it to other areas.
Configuring route summarization on an ABR
If contiguous network segments exist in an area, you can summarize them into one network segment on the ABR. The ABR will advertise only the summary route. Any LSA on the specified network segment will not be advertised, reducing the LSDB size in other areas.
To configure route summarization on an ABR:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enter OSPFv3 area view.
area area-id N/A
4. Configure route summarization on the
ABR. abr-summary ipv6-address prefix-length [ not-advertise ] [ cost cost value ]
By default, route summarization is not configured on an ABR.
Configuring route summarization on an ASBR
Perform this task to enable an ASBR to summarize external routes within the specified address range into a single route.
An ASBR can summarize routes in the following LSAs:
•
Type-5 LSAs.
•
Type-7 LSAs in an NSSA area.
•
Type-5 LSAs translated by the ASBR (also an ABR) from Type-7 LSAs in an NSSA area.
If the ASBR (ABR) is not a translator, it cannot summarize routes in Type-5 LSAs translated from Type-7 LSAs.
To configure route summarization on an ASBR:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
443
Step
3. Configure route summarization on an
ASBR.
Command asbr-summary ipv6-address prefix-length [ cost cost-value | not-advertise | nssa-only | tag tag ] *
Remarks
By default, route summarization is not configured on an ASBR.
Configuring OSPFv3 received route filtering
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
N/A
3. Configure OSPFv3 to filter routes calculated using received LSAs. filter-policy { ipv6 acl-number [ gateway prefix-list-name ] | prefix-list prefix-list-name [ gateway prefix-list-name ] | gateway prefix-list-name | route-policy route-policy-name } import
By default, OSPFv3 accepts all routes calculated using received
LSAs.
This command can only filter routes computed by OSPFv3.
Only routes not filtered out can be added into the local routing table.
Configuring Inter-Area-Prefix LSA filtering
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Enter OSPFv3 area view. area area-id
4. Configure OSPFv3 to filter Inter-Area-Prefix
LSAs. filter { ipv6 acl-number | prefix-list prefix-list-name | route-policy route-policy-name } { export | import }
Remarks
N/A
N/A
N/A
By default, OSPFv3 accepts all
Inter-Area-Prefix LSAs.
This command takes effect only on ABRs.
Setting an OSPFv3 cost for an interface
You can set an OSPFv3 cost for an interface with one of the following methods:
•
Set the cost value in interface view.
•
Set a bandwidth reference value for the interface, and OSPFv3 computes the cost automatically based on the bandwidth reference value by using the following formula:
Interface OSPFv3 cost = Bandwidth reference value (100 Mbps) / Interface bandwidth (Mbps)
If the calculated cost is greater than 65535, the value of 65535 is used.
If the calculated cost is smaller than 1, the value of 1 is used.
•
If no cost is set for an interface, OSPFv3 automatically computes the cost for the interface.
To set an OSPFv3 cost for an interface:
Step
1. Enter system view.
Command system-view
Remarks
N/A
444
Step
2. Enter interface view.
Command interface interface-type interface-number
3. Set an OSPFv3 cost for the interface.
ospfv3 cost cost value
[ instance instance-id ]
Remarks
N/A
By default, the OSPFv3 cost is 1 for a VLAN interface, is 0 for a loopback interface. The OSPFv3 cost is automatically computed according to the interface bandwidth for other interfaces.
To set a bandwidth reference value:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Set a bandwidth reference value.
bandwidth-reference value
Remarks
N/A
N/A
The default setting is 100 Mbps.
Setting the maximum number of OSPFv3 ECMP routes
Perform this task to implement load sharing over ECMP routes.
To set the maximum number of ECMP routes:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Set the maximum number of
ECMP routes. maximum load-balancing number
By default, the maximum number of ECMP routes equals the maximum number of ECMP routes supported by the system.
Setting a preference for OSPFv3
A router can run multiple routing protocols. The system assigns a priority for each protocol. When these routing protocols find the same route, the route found by the protocol with the highest priority is selected.
To set a preference for OSPFv3:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
445
Step
3. Set a preference for
OSPFv3.
Command preference [ ase ] { preference | route-policy route-policy-name } *
Remarks
By default, the preference of
OSPFv3 internal routes is 10, and the priority of OSPFv3 external routes is 150.
Configuring OSPFv3 route redistribution
Because OSPFv3 is a link state routing protocol, it cannot directly filter LSAs to be advertised.
OSPFv3 filters only redistributed routes. Only routes that are not filtered out can be advertised in
LSAs.
Executing the import-route or default-route-advertise command on a router makes it become an
ASBR.
IMPORTANT:
The import-route bgp4+ command redistributes only EBGP routes. Because the import-route bgp4+ allow-ibgp command redistributes both EBGP and IBGP routes, and might cause routing loops, use it with caution.
Redistributing routes from another routing protocol
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
N/A
3. Configure OSPFv3 to redistribute routes from other routing protocols. import-route protocol [ as-number ]
[ process-id | all-processes | allow-ibgp ] [ allow-direct | cost cost-value | nssa-only | route-policy route-policy-name | tag tag | type type ]
*
By default, route redistribution is disabled.
4. (Optional.) Configure
OSPFv3 to filter redistributed routes. filter-policy { ipv6 acl-number | prefix-list prefix-list-name } export
[ protocol [ process-id ] ]
By default, OSPFv3 accepts all redistributed routes.
This command filters only routes redistributed with the import-route command. If the import-route command is not configured, executing this command does not take effect.
Redistributing a default route
The import-route command cannot redistribute a default external route. Perform this task to redistribute a default route.
To redistribute a default route:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
446
Step
3. Redistribute a default route.
Command default-route-advertise [ [ always | permit-calculate-other ] | cost cost-value | route-policy route-policy-name | tag tag | type type ] *
Remarks
By default, no default route is redistributed.
Setting tags for redistributed routes
Perform this task to set tags for redistributed routes to identify information about protocols. For example, when redistributing IPv6 BGP routes, OSPFv3 uses tags to identify AS IDs.
To set a tag for redistributed routes:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Set a tag for redistributed routes.
default tag tag
N/A
By default, the tag of redistributed routes is 1.
Tuning and optimizing OSPFv3 networks
This section describes configurations of OSPFv3 timers, interface DR priority, and the logging of neighbor state changes.
Configuration prerequisites
Before you tune and optimize OSPFv3 networks, perform the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
•
Enable OSPFv3.
Setting OSPFv3 timers
Step
1. Enter system view.
2. Enter interface view.
3. Set the hello interval.
4. Set the dead interval.
5. Set the poll interval.
Command system-view
interface interface-type interface-number ospfv3 timer hello seconds
[ instance instance-id ]
Remarks
N/A
N/A ospfv3 timer dead seconds
[ instance instance-id ] ospfv3 timer poll
[ instance seconds instance-id ]
By default, the hello interval on P2P and broadcast interfaces is 10 seconds.
By default, the dead interval on P2P and broadcast interfaces is 40 seconds.
The dead interval set on neighboring interfaces cannot be too short.
Otherwise, a neighbor is easily considered down.
By default, the poll interval is 120 seconds.
447
Step Command
6. Set the LSA retransmission interval. ospfv3 timer retransmit interval [ instance instance-id ]
Remarks
The default setting is 5 seconds.
The LSA retransmission interval cannot be too short. Otherwise, unnecessary retransmissions will occur.
Setting LSA transmission delay
Each LSA in the LSDB has an age that is incremented by 1 every second, but the age does not change during transmission. Therefore, it is necessary to add a transmission delay into the age time, especially for low-speed links.
To set the LSA transmission delay on an interface:
Step
1. Enter system view.
2. Enter interface view.
3. Set the LSA transmission delay.
Command system-view interface interface-type interface-number ospfv3 trans-delay seconds
[ instance instance-id ]
Remarks
N/A
N/A
By default, the LSA transmission delay is 1 second.
Setting SPF calculation interval
LSDB changes result in SPF calculations. When the topology changes frequently, a large amount of network and router resources are occupied by SPF calculation. You can adjust the SPF calculation interval to reduce the impact.
For a stable network, the minimum interval is used. If network changes become frequent, the SPF calculation interval is incremented by the incremental interval × 2 n-2
for each calculation until the maximum interval is reached. The value n is the number of calculation times.
To set SPF calculation interval:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Set the SPF calculation interval. spf-schedule-interval maximum-interval [ minimum-interval
[ incremental-interval ] ]
By default:
•
The maximum interval is 5 seconds.
•
The minimum interval is 50 milliseconds.
•
The incremental interval is
200 milliseconds.
Setting the LSA generation interval
You can adjust the LSA generation interval to protect network resources and routers from being over consumed by frequent network changes.
448
For a stable network, the minimum interval is used. If network changes become frequent, the LSA generation interval is incremented by the incremental interval × 2 n-2
for each generation until the maximum interval is reached. The value n is the number of generation times.
To set the LSA generation interval:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Set the LSA generation interval. lsa-generation-interval maximum-interval [ minimum-interval
[ incremental-interval ] ]
By default, the maximum interval is 5 seconds, the minimum interval is 0 milliseconds, and the incremental interval is 0 milliseconds.
Setting a DR priority for an interface
The router priority is used for DR election. Interfaces having the priority 0 cannot become a DR or
BDR.
To configure a DR priority for an interface:
Step
1. Enter system view.
2. Enter interface view.
3. Set a router priority.
Command system-view
Remarks
N/A
interface interface-type interface-number N/A ospfv3 dr-priority priority [ instance instance-id ]
The default router priority is 1.
Ignoring MTU check for DD packets
When LSAs are few in DD packets, it is unnecessary to check the MTU in DD packets to improve efficiency.
To ignore MTU check for DD packets:
Step
1. Enter system view.
2. Enter interface view.
Command system-view
interface interface-type interface-number
Remarks
N/A
N/A
3. Ignore MTU check for DD packets. ospfv3 mtu-ignore [ instance instance-id ]
By default, OSPFv3 does not ignore MTU check for DD packets.
Disabling interfaces from receiving and sending OSPFv3 packets
After an OSPFv3 interface is set to silent , direct routes of the interface can still be advertised in
Intra-Area-Prefix LSAs through other interfaces, but other OSPFv3 packets cannot be advertised.
No neighboring relationship can be established on the interface. This feature can enhance the adaptability of OSPFv3 networking.
449
To disable interfaces from receiving and sending OSPFv3 packets:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Disable interfaces from receiving and sending
OSPFv3 packets. silent-interface { interface-type interface-number | all }
By default, the interfaces are able to receive and send OSPFv3 packets.
This command disables only the interfaces associated with the current process. However, multiple OSPFv3 processes can disable the same interface from receiving and sending OSPFv3 packets.
Enabling logging for neighbor state changes
With this feature enabled, the router delivers logs about neighbor state changes to its information center. The information center processes logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see Network
Management and Monitoring Configuration Guide .
To enable logging for neighbor state changes:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable logging for neighbor state changes. log-peer-change By default, this feature is enabled.
Configuring OSPFv3 network management
This task involves the following configurations:
•
Bind an OSPFv3 process to MIB so that you can use network management software to manage the specified OSPFv3 process.
•
Enable SNMP notifications for OSPFv3 to report important events.
•
Set the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval.
SNMP notifications are sent to the SNMP module, which outputs SNMP notifications according to the configured output rules. For more information about SNMP notifications, see Network Management and Monitoring Configuration Guide .
The standard OSPFv3 MIB provides only single-instance MIB objects. To identify multiple OSPFv3 processes in the standard OSPFv3 MIB, you must assign a unique context name to each OSPFv3 process.
Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you must specify a community name as a context name for protocol identification.
450
To configure OSPFv3 network management:
Step
1. Enter system view.
2. Bind MIB to an OSPFv3 process.
3. Enable SNMP notifications for OSPFv3.
4. Enter OSPFv3 view.
Command system-view
ospfv3 mib-binding process-id
Remarks
N/A
By default, MIB is bound to the process with the smallest process ID. snmp-agent trap enable ospfv3
[ grrestarter-status-change | grhelper-status-change | if-state-change | if-cfg-error | if-bad-pkt | neighbor-state-change | nssatranslator-status-change | virtif-bad-pkt | virtif-cfg-error | virtif-state-change | virtgrhelper-status-change | virtneighbor-state-change ]* ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
By default, SNMP notifications for OSPFv3 are enabled.
N/A snmp context-name context-name
By default, no SNMP context is configured for the OSPFv3 process.
5. Configure an SNMP context for the OSPFv3 process.
6. (Optional.) Set the SNMP notification output interval and the maximum number of SNMP notifications that can be output at each interval. snmp trap rate-limit interval
trap-interval count trap-number
By default, OSPFv3 outputs a maximum of seven SNMP notifications within 10 seconds.
Setting the LSU transmit rate
Sending large numbers of LSU packets affects router performance and consumes a large amount of network bandwidth. You can configure the router to send LSU packets at an interval and to limit the maximum number of LSU packets sent out of an OSPFv3 interface at each interval.
To set the LSU transmit rate:
Step Command
1. Enter system view. system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Set the LSU transmit rate.
Remarks
N/A
N/A transmit-pacing interval interval count count
By default, an OSPFv3 interface sends a maximum of three LSU packets every 20 milliseconds.
Configuring stub routers
A stub router is used for traffic control. It reports its status as a stub router to neighboring OSPFv3 routers. The neighboring routers can have a route to the stub router, but they do not use the stub router to forward data.
Use either of the following methods to configure a router as a stub router:
451
•
Clear the R-bit of the Option field in Type-1 LSAs. When the R-bit is clear, the OSPFv3 router can participate in OSPFv3 topology distribution without forwarding traffic.
•
Use the OSPFv3 max-metric router LSA feature. This feature enables OSPFv3 to advertise its locally generated Type-1 LSAs with a maximum cost of 65535. Neighbors do not send packets to the stub router as long as they have a route with a smaller cost.
To configure a router as a stub router:
Step
1. Enter system view.
2. Enter OSPFv3 view.
3. Configure the router as a stub router.
Command system-view
Remarks
N/A ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
•
Method 1: stub-router r-bit [ include-stub | on-startup { seconds | wait-for-bgp [ seconds ] } ] *
•
Method 2: stub-router max-metric
[ external-lsa [ max-metric-value ]
| summary-lsa
[ max-metric-value ] | include-stub | on-startup
{ seconds | wait-for-bgp
[ seconds ] } ] *
N/A
By default, the router is not configured as a stub router.
A stub router is not related to a stub area.
Configuring prefix suppression
By default, an OSPFv3 interface advertises all of its prefixes in LSAs. To speed up OSPFv3 convergence, you can suppress interfaces from advertising all of their prefixes. This feature helps improve network security by preventing IP routing to the suppressed networks.
When prefix suppression is enabled:
•
OSPFv3 does not advertise the prefixes of suppressed interfaces in Type-8 LSAs.
•
On broadcast and NBMA networks, the DR does not advertise the prefixes of suppressed interfaces in Type-9 LSAs that reference Type-2 LSAs.
•
On P2P and P2MP networks, OSPFv3 does not advertise the prefixes of suppressed interfaces in Type-9 LSAs that reference Type-1 LSAs.
IMPORTANT:
As a best practice, configure prefix suppression on all OSPFv3 routers if you want to use prefix suppression.
Configuring prefix suppression for an OSPFv3 process
Enabling prefix suppression for an OSPFv3 process does not suppress the prefixes of loopback interfaces and passive interfaces.
To configure prefix suppression for an OSPFv3 process:
Step Command
1. Enter system view. system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
452
Step
3. Enable prefix suppression for the
OSPFv3 process.
Command prefix-suppression
Configuring prefix suppression for an interface
Step Command
1. Enter system view. system-view
2. Enter interface view.
3. Enable prefix suppression for the interface. interface interface-type interface-number ospfv3 prefix-suppression [ disable ]
[ instance instance-id ]
Remarks
By default, prefix suppression is disabled for an OSPFv3 process.
Remarks
N/A
N/A
By default, prefix suppression is disabled for an interface.
Configuring OSPFv3 authentication
OSPFv3 uses keychain authentication to prevent routing information from being leaked and routers from being attacked.
OSPFv3 adds the Authentication Trailer option into outgoing packets, and uses the authentication information in the option to authenticate incoming packets. Only packets that pass the authentication can be received. If a packet fails the authentication, the OSPFv3 neighbor relationship cannot be established.
The authentication mode specified for an OSPFv3 interface has a higher priority than the mode specified for an OSPFv3 area.
Configuring OSPFv3 area authentication
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Enter OSPFv3 area view. area area-id
4. Specify an authentication mode for the area. authentication-mode keychain keychain-name
Remarks
N/A
N/A
N/A
By default, no authentication is performed for the area.
For more information about keychains, see Security
Configuration Guide .
Configuring OSPFv3 interface authentication
Step
1. Enter system view.
2. Enter interface view.
Command system-view
interface interface-type interface-number
3. Specify an authentication mode for the interface. ospfv3 authentication-mode keychain keychain-name [ instance instance-id ]
Remarks
N/A
N/A
By default, no authentication is performed for the interface.
For more information about keychains, see Security
Configuration Guide .
453
Configuring OSPFv3 GR
GR ensures forwarding continuity when a routing protocol restarts or an active/standby switchover occurs.
Two routers are required to complete a GR process. The following are router roles in a GR process:
•
GR restarter —Graceful restarting router. It must be Graceful Restart capable.
•
GR helper —The neighbor of the GR restarter. It helps the GR restarter to complete the GR process.
To prevent service interruption after a master/backup switchover, a GR restarter running OSPFv3 must perform the following tasks:
•
Keep the GR restarter forwarding entries stable during reboot.
•
Establish all adjacencies and obtain complete topology information after reboot.
After the active/standby switchover, the GR restarter sends a Grace LSA to tell its neighbors that it performs a GR. Upon receiving the Grace LSA, the neighbors with the GR helper capability enter the helper mode (and are called GR helpers). Then, the GR restarter retrieves its adjacencies and LSDB with the help of the GR helpers.
Configuring GR restarter
You can configure the GR restarter capability on a GR restarter.
IMPORTANT:
You cannot enable OSPFv3 NSR on a device that acts as GR restarter.
To configure GR restarter:
Step
1. Enter system view.
2. Enter OSPFv3 view.
3. Enable the GR capability.
4. (Optional.) Set the GR interval.
Command system-view
Remarks
N/A ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
N/A graceful-restart enable [ global
| planned-only ] *
By default, OSPFv3 GR restarter capability is disabled.
graceful-restart interval interval
By default, the GR interval is 120 seconds.
Configuring GR helper
You can configure the GR helper capability on a GR helper.
To configure GR helper:
Step
1. Enter system view.
2. Enter OSPFv3 view.
3. Enable the GR helper capability.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] * graceful-restart helper enable
[ planned-only ]
Remarks
N/A
N/A
By default, the GR helper capability is enabled.
454
Step
4. Enable strict LSA checking.
Command graceful-restart helper strict-lsa-checking
Remarks
By default, strict LSA checking is disabled.
Triggering OSPFv3 GR
OSPFv3 GR is triggered by an active/standby switchover or when the following command is executed.
To trigger OSPFv3 GR, perform the following command in user view:
Task
Trigger OSPFv3 GR.
Command reset ospfv3 [ process id ] process graceful-restart
Configuring OSPFv3 NSR
Nonstop routing (NSR) backs up OSPFv3 link state information from the active process to the standby process. After an active/standby switchover, NSR can complete link state recovery and route regeneration without tearing down adjacencies or impacting forwarding services.
NSR does not require the cooperation of neighboring devices to recover routing information, and it is typically used more often than GR.
IMPORTANT:
A device that has OSPFv3 NSR enabled cannot act as GR restarter.
To enable OSPFv3 NSR:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
Remarks
N/A
N/A
3. Enable OSPFv3 NSR. non-stop-routing
By default, OSPFv3 NSR is disabled.
This command takes effect only for the current process. As a best practice, enable OSPFv3 NSR for each process if multiple OSPFv3 processes exist.
Configuring BFD for OSPFv3
Bidirectional forwarding detection (BFD) provides a mechanism to quickly detect the connectivity of links between OSPFv3 neighbors, improving the convergence speed of OSPFv3. For more information about BFD, see High Availability Configuration Guide .
After discovering neighbors by sending hello packets, OSPFv3 notifies BFD of the neighbor addresses, and BFD uses these addresses to establish sessions. Before a BFD session is established, it is in the down state. In this state, BFD control packets are sent at an interval of no less than 1 second to reduce BFD control packet traffic. After the BFD session is established, BFD control packets are sent at the negotiated interval, thereby implementing fast fault detection.
455
To configure BFD for OSPFv3, you need to configure OSPFv3 first.
To configure BFD for OSPFv3:
Step
1. Enter system view.
2. Enter OSPFv3 view.
Command system-view ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3.
4.
Specify a router ID.
Quit the OSPFv3 view. router-id router-id quit
5. Enter interface view. interface interface-type interface-number
6. Enable an OSPFv3 process on the interface.
ospfv3 process-id area area-id
[ instance instance-id ]
7. Enable BFD on the interface. ospfv3 bfd enable [ instance instance-id ]
Remarks
N/A
N/A
N/A
N/A
N/A
N/A
By default, BFD is disabled on the
OSPFv3 interface.
Configuring OSPFv3 FRR
A primary link failure can cause packet loss and even a routing loop until OSPFv3 completes routing convergence based on the new network topology. OSPFv3 FRR enables fast rerouting to minimize the failover time.
Figure 102 Network diagram for OSPFv3 FRR
Backup nexthop: Router C
Router A Router B Nexthop: Router D Router E
As shown in Figure 102 , configure FRR on Router B. OSPFv3 FRR automatically calculates a
backup next hop or specifies a backup next hop by using a routing policy. When the primary link fails,
OSPFv3 directs packets to the backup next hop. At the same time, OSPFv3 calculates the shortest path based on the new network topology. It forwards packets over the path after network convergence.
You can configure OSPFv3 FRR to calculate a backup next hop by using the loop free alternate (LFA) algorithm, or specify a backup next hop by using a routing policy.
Configuration prerequisites
Before you configure OSPFv3 FRR, perform the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable OSPFv3.
•
Make sure the backup next hop is reachable.
456
Configuration guidelines
Do not use the fast-reroute lfa command together with the vlink-peer command.
Configuration procedure
Configuring OSPFv3 FRR to calculate a backup next hop using the LFA algorithm
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type
interface-number
Remarks
N/A
N/A
3. (Optional.) Disable LFA on an interface. ospfv3 fast-reroute lfa-backup exclude
By default, the interface on which LFA is enabled can be selected as a backup interface.
N/A 4. Return to system view.
5. Enter OSPFv3 view. quit ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
N/A
6. Enable OSPFv3 FRR to calculate a backup next hop by using the LFA algorithm. fast-reroute lfa [ abr-only ]
By default, OSPFv3 FRR is disabled.
If abr-only is specified, the route to the
ABR is selected as the backup path.
Configuring OSPFv3 FRR to specify a backup next hop using a routing policy
Before you perform this task, use the apply ipv6 fast-reroute backup-interface command to specify a backup next hop in the routing policy to be used. For more information about the apply ipv6 fast-reroute backup-interface
command and routing policy configuration, see " Configuring routing policies ."
To configure OSPFv3 FRR to specify a backup next hop using a routing policy:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type
interface-number
Remarks
N/A
N/A
3. (Optional.) Disable LFA on an interface. ospfv3 fast-reroute lfa-backup exclude
By default, the interface is enabled with LFA and it can be selected as a backup interface.
4. Return to system view. quit N/A
5. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
6. Enable OSPFv3 FRR to specify a backup next hop by using a routing policy. fast-reroute route-policy route-policy-name
N/A
By default, OSPFv3 FRR is disabled.
Configuring BFD for OSPFv3 FRR
By default, OSPFv3 FRR does not use BFD to detect primary link failures. To speed up OSPFv3 convergence, enable BFD for OSPFv3 FRR to detect primary link failures.
To configure BFD control packet mode for OSPFv3 FRR:
457
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type
interface-number
3. Enable BFD control packet mode for OSPFv3
FRR. ospfv3 primary-path-detect bfd ctrl [ instance instance-id ]
To configure BFD echo packet mode for OSPFv3 FRR:
Step
1. Enter system view.
Command system-view
2. Configure the source
IPv6 address of BFD echo packets. bfd echo-source-ipv6 ipv6-address
Remarks
N/A
N/A
By default, BFD control packet mode for OSPFv3 FRR is disabled.
Remarks
N/A
By default, the source IPv6 address of BFD echo packets is not configured.
The source IPv6 address cannot be on the same network segment as any local interface's IP address.
For more information about this command, see High Availability
Command Reference .
3. Enter interface view.
4. Enable BFD echo packet mode for OSPFv3 FRR. interface interface-type
interface-number ospfv3 primary-path-detect bfd echo [ instance instance-id ]
N/A
By default, BFD echo packet mode for OSPFv3 FRR is disabled.
Applying an IPsec profile
To protect routing information and prevent attacks, OSPFv3 can authenticate protocol packets by using an IPsec profile. For more information about IPsec profiles, see Security Configuration Guide .
Outbound OSPFv3 packets carry the Security Parameter Index (SPI) defined in the relevant IPsec profile. A device compares the SPI carried in a received packet with the configured IPsec profile. If they match, the device accepts the packet. Otherwise, the device discards the packet and will not establish a neighbor relationship with the sending device.
You can configure an IPsec profile for an area, an interface, a virtual link, or a sham link.
•
To implement area-based IPsec protection, configure the same IPsec profile on the routers in the target area.
•
To implement interface-based IPsec protection, configure the same IPsec profile on the interfaces between two neighboring routers.
•
To implement virtual link-based IPsec protection, configure the same IPsec profile on the two routers connected over the virtual link.
•
To implement sham link-based IPsec protection, configure the same IPsec profile on the two routers connected over the sham link. For more information about sham links, see MPLS
Configuration Guide .
•
If an interface and its area each have an IPsec profile configured, the interface uses its own
IPsec profile.
•
If a virtual link and area 0 each have an IPsec profile configured, the virtual link uses its own
IPsec profile.
458
•
If a sham link and its area have an IPsec profile configured, the sham link uses its own IPsec profile.
To apply an IPsec profile to an area:
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Enter OSPFv3 area view. area area-id
4. Apply an IPsec profile to the area. enable ipsec-profile profile-name
To apply an IPsec profile to an interface:
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type interface-number
3. Apply an IPsec profile to the interface. ospfv3 ipsec-profile profile-name
To apply an IPsec profile to a virtual link:
N/A
N/A
By default, no IPsec profile is applied.
Remarks
N/A
N/A
By default, no IPsec profile is applied.
Remarks
N/A
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Enter OSPFv3 area view. area area-id
4. Apply an IPsec profile to a virtual link.
vlink-peer router-id [ dead seconds |
hello seconds | instance instance-id |
retransmit seconds | trans-delay seconds | ipsec-profile profile-name ] *
To apply an IPsec profile to a sham link:
Step
1. Enter system view.
Command system-view
2. Enter OSPFv3 view. ospfv3 [ process-id | vpn-instance vpn-instance-name ] *
3. Enter OSPFv3 area view. area area-id
4. Apply an IPsec profile to a sham link.
sham-link source-ipv6-address destination-ipv6-address [ cost cost-value | dead dead-interval | hello hello-interval | instance instance-id |
ipsec-profile profile-name | retransmit retrans-interval | trans-delay delay ] *
N/A
N/A
By default, no IPsec profile is applied.
Remarks
N/A
N/A
N/A
By default, no IPsec profile is applied.
459
Displaying and maintaining OSPFv3
Execute display commands in any view and reset commands in user view.
Task
Display information about the routes to OSPFv3 ABR and ASBR.
Command display ospfv3 [ process-id ] abr-asbr
Display summary route information on the OSPFv3 ABR. display ospfv3 [ process-id ] [ area area-id ] abr-summary
[ ipv6-address prefix-length ] [ verbose ]
Display summary route information on the OSPFv3 ASBR. display ospfv3 [ process-id ] asbr-summary [ ipv6-address prefix-length ] [ verbose ]
Display OSPFv3 log information. display ospfv3 [ process-id ] event-log {
Display OSPFv3 process information. display ospfv3 [ process-id ] [ verbose ] lsa-flush | peer | spf }
Display OSPFv3 GR information.
Display OSPFv3 NSR information.
Display OSPFv3 interface information.
Display OSPFv3 LSDB information. display ospfv3 [ process-id ] graceful-restart [ verbose ] display ospfv3 [ process-id ] non-stop-routing display ospfv3 [ process-id ] interface [ interface-type interface-number | verbose ] display ospfv3 [ process-id ] lsdb [ { external | grace | inter-prefix
| inter-router | intra-prefix | link | network | nssa | router | unknown [ type ] } [ link-state-id ] [ originate-router router-id | self-originate ] | statistics | total | verbose ]
Display OSPFv3 next hop information.
Display OSPFv3 neighbor information.
Display OSPFv3 request list information. display ospfv3 [ process-id ] nexthop display ospfv3 [ process-id ] [ area area-id ] peer [ [ interface-type interface-number ] [ verbose ] | peer-router-id | statistics ] display ospfv3 [ process-id ] [ area area-id ] request-queue
[ interface-type interface-number ] [ neighbor-id ]
Display OSPFv3 retransmission list information. display ospfv3
[
[ process-id ] [ area interface-type interface-number ] [ area-id ] retrans-queue neighbor-id ]
Display OSPFv3 routing information. display ospfv3 [ process-id ] routing [ ipv6-address prefix-length ]
Display OSPFv3 topology information. display ospfv3 [ process-id ] [ area area-id ] spf-tree [ verbose ] display ospfv3 [ process-id ] statistics [ error ] Display OSPFv3 statistics.
Display OSPFv3 virtual link information. display ospfv3 [ process-id ] vlink
Clear OSPFv3 log information.
Restart an OSPFv3 process. reset ospfv3 [ process-id ] event-log [ lsa-flush | peer | spf ] reset ospfv3 [ process-id ] process [ graceful-restart ]
Restart OSPFv3 route redistribution. reset ospfv3 [ process-id ] redistribution
Clear OSPFv3 statistics. reset ospfv3 [ process-id ] statistics
460
OSPFv3 configuration examples
OSPFv3 stub area configuration example
Network requirements
•
Enable OSPFv3 on all switches.
•
Split the AS into three areas.
•
Configure Switch B and Switch C as ABRs to forward routing information between areas.
•
Configure Area 2 as a stub area to reduce LSAs in the area without affecting route reachability.
Figure 103 Network diagram
OSPFv3
Switch B
Vlan-int100
Area 0
2001::1/64
Vlan-int100
2001::2/64
Vlan-int200
2001:1::1/64
Switch C
Vlan-int400
2001:2::1/64
OSPFv3
Area 1
Vlan-int200
2001:1::2/64
OSPFv3
Area 2
Vlan-int400
2001:2::2/64
Switch A
Vlan-int300
2001:3::1/64
Switch D
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic OSPFv3:
# On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 300
[SwitchA-Vlan-interface300] ospfv3 1 area 1
[SwitchA-Vlan-interface300] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ospfv3 1 area 1
[SwitchA-Vlan-interface200] quit
# On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
<SwitchB> system-view
[SwitchB] ospfv3
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 0
[SwitchB-Vlan-interface100] quit
461
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 1
[SwitchB-Vlan-interface200] quit
# On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3.
<SwitchC> system-view
[SwitchC] ospfv3
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 0
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 400
[SwitchC-Vlan-interface400] ospfv3 1 area 2
[SwitchC-Vlan-interface400] quit
# On Switch D, enable OSPFv3 and specify the router ID as 4.4.4.4.
<SwitchD> system-view
[SwitchD] ospfv3
[SwitchD-ospfv3-1] router-id 4.4.4.4
[SwitchD-ospfv3-1] quit
[SwitchD] interface vlan-interface 400
[SwitchD-Vlan-interface400] ospfv3 1 area 2
[SwitchD-Vlan-interface400] quit
# Display OSPFv3 neighbors on Switch B.
[SwitchB] display ospfv3 peer
OSPFv3 Process 1 with Router ID 2.2.2.2
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
3.3.3.3 1 Full/BDR 00:00:40 0 Vlan100
Area: 0.0.0.1
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
1.1.1.1 1 Full/DR 00:00:40 0 Vlan200
# Display OSPFv3 neighbors on Switch C.
[SwitchC] display ospfv3 peer
OSPFv3 Process 1 with Router ID 3.3.3.3
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
2.2.2.2 1 Full/DR 00:00:40 0 Vlan100
Area: 0.0.0.2
-------------------------------------------------------------------------
462
Router ID Pri State Dead-Time InstID Interface
4.4.4.4 1 Full/BDR 00:00:40 0 Vlan400
# Display OSPFv3 routing table information on Switch D.
[SwitchD] display ospfv3 routing
OSPFv3 Process 1 with Router ID 4.4.4.4
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:1::/64
Type : IA Cost : 3
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:2::/64
Type : I Cost : 1
Nexthop : :: Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
*Destination: 2001:3::/64
Type : IA Cost : 4
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
Total: 4
Intra area: 1 Inter area: 3 ASE: 0 NSSA: 0
3. Configure Area 2 as a stub area:
# Configure Switch D.
[SwitchD] ospfv3
[SwitchD-ospfv3-1] area 2
[SwitchD-ospfv3-1-area-0.0.0.2] stub
# Configure Switch C, and specify the cost of the default route sent to the stub area as 10.
[SwitchC] ospfv3
[SwitchC-ospfv3-1] area 2
[SwitchC-ospfv3-1-area-0.0.0.2] stub
[SwitchC-ospfv3-1-area-0.0.0.2] default-cost 10
# Display OSPFv3 routing table information on Switch D.
463
[SwitchD] display ospfv3 routing
OSPFv3 Process 1 with Router ID 4.4.4.4
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: ::/0
Type : IA Cost : 11
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:1::/64
Type : IA Cost : 3
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:2::/64
Type : I Cost : 1
Nexthop : :: Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
*Destination: 2001:3::/64
Type : IA Cost : 4
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
Total: 5
Intra area: 1 Inter area: 4 ASE: 0 NSSA: 0
The output shows that a default route is added, and its cost is the cost of a direct route plus the configured cost.
4. Configure Area 2 as a totally stub area:
# Configure Area 2 as a totally stub area on Switch C.
[SwitchC-ospfv3-1-area-0.0.0.2] stub no-summary
# Display OSPFv3 routing table information on Switch D.
[SwitchD] display ospfv3 routing
464
OSPFv3 Process 1 with Router ID 4.4.4.4
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: ::/0
Type : IA Cost : 11
NextHop : FE80::F40D:0:93D0:1 Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
*Destination: 2001:2::/64
Type : I Cost : 1
Nexthop : :: Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
Total: 2
Intra area: 1 Inter area: 1 ASE: 0 NSSA: 0
The output shows that route entries are reduced. All indirect routes are removed, except the default route.
OSPFv3 NSSA area configuration example
Network requirements
•
Configure OSPFv3 on all switches and split the AS into three areas.
•
Configure Switch B and Switch C as ABRs to forward routing information between areas.
•
Configure Area 1 as an NSSA area and configure Switch A as an ASBR to redistribute static routes into the AS.
Figure 104 Network diagram
OSPFv3
Switch B
Vlan-int100
Area 0
2001::1/64
Vlan-int200
2001:1::1/64
Vlan-int100
2001::2/64
Switch C
Vlan-int400
2001:2::1/64
OSPFv3
Area 1
Vlan-int200
2001:1::2/64
OSPFv3
Area 2
Vlan-int400
2001:2::2/64
Switch A
Vlan-int300
2001:3::1/64
Switch D
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2.
Configure basic OSPFv3 (see " OSPFv3 stub area configuration example ").
465
3. Configure Area 1 as an NSSA area:
# Configure Switch A.
[SwitchA] ospfv3
[SwitchA-ospfv3-1] area 1
[SwitchA-ospfv3-1-area-0.0.0.1] nssa
[SwitchA-ospfv3-1-area-0.0.0.1] quit
[SwitchA-ospfv3-1] quit
# Configure Switch B.
[SwitchB] ospfv3
[SwitchB-ospfv3-1] area 1
[SwitchB-ospfv3-1-area-0.0.0.1] nssa
[SwitchB-ospfv3-1-area-0.0.0.1] quit
[SwitchB-ospfv3-1] quit
# Display OSPFv3 routing information on Switch A.
[SwitchA] display ospfv3 1 routing
OSPFv3 Process 1 with Router ID 1.1.1.1
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::20C:29FF:FE74:59C6 Interface: Vlan200
AdvRouter : 2.2.2.2 Area : 0.0.0.1
Preference : 10
*Destination: 2001:1::/64
Type : I Cost : 1
Nexthop : :: Interface: Vlan200
AdvRouter : 1.1.1.1 Area : 0.0.0.1
Preference : 10
*Destination: 2001:2::/64
Type : IA Cost : 3
NextHop : FE80::20C:29FF:FE74:59C6 Interface: Vlan200
AdvRouter : 2.2.2.2 Area : 0.0.0.1
Preference : 10
Total: 3
Intra area: 1 Inter area: 2 ASE: 0 NSSA: 0
4. Configure route redistribution:
# Configure an IPv6 static route, and configure OSPFv3 to redistribute the static route on
Switch A.
[SwitchA] ipv6 route-static 1234:: 64 null 0
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] import-route static
466
[SwitchA-ospfv3-1] quit
# Display OSPFv3 routing information on Switch D.
[SwitchD] display ospfv3 1 routing
OSPFv3 Process 1 with Router ID 4.4.4.4
-------------------------------------------------------------------------
I - Intra area route, E1 - Type 1 external route, N1 - Type 1 NSSA route
IA - Inter area route, E2 - Type 2 external route, N2 - Type 2 NSSA route
* - Selected route
*Destination: 2001::/64
Type : IA Cost : 2
NextHop : FE80::20C:29FF:FEB9:F2EF Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:1::/64
Type : IA Cost : 3
NextHop : FE80::20C:29FF:FEB9:F2EF Interface: Vlan400
AdvRouter : 3.3.3.3 Area : 0.0.0.2
Preference : 10
*Destination: 2001:2::/64
Type : I Cost : 1
NextHop : :: Interface: Vlan400
AdvRouter : 4.4.4.4 Area : 0.0.0.2
Preference : 10
*Destination: 1234::/64
Type : E2 Cost : 1
NextHop : FE80::20C:29FF:FEB9:F2EF Interface: Vlan400
AdvRouter : 2.2.2.2 Area : 0.0.0.2
Preference : 10
Total: 4
Intra area: 1 Inter area: 2 ASE: 1 NSSA: 0
The output shows an AS external route imported from the NSSA area exists on Switch D.
OSPFv3 DR election configuration example
Network requirements
•
Configure router priority 100 for Switch A, the highest priority on the network, so it will become the DR.
•
Configure router priority 2 for Switch C, the second highest priority on the network, so it will become the BDR.
•
Configure router priority 0 for Switch B, so it cannot become a DR or BDR.
•
Switch D uses the default router priority 1.
467
Figure 105 Network diagram
Switch A Switch B
Vlan-int100
2001::1/64
Vlan-int200
2001::2/64
Vlan-int100
2001::3/64
Vlan-int200
2001::4/64
Switch C
Configuration procedure
Switch D
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic OSPFv3:
# On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 0
[SwitchA-Vlan-interface100] quit
# On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
<SwitchB> system-view
[SwitchB] ospfv3
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 0
[SwitchB-Vlan-interface200] quit
# On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3.
<SwitchC> system-view
[SwitchC] ospfv3
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 0
[SwitchC-Vlan-interface100] quit
# On Switch D, enable OSPFv3 and specify the router ID as 4.4.4.4.
<SwitchD> system-view
[SwitchD] ospfv3
[SwitchD-ospfv3-1] router-id 4.4.4.4
[SwitchD-ospfv3-1] quit
[SwitchD] interface vlan-interface 200
[SwitchD-Vlan-interface200] ospfv3 1 area 0
468
[SwitchD-Vlan-interface200] quit
# Display neighbor information on Switch A. The switches have the same default DR priority 1, so Switch D (the switch with the highest router ID) is elected as the DR, and Switch C is the
BDR.
[SwitchA] display ospfv3 peer
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
2.2.2.2 1 2-Way/DROther 00:00:36 0 Vlan200
3.3.3.3 1 Full/BDR 00:00:35 0 Vlan100
4.4.4.4 1 Full/DR 00:00:33 0 Vlan200
# Display neighbor information on Switch D. The neighbor states are all full.
[SwitchD] display ospfv3 peer
OSPFv3 Process 1 with Router ID 4.4.4.4
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
1.1.1.1 1 Full/DROther 00:00:30 0 Vlan100
2.2.2.2 1 Full/DROther 00:00:37 0 Vlan200
3.3.3.3 1 Full/BDR 00:00:31 0 Vlan100
3. Configure router priorities for interfaces:
# Set the router priority of VLAN-interface 100 to 100 on Switch A.
[SwitchA] interface Vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 dr-priority 100
[SwitchA-Vlan-interface100] quit
# Set the router priority of VLAN-interface 200 to 0 on Switch B.
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 dr-priority 0
[SwitchB-Vlan-interface200] quit
# Set the router priority of VLAN-interface 100 to 2 on Switch C.
[SwitchC] interface Vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 dr-priority 2
[SwitchC-Vlan-interface100] quit
# Display neighbor information on Switch A. Router priorities have been updated, but the DR and BDR are not changed.
[SwitchA] display ospfv3 peer
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
2.2.2.2 0 2-Way/DROther 00:00:36 0 Vlan200
469
3.3.3.3 2 Full/BDR 00:00:35 0 Vlan200
4.4.4.4 1 Full/DR 00:00:33 0 Vlan200
# Display neighbor information on Switch D. Switch D is still the DR.
[SwitchD] display ospfv3 peer
OSPFv3 Process 1 with Router ID 4.4.4.4
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
1.1.1.1 100 Full/DROther 00:00:30 0 Vlan100
2.2.2.2 0 Full/DROther 00:00:37 0 Vlan200
3.3.3.3 2 Full/BDR 00:00:31 0 Vlan100
4. Restart DR and BDR election:
# Use the shutdown and undo shutdown commands on interfaces to restart DR and BDR election. (Details not shown.)
# Display neighbor information on Switch A. The output shows that Switch C becomes the BDR.
[SwitchA] display ospfv3 peer
OSPFv3 Process 1 with Router ID 1.1.1.1
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
2.2.2.2 0 Full/DROther 00:00:36 0 Vlan200
3.3.3.3 2 Full/BDR 00:00:35 0 Vlan100
4.4.4.4 1 Full/DROther 00:00:33 0 Vlan200
# Display neighbor information on Switch D.
[SwitchD] display ospfv3 peer
OSPFv3 Process 1 with Router ID 4.4.4.4
Area: 0.0.0.0
-------------------------------------------------------------------------
Router ID Pri State Dead-Time InstID Interface
1.1.1.1 100 Full/DR 00:00:30 0 Vlan100
2.2.2.2 0 2-Way/DROther 00:00:37 0 Vlan200
3.3.3.3 2 Full/BDR 00:00:31 0 Vlan100
The output shows that Switch A becomes the DR.
OSPFv3 route redistribution configuration example
Network requirements
•
Switch A, Switch B, and Switch C are in Area 2.
•
OSPFv3 process 1 and OSPFv3 process 2 run on Switch B. Switch B communicates with
Switch A and Switch C through OSPFv3 process 1 and OSPFv3 process 2.
470
•
Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process
1 on Switch B, and set the default metric for redistributed routes to 3. Switch C can then learn the routes destined for 1::0/64 and 2::0/64, and Switch A cannot learn the routes destined for
3::0/64 or 4::0/64.
Figure 106 Network diagram
Vlan-int200
2::1/64 Vlan-int100
1::1/64
Vlan-int300
3::2/64
Vlan-int400
4::1/64
Switch A Switch C
Process 1
Area 2
Process 2
Area 2
Vlan-int100
1::2/64
Vlan-int300
3::1/64
Switch B
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic OSPFv3:
# Enable OSPFv3 process 1 on Switch A.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 2
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ospfv3 1 area 2
[SwitchA-Vlan-interface200] quit
# Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B.
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 2
[SwitchB-Vlan-interface100] quit
[SwitchB] ospfv3 2
[SwitchB-ospfv3-2] router-id 3.3.3.3
[SwitchB-ospfv3-2] quit
[SwitchB] interface vlan-interface 300
[SwitchB-Vlan-interface300] ospfv3 2 area 2
[SwitchB-Vlan-interface300] quit
# Enable OSPFv3 process 2 on Switch C.
<SwitchC> system-view
[SwitchC] ospfv3 2
[SwitchC-ospfv3-2] router-id 4.4.4.4
[SwitchC-ospfv3-2] quit
471
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] ospfv3 2 area 2
[SwitchC-Vlan-interface300] quit
[SwitchC] interface vlan-interface 400
[SwitchC-Vlan-interface400] ospfv3 2 area 2
[SwitchC-Vlan-interface400] quit
# Display the routing table on Switch C.
[SwitchC] display ipv6 routing-table
Destinations : 7 Routes : 7
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 3::/64 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan300 Cost : 0
Destination: 3::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 4::/64 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan400 Cost : 0
Destination: 4::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0
3. Configure OSPFv3 route redistribution:
# Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B.
[SwitchB] ospfv3 2
[SwitchB-ospfv3-2] default cost 3
[SwitchB-ospfv3-2] import-route ospfv3 1
[SwitchB-ospfv3-2] import-route direct
[SwitchB-ospfv3-2] quit
# Display the routing table on Switch C.
[SwitchC] display ipv6 routing-table
472
Destinations : 9 Routes : 9
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 1::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 3
Destination: 2::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 3
Destination: 3::/64 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan300 Cost : 0
Destination: 3::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 4::/64 Protocol : Direct
NextHop : :: Preference: 0
Interface : Vlan400 Cost : 0
Destination: 4::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0
OSPFv3 route summarization configuration example
Network requirements
•
Switch A, Switch B, and Switch C are in Area 2.
•
OSPFv3 process 1 and OSPFv3 process 2 run on Switch B. Switch B communicates with
Switch A and Switch C through OSPFv3 process 1 and OSPFv3 process 2, respectively.
•
On Switch A, configure IPv6 addresses 2:1:1::1/64, 2:1:2::1/64, and 2:1:3::1/64 for
VLAN-interface 200.
473
•
On Switch B, configure OSPFv3 process 2 to redistribute direct routes and the routes from
OSPFv3 process 1. Switch C can then learn the routes destined for 2::/64, 2:1:1::/64, 2:1:2::/64, and 2:1:3::/64.
•
On Switch B, configure route summarization to advertise only summary route 2::/16 to Switch
C.
Figure 107 Network diagram
Vlan-int200
2::1/64 Vlan-int100
1::1/64
Vlan-int300
3::2/64
Vlan-int400
4::1/64
Switch A Switch C
Process 1
Area 2
Process 2
Area 2
Vlan-int100
1::2/64
Vlan-int300
3::1/64
Switch B
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure OSPFv3:
# Enable OSPFv3 process 1 on Switch A.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 2
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ipv6 address 2:1:1::1 64
[SwitchA-Vlan-interface200] ipv6 address 2:1:2::1 64
[SwitchA-Vlan-interface200] ipv6 address 2:1:3::1 64
[SwitchA-Vlan-interface200] ospfv3 1 area 2
[SwitchA-Vlan-interface200] quit
# Enable OSPFv3 process 1 and OSPFv3 process 2 on Switch B.
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 2
[SwitchB-Vlan-interface100] quit
[SwitchB] ospfv3 2
[SwitchB-ospfv3-2] router-id 3.3.3.3
[SwitchB-ospfv3-2] quit
[SwitchB] interface vlan-interface 300
[SwitchB-Vlan-interface300] ospfv3 2 area 2
[SwitchB-Vlan-interface300] quit
# Enable OSPFv3 process 2 on Switch C.
474
<SwitchC> system-view
[SwitchC] ospfv3 2
[SwitchC-ospfv3-2] router-id 4.4.4.4
[SwitchC-ospfv3-2] quit
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] ospfv3 2 area 2
[SwitchC-Vlan-interface300] quit
[SwitchC] interface vlan-interface 400
[SwitchC-Vlan-interface400] ospfv3 2 area 2
[SwitchC-Vlan-interface400] quit
3. Configure OSPFv3 route redistribution:
# Configure OSPFv3 process 2 to redistribute direct routes and the routes from OSPFv3 process 1 on Switch B.
[SwitchB] ospfv3 2
[SwitchB-ospfv3-2] import-route ospfv3 1
[SwitchB-ospfv3-2] import-route direct
[SwitchB-ospfv3-2] quit
# Display the routing table on Switch C.
[SwitchC] display ipv6 routing-table
Destinations : 12 Routes : 12
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 1::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 2::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 2:1:1::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 2:1:2::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 2:1:3::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 3::/64 Protocol : Direct
NextHop : 3::2 Preference: 0
475
Interface : Vlan300 Cost : 0
Destination: 3::2/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 4::/64 Protocol : Direct
NextHop : 4::1 Preference: 0
Interface : Vlan400 Cost : 0
Destination: 4::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0
4. Configure ASBR route summarization:
# On Switch B, configure OSPFv3 process 2 to advertise a single route 2::/16.
[SwitchB] ospfv3 2
[SwitchB-ospfv3-2] asbr-summary 2:: 16
[SwitchB-ospfv3-2] quit
# Display the routing table on Switch C.
[SwitchC] display ipv6 routing-table
Destinations : 9 Routes : 9
Destination: ::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 1::/64 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 2::/16 Protocol : O_ASE2
NextHop : FE80::200:CFF:FE01:1C03 Preference: 150
Interface : Vlan300 Cost : 1
Destination: 3::/64 Protocol : Direct
NextHop : 3::2 Preference: 0
Interface : Vlan300 Cost : 0
Destination: 3::2/128 Protocol : Direct
476
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: 4::/64 Protocol : Direct
NextHop : 4::1 Preference: 0
Interface : Vlan400 Cost : 0
Destination: 4::1/128 Protocol : Direct
NextHop : ::1 Preference: 0
Interface : InLoop0 Cost : 0
Destination: FE80::/10 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0 Cost : 0
Destination: FF00::/8 Protocol : Direct
NextHop : :: Preference: 0
Interface : NULL0
OSPFv3 GR configuration example
Network requirements
•
Switch A, Switch B, and Switch C that reside in the same AS and the same OSPFv3 routing domain are GR capable.
•
Switch A acts as the GR restarter. Switch B and Switch C act as the GR helpers, and synchronize their LSDBs with Switch A through GR.
Figure 108 Network diagram
Router ID: 1.1.1.1
GR restarter
Switch A
Vlan-int100
2000::1/24
Vlan-int100
2000::2/24
Switch B
Vlan-int100
2000::3/24
Switch C
GR helper
Router ID: 2.2.2.2
Configuration procedure
GR helper
Router ID: 3.3.3.3
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure basic OSPFv3:
# On Switch A, enable OSPFv3 process 1, enable GR, and set the router ID to 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] graceful-restart enable
477
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 1
[SwitchA-Vlan-interface100] quit
# On Switch B, enable OSPFv3 and set the router ID to 2.2.2.2. (By default, GR helper is enabled on Switch B.)
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 1
[SwitchB-Vlan-interface100] quit
# On Switch C, enable OSPFv3 and set the router ID to 3.3.3.3. (By default, GR helper is enabled on Switch C.)
<SwitchC> system-view
[SwitchC] ospfv3 1
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 1
[SwitchC-Vlan-interface100] quit
Verifying the configuration
# Perform a master/backup switchover on Switch A to trigger an OSPFv3 GR operation. (Details not shown.)
OSPFv3 NSR configuration example
Network requirements
As shown in Figure 109 , Switch S, Switch A, and Switch B belong to the same AS and OSPFv3
routing domain. Enable OSPFv3 NSR on Switch S to ensure correct routing when an active/standby switchover occurs on Switch S.
Figure 109 Network diagram
Loop 0
2002::2/128
Switch A
Vlan-int100
1200:1::1/64
Vlan-int100
1200:1::2/64
Switch S
Vlan-int200
1400:1::2/64
Vlan-int200
1400:1::1/64
Switch B
Loop 0
4004::4/128
Configuration procedure
1. Configure IP addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure OSPFv3 on the switches to ensure that Switch S, Switch A, and Switch B can communicate with each other at Layer 3. (Details not shown.)
3. Configure OSPFv3:
# On Switch A, enable OSPFv3, and set the router ID to 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] router-id 1.1.1.1
478
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ospfv3 1 area 1
[SwitchA-Vlan-interface100] quit
# On Switch B, enable OSPFv3, and set the router ID to 2.2.2.2.
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 1
[SwitchB-Vlan-interface200] quit
# On Switch S, enable OSPFv3, set the router ID to 3.3.3.3, and enable NSR.
<SwitchS> system-view
[SwitchS] ospfv3 1
[SwitchS-ospfv3-1] router-id 3.3.3.3
[SwitchS-ospfv3-1] non-stop-routing
[SwitchS-ospfv3-1] quit
[SwitchS] interface vlan-interface 100
[SwitchS-Vlan-interface100] ospfv3 1 area 1
[SwitchS-Vlan-interface100] quit
[SwitchS] interface vlan-interface 200
[SwitchS-Vlan-interface200] ospfv3 1 area 1
[SwitchS-Vlan-interface200] quit
Verifying the configuration
# Verify the following:
•
When an active/standby switchover occurs on Switch S, the neighbor relationships and routing information on Switch A and Switch B have not changed. (Details not shown.)
•
The traffic from Switch A to Switch B has not been impacted. (Details not shown.)
BFD for OSPFv3 configuration example
Network requirements
•
Configure OSPFv3 on Switch A, Switch B and Switch C and configure BFD over the link Switch
A<—>L2 Switch<—>Switch B.
•
After the link Switch A<—>L2 Switch<—>Switch B fails, BFD can quickly detect the failure and notify OSPFv3 of the failure. Then Switch A and Switch B communicate through Switch C.
479
Figure 110 Network diagram
2001:1::/64
Switch A
Vlan-int10
Vlan-int11
BFD
L2 Switch
Vlan-int10
Switch B
2001:4::/64
Vlan-int13
Area 0
Vlan-int11 Vlan-int13
Switch C
Table 26 Interface and IP address assignment
Device
Switch A
Switch A
Switch B
Switch B
Interface
Vlan-int10
Vlan-int11
Vlan-int10
Vlan-int13
IPv6 address
2001::1/64
2001:2::1/64
2001::2/64
2001:3::2/64
Switch C Vlan-int11 2001:2::2/64
Switch C
Configuration procedure
Vlan-int13 2001:3::1/64
1. Configure IPv6 addresses for the interfaces. (Details not shown.)
2. Configure basic OSPFv3:
# On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ospfv3 1 area 0
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] ospfv3 1 area 0
[SwitchA-Vlan-interface11] quit
# On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
<SwitchB> system-view
[SwitchB] ospfv3
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ospfv3 1 area 0
[SwitchB-Vlan-interface10] quit
[SwitchB] interface vlan-interface 13
[SwitchB-Vlan-interface13] ospfv3 1 area 0
480
[SwitchB-Vlan-interface13] quit
# On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3.
<SwitchC> system-view
[SwitchC] ospfv3
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 11
[SwitchC-Vlan-interface11] ospfv3 1 area 0
[SwitchC-Vlan-interface11] quit
[SwitchC] interface vlan-interface 13
[SwitchC-Vlan-interface13] ospfv3 1 area 0
[SwitchC-Vlan-interface13] quit
3. Configure BFD:
# Enable BFD and configure BFD parameters on Switch A.
[SwitchA] bfd session init-mode active
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ospfv3 bfd enable
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500
[SwitchA-Vlan-interface10] bfd min-receive-interval 500
[SwitchA-Vlan-interface10] bfd detect-multiplier 7
[SwitchA-Vlan-interface10] return
# Enable BFD and configure BFD parameters on Switch B.
[SwitchB] bfd session init-mode active
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ospfv3 bfd enable
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500
[SwitchB-Vlan-interface10] bfd min-receive-interval 500
[SwitchB-Vlan-interface10] bfd detect-multiplier 6
Verifying the configuration
# Display the BFD information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Init Mode: Active
IPv6 Session Working Under Ctrl Mode:
Local Discr: 1441 Remote Discr: 1450
Source IP: FE80::20F:FF:FE00:1202 (link-local address of VLAN-interface 10 on
Switch A)
Destination IP: FE80::20F:FF:FE00:1200 (link-local address of VLAN-interface 10 on
Switch B)
Session State: Up Interface: Vlan10
Hold Time: 2319ms
# Display routes destined for 2001:4::0/64 on Switch A.
<SwitchA> display ipv6 routing-table 2001:4::0 64
Summary Count : 1
481
Destination: 2001:4::/64 Protocol : O_INTRA
NextHop : FE80::20F:FF:FE00:1200 Preference: 10
Interface : Vlan10 Cost : 1
The output information shows that Switch A communicates with Switch B through VLAN-interface 10.
The link over VLAN-interface 10 fails.
# Display routes to 2001:4::0/64 on Switch A.
<SwitchA> display ipv6 routing-table 2001:4::0 64
Summary Count : 1
Destination: 2001:4::/64 Protocol : O_INTRA
NextHop : FE80::BAAF:67FF:FE27:DCD0 Preference: 10
Interface : Vlan11 Cost : 2
The output shows that Switch A communicates with Switch B through VLAN-interface 11.
OSPFv3 FRR configuration example
Network requirements
As shown in Figure 111 , Switch A, Switch B, and Switch C reside in the same OSPFv3 domain.
Configure OSPFv3 FRR so that when Link A fails, traffic is immediately switched to Link B.
Figure 111 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
101
Link B
Vlan
-int
100
Link A
Loop0
Switch A
Vlan-int200
Table 27 Interface and IP address assignment
Vlan
-int
101
Vlan-int200
Switch B
Loop0
Device
Switch A
Switch C
Interface IP address
Vlan-int100 1::1/64
Vlan-int200 2::1/64
Loop0 10::1/128
Vlan-int100 1::2/64
Device
Switch B
Interface IP address
Vlan-int101 3::1/64
Vlan-int200 2::2/64
Loop0 20::1/128
Vlan-int101 3::2/64
Configuration procedure
1. Configure IPv6 addresses and subnet masks for interfaces on the switches. (Details not shown.)
2. Configure OSPFv3 on the switches to ensure that Switch A, Switch B, and Switch C can communicate with each other at the network layer. (Details not shown.)
3. Configure OSPFv3 FRR to automatically calculate the backup next hop:
482
You can enable OSPFv3 FRR to either calculate a backup next hop by using the LFA algorithm, or specify a backup next hop by using a routing policy.
(Method 1.) Enable OSPFv3 FRR to calculate the backup next hop by using the LFA algorithm:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] fast-reroute lfa
[SwitchA-ospfv3-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] fast-reroute lfa
[SwitchB-ospfv3-1] quit
(Method 2.) Enable OSPFv3 FRR to designate a backup next hop by using a routing policy:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ipv6 prefix-list abc index 10 permit 10:: 128
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchA-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 100 backup-nexthop 1::2/64
[SwitchA-route-policy-frr-10] quit
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] fast-reroute route-policy frr
[SwitchA-ospfv3-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ipv6 prefix-list abc index 10 permit 20:: 128
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 101 backup-nexthop 3::2/64
[SwitchB-route-policy-frr-10] quit
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] fast-reroute route-policy frr
[SwitchB-ospfv3-1] quit
Verifying the configuration
# Display the route 20::1/128 on Switch A to view the backup next hop information.
[SwitchA] display ipv6 routing-table 20::1 128 verbose
Summary count : 1
Destination: 20::1/128
Protocol: O_INTRA
Process ID: 1
SubProtID: 0x1 Age: 00h03m45s
Cost: 6 Preference: 10
483
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x23000005 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10041 OrigNextHop: FE80::7685:45FF:FEAD:102
Label: NULL RealNextHop: FE80::7685:45FF:FEAD:102
BkLabel: NULL BkNextHop: FE80::34CD:9FF:FE2F:D02
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display the route 10::1/128 on Switch B to view the backup next hop information.
[SwitchB] display ipv6 routing-table 10::1 128 verbose
Summary count : 1
Destination: 10::1/128
Protocol: O_INTRA
Process ID: 1
SubProtID: 0x1 Age: 00h03m10s
Cost: 1 Preference: 10
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0x0 OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x23000006 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10041 OrigNextHop: FE80::34CC:E8FF:FE5B:C02
Label: NULL RealNextHop: FE80::34CC:E8FF:FE5B:C02
BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
OSPFv3 IPsec profile configuration example
Network requirements
As shown in Figure 112 , all switches run OSPFv3, and the AS is divided into two areas.
Configure IPsec profiles on the switches to authenticate and encrypt protocol packets.
484
Figure 112 Network diagram
OSPFv3
Switch B
Vlan-int100
Area 0
2001::1/64
Vlan-int100
2001::2/64
Vlan-int200
2001:1::1/64
Switch C
OSPFv3
Area 1
Vlan-int200
2001:1::2/64
Switch A
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure OSPFv3 basic features:
# On Switch A, enable OSPFv3 and specify the router ID as 1.1.1.1.
<SwitchA> system-view
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] router-id 1.1.1.1
[SwitchA-ospfv3-1] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ospfv3 1 area 1
[SwitchA-Vlan-interface200] quit
# On Switch B, enable OSPFv3 and specify the router ID as 2.2.2.2.
<SwitchB> system-view
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] router-id 2.2.2.2
[SwitchB-ospfv3-1] quit
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ospfv3 1 area 0
[SwitchB-Vlan-interface100] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] ospfv3 1 area 1
[SwitchB-Vlan-interface200] quit
# On Switch C, enable OSPFv3 and specify the router ID as 3.3.3.3.
<SwitchC> system-view
[SwitchC] ospfv3 1
[SwitchC-ospfv3-1] router-id 3.3.3.3
[SwitchC-ospfv3-1] quit
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] ospfv3 1 area 0
[SwitchC-Vlan-interface100] quit
3. Configure OSPFv3 IPsec profiles:
On Switch A:
# Create an IPsec transform set named trans .
[SwitchA] ipsec transform-set trans
485
# Specify the encapsulation mode as transport .
[SwitchA-ipsec-transform-set-trans] encapsulation-mode transport
# Specify the ESP encryption and authentication algorithms.
[SwitchA-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc
[SwitchA-ipsec-transform-set-trans] esp authentication-algorithm md5
# Specify the AH authentication algorithm.
[SwitchA-ipsec-transform-set-trans] ah authentication-algorithm md5
[SwitchA-ipsec-transform-set-trans] quit
# Create a manual IPsec profile named profile001 .
[SwitchA] ipsec profile profile001 manual
# Use IPsec transform set trans .
[SwitchA-ipsec-profile-profile001-manual] transform-set trans
# Configure the inbound and outbound SPIs for AH.
[SwitchA-ipsec-profile-profile001-manual] sa spi inbound ah 111111111
[SwitchA-ipsec-profile-profile001-manual] sa spi outbound ah 111111111
# Configure the inbound and outbound SPIs for ESP.
[SwitchA-ipsec-profile-profile001-manual] sa spi inbound esp 200000
[SwitchA-ipsec-profile-profile001-manual] sa spi outbound esp 200000
# Configure the inbound and outbound SA keys for AH.
[SwitchA-ipsec-profile-profile001-manual] sa string-key inbound ah simple abc
[SwitchA-ipsec-profile-profile001-manual] sa string-key outbound ah simple abc
# Configure the inbound and outbound SA keys for ESP.
[SwitchA-ipsec-profile-profile001-manual] sa string-key inbound esp simple 123
[SwitchA-ipsec-profile-profile001-manual] sa string-key outbound esp simple 123
[SwitchA-ipsec-profile-profile001-manual] quit
On Switch B:
# Create an IPsec transform set named trans .
[SwitchB] ipsec transform-set trans
# Specify the encapsulation mode as transport .
[SwitchB-ipsec-transform-set-trans] encapsulation-mode transport
# Specify the ESP encryption and authentication algorithms.
[SwitchB-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc
[SwitchB-ipsec-transform-set-trans] esp authentication-algorithm md5
# Specify the AH authentication algorithm.
[SwitchB-ipsec-transform-set-trans] ah authentication-algorithm md5
[SwitchB-ipsec-transform-set-trans] quit
# Create a manual IPsec profile named profile001 .
[SwitchB] ipsec profile profile001 manual
# Use IPsec transform set trans .
[SwitchB-ipsec-profile-profile001-manual] transform-set trans
# Configure the inbound and outbound SPIs for AH.
[SwitchB-ipsec-profile-profile001-manual] sa spi inbound ah 111111111
[SwitchB-ipsec-profile-profile001-manual] sa spi outbound ah 111111111
# Configure the inbound and outbound SPIs for ESP.
[SwitchB-ipsec-profile-profile001-manual] sa spi inbound esp 200000
[SwitchB-ipsec-profile-profile001-manual] sa spi outbound esp 200000
# Configure the inbound and outbound SA keys for AH.
486
[SwitchB-ipsec-profile-profile001-manual] sa string-key inbound ah simple abc
[SwitchB-ipsec-profile-profile001-manual] sa string-key outbound ah simple abc
# Configure the inbound and outbound SA keys for ESP.
[SwitchB-ipsec-profile-profile001-manual] sa string-key inbound esp simple 123
[SwitchB-ipsec-profile-profile001-manual] sa string-key outbound esp simple 123
[SwitchB-ipsec-profile-profile001-manual] quit
# Create a manual IPsec profile named profile002 .
[SwitchB] ipsec profile profile002 manual
# Use IPsec transform set trans .
[SwitchB-ipsec-profile-profile002-manual] transform-set trans
# Configure the inbound and outbound SPIs for AH.
[SwitchB-ipsec-profile-profile002-manual] sa spi inbound ah 4294967295
[SwitchB-ipsec-profile-profile002-manual] sa spi outbound ah 4294967295
# Configure the inbound and outbound SPIs for ESP.
[SwitchB-ipsec-profile-profile002-manual] sa spi inbound esp 256
[SwitchB-ipsec-profile-profile002-manual] sa spi outbound esp 256
# Configure the inbound and outbound SA keys for AH.
[SwitchB-ipsec-profile-profile002-manual] sa string-key inbound ah simple hello
[SwitchB-ipsec-profile-profile002-manual] sa string-key outbound ah simple hello
# Configure the inbound and outbound SA keys for ESP.
[SwitchB-ipsec-profile-profile002-manual] sa string-key inbound esp simple byebye
[SwitchB-ipsec-profile-profile002-manual] sa string-key outbound esp simple byebye
[SwitchB-ipsec-profile-profile002-manual] quit
On Switch C:
# Create an IPsec transform set named trans .
[SwitchC] ipsec transform-set trans
# Specify the encapsulation mode as transport .
[SwitchC-ipsec-transform-set-trans] encapsulation-mode transport
# Specify the ESP encryption and authentication algorithms.
[SwitchC-ipsec-transform-set-trans] esp encryption-algorithm 3des-cbc
[SwitchC-ipsec-transform-set-trans] esp authentication-algorithm md5
# Specify the AH authentication algorithm.
[SwitchC-ipsec-transform-set-trans] ah authentication-algorithm md5
[SwitchC-ipsec-transform-set-trans] quit
# Create a manual IPsec profile named profile002 .
[SwitchC] ipsec profile profile002 manual
# Use IPsec transform set trans .
[SwitchC-ipsec-profile-profile002-manual] transform-set trans
# Configure the inbound and outbound SPIs for AH.
[SwitchC-ipsec-profile-profile002-manual] sa spi inbound ah 4294967295
[SwitchC-ipsec-profile-profile002-manual] sa spi outbound ah 4294967295
# Configure the inbound and outbound SPIs for ESP.
[SwitchC-ipsec-profile-profile002-manual] sa spi inbound esp 256
[SwitchC-ipsec-profile-profile002-manual] sa spi outbound esp 256
# Configure the inbound and outbound SA keys for AH.
[SwitchC-ipsec-profile-profile002-manual] sa string-key inbound ah simple hello
487
[SwitchC-ipsec-profile-profile002-manual] sa string-key outbound ah simple hello
# Configure the inbound and outbound SA keys for ESP.
[SwitchC-ipsec-profile-profile002-manual] sa string-key inbound esp simple byebye
[SwitchC-ipsec-profile-profile002-manual] sa string-key outbound esp simple byebye
[SwitchC-ipsec-profile-profile002-manual] quit
4. Apply the IPsec profiles to areas:
# Configure Switch A.
[SwitchA] ospfv3 1
[SwitchA-ospfv3-1] area 1
[SwitchA-ospfv3-1-area-0.0.0.1] enable ipsec-profile profile001
[SwitchA-ospfv3-1-area-0.0.0.1] quit
[SwitchA-ospfv3-1] quit
# Configure Switch B.
[SwitchB] ospfv3 1
[SwitchB-ospfv3-1] area 0
[SwitchB-ospfv3-1-area-0.0.0.0] enable ipsec-profile profile002
[SwitchB-ospfv3-1-area-0.0.0.0] quit
[SwitchB-ospfv3-1] area 1
[SwitchB-ospfv3-1-area-0.0.0.1] enable ipsec-profile profile001
[SwitchB-ospfv3-1-area-0.0.0.1] quit
[SwitchB-ospfv3-1] quit
# Configure Switch C.
[SwitchC] ospfv3 1
[SwitchC-ospfv3-1] area 0
[SwitchC-ospfv3-1-area-0.0.0.0] enable ipsec-profile profile002
[SwitchC-ospfv3-1-area-0.0.0.0] quit
[SwitchC-ospfv3-1] quit
Verifying the configuration
# Verify that OSPFv3 packets between Switches A, B, and C are protected by IPsec. (Details not shown.)
488
Configuring IPv6 IS-IS
Overview
IPv6 IS-IS supports all IPv4 IS-IS features except that it advertises IPv6 routing information. This chapter describes only IPv6 IS-IS specific configuration tasks. For information about IS-IS, see
Intermediate System-to-Intermediate System (IS-IS) supports multiple network protocols, including
IPv6. To support IPv6, the IETF added two type-length-values (TLVs) and a new network layer protocol identifier (NLPID).
The TLVs are as follows:
•
IPv6 Reachability —Contains routing prefix and metric information to describe network reachability and has a type value of 236 (0xEC).
•
IPv6 Interface Address —Same as the "IP Interface Address" TLV in IPv4 ISIS, except that the
32-bit IPv4 address is translated to the 128-bit IPv6 address.
The new NLPID is an 8-bit field that identifies which network layer protocol is supported. For IPv6, the NLPID is 142 (0x8E), which must be carried in hello packets sent by IPv6 IS-IS.
Configuring basic IPv6 IS-IS
Before you configure basic IPv6 IS-IS, complete the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IPv6 connectivity between neighboring nodes.
•
Enable IS-IS.
Basic IPv6 IS-IS configuration can implement the interconnection of IPv6 networks.
To configure basic IPv6 IS-IS:
Step
1. Enter system view.
Command system-view
2. Enable an IS-IS process and enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Configure the network entity title (NET) for the IS-IS process. network-entity net
4. Create the IPv6 address family and enter its view. address-family ipv6 [ unicast ]
5. Return to IS-IS view.
6. Return to system view.
7. Enter interface view. quit quit interface interface-type interface-number
8. Enable IPv6 for IS-IS on the interface. isis ipv6 enable [ process-id ]
Remarks
N/A
By default, no IS-IS process is enabled.
By default, no NET is configured.
By default, no IS-IS IPv6 address family exists.
N/A
N/A
N/A
By default, IPv6 is disabled for
IS-IS on an interface.
489
Configuring IPv6 IS-IS route control
Before you configure IPv6 IS-IS route control, complete basic IPv6 IS-IS configuration.
To configure IPv6 IS-IS route control:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ]
Remarks
N/A
N/A
3. Enter IS-IS IPv6 address family view.
4. Specify a preference for
IPv6 IS-IS routes. address-family ipv6 [ unicast ] N/A
5. Configure an IPv6 IS-IS summary route.
6. Configure IPv6 IS-IS to advertise a default route.
7. Configure IPv6 IS-IS to filter redistributed routes.
8. Configure IPv6 IS-IS to filter received routes.
9. Configure IPv6 IS-IS to redistribute routes from another routing protocol.
10. Configure the maximum number of redistributed
Level 1/Level 2 IPv6 routes.
11. Configure route advertisement from
Level-2 to Level-1.
12. Configure route advertisement from
Level-1 to Level-2.
13. Specify the maximum number of ECMP routes for load balancing. preference { route-policy route-policy-name | preference } *
By default, the default setting is 15.
summary ipv6-prefix prefix-length
[ avoid-feedback | generate_null0_route |
[ level-1 | level-1-2 | level-2 ] | tag tag ] *
By default, no IPv6 IS-IS summary route is configured. default-route-advertise [ avoid-learning |
[ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] *
By default, IPv6 IS-IS does not advertise Level-1 and
Level-2 default routes. filter-policy
[ process-id
{
] ] ipv6-acl-number prefix-list-name | route-policy route-policy-name } export [
| prefix-list protocol
By default, IPv6 IS-IS does not filter redistributed routes.
This command is usually used together with the import-route command. filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } import
By default, IPv6 IS-IS does not filter received routes.
import-route protocol [ as-number | process-id ] [ allow-ibgp ] [ allow-direct | cost cost-value | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name |
tag tag ] *
By default, IPv6 IS-IS does not redistribute routes from any other routing protocol.
import-route limit number
By default, the maximum number of redistributed
Level 1/Level 2 IPv6 routes is not configured. import-route isisv6 level-2 into level-1
[ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
By default, IPv6 IS-IS does not advertise routes from
Level-2 to Level-1. import-route isisv6 level-1 into level-2
[ filter-policy { ipv6-acl-number | prefix-list prefix-list-name | route-policy route-policy-name } | tag tag ] *
By default, IPv6 IS-IS advertises routes from
Level-1 to Level-2.
maximum load-balancing number
By default, the maximum number of ECMP routes equals the maximum number of ECMP routes supported by the system.
490
Configuring IPv6 IS-IS link cost
Configuring an IPv6 IS-IS cost for an interface
Step
1. Enter system view.
2. Enter IS-IS view.
3. Specify an IS-IS cost style.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { narrow | wide | wide-compatible | { compatible | narrow-compatible } [ relax-spf-limit ] }
4. Enter IPv6 address family view. address-family ipv6 [ unicast
5. Enable IPv6 IS-IS MTR. multi-topology [ compatible ]
]
6. Return to IS-IS view.
7. Return to system view.
8. Enter interface view.
9. Enable IPv6 for IS-IS on the interface. quit quit interface interface-type interface-number isis ipv6 enable [ process-id ]
10. Specify an IPv6 cost for the IS-IS interface. isis ipv6 cost
Configuring a global IPv6 IS-IS cost
Remarks
N/A
N/A
By default, the IS-IS cost type is narrow .
N/A
By default, IPv6 IS-IS MTR is disabled.
N/A
N/A
N/A
By default, IPv6 is disabled for IS-IS on an interface.
By default, no IPv6 cost is specified for the interface.
Step Command
1. Enter system view.
system-view
2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Specify an IS-IS cost style.
4. Enter IPv6 address family view.
5. Enable IPv6 IS-IS
MTR. cost-style { wide | wide-compatible | compatible } address-family ipv6 [ unicast ] multi-topology [ compatible ]
6. Specify a global
IPv6 IS-IS cost.
circuit-cost cost-value [ level-1 | level-2 ]
Enabling automatic link cost calculation
Step
1. Enter system view.
Command system-view
2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Specify an IS-IS cost style.
4. Enter IPv6 address family view. cost-style { wide wide-compatible
|
} address-family ipv6 [ unicast ]
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow .
N/A
By default, IPv6 IS-IS MTR is disabled.
By default, no global IPv6 cost is specified.
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow .
N/A
491
Step Command
5. Enable IPv6 IS-IS MTR. multi-topology [ compatible ]
6. Enable automatic IPv6
IS-IS cost calculation.
7. (Optional.) Configure a bandwidth reference value for automatic IPv6
IS-IS cost calculation. auto-cost enable bandwidth-reference value
Remarks
By default, IPv6 IS-IS MTR is disabled.
By default, automatic IPv6 IS-IS cost calculation is disabled.
The default setting is 100 Mbps.
Tuning and optimizing IPv6 IS-IS networks
Configuration prerequisites
Before you tune and optimize IPv6 IS-IS networks, complete basic IPv6 IS-IS tasks.
Assigning a convergence priority to IPv6 IS-IS routes
A topology change causes IS-IS routing convergence. To improve convergence speed, you can assign convergence priorities to IPv6 IS-IS routes. Convergence priority levels are critical, high, medium, and low. The higher the convergence priority, the faster the convergence speed.
By default, IPv6 IS-IS host routes have medium convergence priority, and other IPv6 IS-IS routes have low convergence priority.
To assign a convergence priority to specific IPv6 IS-IS routes:
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { wide | wide-compatible | compatible }
Remarks
N/A
N/A
3. Specify an IS-IS cost style.
By default, the IS-IS cost style is narrow .
4. Enter IPv6 address family view. address-family ipv6 [ unicast ] N/A
5. Enable IPv6 IS-IS MTR.
6. Assign a convergence priority to specific IPv6 IS-IS routes. multi-topology [ compatible ]
By default, IPv6 IS-IS MTR is disabled.
•
Method 1: prefix-priority { critical | high | medium } { prefix-list prefix-list-name | tag tag-value }
•
Method 2: prefix-priority route-policy route-policy-name
By default, IPv6 IS-IS routes, except IPv6 IS-IS host routes, have the low convergence priority.
492
Setting the LSDB overload bit
Step
1. Enter system view.
2. Enter IS-IS view.
3. Specify an IS-IS cost style.
4. Enter IPv6 address family view.
5. Enable IPv6 IS-IS MTR.
6. Set the overload bit.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { wide | wide-compatible | compatible }
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow . address-family ipv6 [ unicast ] N/A multi-topology [ compatible ]
By default, IPv6 IS-IS MTR is disabled. set-overload [ on-startup
[ [ start-from-nbr system-id
[ timeout1 [ nbr-timeout ] ] ] | timeout2 | wait-for-bgp4+
[ timeout3 ] ] ] [ allow { external | interlevel } * ]
By default, the overload bit is not set.
Configuring a tag value on an interface
When IS-IS advertises an IPv6 prefix with a tag value, it adds the tag to the IPv6 reachability information TLV, regardless of the link cost style.
To configure a tag value on an interface:
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
3. Configure a tag value on the interface.
isis ipv6 tag tag
Remarks
N/A
N/A
By default, no tag value is configured on an interface.
Controlling SPF calculation interval
Step
1. Enter system view.
2. Enter IS-IS view.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { wide | wide-compatible | compatible }
3. Specify an IS-IS cost style.
4. Enter IPv6 address family view. address-family ipv6 [ unicast
5. Enable IPv6 IS-IS MTR. multi-topology [ compatible ]
]
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow .
N/A
By default, IPv6 IS-IS MTR is disabled.
493
Step Command
6. Set the SPF calculation interval.
timer spf maximum-interval
[ minimum-interval
[ incremental-interval ] ]
Remarks
By default:
•
The maximum interval is
5 seconds.
•
The minimum interval is
50 milliseconds.
•
The incremental interval is 200 milliseconds.
Enabling IPv6 IS-IS ISPF
Step Command
1. Enter system view.
system-view
2. Enter IS-IS view. isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { wide | wide-compatible | compatible }
3. Specify an IS-IS cost style.
4. Enter IPv6 address family view.
5. Enable IPv6 IS-IS
MTR.
6. Enable IPv6 IS-IS
ISPF. address-family ipv6 [ unicast ] multi-topology [ compatible ] ispf enable
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow .
N/A
By default, IPv6 IS-IS MTR is disabled.
By default, IPv6 IS-IS ISPF is enabled.
Enabling prefix suppression
Perform this task to disable an interface from advertising its prefix in LSPs. This enhances network security by preventing IP routing to the interval nodes and speeds up network convergence.
To enable prefix suppression:
Step
1. Enter system view.
Command system-view
2. Enter interface view. interface interface-type interface-number
3. Enable prefix suppression on the interface. isis ipv6 prefix-suppression
Remarks
N/A
N/A
By default, prefix suppression is disabled on an interface.
Configuring BFD for IPv6 IS-IS
Bidirectional forwarding detection (BFD) can quickly detect faults between IPv6 IS-IS neighbors to improve the convergence speed of IPv6 IS-IS. For more information about BFD, see High Availability
Configuration Guide .
To configure BFD for IPv6 IS-IS:
Step
1. Enter system view.
Command system-view
Remarks
N/A
494
Step
2. Enable an IS-IS process and enter IS-IS view.
Command isis [ process-id ] [ vpn-instance vpn-instance-name ]
3. Configure the NET for the
IS-IS process.
4. Enter IPv6 address family view.
5. Return to system view. network-entity net address-family ipv6 [ unicast ] N/A quit
Remarks
N/A
By default, no NET is configured.
N/A
6. Enter interface view. interface interface-type interface-number
N/A
7. Enable IPv6 for IS-IS on the interface. isis ipv6 enable [ process-id ]
By default, IPv6 is disabled for
IS-IS on an interface.
8. Enable BFD for IPv6 IS-IS. isis ipv6 bfd enable
By default, BFD for IPv6 IS-IS is disabled.
Configuring IPv6 IS-IS FRR
IMPORTANT:
ECMP routes do not support FRR.
A link or router failure on a path can cause packet loss and routing loop. IPv6 IS-IS FRR enables fast rerouting to minimize the failover time.
Figure 113 Network diagram for IPv6 IS-IS FRR
Backup next hop: Router C
Router B Next hop: Router D Router E
In Figure 113 , after you enable FRR on Router B, IPv6 IS-IS FRR automatically calculates or
designates a backup next hop when a link failure is detected. In this way, packets are directed to the backup next hop to reduce traffic recovery time. Meanwhile, IPv6 IS-IS calculates the shortest path based on the new network topology, and forwards packets over the path after network convergence.
You can assign a backup next hop for IPv6 IS-IS FRR in the following ways:
•
Enable IPv6 IS-IS FRR to calculate a backup next hop through Loop Free Alternate (LFA) calculation.
•
Designate a backup next hop with a routing policy for routes matching specific criteria.
Configuration prerequisites
Before you configure IPv6 IS-IS FRR, complete the following tasks:
•
Configure IPv6 addresses for interfaces to ensure IP connectivity between neighboring nodes.
•
Enable IPv6 IS-IS.
•
Make sure the backup next hop is reachable.
495
Configuration procedure
Configuring IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. (Optional.) Disable LFA calculation on the interface. isis ipv6 fast-reroute lfa-backup exclude
By default, the interface participates in LFA calculation and can be elected as a backup interface.
N/A 4. Return to system view. quit
5. Enter IS-IS IPv6 unicast address family view. isis [ process-id ] [ vpn-instance vpn-instance-name ] address-family ipv6 [ unicast ]
N/A
6. Enable IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation. fast-reroute lfa
By default, IPv6 IS-IS FRR is disabled.
Configuring IPv6 IS-IS FRR using a routing policy
You can use the apply ipv6 fast-reroute backup-interface command to specify a backup next hop in a routing policy for routes matching specific criteria. You can also perform this task to reference the routing policy for IPv6 IS-IS FRR. For more information about the apply ipv6 fast-reroute backup-interface
command and routing policy configurations, see " Configuring routing policies ."
To configure IPv6 IS-IS FRR using a routing policy:
Step
1. Enter system view.
2. Enter interface view.
Command system-view
interface interface-type interface-number
Remarks
N/A
N/A
3. (Optional.) Disable LFA calculation on the interface. isis ipv6 fast-reroute lfa-backup exclude
By default, the interface participates in LFA calculation, and can be elected as a backup interface.
4. Return to system view. quit N/A
5. Enter IS-IS IPv6 unicast address family view. isis [ process-id ] [ vpn-instance vpn-instance-name ]
N/A address-family ipv6 [ unicast ]
6. Enable IPv6 IS-IS FRR using a routing policy.
Enabling BFD for IPv6 IS-IS FRR fast-reroute route-policy route-policy-name
By default, IPv6 IS-IS FRR is disabled.
By default, IPv6 IS-IS FRR does not use BFD to detect primary link failures. To speed up IPv6 IS-IS convergence, enable BFD for IPv6 IS-IS FRR to detect primary link failures.
To enable BFD control packet mode for IPv6 IS-IS FRR:
496
Step
1. Enter system view.
2. Enter interface view.
Command system-view interface interface-type interface-number
Remarks
N/A
N/A
3. Enable BFD control packet mode for IPv6 IS-IS FRR. isis ipv6 primary-path-detect bfd ctrl
By default, BFD control packet mode for IPv6 IS-IS FRR is disabled.
To enable BFD echo packet mode for IPv6 IS-IS FRR:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Configure the source IPv6 address of BFD echo packets.
3.
4.
Enter interface view.
Enable BFD echo packet mode for IPv6 IS-IS FRR.
bfd echo-source-ipv6 ip-address
By default, the source IPv6 address of BFD echo packets is not configured.
The source IPv6 address cannot be on the same network segment as any local interface's
IP address.
For more information, see High
Availability Command
Reference . interface interface-type interface-number
N/A isis ipv6 primary-path-detect bfd echo
By default, BFD echo packet mode for IPv6 IS-IS FRR is disabled.
Enabling IPv6 IS-IS MTR
On a network, IPv4 and IPv6 topologies must be consistent so that both IPv6 IS-IS and IPv4 IS-IS can use the SPF algorithm to perform route calculation. If they are different, routers supporting both
IPv4 and IPv6 might send IPv6 packets to routers that do not support IPv6, resulting in packet loss.
To resolve this issue, configure IPv6 IS-IS Multi-Topology Routing (MTR) to perform route calculation separately in IPv4 and IPv6 topologies.
Figure 114 Network diagram
Router A
IPv6 IPv6
Router B
4
IPv6 IPv4
36 3
IPv6
Router D
IPv4
5
IPv4
IPv4
Router C
497
As shown in Figure 114 , the numbers refer to the link costs. Router A, Router B, and Router D
support both IPv4 and IPv6. Router C supports only IPv4 and cannot forward IPv6 packets.
Enable IPv6 IS-IS MTR on Router A, Router B, Router C, and Router D to make them perform route calculation separately in IPv4 and IPv6 topologies. With this configuration, Router A does not forward
IPv6 packets destined to Router D through Router B, avoiding packet loss.
Configuration prerequisites
Before you configure IPv6 IS-IS MTR, configure basic IPv4 and IPv6 IS-IS functions, and establish
IS-IS neighbors.
Configuration procedure
To enable IPv6 IS-IS MTR:
Step
1. Enter system view.
2. Enter IS-IS view.
3. Specify an IS-IS cost style.
Command system-view isis [ process-id ] [ vpn-instance vpn-instance-name ] cost-style { wide | wide-compatible | compatible }
Remarks
N/A
N/A
By default, the IS-IS cost style is narrow .
4. Enter IPv6 address family view. address-family ipv6 [ unicast ] N/A
5. Enable IPv6 IS-IS MTR. multi-topology [ compatible ]
By default, IPv6 IS-IS MTR is disabled.
Displaying and maintaining IPv6 IS-IS
Execute display commands in any view. For other display and reset
Task
Display information about routes redistributed by IPv6 IS-IS.
Display IPv6 IS-IS routing information.
Display IPv6 IS-IS topology information.
Display IPv6 IS-IS route calculation log information.
Command display isis redistribute ipv6 [ ipv6-address mask-length ]
[ level-1 | level-2 ] [ process-id ] display isis route ipv6 [ ipv6-address ] [ [ level-1 | level-2 ] | verbose ] * [ process-id ] display isis spf-tree ipv6 [ [ level-1 | level-2 ] | verbose ] *
[ process-id ] display isis event-log spf ipv6 [ [ level-1 | level-2 ] | verbose ] * [ process-id ]
IPv6 IS-IS configuration examples
IPv6 IS-IS basic configuration example
Network requirements
the same AS. Configure IPv6 IS-IS on the switches so that they can reach each other.
498
Switch A and Switch B are Level-1 switches, Switch D is a Level-2 switch, and Switch C is a
Level-1-2 switch.
Figure 115 Network diagram
Vlan-int100
2001:1::2/64
Switch A
L1
Vlan-int100
2001:1::1/64
Vlan-int200
2001:2::1/64
Switch C
L1/L2
Vlan-int300
2001:3::1/64
Vlan-int300
2001:3::2/64
Switch D
L2
Vlan-int301
2001:4::1/64
Vlan-int200
2001:2::2/64
Area 20
Switch B
L1
Area 10
Configuration procedure
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure IPv6 IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] is-level level-1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] address-family ipv6
[SwitchA-isis-1-ipv6] quit
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] isis ipv6 enable 1
[SwitchA-Vlan-interface100] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] is-level level-1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] address-family ipv6
[SwitchB-isis-1-ipv6] quit
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] isis ipv6 enable 1
[SwitchB-Vlan-interface200] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] address-family ipv6
[SwitchC-isis-1-ipv6] quit
[SwitchC-isis-1] quit
499
[SwitchC] interface vlan-interface 100
[SwitchC-Vlan-interface100] isis ipv6 enable 1
[SwitchC-Vlan-interface100] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis ipv6 enable 1
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 300
[SwitchC-Vlan-interface300] isis ipv6 enable 1
[SwitchC-Vlan-interface300] quit
# Configure Switch D.
<SwitchD> system-view
[SwitchD] isis 1
[SwitchD-isis-1] is-level level-2
[SwitchD-isis-1] network-entity 20.0000.0000.0004.00
[SwitchD-isis-1] address-family ipv6
[SwitchD-isis-1-ipv6] quit
[SwitchD-isis-1] quit
[SwitchD] interface vlan-interface 300
[SwitchD-Vlan-interface300] isis ipv6 enable 1
[SwitchD-Vlan-interface300] quit
[SwitchD] interface vlan-interface 301
[SwitchD-Vlan-interface301] isis ipv6 enable 1
[SwitchD-Vlan-interface301] quit
Verifying the configuration
# Display the IPv6 IS-IS routing table on Switch A.
[SwitchA] display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 Forwarding Table
-----------------------------
Destination : :: PrefixLen: 0
Flag : R/-/- Cost : 10
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100
Destination : 2001:1:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan100
Destination : 2001:2:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100
Destination : 2001:3:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan100
500
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
# Display the IPv6 IS-IS routing table on Switch B.
[SwitchB] display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 Forwarding Table
-----------------------------
Destination : :: PrefixLen: 0
Flag : R/-/- Cost : 10
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200
Destination : 2001:1:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200
Destination : 2001:2:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : Direct Interface: Vlan200
Destination : 2001:3:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan200
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
# Display the IPv6 IS-IS routing table on Switch C.
[SwitchC] display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-1 IPv6 Forwarding Table
-----------------------------
Destination : 2001:1:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan100
Destination : 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan200
Destination : 2001:3:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan300
501
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
Level-2 IPv6 Forwarding Table
-----------------------------
Destination : 2001:1:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan100
Destination : 2001:2:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan200
Destination : 2001:3:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan300
Destination : 2001:4::1 PrefixLen: 128
Flag : R/-/- Cost : 10
Next Hop : FE80::20F:E2FF:FE3E:FA3D Interface: Vlan300
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
# Display the IPv6 IS-IS routing table on Switch D.
[SwitchD] display isis route ipv6
Route information for IS-IS(1)
------------------------------
Level-2 IPv6 Forwarding Table
-----------------------------
Destination : 2001:1:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan300
Destination : 2001:2:: PrefixLen: 64
Flag : R/-/- Cost : 20
Next Hop : FE80::200:FF:FE0F:4 Interface: Vlan300
Destination : 2001:3:: PrefixLen: 64
Flag : D/L/- Cost : 10
Next Hop : Direct Interface: Vlan300
Destination : 2001:4::1 PrefixLen: 128
Flag : D/L/- Cost : 0
Next Hop : Direct Interface: Loop1
502
Flags: D-Direct, R-Added to Rib, L-Advertised in LSPs, U-Up/Down Bit Set
BFD for IPv6 IS-IS configuration example
Network requirements
•
Configure IPv6 IS-IS on Switch A and Switch B so that they can reach other.
•
Enable BFD on VLAN-interface 10 of Switch A and Switch B.
After the link between Switch B and the Layer-2 switch fails, BFD can quickly detect the failure and notify IPv6 IS-IS of the failure. Then Switch A and Switch B communicate through Switch C.
Figure 116 Network diagram
2001:1::/64
Switch A
Vlan-int10
Vlan-int11
BFD
L2 Switch
Vlan-int10
Switch B
2001:4::/64
Vlan-int13
Area 0
Vlan-int11 Vlan-int13
Switch C
Table 28 Interface and IP address assignment
Device
Switch A
Switch A
Switch B
Switch B
Switch C
Interface
Vlan-int10
Vlan-int11
Vlan-int10
Vlan-int13
Vlan-int11
IPv6 address
2001::1/64
2001:2::1/64
2001::2/64
2001:3::2/64
2001:2::2/64
Switch C
Configuration procedure
Vlan-int13
1. Configure IPv6 addresses for interfaces. (Details not shown.)
2. Configure IPv6 IS-IS:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] is-level level-1
[SwitchA-isis-1] network-entity 10.0000.0000.0001.00
[SwitchA-isis-1] address-family ipv6
[SwitchA-isis-1-ipv6] quit
[SwitchA-isis-1] quit
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] isis ipv6 enable 1
2001:3::1/64
503
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] isis ipv6 enable 1
[SwitchA-Vlan-interface11] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] is-level level-1
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] address-family ipv6
[SwitchB-isis-1-ipv6] quit
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] isis ipv6 enable 1
[SwitchB-Vlan-interface10] quit
[SwitchB] interface vlan-interface 13
[SwitchB-Vlan-interface13] isis ipv6 enable 1
[SwitchB-Vlan-interface13] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] isis 1
[SwitchC-isis-1] network-entity 10.0000.0000.0003.00
[SwitchC-isis-1] address-family ipv6
[SwitchC-isis-1-ipv6] quit
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 11
[SwitchC-Vlan-interface11] isis ipv6 enable 1
[SwitchC-Vlan-interface11] quit
[SwitchC] interface vlan-interface 13
[SwitchC-Vlan-interface13] isis ipv6 enable 1
[SwitchC-Vlan-interface13] quit
3. Configure BFD functions:
# Enable BFD and configure BFD parameters on Switch A.
[SwitchA] bfd session init-mode active
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] isis ipv6 bfd enable
[SwitchA-Vlan-interface10] bfd min-transmit-interval 500
[SwitchA-Vlan-interface10] bfd min-receive-interval 500
[SwitchA-Vlan-interface10] bfd detect-multiplier 7
[SwitchA-Vlan-interface10] return
# Enable BFD and configure BFD parameters on Switch B.
[SwitchB] bfd session init-mode active
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] isis ipv6 bfd enable
[SwitchB-Vlan-interface10] bfd min-transmit-interval 500
[SwitchB-Vlan-interface10] bfd min-receive-interval 500
[SwitchB-Vlan-interface10] bfd detect-multiplier 6
504
Verifying the configuration
# Display BFD session information on Switch A.
<SwitchA> display bfd session
Total Session Num: 1 Init Mode: Active
IPv6 Session Working Under Ctrl Mode:
Local Discr: 1441 Remote Discr: 1450
Source IP: FE80::20F:FF:FE00:1202 (link-local address of VLAN-interface 10 on
Switch A)
Destination IP: FE80::20F:FF:FE00:1200 (link-local address of VLAN-interface 10 on
Switch B)
Session State: Up Interface: Vlan10
Hold Time: 2319ms
# Display routes destined for 2001:4::0/64 on Switch A.
<SwitchA> display ipv6 routing-table 2001:4::0 64
Summary Count : 1
Destination: 2001:4::/64 Protocol : IS_L1
NextHop : FE80::20F:FF:FE00:1200 Preference: 15
Interface : Vlan10 Cost : 10
The output shows that Switch A and Switch B communicate through VLAN-interface 10. Then the link over VLAN-interface 10 fails.
# Display routes destined for 2001:4::0/64 on Switch A.
<SwitchA> display ipv6 routing-table 2001:4::0 64
Summary Count : 1
Destination: 2001:4::/64 Protocol : IS_L1
NextHop : FE80::BAAF:67FF:FE27:DCD0 Preference: 15
Interface : Vlan11 Cost : 20
The output shows that Switch A and Switch B communicate through VLAN-interface 11.
IPv6 IS-IS FRR configuration example
Network requirements
As shown in Figure 117 , Switch A, Switch B, and Switch C belong to the same IS-IS routing domain.
Configure IPv6 IS-IS FRR so that when the Link A fails, traffic can be switched to Link B immediately.
505
Figure 117 Network diagram
Switch C
Vlan
-int
100
Vlan
-int
101
Link B
Vlan
-int
100
Link A
Loop0
Switch A
Vlan-int200
Table 29 Interface and IP address assignment
Vlan
-int
101
Vlan-int200
Switch B
Loop0
Device
Switch A
Switch C
Interface IP address
Vlan-int100 1::1/64
Vlan-int200 2::1/64
Loop0 10::1/128
Vlan-int100 1::2/64
Device
Switch B
Interface IP address
Vlan-int101 3::1/64
Vlan-int200 2::2/64
Loop0 20::1/128
Vlan-int101 3::2/64
Configuration procedure
1. Configure IPv6 addresses for interfaces on the switches and enable IPv6 IS-IS. (Details not shown.)
2. Configure IPv6 IS-IS on the switches to make sure Switch A, Switch B, and Switch C can communicate with each other at Layer 3. (Details not shown.)
3. Configure IPv6 IS-IS FRR:
Enable IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation, or designate a backup next hop by using a referenced routing policy.
(Method 1.) Enable IPv6 IS-IS FRR to calculate a backup next hop through LFA calculation:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] isis 1
[SwitchA-isis-1] address-family ipv6
[SwitchA-isis-1-ipv6] fast-reroute lfa
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis 1
[SwitchB-isis-1] address-family ipv6
[SwitchB-isis-1-ipv6] fast-reroute lfa
(Method 2.) Enable IPv6 IS-IS FRR to designate a backup next hop by using a routing policy:
# Configure Switch A.
<SwitchA> system-view
[SwitchA] ipv6 prefix-list abc index 10 permit 20::1 128
[SwitchA] route-policy frr permit node 10
[SwitchA-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchA-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 100 backup-nexthop 1::2
506
[SwitchA-route-policy-frr-10] quit
[SwitchA] isis 1
[SwitchA-isis-1] address-family ipv6
[SwitchA-isis-1-ipv6] fast-reroute route-policy frr
[SwitchA-isis-1-ipv6] quit
[SwitchA-isis-1] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] ipv6 prefix-list abc index 10 permit 10::1 128
[SwitchB] route-policy frr permit node 10
[SwitchB-route-policy-frr-10] if-match ipv6 address prefix-list abc
[SwitchB-route-policy-frr-10] apply ipv6 fast-reroute backup-interface vlan-interface 101 backup-nexthop 3::2
[SwitchB-route-policy-frr-10] quit
[SwitchB] isis 1
[SwitchB-isis-1] address-family ipv6
[SwitchB-isis-1-ipv6] fast-reroute route-policy frr
[SwitchB-isis-1-ipv6] quit
[SwitchB-isis-1] quit
Verifying the configuration
# Display route 20::1/128 on Switch A to view the backup next hop information.
[SwitchA] display ipv6 routing-table 20::1 128 verbose
Summary count : 1
Destination: 20::1/128
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 00h27m45s
Cost: 10 Preference: 15
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0xa OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x24000005 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10041 OrigNextHop: FE80::34CD:9FF:FE2F:D02
Label: NULL RealNextHop: FE80::34CD:9FF:FE2F:D02
BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface100
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
# Display route 10::1/128 on Switch B to view the backup next hop information.
[SwitchB] display ipv6 routing-table 10::1 128 verbose
Summary count : 1
507
Destination: 10::1/128
Protocol: IS_L1
Process ID: 1
SubProtID: 0x1 Age: 00h33m23s
Cost: 10 Preference: 15
IpPre: N/A QosLocalID: N/A
Tag: 0 State: Active Adv
OrigTblID: 0xa OrigVrf: default-vrf
TableID: 0xa OrigAs: 0
NibID: 0x24000006 LastAs: 0
AttrID: 0xffffffff Neighbor: ::
Flags: 0x10041 OrigNextHop: FE80::34CC:E8FF:FE5B:C02
Label: NULL RealNextHop: FE80::34CC:E8FF:FE5B:C02
BkLabel: NULL BkNextHop: FE80::7685:45FF:FEAD:102
Tunnel ID: Invalid Interface: Vlan-interface200
BkTunnel ID: Invalid BkInterface: Vlan-interface101
FtnIndex: 0x0 TrafficIndex: N/A
Connector: N/A
508
Configuring IPv6 PBR
Overview
Policy-based routing (PBR) uses user-defined policies to route packets. A policy can specify the next hop for packets that match specific criteria such as ACLs.
A device forwards received packets using the following process:
1. The device uses PBR to forward matching packets.
2. If the packets do not match the PBR policy or the PBR-based forwarding fails, the device uses the routing table, excluding the default route, to forward the packets.
3. If the routing table-based forwarding fails, the device uses the default route to forward packets.
PBR includes local PBR and interface PBR.
•
Local PBR guides the forwarding of locally generated packets, such as the ICMP packets generated by using the ping command.
•
Interface PBR guides the forwarding of packets received on an interface only.
Policy
An IPv6 policy includes match criteria and actions to be taken on the matching packets. A policy can have one or multiple nodes as follows:
•
Each node is identified by a node number. A smaller node number has a higher priority.
•
A node contains if-match and apply clauses. An if-match clause specifies a match criterion, and an apply clause specifies an action.
•
A node has a match mode of permit or deny .
An IPv6 policy compares packets with nodes in priority order. If a packet matches the criteria on a node, it is processed by the action on the node. Otherwise, it goes to the next node for a match. If the packet does not match the criteria on any node, it is forwarded according to the routing table. if-match clause
IPv6 PBR supports the if-match acl clause, which sets an ACL match criterion.
You can specify only one if-match clause for each node. apply clause
IPv6 PBR supports the types of apply
clauses shown in Table 30 . You can specify multiple
apply clauses for a node, but some of them might not be executed. The following apply clauses determine the packet forwarding paths in a descending order:
• apply next-hop
• apply output-interface
Table 30 Priorities and meanings of apply clauses
Clause apply precedence apply next-hop and apply output-interface
Meaning
Sets an IP precedence.
Sets next hops and sets output interfaces.
Priority
This clause is always executed.
Only the apply next-hop clause is executed when both are configured.
509
Relationship between the match mode and clauses on the node
Does a packet match all the if-match clauses on the node?
Yes
Match mode
In permit mode
•
If the node is configured with apply clauses, IPv6 PBR executes the apply clauses on the node.
If the IPv6 PBR-based forwarding succeeds, IPv6
PBR does not compare the packet with the next node.
If the IPv6 PBR-based forwarding fails, IPv6 PBR does not compare the packet with the next node.
•
If the node is configured with no apply clauses, the packet is forwarded according to the routing table.
In deny mode
The packet is forwarded according to the routing table.
No
IPv6 PBR compares the packet with the next node.
A node that has no if-match clauses matches any packet.
IPv6 PBR compares the packet with the next node.
PBR and Track
PBR can work with the Track feature to dynamically adapt the availability status of an apply clause to the link status of a tracked next hop.
•
When the track entry associated with an object changes to Negative , the apply clause is invalid.
•
When the track entry changes to Positive or NotReady , the apply clause is valid.
For more information about Track-PBR collaboration, see High Availability Configuration Guide .
IPv6 PBR configuration task list
Tasks at a glance
(Required.) Configuring an IPv6 policy :
•
•
Setting match criteria for an IPv6 node
•
Configuring actions for an IPv6 node
(Required.) Configuring IPv6 PBR :
•
•
Configuring IPv6 interface PBR
510
Configuring an IPv6 policy
Creating an IPv6 node
Step
1. Enter system view.
Command system-view
2. Create an IPv6 policy or policy node, and enter IPv6 policy node view. ipv6 policy-based-route policy-name [ deny | permit ] node node-number
Setting match criteria for an IPv6 node
Remarks
N/A
By default, no IPv6 policy node is created.
Step Command
1. Enter system view. system-view
2. Enter IPv6 policy node view. ipv6 policy-based-route policy-name [ deny | permit ] node node-number
3. Set an ACL match criterion. if-match acl { ipv6 acl-number | name ipv6-acl-name }
Remarks
N/A
N/A
By default, no ACL match criterion is set.
NOTE:
If an ACL match criterion is defined, packets are compared with the ACL rules, and the permit or deny action and the time range of the specified ACL are ignored. If the specified ACL does not exist, no packet is matched.
Configuring actions for an IPv6 node
Step
1. Enter system view.
2. Enter IPv6 policy node view.
3. Set an IP precedence.
Command system-view ipv6 policy-based-route policy-name
[ deny | permit ] node node-number apply precedence { type | value }
4. Set next hops for permitted IPv6 packets. apply next-hop [ vpn-instance vpn-instance-name ] { ipv6-address
[ direct ] [ track track-entry-number ] }&<1-2>
5. Set output interfaces. apply output-interface { interface-type interface-number [ track track-entry-number ] }
Remarks
N/A
N/A
By default, no IP precedence is specified.
By default, no next hop is specified.
You can specify two next hops for backup by executing this command twice.
By default, no output interface is specified.
511
Configuring IPv6 PBR
Configuring IPv6 local PBR
Configure IPv6 PBR by applying a policy locally. IPv6 PBR uses the policy to guide the forwarding of locally generated packets. The specified policy must already exist. Otherwise, the IPv6 local PBR configuration fails.
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
IPv6 local PBR might affect local services, such as ping and Telnet. Do not configure IPv6 local PBR unless doing so is required.
To configure IPv6 local PBR:
Step
1. Enter system view.
2. Apply a policy locally.
Command system-view ipv6 local policy-based-route policy-name
Remarks
N/A
By default, no policy is locally applied.
Configuring IPv6 interface PBR
Configure IPv6 PBR by applying an IPv6 policy to an interface. IPv6 PBR uses the policy to guide the forwarding of IPv6 packets received on the interface. The specified policy must already exist.
Otherwise, the IPv6 interface PBR configuration fails.
You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.
You can apply a policy to multiple interfaces.
To configure IPv6 interface PBR:
Step Command
1. Enter system view. system-view
2. Enter interface view.
3. Apply an IPv6 policy to the interface.
Remarks
N/A interface interface-type interface-number N/A ipv6 policy-based-route policy-name
By default, no IPv6 policy is applied to the interface.
Displaying and maintaining IPv6 PBR
Execute display commands in any view and reset commands in user view.
Task
Display IPv6 PBR policy information.
Display IPv6 PBR configuration.
Command display ipv6 policy-based-route [ policy policy-name ] display ipv6 policy-based-route setup
(In standalone mode.) Display IPv6 local PBR configuration and statistics. display ipv6 policy-based-route local [ slot slot-number ]
512
Task
(In IRF mode.) Display IPv6 local PBR configuration and statistics.
(In standalone mode.) Display IPv6 interface
PBR configuration and statistics.
(In IRF mode.) Display IPv6 interface PBR configuration and statistics.
Clear IPv6 PBR statistics.
Command display ipv6 policy-based-route local [ chassis chassis-number slot slot-number ] display ipv6 policy-based-route interface interface-type interface-number [ slot slot-number ] display ipv6 policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ] reset ipv6 policy-based-route statistics [ policy
policy-name ]
IPv6 PBR configuration examples
Packet type-based IPv6 local PBR configuration example
Network requirements
As shown in Figure 118 , configure IPv6 PBR on Switch A to forward all TCP packets to the next hop
1::2. Switch A forwards other packets according to the routing table.
Figure 118 Network diagram
Switch A
Vlan-int10
1::1/64
Vlan-int10
1::2/64
Switch B
Vlan-int20
2::1/64
Vlan-int20
2::2/64
Switch C
Configuration procedure
1. Configure Switch A:
# Create VLAN 10 and VLAN 20.
<SwitchA> system-view
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchA] vlan 20
[SwitchA-vlan20] quit
# Configure the IPv6 addresses of VLAN-interface 10 and VLAN-interface 20.
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ipv6 address 1::1 64
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 20
[SwitchA-Vlan-interface20] ipv6 address 2::1 64
[SwitchA-Vlan-interface20] quit
# Configure ACL 3001 to match TCP packets.
[SwitchA] acl ipv6 advanced 3001
[SwitchA-acl-ipv6-adv-3001] rule permit tcp
[SwitchA-acl-ipv6-adv-3001] quit
# Configure Node 5 for policy aaa to forward TCP packets to next hop 1::2.
513
[SwitchA] ipv6 policy-based-route aaa permit node 5
[SwitchA-pbr6-aaa-5] if-match acl 3001
[SwitchA-pbr6-aaa-5] apply next-hop 1::2
[SwitchA-pbr6-aaa-5] quit
# Configure IPv6 local PBR by applying policy aaa to Switch A.
[SwitchA] ipv6 local policy-based-route aaa
2. Configure Switch B:
# Create VLAN 10.
<SwitchB> system-view
[SwitchB] vlan 10
[SwitchB-vlan10] quit
# Configure the IPv6 address of VLAN-interface 10.
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ipv6 address 1::2 64
3. Configure Switch C:
# Create VLAN 20.
<SwitchC> system-view
[SwitchC] vlan 20
[SwitchC-vlan20] quit
# Configure the IPv6 address of VLAN-interface 20.
[SwitchC] interface vlan-interface 20
[SwitchC-Vlan-interface20] ipv6 address 2::2 64
Verifying the configuration
# Telnet to Switch B on Switch A. The operation succeeds.
# Telnet to Switch C on Switch A. The operation fails.
# Ping Switch C from Switch A. The operation succeeds.
Telnet uses TCP and ping uses ICMP. The results show the following:
•
All TCP packets sent from Switch A are forwarded to the next hop 1::2.
•
Other packets are forwarded through VLAN-interface 20.
•
The IPv6 local PBR configuration is effective.
Packet type-based IPv6 interface PBR configuration example
Network requirements
As shown in Figure 119 , configure IPv6 PBR on Switch A to forward all TCP packets received on
VLAN-interface 11 to the next hop 1::2. Switch A forwards other IPv6 packets according to the routing table.
514
Figure 119 Network diagram
Switch B Switch C
Vlan-int10
1::2/64
Vlan-int20
2::2/64
Vlan-int10
1::1/64
Switch A
Vlan-int20
2::1/64
Vlan-int11
10::2/64
Subnet
10::1/64
Host A
10::3/64
Gateway: 10::2/64
Host B
Configuration procedure
1. Configure Switch A:
# Create VLAN 10 and VLAN 20.
<SwitchA> system-view
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchA] vlan 20
[SwitchA-vlan20] quit
# Configure RIPng.
[SwitchA] ripng 1
[SwitchA-ripng-1] quit
[SwitchA] interface vlan-interface 10
[SwitchA-Vlan-interface10] ipv6 address 1::1 64
[SwitchA-Vlan-interface10] ripng 1 enable
[SwitchA-Vlan-interface10] quit
[SwitchA] interface vlan-interface 20
[SwitchA-Vlan-interface20] ipv6 address 2::1 64
[SwitchA-Vlan-interface20] ripng 1 enable
[SwitchA-Vlan-interface20] quit
# Configure ACL 3001 to match TCP packets.
[SwitchA] acl ipv6 advanced 3001
[SwitchA-acl-ipv6-adv-3001] rule permit tcp
[SwitchA-acl-ipv6-adv-3001] quit
# Configure Node 5 for policy aaa to forward TCP packets to next hop 1::2.
[SwitchA] ipv6 policy-based-route aaa permit node 5
[SwitchA-pbr6-aaa-5] if-match acl 3001
[SwitchA-pbr6-aaa-5] apply next-hop 1::2
515
[SwitchA-pbr6-aaa-5] quit
# Configure IPv6 interface PBR by applying policy aaa to VLAN-interface 11.
[SwitchA] interface vlan-interface 11
[SwitchA-Vlan-interface11] ipv6 address 10::2 64
[SwitchA-Vlan-interface11] undo ipv6 nd ra halt
[SwitchA-Vlan-interface11] ripng 1 enable
[SwitchA-Vlan-interface11] ipv6 policy-based-route aaa
2. Configure Switch B:
# Create VLAN 10.
<SwitchB> system-view
[SwitchB] vlan 10
[SwitchB-vlan10] quit
# Configure RIPng.
[SwitchB] ripng 1
[SwitchB-ripng-1] quit
[SwitchB] interface vlan-interface 10
[SwitchB-Vlan-interface10] ipv6 address 1::2 64
[SwitchB-Vlan-interface10] ripng 1 enable
[SwitchB-Vlan-interface10] quit
3. Configure Switch C:
# Create VLAN 20.
<SwitchC> system-view
[SwitchC] vlan 20
[SwitchC-vlan20] quit
# Configure RIPng.
[SwitchC] ripng 1
[SwitchC-ripng-1] quit
[SwitchC] interface vlan-interface 20
[SwitchC-Vlan-interface20] ipv6 address 2::2 64
[SwitchC-Vlan-interface20] ripng 1 enable
[SwitchC-Vlan-interface20] quit
Verifying the configuration
# Enable IPv6 and configure the IPv6 address 10::3 for Host A.
C:\>ipv6 install
Installing...
Succeeded.
C:\>ipv6 adu 4/10::3
# On Host A, Telnet to Switch B that is directly connected to Switch A. The operation succeeds.
# On Host A, Telnet to Switch C that is directly connected to Switch A. The operation fails.
# Ping Switch C from Host A. The operation succeeds.
Telnet uses TCP, and ping uses ICMP. The results show the following:
•
All TCP packets arriving on VLAN-interface 11 of Switch A are forwarded to next hop 1::2.
•
Other packets are forwarded through VLAN-interface 20.
•
The IPv6 interface PBR configuration is effective.
516
Configuring routing policies
Overview
Routing policies control routing paths by filtering and modifying routing information. This chapter describes both IPv4 and IPv6 routing policies.
Routing policies can filter advertised, received, and redistributed routes, and modify attributes for specific routes.
To configure a routing policy:
1. Configure filters based on route attributes, such as destination address and the advertising router's address.
2. Create a routing policy and apply filters to the routing policy.
Filters
Routing policies can use the following filters to match routes.
ACL
ACLs include IPv4 ACLs and IPv6 ACLs. An ACL can match the destination or next hop of routes.
For more information about ACLs, see ACL and QoS Configuration Guide .
IP prefix list
IP prefix lists include IPv4 prefix lists and IPv6 prefix lists.
An IP prefix list matches the destination address of routes. You can use the gateway option to receive routes only from specific routers. For more information about the gateway option, see
An IP prefix list can contain multiple items that specify prefix ranges. Each destination IP address prefix of a route is compared with these items in ascending order of their index numbers. A prefix matches the IP prefix list if it matches one item in the list.
AS path list
An AS path list matches the AS_PATH attribute of BGP routes.
For more information about AS path lists, see " Configuring BGP ."
Community list
A community list matches the COMMUNITY attribute of BGP routes.
For more information about community lists, see " Configuring BGP ."
Extended community list
MAC list
An extended community list matches the extended community attribute (Route-Target for VPN and
Site of Origin) of BGP routes.
For more information about extended community lists, see MPLS Configuration Guide .
A MAC list matches MAC addresses contained in EVI IS-IS packets.
A MAC list can contain multiple items that specify MAC address ranges. Each MAC address entry in an EVI IS-IS packet is compared with these items in ascending order of their index numbers. A MAC address entry matches the MAC list if it matches one item in the list.
517
Routing policy
A routing policy can contain multiple nodes, which are in a logical OR relationship. A node with a smaller number is matched first. A route matches the routing policy if it matches one node (except the node configured with the continue clause) in the routing policy.
Each node has a match mode of permit or deny .
• permit —Specifies the permit match mode for a routing policy node. If a route meets all the if-match clauses of the node, it is handled by the apply clauses of the node. The route is not compared with the next node unless the continue clause is configured. If a route does not meet all the if-match clauses of the node, it is compared with the next node.
• deny —Specifies the deny match mode for a routing policy node. The apply and continue clauses of a deny node are never executed. If a route meets all the if-match clauses of the node, it is denied without being compared with the next node. If a route does not meet all the if-match clauses of the node, it is compared with the next node.
A node can contain a set of if-match , apply , and continue clauses.
• if-match clauses—Specify the match criteria that match the attributes of routes. The if-match clauses are in a logical AND relationship. A route must meet all the if-match clauses to match the node.
• apply clauses—Specify the actions to be taken on permitted routes, such as modifying a route attribute.
• continue clause—Specifies the next node. A route that matches the current node (permit node) must match the specified next node in the same routing policy. The continue clause combines the if-match and apply clauses of the two nodes to improve flexibility of the routing policy.
Follow these guidelines when you configure if-match , apply , and continue clauses:
•
If you only want to filter routes, do not configure apply clauses.
•
If you do not configure any if-match clauses for a permit node, the node will permit all routes.
•
Configure a permit node containing no if-match or apply clauses following multiple deny nodes to allow unmatched routes to pass.
Configuring filters
Configuration prerequisites
Determine the IP prefix list name, matching address range, and community list number.
Configuring an IP prefix list
Configuring an IPv4 prefix list
If all the items are set to deny mode, no routes can pass the IPv4 prefix list. To permit unmatched
IPv4 routes, you must configure the permit 0.0.0.0 0 less-equal 32 item following multiple deny items.
To configure an IPv4 prefix list:
Step Command
1. Enter system view. system-view
Remarks
N/A
518
Step
2. Configure an IPv4 prefix list.
Command ip prefix-list prefix-list-name [ index index-number ]
{ deny | permit } ip-address mask-length
[ greater-equal min-mask-length ] [ less-equal max-mask-length ]
Remarks
By default, no IPv4 prefix lists exist.
Configuring an IPv6 prefix list
If all items are set to deny mode, no routes can pass the IPv6 prefix list. To permit unmatched IPv6 routes, you must configure the permit :: 0 less-equal 128 item following multiple deny items.
To configure an IPv6 prefix list:
Remarks
N/A
Step Command
1. Enter system view. system-view
2. Configure an IPv6 prefix list. ipv6 prefix-list prefix-list-name [ index index-number ] { deny | permit } ipv6-address
{ prefix-length | inverse inverse-prefix-length
[ greater-equal min-prefix-length ] [ less-equal max-prefix-length ] }
By default, no IPv6 prefix lists exist.
Configuring an AS path list
You can configure multiple items for an AS path list that is identified by a number. The relationship between the items is logical OR. A route matches the AS path list if it matches one item in the list.
To configure an AS path list:
Step
1. Enter system view.
Command system-view
2. Configure an AS path list. ip as-path as-path-number { deny | permit } regular-expression
Remarks
N/A
By default, no AS path lists exist.
Configuring a community list
You can configure multiple items for a community list that is identified by a number. The relationship between the items is logical OR. A route matches the community list if it matches one item in the list.
To configure a community list:
Step
1. Enter system view.
2. Configure a community list.
Command system-view
•
Configure a basic community list: ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit }
[ community-number &<1-32> | aa:nn &<1-32> ]
[ internet | no-advertise | no-export | no-export-subconfed ] *
•
Configure an advanced community list: ip community-list { adv-comm-list-num | advanced adv-comm-list-name } { deny | permit } regular-expression
Remarks
N/A
By default, no community lists exist.
519
Configuring an extended community list
You can configure multiple items for an extended community list that is identified by a number. The relationship between the items is logical OR. A route matches the extended community list if it matches one item in the list.
To configure an extended community list:
Step
1. Enter system view.
2. Configure an extended community list.
Command system-view ip extcommunity-list ext-comm-list-number
{ deny | permit } { rt route-target | soo site-of-origin }&<1-32>
Remarks
N/A
By default, no extended community lists exist.
Configuring a MAC list
If all the items are set to deny mode, no MAC address entries can pass the MAC list. To permit unmatched MAC address entries, you must configure the permit 0-0-0 0 item following multiple deny items.
The MAC list filter applies only to EVI IS-IS. For information about EVI IS-IS, see EVI Configuration
Guide .
To configure a MAC list:
Step Command
1. Enter system view. system-view
2. Configure a MAC list. mac-list mac-list-name [ index index-number ]
{ deny | permit } mac-address [ mask-length ]
Remarks
N/A
By default, no MAC lists exist.
Configuring a routing policy
Configuration prerequisites
Configure filters and routing protocols, and determine the routing policy name, node numbers, match criteria, and the attributes to be modified.
Creating a routing policy
For a routing policy that has more than one node, configure a minimum of one permit node. A route that does not match any node cannot pass the routing policy. If all the nodes are in deny mode, no routes can pass the routing policy.
To create a routing policy:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Create a routing policy and a node, and enter routing policy node view. route-policy route-policy-name { deny | permit } node node-number
By default, no routing policies exist.
520
Configuring if-match clauses
You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit node, all routes can pass the node. If no if-match clause is specified for a deny node, no routes can pass the node.
The if-match clauses of a routing policy node have a logical AND relationship. A route must meet all if-match clauses before it can be executed by the apply clauses of the node. If an if-match command exceeds the maximum length, multiple if-match clauses of the same type are generated.
These clauses have a logical OR relationship. A route only needs to meet one of them.
To configure if-match clauses:
Step
1. Enter system view.
Command system-view
Remarks
N/A
2. Enter routing policy node view. route-policy route-policy-name
{ deny | permit } node node-number
N/A
3. Match routes whose destination, next hop, or source address matches an ACL or prefix list.
•
Match IPv4 routes whose destination, next hop, or source address matches an ACL or
IPv4 prefix list: if-match ip { address | next-hop | route-source } { acl ipv4-acl-number | prefix-list prefix-list-name }
•
Match IPv6 routes whose destination, next hop, or source address matches an ACL or
IPv6 prefix list: if-match ipv6 { address | next-hop | route-source } { acl ipv6-acl-number | prefix-list prefix-list-name }
By default, no ACL or prefix list match criterion is configured.
If the ACL used by an if-match clause does not exist, the clause is always matched. If no rules of the specified ACL are matched or the match rules are inactive, the clause is not matched.
The ACL specified in an if-match clause must be a non-VPN ACL.
All IPv6 routes match a node if the if-match clauses of the node use only IPv4 ACLs.
All IPv4 routes match a node if the if-match clauses of the node use only IPv6 ACLs.
4. Match BGP routes whose
AS_PATH attribute matches a specified AS path list. if-match as-path as-path-number &<1-32>
By default, no AS path match criterion is configured.
5. Match BGP routes whose
COMMUNITY attribute matches a specified community list. if-match community
{ { basic-community-list-number | name comm-list-name }
[ whole-match ] | adv-community-list-number }&<1-32
>
By default, no COMMUNITY match criterion is matched.
6. Match routes having the specified cost.
7. Match BGP routes whose extended community attribute matches a specified extended community list. if-match cost cost-value if-match extcommunity ext-comm-list-number &<1-32>
By default, no cost match criterion is configured.
By default, no extended community list match criterion is configured.
521
Step
8. Match routes having the specified output interface.
9. Match BGP routes having the specified local preference.
10. Match MAC addresses in EVI
IS-IS packets.
11. Match routes having MPLS labels.
12. Match routes having the specified route type.
13. Match IGP routes having the specified tag value.
14. Match VLANs in EVI IS-IS packets.
Command if-match interface { interface-type interface-number }&<1-16>
Remarks
By default, no output interface match criterion is configured.
This command is not supported by BGP. if-match local-preference
preference if-match mac-list mac-list-name if-match mpls-label
By default, no local preference is configured for
BGP routes.
By default, no MAC list match criterion is configured.
The MAC list match criterion applies only to EVI IS-IS. For information about EVI IS-IS, see EVI Configuration Guide .
By default, no MPLS label match criterion is configured. if-match route-type
{ external-type1 | external-type1or2 | external-type2
| internal | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 } *
By default, no route type match criterion is configured. if-match tag if-match vlan tag-value
vlan-list
By default, no tag match criterion is configured.
By default, no VLAN match criterion is configured.
The VLAN match criterion applies only to EVI IS-IS. For information about EVI IS-IS, see EVI Configuration Guide .
Configuring apply clauses
Except for the apply commands used for setting the next hop for IPv4 and IPv6 routes, all apply commands are the same for IPv4 and IPv6 routing.
To configure apply clauses:
Step
1. Enter system view.
2. Enter routing policy node view.
Command system-view route-policy route-policy-name { deny | permit } node node-number
Remarks
N/A
N/A
3. Set the AS_PATH attribute for
BGP routes.
4. Delete the specified
COMMUNITY attribute for
BGP routes. apply as-path as-number &<1-32> [ replace ]
By default, no AS_PATH attribute is set for BGP routes. apply comm-list
{ comm-list-number | comm-list-name } delete
By default, no COMMUNITY attribute is deleted for BGP routes.
522
Step
5. Set the specified
COMMUNITY attribute for
BGP routes.
6. Set a cost for routes.
7. Set a cost type for routes.
Command Remarks apply community { none | additive |
{ community-number &<1-32> | aa:nn &<1-32> | internet | no-advertise | no-export | no-export-subconfed } *
[ additive ] }
By default, no community attribute is set for BGP routes. apply cost [ + | - ] cost-value By default, no cost is set for routes. apply cost-type { external | internal | type-1 | type-2 }
By default, no cost type is set for routes.
8.
9.
Set the extended community attribute for BGP routes.
Set the next hop for routes. apply extcommunity { rt route-target }&<1-32>
[ additive ]
•
Set the next hop for IPv4 routes: apply ip-address next-hop ip-address
[ public | vpn-instance vpn-instance-name ]
•
Set the next hop for IPv6 routes: apply ipv6 next-hop
ipv6-address
By default, no extended community attribute is set for BGP routes.
By default, no next hop is set for
IPv4 or IPv6 routes.
The apply ip-address next-hop and apply ipv6 next-hop commands do not apply to redistributed IPv4 and IPv6 routes.
10.
17.
18.
Set an IP precedence for matching routes.
Set a prefix priority.
Set a local QoS ID for matching routes. apply ip-precedence { value | clear }
By default, no IP precedence is set.
11. Redistribute routes to the specified IS-IS level. apply isis { level-1 | level-1-2
| level-2 }
By default, routes are not redistributed into the specified IS-IS level.
12. Set a local preference for BGP routes. apply local-preference
preference
By default, no local preference is set for BGP routes.
13. Set MPLS labels. apply mpls-label By default, no MPLS label is set.
14. Set the ORIGIN attribute for
BGP routes. apply origin { egp as-number
| igp | incomplete }
By default, no ORIGIN attribute is set for BGP routes.
15. Set a preference.
16. Set a preferred value for BGP routes. apply preference preference By default, no preference is set. apply preferred-value
preferred-value
By default, no preferred value is set for BGP routes. apply prefix-priority { critical
| high | medium }
By default, no prefix priority is set, which means the prefix priority is low. apply qos-local-id
{ local-id-value | clear }
By default, no local QoS ID is set.
19.
20.
Set a tag value for IGP routes.
Set a traffic index for BGP routes.
apply tag tag-value apply traffic-index clear }
{ value |
By default, no tag value is set for
IGP routes.
By default, no traffic index is set for
BGP routes.
523
Step
21. Set a backup link for fast reroute (FRR).
Command
•
Set an IPv4 backup link for FRR: apply fast-reroute
{ backup-interface interface-type interface-number
[ backup-nexthop ip-address ] | backup-nexthop ip-address }
•
Set an IPv6 backup link for FRR: apply ipv6 fast-reroute
{ backup-interface interface-type interface-number
[ backup-nexthop ipv6-address ] |
backup-nexthop ipv6-address }
Remarks
By default, no backup link is set for
FRR.
Configuring the continue clause
Follow these guidelines when you configure the continue clause to combine multiple nodes:
•
If you configure an apply clause that sets different attribute values on all the nodes, the apply clause of the node configured most recently takes effect.
•
If you configure the following apply clauses on all the nodes, the apply clause of each node takes effect:
apply as-path without the replace keyword. apply cost with the + or – keyword. apply community with the additive keyword.
apply extcommunity with the additive keyword.
•
The apply comm-list delete clause configured on the current node cannot delete the community attributes set by the apply community clauses of the preceding nodes.
To configure the continue clause:
Step
1. Enter system view.
2. Enter routing policy node view.
Command system-view route-policy route-policy-name
{ deny | permit } node node-number
Remarks
N/A
N/A
3. Specify the next node to be matched. continue [ node-number ]
By default, no continue clause is configured.
The specified next node must have a larger number than the current node.
Displaying and maintaining the routing policy
Execute display commands in any view and reset commands in user view.
524
Task
Display BGP AS path list information.
Display BGP community list information.
Display BGP extended community list information.
Display IPv4 prefix list statistics.
Display IPv6 prefix list statistics.
Display MAC list statistics.
Display routing policy information.
Clear IPv4 prefix list statistics.
Clear IPv6 prefix list statistics.
Clear MAC list statistics.
Command display ip as-path [ as-path-number ] display ip community-list [ basic-community-list-number | adv-community-list-number | name comm-list-name ] display ip extcommunity-list [ ext-comm-list-number ] display ip prefix-list [ name prefix-list-name ] display ipv6 prefix-list [ name prefix-list-name ] display mac-list [ name mac-list-name ] display route-policy [ name route-policy-name ] reset ip prefix-list [ prefix-list-name ] reset ipv6 prefix-list [ prefix-list-name ] reset mac-list [ mac-list-name ]
Routing policy configuration examples
Routing policy configuration example for IPv4 route redistribution
Network requirements
As shown in Figure 120 , Switch B exchanges routing information with Switch A by using OSPF and
with Switch C by using IS-IS.
On Switch B, enable route redistribution from IS-IS to OSPF. Use a routing policy to set the cost of route 172.17.1.0/24 to 100 and the tag of route 172.17.2.0/24 to 20.
Figure 120 Network diagram
OSPF
IS-IS
Vlan-int100
192.168.1.2/24
Switch B
Vlan-int200
192.168.2.2/24
Vlan-int201
172.17.1.1/24
Vlan-int100
192.168.1.1/24
Vlan-int200
192.168.2.1/24
Vlan-int202
172.17.2.1/24
Switch A Switch C
Vlan-int203
172.17.3.1/24
Configuration procedure
1. Specify IP addresses for interfaces. (Details not shown.)
2. Configure IS-IS:
# Configure Switch C.
<SwitchC> system-view
525
[SwitchC] isis
[SwitchC-isis-1] is-level level-2
[SwitchC-isis-1] network-entity 10.0000.0000.0001.00
[SwitchC-isis-1] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] isis enable
[SwitchC-Vlan-interface200] quit
[SwitchC] interface vlan-interface 201
[SwitchC-Vlan-interface201] isis enable
[SwitchC-Vlan-interface201] quit
[SwitchC] interface vlan-interface 202
[SwitchC-Vlan-interface202] isis enable
[SwitchC-Vlan-interface202] quit
[SwitchC] interface vlan-interface 203
[SwitchC-Vlan-interface203] isis enable
[SwitchC-Vlan-interface203] quit
# Configure Switch B.
<SwitchB> system-view
[SwitchB] isis
[SwitchB-isis-1] is-level level-2
[SwitchB-isis-1] network-entity 10.0000.0000.0002.00
[SwitchB-isis-1] quit
[SwitchB] interface vlan-interface 200
[SwitchB-Vlan-interface200] isis enable
[SwitchB-Vlan-interface200] quit
3. Configure OSPF and route redistribution:
# Configure OSPF on Switch A.
<SwitchA> system-view
[SwitchA] ospf
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
# On Switch B, configure OSPF and enable route redistribution from IS-IS to OSPF.
[SwitchB] ospf
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] import-route isis 1
[SwitchB-ospf-1] quit
# Display the OSPF routing table on Switch A to view redistributed routes.
[SwitchA] display ospf routing
OSPF Process 1 with Router ID 192.168.1.1
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
526
192.168.1.0/24 1 Stub 192.168.1.1 192.168.1.1 0.0.0.0
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
172.17.1.0/24 1 Type2 1 192.168.1.2 192.168.2.2
172.17.2.0/24 1 Type2 1 192.168.1.2 192.168.2.2
172.17.3.0/24 1 Type2 1 192.168.1.2 192.168.2.2
Total Nets: 4
Intra Area: 1 Inter Area: 0 ASE: 3 NSSA: 0
4. Configure filtering lists:
# Configure IPv4 basic ACL 2002 to permit route 172.17.2.0/24.
[SwitchB] acl basic 2002
[SwitchB-acl-ipv4-basic-2002] rule permit source 172.17.2.0 0.0.0.255
[SwitchB-acl-ipv4-basic-2002] quit
# Configure IP prefix list prefix-a to permit route 172.17.1.0/24.
[SwitchB] ip prefix-list prefix-a index 10 permit 172.17.1.0 24
5. Configure a routing policy.
[SwitchB] route-policy isis2ospf permit node 10
[SwitchB-route-policy-isis2ospf-10] if-match ip address prefix-list prefix-a
[SwitchB-route-policy-isis2ospf-10] apply cost 100
[SwitchB-route-policy-isis2ospf-10] quit
[SwitchB] route-policy isis2ospf permit node 20
[SwitchB-route-policy-isis2ospf-20] if-match ip address acl 2002
[SwitchB-route-policy-isis2ospf-20] apply tag 20
[SwitchB-route-policy-isis2ospf-20] quit
[SwitchB] route-policy isis2ospf permit node 30
[SwitchB-route-policy-isis2ospf-30] quit
6. Apply the routing policy to route redistribution:
# On Switch B, enable route redistribution from IS-IS to OSPF and apply the routing policy.
[SwitchB] ospf
[SwitchB-ospf-1] import-route isis 1 route-policy isis2ospf
[SwitchB-ospf-1] quit
# Display the OSPF routing table on Switch A.
[SwitchA] display ospf routing
OSPF Process 1 with Router ID 192.168.1.1
Routing Tables
Routing for Network
Destination Cost Type NextHop AdvRouter Area
192.168.1.0/24 1 Transit 192.168.1.1 192.168.1.1 0.0.0.0
Routing for ASEs
Destination Cost Type Tag NextHop AdvRouter
172.17.1.0/24 100 Type2 1 192.168.1.2 192.168.2.2
172.17.2.0/24 1 Type2 20 192.168.1.2 192.168.2.2
172.17.3.0/24 1 Type2 1 192.168.1.2 192.168.2.2
527
Total Nets: 4
Intra Area: 1 Inter Area: 0 ASE: 3 NSSA: 0
The output shows that the cost of route 172.17.1.0/24 is 100 and the tag of route 172.17.2.0/24 is 20.
Routing policy configuration example for IPv6 route redistribution
Network requirements
•
Run RIPng on Switch A and Switch B.
•
Configure three static routes on Switch A.
•
On Switch A, apply a routing policy to redistribute static routes 20::/32 and 40::/32 and deny route 30::/32.
Figure 121 Network diagram
20::/32
30::/32
40::/32
Vlan-int200
11::1/32
Vlan-int100
10::1/32
Vlan-int100
10::2/32
Switch A
Configuration procedure
Switch B
1. Configure Switch A:
# Configure IPv6 addresses for VLAN-interface 100 and VLAN-interface 200.
<SwitchA> system-view
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ipv6 address 10::1 32
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 200
[SwitchA-Vlan-interface200] ipv6 address 11::1 32
[SwitchA-Vlan-interface200] quit
# Enable RIPng on VLAN-interface 100.
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] ripng 1 enable
[SwitchA-Vlan-interface100] quit
# Configure three static routes with next hop 11::2, and make sure the static routes are active.
[SwitchA] ipv6 route-static 20:: 32 11::2
[SwitchA] ipv6 route-static 30:: 32 11::2
[SwitchA] ipv6 route-static 40:: 32 11::2
# Configure a routing policy.
[SwitchA] ipv6 prefix-list a index 10 permit 30:: 32
[SwitchA] route-policy static2ripng deny node 0
[SwitchA-route-policy-static2ripng-0] if-match ipv6 address prefix-list a
[SwitchA-route-policy-static2ripng-0] quit
528
[SwitchA] route-policy static2ripng permit node 10
[SwitchA-route-policy-static2ripng-10] quit
# Enable RIPng and apply the routing policy to static route redistribution.
[SwitchA] ripng
[SwitchA-ripng-1] import-route static route-policy static2ripng
2. Configure Switch B:
# Configure the IPv6 address for VLAN-interface 100.
<SwitchB> system-view
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ipv6 address 10::2 32
# Enable RIPng.
[SwitchB] ripng
[SwitchB-ripng-1] quit
# Enable RIPng on VLAN-interface 100.
[SwitchB] interface vlan-interface 100
[SwitchB-Vlan-interface100] ripng 1 enable
[SwitchB-Vlan-interface100] quit
Verifying the configuration
# Display the RIPng routing table on Switch B.
[SwitchB] display ripng 1 route
Route Flags: A - Aging, S - Suppressed, G - Garbage-collect
----------------------------------------------------------------
Peer FE80::7D58:0:CA03:1 on Vlan-interface 100
Destination 10::/32,
via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 18 secs
Destination 20::/32,
via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 8 secs
Destination 40::/32,
via FE80::7D58:0:CA03:1, cost 1, tag 0, A, 3 secs
529
Configuring DCN
Overview
Data communication network (DCN) is built for the network management system (NMS) to implement operation, administration, and maintenance (OAM) on the network elements (NEs).
On large-scaled networks with DCN configured, the NMS remotely manages and controls all NEs through the gateway network element (GNE), which reduces operation and maintenance costs.
On the DCN network, all NEs must operate in Area 0 of OSPF process 65535.
Basic concepts
A DCN network includes the following basic elements:
•
NE —A network device managed by the NMS on the DCN network.
•
GNE —The NE that is directly connected to the NMS. The NSM communicates with the GNE at the network layer or application layer and manages the NEs through the GNE.
•
NE table —Stores the NE ID-to-NE IP mappings for each NE in the DCN domain. After DCN is enabled, an NE encapsulates its NE ID and NE IP in a Type-10 Opaque LSA. It floods the LSA to synchronize the mappings with other NEs in the DCN domain. The NE IP in the Type-10
Opaque LSA might be inconsistent with the NE's router ID when DCN is enabled on an OSPF network. Devices from other vendors will fail to identify the NE. To avoid this problem, make sure the following requirements are met:
Change the router ID by modifying the NE IP. Do not change the default IP address of the
DCN's loopback interface.
Do not associate other loopback interfaces to the DCN VPN instance.
Basic features
GNE
The GNE allows the NMS to access NEs on the DCN network. The GNE provides the NE ID-to-NE
IP mappings of all NEs for the Telnet users to access the target NE remotely.
NE search
The NE search feature allows the NMS to search for all NEs that are connected to the GNE. With this feature, the GNE can report information about all NEs in its NE table and the GNE itself to the NMS.
Automatic report
The automatic report feature enables the GNE to automatically report online or offline events of NEs to the NMS.
DCN configuration task list
Tasks at a glance
(Optional.) Configuring the NE ID and NE IP
(Required.) Configuring DCN VPN
530
Tasks at a glance
(Optional.) Enabling the automatic report feature
(Optional.) Configuring the source MAC address of LLDP frames
(Required.) Advertising the LLDP management address
Enabling DCN
After DCN is enabled, the device assigns an NE IP to the loopback interface with the largest interface number and uses the interface for communication. The NE IP is specified as the management address and advertised in an LLDP frame. For more information about LLDP, see Layer 2—LAN
Switching Configuration Guide .
To enable DCN:
Step
1. Enter system view.
2. Enable DCN and enter
DCN view.
Command system-view dcn
Remarks
N/A
By default, DCN is disabled.
Configuring the NE ID and NE IP
Typically an NE automatically generates an NE IP according to its NE ID. The automatically generated NE IP changes when the NE ID changes. When you replan your network or an NE ID conflict occurs, you can manually configure the NE ID and NE IP. The manually configured NE IP does not change when the NE ID changes.
To configure the NE ID and NE IP:
Step
1. Enter system view.
2. Enter DCN view.
3. Configure the NE ID.
4. Configure the NE IP.
Command system-view dcn
ne-id id-number
ne-ip ip-address { mask-length | mask }
Remarks
N/A
N/A
By default, the NE ID is automatically generated by using the 24 low-order bits of the bridge
MAC address.
By default, the NE IP is automatically generated by using
129 as the eight high-order bits and the NE ID as the rest 16 bits. The mask length is 32.
Configuring DCN VPN
Perform this task to ensure the independence of DCN services. For more information about VPN instances, see MPLS Configuration Guide .
To configure DCN VPN:
531
Step
1. Enter system view.
2. Create a VPN instance and enter its view.
3. Quit VPN instance view.
4. Create a loopback interface and enter its view.
5. Associate the loopback interface with a VPN instance.
Command system-view
ip vpn-instance vpn-instance-name quit interface loopback interface-number ip binding vpn-instance vpn-instance-name
Remarks
N/A
By default, no VPN instances exist.
N/A
By default, no loopback interfaces exist.
By default, the loopback interface is not associated with a VPN instance.
Enabling the automatic report feature
Perform this task to enable the GNE to automatically report online or offline events of NEs to the
NMS.
To enable the automatic report feature:
Step
1. Enter system view.
2. Enter DCN view.
3. Enable the automatic report feature.
Command system-view dcn auto-report
Remarks
N/A
N/A
By default, the automatic report feature is disabled.
Configuring the source MAC address of LLDP frames
Perform this task to configure the MAC address of the subinterface that runs Dot1q termination in the specified VLAN as the source MAC address of LLDP frames. For more information about LLDP, see
Layer 2—LAN Switching Configuration Guide .
Step
1. Enter system view.
2. Enter Layer 3 Ethernet interface view.
3. Configure the MAC address of the Dot1q termination-enabled subinterface in the specified VLAN as the source MAC address of
LLDP frames.
Command system-view
Remarks
N/A
interface interface-type interface-number N/A lldp source-mac vlan vlan-id
By default, the MAC address of the current Ethernet interface is specified as the source MAC address of LLDP frames.
532
Advertising the LLDP management address
An NE on the DCN network learns the MAC address of its neighbor through LLDP. Perform this task to enable an NE to advertise the IP address of the specified loopback interface (management address) for ARP entry learning. For more information about LLDP, see Layer 2—LAN Switching
Configuration Guide .
Remarks
N/A
Step Command
1. Enter system view.
system-view
2. Enter interface view.
3. Advertise the
LLDP management address.
interface interface-type interface-number lldp tlv-enable basic-tlv management-address-tlv [ ip-address | interface loopback interface-number ]
N/A
By default, the LLDP management address is not advertised.
Enabling the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port receives an LLDP frame
With this feature enabled, the system performs the following operations when an interface receives an LLDP frame carrying a management address TLV in IPv4 format:
•
Generates an ARP entry that contains the management address and the source MAC address of the frame.
•
Issues the ARP entry to the Layer 3 subinterface associated with the specified VLAN ID in
Dot1q termination.
For more information about LLDP, see Layer 2—LAN Switching Configuration Guide .
To enable the system to issue the generated ARP entry to a Layer 3 Ethernet subinterface after a port receives an LLDP frame:
Step
1. Enter system view.
2. Enter Layer 3 Ethernet subinterface view.
Command system-view
Remarks
N/A
interface interface-type interface-number N/A
3. Enable the system to issue the generated
ARP entry to an interface after a port receives an LLDP frame. lldp management-address arp-learning vlan vlan-id
By default, the system does not issue an ARP entry to interfaces after a port receives an LLDP frame.
The vlan-id argument specifies the VLAN ID associated with a
Layer 3 Ethernet subinterface in
Dot1q termination.
533
DCN configuration examples
Network requirements
As shown in Figure 122 , the GNE, Device A, and Device B run DCN in the same VPN instance. The
NMS uses SNMP to manage the GNE, and the GNE automatically sends notifications to the NMS to report online or offline events of NEs.
Figure 122 Network diagram
Device B
GNE
GE
1/0
/1
GE
1/0
/1
GE
1/0
/2
GE
1/0
/2
GE1/0/2
GE1/0/1
NMS
Device A
Configuration procedure
1. Configure the GNE:
# Enable SNMP on the GNE. (Details not shown. For more information, see Network
Management and Monitoring Configuration Guide .)
# Enable DCN, configure the NE ID as 100001 and NE IP as 11.1.1.1/32, and enable the automatic report feature.
<GNE> system-view
[GNE] dcn
[GNE-dcn] ne-id 100001
[GNE-dcn] ne-ip 11.1.1.1 32
[GNE-dcn] auto-report
[GNE-dcn] quit
# Create a VPN instance named dcn_vpn .
[GNE] ip vpn-instance dcn_vpn
[GNE-vpn-instance-dcn_vpn] quit
# Create interface Loopback 1023, and associate it with VPN instance dcn_vpn .
[GNE] interface loopback 1023
[GNE-LoopBack1023] ip binding vpn-instance dcn_vpn
[GNE-LoopBack1023] quit
# Enable LLDP globally.
[GNE] lldp global enable
# Enable the nearest bridge agents on GigabitEthernet 1/0/1 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[GNE] interface gigabitethernet 1/0/1
[GNE-GigabitEthernet1/0/1] port link-mode route
[GNE-GigabitEthernet1/0/1] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
534
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/1 receives an LLDP frame.
[GNE-GigabitEthernet1/0/1] lldp management-address arp-learning vlan 4094
[GNE-GigabitEthernet1/0/1] quit
# Enable the nearest bridge agents on GigabitEthernet 1/0/2 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[GNE] interface gigabitethernet 1/0/2
[GNE-GigabitEthernet1/0/2] port link-mode route
[GNE-GigabitEthernet1/0/2] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/2 receives an LLDP frame.
[GNE-GigabitEthernet1/0/2] lldp management-address arp-learning vlan 4094
[GNE-GigabitEthernet1/0/2] quit
# Create GigabitEthernet 1/0/1 that borrows the IP address of Loopback 1023.
[GNE] interface gigabitethernet 1/0/1
[GNE-GigabitEthernet1/0/1] ip binding vpn-instance dcn_vpn
[GNE-GigabitEthernet1/0/1] ip address unnumbered interface loopback 1023
[GNE-GigabitEthernet1/0/1] quit
# Create GigabitEthernet 1/0/2 that borrows the IP address of Loopback 1023.
[GNE] interface gigabitethernet 1/0/2
[GNE-GigabitEthernet1/0/2] ip binding vpn-instance dcn_vpn
[GNE-GigabitEthernet1/0/2] ip address unnumbered interface loopback 1023
[GNE-GigabitEthernet1/0/2] quit
# Enable OSPF process 65535 to run in VPN instance dcn_vpn , and create area 0.
[GNE] ospf 65535 vpn-instance dcn_vpn
[GNE-ospf-65535] area 0
[GNE-ospf-65535-area-0.0.0.0] network 0.0.0.0 255.255.255.255
[GNE-ospf-65535-area-0.0.0.0] quit
[GNE-ospf-65535] quit
# Set the OSPF network type for GigabitEthernet 1/0/1 to P2P.
[GNE] interface gigabitethernet 1/0/1
[GNE-GigabitEthernet1/0/1] ospf network-type p2p
[GNE-GigabitEthernet1/0/1] quit
# Set the OSPF network type for GigabitEthernet 1/0/2 to P2P.
[GNE] interface gigabitethernet 1/0/2
[GNE-GigabitEthernet1/0/2] ospf network-type p2p
[GNE-GigabitEthernet1/0/2] quit
2. Configure Device A:
# Enable DCN, configure the NE ID as 200002 and NE IP as 22.2.2.2/32.
<DeviceA> system-view
[DeviceA] dcn
[DeviceA-dcn] ne-id 200002
[DeviceA-dcn] ne-ip 22.2.2.2 32
[DeviceA-dcn] quit
# Create a VPN instance named dcn_vpn .
535
[DeviceA] ip vpn-instance dcn_vpn
[DeviceA-vpn-instance-dcn_vpn] quit
# Create interface Loopback 1023, and associate it with VPN instance dcn_vpn .
[DeviceA] interface loopback 1023
[DeviceA-LoopBack1023] ip binding vpn-instance dcn_vpn
[DeviceA-LoopBack1023] quit
# Enable LLDP globally.
[DeviceA] lldp global enable
# Enable the nearest bridge agents on GigabitEthernet 1/0/1 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] port link-mode route
[DeviceA-GigabitEthernet1/0/1] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/1 receives an LLDP frame.
[DeviceA-GigabitEthernet1/0/1] lldp management-address arp-learning vlan 4094
[DeviceA-GigabitEthernet1/0/1] quit
# Enable the nearest bridge agents on GigabitEthernet 1/0/2 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[DeviceA] interface gigabitethernet 1/0/2
[DeviceA-GigabitEthernet1/0/2] port link-mode route
[DeviceA-GigabitEthernet1/0/2] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/2 receives an LLDP frame.
[DeviceA-GigabitEthernet1/0/2] lldp management-address arp-learning vlan 4094
[DeviceA-GigabitEthernet1/0/2] quit
# Create GigabitEthernet 1/0/1 that borrows the IP address of Loopback 1023.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] ip binding vpn-instance dcn_vpn
[DeviceA-GigabitEthernet1/0/1] ip address unnumbered interface loopback 1023
[DeviceA-GigabitEthernet1/0/1] quit
# Create GigabitEthernet 1/0/2 that borrows the IP address of Loopback 1023.
[DeviceA] interface gigabitethernet 1/0/2
[DeviceA-GigabitEthernet1/0/2] ip binding vpn-instance dcn_vpn
[DeviceA-GigabitEthernet1/0/2] ip address unnumbered interface loopback 1023
[DeviceA-GigabitEthernet1/0/2] quit
# Enable OSPF process 65535 to run in VPN instance dcn_vpn , and create area 0.
[DeviceA] ospf 65535 vpn-instance dcn_vpn
[DeviceA-ospf-65535] area 0
[DeviceA-ospf-65535-area-0.0.0.0] network 0.0.0.0 255.255.255.255
[DeviceA-ospf-65535-area-0.0.0.0] quit
[DeviceA-ospf-65535] quit
# Set the OSPF network type for GigabitEthernet 1/0/1 to P2P.
536
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] ospf network-type p2p
[DeviceA-GigabitEthernet1/0/1] quit
# Set the OSPF network type for GigabitEthernet 1/0/2 to P2P.
[DeviceA] interface gigabitethernet 1/0/2
[DeviceA-GigabitEthernet1/0/2] ospf network-type p2p
[DeviceA-GigabitEthernet1/0/2] quit
3. Configure Device B:
# Enable DCN, configure the NE ID as 300003 and NE IP as 33.3.3.3/32.
<DeviceB> system-view
[DeviceB] dcn
[DeviceB-dcn] ne-id 300003
[DeviceB-dcn] ne-ip 33.3.3.3 32
[DeviceB-dcn] quit
# Create a VPN instance named dcn_vpn .
[DeviceB] ip vpn-instance dcn_vpn
[DeviceB-vpn-instance-dcn_vpn] quit
# Create interface Loopback 1023, and associate it with VPN instance dcn_vpn .
[DeviceB] interface loopback 1023
[DeviceB-LoopBack1023] ip binding vpn-instance dcn_vpn
[DeviceB-LoopBack1023] quit
# Enable LLDP globally.
[DeviceB] lldp global enable
# Enable the nearest bridge agents on GigabitEthernet 1/0/1 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[DeviceB] interface gigabitethernet 1/0/1
[DeviceB-GigabitEthernet1/0/1] port link-mode route
[DeviceB-GigabitEthernet1/0/1] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/1 receives an LLDP frame.
[DeviceB-GigabitEthernet1/0/1] lldp management-address arp-learning vlan 4094
[DeviceB-GigabitEthernet1/0/1] quit
# Enable the nearest bridge agents on GigabitEthernet 1/0/2 to advertise basic LLDP TLVs and management address TLVs. The IP address of interface Loopback 1023 is specified as the management address.
[DeviceB] interface gigabitethernet 1/0/2
[DeviceB-GigabitEthernet1/0/2] port link-mode route
[DeviceB-GigabitEthernet1/0/2] lldp tlv-enable basic-tlv management-address-tlv interface loopback 1023
# Configure the system to issue the generated ARP entry to the Layer 3 Ethernet subinterface associated with VLAN 4094 in Dot1q termination after GigabitEthernet 1/0/2 receives an LLDP frame.
[DeviceB-GigabitEthernet1/0/2] lldp management-address arp-learning vlan 4094
[DeviceB-GigabitEthernet1/0/2] quit
# Create GigabitEthernet 1/0/1 that borrows the IP address of Loopback 1023.
[DeviceB] interface gigabitethernet 1/0/1
537
[DeviceB-GigabitEthernet1/0/1] ip binding vpn-instance dcn_vpn
[DeviceB-GigabitEthernet1/0/1] ip address unnumbered interface loopback 1023
[DeviceB-GigabitEthernet1/0/1] quit
# Create GigabitEthernet 1/0/2 that borrows the IP address of Loopback 1023.
[DeviceB] interface gigabitethernet 1/0/2
[DeviceB-GigabitEthernet1/0/2] ip binding vpn-instance dcn_vpn
[DeviceB-GigabitEthernet1/0/2] ip address unnumbered interface loopback 1023
[DeviceB-GigabitEthernet1/0/2] quit
# Enable OSPF process 65535 to run in VPN instance dcn_vpn , and create area 0.
[DeviceB] ospf 65535 vpn-instance dcn_vpn
[DeviceB-ospf-65535] area 0
[DeviceB-ospf-65535-area-0.0.0.0] network 0.0.0.0 255.255.255.255
[DeviceB-ospf-65535-area-0.0.0.0] quit
[DeviceB-ospf-65535] quit
# Set the OSPF network type for GigabitEthernet 1/0/1 to P2P.
[DeviceB] interface gigabitethernet 1/0/1
[DeviceB-GigabitEthernet1/0/1] ospf network-type p2p
[DeviceB-GigabitEthernet1/0/1] quit
# Set the OSPF network type for GigabitEthernet 1/0/2 to P2P.
[DeviceB] interface gigabitethernet 1/0/2
[DeviceB-GigabitEthernet1/0/2] ospf network-type p2p
[DeviceB-GigabitEthernet1/0/2] quit
Verifying the configuration
# Display brief DCN information on the GNE.
[GNE] display dcn
DCN Brief Information
NE ID : 0x100001
NE IP : 11.1.1.1
Mask : 255.255.255.255
DCN interface: LoopBack1023
Auto report : Enabled
# Display all DCN NE information on the GNE.
[GNE] display dcn ne-info
DCN Network Elements Information
NE ID NE IP Metric Device Type
0x100001 11.1.1.1 0 HPE 10504
0x200002 22.2.2.2 1 HPE 10506
0x300003 33.3.3.3 1 HPE 10510
Total number: 3
The output shows that GNE, Device A, and Device B are online. The GNE notifies the NMS of the online event. You can successfully ping the NE IP addresses of Device A and Device B from the
GNE.
538
# Remove Device B from the DCN network and display all DCN NE information for the GNE.
[GNE] display dcn ne-info
DCN Network Elements Information
NE ID NE IP Metric Device Type
0x100001 11.1.1.1 0 HPE 10504
0x200002 22.2.2.2 1 HPE 10506
Total number: 2
The output shows that GNE and Device A are online. The GNE notifies the NMS of the offline event of Device B. You can still successfully ping the NE IP address of Device A from the GNE.
539
Document conventions and icons
Conventions
This section describes the conventions used in the documentation.
Command conventions
Convention
Boldface
Italic
[ ]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... } *
[ x | y | ... ] *
Description
Bold text represents commands and keywords that you enter literally as shown.
Italic text represents arguments that you replace with actual values.
Square brackets enclose syntax choices (keywords or arguments) that are optional.
Braces enclose a set of required syntax choices separated by vertical bars, from which you select one.
Square brackets enclose a set of optional syntax choices separated by vertical bars, from which you select one or none.
Asterisk marked braces enclose a set of required syntax choices separated by vertical bars, from which you select at least one.
Asterisk marked square brackets enclose optional syntax choices separated by vertical bars, from which you select one choice, multiple choices, or none.
The argument or keyword and argument combination before the ampersand (&) sign can be entered 1 to n times.
A line that starts with a pound (#) sign is comments.
&<1-n>
#
GUI conventions
Convention
Boldface
Description
Window names, button names, field names, and menu items are in Boldface. For example, the New User window opens; click OK .
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder .
Symbols
>
Convention
WARNING!
CAUTION:
IMPORTANT:
NOTE:
TIP:
Description
An alert that calls attention to important information that if not understood or followed can result in personal injury.
An alert that calls attention to important information that if not understood or followed can result in data loss, data corruption, or damage to hardware or software.
An alert that calls attention to essential information.
An alert that contains additional or supplementary information.
An alert that provides helpful information.
540
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model, configuration, or software version. It is normal that the port numbers, sample output, screenshots, and other information in the examples differ from what you have on your device.
541
Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: www.hpe.com/assistance
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website: www.hpe.com/support/hpesc
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
Accessing updates
•
Some software products provide a mechanism for accessing software updates through the product interface. Review your product documentation to identify the recommended software update method.
•
To download product updates, go to either of the following:
Hewlett Packard Enterprise Support Center Get connected with updates page: www.hpe.com/support/e-updates
Software Depot website: www.hpe.com/support/softwaredepot
•
To view and update your entitlements, and to link your contracts, Care Packs, and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
542
Websites
Website
Networking websites
Hewlett Packard Enterprise Information Library for
Networking
Hewlett Packard Enterprise Networking website
Hewlett Packard Enterprise My Networking website
Hewlett Packard Enterprise My Networking Portal
Hewlett Packard Enterprise Networking Warranty
General websites
Hewlett Packard Enterprise Information Library
Hewlett Packard Enterprise Support Center
Hewlett Packard Enterprise Support Services Central
Contact Hewlett Packard Enterprise Worldwide
Subscription Service/Support Alerts
Software Depot
Customer Self Repair (not applicable to all devices)
Insight Remote Support (not applicable to all devices)
Link www.hpe.com/networking/resourcefinder www.hpe.com/info/networking www.hpe.com/networking/support www.hpe.com/networking/mynetworking www.hpe.com/networking/warranty www.hpe.com/info/enterprise/docs www.hpe.com/support/hpesc ssc.hpe.com/portal/site/ssc/ www.hpe.com/assistance www.hpe.com/support/e-updates www.hpe.com/support/softwaredepot www.hpe.com/support/selfrepair www.hpe.com/info/insightremotesupport/docs
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website: www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or contractual support agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly recommends that you register your device for remote support.
For more information and device support details, go to the following website: www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback ( [email protected]
). When submitting your feedback, include the document title,
543
part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
544
Index
Numerics
4-byte
6PE
BGP AS number suppression, 278
BGP 6PE optional capabilities, 310
IPv6 BGP 6PE configuration, 367
A
ABR
OSPF summary network discard route, 82
OSPFv3 route summarization, 443
ACL
action
address
DCN LLDP management address
adjacency
OSPFv3 area configuration (NSSA), 465
OSPFv3 area configuration (stub), 461
OSPFv3 DR election configuration, 467
OSPFv3 IPsec profile configuration, 484
OSPFv3 route redistribution, 470
advertising
BGP COMMUNITY configuration, 295
BGP COMMUNITY NO_ADVERTISE path
BGP default route (peer/peer group)(IPv4),
BGP default route (peer/peer group)(IPv6),
BGP fake AS number (IPv4), 265
BGP fake AS number (IPv6), 265
BGP optimal route (IPv4 unicast), 235
BGP optimal route (IPv6 unicast), 235
BGP route advertisement rules, 199
DCN LLDP management address, 533
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv4 multicast BGP configuration, 353
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP route reflector configuration, 364
IPv6 multicast BGP configuration, 382
IS-IS link state information, 149
OSPF host route advertisement, 84
OSPF route summarization configuration, 109
RIP summary route advertisement configuration,
applying
area
IS-IS authentication (area), 162
OSPF area configuration (NSSA),
OSPF area configuration (stub),
545
OSPF authentication (area), 88
OSPFv3 area configuration (NSSA),
OSPFv3 area configuration (stub),
ARP
DCN LLDP frame ARP entry enable, 533
AS
BGP 4-byte AS number suppression, 278
BGP AS number substitution, 266
BGP confederation compatibility, 301
BGP fake AS number advertisement, 265
BGP first AS number of EBGP route update
BGP link state (LS) AS number, 313
BGP local AS number appearance, 263
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
BGP path AS_PATH attribute, 195
BGP path AS_SEQUENCE attribute, 195
BGP path AS_SET attribute, 195
BGP private AS number removal, 268
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP FRR configuration, 349
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv4 multicast BGP configuration, 353
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP FRR configuration, 378
IPv6 BGP route reflector configuration, 364
IPv6 multicast BGP configuration, 382
IS-IS basic configuration, 142
IS-IS basics configuration, 169
IS-IS DIS election configuration, 174
AS_PATH
ASBR
OSPF redistributed route summarization, 80
OSPF summary network discard route, 82
OSPFv3 redistributed route summarization, 443
assigning
IPv6 IS-IS route convergence priority, 492
ATT
IS-IS ATT bit default route calculation, 157
IS-IS ATT bit Level-1 LSP, 157
attribute
BGP AS_PATH attribute ignore, 265
IPv4 BGP COMMUNITY configuration, 332
MP-BGP MP_REACH_NLRI extended attribute,
MP-BGP MP_UNREACH_NLRI extended
authenticating
BGP peer keychain authentication, 280
BGP peer MD5 authentication, 279
IS-IS authentication (area), 162
IS-IS authentication (neighbor relationship), 162
IS-IS authentication (routing domain), 163
IS-IS network security enhancement, 162
RIPng IPsec profile application, 422
546
RIPv2 message authentication configuration,
authentication
auto
BGP route summarization (automatic)(IPv4),
DCN automatic report enable, 532
IPv6 IS-IS automatic link cost calculation, 491
IPv6 IS-IS FRR automatic backup next hop
IS-IS automatic cost calculation, 145
automatic
RIPv2 automatic route summarization enable,
B backbone
backing up
bandwidth
BDR
BFD
IPv4 BGP BFD configuration configuration,
IPv6 BGP BFD configuration configuration,
IPv6 static route BFD configuration, 401
IPv6 static route BFD control mode (direct
IPv6 static route BFD control mode (indirect
IPv6 static route BFD echo mode (single hop),
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop),
IS-IS FRR BFD enable (control packet mode),
IS-IS FRR BFD enable (echo packet mode),
OSPF detection configuration (bidirectional
OSPF detection configuration (single-hop echo),
RIP BFD configuration (bidirectional control
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination),
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
(indirect next hop), 11 static routing BFD configuration, 11
static routing BFD configuration (direct next hop),
static routing BFD configuration (indirect next
static routing BFD single-hop echo mode, 12
4-byte AS number suppression, 278
6PE optional capabilities, 310
advertising OSPF link state information to BGP,
AS_PATH attribute configuration, 263
BGP Monitoring Protocol.
confederation compatibility, 301
confederation configuration, 300
default local preference configuration, 254
547
default route advertisement (peer/peer group),
dynamic peer configuration, 214
EBGP direct connections after link failure, 276
EBGP peer protection (low memory
EBGP session establishment (multiple hop),
fake AS number advertisement, 265
first AS number of EBGP route update ignore,
first send default route update, 238
IPv4 COMMUNITY configuration, 332
IPv4 confederation configuration, 337
IPv4 dynamic peer configuration, 357
IPv4 IGP route redistribution, 323
IPv4 load balancing configuration, 329
IPv4 multicast configuration, 353
IPv4 path selection configuration, 341
IPv4 route reflector configuration, 335
IPv6 multicast configuration, 382
IPv6 packet IPsec configuration, 373
IPv6 route reflector configuration, 364
keepalive interval+hold time configuration,
large scale network management, 201
large-scale network configuration, 294
link state (LS) AS number, 313
link state (LS) route reflection, 312
link state (LS) router ID, 313
load balancing configuration, 281
local AS number appearance, 263
manual soft reset configuration, 288
MED attribute configuration, 256
548
MP-BGP extended attributes, 204
MPLS local label update delay, 292
nonstop routing (NSR) configuration, 302
optimal route advertisement, 235
optimal route selection disable for labeled routes,
ORIGINATOR_ID attribute ignore, 299
outgoing packet DSCP value, 293
peer keychain authentication, 280
per-prefix label allocation enable, 294
private AS number removal, 268
received route preferred value, 251
route advertisement rules, 199
route dampening configuration, 249
route distribution control, 232
route preference configuration, 252
route reflection, 297 route reflector configuration, 297
routes received limit (peer/peer group), 239
routing policy AS_PATH list, 517 routing policy COMMUNITY list, 517
session establishment disable, 283
session state change logging, 303
SoO attribute configuration, 270
startup policy for BGP route updates, 248
suboptimal route flush to RIB, 292
TCP connection source address, 227
troubleshoot, 385 troubleshoot peer connection state, 385
bidirectional
IPv6 static route BFD control mode (direct
IPv6 static route BFD control mode (indirect
IPv6 static route BFD echo mode (single hop),
OSPF BFD detection configuration
RIP BFD configuration (bidirectional control
RIP BFD configuration (bidirectional
detection/control packet mode), 59
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
BMP
BGP Monitoring Protocol configuration, 313
Border Gateway Protocol.
broadcast
OSPF interface network type, 77
OSPFv3 network type (interface), 442
C calculating
IPv6 IS-IS SPF calculation interval, 493
IS-IS ATT bit default route calculation, 157
IS-IS SPF calculation interval, 155
OSPF FRR backup next hop calculation (LFA
OSPF SPF calculation interval, 86
OSPFv3 FRR backup next hop calculation
OSPFv3 SPF calculation interval, 448
checking
OSPFv3 DD packet ignore MTU check, 449
circuit
classless inter-domain routing.
Use CIDR clearing
CLNP
COMMUNITY
BGP COMMUNITY path attribute, 195
IPv4 BGP COMMUNITY configuration, 332
community
routing policy extended community list, 517 routing policy list, 517
COMMUNITY
BGP COMMUNITY configuration, 295
routing policy COMMUNITY list, 519
community
routing policy extended community list, 520
comparing
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
confederating
BGP confederation compatibility, 301
BGP MED route comparison (confederation
configuring
BGP 6PE optional capabilities, 310
BGP AS number substitution (IPv4), 266
BGP AS number substitution (IPv6), 266
BGP confederation compatibility, 301
BGP default local preference (IPv4), 254
BGP default local preference (IPv6), 254
BGP dynamic peer (IPv4 multicast address), 216
BGP dynamic peer (IPv4 unicast address), 215
BGP dynamic peer (IPv6 multicast address), 216
BGP dynamic peer (IPv6 unicast address), 215
549
BGP first send default route update, 238
BGP FRR (IPv4 unicast address), 306
BGP FRR (IPv6 unicast address), 306
BGP keepalive interval+hold time, 271
BGP link state (LS) route reflection, 312
BGP load balancing (IPv4), 281
BGP load balancing (IPv6), 281
BGP manual soft reset (IPv4), 288
BGP manual soft reset (IPv6), 288
BGP MED default value (IPv4), 256
BGP MED default value (IPv6), 256
BGP Monitoring Protocol (BMP), 313
BGP MPLS local label update delay, 292
BGP NEXT_HOP attribute (IPv4), 260
BGP NEXT_HOP attribute (IPv6), 260
BGP peer (IPv4 multicast address), 214
BGP peer (IPv4 unicast address), 213
BGP peer (IPv6 multicast address), 214
BGP peer (IPv6 unicast address), 213
BGP route dampening (IPv4), 249
BGP route dampening (IPv6), 249
BGP route distribution filtering policy (IPv4),
BGP route distribution filtering policy (IPv6),
BGP route filtering policy, 241
BGP route preference (IPv4), 252
BGP route preference (IPv6), 252
BGP route reception filtering policy (IPv4), 245
BGP route reception filtering policy (IPv6), 245
BGP route reflector (IPv4), 297
BGP route reflector (IPv6), 297
BGP route summarization (automatic)(IPv4),
BGP route summarization (manual)(IPv4),
BGP route summarization (manual)(IPv6),
BGP route update interval (IPv4), 274
BGP route update interval (IPv6), 274
550
DCN LLDP frame source MAC address, 532
EBGP peer group (IPv4 multicast address), 219
EBGP peer group (IPv4 unicast address), 219
EBGP peer group (IPv6 multicast address), 219
EBGP peer group (IPv6 unicast address), 219
EVPN-based service chain PBR, 394
IBGP peer group (IPv4 multicast address), 217
IBGP peer group (IPv4 unicast address), 217
IBGP peer group (IPv6 multicast address), 217
IBGP peer group (IPv6 unicast address), 217
interface exclusion from the base topology in an
IP routing inter-protocol FRR, 6
IP routing IPv4 RIB inter-protocol FRR, 7
IP routing IPv6 RIB inter-protocol FRR, 7
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv6 BGP 6PE configuration, 367
IPv6 IS-IS FRR (routing policy), 496
IPv6 IS-IS FRR automatic backup next hop
IPv6 IS-IS interface cost, 491
IPv6 IS-IS interface tag value, 493
IPv6 PBR interface (packet type-based), 514
IPv6 PBR local (packet type-based), 513
IPv6 PBR node match criteria, 511
IPv6 static route BFD control mode (direct
IPv6 static route BFD control mode (indirect
IPv6 static route BFD echo mode (single hop),
IPv6 static routing basics, 403
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop),
IS-IS ATT bit default route calculation, 157
IS-IS authentication (area), 162
IS-IS authentication (neighbor relationship),
IS-IS authentication (routing domain), 163
IS-IS FRR (routing policy), 167
IS-IS FRR backup next hop (LFA calculation),
551
IS-IS interface DIS priority, 151
IS-IS interface P2P network type, 143
IS-IS interface tag value, 157
IS-IS LSP-calculated route filtering, 148
IS-IS redistributed route filtering, 148
IS-IS route convergence priority, 156
IS-IS route summarization, 146
IS-IS system ID > host name mapping, 158
IS-IS system ID > host name mapping (dynamic),
IS-IS system ID > host name mapping (static),
OSPF authentication (area), 88
OSPF authentication (interface), 89
OSPF BFD detection (bidirectional control), 100
OSPF BFD detection (single-hop echo), 100
OSPF DD packet interface MTU, 89
OSPF FRR backup next hop (routing policy), 102
OSPF FRR backup next hop calculation (LFA
OSPF GR restarter (non-IETF), 98
OSPF host route advertisement, 84
OSPF interface network type (broadcast), 77
OSPF interface network type (NBMA), 77
OSPF interface network type (P2MP), 78
OSPF interface network type (P2P), 79
OSPF prefix suppression (interface), 94
OSPF prefix suppression (OSPF process), 93
OSPF received route filtering, 80
OSPF redistributed route default parameters,
OSPF redistributed route summarization
OSPF route redistribution, 107
OSPF route redistribution (another routing
OSPF route redistribution (default route), 83
OSPF route summarization (ABR), 79
OSPF summary network discard route, 82
OSPFv3 FRR backup next hop (routing policy),
OSPFv3 FRR backup next hop calculation
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 interface DR priority, 449
552
OSPFv3 network management, 450
OSPFv3 network type (interface), 442
OSPFv3 prefix suppression (interface), 453
OSPFv3 prefix suppression (OSPFv3 process),
OSPFv3 received route filtering, 444
OSPFv3 redistributed route tag, 447
OSPFv3 route redistribution, 470
OSPFv3 route redistribution (another routing
OSPFv3 route redistribution (default route), 446
OSPFv3 route summarization, 473
OSPFv3 route summarization (ABR), 443
OSPFv3 route summarization (ASBR), 443
PBR (interface/packet type-based), 392
PBR (local/packet type-based), 391
RIP additional routing metric, 29
RIP BFD (bidirectional control detection), 41
RIP BFD (bidirectional detection/control packet
RIP BFD (single-hop echo detection)(on switch),
RIP BFD (single-hop echo detection/neighbor),
RIP BFD (single-hop echo detection/specific
RIP interface additional metric, 48
RIP received/redistributed route filtering, 32
RIP summary route advertisement, 49
RIPng IPsec profile configuration, 433
RIPng packet zero field check, 417
RIPng received/redistributed route filtering,
RIPng route summarization, 414
RIPv2 message authentication, 35
517, 520, 525 routing policy (IPv4 route redistribution), 525
routing policy (IPv6 route redistribution), 528
routing policy apply clause, 522
routing policy AS_PATH list, 519 routing policy COMMUNITY list, 519
routing policy continue clause, 524
routing policy extended community list, 520
routing policy if-match clause, 521
routing policy IPv4 prefix list, 518
routing policy IPv6 prefix list, 519
routing policy-based recursive lookup, 7
startup policy for BGP route updates, 248
10, 10, 15 static routing basics, 15
static routing BFD (direct next hop), 16
static routing BFD (indirect next hop), 19
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
static routing BFD single-hop echo mode, 12
static routing default route, 24
static routing FRR (auto backup next hop), 14 static routing FRR BFD echo packet mode, 14
static routing FRRs(backup next hop), 13
connecting
BGP TCP connection source address, 227
EBGP direct connections after link failure, 276
continue clause (routing policy),
controlling
IPv6 IS-IS SPF calculation interval, 493
IPv6 static route BFD control mode (direct next
IPv6 static route BFD control mode (indirect next
IS-IS SPF calculation interval, 155
RIP additional routing metric configuration, 29
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP interface advertisement, 28
RIP interface reception, 28, 28
RIP route control configuration, 29
convergence priority (IPv6 IS-IS), 492
convergence priority (IS-IS), 156
cost
IPv6 IS-IS automatic link cost calculation, 491
IPv6 IS-IS interface cost, 491
IS-IS automatic cost calculation, 145
creating
CSNP
IS-IS CSNP packet send interval, 151
D dampening
data communication network.
553
database
DCN
basic concepts, 530 basic features, 530 configuration,
DCN VPN configuration, 531 enable, 531
LLDP frame ARP entry enable, 533
LLDP frame source MAC address, 532
LLDP management address advertisement,
DD
OSPFv3 DD packet ignore MTU check, 449
default
BGP default local preference, 254
BGP default route advertisement (peer/peer
IPv6 default route configuration, 411
IS-IS default route advertisement, 147
OSPF redistributed route default parameters,
OSPFv3 route redistribution (default route),
RIP default route advertisement, 31
RIPng default route advertisement, 415
static routing configuration.
See under static routing delaying
BGP MPLS local label update delay, 292
OSPFv3 LSA transmission delay, 448
detecting
OSPF BFD detection configuration
OSPF BFD detection configuration
RIP BFD configuration (bidirectional control
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination),
RIP BFD single-hop echo detection, 39
device
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP dynamic peer configuration, 357
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv4 multicast BGP configuration, 353
IPv6 BGP 6PE configuration, 367
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP route reflector configuration, 364
IPv6 IS-IS basic configuration, 498
IPv6 IS-IS BFD configuration, 503
IPv6 IS-IS FRR configuration, 505
IPv6 multicast BGP configuration, 382
IPv6 static routing basics, 403
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop), 408
IS-IS basics configuration, 169
IS-IS DIS election configuration, 174
IS-IS route redistribution, 178
OSPF area configuration (NSSA), 114
OSPF area configuration (stub), 112
554
OSPF DR election configuration, 116
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF virtual link configuration, 121
OSPFv3 area configuration (NSSA), 465
OSPFv3 area configuration (stub), 461
OSPFv3 DR election configuration, 467
OSPFv3 IPsec profile configuration, 484
OSPFv3 route redistribution, 470
OSPFv3 route summarization, 473
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination), 57
RIP interface additional metric configuration,
RIP summary route advertisement
RIPng basic configuration, 423
RIPng IPsec profile configuration, 433
RIPng route redistribution, 425
routing policy configuration, 525
routing policy configuration (IPv4 route
routing policy configuration (IPv6 route
static routing basic configuration, 15
static routing BFD configuration (direct next
static routing BFD configuration (indirect next
static routing configuration, 15
static routing FRR configuration, 21
DIS
IS-IS DIS election configuration, 174
IS-IS interface DIS priority, 151
disabling
BGP optimal route selection for labeled routes,
BGP session establishment (IPv4), 283
BGP session establishment (IPv6), 283
IS-IS interface packet send/receive, 151
OSPF interface packet send/receive disable, 87
OSPFv3 interface packet send/receive, 449
recursion policy for routes received from a peer or
displaying
distributing
BGP IGP route redistribution, 230
BGP route distribution control, 232
IP routing extension attribute redistribution, 3
IP routing route redistribution, 3
IPv4 BGP+IGP route redistribution, 323
RIPng received/redistributed route filtering, 415
domain
IS-IS authentication (routing domain), 163
DR
555
OSPF DR election configuration, 116
OSPFv3 DR election configuration, 467
OSPFv3 interface DR priority, 449
DSCP
BGP outgoing packet DSCP value, 293
dynamic
IP routing dynamic routing protocols, 2
IS-IS system ID > host name mapping, 158
E
EBGP
BGP first AS number of route update ignore,
BGP private AS number removal from
direct connections after link failure, 276
peer group configuration (IPv4 multicast
peer group configuration (IPv4 unicast
peer group configuration (IPv6 multicast
peer group configuration (IPv6 unicast
session establishment (multiple hop), 275
echo
IPv6 static route BFD echo mode (single hop),
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination), 57
RIP BFD single-hop echo detection, 39
static routing BFD single-hop echo mode, 12
ECMP
IP routing ECMP route max number, 5
electing
OSPF DR election configuration, 116
OSPFv3 DR election configuration, 467
enabling advertising OSPF link state information to BGP,
BGP 4-byte AS number suppression (IPv4), 278
BGP 4-byte AS number suppression (IPv6), 278
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
BGP peer keychain authentication (IPv4), 280
BGP peer keychain authentication (IPv6), 280
BGP peer MD5 authentication (IPv4), 279
BGP peer MD5 authentication (IPv6), 279
BGP per-prefix label allocation, 294
BGP route flapping logging (IPv4), 304
BGP route flapping logging (IPv6), 304
BGP session state change logging (IPv4), 303
BGP session state change logging (IPv6), 303
EBGP direct connections after link failure, 276
EBGP session establishment (multiple hop)(IPv4),
EBGP session establishment (multiple hop)(IPv6),
IPv6 IS-IS automatic link cost calculation, 491
IPv6 IS-IS prefix suppression, 494
IS-IS automatic cost calculation, 145
IS-IS FRR BFD (control packet mode), 167
IS-IS FRR BFD (echo packet mode), 167
IS-IS interface hello packet send, 152
IS-IS LSP fragment extension, 154
IS-IS neighbor state change logging, 159
556
OSPF neighbor state change logging, 91
OSPF RFC 1583 compatibility, 90
OSPFv3 neighbor state change logging, 450
RIP update source IP address check, 35
RIPv1 incoming message zero field check, 35
RIPv2 automatic route summarization, 30
enhancing
establishing
BGP session establishment disable, 283
EBGP session establishment (multiple hop),
exit overflow interval (OSPF), 90
extending
IS-IS LSP fragment extension, 154
MP-BGP MP_REACH_NLRI extended
MP-BGP MP_UNREACH_NLRI extended
Exterior Gateway Protocol.
Use EGP external
OSPF LSDB external LSAs max, 90
external BGP.
Use EGP
F
FIB
filtering
BGP route distribution filtering policy, 241
BGP route filtering policy, 241
BGP route reception filtering policy, 245
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP FRR configuration, 349
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP FRR configuration, 378
IPv6 BGP route reflector configuration, 364
IS-IS LSP-calculated routes, 148
IS-IS redistributed routes, 148
OSPF outbound LSA (interface), 96
OSPF outbound LSAs (specified neighbor), 96
OSPF received route filtering, 80
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 received route filtering, 444
RIP received/redistributed route filtering, 32
RIPng received/redistributed route filtering, 415
routing policy apply clause, 522
routing policy COMMUNITY list,
routing policy configuration (IPv4 route
routing policy configuration (IPv6 route
routing policy continue clause, 524
routing policy extended community list,
routing policy filter configuration, 518
routing policy if-match clause, 521
routing policy IP prefix list, 518
routing policy prefix list, 517
flapping
BGP route flapping logging, 304
flooding
flushing
BGP suboptimal route to RIB, 292
format
IS-IS NSAP address format, 135
forwarding
EVPN-based service chain PBR configuration,
IP routing inter-protocol FRR, 6
IP routing IPv4 RIB inter-protocol FRR, 7
557
IP routing IPv6 RIB inter-protocol FRR, 7
IPv6 PBR interface configuration, 512
IPv6 PBR interface configuration (packet
IPv6 PBR local configuration, 512
IPv6 PBR local configuration (packet
IPv6 PBR policy configuration, 511
PBR configuration (interface), 390
PBR configuration (interface/packet
PBR configuration (local), 390
PBR configuration (local/packet type-based),
fragment
IS-IS LSP fragment extension, 154
frame
DCN LLDP frame ARP entry enable, 533
FRR
IPv4 BGP FRR configuration, 349
IPv6 BGP FRR configuration, 378
IPv6 IS-IS FRR automatic backup next hop
IPv6 IS-IS FRR configuration, 505
IPv6 IS-IS FRR configuration (routing policy),
IS-IS FRR backup next hop configuration (LFA
IS-IS FRR BFD enable (control packet mode),
IS-IS FRR BFD enable (echo packet mode), 167
IS-IS FRR configuration (routing policy), 167
OSPF backup next hop (routing policy), 102
OSPF backup next hop calculation (LFA
OSPFv3 backup next hop (routing policy), 457
OSPFv3 backup next hop calculation (LFA
static routing FRR configuration,
G
garbage-collect timer (RIP), 33
gateway network element (GNE)
DCN automatic report enable, 532
Generalized TTL Security Mechanism.
generating
OSPFv3 LSA generation interval, 448
Graceful Restart (GR)
IPv4 BGP GR configuration, 344
OSPF GR helper configuration, 98
OSPF GR restarter configuration, 97
OSPFv3 GR helper configuration, 454
OSPFv3 GR restarter configuration, 454
RIP GR helper configuration, 38
558
RIP GR restarter configuration, 38
group
GTSM
H hello
IS-IS hello packet send interval, 150
IS-IS interface hello packet send, 152
HO-DSP (IS-IS area address), 136
hop
EBGP session establishment (multiple hop),
OSPF BFD detection configuration
RIP BFD configuration (bidirectional control
RIP BFD configuration (single-hop echo
host
RIP BFD configuration (single-hop echo
detection/specific destination), 40
IS-IS system ID > host name mapping, 158
OSPF host route advertisement, 84
RIP host route reception disable, 31
I
IBGP
peer group configuration (IPv4 multicast
peer group configuration (IPv4 unicast
peer group configuration (IPv6 multicast
peer group configuration (IPv6 unicast
ICMP
OSPF area configuration (NSSA), 114
OSPF area configuration (stub), 112
OSPF DR election configuration, 116
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF virtual link configuration, 121
OSPFv3 route summarization, 473
ID
BGP link state (LS) router ID, 313
DCN NE ID+IP configuration, 531
IETF
ignoring
BGP first AS number of EBGP route updates, 269
BGP IGP metrics during optimal route selection,
BGP ORIGINATOR_ID attribute (IPv4), 299
BGP ORIGINATOR_ID attribute (IPv6), 299
OSPFv3 DD packet MTU check, 449
IGP
BGP IGP route redistribution, 230
BGP ORIGIN path attribute, 195
IPv4 BGP+IGP route redistribution, 323
IS-IS basic configuration, 142
IS-IS basics configuration, 169
IS-IS DIS election configuration, 174
RIP BFD configuration (bidirectional control
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination), 40
RIP neighbor specification, 36
INCOMPLETE
BGP ORIGIN path attribute, 195
injecting
instance
559
inter-area
interface
EVPN-based service chain PBR configuration,
IPv6 PBR interface configuration, 512
IPv6 PBR interface configuration (packet
PBR configuration (interface), 390
PBR configuration (interface/packet
Intermediate System-to-Intermediate System.
Use
internal
BGP.
INTERNET
BGP COMMUNITY path attribute, 195
interval
BGP route update interval, 274
IPv6 IS-IS SPF calculation interval, 493
IS-IS CSNP packet send interval, 151
IS-IS hello packet send interval, 150
IS-IS SPF calculation interval, 155
OSPF exit overflow interval, 90
OSPF LSA generation interval, 87
OSPF SPF calculation interval, 86
OSPFv3 LSA generation interval, 448
OSPFv3 SPF calculation interval, 448
RIP triggered update interval, 36
RIPng triggered update send interval, 419
intra-area
IP addressing
DCN NE ID+IP configuration, 531
RIP update source IP address check, 35
IP routing advertising IS-IS link state information to BGP,
advertising OSPF link state information to
560
BGP 6PE optional capabilities, 310
BGP COMMUNITY configuration, 295
BGP default local preference, 254
BGP default route advertisement (peer/peer
BGP first AS number of EBGP route update
BGP first send default route update, 238
BGP large scale network management, 201
BGP MPLS local label update delay, 292
BGP optimal route advertisement, 235
BGP peer (IPv4 unicast address), 213
BGP peer (IPv6 unicast address), 213
BGP peer keychain authentication, 280
BGP peer MD5 authentication, 279
BGP protocols and standards, 207
BGP received route preferred value, 251
BGP route dampening configuration, 249
BGP route filtering policy, 241
BGP route flapping logging, 304
BGP route update interval, 274
BGP session establishment disable, 283
BGP session state change logging, 303
BGP SNMP notification enable, 303
BGP suboptimal route flush to RIB, 292
BGP TCP connection source address, 227
DCN NE ID+IP configuration, 531
displaying IPv6 static routing, 403
EBGP peer protection (low memory
ECMP route max number configuration, 5
extension attribute redistribution, 3
flushing route attribute information from RIB to
interface exclusion from the base topology in
inter-protocol FRR configuration, 6
IPv4 RIB inter-protocol FRR configuration, 7
IPv6 default route.
See under IPv6 static routing
IPv6 IS-IS FRR configuration, 505
IPv6 policy-based routing.
IPv6 RIB inter-protocol FRR configuration, 7
IPv6 static routing.
IS-IS authentication (area), 162
IS-IS authentication (neighbor relationship),
IS-IS authentication (routing domain), 163
IS-IS automatic cost calculation, 145
IS-IS basic configuration, 142
IS-IS basics configuration, 169
IS-IS CSNP packet send interval, 151
IS-IS default route advertisement, 147
IS-IS DIS election configuration, 174
561
IS-IS hello packet send interval, 150
IS-IS interface DIS priority, 151
IS-IS interface hello packet send, 152
IS-IS interface packet send/receive, 151
IS-IS interface tag value, 157
IS-IS LSP fragment extension, 154
IS-IS LSP-calculated route filtering, 148
IS-IS network optimization, 150
IS-IS network security enhancement, 162
IS-IS protocols and standards, 141
IS-IS redistributed route filtering, 148
IS-IS route convergence priority, 156
IS-IS route summarization, 146
IS-IS SPF calculation interval, 155
IS-IS system ID > host name mapping, 158
MP-BGP protocols and standards, 207
OSPF area configuration (NSSA),
OSPF area configuration (stub),
OSPF BFD detection configuration
OSPF BFD detection configuration
OSPF DD packet interface MTU, 89
OSPF DR election configuration, 116
OSPF exit overflow interval, 90
OSPF host route advertisement, 84
OSPF interface network type (broadcast), 77
OSPF interface network type (NBMA), 77
OSPF interface network type (P2MP), 78
OSPF interface network type (P2P), 79
OSPF interface packet send/receive disable,
OSPF LSA generation interval, 87
OSPF LSA transmission delay, 86
OSPF LSDB external LSAs max, 90
OSPF neighbor state change, 91
562
OSPF outbound LSA filtering (interface), 96
OSPF outbound LSA filtering (specified neighbor),
OSPF protocols and standards, 71
OSPF received route filtering, 80
OSPF RFC 1583 compatibility, 90
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF SPF calculation interval, 86
OSPF summary network discard route, 82
OSPF virtual link configuration, 121
OSPFv3 area configuration (NSSA),
OSPFv3 area configuration (stub),
OSPFv3 DD packet ignore MTU check, 449
OSPFv3 DR election configuration, 467
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 interface DR priority, 449
OSPFv3 interface packet send/receive
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
OSPFv3 LSA generation interval, 448
OSPFv3 LSA transmission delay, 448
OSPFv3 neighbor state change logging, 450
OSPFv3 network management traps, 450
OSPFv3 network optimization, 447
OSPFv3 network type (interface), 442
OSPFv3 prefix suppression, 452
OSPFv3 protocols and standards, 438
OSPFv3 received route filtering, 444
OSPFv3 SPF calculation interval, 448
outgoing RIP packet DSCP value, 38
PBR configuration (interface), 390
PBR configuration (local), 390
policy AS_PATH list, 519 policy COMMUNITY list, 519
policy configuration (IPv4 route redistribution),
policy configuration (IPv6 route redistribution),
policy extended community list, 520
563
policy filter configuration, 518 policy filtering, 518
policy-based routing.
RIP additional routing metric configuration, 29
RIP BFD configuration (bidirectional control
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination),
RIP default route advertisement, 31
RIP FRR configuration restrictions, 41
RIP host route reception disable, 31
RIP interface additional metric configuration, 48
RIP interface advertisement control, 28
RIP interface reception control, 28
RIP neighbor specification, 36
RIP network management configuration, 37
RIP packet send rate configuration, 37
RIP poison reverse configuration, 34
RIP preference configuration, 32
RIP received/redistributed route filtering, 32
RIP route control configuration, 29
RIP route redistribution configuration, 32
RIP routing loop prevention, 25
RIP split horizon configuration, 34
RIP summary route advertisement
RIP triggered update interval configuration, 36
RIP update source IP address check, 35
RIPng default route advertisement, 415
RIPng IPsec profile application, 422
RIPng IPsec profile configuration, 433
RIPng network optimization, 416
RIPng packet zero field check configuration,
RIPng poison reverse configuration, 417
RIPng protocols and standards, 413
RIPng received/redistributed route filtering,
RIPng route summarization, 414
RIPng routing metric configuration, 414
RIPng split horizon configuration, 417
RIPng timer configuration, 416
RIPng triggered update send interval, 419
RIPv1 message zero field check, 35
RIPv2 message authentication configuration,
RIPv2 route summarization configuration, 30
route recursion, 3 route redistribution, 3
routing policy-based recursive lookup, 7
static routing basic configuration, 15
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
(indirect next hop), 11 static routing BFD configuration, 11
static routing BFD configuration (direct next hop),
static routing BFD configuration (indirect next
static routing BFD single-hop echo mode, 12
static routing default route configuration, 24
static routing FRR configuration,
troubleshooting BGP, 385 troubleshooting BGP peer connection state, 385
troubleshooting OSPF configuration, 133
troubleshooting OSPF incorrect routing
troubleshooting OSPF no neighbor relationship
IPsec
IPv6 BGP packet IPsec configuration, 373
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
RIPng IPsec profile application, 422
RIPng IPsec profile configuration, 433
IPv4
BGP 6PE optional capabilities, 310
BGP dynamic peer configuration (IPv4 unicast
BGP peer configuration (IPv4 multicast address),
BGP+IGP route redistribution, 323
EBGP peer group configuration (IPv4 multicast
EBGP peer group configuration (IPv4 unicast
EBGP peer protection (low memory exemption),
EBGP session establishment (multiple hop), 275
IBGP peer group configuration (IPv4 multicast
IBGP peer group configuration (IPv4 unicast
IP routing FIB route max lifetime, 4
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
IPv6 BGP 6PE configuration, 367
IS-IS basic configuration, 142
IS-IS basics configuration, 169
564
IS-IS DIS election configuration, 174
OSPF area configuration (NSSA), 114
OSPF area configuration (stub), 112
OSPF DR election configuration, 116
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF virtual link configuration, 121
routing policy ACLs, 517 routing policy configuration,
routing policy configuration (IPv4 route
routing policy IP prefix list, 518
routing policy prefix list, 517
IPv4 BGP
4-byte AS number suppression, 278
confederation configuration, 337
default route advertisement (peer/peer group),
dynamic peer configuration, 357
dynamic peer configuration (IPv4 multicast
fake AS number advertisement, 265
keepalive interval+hold time configuration,
load balancing configuration, 329
local AS number appearance, 263
manual soft reset configuration, 288
optimal route advertisement, 235
ORIGINATOR_ID attribute ignore, 299
path selection configuration, 341
peer keychain authentication, 280
private AS number removal, 268
received route preferred value, 251
route distribution filtering policy, 241
route reception filtering policy, 245
route reflector configuration, 335
route summarization (automatic), 232
route summarization (manual), 233
routes received (peer/peer group), 239
session establishment disable, 283
session state change logging, 303
TCP connection source address, 227
IPv6
EBGP peer group configuration (IPv6 multicast
EBGP peer group configuration (IPv6 unicast
EBGP peer protection (low memory exemption),
EBGP session establishment (multiple hop), 275
IBGP peer group configuration (IPv6 multicast
IBGP peer group configuration (IPv6 unicast
IP routing FIB route max lifetime, 4
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
IS-IS.
OSPFv3 area configuration (NSSA),
OSPFv3 area configuration (stub),
565
OSPFv3 DD packet ignore MTU check, 449
OSPFv3 DR election configuration, 467
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 interface DR priority, 449
OSPFv3 interface packet send/receive
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
OSPFv3 LSA generation interval, 448
OSPFv3 LSA transmission delay, 448
OSPFv3 neighbor state change logging, 450
OSPFv3 network optimization, 447
OSPFv3 network type (interface), 442
OSPFv3 received route filtering, 444
OSPFv3 SPF calculation interval, 448
policy-based routing.
provider edge.
routing policy ACLs, 517 routing policy configuration,
routing policy configuration (IPv6 route
routing policy IP prefix list, 518
routing policy prefix list, 517
IPv6 BGP
4-byte AS number suppression, 278
6PE optional capabilities, 310
566
default route advertisement (peer/peer group),
dynamic peer configuration (IPv6 multicast
dynamic peer configuration (IPv6 unicast
fake AS number advertisement, 265
keepalive interval+hold time configuration, 271
local AS number appearance, 263
manual soft reset configuration, 288
optimal route advertisement, 235
ORIGINATOR_ID attribute ignore, 299
packet IPsec configuration, 373
peer configuration (IPv6 multicast address), 214
peer keychain authentication, 280
private AS number removal, 268
received route preferred value, 251
route distribution filtering policy, 241
route reception filtering policy, 245
route reflector configuration, 364
route summarization (manual), 233
routes received (peer/peer group), 239
session establishment disable, 283
session state change logging, 303
TCP connection source address, 227
IPv6 IS-IS
FRR automatic backup next hop LFA
FRR configuration (routing policy), 496
global cost configuration, 491 interface cost configuration, 491
interface tag value configuration, 493
network optimization, 492 network tuning, 492
route control configuration, 490
route convergence priority assignment, 492
IPv6 PBR
apply clause, 509 configuration,
interface configuration (packet type-based),
local configuration (packet type-based), 513
match mode/node clause relationship, 510
node action, 511 node creation, 511 node match criteria, 511
IPv6 static routing
BFD configuration (direct next hop), 405
BFD configuration (indirect next hop), 408
BFD control mode (direct next hop), 402
BFD control mode (indirect next hop), 402
BFD echo mode (single hop), 402
default route configuration, 411
IS-IS
advertising IS-IS link state information to BGP,
ATT bit default route calculation, 157
authentication (area), 162 authentication (neighbor relationship), 162
authentication (routing domain), 163
authentication configuration, 181
CSNP packet send interval, 151
default route advertisement, 147
DIS election configuration, 174
enabling automatic cost calculation, 145
FRR backup next hop configuration (LFA
FRR BFD enable (control packet mode), 167
FRR BFD enable (echo packet mode), 167
FRR configuration (routing policy), 167
global cost configuration, 145
hello multiplier, 150 hello packet send interval, 150
interface cost configuration, 145
interface hello packet send enable, 152
interface P2P network type configuration, 143
interface packet send/receive disable, 151
IPv6 IS-IS.
567
LSP parameter configuration, 152
LSP-calculated route filtering, 148
neighbor state change logging, 159
network security enhancement, 162
nonstop routing (NSR) configuration,
point-to-point network type, 138
prefix suppression enable, 159
redistributed route filtering, 148
route control configuration, 144
route convergence priority, 156
route leaking configuration, 149
system ID > host name mapping, 158
ISPF
K keepalive
BGP route update interval, 274
keychain
IPv4 BGP peer keychain authentication, 280
IPv6 BGP peer keychain authentication, 280
L label
BGP MPLS local label update delay, 292
BGP per-prefix label allocation enable, 294
IP routing RIB label max lifetime, 4
leaking
level
EBGP peer protection (level 2 threshold
Level-1
IS-IS ATT bit Level-1 LSP, 157
limiting
BGP routes received (peer/peer group)(IPv4),
BGP routes received (peer/peer group)(IPv6),
link
EBGP direct connection after link failure, 276
IPv6 IS-IS automatic link cost calculation, 491
IS-IS automatic cost calculation, 145
OSPF virtual link configuration, 121
link state
advertising OSPF information to BGP, 103
list
routing policy COMMUNITY list,
routing policy extended community list,
routing policy IP prefix list, 518
routing policy prefix list, 517
LLDP
568
DCN LLDP frame ARP entry enable, 533
DCN LLDP frame source MAC address, 532
DCN LLDP management address
IP routing ECMP route max number, 5
IPv4 BGP load balancing configuration, 329
load sharing
local
BGP default local preference, 254
BGP local AS number appearance, 263
BGP local network injection, 228
BGP LOCAL_PREF path attribute, 195
BGP MPLS local label update delay, 292
IPv6 PBR local configuration, 512
IPv6 PBR local configuration (packet
PBR configuration (local), 390
PBR configuration (local/packet type-based),
logging
BGP route flapping logging, 304
BGP session state change logging, 303
IS-IS neighbor state change, 159
OSPF neighbor state change, 91
loop
OSPFv3 neighbor state change logging, 450
RIP routing loop prevention, 25
LS
BGP link state (LS) AS number, 313
BGP link state (LS) route reflection, 312
BGP link state (LS) router ID, 313
LSA
OSPF exit overflow interval, 90
OSPF LSA generation interval, 87
OSPF LSA retransmission packet timer, 85
OSPF LSA transmission delay, 86
OSPF LSDB external LSAs max, 90
OSPF outbound LSA filtering (specified neighbor),
OSPFv3 inter-area-prefix LSA, 437
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 inter-area-router LSA, 437
OSPFv3 intra-area-prefix LSA, 437
OSPFv3 LSA generation interval, 448
OSPFv3 LSA transmission delay, 448
LSAck
LSDB
IPv6 IS-IS LSDB overload bit, 493
OSPF LSDB external LSAs max, 90
LSP
IS-IS ATT bit Level-1 LSP, 157
IS-IS LSP fragment extension, 154
LSR
IS-IS route summarization, 146
LSU
M
MAC addressing
DCN LLDP frame source MAC address, 532
569
maintaining
managing
BGP large scale network management, 201
manual
BGP route summarization (IPv4), 233
BGP route summarization (IPv6), 233
mapping
IS-IS system ID > host name mapping, 158
IS-IS system ID > host name mapping
IS-IS system ID > host name mapping (static),
matching
IPv6 PBR node match criteria, 511
routing policy if-match clause,
MD5
BGP peer MD5 authentication, 279
MED
BGP attribute configuration, 256
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
memory
EBGP peer protection (low memory
message
RIPv1 message zero field check enable, 35
RIPv2 message authentication configuration, 35
metric
RIP additional routing metric configuration, 29
RIP interface additional metric configuration, 48
MIB
RIPng routing metric configuration, 414
mode
IPv6 static route BFD control (direct next hop),
IPv6 static route BFD control (indirect next hop),
IPv6 static route BFD echo (single hop), 402
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
static routing BFD single-hop echo mode, 12
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP FRR configuration, 349
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP FRR configuration, 378
IPv6 BGP route reflector configuration, 364
MPLS
BGP 6PE optional capabilities, 310
IPv6 BGP 6PE configuration, 367
routing policy extended community list, 517
MPU
570
MTR
MTU
OSPF DD packet interface MTU, 89
OSPFv3 DD packet ignore MTU check, 449
multicast
EBGP peer group configuration (IPv4
EBGP peer group configuration (IPv6
IBGP peer group configuration (IPv4 multicast
IBGP peer group configuration (IPv6 multicast
RIPng basic configuration, 413
multicast BGP dynamic peer configuration (IPv4 multicast
dynamic peer configuration (IPv6 multicast
IPv4 BGP dynamic peer configuration, 357
peer configuration (IPv4 multicast address),
peer configuration (IPv6 multicast address),
Multiprotocol Extensions for BGP-4.
N naming
IS-IS system ID > host name mapping, 158
NBMA
OSPF interface network type, 77
OSPFv3 network type (interface), 442
ND
OSPFv3 IPsec profile configuration, 484
OSPFv3 neighbor state change logging, 450
OSPFv3 route redistribution, 470
neighbor
IS-IS authentication (neighbor relationship), 162
IS-IS neighbor state change logging, 159
OSPF neighbor state change logging, 91
OSPF outbound LSAs (specified neighbor), 96
RIP neighbor specification, 36
neighbor discovery
OSPFv3 area configuration (NSSA), 465
OSPFv3 area configuration (stub), 461
OSPFv3 DR election configuration, 467
NET
network advertising OSPF link state information to BGP,
BGP 4-byte AS number suppression, 278
BGP 6PE optional capabilities, 310
BGP AS number substitution, 266
BGP AS_PATH attribute ignore, 265
BGP community configuration, 295
BGP default local preference, 254
BGP default route advertisement (peer/peer
BGP fake AS number advertisement, 265
BGP first send default route update, 238
BGP IGP route redistribution, 230
BGP keepalive interval+hold time configuration,
BGP link state (LS) AS number, 313
BGP link state (LS) route reflection, 312
BGP link state (LS) router ID, 313
BGP local network injection, 228
571
BGP MPLS local label update delay, 292
BGP optimal route advertisement, 235
BGP peer keychain authentication, 280
BGP peer MD5 authentication, 279
BGP per-prefix label allocation enable, 294
BGP private AS number removal, 268
BGP route filtering policy, 241
BGP route flapping logging, 304
BGP route update interval, 274
BGP routes received (peer/peer group), 239
BGP session establishment disable, 283
BGP session state change logging, 303
BGP SNMP notification enable, 303
BGP suboptimal route flush to RIB, 292
BGP TCP connection source address, 227
DCN LLDP frame ARP entry enable, 533
DCN LLDP frame source MAC address, 532
DCN LLDP management address
DCN NE ID+IP configuration, 531
EBGP peer protection (low memory
EBGP session establishment (multiple hop),
entity title.
EVPN-based service chain PBR configuration,
flushing route attribute information from RIB to
interface exclusion from the base topology in an
IP routing dynamic routing protocols, 2
IP routing ECMP route max number, 5
IP routing extension attribute redistribution, 3
IP routing FIB route max lifetime, 4
IP routing inter-protocol FRR, 6
IP routing IPv4 RIB inter-protocol FRR, 7
IP routing IPv6 RIB inter-protocol FRR, 7
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
IP routing route preference, 2
IP routing route redistribution, 3
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP dynamic peer configuration, 357
IPv4 BGP FRR configuration, 349
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration, 329
IPv4 BGP received route preferred value, 251
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv4 multicast BGP configuration, 353
IPv6 BGP 6PE configuration, 367
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP FRR configuration, 378
IPv6 BGP packet IPsec configuration, 373
IPv6 BGP received route preferred value, 251
IPv6 BGP route reflector configuration, 364
IPv6 IS-IS automatic link cost calculation, 491
IPv6 IS-IS basic configuration,
IPv6 IS-IS FRR configuration, 505
IPv6 IS-IS interface cost, 491
IPv6 IS-IS interface tag value, 493
572
IPv6 IS-IS LSDB overload bit, 493
IPv6 IS-IS network optimization, 492
IPv6 IS-IS network tuning, 492
IPv6 IS-IS prefix suppression, 494
IPv6 IS-IS route convergence priority, 492
IPv6 IS-IS SPF calculation interval, 493
IPv6 multicast BGP configuration, 382
IPv6 PBR interface configuration, 512
IPv6 PBR local configuration, 512
IPv6 PBR node match criteria, 511
IPv6 PBR policy configuration, 511
IPv6 PBR-Track collaboration, 510
IPv6 static route BFD configuration, 401
IPv6 static route BFD control mode (direct
IPv6 static route BFD control mode (indirect
IPv6 static route BFD echo mode (single hop),
IPv6 static route configuration, 401
IS-IS authentication (area), 162
IS-IS authentication (neighbor relationship),
IS-IS authentication (routing domain), 163
IS-IS automatic cost calculation, 145
IS-IS basic configuration, 142
IS-IS basics configuration, 169
IS-IS DIS election configuration, 174
IS-IS hello packet send interval, 150
573
IS-IS interface DIS priority, 151
IS-IS interface hello packet send, 152
IS-IS interface P2P network type, 143
IS-IS interface packet send/receive, 151
IS-IS interface tag value, 157
IS-IS LSP fragment extension, 154
IS-IS neighbor state change logging, 159
IS-IS network optimization, 150
IS-IS point-to-point type, 138
IS-IS route convergence priority, 156
IS-IS route redistribution, 178
IS-IS security enhancement, 162
IS-IS SPF calculation interval, 155
IS-IS system ID > host name mapping, 158
OSPF area configuration (NSSA),
OSPF area configuration (stub),
OSPF BFD detection configuration (bidirectional
OSPF BFD detection configuration (single-hop
OSPF DD packet interface MTU, 89
OSPF DR election configuration, 116
OSPF exit overflow interval, 90
OSPF host route advertisement, 84
OSPF interface network type (broadcast), 77
OSPF interface network type (NBMA), 77
OSPF interface network type (P2MP), 78
OSPF interface network type (P2P), 79
OSPF interface packet send/receive disable,
OSPF LSA generation interval, 87
OSPF LSA transmission delay, 86
OSPF LSDB external LSAs max, 90
OSPF neighbor state change logging, 91
OSPF outbound LSA filtering (interface), 96
OSPF outbound LSA filtering (specified
OSPF received route filtering, 80
OSPF RFC 1583 compatibility, 90
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF SPF calculation interval, 86
OSPF summary network discard route, 82
574
OSPF virtual link configuration, 121
OSPFv3 area configuration (NSSA),
OSPFv3 area configuration (stub),
OSPFv3 DD packet ignore MTU check, 449
OSPFv3 DR election configuration, 467
OSPFv3 Inter-Area-Prefix LSA filtering, 444
OSPFv3 interface DR priority, 449
OSPFv3 interface packet send/receive disable,
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
OSPFv3 LSA generation interval, 448
OSPFv3 LSA transmission delay, 448
OSPFv3 neighbor state change logging, 450
OSPFv3 network management, 450
OSPFv3 network type (interface), 442
OSPFv3 prefix suppression, 452
OSPFv3 received route filtering, 444
OSPFv3 SPF calculation interval, 448
outgoing RIP packet DSCP value, 38
RIP additional routing metric configuration, 29
RIP BFD configuration (bidirectional
detection/control packet mode), 59
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination), 57
RIP default route advertisement, 31
RIP host route reception disable, 31
RIP interface additional metric configuration,
RIP interface advertisement control, 28
RIP interface reception control, 28
RIP network management configuration, 37
RIP packet send rate configuration, 37
RIP poison reverse configuration, 34
RIP preference configuration, 32
RIP received/redistributed route filtering, 32
RIP route control configuration, 29
RIP route redistribution configuration, 32
RIP routing loop prevention, 25
RIP split horizon configuration, 34
RIP summary route advertisement
RIP triggered update interval configuration, 36
RIP update source IP address check, 35
RIPng default route advertisement, 415
RIPng IPsec profile application, 422
RIPng IPsec profile configuration, 433
RIPng network optimization, 416
RIPng packet zero field check, 417
RIPng received/redistributed route filtering, 415
RIPng route summarization, 414
RIPng routing metric configuration, 414
RIPng timer configuration, 416
RIPng triggered update send interval, 419
RIPv1 message zero field check, 35
RIPv2 message authentication configuration, 35
RIPv2 route summarization configuration, 30
routing policy apply clause, 522
routing policy AS_PATH list, 519 routing policy COMMUNITY list, 519
routing policy configuration, 520
routing policy configuration (IPv4 route
routing policy configuration (IPv6 route
routing policy continue clause, 524
routing policy creation, 520 routing policy extended community list, 520
routing policy filter configuration, 518
routing policy if-match clause, 521
routing policy IP prefix list, 518
routing policy-based recursive lookup, 7
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
(indirect next hop), 11 static routing BFD configuration, 11
static routing BFD single-hop echo mode, 12
static routing configuration, 10
static routing FRR configuration, 13
network element (NE)
DCN NE ID+IP configuration, 531
575
network management
IPv6 default route configuration, 411
IPv6 PBR interface configuration (packet
IPv6 PBR local configuration (packet
IPv6 static routing basic configuration, 403
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop),
IPv6 static routing configuration,
OSPFv3 network optimization, 447
PBR configuration (interface/packet
PBR configuration (local/packet type-based),
static routing basic configuration, 15
static routing BFD configuration (direct next
static routing BFD configuration (indirect next
static routing default route configuration, 24
static routing FRR configuration, 21
NEXT_HOP
BGP attribute configuration, 260
NMS
NO_ADVERTISE
BGP COMMUNITY path attribute, 195
NO_EXPORT
BGP COMMUNITY path attribute, 195
NO_EXPORT_SUBCONFED
BGP COMMUNITY path attribute, 195
node
IPv6 PBR node match criteria, 511
IPv6 PBR-Track collaboration, 510
routing policy continue clause,
routing policy deny match, 518 routing policy if-match clause,
routing policy permit match, 518
non-IETF
nonstop routing.
nonstop routing (NSR)
notifying
BGP SNMP notification enable, 303
NSAP
NSR
576
NSSA
OSPFv3 area configuration, 465
OSPFv3 area configuration (NSSA), 441
number
BGP 4-byte AS number suppression, 278
BGP AS number substitution, 266
BGP fake AS number advertisement, 265
BGP first AS number of EBGP route update
BGP local AS number appearance, 263
BGP private AS number removal, 268
O
OAM
open
Open Shortest Path First.
Open Shortest Path First version 3.
optimal
IP routing FIB table optimal routes, 1
optimizing
ORIGIN
advertising link state information to BGP, 103
authentication configuration, 88
BFD detection configuration (bidirectional
BFD detection configuration (single-hop echo),
577
DD packet interface MTU add, 89
DR election configuration, 116
FRR backup next hop calculation (LFA algorithm),
FRR backup next hop specification (routing
FRR configuration configuration, 130
interface exclusion from the base topology in an
interface network type (broadcast), 77 interface network type (NBMA), 77
interface network type (P2MP), 78
interface network type (P2P), 79
interface packet send/receive disable, 87
LSU transmit rate configuration, 92
neighbor state change logging, 91 network management configuration, 91
network optimization, 84 network tuning, 84
network type configuration, 77
nonstop routing (NSR) configuration,
outbound LSA filtering (interface), 96 outbound LSA filtering (specified neighbor), 96
packet DSCP value configuration, 90
prefix priority configuration, 94
redistributed route default parameters, 83
redistributed route summarization (ASBR), 80
route control configuration, 79
route redistribution configuration, 107
route summarization, 79 route summarization (ABR), 79
route summarization configuration, 109
summary network discard route, 82
troubleshoot configuration, 133 troubleshoot incorrect routing information, 133
troubleshoot no neighbor relationship
area parameter configuration, 440
DD packet ignore MTU check, 449
DR election configuration, 467
FRR backup next hop calculation (LFA
FRR backup next hop specification (routing
FRR configuration configuration, 482
GR restarter configuration, 454
Inter-Area-Prefix LSA filtering, 444 interface cost configuration, 444
interface DR priority, 449 interface packet send/receive disable, 449
IPsec profile application, 458
IPsec profile configuration, 484
NBMA neighbor configuration, 442
neighbor state change logging, 450 network management configuration, 450
network optimization, 447 network tuning, 447
network type configuration, 442 network type configuration (interface), 442
nonstop routing (NSR) configuration,
P2MP neighbor configuration, 442
route control configuration, 443
route redistribution (another routing protocol), 446 route redistribution (default route), 446
route summarization (ABR), 443 route summarization (ASBR), 443
stub router configuration, 451
virtual link configuration, 441
P
P2MP
OSPF interface network type, 78
P2P
578
OSPF interface network type, 79
OSPFv3 network type (interface), 442
packet
EVPN-based service chain PBR configuration,
IP routing dynamic routing protocols, 2
IP routing extension attribute redistribution, 3
IP routing route preference, 2
IP routing route redistribution, 3
IPv6 BGP packet IPsec configuration, 373
IPv6 PBR interface configuration, 512
IPv6 PBR interface configuration (packet
IPv6 PBR local configuration, 512
IPv6 PBR local configuration (packet
IPv6 PBR policy configuration, 511
IS-IS CSNP packet send interval, 151
IS-IS hello packet send interval, 150
IS-IS interface hello packet send, 152
IS-IS interface packet send/receive, 151
OSPF DD packet interface MTU, 89
OSPF exit overflow interval, 90
OSPF interface packet send/receive disable,
OSPF LSDB external LSAs max, 90
OSPF RFC 1583 compatibility, 90
OSPFv3 area configuration (NSSA), 465
OSPFv3 area configuration (stub), 461
OSPFv3 DD packet ignore MTU check, 449
OSPFv3 DR election configuration, 467
OSPFv3 interface packet send/receive disable,
OSPFv3 IPsec profile configuration, 484
OSPFv3 route redistribution, 470
outgoing RIP packet DSCP value, 38
PBR configuration (interface), 390
PBR configuration (interface/packet type-based),
PBR configuration (local), 390
PBR configuration (local/packet type-based), 391
RIP BFD configuration (bidirectional control
RIP BFD configuration (single-hop echo
RIP BFD configuration (single-hop echo
detection/specific destination), 40
RIP network management configuration, 37
RIP packet send rate configuration, 37
RIPng packet zero field check, 417
RIPng triggered update send interval, 419
parameter
IPv6 IS-IS LSDB overload bit, 493
IPv6 IS-IS SPF calculation interval, 493
579
IS-IS route convergence priority, 156
IS-IS SPF calculation interval, 155
OSPF redistributed route default parameters,
path
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
IPv4 BGP COMMUNITY configuration, 332
IPv4 multicast BGP configuration, 353
IPv6 multicast BGP configuration, 382
PBR
configuration (interface), 390
configuration (interface/packet type-based),
configuration (local/packet type-based), 391 displaying, 391
interface PBR, 386 local PBR, 386
node action configuration, 389
node creation, 388 node match criteria, 388
relationship between match mode/clauses,
PDU
PE
BGP 6PE optional capabilities, 310
peer
IPv6 BGP 6PE configuration, 367
BGP default route advertisement (peer/peer
BGP MED route comparison (confederation
BGP peer keychain authentication, 280
BGP peer MD5 authentication, 279
BGP session establishment disable, 283
EBGP peer protection (low memory exemption),
IPv4 BGP dynamic peer configuration, 357
IS-IS neighbor state change logging, 159
permitting
BGP local AS number appearance (IPv4), 263
BGP local AS number appearance (IPv6), 263
PIC
point-to-point IS-IS network type, 138
policy
BGP route distribution filtering policy, 241
BGP route filtering policy, 241
BGP route reception filtering policy, 245
EVPN-based service chain PBR configuration,
IPv6 IS-IS FRR configuration (routing policy), 496
IPv6 PBR interface configuration, 512
IPv6 PBR interface configuration (packet
IPv6 PBR local configuration, 512
IPv6 PBR local configuration (packet type-based),
IPv6 PBR match mode/node clause relationship,
IPv6 PBR policy configuration, 511
IS-IS FRR configuration (routing policy), 167
OSPF FRR backup next hop (routing policy), 102
580
OSPFv3 FRR backup next hop (routing policy),
PBR configuration (interface), 390
PBR configuration (interface/packet
PBR configuration (local), 390
PBR configuration (local/packet type-based),
routing policy apply clause, 522
routing policy AS_PATH list, 519 routing policy COMMUNITY list, 519
routing policy configuration (IPv4 route
routing policy configuration (IPv6 route
routing policy continue clause, 524
routing policy creation, 520 routing policy extended community list, 520
routing policy filter configuration, 518 routing policy filtering, 518
routing policy if-match clause, 521
routing policy IP prefix list, 518
policy-based routing.
preference
IP routing route preference, 2
preferring
BGP default local preference, 254
BGP received route preferred value, 251
IS-IS preference specification, 145
prefix
IPv6 IS-IS prefix suppression, 494
OSPFv3 prefix suppression, 452
routing policy IP prefix list, 518
routing policy prefix list, 517
Prefix Independent Convergence.
priority
IPv6 IS-IS route convergence priority, 492
IS-IS interface DIS priority, 151
IS-IS route convergence priority, 156
OSPF prefix priority configuration, 94
OSPFv3 interface DR priority, 449
procedure advertising BGP default route (peer/peer
advertising BGP default route (peer/peer
advertising BGP fake AS number (IPv4), 265 advertising BGP fake AS number (IPv6), 265
advertising BGP optimal route (IPv4 unicast), 235 advertising BGP optimal route (IPv6 unicast), 235
advertising DCN LLDP management address,
advertising IS-IS default route, 147
advertising IS-IS link state information to BGP,
advertising RIP default route, 31
advertising RIPng default route, 415
advertising RIPv2 summary route, 30
applying OSPFv3 IPsec profile, 458
applying RIPng IPsec profile, 422
assigning IPv6 IS-IS route convergence priority,
clearing IPv4 BGP information, 318 clearing IPv6 BGP information, 318
configuring BGP 6PE, 309 configuring BGP 6PE basics, 309
configuring BGP 6PE optional capabilities, 310
configuring BGP AS number substitution (IPv4),
configuring BGP AS number substitution (IPv6),
configuring BGP AS_PATH attribute, 263
configuring BGP BFD (IPv4), 305 configuring BGP BFD (IPv6), 305
configuring BGP COMMUNITY (IPv4), 295 configuring BGP COMMUNITY (IPv6), 295
configuring BGP confederation, 300
configuring BGP confederation compatibility, 301
configuring BGP default local preference (IPv4),
configuring BGP default local preference (IPv6),
581
configuring BGP dynamic peer (IPv4 multicast
configuring BGP dynamic peer (IPv4 unicast
configuring BGP dynamic peer (IPv6 multicast
configuring BGP dynamic peer (IPv6 unicast
configuring BGP first send default route
configuring BGP FRR (IPv4 unicast address),
configuring BGP FRR (IPv6 unicast address),
configuring BGP GTSM (IPv4), 284 configuring BGP GTSM (IPv6), 284
configuring BGP keepalive interval+hold time,
configuring BGP large-scale network, 294
configuring BGP link state (LS) route reflection,
configuring BGP MED attribute, 256
configuring BGP MED default value (IPv4),
configuring BGP MED default value (IPv6),
configuring BGP Monitoring Protocol (BMP),
configuring BGP MPLS local label update
configuring BGP NEXT_HOP attribute (IPv4),
configuring BGP NEXT_HOP attribute (IPv6),
configuring BGP peer (IPv4 multicast
configuring BGP peer (IPv4 unicast address),
configuring BGP peer (IPv6 multicast
configuring BGP peer (IPv6 unicast address),
configuring BGP route dampening (IPv4), 249 configuring BGP route dampening (IPv6), 249
configuring BGP route distribution filtering
configuring BGP route distribution filtering
policy (IPv6), 241 configuring BGP route filtering policy, 241
configuring BGP route preference (IPv4), 252
582
configuring BGP route preference (IPv6), 252
configuring BGP route reception filtering policy
configuring BGP route reception filtering policy
configuring BGP route summarization
configuring BGP route summarization
configuring BGP route summarization
configuring BGP route update delay, 248
configuring BGP route update interval (IPv4), 274 configuring BGP route update interval (IPv6), 274
configuring BGP soft reset, 285
configuring BGP soft reset manually (IPv4), 288 configuring BGP soft reset manually (IPv6), 288
configuring BGP SoO attribute (IPv4), 270 configuring BGP SoO attribute (IPv6), 270
configuring DCN LLDP frame source MAC
configuring DCN NE ID+IP, 531 configuring DCN VPN, 531
configuring EBGP peer group (IPv4 multicast
configuring EBGP peer group (IPv4 unicast
configuring EBGP peer group (IPv6 multicast
configuring EBGP peer group (IPv6 unicast
configuring EVPN-based service chain PBR, 394
configuring IBGP peer group (IPv4 multicast
configuring IBGP peer group (IPv4 unicast
configuring IBGP peer group (IPv6 multicast
configuring IBGP peer group (IPv6 unicast
configuring inter-protocol FRR, 6
configuring IP routing BGP LS, 312
configuring IP routing RIB NSR, 6
configuring IP routing RIP GR, 52 configuring IP routing RIP NSR, 52
configuring IPv4 BGP basics, 319
configuring IPv4 BGP COMMUNITY, 332
configuring IPv4 BGP confederation, 337
configuring IPv4 BGP dynamic peer, 357
configuring IPv4 BGP load balancing, 329
configuring IPv4 BGP path selection, 341
configuring IPv4 BGP route reflector, 335
configuring IPv4 BGP route summarization,
configuring IPv4 BGP+IGP route redistribution,
configuring IPv4 multicast BGP, 353
configuring IPv4 RIB inter-protocol FRR, 7
configuring IPv6 BGP basics, 361
configuring IPv6 BGP IPsec, 282
configuring IPv6 BGP packet IPsec, 373
configuring IPv6 BGP route reflector, 364
configuring IPv6 IS-IS basics,
configuring IPv6 IS-IS FRR (routing policy),
configuring IPv6 IS-IS FRR automatic backup
configuring IPv6 IS-IS global cost, 491 configuring IPv6 IS-IS interface cost, 491
configuring IPv6 IS-IS interface tag value, 493
configuring IPv6 IS-IS link cost, 491
configuring IPv6 IS-IS route control, 490
configuring IPv6 multicast BGP, 382
configuring IPv6 PBR interface, 512
configuring IPv6 PBR interface (packet
configuring IPv6 PBR local, 512
configuring IPv6 PBR local (packet
configuring IPv6 RIB inter-protocol FRR, 7
configuring IPv6 static route, 401 configuring IPv6 static route BFD, 401
configuring IPv6 static route BFD control
configuring IPv6 static route BFD control mode
configuring IPv6 static route BFD echo mode
configuring IPv6 static routing, 403 configuring IPv6 static routing basics, 403
configuring IPv6 static routing BFD (direct next
configuring IPv6 static routing BFD (indirect next
configuring IS-IS ATT bit, 157
configuring IS-IS ATT bit default route calculation,
configuring IS-IS authentication, 181
configuring IS-IS authentication (area), 162
configuring IS-IS authentication (neighbor
configuring IS-IS authentication (routing domain),
configuring IS-IS DIS election, 174
configuring IS-IS ECMP routes max, 146
configuring IS-IS FRR (routing policy), 167
configuring IS-IS FRR backup next hop (LFA
configuring IS-IS global cost, 145
configuring IS-IS interface cost, 145
configuring IS-IS interface DIS priority, 151
configuring IS-IS interface P2P network type, 143
configuring IS-IS interface tag value, 157
configuring IS-IS link cost, 144
configuring IS-IS LSP parameters, 152 configuring IS-IS LSP timer, 152
configuring IS-IS LSP-calculated route filtering,
configuring IS-IS network management, 160
configuring IS-IS redistributed route filtering, 148
configuring IS-IS route control, 144
configuring IS-IS route convergence priority, 156
configuring IS-IS route filtering, 148
configuring IS-IS route leaking, 149
configuring IS-IS route redistribution,
configuring IS-IS route summarization, 146
configuring IS-IS system ID > host name mapping,
583
configuring IS-IS system ID > host name
configuring IS-IS system ID > host name
configuring OSPF authentication (area), 88
configuring OSPF authentication (interface),
configuring OSPF BFD detection (bidirectional
configuring OSPF BFD detection (single-hop
configuring OSPF DD packet interface MTU,
configuring OSPF DR election, 116
configuring OSPF FRR backup next hop
configuring OSPF FRR backup next hop
calculation (LFA algorithm), 101
configuring OSPF GR helper (IETF), 98
configuring OSPF GR helper (non-IETF), 99
configuring OSPF GR restarter, 97
configuring OSPF GR restarter (IETF), 98 configuring OSPF GR restarter (non-IETF), 98
configuring OSPF host route advertisement,
configuring OSPF interface cost, 81
configuring OSPF interface network type
configuring OSPF interface network type
configuring OSPF interface network type
configuring OSPF interface network type
configuring OSPF LSU transmit rate, 92
configuring OSPF network management, 91
configuring OSPF network type, 77
configuring OSPF packet DSCP value, 90
configuring OSPF preference, 82
584
configuring OSPF prefix priority, 94
configuring OSPF prefix suppression (interface),
configuring OSPF prefix suppression (OSPF
configuring OSPF received route filtering, 80
configuring OSPF redistributed route default
configuring OSPF redistributed route
configuring OSPF route control, 79
configuring OSPF route redistribution, 107
configuring OSPF route redistribution (another
configuring OSPF route redistribution (default
configuring OSPF route summarization, 109
configuring OSPF route summarization (ABR), 79
configuring OSPF stub router, 88
configuring OSPF summary network discard
configuring OSPF Type-3 LSA filtering, 80
configuring OSPF virtual link,
configuring OSPFv3 area (NSSA),
configuring OSPFv3 area (stub),
configuring OSPFv3 area parameter, 440
configuring OSPFv3 authentication, 453
configuring OSPFv3 BFD configuration, 479
configuring OSPFv3 DR election, 467
configuring OSPFv3 FRR backup next hop
configuring OSPFv3 FRR backup next hop
calculation (LFA algorithm), 457 configuring OSPFv3 FRR BFD, 457
configuring OSPFv3 GR helper, 454 configuring OSPFv3 GR restarter, 454
configuring OSPFv3 Inter-Area-Prefix LSA
filtering, 444 configuring OSPFv3 interface cost, 444
configuring OSPFv3 interface DR priority, 449
configuring OSPFv3 IPsec profile, 484
configuring OSPFv3 LSU transmit rate, 451
configuring OSPFv3 NBMA neighbor, 442
configuring OSPFv3 network management, 450
configuring OSPFv3 network type, 442 configuring OSPFv3 network type (interface), 442
configuring OSPFv3 P2MP neighbor, 442
configuring OSPFv3 preference, 445
configuring OSPFv3 prefix suppression
configuring OSPFv3 prefix suppression
configuring OSPFv3 received route filtering,
configuring OSPFv3 redistributed route tag,
configuring OSPFv3 route control, 443
configuring OSPFv3 route redistribution, 470
configuring OSPFv3 route redistribution
(another routing protocol), 446
configuring OSPFv3 route redistribution
configuring OSPFv3 route summarization,
configuring OSPFv3 route summarization
configuring OSPFv3 route summarization
configuring OSPFv3 stub router, 451
configuring OSPFv3 virtual link, 441
configuring PBR (interface), 390
configuring PBR (interface/packet
configuring PBR (local/packet type-based),
configuring PBR node action, 389
configuring PBR node match criteria, 388 configuring PBR policy, 388
configuring RIP additional routing metric, 29
configuring RIP BFD (bidirectional control
configuring RIP BFD (bidirectional
detection/control packet mode), 59
configuring RIP BFD (single-hop echo
configuring RIP BFD (single-hop echo
configuring RIP BFD (single-hop echo
detection/specific destination),
configuring RIP interface additional metric, 48
configuring RIP network management, 37 configuring RIP packet send rate, 37
585 configuring RIP received/redistributed route
configuring RIP route control, 29
configuring RIP route redistribution,
configuring RIP split horizon, 34
configuring RIP summary route advertisement, 49
configuring RIPng, 413 configuring RIPng basics,
configuring RIPng IPsec profile configuration, 433
configuring RIPng packet send rate, 418
configuring RIPng packet zero field check, 417 configuring RIPng poison reverse, 417
configuring RIPng received/redistributed route
configuring RIPng route control, 414
configuring RIPng route redistribution,
configuring RIPng route summarization, 414 configuring RIPng routing metric, 414
configuring RIPng split horizon, 417
configuring RIPv2 message authentication, 35
configuring RIPv2 route summarization, 30
configuring routing policy, 520
configuring routing policy (IPv4 route
configuring routing policy (IPv6 route
configuring routing policy apply clause, 522
configuring routing policy AS_PATH list, 519 configuring routing policy COMMUNITY list, 519
configuring routing policy continue clause, 524
configuring routing policy extended community list,
configuring routing policy filter, 518
configuring routing policy if-match clause, 521
configuring routing policy IPv4 prefix list, 518
configuring routing policy IPv6 prefix list, 519
configuring routing policy MAC list, 520
configuring routing policy-based recursive lookup,
configuring startup policy for BGP route updates,
configuring static route BFD, 11
configuring static route FRR (auto backup next
configuring static routing, 15
configuring static routing basics, 15
configuring static routing BFD (direct next
configuring static routing BFD (indirect next
configuring static routing BFD bidirectional
control mode (direct next hop), 11
configuring static routing BFD bidirectional
control mode (indirect next hop), 11
configuring static routing BFD single-hop echo
configuring static routing default route, 24
configuring static routing FRR,
configuring static routing FRR (backup next
controlling BGP path selection, 251
controlling BGP route distribution, 232 controlling BGP route reception, 232
controlling IPv6 IS-IS SPF calculation interval,
controlling IS-IS SPF calculation interval, 155
controlling RIP interface advertisement, 28 controlling RIP interface reception, 28
disabling BGP optimal route selection for
disabling BGP session establishment (IPv4),
disabling BGP session establishment (IPv6),
disabling IS-IS interface packet send/receive,
disabling OSPF interface packet send/receive,
disabling OSPFv3 interface packet
disabling recursion policy for routes received
from a peer or peer group, 293
disabling RIP host route reception, 31
displaying IP routing table, 8
displaying IPv4 BGP, 314 displaying IPv6 BGP, 314
displaying IPv6 static routing, 403
586
displaying routing policy, 524
enabling BGP 4-byte AS number suppression
enabling BGP 4-byte AS number suppression
enabling BGP load balancing (IPv4), 281 enabling BGP load balancing (IPv6), 281
enabling BGP MED route comparison
enabling BGP MED route comparison (diff ASs),
enabling BGP MED route comparison (per-AS),
enabling BGP ORF capabilities, 276
enabling BGP peer keychain authentication
enabling BGP peer keychain authentication
enabling BGP peer MD5 authentication (IPv4),
enabling BGP peer MD5 authentication (IPv6),
enabling BGP per-prefix label allocation, 294
enabling BGP route flapping logging (IPv4), 304 enabling BGP route flapping logging (IPv6), 304
enabling BGP route-refresh (IPv4), 285 enabling BGP route-refresh (IPv6), 285
enabling BGP session state change logging
enabling BGP session state change logging
(IPv6), 303 enabling BGP SNMP notification, 303
enabling DCN automatic report, 532
enabling DCN LLDP frame ARP entry, 533
enabling EBGP direct connections upon link
enabling EBGP session establishment (multiple
enabling EBGP session establishment (multiple
enabling IPv6 BGP MED AS route comparison
enabling IPv6 IS-IS automatic link cost calculation,
enabling IPv6 IS-IS FRR BFD, 496
enabling IPv6 IS-IS prefix suppression, 494
enabling IS-IS automatic cost calculation, 145
enabling IS-IS FRR BFD (control packet
enabling IS-IS FRR BFD (echo packet mode),
enabling IS-IS interface hello packet send,
enabling IS-IS LSP flash flooding, 154 enabling IS-IS LSP fragment extension, 154
enabling IS-IS neighbor state change logging,
enabling IS-IS PIC, 161 enabling IS-IS PIC BFD, 161
enabling IS-IS prefix suppression, 159
enabling OSPF (interface), 74 enabling OSPF (network), 74
enabling OSPF neighbor state change logging,
enabling OSPF RFC 1583 compatibility, 90
enabling OSPFv3 neighbor state change
enabling RIP poison reverse, 34, 34 enabling RIP split horizon, 34
enabling RIP update source IP address check,
enabling RIPv1 message zero field check, 35
enabling RIPv2 automatic route
enabling static routing FRR BFD echo packet
enabling the device to advertise OSPF link
enhancing IS-IS network security, 162
excluding interfaces in an OSPF area from the
filtering OSPF outbound LSA (interface), 96
filtering OSPF outbound LSAs (specified
flushing BGP suboptimal route to RIB, 292
flushing route attribute information from RIB to
587
ignoring BGP AS_PATH attribute, 265
ignoring BGP first AS number of EBGP route
ignoring BGP IGP metrics during optimal route
ignoring BGP ORIGINATOR_ID attribute (IPv4),
ignoring BGP ORIGINATOR_ID attribute (IPv6),
ignoring OSPFv3 DD packet MTU check, 449
injecting BGP local network (IPv4), 228 injecting BGP local network (IPv6), 228
limiting BGP routes received (peer/peer
limiting BGP routes received (peer/peer
limiting IS-IS LSP flooding, 154
maintaining IP routing table, 8
maintaining routing policy, 524
optimizing IPv6 IS-IS networks, 492
optimizing IS-IS networks, 150
optimizing OSPFv3 network, 447
permitting BGP local AS number appearance
permitting BGP local AS number appearance
protecting EBGP peer (low memory
protecting EBGP peer (low memory
redistributing BGP IGP route, 230
removing BGP private AS number from EBGP
peer/peer group update (IPv4), 268
removing BGP private AS number from EBGP
peer/peer group update (IPv6), 268
resetting IPv4 BGP sessions, 318 resetting IPv6 BGP sessions, 318
saving BGP route update (IPv4), 287 saving BGP route update (IPv6), 287
setting BGP outgoing packet DSCP value, 293
setting BGP received route preferred value
setting BGP received route preferred value
setting BGP session retry timer (IPv4), 273 setting BGP session retry timer (IPv6), 273
setting IP routing ECMP route max number, 5
setting IPv6 IS-IS LSDB overload bit, 493
setting IS-IS ATT bit Level-1 LSP, 157
setting IS-IS IS+circuit level, 143
setting IS-IS LSDB overload bit, 156
setting OSPF ECMP routes max, 82
setting OSPF exit overflow interval, 90
setting OSPF LSA transmission delay, 86
setting OSPF LSDB external LSAs max, 90
setting OSPFv3 ECMP route max, 445
setting outgoing RIP packet DSCP value, 38
setting RIP ECMP route max number, 34
setting RIP packet max length, 38
setting RIP triggered update interval, 36
setting RIPng ECMP route max, 418
setting RIPng triggered update send interval,
specifying BGP link state (LS) AS number,
313 specifying BGP link state (LS) router ID, 313
specifying BGP TCP connection source
specifying BGP TCP connection source
specifying IS-IS CSNP packet send interval,
specifying IS-IS hello multiplier, 150
specifying IS-IS hello packet send interval,
specifying IS-IS LSP length, 153
specifying IS-IS preference, 145
specifying OSPF LSA arrival interval, 86
specifying OSPF LSA generation interval, 87
specifying OSPF SPF calculation interval, 86
troubleshooting BGP peer connection state, 385
troubleshooting OSPF incorrect routing
troubleshooting OSPF no neighbor relationship
tuning IP routing OSPF network, 84
tuning IPv6 IS-IS network, 492
profile
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
protecting
EBGP peer (low memory exemption)(IPv4), 291
EBGP peer (low memory exemption)(IPv6), 291
protocols and standards
IP routing dynamic routing protocols, 2
OSPF RFC 1583 compatibility, 90
R rate
receiving
BGP routes received (peer/peer group), 239
IS-IS interface packet send/receive, 151
OSPF interface packet send/receive disable, 87
OSPF received route filtering, 80
OSPFv3 interface packet send/receive disable,
RIPng received/redistributed route filtering, 415
recursion
BGP load balancing through route recursion, 200
disabling recursion policy for routes received from
588
redistributing
IP routing extension attribute redistribution, 3
IP routing route redistribution, 3
IPv4 BGP+IGP route redistribution, 323
IS-IS redistributed route filtering, 148
OSPF redistributed route default parameters,
OSPF route redistribution configuration, 107
OSPFv3 redistributed route tag, 447
OSPFv3 route redistribution (another routing
OSPFv3 route redistribution (default route),
RIP received/redistributed route filtering, 32
RIPng received/redistributed route filtering,
refreshing
removing
BGP private AS number from EBGP peer/peer
BGP private AS number from EBGP peer/peer
reporting
DCN automatic report enable, 532
resetting
restrictions
RFC 1583 compatibility (OSPF), 90
RIB
BGP suboptimal route flush to RIB, 292
flushing route attribute information from RIB to
IP routing FIB route max lifetime, 4
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
589
additional routing metric configuration, 29
BFD configuration (bidirectional control detection),
BFD configuration (bidirectional detection/control
BFD configuration (single-hop echo detection)(on
BFD configuration (single-hop echo
BFD configuration (single-hop echo
detection/specific destination),
default route advertisement, 31
FRR configuration restrictions,
GR restarter configuration, 38
host route reception disable, 31
interface additional metric configuration, 48
interface advertisement control, 28 interface reception control, 28
IPv6.
network management configuration, 37
network optimization, 33 network tuning, 33
nonstop routing (NSR) enable, 39
outgoing packet DSCP value, 38 packet max length, 38
packet send rate configuration, 37
poison reverse configuration, 34 poison reverse enable, 34
received/redistributed route filtering, 32
RIPv1 message zero field check enable, 35
RIPv2 message authentication configuration, 35
RIPv2 route summarization configuration, 30
route control configuration, 29
route redistribution configuration, 32
split horizon configuration, 34 split horizon enable, 34
summary route advertisement configuration,
triggered update interval configuration, 36
update source IP address check, 35
default route advertisement, 415
IPsec profile application, 422
IPsec profile configuration, 433
network optimization, 416 network tuning, 416
packet send rate configuration, 418
packet zero field check, 417 poison reverse configuration, 417
received/redistributed route filtering, 415
route redistribution configuration, 416
route summarization, 414 routing metric configuration, 414
split horizon configuration, 417
triggered update send interval configuration,
RIPv1
message zero field check enable, 35
RIPv2
automatic route summarization enable, 30
message authentication configuration, 35
route summarization configuration, 30 summary route advertisement, 30
route
BGP default route advertisement (peer/peer
BGP first send default route update, 238
BGP IGP route redistribution, 230
BGP link state (LS) route reflection, 312
BGP MED route comparison (confederation
BGP MED route comparison (diff ASs), 258
BGP MED route comparison (per-AS), 258
BGP optimal route advertisement, 235
BGP optimal route selection disable for labeled
BGP ORIGINATOR_ID attribute ignore, 299
BGP route advertisement rules, 199
BGP route distribution control, 232
BGP route distribution filtering policy, 241
BGP route filtering policy, 241
BGP route flapping logging, 304
BGP route reception control, 232
BGP route reception filtering policy, 245
BGP route update interval, 274
BGP route-refresh message, 195
BGP routes received (peer/peer group), 239
BGP suboptimal route flush to RIB, 292
flushing route attribute information from RIB to
IP routing ECMP route max number, 5
IP routing FIB route max lifetime, 4
IP routing FIB table optimal routes, 1
IP routing inter-protocol FRR, 6
590
IP routing IPv4 RIB inter-protocol FRR, 7
IP routing IPv6 RIB inter-protocol FRR, 7
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
IP routing route preference, 2
IP routing route redistribution, 3
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv6 BGP route reflector configuration, 364
IPv6 default route configuration, 411
IPv6 IS-IS route convergence priority, 492
IPv6 static route BFD configuration, 401
IPv6 static route BFD control mode (direct
IPv6 static route BFD control mode (indirect
IPv6 static route BFD echo mode (single hop),
IPv6 static route configuration, 401
IPv6 static routing basic configuration, 403
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop),
IPv6 static routing configuration,
IS-IS default route advertisement, 147
IS-IS LSP-calculated route filtering, 148
IS-IS redistributed route filtering, 148
IS-IS route summarization, 146
OSPF area configuration (NSSA), 114
OSPF area configuration (stub), 112
OSPF host route advertisement, 84
OSPF received route filtering, 80
OSPF redistributed route default parameters,
OSPF redistributed route summarization
OSPF route redistribution configuration, 107
OSPF route summarization (ABR), 79
OSPF route summarization configuration, 109
OSPF summary network discard route, 82
OSPFv3 received route filtering, 444
OSPFv3 redistributed route tag, 447
OSPFv3 route redistribution (another routing
OSPFv3 route redistribution (default route), 446
OSPFv3 route summarization (ASBR), 443
RIP default route advertisement, 31
RIP host route reception disable, 31
RIP poison reverse configuration, 34
RIP preference configuration, 32
RIP received/redistributed route filtering, 32
RIP route control configuration, 29
RIP route redistribution configuration, 32
RIP split horizon configuration, 34
RIP update source IP address check, 35
RIPng default route advertisement, 415
RIPng received/redistributed route filtering, 415
RIPng route summarization, 414
RIPv1 message zero field check, 35
RIPv2 summary route advertisement, 30
static routing basic configuration, 15
static routing BFD configuration, 11
static routing BFD configuration (direct next hop),
static routing BFD configuration (indirect next
static routing default route configuration, 24
static routing FRR configuration,
router
BGP link state (LS) router ID, 313
591
IS-IS interface P2P network type, 143
routing
BGP Monitoring Protocol (BMP) configuration,
IPv6 BGP packet IPsec configuration, 373
IPv6 default route.
See under IPv6 static routing
IPv6 IS-IS.
IPv6 policy-based routing.
IPv6 static routing.
OSPFv3 route redistribution, 470
policy-based routing.
Routing Information Protocol.
routing policy
rule
BGP route advertisement rules, 199
S saving
searching
security
IPv6 BGP packet IPsec configuration, 373
IPv6 IS-IS prefix suppression, 494
IS-IS authentication (area), 162
IS-IS authentication (neighbor relationship), 162
IS-IS authentication (routing domain), 163
IS-IS network security enhancement, 162
OSPF authentication (area), 88
OSPF authentication (interface), 89
OSPFv3 IPsec profile application, 458
OSPFv3 IPsec profile configuration, 484
OSPFv3 prefix suppression, 452
RIPng IPsec profile application, 422
SEL
RIPng IPsec profile configuration, 433
selecting
BGP load balancing through route selection, 200
IPv4 multicast BGP configuration, 353
IPv6 multicast BGP configuration, 382
sending
BGP first send default route update, 238
IS-IS CSNP packet send interval, 151
IS-IS hello packet send interval, 150
IS-IS interface hello packet send, 152
IS-IS interface packet send/receive, 151
OSPF interface packet send/receive disable, 87
OSPFv3 interface packet send/receive disable,
RIPng triggered update send interval, 419
session
BGP Monitoring Protocol (BMP) configuration,
BGP session establishment disable, 283
BGP session state change logging, 303
EBGP session establishment (multiple hop), 275
setting
BGP outgoing packet DSCP value, 293
BGP received route preferred value (IPv4), 251
BGP received route preferred value (IPv6), 251
BGP session retry timer (IPv4), 273
BGP session retry timer (IPv6), 273
592
flushing route attribute information from RIB to
IP routing ECMP route max number, 5
IP routing FIB route max lifetime, 4
IP routing RIB label max lifetime, 4
IP routing RIB route max lifetime, 4
IPv6 IS-IS LSDB overload bit, 493
IS-IS ATT bit Level-1 LSP, 157
OSPF exit overflow interval, 90
OSPF LSA transmission delay, 86
OSPF LSDB external LSAs max, 90
OSPFv3 LSA generation interval, 448
OSPFv3 LSA transmission delay, 448
OSPFv3 SPF calculation interval, 448
outgoing RIP packet DSCP value, 38
RIP triggered update interval, 36
RIPng triggered update send interval, 419
SNMP
BGP SNMP notification enable, 303
soft reset
SoO
BGP attribute configuration, 270
source
DCN LLDP frame source MAC address, 532
RIP source IP address check, 35
speaker
specifying
BGP link state (LS) AS number, 313
BGP link state (LS) router ID, 313
BGP TCP connection source address, 227
BGP TCP connection source address (IPv4), 227
BGP TCP connection source address (IPv6), 227
IS-IS CSNP packet send interval, 151
IS-IS hello packet send interval, 150
OSPF LSA generation interval, 87
OSPF SPF calculation interval, 86
SPF
IPv6 IS-IS calculation interval, 493
IS-IS calculation interval, 155
OSPF SPF calculation interval, 86
OSPFv3 SPF calculation interval, 448
state
BGP session state change logging, 303
OSPF neighbor state change logging, 91
static
IS-IS system ID > host name mapping, 158
routing.
static routing
BFD configuration (direct next hop), 16
BFD configuration (indirect next hop), 19
default route configuration, 24
IPv6.
static routing BFD bidirectional control mode
static routing BFD bidirectional control mode
(indirect next hop), 11 static routing BFD configuration, 11
static routing BFD single-hop echo mode, 12
static routing FRR configuration, 13
stub
OSPF area configuration (stub), 75
OSPFv3 area configuration, 461
OSPFv3 area configuration (stub), 440
593
substituting
BGP AS number substitution, 266
summarizing
IPv4 BGP route summarization, 326
IS-IS route summarization, 146
OSPF redistributed route summarization
OSPF route summarization (ABR), 79
OSPF route summarization configuration, 109
OSPF summary network discard route, 82
OSPFv3 route summarization, 473
OSPFv3 route summarization (ABR), 443
OSPFv3 route summarization (ASBR), 443
RIPng route summarization, 414
RIPv2 automatic route summarization enable,
RIPv2 route summarization configuration, 30
RIPv2 summary route advertisement, 30
suppressing
BGP 4-byte AS number suppression, 278
IPv6 IS-IS prefix suppression, 494
OSPFv3 prefix suppression, 452
switch
OSPF area configuration (NSSA), 114
OSPF area configuration (stub), 112
OSPF DR election configuration, 116
OSPF route redistribution configuration, 107
OSPF route summarization configuration, 109
OSPF virtual link configuration, 121
OSPFv3 area configuration (stub), 461
system
IS-IS system ID > host name mapping, 158
T table
BGP optimal route advertisement, 235
tag
IPv6 IS-IS interface tag value, 493
IS-IS interface tag value, 157
TCP
OSPFv3 redistributed route tag, 447
BGP TCP connection source address, 227
IPv4 BGP basic configuration, 319
IPv4 BGP BFD configuration, 346
IPv4 BGP COMMUNITY configuration, 332
IPv4 BGP dynamic peer configuration, 357
IPv4 BGP FRR configuration, 349
IPv4 BGP GR configuration, 344
IPv4 BGP load balancing configuration
IPv4 BGP route reflector configuration, 335
IPv4 BGP route summarization, 326
IPv4 BGP+IGP route redistribution, 323
IPv4 multicast BGP configuration, 353
IPv6 BGP basic configuration, 361
IPv6 BGP BFD configuration, 370
IPv6 BGP FRR configuration, 378
IPv6 BGP route reflector configuration, 364
IPv6 multicast BGP configuration, 382
threshold time
EBGP peer protection (level 2 threshold), 291
timeout
timer
IS-IS LSP timer configuration, 152
OSPF LSA retransmission packet, 85
TLV
RIPng timer configuration, 416
IPv6 IS-IS basic configuration, 498
IPv6 IS-IS BFD configuration, 503
594
topology
IPv6 default route configuration, 411
IPv6 static route configuration, 401
IPv6 static routing basic configuration, 403
IPv6 static routing BFD (direct next hop), 405
IPv6 static routing BFD (indirect next hop),
IPv6 static routing configuration,
Track
static routing configuration, 10
transmitting
trapping
BGP SNMP notification enable, 303
OSPF network management, 91, 91
OSPFv3 network management, 450
triggered RIP
triggering
RIP triggered update interval, 36
RIPng triggered update send interval, 419
troubleshooting
BGP peer connection state, 385
OSPF incorrect routing information, 133
OSPF no neighbor relationship established,
TTL
tuning
tunneling
BGP optimal route selection disable for
IPv6 BGP packet IPsec configuration, 373
Type 1 external
Type 2 external
U
UDP
RIPng IPsec profile configuration, 433
RIPng route redistribution, 425
unicast
BGP dynamic peer configuration (IPv4 unicast
BGP dynamic peer configuration (IPv6 unicast
BGP FRR configuration (IPv4 unicast address),
BGP FRR configuration (IPv6 unicast address),
EBGP peer group configuration (IPv4 unicast
EBGP peer group configuration (IPv6 unicast
IBGP peer group configuration (IPv4 unicast
IBGP peer group configuration (IPv6 unicast
IP routing dynamic routing protocols, 2
IP routing extension attribute redistribution, 3
IP routing route preference, 2
IP routing route redistribution, 3
updating
BGP first send default route update, 238
BGP MPLS local label update delay, 292
BGP route update interval, 274
RIP source IP address check, 35
RIP triggered update interval, 36
595
RIPng triggered update send interval, 419
V value
BGP outgoing packet DSCP value, 293
BGP received route preferred value, 251
IPv6 IS-IS interface tag value, 493
virtual
OSPF virtual link configuration, 121
VPN
Z zero field check
596
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement