ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual (IPv4 Routing Volume)

ZXR10 5900E Series
Easy-Maintenance MPLS Routing Switch

User Manual (IPv4 Routing Volume)
Version: 2.8.23.B2
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
R1.0 2011-02-11 First Release
Serial Number: SJ-20101226010430-004
Publishing Date: 2011-02-11(R1.0)

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 Configuring Static Route ..................................................................................... 2-1
2.3 Static Route Configuration Example .................................................................... 2-1
2.3.1 Static Route Configuration Example .......................................................... 2-1
2.3.2 Static Route Summary Example ................................................................ 2-3
2.3.3 Default Route Configuration Example ........................................................ 2-3
2.4 Static Route Maintenance and Diagnosis ............................................................. 2-5
Chapter 3 RIP Configuration ..................................................................... 3-1

3.1 RIP Overview..................................................................................................... 3-1
3.1.1 RIP Basics............................................................................................... 3-1
3.1.2 RIP Routing Metric ................................................................................... 3-1
3.1.3 RIP Timer ................................................................................................ 3-2
3.1.4 Route Updates ......................................................................................... 3-2
3.2 Configuring RIP.................................................................................................. 3-2
3.2.1 Enabling RIP............................................................................................ 3-2
3.2.2 Adjusting RIP Timer.................................................................................. 3-3
3.2.3 Configuring RIP Neighbor ......................................................................... 3-3
3.2.4 Configuring RIP Authentication.................................................................. 3-3
3.2.5 Configuring split horizon mechanism ......................................................... 3-3
3.2.6 Configuring Poison Reverse Mechanism.................................................... 3-3
3.2.7 Redistributing a Route .............................................................................. 3-4
3.2.8 Configuring RIP Version............................................................................ 3-4
3.3 RIP Configuration Example ................................................................................. 3-4
3.4 RIP Maintenance and Diagnosis.......................................................................... 3-5
Chapter 4 OSPF Configuration.................................................................. 4-1

4.1 OSPF Overview ................................................................................................. 4-1
4.1.1 OSPF Basics ........................................................................................... 4-1
4.1.2 OSPF Algorithm ....................................................................................... 4-1
I
4.1.3 OSPF Network Types ............................................................................... 4-2
4.1.4 Hello Packet and Timer............................................................................. 4-2
4.1.5 OSPF Neighbor........................................................................................ 4-3
4.1.6 Adjacency and Designated Routers ........................................................... 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 Stub Area.............................................................. 4-5
4.1.11 Not-So-Stubby Area................................................................................ 4-6
4.1.12 OSPF Authentication .............................................................................. 4-6
4.2 Configuring OSPF .............................................................................................. 4-6
4.2.1 Enabling OSPF ........................................................................................ 4-6
4.2.2 Configuring Interface Timer ....................................................................... 4-6
4.2.3 Configuring Interface Cost ........................................................................ 4-7
4.2.4 Configuring Interface Priority ..................................................................... 4-7
4.2.5 Configuring Neighbor Routers ................................................................... 4-7
4.2.6 Configuring OSPF Area ............................................................................ 4-7
4.2.7 Configuring Inter-Area Route Aggregation.................................................. 4-7
4.2.8 Notifying Default Route ............................................................................. 4-8
4.2.9 Configuring Virtual Link............................................................................. 4-8
4.2.10 Redistributing Other Routing Protocols .................................................... 4-8
4.2.11 Configuring OSPF Authentication ............................................................ 4-9
4.2.12 Enabling Routes to Support Opaque LSA ................................................ 4-9
4.2.13 Modifying OSPF Management Distance................................................... 4-9
4.2.14 Configuring OSPF FRR ........................................................................ 4-10
4.2.15 Configuring OSPF BFD..........................................................................4-11
4.3 OSPF Configuration Example ........................................................................... 4-13
4.3.1 Basic OSPF Configuration Example ........................................................ 4-13
4.3.2 Multi-Area OSPF Configuration Example ................................................. 4-14
4.3.3 OSPF Virtual Links Configuration Example .............................................. 4-16
4.3.4 OSPF Authentication Configuration Example ........................................... 4-17
4.4 OSPF Maintenance and Diagnosis .................................................................... 4-22
Chapter 5 IS-IS Configuration ................................................................... 5-1

5.1 IS-IS Overview ................................................................................................... 5-1
5.1.1 IS-IS Overview ......................................................................................... 5-1
5.1.2 IS-IS Area................................................................................................ 5-2
5.1.3 IS-IS Network Type .................................................................................. 5-3
II
5.1.4 DIS and Router Priority ............................................................................. 5-3
5.2 Configuring IS-IS................................................................................................ 5-3
5.2.1 Enabling IS-IS.......................................................................................... 5-3
5.2.2 Configuring IS-IS Global Parameters ......................................................... 5-3
5.2.3 Configuring IS-IS Interface Parameters...................................................... 5-4
5.2.4 Configuring IS-IS Authentication................................................................ 5-5
5.2.5 Configuring IS-IS FRR .............................................................................. 5-5
5.2.6 Configuring IS-IS BFD .............................................................................. 5-7
5.3 IS-IS Configuration Example ............................................................................... 5-7
5.3.1 Single Area IS-IS Configuration................................................................. 5-7
5.3.2 Multiple Area IS-IS Configuration............................................................... 5-9
5.4 IS-IS Maintenance and Diagnosis...................................................................... 5-12
Chapter 6 BGP Configuration.................................................................... 6-1

6.1 BGP Overview ................................................................................................... 6-1
6.2 Configuring BGP ................................................................................................ 6-2
6.2.1 Enabling BGP ......................................................................................... 6-2
6.2.2 Configuring BGP Route Advertisement ...................................................... 6-4
6.2.3 Configuring BGP Aggregate Advertisement................................................ 6-4
6.2.4 Configuring Multihop in EBGP ................................................................... 6-6
6.2.5 Filtering Routes by Router ........................................................................ 6-7
6.2.6 Filtering Routes Using NLRI...................................................................... 6-8
6.2.7 Filtering Route Based on AS_PATH........................................................... 6-9
6.2.8 Setting LOCAL_PREF Attribute................................................................. 6-9
6.2.9 Setting MED Attribute ..............................................................................6-11
6.2.10 Setting Community Attribute.................................................................. 6-12
6.2.11 Setting BGP Synchronization................................................................. 6-13
6.2.12 Setting BGP Router Reflector................................................................ 6-15
6.2.13 Setting BGP Confederation ................................................................... 6-16
6.2.14 Setting BGP Route Dampening ............................................................. 6-17
6.2.15 Configuring BGP FRR .......................................................................... 6-18
6.3 BGP Configuration Example ............................................................................. 6-19
6.4 BGP Maintenance and Diagnosis ...................................................................... 6-20
Chapter 7 MPLS Configuration ................................................................. 7-1

7.1 MPLS Overview ................................................................................................. 7-1
7.1.1 MPLS Working Principle ........................................................................... 7-2
7.1.2 MPLS Label Header ................................................................................. 7-2
7.1.3 MPLS LDP............................................................................................... 7-3
III
7.2 Configuring MPLS .............................................................................................. 7-4
7.3 Example for Configuring MPLS ........................................................................... 7-7
7.4 MPLS Maintenance and Diagnosis ...................................................................... 7-8
Chapter 8 VPLS Configuration .................................................................. 8-1

8.1 VPLS Overview.................................................................................................. 8-1
8.2 Basic Configuratiaon of VPLS ............................................................................. 8-2
8.2.1 Clearing VPLS-related Statistics Information .............................................. 8-2
8.2.2 Clearing VPWS-related Statistics Information............................................. 8-3
8.2.3 Clearing MAC Address Table Corresponding to Specific VPLS.................... 8-3
8.2.4 Designating other PE Addresses in the same VPLS Area and Originating
PW Establishment................................................................................... 8-4
8.2.5 Designating PW Type Established by VPLS Instance ................................. 8-5
8.2.6 Displaying MAC Forwarding Table of VPLS Instance .................................. 8-6
8.2.7 Displaying Successfully Established PW Information .................................. 8-7
8.2.8 Displaying Counts of L2VPN VPWS, VPLS ............................................... 8-8
8.2.9 Displaying Detailed Information of a VFI .................................................... 8-9
8.2.10 Displaying All Configured VPLS VFI Brief Information ............................ 8-10
8.2.11 Designating vcid for VPLS Instance ....................................................... 8-10
8.2.12 Creating VPLS Instance on PE...............................................................8-11
8.2.13 Connecting Interface to VPLS Instance ................................................. 8-12
8.2.14 Enabling VPWS on the Interface ........................................................... 8-13
8.3 Example for Configuring VPLS .......................................................................... 8-13
8.4 Example for Configuring VPWS......................................................................... 8-18
Chapter 9 Multicast Routing Configuration ............................................. 9-1

9.1 Multicast Overview ............................................................................................. 9-1
9.1.1 Multicast Address..................................................................................... 9-1
9.1.2 IGMP....................................................................................................... 9-2
9.1.3 Multicast Tree .......................................................................................... 9-2
9.1.4 PIM-SM ................................................................................................... 9-3
9.1.5 MSDP ..................................................................................................... 9-4
9.1.6 PIM-SNOOPING ...................................................................................... 9-5
9.2 Configuring Public Multicast ................................................................................ 9-5
9.3 Configuring IGMP Version................................................................................... 9-5
9.3.1 Configuring IGMP Version......................................................................... 9-5
9.3.2 Configuring an IGMP Group...................................................................... 9-5
9.3.3 Configuring IGMP Timer ........................................................................... 9-7
9.3.4 Configuring ssm-mapping ......................................................................... 9-7
IV
9.3.5 Configuring Limit on Numbers of IGMP Users ............................................ 9-8
9.4 Configuring PIM-SM ........................................................................................... 9-9
9.4.1 Booting PIM-SM ....................................................................................... 9-9
9.4.2 Configuring Static RP Address .................................................................. 9-9
9.4.3 Configuring Candidate-BSR ...................................................................... 9-9
9.4.4 Configure the Candidate-RP ................................................................... 9-10
9.4.5 Switching Routers with Directly Connected Receivers............................... 9-10
9.4.6 Configuring the Area Border with the Interface PIM .................................. 9-10
9.4.7 Setting the RP to Filter the Received Register Packet................................9-11
9.4.8 Limiting the BSR Message to Advertise to the Candidate-RP .....................9-11
9.4.9 Setting DR Priority...................................................................................9-11
9.4.10 Setting the Sending Interval of the Hello Message ...................................9-11
9.4.11 Limiting PIM-SM Neighbor......................................................................9-11
9.5 Configuring MSDP............................................................................................ 9-12
9.5.1 Enabling MSDP...................................................................................... 9-12
9.5.2 Configuring Default MSDP Peer .............................................................. 9-12
9.5.3 Configuring an Originating RP ................................................................. 9-12
9.5.4 Configuring the MSDP Peer as a Mesh Group Member ............................ 9-12
9.5.5 Clearing Statistics Counter for MSDP Peers............................................. 9-13
9.6 Configuring PIM-DM ......................................................................................... 9-14
9.7 Configuring PIM-SNOOPING ............................................................................ 9-14
9.8 Multicast Configuration Example ....................................................................... 9-14
9.9 Multicast Maintenance and Diagnosis ................................................................ 9-16
Chapter 10 Load Balance Configuration ................................................ 10-1

10.1 Load Balance Overview .................................................................................. 10-1
10.2 Configuring Load Balance ............................................................................... 10-2
10.3 Load Balance Configuration Example .............................................................. 10-2
10.3.1 Static Routing Load Balance ................................................................. 10-3
10.3.2 OSPF Load Balance ............................................................................ 10-4
10.3.3 BGP Load Balance ............................................................................... 10-5
10.4 Load Balance Maintenance and Diagnosis....................................................... 10-5
Figures............................................................................................................. I
Glossary ........................................................................................................ III
V
VI
About This Manual
Purpose
ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User
Manual (IPv4 Routing Volume). It is applicable for ZXR10 5900E series (V2.8.23.B2)
easy-maintenance MPLS routing switch (brieved as ZXR10 5900E series, also named as
switch in common part). It includes:
l ZXR10 5916E Easy-Maintenance MPLS Routing Switch

l ZXR10 5928E-FI Easy-Maintenance MPLS Routing Switch
What Is in This Manual

ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual
(IPv4 Routing Volume) contains the following chapters:
Chapter Summary
Chapter 1 Safety Instruction This chapter describes safety instruction and safety signs.
Chapter 2 Static Route This chapter introduces static route concept, related configuration
Configuration command and configuration example.
Chapter 3 RIP Configuration This chapter introduces RIP concept, related configuration
command and configuration example.
Chapter 4 OSPF Configuration This chapter introduces OSPF concept, related configuration
Chapter 5 IS-IS Configuration This chapter introduces IS-IS concept, related configuration
Chapter 6 BGP Configuration This chapter introduces BGP concept, related configuration
Chapter 7 MPLS Configuration This chapter introduces MPLS concept, related configuration
Chapter 8 VPLS Configuration This chapter introduces VPLS concept, related configuration
Chapter 9 Multicast Routing This chapter introduces multicast routing concept, related
Configuration configuration command and configuration example.
Chapter 10 Load Balance This chapter introduces load balance concept, related
Configuration configuration command and configuration example.
I
Related Documentation
l ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch
Hardware Manual
l ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User
Manual (Basic Configuration Volume)
Manual (Ethernet Switching Volume)
Manual (IPv4 Routing Volume)
Manual (IPv6 Volume)
The commands supported by ZXR10 5900E series (V2.8.23.B2) easy-maintenance MPLS

routing switch is based on unified platform ZXROS V4.8.23.
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 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 contents 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-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (IPv4 Routing Volume)
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
Configuring Static Route.............................................................................................2-1
Static Route Configuration Example ...........................................................................2-1
Static Route Maintenance and Diagnosis ...................................................................2-5
2.1 Static Route Overview

Static routes are user-defined routes that cause packets moving between a source and a
destination to take a specified path. They are useful for specifying a gateway of last resort
to which, all-unroutable packets will be sent. The static route, unlike a dynamic route, does
not set up the routing table based on routing algorithm. When configuring dynamic route,
sometimes it is necessary to send routing information of the entire Internet to a router,
which is hard to bear such great amount of information. In this cast, it is necessary to use
static route.
The static route requires fewer configurations than the dynamic route. In a routing
environment with many routers and paths, however, it is very difficult to configure the
static route.
2.2 Configuring Static Route

Command Function
ZXR10(config)#ip route < prefix> < net-mask> { < forwarding-router's-addre This configures static route.
ss> | < interface-name> } [global[ < distance-metric> ] [ tag < tag> ]]
2.3 Static Route Configuration Example

2.3.1 Static Route Configuration Example
A simple network with three routers connected is shown in Figure 2-1.
2-1

Figure 2-1 STATIC ROUTE CONFIGURATION
When R1 needs to access network in R3, the static route configuration is as follows.
ZXR10_R1(config)#ip route 192.168.5.0 255.255.255.0
192.168.4.2
192.168.4.2
R2 configuration:
ZXR10_R2(config)#ip route 192.168.6.0 255.255.255.0 192.168.5.1
R3 configuration:
It is seen from the above configuration information that static route is configured in global
configuration mode. Only one static route can be configured once. What next to the
command ip route are remote network, subnet mask and next-hop IP address reaching
remote network. When R1 wants to transmit message to network 192.168.5.0/24, it must
deliver the message to R2 with the IP address of 192.168.4.2; R1 and R2 are connected
directly.
When multiple paths to the same destination are available, configure the router with
multiple static routes with different administrative distance values. Routing table only
shows the routing information with the minimum distance value. When the router is
notified that there are multiple competitive sources to a network, the route with the
minimum administrative distance value has a higher priority. Parameter <distance-metric>
in ip route command can be used to change the administrative distance value of a static
route. Assume that there are two different routes from R1 to 192.168.6.0/24 network
segment, and the configuration is as follows:
192.168.4.2
192.168.3.2 25 tag 150
The above two commands configure two different static routes to the same network. The
first command does not configure administrative distance value, so default value 1 is
applied. The second command configures the administrative distance value to be 25.
2-2

Chapter 2 Static Route Configuration
The administrative distance value of the first route is smaller than that of the second one,
so only the information of the first route is available in the routing table. That is to say,
the router reaches the destination network 192.168.6.0/24 through next-hop 192.168.4.2.
The second route will be available in the routing table only when the first route becomes
invalid and disappears from the routing table.
2.3.2 Static Route Summary Example

Static route is a special static route which summaries two or more specific route
expressions into one expression thus reducing entries of the routing table while keeping
all of the original connections. Summary static route detail is given in Figure 2-2.
Figure 2-2 STATIC ROUTE SUMMARY
As shown in Figure 2-2, R3 has two networks: 10.1.0.0/16 and 10.2.0.0/16. To make R1
access these networks, it is necessary to configure the following two static routes for R1:
192.168.4.2
192.168.4.2
Suppose that R2, R3 has been configured normally, and the above configuration can be
used to complete IP connection. However, static route summary can be used to optimize
the routing table of R1. The following command can be used to replace the above two
commands:
The above command shows that all packets to destination network 10.0.0.0/8 pass
192.168.4.2. It means that packets to subnets (subnet 10.1.0.0/16 and subnet 10.2.0.0/16)
of the destination network 10.0.0.0/8 are sent to 192.168.4.2. In this way static routes are
used to summarize all subnets of the main network 10.0.0.0/8.
2.3.3 Default Route Configuration Example

A router might not be able to determine the routes to all other networks. To provide
complete routing capability, the common practice is to use some routers as smart routers
and give the remaining routers default routes to the smart router. (Smart routers have
routing table information for the entire internet work.) These default routes can be passed
along dynamically and can be configured into individual routers.
2-3

Most dynamic interior routing protocols include a mechanism for causing a smart router to
generate dynamic default information that is then passed along to other routers.
If a router cannot route a packet, the packet has to be dropped. However, it is not hoped
that the packet is dropped in an "unknown" destination. To support complete connection
of the router, it should have a route connected to a network. If the router wants to keep
complete connection and meanwhile does not need to record each independent route,
the default route can be used. By use of the default route, an independent route can be
designated to indicate all the other routes.
An example is given in the following to describe the functions and use of the default route.
Figure 2-3 DEFAULT ROUTE CONFIGURATION
As shown in Figure 2-3. R2 is connected to router R3 in the Internet. R2 does not record
the addresses of all the networks on the Internet. It uses a default route to directly send
unknown packets to R3 for proper processing. The configuration of the default route in R2
is as follows:
When the default route is used in routing protocol configuration, the default route varies
with the routing protocols.
If the default route is configured for a router where an RIP runs, the RIP will advertise the
default route 0.0.0.0/0 to its neighbor, and even route redistribution is not needed in the
RIP domain.
For the OSPF protocol, a router where the OSPF protocol runs will not inject the default
route into its neighbor automatically. For the OSPF to send the default route to the OSPF
domain command notifies default route must be used. If it is necessary to redistribute the
default route in the OSPF domain, such an advertisement is normally implemented by an
ASBR (Autonomous System Border Router) in the OSPF domain.
The default route configuration is completely the same as the static route configuration,
and the only difference is that the network part and subnet mask part are all 0.0.0.0. This
can be seen in routing table of R2.
ZXR10_R2#show ip route
IPv4 Routing Table:
Dest Mask Gw Interface Owner pri metric
0.0.0.0 0.0.0.0 211.211.211.2 vlan1 static 1 0
192.168.4.0 255.255.255.0 192.168.4.2 vlan2 direct0 0
192.168.4.2 255.255.255.255 192.168.4.2 vlan2 address0 0
2-4

Chapter 2 Static Route Configuration
2.4 Static Route Maintenance and Diagnosis

Step Command Function
1 ZXR10#show ip route [ < ip-address> [ < net-mask> ] | < protocol> ] This shows global routing table of
the route and checks if there is any
configured static route in the routing
table.
2 ZXR10#show ip forwarding { hostrt < ip-address> | subnetrt < This views hardware routing table
ip-address> < net-mask> | summary} and checks host route and subnet
route of specific IP address and
statistics of subnet route entry and
all hosts.
2-5

This page intentionally left blank.
2-6

Chapter 3
RIP Configuration
Table of Contents
RIP Overview .............................................................................................................3-1
Configuring RIP..........................................................................................................3-2
RIP Configuration Example ........................................................................................3-4
RIP Maintenance and Diagnosis.................................................................................3-5
3.1 RIP Overview

3.1.1 RIP Basics
RIP is a relatively old but still commonly used interior gateway protocol created for use in
small, homogeneous networks. It is a classical distance-vector routing protocol. RIP is
documented in RFC 1058. RIPv2 is defined by RFC2453.
ZXR10 5900E supports RIPv1 and RIPv2 and adopts RIPv2 by default. Comparing with
RIPv1, RIPv2 has the following advantages:
l Subnet mask contained in the routing update
l Authentication of the routing update
l Multicast route update
3.1.2 RIP Routing Metric

RIP uses the UDP packet (port number 520) to exchange RIP routing information. Routing
information in the RIP packet includes the number of routers that a route passes (that is,
hops). Router determines the route to the destination network according to hops. RFC
stipulates that the maximum hop count cannot go beyond 16, so RIP is only applicable to
a small-sized network. Hop count 16 indicates the infinite distance and this means that the
route is unreachable. Besides, this is a method for RIP to identify and avoid route loop.
RIP only takes the hop count as the metric and does not consider the bandwidth, delay or
other variable factors during the routing. RIP always takes the path with the minimum hop
count as the optimal path which sometimes results in that the selected path is not the best
one.
Administrative Distance (AD) of RIP is 120 by default. Smaller the AD value, more reliable
the routing source is. Therefore, comparing with other routing protocols, RIP is not so
reliable.
3-1

3.1.3 RIP Timer

The router running RIP sends a routing information update packet reflecting all the routing
information of the router at intervals (30 seconds by default), which is called the routing
information announcement. If a router cannot receive update information from another
router within a period of time (180 seconds by default), it will label the route provided
by this router as unavailable. If update information still cannot be received within the
subsequent period of time (240 seconds), the router eliminates the route from the routing
table. Holddown timer introduces a certain amount of skepticism to reduce the acceptance
of bad routing information. If the distance to a destination increases, for example, the hop
count increases from two to four, the router sets a holddown timer for that route. Until the
timer expires, the router will not accept any new updates for the route.
RIP provides four timers:
l Update timer
l Invalid timer
l Holddown timer
l Flush timer
3.1.4 Route Updates

