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

ZXR10 5900E Series
Easy-Maintenance MPLS Routing Switch

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

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

2.1 IPv6 Overview.................................................................................................... 2-1
2.1.1 IPv6 Address Format................................................................................ 2-1
2.1.2 IPv6 Address Prefix .................................................................................. 2-2
2.1.3 IPv6 Address Classification....................................................................... 2-2
2.1.4 IPv6 Header............................................................................................. 2-7
2.1.5 IPv6/IPv4 Dual Protocol Stack................................................................... 2-8
2.2 Configuring IPv6 Address ................................................................................... 2-9
2.3 IPv6 Address Configuration Example................................................................... 2-9
2.4 IPv6 Maintenance and Diagnosis ........................................................................ 2-9
Chapter 3 IPv6 Neighbor Discovery Protocol .......................................... 3-1

3.1 Introduction to NDP ............................................................................................ 3-1
3.2 Configuring NDP ................................................................................................ 3-3
3.3 IPv6 NDP Configuration Example ........................................................................ 3-4
3.4 IPv6 NDP Maintenance and Diagnosis ................................................................ 3-4
Chapter 4 IPv6 Tunnel Configuration ....................................................... 4-1

4.1 IPv6 Tunnel Overview......................................................................................... 4-1
4.2 Configuring IPv6 Tunnel ..................................................................................... 4-3
4.3 Example of IPv6 Manually Configured Tunnel ...................................................... 4-3
4.4 IPv6 Tunnel Maintenance and Diagnosis ............................................................. 4-6
Chapter 5 IPv6 Other Configurations ....................................................... 5-1

5.1 Configuring IPv6 Static Route ............................................................................. 5-1
5.2 Configuring IPv6 DHCP SNOOPING ................................................................... 5-1
5.3 Configuring DHCPv6 relay .................................................................................. 5-3
5.4 Other Configuration Commands .......................................................................... 5-4
5.5 Maintenance and Diagnosis Commands .............................................................. 5-4
5.6 Configuration Example ....................................................................................... 5-5
Chapter 6 RIPng Configuration ................................................................. 6-1
I
6.1 RIPng Overview ................................................................................................. 6-1
6.2 Configuring RIPng .............................................................................................. 6-3
6.2.1 Configuring Basic RIPng........................................................................... 6-3
6.2.2 Configuring RIPng Enhanced Function ...................................................... 6-3
6.3 RIPng Configuration Example ............................................................................. 6-4
6.4 RIPng Maintenance and Diagnosis...................................................................... 6-4
Chapter 7 OSPFv3 Configuration.............................................................. 7-1

7.1 OSPFv3 Overview.............................................................................................. 7-1
7.1.1 Differences between OSPFv3 and OSPFv2 ............................................... 7-1
7.1.2 LSA Types ............................................................................................... 7-3
7.2 Configuring OSPFv3........................................................................................... 7-4
7.2.1 Enabling OSPFv3..................................................................................... 7-4
7.2.2 Configuring OSPFv3 Interface Parameters................................................. 7-4
7.2.3 Configuring OSPFv3 Protocol Parameters ................................................. 7-5
7.3 OSPFv3 Configuration Example .......................................................................... 7-6
7.4 OSPFv3 Maintenance and Diagnosis .................................................................. 7-6
Chapter 8 IS-ISv6 Configuration ............................................................... 8-1

8.1 IS-ISv6 Overview ............................................................................................... 8-1
8.2 Configuring IS-ISv6 ............................................................................................ 8-1
8.2.1 Enabling IS-ISv6 ...................................................................................... 8-1
8.2.2 Configuring IS-ISv6 Global Parameters...................................................... 8-2
8.2.3 Configuring IS-ISv6 Interface Parameters .................................................. 8-3
8.3 IS-ISv6 Configuration Example............................................................................ 8-4
8.3.1 Single Area IS-ISv6 Configuration Example ............................................... 8-4
8.3.2 Multi-Area IS-ISv6 Configuration Example ................................................. 8-5
8.4 IS-ISv6 Maintenance and Diagnosis .................................................................... 8-9
Chapter 9 BGP4+ Configuration ............................................................... 9-1

9.1 BGP4+ Overview ............................................................................................... 9-1
9.2 Configuring BGP4+ ............................................................................................ 9-1
9.2.1 Enabling BGP4+ ...................................................................................... 9-1
9.2.2 Configuring BGP4+ Route Advertisement .................................................. 9-2
9.2.3 Configuring EBGP Multi-Hops of BGP4+.................................................... 9-3
9.2.4 Configuring BGP4+ Route Reflector .......................................................... 9-4
9.2.5 Configuring BGP4+ Confederation ............................................................ 9-6
9.2.6 Configuring BGP4+ Route Attributes ......................................................... 9-7
9.2.7 Configuring BGP4+ IPv6 Address Family................................................... 9-8
9.3 BGP4+ Configuration Example............................................................................ 9-8
II
9.4 BGP4+ Maintenance and Diagnosis .................................................................. 9-10
Chapter 10 IPv6 Multicasting Route Configuration............................... 10-1

10.1 Multicast Overview ......................................................................................... 10-1
10.1.1 Multicast Address ................................................................................. 10-1
10.1.2 MLD Protocol ....................................................................................... 10-2
10.1.3 Multicast Tree ...................................................................................... 10-2
10.1.4 PIM-SM ............................................................................................... 10-3
10.1.5 MLD-SNOOPING ................................................................................. 10-4
10.2 Enabling IPv6 Multicast Routing Function......................................................... 10-4
10.3 Configuring MLD ............................................................................................ 10-4
10.3.1 Configuring a MLD Group on an Interface .............................................. 10-4
10.3.2 Configuring MLD Timers ....................................................................... 10-5
10.4 Configuring PIM-SM ....................................................................................... 10-5
10.4.1 Booting IPv6 PIM-SM ........................................................................... 10-5
10.4.2 Configuring Static RP Address .............................................................. 10-6
10.4.3 Configuring Candidate-BSR .................................................................. 10-6
10.4.4 Configuring Candidate-RP .................................................................... 10-6
10.4.5 Configuring Area Border with the Interface PIM ...................................... 10-7
10.4.6 Limiting BSR Message to Advertise to Candidate-RP ............................. 10-7
10.4.7 Setting DR Priority ................................................................................ 10-7
10.4.8 Configuring Interval to Send Hello Message ........................................... 10-7
10.4.9 Configuring Interval to Send PIM JP Message........................................ 10-8
10.5 Configuring MLD-SNOOPING ......................................................................... 10-8
10.6 IPv6 Multicasting Route Configuration Example................................................ 10-9
10.7 IPv6 Multicast Route Maintenance and Diagnosis............................................ 10-11
Figures............................................................................................................. I
Glossary ........................................................................................................ III
III
IV
About This Manual
Purpose
ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual
(IPv6 Volume). It is applicable for ZXR10 5900E series (V2.8.23.B2) easy-maintenance
MPLS routing switch (brieved as ZXR10 5900E series, also named as switch in common
part). It includes:
l ZXR10 5916E Easy-Maintenance MPLS Routing Switch
l ZXR10 5928E-FI Easy-Maintenance MPLS Routing Switch
What Is in This Manual

ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User Manual
(IPv6 Volume) contains the following chapters:
CHAPTER SUMMARY
Chapter Summary
Chapter 1 Safety Instruction Describes the safety instructions and signs.
Chapter 2 IPv6 Address This chapter introduces IPv6 address and related
Configuration configuration.
Chapter 3 IPv6 Neighbor Discovery This chapter introduces IPv6 Neighbor Discovery Protocol and
Protocol related configuration.
Chapter 4 IPv6 Tunnel Configuration This chapter introduces IPv6 Tunnel and related configuration.
Chapter 5 IPv6 Other Configurations This chapter introduces IPv6 Static Route, IPv6 DHCP
Snooping and DHCPv6 relay configuration.
Chapter 6 RIPng Configuration This chapter introduces RIPng and related configuration.
Chapter 7 OSPFv3 Configuration This chapter introduces OSPFv3 and related configuration.
Chapter 8 IS-ISv6 Configuration This chapter introduces IS-ISv6 and related configuration.
Chapter 9 BGP4+ Configuration This chapter introduces BGP4+ and related configuration.
Chapter 10 IPv6 Multicasting Route This chapter introduces IPv6 Multicasting Routes and related
Configuration configuration.
Related Documentation
l ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch
Hardware Manual
l ZXR10 5900E Series (V2.8.23.B2) Easy-Maintenance MPLS Routing Switch User
Manual (Basic Configuration Volume)
I
Manual (Ethernet Switching Volume)
Manual (IPv4 Routing Volume)
Manual (IPv6 Volume)
The commands supported by ZXR10 5900E series (V2.8.23.B2) easy-maintenance MPLS
routing switch is based on unified platform ZXROS V4.8.23.
II
Chapter 1
Safety Instruction
Table of Contents
Safety Instruction .......................................................................................................1-1
Safety Signs ...............................................................................................................1-1
1.1 Safety Instruction

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

The contents that users should pay attention to when they install, operate and maintain
devices are explained in the following formats:
Warning!
Indicates the matters needing close attention. If this is ignored, serious injury accidents may happen
or devices may be damaged.
Caution!
Indicates the matters needing attention during configuration.
1-1
SJ-20101226010430-005|2011-02-11(R1.0) ZTE Proprietary and Confidential

ZXR10 5900E Series User Manual (IPv6 Volume)
Note:
Indicates the description, hint, tip and so on for configuration operations.
1-2

Chapter 2
IPv6 Address Configuration
Table of Contents
IPv6 Overview ............................................................................................................2-1
Configuring IPv6 Address...........................................................................................2-9
IPv6 Address Configuration Example .........................................................................2-9
IPv6 Maintenance and Diagnosis ...............................................................................2-9
2.1 IPv6 Overview

IPv6 is the next version of IP protocol. With the development of Internet, IPv4 addresses
of 32 bits will be dried up. IPv4 will be superseded by IPv6 in the near future.
IPv6 is first described in RFC 2460 by IETF. It provides services such as point to point
security, QoS and global unique address. Structure of IPv6 allows users to upgrade IPv4
addresses to IPv6 addresses conveniently.
IPv6 development is to provide plenty of global unique addresses to meet more and more
requirements of intelligent devices in network. These devices include Personal Data
Assistant (PDA), mobile telephone and network access device for family.
2.1.1 IPv6 Address Format

An IPv6 address format is X:X:X:X:X:X:X:X, among which X is a 4-bit hex integer (16-bit),
for example:
FEDC:0DB0:7674:3110:FEDC:BC78:7654:1234
FEDC:0DB0:0:0:6:600:7654:6789
IPv6 addresses usually contain continuous hex 0. For writing convenience, use “::” mark
to replace continuous hex 0. This reduces the length of IPv6 addresses in writing. IPv6
address format is described in RFC 2373. Table 2-1 shows examples for compressed
formats of IPv6 addresses.
Caution!
“::” mark can only be used once in an IPv6 address. It is to replace the longest continuous hex 0.
Capitals and lowercases are not distinguished in IPv6 addresses.
2-1

Table 2-1 COMPRESSED FORMATS
IPv6 Address Type Normal Format Compressed Format
Unicast address 1080:0:0:0:8:800:200C:1234 1080::8:800:200C:1234
Multicast address FF01:0:0:0:0:0:0:123 FF01::123
Loopback address 0:0:0:0:0:0:0:1 ::1
Unspecified address 0:0:0:0:0:0:0:0 ::
In Table 2-1 , loopback address is used to send IPv6 data packets to node itself. Its function
is the same as that of IPv4. For example, an initialized node can use loopback address as
packet source address before receiving IPv6 address.
2.1.2 IPv6 Address Prefix

IPv6 address prefix is expressed in the similar way as IPv4 address prefix. It is: IPv6
address/prefix length. The prefix is a decimal integer. It is used to decide how many bits
from the most left are used as prefix. For example, 12AB:0D86:5454:6634::/32 is a correct
prefix.
2.1.3 IPv6 Address Classification

IPv6 address of 128 bits is used to identify either an interface or a group of interfaces.
Three types of IPv6 addresses are described as follows:
l Unicast address: the identifier of a single interface. The packets sent to a unicast
address will be transmitted to the interface with this address identifier.
l Multicast address: the identifier of a group of interfaces tethered to different nodes.
The packets sent to a multicast address will be transmitted to all the interfaces with
this address identifier.
l Anycast: the identifier of a group of interfaces tethered to different nodes. The
packets sent to an anycast address will be transmitted to an interface with this
address identifier (selecting the nearest one by calculating the distance based on
routing protocol).
There is no broadcast address in IPv6. Broadcast address function is replaced by that of
multicast.
The first few bits of the address specify the address type. The number of the bits is variable.
The first few bits are called format prefix. These prefixes are shown in Table 2-2 .
Table 2-2 IPV6 ADDRESS SPACE
Allocation Prefix Occupation Rate of Address

Space
Reserved 0000 0000 1/256
Unallocated 0000 0001 1/256
2-2

Chapter 2 IPv6 Address Configuration
Allocation Prefix Occupation Rate of Address

Space
Reserved for NSAP allocated 0000 001 1/128
Reserved for IPX allocated 0000 010 1/128
Unallocated 0001 1/16
Global unicast 001 1/8
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 1111 1110 10 1/1024
Site-local unicast 1111 1110 11 1/1024
Multicast 1111 1111 1/256
2.1.3.1 Unicast Address

IPv6 unicast address is an interface identifier of single node in network. Packets that use
unicast address as destination address are sent to interface with this identifier. There are
four types of unicast addresses, as described in follows:
Global Unicast Address

Global unicast address uses strict aggregation of route prefixes. This reduces entries in
routing table. Its format is shown in Table 2-3.
2-3

Table 2-3 GLOBAL UNICAST ADDRESS FORMAT
3 bits 45 bits 16 bits 64bits
Format prefix Global route prefix Site-level aggregation Interface ID

ID
Fields in Figure 31 are described as follows:

