ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Routing) PDF

ZXR10 M6000
Carrier-Class Router
Configuration Guide (IPv4 Routing)
Version: V1.00.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R2.1 2011-05-10 Third release, part of the description details are modified
R2.0 2011-01-15 Second release, the document architecture is changed.
R1.0 2010-09-30 First release
Serial Number: SJ-20110504161056-013
Publishing Date: 2010-05-10 (R2.1)

Contents
About This Manual ......................................................................................... I
Chapter 1 Safety Instruction...................................................................... 1-1
1.1 Safety Instruction ............................................................................................... 1-1
1.2 Safety Signs ...................................................................................................... 1-1
Chapter 2 Static Route Configuration ...................................................... 2-1

2.1 Static Route Overview ........................................................................................ 2-1
2.2 Static Route Principle ......................................................................................... 2-1
2.3 Configuring Static Routes ................................................................................... 2-2
2.3.1 Configuring Next Hop of a Direct Route ..................................................... 2-2
2.3.2 Configuring an Out-Interface of a Static Route ........................................... 2-3
2.4 Static Route Maintenance ................................................................................... 2-5
2.5 Static Route Configuration Examples................................................................... 2-6
2.5.1 Static Route Configuration Example .......................................................... 2-6
2.5.2 Static Route Summary Configuration Example ........................................... 2-8
2.5.3 Default Route Configuration Example ........................................................ 2-9
2.6 Static Route Fault Handling................................................................................2-11
2.6.1 Network Topology....................................................................................2-11
2.6.2 Fault Analysis .........................................................................................2-11
2.6.3 Handling Flow .........................................................................................2-11
2.6.4 Handling Procedure................................................................................ 2-12
Chapter 3 RIP Configuration ..................................................................... 3-1

3.1 RIP Overview..................................................................................................... 3-1
3.1.1 RIP Route Metric and Administrative Distance............................................ 3-1
3.1.2 RIP Timers............................................................................................... 3-2
3.1.3 RIP Route Update .................................................................................... 3-2
3.2 RIP Working Principle......................................................................................... 3-2
3.3 RIP Configuration............................................................................................... 3-3
3.3.1 Configuring RIP Basic Functions ............................................................... 3-3
3.3.2 Configuring RIP Enhanced Functions ........................................................ 3-5
3.3.3 Configuring RIP Version............................................................................ 3-7
3.3.4 Configuring RIP Route Load Sharing ......................................................... 3-8
3.4 RIP Maintenance................................................................................................ 3-9
3.4.1 Common Maintenance Commands for Viewing Information......................... 3-9
I
3.4.2 Command Maintenance Commands for Debugging .................................. 3-12
3.5 RIP Configuration Example ............................................................................... 3-13
3.6 RIP Fault Handling ........................................................................................... 3-16
3.6.1 Network Topology................................................................................... 3-16
3.6.2 Fault Analysis ........................................................................................ 3-16
3.6.3 Handling Flow ........................................................................................ 3-16
3.6.4 Handling Procedure................................................................................ 3-17
Chapter 4 OSPF Configuration.................................................................. 4-1

4.1 OSPF Overview ................................................................................................. 4-1
4.1.1 OSPF Basic ............................................................................................. 4-1
4.1.2 OSPF Algorithm ....................................................................................... 4-2
4.1.3 OSPF Network Types ............................................................................... 4-2
4.1.4 HELLO Packet and Timer ......................................................................... 4-2
4.1.5 OSPF Neighbors ...................................................................................... 4-3
4.1.6 Adjacency and DR.................................................................................... 4-3
4.1.7 Router Priority and DR Election................................................................. 4-4
4.1.8 OSPF Area .............................................................................................. 4-4
4.1.9 LSA Type and Flooding ............................................................................ 4-5
4.1.10 Stub Area and Totally Stubby Area .......................................................... 4-7
4.1.11 Not-So-Stubby Area................................................................................ 4-7
4.1.12 OSPF Authentication .............................................................................. 4-7
4.1.13 DownBit ................................................................................................. 4-8
4.1.14 Max-Metric............................................................................................. 4-8
4.2 Configuring OSPF .............................................................................................. 4-8
4.2.1 Enabling OSPF ........................................................................................ 4-8
4.2.2 Configuring OSPF Interface Attributes ......................................................4-11
4.2.3 Configuring OSPF Authentication ............................................................ 4-13
4.2.4 Configuring OSPF Stub Area .................................................................. 4-17
4.2.5 Configuring NSSA Area .......................................................................... 4-20
4.2.6 Configuring OSPF Inter-Area Route Aggregation...................................... 4-22
4.2.7 Configuring Route Aggregation Upon Route Redistribution ....................... 4-26
4.2.8 Configuring OSPF Route Redistribution ................................................... 4-28
4.2.9 Configuring OSPF Default Route............................................................. 4-31
4.2.10 Configuring OSPF Virtual Link ............................................................... 4-32
4.2.11 Configuring Sham-Link.......................................................................... 4-34
4.2.12 Configuring Max-Metric......................................................................... 4-35
4.2.13 Configuring OSPF Route Load Sharing.................................................. 4-36
II
4.2.14 Configuring OSPF FRR ........................................................................ 4-37
4.3 OSPF Maintenance .......................................................................................... 4-37
4.3.1 Common Maintenance Commands for Viewing Information....................... 4-37
4.3.2 Common Maintenance Commands for Debugging.................................... 4-44
4.4 OSPF Configuration Examples.......................................................................... 4-46
4.4.1 OSPF Configuration Example One .......................................................... 4-46
4.4.2 OSPF Configuration Example Two .......................................................... 4-48
4.4.3 OSPF Multi-Instance Configuration Example............................................ 4-50
4.4.4 OSPF Route Load Sharing Configuration Example................................... 4-53
4.5 OSPF Fault Handling........................................................................................ 4-54
4.5.1 OSPF Basic Function Fault Handling ....................................................... 4-54
4.5.2 OSPF Multi-Instance Fault Handling ........................................................ 4-57
4.5.3 OSPF Route Load Sharing Fault Handling ............................................... 4-59
Chapter 5 IS-IS Configuration ................................................................... 5-1

5.1 IS-IS Overview ................................................................................................... 5-1
5.1.1 IS-IS Area................................................................................................ 5-1
5.1.2 IS-IS Network Types................................................................................. 5-2
5.1.3 DIS and Router Priority ............................................................................. 5-3
5.1.4 IS-IS Dynamic Host Name Mapping........................................................... 5-3
5.1.5 IS-IS Mesh-Group .................................................................................... 5-3
5.2 IS-IS Working Principle ....................................................................................... 5-3
5.3 IS-IS Configuration ............................................................................................. 5-4
5.3.1 Enabling IS-IS.......................................................................................... 5-4
5.3.2 Configuring IS-IS Global Parameters ......................................................... 5-5
5.3.3 Configuring IS-IS Interface Parameters...................................................... 5-8
5.3.4 Configuring IS-IS Authentication...............................................................5-11
5.3.5 Configuring IS-IS Hostname.................................................................... 5-12
5.3.6 Configuring IS-IS Mesh-Group ................................................................ 5-13
5.3.7 Configuring IS-IS Redistribution .............................................................. 5-13
5.3.8 Configuring Traffic Engineering ............................................................... 5-14
5.3.9 Configuring IS-IS FRR ............................................................................ 5-14
5.3.10 Configuring IS-IS Route Load Sharing ................................................... 5-15
5.3.11 Configuring IS-IS FRR .......................................................................... 5-15
5.4 IS-IS Maintenance............................................................................................ 5-16
5.4.1 Common Maintenance Commands for Viewing Information....................... 5-16
5.4.2 Common Maintenance Commands for Debugging.................................... 5-21
5.5 IS-IS Configuration Examples ........................................................................... 5-23
III
5.5.1 Single Area IS-IS Configuration Example ................................................. 5-23
5.5.2 Multi-Area IS-IS Configuration Example ................................................... 5-26
5.5.3 IS-IS Multi-Instance Configuration Example ............................................. 5-33
5.5.4 IS-IS FRR Configuration Example ........................................................... 5-35
5.6 IS-IS Fault Handling ......................................................................................... 5-37
5.6.1 IS-IS Basic Function Fault Handling......................................................... 5-37
5.6.2 IS-IS Multi-Instance Fault Handling.......................................................... 5-40
5.6.3 IS-IS FRR Fault Handling........................................................................ 5-43
Chapter 6 BGP Configuration.................................................................... 6-1

6.1 BGP Overview ................................................................................................... 6-1
6.2 BGP Working Principle ....................................................................................... 6-2
6.3 Configuring BGP ................................................................................................ 6-4
6.3.1 BGP Neighborhood Establishment ............................................................ 6-4
6.3.2 Configuring BGP Route Advertisement .................................................... 6-16
6.3.3 Configuring BGP Route Load Sharing...................................................... 6-24
6.3.4 Configuring BGP FRR ............................................................................ 6-25
6.3.5 Configuring BGP Route Attribute and Route Filtering ................................ 6-25
6.3.6 BGP Configuration for Large-scale Network ............................................. 6-46
6.3.7 BGP Maintenance .................................................................................. 6-54
6.4 BGP Configuration Examples............................................................................ 6-60
6.4.1 BGP FRR Configuration Example............................................................ 6-60
6.4.2 BGP Configuration Example One ............................................................ 6-62
6.4.3 BGP Configuration Example Two ............................................................ 6-71
6.5 BGP Fault Handling.......................................................................................... 6-74
6.5.1 BGP Basic Function Fault Handling ......................................................... 6-74
6.5.2 BGP FRR Fault Handling ........................................................................ 6-78
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
IV
About This Manual
Purpose
At first, thank you for choosing ZXR10 routers of ZTE Corporation!
This manual describes the principle, configuration commands, maintenance commands,
configuration examples and fault handling about IPv4 routing function of ZXR10 M6000.
Intended Audience
This manual is intended for the following engineers:
l Network planning engineer
l Commissioning engineer
l On-duty personnel
What Is in This Manual

This manual contains the following contents:
Chapter Summary
Chapter 1 Safety Instruction Introduces safety instruction and symbol description for device
installation, operation and maintenance.
Chapter 2 Static Route Describes the Static Route principle, configuration commands,
Configuration maintenance commands, configuration examples and fault
handling.
Chapter 3 RIP Configuration Describes the RIP principle, configuration commands,

maintenance commands, configuration examples and fault
handling.
Chapter 4 OSPF Configuration Describes the OSPF principle, configuration commands,

handling.
Chapter 5 IS-IS Configuration Describes the IS-IS principle, configuration commands,

handling.
Chapter 6 BGP Configuration Describes the BGP principle, configuration commands,

handling.
Conventions
ZTE documents employ the following typographical conventions.
I
Typeface Meaning
Italics Variables in commands. It may also refers to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters and commands.
CAPS Keys on the keyboard and buttons on screens and company name.
Constant Text that you type, program codes, filenames, directory names, function names.
width
[] Optional parameters.
{} Mandatory parameters.
| Separates individual parameter in series of parameters.
Danger: Indicates an imminently hazardous situation, which if not avoided, will result in
death or serious injury.
Warning: Indicates a hazard that, if not avoided, could result in serious injuries,
equipment damages or interruptions of major services.
Caution: Indicates a potential hazard that, if not avoided, could result in moderate
injuries, equipment damages or partial service interruption.
Note: Provides additional information about a certain topic.
Checkpoint: Indicates that a particular step needs to be checked before proceeding

further.
Tip: Indicates a suggestion or hint to make things easier or more productive for the
reader.
II
Chapter 1
Safety Instruction
Table of Contents
Safety Instruction .......................................................................................................1-1
Safety Signs ...............................................................................................................1-1
1.1 Safety Instruction

Only duly trained and qualified personnel can install, operate and maintain the devices.
During the device installation, operation and maintenance, please abide by the local
safety specifications and related operation instructions, otherwise physical injury may
occur or devices may be broken. The safety precautions mentioned in this manual are
only supplement of local safety specifications.
The debug commands on the devices will affect the performance of the devices, which
may bring serious consequences. So take care to use debug commands. Especially, the
debug all command will open all debug processes, so this command must not be used on
the devices with services. It is not recommended to use the debug commands when the
user networks are in normal state.
ZTE Corporation will assume no responsibility for consequences resulting from violation
of general specifications for safety operations or of safety rules for design, production and
use of the devices.
1.2 Safety Signs

The information that users should pay attention to when they install, operate and maintain
devices are explained in the following formats:
Warning!
Indicates the matters needing close attention. If this is ignored, serious injury accidents
may happen or devices may be damaged.
Caution!
Indicates the matters needing attention during configuration.
1-1
SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

ZXR10 M6000 Configuration Guide (IPv4 Routing)
Note:
Indicates the description, hint, tip, and so on for configuration operations.
1-2

Chapter 2
Static Route Configuration
Table of Contents
Static Route Overview ................................................................................................2-1
Static Route Principle .................................................................................................2-1
Configuring Static Routes...........................................................................................2-2
Static Route Maintenance ..........................................................................................2-5
Static Route Configuration Examples .........................................................................2-6
Static Route Fault Handling ......................................................................................2-11
2.1 Static Route Overview

Static route is the routing information that is designated by network administrator to the
routing table by means of commands. Unlike a dynamic route, it does not set up routing
table according to routing algorithm. In dynamic route configuration, routing information
of the entire Internet must be sent to a router. The router is hard to hold the load. In this
time, static routes can be used to solve the problem. Sometimes, use static route with
less configuration to avoid using dynamic route. However, in a routing environment where
there are multiple routers and paths, it is very complicated to configure static routes.
2.2 Static Route Principle

To generate a static unicast routing table, network administrator has to be familiar with the
network topology and configure it according to the actual routing requirements. In this way,
the routing action can be controlled accurately in network. The static routing table needs
to be reconfigured in time if the network topology is changed.
Static route is different from other dynamic routing protocol. Static route configuration
does not require that configure the related protocol data on interfaces. It only needs to
check the validity of static route parameters configured by users, but whether static route
configuration takes effect is still decided by the state changing of the corresponding egress
interface.
The following content is a routing table of ZXR10 M6000. Here, the administrator distance
of static route is 1.
ZXR10#show ip protocol routing

Protocol routes:
status codes:*valid, >best, i-internal, s-stale
Dest NextHop RoutePrf RouteMetric Protocol
*> 0.0.0.0/0 0.0.0.0 254 8 special
2-1

*> 2.2.2.2/32 2.2.2.2 0 0 connected

*> 120.2.2.0/24 120.2.2.2 1 0 static
*> 120.2.2.2/32 120.2.2.2 0 0 connected
*> 255.255.255.255/32 0.0.0.0 254 0 special
2.3 Configuring Static Routes

In fact, each route should be specified with a next hop address. When a router sends a
packet, it searches for a route that matches the destination address of the packet from the
routing table. Only when the next hop address is specified can the link layer find out the
corresponding link layer address and forward the packet.
2.3.1 Configuring Next Hop of a Direct Route

To configure a next hop of a direct route on ZXR10 M6000, use the following command.
Command Function
ZXR10(config)#ip route [ vrf < vrf-name> ] < prefix> < net-mask> { < This configure a next hop of an IPv4
nexthop-address > [ global] } [ < distance-metric> ] [ metric < metric> ] [ static route. The < nexthop-address >
bfd enable ] parameter can be a direct-connected
address or an indirect-connected
address.
Parameter descriptions:
Parameter Description
vrf < vrf-name> It is used to configure static route of the designated Virtual Route
Forwarding Table (VRF). The VRF name is with 1–32 characters. The
mng port is used as a special VRF.
< prefix> Network Internet Protocol (IP) prefix, in dotted decimal notation
< net-mask> Network Mask, in dotted decimal notation
< nexthop-address > IP address of the next hop, in dotted decimal notation
global Indicating that public network next hop can be configured for a private
network. This is allowed only when it is to configure a next hop of
a private network route.
metric < metric> Route metric, in the range of 1–255
bfd enable Enable static BFD
2.3.1.1 Specifying a Direct Next Hop

Configure the next hop of a static route to a direct-connected network.
2-2

Chapter 2 Static Route Configuration
2.3.1.2 Specifying an Indirect Next Hop

To configure the next hop of a static route to an indirect-connected network, it is necessary
to do iterative resolution for once or more times for the next hop address configured to
obtain the corresponding direct-connected next hop. After the iterative resolution, the next
hop of the static route in the routing table is the direct-connected next hop.
2.3.2 Configuring an Out-Interface of a Static Route

To configure an out-interface of a static route on ZXR10 M6000, use the following
command.
Command Function
ZXR10(config)#ip route [ vrf < vrf-name> ] < prefix> < net-mask> { < This configure an out-interface of
interface-name> | < interface-name> < nexthop-address > } [ < distance-metric> an IPv4 static route. When the
] [ metric < metric> ] [ bfd enable ] out-interface is an Ethernet interface, it
is necessary to configure the next hop
address at the same time.
< interface-name> Interface name
For a point-to-point interface, it is only necessary to specify the out-interface for the static
route, because specifying an out-interface also specifies the next hop implicitly. It is
considered that the address on the peer interface connected to the local interface directly
is the next hop address of the route.
For an Ethernet interface, it is not allowed to specify an Ethernet interface as an
out-interface. In applications, when it is necessary to specify an Ethernet interface as an
out-interface, it is necessary to specify the out-interface first and then specify the next
hop address.
A static route with an out-interface as a null interface can be applied as a black route.
Traffic matches this route will be dropped directly.
Example
Figure 2-1 Indirect Static Route Next Hop Configuration Example
As show in Figure 2-1, configure a static route to 30.2.0.0/16 on R1, and the next hop is
20.20.20.2 (an interface on R3). The next hop is not a direct-connected network of R1. To
make the static route effective, there should be a route to 20.20.20.0/24 with the next hop
2-3

10.10.10.2 (direct-connected next hop of R1) in the routing table. This is once next hop
iterative resolution.
Static route configuration on R1:
R1(config)#ip route 30.2.0.0 255.255.0.0 20.20.20.2
The direct-connected interfaces on R1, R2 and R3 run Intermediate

System-to-Intermediate System (IS-IS) protocol.
IS-IS configuration on R1:
R1(config)#router isis
R1(config-isis)#area 01
R1(config-isis)#is-type level-2
R1(config-isis)#system-id 00D0.D0C7.5460
R1(config-isis)#interface fei-0/1/0/1
R1(config-isis-if)#ip router isis

R2(config-isis)#system-id 00D0.D0C7.53E0
R2(config-isis-if)#exit
View the forwarding table on R1, as shown below.
R1#show ip forwarding route

IPv4 Routing Table:
Dest Gw Interface Owner Pri Metric
10.10.10.0/24 10.10.10.1 fei-0/1/0/2 direct 0 0
10.10.10.1/32 10.10.10.1 fei-0/1/0/2 address 0 0
20.20.20.0/24 10.10.10.2 fei-0/1/0/2 isis_l2 115 20
30.2.0.1/32 10.10.10.2 fei-0/1/0/2 static 1 0
In this example, IS-IS is used to generate a route to 20.20.20.0/24 with the next hop
10.10.10.2 (direct-connected next hop of R1) in the routing table of R1. After once next
2-4

hop iterative resolution, the next hop address to the destination 30.2.0.0/16 in the routing
table is 10.10.10.2 (direct-connected next hop of R1).
2.4 Static Route Maintenance

ZXR10 M6000 provides the following commands to maintain static routes.
Command Function
ZXR10#show ip protocol routing [ vrf < vrf_name> ] This shows routing table of the router.
Vrf_name is the name of vrf.
ZXR10#show ipforwarding route [ vrf < vrf_name> ] This shows forwarding table of the
router. Vrf_name is the name of vrf.
Use the show ip protocol routing command to show global routing table of the router.
Inspect whether the configured static route exists in routing table. This command is often
used for routing protocol diagnose and maintenance.
Use the show ip forwarding route command to show forwarding table of router for
inspecting whether there is static route in forwarding table.
An example of the show ip protocol routing command output is shown below.
ZXR10(config)#show ip protocol routing
Protocol routes:
status codes: *valid, >best, i-internal, s-stale

*> 10.10.10.0/24 10.10.10.1 0 0 connected
* 10.10.10.0/24 10.10.10.0 110 1 ospf
*> 10.10.10.1/32 10.10.10.1 0 0 connected
*> 20.20.20.0/24 10.10.10.2 110 2 ospf
*> 30.2.0.0/16 10.10.10.2 1 0 static
Descriptions of the command output:
Command Output Description
Dest Destination IP address
NextHop IP address of next hop
RouteRrf Management distance metric
RouteMetric Route metric
Protocol Name of the corresponding routing protocol
An example of the show ip forwarding route command output is shown below.

ZXR10(config)#show ip forwarding route
IPv4 Routing Table:
2-5


10.10.10.0/24 10.10.10.1 fei-0/1/0/1 direct 0 0
10.10.10.1/32 10.10.10.1 fei-0/1/0/1 address 0 0
20.20.20.0/24 10.10.10.2 fei-0/1/0/1 ospf 110 2
30.2.0.0/16 10.10.10.2 fei-0/1/0/1 static 1 0
224.0.0.0/4 224.0.0.0 NULL multicast 0 0
224.0.0.0/24 224.0.0.0 NULL multicast 0 0
255.255.255.255/32 255.255.255.255 NULL broadcast 254 0
Dest Destination IP address
Gw Gateway
Interface Outgoing interface
Owner Route type
Pri Route priority
Metric Route metric
2.5 Static Route Configuration Examples

2.5.1 Static Route Configuration Example
As shown in Figure 2-2, if R1 wants to send packets to the remote network 140.1.1.0/24,
it needs to send the packets to R2 (10.6.1.18) first. R1 and R2 are directly connected. In
this time, R2 needs to have two static routes, as shown below.
Destination Address the Next Hop
Static route 1 10.9.1.0 10.6.1.18
Static route 2 140.1.1.0 10.6.1.18
Figure 2-2 Static Route Configuration Example
There are three methods to configure static routes on R1.
2-6

l This configures IP address of the next hop.

R1(config)#ip route 140.1.1.0 255.255.255.0 10.6.1.18
R1(config)#ip route 10.9.1.0 255.255.255.0 10.6.1.18
l This configures the next hop as egress interface.
R1(config)#ip route 140.1.1.0 255.255.255.0 pos192-0/1/0/1
R1(config)#ip route 10.9.1.0 255.255.255.0 pos192-0/1/0/1
Method 2 is similar to method 1. The only difference is that the method 1 uses IP
address as the next hop but method 2 uses local egress interface as the next hop.
That is to say, all the packets transmitted to destination network segment 140.1.1.0/24
and 10.9.1.0/24 are sent by the interface pos192-0/1/0/1 on R1 but not routed to logical
address of the next hop. Method 2 is not suitable for Ethernet interface, and it is only
suitable for POS interface.
l This configures the local egress interface and the direct next hop.
R1(config)#ip route 140.1.1.0 255.255.255.0 fei-0/1/0/2 10.6.1.18
R1(config)#ip route 10.9.1.0 255.255.255.0 fei-0/1/0/2 10.6.1.18
Method 3 is different from method 2. If egress interface and the next hop are
configured to specify egress interface, this mode is suitable for Ethernet interface.
If the next hop is configured and the next hop is direct, the configuration effect
is same to that of egress interface and next hop. But if the indirect next hop is
configured, the next hop will make recursion resolution. The two designs are to meet
the requirements of direct and indirect.
Configuration on R2:
R2(config)#ip route 140.1.1.0 255.255.255.0 10.9.1.39
Use the show command to validate configuration.

Check configuration on R1, as shown below.
R1(config)#show ip protocol routing network 140.1.1.0
Protocol routes:

*> 140.1.1.0/24 10.6.1.18 1 0 static
R1 (config)#show ip pro r network 10.9.1.0

Protocol routes:

*> 10.9.1.0/24 10.6.1.18 1 0 static
Check configuration on R2, as shown below.
2-7


Protocol routes:

*> 140.1.1.0/24 10.9.1.39 1 0 static
If there are multiple paths to the same destination, a router can be configured with multiple
static routes with different administrative distances. However, routing table only displays
information about route with minimum distance because when router is informed of multiple
competition sources to a network, route with minimum administrative distance takes the
precedence.
The < distance-metric> parameter in static route configuration command about IP route can
be used to change administrative distance value of a static route. Supposing there are two
different routes from R1 to network section 140.1.1.0/24, the configuration is as follows:
R1(config)#ip route 140.1.1.0 255.255.255.0 10.6.1.18

R1(config)# ip route 140.1.1.0 255.255.255.0 10.6.1.1 20
Above commands are used to configure two different static routes arriving to the same
network segment. The first command does not configure administrative distance, so
default value “1” is used. The second command configures administrative distance of 20.
Since administrative distance of the first route is less than that of the second route, only
information about first route appears in routing table. That is, the router sends packets to
destination network segment 140.1.1.0/24 through next-hop address 10.6.1.18 only. The
second route appears in routing table only when the first route fails and disappears from
the routing table. The two static routes cannot have the same tag value, which go to the
same destination network but their next-hop is different.
Use the show command to view the routes on R1, as shown below.
Protocol routes:

*> 140.1.1.0/24 10.6.1.18 1 0 static
* 140.1.1.0/24 10.6.1.1 20 0 static
2.5.2 Static Route Summary Configuration Example

A summary static route is a special kind of static routes, which can summarize two or
more special route expressions into one expression. In this way, entries of routing table is
reduced but all of original links is reserved.
As shown in Figure 2-3, R2 connects to two network segments 10.9.1. 0/24 and
10.3.1.0/24. If R1 wants to access these two network segments, it needs to have two
static routes.
2-8

Figure 2-3 Static Route Summary Configuration Example
R1(config)# ip route 10.9.1.0 255.255.255.0 10.6.1.18

R1(config)# ip route 10.3.1.0 255.255.255.0 10.6.1.18
Use the show command to view the routes on R1, as shown below.
R1(config)#show ip protocol routing
Protocol routes:

*> 10.9.1.0/24 10.6.1.18 1 0 static
*> 10.3.1.0/24 10.6.1.18 1 0 static
There are lots of routes in routing table, people can use summary static route to optimize
the routing table of R1. The following command can be used to replace the two commands
above.
R1(config)# ip route 10.0.0.0 255.0.0.0.0 10.6.1.18
By using this command, all the packets transmitted to destination network segment
10.0.0.0/16 pass through 10.6.1.18. That is to say, all the packets which destination
address is 10.0.0.0/8 (sub networks 10.3.1.0/24 and 10.9.1.0/24) are sent to 10.6.1.18. In
this way, multiple static routes with the same destination can be summarized to a static
route, which can optimize routing table.
2.5.3 Default Route Configuration Example

Default route is also a kind of special static routes. When all routes are failed in routing
table, default route is used to make packet has a final destination. In this way, the
processing burden of router can be reduced a lot.
When a router cannot route a packet, the packet has to be dropped. However, this is not
hoped that packet is dropped in an "unknown" destination. To support complete connection
of router, this must have a route connected to a network. If router wants to keep complete
connection and meanwhile does not need to record each independent route, default route
can be used. By use of default route, an independent route can be designated to indicate
all other routes.
2-9

As shown in Figure 2-4, since there is no route pointing to Internet on R1, R1 needs to use
default route that send packets to R2 for processing.
Figure 2-4 Default Route Configuration Example
Default route configuration is completely the same as static route configuration and only
difference is that the network part and subnet mask part are all 0.0.0.0.
R1(config)# ip route 0.0.0.0 0.0.0.0 10.6.1.18
Use the show to view the routing table on R1.

R1#show ip protocol routing
Protocol routes:

*> 0.0.0.0/0 10.6.1.18 1 0 static
Here, if the next hop is configured as null interface, the route is black hole route.
R1(config)# ip route 0.0.0.0 0.0.0.0 null1
View R1 routing table by using the show command, as shown below.
R1#show ip protocol routing

Protocol routes:

*>0.0.0.0/0 0.0.0.0 1 0 static
Default route is not always a static route. It also can be routes of other protocols, such
as Border Gateway Protocol (BGP), Routing Information Protocol (RIP) and so on. When
default route is used in routing protocol configuration, default route varies with routing
protocols.
If default route is configured on a router where RIP runs, the RIP will advertise the default
route to its neighbor, and even route redistribution is not needed in RIP domain.
2-10

For BGP protocol, a router where the BGP runs will not inject the default route into its
neighbor automatically. For BGP to send the default route to BGP domain, the command
default-information-originate has to be used first, and then redistribute default route.
2.6 Static Route Fault Handling

2.6.1 Network Topology
As shown in Figure 2-5, R1 wants to access the network 10.9.1.0/24 connecting to R3.
Figure 2-5 Network Topology of a Static Route Fault
2.6.2 Fault Analysis

R1(config)# ip route 10.9.1.0 255.255.255.0 10.6.1.18
Use the show on R1 to view protocol table and the result shows that the route is not
generated on R1. People fails to ping the destination address 10.9.1.39 on R1.
If the static route pointing to destination address is already configured on R1, but the
static route is not generated successfully and the destination address cannot be pinged
successfully, that because the physical link is failed.
2.6.3 Handling Flow

The flow to handle a static route fault is shown in Figure 2-6.
2-11

Figure 2-6 Flow to Handle a Static Route Fault
2.6.4 Handling Procedure

The procedure to handle a static route fault is described below.
1. Use the show ip protocol routing command to inspect whether the configured static
route is generated on router. Inspect the IP address and the state of physical link if the
static route is failed to generate. Check if the configured static route is correct such
as if the destination network segment, subnet mask and next hop configuration are
correct.
2. If configuration is correct, inspect IP address configuration and the networking physical
connection state.
3. Use the show ip interface brief command or the show ip interface command on the
interfaces to inspect whether the connected physical interfaces are in up state.
4. If interface is down, check if physical connection of network is correct.
2-12

5. Use the ping command to inspect whether the destination network segment can be
pinged successfully.
If the fault cannot be solved according to the steps above, please ask for technical support.
2-13

This page intentionally left blank.
2-14

Chapter 3
RIP Configuration
Table of Contents
RIP Overview .............................................................................................................3-1
RIP Working Principle.................................................................................................3-2
RIP Configuration .......................................................................................................3-3
RIP Maintenance........................................................................................................3-9
RIP Configuration Example ......................................................................................3-13
RIP Fault Handling ...................................................................................................3-16
3.1 RIP Overview

RIP is relatively old but still commonly used interior gateway protocol created for use in
small and homogeneous networks. This is a classical distance-vector routing protocol.
RIPv1 is documented in Request For Comments (RFC) 1058. RIPv2 is documented in
RFC1723. ZXR10 M6000 supports RIPv1 and RIPv2 completely. RIPv2 is used by default.
Compared to RIPv1, RIPv2 has the following advantages.
l Route updating with sub network mask
l Authentication for route updating
l Updating multicast routing
The following topics mainly introduce RIPv2. RIP refers RIPv2 unless special explain.
3.1.1 RIP Route Metric and Administrative Distance

RIP uses User Datagram Protocol (UDP) packet (port number 520) to exchange RIP
routing information. The routing information containing in RIP packet includes the number
of routers that a route passes through, that is, hop count, according to which, router
determines the route to the destination network.
RFC stipulates that the maximum hop count must be less than 16, so RIP is only
applicable to small-sized network. Hop count of 16 indicates infinite distance, representing
unreachable route, which is one way for RIP to identify and prevent the routing loop.
Only hop count is taken as the metric for RIP routing; bandwidth, delay and other variable
factors are not considered. RIP always takes paths with the least hop count as the
optimized path, which results that the selected path is not the best one.
Default Administrative Distance (AD) value of RIP is 120. As for AD, the lower the value,
the higher the reliability of routing source. Compared to other routing protocols, RIP is not
quite reliable.
3-1

3.1.2 RIP Timers

RIP provides the following four types of timers:
l Update timer
l Invalid timer
l Holddown timer
l Flush Timer
Update timer: Router running RIP transmits route update message at a certain interval
(30s by default), which reflects all the routing information of the router. This process is
called routing information advertisement.
Invalid timer: When a router fails to receive update information from another router in
a certain time period (180s by default), it marks the routes provided by the router to be
“unavailable”.
Hold-down timer: After learning that routes are unavailable, the router will enter hold-down
state. If router receives route update packet within the default 180 seconds or if router fails
to receive route update packet after 180 seconds, the holddown timer will stop timing.
Flush timer: When it is not updated in the succeeding period of time (240s by default), the
router clears the route completely from the routing table.
3.1.3 RIP Route Update

RIP protocol employs trigger update to speed up the spread of routing changes in the RIP
routing domain. When a RIP router detects that an interface is working or has stopped
working, a neighbor node is down or a new subnet or neighbor node joins in, it will transmit
a trigger update. The trigger update packet only contains changed route.
RIP protocol uses poison reverse to speed up protocol convergence. The poison reverse
sets the metrics of the unreachable network prefixes to be 16 (meaning unreachable).
After receiving route update packet of the metric, the router will discard the route instead
of waiting for the aging time.
RIP uses split horizon to prevent loop and reduce the size of route update packet. Split
horizon means that if an interface receives a route update packet, it will not transmit this
update packet from itself to others.
3.2 RIP Working Principle

RIP defines two kinds of message types, request and response messages. Request
message is used to send a update to neighbor router, and response message is used to
transmit route update.
At the start, RIP broadcasts or multicasts packets which contain request message from
every RIP interface. Later, RIP enters a loop state, it always monitors the RIP request or
response messages from other routers, and the neighbor routers which accept the request
will reply response messages containing their routing tables.
3-2

Chapter 3 RIP Configuration
When the router which sends request receives the response message, it will process the
route update message information containing in response message.
l For an new route entry, the router adds the new route and IP address of the advertised
router to its routing table.
l For an existent RIP route, the router replaces the original route entry only when the
new route has less hop count.
3.3 RIP Configuration

RIP configuration includes the following contents, basic configuration, enhanced
configuration and version configuration.
3.3.1 Configuring RIP Basic Functions

To configure RIP basic function on ZXR10 M6000, perform the following steps.
1. Enabling RIP
Step Command Function
1 ZXR10(config)#router rip This enables RIP routing process

and enters RIP configuration mode.
2 ZXR10(config-rip)#network < ip-address> < wildcard-mask> This runs RIP on a specified network
segment.
2. Adjusting RIP timer
1 ZXR10(config)#router rip This enables RIP process and enters