RIP sends routing-update messages at regular intervals and when network topology
changes. When a router receives a routing update that includes changes to an entry, it
updates its routing table to reflect the new route. The metric value for path is increased
by 1, and the sender is indicated as the next hop. RIP routers only maintain best route
(the route with the lowest metric value) to a destination.
After updating its routing table, router immediately transmits routing updates to inform other
network routers of the change. These updates are sent independently of the regularly
scheduled updates that RIP routers send.
3.2 Configuring RIP

3.2.1 Enabling RIP
1 ZXR10#ZXR10(config)#router rip This enables RIP.
2 ZXR10(config-router)#network < ip-address> < wild card bits> This associates a network with RIP
routing process.
3-2

Chapter 3 RIP Configuration
3.2.2 Adjusting RIP Timer

Command Function
ZXR10(config-router)#timers basic < update> < invalid> < holddown> This adjusts timer for better RIP
< flush> performance.
3.2.3 Configuring RIP Neighbor

Command Function
ZXR10(config-router)#neighbor < ip-address> This configures neighbor router which

exchanges routing information with this
router.
3.2.4 Configuring RIP Authentication

To specify the type of authentication used in RIP Version 2 packets, designate the key for
interface simple text authentication, use the following command.
1 ZXR10(config-if-vlanX)#ip rip authentication key < key> This designates the key for interface
simple text authentication.
2 ZXR10(config-if-vlanX)#ip rip authentication mode { text| md5} This designates the authentication
type for RIP packet.
3.2.5 Configuring split horizon mechanism

Command Function
ZXR10(config-if-vlanX)# ip split-horizon This enables the split horizon

mechanism.
3.2.6 Configuring Poison Reverse Mechanism

Command Function
ZXR10(config-if-vlanX)#ip poison-reverse This enables the poison reverse

mechanism.
3-3

3.2.7 Redistributing a Route

Command Function
ZXR10(config-router)#redistribute < protocol> [ metric < metric-value> ] This redistributes a route from another
[ route-map < map-tag> ] routing domain to trip routing domain.
3.2.8 Configuring RIP Version

ZXR10 5900E supports RIPv1 and RIPv2. RIPv2 is adopts by default.
1 ZXR10(config-router)#version{ 1| 2} This designates the global RIP

version of the router.
2 ZXR10(config-if-vlanX)#ip rip receive version { 1| 2} [ 1| 2] This designates the RIP version

received by the interface.
3 ZXR10(config-if-vlanX)#ip rip send version { 1| 2 { broadcast| This designates the RIP version sent
multicast} } by the interface.
3.3 RIP Configuration Example

As shown in Figure 3-1, RIP runs on router R1 and router R2.
Figure 3-1 BASIC RIP CONFIGURATION
R1 Configuration:
ZXR10_R1(config)#router rip
ZXR10_R1(config-router)#network 10.1.0.0 0.0.255.255
ZXR10_R1(config-router)#no auto-summary
R2 configuration:
ZXR10_R2(config)#router rip
ZXR10_R1(config-router)#no auto-summary
The result is viewed as follows:
3-4

Chapter 3 RIP Configuration
ZXR10_R2(config)#show ip rip database

Routes of rip:
h : is possibly down,in holddown time
f : out holddown time before flush
Dest Metric RtPrf Time From

*> 10.2.0.0/16 0 0 00:00:00 0.0.0.0
*> 10.1.0.0/16 2 120 00:00:09 192.168.1.1
*> 192.168.1.0/24 0 0 00:00:00 0.0.0.0
3.4 RIP Maintenance and Diagnosis

ZXR10 5900E provides show command for RIP maintenance and diagnosis.
1 ZXR10#show ip rip This displays protocol information.
2 ZXR10#show ip rip interface < interface-name> This shows rip routing interface and
its parameters information.
3 ZXR10#show ip rip database This displays the entire routing entry

database.
4 ZXR10#show ip rip networks This displays all the RIP interfaces

configured by users.
5 ZXR10#show ip route [ < ip-address> < net-mask> ] rip This displays global routing table
and if RIP is in the routing table.
6 ZXR10#show ip forwarding subnetrt < ip-address> < net-mask> This displays driving hardware
routing table and if hardware routing
table is same as global routing table.
ZXR10 5900E also provides debug command for RIP maintenance and diagnosis.
1 ZXR10#debug ip rip This traces the basic RIP sending

and receiving packet.
2 ZXR10#debug ip rip database This traces the change process of

the RIP routing table.
This example shows a debug output example of the debug ip rip command.
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
3-5

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
vlan10 (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
11:01:28: RIP: sending v2 periodic update to 193.1.168.95
via vlan20 (193.1.168.111)
via vlan20 (193.1.168.111)
via vlan20 (193.1.168.111)
via vlan20 (193.1.168.111)
3-6

Chapter 4
OSPF Configuration
Table of Contents
OSPF Overview .........................................................................................................4-1
Configuring OSPF ......................................................................................................4-6
OSPF Configuration Example...................................................................................4-13
OSPF Maintenance and Diagnosis...........................................................................4-22
4.1 OSPF Overview

4.1.1 OSPF Basics
Open Shortest Path First (OSPF) is one of the most popular and widely used routing
protocols. OSPF is a replacement for the problematic Routing Information Protocol (RIP)
and other distance vector protocols. OSPF major advantage is that it supports for much
larger inter-networks and less susceptibility to bad routing information.
OSPF Version 1 is defined by RFC1131. OSPF Version 2 is defined by RFC2328 and
presently in use. ZXR10 5900E fully supports OSPF Version 2.
OSPF has the following features:
l OSPF contains the flow of routing protocol traffic and makes possible construction of
hierarchical inter-network topologies.
l There is no routing loop. The shortest path first (SPF) algorithm ensures a loop free
network.
l Route aggregation decreases the routing table size.
l Support of classless route table lookups, Variable Length Subnet Mask (VLSM) and
Classless Inter-Domain Routing (CIDR).
l Less network bandwidth is needed because the adopted update trigger mechanism
sends update information only when the network topology changes.
l Support of authentication for more secure routing.
l Update information can be multicasted instead of being broadcasted, which reduces
the impact on irrelevant network devices.
4.1.2 OSPF Algorithm

As OSPF is a link state protocol. OSPF router generates a routing table by setting up a
link state database, which contains the information of all networks and routers. Routers
use this information to establish routing tables. To ensure reliability, all routers must have
the same link state database.
4-1

Link state database is built, based on Link State Advertisements (LSAs) ,which are
generated by all routers and spread over the whole OSPF network. There are many types
of LSAs, a complete LSA set shows an accurate distribution diagram over the whole
network.
OSPF uses cost as the metric. The cost is distributed to each port of a router. A port
calculates the cost, that is based on a 100M benchmark by default. The path cost to a
particular destination is the total cost of all links between the router and the destination.
To generate a routing table, based on the LSA database, a router runs the Dijkstra SPF
algorithm to construct a cost routing tree with itself as the root of the routing tree. The
Dijkstra algorithm enables a router to calculate the lowest-cost path between itself and
any node on the network. Router saves the routes of the paths in the routing table.
Different from RIP, OSPF does not simply broadcast all of its routing information regularly.
An OSPF router sends call messages to its neighbors to let them know it is still alive. If
a router does not receive any message from a neighbor within a period of time then the
neighbor might not be alive.
OSPF routing is incrementally updated. Router sends the update information only when
topology changes. When the age of an LSA reaches 1800 seconds, a new version of the
LSA is resent.
4.1.3 OSPF Network Types

Type of the network connecting to a port is used to determine the default OSPF behavior
on that port. The network type affects the adjacency relationship and how the router
designates a timer to the port.
There are five network types in OSPF, and they are as follows:
l Broadcast
l Non-broadcast Multi-access (NBMA) networks
l Point-to-Point networks
l Point-to-multipoint networks
l Virtual links
4.1.4 Hello Packet and Timer

Hello protocol serves several purposes:
l It is the means by which neighbors are discovered.

l It advertises several parameters on which two routers must agree before they can
become neighbors.
l Hello packets act as keepalives between neighbors.
l It ensures bi-directional communication between neighbors.
l It elects designated routers and backup designated routers on Broadcast and
Nonbroadcast Multiaccess (NBMA) networks.
OSPF uses three types of timers related to the Hello Packet.
4-2

Chapter 4 OSPF Configuration
HelloInterval is an attribute of an interface. It defines the length of time between Hello

Packets that the router sends on the interface. Default HelloInterval depends on the
network type. On the broadcast and point-to-point networks the default HelloInterval is
10 seconds. On NBMA and point-to-multipoint networks it is 30 seconds. The router’s
neighbor routers must agree on the HelloInterval to enable them to become neighbors.
It is number of seconds before the router’s neighbors will declare it down. When they stop
receiving the router’s Hello Packets. The default RouterDeadInterval is four times as long
as the HelloInterval, which applies to all the network types.
PollInterval is only used on the NBMA network.
4.1.5 OSPF Neighbor

OSPF neighbors are a group of routers on the same network. They have some of the
same configuration parameters. Routers must first be neighbors before they can set up
adjacency relationship.
Routers analyze the Hello Packets from each other when they become neighbors to
make sure the required parameters are stipulated. Parameters include area ID, area flag,
authentication information, HelloInterval and RouterDeadInterval.
4.1.6 Adjacency and Designated Routers

Two routers when set up adjacency relationship. They can exchange routing information.
Whether two routers can set up an adjacency relationship depends on the type of the
network connecting the routers.
There are only two routers in point-to-point network and virtual links. Routers set up an
adjacency relationship automatically. The point-to-multipoint network can be regarded as
a set of point-to-point networks. Each pair of routers set up an adjacency relationship
automatically.
Neighbors do not necessarily have the adjacency relationship, on broadcast and NBMA
networks. If all routers (the number is n) on a network have set up the adjacency
relationship, each router has (n-1) adjacency relationships and there are n (n-1)/2
adjacency relationships on the network. Tracking so many adjacency relationships
on a large multi-access network will impose a heavy burden on each router. Routing
information between each pair of neighbor routers will waste a great deal of network
bandwidth.
OSPF defines a Designated Router (DR) and a Backup Designated Router (BDR).
Designated Router (DR) has following duties:
l To represent a multi-access network and it’s attached routers to the rest of the
internetwork.
l To manage the flooding process on the multi-access network.
4-3

DR and BDR must establish an adjacency relationship with each OSPF router over the
network. Each OSPF router only establishes adjacency relationships with DR and BDR. If
the DR stops working then BDR take its place and becomes DR.
4.1.7 Router Priority and DR Election

Each multi-access interface of each router has a Router Priority, which is an 8-bit unsigned
integer ranging from 0 to 255. Default priority is 1.
During the DR election, the router with the highest priority becomes the DR. If all routers
have the same priority, the one with the highest IP address will be elected as the DR.
Routers with a priority of 0 are ineligible to become the DR or BDR.
4.1.8 OSPF Area

A network is divided into several smaller OSPF areas to reduce the information that each
router stores and maintains. Each router must have the complete information of its area.
Areas can share their information. Routing information can be filtered out on the area edge
to reduce the routing information stored in routers.
Each area is identified by a 32-bit unsigned number. Area 0 is used to identify the backbone
area. All the other areas must directly connect to Area 0. An OSPF network must have
one backbone area. Based on its tasks in the area, a router can be of one or multiple of
the following roles, as shown in Figure 4-1 .
Figure 4-1 OSPF ROUTER TYPES
l Internal router: Router’s interface is in the same area.

l Backbone router: Router has at least one interface in Area 0.
l Area Border Router (ABR): Router has at least one interface in Area 0 and at least
one interface in another area.
l Autonomous System Border Router (ASBR): Router connects an AS that runs OSPF
to another AS that runs another protocol, such as RIP and IGRP.
4-4

4.1.9 LSA Type and Flooding

OSPF routers use LSAs to exchange information for the link state database. LSAs set
up an accurate and complete network diagram routes in a routing table. ZXR10 5900E
supports six types of LSAs:
l Type 1 Router LSA
l Type 2 Network LSA
l Type 3 Network Summary LSA
l Type 4 ASBR Summary LSA
l Type 5 AS External LSA
l Type 7 NSSA External LSA
OSPF operations are determined by all routers that share one public link state database
in a region. Therefore all LSAs need to be flooded over the region and the processing
must be reliable. Each router sends the LSAs that it receives from a particular area to the
other interfaces in the area. Instead of being packets, LSAs are contained in Link State
Update (LSU) packets. Several LSAs can be included in one LSU. When a router receives
an LSU packet instead of forwarding it directly, router extracts LSAs from the packet and
puts them into its database. In addition, the router constructs its own LSU and forwards
the modified LSU to neighbors connecting to it.
OSPF sends Link State Acknowledgements (LSAck) to make sure that each LSA is
received by neighbors. An LSAck contains the head of the confirmed LSA, which is
sufficient for identifying an LSA uniquely. When a router sends an LSA to an interface,
the LSA is recorded in the resend queue of the interface. Router will wait the preset time
for the LSAck of the LSA. If it does not receive the LSAck within the preset time, it will
resend the LSA. A router can send the original LSU by both unicast and multicast but can
resend the LSU only by unicast.
4.1.10 Stub Area and Totally Stub Area

A stub area is an area into which AS External LSAs are not flooded. If type 5 LSAs are
not known inside an area, type 4 LSAs are unnecessary; these LSAs are blocked. ABRs
at the edge of a stub area will use Network Summary LSAs to advertise a single default
route into the area.
In a stub area, all routers must be configured as stub routers. Hello Packet contains a
“stub area” flag bit, which must be consistent among neighbors.
ABR in a stub area can filter out type 5 LSAs to prevent them from being advertised to the
stub area. In addition, the ABR will generate a type 3 LSA to advertise a default route to
destination addresses outside the AS.
ABR also filters out the Type 3 LSAs and advertises a default route to destination addresses
outside of the area, this area is called totally stubby area.
4-5

4.1.11 Not-So-Stubby Area

Routers in a stub area do not allow type 5 LSAs so the ASBR is not part of a stub area.
To create a stub area with ASBR, routers in this area receive from the ASBR the routes
outside of the AS but external routing information from other areas is blocked.
Not-so-stubby area (NSSA) allows external routes to be advertised into the OSPF
autonomous system while retaining the characteristics of a sub area to the rest of the
autonomous system. To do this, the ASBR in an NSSA originates type 7 LSAs to advertise
the external destinations. These NSSA External LSAs are flooded throughout the NSSA
but are blocked at the ABR. On the other hand, it converts type 7 LSAs into type 5 LSAs.
4.1.12 OSPF Authentication

Authentication applies to packet exchange between OSPF neighbors. Neighbors must
agree on the authentication type, which is included in all packets.
When simple password authentication is configured, one interface can have only one
password and each interface can have a different passwords all interfaces in a particular
network must have the same password. Simple password is transmitted in plain text by
OSPF packets.
4.2 Configuring OSPF

4.2.1 Enabling OSPF
Command Function
ZXR10(config)#router ospf < process-id> This enables OSPF routing.
4.2.2 Configuring Interface Timer

1 ZXR10(config-if-vlanX)#ip ospf hello-interval< seconds> This designates an interval at which

an interface sends Hello packets.
2 ZXR10(config-if-vlanX)#ip ospf retransmit-interval< seconds> This designates the interval at which

an interface retransmits an LSA.
3 ZXR10(config-if-vlanX)#ip ospf transmit-delay< seconds> This designates the delay after which
an interface transmits a LSU packet.
4 ZXR10(config-if-vlanX)#ip ospf dead-interval< seconds> This designates the dead interval for
a neighbor on an interface.
4-6

4.2.3 Configuring Interface Cost

Command Function
ZXR10(config-if-vlanX)#ip ospf cost< cost> This configures interface cost.
4.2.4 Configuring Interface Priority

Command Function
ZXR10(config-if-vlanX)#ip ospf priority< priority> This configures interface priority.
4.2.5 Configuring Neighbor Routers

Command Function
ZXR10(config-router)#neighbor < ip-address> [ cost < cost> ] [ priority This designates the neighbor routers on
< priority> ] [ poll-interval < seconds> ] a non-broadcast.
4.2.6 Configuring OSPF Area

OSPF uses area to implement the hierarchical routing. OSPF areas are divided into stub
area, totally stubby area and not-so-stubby area. Backbone area is a transitional area.
1 ZXR10(config-router)#area < area-id> stub [ no-summary] [ This defines an area as a stub area
default-cost < cost> ] or totally stubby area.
2 ZXR10(config-router)#area < area-id> nssa [ no-redistribution] [ This defines an area as a

default-information-originate [ metric < metric-value> ] [ metric-type not-so-stubby area.
< type> ] [ no-redistribution ] [ no-summary ] ] [ no-summary]
4.2.7 Configuring Inter-Area Route Aggregation

Route aggregation can occur between areas or autonomous systems (AS). Inter-area route
aggregation takes place on the ABR whereas inter-AS route aggregation happens on the
ASBR.
Configuring a stub area can save resources on routers in the stub area but it does not help
the backbone area.
If network addresses in an area are allocated in sequence, configure ABR to advertise an

aggregate route to replace the sequential routes. Route aggregation can save resources
in the backbone area by advertising a summary address for a group of network addresses.
4-7

Command Function
ZXR10(config-router)#area < area-id> range < ip-address> < net-mask> This configures the range of summary
[ advertise| not-advertise] addresses in the area.
4.2.8 Notifying Default Route

When a router uses redistributed routes it becomes an ASBR. ASBR does not
automatically advertise the default route to the whole OSPF area by default.
Command Function
ZXR10(config-router)#notify default route [ always] [ metric < This notifies default route.
metric-value> ] [ metric-type < type> ] [ route-map < map-tag> ]
4.2.9 Configuring Virtual Link

All areas on an OSPF network must directly connect to the backbone area, which will
set a limit to the layout of areas especially when the network is very large. To overcome
this problem, a virtual link can be used to connect a remote area to the backbone area
through another area. The area that the virtual link crosses must have complete routing
information, so it cannot be a stub area.
Command Function
ZXR10(config-router)#area < area-id> virtual-link < router-id> This defines an OSPF virtual link.
[ hello-interval < seconds> ] [ retransmit-intervall < seconds>
] [ transmit-delay < seconds> ] [ dead-intervall < seconds> ] [
authentication-key < key> ] [ message-digest-key < keyid> md5
< cryptkey> [ delay < time> ] [ encrypt ] ] [ authentication [ null|
message-digest] ]
4.2.10 Redistributing Other Routing Protocols

Different dynamic routing protocols can share routing information through route
redistribution. In OSPF the routing information of other routing protocols is the external
routing information of an AS. Only when the AS’s external routing information is
redistributed to OSPF then it can spread it to the whole OSPF network.
Command Function
ZXR10(config-router)#redistribute < protocol> [ as < as-number> ] [ This control the redistribution of routes
peer < peer-address> ] [ tag < tag-value> ] [ metric < metric-value> ] [ of other routing protocols to the OSPF.
metric-type < type> ] [ route-map < map-tag> ]
4-8

4.2.11 Configuring OSPF Authentication

In order to improve the security of routing processes, OSPF authentication can be
configured on router.
1 ZXR10(config-router)#area < area-id> authentication [ This performs authentication on the

message-digest] OSPF area.
2 ZXR10(config-if-vlanX)#ip ospf authentication-key< password> This sets a password for the interface
of simple password authentication.
4.2.12 Enabling Routes to Support Opaque LSA

During the exchange of link state database, opaque LSAs are included in the database
summary list and transmitted to the neighbor routers that also support opaque LSAs.
A router before it floods opaque LSAs to neighbor routers. It first checks whether the
neighbor routers support opaque LSAs or not. Opaque LSAs are transmitted only to the
neighbor routers that support the function and they will be added to the link state retransmit
list of neighbor routers. When LSU packets are multicasted the neighbor routers that do
not support the function receive the LSAs passively and simply discard them.
Command Function
ZXR10(config-router)#capability opaque This enables routes to support opaque

LSAs.
4.2.13 Modifying OSPF Management Distance

Management distance is related to the reliability of the routing information source.
Management distance is an integer between 0 and 255. Higher value represents lower
reliability. If the management distance is 255, the routing information source is unreliable
and the related routes will be ignored.
Command Function
ZXR10(config-router)#distance ospf { [ internal < distance> ] [ ext1 This defines the OSPF route
< distance> ] [ ext2 < distance> ] } management distance based on the
route type.
4-9

4.2.14 Configuring OSPF FRR

4.2.14.1 Setting Route Backup Modes
Command Function
ZXR10(config-router)#fast-reroute alternate-protect-type { default This sets the route backup mode.

| down-stream-path}
ZXR10(config-router)#no fast-reroute alternate-protect-type This removes the set route backup

mode.
Parameter description for the command is as follows:
Parameter Description
default This is a route backup mode providing basic link

protection. That is to say, the sum of the distance
between backup node and the source node and
the distance between the source node and the
destination node must be less than the distance
between the backup node and the destination
node.
down-stream-path This is a route backup mode providing more

strict Down-stream Path. It is requested that the
distance between the backup next hop to the
destination node must be less than the distance
between the source node to the destination node.
This command is available from the platform version 4.8.20.
Example
The route backup mode providing basic link protection is shown as follows:
ZXR10(config)#router ospf 1
ZXR10(config-router)#fast-reroute alternate-protect-type default
4.2.14.2 OSPF Route Backup on Router Outgoing Interface

Command Function
ZXR10(config-if)#ip ospf fast-reroute [ backup-interface < This command implements OSPF route
interface-name> ] backup on router outgoing interface.
ZXR10(config-if)#no ip ospf fast-reroute This command deletes the setting.
4-10

< interface-name> Interface Name
backup-interface Backing up OSPF routes on the outgoing

interface of certain active route
The fast-reroute function is not supported by default on the interface.

This command is available from the version 4.8.20.
Example
This examples shows how to disable the OSPF backup function on fei_1/1 and enables
the OSPF backup function on fei_1/2.
ZXR10(config)#interface fei_1/1
ZXR10(config-if)#no ip ospf fast-reroute
XR10(config)#interface fei_1/1
ZXR10(config-if)#ip ospf fast-reroute backup-interface fei_1/2
4.2.14.3 Displaying FRR Active and Standby Routes

Command Function
show ip backup route This shows FRR active and standby

routes. It can be used in all modes.
Example
This displays FRR active and standby route and management port routes.
ZXR10#show ip backup route
4.2.15 Configuring OSPF BFD

4.2.15.1 Setting All OSPF Interfaces to Support BFD
Command Function
ZXR10(config-router)#bfd-all-interface This sets all OSPF interfaces to support

BFD.
ZXR10(config-router)#no bfd-all-interface This deletes the setting that makes all