1. Format prefix: format prefix of global unicast address, 3 bits. Currently it is 001.
2. Global route prefix: 45 bits.
3. Site-level aggregation ID: it is used to divide subnets by single organization in its own
address space. IPv6 subnets have the similar function as that of IPv4. It is up to
65,535 subnets in IPv6.
4. Interface ID: it is used to identify the interface on a link. Interface ID must be unique on
a link even in a much larger scale. In many situations, it is the same with the interface
link layer address, or it is based on the interface link layer address. Identifiers of global
unicast address and other kind of address types must be 64 bits, in modified EUI-64
format.
For all IEEE 802 interface types (including Ethernet interface and FDDI interface), the
first three bytes (24 bits) of interface ID are obtained from Organization Unique Identifier
(OUI) MAC address. The fourth and fifth bytes are fixed hexadecimal number FFFE. The
last three bytes (24 bits) are obtained from the last three bytes of MAC address. Before
interface ID is finished, it is necessary to set the seventh bit in the first byte. If the value of
this bit is 0, it means it is a local management interface ID. If it is 1, it means it is a global
unique interface ID.
For other interface types, such as serial interface, ATM and frame reply, the method to form
an interface ID is the same as that of IEEE 802 interface types. As these types of interfaces
do not have MAC addresses, the MAC address is the first MAC address in device MAC
address pool.
Site-Local Unicast Address

Site-local unicast address consists of prefix FEC0::/10 (1111 1110 11), subnet ID and
interface ID. It is allocated to a site to use and does not occupy a global unicast address.
Site-local unicast address is private address and only can be used in local site. Its format
is shown in Table 2-4.
Table 2-4 SITE-LOCAL UNICAST ADDRESS FORMAT
10 bits 38 bits 16bits 64 bits
1111111011 0 Subnet ID Interface ID
Link-Local Unicast Address

Link-local unicast address can be automatically configured on interface with prefix
FE80::/10 (1111 1110 10). It is usually used in Neighbor Discovery Protocol (NDP) and
un-stateful automatic configuration. Local nodes can use this address to communicate
2-4

instead of global unicast address and site-local address. IPv6 routers can not transmit
data packets that use link-local unicast address as source or destination address to other
links.
Format of site-local unicast address is shown in Table 2-5.
Table 2-5 SITE-LOCAL UNICAST ADDRESS FORMAT
10 bits 54 bits 64 bits
1111111010 0 Interface ID
IPv4-Compatible IPv6 Address

The high 96 bits of IPv4-compatible IPv6 address are all 0. The low 32 bits are IPv4
addresses. Its format is 0:0:0:0:0:0:A.B.C.D or ::A.B.C.D.
IPv4-compatible IPv6 address is allocated to nodes which support IPv4 and IPv6 double
protocol stacks.
The whole IPv4-compatible IPv6 address is used as the node IPv6 address. The IPv4
address of low 32 bits is used as the node IPv4 address.
Format of this type of address is shown in Table 2-6.
Table 2-6 FORMAT OF IPV6 ADDRESS COMPATIBLE WITH IPV4 ADDRESS
96 bits 32 bits
0000…0000 IPv4 Address
2.1.3.2 Anycast Address

Anycast addresses can be allocated to interfaces of multiple nodes. These nodes
provide the same services. Packets that use anycast address as destination address are
transmitted to the nearest interface with this address. Whether the interface is the nearest
or not is measured in distance calculation of routing protocol.
Anycast address is allocated from unicast address space. It can use any unicast
address format. It is unable to distinguish anycast address and unicast address by the
appearances. If a unicast address is allocated to more than one interfaces, it becomes
an anycast address. It is required to point out it is an anycast address if it is allocated to
a node.
Caution!
Anycast addresses can only be used on routers. Hosts can not use anycast addresses. Anycast
addresses can not be used as source addresses in data packets.
Anycast address format of subnet router is shown in Table 2-7.
2-5

Table 2-7 ANYCAST ADDRESS FORMAT OF SUBNET ROUTER
128 bits
Subnet prefix 0000…0000
Subnet prefix is a prefix for specified link. Set interface ID of interface unicast address on
the link to be 0, then it becomes subnet router anycast address.
Packets that use subnet router anycast address as destination address are transmitted
to a router in this subnet. All routers in this subnet should support subnet router anycast
address.
When a node communicates with a router in a router group that is in a remote network,
subnet router anycast address can be applied.
2.1.3.3 Multicast Address

Prefix of IPv6 multicast address is FF00::/8 (1111 1111). Multicast address is an identifier
for a group of interfaces. These interfaces belong to different nodes. Packets that use
multicast address as destination address are transmitted to all interfaces in this multicast
group. Multicast address format is shown in Table 2-8.
Table 2-8 FORMAT OF MULTICAST ADDRESS
8 bits 4bits 4 bits 112 bits
11111111 Flag Range Group ID
Fields in Table 2-8 are described as follows:

1. In the first field, 8 bits of 1 mean this is a multicast address.
2. When the value in flag field is 0, it means this is a permanent multicast address. If the
value in flag field is 1, it means this is a temporary multicast address.
Range field is used to limit the range of multicast group. The ranges corresponding to
values are shown in Table 2-9 .
Table 2-9 IPV6 MULTICAST RANGE VALUE
Value Range
1 Local node
2 Local link
5 Local site
8 Local organization
E Global
3. Group ID is used to define a permanent multicast group or a temporary multicast group

in some range.
An IPv6 node (router or host) should be added to the following multicast groups:
2-6

l All node multicast groups FF02:0:0:0:0:0:0:1 (local link)

l Request node multicast groups
Request node multicast address consists of prefix FF02:0:0:0:0:1:FF00:0000/104
and low 24 bits of IPv6 address (unicast address or anycast address). For
example, request node multicast address that is related to IPv6 address
4037::01:800:200E:8C6C is FF02::1:FF0E:8C6C.
Request node multicast address is used in neighbor request information.
2.1.4 IPv6 Header

IPv4 header is shown in Table 2-10.
Table 2-10 IPV4 HEADER
4-bit 4-bit header 8-bit type of service 16-bit total length (in byte)
version length (TOS)
16-bit identifications 4-bit 12-bit fragment offset

flags
8-bit time to live (TTL) 8-bit protocol 16-bit header checksum
32-bit source IP address
32-bit destination IP address
24-Options 8-filling
Data
IPv6 header is shown in Table 2-11 .
Table 2-11 IPV6 HEADER
4-bit version 4bit traffic class 24-bit flow label
16 bit payload length 8-bit next header 8-bit hop limit
128-bit source address
128-bit destination address
extense packet header information
data
Fields in Table 2-11 are described as follows:

l Version
with the IPv4 header, it is a four-bit field indicating the IP version. Here, it is set to
binary 0110 to indicate version 6.
l Traffic class
it is an eight-bit field that corresponds to the eight-bit IPv4 ToS field. Given the
evolution of the ToS field over the years, both are now used for Differentiated Class
2-7

of Service (DiffServ). Even though there is a correspondence of this field with the old
ToS field, its name more accurately reflects the current usage of the values carried
here.
l Flow label
it is a field unique to IPv6. The intention of this 20-bit field is to allow labeling of
particular flows of traffic; that is, packets that are not just originated by the same
source and going to the same destination, but that belong to the same applications at
the source and destination.
l Payload length
it specifies the length of the payload, in bytes, that the packet is encapsulating.
l Next header
it specifies which header follows the IPv6 packet header. In this, it is very similar to
the Protocol field in the IPv4 header and, in fact, is used for the same purpose when
the next header is an upper-layer protocol header. In IPv6, the header following the
packet header might be an upper-layer protocol header, or an extension header.
l Hop limit
the value in this field determines the maximum hops that IPv6 packets can pass by.
When the packets pass by a router, the value reduces by one. As there is no checksum
in IPv6 header, the router does not need to calculate checksum again when the value
reduces by one. This saves time.
2.1.5 IPv6/IPv4 Dual Protocol Stack

When IPv4 is upgraded to IPv6, some application programs on network nodes are also
upgraded to use IPv6 protocol stack. Some other application programs are not upgraded,
and they still use IPv4 protocol stack. To make IPv4 stack and IPv6 stack coexist, use dual
protocol stack. Protocol structure of dual protocol stack is shown in Table 2-12.
Table 2-12 PROTOCOL STRUCTURE OF DUAL PROTOCOL STACK
Application Layer Protocol
TCP/UDP protocols
IPv6 protocols IPv4 protocols
Protocols of data link layer and physical layer
ZTE ZXROS supports IPv6/IPv4 dual protocol stack. If both IPv4 address and IPv6
address are configured on an interface, both IPv4 packets and IPv6 packets are
transmitted on this interface.
2-8

2.2 Configuring IPv6 Address

Step Command Function
1 ZXR10(config)#interface < interface-name> This enters into layer 3 interface

configuration mode.
2 ZXR10(config-if-vlanX)#ipv6 enable This enables IPv6.
3 ZXR10(config-if-vlanX)#ipv6 address < ipv6-prefix> /< This sets IPv6 address on an

prefix-length> interface.
4 ZXR10(config-if-vlanX)#ipv6 address link-local < ipv6-prefix> This sets interface linklocal address.
2.3 IPv6 Address Configuration Example

This shows an example of configuring IPv6 address and MTU.
ZXR10(config)#interface vlan 11
ZXR10(config-if-vlan11)#ipv6 enable
ZXR10(config-if-vlan11)#ipv6 address 2005:1234::1/64
ZXR10(config-if-vlan11)#ipv6 mtu 1500
or
ZXR10(config-if-vlan11)#ipv6 address link-local
fe80::1111:2222:3333:4444
2.4 IPv6 Maintenance and Diagnosis

To configure IPv6 address maintenance and diagnosis, perform the following steps.
1 ZXR10#show ipv6 interface < interface-name> This views detailed information on

IPv6 interface.
2 ZXR10#show ipv6 interface [ < interface-name> ] brief This views brief information on IPv6
interface.
2-9

This page intentionally left blank.
2-10

Chapter 3
IPv6 Neighbor Discovery
Protocol
Table of Contents
Introduction to NDP ....................................................................................................3-1
Configuring NDP ........................................................................................................3-3
IPv6 NDP Configuration Example...............................................................................3-4
IPv6 NDP Maintenance and Diagnosis .......................................................................3-4
3.1 Introduction to NDP

IPv6 does not execute the address resolution protocol (ARP) or the reserve address
resolution protocol (RARP) any more but supersedes them with the corresponding
functions of the neighbor discovery protocol (NDP). The following are primary differences
between IPv6 NDP and IPv4 ARP.
l In IPv4, the ARP is an independent protocol. It provides conversion between IP
addresses and link-layer addresses. Different ARPs should be defined for different
link-layer protocols. In IPV6, the NDP contains the ARP functions and runs over the
Internet control message protocol (ICMPv6). It features more universal, more content,
and applicable to various link-layer protocols.
l ARP protocol, ICMPv4 router discovery and ICMPv4 redirection packet are based on
broadcast, while NDP neighbor discovery packet is based on the efficient multicast
and unicast.
l The reachability detection is meant to determine whether the host or router
represented by the corresponding IP address can still receive and send packets,
to which IPv4 has no unified solution. The NDP defines the reachability detection
process to ensure that no IP packet will be sent to a black hole.
RFC 2461 (IPv6 neighbor discovery) describes the neighbor discovery mechanism, which
provides some different purposes, including the following points:
l Router discoveryThis mechanism helps a host to identify the local router.
l Prefix discoveryThis mechanism is used by nodes to determine an address prefix that
is used to specify the link-local address and an address prefix that should be sent to
a router for forwarding.
l Parameter discovery This mechanism helps nodes to determine the information like
link-local MTU.
l Address autoconfigurationThis mechanism is used for IPv6 node auto configuration.
3-1

l Address resolution This mechanism substitutes ARP and RARP to help nodes
determine the link-layer address of the local node, namely the neighbor, from the
destination IP address.
l Next hop determinationThis mechanism is meant to determine the next destination of
a packet, that is, determine whether the destination of a packet is on a local link. If it
is on the local link, then the next hop is the destination. Otherwise, the packet should
route and the next hop will serve as a router. The neighbor discovery can be used to
determine a router to be used.
l Neighbor unreachability detection Neighbor discovery can help nodes to determine
whether a neighbor (destination node or router) is reachable.
l Duplicate address detection Neighbor discovery helps a node to determine whether
an address it wants to use has been occupied on the local link.
l Redirection Sometimes the forwarding router selected by a node is not the optimum
for a packet to be forwarded. In this case, the forwarding router can redirect the node
to send the packet to an optimum router.
The neighbor discovery conducts the execution by defining the special ICMP packets,
including:
l Router Solicitation (RS) message
When an interface on a host is enabled, instead of waiting till next cycle time, the host
sends RS messages immediately.
l Router Advertisement (RA) messages
A router sends this message periodically or when it replies to RS message. RA
messages includes address prefix and maximum hops and so on.
Address prefix includes link-local address prefix and automatic configuration address
prefix. The flag of address prefix decides its type.
The host use link-local address prefix it receives to establish and maintain a list. The
list describes whether the destination of packets is on local links or the packets need
to be transmitted.
RA message tells the host how to perform address autoconfiguration. For example,
the router can specify the host to use stateful address autoconfiguration (DHCPv6) or
stateless address autoconfiguration.
RA message also includes some Internet parameters such as maximum hops, and
optional link parameters such as link MTU. It is possible to configure some important
parameters together on a router, and make the router send these parameters to its
neighbors.
l Neighbor Solicitation (NS) messages
A node sends NS messages and gets link layer from destination node to finish address
resolution. NS message is a multicast message. Its multicast address is request node
multicast address of destination node.
NS messages can be used to judge whether there are multiple nodes using the same
IPv6 address.
3-2

Chapter 3 IPv6 Neighbor Discovery Protocol
l Neighbor Advertisement (NA) messages

(NA) message is used to reply (NS) message. A destination node replies the
request sender with link layer address in this packet. It is a unicast packet. For both
communication sides, they can use a couple of NS and NA messages to get link
layer address from the peer. It is because link layer address of the sender is included
in NS message.
l Redirect messages
A router sends a Redirect message to inform the host that there is a better next hop
to destination.
Other functions of NDP are as follows:
l Link-layer address change
A node may have multiple interfaces for the same network. If the node knows that its
link-layer address is changed, it can send some multicast groups to notify other nodes
of its address change.
l Ingress load balance