RIP configuration mode.
2 ZXR10(config-rip)#timers basic < update> < invalid> < holddown> This adjusts RIP network timer.
< flush>
3 ZXR10(config-rip)#output-delay < packets> < delay> This sets the delay time for sending
RIP update packets.
Descriptions of the parameters in Step 2:
< update> The interval for sending update, the unit is second, the range is
1-65535, and the default value is 30 seconds.
3-3

< invalid> Period before route invalidity in seconds, 1-65535. This value shall be
at least 3 times of update, 180 seconds by default.
When there is no route refreshing, the route is ineffective. Here,
the route is blocked, marked as inaccessible, and advertised as
unreachable, but the route can still be used to forward message
packets.
< holddown> Period for suppressing optimized route in seconds, 0-65535. This
value shall be at least 3 times of update, 180 seconds by default.
When the router receives the update message and obtains a
unreachable route, it will enter the blocked state, be marked as
inaccessible, and be advertised as unreachable, but the route can
still be used to forward packets. After passing the blocked period, it
receives the routes advertised by other routers, and the route will
be accessible again.
< flush> Period from route invalidity to route clearing in seconds, 1-65535,
240 seconds by default.
The designated time must be greater than the holddown value.
Otherwise, it cannot pass the proper block time. In this way, the new
routes will be received before the block expires.
< packets> The number of packets, ranging from 1 to 4294967295, and the
default value is 5.
< delay> The time interval for sending the packets in a designated number.
The unit is second, the range is 0-100, and the default value is 100ms.
Example
This configures optional RIP parameters related to time.
ZXR10(config)#router rip
ZXR10(config-rip)#timers basic 5 15 15 30
ZXR10(config-rip)#output-delay 500 10
The following configurations take effect.
l The interval for sending RIP update is 5 seconds.

l The Period before route becomes invalid is 5 seconds.
l Router has 15 seconds for waiting after enters blocked state.
l There are 30 seconds for waiting from the route entry becoming invalid to clearing the
route entry.
l There are 10ms interval for sending each 500 packets.
3-4

3.3.2 Configuring RIP Enhanced Functions

To configure RIP enhanced function on ZXR10 M6000, perform the following steps.
1. Configuring RIP neighbor
1 ZXR10(config)#router rip This enters RIP configuration mode.
2 ZXR10(config-rip)#neighbor < ip-address> This command applies to

non-broadcast link.
This defines neighbor router to
exchange routing information with
the router.
There are 255 neighbors can be
found and configured.
By using this command, RIP routing information can be exchanged by point-to-point

method (non-broadcast). Once the neighbor is designated, the interfaces which
belong to the same network with the router will not use broadcasting (or multicast) to
exchange RIP routing information.
2. Configuring RIP authentication
RIPv2 supports plain text and Message Digest 5 Algorithm (MD5) authentication
modes. Password is configured on interfaces. Network neighbors have to use the
same authentication mode and password. RIPv1 does not support authentication.
To configure RIP packet plain text authentication mode, perform the following steps.
1 ZXR10(config)#interface < interface-name> This enters interface configuration

mode.
2 ZXR10(config-if)#ip rip authentication mode text This specifies the interface to

authenticate RIP packets by plain
text mode.
3 ZXR10(config-if)#ip rip authentication key < key> This sets the key for interface plain
text authentication. The length of
key is 1-16 characters.
To configure RIP packet MD5 authentication mode, perform the following steps.

mode.
3-5

2 ZXR10(config-if)#ip rip authentication mode md5 This specifies the interface to

authenticate RIP packets with MD5
mode.
3 ZXR10(config-if)#ip rip authentication key-chain < key-id> < This sets to provide key-chain in
key-string> interface MD5 authentication.
< key-id> ID of the key node in key-chain, the range is 1-255.
< key-string> Value of the key, the range is 1-16 characters.
3. Configuring split horizon and poison reverse mechanisms

mode.
2 ZXR10(config-if)#ip split-horizon This enables split horizon

mechanism.
By default, it is enabled. Use no to
disable split horizon mechanism.
3 ZXR10(config-if)#ip poison-reverse This enables poison-reverse

mechanism.
By default, it is enabled. Use no to
disable poison-reverse mechanism.
It is suggested that users do not change the default state of split horizon unless to
ensure to advertise route correctly. If the split horizon is disabled on serial port (and
the port connects to packet switching network), then those of all the related routers
and access servers have to be disabled.
4. Configuring route redistribution
To redistribute routes from a routing domain to RIP routing domain, perform the
following steps.
2 ZXR10(config-rip)#redistribute < protocol> [ process-id] [ metric < This redistributes routes of other
metric-value> ] [ route-map < name> ] routing protocols to RIP.
3-6

< protocol> Source routing protocol of route redistribution, which can be the
following keyword: ospf-ext, ospf-int, static, bgp-ext, bgp-int,
connected, isis-1, isis-2, and isis-1-2
< protocol> The source protocol redistributed. It can be ospf-ext, ospf-int, static,
bgp-ext, bgp-int, connected, isis-1, isis-2 or isis-1-2.
metric < metric-value> Specifies the route metric to introduce the route. If it is not specified,
the default-metric is used. Its range is 0-16.
route-map < map-tag> The name of the route map for redistribution, 1-31 characters.
3.3.3 Configuring RIP Version

ZXR10 M6000 supports RIPv1 and RIPv2, and it uses RIPv2 by default.
To specify RIP version for router receiving or sending packets on ZXR10 M6000, use the
following steps.
2 ZXR10(config-rip)#version { 1| 2} This configures RIPv1 or RIPv2.

The default setting is RIPv2.
To specify the RIP version of packets to be sent or received by an interface, perform the
following steps.
RIP default state specified by using the version command can be ignored.

mode.
2 ZXR10(config-if)#ip rip receive version { 1 | 2} This specifies RIP version (RIPv1 or

RIPv2) of the packets to be received
by an interface.
Use default setting if version is not
used, that is, both of RIPv1 and
RIPv2 packets are received
3 ZXR10(config-if)#ip rip send version { 1 | 2 { broadcast | multicast} } This specifies RIP version (RIPv1 or
RIPv2) of the packets to be sent by
an interface.
3-7

1 The interface only sends RIPv1 packets
2 The interface only sends RIPv2 packets. Here, broadcast or multicast mode can be selected.
broadcast The interface send compatible packets to broadcast address. All of routes are natural networks,
and no supernetting route.
multicast The interface sends RIPv2 packets to multicast address. By using the auto-summary command,
sub network route can be sent.
3.3.4 Configuring RIP Route Load Sharing

To configure RIP route load sharing on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router rip This enters RIP route configuration

mode.
2 ZXR10(config-rip)#maximum-paths < number> This configures the count of routes

that support load sharing. It is in the
range of 1-16. The default value is 1.

mode.
ZXR10(config-if)#ip load-sharing { per-destination | per-packet} This configures load sharing mode

on an interface. Load sharing should
be configured on interfaces. By
default, the mode is per-destination.
Only when the load sharing mode on
all interfaces is per-packet, the load
sharing mode is per-packet indeed.
4 ZXR10(config-if)#load-sharing bandwidth < bandwidth-value> This configures the weight of load

sharing on an interface. The weight
is configured on the egress interface.
The weight is valid when the priority
is configured. The interfaces with
different weights have different
value.
3-8

3.4 RIP Maintenance

3.4.1 Common Maintenance Commands for Viewing Information
ZXR10 M6000 provides the following commands to view RIP information.
Command Function
ZXR10(config)#show ip rip [ vrf < vrf-name> ] This shows the basic information of RIP
running.
ZXR10(config)#show ip rip interface [ vrf < vrf-name> ] < interface-name> This shows the current configuration
and state of a RIP interface.
ZXR10(config)#show ip rip database [ vrf < vrf-name> ] [ network < This shows the route entries generated
ip-address> [ mask < net-mask> ] ] by RIP.
ZXR10(config)#show ip rip networks [ vrf < vrf-name> ] This shows information of all RIP
interfaces.
vrf < vrf-name> VRF name, the length is 1-32 characters.
network < ip-address> Network IP address, in dotted decimal notation.
mask < net-mask> Network mask, in dotted decimal notation
< interface-name> Name of RIP interface
An example of the show ip rip command output is shown below.

ZXR10#show ip rip
router rip
auto-summary
default-metric 1
distance 120
validate-update-source
version 2
flash-update-threshold 5
maximum-paths 1
output-delay 5 100
timers basic 30 180 180 240
network
10.0.0.0 0.255.255.255
3-9

auto-summary This shows that only the summarized routes of natural network and
suppernetting can be sent (for RIPv2).
Use no to sent all RIP routes.
Be noted that the following policy is still available even if auto-summary
is used. When a router has the RIP sub network route of the natural
network to which the IP address of a RIP interface belongs, the RIP
update packet sent by the RIP interface to outside does not contain
the route of natural network to which its IP address belongs, but it
contains the routes of other RIP sub networks which do not belong to
the same natural network segment with RIP the interface.
default-metric This sets the default metric value for redistributing the routes
generated by other protocol to RIP routes.
Use no to restore the default value of 1.
This command can be used with redistribute command together
to make route selection protocol use the same metric value for all
redistributed routes.
Default metric helps to solve the route redistribution problem caused
by routes using different metric values. It can provide a reasonable
alternative method to ensure that the redistribution can be performed
successfully.
distance This defines RIP route administrative distance.

This changes the decision of global routing table to select optimized
route.
validate-update-source This enables the function that check the validity of source IP address
of the received RIP updating packet.
Use no to disable this function.
flash-update-threshold This defines RIP flash timer.

Protocol flash timer can be set according to the actual requirements.
maximum-paths This sets the number of routes supported by load balancing.

The number of routes received by RIP protocol can be changed
according to the actual load balancing requirements.
An example of the show ip rip database command output is shown below.

ZXR10(config)#show ip rip database
Routes of rip:
h : is possibly down,in holddown time
f : out holddown time before flush
Dest Metric RtPrf InstanceID Time From
3-10

*> 137.1.0.0/16 1 254 0 00:00:12 0.0.0.0

*> 137.1.1.0/24 0 0 0 00:00:00 0.0.0.0
Metric It shows the weights of the route.

Metric value is 16 that indicates the route is invalid.
RtPrf Route priority

It shows the credibility of the route.
The priority of a summary route is 254, and 255 means a invalid route.
InstanceID Instance number, only valid for Open Shortest Path First (OSPF)
instance and IS-IS instance
Time It shows the existing time and timer state of the route.
From It indicates where the route is learnt.

From 0.0.0.0 indicates that the route is generated by the local router.
An example of the show ip rip interface command output is shown below.

ZXR10(config-rip)#show ip rip interface fei-0/1/0/3
ip address:137.1.1.2/24 rip is enabled
receive version 1 2
send version 2
split horizon is effective
poison reverse is effective
send subnet only is ineffective
notify default unset
originate default unset
neighbor restrict is ineffective
interface is nomoral
authentication type:none
send subnet only This shows that after this command is used, the interface only sends
the information of the route which belongs to the same sub network
with itself, and it blocks the information of the route which belongs to
other sub network.
It applies to such a case that the lower router sends route information
to upper router. Only the information of local sub network needs to be
advertised. In this way, the route traffic can be reduced a lot.
notify default The route entry sent by interface contains default route.
For parameter only, that means the route entry sent by interface only
contains default route.
3-11

originate default A default route is generated on interface, and it is forced to advertise.

For parameter only, that means the interface only sends default route.
A default route is generated on interface, and it is forced to advertise,
but the default route is not added into the routing table of local router
but it is added into the routing table of neighbor router.
neighbor restrict Interface neighbor restrict mode

When interface neighbor restrict mode is entered but neighbor is
not configured on the interface, the neighbor still can be found but
no point-to-point packets are sent to neighbor, and only multicast
packets are sent. In this time, the neighbor can receive the packets.
After a neighbor is configured on the interface, the neighbor which
is found before will be deleted, and no neighbor can be found. At
the same time, the interface only sends point-to-point packets to the
configured neighbor. Meanwhile, the interface can receive packets
from the configured neighbor only, the packets from other sources
are discarded.
To realize the effect described above, neighbor restrict mode has to be
configured on both of routers, and the routers need to enable neighbor.
An example of the show ip rip neighbors command output is shown below.

ZXR10#show ip rip neighbors
neighbor address interface
10.1.1.15 fei-0/1/0/3
neighbor address IP address identifier of RIP neighbor
interface Learn an interface from the neighbor
3.4.2 Command Maintenance Commands for Debugging

ZXR10 M6000 provides the following commands to debug RIP.
Command Function
ZXR10#debug ip rip This traces the process of RIP packets

receiving and sending.
ZXR10#debug all rip This enables all RIP debug functions.
ZXR10#debug ip rip events This traces the events related to RIP.
ZXR10#debug ip rip database This traces the changing process of

RIP routing table.
3-12

Command Function
ZXR10#debug ip rip trigger This traces RIP trigger events.
An example of the debug ip rip command output is shown below.

ZXR10#debug monitor
ZXR10#debug ip rip
RIP protocol debugging is on
ZXR10#
11:01:28: RIP: building update entries
130.1.0.0/16 via 0.0.0.0, metric 1, tag 0
130.1.1.0/24 via 0.0.0.0, metric 1, tag 0
177.0.0.0/9 via 0.0.0.0, metric 1, tag 0
193.1.168.0/24 via 0.0.0.0, metric 1, tag 0
197.1.0.0/16 via 0.0.0.0, metric 1, tag 0
199.2.0.0/16 via 0.0.0.0, metric 1, tag 0
202.119.8.0/24 via 0.0.0.0, metric 1, tag 0
11:01:28: RIP: sending v2 periodic update to 224.0.0.9
via pos3_3/1 (193.1.1.111)
130.1.0.0/16 via 0.0.0.0, metric 1, tag 0
130.1.1.0/24 via 0.0.0.0, metric 1, tag 0
177.0.0.0/9 via 0.0.0.0, metric 1, tag 0
193.1.1.0/24 via 0.0.0.0, metric 1, tag 0
via fei-0/1/0/1 (193.1.168.111)
via fei-0/1/0/1 (193.1.168.111)
via fei-0/1/0/1 (193.1.168.111)
via fei-0/1/0/1 (193.1.168.111)
224.0.0.9 RIP routes are distributed to outside by multicast mode.
via fei-0/1/0/1 Routes are distributed by an interface.
3.5 RIP Configuration Example

Configuration Description
Since the realizing principle and configuration of RIP are very simple, it is mainly used to
some simple networks. As shown in Figure 3-1, RIP run on both of R1 and R2.
3-13

Figure 3-1 RIP Configuration Example Topology
Configuration Thought
1. Configure interface IP addresses.
2. Configure RIP.
3. Enable RIP configurations on interfaces.
4. Test configuration result to make sure that neighborhood is established between R1
and R2. R1 and R2 can learn the routes advertised by the peer between each other.
Configuration Commands
R1(config)#interface fei-0/1/0/1
R1(config-if)#ip address 192.168.1.1 255.255.255.0
R1(config-if)#exit
R1(config-if)#exit
R1(config)#router rip
R1(config-rip)#network 192.168.1.1 0.0.0.255
R2(config-if)#exit
R2(config-if)#exit
Configuration Verification
After the configuration is finished, the following information needs to be displayed, that
indicates the neighborhood is established between R1 and R2, and they can learn routes
between each other.
3-14

Use the show running-config rip command on R1 to inspect whether RIP configuration is
correct.
R1(config-rip)#show running-config rip
router rip
network 192.168.1.0 0.0.0.255
network 10.1.0.0 0.0.255.255
interface fei-0/1/0/1
$
$
!
R1(config-rip)#
R1(config)#show ip rip database
Routes of rip:
Dest Metric RtPrf Time From

*> 10.0.0.0/8 2 120 00:00:12 192.168.1.2
* 10.0.0.0/8 1 254 00:00:29 0.0.0.0
*> 10.1.0.0/16 0 0 00:00:00 0.0.0.0
*> 192.168.1.0/24 0 0 00:00:00 0.0.0.0
R1(config)#
R1(config)#show ip rip neighbors
192.168.1.2 fei-0/1/0/1
Use the show running-config rip command on R2 to inspect whether RIP configuration is
correct.
R2(config-rip)#show running-config rip
router rip
network 192.168.1.0 0.0.0.255
network 10.2.0.0 0.0.255.255
$
$
!
R2(config)#show ip rip database
Routes of rip:
Dest Metric RtPrf Time From

*> 10.0.0.0/8 1 254 00:00:03 0.0.0.0
3-15

*> 10.2.0.0/16 0 0 00:00:00 0.0.0.0

*> 192.168.1.0/24 0 0 00:00:00 0.0.0.0
R2(config)#show ip rip neighbors
192.168.1.1 fei-0/1/0/1
3.6 RIP Fault Handling

3.6.1 Network Topology
Take the topology shown in Figure 3-2 as an example to describe how to handle an RIP
fault.
Figure 3-2 Network Topology of an RIP Fault
3.6.2 Fault Analysis

Symptom:
R1 and R2 fail to find neighbor, and they cannot learn routes between each other.
Fault analysis:
In general, the first thing is that inspect the fault is caused by hardware or software.
For hardware, inspect master control board, line card, interface card and network cable
(inspect whether the direct-connected interfaces of R1 and R2 can ping each other).
Make sure that the hardware part runs well, and then inspect software. For software,
inspect the global configuration of RIP first, including version, network, time basic, disable
interface and redistribute. Inspect whether these items are configured reasonably.
And then, inspect the RIP configuration of interfaces, such as the type of packets received
and sent by RIP interface, authentication mode and passive/active mode. For the special
default route and sub network advertisement, inspect the configurations of notify and
only-send-subnet.
3.6.3 Handling Flow

The flow to handle an RIP fault is shown in Figure 3-3.
3-16

Figure 3-3 Flow to Handle an RIP Fault
3.6.4 Handling Procedure

The procedure to handle an RIP fault is described below.
3-17

1. Inspect whether the administrative and protocol states of two interconnected interfaces
are up. Inspect whether the cable connection is correct and the working state of
interface card is normal.
2. Inspect whether IP address configuration of interface is correct. Inspect whether the
pair of routers can ping each other successfully. Inspect whether the peer ARP can
be learnt.
3. ZXR10 M6000 supports RIPv1 and RIPv2 by default. Use the no version command to
restore the default setting. Use the show ip rip database command to view interface
address and network segment. Make sure that RIP timers of all routers are configured
consistently. Make sure that all of the RIP interfaces are enabled (the default setting
is that every interface is enabled). Use the show ip rip database command to inspect
whether the routes learnt form other routing protocols are redistributed to RIP.
4. Use the show running-config rip command to inspect the RIP configuration of
direct-connected interface. Make sure that the configurations of type of packets sent
and received, authentication type, passive/active are consistent. Use no ip rip on
interface to restore the default setting. Make sure that the correct authentication and
authentication string are configured on the interface to be authenticated.
3-18

Chapter 4
OSPF Configuration
Table of Contents
OSPF Overview .........................................................................................................4-1
Configuring OSPF ......................................................................................................4-8
OSPF Maintenance ..................................................................................................4-37
OSPF Configuration Examples.................................................................................4-46
OSPF Fault Handling ...............................................................................................4-54
4.1 OSPF Overview

OSPF is one of the most popular and widely used routing protocols. OSPF is a link state
protocol, which overcomes the disadvantages of RIP and other distance vector protocols.
OSPF version 1 is defined by RFC1131. At present, OSPF version 2 is used, which is
defined in RFC2328. ZXR10 M6000 supports OSPF version 2 completely.
OSPF has the following features.
l It converges fast. To ensure the synchronization of database, OSPF fast floods the
updating of link state and calculates routing table at the same time.
l It does not have route loop. Shortest Path First (SPF) algorithm is applied to guarantee
that no loops will be generated.
l It uses route aggregation, which reduces the size of the routing table.
l It supports Variable Length Subnet Mask (VLSM) and Classless Inter-Domain Routing
(CIDR).
l It uses trigger updating mechanism to send updating message only when network
changes.
l It supports interface packet authentication to guarantee the security of routing
calculation
l It sends update packet by multicast mode.
4.1.1 OSPF Basic

An OSPF router generates the routing table by setting up a link state database. The link
state databases of all OSPF routers must be the totally same.
Link state database is built according to Link State Advertisements (LSAs) which are
generated by all routers and spread over the whole OSPF network. There are many
types of LSAs, and a complete LSA set shows an accurate distribution diagram over the
whole network.
4-1

4.1.2 OSPF Algorithm

OSPF uses cost as the metric. The cost is distributed to each port of a router. A port
calculates the cost based on 100 M benchmark by default. The path cost to a particular
destination is the total cost of all links along the path between the router and the destination.
To generate a routing table by using LSA database, a router runs the Dijkstra SPF algorithm
to construct the shortest path tree. Router is the root of the path tree. The Dijkstra algorithm
calculates the a path with the lowest cost to any node on the network. Router saves the
routes of the paths in the routing table.
Compared to RIP, OSPF does not simply broadcast all its routing information regularly.
An OSPF router uses hello packets to keep the neighborhood. When a router does not
receive any hello packets from a neighbor within a period of time (dead-interval), then it
will consider that the neighbor is not already alive.
OSPF routes are incrementally updated. Router sends the update information only when
topology changes. When the age of an LSA reaches 1800 seconds (LSA updating interval,
LSA Refresh Time), router sends an LSA updating packet.
4.1.3 OSPF Network Types

OSPF network type determines the forming of adjacency relationship and the setting of
interface timer.
There are five network types in OSPF, and they are as follows:
l Broadcast network
l Non-Broadcast Multiple Access (NBMA) network
l Point-to-Point network
l Point-to-Multipoint network
l Virtual Links network
4.1.4 HELLO Packet and Timer

OSPF routers exchange HELLO packets in a certain interval, which is to keep alive state
among neighbors. By using HELLO packet, router can detect OSPF neighbor and select
the Designated Router (DR) and the Backup Designated Router (BDR). In broadcast,
point-to-multipoint and point-to-point network types, HELLO packets can be sent in
multicast mode. In NBMA network, point-to-multipoint network and virtual links, HELLO
packets are sent in unicast mode.
OSPF uses three kinds of timers relating to HELLO packets:
1. Sending interval (HELLO interval)
HELLO interval is an attribute of interface, which defines the interval that a router sends
HELLO packets by a router from each interface. The default HELLO packet sending
interval depends on the network type.
In broadcast and point-to-point networks, the default HELLO packet sending interval
is 10 seconds. In NBMA and point-to-multipoint networks, the default HELLO packet
4-2

Chapter 4 OSPF Configuration
sending interval is 30 seconds. The adjacent routers must have the same Hello interval
so as to become neighbors.
2. Router dead-interval
The router dead-interval refers to the waiting time from the router receiving the last
hello packet to the router detecting that the neighbor is offline. The default router
dead-interval is four times of HELLO packet sending interval, which is applicable to all
network types.
3. Poll Interval
Poll interval only applies to NBMA network.
4.1.5 OSPF Neighbors

OSPF neighbors are a group of routers belonging to the same network. These routers
stipulate some configuration parameters. The routers must be neighbors to form
adjacency. To form adjacency, the routers have to be neighborhood.
Routers analyze their HELLO packets to make sure that the required parameters are
stipulated when they want to form neighborhood. The following parameters have to be
consistent so that the adjacent routers can set up neighborhood, area ID, area flag,
authentication information, HELLO packet sending interval and router dead interval.
4.1.6 Adjacency and DR

When two routers form an adjacency, they can exchange routing messages. Whether two
routers can form an adjacency depends upon network type connected to routers. The
network type of the connecting router decides whether two routers can form adjacency.
l There are only two routers in point-to point network or virtual links. The two routers
have to exchange the related routing information, so they can form an adjacency
automatically. A point-to-multipoint network can be regarded as a set of point-to-point
networks, so an adjacency is formed between each pair of routers.
l In a broadcast or an NBMA network, an adjacency may not be formed between two
neighbors. If adjacencies are already established among all routers (the number
of routers is "n" for example) on a network, each router will have "(n-1)" adjacent
connections and the network will have "n×(n-1)/2" adjacent connections.
In a large multi-access network, the router will be too heavy traffic if every one needs to
trace so many adjacent connections. Furthermore, the exchanging of routing information
between each adjacent routers wastes lots of network bandwidths.
Since a large multi-access network has a mass of redundancy information, OSPF defines
a DR and a BDR. The DR and BDR must form an adjacency with each OSPF router on
network. Each OSPF router only forms an adjacent relationships with DR and BDR. All
routers only send routing information to DR, and DR sends the information to other routers
in the same network segment. The two routers (neither DR nor BDR) do not establish an
4-3

adjacency between each other and neither will they exchange routing information. If the
DR stops working, the BDR will become a DR.
4.1.7 Router Priority and DR Election

Every interface has its own priority on router, which affects the capability of the router to
become a DR or BDR on the network. The priority of router interface is expressed by an
eight-bit unsigned integer, ranging from 0 to 255 (the default value is "1").
In DR election, the interface priorities are compared at first. The router with the highest
priority becomes a DR in the network segment. If the priorities of two routers are the same,
the router which router id is the largest will become a DR. The router which priority is 0
cannot be a DR or BDR.
DR is a concept used in network segment, which is based on router interface. That is,
a router can be a DR on its an interface, and it can be BDR or DROther on its another
interface.
4.1.8 OSPF Area

To reduce the information size that each router stores and maintains and shield the range
that network changing influences on, OSPF divides a network into some minor parts.
Each router must have the complete information of the area where it locates. Area
Border Router (ABR) is used to transmit routing information between different areas. The
information is shared by areas. The routing information can be filtered on area edge,
which reduces the routing information stored in routers.
An area is identified with 32-bit unsigned number. Area 0 is reserved to identify backbone
network, and all other areas must be connected to area 0. The backbone area of OSPF
network has to be continuous. Routers can be one or multiple of the following types
according to its tasks in the area, as shown in Figure 4-1.
Figure 4-1 OSPF Router Type
4-4

l Internal router
All interfaces of the router belong to the same OSPF area. An internal router only
generates a Router LSA and saves a Link-state Database (LSDB).
l Backbone router
A router that its one interface belongs to area 0 at least.
l ABR
A router that its one interface belongs to area 0 at least and one interface belongs to
other area at least.
All ABRs are backbone routers.
l Autonomous System Border Routers (ASBR)
The router has other routing protocols, such as static route, interface direct route and
RIP, IGRP and so on.
The advantages of area division are listed below,
l ABR generates LSAs according by using routes in its area after dividing areas, so
the routes can be aggregated firstly according to the rule of IP addresses, and then
generate LSAs. In this way, the number of LSAs is reduced a lot in an Autonomous
System (AS).
l After the area is divided, the changing of network topology is synchronized in the area
firstly. If the changing influences on the aggregated route, ABR will notify the changing
to other areas. In this way, most of topology changes are shielded in the area.
4.1.9 LSA Type and Flooding

LSA is a mode of exchanging link state database information among OSPF routers. A
router uses LSAs to construct an accurate and complete network diagram and generates
the routes used in its routing table. ZXR10 M6000 supports the following eight types of
LSAs.
l Type 1: Router LSA
It is the basic LSA. Every OSPF router generates a Router LSA. Router LSA is used to
describe the information of the interface running OSPF on router, such as connection
status, cost and so on. An ABR generates a Router LSA for every area. A Router
LSA is transmitted in the whole area at where it locates.
l Type 2: Network LSA

The Network LSA is generated by DR. For a broadcast or NBMA network, to reduce
the times of packet exchanging between routers in a network segment, the concept
of DR is advanced. When a DR exists in a network segment, not only the method
of packets sending is changed, but also the description of link state is changed. The
Router LSA generated by a DROther or BDR only describes the connection from itself
to a DR. While, DR uses the Network LSA to describe all routers which already set
4-5

up adjacent relationships with itself in the network segment (it lists the Router IDs of
adjacent routers). A Network LSA is transmitted in the whole area at where it locates.
l Type 3: Network summary LSA
Network summary LSAs are generated by ABRs. When a ABR finishes routing
calculation in the area at where it locates, it enquires the routing table and
encapsulates each OSPF route into a Network Summary LSA. The Network
Summary LSAs are sent out area, which describe some information of a route, such
as the destination address, mask and cost. A Network summary LSA is transmitted
to all areas except the area which generates the LSA.
l Type 4: ASBR summary LSA
The ASBR summary LSA is also generated by an ABR. It describes the route that
goes to the ASBR in the area. The content of ASBR Summary LSA is almost the
same to that of Network summary LSA. The only difference is that the destination
address described by ASBR summary LSA is ASBR (host route, the mask is 0.0.0.0).
A ASBR summary LSA is transmitted to all areas except the area which generates
the LSA.
l Type 5: External LSA of AS
The external LSA of AS is generated by an ASBR. It mainly describes the information
of an route which goes to the external AS. An external LSA of AS contains some
information, such as destination address, mask and cost and so on. External LSA of
AS is an unique type that is independent of area. An external LSA of AS is transmitted
in the whole AS (except STUB area).
l Type 7: External LSA of Not-So-Stubby Area (NSSA)
External LSA of NSSA only applies to NSSA.
l Type 9: Local non-transparent LSA
l Type 10: Area non-transparent LSA
OSPF operation depends on all the routers in one area which share a common link state
database. Therefore, all LSAs are flooded through the area and the processing must be
reliable. A router which receives LSAs from a special area will flood the LSAs to other
interfaces which belong to the i area.
LSAs do not have their own packets, and they are contained in Link state Update (LSU)
packets. A LSU can contain many LSAs.
When a router receives a LSU, it abstracts the LSA from the packet and inputs the LSA to
its database. Meanwhile, the router constructs its own LSU and sends the updated LSU
to its adjacent neighbor router(s).
OSPF uses Link State Acknowledgement (LSAck) to confirm whether each LSA is
successfully received by its neighbor. A LSAck has the header of an acknowledged LSA,
which provides sufficient information for uniquely identifying an LSA.
When a router sends a LSA to an interface, the LSA is recorded in the retransmission
queue of the interface.
4-6

The router will wait the maximum time interval to receive the LSAck of LSA. If the router
does not receive the LSAck in the specified time, it will retransmit the LSA.
The router can send the original LSU in unicast or multicast mode, but the retransmitted
LSU is must in unicast mode.
4.1.10 Stub Area and Totally Stubby Area

When a non-backbone area does not have an ASBR, a router only has one path arriving
to an AS external network, that is, a path passing through an ABR. Therefore, the routers
belonging to these areas will send the LSAs sending to the unknown hosts outside the AS
to ABR.
In this way, it is not required that flood LSAs of type 5 to the area. The area does not have
the LSAs of type 4 either. The area is called stub area.
In a stub area, all routers must be configured as stub routers. A HELLO packet contains
a "stub area" flag bit. The flag bit must be consistent among neighbors.
The ABR in a stub area can filter LSAs of type 5 to prevent them from being advertised to
stub area. In meantime, the ABR generates an LSA of type 3 to advertise a default route
arriving to an AS external destination address.
If the ABR also filters the LSA of type 3 and advertises a default route arriving to an AS
external destination address, the area is called totally stubby area.
4.1.11 Not-So-Stubby Area

A router in a stub area refuses LSAs of type 5, so ASBR is not a part of the stub area.
However, it is hoped that a stub area with an ASBR can be generated. In this way, routers
in the area can receive AS external routes from the ASBR belonging to the same area, but
the external routing information from other areas will be blocked.
To realize such an area, OSPF defines NSSA. In a NSSA, an ASBR generates LSAs of
type 7 instead the LSAs of type 5. The ABR cannot send the LSAs of type 7 to other
OSPF areas. On the one hand, it blocks external routes to arrive the NSSA area at the
area border. On the other hand, it converts the LSAs of tyoe 7 into the LSAs of type 5 and
sends them to other areas.
4.1.12 OSPF Authentication

Authentication is used to exchange packets between two OSPF neighbors. The
authentication type should be consistent on the OSPF neighbors. Authentication type is
contained by all packets.
Authentication type "0" indicates no authentication, "1" indicates simple password
authentication and "2" indicates MD5 encryption authentication.
For plain text authentication , an interface only allows a password. The password of each
interface can be different, but the interfaces in a special network must have the same
passwords. The simple password is sent through OSPF packets in plain text mode.
4-7

4.1.13 DownBit
When Multiprotocol BGP (MP-BGP) routes are redistributed to OSPF vrf instance to
generate LSAs, the option fields of type-3 and type-5 LSAs must be marked as down bit.
The LSAs are displayed as Downward. This is a method to prevent routing loopback.
When a PE router detects that a LSA is already marked as down bit, the PE will not
participate in the OSPF route calculation. When OSPF routes are redistributed to BGP,
the LSAs with down bit are not redistributed to be BGP route.
4.1.14 Max-Metric
Considering the requirements for traffic management and so on, some routers need to act
as the terminal rather than transit points of the route. In order to add the nodes without the
capability of traversing to the network, the max-metric function is used.
For example, a router just restarts, and BGP route does not converge, use the max-metric
router-lsa on-startup wait-for-bgp command to avoid route black hole.
4.2 Configuring OSPF

4.2.1 Enabling OSPF
To enable OSPF on router and make routers can learn routes between each other by OSPF
protocol, perform the following commands.
1 ZXR10(config)#router ospf < process-id> [ vrf < vrf-name> ] This enables OSPF process to
run OSPF and enters OSPF
configuration mode.
After OSPF protocol is enabled, one
of current interfaces will be chosen
as the address of OSPF router-id.
If no interface has IP address
on router, router-id will not be
selected. OSPF is dynamically got
by configuring an interface address
or configure route-id manually and
clear OSPF process.
2 ZXR10(config-ospfv2)#network < ip-address> < wildcard-mask> This defines an interface to run

area < area-id> OSPF protocol, and defines an area
ID to the interface.
Create an area if it does not exist.
4-8

3 ZXR10(config-ospfv2)#router-id < ip-address> This configures router-id of router.

It is suggested that use Loopback
address as router-id of router.
4 ZXR10(config-ospfv2)#end This returns to privileged mode.
ZXR10#clear ip ospf process < process-id> This restarts OSPF process.
Example
As shown in Figure 4-2, enable OSPF on R1 and R2 interfaces.
Router-ids of devices are listed below.
Device Router ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
Figure 4-2 OSPF Basic Configuration Example
R1(config-if)#exit
R1(config)#router ospf 10
R1(config-ospfv2)#network 30.0.0.0 0.0.0.3 area 0
R1(config-ospfv2)#exit
View OSPF information, as shown below.