OSPF interfaces support BFD.

After this command is configured, all OSPF real interfaces support BFD except for
virtual-link interfaces and sham-link interfaces.
4-11

Example
This example shows how to set all interfaces of OSPF 1 to support BFD.
ZXR10(config-router)#bfd-all-interface
Related Commands:
ip ospf bfd
ip ospf bfd disable
4.2.15.2 Enabling OSPF BFD

Command Function
ZXR10(config-if-vlanX)#ip ospf bfd [ disable] This enables OSPF BFD function on a

certain interface. This command only
takes effect on OSPF interface.
ZXR10(config-if-vlanX)#no ip ospf bfd [ disable] This disables OSPF BFD function on

certain interface. This command only
takes effect on OSPF interface.
OSPF interfaces do not support BFD by default.

ip ospf bfd disable and ip ospf bfd are manually exclusive. They cannot be configured at the
same time. Before one of them is configured, if the other one is enabled, it is necessary
to disable it by using no command.
The ip ospf bfd disable command is supplementary to bfd-all-interface command. When
bfd-all-interface is enabled, ip ospf bfd disable is used to set some interfaces not to support
BFD.
Example
This sets certain interface to support BFD.
ZXR10(config)#interface vlan1
ZXR10(config-if-vlan1)#ip ospf bfd
Related Command:
bfd-all-interface
4-12

4.3 OSPF Configuration Example

4.3.1 Basic OSPF Configuration Example
Run OSPF on R1 and R2. Divide the network into three areas. This is shown in Figure
4-2.
Figure 4-2 BASIC OSPF CONFIGURATION
R1 configuration:
ZXR10_R1(config)#router ospf 1
ZXR10_R1(config-router)#network 192.168.2.0 0.0.0.255 area 23
R2 configuration:

ZXR10_R1(config)#show ip ospf neighbor
OSPF Router with ID (10.1.2.1) (Process ID 1)
Neighbor ID Pri State DeadTime Address Interface

10.1.1.2 1 FULL/DR 00:00:36 192.168.1.2 vlan8
ZXR10_R2(config)#show ip ospf neighbor
OSPF Router with ID (10.1.1.2) (Process ID 1)
Neighbor ID Pri State DeadTime Address Interface

10.1.2.1 1 FULL/BDR 00:00:30 192.168.1.1 vlan8
4-13

4.3.2 Multi-Area OSPF Configuration Example

When a network is big, it should be divided into multiple OSPF areas. This is shown in
Figure 4-3 as an example of multi-area OSPF.
Figure 4-3 MULTI-AREA OSPF CONFIGURATION
1. Area 0.0.0.1 is a NSSA; R1 is an ABR working between the NSSA 0.0.0.1 and the
backbone area. R1 advertises a default route in the local area.
R1 configuration:
ZXR10_R1(config)#interface vlan 1
ZXR10_R1(config-if-vlan1)#ip address 10.0.1.1 255.255.255.252
ZXR10_R1(config-if-vlan1)#exit
ZXR10_R1(config)#interface vlan2
ZXR10_R1(config-router)#network 10.0.0.0 0.0.0.255 area 0.0.0.0
ZXR10_R1(config-router)#area 0.0.0.1 nssa
default-information-originate
2. Area 0.0.0.2 is a stub area; R2 is an ABR working between the Area 0.0.0.2 and the
backbone area. In the stub area, the ABR advertises a default route automatically.
R2 configuration:
4-14

ZXR10_R2(config-router)#area 0.0.0.2 stub
3. R3 is a router in the backbone area 0 and connects to other ASs through a BGP. R3
Configuration can be done as egress router of the whole as to advertise a default route
to the entire OSPF area manually.
R3 configuration:
ZXR10_R3(config-router)#notify default route always
4. R4 is the ASBR in NSSA 0.0.0.1. Both OSPF and RIP run on R4. Routes of RIP can
be redistributed to OSPF.
R4 configuration:
ZXR10_R4(config-router)#area 0.0.0.1 nssa
ZXR10_R4(config-router)#redistribute rip metric 10
5. R5 is a router in stub area 0.0.0.2.
R5 configuration:
ZXR10_R5(config-router)#area 0.0.0.2 stub
4-15

Use the show ip ospf neighbor command to ensure if neighbor is established.
4.3.3 OSPF Virtual Links Configuration Example

An OSPF virtual link is shown in Figure 4-4
Figure 4-4 OSPF VIRTUAL LINK
R1 configuration:
R2 configuration:
ZXR10_R2(config-router)#area 1 virtual-link 10.0.1.2
R3 configuration:
4-16

ZXR10_R3(config-router)#area 1 virtual-link 10.0.0.2

ZXR10_R2(config)#show ip ospf virtual-links
Virtual Link to router 10.0.1.2 is UP
Up for 00:01:57 (Demand circuit, Suppress hello)
Transit area 0.0.0.1
via interface vlan8 10.0.1.1
State PTOP, Transmit Delay(sec) 1,
Cost 1, Authentication Type null
Timer intervals(sec) : Hello 10, Dead 40, Retransmit 5
Adjacency State FULL
Dead time : no use Options : 0x62
In Full State for 00:01:47
ZXR10_R3(config)#show ip ospf virtual-links

Virtual Link to router 10.0.0.2 is UP
Up for 00:00:08 (Demand circuit)
Transit area 0.0.0.1
via interface vlan8 10.0.1.2
State PTOP, Transmit Delay(sec) 1,
Cost 1, Authentication Type null
Timer intervals(sec) : Hello 10, Dead 40, Retransmit 5
Adjacency State INIT
Dead time : 00:00:37 Options : 0x22
In Full State for 00:00:00
4.3.4 OSPF Authentication Configuration Example

Plain text authentication is adopted in Area 0, MD5 encrypted authentication is used in
Area 1. This is shown in Figure 4-5.
4-17

Figure 4-5 OSPF AUTHENTICATION
R1 configuration:
ZXR10_R1(config-if-vlan1)#ip ospf authentication-key ZXR10
ZXR10_R1(config-router)#area 0 authentication
R2 configuration:
ZXR10_R2(config-if-vlan1)#ip ospf authentication-key ZXR10
ZXR10_R2(config-if-vlan2)#ip ospf message-digest-key 1 md5 ZXR10
ZXR10_R2(config-router)#area 0 authentication
ZXR10_R2(config-router)#area 1 authentication message-digest
R3 configuration:
ZXR10_R3(config-if-vlan1)#ip ospf message-digest-key 1 md5 ZXR10
4-18

ZXR10_R3(config-router)#area 1 authentication message-digest

ZXR10_R1(config)#show ip ospf 1
OSPF 1 enable
Router ID 10.1.1.1
Domain ID type 0x5,value 0.0.0.1
Enabled for 02:32:48,Debug on
Number of areas 3, Normal 3, Stub 0, NSSA 0
Number of interfaces 1
Number of neighbors 1
Number of adjacent neighbors 1
Number of virtual links 0
Total number of entries in LSDB 11
Number of ASEs in LSDB 0, Checksum Sum 0x00000000
Number of grace LSAs 0
Number of new LSAs received 16
Number of self originated LSAs 112
Hold time between consecutive SPF 1 secs
Non-stop Forwarding disabled, last NSF restart 02:39:27 ago
(took 0 secs)
Area 0.0.0.0 enable (Demand circuit available)

Enabled for 02:31:56
Area has simple password authentication
Times spf has been run 22
Number of interfaces 1. Up 1
Number of ASBR local to this area 0
Number of ABR local to this area 2
Total number of intra/inter entries in LSDB 4.
Checksum Sum 0x00028590
Area-filter out not set
Area-filter in not set
Area ranges count 0

Area has no authentication
4-19


Checksum Sum 0x0002a5bc
Area ranges count 0

Checksum Sum 0x0001cf91
Area ranges count 0
OSPF 1 enable
Router ID 10.0.1.2
(took 0 secs)

Area has simple password authentication
4-20


Checksum Sum 0x00028391
Area ranges count 0

Area has MD5 authentication
Checksum Sum 0x0002c08e
Area ranges count 0

Checksum Sum 0x0001e787
Area ranges count 0
OSPF 1 enable
Router ID 10.0.1.2
4-21


(took 0 secs)

Area has MD5 authentication
Checksum Sum 0x00008e9a
Area ranges count 0
4.4 OSPF Maintenance and Diagnosis

ZXR10 5900E provides show command for maintenance and diagnosis.
1 ZXR10#show ip ospf This views OSPF process detail.
2 ZXR10#show ip ospf interface [ < interface-name> ] [ process < This checks the current configuration
process-id> ] and state of an OSPF interface.
3 ZXR10#show ip ospf neighbor [ interface < interface-name> ] [ This checks the information of OSPF
neighbor-id < neighbor> ] [ process < process-id> ] neighbors.
4 ZXR10#show ip ospf database This displays all or part of the

information of the link state
database.
5 ZXR10#show ip route ospf This displays router global routing

table and views if OSPF route is in
routing table.
4-22

6 ZXR10#show ip forwarding subnetrt < ip-address> < net-mask> This views driving hardware routing
table and view if hardware routing
ZXR10 5900E also provides debug command for maintenance and diagnosis.
1 ZXR10#debug ip ospf adj This enables OSPF adjacency

relationship debugging.
2 ZXR10#debug ip ospf packet This enables OSPF packet

transmission, receipt debugging,
listen to receipt and transmission of
all OSPF packets.
3 ZXR10#debug ip ospf lsa-generation This enables OSPF LSA generation

debugging.
4 ZXR10#debug ip ospf events This enables OSPF important events

debugging.
4-23

4-24

Chapter 5
IS-IS Configuration
Table of Contents
IS-IS Overview ...........................................................................................................5-1
Configuring IS-IS ........................................................................................................5-3
IS-IS Configuration Example ......................................................................................5-7
IS-IS Maintenance and Diagnosis.............................................................................5-12
5.1 IS-IS Overview

5.1.1 IS-IS Overview
Intermediate System-to-Intermediate System (IS-IS) is a routing protocol that is introduced
by the International Organization for Standardization (ISO) for Connectionless Network
Service (CLNS). IS-IS works on the network layer of the Open Systems Interconnection
(OSI). When IS-IS is expanded and added with the function to support IP routing, it
becomes Integrated IS-IS. IS-IS introduced in this document refers to Integrated IS-IS.
IS-IS is widely used as an Interior Gateway Protocol (IGP) on networks. On the surface,
OSPF and IS-IS have many features in common:
l They both maintain a link state database from which a Dijkstra-based SPF algorithm
computers a shortest-path tree.
l They both use Hello packets to form and maintain adjacencies.
l They both use areas to form a two-level hierarchical topology.
l They both have the capability of providing address summarization between areas.
l They both are classless protocols.
l They both have authentication capabilities.
Since the IS-IS protocol is based on CLNS (not IP), IS-IS uses Protocol Data Unit (PDU)
defined by ISO to implement communications among routers. The types of PDUs used in
IS-IS protocol are as follows:
l Call PDU
l Link state PDU (LSP)
l Sequence Number PDU (SNP)
Where, call PDU is similar to the HELLO packet in the OSPF protocol, which is responsible
for the formation of the adjacency between routers, discovery of new neighbors and the
detection of exit of any neighbors.
IS-IS routers exchange routing information, set up and maintain link state database by
use of link state PDUs. An LSP indicates important information about a router, covering
5-1

area and connected network. SNP is used to ensure reliable transmission of LSPs. SNP
contains summary information about each LSP on a network.
When a router receives an SNP, it compares SNP with link state database. If router loses
an LSP in SNP, it originates a multicast SNP and asks for necessary LSPs from other
routers on the network. LSPs are used in conjunction with SNPs so that IS-IS protocol can
complete reliable route interaction on a large network.
Likewise, the IS-IS protocol also uses Dijkstra SPF algorithm to calculate routes. Based on
the link state database, the IS-IS protocol uses SPF algorithm to calculate the best route
and then adds the route to the IP routing table.
5.1.2 IS-IS Area

For convenience of link-state database management, concept of IS-IS area is introduced.
Routers in an area are only responsible for maintaining the link state database in the local
area to reduce the traffic of the routers themselves.
IS-IS areas are classified into backbone areas and non-backbone areas:
l Routers in the backbone area have the information about the database of the entire
network.
l Routers in a non-backbone area only have information about the area.
Based on the area division, IS-IS defines three types of routers:

l Level 1 router exists in a non-backbone area and only exchanges routing information
with L1 router and L1/L2 router in the area.
l Level 2 router exists in the backbone area and exchanges routing information with
other L2 routers and L1/L2 routers.
l Level 1/Level 2 routers exist in a non-backbone area and exchanges routing
information between non-backbone area and the backbone area.
This IS-Is area division and router types are shown in Figure 5-1.
Figure 5-1 IS-IS AREAS
5-2

Chapter 5 IS-IS Configuration
5.1.3 IS-IS Network Type

There are two network types in IS-IS: broadcast network and point-to-point network which
make IS-IS easy for configuration and implementation.
5.1.4 DIS and Router Priority

In a broadcast network IS-IS protocol is similar to OSPF protocol and uses designated
router (DIS that is Designated Intermediate System). The DIS is responsible for advertising
network information to all routers on the broadcast network and meanwhile all other routers
only advertise one adjacency to the DIS.
The router priority parameters can be IS-IS configured for DIS election. L1 and L2 can
be independently IS-IS configured with different priorities. Upon DIS election, a highest
priority router plays the role of DIS.
If priorities are same for a frame relay interface, a router with higher router ID will be elected
as the DIS. While for an Ethernet interface, a router with higher interface MAC value will
be elected as the DIS.
5.2 Configuring IS-IS

5.2.1 Enabling IS-IS
Command Function
ZXR10(config)# router isis This enables the IS-IS routing process.
5.2.2 Configuring IS-IS Global Parameters

IS-IS parameter configuration covers global parameters and interface parameters. IS-IS
global parameters need to be configured in the IS-IS route mode.
1. To define the operation type, use the following command.
Command Function
ZXR10(config-router)#is-type { level-1| level-1-2| level-2-only} This defines the operation type.
2. To define PSNP (Sequence Number PDU) for point to point networks, use the following
command.
Command Function
ZXR10(config-if-vlanX)#isis psnp-interval < interval> [ level-1| level-2] This defines PSNP (Sequence Number
PDU) for point to point networks.
5-3

3. To notify insufficient resources of router running as IS-IS protocol, use the following
command.
Command Function
ZXR10(config-router)#set-overload-bit This notifies insufficient resources of

router running as IS-IS protocol.
4. To configure the policy for advertising the default route, use the following command.
Command Function
ZXR10(config-router)#default-information originate [ always] [ metric < This configures the policy for advertising
metric-value> ] [ metric-type < type> ] [ level-1| level-1-2| level-2] the default route.
5. To summarize entries in IS-IS routing table, use the following command.
Command Function
ZXR10(config-router)#summary-address < ip-address> < net-mask> [ This summarizes entries in IS-IS routing
metric] < metric-value> [ [ level-1| level-1-2| level-2] [ metric] < metric-value> ] table.
5.2.3 Configuring IS-IS Interface Parameters

Interface IS-IS parameters need to be configures on the interface running IS-IS.
1 ZXR10(config-if-vlanX)#isis circuit-type { level-1| level-1-2| This designates an operation types

level-2-only} for an interface.
2 ZXR10(config-if-vlanX)#isis hello-interval < interval> [ level-1| This defines an interval for adjacent
level-2] routers hello packet.
3 ZXR10(config-if-vlanX)#isis hello-multiplier < multiplier> [ level-1| This configures isis hello-multiplier in

level-2] order to save time for sending hello
packets.
4 ZXR10(config-if-vlanX)#isis lsp-interval < interval> [ level-1| This sets time interval for transmitting
level-2] LSP packets.
5 ZXR10(config-if-vlanX)#isis retrasmit-interval < interval> [ level-1| This sets LSP packet retransmission
level-2] internal.
6 ZXR10(config-if-vlanX)#isis priority < priority> [ level-1| level-2] This designates DIS election priority
of an interface.
7 ZXR10(config-if-vlanX)#isis metric < metric-value> [ level-1| This configures IS-IS metric of an

level-2] interface to participate in calculation
for number of shortest IS-IS paths.
5-4

8 ZXR10(config-if-vlanX)#isis csnp-interval < interval> [ level-1| This configures IS-IS CSNP interval
level-2] in order to set the interval between
CSNP packets.
5.2.4 Configuring IS-IS Authentication

ZXR10 5900E supports plain text authentication and MD5 encryption authentication.
1 ZXR10(config-if-vlanX)#isis authentication-type { text| md5} [ This sets the authentication method

level-1| level-2] for an interface.
2 ZXR10(config-router)#authentication-type { text| md5} [ level-1| This sets the authentication method

level-2] for LSP packets.
For each authentication modeZXR10 5900E supports three type authentication modes
1 ZXR10(config-if-vlanX)#isis authentication< key> [ level-1| level-2] This sets interface authentication.
2 ZXR10(config-router)#authentication< key> [ level-1| level-2] This sets LSP authentication.
3 ZXR10(config-router)#enable-snp-authentication This sets SNP authentication.
Configure SNP authentication, and the authentication character string is “welcome”.

ZXR10(config)#router isis
ZXR10(config-router)#authentication welcome
ZXR10(config-router)#enable-snp-authentication
5.2.5 Configuring IS-IS FRR

5.2.5.1 Enabling IS-IS Fast Reroute Function
Command Function
ZXR10(config-router)#fast-reroute { enable} [ alternate-type] { This enables IS-IS fast reroute function.

down-stream-path} To disable the function, use no form of
this command.
enable Enabled globally
5-5

alternate-type Optional FRR types
down-stream-path One type of FRR
The FRR type is IPFRR_LFA by default.

When enabled in global mode, the FRR function is enabled in all interfaces, on which IS-IS
are enabled.
Example
This example shows how to configure IS-IS FRR.
ZXR10(config)#router isis
ZXR10(config-router)#fast-reroute enable
ZXR10(config-router)# fast-reroute alternate-type down-stream-path
Related Commands:
fast-reroute enable
no fast-reroute enable
5.2.5.2 Displaying Topology of Fast Reroute

Command Function
show isis fast-reroute-topology{ [ level-1] [ level-2] } [ vrf< vrf-name> ] This displays the topology of fast
reroute. It can be used in all modes.
level-1 The router is in Level-1 area.
level-2 The router is in Level-2 area.
vrf< vrf-name> VRF name, in the length of 132 characters.
Example
This example shows how to configure IS-IS FRR.
gar15#show isis fast-reroute-topology level-1
IS-IS ipfrr paths to Level-1 routers
System id Interface Ipfrr interface Ipfrr type metric
0001.0000.0001interface fei_1/1interface fei_1/1 down-stream-path 10
5-6

5.2.6 Configuring IS-IS BFD

Command Function
ZXR10(config-if)#isis bfd-enable This enables IS-IS BFD function.
ZXR10(config-if)#no isis bfd-enable This disables the IS-IS BFD function.
Example
Configuring IS-IS multiple topology.
ZXR10(config-if)#isis bfd-enable
Related Commands:
isis bfd-enable
no isis bfd-enable
5.3 IS-IS Configuration Example

5.3.1 Single Area IS-IS Configuration
Before configuring IS-IS, it is necessary to analyze whole network, plan network topology
and to decide whether it is necessary to divide the network into areas or not. Run multiple
routing protocols on the network according to the network size. The following example
shows the basic configuration of IS-IS on a single-area network. This is shown in Figure
5-2.
Figure 5-2 SINGLE AREA CONFIGURATION
In the above figure, R1 and R2 form Area 1 and they run IS-IS.
R1 configuration:
ZXR10_R1(config)#router isis
ZXR10_R1(config-router)#area 01
ZXR10_R1(config-router)#system-id 00D0.D0C7.53E0
ZXR10_R1(config-router)#exit
5-7


ZXR10_R1(config-if-vlan4)#ip router isis
R2 configuration:
ZXR10_R2(config-router)#system-id 00D0.D0C7.5460