A node with repeating interfaces hopes multiple interfaces that are on the same link to
balance the flow loads. For example, a network drive may be a logical interface that
represents multiple network interfaces and it has multiple link layer addresses. Load
balance allows the router to omit the source link layer address in router reply packet.
Then load balance forces the neighbor to use neighbor request packet to learn link
layer address of the router. In neighbor reply packets sent by router, different link layer
addresses are included according to the node that sends request.
3.2 Configuring NDP

1 ZXR10(config-if-vlanX)#ipv6 nd managed-config-flag This configures management

address configuration field flag in RA
message.
2 ZXR10(config-if-vlanX)#ipv6 nd other-config-flag This configures other stateful

configuration flag field in RA
message.
3 ZXR10(config-if-vlanX)#ipv6 nd prefix < ipv6-prefix> /< This configures prefix option in RA

prefix-length> [ [ < Valid-lifetime> < preferred-lifetiem> ] { off-link| message.
no-autoconfig| } | ]
4 ZXR10(config-if-vlanX)#ipv6 nd ra-interval < seconds> This configures RA message

interval.
5 ZXR10(config-if-vlanX)#ipv6 nd ra-lifetime < seconds> This configures the value of router

lifetime field in RA message.
3-3

6 ZXR10(config-if-vlanX)#ipv6 nd reachable-time< milliseconds> This configures Reachable Time

field in RA message.
7 ZXR10(config-if-vlanX)#ipv6 nd retransmit-time < milliseconds> This configures Retransmit Timer

field in RA message
8 ZXR10(config-if-vlanX)#ipv6 nd suppress-ra This configures whether to send a

RA message or not
9 ZXR10(config-if-vlanX)#nd6 add < ipv6-address> < This adds a static entry to neighbor
hardware-address> cache table.
10 ZXR10(config-if-vlanX)#nd6 delete < ipv6-address> This deletes an entry in neighbor

cache table.
11 ZXR10#clear nd-cache [ interface] This clears entries in neighbor cache

table.
3.3 IPv6 NDP Configuration Example

This shows how to configure NDP on switch.
ZXR10(config-if-vlan11)#ipv6 address 8245::202/64
ZXR10(config-if-vlan11)#nd6 add 2003::200 00d0.d0c7.d0d0
3.4 IPv6 NDP Maintenance and Diagnosis

Command Function
ZXR10#show nd6 cache This views neighbor cache.
ZXR10#debug ipv6 nd This views NDP packets.
3-4

Chapter 4
IPv6 Tunnel Configuration
Table of Contents
IPv6 Tunnel Overview ................................................................................................4-1
Configuring IPv6 Tunnel .............................................................................................4-3
Example of IPv6 Manually Configured Tunnel ............................................................4-3
IPv6 Tunnel Maintenance and Diagnosis....................................................................4-6
4.1 IPv6 Tunnel Overview

IPv6 Tunnel Overview
It is impossible for IPv6 to supersede IPv4 immediately. Therefore, they will simultaneously
exist in the same environment for quite a long time. A good transition mechanism is needed
to provide a stable transition and minimize the effects on the existing users.
At present, this topic is the main target of the IETF NGTRANS work group. Many transition
mechanisms have been put forward and some of them have been used for 6Bone. IETF
recommends transition mechanisms such as tunnel technology, Dual Protocol Stack and
network address translation.
IPv6 tunnel technology encapsulates IPv6 packets in IPv4 packets, so IPv6 packets can
be transmitted in IPv4 core network.
IPv6 tunnel has the following common modes:
l IPv6 manually configured tunnel
l Automatic 6to4 tunnel
l Automatic IPv4 compatible tunnel
IPv6 Manually Configured Tunnel

Configuring a tunnel manually is equivalent to configuring a permanent tunnel through an
IPv4 network between two IPv6 networks. It is to provide a stable connection for the two
IPv6 networks at both sides of the tunnel.
To implement this purpose, configure IPv6 address, tunnel source IPv4 address and tunnel
destination IPv4 address on a tunnel interface manually.
Routers or hosts at both sides of the tunnel should support dual protocol stack.
Automatic 6to4 Tunnel

Automatic 6to4 tunnel allows local IPv6 network to connect with a remote IPv6 network
through an IPv4 network.
4-1

An IPv6 manually configured tunnel is a point to point tunnel. While an automatic 6to4
tunnel is a point to multi-point tunnel. In an automatic 6to4 tunnel, an IPv4 network is
looked as a virtual NBMA network. Therefore, routers are not configured in couples. The
other end of the tunnel can be found through an IPv4 address in which an IPv6 address is
embedded in.
IPv6 address prefix of edge router begins with 2002::/16. Its format is shown in Figure 4-1.
This kind of IPv6 address is called 6to4 address for short.
Figure 4-1 6TO4 ADDRESS FORMAT
The IPv4 address in Figure 4-1 should be globally unique. This IPv4 address should be
configured on the interface of edge router that connects with IPv4 network.
Working flow of an automatic 6to4 tunnel is described as follows:
Figure 4-2 AUTOMATIC 6TO4 TUNNEL
As shown in Figure 4-2, R1 and R2 are at two sides of a 6to4 tunnel. 6to4 addresses are
configured on fei_1/2 of R1 and all hosts in site 1. Configure an IPv4 address on fei_1/1
of R1. Embed this IPv4 address in 6to4 addresses.
6to4 addresses are also configured on fei_1/2 of R2 and all hosts in site 2. Configure an
IPv4 address on fei_1/2 of R2. Embed this IPv4 address in 6to4 addresses.
When a host in site 1 visits a host in site 2, a message is transmitted to R1. R1 views the
destination of this message and finds that it is a 6to4 address. R1 obtains IPv4 address at
the other side of the tunnel from this 6to4 address. So R1 encapsulates this IPv6 message
in an IPv4 message. The destination address of this IPv4 message is the peer IPv4
address, that is, the address on fei_1/1 of R2. The source address of this IPv4 message
is the address on fei_1/1 of R1. The message is transmitted to R2. R2 dis-encapsulates
this message and sends the IPv6 message to destination host.
4-2

Chapter 4 IPv6 Tunnel Configuration
Automatic IPv4-Compatible Tunnel

Automatic IPv4-compatible tunnel uses IPv4-compatible IPv6 address. The high 96 bits
of IPv4-compatible IPv6 address are all 0. The low 32 bits are IPv4 addresses. Its format
is 0:0:0:0:0:0:A.B.C.D or ::A.B.C.D.
The IPv4 embedded in IPv6 address decides the destination of the tunnel. Hosts or routers
at both sides of the tunnel should support dual protocol stack.
4.2 Configuring IPv6 Tunnel

1 ZXR10(config)#interface tunnel< tunnel id> This creates a tunnel and enters

tunnel configuration mode.
2 ZXR10(config-tunnelX)#tunnel mode { ipv6ip| ipv6ip[ 6to4] } This configures tunnel mode.
3 ZXR10(config-tunnelX)#tunnel mode ipv6ip [ isatap] } This configures isatap tunnel.
4 ZXR10(config-tunnelX)#tunnel source ipv4 < ip address> This configures the source address
of the tunnel.
5 ZXR10(config-tunnelX)#tunnel destination This configures the destination

address of the tunnel.
4.3 Example of IPv6 Manually Configured Tunnel

1. Example 1:
Figure 4-3 IPv6 TUNNEL Configuration Example 1
As shown in Figure 4-3, R1 and R2 are dual protocol stack routers. PC1 and PC2 are
IPv6 hosts. Configure a manually configured tunnel between R1 and R2.
l IPv6 address on tunnel interface of R1 is 3000:1:1:1::12/64.
l IPv6 address on tunnel interface of R2 is 3000:1:1:1::128/64.
4-3

l IPv6 address of PC1 is 4000::1, and gateway address is 4000::128.

l IPv6 address of PC2 is 5000::1, and gateway address is 5000::128.
R1(config)#interface tunnel1
R1(config-tunnel1)#ipv6 enable
R1(config-tunnel1)#ipv6 address 3000:1:1:1::12/64
R1(config-tunnel1)#tunnel mode ipv6ip
R1(config-tunnel1)#tunnel source ipv4 31.1.1.1
R1(config-tunnel1)#tunnel destination ipv4 31.1.1.2
R1(config-tunnel1)#exit
R1(config)#int fei_1/1
R1(config-fei_1/1)#switchport access vlan 2
R1(config-fei_1/1)#exit
R1(config)#int vlan 2
R1(config-if-vlan2)#ip address 31.1.1.1 255.255.255.0
R1(config-if-vlan2)#exit
R1(config-if-vlan3)#ipv6 enable
R1(config-if-vlan3)#ipv6 address 4000::128/64
R1(config)#ipv6 route 5000::/64 tunnel1
R2(config-tunnel2)#ipv6 address 3000:1:1:1::128/64
R2(config-tunnel2)#tunnel mode ipv6ip
R2(config-tunnel2)#tunnel destination ipv4 31.1.1.1
R2(config)#interface fei_2/1
R2(config)#interface fei_2/2
R2(config-if-vlan3)#ipv6 address 5000::128/64
R2(config)#ipv route 4000::/64 tunnel2
4-4

Chapter 4 IPv6 Tunnel Configuration
2. Example 2:
Figure 4-4 IPv6 TUNNEL Configuration Example 2
As shown in Figure 4-4, R1 and R2 are dual protocol stack routers. PC1 and PC2 are
IPv6 hosts. Configure a manually configured tunnel between R1 and R2.
l 6to4 address of PC1 is 2002:1f01:0101:1::2/64, and gateway address is
2002:1f01:0101:1::1/64.
l 6to4 address of PC2 is 2002:1f01:0102:1::2/64, and gateway address is
2002:1f01:0102:1::1/64.
R1(config-tunnel1)#tunnel mode ipv6ip 6to4
R1(config-if-vlan3)#ipv6 address 2002:1f01:0101:1::1/64
R1(config-if-vlan3)#exit R2(config-tunnel2)#ipv6 enable
R2(config-tunnel2)#tunnel mode ipv6ip 6to4
4-5

R2(config-fei_1/2)#exit R2(config-if-vlan3)#ipv6 enable
R2(config-if-vlan3)#ipv6 address 2002:1f01:0102:1::1/64
4.4 IPv6 Tunnel Maintenance and Diagnosis

To configure IPv6 tunnel maintenance and diagnosis, perform the following steps.
1 ZXR10#show ipv6 interface tunnel< tunnel-number> [ brief] This views information of tunnel
interface.
2 ZXR10#debug ipv6 packet interface tunnel< tunnel-number> This views information of messages
that are sent and received on tunnel
interface.
4-6

Chapter 5
IPv6 Other Configurations
Table of Contents
Configuring IPv6 Static Route.....................................................................................5-1
Configuring IPv6 DHCP SNOOPING ..........................................................................5-1
Configuring DHCPv6 relay .........................................................................................5-3
Other Configuration Commands .................................................................................5-4
Maintenance and Diagnosis Commands ....................................................................5-4
Configuration Example ...............................................................................................5-5
5.1 Configuring IPv6 Static Route

To configure IPv6 static route, perform the following steps.
1 ZXR10(config)#ipv6 route < ipv6 destination prefix> { < ipv6 gateway This configures an IPv6 static route.
address> | loopback | null | supervlan | tunnel | vlan} [ < distance> ]
2 ZXR10(config)#show ipv6 route [ < ipv6 address> | < ipv6 prefix> | This views IPv6 routing table.
bgp | connected | database | isis | ospf | rip | static]
3 ZXR10(config)#show ipv6 route summary This views statistics information of

IPv6 routing table.
5.2 Configuring IPv6 DHCP SNOOPING

1. To use the ipv6 dhcp snooping enable command to enable dhcpv6 snooping function
at the configuration mode and use disable command to disable dhcpv6 snooping
function, perform the following commands.
Command Function
ZXR10(config)#ipv6 dhcp snooping enable This enables dhcpv6 snooping function

at the global configuration mode. This
command can create database for
dhcpv6 user by using the ipv6 dhcp
snooping vlan < 1-4094 > command
and the ipv6 dhcp snooping trust< if-id >
command and detect dhcpv6 message
legality.
5-1

Command Function
ZXR10(config)#ipv6 dhcp snooping disable This disables dhcpv6 snooping function.
2. To clear all dhcpv6 users at the specific interface, perform the following command.
Command Function
ZXR10(config)#ipv6 dhcp snooping clear [ interface-id] < interface-idr >physical interface such
as feigeismartgroup.
3. To bind dhcpv6 user information and create static database, perform the following
command. Use no command to release the binding.
Command Function
ZXR10(config)#ipv6 dhcp snooping bingding < mac> vlan < vlan> < ip < mac > user MAC address; < vlan > the
address> < interface-id> expiry < 60 ～ 2147483647> vlan that an user belongs to, the range
is 1~4096, < ip address > DHCP binding
IPv6 address; < interface-number >
physical interface such as fei, gei and
smartgroup.
ZXR10(config)#no ipv6 dhcp snooping binding < mac> vlan< vlan> < < vlan > the vlan that an user belongs
interface-id> to, the range is 1~4096, < ip address
> DHCP binding IPv6 address; <
interface-number > physical interface
such as fei, gei and smartgroup.
4. To limit global dhcpv6 user number , perform the following command.
Command Function
ZXR10(config)#ipv6 dhcp snooping quota < 1 ～ 2048> This limits global maximum user
number, the range of user number is <
1 2048 >.
5. To configure the interface as trust interface, perform the following commands.
Command Function
ZXR10(config)#ipv6 dhcp snooping trust Interface < interface-id> This configures the interface whose
interface number is < interface-id > as
trust interface.
ZXR10(config)#no ipv6 dhcp snooping trust Interface < interface-id> This cancels the trust interface.
6. To enable Vlan DHCP SNOOPING, perform the following commands.
Command Function
ZXR10(config)#ipv6 dhcp snooping vlan < 1 ～ 4094> This enables dhcpv6 snooping of vlan.
5-2