R1(config)#show ip ospf
OSPF 10 Router ID 30.0.0.1 enable
Enabled for 00:00:21,Debug on
Number of areas 1, Stub 0, Transit 0
Number of interfaces 1
……
Area 0.0.0.0 enable
4-9

Enabled for 00:00:05

Area has no authentication
Times spf has been run 1
Number of interfaces 1. Up 1
Here, OSPF is configured on R1. OSPF is enabled. The Router-ID is the IP address of
interface fei-0/1/0/1.
Configure R2. To set up OSPF connection by using loopback address, the loopback
address has to be configured at first, and then enable OSPF process.
R2(config)#interface loopback1
R2(config-if)#ip adderss 1.1.1.3 255.255.255.255
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
View OSPF information. Here, OSPF selects the IP address of loopback 1 as Router-ID
automatically.
R2(config-ospfv2)#show ip ospf
Number of areas 0, Normal 0, Stub 0, NSSA 0
R3(config-if)#exit
R3(config-if)#exit
View routing table on R3, as shown below.

IPv4 Routing Table:
Dest Mask Gw Interface Owner pri metric
1.1.1.4 255.255.255.255 1.1.1.4 loopback1 address 0 0
4-10

30.0.0.0 255.255.255.252 30.0.1.2 fei-0/1/0/1 ospf 110 2

30.0.1.0 255.255.255.252 30.0.1.1 fei-0/1/0/1 direct 0 0
30.0.1.1 255.255.255.255 30.0.1.1 fei-0/1/0/1 address 0 0
Here, use R3 to ping R1. If the ping is successful, the route is normal and OSPF runs
normally.
4.2.2 Configuring OSPF Interface Attributes

To set up OSPF neighborhood, perform the following steps to modify the attributes of
OSPF interface. The attributes need to be consistent for connecting the devices of different
manufactories.
1 ZXR10(config)#router ospf < process-id> [ vrf < vrf-name> ] This enters OSPF configuration
mode.
2 ZXR10(config-ospfv2)#interface { < interface-name> | byname < This enters interface configuration

byname> } mode.
3 ZXR10(config-ospfv2-if)#hello-interval < seconds> This sets the time interval for sending
HELLO packets on interface.
The unit is second, the range is
1–65535, and the default value is 10
seconds.
ZXR10(config-ospfv2-if)#dead-interval < seconds> This designates the dead interval of

neighbor on an interface.
seconds.
ZXR10(config-ospfv2-if)#retransmit-interval < seconds> This specifies the time interval for

retransmitting LSA on interface.
seconds.
ZXR10(config-ospfv2-if)#transmit-delay < seconds> This specifies a time delay for

sending a link state update packet
on interface.
second.
ZXR10(config-ospfv2-if)#cost < cost> This sets the interface cost.

The range is 1–65535, and the
default value is 100M/interface
bandwidth. The router LSA of
4-11

which the metric is 65535 does not

participate with route calculation.
ZXR10(config-ospfv2-if)#priority < priority> This sets the interface priority.

The range is 0–255, and the default
value is 1.
Example
As shown in Figure 4-3, modify the default priority on the OSPF interfaces of R1 and R2.
Figure 4-3 OSPF Interface Attribute Configuration
The router-IDs of devices are listed below.
Device Router ID
R1 1.1.1.2
R2 1.1.1.3
Enable OSPF protocol on R1 and R2, and advertise the network segment.
R1(config-if)#exit
R1(config-if)#exit
R1(config-ospfv2)#router-id 1.1.1.2
R2(config-if)#exit
4-12

R2(config-if)#exit
Modify OSPF default attributes on interfaces.

R1(config-ospfv2)# interface fei-0/1/0/1
R1(config-ospfv2-if)# hello-interval 20
/*This sets the time interval for sending HELLO packets on the
specified interface as 20 seconds.*/
R1(config-ospfv2-if)# dead-interval 80
/*This sets the dead time of neighbor on the specified interface
as 80 seconds.*/
R1(config-ospfv2-if)# retransmit-interval 10
/*This sets the time interval for retransmitting LSA on the
specified interface as 10 seconds.*/
R1(config-ospfv2-if)# retransmit-delay 2
/*This sets the time delay of transmitting a link state update
packet on the specified interface as 2 seconds.*/
R1(config-ospfv2-if)# cost 10
/*This sets the cost on the specified interface as 100.*/
R1(config-ospfv2-if)# priority 10
/*This sets the interface priority as 10.*/
4.2.3 Configuring OSPF Authentication

To enhance the safety of routing process on network, perform the following steps to
configure OSPF authentication on router. The passwords used by OSPF neighbors have
to be the same.
1 ZXR10(config)#router ospf < process-id> [ vrf < vrf-name> ] This enters OSPF route mode.
ZXR10(config-ospfv2)#area < area-id> authentication [ This enables the authentication in an

message-digest] OSPF area.
2 ZXR10(config-ospfv2)#interface { < interface-name> | byname < This enters interface configuration

byname> } mode.
ZXR10(config-ospfv2-if)#authentication [ null| message-digest] This sets authentication mode on

interface.
4-13

3 ZXR10(config-ospfv2-if)#authentication-key < password> This sets password on the interface

which uses plain text authentication
mode.
ZXR10(config-ospfv2-if)#message-digest-key < keyid> md5 < This sets keyid and authentication
password> [ delay < time> ] encypt< password> [ delay < time> ] password on the interface which
uses MD5 authentication mode.
< keyid> Keyid, it is an integer ranging from 1 to 255.
md5 < password> Authentication password, the length is 1–16 characters (without
space)
delay < time> Time delay, the unit is minute, the range is 0–100000.
encypt This encrypts the password.
Example
As shown in Figure 4-4, configure authentication function on OSPF interfaces of R1 and
R2.
The router-ids of devices are listed below.
Device Router ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
4-14

Figure 4-4 OSPF Authentication Configuration Example
In area 0, set up OSPF neighborhood between R1 and R2. In area 1, set up OSPF
neighborhood between R2 and R3.
R1(config-if)#exit
R1(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
4-15

R3(config-if)#exit
R3(config-if)#exit
R3(config-ospfv2)#ospf-id 1.1.1.4
Enable plain text authentication on the interfaces belonging to area 0, set authentication
password as zte.
R1(config-ospfv2)#area 0 authentication
R1(config-ospfv2)#interface fei-0/1/0/1
R1(config-ospfv2-if)# authentication
R1(config-ospfv2-if)# authentication-key zte
R1(config-ospfv2-if)#exit
R2(config-osp2f)#area 0 authentication
R2(config-ospfv2-if)#authentication
R2(config-ospfv2-if)#authentication-key zte
Use the show ip ospf command to view the configuration that plain text authentication
already takes effect in area 0.
R2(config)#show ip ospf
Number of areas 1, Stub 0, Transit 0
……
Area 0.0.0.0 enable
Area has simple password authentication
Number of ASBR local to this area 0
4-16

Number of ABR local to this area 1

……
Enable MD5 authentication on the interfaces belonging to area 1. The key-id is 1, the
authentication password is zte.
R2(config-ospfv2)#area 1 authentication message-digest
R2(config-ospfv2-if)# authentication message-digest
R2(config-ospfv2-if)# message-digest-key 1 md5 zte
R3(config-ospfv2)#area 1 authentication message-digest
R3(config-ospfv2-if)# authentication message-digest
R3(config-ospfv2-if)# message-digest-key 1 md5 zte
View the information of OSPF interface on R3 that the authentication mode is MD5.
R3(config)#show ip ospf interface fei-0/1/0/1
OSPF Router with ID (1.1.1.4) (Process ID 10)
Fei-0/1/0/1 is up
Internet Address 30.0.1.1 255.255.255.252 enable
Up for 00:09:38
In the area 0.0.0.1 BDR
Cost 1, Priority 1, Network Type broadcast
Transmit Delay(sec) 1, Authentication Type message-digest
……
4.2.4 Configuring OSPF Stub Area

To configure OSPF stub and totally stubby area on ZXR10 M6000, perform the following
steps.
1 ZXR10(config)#router ospf < process-id> [ vrf < vrf-name> ] This enters OSPF route configuration
mode.
2 ZXR10(config-ospfv2)#area < area-id> stub [ default-cost < cost> ] This sets an area as stub area.
4-17

3 ZXR10(config-ospfv2)#area < area-id> stub no-summary [ This configures ABR not to introduce
default-cost < cost> ] any type-3 route information on stub
area and only has one default type-3
LSA.
no-summary This disables ABR to send summary route information to stub area.
default-cost < cost> The cost of a default route advertised to stub area. The range is
0–65535.
Example
As shown in Figure 4-5, set area 1 as stub area.
Device Router ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
Figure 4-5 OSPF Stub and Totally Stubby Area Configuration Example
R1 configuration,
R1(config-if)#exit
4-18

R1(config-if)#exit
R1(config-if)#exit
R1(config-ospfv2)#redistribute connected
R2 configuration,
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-ospfv2)#area 1 stub
R3 configuration,
R3(config-if)#exit
R3(config-if)#exit
R3(config-ospfv2)#area 1 stub
Perform the following configuration on R2 to configure area 1 as totally stubby area if it is

required.
R2(config-ospfv2)#area 1 stub no-summary
4-19

The configuration on R3 is changed as follows.

R3(config-ospfv2)#area 1 stub no-summary
4.2.5 Configuring NSSA Area

To configure NSSA area on ZXR10 M6000, perform the following steps.
2 ZXR10(config-ospfv2)#area < area-id> nssa [ no-redistribution] [ This configures an area as NSSA

default-information-originate [ metric < metric-value> ] [ metric-type area and designates whether to
< type> ] ] [ no-summary] [ trans-type7-suppress-fa ] [ translator-role { forbid ABR to send summary route
always | candidate } ] [ translator-stab-intv< stab-intv> ] information to the NSSA area,
whether to introduce type 7 external
LSA to NSSA area, and whether to
generate type 7 default LSA.
The summary route is not forbidden
by default, the type 7 LSA is
introduced, ABR generates default
type 7 LSA and non-ABR route does
not generate default type 7 LSA.
Parameters Description
no-redistribution Do not redistribute NSSA link state advertisement to the NSSA area
default-information-originate Generate default route link state of type 7
metric < metric-value> The cost of advertising default route link state of type 7, ranging from
0–16777214
metric-type < type> The type of default route link state advertisement of type 7, ext-1 and
ext-2
no-summary Do not send summary link state advertisement to the NSSA area
trans-type7-suppress-fa Suppress address forwarding when type 7 turns to type 5
translator-role Translator role during type 7 turning to type 5
{ always | candidate } Two translator roles, always and candidate
translator-stab-intv< stab-intv The time length for keeping translator role after translator qualification
is lost.
4-20

Example
As shown in Figure 4-6, set area 1 as NSSA area.
Device Router-ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
Figure 4-6 NSSA Area Configuration Example
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
4-21

R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-ospfv2)#area 1 nssa default-information-originate
R3(config-if)#exit
R3(config-if)#exit
R3(config-if)#exit
R3(config-ospfv2)#area 1 nssa
Perform the following configuration on ABR router R2 to forbid the route of type 3 to
advertise to the NSSA area if required.
R2(config-ospfv2)#area 1 nssa default-information-originate no-summary
R2(config)#exit
4.2.6 Configuring OSPF Inter-Area Route Aggregation

Route aggregation saves the resource of backbone area, which advertise a group of
network addresses as an aggregated address.
To configure route aggregation between OSPF areas on ZXR10 M6000, perform the
following steps.
4-22

2 ZXR10(config-ospfv2)#area < area-id> range < ip-address> This sets the range of summary
< net-mask> { summary-link | nssa-external-link } [ advertise | addresses in area.
not-advertise] [ tag < tag-value> ]
summary-link | nssa-external-link summary-link: type-3 summary

nssa-external-link: type-7 summary
advertise Advertise summary LSA of type 3
not-advertise Disable to advertise summary LSA of type 3. The information of the

network segment is not received by other areas.
tag < tag-value> Set tag of summary lsa, type-7 summary has this configuration, the
range is 0–4294967295
Example
As shown in Figure 4-7, configure OSPF on R1, R2 and R3. R2 acts as ABR, configure
route aggregation on R2.
The router-ID of devices are listed below.
Device Router-ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
Figure 4-7 OSPF Inter-Area Route Aggregation Configuration Example
4-23

R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R3(config-if)#exit
R3(config-if)#exit
4-24

View routing table on R3 after finishing the configuration that a route is not aggregated.
IPv4 Routing Table:
1.1.1.2 255.255.255.255 30.0.1.1 fei-0/1/0/1 ospf 110 20
2.2.2.0 255.255.255.252 30.0.1.1 fei-0/1/0/1 ospf 110 20
2.2.2.4 255.255.255.252 30.0.1.1 fei-0/1/0/1 ospf 110 20
30.0.0.0 255.255.255.252 30.0.1.1 fei-0/1/0/1 ospf 110 2
30.0.1.0 255.255.255.252 30.0.1.2 fei-0/1/0/1 direct 0 0
30.0.1.2 255.255.255.255 30.0.1.2 fei-0/1/0/1 address 0 0
Configure inter-area route aggregation on R2, as shown below.

R2(config-ospfv2)#area 1 range 2.2.2.0 255.255.255.248
summary-link
An aggregated route 2.2.2.0/29 is generated on R3 routing table.

R3# show ip forwarding route
IPv4 Routing Table:
2.2.2.0 255.255.255.248 30.0.1.1 fei-0/1/0/1 ospf 110 3
30.0.0.0 255.255.255.252 30.0.1.1 fei-0/1/0/1 ospf 110 2
30.0.1.0 255.255.255.252 30.0.1.2 fei-0/1/0/1 direct 0 0
30.0.1.2 255.255.255.255 30.0.1.2 fei-0/1/0/1 address 0 0
The default setting of "area 1 range 2.2.2.2 255.255.255.248 "is advertise. When the no
t-advertise keyword is chosen, aggregated route of 2.2.2.0 network segment will not be
shown on R3, and this network segment cannot be pinged, as shown below.
R2(config-ospfv2)#area 1 range 2.2.2.0 255.255.255.248
summary-link not-advertise
R3(config)#show ip route
IPv4 Routing Table:
30.0.0.0 255.255.255.252 30.0.1.1 fei-0/1/0/1 ospf 110 2
30.0.1.0 255.255.255.252 30.0.1.2 fei-0/1/0/1 direct 0 0
30.0.1.2 255.255.255.255 30.0.1.2 fei-0/1/0/1 address 0 0
Here, R3 does not learn the routing information of 2.2.2.0. The aggregated information of
2.2.2.0 still exists in R2 database, but not to be advertised to other areas.
4-25

4.2.7 Configuring Route Aggregation Upon Route Redistribution

The following configuration can only be used on ASBRs.
After the routes of other routing protocols are redistributed into OSPF, each independent
route is advertised as an external LSA. By means of aggregating, these external routes are
advertised as a single route, which reduces the size of OSPF link state database greatly.
To configure route aggregation upon route redistribution on ZXR10 M6000, perform the
following steps.
Step Commands Function
2 ZXR10(config-ospfv2)#summary-address < ip-address> < net-mask> This sets up summary address for
OSPF and summarizes other routing
protocol paths redistributed to the
OSPF.
Example
As shown in Figure 4-8, configure OSPF on R1, R2 and R3. Advertise external route of
R1, and configure ASBR route aggregation on R1.
The router-ID of devices are listed below.
Device Router-ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
Figure 4-8 Route Aggregation with Route Redistribution Configuration Example
4-26

R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-ospfv2)#summary-address 2.2.2.0 255.255.255.248
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R3(config-if)#exit
R3(config-if)#exit
4-27

View R2 routing table. There is an aggregated network segment 2.2.2.0/29 exists in routing
table.
R2(config)#show ip forwarding route
IPv4 Routing Table:
1.1.1.2 255.255.255.255 30.0.0.2 fei-0/1/0/1 ospf 110 20
2.2.2.0 255.255.255.248 30.0.0.2 fei-0/1/0/1 ospf 110 20
30.0.0.0 255.255.255.252 30.0.0.1 fei-0/1/0/1 direct 0 0
30.0.0.1 255.255.255.255 30.0.0.1 fei-0/1/0/1 address 0 0
30.0.1.0 255.255.255.252 30.0.1.1 fei-0/1/0/2 direct 0 0
30.0.1.1 255.255.255.255 30.0.1.1 fei-0/1/0/2 address 0 0
4.2.8 Configuring OSPF Route Redistribution

By means of advertising routing information of other route protocols to OSPF, different
dynamic route protocols can share route information.
To configure route redistribution on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router ospf < process-id> [ vrf < vrf-name> ] This enables OSPF process and
runs OSPF.
2 ZXR10(config-ospfv2)#redistribute< protocol> [ as < as-number> ] [ This controls the redistribution of

peer < peer-address> ] [ tag < tag-value> ] [ metric < metric-value> ] [ routes (these routes meet the relative
metric-type < type> ] [ route-map < map-tag> ] conditions) of other protocols into an
OSPF autonomous system.
By default, routes of other routing
protocols are not redistributed to an
OSPF AS. The metric of redistributed
BGP routes is 1, and the metric of
redistributed other routing protocols
is 20.
protocol Filter according to protocol types, valuing as connected, static and RIP,
bgp-ext and bgp-int, IS-IS-1, IS-IS-1-2, IS-IS-2, ospf-int and ospf-ext
as < as-number> AS number of the peer, ranging from 1 to 65535
peer < peer-address> IP address of the peer
tag < tag-value> Tag of redistributed LSA, ranging from 0–4294967295
4-28

metric < metric-value> Metric value of redistributed LSA. By default, use system default
metric, ranging from 0 to 16777214.
metric-type < type> The metric-type of redistributed lsa, valuing ext-1 and ext-2. By
default, it is ext-2.
route-map < map-tag> Set the redistributed route mapping name, the length is 1–16
characters.
As shown in Figure 4-9, redistribute RIP route in area 0.

Device Router-ID
R1 1.1.1.2
R2 1.1.1.3
Figure 4-9 OSPF Redistribution Route Configuration Example
1. Set up OSPF neighborhood between R1 and R2.

R1(config-if)#exit
R1(config-if)#exit
R2(config-if)#ip adderss 1.1.1.3255.255.255.255
R2(config-if)#exit
4-29


R2(config-if)#exit
2. Set up RIP between R1 and R3.
R1(config-if)#exit
R1(config-rip)#exit
R3(config-if)#exit
R3(config-if)#exit
R3(config-rip)#exit
Here, the information related to R3 is not certainly to be viewed in OSPF area.

3. Redistribute RIP route on R1.
R1(config-ospfv2)# redistribute rip
Here, the information of 2.2.2.0 network segment can be viewed on R2.

R2#show ip route
Pv4 Routing Table:
2.0.0.0 255.0.0.0 30.0.0.1 fei-0/1/0/1 ospf 110 20
30.0.0.0 255.255.255.252 30.0.0.2 fei-0/1/0/1 direct 0 0
30.0.0.2 255.255.255.255 30.0.0.2 fei-0/1/0/1 address 0 0
Redistribute direct-connected route on R1,
R1(config-ospfv2)# redistribute connected
4-30

The information of network segment 30.0.1.0 can be viewed on R2.

IPv4 Routing Table:
1.1.1.2 255.255.255.255 30.0.0.1 fei-0/1/0/1 ospf 110 20
2.0.0.0 255.0.0.0 30.0.0.1 fei-0/1/0/1 ospf 110 20
30.0.0.0 255.255.255.252 30.0.0.2 fei-0/1/0/1 direct 0 0
30.0.0.2 255.255.255.255 30.0.0.2 fei-0/1/0/1 address 0 0
30.0.1.0 255.255.255.252 30.0.0.1 fei-0/1/0/1 ospf 110 20
4.2.9 Configuring OSPF Default Route

When a router obtains a default route through other protocols or static route, the default
route needs to be advertised. Advertise the detail reachable route in normal mode if there
is no default route, and use commands to make the router become an ASBR.
mode.
2 ZXR10(config-ospfv2)#notify default route [ always] [ metric < When router obtains a default
metric-value> ] [ metric-type < type> ] [ route-map < map-tag> ] route 0/0 through other protocols or
configuring static route, the default
route is needed to be advertised.
If there is no default route, the detail
reachable route is advertised by
normal way.
The router will be an ASBR after this
command is used.
always If always is specified, it means that the default route will be advertised
no matter whether it exists. If not, whether to advertise the default
route is determined by whether the default route exists in the routing
table. If the default route exists, it will be advertised. Otherwise, the
default route is not advertised.
metric < metric-value> Metric of the default route, 0–16777214, 1 by default
metric-type < type> Type of the default route, ext-1 or ext-2, ext-2 by default
route-map < map-tag> The name of the route map for generating the default route, 1–16
characters.
4-31

4.2.10 Configuring OSPF Virtual Link

In OSPF, all areas must be connected to the backbone area. Virtual link can make a remote
area connect to the backbone area through other areas.
To configure OSPF virtual links on ZXR10 M6000, perform the following steps.
2 ZXR10(config-ospfv2)#area < area-id> virtual-link < router-id> This defines an OSPF virtual link.
[ hello-interval < seconds> ] [ retransmit-interval < seconds> Use the no command to delete the
] [ transmit-delay < seconds> ] [ dead-interval < seconds> ] [ designated virtual link.
authentication-key < key> ] [ message-digest-key < keyid> md5 < Virtual link cannot be created in area
cryptkey> [ delay < time> ] ] [ authentication [ null| message-digest] ] 0, stub and NSSA area.
< area-id> Identifier of transmission area where virtual link transits, cannot be
stub or nssa area or area 0
< router-id> Router ID of the peer of virtual link, it is an IP address in dotted decimal
hello-interval < seconds> Time interval for sending HELLO packets on virtual link, the range is
1–8192 seconds, 10 seconds by default.
retransmit-interval < seconds> Retransmission interval on virtual link, the range is 1–8192 seconds, 5
seconds by default
transmit-delay < seconds> Time delay for transmitting a link state update packet on virtual link,
the range is 1–8192 seconds, 1 second by default
dead-interval < seconds> Time interval for neighbor dead, the range is 1–8192 seconds, 40
seconds by default.
Example
As shown in Figure 4-10, set up virtual link connection between the interconnected
interfaces of R2 and R3.
Router-ID of devices are listed below.
Device Router-ID
R1 1.1.1.2
R2 1.1.1.3
R3 1.1.1.4
4-32

Figure 4-10 OSPF Virtual Link Configuration Example
R1(config-if)#exit
R1(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-ospfv2)#area 1 virtual-link 1.1.1.4
R3(config-if)#exit
4-33

R3(config-if)#exit
R3(config-if)#exit
R3(config-ospfv2)#network 10.0.1.0 0.0.0.3 area 0.0.0.1
R3(config-ospfv2)#area 1 virtual-link 1.1.1.3
4.2.11 Configuring Sham-Link

Since the priority of OSPF route is higher than that of BGP route, OSPF private route is
usually the first choice when both of public and OSPF private network route exist in link.
However, comparing to public route, private network route is not suitable to carry large
flow because its bandwidth is smaller. Therefore, a mechanism is required that the public
network share the private network flow. The public and private network can be selected
flexibly to carry the flow.
As shown in Figure 4-11, R1 and R2 belong to the same area. There are two types of LSAs
are learned by R1 when it accesses to R2. One is LSA of type 3 advertised by PE router,
another is LSA of type 1 flooded by area 0. According to OSPF route selection policy, the
route calculated by LSA of type 1 is optimal, so OSPF private network route is selected.
Sham-link is configured to make public network to share the flow.
Figure 4-11 Sham-link
Enable sham-link between PE routers, set up neighborhood and interact database. In this
way, private network routers belonging to the same area can learn two inner-area routes,
4-34

one route uses sham-link (MPLS VPN Backbone), another uses private network. To select
a route, modify metric attribute of route.
To configure sham-link on a PE, perform the following steps.
mode.
2 ZXR10(config-ospfv2)#area < area-id> sham-link < router-id1> < This sets up MPLS VPN between
router-id2> two PE routers to transmit OSPF
protocol packets.
< area-id> Area identifier, a decimal value (0-4294967295) or a dotted decimal

IP address.
< router-id1> ID of local router in sham-link, it is an IP address in dotted decimal

notation.
< router-id2> ID of the peer router in sham-link, it is an IP address in dotted decimal

notation.
4.2.12 Configuring Max-Metric

To configure max-metric on ZXR10 M6000, perform the following steps.
2 ZXR10(config-ospfv2)#max-metric router-lsa This configures a router not to learn

any OSPF routes. Transit-link of
local router-lsa is set to 65535.
Other routers only learn this router's
routes. The router is reachable for
network topology, but cannot be
through.
The route generated by this router
still can be learnt by other routers.
The router is still accessible in
topology, but other routers cannot
access through it.
4-35

3 ZXR10(config-ospfv2)#max-metric router-lsa on-startup This command realizes the following

wait-for-bgp function,
l If BGP neighbor is up, router
needs to wait 1 minute and then
it can be accessed by other
devices.
l If BGP neighbor is down, router
needs to wait 10 minutes and
then it can be accessed by other
devices.
4 ZXR10(config-ospfv2)#max-metric router-lsa on-startup < seconds> This configures the waiting time after
restarting to avoid route black hole.
and then the router can be through
in seconds, in range of 5-86400.
That is to say, router needs to
wait some time and then it can be
accessed by other devices.
5-86400.
4.2.13 Configuring OSPF Route Load Sharing

To configure OSPF route load sharing on ZXR10 M6000, perform the following steps.
mode.
2 ZXR10(config-ospfv2)#maximum-paths < number> This configures the count of routes


mode.

4-36


value.
4.2.14 Configuring OSPF FRR

To configure OSPF Fast Reroute (FRR) on ZXR10 M6000, perform the following steps.
mode.
2 ZXR10(config-ospf)#fast-reroute alternate-protect-type { default| This enables and configures route

down-stream-path} backup mode. There are two modes,
default mode (LFAs mode) and
down-stream-path mode.
3 ZXR10(config-ospf)#interface < interface-name> This enters protocol interface

configuration mode.
4 ZXR10(config-ospfv2-if)#cost < value> This configures the cost of the

interface. After FRR backup route
automatic calculation is enabled,
the route of which the cost value is
greater becomes the backup route.
5 ZXR10(config-ospf)#fast-reroute [ backup-interface < This configures an FRR backup

interface-name> ] interface of the local interface. When
the automatic FRR route calculation
condition defined in Step 2 is not
met, this static FRR takes effect. But
static FRR cannot filter loops.
4.3 OSPF Maintenance

ZXR10 M6000 provides the following commands to view OSPF information.
4-37

Command Function
ZXR10#show ip ospf [ < process-id> ] This shows the summary information of

OSPF protocol and each OSPF area.
ZXR10#show ip ospf interface [ < interface-name> ] [ process < process-id> ] This shows the information of OSPF
interface.
ZXR10#show ip ospf database [ database-summary | adv-router < router-id> This shows the information about OSPF
| self-originate] [ area < area-id> ] [ process < process-id> ] link database.
ZXR10#show ip ospf database router [ < link-state-id> ] [ adv-router < This shows the information of
router-id> | self-originate] [ area < area-id> ] [ process < process-id> ] router-LSA in OSPF data link state
database.
ZXR10#show ip ospf database network [ < link-state-id> ] [ adv-router < This shows the information of network
router-id> | self-originate] [ area < area-id> ] [ process < process-id> ] LSA in OSPF data link state database.
ZXR10#show ip ospf database summary [ < link-state-id> ] [ adv-router < This shows the information of summary
router-id> | self-originate] [ area < area-id> ] [ process < process-id> ] LSA in OSPF link state database.
ZXR10#show ip ospf database asbr-summary [ < link-state-id> ] [ adv-router This shows the information of
< router-id> | self-originate] [ area < area-id> ] [ process < process-id> ] asbr-summary LSA in OSPF link state
database.
ZXR10#show ip ospf database external [ < link-state-id> ] [ adv-router < This shows the information of external
ZXR10#show ip ospf database nssa [ < link-state-id> ] [ adv-router < This shows the information of NSSA
ZXR10#show ip ospf database { opaque-area | opaque-link} [ < link-state-id> This shows the information of
] [ adv-router < router-id> | self-originate] [ area < area-id> ] [ process < opaque-area LSA and opaque-link LSA
process-id> ] in OSPF link state database.
An example of the show ip ospf command output is shown below.

ZXR10(config)#show ip ospf 1
Domain ID type 0x5,value 0.0.0.1
Number of areas 2, Normal 2, Stub 0, NSSA 0
Number of interfaces 2
Number of neighbors 2
Number of adjacent neighbors 2
Number of virtual links 0
Total number of entries in LSDB 13
Number of ASEs in LSDB 1, Checksum Sum 0x0000dc0d
Number of grace LSAs 0
Number of new LSAs received 23
Number of self originated LSAs 22
Hold time between consecutive SPF 1 secs
4-38

Non-stop Forwarding disabled,

last NSF restart 00:21:13 ago (took 0 secs)
Area 0.0.0.0 enable (Demand circuit available)

Total number of intra/inter entries in LSDB 7.
Checksum Sum 0x00046565
Area-filter out not set
Area-filter in not set
Area ranges count 0
Area 0.0.0.1 enable (Demand circuit available)

Total number of intra/inter entries in LSDB 5.
Checksum Sum 0x00025888
Area-filter out not set
Area-filter in not set
Area ranges count 0
OSPF 1 Router ID 100.100.100.14 enable This OSPF instance is available
Domain ID type 0x5,value 0.0.0.1 The type of domain ID is 0x5, the value is 0.0.0.1
Number of areas 2, Normal 2, Stub 0, There are 2 domains, 2 normal domains and 0 stub area, 0 NSSA
NSSA 0 domain
Area 0.0.0.0 enable (Demand circuit The detailed content of each domain
available) and the following contents
An example of the show ip ospf interface command output is shown below.

ZXR10(config)#show ip os interface
fei-0/1/0/1 is up
4-39

Up for 00:17:51
In the area 0.0.0.0 DR
Transmit Delay(sec) 1, Authentication Type null
Timer intervals(sec) : Hello 10, Dead 40, Retransmit 5
Designated Router (ID) 100.100.100.14,
Interface address 100.100.100.14
Backup Designated router (ID) 100.1.1.2,
Interface address 100.100.100.12
Number of Neighbors 1, Number of Adjacent neighbors 1
100.1.1.2 BDR
fei-0/1/0/2 is up
Up for 00:16:25
In the area 0.0.0.1 DR
Transmit Delay(sec) 1, Authentication Type null
Timer intervals(sec) : Hello 10, Dead 40, Retransmit 5
Designated Router (ID) 100.100.100.14, Interface address 1.1.1.1
Backup Designated router (ID) 100.1.1.2, Interface address 1.1.1.10
Number of Neighbors 1, Number of Adjacent neighbors 1
100.1.1.2 BDR
Internet Address 100.100.100.14 Interface address

255.255.255.0 enable
In the area 0.0.0.0 DR It acts as DR in area 0.0.0.0
Timer intervals(sec) : Hello 10, Dead 40, The time interval for sending HELLO packet is 10 seconds, the dead
Retransmit 5 time is 40 seconds, and LSA retransmission interval is 5 seconds.
An example of the show ip ospf database command output is shown below.

ZXR10#show ip ospf database
Router Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum Link count
110.1.1.1 110.1.1.1 3 0x80000002 0x3dbe 1
Summary Net Link States (Area 0.0.0.0)
Link ID ADV Router Age Seq# Checksum
112.1.1.0 110.1.1.1 6 0x80000001 0xd99f
168.1.0.0 110.1.1.1 6 0x80000001 0xff43
Summary ASB Link States (Area 0.0.0.0)
4-40

168.1.1.3 110.1.1.1 6 0x80000001 0xc875

Link ID ADV Router Age Seq# Checksum Link count
110.1.1.1 110.1.1.1 3 0x80000025 0xf8f8 1
168.1.1.3 168.1.1.3 61 0x80000005 0x70e 2
Net Link States (Area 0.0.0.1)
168.1.1.1 110.1.1.1 1183 0x80000002 0x9787
Type-5 AS External Link States
Link ID ADV Router Age Seq# Checksum Tag
113.1.0.0 168.1.1.3 48 0x80000001 0xa0dd 0
111.1.0.0 110.1.1.1 272 0x80000001 0x4ae3 3489660928
Link ID LSA ID
ADV Router Advertising router
Age Aging time
Seq# Sequence number of LSA
Checksum Checksum
Link count Connection number
An example of the show ip ospf database router command output is shown below.
ZXR10#show ip ospf database router
Routing Bit Set on this LSA
LS age: 1700
Options: (No TOS-capability, No DC)
LS Type: Router Links
Link State ID: 110.1.1.1
Advertising Router: 110.1.1.1
LS Seq Number: 0x8000001f
Checksum: 0xf9e7
Length: 36
Number of Links: 1
Link connected to: a Stub Network
(Link ID) Network/subnet number: 110.1.0.0
(Link Data) Network Mask: 255.255.0.0
Number of TOS metrics: 0
TOS 0 Metrics: 1
4-41

LS age LSA aging time
LS Type LSA type
Link State ID LS ID
Advertising Router Advertisng router
LS Seq Number LSA sequence number
Checksum Checksum
Length Length
An example of the show ip ospf database network command output is shown below.
ZXR10#show ip ospf database network

Net Link States (Area 0.0.0.1)
Routing Bit Set on this LSA
LS age: 789
LS Type: Network Links
Link State ID: 168.1.1.1 (Address of Designated Router)
LS Seq Number: 0x80000002
Checksum: 0x9787
Length: 32
Network Mask: /16
Attached Router: 110.1.1.1
Attached Router: 168.1.1.3
LS Type LSA type
Link State ID LS ID
Advertising Router Advertising router
Checksum Checksum
Length Length
An example of the show ip ospf database summary command output is shown below.
ZXR10#show ip ospf database summary
4-42

Summary Net Link States (Area 0.0.0.0)

LS age: 129
LS Type: Summary Links(Network)
Link State ID: 112.1.1.0 (Summary Network Number)
Checksum: 0xd99f
Length: 28
Network Mask: /24
TOS: 0 Metric: 2
LS Type LSA type
Link State ID LS ID
Checksum Checksum
Length Length
An example of the show ip ospf database external command output is shown below.
ZXR10#show ip ospf database external