ZXR10_R1(config#show isis adjacency
Interface System id State Lev Holds SNPA(802.2) Pri MT
vlan8 ZXR10 UP/UP L1L2 28/28 0000.1000.0009 64/64
ZXR10_R1(config#show ip route
IPv4 Routing Table:
Dest Mask Gw Interface Owner Pri Metric
10.1.1.0 255.255.255.0 10.1.1.2 vlan10 direct 0 0
10.1.1.2 255.255.255.255 10.1.1.2 vlan10 address 0 0
192.168.1.0 255.255.255.0 192.168.1.1 vlan24 direct 0 0
192.168.1.1 255.255.255.255 192.168.1.1 vlan24 address 0 0
192.168.2.0 255.255.255.0 192.168.2.1 vlan8 direct 0 0
192.168.2.1 255.255.255.255 192.168.2.1 vlan8 address 0 0
192.168.6.0 255.255.255.0 192.168.2.2 vlan8 isis-l1 115 20
ZXR10_R2(config)#show isis adjacency

Interface System id State Lev Holds SNPA(802.2) Pri MT
vlan8 ZXR10 UP/UP L1L2 8/8 0019.8310.2321 64/64
5-8

ZXR10_R2(config)#show ip route
IPv4 Routing Table:
10.1.1.0 255.255.255.0 10.1.1.3 vlan1 direct 0 0
10.1.1.3 255.255.255.255 10.1.1.3 vlan1 address 0 0
192.168.1.0 255.255.255.0 192.168.2.1 vlan8 isis-l1 115 20
192.168.2.0 255.255.255.0 192.168.2.2 vlan8 direct 0 0
192.168.2.2 255.255.255.255 192.168.2.2 vlan8 address 0 0
192.168.6.0 255.255.255.0 192.168.6.1 vlan24 direct 0 0
192.168.6.1 255.255.255.255 192.168.6.1 vlan24 address 0 0
5.3.2 Multiple Area IS-IS Configuration

If a network is large, then divide IS-IS network into multiple areas. Routers in a geographic
area or of similar functions can be put into one area. This reduces the demand on memory.
Routers in an area only need to maintain a small link state database. This is shown inFigure
5-3.
Figure 5-3 MULTIPLE AREA IS-IS CONFIGURATION
R1 is in Area 1. R2, R3, and R4 are in Area 0. R5 and R6 are in Area 2. Segments in
Area 1 are aggregated on R1. The default route is redistributed to IS-IS on R6.
R1 configuration:
ZXR10_R1(config-router)#system-id 00D0.D0C7.53E0
ZXR10_R1(config-router)#is-type LEVEL-1-2
ZXR10_R1(config-if-vlan4)#isis circuit-type LEVEL-2
5-9

ZXR10_R1(config-router)#summary-address 192.168.100.0 255.255.252.0
metric 10
R2 configuration:
ZXR10_R2(config-router)#system-id 00D0.E0D7.53E0
ZXR10_R2(config-router)#is-type LEVEL-2
R3 configuration:
ZXR10_R3(config-router)#system-id 00D0.E0C7.53E0
5-10

R4 configuration:
ZXR10_R4(config-router)#system-id 00D0.E0E7.53E0
R5 configuration:
ZXR10_R5(config-router)#system-id 00D0.D0CF.53E0
ZXR10_R5(config-router)#is-type LEVEL-1-2
5-11

R6 configuration:
ZXR10_R6(config-router)#system-id 00D0.0ECD.53E0
ZXR10_R6(config-router)#default-information originate
ZXR10_R6(config-router)#redistribute static metric 10
ZXR10_R6(config-router)#end
5.4 IS-IS Maintenance and Diagnosis

ZXR10 5900E provides show command for maintenance and diagnosis.
1 ZXR10#show isis adjacency [ level-1| level-2] This views the current adjacency.
2 ZXR10#show isis circuits [ detail] This displays the information of the

current IS-IS interface.
3 ZXR10#show isis database [ level-1| level-2] [ detail] This views the information of the
current IS-IS database.
5-12

4 ZXR10#show isis topology [ level-1| level-2] This shows the current IS-IS
topology.
5 ZXR10#show ip route [ isis-l1| isis-l2] This views global routing table and
check if IS-IS route is in this route.
6 ZXR10#show ip forwarding subnetrt < ip-address> < net -mask> This views driving hardware routing
table and check if hardware routing
ZXR10 5900E also provides debug command for maintenance and diagnosis.
1 ZXR10#debug isis adj-packets This tracks and shows the received

transmission of IS-IS Hello packets.
2 ZXR10#debug isis snp-packets This tracks and views the SNP

packets which IS-IS receives and
sends and related handling event.
3 ZXR10#debug isis spf-events This tracks and views the debugging

information of IS-IS route calculation
event.
4 ZXR10#debug isis nsf-event This tracks and views the debugging

information of the IS-IS LSP
processing event.
5-13

5-14

Chapter 6
BGP Configuration
Table of Contents
BGP Overview............................................................................................................6-1
Configuring BGP ........................................................................................................6-2
BGP Configuration Example.....................................................................................6-19
BGP Maintenance and Diagnosis .............................................................................6-20
6.1 BGP Overview

Border Gateway Protocol (BGP) is an inter-area routing protocol. BGP exchanges Network
Layer Reachable Information (NLRI) between ASs that run BGP. This information includes
a list of the ASs that the routes pass. They are enough for creating a diagram indicating
the AS connection state. This makes the AS-based routing policy possible and solves the
route loop problem.
BGP Version 4 (BGP4), defined in RFC1771, supports CIDR, supernet, subnet, route
aggregation, and route filtering, and is widely used on the Internet currently.
Border Gateway Protocol (BGP) is an interautonomous system routing protocol. An

autonomous system is a network or group of networks under a common administration
and with common routing policies.
BGP is used to exchange routing information for the Internet and is the protocol used
between Internet service providers (ISP). Customer networks, such as universities and
corporations, usually employ an Interior Gateway Protocol (IGP) such as RIP or OSPF
for the exchange of routing information within their networks. Customers connect to ISPs,
and ISPs use BGP to exchange customer and ISP routes. When BGP is used between
autonomous systems (AS), the protocol is referred to as External BGP (EBGP). If a service
provider is using BGP to exchange routes within an AS, then the protocol is referred to as
Interior BGP (IBGP).
AS indicator is a 16-bit value ranging from 1 to 65535 of which the numbers from 1 to 32767
are available for allocation. Those from 32768 to 64511 are reserved. Those from 64512
to 65534 are used for private ASs (similar to private network addresses in IP addresses).
BGP runs on the basis of a reliable transfer protocol with TCP as its underlying protocol and
TCP port 179. Routers running BGP first set up a TCP connection and then exchange all
the routing table information after authentication. After that when the routing table changes.
They send route update messages to all BGP neighbors who will further spread the routing
information until it reaches the whole network.
6-1

Routes learned via BGP have associated properties that are used to determine the best
route to a destination when multiple paths exist to a particular destination. These properties
are referred to as BGP attributes. There are four types of path attributes:
1. Mandatory AttributeIt must appear in the route description.
AS-path
Next hop
Origin
2. Self-Defined AttributeIt does not have to appear in the route description.
Local preference
Atomic aggregate
3. Optional Transitional Attribute It does not have to be supported by all BGP
implementations. If it is supported, it can be forwarded to BGP neighbors. If it is not
supported by the current router, it should be forwarded to other BGP routers.
Aggregator
Community
4. Optional Non-Transitional Attribute It should be deleted by the routers that do not
support it.
Multi-exit-discriminator (MED)
6.2 Configuring BGP

6.2.1 Enabling BGP
1 ZXR10(config)#router bgp < as-number> This starts the BGP process.
2 ZXR10(config-router)#neighbor < ip-address> remote-as < This configures BGP neighbors.

number>
3 ZXR10(config-router)# network < ip-address> < net-mask> This configures BGP to advertise a
network.
Example
R1 is in AS 100 and R2 in AS 200. This is shown in Figure 6-1.
6-2

Chapter 6 BGP Configuration
Figure 6-1 BASIC BGP CONFIGURATION
R1 configuration:
ZXR10_R1(config)#router bgp 100
ZXR10_R1(config-router)#neighbor 10.1.1.1 remote-as 200
R2 configuration:
In the above configuration, R1 and R2 define each other as BGP neighbor. R1 and
R2 belong to different Ass. They will set up an EBGP session. R1 advertises network
182.16.0.0/16 and R2 advertises network 182.17.0.0/16.
IPv4 Routing Table:
Dest Mask Gw Interface Owner Pri Metric
10.0.1.0 255.255.255.252 10.0.1.2 vlan8 direct 0 0
10.0.1.2 255.255.255.255 10.0.1.2 vlan8 address 0 0
10.1.1.0 255.255.255.0 10.1.1.2 vlan10 direct 0 0
10.1.1.2 255.255.255.255 10.1.1.2 vlan10 address 0 0
182.16.0.0 255.255.0.0 182.16.1.1 vlan24 direct 0 0
182.16.1.1 255.255.255.255 182.16.1.1 vlan24 address 0 0
182.17.0.0 255.255.0.0 10.0.1.1 vlan8 bgp 20 0
IPv4 Routing Table:
10.0.1.0 255.255.255.252 10.0.1.1 vlan8 direct 0 0
10.0.1.1 255.255.255.255 10.0.1.1 vlan8 address 0 0
10.1.1.0 255.255.255.0 10.1.1.3 vlan1 direct 0 0
10.1.1.3 255.255.255.255 10.1.1.3 vlan1 address 0 0
182.16.0.0 255.255.0.0 10.0.1.2 vlan8 bgp 20 0
182.17.0.0 255.255.0.0 182.17.1.1 vlan24 direct 0 0
6-3

182.17.1.1 255.255.255.255 182.17.1.1 vlan24 address 0 0
6.2.2 Configuring BGP Route Advertisement

1 ZXR10(config-router)#network This advertises network directly

connected to the current router.
2 ZXR10(config-router)#redistribute < protocol> [ metric < This redistributes the routes learnt
metric-value> ] [ route-map < map-tag> ] by other routing protocols to BGP.
Example
Figure 6-2 shows an example of advertising routes to BGP by redistribution.
Figure 6-2 BGP ROUTE ADVERTISEMENT
R3 configuration:
ZXR10_R3(config-router)#redistribute ospf
6.2.3 Configuring BGP Aggregate Advertisement

This section describes that BGP can aggregate multiple learnt routes to one route and
advertise it. These entries in a routing table can be significantly reduced.
Command Function
ZXR10(config-router)#aggregate-address < ip-address> < net-mask> [ This creates an aggregate policy in the
count < count> ] [ as-set] [ summary-only] [ strict] BGP routing table.
6-4

Example
R1 and R2 advertise routes 170.20.0.0/16 and 170.10.0.0/16 respectively.
R3 aggregates the two routes into 170.0.0.0/8 and advertises it to R4. After route
aggregate is configured, R4’s routing table can only learn the aggregate route 170.0.0.0/8.
This is shown in Figure 3.
Figure 6-3 BGP AGGREGATE ADVERTISEMENT
R1 configuration:
R2 configuration:
R3 configuration:
6-5

ZXR10_R3(config-router)# aggregate-address 170.0.0.0 255.0.0.0
summary-only count 0
R3 learns both routes 170.20.0.0 and 170.10.0.0 but it only advertises the aggregate route
170.0.0.0/8. Pay attention to the parameter summary-only in the command. Without that
parameter, R3 will advertise both routes in addition to the aggregate route.
R4 configuration:
6.2.4 Configuring Multihop in EBGP

EBGP neighbor is established on the interfaces directly connecting two routers. If EBGP
neighbor is to be established on indirectly-connected interfaces, neighbor ebgp-multihop
command is used in order to perform EBGP multihop configuration. It is suitable for IGP or
static routing configuration to enable indirectly-connected neighbors to communicate with
each other. This section describes the EBGP neighbor to establish on indirectly-connected
interfaces.
Command Function
ZXR10(config-router)#neighbor < ip-address> ebgp-multihop [ ttl < This configures EBGP neighbors on
value> ] indirectly-connected interface
Example
R1 needs to set up the adjacency relationship with the indirectly-connected interface
180.225.11.1 on R2. Neighbor ebgp-multihop command is configured. This is shown in
Figure 6-4.
6-6

Figure 6-4 CONFIGURATION OF BGP MULTIHOP
R1 configuration:
ZXR10_R1(config-router)#neighbor 180.225.11.1 ebgp-multihop
R2 configuration:
6.2.5 Filtering Routes by Router

Route filtering and attributes are the basis of BGP decision. Route filtering allows
controlling the attributes of the imported and exported routes based on needs.
Route map is used to control the routing information and redistribute routes between areas
by defining conditions. Route map usually works with route attributes to allow making
decisions on routes.
1 ZXR10(config)#route-map < map-tag> [ permit| deny] [ < This defines a route map
sequence-number> ]
2 ZXR10(config-router)#neighbor < ip-address> route-map < This filters the routes advertised or
map-tag> { in| out} being advertised to neighbors.
Example
To configure routes filtering by routers, an example is given below:
ZXR10_R1(config-router)#neighbor 182.17.20.1 route-map MAP1 out
ZXR10_R1(config-router)#neighbor 182.17.20.1 send-med
ZXR10_R1(config)#route-map MAP1 permit 10
ZXR10_R1(config-route-map)#match ip address 1
ZXR10_R1(config-route-map)#set metric 5
ZXR10_R1(config-route-map)#exit
ZXR10_R1(config)#acl standard number 1
6-7

ZXR10_R1(config-std-acl)#rule 1 permit 172.3.0.0 0.0.255.255
MAP1 is a router defined in above example. Its route map allows the network 172.3.0.0 to
be advertised to AS 200 and sets its MED to 5. The route map is often used with match
and set command. Match command defines the match conditions. Set command defines
action to be executed when match conditions are met by match command.
6.2.6 Filtering Routes Using NLRI

To set limit to a router when it gets or advertises the routing information. The route updates
can be filtered from or destined for a particular neighbor. The filter has an update list of
the neighbors where the route updates are from or destined for.
Example
R1 and R2 are IBGP peers. R1 and R3 are EBGP peers. R2 and R4 are EBGP peers.
This is shown in Figure 6-5.
Figure 6-5 FILTERING ROUTES USING NLRI
Avoid AS100 from being a transitional AS and advertise the network 192.18.10.0/24 from
AS300 to AS200. Filtering on R1 is performed.
The configuration on R1 is shown below.
ZXR10_R1(config-router)#no synchronization
6-8

ZXR10_R1(config-std-acl)#rule 1 deny 192.18.10.0 0.0.0.255
ZXR10_R1(config-std-acl)#rule 2 permit any
To prevent R1 from transmitting the prefix 192.18.10.0/24 to AS200, route-map command

and ACL is used.
6.2.7 Filtering Route Based on AS_PATH

When all routes in one or multiple ASs need to be filtered, AS path-based route filtering is
used. It avoids the complexity caused by prefix filtering.
To set a new ACL for imported and exported updates based on AS paths, use the following
command.
Command Function
ZXR10(config)#ip as-path access-list < acl-number> { permit| deny} < This sets a new ACL.
as-regular-expression>
Use the route filtration based on AS path to prevent R1 from advertising the network
192.18.10.0/24 to AS200.
The configuration is shown below.
ZXR10_R1(config-route-map)#match as-path 1
ZXR10_R1(config)#ip as-path access-list 1 permit ^$
In this configuration, the list is accessed through AS paths, which makes R1 advertise only
the networks from AS100 to AS200, so that the network 192.18.10.0/24 can be filtered.
6.2.8 Setting LOCAL_PREF Attribute

Value of the Local preference attribute is used for routing between the IBGP peers inside
an AS.
To set the local preference value of the BGP advertised routes, use the following command.
6-9

Command Function
ZXR10(config-router)#bgp default local-preference < value> This sets the local preference value of
the BGP advertised routes.
R3 and R4 synchronously learn the route to 170.10.0.0. Local preference value of R4 is

greater; packets from AS256 to the destination are passed to R4. This is shown in Figure
6-6.
Figure 6-6 LOCAL_PREF ATTRIBUTE
The following two modes are used to configure the LOCAL_PREF attribute.
1. Set the LOCAL_PREF attribute with the BGP default local-preference command.
R3 configuration:
ZXR10_R3(config-router)#bgp default local-preference 150
R4 configuration:

ZXR10_R4(config-router)#bgp default local-preference 200
2. Set the LOCAL_PREF attribute with the route-mapcommand.

R4 configuration:

ZXR10_R4(config-router)#neighbor 3.3.3.2 route-map setlocalin in
6-10

....
ZXR10_R4(config)#ip as-path access-list 7 permit ^300$
...
ZXR10_R4(config)#route-map setlocalin permit 10
ZXR10_R4(config-route-map)#match as-path 7
ZXR10_R4(config-route-map)#set local-preference 200
ZXR10_R4(config)#route-map setlocalin permit 20
ZXR10_R4(config-route-map)#set local-preference 150
6.2.9 Setting MED Attribute

Metric attribute is also called the Multi_Exit_Discrimination attribute (MED) .Router only
compares the adjacent Metric value of the BGP from the same AS by default. If comparing
adjacent Metric values of neighbors from different ASs, execute necessarily the MED
attribute command to forcefully compare them.
To configure the Metric values of neighbors from different As, use the bgp always-compar
e-med command.
R1 synchronously receives the 180.10.0.0 update from R2, R3 and R4. Only compare the
Metric values of the adjacent R3 and R4 from the same AS by default.
Metric value of the R3 is smaller than that of the R4. Therefore, for the 180.10.0.0 update,
the R1 preferentially uses the R3. This is shown in Figure 6-7.
Figure 6-7 MED ATTRIBUTE
The following is to set the MED value with the route-map command.
R3 configuration:
ZXR10_R3(config-router)#neighbor 2.2.2.2 route-map setmetricout out
6-11


ZXR10_R3(config)#route-map setmetricout permit 10
R4 configuration:
R2 configuration:
In the following contents, force R1 to compare the Metric values with the bgp always-com
pare-med command. The Metric value of the R2 is smaller than that of the R3. Therefore,
for the 180.10.0.0 update, the R1 selects the R2 rather than the R3.
R1 configuration:
ZXR10_R1(config-router)#bgp always-compare-med
6.2.10 Setting Community Attribute

Community attribute is optional transition attribute, with the range from 0 to 4,294,967,200.
According to the Community attribute, decisions are made on a group of routes.
Several recognized definitions of the Community attribute as follows:
l No-export: Forbid advertising the neighbors of the EBGP.
l No-advertise: Forbid advertising any neighbors of the BGP.End of steps.
6-12

l No-export-subconfed: Forbid advertising the route with the attribute outside the
confederation.
1 ZXR10(config)#route-map This defines the Community attribute
2 ZXR10(config-router)#neighbor < ip-address> send-community This sends the community attribute

to neighbor
In the following configuration, the R1 notifies the neighbor to forbid advertising the route
192.166.1.0/24 to other EBGP neighbors.
R1 configuration:
ZXR10_R1(config-router)#neighbor 3.3.3.3 send-community
ZXR10_R1(config-router)#neighbor 3.3.3.3 route-map setcommunityout
ZXR10_R1(config)#route-map setcommunity permit 10
ZXR10_R1(config-route-map)#set community no-export
ZXR10_R1(config)#route-map setcommunity permit 20
6.2.11 Setting BGP Synchronization

In the AS100 both the R1 and the R2 run the IBGP, R5 does not run the BGP. This is shown
in Figure 6-8.
6-13

Figure 6-8 BGP SYNCHRONIZATION CONFIGURATION
R2 learns the route 170.10.0.0 through the IBGP. The next-hop is 2.2.2.1. If R2 reaches
the 170.10.0.0 then actual next-hop is R5. R5 without the route 170.10.0.0 will throw off
the packet. At the moment R2 is also thrown off in R5 if R2 notifies R4 that it has the route
170.10.0.0 itself.
It is necessary to make R5 have the route to the 170.10.0.0 if the packet with the destination
of 170.10.0.0 smoothly passes R5 and reaches R3. Therefore route redistribution should
be used to help R5 learn the route through IGP. R2 must wait for R2 to learn route by
means of the IGP (through R5) before it advertises BGP route to EBGP neighbor. This is
called the route synchronization.
Synchronize both the BGP and the IGP with the synchronization command.
ZXR10 5900E has booting as its synchronization function by default.
For the transitional AS, the route learned from other AS should be advertised to the third
party AS. If the non-BGP route exists inside the AS, the route synchronization should be
used. Here R2 adopts route synchronization.
It is unnecessary to use route synchronization when not advertising the BGP route to the
third party AS or when the routers inside the As run the BGP.
The following configuration shows how to disable the R2 route synchronization.

6-14

6.2.12 Setting BGP Router Reflector

For the BGP routers inside the same AS, the adjacency must be established between every
two routers according to requirements and contribute to the formation of all interconnection.
As the number of IBP routers increases, the number of neighbors will ascend by n*(n-1)/2
(n refers to the number of the IBGP routers). Router reflector and confederation is used to
reduce workload of maintenance and configuration.
Running of IBGP routers inside the AS, select one of preceding routers as Router Reflector
(RR). Take other IBGP routers as clients which only establish adjacency with the RR. All
clients pass the RR to reflect routes. Thus, the number of neighbors decreases to (n-1).
Set the neighbors as the Router Reflector client peers with the neighbor < ip-address> rou
ter-refletor-client command.
AS100 has two router reflectors: R3 and R4. R5 and R6 are the clients of R4. R1 and R2
are the clients of R3. This is shown in Figure 6-9.
Figure 6-9 BGP ROUTER REFLECTOR CONFIGURATION
R3 configuration:
ZXR10_R3(config-router)#neighbor 2.2.2.2 route-reflector-client
ZXR10_R3(config-router)#neighbor 1.1.1.1 route-reflector-client
6-15

R2 configuration:
When a route is received by the RR, the RR reflects according to types of different peers.
1. If a route comes from non-client peers, it is reflected to all client peers.
2. If a route comes from client peers, it is reflected to all non-client peers and client peers.
3. If a route comes from the EBGP peer, it is reflected to all non-client peers and client
peers.
When there are multiple RRs inside an AS, multiple RRs inside an AS are classified as a
cluster. There may be multiple clusters inside one AS. A cluster contains more than one
RR.
6.2.13 Setting BGP Confederation

Route confederation has the same function as router reflector. The purpose is to reduce
the number of IBGP connection neighbors established inside the same AS. Route
confederation divides an AS into multiple sub-Ass. Multiple IBGP routers inside AS
belongs respectively to the sub-Ass. IBGP is established inside the sub-AS. EBGP is
established between sub-ASs. The sub-AS number is called confederation number. For
AS outside the sub-AS is invisible.
1 ZXR10(config-router)#bgp confederation identifier < value> This sets the confederation ID.
2 ZXR10(config-router)#bgp confederation peers < value> [ …< This sets the confederation peer AS
value> ] number.
Example
AS200 has five BGP routers. Divide them into two sub-ASs. One is defined as AS65010
containing R3, R5 and R6. The other one is defined as AS65020 containing R4 and R7.
This is shown in Figure 6-10.
6-16

Figure 6-10 BGP CONFEDERATION CONFIGURATION
R3 configuration:
ZXR10_R3(config-router)#bgp confederation identifier 200
ZXR10_R3(config-router)#bgp confederation peers 65020
R5 configuration:

ZXR10_R5(config-router)#bgp confederation identifier 200
When establishing the adjacency EBGP adjacency between R3 and confederation peers
is established. IBGP adjacency in the confederation is established. This adjacency
also occurs between R3 and AS100. The AS100 does not know the existence of the
confederation so R1 still establishes the adjacency with R3 in AS200.
R1 configuration:

6.2.14 Setting BGP Route Dampening

BGP provides a Route dampening mechanism to reduce the stability caused by Route
Flap.
6-17

Each time the flap occurs the route is given a penalty of 1000. Route will be suppressed to
advertise when the Penalty reaches the Suppress-limit. Each time the half-life-time comes,
Penalty exponentially decreases. The suppressed and advertised route will be cancelled
when the Penalty decreases to the Reuse-limit.
To make the BGP route damping effective or modify the BGP route damping factors,
perform the following steps:
Command Function
ZXR10(config-router)#bgp dampening [ < half-life> < reuse> < suppress> This makes the BGP route damping
< max-suppress-time> | route-map < map-tag> ] effective or modify the BGP route
damping factors.
l Half-life-time: the range is from 1 to 45min and the default value is 15min.
l Reuse-value: the range from 1 to 20000 and the default value is 750.
l Suppress-value: the range from 1 to 20000 and the default value is 2000.
l Max-suppress-time: the range from 1 to 255, four times half-life-time by default.
Example
Boot the suppression function in the router:
ZXR10(config)#router bgp 100
ZXR10(config-router)#bgp dampening
ZXR10(config-router)#network 203.250.15.0 255.255.255.0
ZXR10(config-router)#neighbor 192.208.10.5 remote-as 300
6.2.15 Configuring BGP FRR