Chapter 5 IPv6 Other Configurations
Command Function
ZXR10(config)#no ipv6 dhcp snooping vlan < 1 ～ 4094> This disables dhcpv6 snooping of vlan.
7. To configure user quota at the interface, perform the following commands.
Command Function
ZXR10(config-if-vlanX)#ipv6 dhcp snooping quota < 1 ～ 2000> < 1-2000 > is quota number.
8. To configure trust interface at the interface, perform the following commands.
Command Function
ZXR10(config-if-vlanX)#ipv6 dhcp snooping trust This configures interface as trust

interface.
ZXR10(config-if-vlanX)#no ipv6 dhcp snooping trust This cancels trust interface.
9. To configure whether DHCPv6 SNOOPING inserts 82 option in the forwarding

DHCPv6 packet, perform the following command. By default, 82 option is not inserted.
Command Function
ZXR10(config)#ipv6 dhcp snooping information option This inserts 82 option.
ZXR10(config)#no ipv6 dhcp snooping information option This does not inserts 82 option.

Command Function
ZXR10(config)#ipv6 dhcp snooping information option18 This inserts 18 option.
ZXR10(config)#no ipv6 dhcp snooping information option18 This does not inserts 18 option.

Command Function
ZXR10(config)#ipv6 dhcp snooping information option37 This inserts 37 option.
ZXR10(config)#no ipv6 dhcp snooping information option37 This does not inserts 37 option.
5.3 Configuring DHCPv6 relay

DHCPv6 relay configuration includes the following commands:
5-3

1 ZXR10(config)#ipv6 dhcp [ enable | disable] This enable or disable DHCPv6

relay function at global configuration
mode.
2 ZXR10(config-if-vlanX)#ipv6 dhcp mode < relay> This configures dhcpv6 relay function
at the interface mode.
3 ZXR10(config-if-vlanX)#ipv6 dhcp relay destination < This configures relay forwarding

ipv6_address> [ interface] parameter at the interface mode.
4 ZXR10(config)#show ipv6 dhcp interface vlan < 1 ～ 4094> This views dhcpv6 interface
configuration.
5 ZXR10(config)#show ipv6 dhcp configure This views IPv6 DHCP global

configuration message.
5.4 Other Configuration Commands

Command Function
ZXR10(config-if-vlanX)#ipv6 mtu < bytes> This configures maximum transmission

unit (MTU) which sends IPv6 message
on the interface.
ZXR10(config-if-vlanX)#ipv6 dad-attemps < number> This configures the times of repeat

address detection on the interface.
ZXR10(config)#ipv6 acl { extended | standard } < access-list-name> This configures IPv6 acl rule.
ZXR10(config)#show ipv6 mtu This views route MTU cache table

information.
ZXR10(config)#show ipv6 acl This views ipv6 acl entry information.
5.5 Maintenance and Diagnosis Commands

For convenient maintenance and diagnosis, ZXR10 5900E provides the related
commands.
Command Function
ZXR10#ping6 < ipv6-addres> s [ interface { < interface-name> } | num < 1 ～ This diagnoses if the link to a specific
65535> | size < 64 ～ 8192> | timeout < 1 ～ 60> ] destination is normal.
ZXR10#trace6 < ipv6-address> [ max-ttl < 1 ～ 254> | timeout < 1 ～ 100> ] This diagnoses the real route to a
specific destination.
ZXR10#telnet6 < ipv6-address> [ interface < interface-name> ] This opens a IPv6 Telnet connection.
5-4

Chapter 5 IPv6 Other Configurations
Command Function
ZXR10#debug ipv6 icmp This views IPv6 ICMP message debug

information.
ZXR10#debug ipv6 packet This views IPv6 message information

which system receives and sends.
ZXR10#debug ipv6 tcp driver This sets and closes IPv6 TCP
connection related information debug
switch.
ZXR10#debug ipv6 tcp packet This views system receiving

and sending IPv6 TCP message
information.
ZXR10#debug ipv6 tcp transactions This sets debug switch of IPv6 TCP
status migration information.
ZXR10#debug ipv6 tcp all This opens all IPv6 TCP debug
information switch.
ZXR10#debug ipv6 udp This opens IPv6 UDP debug information

switch.
5.6 Configuration Example

This following shows the MTU configuration example.
ZXR10(config)#interface vlan1
The following example shows how to use the command of ping:

ZXR10#ping6 3ff::2
sending 64-bytes ICMP echos to 3ff::2,timeout is 1 seconds.
!!!!!
Success rate is 100 percent(5/5),round-trip min/avg/max= 0/1/9 ms
The following example shows how to use the command of show ipv6 route:
ZXR10#show ipv6 route summary

IPv6 Routing Table Summary - 13 entries
3 connected, 1 static, 0 RIP, 0 BGP, 4 IS-IS, 5 OSPF
ZXR10#show ipv6 route isis

IPv6 Routing Table
Codes: C - connected, S - static, R - RIP, B - BGP,
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
Timers: Uptime
5-5

DHCPv6 relay configuration example is showed as the follows.

When DHCPv6 client terminal and server are not in the same network, the router which
connects the client terminal directly is needed to be DHCPv6 relay.
As shown in Figure 5-1, enable DHCPv6 relay in R1, the single server 101:: 1/64 provides
DHCPv6 server function.
Figure 5-1 DHCPv6 Relay Configuration Example
R1 configuration is as follows
ZXR10(config)#interface vlan10
ZXR10(config-if-vlan10)#ipv6 dhcp mode relay
ZXR10(config-if-vlan10)# ipv6 dhcp relay destination 101::1
ZXR10(config-if-vlan10)# ipv6 enable
ZXR10(config-if-vlan10)# ipv6 address 2009:1::3/64
ZXR10(config-if-vlan10)#exit
ZXR10(config)#ipv6 dhcp enable
5-6

Chapter 6
RIPng Configuration
Table of Contents
RIPng Overview .........................................................................................................6-1
Configuring RIPng ......................................................................................................6-3
RIPng Configuration Example ....................................................................................6-4
RIPng Maintenance and Diagnosis.............................................................................6-4
6.1 RIPng Overview

As a mature route standard,RIP is widely applied in Internet, especially in some small and
medium-sized networks. Considering this situation and the compatibility between RIP and
IPv6, IETF alters the existing technology and sets the RIP standard under IPv6, namely,
RIPng .
As a UDP-based protocol, RIPng sends and receives packet through Port 521. Generally,
RIPng messages are classified into two categories: request message and update
message.
RIPng is not intended to create a completely new protocol. It is to make necessary

alternation to RIP, enabling it to adapt to the routing requirements under IPv6. Therefore,
RIPng has the same working principle with RIP, except for changes in address and
message format.
l Address version
Both RIPv1 and RIPv2 are based on IPv4 and their address domain is 32-bit. RIPng
is based on IPv6 and all the applied addresses are 128-bit.
l Subnet mask and prefix length
RIPv1 is designed as a network without subnets, so there is no concept of subnet
mask. In this way, RIPv1 cannot be used for propagation of extended subnet
addresses or for CIDR classless addresses. Function of supporting subnet routing is
added to RIPv2, so RIPv2 can use subnet masks to distinguish network routes and
subnet routes.
As IPv6 address prefixes have explicit meanings, RIPng does not have subnet masks
any more but has prefix length. Similarly, due to application of IPv6 addresses, it is
not necessary to distinguish network routes, subnet routes and host routes in RIPng.
l Scope of application
Scope of application for RIPv1 and RIPv2 is designed to adapt to both TCP/IP suite
and other network protocol suites. Therefore, routing table entries of a packet contain
6-1

network protocol suite fields. However, the realization program is seldom used for
other non-IP networks in practice. Therefore, support to this function is removed from
RIPng.
l Next hop indication
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 next hop, thus facilitating selection
of the optimum route and avoiding routing loop and slow convergence.
Different from RIPv1 and RIPv2, the next hop fields in RIPng exist as separate RTEs to
avoid overlong Routing table Entry (RTE) and to improve efficiency in route information
transmission.
l Packet length
Both RIPv1 and RIPv2 set limit to the length of a packet, provisioning that each packet
can only carry at most 25 RTEs.
However, RIPng has no limit on the length of a packet and number of RTEs. The
length of a packet depends on the MTU of a medium. Processing on the packet length
by RIPng enables networks to improve efficiency in route information transmission.
l Security consideration
RIPv1 packets contain no authentication information, which results in insecurity. Any
host that sends packets through the UDP Port 520 will be regarded as a router by its
neighbor host, which is likely to cause router spoofing.
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 route information through broadcast. In this way, both routers and all the
hosts within the same 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 quantity of route information that is
transmitted in networks.
6-2

Chapter 6 RIPng Configuration
6.2 Configuring RIPng

6.2.1 Configuring Basic RIPng
1 ZXR10(config)#ipv6 router rip This enables a RIPng instance.
2 ZXR10(config-if-vlanX)#ipv6 rip active-interface This configures one interface

sending packet only.
3 ZXR10(config-if-vlanX)#ipv6 rip enable This enables RIPng on an interface.
4 ZXR10(config-if-vlanX)#ipv6 rip neighbor X:X::X:X This configures the IP address of

RIPng neighbor.
5 ZXR10(config-if-vlanX)#ipv6 rip originate-default-route [ only] This configures the default route of

RIPng.
6 ZXR10(config-if-vlanX)#ipv6 rip passive-interface This makes an interface receiving

messages only.
7 ZXR10(config-if-vlanX)#ipv6 rip poison-reverse This configures poison-reverse

function.
8 ZXR10(config-if-vlanX)#ipv6 rip split-horizon This configures split-horizon

function.
6.2.2 Configuring RIPng Enhanced Function

To configure RIPng enhanced function, perform the following steps.
1 ZXR10(config-router)#timers basic < update> < timeout> < This configures RIPng timers.
garbage>
2 ZXR10(config-router)#redistribute < protocol> [ { metric < 1-16> } This redistributes routes to RIPng.
| { route-map < name> } ]
3 ZXR10(config-router)#summary-prefix X:X::X:X/< 0-128> This configures route aggregation.
4 ZXR10#clear ipv6 rip route [ X:X::X:X/< 0-128> | all] This deletes RIPng routes.
6-3

6.3 RIPng Configuration Example

Figure 6-1 EXAMPLE OF CONFIGURING RIPNG
As shown in Figure 6-1 , R1 and R2 run RIPng.

Configuration on R1:
ZXR10_R1(config)#ipv6 router rip
ZXR10_R1(config-router)#exit
ZXR10_R1(config)#interface vlan4
ZXR10_R1(config-if-vlan4)#ipv6 enable
ZXR10_R1(config-if-vlan4)#ipv6 address 2001::1/64
ZXR10_R1(config-if-vlan4)#ipv6 rip enable
ZXR10_R1(config-if-vlan4)#exit
ZXR10_R2(config)#ipv6 router rip
6.4 RIPng Maintenance and Diagnosis

To configure RIPng maintenance and diagnosis, perform the following steps.
1 ZXR10#show ipv6 rip This views information of RIPng

protocol.
6-4

Chapter 6 RIPng Configuration
2 ZXR10#show ipv6 rip interface < ifname> This views RIPng information on an
interface.
3 ZXR10#show ipv6 rip database This views information of RIPng

routing database.
4 ZXR10#debug ipv6 rip This traces RIPng running

information.
6-5

6-6

Chapter 7
OSPFv3 Configuration
Table of Contents
OSPFv3 Overview......................................................................................................7-1
Configuring OSPFv3 ..................................................................................................7-4
OSPFv3 Configuration Example .................................................................................7-6
OSPFv3 Maintenance and Diagnosis .........................................................................7-6
7.1 OSPFv3 Overview

IPv6 OSPF protocol reserves most of the IPv4 algorithm, that is, from IPv4 to IPv6, the
essential OSPF mechanism remains unchanged.
Both IPv6 and IPv4 contain link state databases. The link state advertisement (LSA) is
contained in link state databases and such information in the adjacent routers should be
kept synchronous.
Initial database synchronization is implemented through the database exchange process,
which includes exchanging database description packets, link state enquiry packets
and link state update packets. The subsequent database synchronization is maintained
through flooding with link state update messages and link state confirmation messages.
In broadcast and non-broadcast multicast access (NBMA) networks, both OSPFv2 and
OSPFv3 use hello message to discover and maintain adjacency relation, elect assigned
routers and back up assigned routers. OSPFv2 and OSPFv3 also keep consistent with
each other in such aspects as neighbor determination, basic concept of inter-area routes,
introduction of AS external LSA information and different route calculation.
7.1.1 Differences between OSPFv3 and OSPFv2

As OSPFv3 is based on IPv6, OSPFv3 and OSPFv2 have many differences.
l OSPFv3 topology is based on link, while OSPFv2 topology is based on subnet.
IPv6 uses the term of 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 a same link. Two nodes in different IP subnets can
communicate with each other directly over a single link.
l OSPFv3 Deletes address semantic.
OSPF message contains no IPv6 address except for LSA net load carried by the
update message in the link state.
7-1

Router LSA and network LSA do not contain network addresses any longer and only
indicate topology information simply.
OSPF router ID and the LSA link state ID are reserved to be the IPv4 32-bit, without
allocation of IPv6 addresses any more.
l OSPFv3 Expands flooding range.
LS fields of LSA reflect flooding ranges. LSA features the following three flooding
ranges:
à Link-local range: This LSA is only flooded in local links. This range is applicable
to link LSA.
à Area range: This LSA is only flooded in a single OSPF area. This range is
applicable to router LSA, network LSA, inter-area prefix LSA, inter-area router
LSA and intra-area prefix LSA.
à Autonomous area range: This LSA is flooded in route area. This is applicable to
the AS external LSA.
Each link supports multiple instances. OSPF supports running multiple OSPF protocol
instances over a single link.
l OSPFv3 uses link-local address.

IPv6 link-local addresses are used for neighbor discovery and automatic configuration
over a single link. IPv6 routers do not transmit IPv6 packets containing link local
source addresses. IPv6 address range that is allocated to link-local unicast addresses
is FE80/10.
Except for all OSPF interfaces in the virtual link, link-local addresses related to
interfaces can send OSPF packets as source addresses. On virtual link, only global
address and site-local address can serve as the source address.
Link-local addresses can be used in link LSA, but can not be used in other LSA types.
l Authentication format is changed in OSPFv3.

