zxr10 ZSR v2

ZXR10 ZSR V2
Intelligent Integrated Multi-Service Router

Configuration Guide (IPv6)
Version: 2.00.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2014 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-05-10 First edition
Serial Number: SJ-20140504150128-018
Publishing Date: 2014-05-10 (R1.0)
SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 IPv6 Basic Configuration ......................................................... 1-1
1.1 IPv6 Overview.................................................................................................... 1-1
1.2 Configuring IPv6 ................................................................................................ 1-1
Chapter 2 IPv6 Address Configuration..................................................... 2-1

2.1 IPv6 Address Overview ...................................................................................... 2-1
2.1.1 Address Classification .............................................................................. 2-3
2.1.2 Address Format ..................................................................................... 2-10
2.1.3 IPv6 Address Auto Configuration Technology ........................................... 2-12
2.2 Configuring an IPv6 Address............................................................................. 2-13
2.3 IPv6 Address Configuration Example................................................................. 2-15
Chapter 3 NDP Configuration.................................................................... 3-1

3.1 NDP Overview ................................................................................................... 3-1
3.2 Configuring NDP ................................................................................................ 3-2
3.3 NDP Configuration Example ............................................................................... 3-6
Chapter 4 IPv6 Static Route Configuration .............................................. 4-1

4.1 IPv6 Static Route Overview................................................................................. 4-1
4.2 Configuring a Static IPv6 Route........................................................................... 4-1
4.3 Configuration Instances of IPv6 Static Route........................................................ 4-3
4.3.1 Example: Configuring a Direct Static IPv6 Route (Direct Next Hop) ............. 4-3
4.3.2 Example: Configuring a Static IPv6 Route (Indirect Next Hop)..................... 4-5
4.3.3 Example: Configuring a Default IPv6 Route ............................................... 4-6
4.3.4 Example: Configuring FRR for Static IPv6 Route in a Public Network .......... 4-7
4.3.5 Example: Configuring FRR for Static IPv6 Route in a Private Network ....... 4-10
4.3.6 Example: Configuring Load Sharing from Static IPv6 Routes .................... 4-12
4.3.7 Example: Configuring the Next Hop Address of the BFD Source Side of
a Static IPv6 Route ............................................................................... 4-14
Chapter 5 RIPng Configuration ................................................................. 5-1

5.1 RIPng Overview ................................................................................................. 5-1
5.2 Configuring RIPng .............................................................................................. 5-3
5.3 RIPng Configuration Instances ............................................................................ 5-5
5.3.1 RIPng Basic Configuration Example .......................................................... 5-5
5.3.2 RIPng Route Collection Configuration Example........................................ 5-10

Chapter 6 OSPFv3 Configuration.............................................................. 6-1
6.1 OSPFv3 Overview.............................................................................................. 6-1
6.2 Configuring OSPFv3........................................................................................... 6-5
6.3 OSPFv3 Configuration Instances........................................................................6-11
6.3.1 OSPFv3 Basic Configuration Example......................................................6-11
6.3.2 OSPFv3 Redistribution Configuration Example......................................... 6-14
6.3.3 OSPFv3 Route Load-Sharing Configuration Examples ............................. 6-19
Chapter 7 IS-ISv6 Configuration ............................................................... 7-1

7.1 IS-ISv6 Overview ............................................................................................... 7-1
7.2 Configuring IS-ISv6 ............................................................................................ 7-2
7.3 IS-ISv6 Configuration Examples .......................................................................... 7-9
7.3.1 Single-Area IS-ISv6 Configuration Example ............................................... 7-9
7.3.2 Multi-Area IS-ISv6 Configuration Example ............................................... 7-14
Chapter 8 BGP4+ Configuration ............................................................... 8-1

8.1 BGP4+ Overview ............................................................................................... 8-1
8.2 Configuring BGP4+ ............................................................................................ 8-1
8.3 BGP4+ Configuration Instances .......................................................................... 8-3
8.3.1 Example: Configuring a BGP4+ Route Reflector ........................................ 8-3
8.3.2 Example: Configuring BGP4+ Route Load Sharing..................................... 8-5
8.3.3 Example: Configuring BGP4+ ................................................................... 8-7
Chapter 9 IPv6 Route-Map Policy Configuration..................................... 9-1

9.1 IPv6 Routing Policy Configuration ....................................................................... 9-1
9.1.1 Configuring the IPv6 Routing Policy........................................................... 9-1
9.1.2 IPv6 Routing Policy Configuration Instances .............................................. 9-7
9.2 IPv6 Policy Route Configuration ........................................................................ 9-30
9.2.1 Configuring IPv6 Policy Routes ............................................................... 9-30
9.2.2 IPv6 Policy Route Configuration Example ................................................ 9-31
Chapter 10 IPv6 Multicast ........................................................................ 10-1

10.1 Multicast Overview ......................................................................................... 10-1
10.2 Configuring Public IP Multicast ........................................................................ 10-3
Chapter 11 IPv6 Static Multicast Configuration..................................... 11-1

11.1 IPv6 Static Multicast Overview..........................................................................11-1
11.2 Configuring IPv6 Static Multicast.......................................................................11-2
11.3 IPv6 Static Multicast Configuration Example ......................................................11-3
Chapter 12 MLD Configuration................................................................ 12-1

12.1 MLD Overview ............................................................................................... 12-1
II

12.2 Configuring MLD ............................................................................................ 12-2
12.3 MLD Configuration Instances .......................................................................... 12-6
12.3.1 Example: Configurating MLD Querier Router Election............................. 12-6
12.3.2 Example: Configuring a Router to Join a Static MLD Group and a
Dynamic MLD Group............................................................................. 12-8
Chapter 13 IPv6 PIM-DM Configuration.................................................. 13-1

13.1 PIM-DM Overview .......................................................................................... 13-1
13.2 Configuring IPv6 PIM-DM ............................................................................... 13-1
13.3 IPv6 PIM-DM Configuration Example............................................................... 13-2
Chapter 14 IPv6 PIM-SM Configuration .................................................. 14-1

14.1 PIM-SM Overview .......................................................................................... 14-1
14.2 Configuring IPv6 PIM-SM................................................................................ 14-3
14.3 IPv6 PIM-SM Configuration Example ............................................................... 14-7
Chapter 15 IPv6 PIM-SSM Configuration................................................ 15-1

15.1 PIM-SSM Overview ........................................................................................ 15-1
15.2 Configuring IPv6 PIM-SSM ............................................................................. 15-1
15.3 IPv6 PIM-SSM Configuration Example............................................................. 15-2
Chapter 16 IPv6 Tunnel Configuration ................................................... 16-1

16.1 IPv6 Tunnel Configuration ............................................................................... 16-1
16.1.1 IPv6 Tunnel Overview........................................................................... 16-1
16.1.2 Configuring IPv6 Tunnels ...................................................................... 16-5
16.1.3 IPv6 Tunnel Configuration Examples ..................................................... 16-6
16.2 ISATAP Tunnel Configuration .........................................................................16-13
16.2.1 ISATAP Tunnel Overview .....................................................................16-13
16.2.2 Configuring ISATAP Tunnels ................................................................16-14
16.2.3 ISATAP Configuration Example ............................................................16-15
Chapter 17 6RD Configuration ................................................................ 17-1

17.1 6RD Overview................................................................................................ 17-1
17.2 Configuring 6RD Tunnels ................................................................................ 17-5
17.3 6RD Configuration Example ............................................................................ 17-6
Chapter 18 6PE Configuration................................................................. 18-1

18.1 6PE Overview ................................................................................................ 18-1
18.2 Configuring 6PE ............................................................................................. 18-2
18.3 6PE Configuration Example ............................................................................ 18-2
Chapter 19 6VPE Configuration .............................................................. 19-1

19.1 6VPE Overview .............................................................................................. 19-1
III

19.2 Configuring 6VPE........................................................................................... 19-2
19.3 6VPE Configuration Example ......................................................................... 19-11
Chapter 20 IPv6 ACL Configuration........................................................ 20-1

20.1 IPv6 ACL Overview ........................................................................................ 20-1
20.2 Configuring IPv6 ACL ..................................................................................... 20-1
20.3 IPv6 ACL Configuration Example..................................................................... 20-4
Chapter 21 IPv6 URPF Configuration ..................................................... 21-1

21.1 URPF Overview ............................................................................................. 21-1
21.2 Configuring IPv6 URPF................................................................................... 21-2
21.3 IPv6 URPF Configuration Instances................................................................. 21-3
21.3.1 Example: Configuring IPv6 URPF (Strict)............................................... 21-3
21.3.2 Example: Configuring IPv6 URPF (Loose) ............................................. 21-4
Chapter 22 IPv6 QoS Configuration........................................................ 22-1

22.1 IPv6 QoS Overview ........................................................................................ 22-1
22.2 Configuring IPv6 QoS ..................................................................................... 22-1
22.3 IPv6 QoS Configuration Examples................................................................... 22-1
22.3.1 Example: Configuring IPv6 Priority Scheduling....................................... 22-1
22.3.2 Example: Configuring IPv6 WRED ........................................................ 22-3
22.3.3 Example: Configuring IPv6 CAR............................................................ 22-5
22.3.4 Example: Configuring IPv6 Priority Inheritance....................................... 22-6
Chapter 23 IPv6 VRRP Configuration ..................................................... 23-1

23.1 IPv6 VRRP Overview...................................................................................... 23-1
23.2 Configuring IPv6 VRRP .................................................................................. 23-1
23.3 IPv6 VRRP Configuration Examples ................................................................ 23-4
23.3.1 Example: Basic VRRP Configuration ..................................................... 23-4
23.3.2 Example: Symmetrical VRRP Configuration ........................................... 23-7
23.3.3 Example: VRRP Heartbeat Configuration............................................... 23-9
Chapter 24 DHCPv6 Configuration ......................................................... 24-1

24.1 DHCPv6 Overview ......................................................................................... 24-1
24.2 Configuring the DHCPv6 Server ...................................................................... 24-3
24.3 Configuring a DHCPv6 Relay .......................................................................... 24-7
24.4 Configuring the DHCPv6 Client ......................................................................24-10
24.5 DHCPv6 Configuration Examples ...................................................................24-10
24.5.1 DHCPv6 Server Configuration Example ................................................24-10
24.5.2 DHCPv6 Relay Configuration Example .................................................24-13
24.5.3 DHCPv6 Client Configuration Example .................................................24-16
IV

Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII

This page intentionally left blank.
VI

About This Manual
Purpose
This manual describes the principles, configuration commands and configuration
examples about implementing IPv6 on ZXR10 ZSR V2.
Intended Audience
This manual is intended for:
l Network planning engineers
l Commissioning engineers
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, IPv6 Basic Configuration Describes the chief changes of IPv6 relative to IPv4, and the
configuration commands of ICMPv6 and TCPv6.
2, IPv6 Address Configuration Describes the IPv6 Address principle, configuration commands
and configuration examples.
3, NDP Configuration Describes the NDP principle, configuration commands and

configuration examples.
4, IPv6 Static Route Configuration Describes the IPv6 Static Route principle, configuration
commands and configuration examples.
5, RIPng Configuration Describes the RIPng principle, configuration commands and

6, OSPFv3 Configuration Describes the OSPFv3 principle, configuration commands and

7, IS-ISv6 Configuration Describes the IS-ISv6 principle, configuration commands and

8, BGP4+ Configuration Describes the BGP4+ principle, configuration commands and

9, IPv6 Route-Map Policy Describes the IPv6 route policy and its principles, configuration
Configuration commands and configuration examples.
10, IPv6 Multicast Describes the IPv6 Multicast principle, configuration commands

Chapter Summary
11, IPv6 Static Multicast Describes the IPv6 Static Multicast principle, configuration
Configuration commands and configuration examples.
12, MLD Configuration Describes the MLD principle, configuration commands and
13, IPv6 PIM-DM Configuration Describes the IPv6 PIM-DM principle, configuration commands
14, IPv6 PIM-SM Configuration Describes the IPv6 PIM-SM principle, configuration commands
15, IPv6 PIM-SSM Configuration Describes the IPv6 PIM-SSM principle, configuration commands
16, IPv6 Tunnel Configuration Describes the IPv6 Tunnel principle, configuration commands
17, 6RD Configuration Describes the 6RD principle, configuration commands and
18, 6PE Configuration Describes the 6PE principle, configuration commands and
19, 6VPE Configuration Describes the 6VPE principle, configuration commands and
20, IPv6 ACL Configuration Describes the IPv6 ACL principle, configuration commands and
21, IPv6 URPF Configuration Describes the IPv6 URPF principle, configuration commands
22, IPv6 QoS Configuration Describes the IPv6 QoS principle, configuration commands and
23, IPv6 VRRP Configuration Describes the IPv6 VRRP principle, configuration commands
24, DHCPv6 Configuration Describes the DHCPv6 principle, configuration commands and
Conventions
This manual uses the following typographical conventions:
Typeface Meaning
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check boxes,
drop-down lists, dialog box names, window names, parameters, and commands.
Constant Text that you type, program codes, filenames, directory names, and function names.
width
II

Typeface Meaning
[] Optional parameters.
{} Mandatory parameters.
| Separates individual parameter in series of parameters.
Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or serious injury, equipment damage, or site breakdown.
Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.
Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a certain topic.
III

IV

Chapter 1
IPv6 Basic Configuration
Table of Contents
IPv6 Overview ............................................................................................................1-1
Configuring IPv6.........................................................................................................1-1
1.1 IPv6 Overview

Internet Protocol version 6 (IPv6) is a new version of the Internet Protocol. The significant
changes from IPv4 to IPv6 are as follows:
l Expanded addressing capabilities
IPv6 increases the IP address size from 32 bits to 128 bits, to support more levels
of addressing hierarchy, a much greater number of addressable nodes, and simpler
auto-configuration of addresses. The scalability of multicast routing is improved by
adding a "scope" field to multicast addresses. And a new type of address called an
"anycast address" is defined, used to send a packet to any one of a group of nodes.
l Header format simplification
Some IPv4 header fields have been dropped or made optional, to reduce the
common-case processing cost of packet handling and to limit the bandwidth cost of
the IPv6 header.
l Improved support for extensions and options
Changes in the way IP header options are encoded allows for more efficient
forwarding, less stringent limits on the length of options, and greater flexibility for
introducing new options in the future.
l Flow labeling capability
A new capability is added to enable the labeling of packets belonging to particular
traffic "flows" for which the sender requests special handling, such as non-default
quality of service or "real-time" service.
l Authentication and privacy capabilities
Extensions to support authentication, data integrity, and (optional) data confidentiality
are specified for IPv6.
1.2 Configuring IPv6

This procedure describes how to configure the basic functions of IPv6, including ICMPv6
and TCPv6.
1-1

ZXR10 ZSR V2 Configuration Guide (IPv6)
Steps
1. Configure ICMPv6.
If a router cannot process an IP packet due to some reasons (no route can be found
or the packet contains a wrong layer 3 protocol number), an ICMP error packet is
generated possibly and sent back to the source node of the IP packet. The source
node corrects the reported error.
Step Command Function
1 ZXR10(config)#interface <interface-name> Enters interface configuration

mode.
2 ZXR10(config-if-interface-name)#ipv6 forward After this command is

unreachable configured, the forwarding
plane forwards a packet of
an unknown protocol or a
packet whose route cannot
be found to the control plane.
The control plane returns an
ICMP destination unreachable
packet to the source node.
By default, this function is
disabled (the original packet
triggering the generation of
an ICMPv6 error packet is
discarded on the forwarding
plane).
3 ZXR10(config)#icmp-config Enters ICMP configuration

mode.
4 ZXR10(config-icmp)#interface {byname Enters ICMP interface

<interface-byname>|<interface-name>} configuration mode.
5 ZXR10(config-icmp-if-interface-name)#ip Enables a specified interface

unreachable to send ICMPv6 destination
unreachable packets. By
default, this function is
enabled.
<interface-byname>: interface alias, containing up to 32 characters.

<interface-name>: interface name, containing 1 through 32 characters.
2. Configure TCPv6.
TCPv6 is based on IPv6. TCPv6 has the same functions as TCPv4, so this manual
does not cover those functions again.
1-2

Chapter 1 IPv6 Basic Configuration
Command Function
ZXR10(config)#ipv6 tcp synwait-time <wait-time> Sets the duration of attempting to

establish a TCP connection,
which affects the TCP
connections established
afterwards. Range: 3080,
unit: second, default: 75
seconds.
ZXR10(config)#ipv6 tcp window-size <wait-size> Sets the size of the window

for listening to TCP packets,
which is invalid for the existing
TCP connections. Range:
10065535, unit: byte, default:
32768 bytes.
ZXR10(config)#ipv6 tcp finwait-time <wait-time> Sets the duration of waiting to

close a TCP connection. Range:
300675, unit: second, default:
675 seconds.
ZXR10(config)#ipv6 tcp queuemax <packet-numbers> Sets the maximum TCP output

queue length, which is invalid for
the existing connections. Range:
550, unit: packets, default: 5
packets.
3. Verify the configurations.

To improve transfer efficiency, IPv6 does not support fragmentation by intermediate
nodes. When the length of an IPv6 packet that is forwarded by the intermediate node
is greater than the MTU of the interface of the intermediate node, an ICMPv6 error
packet is sent to inform the source node of the Path MTU value (PMTU). In this way,
packets are fragmented on the source node.
Command Function
ZXR10#show ipv6 pmtu Displays the MTU value learned

on the local device.
ZXR10#show tcp6 brief Displays brief information about

all TCPv6 connections.
ZXR10#show tcp6 config Displays information about

TCPv6 configuration parameters.
ZXR10#show tcp6 statistics Displays TCP layer statistical

parameters.
ZXR10#show tcp6 tcb <tcb-index> Displays the TCPv6 connection

parameters of the specified TCB.
1-3

4. Maintain IPv6.
Command Function
ZXR10#clear tcp6 connect {<local-ipv6-address>| vrf Clears IPv6 TCP connections,

<vrf-name><local-ipv6-address>}<local-port><remote-ipv6-addr including the Telnet, FTP, and
ess><remote-port> BGP connections based on IPv6
TCP.
ZXR10#clear tcp6 statistics Clears IPv6 TCP statistical

information.
ZXR10#clear tcp6 tcb <tcb-index> Clears the connection associated

with the specified TCB. TCB
index range: 14294967295.
ZXR10#debug ipv6 packet [interface <interface-name>][proto Enables the debugging function

col {tcp | udp | icmp}][{detail}] of the IPv6 protocol to display
debugging information about
IPv6 protocol processing and
whether a router is sending
or receiving IPv6 packets.
Information can be printed
by specifying an interface, a
protocol number, or details.
ZXR10#debug ipv6 icmp Enables the debugging function

of the ICMPv6 protocol to display
debugging informatio about
ICMPv6 protocol processing,
and whether a router is sending
or receiving ICMP packets.
ZXR10#debug ipv6 tcp all Enables all print functions related

to the IPv6 TCP protocol.
ZXR10#debug ipv6 tcp driver Enables the debugging

function for information about
establishing and closing IPv6
TCP connections.
ZXR10#debug ipv6 tcp packet Enables the debugging function

for IPv6 TCP packets, containing
source, destination, and other
information, received/sent on the
router.
ZXR10#debug ipv6 tcp transactions Enables the debugging function

for information about TCP status
transition.
1-4

Chapter 1 IPv6 Basic Configuration
Command Function
ZXR10#debug ipv6 udp Enables the debugging function

for IPv6 TCP packets, containing
source, destination, and other
information, received/sent on the
router.
ZXR10#show debug ipv6 Displays the IPv6 protocol

debugging functions that have
been enabled.
ZXR10#show debug icmp6 Displays the ICMPv6 protocol

been enabled.
ZXR10#show debug tcp6 Displays the IPv6 TCP protocol

been enabled.
ZXR10#show debug udp6 Displays the IPv6 UDP protocol

been enabled.
<local-ipv6-address>: local IP address in colon-separated, hexadecimal format.

<vrf-name>: VRF name of the IP address, containing 1 to 32 characters.
<local-port>: local port number, range: 165535.
<remote-ipv6-address>: remote IP address in colon-separated, hexadecimal format.

<remote-port>: remote port number, range: 165535.
End of Steps
1-5

1-6

Chapter 2
IPv6 Address Configuration
Table of Contents
IPv6 Address Overview ..............................................................................................2-1
Configuring an IPv6 Address ....................................................................................2-13
IPv6 Address Configuration Example .......................................................................2-15
2.1 IPv6 Address Overview

IPv6 Address Introduction
Internet Protocol (IP) version 6 is a new IP protocol, designed to replace IP version 4,
the Internet protocol that is predominantly deployed and extensively used throughout the
world.
However, the original design did not anticipate the following conditions:
l Recent exponential growth of the Internet and the impending exhaustion of the Internet
Protocol version 4 (IPv4) address space.
l Growth of the Internet and the ability of Internet backbone routers to maintain large
routing tables.
l Need for simpler auto configuration and renumbering.
l Requirement for security at the IP level.
l Need for better support to real-time delivery of data, also called Quality of Service
(QoS).
Note:
Features such as IP Security Protocol (IPSec) and QoS have been specified for both
versions of IP.
Internet Protocol Version 6 (IPv6) features a huge address capacity up to 128 bits, which
is described as follows:
l It provides 2128 different IPv6 addresses, that is, the
number of the allocable addresses around the world is
340,282,366,920,938,463,463,374,607,431,768,211,456.
l It provides 2.2*1020 addresses per cm2 if addresses are allocated based on ground
area.
2-1

IPv4 and IPv6 Header Format

The following are differences between IPv4 and IPv6 in header format.
The header formats of IPv4 and IPv6 as shown in Figure 2-1 andFigure 2-2 respectively.
(Numbers in the figures refer to bit numbers.)
Figure 2-1 IPv4 Header Format
Figure 2-2 IPv6 Header Format
IPv6 header is simpler than IPv4 header in structure because many fields in IPv4 header
that are not frequently used are deleted from IPv6 header, and are put into its options and
header extension, which are defined more strictly.
l IPv4 contains ten fields with fixed length, two address spaces and some options, while
IPv6 contains only six fields and two address spaces.
l Although IPv6 header occupies 40 bytes, which is 1.6 times of IPv4 header with
24-bytes, it does not consume too much memory capacity due to its fixed length (the
length of the IPv4 header is variable).
l The following six fields are deleted from IPv4 header: header length, type of service,
identifier, flags, fragmented offsets and header checksum. Names and some functions
of the three fields of total length, protocol and Time to Live (TTL) are changed, and
its optional functions are completely changed. Apart from this, two fields are added:
traffic type and flow label.
l IPv6 header format is greatly simplified, which effectively pares down overhead of
processing headers by a router or switch. At the same time, IPv6 enhances the
2-2

Chapter 2 IPv6 Address Configuration
support to the extension header and options, which not only allows more efficient
forwarding, but also provides sufficient support for future loading of new applications
to networks. Each IPv6 packet can have 0, 1 or more extension headers. Each
extension header is determined by the "next header" domain of the previous header.
2.1.1 Address Classification

Request For Comments (RFC) contains a "map" of IPv6 address space, which describes
how the address space is allocated, the different types of address allocation, the prefixes
(the starting few bits in address allocation) and the length of address allocation, which is
a part of the whole address space. Table 2-1 shows allocation of IPv6 address space.
Table 2-1 IPv6 Address Space
Allocation Prefix Fraction of Address Space
Reserved 0000 0000 1/256
Unallocated 0000 0001 1/256
Reserved for NSAP allocation 0000 001 1/128
Reserved for IPX allocation 0000 010 1/128
Unallocated 0001 1/32
Aggregatable global unicast 001 [2,3] 1/8

address
Unallocated 010 1/8
Unallocated 011 1/8
Unallocated 100 1/8
Unallocated 101 1/8
Unallocated 110 1/8
Unallocated 1110 1/16
Unallocated 1111 1110 0 1/512
Link local unicast address 1111 1110 10 [FE8] 1/1024
2-3

Allocation Prefix Fraction of Address Space
Site local unicast address 1111 1110 11 [FEC] 1/1024
Multicast address 1111 1111 [FF] 1/256
Note:
The hex number in [] in this table refers to the starting and ending hex numbers of the
corresponding address.
Broadcast address in IPv6 is not valid any more. RFC defines three types of IPv6 address:
l Unicast
It is the identifier of a single interface. The packets sent to a unicast address are
transmitted to the interface with this address identifier.
l Multicast
It is the identifier of a group of interfaces. These interfaces belong to different nodes.

The packets sent to a multicast address are transmitted to all the interfaces with this
address identifier.
l Anycast
It is the identifier of a group of interfaces. These interfaces belong to different nodes.
The packets sent to an anycast address are transmitted to an interface with this
address identifier (selecting the nearest one by calculating the distance based on
routing protocol).
An IPv6 unicast address can be regarded as an entity with two fields. One field is used
to identify networks and the other is used to identify interfaces of nodes on this network.
In the subsequent description of the specific unicast address types, the user finds that
the network identifier can be divided into several parts, each of which identifies different
network parts.
Unicast Address
Functions of an IPv6 unicast address are subject to Classless Inter-Domain Routing
(CIDR), which is the same as that of an IPv4 address. That is, an address is divided into
two parts upon a specific boundary. The high bit part of an address includes a prefix for
routing and the low bit part includes identifiers of network interfaces.
In the IPv6 addressing system structure, any IPv6 unicast address requires an interface
identifier. An interface identifier is very similar to the 48-bit Media Access Control (MAC)
address. The MAC addresses are encoded through hardware in a network interface card.
They are burned by the manufacturer into a network interface card and are globally unique.
2-4

There are no two network interface cards with an identical MAC address. Such addresses
can be used to uniquely identify the interfaces at the network link-layer.
The interface identifier of an IPv6 host address is based on the Institute of Electrical and
Electronics Engineers (IEEE) EUI-64 format, which creates a locally and globally unique
64-bit interface identifier based on the existing MAC addresses.
These 64-bit interface identifiers can address one by one globally and can uniquely identify
the interface of each network. This means that, in theory, there are up to 264 different
physical interfaces and about 1.8 x 1019 different addresses, which, however, only occupy
half of the IPv6 address space. It is enough in the foreseeable future at least.
The IPv6 unicast address can be classified into the following categories:
l Aggregatable Global Unicast Address
This is another kind of aggregation, which is independent of an Internet Service

Provider (ISP). The provider-based aggregatetive addresses must be changed as
a provider changes, while the exchange-based addresses are directly located by
an IPv6 switching entity. The exchange provides address blocks, and users and
providers conclude contracts for the network access.
Such network access is either directly provided by a provider, or indirectly provided

by an exchange. However, the routing is through the exchange. In this way, a user
needs not to address again when it changes a provider. At the same time, users are
allowed to use multiple ISPs to process single-block network address.
Aggregatable global unicast addresses include all the addresses whose three starting
bits are 001, which can be used as prefixes for other unallocated unicast. Table 2-2
lists the aggregatable global unicast address fields.
Table 2-2 Aggregatable Global Unicast Address Fields
3 13 8 24 16 64
FP TLA ID RES NLA ID SLA ID Interface identifier
Table 2-2 includes the following fields.
FP field
This is the 3-bit format prefix in an IPv6 address, indicating to which address
category in the IPv6 address space this address belongs. Currently, the field is
001, indicating this is an aggregatable global unicast address.
TLA ID field
This is the top-level aggregation identifier, including the routing information about
the addresses at the highest level. Here, it refers to the routing information with
the most hosts in network interconnection. Currently, this field is 13 bits and can
obtain at most 8,192 different top level routes.
RES field
2-5

This is an 8-bit field and reserved for future use. It is likely to be used for extending
the top- or next-level aggregation identifier field.
NLA ID field
This is the next-level aggregation identifier with 24 bits. This identifier is used
by some institutions (including large-size ISPs and other institutions that provide
public network access) to control the top-level aggregation for address space
arrangement.
Such institutions can divide this 24-bit field for use in accordance with their own
addressing hierarchical structures. In this way, an entity can divide two bits of
address space into four internal top-level routes, and allocate the other 22 bits of
address space to other entities (for example, a small local ISP).
When these entities obtain enough address space, they can subdivide the obtained
space in the same way as mentioned above.
SLA ID field
This is the site aggregation identifier and is used by some institutions to arrange
their internal network structures. Each institution can create its own internal
hierarchical network structure in the same way as that of IPv4.
When the 16-bit field is dedicated to the plane address space, there are at most
65,535 different subnets available. If the first eight bits are used for the internal
advanced routing of this institution, then there will be 255 advanced subnets
available, and each advanced subnet can have up to 255 sub-subnets.
Interface identifier field
This is a 64-bit field, containing 64-bit values of the IEEE EUI-64 interface
identifier.
l Special Address & Reserved Address
In the first 1/256 IPv6 address space, the first 8 bits 0000 0000 of all the addresses
are reserved. Most of the vacant address spaces are used for special addresses,
including:
Undesignated address
This is an all-zero address and is used if no valid address is available. For

example, if a host does not obtain an IPv6 address upon its initial startup from
the network, it can use this address. That is, it can specify this address for the
source address of the IPv6 packet when it sends out a request for configuration
information. This address can be expressed as 0:0:0:0:0:0:0:0, or expressed as
::.
Loopback address
In IPv4, the loopback address is defined as 127.0.0.1. Any packet that sends a
loopback address must be sent to a network interface through a protocol stack,
instead of being sent to the network link. The network interface itself should
2-6

accept these packets in the same way as it receives packets from external nodes,
and transmits them back to the protocol stack.
The loopback function is used for software test and configuration. Except the
lowest bit, all the other bits of an IPv6 loopback address are 0, that is, a loopback
address can be expressed as 0:0:0:0:0:0:0:1 or ::1.
IPv6 address embedded with IPv4 address
IPv6 provides two kinds of addresses. One is the IPv4-compatible address, which
allows the IPv6 node to access IPv4 nodes that do not support IPv6.. The other is
the IPv4-mapping address, which allows the IPv6 router to transmit IPv6 packets
over the IPv4 network in tunnel mode, where the nodes understand both IPv4
and IPv6.
The high-order 80 bits of these two kinds of addresses are all set to zeros, and
the low-order 32 bits contain the IPv4 address. If the middle 16 bits of an address
are set to FFFF, it indicates that this address is the IPv6 address mapping to IPv4
address. Table 2-3 lists the address structures of these two kinds of addresses.
Table 2-3 Structure of the IPv6 Address Embedded With IPv4 Address
IPv4 Compatible Address
80 16 32
0000.................................0000 0000 IPv4 address
IPv4 image address
80 16 32
0000.................................0000 FFFF IPv4 address
l Link Local Address and Site-Local Address

Using the network Model 10 address to translate IPv4 network addresses provides
an option for the institutions that do not want to request globally unique IPv4 network
addresses.
A router that resides outside of an institution but used by the institution shall not
forward these addresses. It can neither prevent these addresses from being
forwarded, nor distinguish these addresses from other valid IPv4 addresses. It is
comparatively easier to make configurations for a router to enable it to forward these
addresses.
To implement this function, IPv6 allocates two different address segments from the
globally unique Internet space. Table 2-4 is originated from RFC, indicating the
structures of link-local and site-local addresses.
Table 2-4 Structures of Link-local Address and Site-local Address
Link-local Address
10 54 64
2-7

1111111010 0 Interface identifier
Site-local Address
10 38 16 64
1111111011 0 Subnet Interface identifier

identifier
Link-local addresses are used in a single network link for host numbering. The address
identified by the first ten bits of the prefix is the link-local address. Routers do not
process the packets with link-local addresses at their source end and destination end
because they never forward these packets.
The middle 54 bits of this address are set to zero, its 64-bit interface identifier is in the
same IEEE structure as mentioned in the foregoing paragraphs, and the part of this
address space allows some networks to connect up to 264-1 hosts.
Link-local addresses are used for the single network link and site-local addresses are
used for sites. It means that site-local addresses can be used to transmit data in the
interconnected networks but cannot be directly routed to the global Internet from a
site.
Routers within a site can only forward packets within the site instead of forwarding
them outside of the site. The 10-bit prefix of a site-local address is immediately
followed by a succession of zeros, which is slightly different from that of a link-local
address. The subnet identifier of a site-local address is 16-bit, and its interface
identifier is still the 64-bit IEEE-based address.
Note that the special behavior of site-local addresses has been removed from RFC.
Addresses such as fec0::/10 need to be treated as common unicast addresses.
l Open Systems Interconnection (OSI) Network Service Access Point (NSAP) Address
and Internetwork Packet Exchange (IPX) Address
One of the IPv6 objectives is to unify the whole network world for among IP, IPX, and
OSI networks. To support this interoperatability, IPv6 reserves 1/128 address space
for OSI NSAP address and network IPX address respectively.
At present, the IPX addresses have not been precisely defined. Refer to RFC for
description of the NSAP address allocation.
Multicast Address
The format of the IPv6 multicast address is different from that of the IPv6 unicast address.
Multicast addresses can only be used as destination addresses. No packet uses a
multicast address as the source address. Table 2-5 lists the format of a multicast address.
Table 2-5 Multicast Address Format
8 4 4 112
1111111 Flags Scope Group identifier
2-8

The first byte of the address format is set to full-one, identifying it as a multicast address.
The multicast address occupies the entire 1/256 of the IPv6 address space. The other
parts except the first byte of the multicast address format contain the following three fields:
l Flags field
This field consists of four single bit flags. Currently, only bit-4 is designated to indicate
that whether this address is a well-known multicast address designated by the Internet
numbering institution, or a temporary multicast address used in a specific occasion.
If this flag bit is set to zero, it indicates that this address is a well-known address. If
this flag bit is set to one, it indicates that this address is a temporary address. The
other three flag bits are reserved for future use. The initialization value is 0.
l Scope field
This is a 4-bit field and is used to indicate the range of multicast. That is, whether
a multicast group only includes nodes within the same local network, the same site
or the same institution, or includes nodes that resides anywhere in the IPv6 global
address space. The possible values 4-bits value ranges from 0 to 15. Table 2-6 lists
the corresponding range.
Table 2-6 Multicast Scope Values
Hex Decimal Value
0 0 Reserved
1 1 Node-local range
2 2 Link-local range
3 3 Reserved
4 4 Management-local range
5 5 Site-local range
6 6 Unallocated
7 7 Unallocated
8 8 Institution-local range
9 9 Unallocated
10 A Unallocated
11 B Unallocated
12 C Unallocated
13 D Unallocated
14 E Global range
15 F Reserved
l Group ID field
2-9

The 112-bit multicast ID field identifies a multicast group within a specified range
permanently or temporarily.
Anycast Address
A multicast address can be shared by many nodes in a sense. All the nodes of the
members of a multicast address expect to receive all the packets sent to this address. A
router connecting to five different local Ethernet networks should forward a copy of these
multicast packets to each network respectively (supposing at least one node of each
network subscribers to this multicast address).
Anycast addresses are similar to multicast addresses. Although the two are in the same
case that an anycast address can be shared by multiple nodes, only one node of an anycast
address expects to receive the packet sent to the anycast address.
Anycast is helpful in providing services, especially those requiring no relationship between

client and server, such as, a domain name server and a time server. A domain name
server is nothing but a name server, which provides the same performance whether it is
located closely or remotely.
Similarly, a closely located time server is preferable in terms of accuracy. Therefore, when
a host sends a request to an anycast address to obtain information, it is the nearest server
associated to this anycast address that shall respond.
Anycast addresses are allocated outside of the normal IPv6 unicast address space.
Anycast addresses cannot be distinguished from unicast addresses in their forms, and
each member of an anycast address should be explicitly configured to identify an anycast
address.
2.1.2 Address Format

An IPv4 address consists of four parts separated by dots, that is, four numbers separated
by dots. The following are some legal IPv4 addresses expressed by decimal integer:
0.5.3.1, 127.0.0.1, 201.199.244.101.
An IPv4 address is expressed as a group of four 2-bit hex integers or four 8-bit binary
integers, of which the latter one is seldom used.
The length of an IPv6 address is four times greater than an IPv4 address, and the
complicacy of expression for an IPv6 address is also four times greater than an IPv4
address. An IPv6 address can be basically expressed as X:X:X:X:X:X:X:X, among which
X is 4-bit hex integers (16-bit). Each number contains four bits, each integer contains four
numbers and each address contains eight integers. There are totally 128 bits (4 x 4 x 8 =
128). The following are some legal IPv6 addresses:
CDCD: 910A:2222:5498:8475:1111:3900:2020
1030:0:0:0:C9B4:FF12:48AA:1A2B
2000:0:0:0:0:0:0:1
2-10

All these integers are hex integers and those from A to F represent 10 to 15. Each integer
of an address must be indicated except for the starting zero. This is a relatively standard
way to express an IPv6 address. Apart from this, there are two more ways that are clearer
and easier to use.
Some IPv6 addresses contain a succession of zeros, similar to the second and the third
examples as mentioned above. In this case, the succession of zeros can be represented
by "pacing", as provided in the relevant standard.
That is to say, the address 2000:0:0:0:0:0:0:1 can be expressed as 2000::1, of which the
two colons mean that the address can be extended to a complete 128-bit address. In this
method, only when the 16-bit group is all-zero, can it be substituted by two colons, which
can only be used once in the address.
Table 2-7 lists examples for compressed formats of IPv6 addresses.
Table 2-7 IPv6 Address Compression
Add Type Normal Format Compressed Format
Unicast address 1080:0:0:0:8:800:200C:417A 1080::8:800:200C:417A
Multicast address FF01:0:0:0:0:0:0:101 FF01::101
Loopback address 0:0:0:0:0:0:0:1 ::1
Unspecified address 0:0:0:0:0:0:0:0 ::
In the environment mixed with IPv4 and IPv6, there may be a third way. The least
significant 32-bit in an IPv6 address can be used to express an IPv4 address in a mixed
way: X:X:X:X:X:X:d.d.d.d, among which X represents a 16-bit and d indicates a 8-bit
decimal integer.
For example, the address 0:0:0:0:0:0:10.0.0.1 is a legal IPv4 address. Therefore, this
address is expressed as: 10.0.0.1 by combining the two possible expressions.
An IPv6 address consists of two parts: subnet prefix and interface identifier. An IP node
address is expected to be expressed in a way similar to that of a CIDR address, as an
address carrying an extra value, indicating how many bits of the address is the mask.
An IPv6 node address indicates the length of a prefix by separating the length from the
IPv6 address with a slash.
For example, in the address of
1030:0:0:0:C9B4:FF12:48AA:1A2B/60, the length of the prefix for routing is 60-bits
IPv6 Host Address

An IPv6 host has many IPv6 addresses even if it has only one single interface. An IPv6
host can have the following unicast addresses simultaneously.
l The link-local address of each interface
l The unicast address of each interface, which can be a site-local address or one or
more aggregable global addresses
2-11

l Loopback address (::1) of a loopback interface

In addition, each host must always keep receiving the data from the following multicast
addresses.
l Multicast addresses (FF01::1) of all the nodes within the node-local range
l Multicast addresses (FF02::1) of all the nodes within the link-local range
l Multicast address of the solicited-node (if the solicited-node group is added to an
interface of the host)
l Multicast address of a multicast group (if any multicast group is added to an interface
of the host)
IPv6 Router Address

The following unicast addresses can be allocated to an IPv6 router:
l Link-local address of each interface
l Unicast address of each interface, which can be a site-local address or one or more
aggregable global addresses
l Subnet-router anycast address
l Other anycast addresses (optional)
l Loopback address (::1) of a loopback interface
Similarly, apart from these addresses, a router must always keep listening to the data flow
from the following multicast addresses.
l Multicast addresses (FF01::1) of all the nodes within the node-local range
l Multicast addresses (FF02::1) of all the nodes within the link-local range
l Multicast addresses (FF02::2) of all the routers within the link-local range
l Multicast addresses (FF05::2) of all the routers within the site-local range
l Multicast address of the solicited-node (if the solicited-node group is added to an
interface of the router)
l Multicast address of a multicast group (if any multicast group is added to an interface
of the router)
2.1.3 IPv6 Address Auto Configuration Technology

The state auto configuration employs plug-and-play mode to insert a node into the
IPv6 network and starts it up without any manual interference. IPv6 has two different
mechanisms to shore up the plug-and-play network connection.
State Auto Configuration

l Boot protocol (BOOTP)
l Dynamic Host Configuration Protocol (DHCP)
Both of the two mechanisms allow IP nodes to obtain configuration information from
a special BOOTP server or the DHCP server. These protocols use the state auto
configuration, that is, a server must retain and manage the state information about each
node.
2-12

Stateless Auto Configuration

Apart from state auto configuration, IPv6 also employs a kind of auto configuration service
named stateless auto configuration.
For the stateless auto configuration, the local link must support multicast. The network
interface must be able to send and receive multicast packets. In the stateless auto
configuration process, the relevant nodes must meet the following requirements.
l A node for auto configuration must determine its own link-local address.
l Authenticate this link-local address to make sure that it is unique in the link.
l The node must determine the information to be configured. Such information can be
the IP address of this node, other configuration information, or both of them. In case
an IP address is needed, the node must determine whether to obtain it through the
stateless auto configuration or through the state auto configuration.
The procedure is as follows:
1. In the stateless auto configuration process, the host adds its network adapter MAC
address after the 1111111010 prefix of the link-local address to create a link-local
unicast address.
IEEE has modified the network adapter MAC address from 48-bit to 64-bit. If the
network adapter MAC address used by the host is still 48-bit, the IPv6 network adapter
driver will convert the 48-bit MAC address to the 64-bit MAC address in accordance
with an IEEE formula.
2. The host sends a neighbor discovery request to the address to check whether the
address is unique.
If there is no response to the request, it indicates that the link-local unicast address
configured by the host itself is unique. Otherwise, the host will use an interface ID
randomly created to form a new link-local unicast address.
3. Taking the address as the source address, the host sends a router solicitation in the
multicast way to all the routers within the local link to request configuration information.
Routers respond to it with a router advertisement containing the prefix of an aggregable
global unicast address and other relevant configuration information.
The host automatically uses the global address prefix obtained from routers and its
own interface ID to automatically configure a global address to communicate with other
hosts within the Internet.
2.2 Configuring an IPv6 Address

This procedure describes how to configure an IPv6 address for an interface, which is the
prerequisite for managing and configuring other functions.
Steps
1. Configure IPv6 address.
2-13


mode.
2 ZXR10(config-if-interface-name)#ipv6 enable Enables the IPv6 protocol.
3 ZXR10(config-if-interface-name)#ipv6 address Configures an IPv6 address

<ipv6-address>/<prefix-length> on an interface.
ZXR10(config-if-interface-name)#ipv6 address Configures the IPv6 link local

link-local <X:X::X:X> address of the interface.
<ipv6-address>: address configured for the interface. The address format (<X:X::X:X>)
follows the RFC specifications. IPv6 addresses consist of groups of 16bit
hexadeciaml values separated by colons (:). You can also use a simplified form
supported by RFC.
<prefix-length>: prefix length of the IPv6 address, which is a decimal number (1128)
indicating how many bits from the utmost left of the IPv6 address are the address
prefix.
<X:X::X:X>: link-local address, which must be assigned with the prefix fe80::/64.
2. Configure optional parameters of the IPv6 function.
Command Function
ZXR10(config-if-interface-name)#ipv6 mtu <bytes> Sets the Maximum Transfer Unit

(MTU) of the IPv6 packets to
be transmitted on the interface,
unit: bytes, range: 1280 to 9202,
default: 1500.
ZXR10(config-if-interface-name)#ipv6 dad-attemps Sets the maximum of times

<number> that the interface detects the
address repeatedly, range: 0 to
10, default: 3.
Command Function
ZXR10#show ipv6 interface <interface-name> Displays details about the specified IPv6
interface.
ZXR10#show ipv6 interface brief <interface-name> Displays the brief information about the
specified IPv6 address.
End of Steps
2-14

2.3 IPv6 Address Configuration Example

Configuration Description
The interface gei-1/1 of R1 and the interface gei-2/1 of R2 are directly connected with each
other, see Figure 2-3. It is required that R1 and R2 be able to successfully ping each other.
Figure 2-3 IPv6 Address Configuration Example
Configuration Flow
1. Configure the IPv6 addresses of the interfaces of R1 and R2.
2. Check the configuration results and ensure that R1 and R2 can successfully ping each
other.
Configuration Commands
Configuration on R1:
R1(config)#interface gei-1/1
R1(config-if-gei-1/1)#no shutdown
R1(config-if-gei-1/1)#ipv6 enable
R1(config-if-gei-1/1)#ipv6 address 3ffe:100::1/64
Or:
R1(config-if-gei-1/1)#ipv6 address link-local fe80::1111:2222:3333:4444
R1(config-if-gei-1/1)#exit
R2(config-if-gei-2/1)#ipv6 address 3ffe:100::2/64
Or:
R2(config-if-gei-2/1)#ipv6 address link-local fe80::5555:6666:7777:8888
2-15

Configuration Verification
Verify the configuration results on R1:
R1#show ipv6 interface brief gei-1/1
gei-1/1 [up/up]
fe80::2d1:d1ff:fe3a:7be1
3ffe:100::1/64
R1#ping6 3ffe:100::2
sending 5,100-byte ICMP echoes to 3ffe:100::2,timeout is 2 seconds.
!!!!!
Success rate is 100 percent(5/5), round-trip min/avg/max= 0/0/0 ms.
Verify the configuration results on R2:

R1#show ipv6 interface brief gei-2/1
gei-2/1 [up/up]
fe80::1422:30ff:fec4:e999
3ffe:100::2/64
R2#ping6 3ffe:100::1
sending 5,100-byte ICMP echoes to 3ffe:100::1,timeout is 2 seconds.
!!!!!
Success rate is 100 percent(5/5), round-trip min/avg/max= 0/0/0 ms.
2-16

Chapter 3
NDP Configuration
Table of Contents
NDP Overview............................................................................................................3-1
Configuring NDP ........................................................................................................3-2
NDP Configuration Example.......................................................................................3-6
3.1 NDP Overview

The Neighbor Discovery Protocol (NDP) implements the router discovery function of the
Address Resolution Protocol (ARP) and the Internet Control Message Protocol (ICMP)
as well as all functions of the redirection protocol in IPv4. It also provides a neighbor
unreachability detection mechanism.
When one IPv6 node appears on the network, the other IPv6 nodes on the link that directly
connects with the node can discover the node through the neighbor discovery protocol and
can further obtain its link layer address. IPv6 nodes can also search for routers through
the neighbor discovery protocol and maintain the reachability information about the active
neighboring nodes on the path. The neighbor discovery protocol solves the interactions
between nodes on the same link.
The IPv6 NDP provides a group of solutions for solving communication-related problems.
l The NDP supports address resolution, that is, it can resolve the IPv6 address of one
IPv6 node interface into the corresponding link layer address.
l The NDP supports router discovery. A host can detect the existence of routers through
the NDP and determine the IDs of the routers willing to forward packets.
l The NDP supports prefix discovery. A router can distribute prefix information through
the NDP to the other connected links.
l The NDP also supports neighbor unreachability detection. A node can determine the
bidirectional reachability of peer communication entities through the NDP.
l The NDP also supports Duplicate Address Detection (DAD). The addresses
configured on a node cannot become valid addresses until they pass DAD.
All these functions of the NDP are mostly implemented by NDP packets loaded inside
ICMPv6 packets. For this reason, the NDP defines five types of ICMPv6 packets: Router
Solicitation (RS) packets, Router Advertisement (RA) packets, Neighbor Solicitation (NS)
packets, Neighbor Advertisement (NA) packets, and redirection packets.
A router periodically sends RA packets, and may also use them as a response to the RS
packets it has received from hosts. Each RA packet may also contain prefix information,
link configuration information and IPv6 protocol parameters. It indicates the existence of
routers, and routers can forward the packet. The RA packet carries the information about
3-1

the routers. Such information helps a host to determine where the packet should be sent.
The host discovers available routers through the RA packet and constructs a list of all the
discovered routers as the default router list.
A host may send an RS packet to inquire router configuration information and router-related
information. A time interval for consecutively sending RA packets has been set on each
router. The interval ranges from several seconds to several minutes. In order to avoid
long waiting time before the configuration information is obtained and the communication
starts, the host may integrate the sending of RS packets as a part of its startup process.
A node can send an NS packet to interpret the link layer address of another node to verify
the reachability of that node and the address uniqueness of a specific link.
A node can send an NA packet as the response to an NS packet. It also sends unsolicited
NA packets to notify its own link layer address changes to other nodes.
When a new address is generated on a node, the node needs to send a neighbor request
to other nodes on the link to enquire whether the address has been used. If the address
has been used, the node using the address responds with an NA packet. If the node
where the address is generated does not receive any response after multiple detections
(the number is configurable), the address becomes valid.
3.2 Configuring NDP

This procedure describes how to configure the NDP function so that the nodes on a directly
connected link can resolve addresses, discover neighbors, maintain nodes, and perform
neighbor unreachability detection.
Steps
1. Enters interface configuration mode.
Command Function
ZXR10(config)#interface <interface-name> Enters interface configuration

mode.
2. Configure optional parameters for NDP functions.
Command Function
ZXR10(config-if-interface-name)#ipv6 nd Sets the managed-config-flag

managed-config-flag field of the RA packets sent on
the interface, that is, sets the
value of M bit in the packets to
1. Default: 0.
3-2

Chapter 3 NDP Configuration
Command Function
ZXR10(config-if-interface-name)#ipv6 nd Sets the other-config-flag field

other-config-flag of the RA packets sent on the
interface, that is, sets the value
of 0 bit in the packets to 1.
Default: 0.
ZXR10(config-if-interface-name)#ipv6 nd Sets the prefix option of the RA

prefix <ipv6-prefix>/<prefix-length> [{<valid-lifetime> packets sent on the interface.
<preferred-lifetime>} | off-link | no-autoconfig]
ZXR10(config-if-interface-name)#ipv6 nd ra-interval Specifies the interval for sending

<seconds> RA packets on the interface in
seconds. The value range is
31800. The default value is 600
seconds.
ZXR10(config-if-interface-name)#ipv6 nd ra-lifetime Specifies the value of the

<seconds> ra-lifetime field in the RA packets
sent on the interface in seconds,
range: 09000, default: 1800.
ZXR10(config-if-interface-name)#ipv6 nd ra-linkmtu Configures the mtu field value in

<ra-advlinkmtu> RA packets, unit: byte, range:
01500, default: 1500.
ZXR10(config-if-interface-name)#ipv6 nd reachable-time Specifies the time within

< milliseconds> which the remote neighbor
is considered as reachable
after the reachability of the
remote neighbor is confirmed in
milliseconds, default: 30000.
ZXR10(config-if-interface-name)#ipv6 nd Specifies the value of the

retransmit-time <milliseconds> retransmit-time field in the RA
packets in milliseconds, range:
1000360000, default: 1000.
ZXR10(config-if-interface-name)#ipv6 nd Configures the router enables

suppress-ra<disable> sending router advertisement
packets, by default, no RA
packets are sent.
ZXR10(config-if-interface-name)#ipv6 nd Configures the counter limit

ra-curhoplimit<hoplimit> of router advertisement hops,
3-3

Command Function
ZXR10(config-if-interface-name)#ipv6 nd Configures the staled-time (in

staled-time<minutes> minutes) of ND entities in the
neighbor cache table, range:
114400, default: 1440.
ZXR10(config-if-interface-name)#ipv6 nd stale-switch Configures reachability detection

before staled-time expires,
default: disabled.
ZXR10(config-if-interface-name)#ipv6 dad-attemts Sets the number of times that the

<numbers> interface performs DAD for an
address. Range: 010, default:
3.
ZXR10(config-if-interface-name)#ipv6 nd redirect Enables the function of sending

ND redirection packets, default:
disabled.
ZXR10(config-if-interface-name)#ipv6 nd proxy Enables the ND proxy function

between interfaces, default:
disabled.
ZXR10(config-if-interface-name)#ipv6 nd Enables the ND proxy function

inter-vlan-proxy between different VLANs of
the same interface, default:
disabled.
ZXR10(config-if-interface-name)#ipv6 nd Enables the ND proxy function

inner-vlan-proxy in the same VLAN of the same
interface, default: disabled.
Descriptions of the parameters in Step 2:

<valid-lifetime>: indicates the valid lifetime (in seconds) of the prefix in seconds, range:
04294967295, default: 2592000.
<preferred-lifetime>: indicates the preferred lifetime (in seconds) in seconds, range:

04294967295, default: 604800.
no-autoconfig: indicates that the hosts on the link cannot use the prefix for IPv6 address
auto configuration.
off-link: indicates that the L bit (Online flag) of the prefix is not set, default: 1. If this
flag is set to 1, it indicates that the prefix can be used to determine whether addresses
are online, that is, all the addresses belonging to this prefix are online if this flag is set
whereas some addresses may be online but the other addresses are offline if this flag
is not set.
<ipv6-prefix>: network prefix in an RA packet.
<prefix-length>: prefix length.
3-4

<route-lifetime>: route lifetime, unit: second, range: 04294967295, default:

4294967295 second.
<route-preference>: route priority, range: 03, default: 0.
3. Add a static entry to the neighbor buffer table.
Command Function
ZXR10(config-if-interface-name)#nd6 add Adds a static entry to the

<ipv6-address><hardware-address> neighbor cache table.
ZXR10(config-if-supervlan)#nd6 add <ipv6-address><h Adds a static entry in the

ardware-address><interface> neighbor cache table on the
supervlan interface.
<ipv6-address>: destination address in the neighbor cache table.
<hardware-address>: hardware address of the destination address in the neighbor

cache table, consisting of three groups of 16-bit values, separated by ".".
<interface>: specifies the subvlan interface. This value is visible only in supervlan
interface mode and must be configured.
Command Function
ZXR10#show nd6 cache[<interface-name>] Displays information from the IPv6 neighbor cache
table. If an interface is added, only the neighbor
cache entries of this interface are displayed.
The display results show not only the entries
generated by the ND protocol for the routes to
neighbors but also static neighbor cache entries.
5. Maintain NDP.
Command Function
ZXR10(config-if-interface-name)#nd6 delete Deletes a static entry from the

<ipv6-address> neighbor cache table.
ZXR10#clear nd-cache[<interface-name>] Clears all dynamic entries from

the IPv6 neighbor cache table if
no interface name is specified.
Clear the dynamic entries of the
interface from the IPv6 neighbor
cache table if an interface name
is specified. This command can
be used only in privileged mode.
3-5

Command Function
ZXR10#debug ipv6 nd6 Turns on all the debugging

function switches related to the
ND protocol.
ZXR10#show debug nd6 Displays the ND6 protocol

debugging switches that have
already been turned on.
End of Steps
3.3 NDP Configuration Example

This example describes how to configure static entries in the NDP neighbor cache table
of the interface gei-1/1 on a router.
Configuration Flow
1. Enter the interface configuration mode, and add a static entry to the neighbor cache
table.
2. Show the content of the neighbor cache table, and check whether the static entry has
been successfully added.
Configuration on the router:
ZXR10(config)#interface gei-1/1
ZXR10(config-if-gei-1/1)#no shutdown
ZXR10(config-if-gei-1/1)#nd6 add 780::1 0000.0a00.1345
Assume that the echo information on the router before configuration is as follows:
ZXR10#show nd6 cache
Total Cache Number Is:1
Only Current Valid Items Are Shown Below:
Address Link-Address Age Status Interface
3ffe:100::2 0023.e422.1134 23h56m2s Stale gei-1/1
The configuration on the router is verified as follows:

ZXR10#show nd6 cache
Total Cache Number Is:12
Only Current Valid Items Are Shown Below:
Address Link-Address Age Status Interface
3-6

780::1 0000.0a00.1345 static Reachable gei-1/1

3ffe:100::2 0023.e422.1134 23h55m6s Stale gei-1/1
The result above indicates that a static entry has been successfully added to the NDP
neighbor cache table.
3-7

3-8

Chapter 4
IPv6 Static Route
Configuration
Table of Contents
IPv6 Static Route Overview ........................................................................................4-1
Configuring a Static IPv6 Route..................................................................................4-1
Configuration Instances of IPv6 Static Route..............................................................4-3
4.1 IPv6 Static Route Overview

Static routes refer to the routes that the network administrator creates by using
configuration commands in the routing table. Static routing is different from dynamic
routing that creates a routing table according to a routing algorithm.
When dynamic routing is applied, sometimes it is necessary to send the routes of the
entire Internet to a router and then the router can hardly tolerate such a huge load. In that
case, static routing can be applied to solve the problem. With static routing, only a few
configurations are required to eliminate the use of dynamic routes.
In a routing environment involving multiple routers and multiple paths, however, it is rather
complex to configure static routes.
The static unicast routing table is configured by the network administrator according to
his/her routing requirements after he/she gets familiar with the entire network topology.
Therefore, the network administrator can exactly control routing behaviors in the network.
When the network topology changes, however, the network administrator needs to
reconfigure the static routing table.
Unlike dynamic routing protocols, static routing does not require the setting of protocol
data on the related interfaces but requires only a validity check of the user-configured
static routing parameters such as destination address, mask length, next hop and egress
interface. The validity of each configured static route, however, still depends on the status
of the egress interface.
4.2 Configuring a Static IPv6 Route

This procedure describes how to configure a static IPv6 route. The network administrator
configures static routes manually based on the route requirements so that the route
behaviors in the network can be precisely controlled.
4-1

Context
The following issues require attention when configuring static routes:
l For a point-to-point interface, it is only necessary to specify the out-interface for the
static route, because specifying an out-interface also specifies the next hop implicitly.
It is considered that the address on the peer interface connected to the local interface
directly is the next hop address of the route.
l For an Ethernet interface, it is not allowed to specify an Ethernet interface as an
out-interface. In applications, when it is necessary to specify an Ethernet interface
as an out-interface, it is necessary to specify the out-interface first and then specify
the next hop address.
l A static route with an out-interface as a null interface can be applied as a black route.
Traffic matching this route is dropped directly.
Steps
1. Configure IPv6 static route.
Command Function
ZXR10(config)#ipv6 route [vrf {mng |<vrf-name>}]<ipv6-addre Configures an IPv6 static route.

ss-mask>{<ipv6-address>|<interface-name>[<ipv6-address>]}[<di
stance>][metric <cost>][bfd enable][name <static-description>]
ZXR10(config)#ipv6 route [vrf {mng |<vrf-name>}]<ipv6-ad Configures the specified next

dress-mask>{<ipv6-address>}[<distance>][metric <cost>][bfd hop of the IPv6 static route.
enable][name <static-description>] <ipv6-address> can be a directly
connected address or an
indirectly connected address.
ZXR10(config)#ipv6 route [vrf {mng |<vrf-name>}]<ipv6-addre Configures a static IPv6 static

ss-mask>{<interface-name>[<ipv6-address>]}[<distance>][metric route with the specified outgoing
<cost>][bfd enable][name <static-description>] interface or the specified
outgoing interface and next hop.
ZXR10(config)#ipv6 route-static [vrf <vrf-name>] fast-reroute Enables the FRR route

calculation function for the
static IPv6 route.
ZXR10(config)#ipv6 route nexthop source <interface-name> Configures the outgoing interface

of the specified BFD source end
next hop for the static IPv6 route.
Only loopback interfaces are
supported.
vrf <vrf-name>: configures static route of the designated Virtual Route Forwarding
Table (VRF), 1 to 32 characters in length. The mng port is used as a special VRF.
<distance>: the administration distance, range: 1 to 255.
metric<cost>, the route metric, range: 1 to 255.
4-2

Chapter 4 IPv6 Static Route Configuration
bfd enable: enables the static BFD function.
name <static-description>]: description of the static route, containing 164 characters.

The ipv6 route command is described as follows:
l <distance> is equivalent to the priority in a routing protocol. The smaller the

value is, the higher the priority is. By default, static routes take precedence over
dynamic routes. The default value is 1. You can also set dynamic routes to have
a higher priority.
l bfd enable is used to enable the BFD detection configured on the static route.
To cancel the BFD detection, delete the static route, or configure a same route
without the BFD option.
The ipv6 route nexthop source command is described as follows:
l This command is used in concert with static route configuration commands.

l If the command is bound with an interface without an IP address, no BFD session
is created. The static route is informed to create a BFD session only when the
IPv6 address of the interface is updated.
Command Function
ZXR10(config)#show running-config ipv6-static Displays the static routes configured in

the system database.
ZXR10(config)#show ipv6 protocol routing static Displays the static routes in the routing
table and the validity of these routes.
ZXR10(config)#show ipv6 forwarding route static Displays information about static routes
in the forwarding table.
End of Steps
4.3 Configuration Instances of IPv6 Static Route

4.3.1 Example: Configuring a Direct Static IPv6 Route (Direct Next
Hop)
As shown in Figure 4-1, R1 and R2 are directly connected with each other and belong to
the network segment 2005::/64. To enable R1 to successfully ping the network segment
2003::/64 of R2, a static route to the network segment 2003::/64 can be added on R1, with
the next hop being the IPv6 address of the R2 interface that directly connects R1 with R2.
4-3

Figure 4-1 Topology Diagram for Configuring a Static IPv6 Route (Direct Next Hop)
Configuration Flow
1. Configure the IPv6 address of the network segment 2005::/64 for the direct connection
between R1 and R2.
2. Configure the IPv6 address of another different network segment 2003::/64 on the
direct connection interface of R2.
3. Add a static route pointing to the network segment 2003::/64 on R1 so that R1 can
successfully ping the network segment 2003::/64 of R2.
The configuration on R1 is as follows:
R1(config-if-gei-2/1)#ipv6 address 2005::1/64
R1(config)#ipv6 route 2003::/64 2005::2 /*Configure the static route*/
R1(config)#exit

On R1, check whether the address has been successfully configured, whether the interface
is in up status, and whether the static route has been successfully added, and then execute
the "ping6 2003::2 command to check whether the ping operation is successful.
R1(config)#show running-config-interface gei-2/1
! <Interface>
interface gei-2/1
4-4

ipv6 enable
ipv6 address 2005::1/64
no shutdown
!
$! </Interface>
R1(config)#show ipv6 interface gei-2/1
Interface gei-2/1 is up, line protocol is up

IPv6 is enabled, Hardware is Gigabit Ethernet
HWaddr: 0020.231d.0e0e
index 29
Bandwidth 1000000 Kbits
IPv6 MTU is 1500 bytes
inet6 fe80::220:23ff:fe1d:e0e/64
inet6 2005::1/64
DAD attemps number:3
ND reachable-time is 30000 milliseconds
R1(config)#show running-config ipv6-static

!<ipv6-static>
ipv6 route 2003::/64 2005::2
!</ipv6-static>
R1#show ipv6 forwarding route static
IPv6 Routing Table:
Headers: Dest: Destination, Gw: Gateway, Pri: Priority;
Codes : K: kernel, I1: isis-l1, SFN: sf-nat64, R: ripng, AF: aftr, B: bgp,
D: direct, I2: isis-l2, SLN: sl-nat64, O: ospfv3, D6: dhcp, P: ppp,
S: static, N: nd, V: vrrp, A: address, M: multicast, UI: user-ipaddr;
Dest Owner Metric
Interface Pri Gw
2003::/64 S 0
gei-2/1 1 2005::2
4.3.2 Example: Configuring a Static IPv6 Route (Indirect Next Hop)

As shown in Figure 4-2, R1 and R3 are directly connected to R2 separately. If R1 needs
to transmit packets to remote network segment 2003::/64, it must transmit packets to R2
having IPv6 address 2006::2 first. If R2 needs to transmit packets to remote network
segment 2003::/64, it must transmit packets to R3 having IPv6 address 2005::2 first.
4-5

Figure 4-2 Topology Diagram for Configuring a Static IPv6 Route (Indirect Next Hop)
Configuration Flow
1. Configure a static route on R1, with the destination network segment 2003::/64 and
next hop 2005::2.
2. Configure a static route on R1, with the destination network segment 2005::/64 and
next hop 2006::2.
Configuration on R1 (IPv6 address configurations on R1, R2, and R3 are omitted)
R1(config)#ipv6 route 2003::/64 2005::2

/*Configure the static route (indirect next hop).*/
/*Configure the static route (direct next hop).*/
IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2003::/64 S 0
gei-2/1 1 2005::2
2005::/64 S 0
gei-2/1 1 2006::2
4.3.3 Example: Configuring a Default IPv6 Route

The default route is a special kind of static route. When all routes in the routing table fail
to be selected, the default route, which greatly reduces the handling load of the router, is
used. Figure 4-3 shows the topology structure of IPv6 default routes.
4-6

Figure 4-3 Default IPv6 Route Configuration Example
Configuration Flow
1. Establish the networking structure, and configure the IPv6 address for the interface,
as shown in Figure 4-3.
2. Configure the default route, and specify the IPv6 address for gei-4/1 on R2.
R1(config)#ipv6 route ::/0 2005::2
/*The IPv6 address configuration on R2 is omitted.*/
R1(config)#show ipv6 forwarding route
IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
::/0 S 0
gei-2/1 1 2005::2
4.3.4 Example: Configuring FRR for Static IPv6 Route in a Public

Network
FRR provides backup protection for important nodes or links in the network when they
are invalid to implement fast rerouting, thus minimizing the impact on traffic and restoring
traffic quickly. As shown in Figure 4-4, FRR function is configured for static IPv6 routes in
a public network.
4-7

Figure 4-4 Networking Diagram for Configuring FRR for Static IPv6 Route in a Public
Network
Configuration Flow
1. On R1, enable the backup route calculation function for static IPv6 routes in the public
network.
2. Configure a static IPv6 route as the active route.
3. Configure a static IPv6 route as the standby route. Its destination address and mask
must be the same with those of the active route. The priority or metric of the standby
route must be lower than that of the active route. The active and standby routes must
have different outgoing interfaces.
R1(config)#ipv6 route-static fast-reroute /*Enable the FRR function.*/
R1(config)#ipv6 route 1234::1/128 500::2
R1(config)#ipv6 route 1234::1/128 300::2 10
4-8

R3(config)# ipv6 route 1234::1/128 400::3
R2(config)#interface loopback5
R2(config-if-loopback5)#ipv6 enable
R2(config-if-loopback5)#ipv6 address 1234::1/128
R2(config-if-loopback5)#exit
The FRR configuration on R1 is verified as follows:
R1(config)#show ipv6 forwarding route 1234::1

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1234::1/128 S 0
gei-5/5 1 500::2
R1(config)#show ipv6 forwarding backup route 1234::1

IPv6 Routing Table:
Dest Owner Metric
Interface Pri M/S Sta Gw
1234::1/128 S 0
gei-5/5 1 M I 500::2
1234::1/128 S 0
gei-5/3 10 S U 300::2
4-9

4.3.5 Example: Configuring FRR for Static IPv6 Route in a Private

Network
FRR provides backup protection for important nodes or links in the network when they are
invalid to implement fast rerouting, thus minimizing the impact on traffic and restoring traffic
quickly. As shown in Figure 4-5, the FRR function is configured for static IPv6 routes in a
private network.
Figure 4-5 Networking Diagram for Configuring FRR for Static IPv6 Route in a Private
Network
Configuration Flow
1. Configure VRF, and enable the v6 address family of VRF.
2. On R1, enable the backup route calculation function for static IPv6 routes in a private
network.
3. Configure a static IPv6 route as the active route in the private network.
4. Configure a static IPv6 route as the standby route. Its VRF, destination address, and
mask must be the same with those of the active route. The priority or metric of the
standby route must be lower than that of the active route. The active and standby
routes must have different outgoing interfaces.
R1(config)#ip vrf vpn

R1(config-vrf-vpn)#rd 1:3
R1(config-vrf-vpn)#address-family ipv6
R1(config-vrf-vpn-af-ipv6)#route-target 1:1
R1(config-vrf-vpn-af-ipv6)#exit
R1(config-vrf-vpn)#exit
R1(config-if-gei-1/3)#ip vrf forwarding vpn
4-10

R1(config-if-gei-5/1)#ip vrf forwarding vpn

R1(config)#ipv6 route-static vrf vpn fast-reroute /*Enable the FRR function.*/
R1(config)#ipv6 route vrf vpn 1234::1/128 500::2
R1(config)#ipv6 route vrf vpn 1234::1/128 300::2 10
The configuration on R1 is verified as follows:
R1(config)#show ipv6 forwarding route vrf vpn 1234::1

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1234::1/128 S 0
gei-5/1 1 500::2
R1(config)#show ipv6 forwarding backup route vrf vpn 1234::1

IPv6 Routing Table:
Dest Owner Metric
4-11

Interface Pri M/S Sta Gw

1234::1/128 S 0
gei-5/5 1 M I 500::2
1234::1/128 S 0
gei-5/3 10 S U 300::2
4.3.6 Example: Configuring Load Sharing from Static IPv6 Routes

Load sharing enables the traffic beyond the bandwidth of a single interface to be allocated
to multiple links evenly, thus load balancing on links is implemented. As shown in Figure
4-6, load balancing is implemented through load sharing between static IPv6 routes.
Figure 4-6 Networking Diagram of Load Sharing between Static Routes
Configuration Flow
1. Configure interface addresses. Configure IPv6 addresses on the directly connected
interfaces on R1 and R2, and loopback interface address on R2.
2. Configure two static IPv6 routes on R1 to the peer loopback interface address.
Configure the addresses of the peer end interfaces that are connected directly as the
next hop addresses of the two routes. Two static IPv6 routes must have the same
distance value and metric value.
3. The default load sharing mode is the per-flow load sharing, and it can be modified to
the per-packet load sharing mode.
R1(config-if-gei-1/1)#ip load-sharing per-packet
/*Selecting the per-packet load sharing mode*/
R1(config-if-gei-1/2)# ip load-sharing per-packet
4-12

/*Selecting the per-packet load sharing mode*/

Run the show ipv6 forwarding route command to display the route forwarding table on R1:
R1(config)#show ipv6 forwarding route 1234::1

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1234::1/128 S 0
gei-1/1 1 300::2
1234::1/128 S 0
gei-1/2 1 500::2
The above result indicates that there are two next hops to destination 1234::1/128, 300::2
and 500::2 respectively. Outgoing interfaces are gei-1/1 and gei-1/2. Load sharing is
implemented.
4-13

4.3.7 Example: Configuring the Next Hop Address of the BFD

Source Side of a Static IPv6 Route
The next hop of the source end must be specified when a multi-hop BFD session of a
static IPv6 route is created. This function is only available for the loopback interface. The
first non-link-local address on the loopback interface is selected as the local side address
of the BFD session. The topology shown in Figure 4-7 is used as an example. The first
non-link-local address on the loopback interface is selected as the local address of the
BFD session configured on R4.
Figure 4-7 Networking Diagram of the BFD Source-End Next-Hop of IPv6 Static Route
Configuration Flow
1. On R4, configure the address of the interface directly connected to R1, address of the
interface directly connected to R3, loopback interface address, and a static IPv6 route
to the loopback interface address on R2. Enable the BFD function of the static IPv6
route, and configure the next hop of the BFD source side of the static IPv6 route.
interface directly connected to R2, and a static IPv6 route to the loopback address on
R2.
interface directly connected to R2, and a static IPv6 route to the loopback address on
R2.
interface directly connected to R3, loopback interface address, a static IPv6 route to
the loopback address on R4. Enable the BFD function of the static IPv6 route, and
configure the next hop of the BFD source side of the static IPv6 route.
4-14

R4(config)#ipv6 route 1234::1/128 123::1 bfd enable
R4(config)#ipv6 route nexthop source loopback1
4-15

R2(config)#ipv6 route 1234::1/128 1002::1 bfd enable
R2(config)#ipv6 route nexthop source loopback1
Run the show bfd neighbors ip brief command to display BFD session information on R2:
R2(config)#show bfd neighbors ip brief

LocalAddr PeerAddr LD RD Hold State Interface
1002:0:0:0:0:0:0:1 123:0:0:0:0:0:0:1 2051 2049 150 UP ---
The above result indicates that the multi-hop BFD session between R2 and R4 was created
successfully. The peer end address of the BFD session on R2 is the configured next
hop address, and the local address is the loopback1 address of the source-end interface
specified on the local router.
4-16

Chapter 5
RIPng Configuration
Table of Contents
RIPng Overview .........................................................................................................5-1
Configuring RIPng ......................................................................................................5-3
RIPng Configuration Instances ...................................................................................5-5
5.1 RIPng Overview

RIPng Introduction
The Routing Information Protocol (RIP) is widely applied as a mature routing standard on
the Internet, especially on some small-scale and medium-scale networks. Considering
this situation and the compatibility between RIP and IPv6, the Internet Engineering Task
Force (IETF) altered the existing technology and set an RIP standard under IPv6, that is,
RIP next generation (RIPng).
RIPng is a User Datagram Protocol (UDP)-based protocol using port 521 to transmit and
receive data packets. In general, RIPng packets are classified into two categories: routing
information packets and request packets.
RIPng and RIP

RIPng is not intended to create a completely new protocol but to make necessary alteration
to the RIP to enable it to adapt to the routing requirements under IPv6. Therefore, RIPng
has the same working principles as the RIP, except for changes in the address and packet
formats.
l Address length
RIPv1 and RIPv2 are IPv4-based. The address field consists of only 32 bits. In
contrast, RIPng is IPv6-based and all its addresses comprise 128 bits.
l Subnet mask and prefix length
RIPv1 is designed for use in subnet-free networks and thus does not involve
the subnet mask concept. For this reason, RIPv1 cannot be used to propagate
variable-length subnet addresses or CIDR classless addresses. The support for
subnet routing is added to RIPv2, so it can use subnet masks to distinguish between
network routes and subnet routes.
IPv6 address prefixes have express meanings. Therefore, RIPng no longer involves
the subnet mask concept but uses the prefix length instead. Similarly, due to the use
5-1

of IPv6 addresses, it is unnecessary for RIPng to distinguish among network routes,

subnet routes and host routes.
l Protocol applicable scope
The application scope of RIPv1 and RIPv2 is not limited to the Transfer Control
Protocol/Internet Protocol (TCP/IP) protocol suite but also includes other network
protocol suites. Therefore, the routing entries of a packet include the network
protocol suite field. However, it is seldom used for other non-IP networks in practice.
Therefore, support for this function is removed from RIPng.
l Next hop
There is no information about next hop in RIPv1. The router at the receiving end takes
the source address of a packet as the next hop for the route to the destination network.
RIPv2 contains explicit information about the next hop, thus facilitating selection of the
optimum route and avoiding routing loops and slow convergence.
Different from RIPv1 and RIPv2, the next hop field in RIPng exists as a separate RTE
to avoid overlong Routing table Entry (RTE) and to improve the efficiency of routing
information transmission.
l Packet length
In both RIPv1 and RIPv2, the packet length is limited and a packet can carry at most
25 RTEs.
RIPng has no limit on the length of a packet and the number of RTEs. The length of a
packet depends on the MTU of a medium. This packet length processing mechanism
of RIPng has improved the transmission efficiency of routing information on the
network.
l Security consideration
RIPv1 packets do not contain authentication information and thus RIPv1 is not secure.
Any host sending packets via UDP port 520 may be regarded by neighboring hosts
as a router and thus router spoofing may easily take place. RIPv2 is designed to
contain authentication packets to enhance security. Although routers that exchange
routes with each other cannot receive route information from each other before
authentication, RIPv2 does not have adequate security.
IPv6 contains perfect security policies, so there is no need to design separate security
authentication packets for RIPng any more but to use IPv6 security policies.
l Packet transmission mode
RIPv1 sends routing information through broadcast. In this way, both routers and all
the hosts within the same Local Area Network (LAN) can receive packets, which is
unnecessary and insecure.
However, both RIPv2 and RIPng can send packets either through broadcast or
through multicast. In this way, packets can be sent through multicast in networks that
support multicast, thus greatly reducing the volume of routing information transmitted
in networks.
5-2

Chapter 5 RIPng Configuration
5.2 Configuring RIPng

This procedure describes how to configure the attributes and functions of RIPng routes,
including protocol parameters, summarized routes, and redistribution of protocol routes.
Steps
1. Enter RIPng configuration mode.
Command Function
ZXR10(config)#ipv6 router rip Enters RIPng configuration

mode.
2. Configure optional parameters of the RIPng protocol.
Command Function
ZXR10(config-ripng)#timers basic <update><timeout><gar Configures the timers of RIPng.

bage>
ZXR10(config-ripng)#default-metric <metric> Sets the default metric of routes.
ZXR10(config-ripng)#port <1-65535> Specifies the port for listening to

multicast packets, default: 521.
ZXR10(config-ripng)#offset-list <access-list-number>{in | Configures the offset list of

out}<offset> the RIPng, offset metric value,
range: 0 to 16.
<update>: specifies the periodic packet sending interval (in seconds), range: 5 to
65535, default: 30.
<timeout>: specifies the time (in seconds) for the route to become invalid, range: 5 to
65535, default: 180.
<garbage>: specifies the time period (in seconds) from the time when the route
becomes invalid to the time when the route is deleted, range: 5 to 65535, default:
120.
in | out: specifies the route as a receiving/transmitting route.
3. Configures the summarized RIPng routes and the redistribution of protocol routes.
Command Function
ZXR10(config-ripng)#summary-prefix X:X::X:X/<0~128> Configures the summarized

routes of the RIPng.
ZXR10(config-ripng)#redistribute <protocol>[metric Configures the redistribution of

<metric-value>][route-map <map-tag>] protocol routes.
<protocol>: specifies the name of the protocol whose routes are redistributed.
<metric-value>: specifies the metric for the redistributed routes, range: 1 to 16.
5-3

<map-tag>: specifies the route map used for protocol route redistribution.
4. Enable the RIPng protocol function for an interface.
1 ZXR10(config-ripng)#interface <interface-name> Enters RIPng interface

configuration mode.
2 ZXR10(config-ripng-if-interface-name)#ipv6 rip Enables RIPng on an

enable interface.
5. Configure the optional parameters under the RIPng interface.
Command Function
ZXR10(config-ripng-if-interface-name)#ipv6 rip Enables split horizon on the

split-horizon interface, default: Enable.
ZXR10(config-ripng-if-interface-name)#ipv6 rip Enables poison reverse on the

poison-reverse interface, default: Enable.
ZXR10(config-ripng-if-interface-name)#ipv6 rip Configures the active interface

interface active so that the interface only sends
packets but does not receive
packets.
To cancel the configuration and
restore normal packet sending
and receiving, run the no form of
the command.
ZXR10(config-ripng-if-interface-name)#ipv6 rip Configures the passive interface

interface passive so that the interface only
receives packets but does not
send packets.
To cancel the configuration and
restore normal packet sending
and receiving, run the no form of
the command.
ZXR10(config-ripng-if-interface-name)#ipv6 rip Configures the neighbor address

neighbor <X:X::X:X> of the RIPng so that unicast
packets are sent to this neighbor
only.
ZXR10(config-ripng-if-interface-name)#ipv6 rip Originates the default route of

originate-default-route [only] the RIPng on the interface.
5-4

Command Function
ZXR10(config)#show ipv6 rip [vrf <vrf-name>] Displays the content of the RIPng
protocol.
ZXR10(config)#show ipv6 rip database [{X:X::X:X/<0~128 Displays the RIP route database
>|<X:X::X:X>}][vrf <vrf-name>] information.
ZXR10(config)#show ipv6 rip interface [vrf Displays the interfaces on which

<vrf-name>]<interface-name> RIPng is enabled.
7. Maintain RIPng routers.
Command Function
ZXR10(config)#clear ipv6 rip route [vrf <vrf-name Deletes the routes received by
>]{<X:X::X:X>/<0~128>| all} RIPng.
Users can delete all the received
routes or a certain route only.
End of Steps
5.3 RIPng Configuration Instances

5.3.1 RIPng Basic Configuration Example
As shown in Figure 5-1, the RIPng runs on R1 and R2 to notify the RIPng route of these
two routers. The following use a loopback address and a redistribution of direct routes as
an example to illustrate the configuration.
Figure 5-1 Topology of RIPng Basic Configuration Example
Configuration Flow
1. Enable the IPv6 protocol on the interfaces and configure IPv6 addresses.
2. Configure the RIPng protocol.
3. Enable the RIPng-related configurations on the interfaces.
5-5

4. Configure the redistribution commands if it is necessary to redistribute other routes.

5. Check the configuration result, and confirm whether the neighbor relationship is
established correctly between two routers, and whether these two routers can learn
the route notified by the peer end.
R1(config)#ipv6 router rip

R1(config-ripng)#interface gei-3/6
R1(config-ripng-if-gei-3/6)#ipv6 rip enable
R1(config-ripng-if-gei-3/6)#exit
R1(config-ripng)#interface loopback5
R1(config-ripng-if-loopback5)#ipv6 rip enable
R1(config-ripng-if-loopback5)#exit
R1(config-ripng)#redistribute connected
R1(config-ripng)#exit
5-6


R2(config-ripng)#interface loopback5
R2(config-ripng-if-loopback5)#ipv6 rip enable
R2(config-ripng-if-loopback5)#exit
R2(config-ripng)#redistribute connected /*Configure the redistribution*/
Execute the show running-config ripng command on R1 and R2 to check the RIPng
configuration information, and execute the show ipv6 forwarding route ripng command to
check the route information.
Check the route information on R1:
R1#show running-config ripng
! <RIPNG>
ipv6 router rip
redistribute connected
interface gei-3/6
ipv6 rip enable
$
interface loopback5
ipv6 rip enable
$
$
! </RIPNG>
R1#show ipv6 rip

RIPng protocol, port 521, multicast-group FF02::9
administrative distance is 120
default metric is 1
updates every 30 seconds, expire after 180 seconds
garbage collect after 120 seconds
The number of ripng routes:

connect ripng route 3
aggregate ripng route 0
ripng route 2
Redistribution:
5-7

R1#show ipv6 rip database

2255::/64
nexthop: ::, via: unknown
metric: 16, tag: 0
2355::/64
nexthop: fe80::2d0:d0ff:feaf:cc10, via: gei-3/6
metric: 2, tag: 0
2356::/64
metric: 2, tag: 0
2357::/64
metric: 2, tag: 0
2358::/64
metric: 2, tag: 0
2310::/64
metric: 16, tag: 0
3036::/64
nexthop: ::, via: gei-3/6
metric: 1, tag: 0
3550::/64
metric: 2, tag: 0
3555::/64
nexthop: ::, via: loopback5
metric: 1, tag: 0
3611::/64
metric: 1, tag: 0
R1#show ipv6 forwarding route ripng

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2352::/64 R 2
gei-3/6 120 fe80:12::2d0:d0ff:feaf:cc10
3550::/64 R 2
5-8

R1#ping6 2352::52
sending 5,100-byte ICMP echoes to 2352::52,timeout is 2 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 0/0/0 ms.
Check the route information on R2:

! <RIPNG>
ipv6 router rip
interface gei-1/3
ipv6 rip enable
$
interface loopback5
ipv6 rip enable
! </RIPNG>
R2#show ipv6 rip

RIPng protocol, port 521, multicast-group FF02::9
administrative distance is 120
default metric is 1
updates every 30 seconds, expire after 180 seconds
garbage collect after 120 seconds
The number of ripng routes:

connect ripng route 3
aggregate ripng route 0
ripng route 2
Redistribution:

2255::/64
nexthop: fe80::2d0:d0ff:fe78:99dd, via: gei-1/3
metric: 16, tag: 0
2355::/64
metric: 1, tag: 0
2356::/64
metric: 1, tag: 0
2310::/64
5-9

metric: 16, tag: 0

3036::/64
metric: 2, tag: 0
3550::/64
nexthop: ::, via: loopback5
metric: 1, tag: 0
3555::/64
metric: 2, tag: 0
3611::/64
metric: 1, tag: 0

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2310::/64 R 2
gei-1/3 120 fe80:2e::2d0:d0ff:fe78:99dd
3555::/64 R 2
gei-1/3 120 fe80:2e::2d0:d0ff:fe78:99dd
R2#ping6 2310::66
!!!!!
5.3.2 RIPng Route Collection Configuration Example

As shown in Figure 5-2, the RIPng route could be notified to the neighbour after route
collection.
5-10

Figure 5-2 Topology of RIPng Route Collection Configuration Example
Configuration Flow
1. Establish the networking structure and configure the IPv6 address for the interface,
see Figure 5-2.
2. Enable the RIPng protocol for the interface on R1.
3. Configure the loopback address on R2, collect the route and notify R1.
The configuration of R1 is as follows:
R2(config-if-loopback5)#ipv6 address 2001:db8:0:10::/64
5-11

R2(config-ripng-gei-1/3)#ipv6 rip enable
R2(config-ripng-gei-1/3)#exit
R2(config-ripng)#summary-prefix 2001:db8:0:10::/62
/*collect several routers of loopback together*/
The RIPng route learnt from R1 is as follows:
The route information on R1 is as follows:

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2001:db8:0:10::/64 R 2
gei-3/6 120 fe80:c::2d0:d0ff:fe00:500
2001:db8:0:10::/62 R 2
gei-3/6 120 fe80:c::2d0:d0ff:fe00:500
2001:db8:0:11::/64 R 2
gei-3/6 120 fe80:c::2d0:d0ff:fe00:500
2001:db8:0:12::/64 R 2
gei-3/6 120 fe80:c::2d0:d0ff:fe00:500
5-12

Chapter 6
OSPFv3 Configuration
Table of Contents
OSPFv3 Overview......................................................................................................6-1
Configuring OSPFv3 ..................................................................................................6-5
OSPFv3 Configuration Instances..............................................................................6-11
6.1 OSPFv3 Overview

OSPFv3 Introduction
Open Shortest Path First (OSPF) version 2 is a link-status-based interior gateway protocol
developed by IETF. Because it has a wide application scope, provides fast convergence,
eliminates routing loops and facilitates hierarchical network design, it has been widely
applied in IPv4 networks.
With the construction of IPv6 networks, dynamic routing protocols are also required to
provide accurate and valid routing information for IPv6 packet forwarding. For this reason,
IETF revised OSPFv2 for IPv6 networks and developed OSPFv3. OSPFv3 is mostly used
in IPv6 networks to provide the routing function. It is a mainstream routing protocol applied
in IPv6 networks.
The IPv6 OSPF protocol is OSPFv3, and the IPv4 OSPF protocol is OSPFv2.
The IPv6 OSPF keeps the majority of IPv4 algorithms. The essential OSPF mechanism
remains unchanged from IPv4 to IPv6.
Both OSPFv3 and OSPFv2 have a link status database. The Link Status Advertisement
(LSA) is contained in the link status database, and the link status databases of all routers
in the same area must be kept synchronous.
Database synchronization is implemented through the database exchange process, which
includes exchanging database description packets, link state request packets and link state
update packets. The subsequent database synchronization is maintained through flooding
with link state update packets and link state acknowledgment packets.
In broadcast and Non-Broadcast Multicast Access (NBMA) networks, both OSPFv3

and OSPFv2 use the hello packet to discover and maintain adjacency and to elect the
Designate Router (DR) and Backup Designate Router (BDR).
OSPFv3 and OSPFv2 also maintain consistency with each other in such aspects as
neighbor determination, basic concept of inter-area routes, redistribution of Autonomous
System (AS) external routes, and so forth.
6-1

Compared with OSPFv2, OSPFv3 has almost the same working mechanism but has also
revised OSPFv2 to support the IPv6 address format. The following sections describe in
detail the similarities and differences between OSPFv2 and OSPFv3.
Similarities Between OSPFv3 and OSPFv2

OSPFv3 has almost the same protocol design concept and working mechanism as
OSPFv2.
l The same packet types: Hello, DD, Link State Packet (LSP), Link State Update (LSU),
LSAck packets.
l The same area division.
l The same LSA flooding and synchronization mechanisms: To guarantee the
correctness of Link-state Database (LSDB) information, the reliable flooding and
synchronization of LSAs must be guaranteed.
l The same route computation method: Both use the Shortest Path First (SPF)
algorithm to compute routes.
l The same network types: Both support four network types, i.e. broadcast, NBMA,
point-to-point, point-to-multipoint.
l The same neighbor discovery and neighbor establishment mechanisms: After an
OSPF router is started, it sends a Hello packet via the OSPF interface to another
OSPF router. Upon receipt of the Hello packet, the latter OSPF router checks the
parameters defined in the packet. If the parameters in the received packet are the
same as those in its own packet, adjacency is established between the two routers.
Two routers in an adjacency relationship do not necessarily become neighbors. This
depends on the network type. The two routers become real neighbors only when
they have successfully exchanged the DD packet and the LSA and their LSDBs are
synchronized with each other.
l The same DR election mechanism: The DR and BDR need to be elected in NBMA
and broadcast networks.
Differences Between OSPFv3 and OSPFv2

There are differences between OSPFv3 and OSPFv2 because OSPFv3 is based on IPv6.
l The topology of OSPFv3 is link-based whereas that of OSPFv2 is subnet-based.
IPv6 uses the term "link" to describe the facilities or mediums used by nodes for
communications over the link layer. Nodes are connected with links. Multiple IP
subnets can be attached to the same link. Two nodes in different IP subnets can
communicate with each other directly over a single link.
l Address semanteme is deleted from OSPFv3.
The OSPFv3 packet contains no IPv6 address except for the LSA payload carried in
a link state update packet. The router LSA and network LSA do not contain network
addresses but only indicate topology information. The OSPF router ID and the LSA
ID are reserved as 32-bit IPv4 addresses and not assigned with any IPv6 address.
6-2

Chapter 6 OSPFv3 Configuration
l OSPFv3 extends the range of flooding

The LS field of the LSA reflects its flooding range. LSA features the following three
flooding ranges:
Link Local Range: LSAs only flood in the local link range. This range is applicable
to the link LSA.
Area Range: LSAs only flood in a single OSPFv3 area. This range is applicable
to the router LSA, network LSA, inter-area prefix LSA, inter-area router LSA and
intra-area prefix LSA.
AS Range: LSAs flood in the whole OSPFv3 routing domain. This is applicable
to the AS external LSA. Each link supports multiple instances. OSPFv3 supports
the operation of multiple OSPF protocol instances over a single link.
l Usage of link local address.
The IPv6 link local addresses are used for neighbor discovery and automatic
configuration over a single link. IPv6 routers do not forward the IPv6 packets
containing link local source addresses. The IPv6 address range allocated to the link
local unicast addresses is FE80/10.
Except for the virtual link, OSPFv3 link local addresses related to interfaces can
serve as source addresses to send OSPF packets. In the virtual link, only the IPv6
addresses in the global range or of a local site can serve as the source address.
The link local addresses occur in the OSPFv3 LSA but are not allowed to occur in
other types of LSAs.
l Changes to the authentication mode
The authentication type and authentication field are removed from the OSPFv3
header. The authentication-related fields do not occur in the OSPFv3 area data
structure and the interface data structure. The OSPFv3 employs the authentication
mechanism provided by the IPv6 itself to implement integrity and confidentiality in
packet exchanging.
l Changes to the protocol packet format
The OSPFv3 runs over the IPv6 directly. Address semanteme is not contained in
the OSPF header but in different LSA types. Therefore, OSPFv3 is independent of
network protocols. The following are changes to the packet format:
The version number changes from 2 to 3.
Options fields of the Hello packet and the database description packet are
expanded to 24 bits.
The authentication and authentication type fields are removed from the packet
header.
The Hello packet does not contain the address semanteme but contains an
interface ID used by the router to identify the link. If the router becomes the DR
on the link, the interface ID will be the link state ID of the network LSA.
6-3

To process the router LSA during SPF computation, two flag bits R and V6 are
added to the options field. The OSPF header contains an Example ID, thus
allowing the operation of multiple OSPF protocol instances over a single link.
LSA Types
An LSA is the unit to construct the OSPFv3 link state database. A router uses LSAs to
form a complete network topology and further generate a routing table. OSPFv3 has the
following types of LSAs.
l Router LSA
Its link state type is 0x2001. It can generate one or multiple LSAs on each router
within an area.
l Network LSA
Its link state type is 0x2002. It can generate network LSAs for each broadcast and
NBMA link within an area, which supports two or multiple routers. Network LSAs are
created by DR on this link.
l Inter-Area prefix LSA
Its link state type is 0x2003. It is equivalent to the Type-3 LSA in OSPFv2. Created by
an area border router, the inter-area prefix router LSA describes IPv6 address prefixes
in other areas. For stub areas, inter-area prefix LSA can also be used to describe the
default route.
l Inter-Area router LSA
Its link state type is 0x2004. It is equivalent to the Type-4 LSA in IPv4. Created by the
ABR, it describes the ASBR to other areas.
l AS external LSA
Its link state type is 0x4005. It is created by the ASBR and describes the ASBR to
other areas.
l Link LSA
Its link state type is 0x0008. A router advertises a separate link LSA to each link
connecting with it. These LSAs have a local link flooding range and will not be flooded
out of the related link.
l Intra-area prefix LSA
Its link state type is 0x2009. A router uses the intra-area prefix LSA to advertise
one or multiple IPv6 address prefixes, which are associated with the router itself, the
connected stub network segment or the connected transit network segment.
Two types of LSAs are added to OSPFv3. They are the Link LSA and the Intra Area
Prefix LSA. Table 6-1 lists the brief similarities and differences between OSPFv3 LSAs
and OSPFv2 LSAs.
6-4

Table 6-1 Similarities and Differences Between OSPFv3 LSAs and OSPFv2 LSAs
OSPFv2 LSA OSPFv3 LSA Similarities with and Differences from

OSPFv2 LSAs
Router LSA Router LSA The name is the same and the function
is similar, except that the LSA no longer
Network LSA Network LSA
describes address information but is used
only to describe the topology structure of
the routing area.
Network Summary LSA Inter Area Prefix LSA The function is similar but the name is
ASBR Summary LSA Inter Area Router LSA different.
AS External LSA AS External LSA Both the function and the name are
completely the same.
Link LSA The LSA is newly added.
Intra Area Prefix LSA The LSA is newly added.
6.2 Configuring OSPFv3

This procedure describes how to configure the attributes and functions for OSPFv3
protocol routes, including protocol attributes, interface attributes, route summarization,
redistributing routes into OSPFv3 from other routing protocols, and route load sharing.
Steps
1. Enable OSPFv3.
1 ZXR10(config)#ipv6 router ospf <process-id>[vrf Enables the OSPFv3 process.

<vrf-name>]
2 ZXR10(config-ospfv3-process-id)#router-id Specifies the Router ID for an

<router-id> OSPFv3 process.
<process-id>: OSPFv3 process ID, range: 165535.
vrf <vrf-name>: VRF name, range: 132 characters.
<router-id>: OSPF router ID in IP address format.

OSPFv3 instances cannot run properly until the router ID is configured through the
router-id command.
2. Configure OSPFv3 protocol attributes.
6-5

Command Function
ZXR10(config-ospfv3-process-id)#area <area-id> Configures authentication

authentication ipsec spi <spi-id>{md5 | sha1 password of all interfaces in an
<Hex-string>[rollover-interval <rollover-interval>]} OSPFv3 area.
ZXR10(config-ospfv3-process-id)#area <area-id> bfd Configures BFD attribute of all

<disable | enable> interface in an area.
ZXR10(config-ospfv3-process-id)#area <area-id> Configures the default metric

default-cost <cost-value> value for an area, range: 0 to
16777215, default: 1.
ZXR10(config-ospfv3-process-id)#area <area-id> Configures OSPFv3 interface

encryption{ipsec spi <spi-id> esp 3des | aes-cbc 128 | des | encryption.
null [hex-string] md5 | sha1 <Hex-string>[rollover-interval
<rollover-interval>]}
ZXR10(config-ospfv3-process-id)#area <area-id> range Configures the range of

X:X::X:X/<0-128>[advertise | not-advertise] summary addresses in an area.
advertise | not-advertise,
enables/prohibits the
advertisement of summary
3-type LSAs.
ZXR10(config-ospfv3-process-id)#area <area-id> stub Defines an area as the stub

[no-summary] area.
no-summary implies the ABR
is forbidden to send summary
routes to this stub area.
ZXR10(config-ospfv3-process-id)#area <area-id> Defines an OSPF virtual link.

virtual-link [dead-interval <seconds>][hello-interval
<seconds>][retransmit-interval <seconds>][transmit-delay
<seconds>]
ZXR10(config-ospfv3-process-id)# bfd enable Enables the BFD function on all

interfaces.
Run the no format of this
command to restore the default
value.
ZXR10(config-ospfv3-process-id)#default-metric Sets the default metric value for

<metric-value> the OSPFv3 protocol, range: 1
to 16777214, default: 20.
This value is allocated to
redistributed routes.
6-6

Command Function
ZXR10(config-ospfv3-process-id)#distribute-list The distribute-list in command

{access-list <access-list-name> in |route-map <name of a filters routes of which the
route-map> in} owner is OSPF routes. The
distribute-list out command
controls the redistribution
of external routes to OSPF
areas after Type-5 LSAs are
generated. This is a supplement
of the redistribute command.
ZXR10(config-ospfv3-process-id)#timers spf Sets the interval at which the

<delay><holdtime> OPSFv3 protocol computes
routes.
ZXR10(config-ospfv3-process-id)#fast-reroute Sets the OSPFv3 FRR

<per-prefix> parameter.
<spi-id>: security policy index, decimal, range: 256 to 32767.
<Hex-string>: A MD5-key is 132 characters, a SHAL-key is 140 characters.

<rollover-interval>: the delay (in minutes, range is 0 to 100000) of a valid key. As it
costs a long time for a user to modify the key on the router, a smooth transition period
is needed. This parameter is used to set the smooth transition period.
hello-interval <seconds>: specifies the interval (in seconds) at which Hello packets
are sent on the virtual link, range: 1 to 8192, default: 10.
dead-interval <seconds>: specifies the dead interval (in seconds) of neighbors on the
virtual link, range: 1 to 8192, default: 40.
retransmit-interval <seconds>: specifies the retransmission interval of packets on the

virtual link, range: 1 to 8192, default: 5.
transmit-delay <seconds>: specifies the delay (in seconds) after which a link state
update packet is transmitted on the virtual link, range: 1 to 8192, default: 1.
<delay>: specifies the delay (in seconds) of route re-computation that follows after
route updates are received, range: 0 to 65535, default: 5.
<holdtime>: specifies the hold time (in seconds), range: 0 to 65535, default: 10.
3. Configure OSPFv3 route summarization, and redistribute routes into OSPFv3 from
other routing protocols.
Command Function
ZXR10(config-ospfv3-process-id)#redistribute Redistributes the routes of

<protocol>[metric <metric-value>][metric-type protocols into the OSPFv3
<type>][route-map <name>][tag <number>] protocol.
6-7

Command Function
ZXR10(config-ospfv3-process-id)#summary-prefix Summaries the routes of other

<X:X::X:X/<0-128>> protocols that are redistributed
to OSPF.
<protocol>: specifies the name of the redistributed protocol, such as connected,

static, rip, bgp, isis, iaftr,isf-nat64,isl-nat64-ipv6or isubscriber-host.
<metric-value>: specifies the metric of the redistributed LSA. By default, range:

1-16777214.
<type>: specifies the metric-type of the redistributed LSA, range: ext-1 or ext-2, default:
ext-2.
tag <number>: sets a tag for a route redistributed to OSPF. Range: 04294967295.
Default: 0.
4. Configure OSPFv3 route load sharing.
1 ZXR10(config-ospfv3-process-id)#maximum-paths Configures the number of

<number> routes supported by the
protocol for load sharing,
Up to 32 equal-cost route
entries can be stored in
the routing table for load
balancing. This command
can configure up to 32 paths
with the same measurement
value.
2 ZXR10(config)#interface <interface-name> Enters interface

configuration mode.
3 ZXR10(config-if-interface-name)#load-sharing Configures the weight for

bandwidth <bandwidth-value> interface load sharing.
l The weight, which is set
on an outgoing interface,
cannot take effect until
the priority is configured.
l Interfaces with different
weights have different
bandwidth values.
5. Configure OSPFv3 interface attributes.
6-8

1 ZXR10(config-ospfv3-process-id)#interface Adds an interface to

<interface-name>[area <area-id>][instance <0~255>] OSPFv3.
2 ZXR10(config-ospfv3-process-id-if-interface- Specifies the interval of

name)#hello-interval <interval> sending Hello packets on an
interface in seconds, range:
1 to 65535.
The default value for
point-to-point and
broadcast interfaces is
10 seconds.
non-broadcast and
point-to-multipoint
interfaces is 30 seconds.
ZXR10(config-ospfv3-process-id-if-interface- Specifies the time interval

name)#retransmit-interval <interval> (in seconds) at which an
interface retransmits an LSA,
range: 1 to 65535, default: 5.
ZXR10(config-ospfv3-process-id-if-interface- Specifies the delay (in

name)#transmit-delay <interval> seconds) after which an
interface transmits a link
state update packet, range:
1 to 65535, default: 1.
ZXR10(config-ospfv3-process-id-if-interface- Specifies the aging time (in

name)#dead-interval <interval> seconds) of neighbors on an
interface, range: 1 to 65535.
point-to-point and
broadcast interfaces is
40 seconds.
non-broadcast and
point-to-multipoint
interfaces is 120 seconds.
ZXR10(config-ospfv3-process-id-if-interface- Sets the interface cost value

name)#cost <cost-value> (in seconds), range: 1 to
65535.
ZXR10(config-ospfv3-process-id-if-interface- Sets the interface priority (in

name)#priority <value> seconds), range: 0 to 255,
default: 1.
6-9

ZXR10(config-ospfv3-process-id-if- Configures the neighboring

interface-name)#neighbor <X:X::X:X>[{[cost routers in a non-broadcast or
<cost-value>]|[poll-interval <interval>]|[priority point-to-multipoint network.
<value>]}]
ZXR10(config-ospfv3-process-id-if-interface- Sets the network type for an

name)#network {broadcast | non-broadcast | interface.
point-to-multipoint [non-broadcast]| point-to-point}
ZXR10(config-ospfv3-process-id-if-interface- Configures the authentication

name)#authentication [null |{ipsec spi <spi-id> password on an OSPFv3
md5 | sha1 <Hex-string>[rollover-interval interface.
<rollover-interval>]}]
ZXR10(config-ospfv3-process-id-if-interface- Configures the BFD attribute.

name)#bfd <disable | enable>
ZXR10(config-ospfv3-process-id-if-interface- Configures OSPFv3 interface

name)#encryption [null |{ipsec spi <spi-id> encryption.
esp 3des|aes-cbc 128|dst|null [hex-string] md5 |
sha1<Hex-string>[rollover <rollover-interval>]}]
ZXR10(config-ospfv3-process-id-if-interface- Configures to ignore MTU

name)#ipv6-mtu-ignore check during DD packet
exchange.
ZXR10(config-ospfv3-process-id-if-interface- Suppresses an interface to

name)#linklsa-suppress <enable> generate Type-8 link LSA.
ZXR10(config-ospfv3-process-id-if-interface- Disable the FRR function on

name)#fast-reroute <disable> the interface.
Command Function
ZXR10(config)#show ipv6 ospf <process id> Displays an OSPFv3 instance.
ZXR10(config)#show ipv6 ospf database Displays the database information about

an OSPFv3 instance.
ZXR10(config)#show ipv6 ospf interface Displays the interface information about

[<interface-name>] an OSPFv3 instance.
ZXR10(config)#show ipv6 ospf neighbor Displays the neighbor information about

an OSPFv3 instance.
ZXR10(config)#show ipv6 ospf request-list Displays request list information about an

OSPFv3 instance.
ZXR10(config)#show ipv6 ospf retransmission-list Displays retransmission list information

about an OSPFv3 instance.
6-10

Command Function
ZXR10(config)#show ipv6 ospf vertex Displays node information about an

OSPFv3.
ZXR10(config)#show ipv6 ospf virtual-links Displays the virtual link information about
an OSPFv3 instance.
7. Maintain the OSPFv3 interface.
Command Function
ZXR10(config-ospfv3-process-id)#passive-interf Forbids an OSPFv3 interface from

ace <interface-name> receiving and transmitting packets.
In general, interfaces can receive and
transmit OSPF protocol packets properly.
This command forbids an interface from
receiving and transmitting OSPF packets,
the purpose of which is for debugging and
troubleshooting.
End of Steps
6.3 OSPFv3 Configuration Instances

6.3.1 OSPFv3 Basic Configuration Example
As shown in Figure 6-1, R1 and R2 establish a link via direct connection interfaces to
advertise their respective loopback address route.
Figure 6-1 Topology of OSPFv3 Configuration Examples
Configuration Flow
1. Enable the IPv6 protocol on the direct connection interfaces of R1 and R2, configure
IPv6 addresses for the direct connection interfaces, configure loopback interfaces,
enable IPv6 on the loopback interfaces, and configure IPv6 addresses for the loopback
interfaces.
2. Configure OSPFv3.
6-11

3. Add the interfaces to OSPFv3 area 0.

4. Check and verify the configuration results: Neighbors are correctly established
between the two routers, each router can learn the routes advertised by the peer
router, and each router can ping the peer loopback interface successfully.
R1(config)#ipv6 router ospf 1

R1(config-ospfv3-1)#router-id 11.11.11.11
R1(config-ospfv3-1)#interface gei-3/6 area 0
R1(config-ospfv3-1-if-gei-3/6)#exit
R1(config-ospfv3-1)#interface loopback5 area 0
R1(config-ospfv3-1-if-loopback5)#exit
R1(config-ospfv3-1)#exit

6-12

After completing the above configuration, run the show ipv6 ospf neighbor command and
the show ipv6 forwarding route command on each router to check the established neighbor
information and route information. Ping the peer loopback interface from each router. If
both routers can ping the loopback interface of the peer router successfully, it means that
the configuration is successful.
Check and verify the configuration result on R1, as shown below.
R1(config)#show ipv6 ospf neighbor

OSPFv3 Process 1
Neighbor ID Pri State Dead Time Interface ID Interface
10.10.10.10 1 FULL/BDR 00:00:35 46 gei-3/6
R1#show ipv6 forwarding route 3550::55

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3550::55/128 O 1
R1#ping6 3550::55
sending 5,100-byte ICMP echo(es) to 3550:0:0:0:0:0:0:55,timeout is 2 second(s).
!!!!!
R2(config)#show ipv6 ospf neighbor

OSPFv3 Process 1
11.11.11.11 1 FULL/DR 00:00:37 18 gei-1/3

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3555::52/128 O 1
gei-1/3 110 fe80:2e::2d0:d0ff:fe78:99dd
6-13

R1#ping6 3550::52
!!!!!
6.3.2 OSPFv3 Redistribution Configuration Example

As shown in Figure 6-2, R1 and R2 establish a link with each other via the direct connection
interfaces, R1 and R2 establish the link in area 0 whereas R2 and R3 establish a link
with each other in area 10 to advertise their respective loopback address route, and R1
redistributes the direct route.
Figure 6-2 Topology of OSPFv3 Configuration Example 2
Configuration Flow
1. Enable the IPv6 protocol on each interface, configure IPv6 addresses, configure
loopback interfaces, enable IPv6 on the loopback interfaces, and configure IPv6
addresses for the loopback interfaces.
2. Configure OSPFv3.
3. Add the interfaces to OSPFv3. R1 and R2 establish a link with each other in area 0,
R2 and R3 establish a link with each other in area 10, and R1 redistributes the direct
route.
4. Check and verify the configuration results: Neighbor relationships are correctly
established among the routers, each router can learn the routes advertised by the
other two routers, and each router can ping the loopback interfaces of the other two
routers successfully.
6-14


R1(config-ospfv3-1)#redistribute connected


6-15


After completing the above configuration, run the show ipv6 ospf neighbor command
and the show ipv6 forwarding route command on each router to check the established
neighbour information and route information. Ping the peer loopback interface of each
router. If both routers can ping the loopback interface of the peer router successfully, it
means that the configuration is successful.
R1#show running-config ospfv3
! <OSPFV3>
ipv6 router ospf 1
router-id 11.11.11.11
interface gei-3/6 area 0.0.0.0 instance 0
$
$
! </OSPFV3>
R1#show ipv6 ospf neighbor

OSPFv3 Process 1
10.10.10.10 1 FULL/BDR 00:00:35 46 gei-3/6

IPv6 Routing Table:
6-16


Dest Owner Metric
Interface Pri Gw
3550::52/128 O 1
R1#ping6 3550::52
!!!!!

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3500::55/128 O 2
R1 #ping6 3500::55
!!!!!

! <OSPFV3>
ipv6 router ospf 1
router-id 10.10.10.10
$
interface loopback5 area 0.0.0.0 instance 0
$
$
!
! </OSPFV3>

OSPFv3 Process 1
1.1.1.5 1 FULL/BDR 00:00:33 54 gei-1/2
6-17

11.11.11.11 1 FULL/DR 00:00:37 18 gei-1/3

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3555::/64 O 20
gei-1/3 110 fe80:2e::2d0:d0ff:fe78:99dd
R2#ping6 3555::52
!!!!!

! <OSPFV3>
ipv6 router ospf 1
router-id 1.1.1.5
$
interface loopback5 area 0.0.0.10 instance 0
$
!
! </OSPFV3>

OSPFv3 Process 1
10.10.10.10 1 FULL/DR 00:00:31 45 gei-3/6

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3555::/64 O 20
6-18

R3#ping6 3555::52
!!!!!
6.3.3 OSPFv3 Route Load-Sharing Configuration Examples

As shown in Figure 6-3, the load sharing configuration supports 64 nexthops at most. The
following uses two nexthops as an example to illustrate the configuration.
Figure 6-3 Topology of OSPFv3 Route Load-Sharing Configuration Examples
Configuration Flow
1. Establish the networking structure, as shown in Figure 6-3.
2. Configure the address for the interface and configure OSPFv3.
3. Configure the load sharing for the interface.
R1(config-if-loopback11)#ip address 2.2.2.2 255.255.255.255

R1(config-ospfv3-1-if-gei-1/1)#$
R1(config-ospfv3-1)#interface gei-1/2 area 0 /*configure ospfv3*/
6-19

R1(config-ospfv3-1)#maximum-paths 2
/*Configure two paths for load sharing.*/
R2(config-if-loopback11)#ip address 1.1.1.1 255.255.255.255

R2(config-ospfv3-1)#interface gei-2/1 area 0 /*configure ospfv3*/
R2(config-ospfv3-1-if-loopback10)#$
R2(config-ospfv3-1)#maximum-paths 2
Execute the show ipv6 forwarding route ospf command on R1 to check the same
destination address 2000::2, and the route forwarding table items with the same cost.
6-20

Chapter 7
IS-ISv6 Configuration
Table of Contents
IS-ISv6 Overview .......................................................................................................7-1
Configuring IS-ISv6 ....................................................................................................7-2
IS-ISv6 Configuration Examples .................................................................................7-9
7.1 IS-ISv6 Overview

The Intermediate System-to-Intermediate System (IS-IS) protocol is a routing protocol
developed by the International Organization for Standardization (ISO) for CLNS. It is a
network layer protocol of the OSI protocol suite. It has been expanded to support IP
routing and form an integrated IS-IS protocol. The IS-IS protocol currently mentioned
refers to the integrated IS-IS protocol.
The IS-IS protocol is used as an Interior Gateway Protocol (IGP) in plenty of networks.
Its operating mechanism is similar to that of the OSPF protocol. It divides a network into
multiple areas. The routers in an area can manage only the routing information in the area.
This saves router costs and thus makes it suitable for large- and medium-scale networks.
The IS-IS protocol also uses Dijkstra's SPF algorithm to compute routes. It uses the SPF
algorithm to obtain the optimal route according to the link status database and then adds
the route to the IP routing table.
IS-IS is a routing protocol with high expansibility, so it can support the expansion of the
CLNS routing protocol to support IPv4 and support IPv6.
Uni-topology IS-IS can only run a single SPF algorithm. The topologies corresponding to
IPv4 and IPv6 must be identical and with special restriction. While the multi-topology IS-IS
can run multiple SPF algorithms. Then the topologies corresponding to IPv4 and IPv6 may
be different and with certain flexibility.
RFC defines how to use IS-IS to support IPv6. It defines two new Tag, Length, Values
(TLVs): IPv6 Reachability TLV and IPv6 Interface Address TLV.
l The TLV type value of the IPv6 Reachability TLV is 236 (0xEC). Its TLV effects are
equal to the two TLVs of IPv4: IP internally reachable and IP externally reachable.
Up/down and external are defined in this TLV and are used to indicate that routes are
redistributed mutually in the L2/L1 and to determine whether a route is an external
route.
l The TLV type value of the IPv6 Interface Address TLV is 232 (0xE8). Its TLV effects
are equal to the TLV of IPv4: IP port address. The difference is that the original 32-bit
address segment is superseded by the 128-bit address segment in the new TLV.
7-1

The operating principles of IS-ISv6 are similar to those of IS-ISv4.
7.2 Configuring IS-ISv6

This procedure describes how to configure the attributes and functions of IS-ISv6 protocol
routes, including basic attributes, global attributes, summary route, redistributing routes
into IS-ISv6 from other routing protocols, fast rerouting, and interface parameters.
Steps
1. Configure IS-ISv6 basic information.
1 ZXR10(config)#router isis[process-id][vrf <vrf-name>] Enables the IS-ISv6 routing

protocol process.
2 ZXR10(config-isis-process-id)#system-id Configures the system ID of a

<system-id>[range <range-number>] route entity.
ZXR10(config-isis-process-id)#area <area-address> Designates the area address

of IS-ISv6.
<system-id>: specifies the System ID of the instance, which is a hexadecimal string of

6 bytes in the form of xxxx.xxxx.xxxx.
range <range-number>: specifies the extensible range of the System ID, range: 0
to 32, default: 0. The instance assumes an ID ranging from System ID to System
ID+<range-number>.
<area-address>: specifies the area address, which is a hexadecimal string of 1 to 13
bytes.
2. Configure IS-ISv6 global parameters in IS-ISv6 routing mode.
If all the devices on the network are the ZXR10, the default parameters can be used
during the IS-IS configuration. If other vendors' devices exist in the network and
interconnect with the ZXR10, however, the relevant interface parameters and timers
may need to be changed to enable the IS-IS protocol to more efficiently run in the
network.
Command Function
ZXR10(config-isis-process-id)#enable Enable the IS-ISv6 protocol.

Use the disable command
disable the IS-ISv6 protocol.
ZXR10(config-isis-process-id)#authentication-type {md5 | Configures the authentication

text}[level-1 | level-2] mode of the IS-ISv6 route
entity.
7-2

Chapter 7 IS-ISv6 Configuration
Command Function
ZXR10(config-isis-process-id)#ignore-lsp-errors Sets the IS-ISv6 to ignore LSP

checksum errors.
ZXR10(config-isis-process-id)#is-type {level-1 | level-2-only Configures the routing level

| level-1-2} for a router.
ZXR10(config-isis-process-id)#max-lsp-lifetime <interval> Configures the maximum LSP

life time (in seconds), range: 1
to 65535, default: 1200.
ZXR10(config-isis-process-id)#metric-style {narrow | wide} Configures the metric style of

the router.
The narrow mode uses only 6
bits to carry the metric value,
whereas the wide mode uses
24 bits to carry it and supports
more TLVs to be carried.
ZXR10(config-isis-process-id)#authentication {< key>| Configures the LSP/SNP

encrypt < key>}[ level-1 | level-2] authentication of IS-ISv6.
ZXR10(config-isis-process-id)#disable-snp-authentication Disables SNP authentication.

Run this command when only
LSP authentication needs to
be enabled after LSP/SNP
authentication is configured.
ZXR10(config-isis-process-id)#enable-snp-authentication Enables SNP authentication.

Run this command if SNP
authentication needs to be
enabled again.
ZXR10(config-isis-process-id)#hostname dynamic{disable | Configures the dynamic host

enable} name mapping function of
IS-ISv6.
ZXR10(config-isis-process-id)#hello padding Pads 0 to each hello packet

sent on the interface until the
packet size equals the MTU
value of the interface.
3. Configure IS-ISv6 global parameters in IS-ISv6 address family mode.
1 ZXR10(config-isis-process-id)#address-family ipv6 Enters IPv6 address-family

configuration mode.
7-3

2 ZXR10(config-isis-process-id-af)#distance <1-255> Configures the

administrative distance
of IS-ISv6 routes.
ZXR10(config-isis-process-id-af)#multi-topology Enables the multi-topology

function.
ZXR10(config-isis-process-id-af)#set-overload-bit Sets the overload-bit in the

LSP packets sent by IS-IS
itself.
ZXR10(config-isis-process-id-af)#router-leak level-2 Configures the leakage

into level-1 route-map <map-tag> from level-2 to level-1
routes.
ZXR10(config-isis-process-id-af)#distribute-list Configures IS-ISv6 route

route-map <map-tag> in filter policy.
ZXR10(config-isis-process-id-af)#spf-interval Configures the minimum

<interval>[level-1 | level-2] interval (in seconds) at
which the IS-ISv6 makes
topology computation,
ZXR10(config-isis-process-id-af)#prefix-priority Configures the IPv6 prefix

{critical | high | medium}{acl-name <acl-name>| tag priority.
<value>}[{level-1 | level-2}]
Parameters descriptions:
critical: sets the critical prefix rule.
high: sets high prefix rule.
medium: sets medium prefix rule.
acl-name <acl-name>: The ACL list indicates priorities. Range: 131 characters.
tag <value>: sets a tag to indicate the priority. Range: 14294967295.
level-1: The router is in Level-1 area.
level-2: The router is in Level-2 area.

4. Configure IS-ISv6 summary route and redistribution of routes from other protocols into
IS-ISv6.
Command Function
ZXR10(config-isis-process-id-af)#redistribute <protocol Configures the redistribution

>[level-1 | level-1-2 | level-2][metric <metric-value>][route-map of routes from other routing
<map-tag>] protocols into IS-ISv6.
7-4

Command Function
ZXR10(config-isis-process-id-af)#summary-prefix Configures IS-ISv6 route

<ipv6-prefix>[{[metric <metric-value>],[{level-1 | level-1-2 | aggregation.
level-2}]}
<protocol>: specifies the route origin, which can be connect, static, rip, ospf,
bgp, aftr, sf-nat64 or sl-nat64-ipv6, required. To redistribute IS-IS/OSPF routes,
it is necessary to specify the instance number.
level-1 | level-2 | level-1-2: specifies the redistribution range, default: level-2.
metric <metric-value>: specifies the metric value of the IS-ISv6 route. If the metric-style
is narrow, the value range of <metric-value> is 0 to 63. If the metric-style is wide, the
value range of <metric-value> is 0 to 426142864.
route-map <map-tag>: specifies the route map name for the current protocol
redistribution, 1 to 31 characters in length.
<ipv6-prefix>: IPv6 network segment prefix, format: X:X::X:X/<0-128>.

5. Configure load sharing and fast rerouting for IS-ISv6 routes.
Command Function
ZXR10(config-isis-process-id-af)#maximum-paths Configures the maximum

<number> number of next-hop paths,
range: 1 to 32.
ZXR10(config-isis-process-id-af)#fast-reroute enable Enables fast reroute function.
ZXR10(config-isis-process-id-af)#fast-reroute Sets the fast rerouting type of

alternate-type {down-stream-path} IS-IS.
6. Configure IS-ISv6 interface parameters.
1 ZXR10(config-isis-process-id)#interface Enters IS-ISv6 interface

<interface-name> configuration mode.
2 ZXR10(config-isis-process-id-if-interface- Runs the IS-ISv6 protocol

name)#ipv6 router isis on an interface.
7-5

3 ZXR10(config-isis-process-id-if-interface- Configures the circuit-type

name)#circuit-type {level-1 | level-1-2 | level-2-only} on an interface.
ZXR10(config-isis-process-id-if-interface- Configures the interval at

name)#csnp-interval <interval>[level-1 | level-2] which the IS-ISv6 protocol
sends CSNP packets on
an interface, range: 1 to
65535.
The default value is 10
seconds for a broadcast
link and 3,600 seconds for
a point-to-point link.
ZXR10(config-isis-process-id-if-interface- Configures the interval

name)#hello-interval <interval>[level-1 | level-2] (in seconds) at which the
IS-ISv6 protocol sends two
consecutive hello packets
on an interface, range: 1 to
65535, default: 10.
ZXR10(config-isis-process-id-if-interface- Configures the IS-ISv6 hello

name)#hello-multiplier <multiplier>[level-1 | level-2] multiplier on an interface,

name)#lsp-interval <interval>[level-1 | level-2] (in seconds) at which the
IS-ISv6 protocol sends two
consecutive LSP packets
on an interface, range: 33
to 4294967040, default: 33.

name)#psnp-interval <interval>[level-1 | level-2] (in seconds) at which the
IS-ISv6 protocol sends
PSNP packets on an
interface, range: 1 to
65535, default: 3.
ZXR10(config-isis-process-id-if-interface- Configures the IS-ISv6

name)#ipv6 metric <value>[level-1 | level-2] metric on an interface,
range: 1 to 16777215,
default: 10. The set metric
value takes effect after the
multi-topology function is
enabled.
7-6

ZXR10(config-isis-process-id-if-interface- Configures the

name)#authentication-type {md5 | text}[level-1 | level-2] authentication mode of
IS-ISv6 hello packets.
ZXR10(config-isis-process-id-if-interface- Configures the

name)#authentication {key| encrypt <key>}[level-1 | level-2] authentication of IS-ISv6
hello packets.
ZXR10(config-isis-process-id-if-interface- Configures the IS-ISv6

name)#priority <priority>[level-1 | level-2] password on the broadcast
network interface, range: 0
to 127, default: 64.

name)#retransmit-interval <interval>[level-1 | level-2] (in seconds) at which
the IS-ISv6 protocol
retransmits LSP packets on
an interface, default: 5.
ZXR10(config-isis-process-id-if-interface- Sets the maximum number

name)#max-burst <number> of LSP packets to be sent
on an interface, range: 1 to
50, default: 1.
ZXR10(config-isis-process-id-if-interface- Sets the mesh-group

name)#mesh-group {<mesh group number>| blocked} function on an certain
interface, range: 1 to
4294967295.
ZXR10(config-isis-process-id-if-interface- Enables a LAN network

name)#network point-to-point interface to simulate a
point-to-point interface.
ZXR10(config-isis-process-id-if-interface- Configures IS-ISv6 metric

name)#metric <value>[level-1 | level-2] on an interface, range: 1 to
16777215, default: 10.
Command Function
ZXR10(config)#show isis adjacency [level-1{ process-id }| Displays IS-ISv6 neighbor

level-2{ process-id }| process-id | up-time {level-1{ process-id information.
}| level-2{ process-id }}]
ZXR10(config)#show isis database [WORD]|[level- Displays the current IS-ISv6

1]|[level-2]detail{WORD|Process-id{WORD}}|verbose { database.
WORD|[level-1]|[level-2]{WORD|Process-id{WORD}}|
Process-id{WORD}
7-7

Command Function
ZXR10(config)#show isis circuits [process-id|detail{process- Displays IS-ISv6 port

id}] information.
ZXR10(config)#show isis [ipv6] topology [level-1{process-id}| Displays IS-ISv6 topology

level-2{process-id}| process-id] information.
ZXR10(config)#show isis hostname [process-id] Displays current IS-ISv6

hostname information.
ZXR10(config)#show isis mesh-groups{blocked | Displays IS-ISv6 mesh-group

group}[process-id] information.
ZXR10(config)#show isis ipv6 fast-reroute-topology [{level-1 | Displays the topology of fast

level-2 | process-id <process-id>}] rerouting information.
8. Maintain the IS-ISv6 route interface.
Command Function
ZXR10(config-isis-process-id-if-interface-name)#pa Configures an interface as an

ssive-mode IS-ISv6 passive interface.
ZXR10(config-isis-process-id-if-interface-name)#i Enables the bidirectional fast link

pv6 bfd-enable detection protocol of IS-ISv6 on
the interface.
ZXR10(config-isis-process-id-if-interface-name)#i Disables the IPv6 fast rerouting

pv6 fast-reroute block function on the interface.
9. Debug IS-ISv6.
Command Function
ZXR10#debug isis all Tracks and shows all the

debugging information about the
IS-ISv6.
ZXR10#debug isis update-packets [process-id <0-65535>] Tracks and shows the debugging
information about IS-ISv6
updating events.
ZXR10#debug isis adj-packets [process-id <0-65535>] Tracks and shows the debugging
adjacency.
ZXR10#debug isis mpls traffic-eng events [process-id Tracks and shows the debugging
<0-65535>] information about IS-ISv6 MPLS
events.
ZXR10#debug isis spf-events [process-id <0-65535>] Tracks and shows the debugging
information about IS-ISv6 route
computation events.
7-8

Command Function
ZXR10#debug isis snp-packets[process-id <0-65535>] Tracks and shows the debugging

sequence number packets.
End of Steps
7.3 IS-ISv6 Configuration Examples

7.3.1 Single-Area IS-ISv6 Configuration Example
The following example shows how to configure the IS-ISv6 protocol on a single-area
network shown in Figure 7-1.
Figure 7-1 Single-Area IS-ISv6 Configuration Example
Configuration Flow
1. Enable the IPv6 protocol on the direct connection interfaces of R1 and R2, configure
IPv6 addresses for the direct connection interfaces, configure loopback interfaces,
enable IPv6 on the loopback interfaces, and configure IPv6 addresses for the loopback
interfaces.
2. Configure the IS-ISv6 protocol and ensure that the system-ids of the two routers are
not the same. If the IPv4 IS-IS protocol has been configured on certain interfaces of
the two routers, set both routers to the multi-topology mode. To set the multi-topology
mode, first set the metric type of the IS-IS protocol to "wide". If the IPv4 IS-IS protocol
is not configured on any interface of the two routers, adjacency can be established
through the default single-topology settings on the two routers. If any interface of either
router is configured with an IPv4 address and the IS-IS protocol, IS-ISv6 neighbors
can be established through the single-topology function on the two routers. In the
latter case, the interface needs to be configured with both an IPv4 address and an
IPv6 address as well as the commands ip router isis and ipv6 router isis. Here, the
multi-topology environment is taken as an example.
3. Enable the IS-ISv6 protocol on the interfaces.
7-9

4. Check and verify the configuration results: Neighbors are correctly established
between the routers, and each router correctly computes the IPv6 topology and can
successfully ping6 the loopback interface of the peer router.
R1(config)#router isis
R1(config-isis-0)#area 47.0005
R1(config-isis-0)#system-id 0000.0000.0011
R1(config-isis-0)#metric-style wide
R1(config-isis-0)#hostname dynamic disable
R1(config-isis-0)#interface gei-0/6
R1(config-isis-0-if-gei-0/6)#ipv6 router isis
R1(config-isis-0-if-gei-0/6)#exit
R1(config-isis-0)#interface loopback5
R1(config-isis-0-if-loopback5)#ipv6 router isis
R1(config-isis-0-if-loopback5)#exit
R1(config-isis-0)#address-family ipv6
R1(config-isis-0-af)#multi-topology
R1(config-isis-0-af)#end
R2(config-isis-0)#area 47.0005
7-10

R2(config-isis-0)#hostname dynamic disable
After the configuration is completed, run the show command on each router to check the
configuration information: Neighbors are correctly established between the routers, and
each router correctly computes the IPv6 topology and can successfully ping6 the loopback
interface of the peer router.
Check the configuration result on R1. Run the show running-config isis command to check
the IS-IS configuration information, as shown below.
R1#show running-config isis
! <route_isis>
router isis 0
area 47.0005
system-id 0000.0000.0011
hostname dynamic disable
metric-style wide
address-family ipv6
multi-topology
$
interface gei-0/6
ipv6 router isis
$
interface loopback5
ipv6 router isis
$
! </route_isis>
Run the show isis adjacency command to check whether the neighbor status is normal, that
is, check whether the state field is UP. After the neighbor is established, the state field
should indicate UP.
R1#show isis adjacency

Interface System id State Lev Holds SNPA(802.2) Pri MT
gei-0/6 0000.0010.0022 UP/UP L1L2 7/6 00D0.D0AF.CC10 64/64 M
7-11

Run the show isis ipv6 topology command to check whether the topology is correctly
computed (For the single-topology environment, run the show isis topology command
instead to check it). If the topology has been successfully computed, the execution results
will indicate the following item. If the metric is , it indicates the local router. If the metric
is xx, it indicates that the destination is unreachable.
R1#show isis ipv6 topology

Process ID: 0
IS-IS paths to Level-1 routers
System id Metric Next-Hop Interface SNPA
0000.0000.0010 10 0000.0010.0022 gei-0/6 00D0.D0AF.CC10
0000.0000.0011 --
0000.0000.0010 10 0000.0010.0022 gei-0/6 00D0.D0AF.CC10
0000.0000.0011 --
Run the show isis circuits command to check the interface information and Designate IS
(DIS) election. If the interface status is "UP", the interface is normal. If the interface status
is "DOWN", the interface is abnormal. Then it is necessary to check the link status. The
Level1-DR item shows the system-id of the DIS.
R1#show isis circuits
IS-IS interface database:
Interface State Lev CirId Level1-DR Level2-DR Pri(L1/L2)
loopback5 Up L1L2 0 No found No found 64/64
gei-0/6 Up L1L2 6 0000.0000.0010-03 0000.0000.0010-03 64/64
Run the show ipv6 forwarding route isis-l1 or show ipv6 forwarding route isis-l2 command
to check route advertisement. If route advertisement is normal, the route advertised by the
loopback interface of the peer router can be seen.
R1#show ipv6 forwarding route isis-l1

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
3550::/64 I1 20
If neighbor establishment and route advertisement are normal, the loopback interface of
the peer route can be pinged successfully.
R1#ping6 3550::52
!!!!!
7-12

Similarly, check the configuration result on R2, as shown below.

! <route_isis>
router isis 0
area 47.0005
system-id 0000.0000.0010
metric-style wide
hostname dynamic disable
address-family ipv6
multi-topology
$
interface gei-0/3
ipv6 router isis
$
interface loopback5
ipv6 router isis
$
! </route_isis>

gei-0/3 0000.0000.0011 UP/UP L1L2 25/25 00D0.D078.99DD 64/64 M

Process ID: 0
0000.0000.0010 --
0000.0000.0011 10 0000.0000.0011 gei-0/3 00D0.D078.99DD
0000.0000.0010 --
0000.0000.0011 10 0000.0000.0011 gei-0/3 00D0.D078.99DD

loopback5 Up L1L2 0 Disabled Disabled 64/64
gei-0/3 Up L1L2 3 Dis is me Dis is me 64/64

IPv6 Routing Table:
7-13

Dest Owner Metric
Interface Pri Gw
3555::/64 I1 20
gei-0/3 115 fe80:2e::2d0:d0ff:fe78:99dd
R2#ping6 3555::52
!!!!!
7.3.2 Multi-Area IS-ISv6 Configuration Example

For a large-scale network, the use of multiple areas shall be considered in IS-IS. Set the
near routers to be in one area according to their positions and functions because area
division is helpful to decrease the demand for memory, and the routers in each area only
need to maintain a smaller link state database.
Figure 7-2 shows a multi-area IS-IS instance. R1 is in Area 1, R2 in Area 0, and R3 and
R4 in Area 2. On R1, perform route aggregation for the network segments in Area 1. The
static routes are redistributed to the IS-IS on R4.
Figure 7-2 Multi-Area IS-ISv6 Configuration Example
Configuration Flow
1. Enable the IPv6 protocol on the interfaces, configure IPv6 addresses for these
interfaces, configure loopback interfaces, enable IPv6 on the loopback interfaces,
and configure IPv6 addresses for the loopback interfaces.
2. Configure the IS-ISv6 protocol and ensure that the system-ids of the routers are not
the same. Establish L2 neighbors between R2 and R1/R3, and establish L1 neighbors
between R3 and R4. Here, the multi-topology environment is taken as an example.
3. Enable the IS-ISv6 protocol on the interfaces.
7-14

4. Enable route aggregation on R1.

5. Redistribute the direct route on R4.
6. Check and verify the configuration results: The routers can correctly establish
neighbors and correctly compute the IPv6 topology, and the interface addresses of
the routers can be successfully pinged from each other.
R1(config-if-loopback1)#ipv6 address 2000:0:0:1::1/64
R1(config-isis-0)#area 01
R1(config-isis-0)#is-type level-1-2
R1(config-isis-0-if-gei-1/3)#circuit-type level-2-only
R1(config-isis-0-if-loopback1)#circuit-type level-2-only
7-15


R1(config-isis-0-af)#multi-topology /*Multi-topology Configuration*/
R1(config-isis-0-af)#summary-prefix 2000::/48 /*Route aggregation*/
R2(config-isis-0)#is-type level-2
7-16


R3(config-isis-0-if-gei-1/3)#circuit-type level-1
R4(config)#ipv6 route::/0 2400::1

R4(config-isis-0)#is-type level-1
R4(config-isis-0)#default-information originate
R4(config-isis-0-if-gei-1/3)#circuit-type level-1
7-17

R4(config-isis-0-if-loopback4)#circuit-type level-1
R4(config-isis-0-af)#redistribute static metric 10 /*Redistribute the route*/
After the configuration is completed, run the show command on each router to check the
configuration information: Neighbors are correctly established, the topology is computed,
and interfaces can be pinged successfully.
Check the configuration results on R1. Run the show running-config isis command to check
the IS-IS configuration information, as shown below.
ZXR10_R1#show running-config isis

! <route_isis>
router isis 0
area 01
system-id 0000.0000.0011
is-type level-1-2
metric-style wide
address-family ipv6
multi-topology
summary-prefix 2000::/48
$
interface gei-1/3
ipv6 router isis
circuit-type level-2-only
$
interface loopback1
ipv6 router isis
$
interface loopback2
ipv6 router isis
$
interface loopback3
ipv6 router isis
$
! </route_isis>
Run the show isis adjacency command to check whether the neighbor status is normal, that
is, check whether the state field is UP. After the neighbor is established, the state field
should indicate UP, as shown below.
7-18

ZXR10_R1#show isis adjacency

gei-1/3 0000.0000.0012 UP L2 7 00D0.D078.99D2 64 M
Run the show isis ipv6 topology command to check whether the topology is correctly
computed (For the single-topology environment, run the show isis topology command
instead to check it). If the topology has been successfully computed, the execution results
will indicate the following item. If the metric is , it indicates the local router. If the metric
is xx, it indicates that the destination is unreachable.
ZXR10_R1#show isis ipv6 topology
Process ID: 0
0000.0000.0011 --
0000.0000.0012 10 0000.0000.0012 gei-1/3 00D0.D078.99D2
0000.0000.0013 20 0000.0000.0012 gei-1/3 00D0.D078.99D2
0000.0000.0014 30 0000.0000.0012 gei-1/3 00D0.D078.99D2
0000.0000.0011
Run the show ipv6 forwarding route isis-l2 command to check route advertisement. If route
advertisement is normal, the route advertised by the loopback interface of the peer router
can be seen.

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2001::/64 I2 10
gei-1/3 115 fe80:2e::2d0:d0ff:fe78:99d2
2300::/64 I2 20
gei-1/3 115 fe80:2e::2d0:d0ff:fe78:99d2
2400::/64 I2 30
gei-1/3 115 fe80:2e::2d0:d0ff:fe78:99d2
If neighbor establishment and route advertisement are normal, the loopback interface of
R4 can be pinged successfully.
ZXR10_R1#ping6 2400::4
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max=97/120/156 ms.
7-19

Similarly, check the configuration result on R2, as shown below.

! <route_isis>
router isis 0
area 00
system-id 0000.0000.0012
is-type level-2-only
metric-style wide
address-family ipv6
multi-topology
$
interface gei-1/1
ipv6 router isis
$
interface gei-1/3
ipv6 router isis
$
! </route_isis>

gei-1/3 0000.0000.0011 UP L2 25 00D0.D078.99DD 64 M
gei-1/1 0000.0000.0013 UP L2 25 00D0.D078.99D3 64 M

0000.0000.0012 --
0000.0000.0011 10 0000.0000.0011 gei-1/3 00D0.D078.99DD
0000.0000.0013 10 0000.0000.0013 gei-1/1 00D0.D078.99D3
0000.0000.0014 20 0000.0000.0013 gei-1/1 00D0.D078.99D3

Process ID: 0
gei-1/3 Up L2 3 Disabled Dis is me 64/64
gei-1/1 Up L2 2 Disabled 0000.0000.0013-01 64/64

IPv6 Routing Table:
7-20

Dest Owner Metric
Interface Pri Gw
2000::/48 I2 10
gei-1/3 115 fe80:2e::2d0:d0ff:fe78:99dd
2300::/64 I2 10
gei-1/1 115 fe80:2e::2d0:d0ff:fe78:99d3
2400::/64 I2 20
gei-1/1 115 fe80:2e::2d0:d0ff:fe78:99d3
Check the configuration result on R3, as shown below.

! <route_isis>
router isis 0
area 02
system-id 0000.0000.0013
metric-style wide
address-family ipv6
multi-topology
$
interface gei-1/1
ipv6 router isis
$
interface gei-1/3
ipv6 router isis
circuit-type level-1
$
! </route_isis>

gei-1/3 0000.0000.0014 UP L1 25 00D0.D078.99D4 64 M
gei-1/1 0000.0000.0012 UP L2 25 00D0.D078.99D2 64 M

Process ID: 0
0000.0000.0013 --
0000.0000.0014 10 0000.0000.0014 gei-1/3 00D0.D078.99D4
7-21


0000.0000.0013 --
0000.0000.0011 10 0000.0000.0012 gei-1/1 00D0.D078.99D2
0000.0000.0012 20 0000.0000.0012 gei-1/1 00D0.D078.99D2
R3#show ipv6 forwarding route

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2000::/48 I2 20
gei-1/1 115 fe80:2e::2d0:d0ff:fe78:99d4
2003::/64 I2 10
gei-1/1 115 fe80:2e::2d0:d0ff:fe78:99d2
2400::/64 I1 10
gei-1/1 115 fe80:2e::2d0:d0ff:fe78:99d2

! <route_isis>
router isis 0
area 02
system-id 0000.0000.0014
is-type level-1
metric-style wide
address-family ipv6
multi-topology
redistribute connected metric 10
$
interface gei-1/1
ipv6 router isis
circuit-type level-1
$
! </route_isis>

gei-1/3 0000.0000.0013 UP L1 25 00D0.D078.99D3 64 M

Process ID: 0
7-22


0000.0000.0014 --
0000.0000.0013 10 0000.0000.0013 gei-1/3 00D0.1234.561F
R4#ping6 2000:0:0:1::1
sending 5,100-byte ICMP echoes to 2000:0:0:1::1,timeout is 2 seconds.
!!!!!
7-23

7-24

Chapter 8
BGP4+ Configuration
Table of Contents
BGP4+ Overview........................................................................................................8-1
Configuring BGP4+ ....................................................................................................8-1
BGP4+ Configuration Instances .................................................................................8-3
8.1 BGP4+ Overview

The Border Gateway Protocol (BGP) is a routing protocol applied between ASs to
exchange network reachability information between the ASs. The information covers a
list of ASs that a route passes through. It is sufficient for establishing a diagram indicating
the connection status of the ASs. This makes possible AS-based routing policies and at
the same time solves the route loop issue.
BGP4+ is an extension of BGP. It assumes the basic message format of BGP4 as defined
in RFC but has added with the extended attributes to transmit IPv6 routing information, and
processes all IPv6 routes according to RFC. BGP4+ also supports the extended functions
such as BGP route reflection and BGP alliance as defined in RFC. It has the following
features:
l Supporting route aggregation
l Employing TCP as the bottom-layer protocol and using TCP port 179 to guarantee a
reliable operation
l Transmitting route updates only
l Periodically sending the keep-alives signal to guarantee normal TCP connections
l Possessing complete metrics
l Boasting of abundant attributes and powerful control functions
l Suiting huge networks
The operating principles of BGP4+ are similar to those of BGP.
8.2 Configuring BGP4+

This procedure describes how to configure the attributes and functions of BGP4+ protocol
routes, including basic functions and route load sharing.
Steps
1. Configure BGP4+ basic function.
For the ZXR10 ZSR V2, the commands for configuring BGP4+ are similar to those
for configuring BGP in IPv4, except that the ZXR10 ZSR V2 supports IPv6 address
8-1

configuration. For details, refer to the BGP Configuration in Configuration Guide

(IPv4 Routing).
2. Configure BGP4+ route load sharing.
1 ZXR10(config)#router bgp < as-number> Enters RIP route configuration mode.
ZXR10(config-bgp)#address-family ipv6 Enters BGP IPv6 address family

configuration mode.
2 ZXR10(config-bgp-af-ipv6)#maximum-pa Configures the count of routes that

ths ibgp< number> support load sharing. It is in the range
of 1-32. The default value is 1. (This is
for IBGP route load sharing.)
ZXR10(config-bgp-af-ipv6)#maximum-pa Configures the count of routes that

ths < number> support load sharing for EBGP route
load sharing, range: 1 to 32, default: 1.
ZXR10(config-bgp-af-ipv6)#maximum-pa Configures the count of routes that

ths eibgp< number> support load sharing. It is in the range
of 1-32. The default value is 1. (This is
for IBGP route and ESGP route load
sharing.)
3 ZXR10(config-bgp-af-ipv6)#bgp frr Configures the BGP FRR function.

Number of default backup routes: 1.
4 ZXR10(config)#interface < interface-name> Enters interface configuration mode.
ZXR10(config-if-interface-name)#ip Configures load sharing mode on an

load-sharing {per-destination | per-packet} interface.
Load sharing should be configured
on interfaces. By default, the mode
is per-destination. Only when the
load sharing mode on all interfaces is
per-packet, the load sharing mode is
per-packet.
Command Function
ZXR10(config)#show ip bgp protocol Displays configuration information about

the BGP protocol module.
ZXR10(config)#show bgp ipv6 unicast neighbor Displays BGP adjacency and the current
[{<ipv4-addr>|<ipv6-addr>}] neighbor status.
ZXR10(config)#show bgp ipv6 unicast Displays the entries in the BGP routing
table.
8-2

Chapter 8 BGP4+ Configuration
Command Function
ZXR10(config)#show bgp ipv6 unicast summary Displays the states of all BGP neighbors.
4. Maintain BGP4+.
Command Function
ZXR10#debug ip bgpin Tracks and displays notification packets

received by BGP, and lists the error
number and sub-error number.
ZXR10#debug ip bgp out Tracks and displays notification packets

sent by BGP, and lists the error number
and sub-error number.
ZXR10#debug ip bgp keepalives Tracks and displays BGP Keep-Alieve

message processing.
ZXR10#debug ip bgp updates Tracks and displays BGP Update

message processing. Information about
Update message processing related to a
certain peer can be tracked and printed.
ZXR10#debug ip bgp events Tracks and displays the transition events

of the state machine connected to BGP.
ZXR10#show debug bgp Displays debug command configuration

information.
End of Steps
8.3 BGP4+ Configuration Instances

8.3.1 Example: Configuring a BGP4+ Route Reflector
In a network as shown in Figure 8-1, routers R1, R2, and R3 are Interior Border Gateway
Protocol (IBGP)-based but not fully meshed. To eliminate full meshing for IBGP, a route
reflector can be configured so that R3 can forward the routes it receives from an IBGP
neighbor to another IBGP neighbor. Considering that the routers with IBGP are not fully
meshed in AS 200, a route reflector can be configured to avoid full meshing.
8-3

Figure 8-1 BGP4+ Route Reflector Configuration Example
Configuration Flow
1. Enable IPv6 on each interface in accordance with the networking diagram, and
configure IPv6 addresses.
2. Enable BGP.
3. Specify neighbors.
4. Configure a route reflector cluster ID. Set the neighbors as route reflector clients.
The IPv6 interface address configuration is omitted in this example.
R1(config)#router bgp 200
R1(config-bgp)#neighbor 3fe6::1 remote-as 100
R1(config-bgp)#neighbor 2010::126 remote-as 200
R1(config-bgp)#address-family ipv6
R1(config-bgp-af-ipv6)#neighbor 3fe6::1 activate
R1(config-bgp-af-ipv6)#neighbor 2010::126 activate
R1(config-bgp-af-ipv6)#end
R2(config-bgp)#neighbor 6e22::1 remote-as 500
R2(config-bgp-af-ipv6)#neighbor 6e22::1 activate
8-4


R3(config-bgp-af-ipv6)#neighbor 2010::125 route-reflector-client
/*Configure the route reflector*/
R3(config-bgp-af-ipv6)#neighbor 3331::101 route-reflector-client
8.3.2 Example: Configuring BGP4+ Route Load Sharing

Load sharing is a method to evenly distribute traffic that exceeds the bandwidth of an
interface to multiple links to achieve load balancing of traffic on each link.
As shown in Figure 8-2, load sharing is enabled for BGP4+ if multiple links in the same
area can reach the same neighbor node with the same link cost.
Figure 8-2 BGP4+ Route Load-Sharing Configuration Example
Configuration Flow
1. On R1 and R2, enable IPv6 on each interface, and configure IPv6 addresses.
Configure per-packet load sharing (default: per-flow load sharing). On R2, configure
the IPv6 address for the loopback1 interface, and enable IPv6.
2. Enable and configure BGP4+.
3. Configure BGP4+ load sharing on R1.
8-5


R1(config-bgp-af-ipv6)#maximum-paths ibgp 16 /*Configure load sharing.*/

R2(config-bgp-af-ipv6)#network 2000:0:0:1::2/128
Run the show command to verify the configuration result, showing that the IBGP route has
been learned on R1:
R1#show ipv6 forwarding route bgp

IPv6 Routing Table:
8-6


Dest Owner Metric
Interface Pri Gw
2000:0:0:1::/64 B 0
gei-2/1 20 fe80:12::1
2000:0:0:1::/64 B 0
gei-2/2 20 fe80:16::1
8.3.3 Example: Configuring BGP4+

This example describes how to configure BGP4+. It involves the practical use of BGP4+,
such as IBGP/EBGP neighbor establishment, routing policy, route redistribution, and
Message Digest 5 Algorithm (MD5) encryption.
As shown in Figure 8-3, EBGP neighbors are established between R4 and R1, IBGP
neighbors are established between R1 and R2, and multi-hop EBGP neighbors are
established between R2 and R5. R2 and R5 establish an EBGP multi-hop relation
through R3. Before BGP is configured, it is necessary to ensure that the addresses used
for neighbor establishment between the two routers can interwork with each other (via
IGP; IGP configuration is omitted in this example).
Figure 8-3 BGP4+ General Configuration Example
Configuration Flow
1. Enable IPv6 on each interface and configure IPv6 addresses.
2. Create a BGP4+ instance.
3. Configure BGP4+ neighbors and routing policies.
4. Configure the redistribution command and enable neighbors to advertise routes.
8-7

The IPv6 interface address configuration is omitted in this example. For the detailed
configuration, refer to Example: Configuring BGP4+ Route Load Sharing.
R4(config-bgp-af-ipv6)#redistribute static
/*config redistribute static route*/
R2(config-bgp)#neighbor 2007::5 ebgp-multihop /*config ebgp-multihop*/
R2(config-bgp)#neighbor 2007::5 password hello /*config password*/
R3(config-bgp)#neighbor 2005::2 ebgp-multihop
R3(config-bgp)#neighbor 2005::2 password hello
Run the show bgp ipv6 unicast summary command on R1 to check the adjacency, as shown
below.
8-8

ZXR10_R1(config)#show bgp ipv6 unicast summary

Neighbor Ver As MsgRcvd MsgSend Up/Down State/PfxRcd
2003::2 4 1 12 12 00:25:34 0
2001::4 4 2 14 14 00:28:06 4
Run the show bgp ipv6 unicast command on R1 to check the routing table, as shown below.
R1(config)#show bgp ipv6 unicast

Status codes: * valid, > best, i - internal, s - stale
Origin codes: i-IGP, e-EGP, ?-incomplete
Network Next Hop Metric LocPrf RtPrf Path
*> 2004:1::/64 2001::4/64 2 ?
*> 2004:2::/64 2001::4/64 2 ?
*> 2004:3::/64 2001::4/64 2 ?
*> 2004:4::/64 2001::4/64 2 ?
below.
2003::1 4 1 12 12 00:25:34 4
2007::5 4 3 15 15 00:32:30 0

*> 2004:1::/64 2003::1/64 100 2 ?
*> 2004:2::/64 2003::1/64 100 2 ?
*> 2004:3::/64 2003::1/64 100 2 ?
*> 2004:4::/64 2003::1/64 100 2 ?
below.
2001::1 4 1 14 14 00:28:06 0

*> 2004:1::/64 :: 2 ?
*> 2004:2::/64 :: 2 ?
*> 2004:3::/64 :: 2 ?
8-9

*> 2004:4::/64 :: 2 ?
below.

2005::2 4 1 15 15 00:32:30 4

*> 2004:1::/64 2005::2/64 1 2 ?
*> 2004:2::/64 2005::2/64 1 2 ?
*> 2004:3::/64 2005::2/64 1 2 ?
*> 2004:4::/64 2005::2/64 1 2 ?
8-10

Chapter 9
IPv6 Route-Map Policy
Configuration
The IPv6 Router-Map provides IPv6 on the basis of the IPv4 Router-Map. For a brief
description of the Router-Map, see the Router-Map Overview section in the ZXR10 ZSR
V2 (V2.00.10) Configuration Guide (Policy Template).
Table of Contents
IPv6 Routing Policy Configuration ..............................................................................9-1
IPv6 Policy Route Configuration ...............................................................................9-30
9.1 IPv6 Routing Policy Configuration

IPv6 has the same routing policy as IPv4. For the detailed concepts and principles, refer
to the Routing Policy Overview section in the ZXR10 ZSR V2 (V2.00.10) Configuration
Guide (Policy Template).
9.1.1 Configuring the IPv6 Routing Policy

This procedure describes how to configure the IPv6 routing policy, including basic
attributes, route attributes, and how the policy is invoked in a routing protocol.
Steps
1. In route-map configuration mode, configure the basic attributes of the IPv6 routing
policy.
Step Command Description
1 ZXR10(config)#route-map <route-map-name>[permit | Creates a route map for policy

deny][<sequence-number> routing, and enters route-map
configuration mode.
9-1

2 ZXR10(config-route-map)#match ipv6 address Matches the IPv6 address that

*(<access-list-name>) is permitted by a standard or an
extended access list.
ZXR10(config-route-map)#match ipv6 metric Matches the specified

*(<metric-value>) metric value(s), range: 0 to
4294967295.
ZXR10(config-route-map)#match ipv6 tag Matches the specified tag

*(<tag-value>) value(s), for the OSPF protocol
and static routes only, range: 0
to 4294967295.
ZXR10(config-route-map)#match as-path *(<as-path Matches the specified BGP

list number>) autonomous system (AS) path
access list(s), range: 1 to 199.
ZXR10(config-route-map)#match community-list Matches the specified BGP

*(<community-list-number>) community list(s), range: 1 to
499.
ZXR10(config-route-map)#match extcommunity-list Matches the specified BGP/VPN

*(<community-list-number>) extended community list(s),
range: 1 to 500.
ZXR10(config-route-map)#match route-type Matches the specified route

{external [type-1 | type-2]| internal | level-1 | level-2 | type.
local}
<route-map-name>: Defines a meaningful name for the route map, 1 to 31 characters

in length.
permit | deny: permit: If the match criterion is met for this route map, and the permit
keyword is specified, the route is distributed based on the specified policy routing
actions. deny: No policy routing actions are performed regardless whether the match
criterion is met.
<sequence-number>: Sequence ID of the route-map. Each route-map supports one or
more sequence numbers. All routes are matched according to the specified sequence
number(s) in an ascending order. Once a match is found, whether policy routing should
be performed depends on the sequence attribute.
<access-list-number>: Sets a standard access list or an extended access list.
2. Configure the route attributes in the routing policy.
Command Description
ZXR10(config-route-map)#set as-path prepend Sets the autonomous system

*(<as-number>) path(s) for the BGP routes.
9-2

Chapter 9 IPv6 Route-Map Policy Configuration
Command Description
ZXR10(config-route-map)#set community {none | Sets the BGP community attribute.

additive*{no-advertise | no-export | no-export-subconfed |
internet |<0-65535>:<0-65535>|<1-4294967295>})}
ZXR10(config-route-map)#set extcommunity rt-trans Sets the BGP extended community

{{remove | additive *{<0-65535>:<0-4294967295>|<1-655 attribute.
35>.<0-65535>:<0-65535>| A.B.C.D:<0-65535>}}|{<0-65
535>:<0-4294967295>|<1-65535>.<0-65535>:<0-65535>|
A.B.C.D:<0-65535>})}
ZXR10(config-route-map)#set extcommulity soo-trans {<0 Sets the BGP extended community

-65535>:<0-4294967295>|<1-65535>.<0-65535>:<0-65535>| attribute.
A.B.C.D:<0-65535>| remove}
ZXR10(config-route-map)#set dampening Sets the BGP route dampening

<half-life><reuse><suppress><max-suppress-time> factors.
ZXR10(config-route-map)#set local-preference <value> Sets the BGP local-preference

attribute.
ZXR10(config-route-map)#set origin {igp | egp | Sets the BGP origin code.

incomplete}
ZXR10(config-route-map)#set level <level-value> Set the IS-IS route attribute.
ZXR10(config-route-map)#set next-hop <ip-address>[<i Specifies the address of the next

p-address>] hop.
ZXR10(config-route-map)#set ipv6 metric Sets a metric value for the IPv6

[+|-]<metric-value> protocol.
ZXR10(config-route-map)#set ipv6 next-hop Sets the next hop of the route to

*(<ipv6-address>) an IPv6 address.
*(<ipv6-address>): IPv6 address
of the next hop, in dot-separated,
hexadecimal format. Up to ten
IPv6 addresses are supported.
ZXR10(config-route-map)#set ipv6 precedence Sets the priority of an IPv6 header.

{<precedence-value>|<precedence-value>} <precedence-value>: sets the serial
number of priority in the IP header,
range: 07.
ZXR10(config-route-map)#set ipv6 traffic-class Sets the traffic class of an IPv6

<traffic-value> route. Run the no command to
cancel the configuration.
<traffic-value>: traffic class of IPv6
routes, range: 0255.
9-3

Command Description
ZXR10(config-route-map)#set ipv6 path interface When a packet matches the routing

<interface> next-hop <nexthop> policy, run this command to route
the packet to the specified Ethernet
interface and the next hop.
ZXR10(config-route-map)#set ipv6 metric-type {internal | Sets a metric type for the IPv6
external | type-1 | type-2} protocol.
ZXR10(config-route-map)#set ipv6 tag <tag-value> Sets a tag value for the OSPF
protocol or a static route.
<half-life>: Sets the half-life period of the routing damping factors, range: 1 to 45.
<reuse>: Sets the reuse value of the routing damping factors, range: 1 to 20000.
<suppress>: Sets the suppress value of the routing damping factors, range: 1 to 20000.
<max-suppress-time>: Sets the maximum suppress time of the routing damping factors,
range: 1 to 255. The penalty value stops increasing if max-suppress-time is reached.
3. Configure RIPng routing policy referencing.
1 ZXR10(config)#ipv6 router rip Enters the RIPng configuration

mode.
2 ZXR10(config-rip)#redistribute <protocol>[p Redistributes RIPng routes.

rocess-id][metric <metric-value>][route-map
<route-map-name>]
<protocol>: The protocol for which route redistribution is to be performed. Options:

bgp, connected, isis, ospf, static, aftr, sf-nat64, sl-nat64, subscriber-host.
<metric-value>: The metric value, range: 0 to 16.
<route-map-name>: Name of the route map for route redistribution, range: 1 to 31.
4. Configure IS-ISv6 routing policy referencing.
1 ZXR10(config)#router isis <process-id>[vrf <vrf-name>] Enters the IS-IS route

configuration mode.
2 ZXR10(config-isis-id)#address-family ipv6 Enters the IS-ISv6 address

family configuration mode.
3 ZXR10(config-isis-id-af)#redistribute <protoco Redistributes IS-IS routes.

l>[process-id][level-1][level-1-2][level-2][metric-type
<metric-type>][metric <metric-value>][route-map
<route-map-name>]
9-4

4 ZXR10(config-isis-id-af)#router-leak level-2 into Configures route leaking.

level-1 route-map <route-map-name>
<protocol>: Specifies the routing source, required. Options: bgp, connected, isis, ospf,
static, rip. To redistribute IS-IS or OSPF routes, the corresponding process ID should
be specified.
level-1: Redistributes routes to the Level-1 area.
level-1-2: Redistributes routes to the Level-1 and Level-2 areas.
level-2: Redistributes routes to the Level-2 area.
<metric-type>: Sets the metric type (external or internal) carried by the redistributed
routes.
<metric-value>: Sets a metric value, range: 0 to 4261412864.

route-map <route-map-name>: Name of the route-map for route redistribution.
5. Configure OSPFv3 routing policy referencing.
1 ZXR10(config-ospfv3-id)#redistribute bgp Redistributes BGP routes based

route-map <route-map-name> on the specified route-map.
2 ZXR10(config-ospfv3-id)#redistribute connected Redistributes directly-connected

route-map <route-map-name> routes based on the specified
route-map.
3 ZXR10(config-ospfv3-id)#redistribute isis Redistributes IS-IS routes based

<process-id> route-map <route-map-name> on the specified route-map.
4 ZXR10(config-ospfv3-id)#redistribute rip route-map Redistributes RIP routes based

<route-map-name> on the specified route-map.
5 ZXR10(config-ospfv3-id)#redistribute static Redistributes static routes

route-map <route-map-name> based on the specified
route-map.
6. Configure BGP4+ routing policy referencing.
1 ZXR10(config)#router bgp {<1~65535>|<1~65535>. Enters the BGP route

<0~65535>} configuration mode.
2 ZXR10(config-bgp)#bgp dampening [ route-map Enables BGP route dampening

<route-map-name>] or modifies its factors.
9-5

3 ZXR10(config-bgp)#neighbor [<ipv6-address>|<peer-g Filters the routes to/from the

roup-name>] route-map <route-map-name>{in | out} specified peer or its peer group,
or sets the route priorities.
in | out refers to applying the
rule to inbound or outbound
routes respectively.
4 ZXR10(config-bgp)#address-family ipv6 Enters the BGP4+ address

5 ZXR10(config-bgp-af)#redistribute <protocol>[proce Redistributes routes of the

ss-id][route-map <route-map-name>] specified type into BGP.
<protocol> refers to the protocol
type. For the OSPF or ISIS
protocol, the corresponding
process ID should be specified.
7. Configure VRF routing policy referencing.
1 ZXR10(config)#ip vrf <vrf-name> Creates a Virtual Route and

Forwarding (VRF).
2 ZXR10(config-vrf-name)#rd <route-distinguisher> Configures a Route

Distinguisher (RD).
3 ZXR10(config-vrf-name)#route-target [import | Creates a route-target extended

export | both]<extended-community> community attribute for a VRF.
4 ZXR10(config-vrf-name)#address-family ipv6 Activates the IPv6 VRF address

family.
5 ZXR10(config-vrf-name-af-ipv6)#import map Configures an import route map

<route-map-name> for a VRF.
ZXR10(config-vrf-name-af-ipv6)#export map Configures an export route map

<route-map-name> for a VRF.
Command Description
ZXR10(config)#show running-config Displays the RIPNG protocol configuration.

ripng
ZXR10(config)#show running-config isis Displays the ISIS protocol configuration.
ZXR10(config)#show running-config Displays the OSPF protocol configuration.

ospfv3
ZXR10(config)#show running-config bgp Displays the BGP protocol configuration.
9-6

Command Description
ZXR10(config)#show running-config vrf Displays the VRF route configuration.
ZXR10(config)#show ip vrf detail Displays the VRF configuration. You can specify a
[<vrf-name>] VRF instance, and query its configuration.
ZXR10(config)#show route-map Displays the route-map configuration.

[<route-map-name>]
End of Steps
9.1.2 IPv6 Routing Policy Configuration Instances

9.1.2.1 Example: Configuring a Routing Policy for Redistributing RIPng Routes
Both R1 and R2 run the Routing Information Protocol (RIP), see Figure 9-1. This enables
their RIPng routes to be advertised to each other, and other types of routes to be
redistributed. The following shows an example of redistributing static routes.
Figure 9-1 An Example of Configuring a Routing Policy for Redistributing RIPng Routes
Configuration Flow
1. Enable IPv6 and set IPv6 addresses on the corresponding interfaces of R1 and R2.
2. Enable the RIPng protocol configuration on the interfaces.
3. Redistribute other types of routes, and create a redistribution command.
4. Associate the redistribution command with a route-map.
5. Set the route-map.
6. Query the configuration result, and verify that R1 and R2 can learn routes that the peer
advertises.
R1(config-if-gei-1/2)#ipv6 address 192:168::1:1/64
9-7

R1(config)#route-map www permit 10

R1(config-route-map)#set ipv6 metric 10
R1(config-route-map)#exit

R1(config-ripng)#redistribute static route-map www
R1(config)#ipv6 route 1:2:3::0/64 192:168::1:2

R2(config-ripng-if-gei-2/2)#end
Run the show command on R1 and R2 respectively to query the configuration of the RIP
protocol, route-map and static routes, RIP routing table and routing information.
The sample output on R1 is as follows.

! <ripng>
ipv6 router rip
redistribute static route-map www
interface gei-1/2
ipv6 rip enable
$
$
! </ripng>
R1#show running-config ipv6-static

! <ipv6-static>
ipv6 route 1:2:3::/64 192:168::1:2
! </ipv6-static>
9-8

R1#show running-config route-map

! <route-map>
route-map www permit 10
set ip metric 10
$
!</route-map>

1:2:3::/64
metric: 10, tag: 0
192:168::/64
metric: 1, tag: 0
The sample output on R2 is as follows.

! <ripng>
ipv6 router rip
interface gei-2/2
ipv6 rip enable
$
$
! </ripng>

1:2:3::/64
nexthop: fe80::221:1dff:fe1d:1100, via: gei-2/2
metric: 11, tag: 0, time: 00:13
192:168::/64
metric: 1, tag: 0
R2#show ipv6 protocol routing

IPv6 Routing Table
Codes: D - Direct, A - Address, S - Static, R - RIP, UI - USER_IPADDR,
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS static,
O - OSPF intra, OI - OSPF inter, E1 - OSPF ext 1, E2 - OSPF ext 2, N - ND,
B - BGP, IB - IBGP, EB - EBGP, AG - BGP AGG, V - VRRP, P - PPP, D6 - DHCPv6,
SFN - Stateful NAT64, SLN - Stateless NAT64, AF - AFTR
Time: The time of last modified!
R 1:2:3::/64 [120/11]
via fe80::221:1dff:fe1d:1100, gei-2/2, 06h39m58s
D 192:168::/64
9-9

via , gei-2/2, 03h42m55s

A 192:168::1:2/128
via , gei-2/2, 03h42m55s
9.1.2.2 Example: Configuring an IS-ISv6 Routing Policy
An IS-ISv6 neighbor relationship (status: up) is established between R1 and R2, see
Figure 9-2. Static routes are configured on R1, and a route-map is created for IS-ISv6
route redistribution.
Figure 9-2 An Example of Configuring an IS-ISv6 Routing Policy
Configuration Flow
2. Create a neighbor relationship by configuring the IS-ISv6 protocol on R1 and R2.
3. Create route-map testisisv6 on R1.
4. Configure route redistribution on R1.
5. Apply a route-map to static route redistribution.
1. Configure a neighbor relationship between R1 and R2.
Configure IS-ISv6 on R1.
R1(config)#router isis 44
9-10

Configure IS-ISv6 on R2.

R2(config-isis-44-if-gei-2/2)exit
2. Create route-map testisisv6 on R1.
R1(config)#route-map testisisv6 permit 10
3. Configure static routes on R1.
R1(config)#ipv6 route 1:2:3::/64 192:168::1:2
4. Apply the route-map to static route redistribution.
R1(config-isis-44-af)#redistribute static route-map testisisv6
R1(config-isis-44)#exit
The sample output is as follows.
R1(config)#show running-config isis

! <route_isis>
router isis 44
area 44
system-id 5555.5555.5555
is-type level-1-2
metric-style wide
address-family ipv6
multi-topology
redistribute static route-map testisisv6
interface gei-1/2
9-11

ipv6 router isis

$
$
</route_isis>
R2(config)#show running-config isis
! <route_isis>
router isis 44
area 44
system-id 2222.2222.2222
is-type level-1-2
metric-style wide
address-family ipv6
multi-topology
$
interface gei-2/2
ipv6 router isis
$
$
</route_isis>
The route-map configuration is as follows.

R1(config)#show route-map testisisv6
[route-map testisisv6] IP type: IPv6
route-map testisisv6 permit 10
set ipv6 metric 10
The static route configuration is as follows.

R1(config)#show ipv6 forwarding route static
IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1:2:3::/64 S 0
gei-1/2 1 192:168::1:2
On R2, check the IS-ISv6 routing information that is advertised by R1.

R2(config)#show ipv6 protocol routing isis
IPv6 Routing Table
9-12

M - Multicast
* - FIB route
> - selected route, p - stale info
I2 1:2:3::/64 [115/20]
I1 192:168::/64 [115/20]
9.1.2.3 Example: Configuring an OSPFv3 Routing Policy
Both R1 and R2s interfaces are configured in OSPFv3 area 1, and an OSPFv3 neighbor
relationship (status: full) is established between them, see Figure 9-3. A static route is
configured on R1, and a route-map is created for OSPFv3 static route redistribution.
Figure 9-3 An Example of Configuring an OSPFv3 Routing Policy
Configuration Flow
2. Create a neighbor relationship between R1 and R2 in OSPFv3 area 1.
3. Create a route-map on R1.
4. Configure a static route on R1.
5. Apply the route-map to OSPFv3 route redistribution on R1.
1. Create an OSPFv3 neighbor relationship by configuring the directly-connected
interfaces of R1 and R2 to be on the same network segment.
9-13

2. Create a route-map on R1.
R1(config)#route-map ff
R1(config-route-map)#match ipv6 metric 0
R1(config-route-map)#set ipv6 metric-type type-1
R1(config-route-map)#set ipv6 tag 100
3. Configure a static route on R1.
R1(config)#ipv6 route 1:2:3::/64 192:168::1:2
4. On R1, apply the route map to OSPF route redistribution.
R1(config-ospfv3-1026)#redistribute static route-map ff
R1(config-ospfv3-1026)#end
Log in to R1, and run the following commands to check the configuration, static route and
OSPF routes.
R1#show route-map ff
[route-map ff] IP type: IPv6

route-map ff permit 10
match ipv6 metric 0
set ipv6 metric-type type-1
set ipv6 metric 50
set ipv6 tag 100

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1:2:3::/64 S 0
gei-1/2 1 192:168::1:2
9-14

R1#show running-config | begin ipv6 router ospf 1026

ipv6 router ospf 1026
router-id 11.11.11.11
redistribute static route-map ff
$
$
!</ospfv3>
R1#show ipv6 ospf database process 1026
OSPFv3 Router with ID (11.11.11.11) (Process ID 1026)
Router Link States (Area 0.0.0.1)
ADV Router Age Seq# Link count Bits

11.11.11.11 997 0x80000006 1 -|-|E|-
22.22.22.22 1246 0x80000005 1 -|-|-|-
Net Link States (Area 0.0.0.1)
ADV Router Age Seq# Link ID Rtr count

22.22.22.22 997 0x80000006 22 2
Intra Area Prefix Link States (Area 0.0.0.1)
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID

22.22.22.22 1248 0x80000004 2 0x2002 22
Link (Type-8) Link States (Area 0.0.0.1)
ADV Router Age Seq# Link ID Interface

11.11.11.11 1643 0x80000004 22 gei-1/2
22.22.22.22 1256 0x80000004 27 gei-1/2
Type-5 AS External Link States
ADV Router Age Seq# Prefix

11.11.11.11 996 0x80000001 1:2:3::/64
/*Check the tag attributes.*/
R1#show ipv6 ospf database external
OSPFv3 Router with ID (11.11.11.11) (Process ID 1026)

Type-5 AS External Link States
9-15

LS age: 109
LS Type: AS-external-LSA
Link State ID: 0.0.0.13
Advertising Router: 11.11.11.11
LS Seq Number: 0x80000001
Checksum: 0xD1E9
Length: 48
Metric Type: 1 (Larger than any link state path)
Metric: 50
Prefix: 1234::1/128
Prefix Options: 0 (-|-|-|-)
External Route Tag: 100
Log in to R2, and check the OSPFv3 routing attributes.

R2#show ipv6 protocol routing ospf
IPv6 Routing Table
M - Multicast
* - FIB route
> - selected route, p - stale info
E1 1:2:3::/64 [110/51]
O 192:168::/64 [110/1]
via ::, gei-2/2, 07h19m08s
9.1.2.4 Example: Configuring a BGP4+ Routing Policy
An EBGP neighbor relationship is established between R1 and R2, and an IBGP neighbor
relationship is established between R2 and R3, see Figure 9-4. R1 advertises its routes
to R2. Configure route-map test1 on R2, and apply it to the in direction of R2s interface
connecting to R1. Configure route-map test2 on R2, and apply it to the out direction of
R2s interface connecting to R3.
Figure 9-4 An Example of Configuring a BGP4+ Routing Policy
9-16

Configuration Flow
1. Enable IPv6 and set IPv6 addresses on the corresponding interfaces of R1, R2 and
R3.
2. Create an EBGP neighbor relationship between R1 and R2, and create an IBGP neigh-
bor relationship between R2 and R3.
3. R1 advertises its several BGP4+ routes to R2. If R2 and R3 can learn these routes,
proceed to 3.
4. Configure ipv6-access-list 1, ipv6-access-list 2, route-map test1 and route-map test2
on R2
5. Apply route-map test1 to the in direction of R2s interface connecting to R1, and apply
route-map test2 to the out direction of R2s interface connecting to R3.
Note:
The route-map can be used by incoming interface and outgoing interface. Other attributes
are effective except the attribute of next-hop.
For a BGP4+ route-map, the specific attributes are as follows:

l set: community-list, dampening, local-preference, origin, as-path and next-hop.
l Match: as-path and community-list.
1. Create an EBGP neighbor relationship by configuring the directly-connected interfaces
between R1, R2, and R3.
R1(config-if-gei-1/3)#ipv6 address 1:2::1/64
R1(config-bgp)#neighbor 1:2::2 remote-as 200
R1(config-bgp-af-ipv6)#neighbor 1:2::2 activate
R1(config-bgp-af-ipv6)#exit
R1(config-bgp)#exit
9-17


R2(config-bgp)#exit

R3(config-bgp)#exit
2. Run the following commands to advertise five BGP routes from R1 to R2.
R1(config-bgp-af-ipv6)#network 4:4::4/64
R1(config-bgp)#exit
3. Configure route-map test1 and ACLs on R2.
R2(config)#ipv6-access-list 1
R2(config-ipv6-acl)#rule 1 permit ipv6 4:4::/64 any
R2(config-ipv6-acl)#exit
R2(config)#ipv6-access-list 2
9-18

R2(config-ipv6-acl)#rule 1 permit ipv6 7:7::/64 any

R2(config)#route-map test1 permit 10

R2(config-route-map)#match ipv6 address 1
R2(config-route-map)# set local-preference 30000
R2(config-route-map)#match ipv6 metric 5
R2(config-route-map)#match as-path 1
R2(config-route-map)#match community-list 1
R2(config-route-map)#set as-path prepend 2
R2(config-route-map)#set local-preference 200
R2(config-route-map)#set origin incomplete
4. Apply route-map test1 to the in direction of R2s interface connecting to R1, and apply
route-map test2 to the out direction of R2s interface connecting to R3.
R2(config-bgp-af-ipv6)#neighbor 1:2::1 route-map test1 in
R2(config-bgp-af-ipv6)#neighbor 2:3::3 route-map test2 out
After R1 advertises its five routes, run the following commands to verify that R2 and R3
can learn these routes.
R2#show bgp ipv6 unicast

Origin codes: i - IGP, e - EGP, ? - incomplete
*> 4:4::/64 1:2::1 20 1011 i
*> 5:5::/64 1:2::1 20 1011 i
*> 6:6::/64 1:2::1 20 1011 i
*> 7:7::/64 1:2::1 20 1011 i
*> 8:8::/64 1:2::1 20 1011 i
R3#show bgp ipv6 unicast

9-19


i4:4::/64 1:2::1 100 200 1011 i
i5:5::/64 1:2::1 100 200 1011 i
i6:6::/64 1:2::1 100 200 1011 i
i7:7::/64 1:2::1 100 200 1011 i
i8:8::/64 1:2::1 100 200 1011 i
Verify that R2 can only learn routes 4:4:::/64 and 7:7::/64 permitted in route-map test1.
The logical relationships between match items in a routing policy is AND. If route-map
test2 permit 10 is not matched, route 4:4:::/64 cannot be advertised to R3.
After the BGP routing policy is enabled, the sample output is as follows.
R2(config)#show bgp ipv6 unicast /*R2 learns two BGP routes from R1*/
*> 4:4::/64 1:2::1 30000 20 1011 i
*> 7:7::/64 1:2::1 30000 20 1011 i
The detailed information about the two BGP routes is as follows.
R2#show bgp ipv6 unicast detail 4:4::/64

BGP routing table entry for 4:4::/64
08:50:07 received from 1:2::1 (11.1.1.1)
origin i, global nexthop 1:2::1, link-local nexthop FE80::220:23FF:FE1D:E0E,
localpref 30000 rtpref 20
as path [1011]
as4 path
R2#show bgp ipv6 unicast detail 7:7::/64
BGP routing table entry for 7:7::/64
08:50:07 received from 1:2::1 (11.1.1.1)
origin i, global nexthop 1:2::1, link-local nexthop FE80::220:23FF:FE1D:E0E,
localpref 30000 rtpref 20
as path [1011]
as4 path
08:41:38 advertised to 2:3::3 (1.1.1.1)
origin ?, global nexthop 1:2::1, localpref 200
as path [2 1011]
as4 path
9.1.2.5 Example: Configuring a Routing Policy for 6VPE
Figure 9-5 shows a basic L3VPN networking topology. An MP-IBGP neighbor relationship
is established between PE1 and PE2 that are in the same AS. VRF test1 that resides
on PE1 advertises the Address routes generated by the local Loopback address and
9-20

directly-connected routes to peer CE1. VRF test1 that resides on PE2 advertises the
Address routes generated by the local Loopback address and directly-connected routes
to peer CE2. The VRF test1 routing table on PE1 and PE2 contains the local and remote
routes.
The route-map, used for VRF test1 on PE1, allows PE1 to import or export routes from/to
its VPN neighbor.
Figure 9-5 An Example of Configuring a Routing Policy for 6VPE
Table 9-1 lists an IP address planning.
Table 9-1 IP Address Planning
Equipment Interface IP Address
CE1 gei-1/1 1001::20:2/120
PE1 gei-1/2 1001::20:1/120
gei-1/3 10.10.12.1/24
PE2 gei-1/6 10.10.12.2/24
gei-1/7.10 2002::20:2/120
CE2 gei-1/8.10 2002::20:1/120
Configuration Flow
1. Configure the basic L3VPN networking environment (CE1PE1PE2CE2), enable
IPv6 and set IPv6 addresses on the corresponding interfaces of the routers.
2. Configure the protocol, and make sure that the private routing tables on two PEs
contain all planned routes.
3. Create a route-map on PE1, and define the characteristics of the routes for which
policy routing is performed (that is, defining a group of match criteria). Various route
attributes, such as destination address, can be grouped as a match rule.
4. Apply the route-map to a VRF instance on PE1 to implement route importing/exporting,
route publishing and receiving.
1. Configure the basic L3VPN networking environment on PE1 and PE2.
Configuration on PE1:
PE1(config)#ip vrf test1
PE1(config-vrf-test1)#rd 100:1
PE1(config-vrf-test1)#address-family ipv6
PE1(config-vrf-test1-af-ipv6)#route-target import 100:1
9-21

PE1(config-vrf-test1-af-ipv6)#route-target export 100:1

PE1(config-vrf-test1-af-ipv6)#exit
PE1(config-vrf-test1)#exit
PE1(config)#interface loopback1
PE1(config-if-loopback1)#ip address 10.10.1.1 255.255.255.255
PE1(config-if-loopback1)#exit
PE1(config)#interface gei-1/3
PE1(config-if-gei-1/3)#no shutdown
PE1(config-if-gei-1/3)#ip address 10.10.12.1 255.255.255.0
PE1(config-if-gei-1/3)#exit
PE1(config)#mpls ldp instance 1
PE1(config-ldp-1)#route-id loopback1
PE1(config-ldp-1)#interface gei-1/3
PE1(config-ldp-1-if-gei-1/3)#exit
PE1(config-ldp-1)#exit
PE1(config-if-gei-1/2)#ip vrf forwarding test1
PE1(config-if-gei-1/2)#ipv6 enable
PE1(config-if-gei-1/2)#ipv6 address 1001::20:1/120
PE1(config)#router ospf 1
PE1(config-ospf-1)#network 10.0.0.0 0.255.255.255 area 0.0.0.0
PE1(config-ospf-1)#exit
PE1(config)#ipv6 router ospf 1 vrf test1
PE1(config-ospfv3-1)#router-id 10.10.1.1
PE1(config-ospfv3-1)#interface gei-1/2 area 0.0.0.0
PE1(config-ospfv3-if-gei-1/2)#exit
PE1(config-ospfv3-1)#redistribute bgp
PE1(config-ospfv3-1)#exit
PE1(config)#router bgp 100

PE1(config-bgp)#neighbor 10.10.3.3 remote-as 100
PE1(config-bgp)#neighbor 10.10.3.3 update-source loopback1
PE1(config-bgp)#address-family ipv6 vrf test1
PE1(config-bgp-af-ipv6-vrf)#redistribute connected
PE1(config-bgp-af-ipv6-vrf)#exit
PE1(config-bgp)#address-family vpnv6
PE1(config-bgp-af-vpnv6)#neighbor 10.10.3.3 activate
PE1(config-bgp-af-vpnv6)#exit
PE1(config-bgp)#exit
9-22

PE1(config-ldp-1)#router-id loopback1

PE2(config)#interface gei-1/7.10
PE2(config-if-gei-1/7.10)#exit
PE2(config)#vlan-configuration
PE2(config-vlan)#interface gei-1/7.10
PE2(config-vlan-if-gei-1/7.10)#encapsulation-dot1q 10
PE2(config-vlan-if-gei-1/7.10)#exit
PE2(config-vlan)#exit
PE2(config- if-gei-1/7.10)#ip vrf forwarding test1
PE2(config- if-gei-1/7.10)#ipv6 enable
PE2(config- if-gei-1/7.10)#ipv6 address 2002::20:2/120
PE2(config- if-gei-1/7.10)#exit
9-23


PE2(config-ospfv3-1)#interface gei-1/7.10 area 0.0.0.0
PE2(config-ospfv3-1- gei-1/7.10)#exit

PE2(config-bgp-af-ipv6-vrf)#redistribute ospf-int 1
PE2(config-bgp-vpnv6)#exit
2. Check the VRF routes on PE1 and PE2.
The sample output on PE1 is as follows:
PE1#show ipv6 protocol routing vrf test1

Vrf test1 IPv6 Routing Table
IB 22::/64 [200/0]
via ::ffff:10.10.3.3, loopback1, IPv6-mpls, 09h03m49s
D 33::/64
via ::, loopback33, 07h10m49s
A 33::33/128
D 1001::20:0/120
A 1001::20:2/128
IB 2002::20:0/120 [200/0]
via ::ffff:10.10.3.3, loopback1, IPv6-mpls, 08h33h41s
The sample output on PE2 is as follows:
9-24


D 22::/64
A 22::1/128
IB 33::/64 [200/0]
IB 1001::20:0/120 [200/0]
D 2002::20:0/120
via ::, gei-1/10.1, 06h22m11s
A 2002::20:2/128
via ::, gei-1/10.1, 06h22m11s
3. Create a route-map on PE1, and apply it to VRF.
Create route-map test1 for restricting exporting routes.
PE1(config)#ipv6-access-list test1
PE1(config-ipv6-acl)#rule 1 permit ipv6 1001::20:0/120 any
PE1(config-ipv6-acl)#exit
PE1(config)#route-map test1
PE1(config-route-map)#match ipv6 address test1
PE1(config-route-map)#exit
Create route-map test2 for restricting importing routes.

PE1(config)#ipv6-access-list test2
PE1(config-ipv6-acl)#rule 1 permit ipv6 2002::20:0/120 any
PE1(config-ipv6-acl)#exit
PE1(config)#route-map test2
PE1(config-route-map)#match ipv6 address test2
PE1(config-route-map)#exit
Apply the route-maps to vrf test1.

PE1(config-vrf-test1-af-ipv6)#export map test1
PE1(config-vrf-test1-af-ipv6)#import map test2
4. Check the VRF routing table on PE1 and PE2, and verify that the routing policy has
been enabled.
9-25

Run the following command on PE1.

D 33::/64
A 33::33/128
D 1001::20:0/120
A 1001::20:2/128
IB 2002::20:0/120 [200/0]
Run the following command on PE2.

D 22::/64
A 22::1/128
IB 1001::20:0/120 [200/0]
D 2002::20:0/120
via ::, gei-1/10.1, 00h22m27s
A 2002::20:2/128
via ::, gei-1/10.1, 00h22m27s
Run the show running-config command, and the following sample output is displayed.
9-26

PE1#show running-config bgp

! <route-bgp>
router bgp 100
synchronization disable
neighbor 10.10.3.3 remote-as 100
neighbor 10.10.3.3 activate
neighbor 10.10.3.3 update-source loopback1

address-family ipv6 vrf test1
$
address-family vpnv6
$

$
! </route-bgp>
PE1#show running-config vrf

! <vrf>
ip vrf test1
rd 100:1
address-family ipv6
route-target import 100:1
route-target export 100:1
import map test2
export map test1
$
$
! </vrf>
PE1#show route-map test1
[route-map test1] IP type: IPv6

route-map test1 permit 10
match ipv6 address test1
PE1#show route-map test2
[route-map test2] IP type: IPv6

route-map test2 permit 10
match ipv6 address test2
9-27

PE1#show ipv6-access-lists name test1

ipv6-access-list test1
1/1 (showed/total)
1 permit ipv6 1001::20:0/120 any
PE1#show ipv6-access-lists name test2

ipv6-access-list test2
1/1 (showed/total)
1 permit ipv6 2002::20:0/120 any
Before the use of the VRF routing policy, in the export direction, the routing table for vrf
test1 on PE1 is as follows.

IB 22::/64 [200/0]
D 33::/64
A 33::33/128
D 1001::20:0/120
A 1001::20:2/128
IB 2002::20:0/120 [200/0]
After the VRF routing policy is enabled, the routing table for vrf test1 on PE1 is as follows.

D 33::/64
9-28

via ::, loopback33, 00h04m47

A 33::33/128
D 1001::20:0/120
A 1001::20:2/128
IB 2002::20:0/120 [200/0]
via ::ffff:10.10.3.3, loopback1, IPv6-mpls, 21h23m00
The test2 routing policy filters routes advertised from peer PE2.
IB 22::/64 [200/0]
PE1 can learn routes only if rule 1 (permit ipv6 2002::20:0/120 any) defined in route-map
test2 is matched. The command is as follows.
IB 2002::20:0/120 [200/0]
The test1 routing policy works for outgoing routes on PE1. Before the use of the policy,
the routing table for VRF test1 on PE2 is as follows.
D 22::/64
A 22::1/128
IB 33::/64 [200/0]
IB 1001::20:0/120 [200/0]
D 2002::20:0/120
via ::, gei-1/10.1, 06h2211s
A 2002::20:2/128
via ::, gei-1/10.1, 06h22m11s
After the policy is enabled, the routing table for VRF test1 on PE2 is as follows.

9-29


D 22::/64
A 22::1/128
IB 1001::20:0/120 [200/0]
D 2002::20:0/120
via ::, gei-1/10.1, 00h22m27s
A 2002::20:2/128
via ::, gei-1/10.1, 00h22m27s
The following shows that only one route is learned from the remote end:
IB 1001::20:0/120 [200/0]
The route matches the rule 1 permit ipv6 1001::20:0/120 any condition defined in route-map
test1. The mismatched routes have been filtered out:
IB 33::/64 [200/0]
9.2 IPv6 Policy Route Configuration

The concept of IPv6 policy routes is similar to the concept of IPv4 policy routes. For details
about the overview and configuration commands, refer to Policy Routing Configuration
in the ZXR10 ZSR V2 (V2.00.10) Configuration Guide (Policy Template).
9.2.1 Configuring IPv6 Policy Routes

This procedure describes how to configure IPv6 policy routes.
Steps
1. Configure IPv6 policy routes.
The commands for configuring IPv6 policy routes are similar to those for configuring
IPv4 policy routes, except that the addresses are IPv6 addresses. For details about
the configuration commands, refer to Policy Routing Configuration in the ZXR10
ZSR V2 (V2.00.10) Configuration Guide (Policy Template).
9-30

Command Function
ZXR10(config)#show running-config pbr Displays the configuration information

about policy routes in the database.
End of Steps
9.2.2 IPv6 Policy Route Configuration Example

As shown in Figure 9-6, the users of two subnets access the router via different interfaces
and two ISP egresses are available. According to the requirements, different egresses
should be selected for different users according to the users' IP addresses, that is, the
ISP1 egress should be selected for the services of the users whose IP addresses belong
to the subnet 10::1/24 whereas the ISP2 egress should be selected for the services of the
users whose IP addresses belong to the subnet 11::1/24.
Figure 9-6 IPv6 Policy Route Configuration Example
Configuration Flow
1. Enable IPv6 and configure the interface addresses on the ZXR10.
2. Create an ACL to control traffic.
3. Create a route-map, associate it with the ACL, and define the action.
4. Associate the route-map with the corresponding interfaces.
Configure the interfaces on the ZXR10.
ZXR10(config-if-gei-1/1)#description To User1
ZXR10(config-if-gei-1/1)#ipv6 enable
9-31

ZXR10(config-if-gei-1/1)#ipv6 address 10::2/64

ZXR10(config-if-gei-1/1)#exit
ZXR10(config)#show running-config-interface gei-1/1
! <Interface>
interface gei-1/1
no shutdown
description To User1
ipv6 enable
$
! </Interface>
ZXR10(config-if-gei-1/2)#description To User2
! <Interface>
interface gei-1/2
no shutdown
description To User2
ipv6 enable
$
! </Interface>
ZXR10(config-if-gei-2/1)#description To ISP1
! <Interface>
interface gei-2/1
no shutdown
description To ISP1
ipv6 enable
$
! </Interface>
ZXR10(config-if-gei-2/2)#description To ISP2
9-32


! <Interface>
interface gei-2/2
no shutdown
description To ISP2
ipv6 enable
$
! </Interface>
Configure the default route.
ZXR10(config)#ipv6 route 0:0::0:0/0 100::1
Configure the route-map:
/*Configure the ACL applied in the route-map*/

ZXR10(config)#ipv6-access-list 1
ZXR10(config-ipv6-acl)#rule 1 permit ipv6 10::1/64 any
ZXR10(config-ipv6-acl)#exit
ZXR10(config)#show ipv6-access-lists name 1
ipv6-access-list 1
1/1 (showed/total)
1 permit ipv6 10::1/64 any
ZXR10(config)#ipv6-access-list 2
ZXR10(config-ipv6-acl)#rule 1 permit ipv6 20::1/64 any
ZXR10(config-ipv6-acl)#exit
ZXR10(config)#show ipv6-access-lists name 2
ipv6-access-list 2
1/1 (showed/total)
1 permit ipv6 20::1/64 any
/*Configure the route-map information with the sequence

numbers being 10 and 20*/
ZXR10(config)#route-map v6-pbr permit 10
ZXR10(config-route-map)#match ipv6 address 1
ZXR10(config-route-map)#set ipv6 next-hop 100::1
ZXR10(config-route-map)#exit
ZXR10(config)#route-map v6-pbr permit 20
ZXR10(config-route-map)#match ipv6 address 2
ZXR10(config-route-map)#set ipv6 next-hop 200::1
ZXR10(config-route-map)#exit
ZXR10(config)#show route-map v6-pbr
9-33

[route-map v6-pbr] IP type: IPv6

route-map v6-pbr permit 10
match ipv6 address 1
set ipv6 next-hop 100:0:0:0:0:0:0:1
set ipv6 next-hop 200:0:0:0:0:0:0:1
Apply the route-map to the interfaces.

ZXR10(config)#ipv6 policy interface gei-1/1 route-map v6-pbr
ZXR10(config)#show running-config pbr
! <pbr>
ipv6 policy interface gei-1/1 route-map v6-pbr
! </pbr>
ZXR10(config)#ipv6 policy interface gei-1/2 route-map v6-pbr
! <pbr>
! </pbr>
In this example, the following three situations may occur.

l When both the ISP1 egress and the ISP2 egress are normal, the ISP1 egress is
selected for the services of the users of the subnet 10::1/24 whereas the ISP2 egress
is selected for the services of the users of the subnet 11::1/24.
l When the ISP1 egress is normal but the ISP2 egress is abnormal, the ISP1 egress
is selected for the services of the users of both subnets and then the default route is
used for the services of the users of the subnet 11::1/24.
l When the ISP1 egress is abnormal but the ISP2 egress is normal, the services of the
users of the subnet 11::1/24 are normal but the services of the users of the subnet
10::1/24 are interrupted.
Check the route-map configuration information, as shown below.
ZXR10(config)#show route-map v6-pbr
[route-map v6-pbr] IP type: IPv6
set ipv6 next-hop 100:0:0:0:0:0:0:1
set ipv6 next-hop 200:0:0:0:0:0:0:1
Check the PBR binding information on the interface, as shown below.

! <pbr>
9-34


! </pbr>
9-35

9-36

Chapter 10
IPv6 Multicast
Table of Contents
Multicast Overview ...................................................................................................10-1
Configuring Public IP Multicast .................................................................................10-3
10.1 Multicast Overview

Multicast Introduction
As a replacement of IPv4, IPv6 uses a 128bit address structure to solve the problem of IP
address shortage. At the same time, IPv6 optimizes some characteristics. IPv4 multicast
solves the problem of single-point sending and multi-point receiving, and it implements
high-efficiency point-to-multipoint data transmission. It saves a lot of network bandwidth
and reduces network load. Therefore, multicast is applied and enhanced in IPv6.
The most obvious difference between IPv6 multicast and IPv4 multicast is that the IPv6
multicast address mechanism is improved. The group member management, multicast
packet forwarding and multicast path establishment of IPv6 are similar to those of IPv4.
Multicast Address Introduction

An IPv6 address is of 128bit long, divided by colons into eight bytes with four hex numbers
in each byte, such as FEDC:BA98:7654:3210:FEDC:BA98:7654:3210. An IPv6 multicast
address identifies a group of interfaces that belong to different nodes. A node can belong
to 0 or several multicast groups. A packet sent to a multicast address is received by all
interfaces identified by the multicast address.
According to RFC, some IPv6 multicast addresses have been allocated permanently, as
listed in Table 10-1.
Table 10-1 IPv6 Multicast Address Allocation
Name Address Description
Reserved multicast address FF0x:: Not allocated to any multicast

address
All node multicast addresses FF01::1 (node-local)

FF02::1 (link-local)
All router multicast addresses FF01::2 (node-local)

FF02::2 (link-local)
FF05::2 (site-local)
10-1

Name Address Description
Requested node multicast FF02::1:FFxx:xxxx Consisting of the address

addresses prefix FF02::1:FF00:/104 (in
front) and low 24 bits of a
unicast or anycast address of a
requested node. For example,
4307::01:800:200E:8C6C
is corresponding to
FF02::1:FF0E:8C6C.
RFC defines a mode to allocate IPv6 multicast addresses dynamically, that is, an IPv6
multicast address on the basis of unicast prefix. An IPv6 multicast address includes the
unicast address prefix of its multicast source network. Global-unique multicast addresses
can be allocated in this way. Figure 10-1 lists the address structure.
Figure 10-1 Structure of IPv6 Multicast Address on the Basis of Unicast Prefix
Introduction to IPv6 Multicast Protocols

The multicast protocols supported by IPv6 include Multicast Listener Discovery (MLD),
MLD Snooping, IPv6 Protocol Independent Multicast (PIM) and IPv6 MBGP.
1. Multicast routing group management protocol
MLD originates from the Internet Group Management Protocol (IGMP). MLDv1
corresponds to IGMPv2, and Multicast Listener Discovery Version 2 (MLDv2)
corresponds to IGMPv3. Different from IGMP which uses message type of IP
protocol number 2, MLD uses message type of ICMPv6 (the IP protocol number
is 58), including MLD Query message (type value is 130, MLDv1 Report message
(type value is 131), MLDv1 Leaving message (type value is 132) and MLDv2 Report
message (type value is 143). MLD acts completely the same as IGMP does except
for the message structure.
MLD Snooping is similar to IGMP Snooping.

2. Multicast routing protocol
IPv6 PIM protocol action is the same as that of IPv4 PIM except the IP address
structure in messages. IPv6 PIM also supports Sparse Mode (SM), Dense Mode
(DM) and Source Specific Multicast (SSM).
10-2

Chapter 10 IPv6 Multicast
When IPv6 PIM sends a protocol message (such as PIM Hello, Join-Prune, Assert,
Bootstrap, Graft, Graft-Ack or State-refresh) of link-local range, the source IPv6
address of the message is the link-local address on the interface that sends
the message. When IPv6 PIM sends a protocol message (such as Register,
Register-Stop or C-RP Advertisement), the source IPv6 address of the message is
the global unicast address on the interface that sends the message.
IPv6 multicast does not support Multicast Source Discovery Protocol (MSDP). There
are two ways to receive multicast data from other IPv6 PIM domains.
a. One way is to obtain the multicast source addresses in other IPv6 PIM domains
directly through other modes (such as advertisement) and use IPv6 PIM-SSM to
initiate joins of specific source groups.
b. The other way is to use the embedded Rendezvous Point (RP) mechanism. The
device can obtain the RP addresses in other IPv6 PIM domains through the IPv6
multicast addresses with embedded RP addresses, and initiate joins to the RPs
in other domains. To deliver inter-domain IPv6 multicast routing information, IPv6
MBGP can be used, which is similar to IPv4 MBGP.
10.2 Configuring Public IP Multicast

This procedure describes how to configure public multicast.
Steps
1. Configure public IP multicast.
1 ZXR10(config)#ipv6 multicast-routing Enables IPv6 multicast function.
2 ZXR10(config-mcast-ipv6)#router pim Enters PIM mode.
2. Configure a restriction on the number of entries in the multicast forwarding table.
Command Function
ZXR10(config-mcast-ipv6)#mroute6-limit <limit> Restricts the number of entries in

the multicast forwarding table. By
default, the maximum value allowed
by the system is used.
3. Configure multicast damping.
1 ZXR10(config-mcast-ipv6)#damping-enable Enables damping.
10-3

2 ZXR10(config-mcast-ipv6)#damping-threshold Restricts the threshold of the

<threshold> number of times that a route
is delivered. If the threshold is
exceeded, the damping function
is enabled to inhibit route delivery
for at least 10 seconds and up to
60 seconds.
4. Configure multicast load sharing.
Command Function
ZXR10(config-mcast-ipv6)#multipath Enables load sharing. The Hash

algorithm based on source address
is used.
ZXR10(config-mcast-ipv6)#multipath s-g-hash basic Enables load sharing. The Hash

algorithm based on source address
and multicast address is used.
ZXR10(config-mcast-ipv6)#multipath s-g-hash Enables load sharing. The Hash

next-hop-based algorithm based on next hop is used.
Command Function
ZXR10#show ipv6 mroute [group <group-address>][source Displays the content of the IPv6
<source-address>] multicast routing table.
ZXR10#show ipv6 mroute summary Displays the number of the IPv6

multicast routing tables.
ZXR10#show ipv6 mroute brief Displays the content of the IPv6

multicast routing tables.
6. Maintain public IP multicast.
Command Function
ZXR10#clear ipv6 mroute [group-address Clears the multicast route.

<group-address>][source-address <source-address>]
End of Steps
10-4

Chapter 11
IPv6 Static Multicast
Configuration
Table of Contents
IPv6 Static Multicast Overview .................................................................................11-1
Configuring IPv6 Static Multicast ..............................................................................11-2
IPv6 Static Multicast Configuration Example.............................................................11-3
11.1 IPv6 Static Multicast Overview

Static multicast routes are used for forwarding multicast packets through a specific path
instead of the optimum path of the unicast route.
Static multicast provides the outgoing and incoming interfaces in the user-configured
multicast routing table. A multicast forwarding table is formed in accordance with the
configuration of users. If a static multicast route and a dynamic multicast route exist
concurrently, the static multicast route has a higher priority. The logical position of static
multicast is equal to PIM-SM and PIM-DM. It can be understood as a special multicast
routing protocol.
Static multicast routes serve the following two purposes in accordance with different
application environments:
l Changing RPF routes

In general, multicast has the same network topology architecture with unicast.
Multicast data is transmitted through the same path as the unicast data. A static
multicast route can be configured for changing an RPF route, so that a transmission
path different from that of unicast data is created for multicast data.
l Making an RPF route uninterrupted
When a unicast route is blocked in the network, data (including multicast data) cannot
be forwarded because of no RPF route. An RPF route can be generated by configuring
a static multicast route, so that a multicast table entry is created to guide multicast data
forwarding.
Multicast routing protocols use the RPF check mechanism during creation of multicast
routing entries to ensure that multicast data can be transmitted through a correct path.
This can also avoid generation of loops due to various reasons.
11-1

The method for selecting an optimum path with the multicast source address as the
destination address from the unicast routing table, MBGP routing table, and static
multicast routing table.
1. If the longest match algorithm is configured, the route with the longest mask is selected.
2. If the three routes have the same mask, the route with the highest priority is selected.
3. If the three routes have the same priority, routes are selected in order of the static
multicast route, MBGP route, and unicast route.
The selected route serves as the RPF route to determine the RPF interface and RPF
neighbor.
11.2 Configuring IPv6 Static Multicast

This procedure describes how to configure IPv6 static multicast and how to verify the
configurations.
Steps
1. Configure static multicast.
1 ZXR10(config-mcast-ipv6)#ipv6 multicast-static Enables the MSTATIC.

-start
2 ZXR10(config-mcast-ipv6)#ipv6 multicast-static-li Configures the maximum number

mit xg <xg-limit> sg <sg-limit> of static multicast route entries.
3 ZXR10(config-mcast-ipv6)#ipv6 multicast-st Configures the number of static

atic-route <source-address><group-address>[{[iif multicast route entries.
<iif-name>],[oif <oif-index>]}]
4 ZXR10(config-mcast-ipv6)#ipv6 multicast-static-in Configures a set of static

terface index <index> interface <interface-name> multicast outgoing interfaces.
<xg-limit>: number of static multicast (*,G) route entries allowed to be configured,

default: 0.
<sg-limit>: number of static multicast (S,G) route entries allowed to be configured,
default: 0.
<source-address>: specified multicast source address.
<group-address>: specified multicast group address.
<iif-name>: incoming interface name of the multicast route entry.
<oif-index>: serial number of the outgoing interface set of the multicast route entry.
<index>: configures the serial number of the outgoing interface set.
<interface-name>: name of the interface joining the outgoing interface set.
11-2

Chapter 11 IPv6 Static Multicast Configuration
Command Function
ZXR10#show ipv6 multicast-static-interface [index <index>] Displays valid interfaces in an

egress interface set.
ZXR10#show ipv6 multicast-static-route [group Displays the content of the static

<group-address>|[source <source-address>]]|[source multicast routing table.
<source-address>]
ZXR10#show ipv6 multicast-static-route summary Displays statistical summary of

the contents of the static multicast
routing table.
End of Steps
11.3 IPv6 Static Multicast Configuration Example

As shown in Figure 11-1, a static multicast route with source address 1::1 and destination
address ff88::1 is configured so that multicast traffic can be forwarded.
Figure 11-1 Networking Diagram of the IPv6 Static Multicast Configuration Example
Configuration Flow
1. Configure IP addresses of interfaces.
2. Enter multicast mode.
3. Start static multicast.
4. Configure the maximum entries numbers of static multicast (*,G) and (S,G) separately.
5. Configure the outgoing interface list of static multicast.
6. Configure a static multicast route.
R1(config)#ipv6 multicast-routing
R1(config-mcast-ipv6)#ipv6 multicast-static-start
R1(config-mcast-ipv6)#ipv6 multicast-static-limit xg 1024 sg 1024
R1(config-mcast-ipv6)#ipv6 multicast-static-interface index 2 interface
gei-3/7
R1(config-mcast-ipv6)#ipv6 multicast-static-route 1::1 ff88::1 iif
11-3

gei-3/6 oif 2
R1(config-mcast-ipv6)#end
Run the show ipv6 multicast-static-interface command on R1 to display static multicast
information about interfaces:
R1(config)#show ipv6 multicast-static-interface
STATIC-MULTICAST OUT PORT INDEX 2:
Outgoing Interface:
gei-3/7
R1(config)#show ipv6 multicast-static-route

The Capability of Static Multicast6 Route
(*, g) 1024, (s, g) 1024
(1::1, ff88::1)
Incoming interface: gei-3/6 A
Outgoing interface list:
gei-3/7 F
R1(config)#show ipv6 mroute

IPv6 Multicast Routing Table
Flags:NS:SPT upsend,RT:Reg upsend,F:Forward,
NTP:NTP join,DPU:Damping enable,DPD:Damping del,
(1::1, ff88::1), TYPE: STATIC, FLAGS:
Incoming interface: gei-3/6, flags:
gei-3/7, flags: F
11-4

Chapter 12
MLD Configuration
Table of Contents
MLD Overview..........................................................................................................12-1
Configuring MLD ......................................................................................................12-2
MLD Configuration Instances ...................................................................................12-6
12.1 MLD Overview

MLD originates from IGMP. MLDv1 corresponds to IGMPv2, and MLDv2 corresponds to
IGMPv3. Different from IGMP which uses the message type of IP protocol number 2, MLD
uses the message type of ICMPv6 (the IP protocol number is 58), including MLD Query
message (type value is 130, MLDv1 Report message (type value is 131), MLDv1 Leaving
message (type value is 132) and MLDv2 Report message (type value is 143). MLD acts
completely the same as IGMP does except for the message structure.
MLD provides the information that is needed in the last state to forward a multicast packet
to the destination. The multicast router exchanges information with the host receiving the
multicast data. The information is collected from the group members of hosts that connect
to the multicast router directly.
MLD mainly uses two types of messages, group member query message and group
member report message.
l The multicast router sends group member query messages to all hosts periodically to
determine the group members on the interconnected subnets.
l Each host replies with a member report message to report the multicast group which
it belongs to.
When a host joins a new group, it sends a join message immediately instead of waiting
for a query in case it is the first member of the group.
When a host begins to receive information as a member of a group, the multicast router
will query the group periodically to check whether there is any member in the group. As
long as there is one host, the multicast router continues forwarding data.
When a host leaves a group, the multicast router receives a leaving message, and then
it queries whether there is any other active member in the group immediately. If there is
any, the multicast router continues forwarding data. Otherwise, it will not forward data any
longer.
At present, there are two versions of MLD. MLDv1 corresponds to IGMPv2, and it provides
the fast leaving mechanism of group members. MLDv2 corresponds to IGMPv3, and
12-1

it provides the ability to receive or refuse to receive packets from designated multicast
sources, thus to support SSM.
12.2 Configuring MLD

This procedure describes how to configure the basic functions of MLD, including version
information, group joining/leaving functions, and timer-related attribute parameters.
Steps
1. Configure MLD version.
At present, there is MLDv1 and MLDv2. By default, it is v2. Users can set the version
with the version <version> command according to demand. Considering security, it
is required to use the same version on the network elements in the same segment.
The MLD version can be configured based on an instance or an interface. The MLD
version configured based on an interface takes precedence. Different versions can be
configured on different interfaces of the same device.
1 ZXR10(config-mcast-ipv6)#router mld Enters MLD configuration mode.
2 ZXR10(config-mcast-ipv6-mld)#version{1 | 2} Configures the protocol version

number in the MLD instance.
3 ZXR10(config-mcast-ipv6-mld)#interface Enters MLD interface configuration

<interface-name> mode.
4 ZXR10(config-mcast-ipv6-mld-if-interface- Configures the protocol version

name)#version {1 | 2} number under the MLD interface.
2. Disable the MLD querier election.
Command Function
ZXR10(config-mcast-ipv6-mld-if-interface- Disables the querier election, that

name)#querier-election disable is, the router considers itself as the
querier.
3. Configure the Require-Alert-Option option.
Command Function
ZXR10(config-mcast-ipv6-mld)#require-alert-options Receives only the packets in which

the IPv6 header contains the Router
Alert options option.
4. Configure SSM-mapping.
12-2

Chapter 12 MLD Configuration
Command Function
ZXR10(config-mcast-ipv6-mld)#ssm-map static Configures the SSM-mapping function

{default | group-list |<access-list-name>}<source-address> to specify the source address range in
a group list of MLDv1. Default group
range: FF3*/32.
5. Configure restriction on packet loss allowance.
You can configure it in instance mode or in interface mode. The latter takes
precedence.
Command Function
ZXR10(config-mcast-ipv6-mld)#robustness-count Restriction on number of packets

<times> allowed to be lost. Range: 27,
default: 2.
ZXR10(config-mcast-ipv6-mld-if-interface- Restriction on number of packets

name)#robustness-count <times> allowed to be lost. Range: 27,
default: 2. Interface mode takes
precedence.
6. Configure the MLD group function.
1 ZXR10(config)#ipv6 multicast-routing Enters multicast configuration

mode.
2 ZXR10(config-mcast-ipv6)#router mld Enters MLD configuration

mode.
3 ZXR10(config-mcast-ipv6-mld)#interface Enters MLD interface

<interface-name> configuration mode.
4 ZXR10(config-mcast-ipv6-mld-if-interface- Configures the range of

name)#access-group <access-list-number> groups allowing MLD join.
5 ZXR10(config-mcast-ipv6-mld-if-interface- Configures the MLD interface

name)#join-group <group-address> as a member in a static group
for sending report packets.
6 ZXR10(config-mcast-ipv6-mld-if-interface- Configures the MLD interface

name)#static-group <group-address>[source as a member in a static group.
{<source-address>[{include | exclude}]| ssm-map}]
12-3

7 ZXR10(config-mcast-ipv6-mld-if-interface- Configures the range of

name)#immediate-leave {all | group-list <access-list-nam groups allowing MLD leaving
e>} immediately.
By default, when a device
receives an MLD leaving
message, the group member
will leave the group if it
does not receive any report
message within (last member
query interval * 2) seconds. If
no option is configured in the
command, it takes effect in all
multicast groups.
7. Configure MLD timers.

After MLD is enabled on the interfaces if multicast routers in a shared segment, an
optimal interface will be elected as the querier of the segment to obtain group member
information by sending query messages.
After sending a query message, the querier waits for a period to receive the report
messages from member hosts. The period is the value of the maximum response
time contained in the query messages. By default, the period is 10 seconds.
After receiving the query message, a member host in the segment will subtract a
random value on the basis of the maximum response time. It uses the result as its
response time. If the querier receives a report message from another member host
during this period, the host cancels to send a report message. If the querier does not
receive any report message from any other member hosts when the period expires,
the member host will send a report message. Increasing the maximum response time
also increases the wait chances of group members in the segment, and reduces the
rate that several hosts send report messages in the segment.
Users can set the timers related to the querier according to demand.
To configure MLD timers on the ZXR10 ZSR V2, perform the following steps.
1 ZXR10(config-mcast-ipv6-mld)#query-interval Configures the common MLD

<seconds> query interval in instance
mode, range: 165535,
default: 125, unit: second.
ZXR10(config-mcast-ipv6-mld-if-interface- Configures the common

name)#query-interval <seconds> MLD query interval in
interface mode, which
takes precedence. Range:
12-4

165535, default: 125, unit:

second.
2 ZXR10(config-mcast-ipv6-mld)#query-max-response- Configures the maximum

time <seconds> response time carried in the
query message sent by the
MLD protocol in instance
mode. Range: 125, default:
10, unit: second.
ZXR10(config-mcast-ipv6-mld-if-interface- Configures the maximum

name)#query-max-response-time <seconds> response time carried in
the query message sent
by the MLD protocol in
interface mode, which takes
precedence. Range: 125,
3 ZXR10(config-mcast-ipv6-mld)#querier-timeout Configures the time-out

<seconds> duration of the MLD querier
in instance mode. Range:
60300, unit: second.
ZXR10(config-mcast-ipv6-mld-if-interface- Configures the time-out

name)#querier-timeout <seconds> duration of the MLD querier in
unit: second.
4 ZXR10(config-mcast-ipv6-mld)#last-member-query-in Configures the interval of the

terval <seconds> MLD special group query in
instance mode. Range: 125,
ZXR10(config-mcast-ipv6-mld-if-interface- Configures the interval of the

name)#last-member-query-interval <seconds> MLD special group query in
Command Function
ZXR10#show ipv6 mld interface [<interface-name>] Displays MLD configuration on an

interface.
12-5

Command Function
ZXR10#show ipv6 mld groups [{[<interface-name>],[<g Displays joining of multicast groups that
roup-address>]}][detail] are learned through the MLD protocol by
the interface directly connected to the
router.
ZXR10#show ipv6 mld packet-count [<interface-name>] Displays statistics counts of MLD protocol
messages sent and received.
9. Maintain MLD.
Command Function
ZXR10#clear ipv6 mld groups [<interface-name>] Clears multicast groups that are joined
dynamically.
ZXR10#clear ipv6 mld packet-count[<interface-name>] Clears statistics counts of MLD protocol

messages sent and received.
End of Steps
12.3 MLD Configuration Instances

12.3.1 Example: Configurating MLD Querier Router Election
As shown in Figure 12-1, PIM-SM is enabled on R1 and R2. The MLD version is v1.
MLDv1 elects a querier through common query messages. The MLDv1 router with the
smallest link-local address is elected as the querier.
Figure 12-1 MLDv1 Configuration Example
Configuration Flow
1. Configure addresses on the interfaces of the routers in interface configuration mode.
The link-local address of R1 should be smaller than that of R2.
2. Enable the multi-cast function by configuring the ipv6 multicast-routing command.
3. Enter PIM route mode and then enter the interfaces.
4. Enable PIM-SM in interface configuration mode.
12-6

R1(config-if-gei-1/1)#ipv6 address link-local fe80::1
R1(config-mcast-ipv6)#router pim
R1(config-mcast-ipv6-pim)#interface gei-1/1
R1(config-mcast-ipv6-pim-if-gei-1/1)#pimsm
R1(config-mcast-ipv6-pim-if-gei-1/1)#end

R2(config-if-gei-2/1)#ipv6 address link-local fe80::2
Check the validity of the configuration on R1:
R1#show ipv6 mld interface gei-1/1
gei-1/1
Internet address is fe80::1
MLD is enabled on interface
Current MLD version is 2
MLD query interval is 125 seconds
MLD last member query interval is 1 seconds
MLD query max response time is 10 seconds
MLD querier timeout period is 255 seconds
MLD robustness variable is 2
MLD querier is fe80::1, never expire
Inbound MLD access group is not set
MLD immediate leave control is not set
Check the validity of the configuration on R2:

gei-2/1
12-7

Internet address is fe80::2

MLD querier is fe80::2, expire timer: 00:03:33
12.3.2 Example: Configuring a Router to Join a Static MLD Group

and a Dynamic MLD Group
As shown in Figure 12-2, PIM-SM is enabled on R1. The MLD version is v2 (default). It
is required to configure R1 to join a static group ffee::1, and configure it to join a dynamic
group ffee::2 through a PC.
Figure 12-2 Example for Configuring a Router to Join a Static MLD Group and a
Dynamic MLD Group
Configuration Flow
1. Configure addresses on the interfaces of the routers in interface configuration mode.
2. Enable the multicast function by configuring the ipv6 multicast-routing command.
3. Enter PIM route mode and then enter the interfaces.
4. Enable PIM-SM in interface configuration mode.
5. In multicast mode, enter MLD route mode and then enter the interfaces to be
configured.
6. Configure the static group on gei-1/1 of R1.
7. Send MLD group join messages to R1 on the PC.
12-8

R1#configure terminal
R1(config-mcast-ipv6)#router mld
R1(config-mcast-ipv6-mld)#interface gei-1/1
R1(config-mcast-ipv6-mld-if-gei-1/1)#static-group ffee::1 source 200::1
R1(config-mcast-ipv6-mld-if-gei-1/1)#end
Check the interface information on R1:
gei-1/1
Internet address is fe80::2d0:d0ff:fe06:606
MLD querier is fe80::2d0:d0ff:fe06:606, never expire
Check the detailed information about the corresponding interface group on R1:
R1#show ipv6 mld groups gei-1/1 detail
Flags: S - Static Group, SSM - SSM Group, M - MDT Group
Interface: gei-1/1
Group: ffee::1
Flags:
Uptime: 01:06:51
Group mode: INCLUDE
Last reporter: fe80::2d0:e0ff:fe10:201f
Group source list: (M - SSM Mapping, S - Static, R - Report)
Source addr Present Expires Fwd Flag
200::1 01:06:51 Never Yes S
Check the detailed information about a PC requesting to join the multicast groups on R1:
R1(config-mcast-ipv6)#show ipv6 mld groups
Total: 2 groups
12-9

Group Address : ffee::2

Last Reporter : fe80::200:65ff:fe03:102
Interface : gei-1/1
Uptime : 00:01:44
Expires : 00:03:44
Group Address : ffee::1
Last Reporter : fe80::2d0:d0ff:fe06:606
Interface : gei-1/1
Uptime : 00:03:11
Expires : never
12-10

Chapter 13
IPv6 PIM-DM Configuration
Table of Contents
PIM-DM Overview ....................................................................................................13-1
Configuring IPv6 PIM-DM.........................................................................................13-1
IPv6 PIM-DM Configuration Example .......................................................................13-2
13.1 PIM-DM Overview

In the Protocol Independent Multicast-Dense Mode (PIM-DM), it is assumed that there are
many multicast receivers which are distributed on most network devices. Based on the
above application mode, the mechanism of the PIM-DM protocol is relatively simple. It
diffuses the multicast traffic to all devices in the network periodically through the PUSH
mode, and then establish and maintain an SPT forwarding tree.
l With PIM-DM, it is assumed that each sub-net in the network has at least one member
existing in a multicast group. In this case, the multicast data is diffused to all nodes in
the network.
l PIM-DM will cut the branches with no forwarded multicast data, and save only
the branches with a receiver. The "diffuse-cut branches" operation takes place
periodically, and the cut branches recover to forwarding status periodically.
l When the cut branches have a member that exists in the multicast group, this node
sends messages to the upper stream actively. In this case, this node changes to the
forwarding status, and the multicast data is forwarded to this branch.
13.2 Configuring IPv6 PIM-DM

This procedure describes how to configure IPv6 PIM-DM.
Steps
1. Configure IPv6 PIM-DM.
1 ZXR10(config)#ipv6 multicast-routing Enables the IPv6 multicast.
2 ZXR10(config-mcast-ipv6)#router pim Enables the PIM protocol of the IPv6

multicast.
3 ZXR10(config-mcast-ipv6-pim)#interface Enters the IPv6 PIM interface configuration

<interface-name> mode.
13-1

4 ZXR10(config-mcast-ipv6-pim-if- Enables the PIM-DM protocol for the IPv6

interface-name)#pimdm multicast.
Command Function
ZXR10#show ipv6 pim interface [<interface-name>] Checks the configured IPv6 PIM interface.
ZXR10#show ipv6 pim mroute [[group <group-address Checks the content of the IPv6 PIM
>[source <source-address>]]|[summary]] multicast routing table.
ZXR10#show ipv6 pim neighbor [[<interface-name>]|[d Checks the negihbor status of the IPv6
etail]] PIM interface.
3. Maintain IPv6 PIM-DM.
Command Function
ZXR10#debug ipv6 pim data-info Traces all debugging information about

the messages received by IPv6 PIM.
ZXR10#debug ipv6 pim packet-send Traces all debugging information about

the messages sent by IPv6 PIM.
ZXR10#debug ipv6 pim packet-recv Traces all debugging information about

protocol messages received by IPv6 PIM.
ZXR10#debug ipv6 pim mrt Traces all debugging information about

IPv6 PIM route.
ZXR10#debug ipv6 pim ast Traces all debugging information about

IPv6 PIM assertion.
ZXR10#debug ipv6 pim Traces the debugging information about

IPv6 PIM.
ZXR10#debug ipv6 pim all Traces all debugging information about

IPv6 PIM.
End of Steps
13.3 IPv6 PIM-DM Configuration Example

Figure 13-1 is an example of the PIM-DM neighbor between R1 and R2.
13-2

Chapter 13 IPv6 PIM-DM Configuration
Figure 13-1 Network Architecture of PIM-DM Configuration Example
Configuration Flow
1. Configure addresses of related interfaces.
2. Enters the multicast mode.
3. Enters the IPv6 PIM mode.
4. Enable the PIM-DM function for corresponding interfaces.
Run the following commands on R1:
R1(config-mcast-ipv6-pim-if-gei-0/9)#pimdm
R1(config-mcast-ipv6-pim-if-gei-0/9)#exit

13-3

R2(config)#ipv6 route 198::/64 199::1 /*Unicast route to the source*/
Run the show ipv6 pim neighbor command on R1 to check the neighbor status.
R1(config)#show ipv6 pim neighbor
Neighbor Address Interface Uptime Expires DR Pri
fe80::2d0:d0ff:fe06:600 gei-0/9 00:09:12 00:00:26 1
Run the show ipv6 pim interface command on R1 to check the interface status.
R1(config)#show ipv6 pim interface
Interface State Nbr Hello DR PIM Silent Mode
Count Period Priority
gei-0/7 Up 0 30 1 Disabled D
Address: fe80::2d0:d0ff:fe06:606
DR : fe80::2d0:d0ff:fe06:606
gei-0/9 Up 1 30 1 Disabled D
DR : fe80::2d0:d0ff:fe06:606
Run the show ipv6 pim mroute command on R1 to check the status of the IPv6 multicast
routing table.
R1(config)#show ipv6 pim mroute
IPv6 PIM Multicast Routing Table
Flags: T- SPT-bit set,A- Forward,J- Join SPT,U- Upsend,S- PIM-SM,D- PIM-DM,
Macro state: Ind- Pim Include Macro,Exd- Pim Exclude Macro,
Jns- Pim Joins Macro,LAst- Pim Lost_assert Macro,
Imo- Pim Immediate_olist Macro,Ino- Pim Inherited_olist Macro,
13-4

Chapter 13 IPv6 PIM-DM Configuration
Lcd- Pim Local_receiver_include Macro

Timers:Uptime/Expires(Upstream State)
(198::2, ff88::1), 00:07:20/00:00:00(JOINED)/00:03:25,
Reg:NO INFO; RP:0::0; RT:NULL;
Ind:0/Exd:0/Jns:1/LAst:0/Imo:1/Ino:1
Iif: gei-0/7, RPF nbr:0::0(S); AT
RPF nbr:0::0(D); 00:00:00(FORWARD);
Oif:
gei-0/9, JoinsSG / InoSG / DenseOlist
13-5

13-6

Chapter 14
IPv6 PIM-SM Configuration
Table of Contents
PIM-SM Overview ....................................................................................................14-1
Configuring IPv6 PIM-SM .........................................................................................14-3
IPv6 PIM-SM Configuration Example........................................................................14-7
14.1 PIM-SM Overview

PIM-SM Introduction
PIM-SM is mainly used in the following situations:
l Group members sparsely locate in a relatively large scale.
l The network bandwidth resources are limited.
PIM-SM does not depend on a specific unicast routing protocol. PIM-SM assumes that
all routers on a shared segment do not need to send multicast packets. The routers only
can receive and send multicast packets after they request to join a multicast group on
their own initiative. PIM-SM advertises the multicast information to all routers supporting
PIM-SM through an RP. In PIM-SM, a router joins or leaves the multicast group explicitly.
This reduces the number of packets and the bandwidth used by the control packets.
RP
PIM-SM sends multicast packets by using a shared tree. A shared tree has a center point
that is responsible for sending packets to all the source-sending ends in the multicast
group. Each source-sending end sends packets to the center point along the shortest
path, and then takes the center point as the root point to distribute the packets to various
receiving ends of the group.
The group center point of the PIM-SM is called the RP. There may be several RPs in a
network, but there is only one RP in a multicast group.
A router can obtain the location of the RP in two ways.
1. Configure the RP manually and statically on the routers running PIM-SM.
2. PIM-SMv2 obtains the location through the candidate RP advertisement. The
candidate RP with the highest priority becomes a formal RP.
In PIM-SM, some routers running PIM-SM are manually set to work as candidate Bootstrap
Router (BSR). The candidate BSR with the highest priority is elected as the formal BSR.
The BSR is responsible for collecting the candidate RP information on the multicast routers
in group to find out candidate RPs in the multicast domain. It notifies the candidate RPs to
14-1

all the PIM routers in the PIM domain in a unified way. Each PIM router, according to the
similar Hash rules, elects the one with the highest priority as the formal RP from the same
candidate RP set. Candidate RPs are configured manually.
Messages Types
In PIM-SM, there are the following types of messages.
l Hello message: The router interfaces on which PIM-SM runs send Hello messages
periodically to the neighbor interfaces in the same segment to establish a neighbor
relationship. Hello messages are also used for routers running MLD to elect the DR.
l Register message: When receiving a multicast packet sent by a host in the local
network, the DR encapsulates the packet in a Register message and sends it to the
RP through unicast. The source address in the IP header of the Register message is
the address of the DR, and the destination address is the address of the RP.
l Register-Stop message: The RP unicasts a Register-Stop message to the sender of
the Register message to inform it stop sending Register messages.
l Join/Prune message: This message is forwarded in the direction to the source or
the RP. A Join message is used to construct a source tree or a shard tree. When a
receiver leaves a group, it sends a Prune message to prune the source tree or the
shard tree. This message contains the joining information and pruning information
about the multicast route entities. The Join message and the Prune message are in
the same packet. Either message can be null.
l Bootstrap message: A route needs to send Bootstrap messages on all interfaces
except the interface on which the Bootstrap message is received. This message is
generated on the BSR and forwarded by all routers.
l Assert message: When there are several routers on a multi-access network and a
multicast group packet is received on an egress interface of a router, it is necessary
to use the Assert message to designate a forwarder.
l Candidate-RP-Advertisement: A candidate RP unicasts
Candidate-RP-Advertisement to the BSR periodically to advertise the set of group
addresses served by the Candidate RP.
PIM-SM Features
The routers running PIM-SM discover each other and maintain the neighbor relationship by
exchanging Hello messages. In the multi-access network, the Hello messages also contain
the priority information about routers. The DR is elected according to this parameter.
The multicast source or the first hop router (the DR connecting to the source directly)
encapsulates a packet in a Register message, and then sends it to the RP through a unicast
router. When receiving the Register message, the RP de-encapsulates the messages to
take out the packet, and then sends the packet to the receivers of the group along the
shared multicast tree.
Each host acting as a receiver joins the multicast group through the IGMP member report
message. The last hop router (or the DP in the multi-access network) sends the received
Join message to the RP level by level. After receiving the Join message, the intermediate
14-2

Chapter 14 IPv6 PIM-SM Configuration
router checks whether it has already had the routes of the group. If it has, the intermediate
router adds the downstream request router to the shared multicast tree as a branch. If not,
it continues to send the Join message to the RP.
When the RP or the multicast router connects to a receiver directly, it can switch to the
SPT from the shared tree. When the RP receives a Register message sent from a new
multicast source, the RP returns a Join message to the DR directly connecting to the
multicast source. Thus, the SPT from the source to the RP is constructed.
After a DR or a router directly connecting to multicast members receives the first multicast
packet from the multicast group, or the received packets reaches a threshold, it can switch
to the SPT from the shared tree. Once the handover occurs, the router sends a Prune
message to the upstream neighbor and requests to leave the shared tree.
14.2 Configuring IPv6 PIM-SM

This procedure describes how to configure PIM-SM, including basic information, global
parameters, and policy control function.
Steps
1. Enable and configure the IPv6 PIM-SM protocol.
1 ZXR10(config-mcast-ipv6)#router pim Enables IPv6 PIM.
2 ZXR10(config-mcast-ipv6-pim)#interface After IPv6 PIM-SM is enabled

<interface-name> on an interface, MLD is
enabled automatically on the
3 ZXR10(config-mcast-ipv6-pim-if-interface-
interface. By default, PIM-SM
name)#pimsm
is not enabled on an interface.
2. Configure static RP.
Command Function
ZXR10(config-mcast-ipv6-pim)#static-rp <ipv6-address Configures a static RP.

>[{[group-list <prefix-list-name>],[priority <priority>]}]
<ip-address>: The static RP address, in X:X::X:X format.

<priority>: The priority, range: 0 to 255, default: 192.
By default, no static RP is configured.
Usage descriptions of a static RP:
i. After a static RP is configured, it participates in RP set selection, even the router
does not receive any RP information advertisement of BSR.
ii. If the < prifix-list-name > parameter is not configured, the static RP is suitable for
all multicast groups.
14-3

The following example shows how to configure a static RP 2001::1 for all multicast
groups.
ZXR10(config-mcast-ipv6-pim)#static-rp 2001::1
3. Configure candidate BSR.
Command Function
ZXR10(config-mcast-ipv6-pim)#bsr-candidate <ipv6-ad Configures a candidate BSR.

dress>[{[hash-mask-length <hash-mask-length>],[priority
<priority>]}]
<hash-mask-length>: Hash mask length, range: 0 to 128.

<priority>: Priority, range: 0 to 255, default: 0.
If a static RP mechanism is not used, it is necessary to configure a candidate BSR on
one or more multicast routers in each multicast domain and elect a BSR.
A BSR sends bootstrap messages periodically to advertise the RP information. The
routers running PIM-SM update the RP state according to the latest advertisement
messages. The bootstrap messages sent by BSRs are also used to elect a formal
BSR among candidate BSRs.
The default priority of a candidate BSR is 0. The BSR with the highest priority becomes
the formal BSR. If several candidate BSR have the same highest priority, the one with
the largest IP address becomes the formal BSR.
4. Configure candidate RP.
Command Function
ZXR10(config-mcast-ipv6-pim)#rp-candidate Configures a candidate RP.

<ipv6-address>[{[group-list <prefix-list-name>],[priority
<priority>]}]
<prefix-list-name>: Group range in which the RP provides services.

<priority>: Candidate RP priority, range: 0 to 255, default: 0.
In PIM-SM, an RP is the root of the RPT. It is responsible for sending multicast packets
to downstream multicast receiving members along the RPT. There should be only one
formal RP in each multicast group.
Usage descriptions of a candidate RP:
i. If the <prefix-list-name> parameter is not configured, the candidate RP provides
services for all groups.
ii. The default priority of a candidate RP is 192. The RP with the smallest priority
value will become the RP. If some candidate RPs have the same smallest priority
value, the hash values are compared. The candidate RP with the largest hash
value will become the RP. If the hash values are the same, IP addresses are
compared. The candidate RP with the largest IP address will become the RP.
14-4

iii. It is recommended to configure a candidate RP on the loopback interface to reduce

network oscillation due to the physical interface being up/down.
5. Configure IPv6 PIM-SM global parameters.
In IPv6 PIM-SM, different parameters have different default values. Configuring these
parameters can optimize the network.
1 ZXR10(config-mcast-ipv6-pim)#spt-threshold Configures handover of the SPT.

infinity infinity: causes the router never
to move to the SPT tree. It
remains on the shared RP tree.
2 ZXR10(config-mcast-ipv6-pim-if-interface- Configures the DR priority on a

name)#dr-priority <priority> PIM interface.
Range: 0-4294967295, default:
1.
3 ZXR10(config-mcast-ipv6-pim-if-interface- Sets an interface to the border of

name)#bsr-border the PIM domain.
4 ZXR10(config-mcast-ipv6-pim-if-interface- Configures the interval to send

name)#hello-interval <seconds> Hello messages.
By default, the threshold to hand the RPT over to the SPT is 0.

Only the last hop DR and RP can hand over to the SPT on their own initiative. By
default, the handover begins when the RP receives the first Register message. For the
last hop DR, the policy of SPT handover can be configured by using a single multicast
group as the control granularity. If the handover threshold of a group is set to infinity,
handover will not be performed. By default, as long as there is traffic, a handover is
performed.
A DR must be elected in a shared (or multi-access) segment. The candidate DR with

the highest priority becomes the DR. If several candidate DRs have the same highest
priority, the one with the largest IP address becomes the DR.
In a shared segment connecting to the multicast source, only the DR can send Register
messages to RP. In a shared segment connecting to receivers, only the DR reply to the
MLD Join messages and Leaving messages, and send PIM Join/Pruning messages to
upstream devices. The router priority is contained in the Hello messages exchanged
with neighbors, with the default value of 1.
The following example shows how to configure the DR priority on gei-1/1.

ZXR10(config)#ipv6 multicast-routing
ZXR10(config-mcast-ipv6)#router pim
ZXR10(config-mcast-ipv6-pim)#interface gei-1/1
ZXR10(config-mcast-ipv6-pim-if-gei-1/1)#dr-priority 20
ZXR10(config-mcast-ipv6-pim-if-gei-1/1)#exit
14-5

By default, an interface is not the border of the PIM domain. When the interface is
set to the border of the PIM domain, no BSR messages can pass the border in any
direction. This function divides the network into different areas of BSR messages
effectively. Other PIM messages can pass the domain border.
The following example shows how to configure a PIM domain border on gei-1/1.
ZXR10(config-mcast-ipv6-pim-if-gei-1/1)#bsr-border
The intervals of sending Hello messages to PIM-SM neighbors can be set according
to demand.
The following example shows how to configure the intervals of sending PIM Hello
messages on gei-1/1.
ZXR10(config-mcast-ipv6-pim-if-gei-1/1)#hello-interval 25
6. Configure IPv6 PIM-SM control policy.
1 ZXR10(config-mcast-ipv6-pim)#accept-register < Filters the multicast packets

access-list-name > encapsulated in Register
messages.
2 ZXR10(config-mcast-ipv6-pim)#accept-rp Filters the candidate RP

<access-list-name> addresses advertised in the
Bootstrap messages.
Command Function
ZXR10(config)#show ipv6 pim mroute [group Displays the IPv6 PIM routing table.
<group-address>][source <source-address>]
ZXR10(config)#show ipv6 pim mroute summary Displays the summary information

about the PIM routing table.
ZXR10(config)#show ipv6 pim bsr Displays the information about the

BSR.
ZXR10(config)#show ipv6 pim rp mapping [{bsr | default | Displays the RP mapping

embedded | static}] information advertised by the
router.
14-6

Command Function
ZXR10(config)#show ipv6 pim rp hash <group-address> Displays the RP information

selected by a specific multicast
group.
ZXR10(config)#show ipv6 pim interface [<interface-name>] Displays the interface on which PIM
is configured.
ZXR10(config)#show ipv6 pim neighbor [<interface-name>] Displays the neighbor information

about an IPv6 PIM interface.
ZXR10(config)#show ipv6 pim nexthop [dest-address Displays the IPv6 PIM next hop
<ipv6-address>] information.
ZXR10(config)#show ipv6 pim traffic [<interface-name>] Displays traffic statistical information

about the IPv6 PIM protocol.
End of Steps
14.3 IPv6 PIM-SM Configuration Example

As shown in Figure 14-1, an MLD group connects to R2, and a multicast source connects
to R1. It is required to configure BSR neighbors and CRP.
Figure 14-1 PIM-SM Configuration Example
Configuration Flow
1. Configure addresses of related interfaces.
2. Enter multicast configuration mode.
3. Enter PIM configuration mode.
4. Set the loopback5 interface on R2 to CRP and BSR.
5. Enable PIM-SM on interfaces.
6. Configure a unicast route to the RP on R1. Configure a unicast route to the multicast
source on R2 (In this example, static route or IGP can be used).
14-7

R1(config-mcast-ipv6-pim-if-gei-0/7)#dr-priority 20
R2(config-mcast-ipv6-pim)#rp-candidate 100::1
R2(config-mcast-ipv6-pim)#bsr-candidate 100::1
R2(config-mcast-ipv6-pim-if gei-0/8)#exit
14-8

R2(config-mcast-ipv6-pim-if-gei-0/7)#dr-priority 20
Execute the show ipv6 pimsm interface command on R1 to check the interface state, as
shown below.
R1(config)#show ipv6 pim interface
Interface State Nbr Hello DR PIM Mode
Count Period Priority Silent
gei-0/7 Up 0 30 20 Disabled S
DR : fe80::2d0:d0ff:fe06:606
gei-0/9 Up 1 30 1 Disabled S
DR : fe80::2d0:d0ff:fe06:606
Execute the show ipv6 pim neighbor command on R1 to check the neighbor state, as shown
below.
R1(config)#show ipv6 pim neighbor
Neighbor Address(es) Interface Uptime Expires DR Pri
fe80::211:12ff:fe51:ea12 gei-0/9 01:02:30 00:01:19 1
Execute the show ipv6 pim bsr command on R1 to check the BSR state, as shown below.
R1(config)#show ipv6 pim bsr
BSR address: 100::1

Uptime: 00:17:48, BSR Priority :0, Hash mask length:126
Expires:00:01:22
No candidate RP information!
Execute the show ipv6 mroute command on R1 to check the IPv6 multicast routing table.
R1#show ipv6 mroute
(198::2, ff1e::1), TYPE: DYNAMIC, FLAGS:
gei-0/9, flags: F
14-9

14-10

Chapter 15
IPv6 PIM-SSM Configuration
Table of Contents
PIM-SSM Overview ..................................................................................................15-1
Configuring IPv6 PIM-SSM.......................................................................................15-1
IPv6 PIM-SSM Configuration Example .....................................................................15-2
15.1 PIM-SSM Overview

Protocol Independent Multicast-Source Specific Multicast (PIM-SSM) has all the
advantages of PIM-SM. PIM-SSM does not construct a shared tree. Instead, it only
constructs the SPT. When receiving the member relation report messages about a specific
source and a group, PIM-SSM constructs the SPT directly.
PIM-SSM is a subset of PIM-SM. PIM-SSM is suitable for the well known sources. It is
both intra-domain and inter-domain valid. PIM-SM uses MSDP for inter-domain multicast
routing. PIM-SSM does not need to use MSDP. The multicast group address allocated for
PIM-SSM is FF3X::/32. The routers do not construct a shared tree for this group address.
After a host sends a Join message from a specific source to a group, the last hop router
sends a (S, G) Join message to the direction of the source to construct a SPT. The last
hop router does not send a (*, G) Join message to the direction of RP. Once the SPT is
constructed, the first hop router forwards packets along this tree.
15.2 Configuring IPv6 PIM-SSM

This procedure describes how to configure IPv6 PIM-SSM.
Steps
1. Configure IPv6 PIM-SSM.
Command Function
ZXR10(config-mcast-ipv6-pim)#ssm range | default Configures address range of IPv6

[group-list < access-list-name >] SSM groups, or uses the default group
address range.
When the group-list is not configured,
the default group range is FF3X::/32.
15-1

Command Function
ZXR10#show ipv6 pim mroute [group <group-address Displays the IPv6 PIM routing table.
>][source <source-address>]
End of Steps
15.3 IPv6 PIM-SSM Configuration Example

As shown in Figure 15-1, PIM-SM is enabled on R1, and SSM is configured. Configure the
SSM group range. The MLD version is v2. The multicast source sends flows to multicast
groups of multiple specific sources. Only the traffic matching both the source address and
the multicast group address is allowed to pass through.
Figure 15-1 IPv6 PIM-SSM Configuration Example
Configuration Flow
1. In interface configuration mode, configure interface addresses on gei-1/1 and gei-1/2
of R1.
2. Enable the IP multicast function with the ipv6 multicast-routing command.
3. Enter IPv6 PIM route configuration mode to configure the address range of SSM group.
4. Enter the interfaces gei-1/1 and gei-1/2 to enable PIM-SM.
5. Enter MLD route configuration mode and then enter the interfaces to enable MLDv2.
6. Send dynamic group Join messages to specific source on the receiving group.
15-2

Chapter 15 IPv6 PIM-SSM Configuration
R1(config-mcast-ipv6-pim)#ssm range default
R1(config-mcast-ipv6-pim)#exit
Check the configuration information on R1, as shown below.
R1#show running-config multicast6

!<ipv6 multicast>
ipv6 multicast-routing
router pim
ssm range default
interface gei-1/2
pimsm
$
interface gei-1/1
pimsm
$
$
router mld
interface gei-1/1
$
interface gei-1/2
$
$
!</ipv6 multicast>
Check the result of the routes on R1, as shown below.
R1#show ipv6 mroute

(100::2, ff3a::aaaa:1), TYPE: DYNAMIC, FLAGS:
gei-1/2, flags: F
15-3

15-4

Chapter 16
IPv6 Tunnel Configuration
Table of Contents
IPv6 Tunnel Configuration ........................................................................................16-1
ISATAP Tunnel Configuration .................................................................................16-13
16.1 IPv6 Tunnel Configuration

16.1.1 IPv6 Tunnel Overview
IPv6 Tunnel Introduction
Tunneling is an encapsulation technology used to transmit another network protocol
through the use of one network protocol, that is, it utilizes one network transfer protocol
to encapsulate the data packets generated by other protocols into its own packets before
the packets are transmitted in the network.
The IPv6 over IPv4 tunnel mechanism is used to add an IPv4 header in the front of the
IPv6 data packet and then transfer the IPv6 packet through a tunnel so that the IPv6
packet traverses the IPv4 network to implement the interworking between two isolated
IPv6 networks, as shown in Figure 16-1.
Figure 16-1 Principles of the IPv6 over IPv4 Tunnel Mechanism
An IPv6 over IPv4 tunnel can be established between two hosts, between a host and a
router, or between two routers. The termination point of the tunnel may be the ultimate
destination of the IPv6 packet, or the packet may still need to be further forwarded.
Therefore, tunnels are classified into configured tunnels and automatic tunnels based on
the ways to obtain the destination IPv4 address of a tunnel.
16-1

l If the termination address of the IPv6 over IPv4 tunnel cannot be automatically
obtained from the destination address of the IPv6 packet but needs to be manually
configured, the tunnel is called a configured tunnel, such as a 6in4 tunnel.
l If the interface address of the IPv6 over IPv4 tunnel assumes a special
IPv4-embedded IPv6 address format (i.e. the IPv4 address of the tunnel termination
point can be automatically obtained from the destination address of the IPv6 packet),
the tunnel is called an automatic tunnel, such as a 6to4 tunnel or an ISATAP tunnel.
There is another type of IPv4 or IPv6 over IPv6 tunnel. The protocol encapsulates an IPv4
or IPv6 data packet so that the encapsulated data packet can be transmitted in another
IPv6 network. The data packet after the encapsulation is an IPv6 tunnel packet, as shown
in Figure 16-2.
Figure 16-2 Principles of the IPv4 (or IPv6) over IPv4 Tunnel
In Figure 16-2, Original data refers to the IPv4 or IPv6 packet.

A DS-list tunnel enables IPv4 users to access IPv4 Internet after traversing a pure IPv6
network. It implements carrier-class IPv4 address multiplex through IPv4-IPv4 NAT.
Packets are encapsulated and decapsulated in the tunnel on the forwarding plane.
6in4 Tunnel
Figure 16-3 shows the operating principles of a 6in4 tunnel.
Figure 16-3 Principles of a 6in4 Tunnel
The 6in4 tunnel involves a tunnel encapsulation and decapsulation process.
16-2

Chapter 16 IPv6 Tunnel Configuration
l Encapsulation: If the packet egress interface is a tunnel interface when an IPv6 host
or router sends an IPv6 flow, the host or router first determines the tunnel type. If
the tunnel is a 6in4 tunnel, the host or router implements IPv4 header encapsulation.
During the encapsulation, the source and destination addresses of the IPv4 header
are manually configured by the user. The encapsulated packet is then sent according
to the IPv4 packet sending process.
l Decapsulation: The process is just contrary to the encapsulation process. If the
protocol number in the IPv4 header of the received IPv4 packet is 41, the host or router
proceeds to the 6in4 decapsulation process and searches for the matched tunnel
number according to the source and destination addresses of the packet. If the tunnel
number is found, the host or router removes the IPv4 header added during tunnel
encapsulation and delivers the remaining IPv6 packet to the IPv6 packet receiving
process for further handling.
6to4 Tunnel
Figure 16-4 shows the operating principles of a 6to4 tunnel.
Figure 16-4 Principles of a 6to4 Tunnel
A 6to4 tunnel is a point-to-multipoint auto tunnel used to connect multiple isolated IPv6 sites
through an IPv4 network to an IPv6 network. It makes possible the automatic acquisition
of the IPv4 address at the termination point of the tunnel by embedding an IPv4 address
in the destination address of an IPv6 packet.
The 6to4 tunnel assumes a special 6to4 address in the format of 2002:abcd:efgh:Subnet
ID::InterfaceID/64. Of the address, 2002 is a fixed IPv6 address prefix, abcd:efgh is a
globally unique 32-bit IPv4 source address of the 6to4 tunnel in hexadecimal (e.g. 1.1.1.1
can be expressed as 0101:0101), and the rest uniquely identifies the position of a host in
a 6to4 network. As the termination point of the tunnel can be automatically determined by
this embedded IPv4 address, tunnel establishment is very convenient.
Because the 16-bit subnet ID in the 64-bit address prefix of the 6to4 address can be
user-defined whereas the first 48 bits of the prefix are a fixed number or determined by
the IPv4 address of the device at the start or termination point of a tunnel, it is possible to
forward IPv6 packets over the tunnel. The 6to4 tunnel makes possible the interconnection
16-3

of two IPv6 networks through an IPv4 network and thus eliminates the limitations of
automatic IPv4-compatible IPv6 tunnels in practical use.
The 6to4 tunnel involves a tunnel encapsulation and decapsulation process.
l Encapsulation: If the egress interface of the sent IPv6 packet is a tunnel interface,
the host first determines the tunnel type. If the tunnel is a 6to4 tunnel, the host
implements IPv4 header encapsulation. During the encapsulation, the source address
is user-configured whereas the destination address is obtained from the destination
address of the packet. The encapsulated packet is then sent according to the IPv4
packet sending process.
l Decapsulation: If the protocol number in the IPv4 header of the received IPv4 packet is
41, the host proceeds to the 6to4 decapsulation process and searches for the matched
tunnel number according to the source address of the packet. If the tunnel number
is found, the host removes the IPv4 header added during tunnel encapsulation and
delivers the remaining IPv6 packet to the IPv6 packet receiving process for further
handling.
4in6 Tunnel
Figure 16-5 shows the operating principles of a 4in6 tunnel.
Figure 16-5 Principles of a 4in6 Tunnel
The 4in6 tunnel involves a tunnel encapsulation and decapsulation process.

l Encapsulation: If the packet egress interface is a tunnel interface when a host or
router sends an IPv4 flow, the host or router first determines the tunnel type. If the
tunnel is a 4in6 tunnel, the host or router sends the packet to the IPv6 protocol stack
for IPv6 header encapsulation. During the encapsulation, the source and destination
addresses of the IPv6 header are manually configured by the user. The encapsulated
packet is then sent according to the IPv6 packet sending process.
l Decapsulation: The process is just contrary to the encapsulation process. If the
protocol number in the IPv6 header of the received IPv6 packet is 4, the host or router
proceeds to the 4in6 decapsulation process, and searches for the matched tunnel
number according to the source and destination addresses of the packet. If the tunnel
number is found, the host or router removes the IPv6 header added during tunnel
encapsulation and delivers the remaining IPv4 packet to the IPv4 packet receiving
process for further handling.
16-4

16.1.2 Configuring IPv6 Tunnels

The procedure describes how to configure IPv6 tunnels, including 6in4 tunnels, 6to4
tunnels, and 4in6 tunnels.
Steps
1. Create an IPv6 tunnel interface and enter IPv6 tunnel interface configuration mode.
1 ZXR10(config)#interface v6_tunnel<tunnel_no> Creates an IPv6 tunnel

interface, IPv6 tunnel number
range: 13000.
2 ZXR10(config)#ipv6-tunnel-config Enters IPv6 tunnel

configuration mode.
3 ZXR10(config-ipv6-tunnel)#interface {byname Enters IPv6 tunnel interface

<interface-byname>|<interface-name>} configuration mode. The
interface alias and interface
name can contain up to 32
characters.
2. Configure a 6in4 tunnel.
1 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Sets the current tunnel mode

mode ipv6ip 6in4 to 6in4.
2 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Specifies the source address

source ipv4 <src-address> of the tunnel, in IPv4 address
format.
3 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Specifies the destination

destination ipv4 <dst-address> address of the tunnel, in IPv4
address format.
3. Configure a 6to4 tunnel.

mode ipv6ip 6to4 to 6to4.

source ipv4 <src_address> of the tunnel, in IPv4 address
format.
4. Configure a 4in6 tunnel.
16-5


mode ipipv6 4in6 to 4in6.

source ipv6 <src_address> of the tunnel, in IPv6 address
format.
3 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Specifies the destination

destination ipv6 <dst_address> address of the tunnel, in IPv6
address format.
5. Maintain IPv6 tunnels.
Command Function
ZXR10#debug ipv6-tunnel Turns on the IPv6 tunnel debugging switch

to check relevant encapsulation and
decapsulation information.
ZXR10#show debug ipv6-tunnel Checks whether the IPv6 tunnel debugging

switch has been turned on.
End of Steps
16.1.3 IPv6 Tunnel Configuration Examples

16.1.3.1 Example: Configuring a 6in4 Tunnel
As shown in Figure 16-6, suppose R1 and R2 are dual-stack routers whereas PC1 and
PC2 are IPv6 hosts. This example describes how to configure a 6in4 tunnel.
Figure 16-6 6in4 Tunnel Configuration Example
16-6

Configuration Flow
The 6in4 tunnel is of v6 nature and thus IPv6 needs to be enabled. The source address
of the tunnel is the IPv4 address of the local router, whereas the destination address is
the IPv4 address of the peer router. There must be a route for interworking between the
source address and the destination address of the tunnel (via the IPv4 routing protocol,
the static routing protocol or other routing protocols).
1. Create 6in4 tunnel interfaces and enable IPv6 on them.
2. Enter the tunnel configuration mode from the global mode, and then enter the 6in4
tunnel interface to be configured.
3. Configure the tunnel mode, the source address, and the destination address.
R1(config)#interface v6_tunnel3
R1(config-if-v6_tunnel3)#ipv6 enable
R1(config-if-v6_tunnel3)#ipv6 address 3172::27/64
R1(config-if-v6_tunnel3)#exit
R1(config)#ipv6-tunnel-config
R1(config-ipv6-tunnel)#interface v6_tunnel3
R1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel mode ipv6ip 6in4
R1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel destination ipv4 33.1.1.28
R1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel source ipv4 33.1.1.27
R1(config-ipv6-tunnel-if-v6_tunnel3)#exit
R1(config-ipv6-tunnel)#exit
R1(config-if-gei-2/4)#ip address 33.1.1.27 255.255.0.0
R2(config-if-v6_tunnel3)#ipv6 address 3172::28/64
R2(config-ipv6-tunnel-if-v6_tunnel3)#tunnel mode ipv6ip 6in4
16-7

R2(config-ipv6-tunnel-if-v6_tunnel3)#tunnel destination ipv4 33.1.1.27

Check the tunnel configurations on R1, and verify that the configurations have taken effect:
R1(config)#show running-config-interface v6_tunnel3

! <INTERFACE>
interface v6_tunnel3
ipv6 enable
$
! </INTERFACE>
! <ipv6_TUNNEL>
ipv6-tunnel-config
tunnel mode ipv6ip 6in4
tunnel source ipv4 33.1.1.27
tunnel destination ipv4 33.1.1.28
! </ipv6_TUNNEL>
R1(config)#show ip interface gei-2/4

gei-2/4 AdminStatus is up, PhyStatus is up, line protocol is up
Internet address is 33.1.1.27/16
Broadcast address is 255.255.255.255
IP MTU is 1500 bytes
R1(config)#show ipv6 interface brief

v6_tunnel3 [up/up]
fe80::2101:11b
3172::27/64
16-8

16.1.3.2 Example: Configuring a 4in6 Tunnel
PC2 are IPv4 hosts. This example describes how to configure a 4in6 tunnel.
Figure 16-7 4in6 Tunnel Configuration Example
Configuration Flow
The 4in6 tunnel is of v4 nature. The source address of the tunnel is the IPv6 address of
the local router, whereas the destination address is the IPv6 address of the peer router.
There must be a route for interworking between the source address and the destination
address of the tunnel (via the IPv6 routing protocol, the static routing protocol or other
routing protocols).
1. Create a 4in6 tunnel and configure IPv4 addresses.
2. Enter the tunnel configuration mode from the global mode, and then enter the 4in6
3. Configure the tunnel mode, the source address, and the destination address.
R1(config-if-v6_tunnel2)#ip address 27.0.1.1 255.255.0.0
R1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipipv6 4in6
R1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel destination ipv6 2078::28
R1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel source ipv6 2078::27
16-9

R2(config-if-v6_tunnel2)#ip address 27.0.1.2 255.255.0.0
R2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipipv6 4in6
R2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel destination ipv6 2078::27
R2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel source ipv6 2078::28

!<INTERFACE>
ip address 27.0.1.1 255.255.0.0
$
! </INTERFACE>
!<ipv6_TUNNEL>
ipv6-tunnel-config
tunnel mode ipipv6 4in6
tunnel source ipv6 2078::27
16-10

tunnel destination ipv6 2078::28

!</ipv6_TUNNEL>
R1(config)#show ip interface v6_tunnel2
v6_tunnel2 AdminStatus is up, PhyStatus is up, line protocol is up
Internet address is 27.0.1.1/16
Broadcast address is 255.255.255.255
IP MTU is 1460 bytes
16.1.3.3 Example: Configuring a 6to4 Tunnel
PC2 are IPv6 hosts. This example describes how to configure a 6to4 tunnel.
Figure 16-8 6to4 Tunnel Configuration Example
Configuration Flow
A 6to4 tunnel is of v6 nature and thus IPv6 needs to be enabled to connect the 6to4 node
prefixed with 2002::/16. The source end of the tunnel is bound with the IPv4 address of
the local router, and no destination address is required. The tunnel address must assume
a 2002::/16 prefix.
1. Create a 6to4 tunnel, configure IPv6 addresses, and enable IPv6. The first 48 bits of
the tunnel address and the 6to4 sites are of a fixed format and generated according to
the source IPv4 address of the tunnel: Convert the x.x.x.x of the source IPv4 address
of the tunnel into a hexadecimal yyyy:yyyy, and then add 2002::/16 to it to form a 48-bit
prefix 2002:yyyy:yyyy::/48.
2. Enter the tunnel configuration mode from the global mode, and then enter the 6to4
3. Configure the tunnel mode and the source address.
4. Advertise the tunnel route through static routing or BGP4+.
16-11

R1(config-if-v6_tunnel2)#ipv6 address 2002:0101:0101:1::1/64
R1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip 6to4
R1(config)#ipv6 route 2002::/16 v6_tunnel2
R2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip 6to4

! <INTERFACE>
ipv6 enable
ipv6 address 2002:101:101:1::1/64
!
! </INTERFACE>
! <ipv6-tunnel>
ipv6-tunnel-config
16-12

tunnel mode ipv6ip 6to4
! </ipv6-tunnel>
R1(config)#show ipv6 interface brief
v6_tunnel2 [up/up]
fe80::101:101
2002:101:101:1::1/64
16.2 ISATAP Tunnel Configuration

16.2.1 ISATAP Tunnel Overview
ISATAP Tunnel Introduction
With the wide applications of IPv6 technology, there are more IPv6 hosts on the
current IPv4 network. Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnel
technology provides a good solution for such application. ISATAP can obtain the
destination of a tunnel automatically by embedding an IPv4 address in the destination
address of an IPv6 packet.
When an ISATAP tunnel is used, the destination address of an IPv6 packet and the IPv6
address of a tunnel interface should use special ISATAP addresses. The format of an
ISATAP address is Prefix (64 bit):0:5EFE:ip-address. The 64-bit prefix is the prefix of a
legal IPv6 unicast address, and the ip-address is a 32-bit IPv4 source address (in the
a.b.c.d format or abcd:efgh format). Through this embedded IPv4 address, a tunnel can
be established automatically to transmit IPv6 packets. ISATAP tunnels are mainly used to
establish connections between IPv6 routers, and between IPv6 hosts and IPv6 routers on
the IPv4 network.
ISATAP Tunnel Work Flow

ISATAP encapsulation and decapsulation are described below.
l Encapsulation principle: When an IPv6 is sent, the egress is an tunnel interface. The
tunnel type is determined according to packet call-back on the interface. If it is an
ISATAP tunnel, IPv4 header encapsulation is performed. An ISATAP tunnel follows the
encapsulation format of a 6in4 tunnel. The outer IPv4 destination address is the IPv4
address embedded in the destination address of the IPv6 packet, and the outer IPv4
source address is the source address of the ISATAP tunnel. After the encapsulation,
the packet is handled according to the common IPv4 packet sending flow.
l Decapsulation principle: The decapsulation flow of an ISATAP tunnel is the same as
that of a 6in4 tunnel. When an IPv4 packet is received and the protocol number in
the IPv4 header is 41, the protocol number processing functions registered for IPv4
are called and the 6in4 decapsulation function is used. The device searches for the
matched tunnel entity according to the source address and destination address of
16-13

the packet. If the matched tunnel entity is found, the IPv4 header encapsulated is
removed, and the left IPv6 packet is handled according to the IPv6 packet receiving
flow.
Figure 16-9 shows the ISATAP tunnel principle.
Figure 16-9 ISATAP Tunnel Principle
16.2.2 Configuring ISATAP Tunnels

This procedure describes how to configure ISATAP tunnels.
Steps
1. Configure an ISATAP tunnel.
1 ZXR10(config)#interface v6_tunnel<tunnel_no> Creates an IPv6 tunnel

interface.
2 ZXR10(config-if-v6_tunnel)#ipv6 enable Enables IPv6.
3 ZXR10(config-if-v6_tunnel)#ipv6 address <addrprefix Configures an eui-64 address

/ prefix-len> eui-64 on an interface for an ISATAP
tunnel.
4 ZXR10(config)#ipv6-tunnel-config Enters IPv6 tunnel

configuration mode.
5 ZXR10(config-v6_tunnel)#interface {byname Enters IPv6 tunnel interface

interface alias and interface
name can contain up to 32
characters.
6 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Sets the tunnel mode to

mode ipv6ip isatap isatap.
16-14

7 ZXR10(config-ipv6-tunnel-if-v6_tunnel)#tunnel Configures the source

source ipv4 <src-addr> address of an tunnel. It is
only necessary to specify the
IPv4 level and unnecessary to
specify the source address.
<tunnel_no>: Tunnel number, indicating the number of tunnel interfaces that can be
created, range: 1 to 3000.
<src-addr>: Source address on the egress of the tunnel.
<addrprefix /prefix-len>: IPv6 address prefix and prefix length.
2. Maintain the ISATAP tunnel.
Command Function
ZXR10#debug ipv6-tunnel Enables IPv6 tunnel debugging function to

show the information related to encapsulation
and decapsulation.
ZXR10#show debug ipv6-tunnel Displays whether the IPv6 tunnel debugging

function is enabled.
End of Steps
16.2.3 ISATAP Configuration Example

As shown in Figure 16-10, assume that R1 and R2 are dual-stack routers, PC1 and PC2
are IPv6 hosts. It is required to configure an ISATAP tunnel.
Figure 16-10 ISATAP Configuration Example
16-15

Configuration Flow
To configure an ISATAP tunnel, it is necessary to enable IPv6 and bind the IPv4 address
of the router at the source end of the tunnel. It is unnecessary to configure the destination
address. The configuration steps are described below:
1. Create an ISATAP tunnel. Configure an IPv6 address and enable IPv6. The IPv6
address on the ISATAP interface uses eui mode.
2. Enter tunnel configuration mode from global configuration mode, and then enter the
ISATAP tunnel interface to be configured.
3. Configure the tunnel mode and the source address.
4. Configure static routes or BGP4+ to advertise the tunnel route.
R1(config-if-gei-2/4)#ip add 1.1.1.1 255.255.255.0
R1(config-if-v6_tunnel2)#ipv6 add 82::/64 eui-64
R1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip isatap
R2(config-if-gei-3/4)#ip add 1.1.1.2 255.255.255.0
R2(config-if-v6_tunnel2)#ipv6 add 81::/64 eui-64
R2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip isatap
16-16

Check the ISATAP configuration on R1, as shown below.

!<Interface>
ipv6 enable
ipv6 address 82::/64 eui-64
$
!</Interface>
!<ipv6-tunnel>
ipv6-tunnel-config
tunnel mode ipv6ip isatap
$
$
!</ipv6-tunnel>
!<ipv6-static>
ipv6 route 81::/16 v6_tunnel2
!</ipv6-static>
Execute the show ipv6 interface brief v6_tunnel2 command on R1 to view the tunnel
interface information, as shown below.
R1(config)#show ipv6 interface brief v6_tunnel2
v6_tunnel2 [up/up]
fe80::5efe:101:101
82::5efe:101:101/64 [EUI]
16-17

16-18

Chapter 17
6RD Configuration
Table of Contents
6RD Overview ..........................................................................................................17-1
Configuring 6RD Tunnels .........................................................................................17-5
6RD Configuration Example .....................................................................................17-6
17.1 6RD Overview

Introduction
6rd specifies a protocol mechanism to deploy IPv6 to sites through a service providers
(SPs) IPv4 network. It builds on 6to4, with the key differentiator that it utilizes an SPs own
IPv6 address prefix rather than a well-known prefix (2002::/16). By using the SPs IPv6
prefix, the operational domain of 6rd is limited to the SP network, and is under its direct
control. From the perspective of customer sites and the IPv6 Internet at large, the IPv6
service provided is equivalent to native IPv6.
The 6rd mechanism relies upon an algorithmic mapping between the IPv6 and IPv4
addresses that are assigned for use within the SP network. This mapping allows for
automatic determination of IPv4 tunnel endpoints from IPv6 prefixes, allowing stateless
operation of 6rd.
A 6rd domain consists of 6rd Customer Edge (CE) routers and one or more 6rd Border
Relays (BRs). IPv6 packets encapsulated by 6rd follow the IPv4 routing topology within
the SP network among CEs and BRs. 6rd BRs are traversed only for IPv6 packets that
are destined to or are arriving from outside the SPs 6rd domain. As 6rd is stateless, BRs
may be reached using anycast for failover and resiliency.
6rd utilizes the same encapsulation and base mechanism as 6to4, and could be viewed as
a superset of 6to4 (6to4 could be achieved by setting the 6rd prefix to 2002::/16). Unlike
6to4, 6rd is for use only in an environment where a service provider closely manages the
delivery of IPv6 service. 6to4 routes with the 2002::/16 prefix may exist alongside 6rd in
the 6rd CE router, and doing so may offer some efficiencies when communicating directly
with 6to4 routers.
6rd Prefix Delegation

Figure 17-1 shows the format of an IPv6 address with a 6rd prefix and an embedded CE
IPv4 address.
17-1

Figure 17-1 6rd Prefix Delegation
The IPv4 address can be a global unicast address or an aggregation of private addresses.
l Global unicast address
The IPv6 address prefix in a 6rd domain is a CE-based global IPv4 prefix, see Figure
17-2, and can be transmitted in a manual or protocol way (through DHCPv4 or TR-69).
A subnet IPv4 prefix is algorithmically obtained from an IPv6 prefix.
Figure 17-2 A Global Unicast Address
l Private address aggregation

As shown in Figure 17-3, a private address differs from a global IPv4 unicast address
in that:
It reduces the number of bits for an IPv6 prefix.
Domain ID overlays the private IPv4 space.
The IPv6 prefix is fixed in format.
Figure 17-3 Private Address Aggregation
6rd Address Selection

The CE 6rd configuration can be performed manually, which may be rather difficult in
practice. Controlling the 6rd configuration in a centralized way can be implemented by
carrying it in a CE IPv4 address assigned by a DHCP server.
17-2

Chapter 17 6RD Configuration
A CE assigns the IPv6 address of the CE LAN side to a downstream user through DHCPv6
or SLAAC based on the prefix.
Message Forwarding
l Forwarding a message in a 6rd domain
As shown in Figure 17-4, upon arrival of a message from PC1, CPE1 obtains the IPv4
address from the IPv6 destination address after a decapsulation, encapsulates the
message into a 6in4 tunnel, and forwards it to CPE2. Upon receipt of the message,
CPE2 obtains the raw message after a decapsulation, and forwards it to PC3. PC1
and PC2 can be on the same IPv6 subnet. The blue line in Figure 17-4 illustrates the
message forwarding direction.
Figure 17-4 Forwarding a Message in a 6rd Domain
CPE1 works as follows.

1. Upon receipt of a message destined for 2001:db8:0a0a:100::0:0202:0202, CPE1
determines that the next-hop is the tunnel based on the IPv6 route (::/0 -> tunnel1
via 2001:db8:0:100:).
2. The IPv6 destination address indicates that this IPv6 message is addressed to
the same domain. CPE1 then encapsulates the message into a tunnel with the
carried IPv4 address being the destination address.
3. Search the route, and forward the message to CPE2.
CPE2 works as follows.
1. Upon detecting a 6rd label on the IPV4 route, CPE2 decapsulates the received
IPv4 message, and obtains the raw IPv6 message.
2. Forward the raw IPv6 message to (2001:db8:0a0a:100::0:0202:0202).
l Forwarding a message out of a 6rd domain
As shown in Figure 17-5, upon receipt of a message from PC1, CPE1 determines that
the message is addressed to an out-of-domain area by matching the IPv6 prefix. It
then encapsulates the message into a 6in4 tunnel with the destination address being
17-3

the BR address. Upon receipt of the message, BR obtains the raw IPv6 message
after a decapsulation, and forwards it to PC3 (or an IPv6 WAN).
Figure 17-5 Forwarding a Message out of a 6rd Domain
CPE1 works as follows:

1. Upon receipt of a message destined for 200:1, CPE1 determines that the next-hop
is the tunnel based on the IPv6 route (::/0 -> tunnel1 via 2001:db8:0:100:).
2. The IPv6 destination address indicates that the message is addressed to outside
of the domain. This means that the message needs to be forwarded by BR, that is,
the destination address to be encapsulated is that of BR, and the source address
to be encapsulated is that configured for the tunnel. Perform a 6in4 encapsulation.
3. Search the route, and forward the message to BR.
BR works as follows:
1. Check whether there is a 6rd label on the IPv4 route.
2. If the 6rd label is found, decapsulate the message.
3. Forward the message to 200::1.
l Forwarding a message to a 6rd domain
Upon receipt of a message from a WAN, BR performs a decapsulation, and gets the
CPE1 IPv4 address from the carried IPv6 destination address, see Figure 17-6. It
then encapsulates the message into a 6in4 tunnel, and forwards it to CPE1. After a
decapsulation, CPE1 gets the raw IPv6 message, and forwards it to the destination
device within the 6rd domain.
17-4

Figure 17-6 Forwarding a Message to a 6rd domain
BR works as follows:
1. Upon receipt of a message destined for 2001:db8:0:0100::0:0101:0102, BR

determines that the next-hop is the tunnel based on the IPv6 route (2001:db8::/32
-> tunnel).
2. Perform a 6in4 encapsulation. The IPv6 destination address indicates that the
message is an IPv6 message addressed to a 6rd domain. This means that the
message needs to be forwarded by BR to CPE1. BR therefore obtains the IPv4
address from the IPv6 destination address, and uses it as the destination address.
3. Search the route, and forward the message.
CEP1 works as follows:
1. Check whether there is a 6rd label on the IPv4 route.

2. If a 6rd label is found, perform a decapsulation.
3. Forward the message to 2001:db8:0:100::/64.
17.2 Configuring 6RD Tunnels

This procedure describes how to configure 6RD tunnels.
Steps
1. Configure a 6RD tunnel.
1 ZXR10(config)#interface v6_tunnel <tunnel_no> Creates the interface of the IPv6

tunnel.
2 ZXR10(config)#ipv6-tunnel-config Enters IPv6 tunnel mode.
3 ZXR10(config-ipv6-tunnel)#interface {byname Enters IPv6 tunnel interface

interface alias and name can
contain up to 32 characters.
17-5

4 ZXR10(config-ipv6-tunnel-if-interface-name)#t Sets tunnel mode to 6RD.

unnel mode ipv6ip 6rd
5 ZXR10(config-ipv6-tunnel-if-interface-name)#t Configures the source address

unnel source ipv4 <src-addr> of the tunnel, in IPv4 address
format.
6 ZXR10(config-ipv6-tunnel-if-interface-name)#t Configures the IPv6 prefix of

unnel 6rd-prefix <ipv6-address-mask> the 6RD tunnel. Length range:
0128.
7 ZXR10(config-ipv6-tunnel-if-interface-name)#t Configures the IPv4 mask of the

unnel 6rd-ipv4-mask-length <lenth> 6RD tunnel, namely the IPv4
prefix of the 6RD tunnel. Length
range: 032.
<tunnel_no>: serial number of the tunnel. Up to 3000 tunnels can be created.
<ipv6-address-mask>: IPv6 prefix of the 6RD tunnel, length range: 0128.

<lenth>: Length of the IPv4 mask code of the 6RD tunnel, range: 032.
2. Maintain the 6RD tunnel.
Command Description
ZXR10#debug ipv6-tunnel Enables the debug feature for

the specified IPv6 tunnel.
ZXR10#show debug ipv6-tunnel Displays whether the debugging

function of the IPv6 tunnel is
enabled.
End of Steps
17.3 6RD Configuration Example

The following 6RD configuration is based on the networking topology shown in Figure 17-7.
Both R1 and R2 (ZXR10 ZSR V2) can serve as 6rd Border Relays (BRs).
17-6

Figure 17-7 An Example of Configuring 6RD
Configuration Flow
1. Establish a 6RD tunnel between a CPE device and R2. In the following configuration,
a 6RD tunnel is established between CPE2 and R2.
2. Create IPv6 tunnels on R1 and R2, and enable the IPv6 function.
3. Configure the working mode of IPv6 tunnels to 6rd, and set corresponding parameters.
4. Configure the IPv6 addresses on the IPv6 tunnels based on the 6rd rule.
5. Configure an IPv4 route on R1, so that there is an IPv4 route between R2 and CPE
(R1 forwards IPv4 packets only).
/*Configure a v4 route, so that there is v4 route between address 10.0.0.2 on
device CPE2 and the gei-1/1 interface on R2. The configuration is omitted.*/
17-7

R2(config-ipv6-tunnel-if-v6_tunnel1)#tunnel mode ipv6ip 6RD
R2(config-ipv6-tunnel-if-v6_tunnel1)#tunnel 6RD-ipv4-mask-length 0
/*Configure tunnel mode ipv6ip 6RD first, and then configure 6RD-ipv4-mask-length
and other parameters. Otherwise, the system prompts: "%Code 130024: 6RD mode
needs config first!"*/
R2(config-ipv6-tunnel-if-v6_tunnel1)#tunnel 6RD-prefix 3000::1/32
/*The configuration of a v4 route to address 10.0.0.2 on device CPE2 is omitted.*/
Run the debug ipv6-tunnel command, and run the ping6 command on R1. The sample
output is as follows.
R2#ping6 3000:0:a00:2::1
sending 5,100-byte ICMP echo(es) to 3000:0:A00:2:0:0:0:1,timeout is 2 second(s).
R2 MPFU-12/0 2012-10-25 15:54:19 v6_tunnel1: Ipv6/Ip(6rd) packet to be
encapsulated: 3000:0:100:1::1-->3000:0:a00:2::1 (len=100 ttl=64)
R2 MPFU-12/0 2012-10-25 15:54:19 v6_tunnel1: Ipv6/Ip(6rd) packet encapsulated:

1.0.0.1-->10.0.0.2 (len=120 ttl=255)
The above information shows that the correct destination IPv4 address is resolved on R2.
17-8

Chapter 18
6PE Configuration
Table of Contents
6PE Overview ..........................................................................................................18-1
Configuring 6PE .......................................................................................................18-2
6PE Configuration Example......................................................................................18-2
18.1 6PE Overview

IPv6 Provider Edge (referred to as 6PE in short) enables isolated IPv6 CE routers to
communicate with each other through IPv4 PE routers over an MPLS IPv4 backbone
network.
6PE has the following features:
l The IPv6 protocol is implemented only on the specified PE routers.
l The PE routers use the MP-BGP protocol to transmit IPv6 routes over the backbone
network
l The MPLS label is assigned to the IPv6 routes by the PE routers, and transparently
transmitted between the PE routers.
l A two-layer MPLS label stack is used to transmit IPv6 packets over the MPLS IPv4
backbone network. The labels are classified into the LDP labels (in the first layer) for
the egress PE routers and the PE IPv6 labels (in the second layer)
During implementations, the MPLS-labeled IPv6 routes are advertised through MP-BGP.
Figure 18-1 illustrates the implementation of 6PE.
Figure 18-1 6PE Implementation
18-1

18.2 Configuring 6PE

This procedure describes how to configure 6PE.
Steps
1. Configure 6PE.
1 ZXR10(config)#router bgp <as-number> Enters the BGP configuration

mode.
2 ZXR10(config-bgp)#address-family ipv6 Enters the IPv6 unicast address

3 ZXR10(config-bgp-af-ipv6)#neighbor Enables IPv6 for IPv4

{<ipv4-address>|<peer-group-name>} activate neighbors.
4 ZXR10(config-bgp-af-ipv6)#neighbor Enables label advertisement for

{<ipv4-address>|<peer-group-name>} send-labe neighbors.
Command Description
ZXR10(config)#show bgp ipv6 unicast neighbor <ipv4-address> Displays the detailed information
about the IPv6 neighbor.
ZXR10(config)#show bgp ipv6 unicast labels Displays the label information

relating to BGP IPv6 routes.
End of Steps
18.3 6PE Configuration Example

As shown in Figure 18-2, PE1 and PE2 are configured with 6PE. PE1 and PE2 establish
LDP neighbors and OSPF neighbors via the direct connection interfaces to advertise
their loopback1 interface addresses, and establish MP-BGP neighbors via the loopback1
interfaces to advertise their IPv6 network segments and redistribute the direct IPv6 route.
18-2

Chapter 18 6PE Configuration
Figure 18-2 6PE Configuration Example
Configuration Flow
1. Configure IPv4 addresses for the direct connection interfaces between PE1 and PE2.
Configure loopback interfaces and IPv4 addresses for the loopback interfaces on each
router. Enable IPv6 on IPv6 interfaces, and configure IPv6 addresses for the IPv6
interfaces.
2. Establish LDP neighbors via the direct connection interfaces between PE1 and PE2.
3. Establish OSPF neighbors via the direct connection interfaces between PE1 and PE2
to advertise the loopback1 interface addresses of the two routers.
4. Establish MP-BGP neighbors via the loopback1 interface between PE1 and PE2 to
advertise the IPv6 network segments of the two routers and redistribute the direct
IPv6 route.
5. Check the configuration results, and verify the following: LDP, OSPF and BGP
neighbors have been correctly established on the two routers, routes with IPv6 labels
can be seen on each router, and routes are generated.
Command Commands
PE1(config-if-gei-3/10)#ipv6 address 2255::66/64
PE1(config-if-loopback5)#ipv6 enable
PE1(config-if-loopback5)#ipv6 address 3555::52/64
18-3


PE1(config-ldp-1-if-gei-3/9)#discovery transport-address interface
PE1(config-ospf-1)#router-id 1.1.1.1

PE1(config-bgp)#no synchronization
PE1(config-bgp)#neighbor 2.2.2.2 activate
PE1(config-bgp)#address-family ipv6
PE1(config-bgp-af-ipv6)#redistribute connected
PE1(config-bgp-af-ipv6)#neighbor 2.2.2.2 activate
PE1(config-bgp-af-ipv6)#neighbor 2.2.2.2 send-label
PE1(config-bgp-af-ipv6)#network 2255::/64
PE1(config-bgp-af-ipv6)#exit
PE2(config-if-gei-1/2)#ipv6 address 2352::52/64
PE2(config-if-loopback5)#ipv6 enable
PE2(config-if-loopback5)#ipv6 address 2355::10/64
18-4


PE2(config-ldp-1-if-gei-1/1)#discovery transport-address interface
PE2(config-ospf-1)#router-id 2.2.2.2

PE2(config-bgp)#no synchronization
PE2(config-bgp)#address-family ipv6
PE2(config-bgp-af-ipv6)#neighbor 1.1.1.1 activate
PE2(config-bgp-af-ipv6)#neighbor 1.1.1.1 send-label
PE2(config-bgp-af-ipv6)#network 2352::/64
PE2(config-bgp-af-ipv6)#end
Run the commands show running-config ospf and show running-config bgp to check the
OSPF and BGP configurations on each router.
Check the configurations on PE1:
PE1#show running-config ospfv2
!<ospfv2>
router ospf 1
router-id 1.1.1.1
network 56.41.10.0 0.0.0.255 area 0.0.0.0
network 1.1.1.1 0.0.0.0 area 0.0.0.0
$
!</ospfv2>

!<route-bgp>
router bgp 100
18-5


address-family ipv4 multicast
$
address-family l2vpn vpls
$
$
address-family vpnv4 mcast
$
address-family vpnv4 multicast
$
address-family ipv6
network 2255::/64
neighbor 2.2.2.2 send-label
$
$
$
address-family route-target
$
$
!</route-bgp>
Run the show ip ospf neighbor command to check OSPF neighbor establishment on the
router. If the State is FULL, it indicates that the neighbor has been established, as shown
below:
PE1#show ip ospf neighbor

OSPF Router with ID (1.1.1.1) (Process ID 1)
Neighbor ID Pri State DeadTime Address Interface
2.2.2.2 1 FULL/DR 00:00:35 56.41.10.10 gei-3/9
Verify that the OSPF neighbor has advertised the loopback1 route, as shown below:
PE1#show ip forwarding route ospf

IPv4 Routing Table:
Codes : BROADC: Broadcast, USER-I: User-ipaddr, USER-S: User-special,
MULTIC: Multicast, USER-N: User-network, DHCP-D: DHCP-DFT,
ASBR-V: ASBR-VPN, STAT-V: Static-VRF, DHCP-S: DHCP-static,
GW-FWD: PS-BUSI, NAT64: Stateless-NAT64, LDP-A: LDP-area,
GW-UE: PS-USER, P-VRF: Per-VRF-label, TE: RSVP-TE;
18-6

Status codes: *valid, >best;

Dest Gw Interface Owner Pri Metric
2.2.2.2/32 56.41.10.10 gei-3/9 OSPF 110 2
Run the show ip bgp summary command to check BGP neighbor establishment on the
router:
PE1#show ip bgp summary

2.2.2.2 4 100 32 35 00:17:00 0
Check the IPv6 route advertised by the BGP neighbor:
PE1(config-bgp-af)#show ipv6 forwarding route bgp

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2352::/64 B 0
gei-3/9 200 ::ffff:2.2.2.2
2355::/64 B 0
gei-3/9 200 ::ffff:2.2.2.2
Check the labels of the IPv6 routes:
PE1#show bgp ipv6 unicast labels

Network Next Hop In Label/Out Label
2255::/64 2255::66 212997/notag
2352::/64 ::ffff:2.2.2.2 213031/212998
2355::/64 ::ffff:2.2.2.2 213024/212999
3555::/64 3555::52 213020/notag
Similarly, check the configurations on PE2:
PE2#show running-config ospfv2

!<ospfv2>
router ospf 1
router-id 2.2.2.2
network 56.41.10.0 0.0.0.255 area 0.0.0.0
network 2.2.2.2 0.0.0.0 area 0.0.0.0
$
!</ospfv2>
!</route-bgp>
router bgp 100
18-7


$
address-family l2vpn vpls
$
$
address-family vpnv4 mcast
$
address-family vpnv4 multicast
$
address-family ipv6
network 2352::/64
neighbor 1.1.1.1 send-label
$
$
$
address-family route-target
$
$
!</route-bgp>
PE2#show ip ospf neighbor

OSPF Router with ID (56.41.41.10) (Process ID 1)
Neighbor ID Pri State DeadTime Address Interface

1.1.1.1 1 FULL/BDR 00:00:35 56.41.10.11 gei-1/1
PE2#show ip forwarding route ospf

IPv4 Routing Table:
Dest Gw Interface Owner Pri Metric
1.1.1.1/32 56.41.10.11 gei-1/1 o 110 2
PE2#show ip bgp summary

1.1.1.1 4 100 31 30 00:15:51 0
PE2(config-bgp-af)#show ipv6 forwarding route bgp

IPv6 Routing Table:
18-8


Dest Owner Metric
Interface Pri Gw
2255::/64 B 0
gei-1/1 200 ::ffff:2.2.2.2
3555::/64 B 0
gei-1/1 200 ::ffff:2.2.2.2
PE2#show bgp ipv6 unicast labels

2255::/64 ::ffff:1.1.1.1 212994/212997
2352::/64 2352::52 212998/notag
2355::/64 2355::10 212999/notag
3555::/64 ::ffff:1.1.1.1 213027/213020
18-9

18-10

Chapter 19
6VPE Configuration
Table of Contents
6VPE Overview ........................................................................................................19-1
Configuring 6VPE.....................................................................................................19-2
6VPE Configuration Example ................................................................................. 19-11
19.1 6VPE Overview

IPv6 VPN Provider Edge (6VPE) is a technology that provides BGP Multi Protocol Label
Switching (MPLS) Virtual Private Network (VPN) service on an IPv6 network. The 6VPE
technology originates from IPv4 BGP MPLS VPN. It is an extension of the IPv4 BGP MPLS
VPN.
The handling procedure on the 6VPE control plane consists of six steps.
1. 6VPE uses IPv4/IPv6 IGP (such as OSPF/OSPFv3) to establish the routes among
backbone routers. The loopback address of a 6VPE router is advertised to all P routers
and other 6VPE routers on the network.
2. 6VPE uses IPv4/IPv6 label distribution protocols (such as Label Distribution Protocol
(LDP), Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE)) to establish
Label Switch Paths (LSPs) among 6VPE routers, that is, the MPLS tunnels among
6VPE routers.
3. 6VPE routers contact each other according to the VPN route reachability information.
It is necessary to configure IPv4/IPv6 Virtual Route Forwarding (VRF).
4. 6VPE routers obtain route reachability information from Customer Edge (CE) routers
on IPv4/IPv6 sites.
5. 6VPE routers distribute labels for route reachability information, and advertise the
reachability information for address prefixes in VPNs through the extended attributes
of MP-BGP. If the user network that 6VPE routers connected to uses the IPv4
protocol, the route reachability information uses VPN-IPv4 address family. If the user
network that 6VPE routers connected to uses the IPv6 protocol, the route reachability
information uses new-defined VPN-IPv6 address family.
6. 6VPE routers advertise IPv4/IPv6 route reachability information to IPv4/IPv6 CE sites
through IPv4/IPv6 routing protocols.
According to the 6VPE handling procedure, the key part of 6VPE is that the VPN-IPv6
address family is defined to distinguish the IPv6 routing information from different VPNs.
VPN-IPv6 is a new-defined address family. In the extended attributes of MP-BGP, the
codes of VPN-IPv6 address family are expressed as:
l AFI = 2: indicating IPv6
19-1

l SAFI = 128: indicating a VPN-IPv6 address
The format of a VPN-IPv6 address is shown in Figure 19-1. The length of the Route
Distinguisher (RD) is 8 bytes, and the length of the IPv6 address is 16 bytes. 6VPE does
not limit the IP version of the backbone network, so IPv6 VPN traffic can be transmitted in
IPv6 tunnels or IPv4 tunnels.
Figure 19-1 VPN-IPv6 Address Format
19.2 Configuring 6VPE

This procedure describes how to configure the 6VPE function on the PE and CE devices
in the MPLS VPN network to provide the VPN service to IPv6 users.
Steps
1. Create VRF and activate IPv6 address family.
1 ZXR10(config)#ip vrf < vrf-name> Creates a VPN instance.
2 ZXR10(config-vrf-vrf-name)#rd <route-distinguisher> Defines an RD for VRF.

There are three formats,
0-65535:0-4294967295,
1-65535.0-65535:0-65535
and A.B.C.D:0-65535.
3 ZXR10(config-vrf-vrf-name)#address-family ipv6 Activates IPv6 address family.
4 ZXR10(config-vrf-vrf-name-af-ipv6)#route-target [ Creates a route-target

import|export | both]<extended-community> extended community attribute
associated with VRF in IPv6
address family configuration
mode.
import: Imports routes to VRF according to the route-target extended community

attribute.
export: Exports VRF routes with route-target extended community attribute.

both: import and export.
<extended-community>: Route-target extended community attribute.

There are three formats, 0-65535 :0-4294967295, A.B.C.D:0-65535 and
<1-65535>.<0-65535>:<0-65535>.
19-2

Chapter 19 6VPE Configuration
2. Associate the interface with VRF, and configure an IPv6 address on the interface.

mode.
2 ZXR10(config-if-interface-name)#ip vrf forwarding Associates the interface

<vrf-name> with VRF. If an IP address
has been configured on the
interface, it is necessary to
delete the IP address and then
configure a new IP address.
3 ZXR10(config-if-interface-name)#ipv6 enable Enables IPv6 on an interface.
4 ZXR10(config-if-interface-name)#ipv6 address Configures an IPv6 address

{X:X::X:X/<1-128>[anycast | eui-64]| link-local on an interface.
<X:X::X:X>} anycast, the anycast address.
eui-64, the Eui64 prefix
address.
3. Configure IPv6 static route between a CE and a PE.
When IPv6 static route runs between a CE and a Provider Edge (PE), it is necessary
to configure an IPv6 static route to the CE on the PE and redistribute the static route
to BGP.
1 ZXR10(config)#ipv6 route vrf< vrf-name>< prefix of Configures an IPv6 static

destination ipaddress>< network mask>< next hop address> route to a CE on a PE. It is
necessary to specify the VRF
which the static route belongs
to.
2 ZXR10(config)#router bgp < as-number> Enters BGP route

configuration mode.
3 ZXR10(config-bgp)#address-family ipv6 vrf <vrf-name> Enters VRF address family

configuration mode.
4 ZXR10(config-bgp-af-ipv6-vrf)#redistribute static Redistributes the static route.

[metric <metric-value>],[route-map <map-tag>]
As shown in Figure 19-2, it is required to run static route between CE1 and PE1. The
following example shows how to configure static routes on CE1 and PE1 respectively.
19-3

Figure 19-2 Network Topology of the IPv6 Static Route Configuration Between
CE and PE
Configuration on CE1:
CE1(config)#interface gei-1/1
CE1(config-if-gei-1/1)#ipv6 enable
CE1(config-if-gei-1/1)#ipv6 address 1001::20:1/96
CE1(config-if-gei-1/1)#exit
CE1(config)#ipv6 route 2002::0/96 1001::10:1
PE1(config)#ipv6 route vrf vpn_a 1001::0/96 1001::10:2

PE1(config-bgp)#address-family ipv6 vrf vpn_a
PE1(config-bgp-af-ipv6-vrf)#redistribute static
4. Configure RIPng between a CE and a PE.
1 ZXR10(config)#ipv6 router rip vrf <vrf-name> Enables RIPng and enters

RIPng configuration mode.
2 ZXR10(config-ripng-vrf-vrf-name)#redistribute bgp Redistributes BGP to RIPng.

[metric <metric-value>],[route-map <map-tag>]
19-4

3 ZXR10(config-ripng-vrf-vrf-name)#interface Enters RIPng interface

<interface-name> configuration. The interface is
bound to VRF.
ZXR10(config-ripng-vrf-vrf-name)#ipv6 rip enable Enables RIPng on an

interface.
4 ZXR10(config)#router bgp <as-number> Enters BGP route

configuration mode.
5 ZXR10(config-bgp)#address-family ipv6 vrf < vrf- name> Enters VRF address family
configuration mode.
ZXR10(config-bgp-af-ipv6-vrf)#redistribute rip Redistributes the RIPng

[metric <metric-value>],[route-map <map-tag>] routes.
As shown in Figure 19-3, it is required to run RIPng between CE1 and PE1. The
following example shows how to configure RIPng on CE1 and PE1 respectively.
Figure 19-3 Network Topology of the RIPng Configuration Between CE and PE
CE1(config)#ipv6 router rip
CE1(config-ripng)#interface gei-1/1
CE1(config-ripng-if-gei-1/1)#ipv6 rip enable
CE1(config-ripng-if-gei-1/1)#exit
PE1(config)#ipv6 router rip vrf vpn_a
PE1(config-ripng-vrf-vpn_a)#redistribute bgp
19-5

PE1(config-ripng-vrf-vpn_a)#interface gei-1/1
PE1(config-ripng-vrf-vpn_a-if-gei-1/1)#ipv6 rip enable
PE1(config-ripng-vrf-vpn_a-if-gei-1/1)#exit
PE1(config-ripng-vrf-vpn_a)#exit

PE1(config-bgp-af-ipv6-vrf)#redistribute rip
5. Configure OSPFv3 between a CE and a PE.
1 ZXR10(config)#ipv6 router ospf <process-id>[vrf < Enables OSPFve and enters

vrf-name>] OSPF VRF configuration
mode.
ZXR10(config-ospfv3-process-id)#router-id Configures an OSPFv3

<router-id> Router-ID.
2 ZXR10(config-ospfv3-process-id)#interface Defines an interface that runs

<interface-name> area < area-id>[instance <instance-id>] OSPFve and configures area
IDs of the interface
3 ZXR10(config-ospfv3-process-id)#redistribute bgp Redistributes BGP routes

[{[tag <tag-value>],[metric <metric-value>],[metric-type
{ext-2|ext-1}],[route-map <routemap>]}]

configuration mode.
5 ZXR10(config-bgp)#address-family ipv6 vrf < vrf-name> Enters VRF address family

configuration mode.
6 ZXR10(config-bgp-af-ipv6-vrf)#redistribute { Redistributes the OSPFv3

ospf-int | ospf-ext}<process-id>[metric <metric-value>],[ro routes.
ute-map <map-tag>]
As shown in Figure 19-4, it is required to run OSPFv3 between CE1 and PE1. The
following example shows how to configure OSPFv3 on CE1 and PE1 respectively.
19-6

Figure 19-4 Network Topology of the OSPFv3 Configuration Between CE and PE
CE1(config)#ipv6 router ospf 1
CE1(config-ospfv3-1)#router-id 1.1.1.1
CE1(config-ospfv3-1)#interface gei-1/1 area 0.0.0.0
PE1(config)#ipv6 router ospf 2 vrf vpn_a
PE1(config-ospfv3-2)#interface gei-1/1 area 0.0.0.0
PE1(config-ospfv3-2-if-gei-1/1)exit
PE1(config-ospfv3-2)#redistribute bgp
6. Configure EBGP between a CE and a PE.

configuration mode.
2 ZXR10(config-bgp)#address-family ipv6 vrf < vrf-name> Enters VRF address family

configuration mode.
19-7

3 ZXR10(config-bgp-af-ipv6-vrf)#neighbor < Configures an EBGP neighbor

ipv6-address> remote-as <as-number> or configures the AS number
of a neighbor peer group.
As shown in Figure 19-5, it is required to run EBGP between CE1 and PE1. The
following example shows how to configure BGP on CE1 and PE1 respectively.
Figure 19-5 Network Topology of the EBGP Configuration Between CE and PE
CE1(config)#router bgp 65001

CE1(config-bgp)#neighbor 1001::10:1 remote-as 100
CE1(config-bgp)#neighbor 1001::10:1 activate
CE1(config-bgp)#redistribute connected
CE1(config-bgp)#exit

PE1(config-bgp-af-ipv6-vrf)#neighbor 1001::10:2 remote-as 65001
PE1(config-bgp-af-ipv6-vrf)#neighbor 1001::10:2 activate
7. Configure MPBGP between a PE1 and a PE2.
19-8

1 ZXR10(config)#router bgp <as-number> Enters BGP route

configuration mode.
2 ZXR10(config-bgp)#neighbor {<ipv4-address>|<peer-gr Configures a BGP neighbor.

oup-name>} remote-as <as-number>
3 ZXR10(config-bgp)#neighbor {<ipv4-address>|<peer-gro Sets the source address of

up-name>} update-source <interface-name> the specified route update to
the interface address that is
used to establish the MPBGP
connection.
4 ZXR10(config-bgp)#address-family vpnv6 Enters VPNv6 address family

configuration mode.
5 ZXR10(config-bgp-af-vpnv6)#neighbor Activates VPNv6 of a

{<ipv4-address>|<peer-group-name>} activate neighbor.
As shown in Figure 19-6, it is required to run MPBGP between PE1 and PE2. The
following example shows how to configure MPBGP on PE1 and PE2 respectively.
Figure 19-6 Network Topology of the MPBGP Configuration
It is necessary to make sure that the loopback addresses of PE1 and PE2 can be
pinged successfully from each other in advance.
19-9


8. Configure AS overriding.
When BGP runs between PEs and CEs, sometimes different nodes need to reuse the
AS number. To ensure the connectivity between CE1 and CE2, AS overriding can be
performed. When AS overriding is configured on a PE, before the PE sends a route
update to CEs, the PE replaces the AS number of the CEs connected directly along
the AS_PATH with the AS number of it own. The length of AS_PATH does not change.
1 ZXR10(config)#router bgp<as-number> Enters BGP route

configuration mode.
2 ZXR10(config-bgp)#address-family ipv6 vrf <vrf-name> Enters IPv6 VRF address

3 ZXR10(config-bgp-af-ipv6-vrf)#neighbor Replaces the AS number of

<neighbor-address> as-override the CEs connected directly
along the AS_PATH with the
AS number of it own.
9. Configure export map and import map.

The export map and import map are described below.
l Import Map: Users can filter the routes imported to the VRF according to the
import map. The VRF can store the route prefixes that it cares.
l Export Map: Users can configure different Route Targets (RTs) for route prefixes
by using the export map. Different VRFs can select to accept prefixes with
different RTs.
1 ZXR10(config)#ip vrf <vrf-name> Configures a VPN instance

and enters VPN instance
configuration mode.
2 ZXR10(config-vrf-vrf-name)#address-family ipv6 Activates IPv6 address family.
19-10

3 ZXR10(config-vrf-vrf-name-af-ipv6)#export map < Configures the export map

route-map-name> associated with the VRF. The
name of the route map is 1 to
31 characters in length.
ZXR10(config-vrf-vrf-name-af-ipv6)#import map < Configures the import map

route-map-name> associated with the VRF. The
name of the route map is 1 to
31 characters in length.
Command Function
ZXR10#ping6 [vrf <vrf-name>]{<ipv6-address>| domain Checks network connectivity.

<domain-name>}{[limit {0 |<limit-num>}], [repeat
<repeat-count>],[size <datagram-size>],[timeout
<timeout>],[interface <interface-name>],[source
<source-address>]}
ZXR10#show ip vrf [[[brief | detail][< vrf-name>]]| summary] Displays the VRF information.
ZXR10#show ipv6 protocol routing vrf <vrf-name>[[network Displays the VRF routing table.
<ipv6-address>[/<mask_len>]]|<protocol>| database]
End of Steps
19.3 6VPE Configuration Example

As shown in Figure 19-7, CE1 and CE2 are in the same VPN. The loopback address of
CE1 is 1001::10:1/112, and the loopback address of CE2 is 2002::10:1/112.
It is required to configure a VPN and OSPFv3 to make CE1 and CE2 learn routes from
each other. BGP runs between CE1 and PE1, and OSPFv3 runs between CE2 and PE2,
which makes CE1 and CE2 learn routes from each other and can be pinged successfully.
19-11

Figure 19-7 6VPE Configuration Example
The addresses on the interfaces are listed in Table 19-1.
Table 19-1 Addresses on the Interfaces
Device Interface Name IP Address
CE1 gei-1/1 1001::20:2/120
PE1 gei-1/2 1001::20:1/120
gei-1/3 10.10.12.1/24
P gei-1/4 10.10.12.2/24
gei-1/5 10.10.23.2/24
PE2 gei-1/6 10.10.23.3/24
gei-1/7.10 2002::20:2/120
CE2 gei-1/8.10 2002::20:1/120
Configuration Flow
1. Configure loopback1 interface on CE1. Establish an IPv6 EBGP neighbor relation with
PE1, and advertise the loopback1 interface address in BGP.
2. Configure IP addresses on loopback1, gei-1/2 and gei-1/3 of PE1. Configure vrf test1,
and bind gei-1/2 to vrf test1. Configure OSPF on PE1 and advertise the 10.10.0.0/16
segment. Establish MPBGP neighbor relationship with PE2 and enable VPNv6.
Establish an EBGP neighbor relationship with CE1. Configure LDP on gei-1/3.
3. Configure IP addresses on gei-1/4 and gei-1/5 of P. Configure OSPF and advertise
the 10.10.0.0/16 segment. Configure LDP on gei-1/4 and gei-1/5.
4. Configure IP addresses on loopback1, gei-1/6 and gei-1/7 of PE2. Configure vrf
test1, and bind gei-1/7.10 to vrf test1. Configure OSPF on PE2 and advertise the
10.10.0.0/16 segment. Establish an MPBGP neighbor relationship with PE1 and
enable VPNv6. Establish an OSPF neighbor relationship with CE2. Configure LDP
on gei-1/6.
5. Configure IP addresses on loopback1 and gei-1/8.10 of CE2. Configure OSPF, and
advertise the IP addresses in OSPF.
19-12

CE1(config)#interface loopback1
CE1(config-if-loopback1)#ipv6 enable
CE1(config-if-loopback1)#ipv6 address 1001::10:1/112
CE1(config-if-loopback1)#exit
CE1(config-if-gei-1/1)#no shutdown
CE1(config)#router bgp 200

CE1(config-bgp)#neighbor 1001::20:1 remote-as 100
CE1(config-bgp)#address-family ipv6
CE1(config-bgp-af-ipv6)#neighbor 1001::20:1 activate
CE1(config-bgp-af-ipv6)#exit


PE1(config-if-gei-1/2)#ip vrf forwarding test1
19-13

PE1(config-if-gei-1/2)#ipv6 address 1001::20:1/120


PE1(config-bgp-af-ipv6-vrf)#neighbor 1001::20:2 remote-as 200
Configuration on P:
P(config)#interface gei-1/4
P(config-if-gei-1/4)#ip address 10.10.12.2 255.255.255.0
P(config-if-gei-1/4)#no shutdown
P(config-if-gei-1/4)#exit
P(config)#interface gei-1/5
P(config-if-gei-1/5)#ip address 10.10.23.2 255.255.255.0
P(config-if-gei-1/5)#no shutdown
P(config-if-gei-1/5)#exit
P(config)#interface loopback1
P(config-if-loopback1)#ip address 10.10.2.2 255.255.255.255
P(config-if-loopback1)#exit
P(config)#router ospf 1
P(config-ospf-1)#network 10.10.0.0 0.0.255.255 area 0.0.0.0
P(config-ospf-1)#exit
P(config)#mpls ldp instance 1

P(config-ldp-1)#router-id loopback1
P(config-ldp-1)#interface gei-1/4
P(config-ldp-1-if-gei-1/4)#exit
P(config-ldp-1)#interface gei-1/5
P(config-ldp-1-if-gei-1/5)#exit
19-14

P(config-ldp-1)#exit
Configuration on PE2 (here an Ethernet sub-interface is used to connect to CE2):

PE2(config)#vlan-configuration
PE2(config-vlan)#interface gei-1/7.10
PE2(config-vlan-if-gei-1/7.10)#encapsulation-dot1q 10
PE2(config-vlan-if-gei-1/7.10)#exit
PE2(config-vlan)#exit
PE2(config-if-gei-1/7.10)#ip vrf forwarding test1
PE2(config-if-gei-1/7.10)#ipv6 enable
PE2(config-if-gei-1/7.10)#ipv6 address 2002::20:2/120

PE2(config-ospfv3-2)#interface gei-1/7.10 area 0.0.0.0
PE2(config-ospfv3-2-if-gei-1/7.10)#exit

19-15



CE2(config)#interface loopback1
CE2(config-if-loopback1)#ipv6 enable
CE2(config-if-loopback1)#ipv6 address 2002::10:1/112
CE2(config-if-loopback1)#exit
CE2(config)#interface gei-1/8.10
CE2(config-if-gei-1/8.10)#exit
CE2(config)#vlan-configuration
CE2(config-vlan)#interface gei-2/8.10
CE2(config-vlan-if-gei-2/8.10)#encapsulation-dot1q 10
CE2(config-vlan-if-gei-2/8.10)#exit
CE2(config-vlan)#exit
CE2(config)#interface gei-2/8.10
CE2(config-if-gei-2/8.10)#ipv6 enable
CE2(config-if-gei-2/8.10)#ipv6 address 2002::20:1/120
CE2(config-if-gei-2/8.10)#no shutdown
CE2(config-if-gei-2/8.10)#exit
CE2(config)#ipv6 router ospf 3

CE2(config-ospfv3-3)#router-id 3.3.3.3
CE2(config-ospfv3-3)#interface gei-1/8.10 area 0.0.0.0
CE2(config-ospfv3-3-if-gei-1/8.10)#end
Check information about the BGP neighbor created on PE1:
PE1#show bgp vpnv6 unicast summary

19-16

10.10.3.3 4 100 29 112 03:38:29 1
Check information about the IPv6 route advertised by the BGP neighbor:
PE1#show ipv6 forwarding route vrf test1 bgp
IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
2002::20:0/120 B 0
gei-1/3 200 ::ffff:10.10.3.3
Display the IPv6 route lables:
PE1#show bgp vpnv6 unicast labels

Route Distinguisher: 666:666 (default for vrf test1)
2002::20:0/120 ::ffff:10.10.3.3 212994/212997
1001::20:0/120 1001::20:1 212999/notag
Ping the IPv6 address of the peer device successfully:
PE1#ping6 vrf test1 2002::20:2

sending 5,100-byte ICMP echoes to 2002::20:2,timeout is 2 seconds.
!!!!!
Perform verification on PE2 in the same way:
PE2#show bgp vpnv6 unicast summary

10.10.1.1 4 100 27 109 03:35:22 1
PE2#show ipv6 forwarding route vrf test1 bgp

IPv6 Routing Table:
Dest Owner Metric
Interface Pri Gw
1001::20:0/120 B 0
gei-1/6 200 ::ffff:10.10.1.1
PE2#show bgp vpnv6 unicast labels

Route Distinguisher: 100:1 (default for vrf test1)
19-17

1001::20:0/120 ::ffff:10.10.1.1 212997/212999

2002::20:0/120 2002::20:2 212997/notag
PE2#ping6 vrf test1 1001::20:1

sending 5,100-byte ICMP echoes to 1001::20:1,timeout is 2 seconds.
!!!!!
19-18

Chapter 20
IPv6 ACL Configuration
Table of Contents
IPv6 ACL Overview ..................................................................................................20-1
Configuring IPv6 ACL...............................................................................................20-1
IPv6 ACL Configuration Example .............................................................................20-4
20.1 IPv6 ACL Overview

The Access Control List (ACL) is a kind of flow classification policy used to implement
numerous functions such as port-ACL, Unicast Reverse Path Forwarding (URPF) and
policy routing.
The IPv6 ACL mechanism is used to filter packets by the fields in IPv6 packets.
One IPv6 ACL can have multiple rules, with each rule describing certain matching
conditions. For a given packet, matching starts from the first rule. Once a packet matches
a certain rule, the permit or deny action set in the rule is returned.
20.2 Configuring IPv6 ACL

This procedure describes how to configure an IPv6 ACL rule policy.
Steps
1. Enter IPv6 ACL configuration mode and configure the IPv6 ACL rule.
1 ZXR10(config)#ipv6-access-list <acl-name> Configures the specified IPv6

ACL.
2 ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit Configures the extended IPv6

| deny}[flowlabel <flowlabel-value>]{<0-255>| ACL rule.
ipv6 |<protocol-type>}{[<source-ipv6-address>|
any}{<destination-ipv6-address>| any}[dscp
<dscp-value>][{[routing],[authen],[destopts],[fragme
nts],[hop-by-hop],[esp]}][time-range <time-range-name>]
ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit|den Configures the IPv6 ACL rule

y}[flowlabel <flowlabel-value>] tcp {<source-ipv6-address>| based on TCP.
any}[{<operator>{<0-65535>|<source-porttype>}| range
<0-65535>-<0-65535>}]{<destination-ipv6-address>|
any}[{<operator>{<0-65535>|<destination-porttype>}|
20-1

range <0-65535>-<0-65535>}][{[established],[rst<rst>],[ac
k<ack>],[fin<fin>],[syn<syn>],[urg<urg>],[psh<psh>]}][d
scp<dscp-value>][{[routing],[authen],[destopts],[fragment
s],[hop-by-hop],[esp]}][time-range <time-range-name>]
ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit | Configures the IPv6 ACL rule

deny}[flowlabel <flowlabel-value>] udp {<source-ip based on UDP.
v6-address>| any}[<oper><source-port>]{<destination
-ipv6-address>| any}[<oper><destination-port>][dscp
<dscp-value>][{[routing],[authen],[destopts],[fragments],[h
op-by-hop],[esp]}][time-range <time-range-name>]
ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit Configures the IPv6 ACL rule

| deny}[flowlabel <flowlabel-value>] icmp based on ICMP.
{<source-ipv6-address>| any}{<destination-ipv6-address>|
any}[{<icmp-type>|<icmp-type-value>}[<icmp-code>]][dscp
<dscp-value>][{[routing],[authen],[destopts],[fragments],[h
op-by-hop],[esp]}][time-range <time-range-name>]
3 ZXR10(config)#resequence-access-list ipv6 Numbers the rules in the

<acl-name>[<base>[<increment>]] specified ACL again.
<rule-id>: unique identity of a rule in the IPv6 ACL table, range: 1 to 2147483644. This
ID determines the sequence of the rule in the IPv6 ACL table. If this parameter is not
specified, the system inserts the rule at the end of the table by default and allocates
the rule-id according to the default base and increment.
<0-255>| ipv6 |<protocol-type>: Indicates the protocol type to be matched, which can
be one of the tcp, udp and ip keywords, or can be an integer representing the IP
protocol number and ranging from 0 to 255. If this parameter is set to ipv6, it indicates
that any protocol type is matched.
<icmp-type>: ICMP type, options: destination-unreachable, packet-too-big,

time-exceeded, parameter-problem, echo-request, echo-reply, mld-query, mld-report,
mld-reduction, router-solicitation, router-advertisment, nd-ns, nd-na, redirect and
router-renumbering.
<icmp-type-value>: ICMP packet type field, range: 0255.
<icmp-code>: ICMP message type, range: 0 to 255.
<protocol-type>: IP protocol type, options: gre, ospf, pim and vrrp.

<operator>: port operation, options: eq, ge and le.
<source-porttype>: source port type, options: ftp, telnet, smtp, domain, finger, www,
pop2, pop3, bgp and login.
<destination-porttype>: destination port type, options: ftp, telnet, smtp, domain, finger,
www, pop2, pop3, bgp and login.
20-2

Chapter 20 IPv6 ACL Configuration
range: number of port operations, range: 065535.
<source-port>: indicates that the source port number ranges from 0 to 255.
<destination-port>: indicates the destination port number ranges from 0 to 255.
dscp <value>: indicates the DSCP field, range: 0 to 63.
established: indicates TCP link establishment. This parameter is valid for TCP only.
<rst><ack><fin><syn><psh><urg>: A combination of URG, ACK, PSH, RST, SYN and

FINT flags in a TCP header.
routing, authen, destopts, fragments, hop-by-hop, and esp: Options: routing header,
authentication header, destination option header, fragment header, Hop-by-Hop
Options Header and ESP Header.
time-range: binds a specified, existing time-range.
<base>: base value of rule-id, indicating the serial number of the first rule after rules
are renumbered successfully. Default: 10, range: 12147483644.
<increment>: step size of rule-id, which is the difference between two neighboring
rule-ids after rules are renumbered. Default: 10, range: 12147483644.
2. Bind IPv6 ACL to an interface.
1 ZXR10(config)#ipv6-access-group interface Binds the specified IPv6 ACL

<interface-name>{ingress | egress}<acl-name> to the specified interface.

mode.
ZXR10(config-if-interface-name)#ipv6-access-group Binds the specified IPv6 ACL

{ingress | egress}<acl-name> in interface configuration
mode.
Command Function
ZXR10(config)#show ipv6-access-lists [config | brief Displays the IPv6 ACL list or brief
[name <acl-name>]| name <acl-name>[from <from-id> information.
to <to-id>]][|<match-type><LINE>]
ZXR10(config)#show ipv6-access-groups Displays the IPv6 ACL binding

[{[by-access-list <acl-name>],[by-direction information. The information can be
{ingress | egress}],[by-interface <interface-name>]}] selectively displayed according to the
command parameters.
ZXR10(config)#show running-config ipv6-acl[ Displays the entire IPv6 ACL

all][|{begin |exclude |include}<key_words>] information.
20-3

Command Function
ZXR10(config)#show running-config port-acl[ Displays all the IPv6 ACL binding

all][|{begin |exclude |include}<key_words>] information (and the IPv4 ACL binding
information as well as if any IPv4 ACL
is bound).
End of Steps
20.3 IPv6 ACL Configuration Example

In the network as shown in Figure 20-1, suppose both PC1 and PC2 send telnet requests
through R2 to R1. R1 expects to receive the login requests of PC1 only but not the login
requests of PC2. Then an ACL can be bound to the ingress direction of the interface
gei-1/3 to filter out the telnet packets from PC2 (or the ACL may be binded to the egress
direction of the interface gei-1/4).
Figure 20-1 IPv6 ACL Configuration Example
In this case, it is only necessary to create one ACL and add the following rule to this ACL:
Deny the telnet packets matching the IP address of PC2 and using the protocol type TCP
and the port type telnet. Then bind the ACL to the ingress direction of the interface gei-1/3
or the egress direction of the interface gei-1/4.
After the above configuration is completed, the requests initiated by PC2 do not reach R1
but are discarded when they reach R2 even if PC2 has not obtained the telnet username
and password of R1. The other communications of R1 and PC2, however, are not be
affected.
Configuration Flow
1. Enable IPv6 and configure the interface addresses on routers.
2. First create an ipv6-access-list. During the creation, a customized name can be
assigned to this list but the length of the name shall not exceed 31 characters.
20-4

Chapter 20 IPv6 ACL Configuration
3. Enter the IPv6 ACL configuration mode after the list is created and then add rules. A
packet type can be specified for each rule, and the permit or deny action applies to
the packet type.
4. Bind the customized ipv6-access-list to the ingress or egress direction of the interface
to which traffic filtering applies.
This example does not cover the interface address configuration, and is omitted in this
example.
R2(config)#ipv6-access-list test
R2(config-ipv6-acl)# rule deny tcp 100:1::1:2/128 eq 23 110:1::1:2/128
R2(config-ipv6-acl)#rule permit ip any any
R2(config)#ipv6-access-group interface gei-1/3 ingress test
Check the configured ACL in one of the following three modes, as shown below.
/*Check all the ACLs on the router. In this mode, all the names
and number of ACLs are shown*/
R2(config)#show ipv6-access-lists brief
No. ACL RuleSum
-------------------------------------------------------
1 test 2
/*Check the ACL of the specified name. In this mode, information

about the number of rules of the specified ACL is shown.*/
R2(config)#show ipv6-access-lists name test
ipv6-access-list test
2/2 (showed/total)
10 deny tcp 100:1::1:2/128 eq telnet 110:1::1:2/128
20 permit ip any any
/*Check the details of all ACLs on the router. In this mode,

information about the number of rules of each ACL is shown.*/
R2(config)#show ipv6-access-lists
ipv6-access-list test
2/2 (showed/total)
10 deny tcp 100:1::1:2/128 eq telnet 110:1::1:2/128
20 permit ipv6 any any
Check the interface bound with the ACL. Two methods are available for checking the
binding between the ACL and the interface, as shown below.
20-5

/*Check the binding between IPv6 ACLs on the router and the
related interfaces*/
R2(config)#show ipv6-access-groups
Interface name|vlan Direction ACL name
------------------------------------------------------
gei-1/3 Ingress test
/*Check the binding between all ACLs on the router and the
related interfaces, including IPv4 ACLs and IPv6 ACLs*/
R2(config)#show running-config port-acl
! <PORT-ACL>
interface gei-0/8 /*Bind other interface of IPv4 ACL to the device.*/
ipv4-access-group ingress 1K
$
interface gei-1/3
ipv6-access-group ingress test
$
! </PORT-ACL>
20-6

Chapter 21
IPv6 URPF Configuration
Table of Contents
URPF Overview .......................................................................................................21-1
Configuring IPv6 URPF ............................................................................................21-2
IPv6 URPF Configuration Instances .........................................................................21-3
21.1 URPF Overview

URPF Introduction
Unicast Reverse Path Forwarding (URPF) can prevent the network attack behavior that is
based on source address spoofing.
By checking the source IP addresses contained in packets, URPF decides whether traffic
is valid and whether to forward or drop the packets according to the interface on which
packets are received and whether the routes of the source addresses exist in the routing
table.
URPF is divided into three kinds.
l sRPF: strict URPF

l lRPF: loose URPF
l lnRPF: URPF ignoring default route
Strict RPF
Strict RPF is an easier method to filter source address. It performs routing lookup by source
address and estimates whether the egress interface of return path is consistent with the
ingress interface of the packets arriving. If they are consistent, the forwarding continues.
If they are inconsistent, URPF ACL matching is considered. If URPF ACL matching is not
performed, then the packets are discarded directly. Conversely, if URPF ACL matching is
performed and the result is matched, the forwarding continues. If the result is not matched,
the packets are discarded.
Strict RPF is only applicable to route symmetry. That is, when the packets enter from
a direction, its entrance path is the same with its return path. However, the route paths
normally are asymmetric between ISPs. At the same time, if some BGP valid network
segment addresses are not advertised or accepted by ISP policy, sRPF just like an ACL
with incomplete configuration. Some valid data flow will be discarded because of lack of
information in the forwarding table of the filter router.
21-1

Loose RPF
In loose RPF mode, the router only checks whether the source IP address of the packet
exists in the routing table (normal source address route or default route). It does not check
whether the ingress for receiving packets matches with the content of the routing table. In
this way, URPF can effectively prevent network from attacks, and it can also prevent the
interception of legal user packets.
Loose RPF Ignoring Default Route

If a default route is configured on the device, when URPF checks source addresses
according to the routing table, the next-hop information of all the source addresses can be
queried. In this case, you can configure whether to allow URPF to introduce default route
(if URPF ignoring the default route is configured, URPF does not check the default route).
ACL Application in URPF

By means of ACL, URPF provides a more flexible customization solution. When the
network administrator trusts that the packets with some features are legal packets, he can
configure ACL rules to forward these packets properly that are not discarded even if the
packets lack a source route (or, the source route is default route, but the default route is
disabled in URPF). That is, when URPF check fails, the packets are permitted or denied
according to the ACL rules.
21.2 Configuring IPv6 URPF

This procedure describes how to configure the IPv6 URPF function.
Steps
1. Configure the IPv6 URPF function on the interface.
1 ZXR10(config)#ipv6 verify unicast Enables IPv6 URPF function on an

source reachable-via {rx interface interface.
<interface-name>[acl-name <acl-name>]|
any interface <interface-name>[acl-name
<acl-name>][ignore-default-route]}
2 ZXR10(config)#interface <interface-name> Enters interface configuration mode.
3 ZXR10(config-if-interface-name)#ipv6 Enables interface IPv6 URPF

verify unicast source reachable-via {rx function on an interface configuration
[acl-name <acl-name>]| any [acl-name mode.
<acl-name>][ignore-default-route]}
rx: strict mode.

any: loose mode.
21-2

Chapter 21 IPv6 URPF Configuration
interface <interface-name>: name of the interface where the IPv6 URPF function is
configured.
ignore-default-route: It is only available for loose mode.
Command Function
ZXR10#show running-config urpf [all] Displays all the URPF configurations.
ZXR10#show running-config-interface Displays URPF configuration of a

<interface-name>[all] specified interface.
End of Steps
21.3 IPv6 URPF Configuration Instances

21.3.1 Example: Configuring IPv6 URPF (Strict)
As shown in Figure 21-1, strict URPF is configured for the interface gei-2/1 on R1, which
prevents the network users coming from the network segment before 1:1::ad:ea/64 from
attacking the network connecting to R1, and permits the data flow from the network
segment 1:11::ad:ea/64 to pass through URPF inspection.
Figure 21-1 Topology of IPv6 URPF Configuration Example (Strict)
Configuration Flow
1. Configure IPv6 address for the interface.
2. Create ACL, add the ACL matching requirements. For example, permit the traffic
coming from 1:11::ad:ea/64 to pass.
3. Bind strict IPv6 URPF with ACL list to the interface.
R1(config-if-gei-2/1)#ipv6 address 1:1::ad:ea/64
21-3

R1(config)#ipv6-access-list acl
R1(config-ipv6-acl)#rule permit ipv6 1:11::ad:ea/64 any
R1(config)#ipv6 verify unicast source reachable-via rx interface
gei-2/1 acl-name acl
Check the configuration results:
R1(config)#show running-config urpf

! <URPF>
interface gei-2/1
ipv6 verify unicast source reachable-via rx acl-name acl
$
! </URPF>
R1(config)#show running-config-interface gei-2/1

! <interface>
interface gei-2/1
no shutdown
ipv6 enable
ipv6 address 1:1::ad:ea/64
$
! </interface>
! <URPF>
interface gei-2/1
ipv6 verify unicast source reachable-via rx acl-name acl
$
! </URPF>
R1(config)#show ipv6-access-lists name acl

ipv6-access-list acl
1/1 (showed/total)
10 permit ipv6 1:11::ad:ea/64 any
21.3.2 Example: Configuring IPv6 URPF (Loose)

This section takes the loose IPv6 URPF configuration as an example, as shown in Figure
21-2.
21-4

Chapter 21 IPv6 URPF Configuration
Figure 21-2 Topology of IPv6 URPF Configuration Example (Loose)
Configuration Flow
1. As shown in Figure 21-2, establish the networking structure, add a link for the
sub-interface between R1 and R2, and configure the IPv6 address for each interface.
2. Configure the OSPFv3 protocol between R1 and R2 to ensure the unicast interworking.
3. Configure loose URPF for the ingress gei-2/1 on R1 and configure ACL.
4. The source address is 3ff1::1, the destination network segment is 1:20::/64, and the
direction is from R1 to R2.
R1(config-if-gei-2/1)#ipv6 address 1:1:ad::ea/64
R1(config-if-gei-2/2)#ipv6 address 1:10::ad:ea/64
R1(config)#interface gei-2/2.1
R1(config-if-gei-2/2.1)#exit
R1(config)#vlan-configuration
R1(config-vlan)#interface gei-2/2.1
R1(config-vlan-if-gei-2/2.1)#encapsulation-dot1q 100
/*configure sub-interface and establish another link*/
R1(config-vlan-if-gei-2/2.1)#exit
R1(config-vlan)#exit
R1(config-if-gei-2/2.1)#ipv6 enable
R1(config-if-gei-2/2.1)#ipv6 address 200::1/64

R1(config-ospfv3-1)#interface gei-2/1 area 0.0.0.0 instance 0
21-5

R1(config-ospfv3-1)#interface gei-2/2 area 0.0.0.0 instance 0

R2(config-if-gei-3/1)#ipv6 verify unicast source reachable-via
any acl-name wd /*bind the interface with loose URPF*/
R2(config)#ipv6 route 3ff1::/64 200::2
/*Configure the static route and specify that the interface to
source route is different from the ingress interface*/
The other configurations of R2 are similar to the configurations of R1.
The traffic that meets the URPF configuration can be transmitted normally.
21-6

Chapter 22
IPv6 QoS Configuration
Table of Contents
IPv6 QoS Overview ..................................................................................................22-1
Configuring IPv6 QoS...............................................................................................22-1
IPv6 QoS Configuration Examples ...........................................................................22-1
22.1 IPv6 QoS Overview

IPv6 QoS is added with IPv6 support in addition to the functions of IPv4 QoS. For details
about QoS, refer to the Introduction to QoS in Configuration Guide (QoS).
22.2 Configuring IPv6 QoS

The commands for configuring IPv6 QoS are similar to those for configuring IPv4 QoS,
except that IPv6 addresses are involved during the configuration. For details about the
configuration commands, refer to the topics about QoS configuration in Configuration
Guide (QoS).
22.3 IPv6 QoS Configuration Examples

22.3.1 Example: Configuring IPv6 Priority Scheduling
As shown in Figure 22-1, four users access the ZXR10 via interfaces gei-1/1 and gei-1/2.
They are user1, user2, user3, and user4. The following requirements need to be met:
l User1 is allowed to pass at the first priority with the maximum bandwidth of 400 Mbps.
l User2 is provided with a guaranteed bandwidth of 300 Mbps or a greater bandwidth.
Figure 22-1 IPv6 Priority Scheduling Configuration Example
22-1

Configuration Flow
1. Configure H-QoS in the downlink of the interface gei-1/3 to guarantee the bandwidth
of every user when port congestion occurs.
2. Set the Differentiated Services Code Point (DSCP) values of the four users to 1, 2, 3,
and 4 respectively, and configure four classes.
3. Add user1 to the Low Latency Queueing (LLQ) queue with a limited rate of 400 Mbps.
4. Add user2 to the Weighted Fair Queuing (WFQ) queue. The bandwidth is set to 30%
of the port bandwidth.
5. Add user3 to the WFQ queue. The bandwidth is set to 20% of the port bandwidth.
6. Add user4 to the WFQ queue. The bandwidth is set to 10% of the port bandwidth.
1. Configure the interfaces on ZXR10.
2. Configure the classes.
ZXR10(config)#class-map dscp1 match-all ipv6
ZXR10(config-cmap)#match dscp 1
ZXR10(config-cmap)#exit
3. Configure the second level policy.
ZXR10(config)#policy-map test
ZXR10(config-pmap)#class dscp1
ZXR10(config-pmap-c)#priority-llq
ZXR10(config-pmap-c)#police cir 400000 cbs 400 conform-action transmit
exceed-action drop violate-action drop
22-2

Chapter 22 IPv6 QoS Configuration
ZXR10(config-pmap-c)#exit
ZXR10(config-pmap-c)#bandwidth percent 30
ZXR10(config-pmap)#exit
4. Bind the policies to the interface.
ZXR10(config)#service-policy gei-1/3 output test
Run the show policy-map command to check the correctness of policy configuration.
ZXR10(config)#show policy-map
policy-map test
class dscp1
priority-llq
police cir 400000 cbs 400 conform-action transmit exceed-action drop
violate-action drop
class dscp2
bandwidth percent 30
class dscp3
class dscp4
Run the show service-policy command to check the correctness of interface-policy binding.
ZXR10#show service-policy
service-policy gei-1/3 output test
22.3.2 Example: Configuring IPv6 WRED

Configure a Weighted Random Early Detection (WRED) policy in the uplink of the router
interface, so that different discard policies are applied to the packets of different priorities
when congestion occurs. The following objectives should be attained:
22-3

l For queues with the priority value 0, the lowest discard threshold is 30 kb, the highest
discard threshold is 100 kb, the discard probability is 90%, and the average queue
length indicator is 8.
Configuration Flow
1. Create a class-map and match it with precedence 0-2.
2. Create a policy-map, add the new class matching precedence 0-2 to the policy, and
add the queues of different priorities in the class to WRED.
3. Select a PQ from the policy classes.
4. Bind the policy-map to the egress direction of the interface.
1. Configure the class.
ZXR10(config)#class-map pre0-2 match-all ipv6
ZXR10(config-cmap)#match precedence 0-2
2. Configure the policy.
ZXR10(config)#policy-map wred
ZXR10(config-pmap)#class pre0-2
ZXR10(config-pmap-c)#random-detect enable
ZXR10(config-pmap-c)#random-detect weight 8
ZXR10(config-pmap-c)#random-detect precedence 0 30 100 90
ZXR10(config-pmap-c)#priority-level 1
ZXR10(config-pmap)#exit
3. Bind the policy to the interface.
ZXR10(config)#service-policy gei-1/7 output wred
Check policy configuration.
ZXR10(config)#show policy-map
policy-map wred
class pre0-2
random-detect enable
random-detect weight 8
22-4

random-detect precedence 0 30 100 90

priority-level 1
ZXR10#show service-policy
service-policy gei-1/7 output wred
When traffic is congested on the outgoing interface, capture packets on the interface and
the discard probability of the packets in the queues of different priorities is the same as
that described in Configuration Description.
22.3.3 Example: Configuring IPv6 CAR

As shown in Figure 22-2, user1 accesses the system via the interface gei-1/1 whereas
user2 accesses the system via the interface gei-1/2. The DSCP values are 1 and 2
respectively. Packets are sent via the interface gei-1/3.
According to the requirements, the DSCP values of the packets of the two users sent via
the interface gei-1/3 should be 7, the guaranteed bandwidth should be 100 M, and the
maximum bandwidth should be 150 M.
Figure 22-2 IPv6 CAR SET Configuration Example
Configuration Flow
Configure two Committed Access Rates (CARs) in the downlink of the interface gei-1/3,
match them with DSCP values 1 and 2 respectively, and set the DSCP value of the
permitted traffic to 7. Set the guaranteed bandwidth to 100 M, and set the maximum
bandwidth to 150 M.
1. Enter CAR configuration mode.
22-5

ZXR10(config)#qos
ZXR10(config-qos)#
2. Enter interface configuration mode.
ZXR10(config-qos)#interface gei-1/3
ZXR10(config-qos-if-gei-1/3)#
3. Configure CAR commands.
ZXR10(config-qos-if-gei-1/3)#rate-limit output ipv6 dscp 1 cir 100000 cbs
200000 pir 150000 pbs 300000 conform-action set-dscp-transmit 7
exceed-action set-dscp-transmit 7 violate-action drop
ZXR10(config-qos-if)#rate-limit output ipv6 dscp 2 cir 100000 cbs 200000
pir 150000 pbs 300000 conform-action set-dscp-transmit 7
exceed-action set-dscp-transmit 7 violate-action drop
Run the show running-config carset command to check the CAR configured on the
interface:
ZXR10(config)#show running-config carset

!<carset>
qos
interface gei-1/3
rate-limit output ipv6 dscp 1 cir 100000 cbs 200000 pir 150000 pbs
300000 conform-action set-dscp-transmit 7 exceed-action
set-dscp-transmit 7 violate-action drop
rate-limit output ipv6 dscp 2 cir 100000 cbs 200000 pir 150000 pbs
300000 conform-action set-dscp-transmit 7 exceed-action
set-dscp-transmit 7 violate-action drop
$
$
!</carset>
22.3.4 Example: Configuring IPv6 Priority Inheritance

As shown in Figure 22-3, a mapping from inbound flow 802.1p to outbound flow IPP
should be implemented when the flow inbound via the Virtual Local Area Network (VLAN)
subinterface gei-1/1.1 to R2 is forwarded out of R2.
Figure 22-3 IPv6 Priority Inheritance Configuration Example
22-6

Configuration Flow
1. Create a VLAN sub-interface and configure an IP address on the sub-interface.
2. Configure a VLAN ID for the sub-interface.
3. Configure 802.1p inheritance.
R2(config)#vlan-configuration
R2(config-vlan)#exit
R2(config)#class-map 802.1p match-all ipv6

R2(config-cmap)#match child
R2(config-cmap)#exit
R2(config)#policy-map 802.1p
R2(config-pmap)#class 802.1p
R2(config-pmap-c)#set precedence inherit-from 8021p
R2(config-pmap-c)#exit
R2(config-pmap)#exit
R2(config)#service-policy gei-1/1.1 input 802.1p
On R1 and R3, it is only necessary to configure the VLAN sub-interfaces and addresses.
R2(config)#show class-map 802.1p
class-map 802.1p match-all ipv6
match child
R2(config)#show policy-map 802.1p
policy-map 802.1p
22-7

class 802.1p
set precedence inherit-from 8021p
R2(config)#show service-policy gei-1/1.1
service-policy gei-1/1.1 input 802.1p
Figure 22-4 shows the inheritance from the inbound interface 802.1p to the outbound
interface IPP.
Figure 22-4 Inheritance from 802.1p to IPP
22-8

Chapter 23
IPv6 VRRP Configuration
Table of Contents
IPv6 VRRP Overview ...............................................................................................23-1
Configuring IPv6 VRRP ............................................................................................23-1
IPv6 VRRP Configuration Examples.........................................................................23-4
23.1 IPv6 VRRP Overview

IPv6 VRRP provides router backup for multicast LANs as IPv4 VRRP does, except that it
runs the IPv6 protocol (this means that IPv6 addresses need to be configured). IPv6 VRRP
operates in a network using the IPv6 protocol. A group of routers acts as a virtual router,
which provides a virtual IP address as the gateway address for users. This implements
backup of gateways in a way, thus avoiding communication failures caused by the failure
of a single router.
For the principle of VRRP, refer to the ZXR10 ZSR V2 Configuration Guide (Reliability).
23.2 Configuring IPv6 VRRP

This procedure describes how to configure IPv6 VRRP, including version number, packet
sending mode, and interface attributes.
Steps
1. Configure the basic attributes of IPv6 VRRP.
1 ZXR10(config)#vrrp Enters VRRP configuration

mode.
2 ZXR10(config-vrrp-if-interface-name)#vrrp Configures the VRRP protocol

<vrid> version {2|3} version number. Default: 3.
ZXR10(config-vrrp-if-interface-name)#vrrp Configures the sending mode of

<vrid> send-mode {all|rotation} VRRP packets, default: all.
ZXR10(config-vrrp-if-interface-name)#vrrp Configures the duration of

<vrid> reload-delay <reload-delay> delaying startup of the state
machine of the VRRP group
interface.
all: Packets are sent to all outgoing interfaces.
23-1

rotation: A packet is sent to each outgoing interface in turn.
<reload-delay>: configures the duration of delaying startup of the interface state

machine. Range: 065535, unit: second, default: 0 second.
2. Configure the optional parameters of the IPv6 VRRP interface attributes.
1 ZXR10(config-vrrp)#interface <interface-name> Enters VRRP interface

configuration mode.
2 ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Enables VRRP in VRRP

ipv6 <ip-address>[secondary] interface configuration mode,
and configures a virtual IPv6
address for VRRP.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures VRRP priority in

priority <level> VRRP interface configuration
mode. The range of <level> is
1-254. The default priority is
100.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures VRRP group

preempt {[delay <delay-time>]|[{disable}]} preemption in VRRP interface
configuration mode. default:
preempt.
The default preemption delay
is 0.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures the interval (in

timers advertise {<1-40>|msec <50-40000>} seconds) to send VRRP
advertisements in VRRP
interface configuration mode,
default: 1.
<1-40>: measured in seconds.
<50-40000>: Measured in
milliseconds.
The parameter msec is
optional and it is to change
the unit of the interval to
millisecond from second.
ZXR10(config-vrrp-if-interface-name)#vrrp Sets whether to enable

<vrid> timers {advertise {<adver-time-in-seconds>|msec VRRP to learn the time
<adver-time-in-milliseconds>}| learn [disable]} interval between successive
messages, default: no
23-2

Chapter 23 IPv6 VRRP Configuration
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures a VRRP track

track interface <interface-name>[priority-decrement interface in VRRP interface
<1-254>| rapid-down] configuration mode.
When the priority decrement
is not configured, the default
value (10) is used.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures VRRP heartbeat in

out-interface <interface-name> VRRP interface configuration
mode, that is, configuring a
VRRP packets out-interface.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures the detection

track { group | object}<string>{ link-type | peer-type | group, object and policy for
priority-decrement <1-254>} VRRP tracking.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Enables the accept function in

accept [disable] VRRP interface configuration
mode, default: Enable.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Enables the check-ttl

check-ttl [disable] function in VRRP interface
configuration mode, default:
Enable.
ZXR10(config-vrrp-if-interface-name)#vrrp <vrid> Configures VRRP

admin-group { owner | interface <interface-name> vrid administration group
<1-255>} function in VRRP interface
configuration mode.
owner, sets the VRRP group
as a management group,
in charge of receiving and
sending messages, and
managing status.
group : the concerned group.
object: the concerned object.
string, name of the concerned group or object.

link-type: the link type, used for tracking the link status of the local device.
peer-type: the peer type, used for tracking the link status of the peer device.
priority-decrement<1-254>: specifies the value deducted from the priority of a router.

23-3

Command Function
ZXR10#show vrrp ipv6 brief Displays the brief information about

all IPv6 VRRP groups on a router.
ZXR10#show vrrp ipv6 brief interface <interface-name> Displays the brief information about
all IPv6 VRRP groups on a specific
interface.
ZXR10#show vrrp interface <interface-name>[vrid <1-255>] Displays the detailed information

about all VRRP groups or a specified
group on a specified interface.
End of Steps
23.3 IPv6 VRRP Configuration Examples

23.3.1 Example: Basic VRRP Configuration
As shown in Figure 23-1, R1 and R2 run IPv6 VRRP. The address of an interface for R1
is set to FE80::1:1, and the address of an interface for R2 is set to FE80::1:2. The same
VRRP group number and virtual address are configured on the interfaces of R1 and R2.
The virtual address is set to FE80::1:1. In this case, the VRRP virtual address is the same
as the actual address of an interface for R1, and therefore R1 is called IP address owner
with a top priority of 255 (that is, R1 is elected as the master router).
The VRRP virtual address can be configured as other Link-Local address (note that the
master virtual address should be the link-local address, prefixed with FE80::). A higher
priority should be set for R1 to make it as the master router.
Figure 23-1 Basic VRRP Configuration (IPv6)
23-4

Configuration Flow
1. Enter the interfaces on which VRRP should be enabled. Enable IPv6, and configure
IPv6 addresses.
2. Enter VRRP configuration mode from global configuration mode, and then enter the
interfaces to configure VRRP.
3. Configure the same VRRP group ID and virtual addresses for R1 and R2. To make R1
as the master router, set a priority for R1 higher than that for R2 in the same group, or
configure R1 as the IP address owner (if the R1 address is used as the virtual address,
R1 has a top priority of 255). The priorities (the default priority is 100) are all the same,
and the router where VRRP is enabled first to publish messages becomes the master
one in the group. This means that you can also configure related commands on R1
first to make it as the master one.
R1(config-if-gei-1/1)#ipv6 address link-local fe80::1:1
R1(config)#vrrp
R1(config-vrrp)#interface gei-1/1
R1(config-vrrp-if-gei-1/1)#vrrp 1 ipv6 fe80::1:1
/*For the configuration of the IPv6 address in VRRPv3, the virtual master IP
address must be a link-local address, that is, an address beginning with FE80,
such as vrrp 1 ipv6 fe80::1. If the address configured here is a global, the
address can only be used as the virtual secondary IP address, such as
vrrp 1 ipv6 1::2 secondary.*/
R1(config-vrrp-if-gei-1/1)#end
R2(config)#vrrp
View the VRRP information and configuration result on R1, as shown below.
23-5

R1#show vrrp ipv6 brief

Interface vrID Pri Time A P L State Master addr VRouter addr
gei-1/1 1 255 1000 A P Master FE80:0:0:0:0:0:1:1 FE80:0:0:0:0:0:1:1
gei-1/1 2 100 1000 P backup FE80:0:0:0:0:0:1:1 FE80:0:0:0:0:0:1:2
/*A: whether the router is the address owner.
P: whether preemption is configured.
L: whether to learn the interval to advertise VRRP messages on the
master.*/
R1#show vrrp interface gei-1/1
gei-1/1 - vrID 1
Vrrp configure info:
IP version 6, VRRP version 3
Virtual IP address is FE80:0:0:0:0:0:1:1
Virtual MAC address is 0000.5e00.0201
Advertise time is 1.000 (s)
Configured priority is 100
Preemption enable, delay 0 (s)
Reload delay 5 (s)
No authentication data
Check ttl enable
Vrrp accept mode enable
Out-interface send-mode is all
Tracked interface items: 0
Interface State Policy Reduce-Priority
Tracked detect items: 0
Admin-group is None
Vrrp run info:
State is Master
5 state changes, last state change 17:05:34 1 day(s)
Current priority is 255
Master router is local
Master router address is FE80:0:0:0:0:0:1:1
Master router priority is 255
Master Advertisement interval is 1.000 (s)
Master Down interval is 3.003 (s), no learn
gei-1/1 - vrID 2
Vrrp configure info:
Advertise time is 1.000 (s)
Preemption enable, delay 0 (s)
Reload delay 5 (s)
23-6

Check ttl enable
Interface State Policy Reduce-Priority
Admin-group is None
Vrrp run info:
State is Backup
6 state changes, last state change 17:05:34 1 day(s)
Master router is remote
Master Advertisement interval is 1.000 (s)
Master Down interval is 3.609 (s), no learn
23.3.2 Example: Symmetrical VRRP Configuration

As shown in Figure 23-2, two VRRP groups are deployed in backup mode to support load
sharing. PC1 and PC2 use the virtual router in Group 1 as the default network gateway,
and the address is FE80::1:1. PC3 and PC4 use the virtual router in Group 2 as the default
network gateway, and the address is FE80::1:2. R1 and R2 act as backup routers for each
other. When both routers are invalid, the communication between the hosts and external
network is interrupted.
Figure 23-2 Symmetrical VRRP Configuration (IPv6)
Configuration Flow
IPv6 addresses.
23-7

3. Configure VRRP 1 and corresponding virtual address on R1. Configure VRRP 2 and
corresponding virtual address on R2. Set a priority for VRRP 1 higher than that for
VRRP 2 on R1, and set a priority for VRRP 2 higher than that for VRRP 1 on R2. In
this way, R1 acts as a master router in group 1, while being a slave router in group
2. R2 acts as a master router in group 2, while being a slave router in group 1. This
enables R1 and R2 to act as backup routers for each other.
R1(config)#vrrp

R2(config)#vrrp
gei-1/1 1 255 1000 A P Master FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :1
gei-1/1 2 100 1000 P Backup FE80:0:0:0:0:0: FE80:0:0:0:0:0:1
1:1 :2
23-8


master.*/
gei-1/1 - vrID 1
Vrrp configure info: /*VRRP configuration information*/
Advertise time is 1.000 sec
Preemption enable, delay 0 secs
Check ttl enable
Interface State Decrement-Priority
Admin-group is None
Vrrp run info:
/*Running information about VRRP on current interface*/
State is Master /*VRRP running state*/
1 state changes, last state change 03:12:14
/*Number of state changes and the time for how long the system has been
running until the last change.*/
/*current priority, the largest priority of the Owner is 255*/
Master Advertisement interval is 1.000 sec
Master Down interval is 3.003 sec, no learn
23.3.3 Example: VRRP Heartbeat Configuration

As shown in Figure 23-3, VRRP operates between R1 and R2. The VRRP virtual address
is the same as the IP address FE80::1:1 of an interface for R1, and therefore R1 is elected
as the master router.
23-9

Figure 23-3 VRRP Heartbeat Configuration (IPv6)
Configuration Flow
IPv6 addresses.
3. Configure the same VRRP group ID and virtual addresses for R1 and R2. To make
R1 as the master router, set a priority for R1 higher than that for R2 in the same group,
or configure it to be the IP address owner by setting the IP address of an interface for
R1 to be the virtual address.
4. In VRRP interface configuration mode, set and enable egress interfaces over which
packets are transmitted for VRRP groups.
R1(config)#vrrp
R1(config-vrrp-if-gei-0/2)#vrrp 1 out-interface gei-0/2
R2(config)#vrrp
23-10

R2(config-vrrp-if-gei-0/2)#vrrp 1 out-interface gei-0/2

gei-0/2 1 255 1000 A P Master FE80:0:0:0: FE80:0:0:0:
0:0:1:1 0:0:1:1
master.*/

gei-0/2 - vrID 1
Vrrp configure info: /*VRRP configuration information*/
Advertise time is 1.000 sec
Preemption enable, delay 0(s)
Reload delay 0 (s)
Check ttl enable
Out-interface(heartbeat line) is gei-0/2
Interface State Decrement-Priority
Admin-group is None
Vrrp run info:
/*Running information about VRRP on current interface*/
State is Master /*VRRP running state*/
3 state changes, last state change 03:38:35
/*Number of state changes and the time for how long the system has been
running until the last change.*/
/*Current priority, the largest priority of the Owner is 255*/
23-11


Master Advertisement interval is 1.000 sec
Master Down interval is 3.003 sec, no learn
23-12

Chapter 24
DHCPv6 Configuration
Table of Contents
DHCPv6 Overview ...................................................................................................24-1
Configuring the DHCPv6 Server ...............................................................................24-3
Configuring a DHCPv6 Relay ...................................................................................24-7
Configuring the DHCPv6 Client ..............................................................................24-10
DHCPv6 Configuration Examples...........................................................................24-10
24.1 DHCPv6 Overview

DHCPv6 Introduction
DHCPv6 is an automatic address allocation protocol defined by IETF on IPv6 networks.
Through DHCPv6, a network node can request IPv6 addresses and some other
configuration parameters from a DHCPv6 server. The network node also can obtain IPv6
addresses through other methods, and just obtain other network parameters from the
DHCPv6 server.
On an IPv6 network, a DHCP client uses a reserved multicast address that is valid on a
link to locate the DHCPv6 server. Therefore, it is required that the client and the server
should be on the same link. However, in some applications, considering management,
economy and extension, it is required that a client can communicate with a server that is
not on the same link with the client. This function is implemented by a DHCPv6 relay. A
DHCPv6 relay can relay access requests from other clients or relays.
Figure 24-1 shows the relationships between DHCPv6 clients, relays and a server.
Figure 24-1 Relation Among DHCPv6 Client, Relay and Server
24-1

DHCPv6 Features
Each DHCPv6 client or server has a unique identifier, that is, a DHCP Unique Identifier
(DUID). There are several modes to generate DUIDs. The lengths of DUIDs are different.
Not every message needs to carry a DUID, therefore a DUID is contained in the option
information.
Identity Association (IA) is an abstract concept used by DHCPv6 servers and clients to
identify, group and management multiple addresses. A network interface needs at least
one IA to manage the IPv6 address information obtained on this interface. An IA must
be associated with a unique network interface. Different IAs are identified by IAIDs. The
IPv6 address information allocated by DHCPv6 is contained in IAs. An IA can carry the
information about several addresses.
DHCPv6 uses UDP to transport the protocol packets. The detection port on clients is
port 546, and the detection port on servers and relays is port 547. Clients always use
multicast packets to start interactions. DHCPv6 defines two multicast addresses. One is
the multicast address (FF05::1:3) of all local DHCP servers, and the other is the multicast
address (FF02::1:2) of all servers and relay agents.
DHCPv6 Work Flow

The standard DHCPv6 message types are as follows:
l Solicit message (1): A client uses Solicit messages to locate the position of a server.
l Advertise message (2): A server sends an Advertise message to reply to a Solicit. An
Advertise message contains the allocated address and option information.
l Request message (3): A client sends a Request message to a specified server to
request an address and configuration information.
l Confirm message (4): A client sends Confirm messages to any reachable server to
check whether the current IPv6 address it obtained is applicable to the connected
links.
l Renew message (5): A client uses Renew messages to extend the address lease
term, and update other configuration information.
l Rebind message (6): If the renew message is not replied, a client uses a Rebind
message to extend the address lease term, and update other configuration
information.
l Reply message (7): A server uses Reply message to respond Request, Renew,
Rebind, Release, Decline and Information-request messages. A Reply message can
carry an address and configuration information. In an exception, a Reply message
also can carry the status code information about an error.
l Release message (8): When a client sends a Release message to a server that
allocates an address for this client, the client does not use the address (or addresses)
any longer.
l Decline message (9): When a client sends a Decline message to a server, the address
(or addresses) has (have) been used on a link (or links).
l Reconfigure message (10): A server can send a Reconfigure message to a client to
hint the configuration information that the client can update.
24-2

Chapter 24 DHCPv6 Configuration
l Information-request message (11): A client sends an Information-request message to

a sever to request configuration information without requesting an IP address.
l Relay-forward message (12): A relay agent sends a Relay-forward message to a serv-
er to replay information.
l Relay-replay message (13): A server sends a Relay-replay message carrying the
information that is to be sent to a client to a rely agent.
Figure 24-2 shows the interaction procedure of DHCPv6 messages in a standard
networking environment.
Figure 24-2 DHCPv6 Protocol Message Interaction
24.2 Configuring the DHCPv6 Server

This procedure describes how to configure the DHCPv6 server.
24-3

Steps
1. Enable the DHCPv6 function, and set the DHCPv6 mode of the interface to DHCPv6
Server.
1 ZXR10(config)#dhcp ipv6 Enters DHCPv6 configuration

mode.
2 ZXR10(config-dhcpv6)#enable Enables the embedded

DHCPv6 function.
3 ZXR10(config-dhcpv6)#interface <interface-name> Enters DHCPv6 interface

configuration mode.
4 ZXR10(config-dhcpv6-if-interface-name)#mode Enables DHCPv6 working

{server | relay} mode of an interface.
2. Configure the IPv6 address pool.
1 ZXR10(config)#ipv6 addr-pool <pool-name> Enters IPv6 address pool

configuration mode.
2 ZXR10(config-ipv6-addr-pool)#addr-range Configures the range of the

<start-ipv6><end-ipv6>[vrf-instance <vrf-name>] IPv6 address pool.
3 ZXR10(config-ipv6-addr-pool)#exclude-range Configures IPv6 reserved

<start-ipv6><end-ipv6>[vrf-instance <vrf-name>] addresses.
4 ZXR10(config-ipv6-addr-pool)#conflict-time Configures the release time

<timeout> (in minutes) of conflicting
addresses in the IPv6 address
pool, range: 1 to 18000,
default: 30.
5 ZXR10(config-ipv6-addr-pool)#lock Locks the IPv6 address pool,

default: unlocked.
6 ZXR10(config-ipv6-addr-pool)#threshold <percent> Configures the alarm

threshold of the IPv6 address
pool, range: 50 to 100,
default: 100%.
3. Configure IPv6 prefix-pool.
1 ZXR10(config)#ipv6 prefix-pool <pool-name> Enters IPv6 prefix-pool

configuration mode.
24-4

2 ZXR10(config-ipv6-prefix-pool)#lock Locks the IPv6 prefix-pool,

default: Unlocked.
3 ZXR10(config-ipv6-prefix-pool)#prefix-delegation Configures an IPv6

<ipv6 prefix-delegation><prefix-length>[vrf-instance prefix-delegation.
<vrf-name>]
4 ZXR10(config-ipv6-prefix-pool)#exclude-prefix Configures IPv6 reserved

<ipv6-prefix-delegation><1-128>[vrf-instance <vrf-name>] prefix attributes.
5 ZXR10(config-ipv6-prefix-pool)#threshold Configures the alarm

<percent> threshold of the IPv6
prefix-pool, default: 100%.
4. Configure the DHCPv6 pool.
1 ZXR10(config-dhcpv6)#pool <pool-name> Enters DHCPv6 address

pool configuration mode from
DHCPv6 configuration mode.
2 ZXR10(config-dhcpv6-pool)#prefix-pool <pool-name> Binds the specified prefix-pool

to the DHCPv6 pool.
3 ZXR10(config-dhcpv6-pool)#prefix-lifetime Specifies the lifetime of

{<valid-lifetime1>| infinite}{<preferred-lifetime1>| infinite} address prefixes (valid lifetime
and preferred lifetime).
4 ZXR10(config-dhcpv6-pool)#aftr {address In DHCPv6 pool mode,

<xx:xx::xx:xx>| fqdn <word>}[option-code-value configures the aftr option.
<1-65535>] There are two aftr types,
address and domain name.
Either address or domain
name can be configured in
this command.
5 ZXR10(config-dhcpv6-pool)#address-pool Binds the specified IPv6

<pool-name> address-pool to DHCPv6
pool.
6 ZXR10(config-dhcpv6-pool)#address-lifetime Specifies the lifetime of

{<valid-lifetime2>| infinite}{<preferred-lifetime2>| infinite} addresses (valid lifetime and
preferred time)
7 ZXR10(config-dhcpv6-pool)#dns-server Configures the address of an

<server-number><server-ipv6> IPv6 DNS server.
8 ZXR10(config-dhcpv6-pool)#domain-name Configures the domain name

<domain-name-number><domain-name> of an IPv6 DNS server.
24-5

9 ZXR10(config-dhcpv6-pool)#preference Configures the server

<preference-value> preference, range: 1 to
255.
10 ZXR10(config-dhcpv6-pool)#server-unicast-address Configures the unicast

<ipv6-address> address of the server.
<valid-lifetime1>: valid lifetime of the prefixes allocated from the address pool, range:
604294967295, unit: second, default: 3600.
<preferred-lifetime1>: preferred lifetime of the prefixes allocated from the address pool,
range: 604294967295, unit: second, default: 3600.
infinite: sets the valid/preferred lifetime of the prefixes allocated from the address pool
to permanent.
<valid-lifetime2>: valid lifetime of the addresses allocated from the address pool, range:
604294967295, unit: second, default: 3600.
<preferred-lifetime2>: preferred lifetime of the addresses allocated from the address
pool, range: 604294967295, unit: second, default: 3600.
<server-number>: DNS server number, options: 12.
5. Configure a DHCPv6 policy.
1 ZXR10(config-dhcpv6)#policy <policy-name><priority> Enters DHCPv6 policy

configuration mode from
DHCPv6 configuration mode,
and configures the priority of
the policy, range: 1 to 5.
2 ZXR10(config-dhcpv6-policy)#dhcpv6-pool Binds a DHCPv6 policy to a

<pool-name> DHCPv6 address pool.
3 ZXR10(config-dhcpv6-policy)#link-addrss Configures a DHCPv6 policy

<ipv6-address> link-address.
6. Configure the DHCPv6 server interface.

configuration mode.
2 ZXR10(config-dhcpv6-if)#server policy <policy-name> Configures a DHCPv6 server

policy on the interface.
3 ZXR10(config-dhcpv6-if)#enable server-unicast Enables unicast on a DHCPv6

interface.
24-6

Command Function
ZXR10#show ipv6 dhcp server user [interface Shows the client information on a
<interface-name>]|[summary] DHCPv6 server.
8. Maintain DHCPv6.
Command Function
ZXR10#debug dhcpv6 server Enables DHCPv6 server debugging

function.
ZXR10#kick-off ipv6 dhcp server user [[interface Kicks off online users of the DHCP
<interface-name>]|[prefix<IPv6 prefix>[vrf-instance server by the specified attribute, such as
<vrf-name>]]|[address <IPv6 address>[vrf-instance interface, IPv6 prefix and IPv6 address.
<vrf-name>]]
End of Steps
24.3 Configuring a DHCPv6 Relay

This procedure describes how to configure a DHCPv6 relay.
Steps
1. Enable the DHCPv6 function.
1 ZXR10(config)#dhcp ipv6 Enters DHCPv6 configuration

mode.
2 ZXR10(config-dhcpv6)#enable Enables the embedded

DHCPv6 function.
2. Configure a DHCPv6 relay server group.
1 ZXR10(config-dhcpv6)#relay server group <number> Enters DHCPv6 relay server

group configuration mode
from DHCPv6 configuration
mode.
2 ZXR10(config-dhcpv6r-server-group)#algorithm Configures the DHCPv6 relay

{normal | first | round-robin} server to use a policy. The
default forwarding mode is
normal.
24-7

3 ZXR10(config-dhcpv6r-server-group)#server <server Configures the DHCPv6 relay

-no><server-ipv6>[interface <interface-name>][master] server to trust information.
4 ZXR10(config-dhcpv6r-server-group)#deadtime Configures the unavailable

<time> duration after the DHCPv6
relay server fails to send
messages.
5 ZXR10(config-dhcpv6r-server-group)#description Configures the description for

<descript-string> a DHCP relay server.
6 ZXR10(config-dhcpv6r-server-group)#max-retry Configures the number of retry

<limit-value> attempts that the DHCPv6
relay server group requests
the address from an external
DHCPv6 server, default: 10.
normal: The normal mode is to forward to all servers.

first: The first mode is master/slave mode.
round-robin: Round-robin refers to load sharing mode.
<server-no>: server number, range: 15.

[master]: master server.
3. Configure a DHCPv6 relay policy.
1 ZXR10(config-dhcpv6)#relay policy <policy-name> Enters DHCPv6 relay policy

configuration mode from
DHCPv6 configuration mode.
2 ZXR10(config-dhcpv6r-policy-group)#default Configures the DHCPv6 relay

server-group <server-group-number> server group that is binded
to the DHCPv6 relay policy
group by default.
4. Configure DHCPv6 relay parameters.
1 ZXR10(config-dhcpv6)#relay intfid-format {china-tel | Configures the interface-ID

dsl-forum | user-configuration} format of the DHCPv6 relay.
By default, the L3 interface
index is used directly.
24-8

2 ZXR10(config-dhcpv6)#relay remote-id Configures the global

<enterprise-number><remote-id> remote-ID of a relay. It is
allowed not to configure this
command. By default, the
value is not configured.
china-tel: China Telecommunication mode.
dsl-forum: DSL forum mode.
user-configuration: user configuration mode.

<enterprise-number>: the enterprise number, range: 0 to 4294967295.
<remote-id>: the remote-ID string, 1 to 32 characters in length.
5. Configure a DHCPv6 relay interface.

configuration mode.
2 ZXR10(config-dhcpv6-if-interface-name)#relay Configures the IP address

agent <ipv6-address> of a DHCPv6 agent on an
interface.
3 ZXR10(config-dhcpv6-if-interface-name)#relay Configures an interface-ID

interface-id <interface-id> of a DHCPv6 relay on an
interface. The ID is valid
when the interface-ID format
is user-configuration.
The interface-ID is a string
with 1 to 16 characters. By
default, the primary Option82
is kept, that is, transparent
transmission.
4 ZXR10(config-dhcpv6-if-interface-name)#relay Configures a DHCPv6 relay

policy <policy-name> policy of an interface.
Command Function
ZXR10#show ipv6 dhcp relay user [interface Displays the client information on a
<interface-name>]|[summary] DHCPv6 relay.
7. Maintain DHCPv6.
24-9

Command Function
ZXR10#debug dhcpv6 relay Enables DHCPv6 relay debugging

function.
ZXR10#kick-off ipv6 dhcp relay user [[interface Kicks off online users of the DHCP
<interface-name>]|[prefix<IPv6 prefix>[vrf-instance relay by the specified attribute, such
<vrf-name>]]|[address <IPv6 address>[vrf-instance as interface, IPv6 prefix and IPv6
<vrf-name>]] address.
End of Steps
24.4 Configuring the DHCPv6 Client

This procedure describes how to configure the DHCPv6 client.
Steps
1. Run the following command to configure the DHCPv6 client.
1 ZXR10(config-interface-name)#ipv6 dhcp client Obtains an IPv6 address.

address [<rapid-commit>]
2 ZXR10(config-interface-name)#ipv6 dhcp address Configures the prefix of the

<name> X:X::X:X/<1-128> address of the DHCPv6 client.
3 ZXR10(config-interface-name)#ipv6 dhcp client Enables the DHCPv6 client

pd <name>[<rapid-commit>] address prefix and configuration
parameter application functions.
<rapid-commit>: rapid negotiation.

End of Steps
24.5 DHCPv6 Configuration Examples

24.5.1 DHCPv6 Server Configuration Example
As shown in Figure 24-3, R1 acts as a DHCP server and the default gateway. The PC
obtains an IP address dynamically through the DHCP.
24-10

Figure 24-3 DHCPv6 Server Configuration Example
The configuration requirements of ZXR10 are described below.

l In global configuration mode, configure an IPv6 address, an IPv6 pool, a DHCPv6
pool, and a DHCPv6 policy. Enable DHCPv6 function.
l In interface configuration mode, configure an IP address and DHCP server mode.
Bind the DHCPv6 policy.
Configuration Flow
1. Enable IPv6 on the interface, and configure an IPv6 address.
2. Configure an IPv6 address pool, and configure related parameters such as the range
of the address pool. The range of the addresses in the pool should be on the same
network segment.
3. Enable DHCPv6 globally.
4. Configure DHCPv6 pool. The DHCPv6 pool needs to be bounded to an IP pool.
Configure DNS, lease time and other parameters.
5. Configure a DHCPv6 policy. The DHCPv6 policy is a policy option. Many priorities are
supported by a name for policy management.
6. Configure a DHCPv6 server. Configure the server mode in DHCPv6 interface
configuration mode. Bind the policy.
Configuration on ZXR10:
ZXR10(config-if-gei-0/1)#ipv6 address 86::1:1/96
/*Configure an IPv6 address pool*/

ZXR10(config)#ipv6 addr-pool zte
ZXR10(config-ipv6-addr-pool)#addr-range 86::1:2 86::1:10
ZXR10(config-ipv6-addr-pool)#exit
/*Enable DHCPv6*/
ZXR10(config)#dhcp ipv6
ZXR10(config-dhcpv6)#enable
/*Bind the IPv6 address pool to the DHCPv6 pool*/

ZXR10(config-dhcpv6)#pool zte
24-11

ZXR10(config-dhcpv6-pool)#address-pool zte
ZXR10(config-dhcpv6-pool)#exit
/*Bind the DHCPv6 pool to the DHCPv6 policy*/

ZXR10(config-dhcpv6)#policy zte 1
ZXR10(config-dhcpv6-policy)#dhcpv6-pool zte
ZXR10(config-dhcpv6-policy)#exit
/*Configure server mode in interface configuration mode and bind the policy*/
ZXR10(config-dhcpv6)#interface gei-0/1
ZXR10(config-dhcpv6-if-gei-0/1)#mode server
ZXR10(config-dhcpv6-if-gei-0/1)#server policy zte
ZXR10(config-dhcpv6-if-gei-0/1)#exit
Check the configuration of the IPv6 address pool on ZXR10, as shown below.
ZXR10#show ipv6 addr-pool configure zte
PoolName Lock Begin End Vrf Used Free
zte no 86::1:2 86::1:10 0 15
RangeTotal:1
Check the DHCPv6 configuration on ZXR10, as shown below.

ZXR10#show running-config dhcpv6
! <DHCPV6>
dhcp ipv6
policy zte 1
dhcpv6-pool zte
$
pool zte
address-pool zte
$
interface gei-0/1
mode server
server policy zte
enable
$
! </DHCPV6>
After the PC user obtains an address through DHCPv6, check the user information on
ZXR10, as shown below.
ZXR10#show ipv6 dhcp server user
Client DUID: 000100014CFBF3DB001094000001
IA NA: IA ID 0, T1 50000, T2 80000
Address: 86::1:2
preferred lifetime 1000, valid lifetime 1000
24-12

expires at 11:08:10 12/07/2010 (994 seconds)
24.5.2 DHCPv6 Relay Configuration Example

If a DHCP client and a server do not belong to the same network, it is necessary to use a
router that is directly connected to the user as a DHCPv6 relay.
As shown in Figure 24-4, enable the DHCPv6 relay function on R1. R2 provides the
DHCPv6 server function. This method is usually applied if there are many hosts requesting
the DHCPv6 service.
Figure 24-4 DHCPv6 Relay Configuration Example
The configuration requirements are described as follows.

l Configure an IPv6 address, a DHCPv6 server address, and DHCPv6 relay mode on
the interface of R1.
l Configure an IPv6 address and DHCPv6 server mode on the interface of R2. Bind a
DHCPv6 policy to the interface of R2.
l In global configuration mode on R2, enable DHCPv6. Configure an IPv6 address pool,
a DHCPv6 pool, and a DHCPv6 policy. Configure a route pointing to the interface
network segment of R1.
Configuration Flow
1. Configure an IPv6 address on the interface of the relay, and enable DHCPv6.
2. Configure a relay server group on the relay. Bind the group in the relay policy.
3. Configure relay agent mode on the interface connected to the PC on the relay.
4. The configuration on the server is similar to that on the server in the DHCPv6 Server
Configuration Example section. It is necessary to specify the IPv6 address of the
relay interface in the DHCPv6 policy.
5. Configure a static route to the network segment of the relay interface on the server.
/*Configure an interface*/
R1(config-if-gei-0/1)#ipv6 address 86::1:1/96
24-13

/*Enable DHCPv6 function*/

R1(config)#dhcp ipv6
R1(config-dhcpv6)#enable
/*Specify a server*/
R1(config-dhcpv6)#relay server group 1
R1(config-dhcpv6-server-group)#server 1 87::1:2
R1(config-dhcpv6-server-group)#exit
/*Configure a relay policy*/

R2(config-dhcpv6)#pool zte1
R2(config-dhcpv6-pool)#address-pool zte1
R2(config-dhcpv6-pool)#exit
/*Configure interface DHCP mode and other attributes*/

R1(config-dhcpv6)#interface gei-0/1
R1(config-dhcpv6-if-gei-0/1)#mode relay
R1(config-dhcpv6-if-gei-0/1)#relay agent 86::1:1
R1(config-dhcpv6-if-gei-0/1)#relay policy 1
R1(config-dhcpv6-if-gei-0/1)#exit
R1(config-dhcpv6)#exit
/*Configure an interface*/
/*Configure an IPv6 address pool*/

R2(config)#ipv6 addr-pool zte1
R2(config-ipv6-addr-pool)#addr-range 86::1:10 86::1:50
R2(config-ipv6-addr-pool)#exit
/*Enable DHCPv6*/
24-14

/*Bind the IPv6 address pool to the DHCPv6 pool*/

R2(config-dhcpv6)#pool zte1
R2(config-dhcpv6-pool)#address-pool zte1
/*Bind the DHCPv6 pool to the DHCPv6 policy*/

R2(config-dhcpv6)#policy zte1 1
R2(config-dhcpv6-policy)#dhcpv6-pool zte1
R2(config-dhcpv6-policy)#link-address 86::1:1
R2(config-dhcpv6-policy)#exit
/*Configure DHCP mode of the interface*/

R2(config-dhcpv6-if-gei-0/2)#mode server
R2(config-dhcpv6-if-gei-0/2)#server policy zte1
R2(config-dhcpv6-if-gei-0/2)#exit
/*Configure a static route*/

R2(config)#ipv6 route 86::/96 87::1:1
Check the DHCPv6 configuration on R1, as shown below.
R1#show running-config dhcpv6

! <DHCPV6>
dhcp ipv6
relay policy 1
default server-group 1
$
relay server group 1
server 1 87::1:2
$
interface gei-0/1
mode relay
relay agent 86::1:1
relay policy 1
$
enable
! </DHCPV6>
Check the configuration of the IPv6 address pool on R2, as shown below.
R2#show ipv6 addr-pool configure zte1

PoolName Lock Begin End Vrf Used Free
zte1 no 86::1:10 86::1:50 0 65
RangeTotal:1
24-15

Check the DHCPv6 configuration on R2, as shown below.
R2#show running-config dhcpv6

! <DHCPV6>
dhcp ipv6
policy zte1 1
dhcpv6-pool zte1
link-address 86::1:1
$
pool zte1
address-pool zte1 lifetime 10000 10000
$
interface gei-0/2
mode server
server policy zte1
$
enable
! </DHCPV6>
After the PC user obtains an address through the DHCPv6, check the user information on
R2, as shown below.
R2#show ipv6 dhcp server user
IA NA: IA ID 0, T1 50000, T2 80000
Address: 86::1:10
IA NA: IA ID 0, T1 50000, T2 80000
Address: 86::1:11
IA NA: IA ID 0, T1 50000, T2 80000
Address: 86::1:12
24.5.3 DHCPv6 Client Configuration Example

R2 operates as a DHCPv6 server and a default gateway. R1 obtains an IPv6 address
dynamically through the DHCP and uses this address to connect to the network, see Figure
24-5.
24-16

Figure 24-5 DHCPv6 Client Configuration Example
Configuration Flow
1. Configure R2 as the DHCPv6 server.
2. Enable the DHCPv6 Client function on R1.
R2(config)#ipv6 addr-pool zte
R2(config-ipv6-addr-pool)#addr-range 11:12::1:1 11:12::1:100
R2(config-ipv6-addr-pool)#exit
R2(config)#ipv6 prefix-pool zte1
R2(config-ipv6-prefix-pool)#prefix-delegation 11:11::12:0/112 112
R2(config-ipv6-prefix-pool)#exit
R2(config-dhcpv6)#pool zte
R2(config-dhcpv6-pool)#address-pool zte
R2(config-dhcpv6-pool)#address-lifetime 60 60
R2(config-dhcpv6-pool)#prefix-lifetime 60 60
R2(config-dhcpv6-pool)#prefix-pool zte1
R2(config-dhcpv6)#policy zte 1
R2(config-dhcpv6-policy)#dhcpv6-pool zte
R2(config-dhcpv6-policy)#exit
R2(config-dhcpv6-if-gei-1/2)#mode server
R2(config-dhcpv6-if-gei-1/2)#server policy zte
24-17

R1(config-if-gei-1/2)#ipv6 dhcp client address

/*obtain an IPv6 address*/
R1(config-if-gei-1/2)#ipv6 dhcp address zte ::110/112
/*Configure the suffix*/
R1(config-if-gei-1/2)#ipv6 dhcp client pd zte rapid-commit
/*Obtain the IPv6 prefix*/
Run the show ipv6 interface<interface-name> command on R1 to check the interface:
R1(config)#show ipv6 interface gei-1/2

Interface gei-1/2 is up, line protocol is up
IPv6 is enabled, Hardware is Gigabit Ethernet
Hardware address is 000d.0d00.000c
Index 17
Bandwidth 1000000 Kbits
IPv6 MTU 1500 bytes
inet6 fe80::20d:dff:fe00:c/10
inet6 11:12::1:1/128
inet6 11:11::12:110/112
ND DAD is enabled, number of DAD attempts: 3
ND reachable time is 30000 milliseconds
The client has two IPv6 addresses. One is obtained directly: 11:12::1:1/128. The suffix is
128 bits. The other consists of two parts: the obtained IP prefix and the configured suffix:
11:11::12:110/112.
You can also run the following command on R2 to check the allocated IPv6 addresses and
the prefix:
R2(config)#sho ipv6 dhcp server user
Client DUID: 00030001000D0D00000C
IA NA: IA ID 17, T1 30, T2 48
Address: 11:12::1:1
IA PD: IA ID 17, T1 30, T2 48
Prefix: 11:11::12:0/112
24-18

Figures
Figure 2-1 IPv4 Header Format................................................................................. 2-2
Figure 2-2 IPv6 Header Format................................................................................. 2-2
Figure 2-3 IPv6 Address Configuration Example ..................................................... 2-15
Figure 4-1 Topology Diagram for Configuring a Static IPv6 Route (Direct Next
Hop) ....................................................................................................... 4-4
Figure 4-2 Topology Diagram for Configuring a Static IPv6 Route (Indirect Next
Hop) ....................................................................................................... 4-6
Figure 4-3 Default IPv6 Route Configuration Example .............................................. 4-7
Figure 4-4 Networking Diagram for Configuring FRR for Static IPv6 Route in a
Public Network........................................................................................ 4-8
Figure 4-5 Networking Diagram for Configuring FRR for Static IPv6 Route in a
Private Network .................................................................................... 4-10
Figure 4-6 Networking Diagram of Load Sharing between Static Routes................. 4-12
Figure 4-7 Networking Diagram of the BFD Source-End Next-Hop of IPv6 Static
Route.................................................................................................... 4-14
Figure 5-1 Topology of RIPng Basic Configuration Example...................................... 5-5
Figure 5-2 Topology of RIPng Route Collection Configuration Example .................. 5-11
Figure 6-1 Topology of OSPFv3 Configuration Examples........................................ 6-11
Figure 6-2 Topology of OSPFv3 Configuration Example 2....................................... 6-14
Figure 6-3 Topology of OSPFv3 Route Load-Sharing Configuration
Examples.............................................................................................. 6-19
Figure 7-1 Single-Area IS-ISv6 Configuration Example ............................................. 7-9
Figure 7-2 Multi-Area IS-ISv6 Configuration Example ............................................. 7-14
Figure 8-1 BGP4+ Route Reflector Configuration Example ....................................... 8-4
Figure 8-2 BGP4+ Route Load-Sharing Configuration Example ................................ 8-5
Figure 8-3 BGP4+ General Configuration Example ................................................... 8-7
Figure 9-1 An Example of Configuring a Routing Policy for Redistributing RIPng
Routes .................................................................................................... 9-7
Figure 9-2 An Example of Configuring an IS-ISv6 Routing Policy............................ 9-10
Figure 9-3 An Example of Configuring an OSPFv3 Routing Policy .......................... 9-13
Figure 9-4 An Example of Configuring a BGP4+ Routing Policy.............................. 9-16
Figure 9-5 An Example of Configuring a Routing Policy for 6VPE ........................... 9-21
Figure 9-6 IPv6 Policy Route Configuration Example .............................................. 9-31

Figure 10-1 Structure of IPv6 Multicast Address on the Basis of Unicast

Prefix .................................................................................................... 10-2
Figure 11-1 Networking Diagram of the IPv6 Static Multicast Configuration
Example ............................................................................................... 11-3
Figure 12-1 MLDv1 Configuration Example............................................................. 12-6
Figure 12-2 Example for Configuring a Router to Join a Static MLD Group and a
Dynamic MLD Group ............................................................................ 12-8
Figure 13-1 Network Architecture of PIM-DM Configuration Example...................... 13-3
Figure 14-1 PIM-SM Configuration Example ........................................................... 14-7
Figure 15-1 IPv6 PIM-SSM Configuration Example................................................. 15-2
Figure 16-1 Principles of the IPv6 over IPv4 Tunnel Mechanism ............................. 16-1
Figure 16-2 Principles of the IPv4 (or IPv6) over IPv4 Tunnel.................................. 16-2
Figure 16-3 Principles of a 6in4 Tunnel ................................................................... 16-2
Figure 16-4 Principles of a 6to4 Tunnel................................................................... 16-3
Figure 16-5 Principles of a 4in6 Tunnel ................................................................... 16-4
Figure 16-6 6in4 Tunnel Configuration Example...................................................... 16-6
Figure 16-7 4in6 Tunnel Configuration Example...................................................... 16-9
Figure 16-8 6to4 Tunnel Configuration Example ................................................... 16-11
Figure 16-9 ISATAP Tunnel Principle .................................................................... 16-14
Figure 16-10 ISATAP Configuration Example........................................................ 16-15
Figure 17-1 6rd Prefix Delegation ........................................................................... 17-2
Figure 17-2 A Global Unicast Address .................................................................... 17-2
Figure 17-3 Private Address Aggregation................................................................ 17-2
Figure 17-4 Forwarding a Message in a 6rd Domain............................................... 17-3
Figure 17-5 Forwarding a Message out of a 6rd Domain......................................... 17-4
Figure 17-6 Forwarding a Message to a 6rd domain ............................................... 17-5
Figure 17-7 An Example of Configuring 6RD........................................................... 17-7
Figure 18-1 6PE Implementation............................................................................. 18-1
Figure 18-2 6PE Configuration Example ................................................................. 18-3
Figure 19-1 VPN-IPv6 Address Format ................................................................... 19-2
Figure 19-2 Network Topology of the IPv6 Static Route Configuration Between CE
and PE.................................................................................................. 19-4
Figure 19-3 Network Topology of the RIPng Configuration Between CE and
PE ........................................................................................................ 19-5
Figure 19-4 Network Topology of the OSPFv3 Configuration Between CE and
PE ........................................................................................................ 19-7
II

Figures
Figure 19-5 Network Topology of the EBGP Configuration Between CE and

PE ........................................................................................................ 19-8
Figure 19-6 Network Topology of the MPBGP Configuration ................................... 19-9
Figure 19-7 6VPE Configuration Example............................................................. 19-12
Figure 20-1 IPv6 ACL Configuration Example ......................................................... 20-4
Figure 21-1 Topology of IPv6 URPF Configuration Example (Strict) ........................ 21-3
Figure 21-2 Topology of IPv6 URPF Configuration Example (Loose)....................... 21-5
Figure 22-1 IPv6 Priority Scheduling Configuration Example................................... 22-1
Figure 22-2 IPv6 CAR SET Configuration Example................................................. 22-5
Figure 22-3 IPv6 Priority Inheritance Configuration Example................................... 22-6
Figure 22-4 Inheritance from 802.1p to IPP............................................................. 22-8
Figure 23-1 Basic VRRP Configuration (IPv6)......................................................... 23-4
Figure 23-2 Symmetrical VRRP Configuration (IPv6) .............................................. 23-7
Figure 23-3 VRRP Heartbeat Configuration (IPv6) ................................................ 23-10
Figure 24-1 Relation Among DHCPv6 Client, Relay and Server.............................. 24-1
Figure 24-2 DHCPv6 Protocol Message Interaction ................................................ 24-3
Figure 24-3 DHCPv6 Server Configuration Example............................................. 24-11
Figure 24-4 DHCPv6 Relay Configuration Example .............................................. 24-13
Figure 24-5 DHCPv6 Client Configuration Example .............................................. 24-17
III

Figures
IV

Tables
Table 2-1 IPv6 Address Space .................................................................................. 2-3
Table 2-2 Aggregatable Global Unicast Address Fields ............................................. 2-5
Table 2-3 Structure of the IPv6 Address Embedded With IPv4 Address .................... 2-7
Table 2-4 Structures of Link-local Address and Site-local Address ............................ 2-7
Table 2-5 Multicast Address Format .......................................................................... 2-8
Table 2-6 Multicast Scope Values ............................................................................. 2-9
Table 2-7 IPv6 Address Compression ..................................................................... 2-11
Table 6-1 Similarities and Differences Between OSPFv3 LSAs and OSPFv2
LSAs ........................................................................................................ 6-5
Table 9-1 IP Address Planning ................................................................................ 9-21
Table 10-1 IPv6 Multicast Address Allocation .......................................................... 10-1
Table 19-1 Addresses on the Interfaces ................................................................ 19-12

VI

Glossary
6VPE
- IPv6 VPN Provider Edge
ACL
- Access Control List
ARP
- Address Resolution Protocol
AS
- Autonomous System
BDR
- Backup Designate Router
BGP
- Border Gateway Protocol
BOOTP
- Bootstrap Protocol
BR
- Border Router
BSR
- Bootstrap Router
CAR
- Committed Access Rate
CE
- Customer Edge
CIDR
- Classless Inter-Domain Routing
DHCP
- Dynamic Host Configuration Protocol
DIS
- Designate IS
DR
- Designated Router
DSCP
- Differentiated Services Code Point
DUID
- DHCP Unique Identifier
VII

IA
- Identity Association
IBGP
- Interior Border Gateway Protocol
ICMP
- Internet Control Message Protocol
IEEE
- Institute of Electrical and Electronics Engineers
IETF
- Internet Engineering Task Force
IGMP
- Internet Group Management Protocol
IGP
- Interior Gateway Protocol
IP
- Internet Protocol
IPSec
- IP SecurityProtocol
IPX
- Internetwork Packet Exchange protocol
IPv4
- Internet Protocol version 4
IPv6
- Internet Protocol Version 6
IS-IS
- Intermediate System-to-Intermediate System
ISATAP
- Intra-Site Automatic Tunnel Addressing Protocol
ISO
- International Organization for Standardization
ISP
- Internet Service Provider
LAN
- Local Area Network
LDP
- Label Distribution Protocol
LLQ
- Low Latency Queueing
VIII

Glossary
LSA
- Link State Advertisement
LSDB
- Link-state Database
LSP
- Link State Packet
LSP
- Label Switched Path
LSU
- Link State Update
MAC
- Media Access Control
MD5
- Message Digest 5 Algorithm
MLD
- Multicast Listener Discovery
MLDv2
- Multicast Listener Discovery Version 2
MPLS
- Multiprotocol Label Switching
MSDP
- Multicast Source Discovery Protocol
MTU
- Maximum Transfer Unit
NA
- Neighbor Advertisement
NBMA
- Non-Broadcast Multiple Access
NDP
- Neighbor Discovery Protocol
NS
- Neighbor Solicitation
NSAP
- Network Service Access Point
OSI
- Open System Interconnection
OSPF
- Open Shortest Path First
IX

PE
- Provider Edge
PIM-DM
- Protocol Independent Multicast - Dense Mode
PIM-SSM
- Protocol Independent Multicast-Source Specific Multicast
QoS
- Quality of Service
RA
- Router Advertisement
RD
- Route Distinguisher
RFC
- Request For Comments
RIP
- Routing Information Protocol
RIPng
- Routing Information Protocol next generation
RP
- Rendezvous Point
RS
- Router Solicitation
RSVP-TE
- Resource Reservation Protocol - Traffic Engineering
RT
- Route Target
SPF
- Shortest Path First
SPT
- Shortest Path Tree
SSM
- Source Specific Multicast
TCP/IP
- Transmission Control Protocol/Internet Protocol
TLV
- Tag, Length, Value
TTL
- Time To Live

Glossary
UDP
- User Datagram Protocol
URPF
- Unicast Reverse Path Forwarding
VLAN
- Virtual Local Area Network
VPN
- Virtual Private Network
VRF
- Virtual Route Forwarding
WFQ
- Weighted Fair Queuing
WRED
- Weighted Random Early Detection
XI

zxr10 ZSR v2

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

zxr10 ZSR v2

Încărcat de

Drepturi de autor:

Formate disponibile

ZXR10 ZSR V2

Intelligent Integrated Multi-Service Router

Revision No. Revision Date Revision Reason

R1.0 2014-05-10 First edition

Serial Number: SJ-20140504150128-018

Publishing Date: 2014-05-10 (R1.0)

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Chapter 2 IPv6 Address Configuration..................................................... 2-1

Chapter 3 NDP Configuration.................................................................... 3-1

Chapter 4 IPv6 Static Route Configuration .............................................. 4-1

Chapter 5 RIPng Configuration ................................................................. 5-1

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Chapter 7 IS-ISv6 Configuration ............................................................... 7-1

Chapter 8 BGP4+ Configuration ............................................................... 8-1

Chapter 9 IPv6 Route-Map Policy Configuration..................................... 9-1

Chapter 10 IPv6 Multicast ........................................................................ 10-1

Chapter 11 IPv6 Static Multicast Configuration..................................... 11-1

Chapter 12 MLD Configuration................................................................ 12-1

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Chapter 13 IPv6 PIM-DM Configuration.................................................. 13-1

Chapter 14 IPv6 PIM-SM Configuration .................................................. 14-1

Chapter 15 IPv6 PIM-SSM Configuration................................................ 15-1

Chapter 16 IPv6 Tunnel Configuration ................................................... 16-1

Chapter 17 6RD Configuration ................................................................ 17-1

Chapter 18 6PE Configuration................................................................. 18-1

Chapter 19 6VPE Configuration .............................................................. 19-1

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Chapter 20 IPv6 ACL Configuration........................................................ 20-1

Chapter 21 IPv6 URPF Configuration ..................................................... 21-1

Chapter 22 IPv6 QoS Configuration........................................................ 22-1

Chapter 23 IPv6 VRRP Configuration ..................................................... 23-1

Chapter 24 DHCPv6 Configuration ......................................................... 24-1

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

3, NDP Configuration Describes the NDP principle, configuration commands and

5, RIPng Configuration Describes the RIPng principle, configuration commands and

6, OSPFv3 Configuration Describes the OSPFv3 principle, configuration commands and

7, IS-ISv6 Configuration Describes the IS-ISv6 principle, configuration commands and

8, BGP4+ Configuration Describes the BGP4+ principle, configuration commands and

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

| Separates individual parameter in series of parameters.

Danger: indicates an imminently hazardous situation. Failure to comply can result in

Warning: indicates a potentially hazardous situation. Failure to comply can result in

Caution: indicates a potentially hazardous situation. Failure to comply can result in

Note: provides additional information about a certain topic.

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

1.1 IPv6 Overview

1.2 Configuring IPv6

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

Step Command Function

1 ZXR10(config)#interface <interface-name> Enters interface configuration

2 ZXR10(config-if-interface-name)#ipv6 forward After this command is

3 ZXR10(config)#icmp-config Enters ICMP configuration

4 ZXR10(config-icmp)#interface {byname Enters ICMP interface

5 ZXR10(config-icmp-if-interface-name)#ip Enables a specified interface

<interface-byname>: interface alias, containing up to 32 characters.

SJ-20140504150128-018|2014-05-10 (R1.0) ZTE Proprietary and Confidential

ZXR10(config)#ipv6 tcp synwait-time <wait-time> Sets the duration of attempting to

ZXR10(config)#ipv6 tcp window-size <wait-size> Sets the size of the window