Command Function
ZXR10(config-router)#bgp frr This configures BGP FRR function.
ZXR10(config-router)#no bgp frr This disables BGP FRR function.
This function is disabled by default.
Example
This configures BGP FRR function.
ZXR10(config)#router bgp 1
ZXR10(config-router)#bgp frr
6-18

6.3 BGP Configuration Example

The following is a BGP comprehensive example. It involves the actual applications of such
BGP functions as route aggregation and static route redistribution. This is shown in Figure
6-11.
R4 establishes the EBGP with the R1. R1 establishes the IBGP with R2. R2 establishes
the multi-hop EBGP with tR5.
Suppose that R4 has four static routes marked at the top right corner of the Figure 6-11.
In R4 configuration, only aggregate and advertise the network segment 192.16.0.0/16 and
forbid advertising the network segment 170.16.10.0/24 outside by the BGP through the
route figure.
EBGP multi-hop relationship is established between R2 and R5 through R3. At the
moment, ensure that the addresses on which to establish adjacency can be interconnected
in the two routers. This is shown in Figure 6-11.
Figure 6-11 BGP CONFIGURATION
R4 configuration:
ZXR10_R4(config)#route bgp 2
ZXR10_R4(config-router)#redistribute static
ZXR10_R4(config-router)#aggregate-address 192.16.0.0 255.255.0.0
count 0 as-set summary-only
ZXR10_R4(config-router)#neighbor 172.16.20.2 route-map torouter1
out
ZXR10_R4(config-std-acl)#exit
ZXR10_R4(config)#route-map torouter1 deny 10
ZXR10_R4(config)#route-map torouter1 permit 20
6-19

R1 configuration:
ZXR10_R1(config-router)#neighbor 172.16.1.2 next-hop-self
R2 configuration:
172.16.20.2
ZXR10_R2(config-router)#neighbor 172.16.1.1 next-hop-self
ZXR10_R2(config-router)#neighbor 183.16.20.2 ebgp-multihop 2
ZXR10_R2(config-router)#neighbor 183.16.20.2 route-map
torouter5 in
ZXR10_R2(config-std-acl)#exit
ZXR10_R2(config)#route-map torouter5 deny 10
ZXR10_R2(config)#route-map torouter5 permit 20
R5 configuration:
183.16.20.2
ZXR10_R5(config-router)#neighbor 173.16.20.2 ebgp-multihop 2
6.4 BGP Maintenance and Diagnosis

1 ZXR10(config)#show ip bgp protocol This displays the configuration

information of the BGP module.
2 ZXR10(config)#show ip bgp neighbor [ in| out] < ip-address> This displays the BGP adjacency
and the current neighbor state.
6-20

3 ZXR10(config)#show ip bgp[ network < ip-address> [ mask < This displays the BGP routing table
net-mask> ] ] entries.
4 ZXR10(config)#show ip bgp summary This displays the connection state of

all BGP neighbors.
5 ZXR10(config)#show ip route [ < ip-address> < net-mask> ] bgp This displays routing table and
checks if BGP in the route table.
6 ZXR10(config)#show ip forwarding subnetrt < ip-address> < This displays hardware driving
net-mask> routing table.
7 ZXR10#debug ip bgp in This traces and show the notification

packet sent by the BGP.
8 ZXR10#debug ip bgp out This tracks and display the

notification packet sent by the BGP.
9 ZXR10#debug ip bgp events This traces and display the transition

of state machine connected to the
BGP.
Example
This example is to trace the state transition of the BGP with the debug ip bgp events
command.
ZXR10#debug ip bgp events
BGP events debugging is on
ZXR10#
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
ZXR10#
6-21

6-22

Chapter 7
MPLS Configuration
Table of Contents
MPLS Overview .........................................................................................................7-1
Configuring MPLS ......................................................................................................7-4
Example for Configuring MPLS ..................................................................................7-7
MPLS Maintenance and Diagnosis.............................................................................7-8
7.1 MPLS Overview

Multi-Protocol Label Switching(MPLS) is a multi-layer switching technology, which
combines L2 switching technologies with L3 routing technologies and uses labels to
aggregate forwarding information. MPLS runs under the routing hierarchy, supports
multiple upper-level protocols and can be implemented on multiple physical platforms.
Label switching can be visually imagined as postal codes for mails. With the application
of postal codes, the destination addresses and some special requirements (such as QoS,
CoS and management information) of the mails are coded in a certain method to facilitate
rapid and efficient mail processing and speed up the routing of the mails to individual
destinations. The basic concept of MPLS is the assignment of labels, that is, labels are
bound with network layer routes.
The basic MPLS routing mode is routing hop by hop, which permits a forwarding
mechanism simpler than packets and can implement faster routing. Since the common
label allocation method and generic routing protocols are used in multiple types of media
(such as packets, cells and frames), MPLS supports efficient definite routing mode (such
as QoS) that can be used to fulfill different purposes, common traffic engineering method
and other operation modes.
LDP (Label Distribution Protocol) is the core protocol of MPLS. LDP works in conjunction
with standard network layer routing protocols and distributes label information among
different pieces of equipment on an MPLS network in the connectionless working mode.
LDP divides Forwarding Equivalence Class (FEC) based on IP prefixes. In an MPLS
network, internal gateway protocols are used to discover the information about IP prefixes.
When a Label Switch Router (LSR) discovers such information, it will distribute a label to
the FEC and advertise the label to all upstream LDP neighbors.
The hop-by-hop dynamic label distribution of LDP leads to the generation of a series of
labeled paths, called Label Switched Paths (LSPs). Along these LSPs, the label traffic can
pass the MPLS backbone to reach a designated destination.
7-1

With this capability, a service provider can deploy MPLS-based IP VPN, as well as the IP
+ ATM service over multi-proxy MPLS networks.
The propagation process of IP packets through the MPLS backbone is as follows.
1. An ingress border LSR receives a packet, puts the packet into an FEC and then uses
the outgoing label corresponding to the FEC to label the packet. For a unicast IP route
based on destination address, the FEC corresponds to a destination subnet.
2. A backbone LSR receives the labeled packet, searches the label forwarding table and
uses a new outgoing label to replace the label in the input packet.
3. An egress border LSR receives the labeled packet, deletes the label and performs the
traditional L3 search for the IP packet.
7.1.1 MPLS Working Principle

MPLS is a label-based IP routing method. These labels can be used to stand for
hop-by-hop mode or explicit routes and also to indicate QoS, VPN and the transmission
of special types of traffic (or special user’s traffic) on a network.
MPLS uses a simplified technology to complete conversion between L2 and L3. MPLS
can provide a label for each IP packet that can be encapsulated into a new MPLS packet
in conjunction with the IP packet, to determine the transmission path and priority sequence
of the IP packet.
Before forwarding the IP packet according to the corresponding path, an MPLS switch will
read the header label of the MPLS packet, but will not read the information such as the
IP address in each IP packet. Therefore, the switching and routing speed of packets is
greatly improved.
Labels are used to forward headers of packets, and format of packet headers depends
upon network features. In a switch network, a label is an independent 32-bit header.
When an IP packet enters the network core, a border router will assign a label to it. Since
then, the MPLS equipment will check the label information all the time and switch the
labeled packet to the destination. Since route processing is reduced, the waiting time of
the network is shortened and the scalability is improved.
7.1.2 MPLS Label Header

An MPLS label is inserted between an L2 header and an L3 packet. Therefore, an MPLS
label header is also called a shim header. The length of an MPLS label header is four
bytes, containing a 20-bit label, a 3 test bits, a 1-bit stack bottom tag and 8-bit TTL (Time-To
Live).
A router sending an MPLS packet needs to use a method to notify a router receiving the
packet. The transmitted packet is not a pure IP packet, but an MPLS datagram.
For Ethernet packets, Ethernet types 8847 and 8848 (in hexadecimal notation) are used
to label MPLS packets.
7-2

Chapter 7 MPLS Configuration
7.1.3 MPLS LDP

LDP label binding is an association relation between a destination prefix and a label.
Labels used for label binding are locked from a label set called "label space".
LDP uses six bytes to name a label space, called LDP identity (LDP Id), which is composed
of two parts: the first four bytes indicate the router ID of the router that has the label space
(router id).
The rules for selecting the router ID of an LDP on a ZXR10 5900E are as follows:
1. If the mpls ldp router-id command is used to designate the address of an interface
as the router ID, and also the interface has an IP address and is in UP status, the
interface will serve as the router ID.
2. If there are loopback interfaces configured with an IP address, the maximum IP
address among the IP addresses of all the loopback interfaces will serve as the router
ID;
3. The maximum one among the IP addresses of interfaces configured with IP addresses
in UP status is selected as the router ID.
An LSR sends LDP hello messages periodically, indicating that it hopes to advertise label
binding to find LDP peers. A Hello message contains the LDP ID of the label space that
the LSR wants to advertise. The LDP uses UDP as a transmission protocol to send the
Hello message, with the port ID of 646.
When an LSR receives a Hello message from another LSR, it will "think" that it has found
an LSR and its special label space. If two LSRs find each other, they will start to set up an
LDP session.
LDP defines two types of discovery mechanisms. At present, ZXR10 59E support the basic
discovery mechanism, used to discover directly-connected peers. The Hello message in
the basic discovery mechanism is sent on all interfaces configured with LDP, with multicast
addresses of "all devices on the subnet" as the destination addresses.
The procedure for setting up an LDP session between two LSRs is as follows.
1. Open a TCP connection used for label distribution
On a ZXR10 59E, by default, the router ID of LDP serves as the transport address of
the TCP connection. Alternatively, in the interface configuration mode, the mpls ldp
discovery transport-address command can be used to designate an IP address or the
source IP address for sending Hello messages can serve as the transport address of
the TCP connection.
Note:
To set up a TCP connection, an LSR should have a route to the TCP transport address of another
LSR.
2. Negotiate LDP session parameters
7-3

Parameters to be negotiated are label distribution mode (independent downstream

label distribution/downstream label distribution on demand) and other parameters.
After the LDP session is set up, the LDP can start label distribution.
7.2 Configuring MPLS

The MPLS configuration covers the following contents.
1. In global configuration mode, enable MPLS LDP.
mpls ip (Global Configuration)
Enables LDP to set up an LSP along a common hop-by-hop routing path. Use no
command to disable LDP.
2. Enable MPLS LDP in VLAN L3 interface.
mpls ip(Interface Configuration)
Enable LDP label switch on interface. Use no form of this command to disable LDP
label switch.
3. Configure the label range which can be used by LDP in global configuration mode.
mpls label range < min-label> < max-label>
Configure the label range, which can be used by LDP. Use no command to reset the
default setting.
4. In global configuration mode, control the LDP to create the FEC item (that is, FEC
filtering policy) for which destination network sections.
mpls ldp access-fec { for < prefix-access-list> | host-route-only| force| bgp}

The for < prefix-access-list> parameter sets to filter based on access list. All destination
addresses permitted by access list can create FEC, otherwise, FEC can not be
created.
The host-route-only parameter configures that only create FEC for destination network
segments with 32-bit mask
5. In global configuration mode, controls locally distributed labels (incoming labels) to be
distributed upstream by means of LDP
mpls ldp advertise-labels [ { for < prefix-access-list> [ to < peer-access-list> ] | old-style} ]

Controls locally distributed labels (incoming labels) to be distributed by means of LDP.
This command controls to which neighbors the destination segments are advertised.
6. In global configuration mode, it sets LDP session back-off and reestablishment

mechanism.
mpls ldp backoff < initial-backoff> < maximum-backoff>
It prevents two incompatible LSRs from entering undying session establishment to

failure circle.
7-4

7. Configures the interval for sending the LDP hello discovery message and the timeout
time of the discovered LDP neighbor between direct-connected/undirect-connected
LSRs in global configuration mode.
mpls ldp discovery { hello | targeted-hello} { holdtime < holdtime> | interval < interval> }
8. Configures the transport address parameter contained in the Hello message in L3 vlan
interface mode.
mpls ldp discovery transport-address { interface| < ip-address> }
By default, a ZXR10 59E router regards the router ID on an interface in frame mode
as the transport address and advertises the address in the Hello message. The
above command can change the default behavior of the router on an interface. If the
parameter interface is used, the LDP will advertise the IP address of the interface in
the Hello message of the interface. If the parameter < ip-address> is used, the LDP
will advertise the IP address of the interface in the Hello message of the interface. If
the parameter.
9. In global configuration, it controls LDP to distribute pop-tags for specific

undirected-connected destination segments.
mpls ldp egress { for < prefix-access-list> | nexthop < nexthop-access-list> }

By default, LDP only distributes pop-tags for direct-connected segments and advertise
to peer LSP.
10. In global configuration mode, set the label advertisement mode compatibility.
mpls ldp enable connect-with-dod
Use this command to interconnect with LSR in DOD mode.
11. This configures to use explicit null tag instead of implicit null tag in global configuration
mode.
mpls ldp explicit-null [ for < prefix-access-list> ] [ to < peer-access-list> ]
By default, ZXR10 advertises implicit null tags of direct-connected segments to all
neighbors. The implicit null tag causes penultimate hop popping on penultimate router.
While in some cases, penultimate hop popping on penultimate router must be banned,
so it is requested to use explicit null tag as tag forwarding packet.
12. In global configuration mode, it sets the holdtime when LDP session cannot receive
subsequent LDP messages.
mpls ldp holdtime < seconds>

When the two LSRs establish session, the negotiation holdtime is the smaller value
between them.
13. In global configuration mode, it configures the MD5 key for establishing TCP
connection session between LDP and neighbors.
mpls ldp neighbor < ip-address> password < password>
7-5

Use MD5 authentication between two LDP peers and authenticate each TCP segment
between them. It is necessary to authenticate and use the same MD5 key on the two
LSRs to enable MD5 authentication, otherwise the session cannot be established.
14. In global configuration mode, configure the prefix and downstream neighbors for the
request message sent by LDP.
mpls ldp request-labels for < prefix-access-list>
This command can send tag request message based on some prefixes. If the
parameter is configured, then the router sends tag request message to the
downstream of prefixes permitted in the list.
15. In global configuration mode, configure LDP router ID.
mpls ldp router-id < interface-name> [ force]
a. By default, the rules for selecting the router ID of an LDP on a ZXR10 router are
as follows:
l If the mpls ldp router-id command is used to designate the address of an
interface as the router ID, and also the interface has an IP address and is in
UP status, the interface will serve as the router ID.
l If there are loopback interfaces configured with an IP address, the maximum
IP address among the IP addresses of all the loopback interfaces will serve
as the router ID.
l The maximum one among the IP addresses of interfaces configured with IP
addresses in UP status is selected as the router ID.
b. If the no force parameter can be selected, the router ID designated by mpls ldp
router-id command takes effect till the next router ID election. The following events
occur on the router ID election.
l LDP restarts;
l The interface address serving as current router ID shuts down.
l The interface address serving as current router ID is not configured.
c. When the force parameter are contained, whether the mpls ldp router-id command
takes effect depends on the current status of the designated interface.
l If the designated interface is in UP status, and the address is not the current
router ID. The router will change the router ID to be the designated value
forcibly, suspends all current sessions, release tags learned from sessions
and suspends MPLS forwarding related to these tags.
l If the designated interface is down, once it becomes UP, the router ID is
changed to be the designated value forcibly, suspends all current sessions,
release tags learned from sessions and suspends MPLS forwarding related
to these tags.
16. In privileged configuration mode, reset connection between LDP router and a neighbor.
clear mpls ldp [ neighbor < ip-address> ] ]
The router resets termination and resets all LDP session an reviews access-fec policy
and egress policy on FEC, reviews advertise and request policy, and reviews explicit
7-6

popping tag advertisement policy; reset to terminate the session with designated
neighbors and reestablish the LDP session with the neighbor. Only reviews the
policies related to the neighbor (advertise, request and exp-null policies) .
17. In global configuration mode, configure address for non-direct connect remote target
session and establish target session
mpls ldp target-session < ip-address>
7.3 Example for Configuring MPLS

Figure 7-1 shows a simple network used for MPLS forwarding.
Figure 7-1 MPLS Configuration Example
Basic configuration tasks of three routers include:

1. Enable MPLS hop-by-hop forwardingbetween R1 and R2 and that between R1 and
R3.
2. Configure LDP label distribution between R1 and R2 and that between R1 and R3.
3. Configure the IP address of a loopback interface to serve as the router ID of the LSR.
l Configuration of R1:
ZXR10_R1(config)#mpls ip
ZXR10_R1(config)#interface Loopback1
ZXR10_R1(config-if)#ip address 10.10.1.1 255.255.255.255
ZXR10_R1(config-if)#mpls ip
ZXR10_R1(config)#mpls ldp router-id loopback1
ZXR10_R1(config-router)#network 10.0.0.0 0.255.255.255 area
7-7

0.0.0.0
0.0.0.0
0.0.0.0
In the above configuration, the OSPF dynamic routing protocol is run to advertise the
Route-id of each LSR, that is, the route of the loopback interface address.
Note:
The use of the loopback interface address as the router ID facilitates the stability of the LDP id of a
router, since the status of the loopback interface address does not change (unless the interface is
disabled manually).
7.4 MPLS Maintenance and Diagnosis

ZXR10 5900E provide some commands for viewing the work status of MPLS. The common
maintenance commands are as follows.
1. Displays interface with MPLS enabled.

show mpls interface
View interfaces with MPLS enabled on R2, "Yes" indicates normal start:
7-8

ZXR10_R2#show mpls interface

interface of LDP:
Interface IP Tunnel Operational
VLAN10 Yes(ldp) No Yes
VLAN20 Yes(ldp) No Yes
2. Check MPLS LDP parameters, that is, LDP timer parameters
show mpls ldp parameters
View the LDP parameter information on R2:
ZXR10_R2#show mpls ldp parameters
Protocol version: 1
Downstream label pool: min label: 16; max label: 1048575
Session hold time: 180 sec; keep alive interval: 60 sec
Discovery hello: holdtime: 15 sec; interval: 5 sec
Downstream on Demand max hop count: 255
LDP initial/maximum backoff: 15/120 sec
LDP loop detection: off
3. View the LDP parameter information on R2.
show mpls ldp discovery
View the detailed LDP discovery information on R2:
ZXR10_R2#show mpls ldp discovery detail
Local LDP Identifier:
10.10.2.2:0
Discovery Sources:
Interfaces:
VLAN10 (ldp): xmit/recv
LDP Id: 10.10.1.1:0
Src IP addr: 10.10.12.1; Transport IP addr: 10.10.12.1
VLAN20(ldp): xmit/recv
LDP Id: 10.10.3.3:0
Src IP addr: 10.10.23.3; Transport IP addr: 10.10.3.3
The command can be used to view the IP address that is discovered on each interface
and is used to set up a TCP connection (that is, the transport IP address) by an LDP
neighbor. To set up an LDP session, a router should have a reachable route to the
address, that is, the router can ping the address successfully. "xmit/recv" indicates the
interface is transmitting/receiving Hello packets (both are indispensable).
4. View LDP session information
show mpls ldp neighbor
View the LDP session information on R2. Label distribution can be performed only
after an LDP session is set up between LSRs:
ZXR10_R2#show mpls ldp neighbor detail
Peer LDP Ident: 10.10.1.1:0; Local LDP Ident 10.10.2.2:0
7-9

TCP connection: 10.10.12.1.1025 - 10.10.2.2.646

state: Oper; Msgs sent/rcvd: 240/240; Downstream
Up Time: 03:52:25
LDP discovery sources:
Vlan10; Src IP addr: 10.10.12.1
holdtime: 15000 ms, hello interval: 5000 ms
Addresses bound to peer LDP Ident:
10.10.12.1 10.10.1.1
Peer holdtime: 180000 ms; KA interval: 60000 ms
ZXR10_R2#
The above information indicates that a normal TCP connection has been set up
between LDPs, including the source/destination address and port ID of the TCP
connection. The status is "operation".If no normal LDP session is set up, the following
contents will be displayed:
ZXR10_R2#show mpls ldp neighbor
Peer LDP Ident: 10.10.1.1:0; Local LDP Ident 10.10.2.2:0
No TCP connection
state: Non; Msgs sent/rcvd: 0/0; Downstream
Up Time: 00:00:45
LDP discovery sources:
Vlan10; Src IP addr: 10.10.12.1
Addresses bound to peer LDP Ident:
5. After the LDP session is set up normally, use the following command to check LDP
label binding.
show mpls ldp bingdings
View the learned LDP label binding on R2:
ZXR10_R2#show mpls ldp bindings
10.10.1.1/255.255.255.255
local binding: label: 17
remote binding: lsr: 10.10.3.3:0, label: 18
remote binding: lsr: 10.10.1.1:0, label: imp-null(inuse)
10.10.2.2/255.255.255.255
local binding: label: imp-null
10.10.3.3/255.255.255.255
local binding: label: 16
remote binding: lsr: 10.10.3.3:0, label: imp-null(inuse)
10.10.12.0/255.255.255.0
remote binding: lsr: 10.10.1.1:0, label: imp-null
7-10

10.10.23.0/255.255.255.0
remote binding: lsr: 10.10.3.3:0, label: imp-null
remote binding: lsr: 10.10.1.1:0, label: 16:
Here, "local binding" refers to local label distribution and advertisement to upstream
LSRs, while "remote binding" refers to labels advertised from downstream LSRS.
Where, for a local network section, label distribution is set to "imp-null", and the
receiver executes "not-so-stubby" processing so that a label can pop up.
Commands similar to the above commands:
ZXR10_R1#show mpls forwarding-table
Mpls Ldp Forwarding-table:
InLabel OutLabel Dest Pfxlen Interface NextHop
18 Pop tag 10.10.2.2 32 vlan10 10.10.12.2
17 16 10.10.3.3 32 vlan10 10.10.12.2
16 Pop tag 10.10.23.0 24 vlan10 10.10.12.2

17 Pop tag 10.10.1.1 32 vlan10 10.10.12.1
16 Pop tag 10.10.3.3 32 vlan20 10.10.23.3

18 17 10.10.1.1 32 vlan20 10.10.23.2
17 Pop tag 10.10.2.2 32 vlan20 10.10.23.2
16 Pop tag 10.10.12.0 24 vlan20 10.10.23.2
Here, "InLabel" refers to a locally bound label, and "OutLabel" refers to a label learned
fro a downstream LSR. If the downstream LSR advertises "imp-null," the "Pop tag"
action will be executed.
For complicated troubleshooting, the following debug commands may be used:
1 debug mpls ldp transport Monitor the information discovered

by LDP.
2 debug mpls ldp session Monitor LDP session activities
3 debug mpls ldp messages Monitors messages from/to an LDP