Authentication type and authentication field are deleted from IPv6 OSPF header. All
authentication-related fields do not appear in OSPF area data structure and interface
data structure. IPv6 OSPF uses mechanism that is supported by it self to provide
security protection to integrity and confidentiality.
l Message format is changed in OSPFv3.
OSPFv3 runs over IPv6 directly. Address semantic is not contained in OSPF header
but in different LSA types. Therefore, IPv6 OSPF is independent of network protocols.
Changes of OSPF packet format are described as follows:
à Version increases from 2 to 3.

à Optional fields of Hello message and database description message expands to
24 bits.
à Authentication and authentication type fields are deleted from OSPF header.
7-2

Chapter 7 OSPFv3 Configuration
à Hello message does not contain address semantics. It contains an interface ID

that is used to identify the links on this router. If the router becomes the DR on
the link, the interface ID will be the link state ID of the network LSA.
à To process router LSAs during SPF calculation, two option flag fields of R and V6
are added to option field. OSPF header contains an Instance ID, which allows
running multiple OSPF protocol instances over a single link.
l LSA format is changed in OSPFv3.
All address semantics are deleted from LSA header, router LSA and network
LSA. Router LSA and network LSA describe the topology of routing area in a way
independent of network protocols. New LSA that is used to allocate IPv6 address
information and the data that is required for next hop resolution are added.
Type-3 LSA is renamed intra-area prefix LSA and Type-4 LSA is renamed intra-area
router LSA.
l OSPFv3 and OSPFv2 process unknown types of LSAs differently.
In OSPFv3, unknown types of LSAs can be regarded as having link-local flooding
range, or be regarded as the known LSA type to be saved and flooded. IPv4 OSPF
discards unknown types of LSAs.
l OSPFv3 supports stub area.
In OSPFv3, routers in stub area can only process router LSA, network LSA and
intra-area prefix LSA. These routers allow unknown types of LSAs to be saved and
flooded as known LSAs.
l In OSPFv3, router uses router ID identify neighbor.
In OSPFv3, neighbor routers on a designated link are identified by router IDs. In IPv4
OSPF, neighbors on point-to-point networks and virtual links are identified by their
router IDs. Neighbors on broadcast, NBMA and point-to-multipoint links are identified
by interface ID.
7.1.2 LSA Types

An LSA is the basic unit of OSPFv3 link state database. Routers use LSAs to sets up a
complete network topology and generate a routing table. OSPFv3 has the following types
of LSAs:
l Router LSA
The LS type of this LSA is 0x2001. It can generate one or multiple LSAs on each
router within an area.
l Network LSA
The LS type of this LSA 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 DRs.
l Inter-area prefix LSA
7-3

The LS type of this LSA is 0x2003. It is equivalent to Type-3 LSA in OSPFv2.

Inter-area prefix LSAs are created by border routers. Intra-area prefix router LSA
describes routes to IPv6 address prefixes in other areas. For stub areas, inter-area
prefix LSA is also used to describe default routes.
l Inter-area router LSA
The LS type for this LSA is 0x2004. It is equivalent to Type-4 LSA in OSPFv2.
Inter-area router LSA is created by area border routers. It describes routes to routers
in other areas.
l AS external LSA
The LS type of this LSA is 0x4005. It is created by AS border routers. It describes

routes to destinations outside the AS.
l Link LSA
The LS type of this LSA is 0x0008. A router initiates separate link LSA to each link
that connects with it. These LSAs have link-local flooding ranges and are not flooded
out of the related links.
l Intra-area prefix LSA
The LS type of this LSA is 0x2009. A router uses this LSA to advertise one or multiple
IPv6 address prefixes. These prefixes are related to the router itself, the connected
stub network segment and the connected Transit network segment.
7.2 Configuring OSPFv3

7.2.1 Enabling OSPFv3
To enable OSPFv3, perform the following steps.
1 ZXR10(config)#ipv6 router ospf < process-id> This enables OSPFv3 process.
2 ZXR10(config-router)#router-id < router-id> This specifies a Router ID of an

instance.
3 ZXR10(config)#interface < interface-name> This enters Layer 3 interface

configuration mode.
4 ZXR10(config-if-vlanX)#ipv6 ospf < process-id> area < area-id> This enables OSPFv3 on an
[ instance-id < 0-255> ] interface.
7.2.2 Configuring OSPFv3 Interface Parameters

To configure interface attributes, perform the following steps.
7-4


configuration mode.
2 ZXR10(config-if-vlanX)#ipv6 ospf hello-interval < interval> [ This sets Hello message interval.
instance-id < 0-255> ]
3 ZXR10(config-if-vlanX)#ipv6 ospf retransmit-interval < interval> This sets LSA retransmission interval
[ instance-id < 0-255> ] on an interface.
4 ZXR10(config-if-vlanX)#ipv6 ospf transmit-delay < interval> [ This sets time delay of sending a
instance-id < 0-255> ] link state update message on an
interface.
5 ZXR10(config-if-vlanX)#ipv6 ospf dead-interval < interval> [ This sets aging time of a neighbor.
instance-id < 0-255> ]
6 ZXR10(config-if-vlanX)#ipv6 ospf cost < cost-value> [ instance-id This sets interface cost.
< 0-255> ]
7 ZXR10(config-if-vlanX)#ipv6 ospf priority < value> [ instance-id This sets interface priority.
< 0-255> ]
7.2.3 Configuring OSPFv3 Protocol Parameters

To configure protocol attributes, perform the following steps.
1 ZXR10(config-router)#area < area-id> default-cost < cost-value> This configures default cost in an
area.
2 ZXR10(config-router)#area < area-id> range { X:X::X:X/< 0-128> } This configures address aggregation
[ advertise| not-advertise] range in an area.
3 ZXR10(config-router)#area < area-id> stub [ no-summary] This configures an area to a stub

area.
4 ZXR10(config-router)#area < area-id> virtual-link < router-id> This defines a virtual link.
[ hello-interval < seconds> ] [ retransmit-interval < seconds> ] [
transmit-delay < seconds> ] [ dead-interval < seconds> ]
5 ZXR10(config-router)#default-metric < metric-value> This configures default metric of

redistributed routes.
6 ZXR10(config-router)#passive-interface < ifname> This forbids OSPFv3 interface to

transmit OSPFv3 messages.
7 ZXR10(config-router)#redistribute < protocol> [ metric < This redistributes other routes to

metric-value> ] [ metric-type < type> ] [ route-map < name> ] OSPFv3.
8 ZXR10(config-router)#timers spf < delay> < holdtime> This sets route recalculation interval
of OSPFv3.
7-5

7.3 OSPFv3 Configuration Example

As shown in Figure 7-1 , R1 and R2 run OSPFv3. The network is divided into three areas.
Figure 7-1 OSPFv3 Configuration Example
ZXR10_R1(config)#ipv6 router ospf 1
ZXR10_R1(config-router)# router-id 1.1.1.1
ZXR10_R1(config-router)# exit
ZXR10_R1(config-if-vlan4)#ipv6 ospf 1 area 23
ZXR10_R2(config-router)# router-id 2.2.2.2
ZXR10_R2(config-router)# exit
ZXR10_R2((config-if-vlan6)#ipv6 ospf 1 area 24
7.4 OSPFv3 Maintenance and Diagnosis

To configure OSPFv3 maintenance and diagnosis, perform the following steps.
1 ZXR10#show ipv6 ospf < tag> This views OSPFv3 instance

information.
7-6

2 ZXR10#show ipv6 ospf database This views database information of

an OSPFv3 instance.
3 ZXR10#show ipv6 ospf interface [ < ifname> ] This views interface information of
an OSPFv3 instance.
4 ZXR10#show ipv6 ospf neighbor This views neighbor information of

an OSPFv3 instance.
5 ZXR10#show ipv6 route ospf This views routes of an OSPFv3

instance.
6 ZXR10#show ipv6 ospf virtual-links This views virtual link information of

an OSPFv3 instance.
7 ZXR10#debug ipv6 ospf adj This traces adjacency information.
8 ZXR10#debug ipv6 ospf lsa-generation This traces LSA information.
9 ZXR10#debug ipv6 ospf packet This traces receiving messages and

sending messages.
7-7

7-8

Chapter 8
IS-ISv6 Configuration
Table of Contents
IS-ISv6 Overview .......................................................................................................8-1
Configuring IS-ISv6 ....................................................................................................8-1
IS-ISv6 Configuration Example...................................................................................8-4
IS-ISv6 Maintenance and Diagnosis ...........................................................................8-9
8.1 IS-ISv6 Overview

IS-IS has an early development. ISO 10589 and RFC1195 define how to use IS-IS as
a link state routing protocol to provide service to TCP/IP. The subsequent specifications
perfect IS-IS protocol gradually. The latest draft defines how to use IS-IS to support IPv6.
IS-IS is a routing protocol with high expansibility, so it can support CLNS routing protocol
expanding to support IPv4 and IPv6.
The draft-ietf-isis-IPv6-05.txt (Routing IPv6 with IS-IS) draft defines two new TLVs: IPv6
Reachability and IPv6 Interface Address.
l TLV type value of IPv6 Reachability TLV is 236(0xEC). Its TLV effects are equal to
two IPv4 TLVs: IP internally reachable and IP externally reachable. Up/down and
external are defined in this TLV. They are used to indicate that routes are redistributed
mutually in L2/L1. They also determine whether a route is an external route.
l TLV type value of IPv6 Interface Address TLV is 232(0xE8). Its TLV effects are equal
to TLV of IPv4: IP port address. The difference is that the original 32-bit address
segment is superseded by 128-bit address segment in the new TLV.
The uni-topology IS-IS can only run a single SPF algorithm. Then, 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 some flexibility.
8.2 Configuring IS-ISv6

8.2.1 Enabling IS-ISv6
To enable IS-ISv6 process, perform the following steps.
1 ZXR10(config)#router isis This initializes an IS-IS routing entry.
8-1

2 ZXR10(config-router)#area < area address> This configures IS-ISv6 area

address.
3 ZXR10(config-router)#system-id < id> This configures system ID of an

IS-IS routing entry.

configuration mode.
5 ZXR10(config-if-vlanX)#ipv6 router isis This runs IS-ISv6 on an interface.
8.2.2 Configuring IS-ISv6 Global Parameters

To configure global parameters, perform the following steps.
1 ZXR10(config-router)#address-family ipv6 This enters into ipv6 family

configuration mode.
2 ZXR10(config-router)#authentication < word> This configures password.
3 ZXR10(config-router)#authentication-type { md5 | text} [ level-1 | This configures IS-ISv6

level-2] authentication type.
4 ZXR10(config-router)#disable-snp-authentication This disables SNP authentication.
5 ZXR10(config-router)#distance < 1-255> This configures administrative

distance of IS-ISv6.
6 ZXR10(config-router)#enable-snp-authentication This enables SNP authentication.
7 ZXR10(config-router)#hello padding This configures sending hello

message padding on the interface till
the message size is equal to mtu of
interface.
8 ZXR10(config-router)#ignore-lsp-errors This configures IS-ISv6 ignore LSP

error.
9 ZXR10(config-router)#is-type { level-1 | level-2-only | level-1-2} This configures route level.
10 ZXR10(config-router)#lsp-refresh-time < 1-65535> This configures LSP refresh time.
11 ZXR10(config-router)#maximum-paths < 1-8> This configures maximum

route number at IS-ISv6 route
configuration mode.
12 ZXR10(config-router)#max-lsp-lifetime < 1-65535> This configures LSP lifetime.
13 ZXR10(config-router)#lsp-mtu < 512-1497> This configures LSP mtu.
8-2

Chapter 8 IS-ISv6 Configuration
14 ZXR10(config-router)#metric-style { narrow | wide} [ level-1 | This configures metric type of router.

level-2 | level-1-2]
15 ZXR10(config-router)#redistribute { { bgp | connected | ospf | rip | This configures route redistribution

static} [ [ level-1 | level-2 | level-1-2] | metric < 0-4261412864> | } from other route protocols, static
route and direct connected route.
16 ZXR10(config-router)#set-overload-bit [ suppress { external [ This sets overload-bit in its own LSP

interlevel] | interlevel [ external] } | on-startup < 5-86400> [ suppress { message.
external [ interlevel] | interlevel [ external] } ] ]
17 ZXR10(config-router)#spf-interval < 1-120> [ level-1 | level-2] This configures the minimum interval
that configures IS-ISv6 topology.
18 ZXR10(config-router-af)#summary-prefix X:X::X:X/< 0-128> [ This configures IS-ISv6 route

level-1 | level-1-2 | level-2 ] aggregation.
8.2.3 Configuring IS-ISv6 Interface Parameters

To configure interface parameters, perform the following steps.
1 ZXR10(config-if-vlanX)#isis authentication < word> [ level-1 | This configures IS-ISv6

level-2] authentication on the interface.
2 ZXR10(config-if-vlanX)#isis authentication-type { md5 | text} [ This configures IS-ISv6

level-1 | level-2] authentication type on the interface.
3 ZXR10(config-if-vlanX)#isis circuit-type { level-1 | level-1-2 | This configures IS-ISv6 circuit-type

level-2-only} on interface.
4 ZXR10(config-if-vlanX)#isis csnp-interval < 1-65535> [ level-1 | This configures CSNP sending

level-2] interval on an interface.
5 ZXR10(config-if-vlanX)#isis hello-interval < 1-65535> [ level-1 | This configures Hello message

level-2] interval on an interval.
6 ZXR10(config-if-vlanX)#isis hello-multipiler < 3-1000> [ level-1 | This configures multiplier for Hello
level-2] holding time.
7 ZXR10(config-if-vlanX)#isis ignore-mtu This configures ignore-mtu.
8 ZXR10(config-if-vlanX)#isis lsp-interval < 1-65535> [ level-1 | This configures LSP transmission

level-2] interval on an interface.
9 ZXR10(config-if-vlanX)#isis max-burst < 1-65535> This configures the number that LSP
sends each time.
10 ZXR10(config-if-vlanX)#isis metric < 0-16777214> [ level-1 | This configures metric on interface.

level-2]
8-3

11 ZXR10(config-if-vlanX)#isis priority < 0-127> [ level-1 | level-2] This configures IS-ISv6 priority on
interface.
12 ZXR10(config-if-vlanX)#isis psnp-interval < 1-65535> [ level-1 | This configures IS-ISv6 sending