Type-5 AS External Link States
LS age: 18
LS Type: AS External Link
Link State ID: 111.1.0.0 (External Network Number)
Checksum: 0x4ae3
Length: 36
Network Mask: /16
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 20
Forward Address: 110.1.1.111
External Route Tag: 3489660928
4-43

LS Type LSA type
Link State ID LS ID
An example of the show ip ospf database asbr-summary command output is shown below.
ZXR10#show ip ospf database asbr-summary
Summary ASB Link States (Area 0.0.0.0)
LS age: 68
LS Type: Summary Links(AS Boundary Router)
Link State ID: 168.1.1.3 (AS Boundary Router address)
Checksum: 0xc875
Length: 28
Network Mask: /0
TOS: 0 Metric: 1
LS Type LSA type
Link State ID LS ID
Checksum Checksum
4.3.2 Common Maintenance Commands for Debugging

ZXR10 M6000 provides the following commands to debug OSPF.
Command Function
ZXR10#debug ip ospf adj < process-id> This enables the function that send
the debugging information of OSPF
adjacency events.
4-44

Command Function
ZXR10#debug ip ospf all < process-id> This enables all functions of OSPF
debugging.
ZXR10#debug ip ospf cspf < process-id> This enables the debugging function of
OSPF constrained-based shortest path
calculation.
ZXR10#debug ip ospf database-timer< process-id> This enables the function that send the
debugging information of OSPF link
state database timer events.
ZXR10#debug ip ospf events < process-id> This enables the function that send
important events.
ZXR10#debug ip ospf fast-reroute[ external | inter | intra | nbrspf] < This enables the function that send the
process-id> debugging information of OSPF fast
reroute.
ZXR10#debug ip ospf flood < process-id> This enables the function that send
flooding events.
ZXR10#debug ip ospf lsa-generation < process-id> This enables the function that send
debugging information of OSPF LSA
generation.
ZXR10#debug ip ospf nsf < process-id> This makes OSPF forward event
debugging information without
interruption.
ZXR10#debug ip ospf packet < process-id> This monitors the sending and receiving
of all OSPF packets.
ZXR10#debug ip ospf retransmission < process-id> This enables the function that send
retransmission queue events.
ZXR10#debug ip ospf spf [ external | inter | intra] < process-id> This enables the function that send the
debugging information of OSPF route
calculation events.
An example of the debug ip ospf all command output is shown below.

ZXR10#debug ip ospf all
ZXR10#debug monitor
ZXR10#
01:03:25: OSPF: send v:2 t:1 l:48 rid:100.100.100.20 aid:0.0.0.1
chk:a367 aut:0 auk:
int:fei-0/1/0/2 src:1.1.1.8 dest:AllSPFRouters
01:03:25: OSPF: Rcv v:2 t:1 l:48 rid:100.100.100.14 aid:0.0.0.0
4-45

chk:c3da aut:0 auk:

int:fei-0/1/0/1 src:100.100.100.14 dest:224.0.0.5
01:03:25: OSPF: Rcv hello from 100.100.100.14 area 0.0.0.0 on
intf 100.100.100.20
01:03:25: OSPF: End of hello processing
01:03:26: OSPF: 100.100.100.20 db aging timer activated
01:03:27: OSPF: 100.100.100.20 As external export timer activated
01:03:28: OSPF: send v:2 t:1 l:48 rid:100.100.100.20 aid:0.0.0.0
chk:c3da aut:0 auk:
int:fei-0/1/0/1 src:100.100.100.20 dest:AllSPFRouters
01:03:29: OSPF: Rcv v:2 t:1 l:48 rid:100.100.100.14 aid:0.0.0.1
chk:a367 aut:0 auk:
int:fei-0/1/0/2 src:1.1.1.1 dest:224.0.0.5
OSPF: send v:2 t:1 l:48 rid:100.100.100.20 Send a OSPFv2 Hello packet, the ttl is 1, the packet length (1) is 48
aid:0.0.0.1 chk:a367 aut:0 auk: bytes, and the router-ID is 100.100.100.20, the domain ID is 0.0.0.1,
the checksum (chk) is a367, and the authentication type (aut) is 0,
authentication key (auk) is null.
OSPF: Rcv hello from 100.100.100.14 area The interface 100.100.100.20 receives a Hello packet from IP address
0.0.0.0 on intf 100.100.100.20 100.100.100.14 in area 0.
OSPF: 100.100.100.20 db aging timer Aging timer of 100.100.100.20 is activated.

activated
4.4 OSPF Configuration Examples

4.4.1 OSPF Configuration Example One
As shown in Figure 4-12, R1 and R2 set up connection by two links, and advertise their
loopback address route respectively.
4-46

Figure 4-12 OSPF Configuration Example One
1. Configure IP addresses of the interconnected interfaces between R1 and R2, and
configure loopback interface IP address.
2. Add interfaces to OSPF area 0.
3. Configure load balancing on both R1 and R2. R1 and R2 can learn the loopback
address route advertised by the peer through two links.
R1(config)#interface gei-0/2/0/3
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-ospfv2)# network 11.22.1.0 0.0.0.255 area 0
R1(config-ospfv2)# maximum-paths 2
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
4-47

R2(config-ospfv2)# router-id 32.33.1.1

The following information will be shown after the configuration above is finished. It shows
that R1 and R2 set up neighborhood already.
R1 and R2 ping the loopback interface of the peer between each other, and the pings are
successful. It shows that the configuration is successful.
R1#show ip ospf neighbor
Neighbor ID Pri State DeadTime Address Interface

32.33.1.1 1 FULL/DR 00:00:40 11.22.1.2 gei-0/2/0/3
32.33.1.1 1 FULL/DR 00:00:37 11.22.10.2 gei-0/2/0/4
R1(config)#show ip forwarding route 1.1.1.22

IPv4 Routing Table:
1.1.1.22/32 11.22.1.2 gei-0/2/0/3 OSPF 110 2
1.1.1.22/32 11.22.10.2 gei-0/2/0/4 OSPF 110 2
Use the ping command to test the connectivity.

R1#ping 1.1.1.22
sending 5,100-byte ICMP echoes to 1.1.1.22,timeout is 2 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 1/1/2 ms.
4.4.2 OSPF Configuration Example Two

As shown in Figure 4-13, R1 does not need to learn the external route of backbone area,
while it needs to advertise itself external route. Here, establish NSSA area between R1
and R2, set up link between R2 and R3 in in backbone area.
4-48

Figure 4-13 OSPF Configuration Example Two
1. Set up link between R1 and R2 in NSSA area 255, and set up link between R2 and
R3 in area 0.
2. Redistribute direct-connected route on R3 and R1 respectively.
3. Configure NSSA default route advertisement on R2.
4. As a result, R1 cannot learn the detailed route of R3 address, but there is a default
route pointing to R2. R3 can learn the direct-connected route redistributed by R1.
R1(config-if)#exit
R1(config-if)#exit
R1(config-ospfv2)# area 255 nssa
R2(config-if)#exit
R2(config-if)#exit
R2(config-ospfv2)# area 255 nssa default-information-originate
4-49

R3(config-if)#exit
R3(config-if)#exit
Use the show ip forwarding route 1.1.1.33 command on R1 to view whether R1 learns the
detailed route of R3.
R1(config)# show ip forwarding route 1.1.1.33
IPv4 Routing Table:
Use the show ip forwarding route 0.0.0.0 command on R1 to view whether there is a default
route pointing to R2.
R1(config)# show ip forwarding route 0.0.0.0
IPv4 Routing Table:
0.0.0.0/0 11.22.1.2 gei-0/2/0/2 OSPF 110 2
Use the show ip forwarding route 1.1.1.11 command to inspect whether R3 learns the
detailed route of R1.
R3(config)#show ip forwarding route 1.1.1.11
IPv4 Routing Table:
1.1.1.11/32 33.32.1.1 gei-0/2/0/4 OSPF 110 2
Use the ping command on R2 to detect the connectivity from R3 to R1.

R3#ping 1.1.1.11
!!!!!
4.4.3 OSPF Multi-Instance Configuration Example

Users can configure multiple protocol instances. These protocol instances can belong
to the same VPN/public network or different Virtual Private Networks (VPNs). Different
protocol instances are independent of each other. They maintain the neighbor relationship,
LSDB of their own and calculate routes. However, the multiple instances belonging to the
4-50

same VPN/pbulic network share the same VPN/public network routing table. This is mainly
to divide and isolate networks.
In the following example, CE1 isolates the information flooded by PE1 and PE2. The
network topology is shown in Figure 4-14.
Figure 4-14 OSPF Multi-Instance Configuration Example
1. PE1 and CE1 establish OSPF neighbor relationship.
2. PE2 and CE1 establish OSPF neighbor relationship.
3. PE2 should not learn the link-state information related to vpn1.
Configuration on PE1:
PE1(config)#interface loopback1
PE1(config-if)#ip vrf forwarding vpn1
PE1(config-if)#ip address 1.1.1.17 255.255.255.255
PE1(config-if)#exit
PE1(config)#interface Int1
PE1(config-if)#exit
PE1(config)#router ospf 1 vrf vpn1
PE1(config-ospfv2)#network 1.1.1.17 0.0.0.0 area 0
PE1(config-ospfv2)#exit
Configuration on CE1:
CE1(config)#interface loopback1
CE1(config-if)#ip address 1.1.1.18 255.255.255.255
CE1(config-if)#exit
CE1(config)#interface loopback2
CE1(config-if)#exit
4-51

CE1(config)#interface Int2
CE1(config-if)#exit
CE1(config)#interface Int3
CE1(config-if)#exit
CE1(config)#router ospf 1
CE1(config-ospfv2)#network 1.1.1.18 0.0.0.0 area 0
CE1(config-ospfv2)#exit
CE1(config)#router ospf 2
CE1(config-ospfv2)#exit
Configuration on PE2:
PE2(config)#interface loopback1
PE2(config-if)#exit
PE2(config)#interface Int4
PE2(config-if)#exit
PE2(config)#router ospf 1 vrf vpn2
PE2(config-ospfv2)#exit
CE1 can learn the looback1 route advertised by PE1 and the loopback1 route advertised
by PE2. PE2 and PE1 cannot learn routes from each other. This indicates that the
multi-instance configuration takes effect.
CE1#show ip forwarding route ospf
IPv4 Routing Table:
1.1.1.17/32 100.101.102.17 int2 ospf 110 2
1.1.1.18/32 100.102.102.17 int3 ospf 110 2
PE2#show ip forwarding route vrf vpn2

IPv4 Routing Table:
2.2.2.18/32 100.102.102.18 int3 ospf 110 2
4-52

PE1#show ip forwarding route vrf vpn1

IPv4 Routing Table:
1.1.1.18/32 100.101.102.18 int1 ospf 110 2
4.4.4 OSPF Route Load Sharing Configuration Example

Load sharing makes the traffic that exceeds the bandwidth on a single interface be shared
on several links. In this way, traffic can be balanced on the links.
As shown in Figure 4-15, take OSPF as an example. In an area, there are several links
reaching the same destination. The costs of the links are the same. Enable load sharing
to realize OSPF load sharing.
Figure 4-15 OSPFv2 Route Load Sharing Configuration Example
1. Configure an interface and set the load sharing of per-packet mode (By default, it is
per-destination).
2. Enable and configure OSPF
3. Configure OSPF load sharing on R1
The configuration of R1:
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#ip load-sharing per-packet
R1(config-if)#ip load-sharing per-packet
4-53

The configuration of R2:

R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
Use the show command to check the configuration result, as shown below.
R1#show ip forwarding route ospf
IPv4 Routing Table:
1.1.1.200/32 101.2.1.200 gei-0/2/1/1 OSPF 110 2
1.1.1.200/32 102.2.1.200 gei-0/2/1/2 OSPF 110 2
4.5 OSPF Fault Handling

4.5.1 OSPF Basic Function Fault Handling
4.5.1.1 Network Topology
Take the topology shown in Figure 4-16 as an example to describe how to handle an OSPF
fault.
Figure 4-16 Network Topology of an OSPF Fault
4.5.1.2 Fault Analysis

Symptom:
R1 and R2 fail to set up neighborhood between each other.
Fault analysis:
4-54

l Inspect whether interfaces receive IP packets normally.

l Inspect whether add interfaces to OSPF area.
l Inspect whether authentication type is configured correctly.
l Inspect whether HELLO interval and Dead interval are configured consistently.
l Inspect whether the area added by interface is matched with the area of neighbor
interface.
l Since DD packet master/slave negotiation needs matched MTU values, inspect
whether the MTU values of two routers are consistent if any a router is in exstart
state. In addition, see if unicast route can be reachable.
l Use show ip ospf to inspect whether the process or area is disabled.
l Inspect whether the interface is disabled and whether it is configured to be a passive
interface.
l Inspect whether the Router-IDs of two routers are conflicted. For a broadcast network,
inspect whether the subnetwork masks are consistent.
4.5.1.3 Handling Flow

The flow to handle an OSPF fault is shown in Figure 4-17.
4-55

Figure 4-17 Flow to Handle an OSPF Fault
4-56

4.5.1.4 Handling Procedure

The procedure to handle an OSPF fault is described below.
1. Ping interface of the peer to inspect whether the packets receiving and sending are
normal.
2. Use the show ip ospf interface command to inspect whether add the interfaces to OSPF
area, whether the authentication type is correct and whether the Hello interval and
Dead interval are consistent. Use the show running-config ospf command to inspect
whether the interface is configured to be a passive interface.
3. Use the show ip ospf command to inspect whether the process or area is disabled,
whether the area types are matched and whether the Router-ID are conflicted.
4. Use the show interface command to inspect whether the MTU values of interfaces are
matched.
5. Use the show running-config-interface command to inspect whether the masks of
interfaces are consistent.
4.5.2 OSPF Multi-Instance Fault Handling

Take the topology shown in Figure 4-18 as an example to describe how to handle an OSPF
multi-instance fault.
Figure 4-18 Network Topology of an OSPF Multi-Instance Fault

Symptom:
R3 cannot learn the direct route advertised by R1.
Inspect whether neighbor relation is established between R2 and R1 and between R2
and R3. Inspect whether the interfaces on R2 connecting to R1 and R3 are in the same
instance. Inspect whether the direct route advertised by R1 and the interfaces establishing
neighbor relationship are in the same instance. Inspect whether the network type on the
interfaces are consistent. Inspect whether the area in which R1 and R2 establish neighbor
relationship is connected to the backbone area, or whether multiple non-backbone areas
are connected. Inspect whether the device retransmits, whether the interface cost is set
to 65535, and whether the max-metric router lsa command is configured on R2 or R3.

The flow to handle an OSPF multi-instance fault is shown in Figure 4-19.
4-57

Figure 4-19 Flow to Handle an OSPF Multi-Instance Fault

The procedure to handle an OSPF multi-instance is described below.
1. If neighbor relationship cannot be established, please refer to the handling of neighbor

relationship establishment fault.
2. Put the interfaces in the same network structure to the same instance.
4-58

3. Network type on interfaces should be consistent. It is not allowed that the type on one
interface is broadcast and the type on the other interface is point to pint.
4. Addresses should not be conflicted. Otherwise there will be route calculation error.
5. Interface cost should not be 65535. Otherwise the interface will not participate in route
calculation.
If the fault cannot be solved according to the above steps, please ask for technical support.
4.5.3 OSPF Route Load Sharing Fault Handling

The network topology of a route load sharing fault is shown in Figure 4-20. It is required
to accomplish load sharing between R1 and R2.
Figure 4-20 Network Topology of a Route Load Sharing Fault

The traffic is not shared on the links. Check whether load sharing is enabled and whether
there are multiple route entities to the same destination in the routing table.
If there are multiple route entities to the same destination and the ip load-sharing per-packet
command is not configured, the load sharing is in per-destination mode. Therefore, check
whether the traffic meets the condition of load sharing.
There are two modes of load sharing, per-destination and per-packet. In the per-packet
mode, as long as there are multiple next hops, the traffic can be shared. If there is a
hop on which the mode is per-destination, the load sharing mode is per-destination.
In per-destination mode, for a flow of which the attributes in the quintuple group are
completely the same, the traffic is forwarded only on one egress interface. For flows of
which the attributes in the quintuple group are not completely the same, the flows are
forwarded on different egress interfaces.
If there are not multiple route entities in the routing table, check whether the costs of the
links are the same. If there is still any problem, please ask for technical support.

The flow to handle a load sharing fault is shown in Figure 4-21.
4-59

Figure 4-21 Flow to Handle an OSPF Route Load Sharing Fault

The procedure to handle a load sharing fault is described below. Take the OSPF
configuration as an example.
1. Check whether there are multiple route entities that can share the traffic in the routing
table, as shown below.
ZXR10#show ip forwarding route ospf
IPv4 Routing Table:
1.1.1.200/32 101.2.1.200 gei-0/2/1/1 OSPF 110 2
1.1.1.200/32 102.2.1.200 gei-0/2/1/2 OSPF 110 2
2. Check whether load sharing is enabled, that is, whether the maximum-paths command
is configured.
ZXR10#show running-config ospf
4-60

router ospf 1
maximum-paths 2
network 101.2.1.0 0.0.0.255 area 0.0.0.0
network 102.2.1.0 0.0.0.255 area 0.0.0.0
!
3. Check whether the link costs are the same.
4. Check that the load sharing mode on the interface is per-destination or per-packet.
It is necessary to check the load sharing mode on each interface. As long as there
is one interface on which the load sharing mode is per-destination, the load sharing
mode is per-destination.
ZXR10#show running-config-interface gei-0/2/1/1
!
interface gei-0/2/1/1
index 2
ip address 101.2.1.100 255.255.255.0
ip load-sharing per-packet
!
5. If the load sharing mode is per-destination, check whether the attributes in the
quintuple group are regular.
4-61

4-62

Chapter 5
IS-IS Configuration
Table of Contents
IS-IS Overview ...........................................................................................................5-1
IS-IS Working Principle...............................................................................................5-3
IS-IS Configuration .....................................................................................................5-4
IS-IS Maintenance....................................................................................................5-16
IS-IS Configuration Examples...................................................................................5-23
IS-IS Fault Handling .................................................................................................5-37
5.1 IS-IS Overview

IS-IS is launched by International Standard Organization (ISO), which is a routing protocol
used for Connectionless Network Service (CLNS). IS-IS is a network layer protocol of Open
System Interconnection (OSI). By expanding IS-IS protocol, the support to IP routing is
added, and the integrated IS-IS protocol is formed.
5.1.1 IS-IS Area

In order to manage link-state database easily, the concept of area is used in IS-IS. A
network is divided into many area. Corresponding to the areas, IS-IS defines three kinds
of routers.
l Level-1 router (L1 router)
The L1 router is responsible for the intra-area routes. It respectively sets up
neighborhood with other L1 and Level-1–2 (L1/L2) routers in area, and maintains
a L1 LSDB. The LSDB contains the routing information of the area. The packets
sending to area outside are forwarded to the nearest L1/L2 router.
l Level–2 router (L2 router)

The L2 router is responsible for the inter-area routes. It respectively sets up
neighborhood with L2 and L1/L2 routers of other areas, and maintains a L2 LSDB.
The LSDB contains inter-area routing information. All L2 routers construct the
backbone network in routing area, which are responsible for the communication
among areas. L2 routers have to be continuous that makes sure that the continuity
of backbone network.
l L1/L2 router
The router belonging to L1 and L2 at the same time is called L1/L2 router. Every
area has a L1/L2 router at least, which connects the area to backbone network. A
5-1

L1/L2 router maintains two LSDBs, L1 LSDB is responsible for intra-area routes and
L2 LSDB is responsible for inter-area routes.
IS-IS area division and router types are shown in Figure 5-1.
Figure 5-1 IS-IS Area Division and Router Types
l L1 router
A L1 router exists in non-backbone area, and it only interacts routing information with
other L1 and L1/L2 routers in area.
l L2 router
A L2 router exists in backbone area, and it interacts routing information with other L2
and L1/L2 routers.
l L1/L2 router
A L1/L2 router exists in non-backbone area, and it interacts routing information
between its area and backbone area.
The routers of an area only maintain the link state database in their area. In this way, the
burden of routers themselves can be saved.
5.1.2 IS-IS Network Types

There are two network types in IS-IS, broadcast network and point-to-point network. IS-IS
is easily configured and to be realized.
The concept of NBMA does not applies to IS-IS. Therefore, some NBMA networks, such
as frame delay, ATM and X.25 and so on are considered to be point-to-point networks by
using sub-interface division.
5-2

Chapter 5 IS-IS Configuration
5.1.3 DIS and Router Priority

Similaring to OSPF protocol, IS-IS also uses designated router in broadcast network. In
IS-IS, the designated router is called Designated Intermediate System (DIS. The DIS
advertises network information to all routers on the broadcast network , and meanwhile
all other routers only advertise one adjacency pointing to DIS.
The parameters of router priority can be configured for performing DIS election, and L1
and L2 also can be independently configured with different priorities.
In DIS election, a router with the highest priority is elected to be the DIS. When the priorities
of all routers are the same, for a frame relay interface, a router with higher system ID is
elected to be the DIS; while for an Ethernet interface, a router with higher interface MAC
value is elected to be the DIS.
5.1.4 IS-IS Dynamic Host Name Mapping

In a network, IS-IS uses system ID to uniquely identify the router. In order to manage
network easily, host name (hostname) is used to replace system ID. In this way, the network
management is more visual and humanism.
5.1.5 IS-IS Mesh-Group

Mesh-Group is defined to decrease the redundancy diffusion of Link State Packets (LSP)
in a full-connected point-to-point link. Every interface has two new added attributes,
meshEnable and mesh group number. The mesh group number is used to identify whether
belong to the same Mesh-Group. The meshEnable has three states, meshInactive,
meshBlocked and meshSet. Protocol controls the packets according to these three states
of port.
l For a packet received from meshInactive port, it will be diffused to other ports, but
these ports cannot be in mesh-Blocked state.
l For a packet received from meshSet port, it will be diffused to meshIacvtive port and
the ports whose meshSet group IDs are different to the port.
l For a packet received from meshBlocked port, it will be diffused to all ports which are
in meshInactive and meshSet states. Meanwhile, add CSNP interval diffusion to the
ports which are in meshSet and meshBlocked states in point-to-point link
5.2 IS-IS Working Principle

IS-IS is already widely used in network acting as a kind of Interior Gateway Protocol (IGP).
The working principle of IS-IS is similar to that of OSPF. IS-IS divides a network into some
areas. The routers of an area only manage the routing information of their area. In this
way, the router cost is saved. IS-IS can satisfy the requirements for middle and large-scale
network.
5-3

Since the IS-IS protocol is based on CLNS (not IP), IS-IS uses Protocol Data Unit (PDU)
defined by ISO to implement communication between routers. The types of PDUs used in
IS-IS protocol are as follows:
l Hello PDU
l Link state PDU
l Sequence Number PDU (SNP)
Where, Hello PDU is similar to the HELLO packet in OSPF protocol, which is responsible
to form adjacency between routers, discovers new neighbors and detects the leaving of
any neighbors.
IS-IS routers uses LSA to exchange routing information, set up and maintain link state
database. A LSP indicates the important information related to a router, including the area
and the connected network. SNP is used to ensure that LSPs can be transmitted reliably.
SNP contains the summary information of every LSP on the network. When a router
receives a SNP, it compares the SNP with its link state database. If the router loses a
LSP existing in the SNP, it will send a SNP in multicast mode to ask for the required LSP
from other routers on the network.
By using LSPs in conjunction with SNPs, IS-IS protocol can interact routes reliably on a
large network.
Likewise, IS-IS protocol also uses the Dijkstra SPF algorithm to calculate routes. Based
on the link state database, it uses the SPF algorithm to calculate the optimal route and
then adds the route to IP routing table.
5.3 IS-IS Configuration

The IS-IS configuration described in this section is on the base of IP routing.
5.3.1 Enabling IS-IS

To enable IS-IS on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router isis < process-id> [ vrf < vrf-name> ] This enables IS-IS route protocol
and enters IS-IS route configuration
mode.
2 ZXR10(config-isis)#area < area-address> This configures IS-IS area in IS-IS

route mode and specifies the router
to belong to the area.
The area address to be configured
is a hex character string with 1–13
bytes.
5-4

3 ZXR10(config-isis)#system-id < system-id> [ range < This sets system ID of IS-IS. System
range-number> ] ID is used to identify a router in an
area. It is a hex character string with
6 bytes. Usually, it is a MAC address
of an interface on the router.
4 ZXR10(config-isis)#interface < interface-name> This enters interface configuration

mode.
ZXR10(config-isis-if)#ip router isis This specifies an interface to run

IS-IS.
5.3.2 Configuring IS-IS Global Parameters

For a network running with all ZXR10 series routers or switches, use the default parameters
in IS-IS configuration. For connecting with devices of other manufactories, the related
interface parameters and timers are required to adjust to acquire higher running efficiency.
To configure IS-IS global parameters on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router isis < process-id> [ vrf < vrf-name> ] This enables IS-IS and enters IS-IS
route configuration mode.
2 ZXR10(config-isis)#is-type { level-1 | level-1-2 | level-2-only} This configures the level of the

router.
The level includes level-1, level-1–2
and level-2–only.
Level-1–2 is the default setting.
3 ZXR10(config-isis)#metric-style { narrow | wide } This configures metric-style.

The default setting is narrow mode.
4 ZXR10(config-isis)#lsp-refresh-time < refresh-time > This configures the time interval

for refreshing local LSP. The unit is
second, the range is 1-65535.
In a stable network, the local is is
refreshed regularly.
The default refreshing interval is 900
seconds.
5-5

5 ZXR10(config-isis)#max-lsp-lifetime < time > This configures the maximum life

time of local LSP, that is, the life time
is that the local LSP packets can live
in the databases of all accessible
nodes. The unit is second, the range
is 1-65535.
By default, the maximum life time of
LSP is 1200 seconds.
6 ZXR10(config-isis)#distance < value > This sets the priority of IS-IS protocol
on local and compares it to those of
other protocols.
The range is 1-255, and the default
value is 115.
7 ZXR10(config-isis)#passive-interface { default | < interface-name> } This configures the passive interface.

When an interface is configured to
be a passive interface, its address
information will be added to the
local LSP, but the passive interface
does not participate in the packet
forwarding.
Use the parameter default to
configure all local interfaces to be
passive interfaces. Without default,
the command configures a specified
interface to be passive interface.
8 ZXR10(config-isis)#set-overload-bit [ on-start-up { < 5-86400> | This configures the IS-IS OL bit.

auto| wait-for-bgp} ] [ suppress { all | external | interlevel} ] This bit is used to inform other IS-IS
routers that the topology and routing
information cannot be transmitted
by this router when the router
processing capability is not enough.
9 ZXR10(config-isis)#default-information originate [ always] [ This generates the default route.

metric < metric-value> ] [ metric-type < type> ] [ level-1 | level-1-2 | In route redistribution configuration,
level-2] use this command to make router
redistribute the default route to IS-IS
area.
5-6

10 ZXR10(config-isis)#summary-address < ip-address> < net-mask> [ This configures route summary.

metric < metric-value> ] [ level-1 | level-1-2 | level-2] IS-IS generates an aggregated route
by summarizing some route entries.
It advertises the aggregated route
rather than advertises the detailed
route entries.
11 ZXR10(config-isis)#hello padding { multi-point | point-to-point } This configures hello packet padding

to the maximum length including
broadcast network and point-to-point
padding modes.
12 ZXR10(config-isis-if)#network point-to-point This configures a broadcast link

interface on which IS-IS is enabled
to simulate a point-to-point interface.
Description of the parameters in Step 2:
< narrow | wide > In narrow mode, there are 6 bits to carry metric value. In wide mode,
there are 24 bits to carry metric value, and it supports to bring more
TLV extensions.
When devices are connected and neighborhood is set up, the types
of metric-style are different that causes the topology establishment
is failed.
on-start-up { 5-86400 | auto | wait-for-bgp } l 5-86400: It is a range for selection. After restarting, the OL bit can
be set in some seconds (5–86400). After some seconds, the OL
bit cannot not set.
l auto: The OL bit cannot be set after the databases are
synchronized.
l wait-for-bgp: The OL bit cannot be set after BGP is synchronized.
suppress { all | external | interlevel} l all: Suppress the redistribution and route leakage between
level–1 and level–2
l external: Suppress the local learning of redistributed routes
l interlevel: Suppress the leakage between routes.
5-7

always No matter whether there is a default route exists in redistributed route

entries, system always generates a default route advertisement entry.
Without this parameter, system only advertises default route when the
redistributed route entries have a default route.
metric < metric-value> metric value, range is 0-4261412864
metric-type < type> metric type, valuing external or internal. By default, it is internal.
level-1 The default route is generated on level-1
level-1-2 The default route is generated on both level-1 and level-2.
level-2 The default route is generated on level-2 (default setting).
< ip-address> The allocated summary address, in dotted decimal notation
< net-mask> IP subnetwork mask, it is used to summary route, in dotted decimal

notation
metric < metric-value> Metric value, range is 0-4261412864
level-1 Router locates at level-1
level-1-2 Router locates at level-1–2
5.3.3 Configuring IS-IS Interface Parameters

To configure IS-IS interface parameters on ZXR10 M6000, perform the following steps.
configuration mode.
2 ZXR10(config-isis)#interface < interface-name> This enters IS-IS interface

configuration mode.
5-8

3 ZXR10 (config-isis-if)#circuit-type { level-1| level-1-2| This configures interface operation

level-2-only} type. It is a basic parameter
configuration.
The default setting is level-1–2.
The configuration must match
with IS-IS global operation type.
The peers of direct-connected
neighborhood also require the
matched entries.
ZXR10 (config-isis-if)#hello-interval < interval> [ level-1 | level-2] This configures the time interval for
sending HELLO packets. The unit is
second, the range is 1–65535, and
the default setting is 10 seconds.
The time interval is 3 seconds after
DIS is elected on broadcast link. It
cannot be modified.
When the command is used without
optional parameters, the interval
configuration is effective to both
level-1 and level-2.
ZXR10 (config-isis-if)#hello-multiplier < multiplier> [ level-1 | This configures the time for keeping
level-2] neighborhood.
This time has to be the multiplier of
the time interval for sending HELLO
packets, in range of 3-1000, 3 by
default.
optional parameters, the multiplier
ZXR10 (config-isis-if)#lsp-interval < interval> [ level-1 | level-2] This configures the time interval
for transmitting LSPs. The unit is
second, the range is 1–65535, and
the default setting is 2 seconds.
ZXR10 (config-isis-if)#retransmit-interval < interval> [ level-1 | This configures the time interval
level-2] for retransmitting LSPs. The unit
is second, the range is 1-65535, 5
seconds by default.
5-9

The configuration only applies to

point to point link.
When the command is used
without optional parameters, the
retransmit-interval configuration is
effective to both level-1 and level-2.
ZXR10 (config-isis-if)#priority < priority> [ level-1 | level-2] This configures DIS election priority
on an interface, in range of 0-127,
64 by default. The router with higher
priority is elected to be the DIS.
The configuration only takes effect
on broadcast links.
optional parameters, the priority
ZXR10 (config-isis-if)#metric < metric-value> [ level-1 | level-2] This sets the metric value of an
IS-IS interface. The default value
is 10. In wide mode, the range is
0-16777214. In narrow mode, the
range is 0–63.
metric-value configuration is effective
to both level-1 and level-2.
ZXR10 (config-isis-if)#csnp-interval < interval> [ level-1 | level-2] This defines the interval for sending
CSNP packets. The unit is second,
the range is 1-65535. For broadcast
link, the default setting is 10
seconds. For point-to-point network,
the default value is 3600 seconds.
ZXR10 (config-isis-if)#psnp-interval < interval> [ level-1 | level-2] This configures the time interval for
sending PSNP packets on interface.
The unit is second, and the range is
1–65535, and the default setting is
3 seconds.
5-10


5.3.4 Configuring IS-IS Authentication

ZXR10 M6000 supports four IS-IS authentication types:
l Inter-neighbor authentication
l Intra-area authentication
l Inter-area authentication
l Inter-SNP authentication
At present, ZXR10 M6000 supports plain text and MD5 authentication modes.
To configure IS-IS authentication on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#authentication-type < type> [ level-1 | level-2] This configures authentication mode,

text or md5.
authentication mode is effective to
both level-1 and level-2.
ZXR10(config-isis)#authentication { < password> | [ encrypt< This configures IS-IS authentication

password> ] } [ level-1 | level-2] password in route mode. The length
of password is 1–180 characters.
By default, authenticate SNP and
LSP packets in route mode. To
authenticate LSP packets only, use
disable-snp-authentication command.
the SNP packets of both level-1 and
level-2.
3 ZXR10(config-isis)#interface < interface-name> This enters IS-IS interface

configuration mode.
5-11

4 ZXR10(config-isis-if)#authentication-type < type> [ level-1 | This configures authentication mode

level-2] in interface mode,
both level-1 and level-2.
ZXR10(config-isis-if)#authentication { < password> | [ encrypt< This configures to authenticate

password> ] } [ level-1 | level-2] HELLO packets. The password
ranges from 1 to 180 characters.
HELLO packets of both level-1 and
level-2.
6 ZXR10(config-isis)#enable-snp-authentication After LSP authentication is

configured, the same authentication
code is configured for authenticating
SNP packets. By default,
authenticate SNP packets at
the same time.
ZXR10(config-isis)#disable-snp-authentication This disables the authentication of

SNP packets.
5.3.5 Configuring IS-IS Hostname

To configure IS-IS hostname on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#hostname dynamic This sets the IS-IS function to

obtain hostname dynamically. It
dynamically acquires system name.
By default, this function is enabled.
ZXR10(config-isis)#no hostname dynamic This cancels IS-IS system name

dynamic acquiring function.
5-12

5.3.6 Configuring IS-IS Mesh-Group

To configure IS-IS mesh-group on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#interface < interface name> This enters interface configuration

mode.
3 ZXR10(config-isis-if)#mesh-group blocked This sets the mesh-group attribute

to meshBlocked, that is, the LSP
packets will be blocked on the
interface.
4 ZXR10(config-isis-if)#mesh-group < mesh_group_number> This configures the interface to