neighbor.
4 debug mpls ldp bindings Monitor the addresses and labels

advertised by LDP neighbors.
7-11

5 debug mpls ldp advertisements Monitor the addresses and labels

advertised to the LDP neighbors
In the following example, events related to the mechanism discovered by LDP on R1 are
monitored:
ZXR10_R1#debug mpls ldp transport events
LDP transport events debugging is on
ZXR10_R1#
ldp: Send ldp hello; Vlan10, scr/dst 10.10.12.1(0.0.0.0)
/224.0.0.2, intf_id 257
ldp: Rcvd ldp hello; Vlan10, from 10.10.12.2(10.10.2.2:0),
intf_id 257
ZXR10_R1#debug mpls ldp transport connections
LDP transport connection debugging is on
ZXR10_R1#
ldp: Hold timer expired for adj 0, will close adj
ldp: Closing ldp conn; 10.10.12.1:1025<-->10.10.2.2:646
ldp: Opening ldp conn; 10.10.12.1<-->10.10.2.2
ldp: ldp conn closed; 10.10.12.1:1026<-->10.10.2.2:646
ldp: ldp conn closed; 10.10.12.1:1027<-->10.10.2.2:646
ldp: ldp conn is up; 10.10.12.1:1028<-->10.10.2.2:646
7-12

Chapter 8
VPLS Configuration
Table of Contents
VPLS Overview ..........................................................................................................8-1
Basic Configuratiaon of VPLS ....................................................................................8-2
Example for Configuring VPLS .................................................................................8-13
Example for Configuring VPWS................................................................................8-18
8.1 VPLS Overview

VPLS (Virtual Private LAN Service) is a kind of point-to-point l2 VPN service, providing
Ethernet emulation services in IP/MPLS network, connecting multiple LAN/VLAN
networks.
For MPLS-based L2 VPN, the network operator provides L2 connectivity to users but not
calculate routes for VPN users. When providing full-connected L2 VPN, note that there
are N parties. That is to say, one connection between CE and PE shall be assigned for
each CE of VPN to other CE.
For PE, when a VPN contains N sites, there must be N-1 physical or logical port
connections between CE-PE. L2 MPLS VPN scalability is only related to the number of
users connected to VPN.
L2 VPN can be performed through MP-BGP extension or LDP extension. Their draft
respectively are:draft-ietf-l2vpn-vpls-bgp-xx and draft-ietf-l2vpn-vpls-ldp-xx.
The VPLS LDP solution solves the problem how to establish virtual circuit between two
CEs. Martini L2 VPN uses VC-TYPE+VC-ID to identify VC, of which VC-TYPE indicates
that the VC types are ATM, VLAN or PPP, while VC-ID is used to identify a unique VC.
The VC-ID of all VCs with the same VC-TYPE is unique in the whole SP network. The
PE connecting two CEs exchanges VC ID through LDP and binds the corresponding CEs
through VC-ID
When two LSP connecting two PEs are established successfully and tags of both parties
are exchanged and bound, a VC is established. Two CEs transmit L2 data through the VC.
To exchange VC labels between PEs, Martini draft makes some extensions to LDP and
adds VC FEC types (128 type and 129 type). In addition, as the two PEs exchanging VC
labels might not be connected each other, LDP must use Remote peer to establish session
and transfer VC FEC and VC label on the session.
8-1

Figure 8-1 VPLS Networking
As shown in Figure 8-1, CE1, CE2 and CE3 are connected each other through MPLS
backbone network. For users, they seem to be connected through one LAN network
segment.
VPLS network working procedure is shown as follows:
First, VPLS establishs a PW full-connection between VPLS instances of PE1, PE2 and
PE3. All VPLS instances in the same VPLS area uses the same VCID.
Supposing PE1 distributes VC labels 102 and 103 for PE2 and PE3 respectively. PE2
distributes VC labels 201 and 203 for PE1 and PE3 respectively. And PE2 distributes VC
labels 301 and 302 for PE1 and PE2 respectively.
If one source address of the host behind CE is X, the MAC frame with destination address
is set from PE1. If PE1 does not know the where the PE with the MAC address Y is, it will
send the MAC frame to PE2 and PE3 by adding 201 and 301 on it respectively.
After receiving MAC frame, PE2 knows that MAC X is behind PE1 according to VC label
201 and learns the MAC address X and bind the MAC address X with VC label 102
(assigned by PE1).
8.2 Basic Configuratiaon of VPLS

8.2.1 Clearing VPLS-related Statistics Information
Command Function
ZXR10#clear flowstat vpls [ vfi < vfi-name> ] It clears VPLS-related flow statistics
information.
ZXR10#clear flowstat vpls It clears all VPLS VFI flow statistics

information.
8-2

Chapter 8 VPLS Configuration
< vfi-name> The VFI name corresponding to VPLS instance

in traffic statistics.
It clears VPLS flow statistics information forcibly.
Example
It clears vfi1 and all vfi flow.
ZXR10#clear flowstat vpls vfi vfi1
ZXR10#clear flowstat vpls
Related Commands:
show mac-table
8.2.2 Clearing VPWS-related Statistics Information

Command Function
ZXR10#clear flowstat vpws vcid < vcid> It clears VPLS-related flow statistics
information.
ZXR10#clear flowstat vpws vlanid < vlanid> It clears VPLS-related flow statistics
information.
< vcid> vcid corresponding to VPWS
< vlanid> vlanid corresponding to VPWS
It clears VPWS flow statistics information forcibly.
Example
It clears VPWS traffic.
ZXR10#clear flowstat vpws vcid 2
ZXR10#clear flowstat vpws vlanid 2
Related Commands:
show mac-table
8.2.3 Clearing MAC Address Table Corresponding to Specific VPLS

Command Function
ZXR10#clear mac-table vfi < vfi-name> It clears MAC address table

corresponding to specific VPLS.
8-3

< vfi-name> The VFI name corresponding to VPLS instance

of the MAC address to be cleared
It clears VPLS MAC address forwarding table of this VPLS forcibly but not through aging.
Example
it clears vfi1 MAC address table.
ZXR10#clear mac-table vfi vfi1
Related Command:
show mac-table
8.2.4 Designating other PE Addresses in the same VPLS Area and

Originating PW Establishment
Command Function
ZXR10(config-vfi)#peer < peer-ip-address> It designates other PE addresses in the

same VPLS area and originating PW
establishment.
ZXR10(config-vfi)#no peer < peer-ip-address> It deletes the established PW.
ZXR10(config-vfi)#peer static-pw < peer-ip-address> < static-pw name> It configures the static PW VPLS
[ spoke] service.
< peer-ip-address> IP address of peer PE. Generally, it is router-id.
spoke If the optional parameter spoke is contained, the

PW type is spoke, otherwise it is hub.
< vcid> Different VPLS instances on the same PE have

different vcid. The VPLS instances with th same
vcid on different PEs belong to the same VPLS
area.
vcid 1 4294967294
< static-pw name> It configures the static PW which is designated

when using static PW VPLS service.
It configures th default peer to be hub in VFI configuration mode.

The current plan does not support VPLS automatic discovery mechanism, so it is
necessary to designate all PE addresses belonging to the same VPLS area. This
8-4

command establishes PW by using the parameters designated by vcid command and

pwtype command. The spoke is used in VPLS layering and cross domain.
Example
It configures peer on peer.
ZXR10(config)#vfi vfi1
ZXR10(config-vfi)#peer 4.4.4.4
It configures peer on PE to make spoke access fail.

ZXR10(config-vfi)#peer 3.3.3.3 spoke 20
ZXR10(config-vfi)#peer 4.4.4.4 spoke 30
Configure static peer on PE.

ZXR10(config-vfi)#peer static-pw 4.4.4.4 test
Related Commands:
vfi
vcid
pwtype
8.2.5 Designating PW Type Established by VPLS Instance

Command Function
ZXR10(config-vfi)#pwtype { ethernet | ethernet-vlan} It designating PW type established by

VPLS instance.
ethernet | ethernet-vlan The PW type is Ethernet or ethernet-vlan.
Before two PEs establish PW, it is necessary to negotiate the PW type. There are two PW
types in VPLS: ethernet and ethernet-vlan. The pw can be established only when the pw
types designated by two PEs are the same.
Two PW types provide two VPLS services. If the PW type is ethernet, VPLS service mode
is transparent transmission, i.e., PE does not verify and process vlan tags but only forwards
it. Thus, the vlan tag is the distinguish mark for private network management. In this mode,
the access interface provided for users is real interface.
If pw type is ethernet-vlan, VPLS service provides rewrite mode, i.e., the ingress PE router
removes the vlan tag from user data and sends it to PW, the egress PE attaches related
vlan tag based on outgoing interface types and send it to the user.
8-5

Example
Configure pw type on PE.
ZXR10(config-vfi)#pwtype Ethernet
Related Commands:
vfi
vcid
peer
no peer
8.2.6 Displaying MAC Forwarding Table of VPLS Instance

Command Function
show mac-table < vfi-name> It displays MAC forwarding table of

VPLS instance. It is used in Exec mode
and privileged mode.
< vfi-name> In VPLS, the name of specific VFI.
Example
It displays the MAC table of current vfi1.
ZXR10#show mac-table vfi1

MAC peer-address outIntLab outExtLab outInterface type
0000.0000.2009 Local NULL NULL fei_7/8 dynamic
0000.0000.3005 1.1.1.1 16 3 fei_7/5 dynamic
0000.0000.3004 1.1.1.1 16 3 fei_7/5 dynamic
Description of the displayed fields:
Field Description
MAC MAC address
peer-address peer address, remote address
outIntLab inner outgoing tag
outExtLab outer outgoing tag
outInterface Outgoing interface
type MAC address tag, static configuration or dynamic

learned MAC address
8-6

Related Command:
clear mac-table vfi
8.2.7 Displaying Successfully Established PW Information

Command Function
show mpls l2transport vc vpls [ { [ vcid < vc-id> [ < max-vc-id> ] ] [ vfi < It displays successfully established
vfi-name> ] [ destination < ip-address> ] [ detail] } ] PW information, which is used in Exce
mode and privileged mode.
< vc-id> The vc-id of specific VPLS or the minimum vc-id

value in the range of 042949672955.
< max-vc-id> The maximum vc-id value, in the range of

0 42949672955.
< vfi-name> VFI name of VPLS information corresponding to

specific VFI.
< ip-address> The pw information established by specific peer

address.
detail Detailed information of VPLS information.
Example
1. It displays the VPLS information whose VFI name is 1.
ZXR10#show mpls l2 vc vpls vfi 1
VFIName LocalCircuit DestAddress VC ID Status
1 VFI 7.7.7.7 1 up
1 VFI 6.6.6.6 1 up
2. It displays the detailed information of VFI1.
ZXR10#show mpls l2transport vc vpls vfi 1 detail
Local interface: VFI 1 up
Destination address: 7.7.7.7, VC ID: 1, VC status: up
Output interface: fei_3/7, imposed label stack { 16, 17 }
Create time: 00:00:18, last status change time: 00:00:18
Signaling protocol: LDP, peer 7.7.7.7 : 0, up
MPLS VC labels: local 2518, remote 17
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
Local interface: VFI 1 up
Destination address: 6.6.6.6, VC ID: 1, VC status: up
8-7

Output interface: fei_3/6, imposed label stack { 50016, 50017 }

Create time: 00:00:18, last status change time: 00:00:18
Signaling protocol: LDP, peer 6.6.6.6 : 0, up
MPLS VC labels: local 2517, remote 50017
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Remote interface description:
Sequencing: receive disabled, send disabled
Field Description
VFIName VFI name
LocalCircuit Local circuit name, it indicates the VPLS belong

to L2VPN.
DestAddress Remote destination address
VC ID Established VC ID
Status VC corresponding to VPLS.
Related Command:
show mpls l2transport vpn summary
8.2.8 Displaying Counts of L2VPN VPWS, VPLS

Command Description
show mpls l2transport vpn summary It displays the counts of L2VPN VPWS,
VPLS. It is used in Exec mode and
privileged mode.
Example
It displays the count of all L2VPN configured on router.
ZXR10#show mpls l2transport vpn summary
The summary information about configured l2 vpn:
vpn_type current/max
vpws 0/1024
vpls 3/1024
Related Command:
show mpls l2transport vc vpls
8-8

8.2.9 Displaying Detailed Information of a VFI

Command Function
show vfi < vfi-name> In Exec mode and privileged mode,

it displays the detailed information of
certain VFI.
< vfi-name> The name of VFI in VPLS.
Example
It displays the detailed information of current VPLS VFI.
ZXR10#show vfi test

Flag: (Spoke) Spoke type PW
Vfi name:test VCID:100 PwType:Ethernet L2protocol-Tunnel: Disable
Unsymmetric-mode: no
Learn remote MAC: yes
Local attachment circuit:
Maximum Transmit Unit:1500
In Pkts: 151187 In Bytes: 18747188
Out Pkts: 151186 Out Bytes: 20863668
vlan2
C/S Attribute : Server Interface
Vlan id: 2
Neighbors connected via pseudowires:
3.1.1.1
Field Description
spoke The topology type is spoke.
tunnelId:X The outer tunnel ID is RSVPTE, X is the

corresponding tunnel ID
Vfi name VFI name
Unsymmetric-mode Unsymmetrical mode mark
Learn remote MAC Remote MAC learning mark
Local attachment circuit The circuit interface bound locally
Vlan id VLAN ID of in case of Ethernet-vlan mode VFI
Vlan range VLAN range in case of Ethernet mode VFI
Neighbors connected via pseudowires Which PE are neighbors of local VFIs.
8-9

Related Command:
show vfi brief
8.2.10 Displaying All Configured VPLS VFI Brief Information

Command Function
show vfi brief In Exec mode and privileged mode, it

displays all configured VPLS VFI brief
information.
Example
It displays MAC virtual forwarding table of VPLS.
ZXR10#show vfi brief

Total VFI number is 2
VFI name VCID PWtype
aa 2 Ethernet-vlan
vfi 1 Ethernet
Field Description
Total VFI number is 2 Total number of configured VFIs
VFI name VFI name
VCID vcid of VFI
PWtype Forwarding mode of VFI
Related Command:
show vfi
8.2.11 Designating vcid for VPLS Instance

Command Function
ZXR10(config-vfi)#vcid < vcid> It designates vcid for VPLS instance.
< vcid> Different VPLS instances in the same PE have

different vcid; the VPLS instances with same vcid
in different PEs belong to the same VPLS area.
vcid is in the range of 14294967294
8-10

If VPLS instances on two PE routers belong to the same VPLS area, it is necessary
to establish pw for the communication between VPLS instances. To establish pw is to
exchange MPLS inner tag identifying VPLS area or VC tag between two PEs. (PW contains
VC tag and MPLS outer tags which compose LSP ).
Example
Set vcid to 100 on PE.
ZXR10(config-vfi)#vcid 100

Related Command:
vfi
pwtype
peer
8.2.12 Creating VPLS Instance on PE

Command Function
ZXR10(config)#vfi < vfi-name> It creates a VPLS instance on PE.
ZXR10(config)#no vfi < vfi-name> It deletes created VPLS instance.
< vfi-name> VFI name, L2 VPN name.
VFI is VPLS instance on PE router. VPLS instances with the same vcid on different PE
routers belong to the same VPLS area and they can communicate each other. Use this
command to enter VFI configuration mode.
Example
Configure VPLS instance name on PE.
ZXR10(config-vfi)#
Related Command:
no vfi
vcid
pwtype
peer
no peer
8-11

8.2.13 Connecting Interface to VPLS Instance

Command Function
ZXR10(config-if)#xconnect vfi < vfi-name> Connects the interface to VPLS VFI.
ZXR10(config-if)#no xconnect vfi Deletes the operation of connecting

interface to VPLS instance.
ZXR10(config-if)#xconnect vfi < vfi_name> [ localgroup < In real interface configuration mode,
local_group_id> ] [ outvlan < vlan_id> ] [ outvlanrange range1 < top> < port/port+VLAN/port+VLAN range
bottom> [ range2 < top> < bottom> ] [ range3 < top> < bottom> ] ] access is supported. It connects
interface to VPLS VFI.
ZXR10(config-if)#no xconnect vfi [ outvlan < vlan_id> ] In real interface configuration mode,
port/port+VLAN/port+VLAN range
access is supported. It deletes the
operation of connecting interface to
VPLS VFI.
< vfi-name> VPLS VFI name
< vlan-id> Outer VLAN ID of port+VLAN access, in the

range of 1 4094
< top> The top limit of VLAN range in port+VLAN

access:1 4094
< bottom> The bottom limit of VLAN range in port+VLAN

access:1 4094
Add the local interface to VPLS instance, and users access VPLS services through this
interface. The data received from this interface are user data.
The multiple-interface access function is supported from the version 4.8.22, including
access modes such as VLAN, port, port+VLAN, port+VLAN range. Of which, port+VLAN
access in single interface supports multiple configurations; in port/port+VLAN range
access, the instance only works in RAW mode. Use group numbers to determine whether
local access is interconnected. Only when the group numbers are identical, the group
numbers are interconnected.
Example
In PE interface mode, add vfi1 to this interface.
ZXR10(config)#interface fei_3/1
ZXR10(config-if)#xconnect vfi vfi1
In PE interface mode, add this interface to vfi1 by port+VLAN range access.

ZXR10(config)#interface vlan100
8-12

ZXR10(config-if)#xconnect vfi vfi1 outvlanrange range1 14 20
8.2.14 Enabling VPWS on the Interface

Command Function
ZXR10(config-if-vlanX)#mpls xconnect [ static-pw] < ip-address> < This configures remote interface
vc-id> [ < static-pw-name> ] < port-name> [ mtu < mtu-value> ] address, and VPWS identifier,
specifies local binding interface and
configures vpws interface mtu. VPWS
establishment is triggered between this
interface and remote interface.
ZXR10(config-if-vlanX)#no mpls xconnect [ static-pw] This deletes this VPWS.
static-pw Uses static PW VPWS service
<ip-address> Remote interface IP address
<vc-id> Identifies ID number of VPWS, in range of

1~4294967294
<static-pw-name> Static pw name
<port-name> Port name
mtu < mtu-value> Configures vpws interface mtu
Example
This example shows how to establish VPWS whose vc-id is 100 between gei_1/2 and node
that Router-id is 1.1.1.1 and specifies local binding interface as gei_1/2.
ZXR10(config)#interface vlan 2
ZXR10(config-if-vlan2)#mpls xconnect 1.1.1.1 100 gei_1/2
8.3 Example for Configuring VPLS

As shown in Figure 8-2, CE1, CE2 and CE3 need to be interconnected in VPLS L2 VPN.
8-13

Figure 8-2 VPLS Configuration Example 1
The configurations are as follows:

1. Create VFI and configure vcid, pwtype, peer parameters on VFI;
2. Bind VLAN to the physical port, bind vlan 100 to gei_1/1 of PE1, and bind vlan 10 to
gei_1/2;
3. Configure the interface address on vlan 10 of PE1, vlan 20 and vlan 30 on P and vlan
40 on PE2.
4. Confiugre loopback address on PE1, P, PE2;
5. Run IGP protocol (such as OSPF) on PE1, P, PE2 to make PE1 and PE2 interconnect
each other and learn the loopback interface address route of the peer.
6. Enable MPLS on PE1, P, PE2; configure mpls ip globally and designate the router-id
of mpls ldp; enable mpls ip on vlan 10 of PE1, vlan 20 and vlan 30 of P, vlan 40 of PE2;
7. Configure target session on PE1, PE2 to establish LDP neighborhood between PE1
and PE2 (if no P exists, this parameter does not need to be configured.)
8. Enable connect vfi vfi-name on interfaces vlan 100, vlan 200 and vlan 300, which are
located on PE1, PE2 and connected to CE.
The configurations on each devices are described as follows:
l Configuration on PE1:
PE1(config)#vfi vpls_a
PE1(config-vfi)#vcid 100
PE1(config-vfi)#pwtype Ethernet
PE1(config-vfi)#peer 1.1.1.3
PE1(config)#interface gei_1/1
PE1(config-gei_1/1)#switchport mode trunk
PE1(config-gei_1/1)#switchport trunk vlan 100
PE1(config-gei_1/1)#exit
PE1(config)#interface loopback10
PE1(config-loopback10)#ip address 1.1.1.1 255.255.255.255
8-14

PE1(config-loopback10)#exit
PE1(config)#interface vlan 100
PE1(config-if-vlan100)#xconnect vfi vpls_a
PE1(config-if-vlan100)#exit
PE1(config-if-vlan10)#ip address 175.1.1.1 255.255.255.0
PE1(config-if-vlan10)#mpls ip
PE1(config)#mpls ip
PE1(config)#mpls ldp router-id loopback10 force
PE1(config)#mpls ldp target-session 1.1.1.3
PE1(config)#router ospf 1
PE1(config-router)#network 1.1.1.1 0.0.0.0 area 0.0.0.0
l Configuration on P:
P(config)#interface gei_1/3
P(config-gei_1/3)#switchport mode trunk
P(config-gei_1/3)#switchport trunk vlan 20
P(config-gei_1/3)#exit
P(config)#interface loopback10
P(config-loopback10)#ip address 1.1.1.2 255.255.255.255
P(config-loopback10)#exit
P(config)#interface vlan 20
P(config-if-vlan20)#ip address 175.1.1.2 255.255.255.0
P(config-if-vlan20)#mpls ip
P(config-if-vlan20)#exit
P(config-if-vlan30)#ip address 148.1.1.2 255.255.255.0
P(config-if-vlan30)#mpls ip
P(config-if-vlan30)#exit
P(config)#mpls ip
P(config)#mpls ldp router-id loopback10 force
P(config)#router ospf 1
P(config-router)#network 1.1.1.2 0.0.0.0 area 0.0.0.0
PE2(config-vfi)#vcid 100
PE2(config-vfi)#pwtype ethernet
8-15

PE2(config)#interface loopback10
PE2(config-loopback10)#ip address 1.1.1.3 255.255.255.255
PE2(config-if-vlan40)#ip address 148.1.1.3 255.255.255.0
PE2(config-if-vlan40)#mpls ip
PE2(config)#mpls ip
PE2(config)#mpls ldp router-id loopback10 force
PE2(config)#mpls ldp target-session 1.1.1.1
PE2(config)#router ospf 1
If the networking shown in Figure 8-2 is changed to form that shown in Figure 8-3, in which
connect CE4 to P to make CE1, CE2, CE3 and CE4 belong to the same VFI. Thus, the P
can be configured to PE (also called PE3).
8-16

The changed configurations are shown as follows:

l Configuration on P(PE3):
P(config)#vfi vpls_a
P(config-vfi)#vcid 100
P(config-vfi)#pwtype Ethernet
P(config-vfi)#peer 1.1.1.1
P(config-vfi)#peer 1.1.1.3
P(config-if-vlan400)#xconnect vfi vpls_a
In the two networking environments Figure 8-2 and Figure 8-3, MPLS network contains
flat VPLS networks. the PWs between PEs in one VPLS instances is HUB PW.
When a new PE is added to the VPLS instances, no PW needs to be created between this
PE and other PEs, as shown in Figure 8-4. PE10, PE20 only eatablishi PW relationship
with P(PE3 in the figure) but not with PE1 or PE2. This PW mode is called SPOKE PW.
8-17

The configuration to be changed is shown as follows: (ROUTER-ID of PE10, PE20 are

1.1.1.10 and 1.1.1.20):
l Configuration on P (also called PE3):
P(config)#vfi vpls_a
P(config-vfi)#peer 1.1.1.10 spoke
P(config-vfi)#peer 1.1.1.20 spoke
l Configuration on PE10 (other configurations are omitted, refer to PE1):
PE10(config-vfi)#peer 1.1.1.2 spoke
l Configuration on PE20 (other configurations are omitted, refer to PE1):
PE20(config-vfi)#peer 1.1.1.2 spoke
8.4 Example for Configuring VPWS

As shown in Figure 8-5, CE1 and CE2 need to be interconnected in VPWS L2 VPN.
8-18

Figure 8-5 VPWS Configuration Example
The configurations are as follows:

1. Create two layer 3 interfaces on PEs of two ends and add the corresponding port,
configure IP address on the layer 3 interface which connects PE and P.
2. Configure loopback interface on PE1 and P and configure corresponding IP addresses.
3. Run routing protocol (such as OSPF) on PE1, P, PE2 to make PE1 and PE2
interconnect each other and learn the loopback interface address route of the peer.
4. Enable MPLS on PE1, P, PE2, that is, configure mpls ip globally, and designate the
router-id of mpls ldp, enable mpls ip on vlan3 of PE1, vlan3 and vlan4 of P, vlan4 of
PE2.
5. Configure target session on PE1, PE2 to establish LDP neighborhood between PE1
and PE2 (if no P exists, this parameter does not need to be configured.)
6. mpls xconnect< ip-address> < vc-id> < port-name> is implemented on VLAN2 of PE1
and PE2 which connect CE.
The configurations on each devices are described as follows:
PE1 configuration:
ZXR10(config)#interface gei_1/16
ZXR10(config-gei_1/16)#switchport mode trunk
ZXR10(config-gei_1/16)#switchport trunk vlan 2
ZXR10(config)#interface loopback1
ZXR10(config-loopback1)#ip address 1.1.1.1 255.255.255.255
ZXR10(config)#int vlan2
8-19

ZXR10(config-if-vlan3)#mpls ip
ZXR10(config-if-vlan3)#ip address 8.1.1.1 255.255.255.0
ZXR10(config)#mpls ip
ZXR10(config)#mpls ldp router-id loopback1 force
ZXR10(config-router)#network 1.1.1.1 0.0.0.0 area 0
P configuration:
PE2 configuration:
8-20


8-21

8-22

Chapter 9
Multicast Routing
Configuration
Table of Contents
Multicast Overview .....................................................................................................9-1
Configuring Public Multicast .......................................................................................9-5
Configuring IGMP Version ..........................................................................................9-5
Configuring PIM-SM ...................................................................................................9-9
Configuring MSDP....................................................................................................9-12
Configuring PIM-DM.................................................................................................9-14
Configuring PIM-SNOOPING ...................................................................................9-14
Multicast Configuration Example ..............................................................................9-14
Multicast Maintenance and Diagnosis.......................................................................9-16
9.1 Multicast Overview

Multicast is a point-to-multipoint or multipoint-to-multipoint communication mode.
Multiple receivers can synchronously receive the same message from one source. The
applications based on multicast include video conference, distance learning and software
distribution.
Multicast protocol consists of the group member management protocol and the multicast
routing protocol. The group member management protocol is applicable to management
of the joining or leaving of multicast group members. Multicast routing protocol is
responsible for the establishment of a multicast tree by exchanging information between
routers. Multicast routing protocol can be divided into the intra-area multicast routing
protocol and the inter-area multicast routing protocol.
ZXR10 5900E supports the following protocols:
l IGMPInternet Group Management Protocol

l PIM-SMProtocol Independent Multicast Sparse Mode
l MSDPMulticast Source Discovery Protocol
l PIM-DMProtocol Independent Multicast Dense Mode
9.1.1 Multicast Address

In a multicast network the sender sends a packet to multiple receivers in a multicast mode.
In this situation the sender is called the multicast source. Multiple receivers for the same
packet are identified by same ID. This is called the multicast group address. In the IP
9-1

address allocation scheme class D IP address is 224.0.0.0-239.255.255.255. It is just a

multicast address. 224.0.0.0-224.0.0.255 and 239.0.0.0-239.255.255.255 are used for the
purpose of research and management.
9.1.2 IGMP
IGMP is a protocol that is used to help the multicast router to get information of multicast
group members which are running between mainframe and multicast router.
Multicast router periodically sends query messages of group members to all mainframes
in order to know which specific group members exist in the connected networks. The
mainframe returns a report message of group members, reporting the multicast group
which they belong to. A mainframe immediately sends report messages of group members
instead of awaiting a query when it joins a new group.
When the mainframe leaves the group, it sends a message indicating its purpose to the
multicast router. The multicast router will immediately query whether there are still group
members running in the group. If so, the multicast router will continue to forward data. If
not, it will not forward data any longer.
In the current actual applications there are two versions: IGMP V1 and IGMP V2.
IGMP V2 has more enhanced features than the IGMP V1. It finishes exchanging
information between the mainframe and the routers by means of four types of messages.
1. Group member query
2. V2 member report
3. Leave report
4. V1 member report
V1 member report is used for the compatibility with the IGMP V1.
9.1.3 Multicast Tree

In a multicast communication router the possession of multicast source, receiver and of
multicast packet path is essential. For path selection, the most common method is to
construct tree routes. Tree route has the following two advantages:
1. The packet reaches different receivers along branches in a parallel mode.
2. The packet copy only occurs in the branch position which makes the sent packets over
network minimum.
A multicast tree is a set, which is composed of a series of input interfaces and output
interfaces of routes. It determines only one forwarding path between both the subnet
where the multicast source lies and the subnets containing group members.
There are two basic methods to construct multicast trees: the source-based multicast tree
and the multicast rendezvous point tree (RPT).
1. Source-Based Multicast Tree
9-2

Chapter 9 Multicast Routing Configuration
The source-based multicast tree is also called source shortest path tree. It constructs a
spanning tree toward all receivers for each source. The spanning tree with the subnet
of the source as a root node extends to the subnet where receivers exist. A multicast
group may have multiple multicast sources.
Each source or each pair (S, G) has a corresponding multicast tree.
Method to construct the source-based multicast trees is the reverse path forwarding
(RPF). Each router can find the shortest path toward the source and the corresponding
output interface according to a unicast route. When receiving a multicast packet, a
router checks whether the input interface receiving it is the output interface of the
shortest unicast path toward the source itself. If so, the router copies and forwards the
packet to other interfaces. If not, the router discards the multicast packet.
The input interface receiving the multicast packet in the router is called the father link.
The output interface sending the multicast packet is called the sub-link.
2. Multicast Rendezvous Point Tree
The multicast rendezvous point tree constructs a multicast tree for each multicast
group. This tree is shared by all members. Namely, the (*, G) use commonly a
preceding multicast tree but not construct a tree for each pair (S, G). Each device
wanting to receive the multicast packet of the group must explicitly join the RPT.
The multicast RPT uses a router or a group of routers as the center of the multicast
tree. All source direction receivers send the packet to the center in a unicast mode,
and start to forward from the center along the multicast RPT tree in a multicast mode.
9.1.4 PIM-SM
PIM-SM sends multicast packet by using the multicast RPT. A multicast RPT has a center
point that is responsible for sending packets to the ports of all sources of a multicast
group. Send ports of each source sends packets to the center point along the shortest
path and distribute packets to receiving ports. The group center point of the PIM-SM is
called Rendezvous Point (RP). A network may have multiple RPs, whereas a multicast
group has only one RP.
A router can determine the location of the RP by three methods. The first method is the
manual static configuration RP running routers of the PIM-SM. The other two methods
are dynamic. They are determined according to the PIM-SM version adopted by the
network. The PIM-SM V 1 adopts the Auto-RP whereas PIM-SM V2 adopts Candidate-RP
advertising mode. The Candidate-RP with higher priority is the formal RP.
PIM-SM V2 manually configures some routers running PIM-SM as Candidate-BSR

(BootStrap Router) and selects the Candidate-BSR as the formal BSR. The BSR is
responsible for collecting Candidate-RP information of multicast routers. If finding some
Candidate-RP, the BSR advertises them to all PIM routers in the PIM area. These PIM
routers according to the similar Hash rules select one with higher priority as the formal
RP from the same candidate-RP set. The candidate-RP is manually configured.
9-3

The routers running PIM-SM find them and maintain the adjacency by exchanging the
Hello messages. In the Multi-access network the Hello message also contains the priority
information of the router. According to the parameter, select the Designate Router (DR).
Multicast source or the first hop router (DR directly connected with the source)
encapsulates the packet in a registration message and sends it to the RP through the
unicast router. When receiving the registration message the RP decapsulates and takes
out the packet and sends it to the receiver of the group along the RPT.
Each mainframe acting as the receiver joins the multicast group through the member report
message of the IGMP. The last hop router (or the DR in the multi-access network) sends
the received joining message to the RP for registration level by level. Intermediary router
checks whether to have the router of the group after receiving the joining message. If so,
the intermediary router adds the request router of the downstream to the RPT as a branch.
If not, it continues to send the joining message to the RP.
When the RP or the multicast router is directly connected with the receiver they can switch
to the source-based shortest path tree from the RPT. When the RP receives registration
messages sent from a new multicast source, the RP returns a joining message to the DR
directly connected with the multicast source. Thus, the shortest path tree from the source
to the RP is established.
A DR or router directly connected with the multicast members receives the first multicast
packet from the multicast or the received packet reaches a threshold. They can switch to
the source-based shortest path tree from the RPT. Once switchover occurs, the router will
send a prune message to the neighbor of the upstream and require leaving the RPT.
9.1.5 MSDP
MSDP is a mechanism that allows RPs in each PIM-SM domain to share information
about active sources. Each RP knows the receivers within the local domain. When RPs
has learned information about active sources in remote domains, they can transfer the
information to receivers in local domain. Thus, multicast packets can be forwarded among
domains.
MSDP speaker in a PIM-SM domain establishes MSDP peering session with MSDP
peers in other domains through TCP connection. When MSDP speaker has learnt a
new multicast source (through the PIM register mechanism) in local domain, it creates a
Source-Active message and sends it to all the MSDP peers.
Each MSDP peer that receives the message uses peer-RPF check and only the SA
message received on correct interface is forwarded, discarding the others. When an
MSDP peer which is also an RP for its own domain receives a new SA message and
the outgoing interface list in (*, G) entry is non-empty, that is, there are receivers within
the domain, RP creates a (S, G) state for multicast source and adds this entry to the
shortest-path tree of the source.
In addition, each MSDP peer saves the received SA messages in a cache, thus
establishing a SA cache table. If the RP in a PIM-SM domain receives a new PIM join
message for multicast group G, the RP searches its own SA cache table to get all the
9-4

active multicast sources immediately, thus generating the corresponding (S, G) Join
message.
9.1.6 PIM-SNOOPING
PIM Snooping obtains the multicast routing port by snooping the HELLO and JOIN/PRUNE
messages of the multicast protocol and forwards the multicast data as well as reduces
network traffic.
9.2 Configuring Public Multicast

1 ZXR10(config)#ip multicast-routing This boots the IP multicast route.
2 ZXR10#clear ip mroute [ group-address < group-address> ] [ This deletes the IP multicast routing
source-address < source-address> ] table.
9.3 Configuring IGMP Version

ZXR10 5900E IGMP function is based on PIM interface. All interfaces enabling PIM
enables IGMP function automatically.
9.3.1 Configuring IGMP Version

At present the IGMP has the V1 and the V2. Default value is V2. For security, a router
requires router requires the Network Element (NE) in the same network segment to be the
IGMP V1 or the IGMP V2.
For the configuration of IGMP version number of the interface, use the following command.
Command Function
ZXR10(config-if-vlanX)#ip igmp version < version> This configures IGMP version.
9.3.2 Configuring an IGMP Group

1. To configure group range that allows IGMP to join, use the following command.
Command Function
ZXR10(config-if-vlanX)#ip igmp access-group< acl-number> This configures group range that allows
IGMP to join.
This example shows running of IGMP on the interface. The interface receives all
multicast groups by default and sets the receiving group range on the interface. When
9-5

the joining request from the mainframe does not belong to the range discard the joining
request.
Only receive the group 239.10.10.10 on the Vlanl interface.
ZXR10(config)#acl standard number 10
ZXR10(config-std-acl)#rule 1 permit 239.10.10.10 0.0.0.0
ZXR10(config-std-acl)#exit
ZXR10(config-if-vlan1)#ip igmp access-group 10
2. To configure the group range permitting the IGMP to leave right away, use the following
command.
Command Function
ZXR10(config-if-vlanX)#ip igmp immediate-leave [ group-list < This configures the group range
acl-number> ] permitting the IGMP to leave right away.
Upon receiving the message of the IGMP leaving or not receiving the Report message
within (last member query intervalx2+1) seconds then the group members leaves.
In the below configuration the group is permitted 239.10.10.10 to leave right away on
the Vlanl interface.
ZXR10(config-std-acl)#exit
ZXR10(config-if-vlan1)#ip igmp immediate-leave group-list 10
3. To configure the static group member on the IGMP interface, use the following
command.
Command Function
ZXR10(config-if-vlanX)#ip igmp static-group< group-address> This configures the static group member
on the IGMP interface.
Above configuration statically binds the group address to an interface. Supposing

there are always members of the group on the interface.
To configure the static group 239.10.10.10 on the Vlanl interface is shown below:
ZXR10(config-if-vlan1)#ip igmp static-group 239.10.10.10
9-6

9.3.3 Configuring IGMP Timer

IGMP boots on the multicast router interface that is connected with a shared network
segment. Select the optimum one as the Querier of the network segment which is
responsible for sending the query message to obtain the information of the group
members.
After sending query messages, the Querier will wait for the member report of the receiving
mainframe for some time. The duration is the Max Response Time value carried when
sending query messages. The default value is 10 seconds.
Upon receiving query messages the mainframe member on the network segment will
reduce a random deviation value based on the maximum response time. It will take the
result as its own response time.
During this period the mainframe member will cancel the receiving reports of other
mainframe. If the mainframe report is not cancelled then mainframe member will send
the mainframe report at the right time. Therefore, prolonging the max response time will
accordingly increase the waiting chances for the group member of the network segment.
The mainframe member will reduce the burst rate of multiple mainframe reports on the
network segment.
1 ZXR10(config-if-vlanX)#ip igmp query-interval< seconds> This configures IGMP query time

interval.
2 ZXR10(config-if-vlanX)#ip igmp querier-timeout< seconds> This configures the IGMP querier

timeout length.
3 ZXR10(config-if-vlanX)#ip igmp query-max-response-time< This configures the maximum

seconds> response time value carried by query
messages when the IGMP sends
query messages.
4 ZXR10(config-if-vlanX)#ip igmp last-member-query-interval< This configures the query interval of

seconds> a specific group of the IGMP.
9.3.4 Configuring ssm-mapping

To configure ssm-mapping and take received igmp v2 user as v3 user, use the following
command.
1 ZXR10(config)#ip igmp snooping ssm-mapping This enables ssm-mapping function

globally.
2 ZXR10(config)#ip igmp snooping ssm-mapping-rule < group address> This configures ssm-mapping rule.
< source address>
9-7

3 ZXR10(config)#ip igmp snooping clear-ssm-mapping This clears all configured

ssm-mapping rules.
9.3.5 Configuring Limit on Numbers of IGMP Users

1. This configures the maximum number of IGMP users to add based on interfaces.
Command Function
ZXR10(config-if-vlanX)#ip igmp max-host-limit< limit-num> This configures the maximum number of

IGMP users to add based on interfaces
and limits the amount of groups to add
to L3 interface.
Run IGMP on interface, up to 256 users can be added by default.

In vlan 1, set the maximum amount of IGMP users to be 100.
ZXR10(config-if-vlan1)#ip igmp max-host-limit 100
This deletes the configuration of the maximum amount of IGMP users in L3 interface
VLAN1.
ZXR10(config-if-vlan1)#no ip igmp max-host-limit
2. This configures the maximum number of IGMP users to add based on group.
Command Function
ZXR10(config)#ip igmp max-host-limit group < group-address> limit-num This configures the maximum number
< limit-num> of IGMP users to add based on groups
and limits the amount of interfaces to
add to a certain group.
Up to 2048 groups, on which the maximum number of IGMP users to add, can be set.
This sets up to 50 L3 interfaces to be added to the group 239.10.10.10.

ZXR10(config)#ip igmp max-host-limit group 239.10.10.10 limit-num 50
This deletes the setting of the maximum numbers of users to add to the group
239.10.10.10.
ZXR10(config)#no ip igmp max-host-limit group 239.10.10.10
9-8

9.4 Configuring PIM-SM

9.4.1 Booting PIM-SM
Command Function
ZXR10(config)#router pimsm This boots PIM-SM.
9.4.2 Configuring Static RP Address

Configuration should be done of a static RP for a multiple specific groups and also configure
same static RPs for the group on all PIM-SM multicast routers in the multicast area.
Usually the loopback interface address is used to reduce the network vibration caused by
the Up/Down of a physical interface.
After the static RP is configured, it is not necessary to configure the Candidate-RP for the
group.
To configure the static RP address, use the following command.
Command Function
ZXR10(config-router)#static-rp < ip-address> [ group-list < acl-number> This configures static RP address.
] [ priority < priority> ]
Example
1. This example shows configuration of static RP 10.1.1.1 for all groups.
ZXR10(config-router)#static-rp 10.1.1.1
2. Configuration of the static RP 10.1.1.1 for the group 239.132.10.100 is shown below.
ZXR10(config-router)#static-rp 10.1.1.1 group-list 10
ZXR10(config-router)#exit
9.4.3 Configuring Candidate-BSR

If the static RP mechanism is not used then every multicast area must be configured
with the Candidate-BSR on more than one multicast routers. A BSR should be selected.
The BSR sends booting messages to advertise RP information. According to the latest
advertising messages, router running the PIM-SM updates the RP state. The bootstrap
message send by the BSR is also used to select the formal BSR in the Candidate-BSR.
To configure Candidate-BSR, use the following command
9-9

Command Function
ZXR10(config-router)#bsr-candidate < interface-name> [ < This configures Candidate-BSR.

hash-mask-length> ] [ < priority> ]
The default priority of Candidate-BSR is 0. Candidate-BSR with higher priority becomes

formal BSR.
9.4.4 Configure the Candidate-RP

In the PIM-SM, the RP is a root of the multicast RPT. It is responsible for sending the
multicast packet to the receiving member of the group in the downstream along the tree.
Each multicast group has only one formal RP.
To configure the Candidate-RP, use the following command.
Command Function
ZXR10(config-router)#rp-candidate < interface-name> [ group-list < This configures the Candidate-RP.

acl-number> ] [ priority < priority> ]
The default priority of the Candidate-RP is 0. The candidate-RP with greater priority value
has smaller priority.
9.4.5 Switching Routers with Directly Connected Receivers

Only the last hop DR and the RP can actively switch to the source shortest path tree.
By default, start to switch the source shortest path tree when the RP receives the first
registration information. For the last hop DR, configure the switch threshold strategy of
the source shortest path tree, with the unicast group as control granularity. If configuring
the switch threshold with infinity, switching does not occur. By default, switch must take
place if traffic exists.
Command Function
ZXR10(config-router)#spt-threshold infinity [ group-list < This switches routers with directly

access-list-number> ] connected receivers from SPT tree to
the RPT
9.4.6 Configuring the Area Border with the Interface PIM

Command Function
ZXR10(config-if-vlanX)#ip pim bsr-border This configures the area border with the
interface PIM.
Bootstrap data packets cannot pass the border in any direction. The command effectively
divides a network into different BSR areas. Other PIM packets can pass the area border.
9-10

9.4.7 Setting the RP to Filter the Received Register Packet

Command Function
ZXR10(config-router)#accept-register< acl-number> This sets the RP to filter the received

Register packet.
9.4.8 Limiting the BSR Message to Advertise to the Candidate-RP

To limit the BSR message to advertise to the Candidate-RP, use the following command
Command Function
ZXR10(config-router)#accept-rp < acl-number> This limits the BSR message to

advertise to the Candidate-RP.
9.4.9 Setting DR Priority

Command Function
ZXR10(config-if-vlanX)#ip pim dr-priority< priority> This sets the DR priority.
It is necessary to select a DR in a shared (or Multi-Access) network segment. Router with

the highest priority will win the selection. If the priorities are similar, the router with the
greatest IP address will be selected.
In the shared network segment connected with the multicast data source only the DR can
send the registration information to the RP. In the shared network segment connected with
the receiver only the DR can respond to the joining and leaving messages of the IGMP
and sends the PIM joining/prune message to the upstream.
The priority of the router is contained in the exchanging Hello message with the neighbor.
The default value is 0.
9.4.10 Setting the Sending Interval of the Hello Message

Command Function
ZXR10(config-if-vlanX)#ip pim query-interval < seconds> This sets the sending interval of the
Hello message.
9.4.11 Limiting PIM-SM Neighbor

Command Function
ZXR10(config-if-vlanX)#ip pim neighbor-filter < acl-number> This limits some routers to be PIM
neighbor.
9-11

Example
This example shows that the router 10.1.1.1 is limited to be the PIM neighbors on the
interface Vlan1.
ZXR10(config-std-acl)#rule 1 deny 10.1.1.1 0.0.0.0
ZXR10(config-std-acl)#rule 2 permit any
ZXR10(config-router)#exit
ZXR10(config-if-vlan1)#ip pim neighbor-filter 10
9.5 Configuring MSDP

9.5.1 Enabling MSDP
Command Function
ZXR10(config)#ip msdp peer < peer-address> connect-source < This configures an MSDP peer and
interface-name> enables MSDP.
9.5.2 Configuring Default MSDP Peer