level-2] psnp interval on the interface.
8.3 IS-ISv6 Configuration Example

8.3.1 Single Area IS-ISv6 Configuration Example
Analyze the entire network before configuring IS-ISv6, and then design the network
topology according to the network size, whether dividing multiple areas is needed,
whether multiple routing protocols are running in the network. The following illustrates the
basic configuration of IS-IS protocol taking single-area network as an example, as shown
in Figure 8-1 .
Figure 8-1 Single Area IS-ISv6 Configuration Example
R1 and R2 form area 1, running IS-ISv6 protocol.

ZXR10_R1(config)#router isis
ZXR10_R1(config-router)#area 01
ZXR10_R1(config-router)#system-id 00D0.D0C7.53E0
ZXR10_R1(config-if-vlan4)#ipv6 router isis
8-4

ZXR10_R2(config-router)#system-id 00D0.D0C7.5460
8.3.2 Multi-Area IS-ISv6 Configuration Example

When network is vast, use multiple areas in the IS-ISv6. Divide the similar routers into
the same area according to the zone and functionality. Partition of area reduces memory
requirement. It makes the router in an area maintain relatively smaller link state database.
As shown in Figure 8-2, R1 belongs to area 1. R2, R3 and R4 belong to area 0. R5 and
R6 belong to area 3. On R1, implement route aggregation to network segment in area 1.
On R6, redistribute the static route to IS-ISv6.
Figure 8-2 Multi-Area IS-ISv6 Configuration Example
ZXR10_R1(config-router)#system-id 00D0.D0C7.53E0
ZXR10_R1(config-router)#is-type LEVEL-1-2
8-5

ZXR10_R1(config-if-vlan4)#isis circuit-type LEVEL-2-only
ZXR10_R1(config-if-vlan6)#ipv6 address 2001:1::1/64
ZXR10_R1(config-if-vlan6)#isis circuit-type LEVEL-1
ZXR10_R1(config-router)#address-family ipv6
ZXR10_R1(config-router-af)# summary-prefix 2001::/16
ZXR10_R2(config-router)#system-id 00D0.E0D7.53E0
ZXR10_R2(config-router)#is-type LEVEL-2-only
8-6


ZXR10_R3(config-router)#system-id 00D0.E0C7.53E0
ZXR10_R4(config-router)#system-id 00D0.E0E7.53E0
8-7


ZXR10_R5(config-router)#system-id 00D0.D0CF.53E0
ZXR10_R5(config-router)#is-type LEVEL-1-2
ZXR10_R6(config-router)#system-id 00D0.0ECD.53E0
ZXR10_R6(config-router)#is-type LEVEL-1
ZXR10_R6(config-if-vlan4)#ipv6 address 2007：：6/64
8-8

ZXR10_R6(config-if-vlan8)#ipv6 address 2008：：6/64
ZXR10_R6(config)# ipv6 route 2009::/64 2008::10
ZXR10_R6(config-router)# address-family ipv6
ZXR10_R6(config-router-af)# redistribute static level-1
ZXR10_R6(config-router)#end
ZXR10_R6#
8.4 IS-ISv6 Maintenance and Diagnosis

To configure IS-ISv6 maintenance and diagnosis, perform the following steps.
1 ZXR10#show isis adjacency This views IS-ISv6 adjacency

information
2 ZXR10#show isis database This views IS-ISv6 database
3 ZXR10#show isis circuits This views interface information
4 ZXR10#show ipv6 route isis This views IS-ISv6 routing table
5 ZXR10#show isis topology This views IS-ISv6 topology
6 ZXR10#debug isis all This traces all IS-ISv6 information
7 ZXR10#debug isis update-packets This traces IS-ISv6 update

information
8 ZXR10#debug isis adj-packets This traces IS-ISv6 adjacency

information
9 ZXR10#debug isis spf-events This traces IS-ISv6 route calculation

events
10 ZXR10#debug isis snp-packets This traces IS-ISv6 SNP information
8-9

8-10

Chapter 9
BGP4+ Configuration
Table of Contents
BGP4+ Overview........................................................................................................9-1
Configuring BGP4+ ....................................................................................................9-1
BGP4+ Configuration Example...................................................................................9-8
BGP4+ Maintenance and Diagnosis .........................................................................9-10
9.1 BGP4+ Overview

BGP4 multi-protocol extension, namely BGP4+, is specified to enable the BGP4 to support
multiple network layer protocols such as IPv6 and IPX.
To make BGP4 protocol support multiple network layer protocols to select routes, the
following functions must be added to it:
l The information newly added to BGP4 must make a specific network layer protocol
associated with the next hop information. That is, the address of the next hop should
be indicated by a designated network layer protocol address.
l BGP4 protocol should be able to enable a specific protocol associated with the NLRI,
and employ address family to distinguish various network layer protocols.
BGP4+ defined two attributes MP_REACH_NLRI and MP_UNREACH_NLRI BGP. They
are used to transmit IPv6 routing information. Similar to common distance vector routing
protocols, BGP4 protocol is usually independent of specific address family used by the
protocol.
IPv6 protocol is supported by BGP4. IPv6 introduces area-based unicast addresses and
defines the specific situations where specific address ranges must be applied. That is the
fundamental difference between IPv6 and IPv4 protocols in route information.
9.2 Configuring BGP4+

9.2.1 Enabling BGP4+
1 ZXR10(config)#router bgp < as-number> This enables BGP4+ process.
2 ZXR10(config-router)#neighbor < ipv6-address> remote-as < This configures IPv6 neighbor.

number>
9-1

3 ZXR10(config-router-af)#network < ipv6-address> /< This advertises routes.

prefix-length>
Example
Figure 9-1shows an example of configuring basic BGP4+. R1 is in AS100, and R2 is in
AS200.
Figure 9-1 Basic BGP4+ Configuration Example
ZXR10_R1(config)#router bgp 100
ZXR10_R1(config-router)#neighbor 2005::2 remote-as 200
ZXR10_R1(config-router-af)#neighbor 2005::2 activate
ZXR10_R1(config-router-af)#network 2001::/64
ZXR10_R2(config-router-af)#neighbor 2005::1 activate
ZXR10_R2(config-router-af)#network 2003::/64
In this example, R1 and R2 define the peer as neighbor. As they are in different
autonomous systems, they establish an EBGP connection.
R1 advertises network 2001::/64, and R2 advertises network 2003::/64.
9.2.2 Configuring BGP4+ Route Advertisement

To configure BGP4+ route advertisement, use one of the following commands.
Command Function
ZXR10(config-router)#network < ipv6 network number> [ route-map < This advertises known routes on local
name> ] device
ZXR10(config-router)#redistribute < protocol> [ metric < metric-value> ] This redistributes routes learnt by IGP
[ route-map < map-tag> ] protocols
9-2

Chapter 9 BGP4+ Configuration
Note:
Known routes on local device include direct-connected route, static route and the route learnt through
dynamic routing protocols.
Redistribute command is used to redistribute routes learnt by IGP protocols (RIPng, OSPFv3 and
IS-ISv6) into BGP4+. When using this command, make sure that the routes learned by IGP from
BGP4+ are not redistributed into BGP4+. Use the filtering command to prevent the loop from occurring
if necessary.
9.2.3 Configuring EBGP Multi-Hops of BGP4+

To configure EBGP multi-hops of BGP4+, use the following command.
Command Function
ZXR10(config-router)#neighbor < ipv6-address> ebgp-multihop [ ttl < This configures EBGP multi-hops of
value> ] BGP4+
Note:
EBGP neighbors should be established on the straight-through interfaces of two routers. To estab-
lish EBGP neighbors on the interfaces that are not directly connected, use this command to configure
EBGP multi-hops. In addition, appropriate IGP or static route configuration is required to enable the
inter-working of these neighbors.
R1 needs to establish the neighbor relation with the interface with the IP address
2003::2/64 on R2, to which R1 is not connected directly, as shown in Figure 9-2.
Figure 9-2 EBGP Multi-Hops Configuration Example

ZXR10_R1(config-router)#neighbor 2003::2 ebgp-multihop
ZXR10_R2(config-router)#neighbor 2005：：1 remote-as 100
9-3

9.2.4 Configuring BGP4+ Route Reflector

For the BGP routers within the same AS, the neighbor relation should be established
between every two routers to enable an overall interconnection. In this way, the number of
neighbors increases to n*(n-1)/2 (“n” is the number of IBGP routers). Route reflector and
confederation are used to reduce the workload of maintenance and configuration.
For IBGP speaking routers within an AS, one of them is selected to be the route reflector
(RR). All the other IBGP routers act as clients and establish neighbor relation only with the
RR. All the clients reflect routes by RR. This reduces the number of neighbors to n-1.
When a route is received by the RR, it is reflected depending on the type of peer.
l A route from a Non-Client peer is reflected to all Client peers.
l A route from a Client peer is reflected to all Non-Client peers and Client peers.
l A route from an EBGP peer is reflected to all Non-Client peers and Client peers.
When there are multiple RRs in an AS, these RRs can be grouped into a cluster. An AS
can include multi clusters. A cluster includes more than one RR at least.
To configure BGP4+ route reflector, perform the following steps.
1 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This configures a router as a RR

peer-group-name> } route-reflector-client client.
2 ZXR10(config-router)#bgp client-to-client reflection This configures client-to-client

reflection.
3 ZXR10(config-router)#bgp cluster-id { < value> | < ip-address> } This configures the ID of RR cluster.
Example
R3 and R4 are two route reflectors in AS100. The clients of R4 are R5 and R6. The clients
of R3 are R1 and R2. Network topology is shown in Figure 9-3.
9-4

Figure 9-3 BGP4+ Route Reflector Configuration Example
ZXR10_R3(config-router)#bgp router-id 3.3.3.3
ZXR10_R3(config-router)#neighbor 3ffe::1 remote-as 100
ZXR10_R3 (config-router)#address-family ipv6
ZXR10_R3 (config-router-af)#neighbor 3ffe::1 activate
ZXR10_R3 (config-router-af)#neighbor 3ffe::2 activate
ZXR10_R3 (config-router-af)#neighbor 3ffe::1
route-reflector-client
ZXR10_R3 (config-router-af)#neighbor 3ffe::2
route-reflector-client

ZXR10_R2(config-router)#bgp route-id 2.2.2.2
ZXR10_R2(config-router-af)#neighbor 3ffe::3 activate
9-5

9.2.5 Configuring BGP4+ Confederation

Route confederation has the similar function as the route reflector. It is to reduce the
number of IBGP neighbor connections in an AS. Route confederation allows an AS to be
divided into multi sub-ASs. IBGP routers in the AS belong to the sub-ASs respectively.
IBGP is established within the sub-ASs. EBGP is established between the sub-ASs. The
sub-AS ID is called confederation ID. Sub-ASs are invisible to the outside world of the AS.
To configure BGP4+ confederation, perform the following steps.
1 ZXR10(config-router)#bgp confederation identifier < value> This sets confederation ID
2 ZXR10(config-router)#bgp confederation peers < value> [ < value> ] This sets AS ID of a confederation
peer
Example
There are 5 BGP4+ routers in AS200, as shown in Figure 9-4 , It is divided into two
sub-ASs. One is defined as AS65010, which includes R3, R5 and R6, and the other is
defined as AS65020, which includes R4 and R7.
Figure 9-4 BGP4+ Confederation Configuration Example
ZXR10_R3(config-router)#bgp confederation identifier 200
ZXR10_R3(config-router)#bgp confederation peers 65020
ZXR10_R3(config-router)#neighbor 3ffe:5:3::5 remote-as 65010
9-6

ZXR10_R3(config-router-af)#neighbor 3ffe:5:3::5 activate
ZXR10_R5(config-router)#bgp confederation identifier 200
When establishing neighbor relation, EBGP neighbor relation is established between R3

and the confederation peers. IBGP neighbor relation is established with the confederation,
and the EBGP neighbor relation is also established with AS100. The confederation is
non-existent to AS100, so AS100 still establishes neighbor relation with R3 as AS200.
ZXR10_R1(config-router)#bgp route-id 1.1.1.1
9.2.6 Configuring BGP4+ Route Attributes

To configure BGP4+ route attributes, perform the following steps.
1 ZXR10(config-router)#bgp always-compare-med This allows a mandatory comparison

of various neighbor route MED
values in different ASs.
2 ZXR10(config-router)#bgp default local-preference < value> This sets BGP4+ default local priority
value.
3 ZXR10(config-router)#neighbor { < ipv6-address> | < This configures interval of advertising

peer-group-name> } advertisement-interval < interval> routes to neighbors.
4 ZXR10(config-router)#neighbor { < ipv6-address> | < This sets neighbor description.

peer-group-name> } description < line>
5 ZXR10(config-router)#neighbor { < ipv6-address> | < This makes a router not send open
peer-group-name> } passive messages to neighbors.
9-7

6 ZXR10(config-router)#neighbor < ipv6-address> peer-group [ < This creates a peer group and add a
group-name> ] neighbor to this group.
7 ZXR10(config-router)#neighbor { < ipv6-address> | < This administratively shuts down a

peer-group-name> } shut-down neighbor.
8 ZXR10(config-router)#neighbor { < ipv6-address> | < This sets related timers of a neighbor.

peer-group-name> } timers < keepalive> < holdtime>
9 ZXR10(config-router)#neighbor { < ipv6-address> | < This sets source address that is

peer-group-name> } update-source { loopback< interface number> | used to establish TCP connection
supervlan < interface number> | vlan < interface number> } with neighbor.
9.2.7 Configuring BGP4+ IPv6 Address Family

To configure IPv6 address family, perform the following command.
1 ZXR10(config-router-af)#address-family ipv6 This enters IPv6 address family

configuration mode
2 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This sends default route to specified

peer-group-name> } default-originate neighbor
3 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This sets the maximum number of

peer-group-name> } maximum-prefix < value> route entries from neighbors
4 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This sets self to be the next hop
peer-group-name> } next-hop-self
5 ZXR10(config-router-af)#neighbor { < ipv6-address> < This filters private AS in routes that

peer-group-name> } remove-private-as are advertised to neighbors
6 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This sends community attribute to