belong to which mesh-group.
The range of mesh-group is
1–4294967295.
5.3.7 Configuring IS-IS Redistribution

To configure IS-IS redistribution on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#redistribute < protocol> [ level-1 ] [ level-1-2 ] This configures route redistribution

[ level-2 ] [ metric-type < metric-type> ] [ metric < metric-value> ] [ in IS-IS route mode.
route-map < map-tag> ]
Descriptions of the parameters used by step 2 are shown below.
< protocol> Protocol source. It can be connect, static, rip, isis <process-id>, ospf
<process-id> and bgp. It is mandatory. To redistribute isis/ospf routes,
it is necessary to specify the process-id.
level-1 Sets the redistributed routes to enter Level-1
level-1-2 Sets the redistributed routes to enter Level-1 and Level-2
level-2 Sets the redistributed routes to enter Level-2
< metric-type> The redistributed route brings external or internal metric values.
< metric-value> Metric value, range is 0–4261412864
route-map < map-name> Use a route-map
5-13

5.3.8 Configuring Traffic Engineering

ZXR10 M6000 IS-IS IPv4 supports public network Traffic Engineering (TE) function.
To configure IS-IS traffic engineering on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#metric-style wide This configures a wide metric in

IS-IS route mode.
3 ZXR10(config-isis)#mpls traffic-eng level-1 This enables TE on IS-IS Level-1.
4 ZXR10(config-isis)#mpls traffic-eng level-2 This enable TE on IS-IS Level-2.
5 ZXR10(config-isis)#mpls traffic-eng router-id < interface-name> This selects an interface to configure

router id to enable IS-IS protocol
local device.
5.3.9 Configuring IS-IS FRR

IS-IS FRR function is mainly used to calculate backup topology. When main link is invalid,
traffic can be forwarded to backup route immediately to avoid data loss.
To configure IS-IS FRR on ZXR10 M6000, perform the following steps.
2 ZXR10(config-isis)#fast-reroute enable At IS-IS routing mode, configure

wide metric.
3 ZXR10(config-isis)#fast-reroute alternate-type down-stream-path This configures IS-IS

FRR calculation mode as
down-stream-path. The default
is LFAS.
4 ZXR10(config-isis)#interface < interface-name> This enters route configuration

mode.
5 ZXR10(config-isis-if)#fast-reroute block This configures this interface does

not join IS-IS FRR calculation and is
not used to form backup link.
5-14

5.3.10 Configuring IS-IS Route Load Sharing

IS-IS supports load sharing. Load sharing indicates that many links with the same cost
and destination can share traffic. Load sharing is divided into two kinds, packet-based
and flow-based. The default kind is flow-based.
To configure IS-IS route load sharing on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router isis [ < process-id> ] [ vrf < vrf-name> ] This enters IS-IS route configuration
mode.
2 ZXR10(config-isis)#maximum-paths < number> This configures the count of routes


mode.


value.
5.3.11 Configuring IS-IS FRR

To configure IS-IS FRR on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router isis [ vrf < vrf-name> ] This enters IS-IS configuration

mode.
2 ZXR10(config-isis)#fast-reroute enable This enables IS-IS FRR function.
5-15

3 ZXR10(config-isis)#fast-reroute alternate-protect-type This changes the IS-IS FRR

down-stream-path calculation mode from the
default mode (LFAs mode) to
down-stream-path mode.
Use the no fast-reroute
alternate-protect-type command
to restore the default LFAs mode.
4 ZXR10(config-isis)#interface < interface-name> This enters protocol interface

configuration mode.
5 ZXR10(config-isis-if)#metric < value> This configures the cost of the

interface. During FRR calculation,
the route of which the cost value is
greater becomes the backup route.
6 ZXR10(config-isis-if)#fast-reroute block This forbids this interface to be on

the backup path during backup path
calculation.
5.4 IS-IS Maintenance

ZXR10 M6000 provides the following commands to view IS-IS information.
Command Function
ZXR10#show isis adjacency [ up-time] [ level-1 | level-2] [ process-id] This shows the adjacency and displays
the current neighbor status.
ZXR10#show isis circuits [ detail] [ process-id] This displays the information of the
current IS-IS interface.
ZXR10#show isis database [ LSP-ID] [ level-1| level-2] [ verbose] [ detail] This shows the information of IS-IS
[ process-id] neighbor.
ZXR10#show isis topology [ level-1| level-2] [ process-id] [ vrf < vrf-name> ] This shows the numbers of each LSA in
every area and the total number of LSA
in the whole database.
ZXR10#show isis mpls traffic-eng tunnel [ process-id] This shows the use of IS-IS tunnel.
ZXR10#show isis fast-reroute-topology [ level-1| level-2] [ process-id] This views the current IS-IS backup
topology structure.
5-16

level-2 Routers locates at level-2
up_time The up time of neighbor
process-id Instance number, in the range of 0-65535
detail Show the information in detail
An example of the show isis adjacency command output is shown below.

ZXR10(config-isis)#show isis adjacency
Process ID: 0
Interface System id State Lev Holds SNPA(802.2) Pri MT
fei-0/1/0/1 3333.3333.3333 UP L1 23 00E0.D021.0205 64
fei-0/1/0/2 3333.3333.3333 UP L2 24 00E0.D021.0203 64
Process ID Instance number
Interface The name of local interface which sets up neighborhood with the peer
System id System ID of neighbor, represented as xxxx.xxxx.xxxx
State Neighborhood status, there are two status, UP and INIT
Lev The level at where neighborhood locates. There are three levels,
L1, L2 and L3.
Holds The keeping time of neighborhood
SNPA(802.2) The accessing point of subnetwork
Pri Priority for router election
MT Multiple topology identifier
An example of the show isis circuits command output is shown below.

ZXR10(config-router)#show isis circuits
Process ID: 0
Interface State Lev CirId Level1-DR Level2-DR Pri(L1/L2)
fei-0/1/0/1 Up L1 2 No found Disabled 64/64
Interface IS-IS port name
State IS-IS protocol is enabled on interface, and it is in UP state.
5-17

Lev Interface level
CirId Interface ID
Level1-DR The DR of level 1
Level2-DR The DR of level 2
Pri(L1/L2) L1/L2 priority
An example of the show isis database command output is shown below.

ZXR10(config-router)#show isis database detail
Process ID: 0
LSPID LSP Seq LSP LSP ATT/P/OL
Num Checksum Holdtime
2222.2222.2222-00-00* 0xd 0xa25e 896 0/0/0
NLPID 0xcc
Area Address 11
Area Address 22
Ip address 1.1.1.2
Hostname
Metric: 10 IS neighbor 2222.2222.2222-02
Metric: 10 IP-Internal 1.0.0.0 255.0.0.0

2222.2222.2222-02-00* 0x2 0x91f4 895 0/0/0
Hostname

3333.3333.3333-00-00 0xa 0x45ba 867 0/0/0
NLPID 0xcc
Area Address 11
Area Address 22
Ip address 2.2.2.3
Hostname
IS-IS Level-2 Link State Database:
5-18


2222.2222.2222-00-00* 0x7 0x6408 986 0/0/0
NLPID 0xcc
Area Address 11
Area Address 22
Ip address 1.1.1.2
Hostname

2222.2222.2222-03-00* 0x1 0x8cf9 964 0/0/0
Hostname

3333.3333.3333-00-00 0x6 0x6d95 955 0/0/0
NLPID 0xcc
Area Address 11
Area Address 22
Ip address 2.2.2.3
Hostname
LSPID Link state packet ID
LSP Seq Num Link state packet sequence number
LSP Checksum Link state packet checksum
LSP Holdtime LSP life time
ATT/P/OL Whether to connect to external area bit /partition bit /over load bit
An example of the show isis topology command output is shown below.

ZXR10(config-isis)#show isis topology
Process ID: 0
5-19

IS-IS paths to Level-1 routers

System id Metric Next-Hop Interface SNPA
2222.2222.2222 10 2222.2222.2222 fei-0/1/0/1 00E0.D021.0204
3333.3333.3333 --
2222.2222.2222 10 2222.2222.2222 fei-0/1/0/2 00E0.D021.0205
3333.3333.3333 --
System id System ID of destination IS
Metric Metric value to destination IS, “--” marks itself, “**” means that the
route cannot be calculated.
Next-Hop The next hop IS to the destination IS
Interface Interface for forwarding route
SNPA “*ppp*” SNPA address of the next hop, P-P port identifier
An example of the show isis mpls traffic-eng tunnel command output is shown below.
ZXR10(config-router)#show isis mpls traffic-eng tunnel
Process ID: 0
state codes: * the only next hop, ** one of next hops,
-not chosen as next hop
System id Tunnel-name Next-hop Metric Mode State

2222.2222.1111 te_tunnel1 1.1.2.110 10 Absolute **
System Id System ID of the destination IS
Tunnel-name Tunnel name
Next-Hop The next hop IS to the destination IS
Metric The metric to the destination IS
Mode Metric mode of an automatic tunnel
State Use state of an automatic tunnel in espf calculation
An example of the show isis fast-reroute-topology command output is shown below.

ZXR10(config)#show isis fast-reroute-topology
5-20

Process ID: 0
IS-IS ipfrr paths to Level-1 routers
System id Interface Ipfrr interface Ipfrr type metric
1111.1111.1111 fei-0/1/0/2 fei-0/1/0/1 Link 10
1111.1111.1111 fei-0/1/0/2 fei-0/1/0/1 Link 10
System id System ID of destination IS
Interface Master outgoing interface to destination IS
Ipfrr interface Backup outgoing interface to destination IS
Ipfrr type IS-IS FRR calculation mode including LFA and down-stream-path
metric Metric to destination IS
5.4.2 Common Maintenance Commands for Debugging

ZXR10 M6000 provides the following commands to debug IS-IS.
Command Function
ZXR10#debug isis all [ process-id] This enables all IS-IS debugging

functions.
ZXR10#debug isis adj-packets[ process-id] This traces and shows the received and
sent HELLO packets.
ZXR10#debug isis snp-packets[ process-id] This traces and shows the SNP packet
and the related events which are
received and sent by IS-IS.
ZXR10#debug isis spf-events[ process-id] This traces and shows the debugging
information of IS-IS routing calculation
events.
ZXR10#debug isis update-packets[ process-id] This traces and shows the debugging
information of IS-IS LSP packet
processing events.
ZXR10#debug isis nsf-event[ process-id] This traces and shows the information
related to IS-IS GR.
5-21

Command Function
ZXR10#debug isis mpls traffic-eng events[ process-id] This traces and shows the debugging
information of IS-IS cspf route
calculation events.
An example of the debug isis all command output is shown below.

ZXR10#terminal monitor
ZXR10#debug isis all
All IS-IS debugging has been turned on
ZXR10#
00:58:26: ISIS-Adj: Recv LAN_IIH(1) from 2222.2222.2222(fei-0/1/0/1)
00:58:26: cir type L1L2, lan id 2222.2222.2222-03, length 48
00:58:28: ISIS-Adj: Sending LAN_IIH(1) on fei-0/1/0/2 length 50
00:58:28: ISIS-Adj: Sending LAN_IIH(1) on fei-0/1/0/1 length 50
00:58:29: ISIS-Snp: Rec L1 CSNP from 2222.2222.2222 (fei-0/1/0/2)
00:58:29: ISIS-Snp: CSNP range 0000.0000.0000-00 to FFFF.FFFF.FFFF-FF
00:58:29: ISIS-Snp: Same entry 2222.2222.2222-00-00, seq c
00:58:29: ISIS-Snp: Same entry 2222.2222.2222-02-00, seq 4
ISIS-Adj: Recv LAN_IIH(1) from IS-IS neighbor information: Receive LAN_IIH (1) packet from interface
2222.2222.2222(fei-0/1/0/1) fei-0/1/0/1 on router 2222.2222.2222
ISIS-Adj: Sending LAN_IIH(1) on IS-IS neighbor information: Send LAN_IIH(1) packet on interface
fei-0/1/0/2 length 50 fei-0/1/0/2. The packet length is 50 bytes.
cir type L1L2, lan id 2222.2222.2222-02, Interface information

length 48
ISIS-Snp: Rec L1 CSNP from SNP information: Receive L1 CSNP packet from interface fei-0/1/0/2
2222.2222.2222 (fei-0/1/0/2) on router 2222.2222.2222
5-22

5.5 IS-IS Configuration Examples

5.5.1 Single Area IS-IS Configuration Example
It is required that analyze the network before starting IS-IS configuration. According to
network size, decide the network topology that how many areas to be divided and how
many routing protocol to be ran on network. Configure IS-IS on a single area if the network
scale is not much larger.
As shown in Figure 5-2, configure IS-IS on a single area.
Figure 5-2 Single Area IS-IS Configuration Example
1. Configure IP addresses of interfaces
2. Configure IS-IS protocol
3. Enable IS-IS protocol on interface
4. Test the configuration result. Make sure that R1 and R2 can set up neighborhood
between each other and calculate topology correctly. Make sure that R1 and R2 can
ping the loopback interface of the peer between each other.
R1(config-if)#exit
R1(config-if)#exit
5-23


R1(config-isis)#interface loopback1
R2(config-if)#exit
R2(config-if)#exit
R2(config-isis)#interface loopback1
After finishing the configuration above, the following content can be viewed on both R1
and R2. It means that R1 and R2 can set up neighborhood and calculate topology. Ping
the loopback address of the peer on R1 and R2 respectively.
Use the show running-config isis command on R1 to view whether the IS-IS configuration
is correct.
R1(config-isis)#show running-config isis
!
router isis
area 01
system-id 00D0.D0C7.5460
ip router isis
$
interface loopback1
ip router isis
$
Use the show isis adjacency command on R1 to view whether the neighborhood is normal.
After the neighborhood is set up, UP will be shown under the field of state.
R1(config-isis)#show isis adjacency
fei-0/1/0/1 00D0.D0C7.53E0 UP/UP L1L2 8/7 0030.3144.5566 64/64
5-24

Use the show isis topology command on R1 to view whether the topology can be calculated
correctly. If the topology is calculated correctly, the following entry can be viewed on the
command output. If “– ” is shown under the field of metric, it means the local router. If “**”
is shown under the field of metric, it means inaccessible.
R1(config-isis)#show isis topology
00D0.D0C7.53E0 10 00D0.D0C7.53E0 fei-0/1/0/1 0030.3144.5566
00D0.D0C7.5460 --

00D0.D0C7.53E0 10 00D0.D0C7.53E0 fei-0/1/0/1 0030.3144.5566
00D0.D0C7.5460 --
Use the show isis circuits command on R1 to view the interface information and the DIS
election. The UP means that the interface state is normal. The Down means that the
interface state is abnormal. For abnormal interface state, it is required that inspect the link
state and IP configuration.
R1(config-isis)#show isis circuits

IS-IS interface database:
loopback1 Up L1L2 0 No found No found 64/64
fei-0/1/0/1 Up L1L2 2 00D0.D0C7.53E0-02 00D0.D0C7.53E0-02 64/64
R1#ping 192.168.6.1
!!!!!
Check the configuration on R2.

R2(config)#show running-config isis
!
router isis
area 01
system-id 00D0.D0C7.53E0
ip router isis
$
interface loopback1
ip router isis
$
!
R2(config)#show isis circuits
5-25


loopback1 Up L1L2 0 No found No found 64/64
fei-0/1/0/1 Up L1L2 2 Dis is me Dis is me 64/64
zxr10(config)#show isis adjacency
Interface System id State Lev Holds SNPA(802.2)Pri MT
fei-0/1/0/1 00D0.D0C7.5460 UP/UP L1L2 23/23 0030.3144.5560 64/64
zxr10(config)#show isis top
00D0.D0C7.53E0 --
00D0.D0C7.5460 10 00D0.D0C7.5460 fei-0/1/0/1 0030.3144.5560

00D0.D0C7.53E0 --
00D0.D0C7.5460 10 00D0.D0C7.5460 fei-0/1/0/1 0030.3144.5560
R2#ping 192.168.3.1
!!!!!
5.5.2 Multi-Area IS-IS Configuration Example

For a larger size network, use multiple IS-IS areas. According to the geographic locations
and the functions of routers, partition the close routers to an area. Area division helps
to lighten the demands for memory. The area only need to maintain a smaller link state
database. A router only needs to maintain a smaller link state database in its area.
As shown in Figure 5-3, R1 belongs to area 1, R2 belongs to area 0, and R3 and R4 belong
to area 2. R1 aggregates the routes of the network segment in area 1, and R4 redistributes
the default route to IS-IS.
Figure 5-3 Multi-Area IS-IS Configuration Example
5-26

1. Configure IP addresses of interfaces.
2. Configure IS-IS protocol.
3. Enable IS-IS protocol on interfaces.
4. Enable route aggregation on R1.
5. Configure static route on R4 and redistribute default route.
6. Test the configuration. Make sure that the neighborhood is set up between R1 and R2,
between R2 and R3, and between R3 and R4 already and the topology is calculated
correctly. Ping the peer interface by one of any pair of interfaces successfully.
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-isis)#is-type level-1-2
R1(config-isis-if)#circuit-type level-2
5-27

R1(config-isis)#summary-address 192.168.100.0 255.255.252.0
R2(config-if)#exit
R2(config-if)#exit
R3(config-if)#exit
R3(config-if)#exit
R3(config-isis)#system-id EF00.AB00.DF12
R3(config-isis)#is-type level-1-2
R4(config-if)#exit
5-28

R4(config-isis)#system-id 00DE.FD11.AD00
R4(config-isis-if)# circuit-type level-1
R4(config-isis)#exit
R4(config)#ip route 0.0.0.0 0.0.0.0 192.168.13.1
R4(config-isis)#default-information originate
R4(config-isis)#redistribute static metric 10
R4(config-isis)#end
After the configuration above is finished, the following content can be viewed on one of
any pair of devices. It shows that the neighborhood is set up already and the topology is
calculated correctly. The peer interface can be pinged successfully by one end of any pair
of devices.
Use the show ip protocol routing command to view the default static route redistributed by
R4 on R1.
!
router isis
area 01
system-id 00D0.D0C7.5460
is-type level-1-2
summary-address 192.168.100.0 255.255.252.0
ip router isis
circuit-type level-2-only
$
ip router isis
$
ip router isis
$
ip router isis
5-29

$
!
R1(config)#show isis adjacency
fei-0/1/0/3 00D0.D0C7.53E0 UP L2 7 0030.3144.5566 64
R1(config)#show isis topology
00D0.D0C7.5460 --

00D0.D0C7.53E0 10 00D0.D0C7.53E0 fei-0/1/0/3 0030.3144.5566
00D0.D0C7.5460 --
Router 30 00D0.D0C7.53E0 fei-0/1/0/3 0030.3144.5566
Router 20 00D0.D0C7.53E0 fei-0/1/0/3 0030.3144.5566

Protocol routes:

*> 0.0.0.0/0 192.168.15.2 115 30 isis-l2
* 0.0.0.0/0 0.0.0.0 254 8 special
View the configuration on R2, as shown below.

!
router isis
area 00
system-id 00D0.D0C7.53E0
is-type level-2-only
ip router isis
$
ip router isis
$
!
5-30


00D0.D0C7.53E0 --
00D0.D0C7.5460 10 00D0.D0C7.5460 fei-0/1/0/3 0030.3144.5560
Router 20 Router fei-0/1/0/1 CA00.1016.0008
Router 10 Router fei-0/1/0/1 CA00.1016.0008

fei-0/1/0/3 Up L2 3 Disabled Dis is me 64/64
fei-0/1/0/1 Up L2 2 Disabled Router.01 64/64
Protocol routes:

*> 0.0.0.0/0 192.168.14.2 115 20 isis-l2
* 0.0.0.0/0 0.0.0.0 254 8 special
*> 192.168.100.0/22 192.168.15.1 115 10 isis-l2
View R3 configuration,
!
router isis
area 02
system-id EF00.AB00.DF12
is-type LEVEL-1-2
ip router isis
$
ip router isis
circuit-type level-1
$
!
IS-IS paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
Router --

00D0.D0C7.53E0 10 00D0.D0C7.53E0 fei-0/1/0/1 0030.3144.5566
5-31

00D0.D0C7.5460 20 00D0.D0C7.53E0 fei-0/1/0/1 0030.3144.5566

Router 10 Router fei-0/1/0/3 ca01.1016.001c
Router --
System Id Type Interface IP Address State Holdtime Circuit Id

00D0.D0C7.53E0 L2 fei-0/1/0/1 192.168.14.1 UP 27 Router.01
Router L2 fei-0/1/0/3 192.168.13.2 UP 7 Router.01
Protocol routes:

*> 0.0.0.0/0 192.168.13.2 115 20 isis-l2
* 0.0.0.0/0 0.0.0.0 254 8 special
*> 192.168.100.0/22 192.168.14.1 115 10 isis-l2
View R4 configuration,
R4(config)#show running-config
!
router isis
area 02
system-id 00de.fb11.ad00
is-type LEVEL-1
redistribute static ip metric 10
default-information originate
ip router isis
circuit-type level-1
!
ip route 0.0.0.0 0.0.0.0 192.168.13.1
Router --

00D0.D0C7.53E0 20 Router fei-0/1/0/3 ca00.1016.001c
00D0.D0C7.5460 30 Router fei-0/1/0/3 ca00.1016.001c
Router --
Router 10 Router fei-0/1/0/3 ca00.1016.001c
R4(config)#show isis neighbors
System Id Type Interface IP Address State Holdtime Circuit Id
Router L2 fei-0/1/0/3 192.168.13.1 UP 29 Router.01
5-32

R4#ping 192.168.100.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max =
192/709/1148 ms
5.5.3 IS-IS Multi-Instance Configuration Example

It is required to configure two instances on R1, and then add gei-0/1/0/1 and gei-0/1/0/2 to
the instances. Meanwhile, configure two instances on R2, and then add two interfaces to
Instance 1 and Instance 2 respectively. The network topology is shown in Figure 5-4.
Figure 5-4 IS-IS Multi-Instance Configuration Example
1. Establish neighbor relationship on fei-0/1/0/1 of R1 and fei-0/1/0/1 of R2 in Instance
100.
2. Establish neighbor relationship on fei-0/1/0/2 of R1 and fei-0/1/0/2 of R2 in Instance
200.
3. Redistribute direct-connected routes in the instances of R1. Check whether load
sharing is performed through different instances on R2. (Load sharing cannot be
performed, as the route with a smaller instance number of the same prefix has a
higher priority.)
R1(config)#router isis 100

R1(config-isis)#system-id 1111.0100.0000
R1(config-isis)#redistribute connected
5-33

R1(config-isis)#redistribute connected
R1#show isis adjacency
Process ID: 100
fei-0/1/0/1 R2 UP/UP L1L2 26/26 0021.8844.5541 64/64
Process ID: 200
fei-0/1/0/2 R2 UP/UP L1L2 25/25 0021.8844.5541 64/64
The result shows that the traffic goes through gei-0/1/0/1, that is, the route with a smaller
instance number is preferred.
R2#show ip forwarding route isis-l2
IPv4 Routing Table:
1.1.1.12/32 56.3.3.2 fei-0/1/0/1 isis_l2 115 10
88.6.5.5/32 56.3.3.2 fei-0/1/0/1 isis_l2 115 10
5-34

5.5.4 IS-IS FRR Configuration Example

FRR is to provide backup protection for important nodes and links when the nodes or links
become invalid in the network. It realizes fast re-routing, thus decreases the influence to
the traffic caused by the invalid nodes or links to make the traffic recovered quickly.
There are two typical network structures of FRR, as shown below.
1. The typical network structure of node protection is shown in Figure 5-5.
Figure 5-5 Network Structure of FRR Node Protection
2. The typical network structure of link protection is shown in Figure 5-6. IS-IS neighbor
topology is established on the two links. One of the link has high priority and the other
link has lower priority.
Figure 5-6 Network Structure of FRR Link Protection
1. Configure routing protocols.
2. On the nodes forming FRR relationship, there are more than two next hops reachable
to the same destination, and the routes to the same destination have different costs.
3. Enable FRR function in related routing protocol on corresponding devices.
The detailed configuration is described below.
1. For the FRR configuration of node protection type, please refer to the “BGP FRR
Configuration Example” topic.
2. Configuration of FRR link protection
Take IS-IS protocol in Figure 5-6 as an example.
Configuration of R1:
5-35

R1(config-isis)#fast-reroute enable
R1(config-isis)#interface gei-0/2/1/1
R1(config-isis-if)#metric 20
Use the show ip forwarding backup route command to check whether the FRR
configuration takes effect.
The result of IS-IS FRR on R1 is shown below.

R1#show isis fast-reroute-topology
00D0.D0C7.6788 gei-0/2/1/1 gei-0/2/1/2 Link 20
00D0.D0C7.6788 gei-0/2/1/1 gei-0/2/1/2 Link 20
R1#show ip forwarding backup route

IPv4 Backup Routing Table:
1.1.1.0/24 190.1.1.200 fei-0/1/0/4 ISIS_LEVEL1 115 30
5-36

5.6 IS-IS Fault Handling

5.6.1 IS-IS Basic Function Fault Handling
Take the topology shown in Figure 5-7 as an example to describe how to handle an IS-IS
fault.
Figure 5-7 Network Topology of an IS-IS Fault

Symptom:
R1 and R2 fail to set up neighborhood.

Fault analysis:
1. Inspect whether the management state of physical port is in up state. If it is down,
check if down is in shutdown state. When interface management, physical and
protocol state are up, check if the interconnected interfaces can ping each other
successfully. If all physical interfaces are in up state but the ping is still failed, inspect
and change cables.
2. Use the show isis circuits command to view the conditions and states of IS-IS
interfaces. Inspect whether the interfaces are in UP state. If the interfaces are in
down state, inspect the link state.
3. Use the show isis adjacency command to view the condition of neighborhood. If the
neighborhood is in up state, it means that the neighborhood is set up well. If the
neighborhood is in init state, it means that the packets are received from the peer
already. The link is in init state of 10 seconds when it just set up. The time of 10
seconds is to wait to receive packets from the peer. If the link is always in init state,
inspect whether the peer has authentication configuration.
4. Inspect whether the topology is calculated correctly. Use the show isis topology
command to view the topology calculation. If the topology is failed to calculate,
inspect whether the metric-types are consistent in a pair of peers, inspect whether
the authentication modes are the same in route mode.
5-37


The flow to handle an IS-IS fault is shown in Figure 5-8.
5-38

Figure 5-8 Flow to Handle an IS-IS Fault
5-39


The procedure to handle an IS-IS fault is described below.
1. Inspect whether a pair of interfaces can ping each other.
2. Use the show running-config isis command to view whether IS-IS protocol is enabled.
3. Inspect whether the system-ID is unique. Two routers with the same system-ID cannot
establish neighborhood.
4. Inspect whether the configuration of area is correct. When IS-type is lvel-1, the areas
have to the same in the interconnected devices. Otherwise, level-1 neighborhood
cannot be set up.
5. Inspect whether the IS-type is correct. The range of IS-type needs to have intersection
with the range of circuit-type on interface. Otherwise, the neighborhood cannot be set
up.
6. Inspect whether IS-IS is enabled on the interconnected interfaces.
7. Inspect whether the configuration of circuit-type is correct on interface.
8. Inspect whether the authentication information and modes are consistent on two ends.
9. Inspect whether the configurations of metric-type are consistent on two ends in route
mode.
10. Inspect whether the configuration of authentication are consistent on two ends in route
mode.
5.6.2 IS-IS Multi-Instance Fault Handling

Take the topology shown in Figure 5-9 as an example to describe how to handle an IS-IS
multi-instance fault.
Figure 5-9 Network Topology of an IS-IS Multi-Instance Fault

Symptom:
R1 and R2 could not establish neighbor relationship properly.

Fault analysis:
1. Inspect whether the management state of physical port is in up state. If it is down,

check if down is in shutdown state. When interface management, physical and
protocol state are up, check if the interconnected interfaces can ping each other
5-40

successfully. If all physical interfaces are in up state but the ping is still failed, inspect
and change cables.
2. Use the show isis circuits command to view the conditions and states of IS-IS
interfaces. Inspect whether the interfaces are in UP state. If the interfaces are in
down state, inspect the link state.
3. Use the show isis adjacency command to view the condition of neighborhood. If the
neighborhood is in up state, it means that the neighborhood is set up well. If the neigh-
borhood is in init state, it means that the packets are received from the peer already.
The link is in init state of 10 seconds when it just set up. The time of 10 seconds is to
wait to receive packets from the peer. If the link is always in init state, inspect whether
the peer has authentication configuration.
4. Inspect whether the topology is calculated correctly. Use the show isis topology
command to view the topology calculation. If the topology is failed to calculate,
inspect whether the metric-types are consistent in a pair of peers, inspect whether
the authentication modes are the same in route mode.

The flow to handle an IS-IS multi-instance fault is shown in Figure 5-10.
5-41

Figure 5-10 Flow to Handle an IS-IS Multi-Instance Fault

The procedure to handle an IS-IS multi-instance fault is described below.
1. Inspect whether a pair of interfaces can ping each other successfully.
5-42

2. Use the show running-config isis command to view whether IS-IS protocol is enabled.
3. Inspect whether the system-ID is unique. Two routers with the same system-ID cannot
establish neighborhood.
4. Inspect whether the configuration of area is correct. When IS-type is lvel-1, the
areas have to the same in the interconnected devices. Otherwise, level-1 neighbor
relationship cannot be established.
5. Inspect whether the IS-type is correct. The range of IS-type needs to have an
intersection with the range of circuit-type on interface. Otherwise, the neighbor
relationship cannot be established. Inspect whether ip router isis is enabled on the
direct-connected interfaces.
6. Inspect whether the configuration of circuit-type is correct on interface.
7. Inspect whether the authentication information and modes are consistent on two ends.
8. Inspect whether the configurations of metric-type are consistent on two ends in route
mode.
9. Inspect whether the configuration of authentication are consistent on two ends in route
mode.
5.6.3 IS-IS FRR Fault Handling

The network topology of a IS-IS fault is shown in Figure 5-11.
Figure 5-11 Network Topology of a IS-IS FRR Fault

For the primary/backup relationship in IGP protocols, when there are more than two links
to the same destination route and all links work properly, it is necessary to check the
FRR configuration and check whether the conditions to form an FRR relationship are met.
For the down-stream-path mode, the algorithm meets the condition Distance_opt(Ni, D) <
Distance(S, D). That is, the distance from the next hop on the backup link to the destination
should be shorter than that from the source node on the primary link to the destination. The
default mode of the FRR relationship is LFAs test mode, and the algorithm should meet the
condition Distance_opt(Ni, D) < Distance_opt(Ni, S) + Distance(S, D). That is, the distance
from the next hop on the backup link to the destination should be shorter than the sum of
the distance from the next hop on the backup link to the source node and the distance from
the source node on the primary link to the destination.
5-43

If the costs of the links meets the algorithm requirement, check whether the fast-reroute di
sable command or the fast-reroute block command is enabled on the backup link interface.

The flow to handle a IS-IS FRR fault is shown in Figure 5-12.
Figure 5-12 Flow to Handle a IS-IS FRR Fault

The procedure to handle an IP FRR fault is described below.
1. Check whether FRR configuration is configured on routers with the show running-con
fig isis command.
Use the show isis fast-reroute-topology [ level-1 | level-2] command. If the Ipfrr type
(that is, the protection) is Link or Node and there is no ECMP mark in the output
result, the primary/backup relationship is formed.
2. If the primary/backup links are not formed, check whether the link costs meet the
algorithm requirement.
3. Check whether the backup link is forbidden to back up.
5-44

Chapter 6
BGP Configuration
Table of Contents
BGP Overview............................................................................................................6-1
BGP Working Principle ...............................................................................................6-2
Configuring BGP ........................................................................................................6-4
BGP Configuration Examples ...................................................................................6-60
BGP Fault Handling..................................................................................................6-74
6.1 BGP Overview

BGP is an inter-domain routing protocol used between ASs. By means of BGP, ASs can
exchange the information of network reachability between each other. The information
is a list of ASs where a route passes through, which is sufficient to set up a diagram to
indicate the connection status of the ASs. In this way, AS-based routing selection policy
is available, and BGP also solves the problem of route loop.
BGP of version 4 (BGP4) is the latest BGP version, which is defined in RFC1771. It has
the following features,
l It supports to realize CIDR, supernet and subnet and so on.
l It supports route aggregation.
l BGP running is reliable. It uses Transfer Control Protocol (TCP) as its bottom layer
protocol. It uses TCP No.179 port.
l It only sends route updating information.
l It sends keepalive packets regularly to make sure that TCP connection is well.
l It has consummate metric values.
l It has abundant attributes and control functions.
l It applies to large-scale network especially.
The session which is set up by BGP routers belonging to different ASs is called External
Border Gateway Protocol (EBGP) session, while a session which is set up between BGP
routers belonging to the same AS is called Internal Border Gateway Protocol (IBGP)
session.
An administrative area with independent routing policies is called an AS. The important
feature of an AS is that it has a unified internal route for another AS, and it has a consistent
topology for reachable destinations. The AS indicator is a value of 16-bit, ranging from 1
to 65535, where, 1 – 32767 are assignable, 32768 – 64511 are reserved, and 64512 –
65534 are used for private ASs (similar to private network addresses). When 16–bit AS
number is used, the AS number range is 1 – 65535. Current version also supports 32–bit
AS which is in the range of 1-4294967295.
6-1

The router sends BGP update messages related to the destination network to its peer
router. The BGP updating messages contain the information related to BGP metric (called
path attribute). By means of BGP attributes, the special route can be described in detail.
In this way, user can select and filter routes. The path attributes have the following four
independent types,
1. Well-known mandatory attribute: This kind of attributes has to be contained by route
description.
l AS-path
l Next-hop
l Origin
2. Well-known discretionary attribute: The kind of attributes is not necessary contained
by route description.
l Local preference
l Atomic aggregate
3. Optional transitive attributes: This kind of attributes does not require that all BGP
operations support it. However, if it is supported, it can be transmitted to its BGP
neighbor. while, if it is not supported by the current router, it will be transmitted to
other BGP routers continuously.
l Aggregator
l Community
4. Optional nontransitive attribute: This kind of attributes shows that the routers which
do not support the attribute need to delete it.
l Multi-Exit Discriminator (MED)
The kinds of BGP attributes can be expanded into 256 but not all attributes are used
together. The attributes can be used selectively and flexibly.
6.2 BGP Working Principle