Command Function
ZXR10(config)#ip msdp default-peer < peer-address> [ list < acl-number> ] This configures default MSDP peer.
When default MSDP peer is configured, the local router accepts all SA messages from the
peer.
9.5.3 Configuring an Originating RP

Command Function
ZXR10(config)#ip msdp originator-id < interface-name> This configures an originating RP.
This command generates the MSDP speaker of SA messages. It also uses address of
specified interface as the RP address in a SA.
9.5.4 Configuring the MSDP Peer as a Mesh Group Member

Command Function
ZXR10(config)#ip msdp mesh-group < peer-address> < mesh-name> This configures the MSDP peer as a
mesh group member.
9-12

A "mesh group" is a group of MSDP speakers. These speakers have fully meshed
connectivity.
9.5.5 Clearing Statistics Counter for MSDP Peers

Command Function
ZXR10#clear ip msdp statistics [ < peer-address> ] This clears statistics counter for MSDP
peers.

Command Function
peers.

Command Function
peers.

Command Function
peers.

Command Function
peers.
9-13

9.6 Configuring PIM-DM

1 ZXR10(config)#router pimdm This enables PIM-DM function.
2 ZXR10(config-if)#ip pim dm This adds an interface that runs

PIM-DM.
9.7 Configuring PIM-SNOOPING

1 ZXR10(config)#ip pim snooping This enables PIM-SNOOPING

function.
2 ZXR10(config-vlanX)#pim snooping This enables PIM-SNOOPING

function in VLAN.
9.8 Multicast Configuration Example

PIM-SM configuration and network topology is shown in Figure 9-1.
Figure 9-1 MULTICAST CONFIGURATION
R1 configuration:
ZXR10_R1(config)#ip multicast-routing
ZXR10_R1(config)#interface loopback1
ZXR10_R1(config-loopback1)#ip address 10.1.1.1 255.255.255.255
ZXR10_R1(config)#router pimsm
9-14

ZXR10_R1(config-router)#rp-candidate loopback1 priority 10

ZXR10_R1(config-router)#bsr-candidate loopback1 10 10
ZXR10_R1(config-if-vlan1)#ip pim sm
R2 configuration:
R3 configuration:
9-15


Note: Note the order of the configuration. Only ip multicast-routing is configured, can router
pimsm be configuredand then ip pim sm can be enabled on the interface.
9.9 Multicast Maintenance and Diagnosis

Common View Command
1. To view the IP multicast routing table, use the following command.
Command Function
ZXR10#show ip mroute [ group < group-address> ] [ source < This views the IP multicast routing table.
source-address> ] [ summary]
This shows the contents of the current IP multicast routing table.

ZXR10#show ip mroute
IP Multicast Routing Table
Flags:D -Dense,S -Sparse,C -Connected,L -Local,P -Pruned
R -RP-bit set,F -Register flag,T -SPT-bit set,J -Join SPT,
M - MSDP created entry,N -No Used,U -Up Send,
A - Advertised via MSDP,X -Proxy Join Timer Running,
* -Assert flag
Statistic：Receive packet count/Send packet count
Timers:Uptime/Expires
Interface state:Interface,Next-Hop or VCD,State/Mode
(*, 229.3.3.16), 00:00:01/00:03:34, RP 5.5.5.6 , 0/0, flags: SP

Incoming interface: vlan5, RPF nbr 5.5.5.6
Outgoing interface list: NULL
(100.1.1.100, 229.3.3.16), 00:00:01/00:03:34 , 0/0, flags: UN
Incoming interface: vlan4, RPF nbr 4.4.4.5
Outgoing interface list:
vlan6, Forward/Sparse, 00:00:01/00:03:29
2. To show multicast forwarding entries, use the following command.
9-16

Command Function
ZXR10#show ip mforwarding [ device < device-number> ] group-address This shows multicast forwarding entries.
< group-address> [ source-address < source-address> ] If the command does not carry source
address options, show (*, G) multicast
forwarding entries. If carrying source
address options, show (S, G) multicast
forwarding entries.
This shows the multicast forwarding entries.

ZXR10#show ip mforwarding group-address 229.3.3.16
IP Forwarding Multicast Routing Table
Flags: N -No Used,U -Up Send,L -Limit upSend,A - Assert send
(*, 229.3.3.16), Flags:, HitFlag:0, Incoming interface: Null,

LastSrcIp: 0.0.0.0
Outgoing vlan interface list: NULL
L2bitmap:0x0000000000000000 L3bitmap:0x0000000000000000
(100.1.1.100, 229.3.3.16), Flags:, HitFlag:0,

Incoming interface: vlan4 19/3, LastSrcIp: 0.0.0.0
Outgoing vlan interface list: NULL
L2bitmap:0x4000000000000008 L3bitmap:0x0000000000000000
3. To show the multicast reverse path forwarding message, use the following command.
Command Function
ZXR10(config)#show ip rpf < source-address> This shows the multicast reverse path
forwarding message.
4. To view the PIM-SM multicast routing table, use the following command.
Command Function
ZXR10(config)#show ip pimsm mroute [ group < group-address> ] [ This views the PIM-SM multicast routing
source < source-address> ] [ summary] table.
Viewing IGMP Information Commands

1. To view the IGMP configuration on the interface, use the following command.
Command Function
ZXR10#show ip igmp interface[ < interface-name> ] This views the IGMP configuration on
the interface.
9-17

This shows the IGMP configuration information of the Vlan4 interface.

ZXR10#show ip igmp interface vlan4
vlan4
Internet address is 4.4.4.4, subnet mask is 255.255.255.0
IGMP is enabled on interface
Current IGMP version is 2
IGMP query interval is 125 seconds
IGMP last member query interval is 1 seconds
IGMP query max response time is 10 seconds
IGMP querier timeout period is 251 seconds
IGMP querier is 4.4.4.4, never expire
Inbound IGMP access group is not set
IGMP immediate leave control is not set
2. To view the joining information of the IGMP group on the interface, use the following
command.
Command Function
ZXR10#show ip igmp groups[ < interface-name> ] This views the joining information of the
IGMP group on the interface.
This shows the group member information on the Vlan1 interface.
ZXR10#show ip igmp groups

IGMP Connected Group Membership
Group addr Interface Present Expire Last Reporter
224.1.1.1 vlan4 00:00:48 never 4.4.4.4
Viewing PIM-SM Information Commands

1. To view the BootStrap Router (BSR) information, use the following command.
Command Function
ZXR10#show ip pim bsr This views the BootStrap Router (BSR)

information.
This shows BSR information.

ZXR10#show ip pim bsr
BSR address: 6.6.6.6
Uptime: 00:00:11, BSR Priority :0, Hash mask length:30
Expires:00:00:49
This system is a candidate BSR
candidate BSR address: 6.6.6.6,priority: 0,hash mask length: 30
This System is Candidate_RP:
9-18

candidate RP address: 6.6.6.6(vlan6),priority:192
2. To view the RP set information advertised by the BSP, use the following command.
Command Function
ZXR10#show ip pim rp mapping This views the RP set information

advertised by the BSP.
This shows the RP set information advertised by the BSR.

ZXR10#show ip pim rp mapping
Group(s) 224.0.0.0/4
RP 5.5.5.6 static, Priority :192
RP 6.6.6.6 , :v2, Priority :192
BSR: 6.6.6.6 , via bootstrap
Uptime: 00:00:14, expires: 00:02:16
3. To show the RP information selected by the given multicast group, use the following
command.
Command Function
ZXR10#show ip pim rp hash < group-address> This shows the RP information selected
by the given multicast group.
This shows the RP information selected by the group 224.1.1.1.

ZXR10#show ip pim rp ha 224.1.1.1
rp address:5.5.5.6 static
4. To view the configuration of the PIM-SM interface, use the following command.
Command Function
ZXR10#show ip pimsm interface[ < interface-name> ] This views the configuration of the
PIM-SM interface.
This shows the configuration of the PIM-SM interface.
ZXR10#show ip pimsm interface

Address Interface State Nbr Query DR DR
Count Intvl Priority
4.4.4.4 vlan4 Up 0 30 4.4.4.4 1
5.5.5.5 vlan5 Up 0 30 5.5.5.5 1
6.6.6.6 vlan6 Up 0 30 6.6.6.6 1
0.0.0.0 vlan100 Down 0 30 0.0.0.0 1
5. To view the neighbors of the PIM-SM interface, use the following command.
9-19

Command Function
ZXR10#show ip pimsm neighbor[ < interface-name> ] This views the neighbors of the PIM-SM
interface.
This shows the neighbors of the PIM-SM interface.

ZXR10#show ip pimsm neighbor
Neighbor AddressInterface DR Prio Uptime Expires
131.1.1.91 vlan4 30000 00:19:34 00:01:29
22.22.22.43 vlan5 1 03:21:25 00:01:16
6. To trace the related information of the PIM-SM interface, use the following command.
Command Function
ZXR10#debug ip pimsm This traces the related information of

the PIM-SM interface.
This shows related information of the PIM-SM interface.
ZXR10#debug ip pimsm
PIMSM debugging is on
00:04:11 PIMSM: Received multicast data packet
(5.1.1.2, 224.1.1.1) from vlan1
00:04:11 PIMSM: Start creating (*,224.1.1.1)entry ...
00:04:11 PIMSM: (*,224.1.1.1)entry is created successfully
00:04:11 PIMSM: Start creating (5.1.1.2,224.1.1.1)entry ...
Viewing PIM-DM Information Commands
1 ZXR10#show ip pimdm interface [ < interface-name> ] This views configured PIM-DM

interface status.
2 ZXR10#show ip pimdm neighbor [ < interface-name> ] This views PIM-DM interface status.
3 ZXR10#show ip pimdm mroute [ [ group < group-address> [ source < This views PIM-DM multicast routing
source-address> ] ] | [ summary ] ] table content.
group < group-address> multicast group address, in dotted decimal mode
source < source-address> source addressin dotted decimal mode
summary brief
9-20

Viewing MSDP Commands

1. To view SA message statistics, use the following command.
Command Function
ZXR10#show ip msdp count This views SA message statistics.
2. To view MSDP neighbor detailed information, use the following command.
Command Function
ZXR10#show ip msdp peer [ < peer-address> ] This views MSDP neighbor detailed
information.
This shows MSDP neighbor detailed information.

ZXR10(config)#show ip msdp peer
MSDP Peer 11.1.1.1
Description:
Connection status:
State: Down, Resets: 0, Connection source: vlan4 (4.4.4.4)
Uptime(Downtime): 00:00:04, Messages sent/received: 0/0
Connection and counters cleared 00:00:04 ago
SA Filtering:
Input (S,G) filter: none
Output (S,G) filter: none
Peer ttl threshold: 0
SAs learned from this peer: 0
3. To view S and G status from each MSDP neighbor, use the following command.
Command Function
ZXR10#show ip msdp sa-cache [ < group-address> [ < source-address> ] ] This views S and G status from each
MSDP neighbor.
This views S and G status from each MSDP neighbor.

ZXR10#show ip msdp sa-cache
MSDP Source-Active Cache - 4 entries
(101.101.101.101, 224.1.1.1), RP 49.4.4.4, 00:21:45/ 00:05:57
(101.101.101.101, 224.1.1.2), RP 49.4.4.4, 00:21:45/ 00:05:57
(101.101.101.101, 226.1.1.1), RP 50.4.4.4, 00:09:04/ 00:04:57
(101.101.101.101, 226.1.1.2), RP 50.4.4.4, 00:09:04/ 00:04:57
4. To view MSDP neighbor status, use the following command.
Command Function
ZXR10#show ip msdp summary This views MSDP neighbor status.
9-21

This views MSDP neighbor status.

ZXR10#show ip msdp summary
MSDP Peer Status Summary
Peer Address State Uptime/ Reset SA
Downtime Count Count
101.1.1.1 Up 1d10h 9 2
*102.2.2.2 Up 14:24:00 5 20
103.3.3.3 Up 12:36:17 5 10
9-22

Chapter 10
Load Balance Configuration
Table of Contents
Load Balance Overview............................................................................................10-1
Configuring Load Balance ........................................................................................10-2
Load Balance Configuration Example.......................................................................10-2
Load Balance Maintenance and Diagnosis ...............................................................10-5
10.1 Load Balance Overview

Load balance is to forward data traffic through multiple activated links existing between
equipment and to fully take use of the bandwidth of multiple links. Load balance does not
mean that data traffic on links have same size.
Data traffic covers incoming traffic and outgoing traffic. Incoming and outgoing traffic load
balance is closely related to the route announced outside and learned by the equipment.
Incoming traffic load balance is affected by internal route announced outside by the
equipment and outgoing traffic load balance is affected by route announced inside by
the equipment. They directly affect the installation of multiple route entries reaching the
destination in the equipment forwarding table and the control of multiple routes.
ZXR10 5900E adopts route-based load balance to install multiple reachable route entries
for a destination address in the forwarding table through configuring the static route, routing
protocol and number of routes, thus laying foundation for load balance implementation.
ZXR10 5900E supports per-destination load balance policy. This policy considers the
source addresses and destination addresses of packets at the same time and make the
packets with the same “source address-destination address” pair pass through the same
path (even there are multiple available paths), and the packets with different “source
address-destination address” pairs pass through different paths. Such a policy ensures
the packets with the same “source address-destination address” pair to arrive in order.
Load balance becomes more effective if there are multiple “source address-destination
address” pairs in traffic.
Eight different paths can arrive at the destination at most in the ZXR10 5900E. Once load
balance is configured, interface traffic becomes balanced after a period.
10-1

10.2 Configuring Load Balance

1 ZXR10(config)#ip load-balance { sip-dip | sip | sip-l4port | This configures hash route method
sip-dip-l4port} of load balance. By default, SIP-DIP
is selected.
2 ZXR10(config-router)#maximum-paths { < number> | ibgp< This configures the maximum

number> } number of routers. This configures
the maximum count of routes in
the RIP, OSPF, IS-IS and BGP
route configuration mode. The
default number of route is 1 and the
maximum count is 32.
3 ZXR10(config)#ip route < prefix> < net-mask> { < forwarding-router's- This configures the load balance of
address> | < interface-name> } [ < distance-metric> ] [ tag < tag> ] static route. This configures multiple
static routes to the same destination
and supports at most 32 routes with
different tags. The default value of
the tag is 3.
10.3 Load Balance Configuration Example

R1 is connected to R2 over seven links. This is shown in Figure 10-1.
Figure 10-1 LOAD BALANCE CONFIGURATION
Static route and dynamic route protocol OSPF is taken as an example to describe load
balance configuration.
10-2

Chapter 10 Load Balance Configuration
10.3.1 Static Routing Load Balance

R1 configuration:
ZXR10_R1(config)#ip route 20.1.1.0 255.255.255.0 107.1.1.2 1

tag 157
tag 156
tag 155
tag 154
tag 153
tag 152
tag 151
R2 configuration:
10-3


tag 157
tag 156
tag 155
tag 154
tag 153
tag 152
tag 151
Seven links between R1 and R2 implement load balance and over these links, the user
PC1 and the user PC2 can access each other.
10.3.2 OSPF Load Balance

R1 configuration:
ZXR10_R1(config-router)#maximum-paths 7
R2 configuration:
10-4

Chapter 10 Load Balance Configuration

10.3.3 BGP Load Balance

R1 configuration:
ZXR10_R1(config-router)# neighbor 101.1.1.2 remote-as 200
R2 configuration:
ZXR10_R2(config-router)# network 20.1.1.0 255.255.255.0
Seven links between R1 and R2 implement load balance and over these links, the user
PC1 and the user PC2 can access each other.
10.4 Load Balance Maintenance and Diagnosis

To configure load balance maintenance and diagnosis, use the following command.
10-5

Command Function
ZXR10#show ip route [ < ip-address> [ < net-mask> ] | < protocol> ] This configures load balance
maintenance and diagnosis.
This can be seen that seven paths reaching the destination network segment 20.1.1.0/24
on R1 when adopting static route load balance:
ZXR10_R1#show ip route
IPv4 Routing Table:
20.1.1.0 255.255.255.255 107.1.1.1 Vlan1 static 1 0
106.1.1.1 Vlan2 static 1 0
105.1.1.1 Vlan3 static 1 0
104.1.1.1 Vlan4 static 1 0
103.1.1.1 Vlan5 static 1 0
102.1.1.1 Vlan6 static 1 0
101.1.1.1 Vlan7 static 1 0
10-6

Figures
Figure 2-1 STATIC ROUTE CONFIGURATION......................................................... 2-2
Figure 2-2 STATIC ROUTE SUMMARY .................................................................... 2-3
Figure 2-3 DEFAULT ROUTE CONFIGURATION ..................................................... 2-4
Figure 3-1 BASIC RIP CONFIGURATION................................................................. 3-4
Figure 4-1 OSPF ROUTER TYPES .......................................................................... 4-4
Figure 4-2 BASIC OSPF CONFIGURATION ........................................................... 4-13
Figure 4-3 MULTI-AREA OSPF CONFIGURATION................................................ 4-14
Figure 4-4 OSPF VIRTUAL LINK ........................................................................... 4-16
Figure 4-5 OSPF AUTHENTICATION ..................................................................... 4-18
Figure 5-1 IS-IS AREAS ........................................................................................... 5-2
Figure 5-2 SINGLE AREA CONFIGURATION........................................................... 5-7
Figure 5-3 MULTIPLE AREA IS-IS CONFIGURATION .............................................. 5-9
Figure 6-1 BASIC BGP CONFIGURATION ............................................................... 6-3
Figure 6-2 BGP ROUTE ADVERTISEMENT............................................................. 6-4
Figure 6-3 BGP AGGREGATE ADVERTISEMENT ................................................... 6-5
Figure 6-4 CONFIGURATION OF BGP MULTIHOP .................................................. 6-7
Figure 6-5 FILTERING ROUTES USING NLRI ......................................................... 6-8
Figure 6-6 LOCAL_PREF ATTRIBUTE ................................................................... 6-10
Figure 6-7 MED ATTRIBUTE .................................................................................. 6-11
Figure 6-8 BGP SYNCHRONIZATION CONFIGURATION ...................................... 6-14
Figure 6-9 BGP ROUTER REFLECTOR CONFIGURATION................................... 6-15
Figure 6-10 BGP CONFEDERATION CONFIGURATION........................................ 6-17
Figure 6-11 BGP CONFIGURATION ....................................................................... 6-19
Figure 7-1 MPLS Configuration Example .................................................................. 7-7
Figure 8-1 VPLS Networking..................................................................................... 8-2
Figure 8-2 VPLS Configuration Example 1.............................................................. 8-14
Figure 8-5 VPWS Configuration Example ............................................................... 8-19
Figure 9-1 MULTICAST CONFIGURATION ........................................................... 9-14
Figure 10-1 LOAD BALANCE CONFIGURATION .................................................. 10-2
I
Figures

Glossary
ABR
- Area Border Router
AS
- Autonomous System
AS
- Application Server
ASBR
- Autonomous System Boundary Router
BDR
- Backup Designate Router
BGP
- Border Gateway Protocol
BSR
- Bootstrap Router
CIDR
- Classless Inter-Domain Routing
CLNS
- ConnectionLess Network Sevice
DIS
- Designate IS
DR
- Designate Router
EBGP
- External Border Gateway Protocol
IBGP
- Interior Border Gateway Protocol
IGP
- Interior Gateway Protocol
IS-IS
- Intermediate System-to-Intermediate System
LSA
- Link State Advertisement
LSU
- Link State Update
III
MPLS
- Multi Protocol Label Switching
NBMA
- Non-Broadcast Multiple Access
NSSA
- Not-So-Stubby Area
OSPF
- Open Shortest Path First
PDU
- Protocol Data Unit
PIM-SM
- Protocol Independent Multicast - Sparse Mode
RP
- Rendezvous Point
SNP
- Sequence Num PDU
SPF
- Shortest Path First
VLSM
- Variable Length Subnet Mask
IV

ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual (IPv4 Routing Volume)

Uploaded by

Document Information

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 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual (IPv4 Routing Volume)

Uploaded by

Copyright:

Available Formats

ZXR10 5900E Series

Easy-Maintenance MPLS Routing Switch

Revision No. Revision Date Revision Reason

R1.0 2011-02-11 First Release

Serial Number: SJ-20101226010430-004

Publishing Date: 2011-02-11(R1.0)

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

Chapter 7 MPLS Configuration ................................................................. 7-1

Chapter 8 VPLS Configuration .................................................................. 8-1

Chapter 9 Multicast Routing Configuration ............................................. 9-1

Chapter 10 Load Balance Configuration ................................................ 10-1

l ZXR10 5916E Easy-Maintenance MPLS Routing Switch

What Is in This Manual

The commands supported by ZXR10 5900E series (V2.8.23.B2) easy-maintenance MPLS

1.1 Safety Instruction

1.2 Safety Signs

Indicates the matters needing attention during configuration.

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

Indicates the description, hint, tip and so on for configuration operations.

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

2.1 Static Route Overview

2.2 Configuring Static Route

2.3 Static Route Configuration Example

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

Figure 2-1 STATIC ROUTE CONFIGURATION

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

2.3.2 Static Route Summary Example

Figure 2-2 STATIC ROUTE SUMMARY

2.3.3 Default Route Configuration Example

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

Figure 2-3 DEFAULT ROUTE CONFIGURATION

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

2.4 Static Route Maintenance and Diagnosis

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

3.1 RIP Overview

3.1.2 RIP Routing Metric

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

3.1.3 RIP Timer

3.1.4 Route Updates

3.2 Configuring RIP

1 ZXR10#ZXR10(config)#router rip This enables RIP.

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

3.2.2 Adjusting RIP Timer

3.2.3 Configuring RIP Neighbor

ZXR10(config-router)#neighbor < ip-address> This configures neighbor router which

3.2.4 Configuring RIP Authentication

Step Command Function

3.2.5 Configuring split horizon mechanism

ZXR10(config-if-vlanX)# ip split-horizon This enables the split horizon

3.2.6 Configuring Poison Reverse Mechanism

ZXR10(config-if-vlanX)#ip poison-reverse This enables the poison reverse

SJ-20101226010430-004|2011-02-11(R1.0) ZTE Proprietary and Confidential

3.2.7 Redistributing a Route

3.2.8 Configuring RIP Version

Step Command Function

1 ZXR10(config-router)#version{ 1| 2} This designates the global RIP

2 ZXR10(config-if-vlanX)#ip rip receive version { 1| 2} [ 1| 2] This designates the RIP version

3.3 RIP Configuration Example