peer-group-name> } send-community neighbor when advertising routes
7 ZXR10(config-router-af)#neighbor { < ipv6-address> | < This sets a neighbor to support soft

peer-group-name> } soft-reconfiguration reconfiguration
9.3 BGP4+ Configuration Example

As shown in Figure 9-5 , EBGP is established between R4 and R1. IBGP is established
between R1 and R2. Multi-hop EBGP is established between R2 and R5.
9-8

Figure 9-5 BGP4+ Configuration Example
ZXR10_R4(config-router)#neighbor 2001：：1 remote-as 1
ZXR10_R4(config-router-af)#neighbor 2001：：1 activate
ZXR10_R4(config-router-af)#redistribute static
ZXR10_R1(config-router-af)# neighbor 2001：：4 activate
ZXR10_R1(config-router-af)# neighbor 2003：：2 activate
ZXR10_R1(config-router-af)# neighbor 2003::2 next-hop-self
ZXR10_R2(config-router-af)# neighbor 2003::1 activate
ZXR10_R2(config-router-af)#neighbor 2003::1 next-hop-self
9-9


9.4 BGP4+ Maintenance and Diagnosis

To configure BGP4+ maintenance and diagnosis, perform the following steps.
1 ZXR10#show bgp ipv6 unicast This views BGP4+ routing table.
2 ZXR10#show bgp ipv6 unicast neighbor This views BGP4+ neighbor

information.
3 ZXR10#show bgp ipv6 unicast summary This views all BGP4+ neighbor
states.
4 ZXR10#show bgp ipv6 unicast summary This views all BGP neighbor
connection status.
5 ZXR10#show bgp ipv6 unicast neighbors This views BGPv6 neighbor

information.
9-10

Chapter 10
IPv6 Multicasting Route
Configuration
Table of Contents
Multicast Overview ...................................................................................................10-1
Enabling IPv6 Multicast Routing Function.................................................................10-4
Configuring MLD ......................................................................................................10-4
Configuring PIM-SM .................................................................................................10-5
Configuring MLD-SNOOPING ..................................................................................10-8
IPv6 Multicasting Route Configuration Example .......................................................10-9
IPv6 Multicast Route Maintenance and Diagnosis .................................................. 10-11
10.1 Multicast Overview

Multicast refers to a point-to-multipoint or multipoint -to- multipoint communication mode.
That is, multi-receivers receive the same information sent from one source. Applications
based on multicast contain videoconference, distance learning, software distribution and
so on.
IPv6 multicast protocol includes group management protocol and multicast routing
protocol. The former is used to manage the joint and leave of the group members, the
latter is used to transmit information between routers to create a multicast tree.
ZXR10 5900E supports the following protocols:
l Multicast Listener Discovery Protocol (MLD)
l Protocol Independent Multicast Sparse Mode (PIM-SM)
10.1.1 Multicast Address

Multicast is a technology, by which one source node sends a single data packet to multiple
destinations (one to many) at the same time. Relatively speaking, unicast means one
source node sends a single data packet to one destination (one to one). The main purpose
of multicast is to enhance network efficiency and to save link bandwidth by optimizing data
packet flow. In IPv6, the multicast addressing is defined by IPv6 prefix, the proffered format
FF00:0000:0000:0000:0000:0000:0000:0000/8, which is compressed to FF00::/8.
10-1

10.1.2 MLD Protocol

Multicast Listener Discovery (MLD) can enable each IPv6 router to discover multicast
group members on its own local links (namely, those nodes receiving multicast packets)
and those adjacent nodes which are interested in specified multicast addresses. To
ensure that all multicast packets are sent to all interested receivers (group members), the
information is provided to any multicast protocol used in this router (other protocols).
MLD is an unsymmetrical protocol. IPv6 multicast members (hosts or routers) and IPv6
multicast routers have different protocol behaviors. The purpose is to make IPv6 routers
discover directly connected IPv6 multicast monitors by using MLD. MLD collects and
maintains the group member relationship and provides the information to the links where
IPv6 monitors exist. Those routers, to which multicast addressing one router (they are
receivers themselves), execute two parts of the protocol, including messages returned
to themselves.
If more than one interfaces of a multicast router are connected to a link, it is only necessary
to execute MLD protocol routing on one interface. For multicast members, it is necessary
to execute receiver of MLD protocol.
10.1.3 Multicast Tree

To enable multicast communication in the networks, the multicast source, receivers and the
paths of multicast packets should be available. The most commonly used routing method
is to establish tree routes, which provides the following two advantages:
1. Packets are sent to different receivers along the tree branches in parallel.
2. Packets are copied only on crotches, which minimizes the number of packets
transmitted in the networks.
A multicast tree is a set that comprises a series of incoming interfaces and outgoing
interfaces on router. It determines a unique forwarding path between the subnet to which
the multicast source belongs and all the subnets that contain the group members.
There are two ways to construct a multicast tree: per-source multicast tree and shared
multicast tree.
l Per-Source Multicast Tree
Per-source multicast tree is also called source shortest path tree. It establishes a
spanning tree to all receivers for each source. This spanning tree takes the subnet to
which the source belongs as the root node. This tree reaches the subnets to which
the receivers belong. A multicast group may include multi multicast sources. Each
source or pair (S, G) has a corresponding multicast tree.
The method to construct a per-source multicast tree is reverse path forwarding
(RPF). Each router can find the shortest path to the source and the corresponding
outgoing interface according to uni-cast route. When a router receives a multicast
packet, it verifies whether the incoming interface that the packet reaches is the
outgoing interface to the source with the shortest uni-cast path. If yes, the route
10-2

Chapter 10 IPv6 Multicasting Route Configuration
copies the packet and forwards it to outgoing interfaces; otherwise, it discards the
multicast packet.
The incoming interface from which the router receives multicast packets is called
parent link. The outgoing interface that sends multicast packets is called child link.
l Shared Multicast Tree
Shared multicast tree establishes a multicast route tree for each multicast group,
which is shared by all group members. That is, the tree is shared by the group (*,
G) instead of every pair (S, G). Each device to receive the multicast packets from the
group should be added to the shared tree explicitly.
A shared multicast tree uses one or a group of routers as the center of the tree.
Multicast packets from all sources in this group to the receivers are sent as uni-cast
packets to the center. Then these packets are forwarded as multicast packets along
the tree from the center.
10.1.4 PIM-SM
PIM-SM uses a shared tree to transmit multicast packets. A shared tree has a central
point, which is responsible for sending packets for all the sources in a multicast group.
Each source sends packets to the central point along the shortest-path route. Then the
source takes the central point as root node to distribute the packets to all the receivers
in the group. The central point of a PIM-SM group is called Rendezvous Point (RP). A
network is allowed to have multiple RPs, but a multicast group only has one RP.
A router can obtain the location of the RP by three methods.
l Configure RPs manually and statically on various routers running the PIM-SM.
l PIM-SM V1 obtains such locations through automatic RPs (Auto-RP) dynamically.
l PIM-SM V2 obtains such locations through the candidate-RP notification. The C-RPs
with higher priority will become formal RPs.
PIM-SM V2 manually configures some routers running PIM-SM as candidate-BSRs
(BootStrap Router), and selects the candidate-BSR with the highest priority as the formal
BSR. BSR is responsible for collecting candidate RP messages from the entire multicast
routers. It also tries to find the candidate RPs existing in the multicast domain and
advertises them to all the PIM routers in the PIM domain. Each PIM router selects the
optimum RP for each group in the RP set according to the unified RP election rule. RP
candidates are configured manually.
Routers running PIM-SM attempt to find each other and maintain the neighbor relation by
exchanging hello messages. On the multi-access network, a hello message also includes
router priority information. It is used to elect the designated router (DR).
Multicast source or the first-hop router (DR directly connected to the source) encapsulates
the packet into a Register message and sends it to RP through a uni-cast route. When
receiving the Register message, RP de-encapsulates the packet and sends it along the
shared tree downward to receivers in this group.
10-3

Each host acting as a receiver joins multicast group by an MLD member report message.
The last-hop router (or DR on the multi-access network) sends received Join message
to RP level by level for registration. The media router checks if a route for this group is
available after receiving Join message. If yes, it adds the downstream requesting router to
the shared tree as a branch. Otherwise, it creates a route for the group with the incoming
interface pointing to the RP and the outgoing interface pointing to the downstream
requesting router, and then the Join message proceeds to RP continuously level by level.
When the RP or multicast router is directly connected to any receiver, it can be switched
over from the shared tree to the per-source multicast tree. When receiving a Register
message from a new multicast source, RP returns a Join message to DR that is directly
connected to multicast source. Thus, the shortest path tree from the source to the RP is
established.
When a DR or a router with multicast members connected directly receives the first
multicast packet from the multicast group, or when the received packets reach a threshold,
it can be switched over from the shared tree to the per-source, shortest-path tree. Once
the switchover occurs, the route will send a Prune message to the upstream neighbors,
requesting to be separated from the shared tree.
10.1.5 MLD-SNOOPING
MLD SNOOPING is one of L2 switch features, which can control the forwarding of IP
multipoint transmission flow. Additionally, it can transmit packets to the port designated by
IPv6 host instead of all ports in a group. This optimizes the network bandwidth efficiently.
MLD SNOOPING also enables switch to learn which port belongs to multicast member
before transmitting packets in order to obtain forwarded information.
10.2 Enabling IPv6 Multicast Routing Function

Command Function
ZXR10(config)#Ipv6 multicast-routing This enables multicast routing function.
10.3 Configuring MLD

10.3.1 Configuring a MLD Group on an Interface
Command Function
ZXR10(config-if-vlanX)#ipv6 mld static-group < group-address> This configures a MLD group on an

interface.
It is allowed to bind the group addresses on interfaces statically, that is, supposing the
group member exists all the time.
10-4

Example
This example shows how to configure static group ffe1::1 on interface vlan1.
ZXR10(config-if-vlan1)#ipv6 mld static-group ffe1::1
10.3.2 Configuring MLD Timers

After MLD is enabled on the interface of multicast router that is connected to the sharing
network segment, an optimal router is selected as the querier. The querier is responsible
for obtaining member information by sending query messages.
After querier sends query message, it will wait for the host to send report that contains
member information within a period. The period is the maximum response time contained
in the query message. After receiving the query message, the host member in the network
will subtract a random offset time from the maximum response time and takes the outcome
as its response time. If the querier receives response reports from other host members
within the period, the reports will be discarded. Otherwise, the host report will be sent.
Therefore, to increase the maximum response time is to add waiting opportunities of group
members in network segment and to reduce the rate of multi-host reports.
To configure MLD timers, perform the following steps.
1 ZXR10(config-if-vlanX)#ipv6 mld query-interval < seconds> This configures MLD query interval.
2 ZXR10(config-if-vlanX)#ipv6 mld query-timeout < seconds> This configures MLD query timeout.
3 ZXR10(config-if-vlanX)#ipv6 mld query-max-response-time < This configures maximum response

seconds> time contained in the query message.
4 ZXR10(config-if-vlanX)#ipv6 mld last-member-query-interval This configures MLD query interval

< seconds> of specified group.
10.4 Configuring PIM-SM

10.4.1 Booting IPv6 PIM-SM
1 ZXR10(config)#ipv6 router pimsm This boots IPv6 PIM-SM.
2 ZXR10(config-if-vlanX)#ipv6 pim This enables IPv6 PIM-SM on an

interface.
10-5

10.4.2 Configuring Static RP Address

One static RP is allowed to be configured for one or multiple specific groups. It is required
to configure same static RPs for the group on all PIM-SM multicast routers in the multicast
area. Usually the loopback interface address is used to reduce the network vibration
caused by the Up/Down of a physical interface. After the static RP is configured, it is
not necessary to configure the Candidate-RP for the group.
To configure the static RP address, use the following command.
Command Function
ZXR10(config)#ipv6 router pimsm static-rp < ipv6-addr> [ group-list This configures the static RP address.
< access-name> ]
Example
This example shows configuration of static RP 2001::1 for all groups.
ZXR10(config)#ipv6 router pimsm static-rp 2001::1
10.4.3 Configuring Candidate-BSR

If the static RP mechanism is not used, each multicast area must be configured with the
Candidate-BSR on more than one multicast routers. A BSR should be selected. The BSR
sends booting messages to advertise RP information. According to the latest advertising
messages, the router running the PIM-SM updates the RP state. The bootstrap message
send by the BSR is also used to select the formal BSR in the Candidate-BSR.
The default priority of Candidate-BSR is 0. Candidate-BSR with higher priority becomes
formal BSR. If the priorities of multiple candidate BSRs are the same, the one with the
biggest IPv6 address becomes the BSR.
To configure Candidate-BSR, use the following command.
Command Function
ZXR10(config)#ipv6 router pimsm bsr-candidate < ipv6 addr> [ < This configures the Candidate-BSR.
hash-mask-length> ] [ < priority> ]
10.4.4 Configuring Candidate-RP

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

The default priority of the Candidate-RP is 0. The candidate-RP with greater priority value
has smaller priority.
10.4.5 Configuring Area Border with the Interface PIM

Command Function
ZXR10(config-if-vlanX)#ipv6 pim bsr-border This configures area border with the

interface PIM.
Bootstrap data packets cannot pass the border in any direction. The command effectively
divides a network into different BSR areas. Other PIM packets can pass the area border.
10.4.6 Limiting BSR Message to Advertise to Candidate-RP

Command Function
ZXR10(config)#ipv6 router pimsm accept-rp < access-name> This limits BSR message to advertise
to Candidate-RP.
10.4.7 Setting DR Priority

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

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

Command Function
ZXR10(config-if-vlanX)#ipv6 pim hello-interval < seconds> This configures interval to send Hello
message.
The interval to send hello message can be configured according to network conditions. It
is 30 seconds by default.
10-7

10.4.9 Configuring Interval to Send PIM JP Message

Command Function
ZXR10(config-if-vlanX)#ipv6 pim join-prune-interval < seconds> This configures interval to send PIM JP
message.
10.5 Configuring MLD-SNOOPING

1 ZXR10(config)#ipv6 mld snooping This enables MLD SNOOPING.
2 ZXR10(config-vlanX)#mld snooping This configures MLD SNOOPING