Four types of messages are available for BGP working:
l OPEN
It establishes BGP connection. The message includes BGP version number, local
AS number and the shortest hold time for negotiation, BGP ID and other optional
parameters.
l UPDATE
It sends BGP route updating packets. The message is sent only once route is updated.
l KEEPALIVE
It confirms the peer status. The default sending interval is 30 seconds, and the
Hold-time is 90 seconds by default. Once the neighbor receives the KEEPALIVE
packet, the Hold-time timer will be reset. If the hold-time expires, then consider that
the neighbor is in abnormal status, and disconnect the BGP connection with neighbor.
l NOTIFICATION
6-2

Chapter 6 BGP Configuration
It is used to notify error. The router sends NOTIFICATION packet because of errors,
such as the TCP connection is failed with neighbor, failed authentication and routing
loop and so on. After sending NOTIFICATION packet, BGP connection will be
disabled.
BGP working flow is listed as follows,
1. Idle State
It is the initial state. The BGP starts initialization after the protocol is activated. It resets
the timer, launches the first TCP connection and enters state 2.
2. Connect state
The BGP starts TCP connection and waits for the message of TCP successful
connection. If the connection is successful, then the BGP enters OpenSent state.
Otherwise, the BGP enters Active state.
3. Active state: The BGP always tries to establish TCP connection. If the connection
timer times out, then the BGP returns to Connect state. If TCP connection is
successful, then BGP enters OpenSent state.
4. OpenSent state
TCP connection is established already. The BGP sends the first OPEN packet and
waits for the reply from the peer. BGP examines the reply packet. If the BGP finds
error, it will send a NOTIFICATION packet and return to Idle state. If there is no error
in the reply packet, BGP will send a KEEPALIVE packet. KEEKALIVE timer starts
timing. The BGP enters into OpenConfirm state.
5. OpenConfirm state
The BGP waits for KEEPALIVE packet and resets the KEEPALIVE timer. When the
BGP receives a KEEPALIVE packet, it enters Established state.
6. Established state
Neighborhood is set up already. Router exchanges Update packet with its neighbor,
and meanwhile, the KEEPALIVE timer is reset.
In initial, the exchanging of routing information includes all BGP routes, that is, all entries
in BGP routing table will be exchanged. After the initial exchanging is finished, the
incremental and burst routing update is launched only when the route entries are changed
or been unavailable. The meaning of the so-called incremental is that not the entity BGP
table will be exchanged but only update the changed route entries. The burst means
that update routes only when the routing table is changed rather than periodically route
updating.
When a router sends route information to its neighbor, it will save the route entries sent
to neighbor at local. When the router receives a route updating packet, it will compare
updating packet with the locally saved routing entries. If this entry is not sent before, then
the router will send it to its neighbor. If the entry is sent already and better, the router will
send the entry to its neighbor and update its locally saved routing entries. Compared with
6-3

the conventional periodical routing table updating, this updating mode saves the bandwidth
a lot. Route updating is achieved by UPDATE packets.
During the process above, if the BGP connection fails to be established because of any
connection failure, authentication failure and route loopback and so on, the router will send
NOTIFICATION packet to its peer that close BGP session will be closed. Later, the router
enters Idle state.
BGP working process is shown in Figure 6-1.
Figure 6-1 BGP Working Process
6.3 Configuring BGP

6.3.1 BGP Neighborhood Establishment
Two routers are called as peers or neighbors if BGP session is set up between them. There
are two connection modes of peers, IBGP and EBGP. If the two routers which exchange
BGP packets belong to the same AS, then these two routers use IBGP as their connection
6-4

mode. Otherwise, if the two routers belong to different ASs, then they use EBGP as their
connection mode.
As shown in Figure 6-2, R1 and R2 are EBGP neighbors, R2 and R3 are IBGP neighbors.
Figure 6-2 IBGP and EBGP
6.3.1.1 Establishing EBGP Neighborhood

Make sure that the physical connection between two nodes is normal and the nodes belong
to different ASs before configure EBGP neighbor.
In most of EBGP cases, two routers are directly connected by physical interfaces. Usually,
use the IP addresses of the interconnected interfaces to set up BGP connection, but also
can use loopback addresses to set up BGP connection.
What draws special attention during the configuration is that multi-hop connection has to
be specified if do not use physical connection to set up EBGP connection. That because
the router sets the TTL value of BGP protocol packet as 1 by default. Therefore, even if
TCP connection is set up, OPEN packets still cannot be sent to the CPU of the peer. In
this way, BGP connection cannot enter Established status.
To establish EBGP neighborhood on ZXR10 M6000, perform the following steps.
6-5

Step- Command Function

s
1 ZXR10(config)#router bgp < as-number> This starts BGP routing process and
specifies the AS number of router.
< as-number> is the AS system ID
of router, the range is 1–65535.
1–64511 is the global common AS
number. 64512–65535 is used by
private networks. Current version
also supports 32–bit AS which is in
the range of 1-4294967295.
2 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This configures a BGP neighbor or a

] remote-as < number> peer and the AS number.
3 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This establishes EBGP

] ebgp-multihop [ ttl < value> ] neighborhood on indirect-connected
networks.
4 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This specifies local loopback address
] update-source < interface-name> as source IP address to set up TCP
connection.
< ipv4-address> IPv4 address of neighbor, in dotted decimal notation
< peer-group-name> peer-group name
< number> The AS system that the neighbor belongs to. The range is 1–65535
< number> The AS system that the neighbor belongs to. The range of a 2–byte
AS number is 1–65535, and the range of a 4–byte AS number is
1-4294967295.
< value> The number of ttls, the range is 1–255
6-6

< interface-name> The interface to be specified as source address to set up TCP

connection in BGP session
Set Up EBGP through Direct-Connected Address

As shown in Figure 6-3, R1 belongs to AS65000, and R2 belongs to AS65001. Establish
EBGP neighborhood between R1 and R2 through physical interfaces.
Figure 6-3 EBGP Physical Direct-Connected Configuration Topology
R1#config terminal
R1(config-if)#exit
R1(config)#router bgp 65000
R1(config-bgp)#neighbor 129.213.1.2 remote-as 65001
R1(config-bgp)#exit
R2#config terminal
R2(config-if)#exit
R2(config-bgp)#exit
View the configuration result.
6-7

To view the established BGP neighborhood, use the show ip bgp neighbor command on
R1.
R1#show ip bgp neighbor
BGP neighbor is 129.213.1.2, remote AS 65001, external link
BGP version 4, remote router ID 129.213.1.2
BGP state = Established, up for 00:04:21
hold time is 90 seconds, keepalive interval is 30 seconds
……
Connections established 1
Local host: 129.213.1.1, Local port: 179
Foreign host: 129.213.1.2, Foreign port: 1024
The IP address of BGP neighbor is 129.213.1.2. The neighbor belongs to AS65001. EBGP
connection is set up already. The router-ID of neighbor is 129.213.1.2 and the state is
Established. The session is set up 4 minutes 21 seconds.
R2.
……
Set Up EBGP through Loopback Addresses

As shown in Figure 6-4, EBGP neighborhood is set up through loopback addresses
between R1 and R2.
6-8

Figure 6-4 EBGP Configuration through Loopback Address
R1#config terminal
R1(config)# interface fei-0/1/0/1
R1(config-if)#exit
R1(config)#interface Loopback1
R1(config-if)#exit
R1(config-bgp)#neighbor 1.1.1.2 ebgp-multihop ttl 5
R1(config-bgp)#neighbor 1.1.1.2 update-source Loopback1
R1(config-bgp)#exit
R1(config)#ip route 1.1.1.2 255.255.255.255 192.168.1.2
R2#config terminal
R2(config-if)#exit
R2(config-if)#exit
6-9


R2(config-bgp)#exit
R2(config)#ip route 1.1.1.1 255.255.255.255 192.168.1.1
Note that if the number of hops is not designated behind ebgp-mulitihop, the system will
set TTL value as 8 by default.
R1.

……
R1 establishes EBGP connection with the router 1.1.1.2 belonging to AS 65000 already.
R2.
……
R2 establishes EBGP connection with the router 1.1.1.1 belonging to AS 65000 already.
6.3.1.2 Establishing IBGP Neighborhood

Make sure that the physical connection between two nodes is normal and the nodes belong
to the same AS before configure IBGP neighbor.
IBGP is used to exchange BGP update packets in an AS and maintain the internal
connectivity.
BGP rules that an IBGP router cannot send the routes received from another IBGP router
to the third IBGP router. This is the rule of Split-horizon. When a router receives a update
packet through EBGP, it will process and send the packet to all IGBP routers and EBGP
peers, but when a router receives update packet through IBGP, it will process and send
6-10

the packet through EBGP rather than send it to IBGP neighbors. Therefore, to keep the
connectivity of the BGP, BGP routers have to set up a full meshed network through IBGP
session.
1 ZXR10(config)#router bgp < as-number> This starts BGP process and

2 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This configures a BGP neighbor or a

] remote-as < number> peer and the AS number.
3 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> (Optional) This specifies the local
] update-source < interface-name> loopback address as the source
IP address to establish a TCP
connection. This command is used
when the loopback address is used
to establish an EBGP connection.
4 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This makes the interface address of
] next-hop-self the router itself as the next hop for
advertising routes by constraint.
5 ZXR10(config-bgp)#no synchronization This disables synchronization so

that BGP will advertise network
route without waiting until IGP is
synchronized.
< number> The AS that the neighbor belongs to. The range of a 2–byte AS
number is 1–65535, and the range of a 4–byte AS number is
1-4294967295.
< interface-name> The interface to be specified as source address to set up TCP

connection in BGP session
6-11

In Step 4, NEXT_HOP is a BGP well-known mandatory attribute. It shows the IP address

of the next-hop to destination address. There are three kinds of conditions,
l If the advertising and receiving routers belong to different ASs, the next-hop is the IP
address of the interface of the advertising router.
l If the advertising and receiving routers belong to the same ASs, and the NLRI
destination address containing in updating message also belongs to the AS, the
next-hop is the interface of the router which advertises the route information.
l If the advertising and receiving routers are a pair of internal peers, and the NLRI
containing in updating message points to another AS, the next-hop is the IP address
of the external peer. The IP address has to be accessible, otherwise, the advertised
entry is invalid.
In Step 5, the synchronization rule is that when an AS provides transition service for
another AS, after all the routers belonging to the AS receive the route through the
transmission of IGP route information, BGP can send the route to outside. When a router
receives a route updating message from IBGP, it will valid the synchronization before
forward the message to other EBGP peers. Once IGP routing table contains the entry
corresponding to the updating message, the router will forward the message by EBGP.
Otherwise, the router will not forward the message.
Synchronization rule is to ensure the connectivity in AS and prevent route blackhole.
However, in practical use, synchronization function is usually disabled, and IBGP full
meshed structure is used to ensure the connectivity in AS. Full-meshed structure can
avoid that lots of BGP routes are sent to IGP, which can quicken the speed of router
processing. Additionally, it ensures that the data packets are not lost. To disable
synchronization function, one of the following two conditions needs to be satisfied.
1. The AS at where routers locate only has one egress, or it is a stub AS. That is to say,
the AS only has one point to connect to external network.
2. The AS at where routers locate is a transition type (that is to say, an AS can connect
to the third AS through the AS), but all routers of the AS run BGP.
The second condition is common. Since all routers have BGP information in AS, IGP only
needs to transmit routing information for local AS.
Synchronization function is enabled on router by default. Use the no synchronization

command to cancel synchronization function.
Set Up IBGP through Loopback Addresses

As shown in Figure 6-5, R2 and R3 belong to the same AS. Set up IBGP connection
between R2 and R3 through Loopback addresses.
6-12

Figure 6-5 IBGP Configuration
R2#config terminal
R2(config-if)#exit
R2(config-if)#exit
R2(config-bgp)#neighbor 1.1.1.3 next-hop-self
R2(config-bgp)#no synchronization
R2(config-bgp)#exit
R3#config terminal
R3(config-if)#exit
6-13

R3(config-if)#exit
R3(config-bgp)#exit
Use the show ip bgp neighbor command to view the established BGP neighborhood on R2.
BGP neighbor is 1.1.1.3, remote AS 65001, internal link
……
last error code is 6
R2 sets up IBGP neighborhood with R3 (1.1.1.3) already.

Use the show ip bgp neighbor command to view the established BGP neighborhood on R3.

BGP neighbor is 1.1.1.2, remote AS 65001, internal link
……
last error code is 5
R3 sets up IBGP connection with R2 (1.1.1.2) already.
6.3.1.3 Configuring BGP Neighborhood Authentication Password

To make the MD5 authentication be available on TCP connection between a pair of BGP
peers, perform the following steps to configure neighborhood password. The password
can be encrypted to enhance the safety of BGP connection.
6-14


2 ZXR10(config-bgp)#neighbor < ip-address> password [ < string 1> | This configures the BGP neighbor
encrypt < string 2> ] authentication, including plain text
display and cryptograph display.
< ip-address> IPv4 address of neighbor, in dotted decimal notation
< string 1> Character string password, in case sensitive, the length is 3–80
characters.
< string 2> The length is 3–80 characters
Example
The following example shows how to configure BGP neighbor password authentication
and encrypt the password.
ZXR10(config)#router bgp 100
ZXR10(config-bgp)#neighbor 192.168.0.2 remote-as 100
ZXR10(config-bgp)#neighbor 192.168.0.2 password 789
ZXR10(config-bgp)#neighbor 192.168.0.2 password encrypt 123
ZXR10(config-bgp)#show running-config bgp
router bgp 100
neighbor 192.168.0.2 password encrypt u5pd4oR1YGR1E+My5y4ec1dbC7
eZf4gsX0qhVYXcb6KV1CMnm8VFlX9dcceOjgUYrxPGh3Gy7Rl8VxSlqtHcujwZ5qzj
LbVOkiKWz41nHPk=
!
6.3.1.4 Restarting BGP Process

When BGP neighbor enters abnormal state, restart BGP neighbor process to recover.
To restart a BGP neighbor on ZXR10 M6000, use the following command in global
configuration mode.
Command Function
ZXR10(config-bgp)#reset ip bgp [ vrf < vrf-name> ] [ < ipv4-address> | This restarts BGP instance, a peer or
< peer-group-name> ] a pair of peers.
< vrf-name> VRF name, the length is 1–32 characters.
6-15

< ipv4-address> IPv4 address of neighbor
< peer-group-name> Name of the peer group
6.3.2 Configuring BGP Route Advertisement

6.3.2.1 BGP Route Advertisement Rules
The routes to be advertised by BGP have to exist in IGP routing table already. The source
of BGP route updating is that inject IGP routing information to BGP. It has an influence
on the stability of Internet routes directly. There are two route injection methods, dynamic
injection and static injection.
Dynamic injection is divided into two types, full dynamic injection and selective dynamic
injection.
Full dynamic injection means that all IGP routes are redistributed (Redistribution) to BGP.
This method is very easy to configure but controllability is weak and low efficient.
Selective dynamic injection means that inject a part of IGP routes to BGP (use network
command). This method verifies address and mask first, which improves controllability
and efficiency. In this way, the error routing information can be avoided to inject.
However, no matter which method is used, the routes will be unstable. That because
dynamic injection totally depends on IGP information. When route flapping occurs on
IGP routes, BGP route update will be affected. Lots of updating packets are generated
because of the unstable routes, and the bandwidth will be wasted heavily. To make up this
disadvantage, route dampening and aggregation can be used on the border.
Static injection solves the unstable routes greatly. It injects static routes to BGP. Static
routes are added manually, so it is influenced by IGP route flapping. Therefore, the
repeated updating will be prevented by the stability. However, if the subnetwork partition
is not very clear, static injection also brings data flow blocking.
In conclusion, there are three BGP route advertisement methods.

l Use network command to advertise routes.
l Use redistribute command to redistribute the routes learned by other protocols to BGP.
l Use BGP route aggregation to advertisement.
6.3.2.2 Advertising Routes by Using the network Command

The routes to be advertised by BGP have to exist in IGP routing table already.
The common method of BGP route advertisement is to select the network segment to
advertise by the network command. This command specifies the destination network
segment and mask, and then the routes which match with the rule accurately will enter
into BGP routing table. The routes will be filtered and advertised.
6-16

For example, use the network 18.0.0.0 255.0.0.0 command in BGP. The network segments
18.0.0.0/8, 18.1.0.0/16 and 18.2.0.0/24 are added to BGP routing table. If these network
segments and subnetworks do not exist in routing table, then no route is injected to BGP
routing table. In order to cooperate with BGP route advertisement, it is required that
configure some static routes pointing to loopback address on router.
It is notable that not all routes injected to BGP routing table can be advertised. It relates
to BGP route filtering or routing policy.
In BGP, use the network command to advertise known network to router. The known
network can be learned by direct-connected route, static route and dynamic route. The
usage of the network command in BGP is different to that in IGP.

2 ZXR10(config-bgp)#network< ip-address> < net-mask> [ This outputs the routes to be

route-map< map-tag> ] advertised to BGP routing table.
The routes are learnt from the
direct-connected route, dynamic
routing selection and static route.
Advertise Route by Using the network Command

As shown in Figure 6-6, R2 runs OSPF as IGP protocol. R2 requires that advertise the
network segment 18.0.0.0/8 advertised by OSPF to BGP.
Figure 6-6 Use network Command to Advertise BGP Route
6-17

R2#config terminal
R2(config-if)#exit
R2(config-bgp)#network 18.0.0.0 255.255.255.0
R2(config-bgp)#exit
R1#config terminal
R1(config-if)#exit
R1(config-bgp)#exit
Use the show ip bgp route command to view BGP routing table on R1.
R1#show ip bgp route
Status codes: *-valid, >-best, i-internal,s-stale
Origin codes: i-IGP, e-EGP, ?-incomplete
Dest NextHop Metric LocPrf RtPrf Path

*>18.0.0.0/8 192.168.2.1 20 65001 i
Note:
l The symbol * indicates the route is available.
l The symbol > indicates the route is the optimized choice.
l The symbol i indicates the route is a IBGP route.
l The route without “i” indicates this is a EBGP route or local route.
l The address under the entry of Next-hop is the next-hop address of BGP route. If the
address is represented as full zero, that means this route is generated by router itself.
l The value under the Local-Pre is the priority level of route which is learned by BGP.
The default value is 100.
l The field Path shows the origin of this route. Three types: IGP, EGP and incomplete.
The example above shows that the network segment 18.0.0.0/8 exists in BGP routing table
already. The next hop address is the interface 192.168.2.1 of R2.
6-18

6.3.2.3 Redistributing Routes by Using the redistribute Command

IGP needs to be configured on router already.
Full dynamic injection has to be chosen to advertise BGP routes when there are lots of
route entries and aggregation is not convenient.
When there are lots of route entries and aggregation is not convenient, use the redistribute
command to redistribute one or more IGP protocol (RIP, OSPF and IS-IS) routes to BGP.
Make sure that IGP does not redistribute the routes learnt by BGP to BGP again. Use
filter command to avoid loopback if it is necessary.
To redistribute routes on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#router bgp < as-number> This enters BGP route configuration

mode and specifies AS number of
router.
2 ZXR10(config-bgp)#redistribute < protocol> [ metric < metric-value> This redistributes the routes learned
] [ route-map < map-tag> ] from other routing protocol to BGP
routing table.
< protocol> The name of other protocols, connected, static and rip, ospf-int and
ospf-ext, isis-1, isis-2 and isis–1–2
< metric-value> Metric value of the redistributed routes. Use default value if it is not
specified. The range is 0-4294967295.
< map-tag> The name of route mapping of the redistributed route, the length is
1-32 characters.
Redistribute OSPF Routes by Using the redistribute Command

As shown in Figure 6-7, R2 runs OSPF as IGP protocol. It is required that redistribute all
OSPF routing information of R2 to BGP.
6-19

Figure 6-7 Redistribute OSPF Routes by Using redistribute Command
R2#config terminal
R2(config-if)#exit
R2(config)#exit
R2(config-bgp)#redistribute ospf-int
R2(config-bgp)#redistribute connected
R2(config)#exit
Use the show ip bgp route command to view BGP routing table of R1.

*> 18.0.0.0/8 192.168.2.1 20 65001 ?
Add the OSPF external route to R2 and set the metric value as 5.
R2#config terminal
6-20


R2(config-if)#exit
R2(config)#exit
R2(config-bgp)#redistribute ospf-ext metric 5
R2(config)#exit
6.3.2.4 Configuring Route Aggregation

To prevent route black hole, aggregate the routes with the same mask on router in route
aggregation configuration.
BGP protocol aggregates the learnt routes to a route for advertisement. Thus, route entries
can be reduced a lot in routing table.
To configure route aggregation on ZXR10 M6000, perform the following steps.

2 ZXR10(config-bgp)#aggregate-address < ip-address> < net-mask> [ This creates a route aggregation

count < count> ] [ as-set] [ summary-only] [ strict] policy in BGP routing table.
< ip-address> The aggregation network to be aggregated, in dotted decimal notation
< net-mask> The aggregation mask to be generated, in dotted decimal notation
< count> The number of sub-networks, the range is 0–255, and the default
value is 1.
as-set Set path information
summary-only If this keyword is configured, the router only advertises the aggregation
route to BGP neighbors. The subnet routes aggregated are not
strict According to RFC1771, only the routes which the attributes of MED
advertised.
and NEXT_HOP are the same respecivetily can be aggregated.
If the command is used without strict, do not consider MED and
NEXT_HOP attributes.
6-21

Route Aggregation Configuration

As shown in Figure 6-8, R1 advertises the network segments 192.168.0.0/24,
192.168.1.0/24 and 192.168.2.0/24, 192.168.3.0/24 to R2 belonging to AS300. Run
OSPF routing protocol between R1 and R3.
Figure 6-8 Route Aggregation Configuration Example
R1(config-if)#exit
R1(config-bgp)#aggregate-address 192.168.0.0 255.255.252.0 summary-only
R1(config-bgp)#exit
R1 learns four routes 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0/24

through IBGP, but it advertises the aggregated route 192.168.0.0/22 to R2 running EBGP
6-22

only. If the command is used without the summary-only keyword, R2 will advertise the
aggregated route and the detailed routes.
Use the show ip bgp route command on R2 to view the routing table.
Status codes: *valid, >best, i-internal
*>192.168.0.0/22 2.2.2.2 20 100 i
R2#show ip bgp route detail 192.168.0.0 255.255.252.0

BGP routing table entry for 192.168.0.0/22
01:02:19 received from 2.2.2.2
origin i,nexthop 2.2.2.2,atomic,aggr 100 2.2.2.2,
as path [100]
After the aggregation, there is only one route in BGP routing table of R2 belonging to
AS300. It reduces the size of routing table.
If the command is used without the summary-only keyword, R2 will advertise the detailed
routes with the aggregated route.


*>192.168.0.0/22 2.2.2.2 20 100 i
*>192.168.0.0/24 2.2.2.2 20 100 i
*>192.168.1.0/24 2.2.2.2 20 100 i
*>192.168.2.0/24 2.2.2.2 20 100 i
*>192.168.3.0/24 2.2.2.2 20 100 i
In BGP routing table, there are four routes 192.168.0.0/24, 192.168.1.0/24 and
192.168.2.0/24, 192.168.3.0/24 except the aggregated route 192.168.0.0/22.
The count < count> parameter indicates the number of subnetworks which are waiting to
implement aggregation. The <count> parameter ranges from 0 to 255 and the default
value is 1, which means the number of subnetworks has to exist in IGP. If the parameter
is 0, that means advertise the route 192.168.0.0/22 when any subnetwork of 192.168.0.0
255.255.252.0 appears in IGP routes. If the parameter is 1 or other value, the following
command is required using to specify the related subnetwork segment.
aggregate-address < ip-address> < net-mask> subnet < subnet-address> < subnet-mask>
The above command means that the routing information can be aggregated and advertised
only when the specified subnetwork routing information appears in IGP routing table and
the route number satisfies the defined count number.
6-23

Aggregate Routes Using the Parameters count and subnet

When IGP ran by R1 confirms that the three routes 192.168.1.0/24, 192.168.2.0/24 and
192.168.3.0/24 exist in the routing table, it will send the aggregated route 192.168.0.0/22
to R2.
R1(config-if)#exit
R1(config-bgp)#aggregate-address 192.168.0.0 255.255.252.0 count 0 summary-only
R1(config-bgp)#exit
For that moment, as long as these three routes 192.168.1.0/24, 192.168.2.0/24 and
192.168.3.0/24 are normal, R2 will send an aggregated route 192.168.0.0/22 to R1 no
matter whether 192.168.0.0/22 normal or not. However, if any one of these three routes
is abnormal, R2 will not advertise the aggregated route 192.168.0.0/22.
6.3.3 Configuring BGP Route Load Sharing

To configure BGP route load sharing on ZXR10 M6000, perform the following steps.

mode.
2 ZXR10(config-bgp)#maximum-paths ibgp< number> This configures the count of routes

(This is for IBGP route load sharing.)
ZXR10(config-bgp)#maximum-paths < number> This configures the count of routes

that support load sharing. It is in
the range of 1-16. The default value
is 1. (This is for EBGP route load
sharing.)
6-24


mode.

6.3.4 Configuring BGP FRR

To configure BGP FRR on ZXR10 M6000, perform the following steps.

mode.
2 ZXR10(config-bgp)#bgp frr This enables BGP FRR function.
6.3.5 Configuring BGP Route Attribute and Route Filtering

6.3.5.1 The Concept of BGP Attributes
BGP defines various attributes. each attribute has its own function, that is why BGP is the
most flexible route protocol with the best expansibility and high controllability.
BGP routING attribute is the core concept of BGP route protocol. It is a group of parameters
sent to the connected peer in UPDATE packets. These parameters records BGP routing
information for route selection and filter, which can be considered as Metric.
Route attributes are divided into four types:
l Well-known mandatory attributes
l Well-known discretionary attributes
l Optional transitive attributes
l Optional nontransitive attributes
The attribute Well-known is identified by all BGP routers. Each UPDATE message has to
contain the attribute mandatory, but the attribute discretionary is optional.
For an optional attribute, it is not supported by all BGP routers. When BGP does not
support an attribute, if it is transitive, it will be accepted and sent to other BGP peers. If
this attribute is nontransitive, itwilll be ignored and not sent to other peers.
RFC1771 defines No.1–7 BGP route attribute, as follows:
6-25

l No.1: ORIGIN
Route origin, that is the AS that generate this routing information.
l No.2: AS_PATH
AS path, that is the AS group or series which has been passed by route entry.
l No.3: NEXT-HOP
The next hop address. IBGP connection will not change NEXT-HOP sent by EBGP.
l No.4: MULTI_EXIT_DISC
It is used to distinguish many exits to other ASs, which is used by local AS router.
l No.5: LOCAL-PREF
It is transmitted within the local AS, indicating the priority of each path.
l No.6: ATOMIC_AGGREGATOR
l No.7: AGGREGATOR
l No.8: RFC1997 defines another common attribute: COMMUNITY
Here, No.1, 2 and 3 attribute are well-known mandatory attributes. No.5 and 6 are
well-konwn discretionary attributes. No.7 and 8 are optional transitive attributes. No.4
is optional nontransitive attribute. They have different priorities, LOCAL-PREF has the
highest priority, and the second one is AS-PATH and ORIGIN.
For other attributes used by BGP, please refer to RFC documentation.
6.3.5.2 Filtering Routes by Route Map

The bases of performing BGP are route filter and attribute configuration. By means of
route filter, the input or output route attributes can be controlled.
Route map is used to control routing information, which redistributes routes between
routing areas by defining rules. The route map usually cooperates with the route attributes
to decide route.
To filter routes by route map on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#route-map < map-tag> [ permit | deny] [ < This creates a route map.
sequence-number> ]
2 ZXR10(config)#ipv4-access-list < name> This creates and names an Access

Control List (ACL).
ZXR10(config-ipv4-acl)#rule < rule-id > { permit | deny} { < This defines an ACL rule.
source> [ < source-wildcard> ] | any}
6-26


specifies AS number of router.
ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This binds a specified ACL to match
] route-map < map-tag> { in | out} BGP routes or modify the route
attributes.
< map-tag> Name of route mapping, the length is 1–31 characters.
permit Permits redistribution or policy routing tag if the route map meets the
matching condition
deny Denies redistribution or policy routing tag if the route map meets the
matching condition
< sequence-number> Sequence number, in the range of 0–65535
< acl-name> Standard ACL list name, the length is 1–31 characters.
< rule-id > The unique ID of a rule in an ACL, determining the sequence of the
rule in the ACL, in the range of 1–2147483644
permit Permit the packets matching with the rule to pass
deny Deny the packets matching with the rule to pass
< source> Source IP address
< source-wildcard> Wild mask of source IP address
any Any source IP address
< map-tag> Name of route mapping, the length is 1–31 characters
in | out It applies to in or out
6-27

Filter Routes by Using Route-Map

As shown in Figure 6-9, R1 and R2 set up EBGP connection between them. Configure
a route-map on R1. The route-map permits to advertise network 172.3.0.0/16 to AS200,
and set the MED value as 5.
Figure 6-9 Filter Routes by Using Route-Map
R1(config-bgp)#neighbor 182.17.20.1 route-map MAP1 out
R1(config-bgp)#neighbor 182.17.20.1 send-med
R1(config-bgp)#exit
R1(config)#route-map MAP1 permit 10
R1(config-route-map)#match ip address 1
R1(config-route-map)#set metric 5
R1(config-route-map)#exit
R1(config)#ipv4-access-list 1
R1(config-ipv4-acl)#rule 1 permit 172.3.0.0 0.0.255.255
R1(config-ipv4-acl)#exit
When filtering route through route map, the match and set commands are usually used
together with route map. The match command defines the matching standard. The set
command defines the action satisfying matching standard.
Use the neighbor 182.17.20.1 send-med command to send MED attribute with advertising
routes to neighbor 182.17.20.1.
6-28

To view BGP routing table on R2, use the show ip bgp route command.

*>172.3.0.0/16 182.17.20.2 5 20 100 i

07:18:49 received from 182.17.20.2 (172.3.0.1)
origin i,nexthop 182.17.20.2,metric 5,
as path [100]
The above result shows that R2 learns the route from 172.3.0.0/16 only, and its MED value
is 5.
6.3.5.3 Filtering Routes by Using NLRI

To restrict a router to receive or advertise routing information, filter the route updating
packets from or send to a special device. The filter includes a update list sent to neighbor,
or a list coming from neighbor.
To configure NLRI to filter route on ZXR10 M6000, perform the following steps.
1 ZXR10(config)#route-map < map-tag> [ permit | deny] [ < This creates a route-map.

sequence-number> ]
2 ZXR10(config)#ipv4-access-list < acl-name> This creates and names an ACL.
ZXR10(config-ipv4-acl)#rule < rule-id > { permit | deny} { < This defines a rule of an ACL.

mode.
ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This binds a specified ACL to match
] route-map < map-tag> { in | out} BGP routes or modify the route
attributes.
< map-tag> Name of route mapping, the length is 1–31 characters
permit Permit redistribution if the route mapping matches condition
deny Do not permit redistribution if the route mapping matches condition
< sequence-number> Sequence number, 0–65535
6-29

< acl-name> Standard ACL table name, the length is 1–31 characters
permit Permit the packets matching rule to pass
deny Deny the packets matching rule to pass
< map-tag> The name of route mapping, the length is 1–31 characters
in | out It applies to in or out
Filtering Route by Using NLRI

As shown in Figure 6-10, R1 and R2 are a pair of IBGP peers, R1 and R3 are a pair of
EBGP peers, R2 and R4 are a pair of EBGP peers, R2 and R4 are a pair of EBGP peers.
To avoid AS100 to act as transitive AS and prevent R1 from advertising network segment
192.18.10.0/24 of AS300 to AS200, configure filter function on R1.
6-30

Figure 6-10 Filtering Route by Using NLRI
Configuration on R1 (configurations of port and IGP are omitted):

R1(config-bgp)#neighbor 182.17.20.1 route-map MAP1 out
R1(config-bgp)#exit
R1(config)#route-map MAP1 permit 10
R1(config-ipv4-acl)#rule 1 deny 192.18.10.0 0.0.0.255
R1(config-ipv4-acl)#rule 2 permit any
The route-map command and ACL are used to prevent R1 from advertising the route with
prefix 192.18.10.0/24 to AS200, that is, this route is filtered on R1. Therefore, R3 cannot
learn the route 192.18.10.0/24.
6-31

*>192.168.11.0/24 182.17.20.2 20 300 100 i

*>192.168.12.0/24 182.17.20.2 20 300 100 i
*>192.168.13..0/24 182.17.20.2 20 300 100 i
The above result shows R3 locating at AS200 does not learn the route pointing to
192.18.10.0/24.
6.3.5.4 Restricting the Number of Route Advertisements Received by Neighbor

To restrict the number of route received by a neighbor, perform the following steps.

2 ZXR10(config-bgp)#neighbor < ip-address> maximum-prefix This configures the maximum

< value> [ < threshold-value> | drop-routes | restart < time> | number of route received by a
warning-only] neighbor.
< ip-address> Neighbor IP address, in dotted decimal notation
< value> The maximum number of routes received by a neighbor, the range is
< threshold-value> Generate an alarm when the number of the received routes reaches
to the threshold value, the unit is %.
drop-routes Drop the routes when the number of the received routes exceeds
the threshold value
< time> The connection will be disconnected when the number of the received
routes exceeds the threshold value, and set up neighborhood after
waiting a specified time. The unit is minute, the range is 1–30000
warning-only Print the alarm when the number of the received routes exceeds the
threshold value
Example
As shown in Figure 6-11, R1 can receive 10 routes advertised by R2 at most, and it will
drop routes if more than 10 routes are received. R2 can receive 20 routes advertised by
R1, and neighborhood will be disconnected and set up again after 10 minutes if more than
20 routes advertised by R1.
6-32

Figure 6-11 Restrict the Number of Route Advertisements Received by Neighbor

R1(config-bgp)#neighbor 10.1.1.1 maximum-prefix 10 drop-routes
R2(config-bgp)#neighbor 10.1.1.2 maximum-prefix 20 restart 1
Without the configuration of time for waiting reconnection (use the warning-only keyword),
when R1 advertises more than 20 routes to R2, R2 will display the alarm information only.