function in VLAN.
3 ZXR10(config-vlanx)#mld snooping drop < group-address> [ num < This configures DROP function of
num> ] MLD SNOOPING.
4 ZXR10(config-vlanX)#mld snooping fast-leave This configures group fast-leave

function of VLAN.
5 ZXR10(config-vlanX)#mld snooping host-time-out < time> This configures aging time of users.
6 ZXR10(config-vlanX)#mld snooping last-member-query-interval This configures the last member

< interval> querying interval.
7 ZXR10(config-vlanX)#mld snooping max-host-in-group < This configures the maximum

group-address> [ limit-num < num> ] number of users in one group.
8 ZXR10(config-vlanX)#mld snooping mrouter interface < port-name> This configures the multicast routing
port in VLAN.
9 ZXR10(config-vlanX)#mld snooping mrouter-time-out < time> This configures the aging time of
multicast routing port in VLAN.
10 ZXR10(config-vlanX)#mld snooping querier This configures MLD SNOOPING

querier function.
11 ZXR10(config-vlanX)#mld snooping static < group-address> This configures static users in VLAN.
interface < port-name>
12 ZXR10(config-vlanX)#ipv6 mld snooping querier [ vlan < word> ] This configures multiple MLD
SNOOPING agent queriers.
13 ZXR10(config-vlanX)#ipv6 mld snooping query-interval < interval> This configures the query interval of
agent querier.
14 ZXR10(config-vlanX)#ipv6 mld snooping query-response-interval This configures the maximum query

< interval> response time of agent querier.
10-8

10.6 IPv6 Multicasting Route Configuration Example

This is an example of IPv6 multicast route configuration. The topology is shown in Figure
10-1.
Figure 10-1 IPV6 MULTICASTING ROUTE CONFIGURATION EXAMPLE
ZXR10_R1(config)#interface loopback1
ZXR10_R1(config-loopback1)#ipv6 enable
ZXR10_R1(config-loopback1)#ipv6 address 1000::1/128
ZXR10_R1(config)#ipv6 multicast-routing
ZXR10_R1(config)#ipv6 router pimsm
ZXR10_R1(config)#ipv6 router pimsm static-rp 1000::3
ZXR10_R1(config)#interface vlan 1
ZXR10_R1(config-if-vlan1)#ipv6 pim
ZXR10_R1(config-if-vlan2)#ipv6 2001:2::1/64
ZXR10_R1(config-router)#router-id 1.1.1.1
ZXR10_R1(config)#int vlan 2
10-9


ZXR10_R2(config-loopback1)#ipv6 1000::2/128
ZXR10_R2(config-if-vlan2)#ipv6 ddress 2001:3::2/64
ZXR10_R2(config-if-vlan3)#ipv6 ddress 2001:4::1/64
ZXR10_R2(config-router)#router-id 2.2.2.2
ZXR10_R2(config-if-vlan2)#ipv6 ospf area 0
ZXR10_R3(config-loopback1)#ipv6 address 1000::3/128
10-10

ZXR10_R3(config)#router-id 3.3.3.3
ZXR10_R3(config-loopback1)#ipv6 ospf 1 area 0
Pay attention to the order of configurations: configure ipv6 multicast-routing command

firstly, and then configure ipv6 router pimsm command, and finally configure ipv6 pim
command on interfaces. Otherwise the configuration can not be successful.
10.7 IPv6 Multicast Route Maintenance and Diagnosis

Viewing Public Information
1. To display IPv6 multicast route statistical information, use the following command.
Command Function
ZXR10#show ipv6 mr6 stat This displays IPv6 multicast route

statistical information.
The description of displayed information is shown below.
Information Description
mr6 data rcv The number of data packets received by mr.
mr6 data upsend suc The number of data packets sent by mr successfully.
mr6 data upsend fail The number of data packets sent by mr unsuccessfully.
mr6 pim6 upsend suc The number of data packets sent by pim successfully.
mr6 pim6 upsend fail The number of data packets sent by pim unsuccessfully.
mr6 pim6 send The total number of data packets sent by pim.
mr6 mld upsend suc The number of data packets sent by mld successfully.
mr6 mld upsend fail The number of data packets sent by mld unsuccessfully.
mr6 mld send The total number of data packets sent by mld.
mr6 pro send The total number of data packets sent by mr.
2. To display information in multicast forwarding table, use the following command.
10-11

Command Function
ZXR10#show ipv6 mroute [ [ group < group-address> [ source < This displays information in multicast
source-address> ] ] | [ summary] forwarding table.
Instructions:
a. If there is no option specified, this command displays all multicast forwarding
tables.
b. If any group is specified, this command displays the group (*, g) and all related
forwarding entries (s, g).
c. If group and source addresses are specified, this command displays the specified
(s, g) forwarding entries.
d. If keyword summary is specified, this command displays statistics on routing
entries.
e. The description of displayed information is shown below.
Entry flags Forwarding routing entry state: F can be forwarded, U protocol needs to
be sent, P in pruned state, can not be forwarded.
Interface flags Outgoing interface state: F: can be forwarded, A: the interface is in

receiving state.
RPF nbr Rpf neighborhood information.
Viewing MLD Information

To view MLD information, perform the following steps.
1. To view the added MLD group information on interface, use the following command.
Command Function
ZXR10#show ipv6 mld groups [ < interface-name> ] | [ < group-addr> ] This views the added MLD group
information on interface.
The description of displayed information is shown below.
Group addr Group Address
Interface Interface
Present The time when group members appear
Expire Left time in time-out timer, never indicates that there is a static group, timer
is inactivated
2. To view the MLD configuration information on interface, use the following command.
10-12

Command Function
ZXR10#show ipv6 mld interface [ < interface-name> ] This views the MLD configuration
information on interface.
This example shows how to view MLD configuration information on vlan 1.

ZXR10#show ipv6 mld interface
vlan1
Internet address is fe80::2d0:d0ff:fec5:a5d8
MLD is enabled on interface
Current MLD version is 1
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 querier is fe80::2d0:d0ff:fec5:a5d8, this system
The number of joined MLD groups is 3
The number of configured static groups is 3
Viewing PIM-SM Information

To view PIM-SM information, perform the following steps.
1 ZXR10#show ipv6 pim mroute [ [ group < group-address> [ source < This displays information of IPv6
source-address> ] ] | [ group < group-address> ] PIM-SM routing table.
2 ZXR10#show ipv6 pim bsr candidate-rp This displasy current candidate rp

information.
3 ZXR10#show ipv6 pim bsr election This displays information of BSR.
4 ZXR10#show ipv6 pim bsr rp-cache This displays CRP information

learned through BSR.
5 ZXR10#show ipv6 pimsm interface [ < interface-name> ] This displays information on PIM-SM
interface.
6 ZXR10#show ipv6 pim neighbor [ < interface-name> ] This displays neighbor information of
PIM-SM Interface.
7 ZXR10#show ipv6 pim nexthop This displays next hop route

information.
8 ZXR10#show ipv6 pim rp mapping [ info-source< info-source> ] This displays information of RP set.
9 ZXR10#show ipv6 pim rp hash < group-address/prefix> This displays RP information

selected by specified multicast
group.
10-13

10 ZXR10#show ipv6 pim topology [ [ group < group-address> [ source < This displays topology information of
source-address> ] ] | [ route-count] PIM-SM multicast routing table.
11 ZXR10#show ipv6 pim traffic This displays the statistical

information of PIM-SM.
12 ZXR10#show ipv6 rpf [ address< ipv6-addr> ] This displays the checking result rpf
sent to RP or source.
Viewing MLD SNOOPING Information
1 ZXR10#show ipv6 mld snooping This displays MLD SNOOPING

related information.
2 ZXR10#show ipv6 mld snooping group < ipv6-address> vlan < vlan-id> This displays configuration and
running information of a specified
group.
3 ZXR10#show ipv6 mld snooping mr-port-info This displays related multicast

routing interface information of MLD
SNOOPING.
4 ZXR10#show ipv6 mld snooping port-info vlan < vlan-id> This displays VLAN interface
information related to MLD
SNOOPING.
5 ZXR10#show ipv6 mld snooping statistic [ clear] [ < port-name> ] This displays statistics information
of MLD packets.
6 ZXR10#show ipv6 mld snooping vlan < vlan-id> This displays MLD SNOOPING
configuration related to specified
VLAN.
Debugging PIM-SM
To debug PIM-SM, perform the following steps.
1 ZXR10#debug ipv6 pimsm bsr This enables debugging IPv6 pimsm

bsr.
2 ZXR10#debug ipv6 pimsm df-election This enables debugging DF

(Designated Forwarder).
3 ZXR10#debug ipv6 pimsm interfac This enables debugging related

interface.
4 ZXR10#debug ipv6 pimsm mrt This enables debugging related

multicast routing table.
10-14

5 ZXR10#debug ipv6 pimsm neighbor This enables debugging related

neighbor.
6 ZXR10#debug ipv6 pimsm nexthop This enables debugging related next

hop.
7 ZXR10#debug ipv6 mr This enables debugging related IPv6

multicast.
8 ZXR10#debug ipv6 mld This enables debugging all mld.
9 ZXR10#debug ipv6 mld group < group-addr> This enables debugging mld related
to group.
10 ZXR10#debug ipv6 mld interface < interface-name> This enables debugging mld related
to interface.
10-15

10-16

Figures
Figure 4-1 6TO4 ADDRESS FORMAT ...................................................................... 4-2
Figure 4-2 AUTOMATIC 6TO4 TUNNEL ................................................................... 4-2
Figure 4-3 IPv6 TUNNEL Configuration Example 1................................................... 4-3
Figure 4-4 IPv6 TUNNEL Configuration Example 2................................................... 4-5
Figure 5-1 DHCPv6 Relay Configuration Example .................................................... 5-6
Figure 6-1 EXAMPLE OF CONFIGURING RIPNG.................................................... 6-4
Figure 7-1 OSPFv3 Configuration Example .............................................................. 7-6
Figure 8-1 Single Area IS-ISv6 Configuration Example ............................................. 8-4
Figure 8-2 Multi-Area IS-ISv6 Configuration Example ............................................... 8-5
Figure 9-1 Basic BGP4+ Configuration Example....................................................... 9-2
Figure 9-2 EBGP Multi-Hops Configuration Example ................................................ 9-3
Figure 9-3 BGP4+ Route Reflector Configuration Example ....................................... 9-5
Figure 9-4 BGP4+ Confederation Configuration Example ......................................... 9-6
Figure 9-5 BGP4+ Configuration Example ................................................................ 9-9
Figure 10-1 IPV6 MULTICASTING ROUTE CONFIGURATION EXAMPLE ............. 10-9
I
Figures

Glossary
ARP
- Address Resolution Protocol
ATM
- Asynchronous Transfer Mode
CIDR
- Classless Inter-Domain Routing
CLNS
- ConnectionLess Network Sevice
FDDI
- Fiber Distributed Data Interface
ICMP
- Internet Control Message Protocol
IETF
- Internet Engineering Task Force
IPX
- Internetwork Packet Exchange protocol
IS-IS
- Intermediate System-to-Intermediate System
LSA
- Link State Advertisement
NBMA
- Non-Broadcast Multiple Access
NDP
- Neighbor Discovery Protocol
NLRI
- Network Layer Reachable Information
NSAP
- Network Service Access Point
OSPF
- Open Shortest Path First
OUI
- Organizationally Unique Identifier
PDA
- Personal Digital Assistant
III
QoS
- Quality of Service
RARP
- Reverse Address Resolution Protocol
RIPng
- Routing Information Protocol next generation
SPF
- Shortest Path First
TLV
- Type/Length/Value
UDP
- User Datagram Protocol
IV

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

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

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

Uploaded by

Copyright:

Available Formats

ZXR10 5900E Series

Easy-Maintenance MPLS Routing Switch

Revision No. Revision Date Revision Reason

R1.0 2011-02-11 First Release

Serial Number: SJ-20101226010430-005

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

Chapter 2 IPv6 Address Configuration..................................................... 2-1

Chapter 3 IPv6 Neighbor Discovery Protocol .......................................... 3-1

Chapter 4 IPv6 Tunnel Configuration ....................................................... 4-1

Chapter 5 IPv6 Other Configurations ....................................................... 5-1

Chapter 6 RIPng Configuration ................................................................. 6-1

Chapter 7 OSPFv3 Configuration.............................................................. 7-1

Chapter 8 IS-ISv6 Configuration ............................................................... 8-1

Chapter 9 BGP4+ Configuration ............................................................... 9-1

Chapter 10 IPv6 Multicasting Route Configuration............................... 10-1

What Is in This Manual

Chapter 1 Safety Instruction Describes the safety instructions and signs.

1.1 Safety Instruction

1.2 Safety Signs

Indicates the matters needing attention during configuration.

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

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

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

2.1 IPv6 Overview

2.1.1 IPv6 Address Format

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

Table 2-1 COMPRESSED FORMATS

IPv6 Address Type Normal Format Compressed Format

Unicast address 1080:0:0:0:8:800:200C:1234 1080::8:800:200C:1234

Multicast address FF01:0:0:0:0:0:0:123 FF01::123

Loopback address 0:0:0:0:0:0:0:1 ::1

Unspecified address 0:0:0:0:0:0:0:0 ::

2.1.2 IPv6 Address Prefix

2.1.3 IPv6 Address Classification

Table 2-2 IPV6 ADDRESS SPACE

Allocation Prefix Occupation Rate of Address

Reserved 0000 0000 1/256

Unallocated 0000 0001 1/256

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

Allocation Prefix Occupation Rate of Address

Reserved for NSAP allocated 0000 001 1/128

Reserved for IPX allocated 0000 010 1/128

Unallocated 0000 011 1/128

Unallocated 0000 1 1/32

Unallocated 0001 1/16

Global unicast 001 1/8

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 0 1/32

Unallocated 1111 10 1/64

Unallocated 1111 110 1/128

Unallocated 1111 1110 0 1/512

Link-local unicast 1111 1110 10 1/1024

Site-local unicast 1111 1110 11 1/1024

Multicast 1111 1111 1/256

2.1.3.1 Unicast Address

Global Unicast Address

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

Table 2-3 GLOBAL UNICAST ADDRESS FORMAT

3 bits 45 bits 16 bits 64bits