R2(config-bgp)#neighbor 10.1.1.2 maximum-prefix 20 warning-only
6.3.5.5 Filtering Routes by Using AS_PATH

AS-PATH is a well-known mandatory attribute. The attribute is a path filed, which is
composed of a series of AS numbers passing by a route pointing to one destination. When
the origin AS initiates a route to other external BGP peers, it will add its AS number into
the route. Subsequently, each route receiver will add its AS number into route and place
AS number on the head of AS sequence when sending the route to other BGP peers.
BGP uses AS-PATH as the factor of its route update to realize no—loop topology of
Internet. Each route contains a list with all passed AS numbers. When the route is
advertised to its origin AS, AS examines its AS number has been existed in AS sequence,
and it will not accept this route. Meanwhile, AS-PATH will be used for deciding the
optimum route. When multiple routes (their attributes except for AS-PATH are the same)
to the same destination are available, BGP will select a route with the shortest path as the
optimum route according to AS-PATH. Therefore, increasing AS-PATH can affect BGP
route selection.
When all routes of one or multiple AS require filtering, the filter method based on AS-PATH
is usually used.
6-33


sequence-number> ]
2 ZXR10(config)#ip as-path access-list < access-list-number> { permit This defines an ACL related to BGP
| deny} < as-regular-expression> AS_PATH.
3 ZXR10(config)#route-map < map-tag> [ permit | deny] [ < This enters route mapping
sequence-number> ] configuration mode.
ZXR10(config-route-map)#set as-path prepend < as-path-number> [ This modifies BGP route AS path.
< as-path-number> ] as-path-number ranges from 1 to
65535 or 1 to 4294967295.
< map-tag> The name of route mapping, the length is 1-31 characters.
< sequence-number> Sequence number, ranging from 0–65535
< access-list-number> The number of regular express access list
< as-regular-expression> Use AS represented as regular express in access list
Filtering Routes by Using AS_PATH

As shown in Figure 6-12, in Internet, the route to 10.10.0.0/24 of AS 100 is the optimum
path, and the path must be AS500→AS300→AS200→AS100.
6-34

Figure 6-12 Filtering Routes by Using AS_PATH
Configuration on the egress router of AS100:
ZXR10_AS100(config)#router bgp 100

ZXR10_AS100(config-bgp)#network 10.0.1.0 255.255.255.0
ZXR10_AS100(config-bgp)#neighbor 192.168.1.2 remote_as 400
ZXR10_AS100(config-bgp)#neighbor 192.168.1.2 activate
ZXR10_AS100(config-bgp)#neighbor 192.168.1.2 route_map PATH out
ZXR10_AS100(config-bgp)#exit
ZXR10_AS100(config)# ipv4-access-list 1
ZXR10_AS100(config-ipv4-acl)#permit 10.1.0.0 0.0.0.255
ZXR10_AS100(config-ipv4-acl)#exit
ZXR10_AS100(config)#route_map PATH permit 0
ZXR10_AS100(config-route-map)#match ip address 1
ZXR10_AS100(config-route-map)#set as_path prepend 100 100 100 100
ZXR10-AS100(config-route-map)#exit
By means of routing policy, AS_PATH is configured on the advertised route. Thus, the
route from AS 500 to AS 100 is changed.
To view BGP routing table on a router in AS500, use the show ip bgp route command.
ZXR10_AS500#show ip bgp route

6-35


*>10.0.1.0/24 192.168.1.17 20 300 200 100 i
*>10.0.2.0/24 192.168.1.17 20 300 200 100 400 i
*>10.0.3.0/24 192.168.1.17 20 300 200 i
*>10.0.4.0/24 192.168.1.17 0 300 i
*>10.1.0.0/24 192.168.1.17 20 300 200 100 i
>10.1.0.0/24 192.168.1.13 20 400 100 100 100 100 100 i
ZXR10_AS500#show ip bgp route detail 10.1.0.0 255.255.255.0

01:19:50 received from 192.168.1.11 (10.0.2.1)
origin i,nexthop 192.168.1.13,
as path [400 100 100 100 100 100]
AS 500 realizes that there are 6 ASs passing by the route from AS 400 to AS 100, and
3 ASs passing by the route if it is from AS 300 to AS 100. Therefore, BGP will select the
routing that passes the less ASs if other priorities are the default settings. That is, the
routing that is from AS 300 to AS 100 satisfies the configuration requirement.
6.3.5.6 Selecting Routes by Using LOCAL_PREF

Local_PREF is a well-known discretionary attribute. The default value is 100.
When a BGP router broadcasts routes to other BGP routers in the same AS, this attribute
shall be used. The value of attribute has influence on the path priority directly. The route
with the highest priority will be chosen as the optimum path. This attribute also affects the
local outbound traffic, and it is only used for local AS, that is, other ASs will not affected by
this attribute. Local-PREF is only exchanged between IBGP neighbors, and it will not be
advertised to EBGP neighbors.

sequence-number> ]
2 ZXR10(config)#ipv4-access-list < acl-name> This defines and names an ACL.
ZXR10(config-ipv4-acl)#rule < rule-id > { permit | deny} { < This defines a rule of an ACL.
ZXR10(config-route-map)#set local-preference < value> This specifies priority value for AS.
0–4294967295, and the default
value is 100.
6-36

< map-tag> The name of route mapping, the length is 1–31 characters.
< acl-name> ACL list name, the length is l–31 characters.
permit Permit the matched packets to pass
deny Deny the matched packets to pass
Select Route by Using LOCAL_PREF Attribute

As shown in Figure 6-13, R1, R2 and R3 use IBGP full connection. Use BGP LOCAL-PREF
attribute to meet the requirement that all egress services arrive AS300 by using the egress
of R1.
Figure 6-13 Select Route by Using LOCAL_PREF Attribute
6-37

R1(config-bgp)#neighbor 172.16.1.2 activate
R1(config-bgp)#neighbor 172.16.1.2 route-map Local_Pref in
R1(config-bgp)#exit
R1(config)# ipv4-access-list 1
R1(config-ipv4-acl)#permit any
R1(config)#route-map Local_Pref permit 10

R1(config-route-map)#set local-preference 200
R1(config-route-map)#end
R2(config-bgp)#neighbor 192.168.1.10
R2(config-bgp)#neighbor 172.16.0.2 route-map Local_Pref in
R2(config-ipv4-acl)#permit any
R2(config)#route-map Local_Pref permit 10

R2(config-route-map)#end
6-38



*>i 10.0.0.0/24 192.168.1.6 200 200 300 i
*i 10.0.0.0/24 192.168.1.2 100 200 300 i

01:24:10 received from 192.168.1.2 (172.16.0.1)
origin i,nexthop 192.168.1.2, localpref 100,
as path [300]
01:21:46 received from 192.168.1.6 (172.16.1.1)
origin i,nexthop 192.168.1.6, localpref 200,
as path [300]
Modify the Local_Pref value of R3 to specify an egress for the service. In this example,
the traffic going to 10.0.0.0/24 of AS300 are forwarded by R1 preferably. Therefore, the
route coming from R1 has higher Local_Pref value.
6.3.5.7 Selecting Route by Using MED

MED is an optional nontransitive attribute. MED is used to affect the inbound service flow.
When there are many ingress in an AS, the one with the smallest MED will be the ingress
for external neighbor router entering AS. The default MED value is 0.

sequence-number> ]
2 ZXR10(config)#ipv4-access-list < acl-name> This creates and names an ACL.
ZXR10(config-ipv4-acl)#rule < rule-id > { permit | deny} { < This defines the rule of standard
source> [ < source-wildcard> ] | any} ACL.
ZXR10(config-route-map)#set metric [ + | -] < metric-value> This sets the metric of BGP.
< map-tag> The name of route mapping, the length is 1–31 characters
6-39

< acl-name> ACL list name, the length is l–31 characters.
permit Permit the matched packets to pass
deny Deny the matched packets to pass
+ Add metric value
- Decrease metric value
< metric-value> MED value, the range is 0–4294967295
Select Route by Using MED

As shown in Figure 6-14, AS 100 and AS 400 are interconnected by two links. Configure
AS100 to make AS400 select link 1 to route to AS100 preferably.
Figure 6-14 Select Route by Using MED
Configuration on R1 (Configuration of port and IGP are omitted):

6-40


R1(config-bgp)#neighbor 192.168.1.2 route-map Med1 out
R1(config-bgp)#neighbor 192.168.2.2 route-map Med2 out
R1(config-bgp)#exit
R1(config)#route-map Med1 permit 10
R1(config)#route-map Med2 permit 10
R2(config-bgp)#exit
R2(config)#show ip bgp route

*>10.0.1.0/24 192.168.2.1 50 20 100 i
*10.0.1.0/24 192.168.1.1 100 20 100 i
*>10.0.2.0/24 0.0.0.0 0 i
R2(config)#show ip bgp route detail 10.0.1.0 255.255.255.0

01:44:13 received from 192.168.2.1 (10.0.1.1)
as path [100]
01:47:25 received from 192.168.1.1 (10.0.1.1)
6-41


as path [100]
By means of MED modification, R2 selects the link 1 (MED value is 50 smaller than that
of link 2) to route to AS 100 preferably.
6.3.5.8 Configuring BGP Community String Attributes

The community string attributes are optional transitive attributes. The community is a group
of destination routes with one or more common features. It has 4 bytes, the first 2 bytes
are AS number and the last 2 bytes are identifier. When aggregate community routes, the
aggregated route inherits all the community attributes from all routes.
The definitions of several well-known community attributes are given as follows:

l no-export: Advertisement to EBGP neighbors is disabled.
l no-advertise: Advertisement to any BGP neighbors is disabled.
l no-export-subconfed: Forbid to advertise the route with this attribute to confederation
outside.
l local-AS: Advertise the route with this attribute to BGP neighbor routers in AS.
l Internet: Advertise the route with this attribute to all other routers.
To configure BGP community string attributes on ZXR10 M6000, perform the following
steps.
1 ZXR10(config)#route-map < map-tag> [ permit | deny] [ < This creates a route map.
sequence-number> ]
2 ZXR10(config)#ip prefix-list < prefix-list-name> [ seq < seq-number> This configures a list of address
] { permit | deny} < network-num> < len> [ ge < value> | le < value> ] prefixes. It is used to filter the route
advertisements.
ZXR10(config-route-map)#set as-path prepend < as-path-number> [ This modifies BGP route AS path.
< as-path-number> ]
ZXR10(config-route-map)#set local-preference < value> This specifies priority for AS path.
ZXR10(config-route-map)#set metric [ + | -] < metric-value> This configures the metric of routing.
ZXR10(config-route-map)#set community { none | [ additive] { This sets community attribute of

no-advertise | no-export | no-export-subconfed | < aa:nn> | < nn> } [ { BGP route.
no-advertise | no-export | no-export-subconfed | < aa:nn> | < nn> } ] }
ZXR10(config-route-map)#set dampening < half-life> < reuse> < This sets BGP route dampening.
suppress> < max-suppress-time>
6-42

< map-tag> The name of route mapping, the length is 1–31 characters.
< prefix-list-name> The name of prefix-list, the length is 1–31 characters
seq < seq-number> Sequence number of prefix-list entry. The matching starts from the
one with smaller value. The range is 1–4294967294
permit If a IP address to be filtered is in the range of prefixes of the entry,

do not perform further matching.
If a IP address to be filtered is not in the range of prefixes of the entry,
perform further matching.
deny If a IP address to be filtered is in the range of prefixes of the entry, the

IP address will be filtered and do not perform further matching.
If a IP address to be filtered is not in the range of prefixes of the entry,
perform further matching.
< network-num> Specify the range of IP address prefixes
< len> Specify the length of mask of IP address, the range is 0–32
ge < value> Specify the matching range of IP address prefixes, and the length
of the prefix of the matched IP address needs to be larger than the
specified value. The value ranges from 0–32
le < value> Specify the matching range of IP address prefixes, and the length of
the prefix of the matched IP address needs to be smaller than the
specified value. The value ranges from 0–32
Marking the Routes with Community

As shown in Figure 6-15, AS600 configures attribute values for the route coming from
different ASs. The attribute of AS300 is 300:1, and attribute of AS400 is 400:1.
6-43

Figure 6-15 Use Community to Control Routes
Configuration on the router in AS300 (Configurations of port and IGP are omitted):
ZXR10_AS300(config-bgp)#neighbor 192.168.1.9 remote-as 200
ZXR10_AS300(config-bgp)#neighbor 192.168.1.18 route-map community out
ZXR10_AS300(config-bgp)#neighbor 192.168.1.18 send-community
ZXR10_AS300(config)#ip prefix-list AS200 seq 5 permit 10.0.3.0 24
ZXR10_AS300(config)#route-map Community permit 10
ZXR10_AS300(config-route-map)#match ip address prefix-list AS200
ZXR10_AS300(config-route-map)#set community 300:1
ZXR10_AS300(config-route-map)#exit
Configuration on the router in AS400 (configurations of port and IGP are omitted):
6-44


ZXR10_AS400(config-bgp)#neighbor 192.168.1.14 route-map community out
ZXR10_AS400(config-bgp)#neighbor 192.168.1.14 send-community
ZXR10_AS400(config)#ipv4-access-list 1
ZXR10_AS400(config-ipv4-acl)#rule 1 permit any
ZXR10_AS400(config-ipv4-acl)#exit
ZXR10_AS400(config)#route-map Community permit 10
ZXR10_AS400(config-route-map)#match ip address 1
ZXR10_AS400(config-route-map)#set community 400:1
Use the show ip bgp route command to view BGP routing table on AS600.
ZXR10_AS600(config)# show ip bgp route

*>10.0.1.0/24 192.168.1.13 20 400 100 i
*>10.0.2.0/24 192.168.1.13 20 400 i
*>10.0.3.0/24 192.168.1.17 20 300 200 i
*10.0.3.0/24 192.168.1.13 20 400 100 200 i
*>10.0.4.0/24 192.168.1.13 20 400 100 200 300 i
ZXR10_AS600(config)#show ip bgp route detail 10.0.3.0 255.255.255.0

00:28:52 received from 192.168.1.17 (10.0.4.1)
community 300:1
as path [300 200]
00:28:54 received from 192.168.1.13 (10.0.2.1)
community 400:1
as path [400 100 200]
The BGP routes received by AS600 device are marked, the routes coming from AS300
are marked as 300:1, and the routes coming from AS400 are marked as 400:1
Filter Routes by Using Community

Configuration requirements: According to the community attribute of AS600, select route
by configuring Local_Pref.
6-45

Configuration on the router in AS600 (configurations of port and IGP are omitted):
ZXR10_AS600(config-bgp)#neighbor 192.168.1.13 route-map Local_Pref in
ZXR10_AS600(config)#route-map Local_Pref permit 10
ZXR10_AS600(config-route-map)#match community-list 1
ZXR10_AS600(config-route-map)#set local-preference 200
ZXR10_AS600(config)#ip community-list 1 permit 400:1
Use the show ip bgp route command to view BGP routing table of AS600.
ZXR10_AS600(config)# show ip bgp route

*>10.0.1.0/24 192.168.1.13 200 20 400 100 i
*>10.0.2.0/24 192.168.1.13 200 20 400 i
*>10.0.3.0/24 192.168.1.13 200 20 400 100 200 i
*10.0.3.0/24 192.168.1.17 20 300 200 i
*>10.0.4.0/24 192.168.1.13 200 20 400 100 200 300 i
BGP select the route with higher Local_Pref value preferably. In this example, the route
from AS400 to 10.0.3.0/24 is selected.
6.3.6 BGP Configuration for Large-scale Network

Neighborhood must be established between every two BGP routers in the same AS to
form full interconnection. In this way, with the increasing of the number of IBGP routers,
the number of neighbors will increment by n×(n-1)/2 (n is the number of IBGP routers).
To reduce the work load of maintenance and configuration, use route reflector and
confederation.
6.3.6.1 Configuring BGP Route Reflector

IBGP routers are not fully connected in an AS, and every IBGP router has more than 100
BGP sessions.
For an AS of a large-scale network, select a IBGP router to be a Route Reflector (RR), and
all other IBGP routers serve as clients. Each client only establishes neighborhood with RR
and then multiple RRs establish neighborhood with each other. All clients reflect routes
through the RR. In this way, the number of neighbors is reduced to n-1. The clients stand
6-46

for that IBGP neighbors which set up full interconnection with the RR. The clients form a
group. IBGP neighbors of the RR whom do not belong to the group are non-clients.
When a route is received by RR, it will be reflected according to the different peer types.
l If the update message is sent by an EBGP neighbor, then advertise it to all clients and
non-clients.
l If the update message is sent by a non-client, then advertise it to clients.
l If the update message is sent by a RRC, then advertise it to all clients and non-clients
except the originator of this update message.
When multiple RRs are available in an AS, divide many RRs belonging to the same AS to
a cluster. An AS can have many clusters, and a cluster has one RR at least.
Note that RR is recommended to use only when every router holds more than 100 BGP
sessions in an AS.
To configure BGP RR on ZXR10 M6000, perform the following steps.

2 ZXR10(config-bgp)#bgp cluster-id { < value> | < ip-address> } This configures the cluster ID of a
RR.
By default, router-ID is the cluster ID.
3 ZXR10(config-bgp)#neighbor [ < ipv4-address> | < peer-group-name> This sets a neighbor or neighbor

] router-refletor-client peer group to route reflector client
peer.
< value> Cluster ID, the range is 1-4294967295
< ip-address> Cluster ID, in dotted decimal notation
< ipv4-address> IPv4 address, in the dotted decimal notation
< peer-group-name> The name of peer-group
Route Reflector Configuration Example

As shown in Figure 6-16, R1, R2 and R3 are IBGP neighbors but they are not fully
connected. Configure a router reflector to make R3 forward the routes received by an
IBGP neighbor to another IBGP neighbor. Considering IBGP neighbors are not fully
interconnected in AS600, configure router reflector to avoid full interconnection.
6-47

Figure 6-16 BGP Route Reflector Configuration Example

R1(config-bgp)#exit

R2(config-bgp)#exit
R3(config-bgp)#bgp cluster-id 3.3.3.3
R3(config-bgp)#neighbor 192.168.1.2 route-reflector-client
R3(config-bgp)#neighbor 192.168.1.6 route-reflector-client
6-48

R3(config-bgp)#exit

*> 10.0.0.0/24 172.16.1.2 20 300 i
*>i 10.0.1.0/24 192.168.1.2 100 200 400 i

05:04:45 received from 192.168.1.5 (192.168.1.1)
origin i,nexthop 192.168.1.2,localpref 100, originator_id 172.16.0.1
cluster_id 3.3.3.3
as path [400]

*>i 10.0.0.0/24 192.168.1.6 100 200 300 i
*> 10.0.1.0/24 172.16.0.2 20 400 i

05:05:19 received from 192.168.1.1 (192.168.1.1)
origin i,nexthop 192.168.1.6,localpref 100, originator_id 172.16.1.1
cluster_id 3.3.3.3
as path [300]
Here, R1 and R2 learn the route from their peers respectively.
6.3.6.2 Configuring BGP Confederation

The function of route confederation is the same to that of RR. The route confederation is
used to reduce the number of BGP neighbor connections in an AS. Route confederation
divides an AS into many sub-ASs, and the IBGP routers in the AS belong to different
sub-ASs. IBGP is established inside each sub-AS, and EBGP is established among
sub-ASs. Sub-ASs are invisible to the external AS.
To configure BGP confederation on ZXR10 M6000, perform the following steps.
6-49


2 ZXR10(config-bgp)#bgp confederation identifier < value> This sets confederation ID, the range
is 1-65535.
3 ZXR10(config-bgp)#bgp confederation peers < value> [ < value> ] This configures the AS number of
confederation peer. The range is
1-65535
Use Confederation to Avoid IBGP Full Connection

As shown in Figure 6-17, use confederation to avoid IBGP full connection in AS600.
Figure 6-17 BGP Confederation Configuration Example

R2(config-bgp)#bgp confederation identifier 600
R2(config-bgp)#bgp confederation peers 65001 65002
R2(config-bgp)#exit
6-50


R4(config-bgp)#bgp confederation identifier 600
R4(config-bgp)#bgp confederation peers 65003
R4(config-bgp)#exit

*>i 10.0.0.0/24 172.16.1.2 100 200 65002 i
*> 10.1.0.0/24 172.16.2.2 20 500 i
The output above shows that there is a route pointing to R4 on R2.

*>10.0.0.0/24 0.0.0.0 0 i
*>10.1.0.0/24 172.16.2.2 100 200 65003 500 i

06:27:14 received from 172.16.1.1 (172.16.1.1)
origin i,nexthop 172.16.2.2,localpref 100,
as path (65003) [500]
The output above shows that there is a route pointing to AS500 on R4.
A larger AS is divided into some smaller ASs, and these samller ASs are connected by
EBGP. Each AS acts as an independent BGP AS to run IBGP.
A complete AS only runs an IGP protocol, and every sub-AS has IGP routing information
of all other sub-ASs.
6.3.6.3 Configuring BGP Route Dampening

BGP provides a mechanism called Route Dampening to reduce the network instability
caused by route flapping. Since the update and cancellation messages are transmitted
6-51

in network continually when route flapping occurs, the bandwidth and router processing
resource are used a lot.
The principle of BGP route dampening is that allocate a penalty of 1000 to route
whenever the route flapping occurs. When the penalty reaches to a suppress-limit, the
advertisement of the route will be suppressed. The penalty decreases geometrically
after passing every half-life-time. When the penalty reduces to the reuse-limit, the route
advertisement dampening will be cancelled.
The following values are used by BGP route dampening.
l Half-life-time: Ranging from 1 to 45 minutes (The default value is 15 minutes)
l Reuse-value: Ranging from 1 to 20000 (The default value is 750)
l Suppress-value: Ranging from 1 to 20000 (The default value is 2000)
l Max-suppress-time: Ranging from 1 to 255 (The default value is four times of the
value of half-life-time)
To configure BGP route dampening on ZXR10 M6000, perform the following steps.

2 ZXR10(config-bgp)#bgp dampening [ < half-life> < reuse> < This activates BGP route dampening
suppress> < max-suppress-time> | route-map < map-tag> ] and modifies the factors of route
dampening.
< half-life> Half-life, the range is 1-45, the default value is 15 and the unit is
minute.
< reuse> Reuse value, the range is 1-20000, and the default value 750
< suppress> Route suppress value, the range is 1-20000, and the default value
is 2000
< max-suppress-time> The maximum suppress time, the range is 1-255, the default value is
60, and the unit is minute
< map-tag> Available route mapping tag, the length is 1-31 characters.
Enable Route Dampening Function on Router

Enable BGP route dampening function on router. Set the half-life is 30 minutes, the re-use
value is 500, and the suppress value is 2000, the maximum suppress time is 120 minutes.
ZXR10(config-bgp)#bgp dampening 30 500 2000 120
ZXR10(config-bgp)#network 203.250.15.0 255.255.255.0
ZXR10(config-bgp)#neighbor 192.208.10.5 remote-as 300
6-52

ZXR10(config-bgp)#exit
Use the show ip bgp protocol command to view the configuration of route dampening on
router.
ZXR10#show ip bgp protocol
BGP router ID is 1.1.1.2, Local as is 1
Hold time is 90 seconds, KeepAlive time is 30 seconds
Default local preference is 100
Default export metric is 0
IGP synchronization is disabled
Default information advertise is disabled
Always compare med is disabled
Fast fallover is enabled
Client-to-client reflection is enabled
Ipv4 unicast is activated
Router target is filtered
Route dampening enabled, halflife-time is 30,
reuse is 500, suppress is 2000, max-suppress-time is 120
Distance : external 20 internal 200
Here, the route dampening mechanism is activated. The half-life is 30 minutes, the reuse
value is 500, and the suppress value is 2000, and the maximum suppress time is 120
minutes.
6.3.6.4 Configuring BGP Peer Group

BGP peer group is to implement cluster management to BGP peer, which adds peers
into the uniform peer group and configure them. In this way, reduce the work load of
peer configuration, simply the configuration process and manage peers in classification,
improve the reliability and convenience of maintenance.

2 ZXR10(config-bgp)#neighbor < word> peer-group This creates a BGP peer group. The
length of peer group ranges from 1
to 16 characters.
3 ZXR10(config-bgp)#neighbor < word> remote-as < number> This configures an AS number of a

neighbor peer group.
4 ZXR10(config-bgp)#neighbor < ip-address> peer-group < word> This adds a neighbor to BGP peer
group.
Descriptions of the parameter in Step 2:
6-53

< word> Name of peer group, the length is 1-16 characters
< word> Name of peer group, the length is 1-16 characters.
< number> AS of neighbor, the range is 1-65535 or 1-4294967295
< ip-address> IPv4 address of neighbor, in dotted decimal notation
< word> Name of peergroup, the length is 1-16 characters
Example
ZXR10(config-bgp)#neighbor zte peer-group
ZXR10(config-bgp)#neighbor zte remote-as 100
ZXR10(config-bgp)#neighbor 192.168.0.2 peer-group zte
ZXR10(config-bgp)#neighbor 192.168.0.3 peer-group zte
6.3.7 BGP Maintenance

6.3.7.1 Common Maintenance Commands for Viewing Information
When BGP route faults occur, use debugging commands to locate and solve fault. show
commands are common-used commands. The show commands can be used to view the
current status of a BGP neighbor and the BGP routing information learned by a router.
ZXR10 M6000 provides the following commands to view BGP information.
Command Function
ZXR10#show ip bgp protocol This displays the configuration of local

BGP module.
ZXR10#.show ip bgp neighbor This displays BGP adjacency and the

current neighbor status.
ZXR10#show ip bgp route [ network < ip-address> [ mask < net-mask> ] ] This displays the entries in the BGP
routing table.
ZXR10#show ip bgp summary This displays the status of all BGP

neighbor connections.
6-54

An example of the show ip bgp protocol command output is shown below.

ZXR10#show ip bgp protocol
BGP router ID is 1.1.1.2, Local as is 1
Hold time is 90 seconds, KeepAlive time is 30 seconds
Default local preference is 100
Default export metric is 0
IGP synchronization is disabled
Default information advertise is disabled
Always compare med is disabled
Fast fallover is enabled
Client-to-client reflection is enabled
Ipv4 unicast is activated
Router target is filtered
Route dampening is disabled
Distance : external 20 internal 200
Hold time is 90 seconds, KeepAlive time is The hold time is 90 seconds, and the keep-alive time is 30 seconds.
30 seconds
Default local preference is 100 Local priority is 100 by default
Default export metric is 0 export metric value is 0 by default
Distance : external 20 internal 200 External administrative distance is 20 and the internal administrative
distance is 200
An example of the show ip bgp neighbor command output is shown below.

ZXR10#show ip bgp neighbor
Neighbor capabilities:
Route refresh: advertised and received
Address family IPv4 Unicast: advertised and received
All received 10 messages
0 updates, 0 errs
1 opens, 0 errs
9 keepalives
0 vpnv4 refreshs, 0 ipv4 refreshs, 0 ipv4 multicast refreshs,
0 ipv6 refreshs, 0 errs
0 notifications, 0 other errs
After last established received 8 messages
0 updates, 0 errs
6-55

0 opens, 0 errs
8 keepalives
0 ipv6 refreshs, 0 errs
All sent 10 messages
0 updates, 1 opens, 9 keepalives
0 ipv6 refreshs, 0 notifications
After last established sent 8 messages
0 updates, 0 opens, 8 keepalives
0 ipv6 refreshs, 0 notifications
For address family: IPv4 Unicast

All received nlri 0, unnlri 0, 0 accepted prefixes
All sent nlri 0, unnlri 0, 0 advertised prefixes
maximum limit 4294967295
Minimum time between advertisement runs is 30 seconds
Minimum time between origin runs is 15 seconds
……
BGP neighbor is 129.213.1.2, remote AS The IP address is the peer address used by TCP connection between
65001, external link a pair of BGP peers. The peer belongs to AS65001, and it uses
EBGP connection.
BGP version 4, remote router ID BGP-4 is used. Router-ID of the peer BGP router is 129.213.1.2.
129.213.1.2
BGP state = Established, up for 00:04:21 The neighbor state is Established. The session is set up for 4 minutes
21 seconds already.
hold time is 90 seconds, keepalive interval The hold time is 90 seconds, and the keepalive time is 30 seconds.
is 30 seconds
Neighbor capabilities: The following content describes The capability of the peer
Route refresh: advertised and received The peer supports route refreshing.
Address family IPv4 Unicast: advertised The peer supports unicast NLRI.
and received
6-56

All received 10 messages 10 messages are received in total, including 1 open message, 9
0 updates, 0 errs keepalive messages. VPNV4 route update message is not received.
1 opens, 0 errs There is no IPv4 route update, Notification message and error
9 keepalives message.
0 vpnv4 refreshs, 0 ipv4 refreshs, 0 ipv4
multicast refreshs, 0 ipv6 refreshs, 0 errs
After last established received 8 messages 8 messages have been received since the last neighborhood
0 updates, 0 errs establishment. They are keepalive messages.
0 opens, 0 errs
8 keepalives
multicast refreshs, 0 ipv6 refreshs, 0 errs
All sent 10 messages 10 messages are sent in total, including 0 update message, 1 open
0 updates, 1 opens, 9 keepalives message and 9 keepalive messages.
multicast refreshs, 0 ipv6 refreshs, 0
notifications
After last established sent 8 messages 0 8 messages have been sent in total since the last neighborhood
updates, 0 opens, 8 keepalives 0 vpnv4 establishment, including 0 update message, 0 open message and 8
refreshs, 0 ipv4 refreshs, 0 ipv4 multicast keepalive messages.
refreshs, 0 ipv6 refreshs, 0 notifications
For address family: IPv4 Unicast Unicast IPv4 route is described as follow:
All received nlri 0, unnlri 0, 0 accepted NLRI and unnlri messages are not received. The prefix of unicast is
prefixes not received either.
All sent nlri 0, unnlri 0, 0 advertised prefixes NLRI and unnlri message are not sent. A prefix of unicast is
advertised.
Minimum time between advertisement runs The minimum update interval is 30 seconds.
is 30 seconds
Connections established 1 BGP connection with the peer is established once already.
Local host: 129.213.1.1, Local port: 179 Local IP socket, including local IP address and TCP port number
Foreign host: 129.213.1.2, Foreign port: The peer IP socket, including the peer IP address and TCP port
1024 number
An example of the show ip bgp route command output is shown below.

ZXR10#show ip bgp route
6-57


*>10.0.1.0/24 192.168.2.1 50 20 100 i
*10.0.1.0/24 192.168.1.1 100 20 100 i
*>10.0.2.0/24 0.0.0.0 0 i
ZXR10(config)#show ip bgp route detail 10.0.1.0 255.255.255.0

01:44:13 received from 192.168.2.1 (10.0.1.1)
as path [100]
01:47:25 received from 192.168.1.1 (10.0.1.1)
as path [100]
l The symbol * indicates the route is available.
l The symbol > indicates the route is the best choice.
l The symbol i indicates this is a IBGP route.
l The route without “i” indicates this is a EBGP route or local route.
l The address under the entry of Next-hop is the next-hop address of BGP route. If the
address is full zero, that means this route is generated by router itself.
l The value under the Local-Pre is the priority level of route which is learned by BGP.
The default value is 100.
l The field Path indicates the origin of this route. Three types: IGP, EGP and incomplete.
The result shows that two routes arriving 10.0.1.0/24 are valid. The next-hop addresses
are 192.168.2.1 and 192.168.1.1. The optimum route is the route whose next hop is
192.168.2.1, because its metric value is 50, less then another one.
Dest Destination address
Next-hop The next-hop of BGP route. The next-hop represented as full zero
means that the route is generated by local router itself.
Metric Metric value
LocPrf The local priority of route learnt by BGP
RtPrf Route priority
Path Route source, there are three kinds, IGP, EGP and incomplete
An example of the show ip bgp summary command output is shown below.

ZXR10#show ip bgp summary
Neighbor Ver As MsgRcvd MsgSend Up/Down(s) State/PfxRcd
1.1.1.1 4 2 14 13 00:06:06 6
1.1.1.3 4 1 6 9 00:02:33 2
6-58

Neighbor BGP neighbor
Ver BGP version
As AS number of neighbor
MsgRcvd The number of messages received by BGP
MsgSend The number of messages sent by BGP
Up/Down(s) The time for setting up connection
State/PfxRcd A number will be displayed if the neighborhood is set up. It indicates

how many routes are received. A character will be displayed if the
neighborhood is failed to set up.
6.3.7.2 Common Maintenance Commands for Debugging

ZXR10 M6000 provides the following commands to debug BGP.
Command Function
ZXR10#debug ip bgp in This traces and displays the notification

packets received by BGP, and it lists
error ID and sub error ID.
ZXR10#debug ip bgp out This traces and displays the notification

packets sent by BGP and it lists error
ID and sub error ID.
ZXR10#debug ip bgp dampening It traces the condition of BGP route

dampening.
ZXR10#debug ip bgp keepalieves It traces the processing of BGP

KeepAlive messages.
ZXR10#debug ip bgp updates It traces the processing of BGP update

messages. It can traces and prints the
processing of a specified peer.
ZXR10#debug ip bgp events It traces and shows the transferring of

BGP connection state.
ZXR10# debug all bgp It traces and shows the related

information of all BGP debug
commands.
ZXR10#show debug bgp It shows the configuration of debug

commands.
An example of the debug ip bgp events command output is shown below.
ZXR10#terminal monitor
6-59

ZXR10#debug ip bgp events

BGP events debugging is on
04:10:07: BGP: 192.168.1.2 reset due to Erroneous BGP Open received
04:10:07: BGP: 192.168.1.2 went from Connect to Idle
04:10:08: BGP: 192.168.1.2 went from Idle to Connect
04:10:13: BGP: 192.168.1.2 went from Connect to OpenSent
04:10:13: BGP: 192.168.1.2 went from OpenSent to OpenConfirm
04:10:13: BGP: 192.168.1.2 went from OpenConfirm to Established
The result shows that the transferring process of BGP status is

Connect→Idle→Connect→OpenSent→OpenConfirm→Established
6.3.7.3 BGP Alarm Message

For some important faults, system gives alarms. The common BGP alarms are listed
below.
Alarm Code Description
INFORM_BGP_ACTIVE_GET_TCB Fail to acquire Transmission Control Block (TCB) for automatic BGP
connection setting up
INFORM_BGP_IF_CHANGE BGP interface is down, the neighborhood is interrupted.
INFORM_BGP_HOLD_EXPIRED Hold timer of neighbor expires
A complete alarm message contains alarm type, alarm code and alarm additional
information. The alarm code indicates what is the alarm. Background can know what
happens according to the value of alarm code. Every alarm message can bring some
additional information, such as alarm reason. For detailed BGP alarm message, refer to
the related alarm message manual.
6.4 BGP Configuration Examples

6.4.1 BGP FRR Configuration Example
FRR is to provide backup protection for important nodes and links when the nodes or links
become invalid in the network. It realizes fast re-routing, thus decreases the influence to
the traffic caused by the invalid nodes or links to make the traffic recovered quickly.
There are two typical network structures of FRR, as shown below.
1. The typical network structure of node protection is shown in Figure 6-18.
6-60

Figure 6-18 Network Structure of FRR Node Protection
2. The typical network structure of link protection is shown in Figure 6-19. IS-IS neighbor
topology is established on the two links. One of the link has high priority and the other
link has lower priority.
Figure 6-19 Network Structure of FRR Link Protection
1. Configure routing protocols.
2. On the nodes forming FRR relationship, there are more than two next hops reachable
to the same destination, and the routes to the same destination have different costs.
3. Enable FRR function in related routing protocol on corresponding devices.
The detailed configuration is described below.
1. Configuration of FRR node protection
Take BGP in Figure 6-18 as an example. First, establish EBGP neighbor relationship
between the routers through real interfaces. Enable FRR function on R1. Set the
routes advertised by R3 that go through the path R1—R2—R3 as the optimal routes.
R1(config-bgp)#bgp frr
R1(config-bgp)#exit
R1(config)#route-map lt
R1(config-bgp)#neighbor 172.16.1.2 route-map lt in
6-61

R2(config-bgp)#exit
R3(config-bgp)#exit
2. Configuration of FRR link protection
Take IS-IS protocol in Figure 6-19 as an example. For details, please refer to the “IS-IS
FRR Configuration Example” topic.
Use the show ip forwarding backup route command to check whether the FRR
configuration takes effect.
The result of BGP FRR on R1 is shown below.
R1#show ip forwarding backup route
IPv4 Backup Routing Table:
1.1.1.150/32 172.16.20.2 gei_0/2/1/2 BGP 20 0
The result of IS-IS FRR on R1 is shown below.
6.4.2 BGP Configuration Example One

As shown in Figure 6-20, R1 and R2 belong to AS1, R4 belongs to AS2, and R3 and R5
belong to AS3. Loopback address of each router is shown below.
Router Loopback Address
R1 1.1.1.2/32
R2 1.1.1.3/32
R3 1.1.1.4/32
R4 1.1.1.1/32
R5 1.1.1.5/32
6-62

Figure 6-20 BGP Configuration Example One
1. Set up IBGP connection between R1 and R2; set up EBGP connection between R1
and R4; Set up EBGP connection between R2 and R3.
2. R3 and R5 are interconnected by static route and OSPF.
3. R3 distributes OSPF route to BGP, and configure Metric value of the OSPF route is
122.
4. There are some static routes pointing to 192.168.0.0/24, 192.168.1.0/24,
192.168.2.0/24, 192.168.3.0/24 and 192.168.100.0/24 and 10.1.1.0/24 on R4.
5. R4 distributes its static routes to BGP and sets Metric value as 33. The route of
192.168.100.0/24 requires filtering.
6. Implement route aggregation on R4 and advertise the detailed routes.
7. Make sure that PCs in AS2 can intercommunicate with 20.1.1.0/24 connecting to R5.
8. All routers use the address of Loopback1 as source address for connection, and the
mask of interconnection address is 30 bits.
1. Configure static route.
2. Configure IGP (OSPF).
3. Enable BGP.
4. Configure neighbor.
5. Modify source address.
6. Configure route aggregation.
7. Configure multi-hops.
8. Cancel synchronization.
9. Configure route-map to filter the specified route.
10. Modify the Metric value of route to be advertised.
6-63


R1(config-if)#exit
R1(config-if)#exit
R1(config-if)#exit
R1(config-bgp)#neighbor 1.1.1.1 update-source loopback1
R1(config-bgp)#exit
R1(config)#ip route 1.1.1.1 255.255.255.255 11.1.1.1
R1(config)#ip route 1.1.1.3 255.255.255.255 13.1.1.2
R2(config-if)#exit
R2(config-if)#exit
R2(config-if)#exit
R2(config-bgp)#exit
6-64

R2(config)#ip route 1.1.1.4 255.255.255.255 12.1.1.1

R2(config)#ip route 1.1.1.2 255.255.255.255 13.1.1.1
R3(config-if)#exit
R3(config-if)#exit
R3(config-if)#exit
R3(config-bgp)#redistribute ospf-int metric 122
R3(config-bgp)#exit
R3(config)#ip route 1.1.1.3 255.255.255.255 12.1.1.2
R4(config-if)#exit
R4(config-if)#negotiation auto
R4(config-if)#exit
R4(config-if)#exit
R4(config-bgp)#redistribute static
R4(config-bgp)#aggregate-address 192.168.0.0 255.255.252.0 count 0 as-set
6-65


R4(config-bgp)#neighbor 1.1.1.2 route-map test-static out
R4(config-bgp)#exit
R4(config)#ip route 1.1.1.2 255.255.255.255 11.1.1.2
R4(config)#ip route 192.168.100.0 255.255.255.0 10.1.1.2
R4(config)#ip route 192.168.1.0 255.255.255.0 10.1.1.2
R4(config)#ip route 192.168.0.0 255.255.255.0 10.1.1.2
R4(config)#ip route 192.168.3.0 255.255.255.0 10.1.1.2
R4(config)#ip route 192.168.2.0 255.255.255.0 10.1.1.2
R4(config-ipv4-acl)# rule 1 permit 192.168.0.0 0.0.3.255
R4(config-ipv4-acl)# rule 2 permit 10.1.1.0 0.0.0.255
R4(config)#route-map test-static permit 10
R5(config-if)#exit
R5(config)#interface null1
R5(config-if)#exit
R5(config-if)#exit
R5(config-if)#exit
R5(config)#ip route 0.0.0.0 0.0.0.0 14.1.1.1
View BGP routing table and route forwarding table on R1.
R1# show ip bgp route

6-66


*>1.1.1.2/32 1.1.1.2 0 ?
*>10.1.1.0/24 1.1.1.1 33 20 2 i
*>11.1.1.0/30 11.1.1.2 0 ?
*>I 12.1.1.0/30 1.1.1.3 100 200 ?
*>13.1.1.0/30 13.1.1.1 0 ?
*i 13.1.1.0/30 1.1.1.3 100 200 ?
*>i 14.1.1.0/30 1.1.1.3 0 100 200 3 ?
*>i 20.1.1.0/24 1.1.1.3 122 100 200 3 ?
*>192.168.0.0/22 1.1.1.1 33 20 2 i
*>192.168.0.0/24 1.1.1.1 33 20 2 ?
*>192.168.1.0/24 1.1.1.1 33 20 2 ?
*>192.168.2.0/24 1.1.1.1 33 20 2 ?
*>192.168.3.0/24 1.1.1.1 33 20 2 ?

IPv4 Routing Table:
1.1.1.1 255.255.255.255 11.1.1.1 fei-0/1/0/1 static 1 0
1.1.1.3 255.255.255.255 13.1.1.2 fei-0/2/0/1 static 1 0
10.1.1.0 255.255.255.0 11.1.1.1 fei-0/1/0/1 bgp 20 33
11.1.1.0 255.255.255.252 11.1.1.2 fei-0/1/0/1 direct 0 0
11.1.1.2 255.255.255.255 11.1.1.2 fei-0/1/0/1 address 0 0
12.1.1.0 255.255.255.252 13.1.1.2 fei-0/2/0/1 bgp 200 0
13.1.1.0 255.255.255.252 13.1.1.1 fei-0/2/0/1 direct 0 0
13.1.1.1 255.255.255.255 13.1.1.1 fei-0/2/0/1 address 0 0
14.1.1.0 255.255.255.252 13.1.1.2 fei-0/2/0/1 bgp 200 0
20.1.1.0 255.255.255.0 13.1.1.2 fei-0/2/0/1 bgp 200 122
192.168.0.0 255.255.252.0 11.1.1.1fei-0/1/0/1 bgp 20 33
192.168.0.0 255.255.255.0 11.1.1.1fei-0/1/0/1 bgp 20 33
192.168.1.0 255.255.255.0 11.1.1.1fei-0/1/0/1 bgp 20 33
192.168.2.0 255.255.255.0 11.1.1.1fei-0/1/0/1 bgp 20 33
192.168.3.0 255.255.255.0 11.1.1.1fei-0/1/0/1 bgp 20 33


*>1.1.1.3/32 1.1.1.3 0 ?
*>i 10.1.1.0/24 1.1.1.2 33 100 200 2 i
6-67

*>i 11.1.1.0/30 1.1.1.2 100 200 ?

*> 12.1.1.0/30 12.1.1.2 0 ?
* 12.1.1.0/30 1.1.1.4 0 20 3 ?
*> 13.1.1.0/30 13.1.1.2 0 ?
*i 13.1.1.0/30 1.1.1.2 100 200 ?
*>14.1.1.0/30 1.1.1.4 0 20 3 ?
*>20.1.1.0/24 1.1.1.4 122 20 3 ?
*>i 192.168.0.0/22 1.1.1.2 33 100 200 2 i
*>i 192.168.0.0/24 1.1.1.2 33 100 200 2 ?
*>i 192.168.1.0/24 1.1.1.2 33 100 200 2 ?
*>i 192.168.2.0/24 1.1.1.2 33 100 200 2 ?
*>i 192.168.3.0/24 1.1.1.2 33 100 200 2 ?

IPv4 Routing Table:
1.1.1.2 255.255.255.255 13.1.1.1 fei-0/1/0/1 static 1 0
1.1.1.4 255.255.255.255 12.1.1.1 fei-0/2/0/1 static 1 0
10.1.1.0 255.255.255.0 13.1.1.1 fei-0/1/0/1 bgp 200 33
11.1.1.0 255.255.255.252 13.1.1.1 fei_1/11 bgp 200 0
12.1.1.0 255.255.255.252 12.1.1.2 fei-0/2/0/1 direct 0 0
12.1.1.2 255.255.255.255 12.1.1.2 fei-0/2/0/1 address 0 0
13.1.1.0 255.255.255.252 13.1.1.2 fei-0/1/0/1 direct 0 0
13.1.1.2 255.255.255.255 13.1.1.2 fei-0/1/0/1 address 0 0
14.1.1.0 255.255.255.252 12.1.1.1 fei-0/2/0/1 bgp 20 0
20.1.1.0 255.255.255.0 12.1.1.1 fei-0/2/0/1 bgp 20 122
192.168.0.0 255.255.252.0 13.1.1.1 fei-0/1/0/1 bgp 200 33
192.168.0.0 255.255.255.0 13.1.1.1 fei-0/1/0/1 bgp 200 33
192.168.1.0 255.255.255.0 13.1.1.1 fei-0/1/0/1 bgp 200 33
192.168.2.0 255.255.255.0 13.1.1.1 fei-0/1/0/1 bgp 200 33
192.168.3.0 255.255.255.0 13.1.1.1 fei-0/1/0/1 bgp 200 33


*>1.1.1.4/32 1.1.1.4 0 ?
*>10.1.1.0/24 1.1.1.3 20 1 2 i
*>11.1.1.0/30 1.1.1.3 20 1 ?
*>12.1.1.0/30 12.1.1.1 0 ?
*12.1.1.0/30 1.1.1.3 20 1 ?
*>13.1.1.0/30 1.1.1.3 20 1 ?
6-68

*>14.1.1.0/30 14.1.1.1 0 ?
*>20.1.1.0/24 14.1.1.2 122 110 ?
*>192.168.0.0/22 1.1.1.3 20 1 2 ?
*>192.168.0.0/24 1.1.1.3 20 1 2 ?
*>192.168.1.0/24 1.1.1.3 20 1 2 ?
*>192.168.2.0/24 1.1.1.3 20 1 2 ?
*>192.168.3.0/24 1.1.1.3 20 1 2 ?

IPv4 Routing Table:
1.1.1.3 255.255.255.255 12.1.1.2 fei-0/1/0/1 static 1 0
10.1.1.0 255.255.255.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
11.1.1.0 255.255.255.252 12.1.1.2 fei-0/1/0/1 bgp 20 0
12.1.1.0 255.255.255.252 12.1.1.1 fei-0/1/0/1 direct 0 0
12.1.1.1 255.255.255.255 12.1.1.1 fei-0/1/0/1 address 0 0
13.1.1.0 255.255.255.252 12.1.1.2 fei-0/1/0/1 bgp 20 0
14.1.1.0 255.255.255.252 14.1.1.1 fei-0/2/0/1 direct 0 0
14.1.1.1 255.255.255.255 14.1.1.1 fei-0/2/0/1 address 0 0
20.1.1.0 255.255.255.0 14.1.1.2 fei-0/2/0/1 ospf 110 2
192.168.0.0 255.255.252.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
192.168.0.0 255.255.255.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
192.168.1.0 255.255.255.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
192.168.2.0 255.255.255.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
192.168.3.0 255.255.255.0 12.1.1.2 fei-0/1/0/1 bgp 20 0
R3#show ip route forwarding ospf

IPv4 Routing Table:
20.1.1.0 255.255.255.0 14.1.1.2 vlan2 ospf 110 2

R4# show ip bgp route

*>1.1.1.1/32 1.1.1.1 0 ?
*>1.1.1.2/32 11.1.1.2 1 ?
*>10.1.1.0/24 10.1.1.1 0 i
*>11.1.1.0/30 11.1.1.1 0 ?
*11.1.1.0/30 1.1.1.2 20 1 ?
*>12.1.1.0/30 1.1.1.2 20 1 ?
*>13.1.1.0/30 1.1.1.2 20 1 ?
6-69

*>14.1.1.0/30 1.1.1.2 20 1 3 ?
*>20.1.1.0/24 1.1.1.2 20 1 3 ?
*>192.168.0.0/22 0.0.0.0 254 i
*>192.168.0.0/24 10.1.1.2 1 ?
*>192.168.1.0/24 10.1.1.2 1 ?
*>192.168.2.0/24 10.1.1.2 1 ?
*>192.168.3.0/24 10.1.1.2 1 ?
*>192.168.100.0/24 10.1.1.2 1 ?

IPv4 Routing Table:
1.1.1.2 255.255.255.255 11.1.1.2 fei-0/1/0/1 static 1 0
10.1.1.0 255.255.255.0 10.1.1.1 fei-0/2/0/1 direct 0 0
10.1.1.1 255.255.255.255 10.1.1.1 fei-0/2/0/1 address 0 0
11.1.1.0 255.255.255.252 11.1.1.1 fei-0/1/0/1 direct 0 0
11.1.1.1 255.255.255.255 11.1.1.1 fei-0/1/0/1 address 0 0
12.1.1.0 255.255.255.252 11.1.1.2 fei-0/1/0/1 bgp 20 0
13.1.1.0 255.255.255.252 11.1.1.2 fei-0/1/0/1 bgp 20 0
14.1.1.0 255.255.255.252 11.1.1.2 fei-0/1/0/1 bgp 20 0
20.1.1.0 255.255.255.0 11.1.1.2 fei-0/1/0/1 bgp 20 0
192.168.0.0 255.255.255.0 10.1.1.2 fei-0/2/0/1 static 1 0
192.168.1.0 255.255.255.0 10.1.1.2 fei-0/2/0/1 static 1 0
192.168.2.0 255.255.255.0 10.1.1.2 fei-0/2/0/1 static 1 0
192.168.3.0 255.255.255.0 10.1.1.2 fei-0/2/0/1 static 1 0
192.168.100.0 255.255.255.0 10.1.1.2 fei-0/2/0/1static 1 0
Test network connectivity between R4 and R5.

R4#ping 20.1.1.1
sending 5,100-byte ICMP echos to 20.1.1.1,timeout is 2 seconds.
!!!!!
ZXR10_R4#trace 20.1.1.1
tracing the route to 20.1.1.1
1 11.1.1.2 20 ms <20ms <20ms
2 13.1.1.2 <20ms <20ms <20ms
3 12.1.1.1 <20ms <20ms <20ms
4 14.1.1.2 <20ms <20ms <20ms
[finished]
R5#ping 10.1.1.2
sending 5,100-byte ICMP echos to 10.1.1.2,timeout is 2 seconds.
!!!!!
6-70

R5#trace 10.1.1.2
tracing the route to 10.1.1.2
1 14.1.1.1 <20ms <20ms <20ms
2 12.1.1.2 <20ms <20ms <20ms
3 13.1.1.1 <20ms <20ms <20ms
4 11.1.1.1 <20ms <20ms <20ms
5 * * *
[finished]
Test network connectivity on a PC (IP address is 10.1.1.2 255.255.255.0)

C:\Documents and Settings\Administrator>ping 20.1.1.1
Pinging 20.1.1.1 with 32 bytes of data:
Reply from 20.1.1.1: bytes=32 time=1ms TTL=251
Ping statistics for 20.1.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
C:\Documents and Settings\Administrator>tracert 20.1.1.1

Tracing route to 20.1.1.1 over a maximum of 30 hops
1 <1 ms 6 ms <1 ms 10.1.1.1
2 1 ms 1 ms 1 ms 11.1.1.2
3 1 ms 1 ms 1 ms 13.1.1.2
4 1 ms 1 ms 1 ms 12.1.1.1
5 1 ms 1 ms 1 ms 20.1.1.1
Trace complete.
The test results above show that the communication of specified network segment between
AS2 and AS3 is normal.
6.4.3 BGP Configuration Example Two

As shown in Figure 6-21, R4 and R1 set up EBGP neighborhood, R1 and R2 set up IBGP
neighborhood, R2 and R5 set up multi-hops EBGP neighborhood. Here, suppose that
there are four static routes exist on R4.
R4 only advertises the network segment 192.16.0.0/16 by aggregation, and it uses

route-map to forbid BGP to advertise the network segment 170.16.10.0/24. R2 and R5
set up EBGP multi-hop connection through R3. Make sure that the addresses used by
two routers (R2 and R5) to establish neighborhood can ping each other.
6-71

Figure 6-21 BGP Configuration Example
R2(config)#ip route 183.16.0.0 255.255.0.0 173.16.2.1
R4(config-bgp)#exit
R4(config-bgp)#redistribute static
R4(config-bgp)#aggregate-address 192.16.0.0 255.255.0.0 count 0
as-set summary-only
R4(config-bgp)#neighbor 172.16.20.2 route-map torouter1 out
R4(config-bgp)#exit
R4(config-ipv4-acl)#rule 1 deny 170.16.10.0 0.0.0.255
6-72

R4(config)#route-map torouter1 permit 10
Configuration on R5
R5(config)#ip route 173.16.0.0 255.255.0.0 183.16.20.1
Configuration Check
Use the show ip bgp summary command to view neighborhood on R4.
R4(config)#show ip bgp summary
172.16.20.2 4 1 46 140 00:22:35 0
Use show ip bgp route to view BGP routing table on R4.

Status codes: *-valid, >-best, i-internal, s-stale
Origin codes: i-IGP, e-EGP, ?-incomplet

*>192.16.0.0/16 0.0.0.0 254 i
*> 192.16.20.0/24 10.9.1.39 1 ?
*> 192.16.21.0/24 10.9.1.39 1 ?
*> 192.16.22.0/24 10.9.1.39 1 ?
*> 170.16.10.0/24 10.9.1.39 1 ?
Use the show ip bgp summary command to view neighborhood on R1.

172.16.20.1 4 2 46 140 00:22:35 1
172.16.1.2 4 1 46 140 00:22:35 0
View BGP routing table on R1,


*> 192.16.0.0/16 172.16.20.1 20 i 2
Use the show ip bgp summary command to view neighborhood on R2,

6-73

183.16.20.2 4 3 46 140 00:22:35 0

172.16.1.1 4 1 46 140 00:22:35 1
View BGP routing table on R2, as shown below.


*>i 192.16.0.0/16 172.16.1.1 200 i 2
Use the show ip bgp summay command to view neighborhood on R5,

173.16.20.2 4 1 46 140 00:22:35 1
View BGP routing table on R5, as shown below.


*> 192.16.0.0/16 173.16.20.2 20 i 1 2
6.5 BGP Fault Handling

6.5.1 BGP Basic Function Fault Handling
As shown in Figure 6-22, it is required to set up EBGP neighborhood between R1 and R2
through their loopback1 interfaces.
Figure 6-22 Network Topology of a BGP Fault

Symptom:
R1 and R2 loopback interfaces fail to set up connection.
6-74

Fault analysis:
In general, inspect whether the IP addresses of interfaces used to connect can ping each
other. If the ping is unsuccessful, inspect whether the physical link is in up state and
whether the physical interfaces can ping each other. If the physical interface cannot be
pinged, inspect whether the physical interface is in up state. If the physical interface is in
up state, but it still cannot be pinged successfully. Inspect cable, and modify the cable if
required. If physical state is up, maybe there is not the route to the peer loopback interface.
If there is not route make the related configuration to create route. If it can be pinged
successfully maybe AS number, multi-hop and TCP sender are not configured correctly.
Use the show ip bgp neighbor command to view error code. Compare BGP error code
table to locate error reason. If the problem still exists call technical support.
Configuration Item Notice
Remote-as AS number of neighbor behind the Remote-as
Update source The configuration item is required if use loopback interfaces to set
up connection.
ebgp-multihop The configuration item is required if set up EBGP multi-hop

neighborhood

The flow to handle a BGP fault is shown in Figure 6-23.
6-75

Figure 6-23 Flow to Handle a BGP Fault
BGP error code table is shown in Table 6-1.
Table 6-1 BGP Error Code Table
Error Signification Wrong Sub-ID Description

Code
1 The connection is
non-synchronized
The header of message is
1
wrong 2 The length of error message
3 The format of error message
6-76

Error Signification Wrong Sub-ID Description

Code
2 1 Non-supported version number
2 Wrong AS of the peer
3 Wrong BGP identifier

Open message is wrong
4 Wrong optional field
5 Authentication failed
6 Non-acceptable Holdtime
1 Abnormal attribute list
2 Unidentifiable well-known
attribute
3 The lost well-known attribute
4 Attribute symbol is wrong
5 Attribute length is wrong

3 Update message is wrong
6 Illegal ORINGIN attribute
7 AS route loop
8 Illegal the next-hop attribute
9 Optional attribute error
10 Illegal network segment
11 Abnormal AS_PATH
4 Hold timer expires 0 —
5 Finite State Machine error 0 —
6 Stop 1 Exceed the maximum prefix

that this neighbor receives
2 Neighbor is in invalid state
3 Neighbor is invalid because

configuration is modified.
4 Reset bgp instance or neighbor
5 Refuse this connection
6 Modify neighbor change
7 Connection conflict
8 Neighbor is disabled because

memory is used up.
6-77


The procedure to handle a BGP fault is described below.
1. Inspect whether the physical interfaces are in up state and whether the physical
interfaces can ping each other.
2. Inspect whether there is a route between loopback interfaces of two ends and whether
the loopback interfaces can ping each other.
3. Inspect whether the AS numbers of two ends are configured correctly.
4. For a EBGP multi-hop connection, the configuration of ebgp-multihop is required.
5. For a loopback-based link, the configuration of update source is required.
6. Use the show ip bgp neighbor command to view the error code, and compare BGP
error code table to locate error reason.
6.5.2 BGP FRR Fault Handling

The network topology of a BGP fault is shown in Figure 6-24.
Figure 6-24 Network Topology of a BGP FRR Fault

The conditions to form a BGP FRR relationship are easy to meet. When there are two
different next hops for the same destination, but there is no related routes in the backup
routing table, it is necessary to check whether load sharing is enabled at the same time.
If both FRR and load sharing are configured, and the routes meet the conditions of load
sharing, load sharing will take effect.

The flow to handle a BGP FRR fault is shown in Figure 6-25.
6-78

Figure 6-25 Flow to Handle a BGP FRR Fault

The procedure to handle an IP BGP fault is described below.
1. Check whether FRR configuration is configured on routers with the show running-con
fig bgp command.
2. If the primary/backup links are not formed, check whether the link costs meet the
algorithm requirement.
3. Check whether the backup link is forbidden to back up.
6-79

6-80

Figures
Figure 2-1 Indirect Static Route Next Hop Configuration Example............................. 2-3
Figure 2-2 Static Route Configuration Example......................................................... 2-6
Figure 2-3 Static Route Summary Configuration Example......................................... 2-9
Figure 2-4 Default Route Configuration Example .................................................... 2-10
Figure 2-5 Network Topology of a Static Route Fault.............................................. 2-11
Figure 2-6 Flow to Handle a Static Route Fault ....................................................... 2-12
Figure 3-1 RIP Configuration Example Topology ..................................................... 3-14
Figure 3-2 Network Topology of an RIP Fault .......................................................... 3-16
Figure 3-3 Flow to Handle an RIP Fault .................................................................. 3-17
Figure 4-1 OSPF Router Type .................................................................................. 4-4
Figure 4-2 OSPF Basic Configuration Example......................................................... 4-9
Figure 4-3 OSPF Interface Attribute Configuration .................................................. 4-12
Figure 4-4 OSPF Authentication Configuration Example ......................................... 4-15
Figure 4-5 OSPF Stub and Totally Stubby Area Configuration Example .................. 4-18
Figure 4-6 NSSA Area Configuration Example........................................................ 4-21
Figure 4-7 OSPF Inter-Area Route Aggregation Configuration Example ................. 4-23
Figure 4-8 Route Aggregation with Route Redistribution Configuration
Example ............................................................................................... 4-26
Figure 4-9 OSPF Redistribution Route Configuration Example ............................... 4-29
Figure 4-10 OSPF Virtual Link Configuration Example ............................................ 4-33
Figure 4-11 Sham-link............................................................................................. 4-34
Figure 4-12 OSPF Configuration Example One....................................................... 4-47
Figure 4-13 OSPF Configuration Example Two....................................................... 4-49
Figure 4-14 OSPF Multi-Instance Configuration Example ....................................... 4-51
Figure 4-15 OSPFv2 Route Load Sharing Configuration Example .......................... 4-53
Figure 4-16 Network Topology of an OSPF Fault .................................................... 4-54
Figure 4-17 Flow to Handle an OSPF Fault............................................................. 4-56
Figure 4-18 Network Topology of an OSPF Multi-Instance Fault.............................. 4-57
Figure 4-19 Flow to Handle an OSPF Multi-Instance Fault ...................................... 4-58
Figure 4-20 Network Topology of a Route Load Sharing Fault................................. 4-59
Figure 4-21 Flow to Handle an OSPF Route Load Sharing Fault............................. 4-60
Figure 5-1 IS-IS Area Division and Router Types ...................................................... 5-2
I
Figure 5-2 Single Area IS-IS Configuration Example............................................... 5-23

Figure 5-3 Multi-Area IS-IS Configuration Example ................................................. 5-26
Figure 5-4 IS-IS Multi-Instance Configuration Example ........................................... 5-33
Figure 5-5 Network Structure of FRR Node Protection ............................................ 5-35
Figure 5-6 Network Structure of FRR Link Protection .............................................. 5-35
Figure 5-7 Network Topology of an IS-IS Fault ........................................................ 5-37
Figure 5-8 Flow to Handle an IS-IS Fault ................................................................ 5-39
Figure 5-9 Network Topology of an IS-IS Multi-Instance Fault ................................. 5-40
Figure 5-10 Flow to Handle an IS-IS Multi-Instance Fault........................................ 5-42
Figure 5-11 Network Topology of a IS-IS FRR Fault ................................................ 5-43
Figure 5-12 Flow to Handle a IS-IS FRR Fault ........................................................ 5-44
Figure 6-1 BGP Working Process ............................................................................. 6-4
Figure 6-2 IBGP and EBGP ..................................................................................... 6-5
Figure 6-3 EBGP Physical Direct-Connected Configuration Topology ....................... 6-7
Figure 6-4 EBGP Configuration through Loopback Address...................................... 6-9
Figure 6-5 IBGP Configuration ............................................................................... 6-13
Figure 6-6 Use network Command to Advertise BGP Route ................................... 6-17
Figure 6-7 Redistribute OSPF Routes by Using redistribute Command................... 6-20
Figure 6-8 Route Aggregation Configuration Example ............................................ 6-22
Figure 6-9 Filter Routes by Using Route-Map ......................................................... 6-28
Figure 6-10 Filtering Route by Using NLRI.............................................................. 6-31
Figure 6-11 Restrict the Number of Route Advertisements Received by
Neighbor............................................................................................... 6-33
Figure 6-12 Filtering Routes by Using AS_PATH..................................................... 6-35
Figure 6-13 Select Route by Using LOCAL_PREF Attribute ................................... 6-37
Figure 6-14 Select Route by Using MED................................................................. 6-40
Figure 6-15 Use Community to Control Routes ....................................................... 6-44
Figure 6-16 BGP Route Reflector Configuration Example ....................................... 6-48
Figure 6-17 BGP Confederation Configuration Example ......................................... 6-50
Figure 6-18 Network Structure of FRR Node Protection .......................................... 6-61
Figure 6-19 Network Structure of FRR Link Protection ............................................ 6-61
Figure 6-20 BGP Configuration Example One......................................................... 6-63
Figure 6-21 BGP Configuration Example ................................................................ 6-72
Figure 6-22 Network Topology of a BGP Fault ........................................................ 6-74
Figure 6-23 Flow to Handle a BGP Fault................................................................. 6-76
Figure 6-24 Network Topology of a BGP FRR Fault ................................................ 6-78
II
Figures
Figure 6-25 Flow to Handle a BGP FRR Fault......................................................... 6-79
III
Figures

Tables
Table 6-1 BGP Error Code Table............................................................................. 6-76
V
Tables

Glossary
ABR
- Area Border Router
ACL
- Access Control List
AD
- Administrative Domain
AS
- Autonomous System
ASBR
- Autonomous System Boundary Router
BDR
- Backup Designate Router
BGP
- Border Gateway Protocol
CIDR
- Classless Inter-Domain Routing
CLNS
- ConnectionLess Network Sevice
DIS
- Designate IS
DR
- Designate Router
EBGP
- External Border Gateway Protocol
FRR
- Fast Reroute
IBGP
- Interior Border Gateway Protocol
IGP
- Interior Gateway Protocol
IP
- Intelligent Peripheral
IS-IS
- Intermediate System-to-Intermediate System
VII
ISO
- International Organization for Standardization
LSA
- Link State Advertisement
LSDB
- Link-state Database
LSP
- Link State Packet
LSU
- Link State Update
MD5
- Message Digest 5 Algorithm
MED
- MULTI_EXIT_DISC
MP-BGP
- Multiprotocol BGP
NBMA
- Non-Broadcast Multiple Access
NSSA
- Not-So-Stubby Area
OSI
- Open System Interconnection
OSPF
- Open Shortest Path First
PDU
- Protocol Data Unit
RFC
- Remote Feature Control
RIP
- Request In Progress
RR
- Router Reflector
SNP
- Sequence Num PDU
SPF
- Shortest Path First
TCB
- Transmission Control Block
VIII
Glossary
TCP
- Transfer Control Protocol
TE
- Traffic Engineering
UDP
- User Datagram Protocol
VLSM
- Variable Length Subnet Mask
VPN
- Virtual Private Network
VRF
- Virtual Route Forwarding
IX

ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Routing) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXR10 M6000 (V1.00.30) Carrier-Class Router Configuration Guide (IPv4 Routing) PDF

Uploaded by

Copyright:

Available Formats

ZXR10 M6000

Revision No. Revision Date Revision Reason

R2.0 2011-01-15 Second release, the document architecture is changed.

R1.0 2010-09-30 First release

Serial Number: SJ-20110504161056-013

Publishing Date: 2010-05-10 (R2.1)

Chapter 2 Static Route Configuration ...................................................... 2-1

Chapter 3 RIP Configuration ..................................................................... 3-1

Chapter 4 OSPF Configuration.................................................................. 4-1

Chapter 5 IS-IS Configuration ................................................................... 5-1

Chapter 6 BGP Configuration.................................................................... 6-1

What Is in This Manual

Chapter 3 RIP Configuration Describes the RIP principle, configuration commands,

Chapter 4 OSPF Configuration Describes the OSPF principle, configuration commands,

Chapter 5 IS-IS Configuration Describes the IS-IS principle, configuration commands,

Chapter 6 BGP Configuration Describes the BGP principle, configuration commands,

| Separates individual parameter in series of parameters.

Note: Provides additional information about a certain topic.

Checkpoint: Indicates that a particular step needs to be checked before proceeding

1.1 Safety Instruction

1.2 Safety Signs

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

2.1 Static Route Overview

2.2 Static Route Principle

ZXR10#show ip protocol routing

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

*> 2.2.2.2/32 2.2.2.2 0 0 connected

2.3 Configuring Static Routes

2.3.1 Configuring Next Hop of a Direct Route

< net-mask> Network Mask, in dotted decimal notation

metric < metric> Route metric, in the range of 1–255

bfd enable Enable static BFD

2.3.1.1 Specifying a Direct Next Hop

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

2.3.1.2 Specifying an Indirect Next Hop

2.3.2 Configuring an Out-Interface of a Static Route

< interface-name> Interface name

Figure 2-1 Indirect Static Route Next Hop Configuration Example

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

The direct-connected interfaces on R1, R2 and R3 run Intermediate

IS-IS configuration on R2:

IS-IS configuration on R3:

View the forwarding table on R1, as shown below.

R1#show ip forwarding route

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

2.4 Static Route Maintenance

Dest NextHop RoutePrf RouteMetric Protocol

Descriptions of the command output:

Command Output Description

Dest Destination IP address

NextHop IP address of next hop

RouteRrf Management distance metric

RouteMetric Route metric

Protocol Name of the corresponding routing protocol

An example of the show ip forwarding route command output is shown below.

SJ-20110504161056-013|2010-05-10 (R2.1) ZTE Proprietary and Confidential

Dest Gw Interface Owner Pri Metric

Descriptions of the command output:

Command Output Description

Dest Destination IP address

Interface Outgoing interface

Owner Route type