ZXR105900ESeries - nova-minsk.com · ZXR105900ESeries Easy-MaintenanceMPLSRoutingSwitch ConfigurationGuide (IPv6) Version: 3.00.11 ZTECORPORATION No.55,Hi-techRoadSouth,ShenZhen,P.R.China

ZXR10 5900E SeriesEasy-Maintenance MPLS Routing Switch

Configuration Guide (IPv6)

Version: 3.00.11

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://support.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2014 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2015–01–15 First edition

Serial Number: SJ-20150114102049-011

Publishing Date: 2015-01-15 (R1.0)

SJ-20150114102049-011|2015-01-15 (R1.0) ZTE Proprietary and Confidential

ContentsAbout This Manual ......................................................................................... I

Chapter 1 IPv6 Address Configuration..................................................... 1-11.1 IPv6 Address Overview ...................................................................................... 1-1

1.2 Configuring IPv6 Addresses.............................................................................. 1-13

1.3 Maintaining IPv6 Addresses.............................................................................. 1-13

1.4 IPv6 Address Configuration Example................................................................. 1-15

Chapter 2 NDP Configuration.................................................................... 2-12.1 NDP Overview ................................................................................................... 2-1

2.2 Configuring NDP ................................................................................................ 2-2

2.3 NDP Maintenance and Diagnosis ........................................................................ 2-5

2.4 NDP Configuration Example ............................................................................... 2-7

Chapter 3 IPv6 Tunnel Configuration ....................................................... 3-13.1 IPv6 Tunnel Overview......................................................................................... 3-1

3.2 Configuring IPv6 Tunnel ..................................................................................... 3-4

3.3 IPv6 Tunnel Configuration Examples ................................................................... 3-6

3.3.1 6in4 Tunnel Configuration Example ........................................................... 3-6

3.3.2 6to4 Tunnel Configuration Example ........................................................... 3-8

Chapter 4 IPv6 ACL Configuration............................................................ 4-14.1 IPv6 ACL Overview ............................................................................................ 4-1

4.2 Configuring IPv6 ACL ......................................................................................... 4-1

4.3 IPv6 mixed-ACL Maintenance and Diagnosis ....................................................... 4-7

4.4 IPv6 ACL Configuration Example ........................................................................ 4-9

Chapter 5 IPv6 Static Route Configuration .............................................. 5-15.1 IPv6 Static Route Overview................................................................................. 5-1

5.2 Configuring IPv6 Static Routes............................................................................ 5-1

5.3 Maintaining IPv6 Static Routes............................................................................ 5-2

5.4 IPv6 Static Route Configuration Example............................................................. 5-4

Chapter 6 RIPng Configuration................................................................. 6-16.1 RIPng Overview ................................................................................................. 6-1

6.2 Configuring the RIPng ........................................................................................ 6-3

6.3 RIPng Maintenance and Diagnosis...................................................................... 6-7

6.4 RIPng Configuration Example ............................................................................. 6-9

I


Chapter 7 OSPFv3 Configuration.............................................................. 7-17.1 OSPFv3 Overview.............................................................................................. 7-1

7.2 Configuring OSPFv3........................................................................................... 7-5

7.3 OSPFv3 Maintenance and Diagnosis .................................................................7-11

7.4 OSPFv3 Configuration Examples ...................................................................... 7-13

7.4.1 OSPFv3 Configuration Example 1 ........................................................... 7-13

7.4.2 OSPFv3 Configuration Example 2 ........................................................... 7-16

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

8.2 Configuring IS-ISv6 ............................................................................................ 8-2

8.3 Maintaining IS-ISv6 .......................................................................................... 8-14

8.4 IS-ISv6 Configuration Examples........................................................................ 8-18

8.4.1 Single-Area IS-ISv6 Configuration Example ............................................. 8-18

8.4.2 Multi-Area IS-ISv6 Configuration Example ............................................... 8-22

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

9.2 Configuring BGP4+ ............................................................................................ 9-1

9.3 Maintaining BGP4+ ............................................................................................ 9-2

9.4 BGP4+ Configuration Examples .......................................................................... 9-8

9.4.1 BGP4+ Route Reflector Configuration Example.......................................... 9-8

9.4.2 BGP4+ General Configuration Example................................................... 9-10

Chapter 10 IPv6 QoS Configuration........................................................ 10-110.1 IPv6 QoS Overview ........................................................................................ 10-1

10.2 Configuring IPv6 QoS ..................................................................................... 10-1

10.3 IPv6 QoS Configuration Examples................................................................... 10-1

Chapter 11 IPv6 Multicast Configuration................................................ 11-111.1 IPv6 Multicast Overview ...................................................................................11-1

11.2 Configuring Public IP Multicast .........................................................................11-3

Chapter 12 MLD Configuration................................................................ 12-112.1 MLD Overview ............................................................................................... 12-1

12.2 Configuring MLD ............................................................................................ 12-2

12.3 Maintaining MLD ............................................................................................ 12-6

12.4 MLD Configuration Examples .......................................................................... 12-8

12.4.1 MLDv2 Configuration Example .............................................................. 12-8

12.4.2 Static Group Configuration Example ...................................................... 12-9

Chapter 13 IPv6 PIM-SM Configuration.................................................. 13-1

II


13.1 PIM-SM Overview .......................................................................................... 13-1

13.2 Configuring IPv6 PIM-SM................................................................................ 13-3

13.3 IPv6 PIM-SM Maintenance and Diagnosis........................................................ 13-9

13.4 IPv6 PIM-SM Configuration Example ..............................................................13-16

Chapter 14 IPv6 PIM-SSM Configuration................................................ 14-114.1 PIM-SSM Overview ........................................................................................ 14-1

14.2 Configuring IPv6 PIM-SSM ............................................................................. 14-1

14.3 IPv6 PIM-SSM Maintenance and Diagnosis ..................................................... 14-2

14.4 IPv6 PIM-SSM Configuration Example............................................................. 14-3

Chapter 15 IPv6 Static Multicast Configuration..................................... 15-115.1 IPv6 Static Multicast Introduction ..................................................................... 15-1

15.2 Configuring IPv6 Static Multicast ..................................................................... 15-2

15.3 Maintaining IPv6 Static Multicast ..................................................................... 15-3

15.4 IPv6 Static Multicast Configuration Example..................................................... 15-3

Chapter 16 ISATAP Tunnel Configuration .............................................. 16-116.1 ISATAP Tunnel Overview ................................................................................ 16-1

16.2 Configuring an ISATAP Tunnel ........................................................................ 16-2

16.3 ISATAP Configuration Example ....................................................................... 16-3

Chapter 17 IPv6 Basic Configuration ..................................................... 17-1

Chapter 18 TCP6 Configuration .............................................................. 18-118.1 TCP6 Overview .............................................................................................. 18-1

18.2 Configuring the TCP6 ..................................................................................... 18-1

18.3 TCP6 Maintenance and Diagnosis................................................................... 18-3

Chapter 19 UDP6 Configuration.............................................................. 19-1

Chapter 20 DHCPv6 Configuration ......................................................... 20-120.1 DHCPv6 Overview ......................................................................................... 20-1

20.2 Configuring DHCPv6 ...................................................................................... 20-3

20.3 Maintaining DHCPv6 ...................................................................................... 20-9

20.4 DHCPv6 Configuration Examples ...................................................................20-10

20.4.1 DHCPv6 Server Configuration Instance ................................................20-10

20.4.2 DHCPv6 Relay Configuration Instance..................................................20-12

Figures............................................................................................................. I

Tables ............................................................................................................ III

Glossary .........................................................................................................V

III


This page intentionally left blank.

IV


About This ManualPurposeThis manual is the ZXR10 5900E Series (V3.00.11) Easy-Maintenance MPLS RoutingSwitch Configuration Guide (IPv6), which is applicable to the ZXR10 5900E (V3.00.11)series switches.

Intended AudienceThis manual is intended for:

l Network planning engineersl Commissioning engineersl On-duty personnel

What Is in This ManualThis manual contains the following chapters:

Chapter 1, IPv6 Address Configuration Describes IPv6 address, configuration

commands, maintenance commands and

configuration examples on the ZXR10 5900E.

Chapter 2, NDP Configuration Describes NDP technology and principle,

configuration commands, maintenance

commands and configuration examples on the

ZXR10 5900E.

Chapter 3, IPv6 Tunnel Configuration Describes IPv6 tunnel technology and principle,



ZXR10 5900E.

Chapter 4, IPv6 ACL Configuration Describes IPv6 ACL technology and principle,



ZXR10 5900E.

Chapter 5, IPv6 Static Route Configuration Describes IPv6 static route technology and

principle, configuration commands, maintenance


ZXR10 5900E.

Chapter 6, RIPng Configuration Describes RIPng technology and principle,



ZXR10 5900E.

I


Chapter 7, OSPFv3 Configuration Describes OSPFv3 technology and principle,



ZXR10 5900E.

Chapter 8, IS-ISv6 Configuration Describes IS-ISv6 technology and principle,



ZXR10 5900E.

Chapter 9, BGP4+ Configuration Describes BGP4+ technology and principle,



ZXR10 5900E.

Chapter 10, IPv6 QoS Configuration Describes IPv6 QoS technology and principle,



ZXR10 5900E.

Chapter 11, IPv6 Multicast Configuration Describes IPv6 multicast technology and



ZXR10 5900E.

Chapter 12, MLD Configuration Describes MLD technology and principle,



ZXR10 5900E.

Chapter 13, IPv6 PIM-SM Configuration Describes IPv6 PIM-SM technology and



ZXR10 5900E.

Chapter 14, IPv6 PIM-SSM Configuration Describes IPv6 PIM-SSM technology and



ZXR10 5900E.

Chapter 15, IPv6 Static Multicast Configuration Describes IPv6 Static Multicast technology and



ZXR10 5900E.

Chapter 16, ISATAP Tunnel Configuration Describes ISATAP tunnel technology and



ZXR10 5900E.

II


Chapter 17, IPv6 Basic Configuration Describes frequently used IPv6 configuration

commands and maintenance commands.

Chapter 18, TCP6 Configuration Describes TCP6 principles and maintenance

commands.

Chapter 19, UDP6 Configuration Describes UDP6 principles and maintenance

commands.

Chapter 20, DHCPv6 Configuration Describes UDP6 principles, configuration

commands, maintenance commands and

configuration examples on the ZXR10 5900E.

ConventionsThis manual uses the following typographical conventions:

Italics Variables in commands. It may also refer to other related manuals and documents.

Bold Menus, menu options, function names, input fields, option button names, check boxes,

drop-down lists, dialog box names, window names, parameters, and commands.

Constant

width

Text that you type, program codes, filenames, directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Separates individual parameters in a series of parameters.

Danger: indicates an imminently hazardous situation. Failure to comply can result in

death or serious injury, equipment damage, or site breakdown.

Warning: indicates a potentially hazardous situation. Failure to comply can result in

serious injury, equipment damage, or interruption of major services.

Caution: indicates a potentially hazardous situation. Failure to comply can result in

moderate injury, equipment damage, or interruption of minor services.

Note: provides additional information about a certain topic.

III



IV


Chapter 1IPv6 Address ConfigurationTable of ContentsIPv6 Address Overview ..............................................................................................1-1Configuring IPv6 Addresses .....................................................................................1-13Maintaining IPv6 Addresses .....................................................................................1-13IPv6 Address Configuration Example .......................................................................1-15

1.1 IPv6 Address OverviewIntroduction to IPv6Internet Protocol (IP) version 6 is a new IP protocol, designed to replace IP version 4,the Internet protocol that is predominantly deployed and extensively used throughout theworld.

However, the original design did not anticipate the following conditions:

l Recent exponential growth of the Internet and the impending exhaustion of the InternetProtocol version 4 (IPv4) address space.

l Growth of the Internet and the ability of Internet backbone routers to maintain largerouting tables.

l Need for simpler auto configuration and renumbering.l Requirement for security at the IP level.l Need for better support to real-time delivery of data—also called Quality of Service

(QoS).

Note:

Features such as IP Security Protocol (IPSec) and QoS have been specified for bothversions of IP.

Internet Protocol Version 6 (IPv6) features a huge address capacity up to 128 bits, whichis described as below:

l It provides 2128 different IPv6 addresses, that is, thenumber of the allocable addresses around the world is340,282,366,920,938,463,463,374,607,431,768,211,456.

l It provides 2.2×1020 addresses per cm2 if addresses are allocated based on groundarea of the whole world.

1-1


ZXR10 5900E Series Configuration Guide (IPv6)

The following are differences between IPv4 and IPv6 in header format.

Figure 1-1 and Figure 1-2 are the header formats of IPv4 and IPv6 respectively. (Numbersin the tables refer to bit numbers.)

Figure 1-1 IPv4 Header Format

Figure 1-2 IPv6 Header Format

An IPv6 header is simpler than an IPv4 header in structure because many fields in theIPv4 header that are not frequently used are deleted from the IPv6 header, and are putinto its options and header extension, which are defined more strictly.

l IPv4 contains ten fields with fixed length, two address spaces and some options, whileIPv6 contains only six fields and two address spaces.

l Although an IPv6 header occupies 40 bytes, which is 1.6 times of an IPv4 header with24-bytes, it does not consume too much memory capacity due to its fixed length (thelength of the IPv4 header is variable).

l The following six fields are deleted from an IPv4 header: header length, type ofservice, identifier, flags, fragmented offsets and header checksum. Names andsome functions of the three fields of total length, protocol and Time to Live (TTL) arechanged, and its optional functions is completely changed. Apart from this, two fieldsare added: traffic type and flow label.

l The IPv6 header format is greatly simplified, which effectively pares down overhead ofprocessing header by a router or switch. At the same time, IPv6 enhances the supportto the extension header and options, which not only allows more efficient forwarding,but also provides sufficient supports for future load of new applications to networks.

1-2


Chapter 1 IPv6 Address Configuration

Each IPv6 packet can have 0, 1 or more extension headers. Each extension headeris determined by the "next header" domain of the previous header.

Address ClassificationsIn RFC 2373, addresses are classified based on the address prefix. For a list of IPv6address types, refer to Table 1-1.

Table 1-1 IPv6 Address Types

Address Type Prefix (Binary)

Unassigned addresses 00...0(128 bits)[::/128]

Loopback addresses 00...1(128 bits )[::1/128]

Multicast addresses 11111111[FF00::/8]

Link-local unicast addresses 1111111010[FE80::/10]

Global unicast addresses Others

The broadcast address in IPv6 is not valid any more. RFC2373 defines three types of IPv6address:

l Unicast

It is the identifier of a single interface. The packets sent to a unicast address will betransmitted to the interface with this address identifier.

l Multicast

It is the identifier of a group of interfaces. These interfaces belong to different nodes.The packets sent to a multicast address will be transmitted to all the interfaces withthis address identifier.

l Anycast

It is the identifier of a group of interfaces. These interfaces belong to different nodes.The packets sent to an anycast address will be transmitted to an interface with thisaddress identifier (selecting the nearest one by calculating the distance based onrouting protocol).

An IPv6 unicast address can be regarded as an entity with two fields. One field is usedto identify networks and the other is used to identify interfaces of nodes on this network.In the subsequent description of the specific unicast address types, the user will find thatthe network identifier can be divided into several parts, each of which identifies differentnetwork part.

1. Unicast address

An IPv6 unicast address can have a varied-length prefix. For the structure of the IPv6unicast address, refer to Figure 1-3.

1-3



Figure 1-3 Structure of an IPv6 unicast address

The IPv6 unicast address can be classified into the following categories:

l Aggregatable Global Unicast Address

This is another kind of aggregation, which is independent of Internet ServiceProvider (ISP). The provider aggregatable addresses must be changed as aprovider changes, while the exchange-based addresses are directly located byan IPv6 switching entity. The exchange provides address blocks, and users andproviders conclude contracts for the network access.

Such network access is either directly provided by a provider, or indirectly providedby an exchange. However, the routing is through the exchange. In this way, a userneeds not to address again when it changes a provider. At the same time, usersare allowed to use multiple ISPs to process single-block network address.

Aggregatable global unicast addresses include all the addresses whose threestarting bits are 001, which can be used as prefixes for other unallocatedunicast.Table 1-2 lists the aggregatable global unicast address fields.

Table 1-2 Aggregatable Global Unicast Address Fields

3 13 8 24 16 64

FP TLA ID RES NLA ID SLA ID Interface identifier

The table includes the following fields.

à FP

This is the 3-bit format prefix in an IPv6 address, indicating to which addresscategory in the IPv6 address space this address belongs. Currently, the fieldis 001, indicating this is the aggregatable global unicast address.

à TLA ID

This is the top-level aggregation identifier, including the routing informationabout the addresses at the highest level. Here, it refers to the routinginformation with the most hosts in network interconnection. Currently, thisfield is 13-bit and can obtain at most 8,192 different top level routes.

à RES

This is an 8-bit field and reserved for future use. It is likely to be used forextending the top- or next-level aggregation identifier field.

à NLA ID

This is the next-level aggregation identifier with 24-bit. This identifier isused by some institutions (including large-size ISPs and other institutions

1-4



that provide public network access) to control the top-level aggregation foraddress space arrangement.

Such institutions can divide this 24-bit field for use in accordance with their ownaddressing hierarchical structures. In this way, an entity can divide two bits ofaddress space into four internal top-level routes, and allocate the other 22 bits ofaddress space to other entities (for example, a small local ISP).

When these entities obtain enough address space, they can subdivide theobtained space in the same way as mentioned above.

à SLA ID

This is the site aggregation identifier and is used by some institutions toarrange their internal network structures. Each institution can create its owninternal hierarchical network structure in the same way as that of IPv4.

When the 16-bit field is dedicated to the plane address space, there areat most 65,535 different subnets available. If the first eight bits are usedfor the internal advanced routing of this institution, then there will be 255advanced subnets available, and each advanced subnet can have up to 255sub-subnets.

à Interface identifier

This is a 64-bit field, containing 64-bit values of the IEEE EUI-64 interfaceidentifier.

l Special Address & Reserved Address

In the first 1/256 IPv6 address space, the first 8 bits 0000 0000 of all the addressesare reserved. Most of the vacant address spaces are used for special addresses,including:

à Undesignated address

This is an all-zero address and is used if no valid address is available. Forexample, if a host does not obtain an IPv6 address upon its initial startupfrom the network, it can use this address. That is, it can specify this addressfor the source address of the IPv6 packet when it sends out a request forconfiguration information. This address can be expressed as 0:0:0:0:0:0:0:0,or expressed as ::.

à Loopback address

In IPv4, the loopback address is defined as 127.0.0.1. Any packet that sendsa loopback address must be sent to a network interface through protocolstack, instead of being sent to the network link. The network interface itselfshall accept these packets in the same way as it receives packets fromexternal nodes, and transmits them back to the protocol stack.

The loopback function is used for software test and configuration. Exceptthe lowest bit, all the other bits of an IPv6 loopback address are 0, that is, aloopback address can be expressed as 0:0:0:0:0:0:0:1 or ::1.

1-5



à IPv6 address embedded with IPv4 address

In the RFC 2373, IPv6 provides two kinds of addresses. One is theIPv4-compatible address, which allows the IPv6 node to access IPv4 nodesthat do not support IPv6.. The other is the IPv4-mapping address, whichallows the IPv6 router to transmit IPv6 packets over the IPv4 network in thetunnel mode, where the nodes understand both IPv4 and IPv6.

The high-order 80 bits of these two kinds of addresses are all set to zeros,and the low-order 32 bits contain the IPv4 address. If the middle 16 bits ofan address are set to FFFF, it indicates that this address is the IPv6 addressmapping to IPv4 address. For the address structures of these two kinds ofaddresses, refer to Table 1-3.

Table 1-3 Structure of the IPv6 Address Embedded With IPv4 Address

IPv4 Compatible Address

80 16 32

0000.................................0000 0000 IPv4 address

IPv4 image address

80 16 32

0000.................................0000 FFFF IPv4 address

RFC 4291 specifies that these addresses are not used in the IPv6 transitionmechanism. It is not required for new implementations to support the aboveaddress structures.

l Link Local Address and Site-Local Address

Using the networkModel 10 address to translate IPv4 network addresses providesan option for the institutions that do not want to apply for globally unique IPv4network addresses.

A router that resides outside of an institution but used by the institution shall notforward these addresses. It can neither prevent these addresses from beingforwarded, nor distinguish these addresses from other valid IPv4 addresses. Itis comparatively easier to make configurations for a router to enable it to forwardthese addresses.

To realize this function, IPv6 allocates two different address segments from theglobally unique Internet space. Table 1-4 is originated from RFC 4291, indicatingthe structures of link-local and site-local addresses. Site-local addresses wereoriginally designed to be used for addressing inside a site without the need fora global prefix. The special behavior of this prefix is no longer supported innew implementations (meaning that new implementations must treat this prefix asGlobal Unicast). Existing implementations and deployments may continue usingthis prefix.

1-6



Table 1-4 Structures of Link-local Address and Site-local Address

Link-local Address

10 54 64

1111111010 0 Interface identifier

Site-local Address

10 38 16 64

1111111011 0 Subnet

identifier

Interface identifier

Link-local addresses are used in single network link for host numbering. Theaddress identified by the first ten bits of the prefix is the link-local address. Routersdo not process the packets with link-local addresses at their source end anddestination end because they will never forward these packets.

The middle 54 bits of this address are set to zero, its 64-bit interface identifier is inthe same IEEE structure as mentioned in the foregoing paragraphs, and the partof this address space allows some networks to connect up to 264-1 hosts.

Link-local addresses are used for the single network link and site-local addressesare used for sites. It means that site-local addresses can be used to transmit datain the interconnected networks but cannot be directly routed to the global Internetfrom a site.

Routers within a site can only forward packets within the site instead of forwardingthem outside of the site. The 10-bit prefix of a site-local address is immediatelyfollowed by a succession of zeros, which is slightly different from that of a link-localaddress. The subnet identifier of a site-local address is 16-bit, and its interfaceidentifier is still the 64-bit IEEE-based address.

l Open Systems Interconnection (OSI) Network Service Access Point (NSAP)Address and Internetwork Packet Exchange (IPX) Address

One of the IPv6 objects is to unify the whole network world for among networksof IP, IPX and OSI. To support this interoperability, IPv6 reserves 1/128 addressspace for OSI NSAP address and network IPX address respectively.

At present, the IPX addresses have not been precisely defined. Refer to RFC1888 (OSI NSAP and IPv6) for description of the NSAP address allocation.

2. Multicast Address

The format of the IPv6 multicast address is different from that of the IPv6 unicastaddress. Multicast addresses can only be used as destination addresses. No packetuses a multicast address as the source address. Table 1-5 shows the format of amulticast address.

1-7



Table 1-5 Multicast Address Format

8 4 4 112

1111111 Flags Scope Group identifier

The first byte of the address format is set to full-one, identifying it as a multicastaddress. The multicast address occupies the entire 1/256 of the IPv6 address space.The other parts except the first byte of the multicast address format contain thefollowing three fields:

l Flags field

This field consists of four single bit flags. Currently, only the bit-4 is designated toindicate that whether this address is a well-known multicast address designatedby the Internet numbering institution, or a temporary multicast address used in aspecific occasion.

If this flag bit is set to zero, it indicates that this address is a well-known address.If this flag bit is set to one, it indicates that this address is a temporary address.The other three flag bits are reserved for future use. The initialization value is 0.

l Scope field

This is a 4-bit field and is used to indicate the range of multicast. That is, whethera multicast group only includes nodes within the same local network, the samesite or the same institution, or includes nodes that resides anywhere in the IPv6global address space. The possible 4-bits value ranges from 0 to 15. For thecorresponding ranges, refer to Table 1-6.

Table 1-6 Multicast Scope Value

Hex Decimal Value

0 0 Reserved

1 1 Node-local range

2 2 Link-local range

3 3 Unallocated

4 4 Unallocated

5 5 Site-local range

6 6 Unallocated

7 7 Unallocated

8 8 Institution-local range

9 9 Unallocated

10 A Unallocated

11 B Unallocated

12 C Unallocated

1-8



Hex Decimal Value

13 D Unallocated

14 E Global range

15 F Reserved

l Group ID field

The 112-bit multicast ID field identifies a multicast group within a specified rangepermanently or temporarily.

3. Anycast Address

A multicast address can be shared by many nodes in a sense. All the nodes of themembers of a multicast address expect to receive all the packets sent to this address.A router connecting to five different local Ethernet networks shall forward a copy ofthese multicast packets to each network respectively (supposing at least one node ofeach network subscribes to this multicast address).

Anycast addresses are similar to multicast addresses. Although the two are in thesame case that an anycast address can be shared by multiple nodes, only one nodeof an anycast address expects to receive the packet sent to the anycast address.

Anycast is helpful in providing services, especially those requiring no relationshipbetween client and server, such as, a domain name server and a time server.A domain name server is nothing but a name server, which provides the sameperformance whether it is located closely or remotely.

Similarly, a closely located time server is preferable in terms of accuracy. Therefore,when a host sends a request to an anycast address to obtain information, it is thenearest server associated to this anycast address that shall respond.

Anycast addresses are allocated outside of the normal IPv6 unicast address space.Anycast addresses cannot be distinguished from unicast addresses in their forms, andeachmember of an anycast address shall be explicitly configured to identify an anycastaddress.

Address Expression WayAn IPv4 address is expressed in four parts separated by dots, that is, four numbersseparated by dots. The following are some legal IPv4 addresses expressed by decimalinteger: 0.5.3.1, 127.0.0.1, 201.199.244.101.

An IPv4 address is expressed as a group of four 2-bit hex integers or four 8-bit binaryintegers, of which the latter one is seldom used.

The length of an IPv6 address is four times greater than an IPv4 address, and thecomplicacy of expression for an IPv6 address is also four times greater than an IPv4address. An IPv6 address can be basically expressed as X:X:X:X:X:X:X:X, among whichX is 4-bit hex integers (16-bit). Each number contains four bits, each integer contains four

1-9



numbers and each address contains eight integers. There are totally 128 bits (4 x 4 x 8 =128). The following are some legal IPv6 addresses:

CDCD: 910A:2222:5498:8475:1111:3900:2020

1030:0:0:0:C9B4:FF12:48AA:1A2B

2000:0:0:0:0:0:0:1

All these integers are hex integers and those from A to F represent 10 to 15. Each integerof an address must be indicated except for the starting zero. This is a relatively standardway to express an IPv6 address. Apart from this, there are two more ways that are clearerand easier to use.

Some IPv6 addresses contain a succession of zeros, similar to the second and the thirdexamples as mentioned above. In this case, the succession of zeros can be representedby "pacing", as provided in the relevant standard.

That is to say, the address 2000:0:0:0:0:0:0:1 can be expressed as 2000::1, of which thetwo colons mean that the address can be extended to a complete 128-bit address. In thismethod, only when the 16-bit group is all-zero, can it be substituted by two colons, whichcan only be used once in the address.

Table 1-7 shows examples for compressed formats of IPv6 addresses.

Table 1-7 IPv6 Address Compression

Add Type Normal Format Compressed Format

Unicast address 1080:0:0:0:8:800:200C:417A 1080::8:800:200C:417A

Multicast address FF01:0:0:0:0:0:0:101 FF01::101

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

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

In the environment mixed with IPv4 and IPv6, there may be a third way. The leastsignificant 32-bit in an IPv6 address can be used to express an IPv4 address in a mixedway: X:X:X:X:X:X:d.d.d.d, among which X represents a 16-bit and d indicates a 8-bitdecimal integer.

For example, the address 0:0:0:0:0:0:10.0.0.1 is a legal IPv4 address. Therefore, thisaddress is expressed as: 10.0.0.1 by combining the two possible expressions.

An IPv6 address consists of two parts: subnet prefix and interface identifier. An IP nodeaddress is expected to be expressed in a way similar to that of a CIDR address, as anaddress carrying an extra value, indicating how many bits of the address is the mask.

An IPv6 node address indicates the length of a prefix by separating the length from theIPv6 address with a slash.

For example, in the address of 1030:0:0:0:C9B4:FF12:48AA:1A2B/60, the length of theprefix for routing is 60-bits

l IPv6 Host Address

1-10



An IPv6 host has many IPv6 addresses even if it has only one single interface. AnIPv6 host can have the following unicast addresses simultaneously.

à The link-local address of each interface

à The unicast address of each interface, which can be a site-local address or oneor more aggregable global addresses

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

In addition, each host must always keep receiving the data from the following multicastaddresses.

à Multicast addresses (FF01::1) of all the nodes within the node-local range

à Multicast addresses (FF02::1) of all the nodes within the link-local range

à Multicast address of the solicited-node (if the solicited-node group is added to aninterface of the host)

à Multicast address of a multicast group (if any multicast group is added to aninterface of the host)

l IPv6 Router Address

The following unicast addresses can be allocated to an IPv6 router:

à Link-local address of each interface

à Unicast address of each interface, which can be a site-local address or one ormore aggregable global addresses

à Subnet-router anycast address

à Other anycast addresses (optional)

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

Similarly, apart from these addresses, a router must always keep listening to the dataflow from the following multicast addresses.

à Multicast addresses (FF01::1) of all the nodes within the node-local range

à Multicast addresses (FF02::1) of all the nodes within the link-local range

à Multicast addresses (FF02::2) of all the routers within the link-local range

à Multicast addresses (FF05::2) of all the routers within the site-local range

à Multicast address of the solicited-node (if the solicited-node group is added to aninterface of the router)

à Multicast address of a multicast group (if any multicast group is added to aninterface of the router)

IPv6 Address Auto Configuration TechnologyThe state auto configuration employs the plug-and-play mode to insert a node into theIPv6 network and starts it up without any manual interference. IPv6 has two differentmechanisms to shore up the plug-and-play network connection:

1-11



l State auto configuration

à Boot protocol (BOOTstrap Protocol (BOOTP)

à Dynamic Host Configuration Protocol (DHCP)

Both of the two mechanisms allow IP nodes to obtain configuration information froma special BOOTP server or the DHCP server. These protocols use the state autoconfiguration, that is, a server must retain and manage the state information of eachnode.

l Stateless auto configuration

Apart from state auto configuration, IPv6 also employs a kind of auto configurationservice named stateless auto configuration. RFC2462 describes the IPv6 statelessauto configuration.

For the stateless auto configuration, the local link must support multicast. Networkinterface must be able to send and receive multicast packets. In the stateless autoconfiguration process, the relevant nodes must meet the following requirements.

à A node for auto configuration must determine its own link-local address.

à Authenticate this link-local address to make sure that it is unique in the link.

à The node must determine the information to be configured. Such information canbe the IP address of this node, other configuration information, or both of them.In case an IP address is needed, the node must determine whether to obtain itthrough the stateless auto configuration or through the state auto configuration.

The procedure is as follows:

1. In the stateless auto configuration process, the host adds its network adapter MACaddress after the 1111111010 prefix of the link-local address to create a link-localunicast address.

IEEE has modified the network adapter MAC address from 48-bit to 64-bit. If thenetwork adapter MAC address used by the host is still 48-bit, the IPv6 networkadapter driver will convert the 48-bit MAC address to the 64-bit MAC address inaccordance with an IEEE formula.

2. The host sends a neighbor discovery request to the address to check whether theaddress is unique.

If there is no response to the request, it indicates that the link-local unicast addressconfigured by the host itself is unique. Otherwise, the host will use an interfaceID randomly created to form a new link-local unicast address.

3. Taking the address as the source address, the host sends a router solicitation inthe multicast way to all the routers within the local link to request configurationinformation. Routers respond to it with a router advertisement containing theprefix of an aggregable global unicast address and other relevant configurationinformation.

1-12



The host automatically uses the global address prefix obtained from routers andits own interface ID to automatically configure a global address to communicatewith other hosts within the Internet.

1.2 Configuring IPv6 AddressesTo configure IPv6 addresses, perform the following steps:

Step Command Function

1 ZXR10(config)#interface <interface-name> Enters the interface

configuration mode.

ZXR10(config-if-interface-name)#ipv6 enable Enables the IPv6 protocol.

ZXR10(config-if-interface-name)#ipv6 address

<ipv6-address>/<prefix-length>[{eui-64|anycast}]Configures an IPv6 address on

an interface.

ZXR10(config-if-interface-name)#ipv6 address

link-local <X:X::X:X>

Configures the IPv6 link local

address of the interface.

2

ZXR10(config-if-interface-name)#ipv6 mtu <bytes> Sets the MTU of the IPv6

packets to be transmitted on

the interface.

For a description of the parameters in Step 2, refer to the following table:

Parameter Description

<ipv6-address> Specifies the address to be configured on the interface. The

address format follows RFC 2373. 16 bits form a group and

groups are separated by colons. The address may also

assume the simplified mode as defined in RFC 2373.

<prefix-length> Specifies the prefix length of the IPv6 address in decimal

system, indicating the number of consecutive most significant

bits that form the prefix in the IPv6 address.

eui-64 EUI-64 address.

anycast Anycast address identifier.

<bytes> Specifies the MTU value in the unit of bytes. The default

value depends on the specific interface type. The minimum

value is 1,280 bytes, and the value range is 1280-9202.

1.3 Maintaining IPv6 AddressesTo maintain IPv6 addresses, run the following commands:

1-13



Command Function

ZXR10#show ipv6 interface <interface-name> Shows details about the specified

IPv6 interface.

ZXR10#show ipv6 interface brief <interface-name> Shows the brief information about

the specified IPv6 address.

The following is sample output from the show ipv6 interface <interface-name> command:

ZXR10(config)#show ipv6 interface vlan10

Interface vlan10 is up, line protocol is up

IPv6 is enabled, Hardware is Vlan

HWaddr: 0022.935a.f750

index 151 Bandwidth 1000000 Kbits

IPv6 MTU is 1500 bytes

inet6 fe80::222:93ff:fe5a:f750/64

inet6 1000::2/64

DAD attemps number:3

ND reachable-time is 30000 milliseconds

ZXR10(config)#show ipv6 interface brief

vlan2 [up/down]

fe80::200:22ff:fe22:0 [tentative]

15::2/64 [tentative]

vlan10 [up/up]

fe80::222:93ff:fe5a:f750

1000::2/64

ZXR10(config)#

For a description of the sample output from the show ipv6 interface <interface-name>command, refer to the following table:

Command Output Description

IPv6 is enable Indicates that IPv6 is enabled on the interface.

Hardware is Vlan Indicates that the interface is an VLAN interface.

HWaddr Indicates the physical address.

index Indicates the interface index.

Bandwidth Indicates the bandwidth.

[tentative]/[duplicated] Indicates the IPv6 address status.

[disable/down] [disable/down] indicates that IPv6 is disabled and the

interface protocol is down; [up/down] indicates that IPv6 is

enabled and the interface protocol is down.

1-14



1.4 IPv6 Address Configuration ExampleGeneral DescriptionAs shown in Figure 1-4, the interface vlan1 of S1 and the interface vlan1 of S2 are directlyconnected with each other. It is required that S1 and S2 be able to successfully ping eachother.

Figure 1-4 IPv6 Address Configuration Example

Method1. Configure the IP addresses of the interfaces of S1 and S2.2. Check the configuration results and ensure that S1 and S2 can successfully ping each

other.

StepsS1 configuration:

S1(config)#interface vlan10

S1(config-if-vlan10)#ipv6 enable

S1(config-if-vlan10)#ipv6 address 3ffe:100::1/64

Or:



S1(config-if-vlan10)#ipv6 address link-local fe80::1111:2222:3333:4444

S1(config-if-vlan10)#exit

S2 configuration:



S2(config-if-vlan10)#ipv6 address 3ffe:100::2/64

Or:



S2(config-if-vlan10)#ipv6 address link-local fe80::5555:6666:7777:8888


VerificationVerify the configuration results on S1:

S1#show ipv6 interface brief vlan10

1-15



vlan10 [up/up]

fe80::2d1:d1ff:fe3a:7be1

3ffe:100::1/64

S1#ping6 3ffe:100::2

sending 5,100-byte ICMP echoes to 3ffe:100::2,timeout is 2 seconds.

!!!!!

Success rate is 100 percent(5/5), round-trip min/avg/max= 0/0/0 ms.

Verify the configuration results on S2:

S2#show ipv6 interface brief vlan10

vlan10 [up/up]

fe80::1422:30ff:fec4:e999

3ffe:100::2/64

S2#ping6 3ffe:100::1

sending 5,100-byte ICMP echoes to 3ffe:100::1,timeout is 2 seconds.

!!!!!

Success rate is 100 percent(5/5), round-trip min/avg/max= 0/0/0 ms.

1-16


Chapter 2NDP ConfigurationTable of Contents

NDP Overview............................................................................................................2-1Configuring NDP ........................................................................................................2-2NDP Maintenance and Diagnosis ...............................................................................2-5NDP Configuration Example.......................................................................................2-7

2.1 NDP OverviewIntroduction to NDPThe Neighbor Discovery Protocol (NDP) implements the router discovery function of theAddress Resolution Protocol (ARP) and the Internet Control Message Protocol (ICMP)as well as all functions of the redirection protocol in IPv4. It also provides a neighborunreachability detection mechanism.

When one IPv6 node appears on the network, the other IPv6 nodes on the link that directlyconnects with the node can discover the node through the neighbor discovery protocol andcan further obtain its link layer address. IPv6 nodes can also search for routers throughthe neighbor discovery protocol and maintain the reachability information of the activeneighboring nodes on the path. The neighbor discovery protocol solves the interactionsbetween nodes on the same link.

NDP PrincipleThe IPv6 NDP provides a group of solutions for solving communication-related problems.

The NDP supports address resolution, that is, it can resolve the IPv6 address of one IPv6node interface into the corresponding link layer address.

The NDP supports router discovery. A host can detect the existence of routers throughthe NDP and determine the IDs of the routers willing to forward packets.

The NDP supports prefix discovery. A router can distribute prefix information through theNDP to the other connected links.

The NDP also supports neighbor unreachability detection. A node can determine thebidirectional reachability of peer communication entities through the NDP.

All these functions of the NDP are mostly implemented by NDP packets loaded insideICMPv6 packets. For this reason, the NDP defines five types of ICMPv6 packets: RouterSolicitation (RS) packets, Router Advertisement (RA) packets, Neighbor Solicitation (NS)packets, Neighbor Advertisement (NA) packets, and redirection packets.

2-1



A router will periodically send RA packets and may also use them as a response to the RSpackets it has received from hosts. Each RA packet may also contain prefix information,link configuration information and IPv6 protocol parameters. It indicates the existence ofrouters, and routers can forward the packet. The RA packet carries the information of therouters. Such information helps a host make the next judgment for the packet to be sent.The host discovers available routers through the RA packet and constructs a list of all thediscovered routers as the default router list.

A host may send anRS packet to inquire router configuration information and router-relatedinformation. A time interval for consecutively sending RA packets has been set on eachrouter. The interval ranges from several seconds to several minutes. In order to avoidlong-time waiting before the configuration information is obtained and the communicationstarts, the host may integrate the sending of RS packets as a part of its startup process.

A node can send an NS packet to interpret the link layer address of another node so as toverify the reachability of that node and the address uniqueness of a specific link.

A node can send an NA packet as the response to an NS packet. It will also sendunsolicited NA packets to notify its own link layer address changes to other nodes.

2.2 Configuring NDPTo configure NDP, perform the following steps.


1 ZXR10(config)#interface <interface-name> Enters the interface

configuration mode.

ZXR10(config-if-interface-name)#ipv6 nd

managed-config-flag

Sets the managed-config-flag

field of the RA packets sent on

the interface, that is, sets the

value of M bit in the packets to

1.

2

ZXR10(config-if-interface-name)#no ipv6 nd

managed-config-flag

Clears the settings of the

managed-config-flag field and

restores the default value.


other-config-flag

Sets the other-config-flag field

of the RA packets sent on the

interface, that is, sets the value

of 0 bit in the packets to 1.

3


other-config-flag

Clears the settings of the

other-config-flag field and

restores the default value.

2-2


Chapter 2 NDP Configuration



prefix <ipv6-prefix>/<prefix-length> [{<valid-lifetime>

<preferred-lifetime>} | off-link | no-autoconfig]

Sets the prefix option of the

router response packets sent

on the interface.

4

ZXR10(config-if-interface-name)#no ipv6 nd prefix

<ipv6-prefix>/<prefix-length>Clears the prefix option of the

router response packets sent

on the interface.

ZXR10(config-if-interface-name)#ipv6 nd ra-interval

<seconds>

Specifies the interval for

sending router response

packets on the interface in the

unit of seconds. The value

range is 3-1800. The default

value is 600 seconds.

5


ra-interval

Restores the default

advertisement interval.

ZXR10(config-if-interface-name)#ipv6 nd ra-lifetime

<seconds>

Specifies the value of the

ra-lifetime field in the router

response packets sent on the

interface in the unit of seconds.

The value range is 0-9000. The

default value is 1,800 seconds.

6


ra-lifetime

Restores the default value of

the ra-lifetime field.


reachable-time < milliseconds>

Specifies the time within

which the remote neighbor

is considered as reachable

after the reachability of the

remote neighbor is confirmed

in the unit of milliseconds.

The default value is 30,000

milliseconds.

7


reachable-time

Restores the default time.


retransmit-time <milliseconds>

Specifies the value of the

retransmit-time field in the

router response packets

in the unit of milliseconds.

The default value is 1,000

milliseconds.

8


retransmit-time


the retransmit-time field.

2-3




ZXR10(config-if-interface-name)#ipv6 nd suppress-ra Prohibits the router from

sending router advertisement

packets.

9


suppress-ra

Enables the router to send

router advertisement packets.


ra-curhoplimit

Configures the counter limit of

router advertisement hops.

10


ra-curhoplimit

Restores the hop limit of

routing advertisement to the

default value.

ZXR10(config-if-interface-name)#ipv6 nd staled-time Configures the staled-time of

ND entities in the neighbor

cache table. The time is in unit

of minute, and in the range of

1-14400.

11


staled-time


the stale status period of the

nd entry in the neighbor's catch

table.

ZXR10(config-if-interface-name)#ipv6 nd stale-switch Configures reachability

detection before staled-time

expires.

12


stale-switch

Disables reachability detection

before staled-time expires.

By default, the reachability

detection function is not

enabled.

ZXR10(config-if-interface-name)#ipv6 nd ra-linkmtu

<mtu>

Sets the mtu field in route

advertisement. Range:

0-1500, default: 1500.

13


ra-linkmtu

Restores the default value

of the linkmtu in route

advertisement.

ZXR10(config-if-interface-name)#nd6 add

<ipv6-address><hardware-address>

Adds a static entry to the

neighbor cache table.

14

ZXR10(config-if-interface-name)#nd6 delete

<ipv6-address>

Deletes a static entry from the

neighbor cache table.

15 ZXR10#clear nd-cache Clears all the entries in the

IPv6 neighbor cache table.

2-4




ZXR10(config-if-interface-name)#ipv6 dad-attemps

<numbers>

Sets the number of times for

checking duplicate addresses

by the interface.

16

ZXR10(config-if-interface-name)#no ipv6

dad-attemps

Restores the default number

of times for checking duplicate

addresses by the interface.

ZXR10(config-if-interface-name)#ipv6 source guard {

ip-base | mac-base | mac-ip-base }[vlan {<1-4094>|default}]

Configures the mode of the

IPv6 source-guard function and

the VLAN ID.

17

ZXR10(config-if-interface-name)#no ipv6 source

guard

Disables the IPv6 source-guard

function.

ZXR10(config-if-interface-name)#ipv6 nd redirect Enables the interface

redirection function.

18

ZXR10(config-if-interface-name)#no ipv6 nd redirect Disables the interface

redirection function.

The command parameters in step 4 are described as follows:


<ipv6-prefix> Indicates the network prefix included in the RA packet.

<prefix-length> Indicates the prefix length.

<valid-lifetime> Indicates the valid lifetime of the prefix in the unit of seconds.

The default value is 604800 seconds.

<preferred-lifetime> Indicates the preferred lifetime in the unit of seconds. The

default value is 86400 seconds.

no-autoconfig Indicates that the hosts on the link cannot use the prefix for

IPv6 address auto configuration.

off-link Indicates that the L bit (Online flag) of the prefix is not set. By

default, the flag bit is set to 1.

If this flag is set to 1, it indicates that the prefix can be used

to determine whether addresses are online, that is, all the

addresses belonging to this prefix are online if this flag is

set whereas some addresses may be online but the other

addresses are offline if this flag is not set.

2.3 NDP Maintenance and DiagnosisThe ZXR10 5900E provides the following show commands to maintain the NDP:

2-5



Command Function

ZXR10#show nd6 cache Shows the IPv6 neighbor cache

table. The display results show

not only the entries generated by

the ND protocol for the routes to

neighbors but also static neighbor

cache entries.

The following example shows the outputs of the command show nd6 cache. This commandcan be run to check the static ND entries and the ND entries dynamically learned includingthe MAC address, the entry status, the age of this status, and the corresponding interfacename:

ZXR10#show nd6 cache

Total Cache Number Is:5

Only Current Valid Items Are Shown Below:

Address Link-Address Age Status Interface

106::2 0022.19a4.fe7a 4s Delay vlan52

fe80::2d0:ff:fe57:1000 00d0.0057.1000 3s Delay vlan500

fe80::200:65ff:fe3e:19f9 0000.653e.19f9 22s Reachable vlan10

2000::2 0000.653e.19f9 13s Reachable vlan10

The outputs of the command show nd6 cache are described as follows:


Address Indicates the IP address.

link-Address Indicates the link layer address.

age Indicates the age of the entry in this status or other attributes.

infinity: Indicates that the corresponding interface address

is infinitely valid.

static: Indicates that the entry is a static entry infinitely valid.

status Indicates the status of the ND entry. Incomplete: The

entry has been generated but the link layer address is not

determined because address resolution is under way.

Reachable: The known entry is recently reachable.

Stale: The known entry is recently unreachable. If

stale-switch function is configured, the neighbor reachability

is before the entity is deleted. Otherwise, the neighbor

reachability is not verified until there are communication

messages to the neighbor.

Delay: The known entry is recently unreachable and there are

communication messages to the neighbor. In this status, the

NS packet (also called the probe packet) will be delayed for a

period of time to provide the opportunity for the upper-layer

protocol to verify the reachability of the neighbor.

2-6




Probe: The neighbor reachability is indeterminate. A probe

message is sent to verify the reachability.

Interface Indicates the interface name of the entry.

2.4 NDP Configuration ExampleGeneral DescriptionThis example describes how to configure static entries in the NDP neighbor cache tableof the interface VLAN10 on a switch.

Method1. Enter the interface configuration mode, and add a static entry to the neighbor cache

table.2. Show the content of the neighbor cache table, and check whether the static entry has

been successfully added.

StepsRouter configuration:

ZXR10(config)#interface vlan10

ZXR10(config-if-vlan10)#nd6 add 780::1 0000.0a00.1345

VerificationVerify the configuration results on the router:

ZXR10#show nd6 cache

Total Cache Number Is:1

Only Current Valid Items Are Shown Below:

Address link-Address age status Interface

780::1 0000.0a00.1345 static Reachable vlan10

The above results indicate that a static entry has been successfully added to the NDPneighbor cache table.

2-7




2-8


Chapter 3IPv6 Tunnel ConfigurationTable of Contents

IPv6 Tunnel Overview ................................................................................................3-1Configuring IPv6 Tunnel .............................................................................................3-4IPv6 Tunnel Configuration Examples..........................................................................3-6

3.1 IPv6 Tunnel OverviewIntroduction to IPv6 TunnelTunneling is an encapsulation technology used to transmit another network protocolthrough the use of one network protocol, that is, it utilizes one network transfer protocolto encapsulate the data packets generated by other protocols into its own packets beforethe packets are transmitted in the network.

The IPv6 over IPv4 tunnel mechanism is used to add an IPv4 header in the front of theIPv6 data packet and then transfer the IPv6 packet through a tunnel so that the IPv6packet traverses the IPv4 network to implement the interworking between two isolatedIPv6 networks, as shown in Figure 3-1.

Figure 3-1 Principles of the IPv6 over IPv4 Tunnel Mechanism

An IPv6 over IPv4 tunnel can be established between two hosts, between a host and arouter, or between two routers. The termination point of the tunnel may be the ultimatedestination of the IPv6 packet, or the packet may still need to be further forwarded.Therefore, tunnels are classified into configured tunnels and automatic tunnels based onthe ways to obtain the destination IPv4 address of a tunnel.

l If the termination address of the IPv6 over IPv4 tunnel cannot be automaticallyobtained from the destination address of the IPv6 packet but needs to be manually

3-1



configured, the tunnel is called a configured tunnel, such as a 6in4 tunnel or a GREtunnel.

l If the interface address of the IPv6 over IPv4 tunnel assumes a specialIPv4-embedded IPv6 address format (i.e. the IPv4 address of the tunnel terminationpoint can be automatically obtained from the destination address of the IPv6 packet),the tunnel is called an automatic tunnel, such as a 6to4 tunnel or an ISATAP tunnel.

There is another type of IPv4 or IPv6 over IPv6 tunnel (see RFC 2473). The protocolencapsulates an IPv4 or IPv6 data packet so that the encapsulated data packet can betransmitted in another IPv6 network. The data packet after the encapsulation is an IPv6tunnel packet, as shown in Figure 3-2.

Figure 3-2 Principles of the IPv4 (or IPv6) over IPv4 Tunnel

In the above figure, Original data refers to the IPv4 or IPv6 packet.

IPv6 Tunnel Principlel 6in4 Tunnel

Figure 3-3 shows the operating principles of a 6in4 tunnel.

Figure 3-3 Principles of a 6in4 Tunnel

The 6in4 tunnel involves a tunnel encapsulation and decapsulation process.

à Encapsulation: If the packet egress interface is a tunnel interface when an IPv6host or router or switch sends an IPv6 flow, the host or router first determinesthe tunnel type. If the tunnel is a 6in4 tunnel, the host or router implements IPv4

3-2


Chapter 3 IPv6 Tunnel Configuration

header encapsulation. During the encapsulation, the source and destinationaddresses of the IPv4 header are manually configured by the user. Theencapsulated packet is then sent according to the IPv4 packet sending process.

à Decapsulation: The process is just contrary to the encapsulation process. If theprotocol number in the IPv4 header of the received IPv4 packet is 41, the host orrouter proceeds to the 6in4 decapsulation process and searches for the matchedtunnel number according to the source and destination addresses of the packet.If the tunnel number is found, the host or router removes the IPv4 header addedduring tunnel encapsulation and delivers the remaining IPv6 packet to the IPv6packet receiving process for further handling.

l 6to4 Tunnel

Figure 3-4 shows the operating principles of a 6to4 tunnel.

Figure 3-4 Principles of a 6to4 Tunnel

A 6to4 tunnel is a point-to-multipoint auto tunnel used to connect multiple isolated IPv6sites through an IPv4 network to an IPv6 network. It makes possible the automaticacquisition of the IPv4 address at the termination point of the tunnel by embedding anIPv4 address in the destination address of an IPv6 packet.

The 6to4 tunnel assumes a special 6to4 address in the format of2002:abcd:efgh:Subnet ID::InterfaceID/64. Of the address, 2002 is a fixed IPv6address prefix, abcd:efgh is a globally unique 32-bit IPv4 source address of the 6to4tunnel in hexadecimal system (e.g. 1.1.1.1 can be expressed as 0101:0101), andthe rest portion uniquely identifies the position of a host in a 6to4 network. As thetermination point of the tunnel can be automatically determined by this embeddedIPv4 address, tunnel establishment becomes very convenient.

Because the 16-bit subnet ID in the 64-bit address prefix of the 6to4 address can beuser-defined whereas the first 48 bits of the prefix are a fixed number or determined bythe IPv4 address of the device at the start or termination point of a tunnel, it becomespossible to forward IPv6 packets over the tunnel. The 6to4 tunnel makes possible theinterconnection of two IPv6 networks through an IPv4 network and thus conquers thelimitations of automatic IPv4-compatible IPv6 tunnels in practical use.

The 6to4 tunnel involves a tunnel encapsulation and decapsulation process.

3-3



à Encapsulation: If the egress interface of the sent IPv6 packet is a tunnel interface,the host first determines the tunnel type. If the tunnel is a 6to4 tunnel, the hostimplements IPv4 header encapsulation. During the encapsulation, the sourceaddress is user-configured whereas the destination address is obtained fromthe destination address of the packet. The encapsulated packet is then sentaccording to the IPv4 packet sending process.

à Decapsulation: If the protocol number in the IPv4 header of the received IPv4packet is 41, the host proceeds to the 6to4 decapsulation process and searchesfor the matched tunnel number according to the source address of the packet.If the tunnel number is found, the host removes the IPv4 header added duringtunnel encapsulation and delivers the remaining IPv6 packet to the IPv6 packetreceiving process for further handling.

3.2 Configuring IPv6 TunnelConfiguring 6in4 TunnelTo configure a 6in4 tunnel, perform the following steps:


1 ZXR10(config)#interface v6_tunnel<tunnel_no> Creates an IPv6 tunnel

interface. To delete the tunnel

interface, use the no format of

the command.

The parameter <tunnel_no>

indicates the tunnel number.

The number of tunnel interfaces

that can be created ranges

from 1 to 512.

2 ZXR10(config)#ipv6-tunnel-config Enters the IPv6 tunnel

configuration mode.

3 ZXR10(config-ipv6-tunnel)#interface v6_tunnel<tunne

l_no>

Enters the IPv6 tunnel interface

configuration mode.

4 ZXR10(config-ipv6-tunnel-if-v6_tunnel1)#tunnel

mode ipv6ip 6in4

Sets the current tunnel mode

to 6in4. To cancel the current

tunnel mode, use the no format

of the command.


source ipv4<ipv4-address>

Specifies the source address

of the tunnel. To delete the

source address configuration

of the tunnel, use the no format

of the command.

3-4





destination ipv4<ipv4-address>

Specifies the destination

address of the tunnel. To

delete the destination address

configuration of the tunnel, use

the no of the command.

Configuring 6to4 TunnelTo configure a 6to4 tunnel, perform the following steps:


1 ZXR10(config)#interface v6_tunnel1<tunnel_no> Creates an IPv6 tunnel

interface. To delete the tunnel

interface, use the no format of

the command.

The parameter <tunnel_no>

indicates the tunnel number.

The number of tunnel interfaces

that can be created ranges

from 1 to 512.

2 ZXR10(config)#ipv6-tunnel-config Enters the IPv6 tunnel

configuration mode.

3 ZXR10(config-ipv6-tunnel)#interface v6_tunnel<tunne

l_no>

Enters the IPv6 tunnel interface

configuration mode.


mode ipv6ip 6to4

Sets the current tunnel mode

to 6to4. To cancel the current

tunnel mode, use the no format

of the command.


source ipv4 <src_address>

Specifies the source address

of the tunnel. To delete the

source address configuration

of the tunnel, use the no format

of the command.

3-5



3.3 IPv6 Tunnel Configuration Examples

3.3.1 6in4 Tunnel Configuration Example

Configuration DescriptionAs shown in Figure 3-5, suppose S1 and S2 are dual-stack routers whereas PC1 and PC2are IPv6 hosts. This example describes how to configure a 6in4 tunnel.

Figure 3-5 6in4 Tunnel Configuration Example

Configuration ThoughtThe 6in4 tunnel is of v6 nature and thus IPv6 needs to be enabled. The source addressof the tunnel is the IPv4 address of the local router, whereas the destination address isthe IPv4 address of the peer router. There must be a route for interworking between thesource address and the destination address of the tunnel (via the IPv4 routing protocol,the static routing protocol or other routing protocols).

1. Create 6in4 tunnel interfaces and enable IPv6 on them.2. Enter the tunnel configuration mode from the global mode, and then enter the 6in4

tunnel interface to be configured.3. Configure the tunnel mode, the source address, and the destination address.

Configuration CommandsS1 configuration:

S1(config)#interface v6_tunnel3

S1(config-if-v6_tunnel3)#ipv6 enable

S1(config-if-v6_tunnel3)#ipv6 address 3172::27/64

S1(config-if-v6_tunnel3)#exit

S1(config)#ipv6-tunnel-config

S1(config-ipv6-tunnel)#interface v6_tunnel3

S1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel mode ipv6ip 6in4

S1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel destination ipv4 33.1.1.28

S1(config-ipv6-tunnel-if-v6_tunnel3)#tunnel source ipv4 33.1.1.27

3-6



S1(config-ipv6-tunnel-if-v6_tunnel3)#exit

S1(config-ipv6-tunnel)#exit


S1(config-if-vlan10)#ip address 33.1.1.27 255.255.0.0

S2 configuration:



S2(config-if-v6_tunnel3)#ipv6 address 3172::28/64

S2(config-if-v6_tunnel3)#exit



S2(config-ipv6-tunnel-if-v6_tunnel3)#tunnel mode ipv6ip 6in4

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


S2(config-ipv6-tunnel-if-v6_tunnel3)#exit

S2(config-ipv6-tunnel)#exit


S2(config-if-vlan10)#ip address 33.1.1.28 255.255.0.0

Configuration VerificationCheck the tunnel configurations on S1 and verify whether the configurations have takeneffect:

S1(config)#show running-config-interface v6_tunnel3

! <INTERFACE>

interface v6_tunnel3

index 49

ipv6 enable

ipv6 address 3172::27/64

!

! </INTERFACE>

! <V6_TUNNEL>

ipv6-tunnel-config


tunnel mode ipv6ip 6in4

tunnel source ipv4 33.1.1.27

tunnel destination ipv4 33.1.1.28

! </V6_TUNNEL>

S1(config)#show ip interface vlan4

vlan4 AdminStatus is up, PhyStatus is up, line protocol is up

Internet address is 33.1.1.27/16

Broadcast address is 255.255.255.255

IP MTU is 1500 bytes

3-7



S1(config)#show ipv6 interface brief

v6_tunnel3 [up/up]

fe80::2d0:d0ff:fe52:abcf

3172::27/64

3.3.2 6to4 Tunnel Configuration Example

Configuration DescriptionAs shown in Figure 3-6, suppose S1 and S2 are dual-stack routers whereas PC1 and PC2are IPv6 hosts. This example describes how to configure a 6to4 tunnel.

Figure 3-6 6to4 Tunnel Configuration Example

Configuration ThoughtA 6to4 tunnel is of v6 nature and thus IPv6 needs to be enabled to connect the 6to4 nodeprefixed with 2002::/16. The source end of the tunnel is bound with the IPv4 address ofthe local router, and no destination address is required. The tunnel address must assumea 2002::/16 prefix.

1. Create a 6to4 tunnel, configure IPv6 addresses, and enable IPv6. The first 48 bits ofthe tunnel address and the 6to4 sites are of a fixed format and generated according tothe source IPv4 address of the tunnel: Convert the x.x.x.x of the source IPv4 addressof the tunnel into a hexadecimal yyyy:yyyy, and then add 2002::/16 to it to form a 48-bitprefix 2002:yyyy:yyyy::/48.

2. Enter the tunnel configuration mode from the global mode, and then enter the 6to4tunnel interface to be configured.

3. Configure the tunnel mode and the source address.4. Advertise the tunnel route through static routing or BGP4+.



3-8



S1(config-if-v6_tunnel2)#ipv6 address 2002:0101:0101::1/64


S1(config-if-v6_tunnel2)#!



S1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip 6to4

S1(c config-ipv6-tunnel-if-v6_tunnel2)#tunnel source ipv4 1.1.1.1

S1(config-ipv6-tunnel-if-v6_tunnel2)#!

S1(config)#ipv6 route 2002::/16 v6_tunnel2

S2 configuration:


S2(config-if-v6_tunnel2)#ipv6 address 2002:0101:0102::1/64





S2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip 6to4




Configuration VerificationCheck the tunnel configurations on S1 and verify whether the configurations have takeneffect:


! <INTERFACE>


index 1348

ipv6 enable

ipv6 address 2002:101:101::1/48

!

! </INTERFACE>

! <V6_TUNNEL>

ipv6-tunnel-config


tunnel mode ipv6ip 6to4


! </V6_TUNNEL>

S1(config)#show ipv6 interface brief

v6_tunnel2 [up/up]

fe80::2d0:d0ff:fe52:abcf

2002:101:101::1/64

3-9




3-10


Chapter 4IPv6 ACL ConfigurationTable of Contents

IPv6 ACL Overview ....................................................................................................4-1Configuring IPv6 ACL.................................................................................................4-1IPv6 mixed-ACL Maintenance and Diagnosis .............................................................4-7IPv6 ACL Configuration Example ...............................................................................4-9

4.1 IPv6 ACL OverviewThe Access Control List (ACL) is a kind of flow classification policies used to implementnumerous functions such as port-ACL, Unicast Reverse Path Forwarding (URPF) andpolicy routing.

The IPv6 ACL mechanism is used to filter packets by the fields in IPv6 packets. One IPv6ACL can have multiple rules, with each rule describing certain matching conditions. Fora given packet, matching starts from the first rule. Once a packet matches a certain rule,the permit or deny action set in the rule is returned.

4.2 Configuring IPv6 ACLConfiguring IPv6 ACLTo configure IPv6 ACL, perform the following steps.


ZXR10(config)#ipv6-access-list <acl-name> Configures the specified IPv6

ACL.

1

ZXR10(config)#no ipv6-access-list <acl-name> Deletes the specified IPv6

ACL.

4-1




ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit |

deny}{source | any }{ destination | any }[ time-range<name>]

Configures the IPv6 ACL rule

based on the source address.

ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit | deny}

protocol {source | any}{destination | any}[{dscp <value>}][

time-range <name>][traffic-class<value>]

Configures the extended IPv6

ACL rule.


deny} tcp {source | any}[oper <source-port>]{destination| any}[oper <destination-port>][{dscp <value>}][es

tablish][fin][psh][range][rst][syn][urg][ time-range<name>][traffic-class<value>]


based on TCP.


deny} udp {source | any}[oper <source-port>]{destination |any}[oper <destination-port>][{dscp <value>}][ time-range<name>][traffic-class<value>]


based on UDP.

ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit

| deny} icmp {source | any }{destination | any}[

icmp-type |icmp-code][{dscp <value>}][ time-range<name>][traffic-class<value>]


based on ICMP.

2

ZXR10(config-ipv6-acl)#rule [<rule-id>]{permit | deny}

protocol {source | any }{destination | any}[ authen][ destopts][

esp][ fragments][ hop-by-hop][ routing][ time-range<name>][traffic-class<value>]

This configures an ACL with an

IPv6 extended header.

ZXR10(config-ipv6-acl)#no rule {<rule-id>| all} Deletes the specified IPv6 ACL

rule or all rules.

3

ZXR10(config-ipv6-acl)#move < target-rule-id><

target-New-rule-id>

Move the ACL.

ZXR10(config)#ipv6-access-group {interface<interface-name>}{ingress | egress<acl-name>}

Binds the specified IPv6 ACL

to the specified interface.

4

ZXR10(config)#no ipv6-access-group {ingress | egress} Deletes the bound IPv6 ACL

from the specified interface.

ZXR10(config)#interface <interface-name> Enters the interface

configuration mode.

ZXR10(config-if)#ipv6-access-group <interface-name>{i

ngress | egress}<acl-name>

Binds the specified IPv6 ACL in

interface configuration mode.

5

ZXR10(config-if)#no ipv6-access-group {ingress | egress} Deletes the bound IPv6 ACL in

interface configuration mode.


4-2


Chapter 4 IPv6 ACL Configuration


<rule-id> Indicates the unique identity of a rule in the IPv6 ACL table.

This ID determines the sequence of the rule in the IPv6 ACL

table. It ranges from 1 to 2147483644.

If this parameter is not specified, the system inserts the rule

to the end of the table by default and allocates the rule-id

according to the default base and increment.

permit Indicates that the rule is the permit rule.

deny Indicates that the rule is the deny rule.

protocol Indicates the protocol type to be matched, which can be one

of the keywords "tcp", "udp" and "ip", or can be an integer

representing the IP protocol number and ranging from 0

to 255. If this parameter is set to "ip", it indicates that any

protocol type is matched.

source Indicates the source IPv6 address.

destination Indicates the destination IPv6 address.

oper Indicates the port operation type, which can be any of the

keywords "eq", "ge", "le", and "range". If this parameter is set

to "range", two port numbers need to be specified behind

"range".

<source-port> Indicates the source port number ranging from 0 to 255.

<destination-port> Indicates the destination port number ranging from 0 to 255.

dscp <value> Indicates the DSCP field. The value range is 0-63.

traffic-class<value> Indicates the traffic-class field. The value range is 0-255.

established, fin, rst, ack, urg, psh, syn Indicates TCP link establishment. This parameter is valid

for TCP only.

authen, destopts, esp, fragments,

hop-by-hop, routing

Fields in an IPv6 extended header.



ingress Indicates that the IPv6 ACL is bound to the ingress direction

of the interface.

egress Indicates that the IPv6 ACL is bound to the egress direction

of the interface.

Configuring IPv6-MIXED-ACLTo configure the IPv6-MIXED-ACL on ZXR10 5900E, use the following commands:

4-3




ZXR10(config)#ipv6-mixed-access-list <name> Configures an ACL list.1

ZXR10(config)#no ipv6-mixed-access-list <name> To delete the ACL list, use this

command.

ZXR10(config-ipv6-mixed-acl)#rule [<rule-id>]{permit

| deny}[{link-protocol<value>|[{source-mac<sourcemac-wildcard>| any }][{ inner-cos <value>| inner-vlan<value>| outer-cos <value>| outer- vlan <value>}]

protocol {source | any}{destination | any}[{dscp <value>}][

time-range <name>]

Configures the LINK ACL

based and extension based

IPv6 ACL rule.


| deny}[{link-protocol<value>|[{source-mac<sourcemac-wildcard>| any }][{ inner-cos <value>| inner-vlan<value>| outer-cos <value>| outer- vlan <value>}] tcp

{source | any}[oper <source-port>]{destination | any}[oper<destination-port>][{dscp <value>}][establish][fin][psh][rang

e][rst][syn][urg][ time-range <name>]


based and TCP based IPv6

ACL rule.


| deny}[{link-protocol<value>|[{source-mac<sourcemac-wildcard>| any }][{ inner-cos <value>| inner-vlan<value>| outer-cos <value>| outer- vlan <value>}] udp

{source | any}[oper <source-port>]{destination | any}[oper<destination-port>][{dscp <value>}][ time-range <name>]


based and UDP based IPv6

ACL rule.


| deny}[{link-protocol<value>|[{source-mac<sourcemac-wildcard>| any }][{ inner-cos <value>| inner-vlan<value>| outer-cos <value>| outer- vlan <value>}]

icmp {source | any }{destination | any}[ icmp-type

|icmp-code][{dscp <value>}][ time-range <name>]


based and ICMP based IPv6

ACL rule.

2


deny}[{link-protocol<value>|[{source-mac<sourcemac-wildcard>| any }][{ inner-cos <value>| inner-vlan<value>| outer-cos <value>| outer- vlan <value>}] protocol

{source | any }{destination | any}[ authen][ destopts][

esp][ fragments][ hop-by-hop][ routing][ time-range<name>][traffic-class<value>]


based IPv6 ACL rule that

carries the IPv6 extension

prefix.

3 ZXR10(config-ipv6-mixed-acl)#move < target-rule-id><

target-New-rule-id>

Moves an ACL rule.

4 ZXR10(config-ipv6-mixed-acl)#no rule {<rule-id>| all } Deletes an ACL rule/all rules.

Command parameters are describes as follows:

4-4




<rule-id> Indicates the unique identity of a rule in the ACL. This

ID determines the sequence of the rule. Range: 1 to

2147483646.

If this parameter is not set, the system inserts the rule to the

end of the ACL by default and sets the rule-id according to

the default base and increment.

permit Keyword indicating that the rule is a permit rule.

deny Keyword indicating that the rule is a deny rule.

protocol Protocol type to be matched, which can be set to "tcp", "udp"

or "ip", or an integer representing the IP protocol number

ranging from 0 to 255. If this parameter is set to "ip", it

indicates that any protocol type is matched.

source Source IPv6 address, in the form of dotted decimal notation

<source-wildcard> Wildcard mask of the source IPv6 address, in the form of

dotted decimal notation.

destination Destination IPv6 address, in the form of dotted decimal

notation.

<sdestination-wildcard> Wildcard mask of the destination IPv6 address, in the form of

dotted decimal notation.

oper Port operation type, which can be any of the keywords "eq",

"ge", "le", and "range". If this parameter is set to "range", two

port numbers need to be specified behind "range".

source-port Source port number, range: 0 to 65535.

destination-port Destination port number, range: 0 to 65535

precedence <value> Precedence. Range: 0 to 7

established ,fin,rst,ack,urg,psh,syn Keywords for TCP link establishment. This parameter is valid

for TCP only.

dscp <value> DSCP field, range: 0 to 63.

authen,destopts, esp, fragments,

hop-by-hop, routing

IPv6 extension prefix field.

time-tange Time range.

established Keyword for TCP link establishment. This parameter is valid

for TCP only.

link-protocol Type of the level 2 protocol to be matched. Value: 34525.

source-mac Source MAC address, in the form of dotted hexadecimal

notation.

4-5




<source-mac-wildcard> Wildcard mask of the source MAC address, in the form of

dotted hexadecimal notation.

destination-mac Destination MAC address, in the form of dotted hexadecimal

notation.

<destination-mac-wildcard> Wildcard mask of the destination MAC address, in the form of

dotted hexadecimal notation.

inner-cos Priority of the VLAN header for the inner layer, range: 0 to 7.

inner-vlan ID of the VLAN header for the inner layer, range: 1 to 4094.

outer-cos Priority of the VLAN header for the outer layer, range: 0 to 7.

outer-vlan ID of the VLAN header for the outer layer, range: 1 to 4094.

Tip:

If the IPv6-MIXED-ACL is bound to the egress direction, IPv6-MIXED-ACL is not valid.

Bind the VLAN to the IPv6 ACLTo bind the VLAN to the IPv6 ACL on the ZXR10 5900E, perform the following steps:


ZXR10(config)#ipv6-access-group vlan <vlan-id>{ingress |

egress}

The IPv6 ACL bound on the

VLAN.

1

ZXR10(config)#no ipv6-access-group vlan

<vlan-id>{ingress | egress}

Deletes the IPv6 ACL bound

on the VLAN.

ZXR10(config)#ipv6-mixed-access-group vlan


Binds mixed v6 ACL on the

VLAN.

2

ZXR10(config)#no ipv6-mixed-access-group vlan


Deletes the bound mixed v6

ACL on the VLAN.



ingress Indicates that the ACL is bound to the ingress direction of

the interface.

egress Indicates that the ACL is bound to the egress direction of

the interface.

4-6



Tip:

If the IPv6-MIXED-ACL is bound on the VLAN, and the bound VLAN is inconsistent withthe out-vlan in the rule, the bound VLAN is used as the out-vlan.

4.3 IPv6 mixed-ACL Maintenance and DiagnosisIPv6 ACL Maintenance and DiagnosisTo maintain and diagnose IPv6 ACLs, use the following commands.

Command Function

ZXR10(config)#show ipv6-access-lists [{name <a

cl-name>[{from<value>|to <value>}]|[ brief [name<acl-name>]|[config]}[|{begin|exclude|include}]

Shows the IPv6 ACL list or brief

information.

ZXR10(config)#show ipv6-access-groups [{by-access-list<acl-name>|by-direction {ingress | egress}|by-interface-or-vlan<interface-name or vlan- id>by-interface <interface-name>}]

Shows the IPv6 ACL binding

information. The information can

be selectively displayed according

to the command parameters.

ZXR10(config)#show running-config ipv6-acl Shows the entire IPv6 ACL

information.

ZXR10(config)#show running-config port-acl Shows all the IPv6 ACL binding

information (and the IPv4 ACL

binding information as well if any

IPv4 ACL is bound).

ZXR10(config)#show running-config-interface port-acl

[<interface-name>]

Shows the IPv6 ACL binding

information related to a certain

interface (and the IPv4 ACL

binding information as well if any

IPv4 ACL is bound).

The command parameters are described as follows.

Command Function

<acl-name> Shows IPv6 ACL information by the specified ACL name.

ingress/egress Shows ACL information by the ingress or egress.

<interface-name> Shows ACL information by the interface name.

[<interface-name>] Shows the ACL (IPv4 and IPv6) binding information related

to a certain interface.

4-7



The following example shows the outputs of the commandshow ipv6-access-lists:

ZXR10(config)#show ipv6-access-lists

ipv6-access-list kkk

1/1 (showed/total)

10 permit tcp 200:300::400:500/64 any

The following example shows the outputs of the command show ipv6-access-groups:

ZXR10(config)#show ipv6-access-groups

Interface name Direction ACl name

--------------------------------------------------------

gei-0/1/1/1 Ingress kkk

The following example shows the outputs of the command show running-config port-acl:

ZXR10(config)#show running-config port-acl

! <PORT_ACL>

interface gei-0/1/1/1

ipv4-access-group ingress lll

!


ipv6-access-group ingress kkk

!

! </PORT_ACL>

The following example shows the outputs of the command show running-config-interfaceport-acl [<interface-name>]:

ZXR10(config)#show running-config-interface port-acl gei-0/1/1/1

! <PORT_ACL>


ipv4-access-group ingress lll

!


ipv6-access-group ingress kkk

!

! </PORT_ACL>

The outputs of the command show ipv6-access-groups are described as follows.


Interface name Indicates the name of the interface bound with the IPv6 ACL.

Direction Indicates the IPv6 ACL binding direction.

ACl name Indicates the IPv6 ACL name such as "kkk" for the IPv6 ACL

described in this example.

IPv6 mixed-ACL Maintenance and DiagnosisTo maintain and diagnose MIXED-ACL, use the following commands.

4-8



Command Function

ZXR10#show ipv6-mixed-access-lists name<acl-name>[{from<valu

e>|to <value>}|{begin|exclude|include}]

Shows the ACL list.

ZXR10#show ipv6-mixed-access-lists brief {name<acl-name>|[|{begin|exclude|include}]}

Shows the brief information.

ZXR10#show ipv6-mixed-access-lists |{begin|exclude|include} Shows the ACL list

ZXR10#show ipv6-mixed-access-lists config [{begin|exclude|inclu

de}]

Shows the ACL configured in the

system database.

ZXR10#show ipv6-mixed-access-groups[{by-access-list<acl-name>|by-direction {ingress | egress}|by-interface<interface-name>}]

hows the ACL binding information.


Parameter Function

<acl-name> Shows IPv6 MIXED ACLinformation by the specified ACL

name.

ingress | egress Shows ACL information by the ingress or egress.

<interface-name> Shows ACL information by the interface name.

[<interface-name>] Shows the ACL (IPv4 and IPv6) binding information related

to a certain interface.

4.4 IPv6 ACL Configuration ExampleGeneral DescriptionIn the network as shown in Figure 4-1, suppose both PC1 and PC2 send telnet requeststhrough S2 to S1. S1 expects to receive the login requests of PC1 only but not the loginrequests of PC2. Then an ACL can be bound to the ingress direction of the interfacegei-0/1/1/3 to filter out the telnet packets from PC2 (or the ACL may be bound to the egressdirection of the interface gei-0/1/1/4).

4-9



Figure 4-1 IPv6 ACL Configuration Example

In this case, it is only necessary to create one ACL and add the following rule to thisACL: Deny the telnet packets matching the IP address of PC2 and using the protocol typeTCP and the port type telnet. Then bind the ACL to the ingress direction of the interfacegei-0/1/1/3 or the egress direction of the interface gei-0/1/1/4.

After the above configuration is completed, the requests initiated by PC2 will not reach S1but will be discarded when they reach S2 even if PC2 has obtained the telnet usernameand password of S1. The other communications of S1 and PC2, however, will not beaffected.

Method1. First create an ipv6-access-list. During the creation, a customized name can be

assigned to this list but the length of the name shall not exceed 31 characters.2. Enter the IPv6 ACL configuration mode after the list is created and then add rules. A

packet type can be specified for each rule, and the permit or deny action applies tothe packet type.

3. Bind the customized ipv6-access-list to the ingress or egress direction of the interfaceto which traffic filtering applies.


S2(config)#ipv6-access-list test

S2(config-ipv6-acl)#rule deny tcp 100:1::1:2/128 eq 23 110:1::1:2/128

S2(config-ipv6-acl)#rule permit ip any any

S2(config-ipv6-acl)#exit

S2(config)#ipv6-access-group gei-0/1/1/3 ingress test

VerificationCheck the configured ACL in one of the following three modes:

/*Check all the ACLs on the router. In this mode, all the names

and number of ACLs are shown.*/

4-10



S2(config)#show ipv6-access-lists brief

No. ACL RuleSum

-------------------------------------------------------

1 test 2

/*Check the ACL of the specified name. In this mode, information

about the number of rules of the specified ACL is shown.*/

S2(config)#show ipv6-access-lists name test

ipv6-access-list test

2/2 (showed/total)

10 deny tcp 100:1::1:2/128 eq telnet 110:1::1:2/128

20 permit ip any any

/*Check the details of all ACLs on the router. In this mode,

information about the number of rules of each ACL is shown.*/

S2(config)#show ipv6-access-lists

ipv6-access-list test

2/2 (showed/total)

10 deny tcp 100:1::1:2/128 eq telnet 110:1::1:2/128

20 permit ip any any

Check the interface bound with the ACL. Two methods are available for checking thebinding between the ACL and the interface:

/*Check the binding between IPv6 ACLs on the router and the

related interfaces*/

S2(config)#show ipv6-access-groups

Interface name Direction ACl name

------------------------------------------------------

gei-0/1/1/3 Ingress test

/*Check the binding between the specified interface and the

corresponding ACL*/

S2(config)#show running-config-interface port-acl gei-0/1/1/3

! <PORT_ACL>


ipv6-access-group ingress test

!

! </PORT_ACL>

/*Check the binding between all ACLs on the router and the

related interfaces, including IPv4 ACLs and IPv6 ACLs*/

S2(config)#show running-config port-acl

! <PORT_ACL>


ipv4-access-group ingress 1K

4-11



!


ipv6-access-group ingress test

!

! </PORT_ACL>

4-12


Chapter 5IPv6 Static RouteConfigurationTable of Contents

IPv6 Static Route Overview........................................................................................5-1Configuring IPv6 Static Routes...................................................................................5-1Maintaining IPv6 Static Routes...................................................................................5-2IPv6 Static Route Configuration Example ...................................................................5-4

5.1 IPv6 Static Route OverviewStatic routes refer to the routes that the network administrator creates by usingconfiguration commands in the routing table. Static routing is different from dynamicrouting that creates a routing table according to the routing algorithm.

When dynamic routing is applied, sometimes it is necessary to send the routes of theentire Internet to a router and then the router can hardly tolerate such a huge load. In thatcase, static routing can be applied to solve the problem. With static routing, only a fewconfigurations are required to eliminate the use of dynamic routes.

In a routing environment involving multiple routers and multiple paths, however, it is rathercomplex to configure static routes.

The static unicast routing table is configured by the network administrator according tohis/her routing requirements after he/she gets familiar with the entire network topology.Therefore, the network administrator can exactly control routing behaviors in the network.When the network topology changes, however, the network administrator needs toreconfigure the static routing table.

Unlike dynamic routing protocols, static routing does not require the setting of protocoldata on the related interfaces but requires only the validity check of the user-configuredstatic routing parameters such as destination address, mask length, next hop and egressinterface. The validity of each configured static route, however, still depends on the statusof the egress interface.

5.2 Configuring IPv6 Static RoutesTo configure IPv6 static routes, run the following commands:

5-1



Command Function

ZXR10(config)#ipv6 route [vrf <vrf-name>]<prefix>/<mask-len><interface-name>[<distance-metric>][bfd enable]

Configures a static route with the

specified egress interface. If the

egress interface is a broadcast

interface, the next hop should also

be specified.

ZXR10(config)#ipv6 route <prefix>/<mask-len><forwarding-router's-address>[<distance-metric>][bfd enable]

Configures a static route with the

specified next hop.

ZXR10(config)#ipv6 route <prefix>/<mask-len><interface-name><forwarding-router's-address>[<distance-metric>][bfd enable]

Configures a static route with both

the specified egress interface and

the specified next hop.

For a description of the parameters, refer to the following table:


<vrf-name> Used to configure static route in a specific VRF. The VRF

name is with 1–32 characters. The management port mng

is a special VRF.

<prefix> Indicates the IPv6 address prefix.

<mask-len> Indicates the mask length ranging from 0 to 128.

<forwarding-router's-address> Indicates the next-hop IPv6 address.

<interface-name> Indicates the interface name.

<distance-metric> Indicates the administrative distance ranging from 1 to 255.

bfd enable Enables the BFD for the route in the IPv6 route configuration.

5.3 Maintaining IPv6 Static RoutesTo maintain IPv6 static routes, run the following commands:

Command Function

ZXR10(config)#show running-config ipv6-static-route Shows the static routes configured

in the system database.

ZXR10(config)#show ipv6 protocol routing static Shows the static routes in the

routing table and the validity of

these routes.

Run the show running-config ipv6-static-route command to show the static routesconfigured in the system database. The display results indicate the user-configured staticroutes but these routes are not necessarily effective.

5-2


Chapter 5 IPv6 Static Route Configuration

Run the show ipv6 protocol routing static command to show the static routing table of therouter and check the validity of the static routes in the routing table. This command is oftenused during the maintenance and diagnosis of routing protocols.

The following is a sample output from the show running-config ipv6-static-route command:

ZXR10(config)#show running-config ipv6-static-route

! <NSM>

ipv6 route 2002::/16 v6_tunnel2

ipv6 route 1::/64 null1

ipv6 route 457::/64 null1

ipv6 route 3::/64 null1 1

ipv6 route 0::/0 loopback1

ipv6 route 23::/56 loopback10 3

ipv6 route 23::/56 loopback11 4








! </NSM>

For a description of the sample output from the show running-config ipv6-static-routecommand, refer to the following table:


ipv6 route Indicates the keyword of the configuration command.

23::/56 Indicates the destination address and mask length.

loopback18 Indicates the egress interface.

The following is a sample output from the show ipv6 protocol routing static command:

IPv6 Routing Table

Codes: D - Direct, A - Address, S - Static, R - RIP, UI - USER_IPADDR,

I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS static,

O - OSPF intra, OI - OSPF inter, E1 - OSPF ext 1, E2 - OSPF ext 2,

N - ND, B - BGP, IB - IBGP, EB - EBGP, AG - BGP AGG, V - VRRP, P - PPP,

D6 - DHCPv6, SFN - Stateful NAT64, SLN - Stateless NAT64, AF - AFTR,

NP - ND_PREFIX, NF - ND_DFROUTE, NH - ND_HOST

M - Multicast

* - FIB route

> - selected route, p - stale info

Time: The time of last modified!

S> ::/0 [1/0]

* via ::, loopback1, 00:00:23

5-3



S> 1::/64 [1/0]

* via ::, null1, 00:00:23

S> 3::/64 [1/0]

* via ::, null1, 00:00:23

S> 23::/56 [1/0]

* via ::, loopback10, 00:47:07

* via ::, loopback11, 00:47:07

* via ::, loopback12, 00:47:07

* via ::, loopback13, 00:47:07

* via ::, loopback14, 00:47:07

* via ::, loopback15, 00:47:07

* via ::, loopback16, 00:47:07

* via ::, loopback17, 00:47:07

* via ::, loopback18, 00:47:07

S> 234::/56 [44/0]

* via 1000::3, gei-0/1/1/1, 00:56:39

S> 457::/64 [1/0]

* via ::, null1, 00:00:23

S> 2002::/16 [1/0]

* via ::, v6_tunnel2, 00:00:23

5.4 IPv6 Static Route Configuration ExampleGeneral DescriptionAs shown in Figure 5-1, S1 and S2 are directly connected with each other and belong tothe network segment 2005::/64. To enable S1 to successfully ping the network segment2003::/64 of S2, a static route to the network segment 2003::/64 can be added on S1, withthe next hop being the IPv6 address of the S2 interface that directly connects S1 with S2.

Figure 5-1 IPv6 Static Route Configuration Example

Method1. Configure the IPv6 address of the network segment 2005::/64 for the direct connection

between S1 and S2.2. Configure the IPv6 address of another different network segment 2003::/64 on the

non-direct connection interface of S2.3. Add a static route pointing to the network segment 2003::/64 on S1 so that S1 can

successfully ping the network segment 2003::/64 of S2.

5-4


Chapter 5 IPv6 Static Route Configuration




S1(config-if-vlan10)#ipv6 address 2005::1/64


S1(config)#ipv6 route 2003::/64 2005::2

S1(config)#exit

S2 configuration:









VerificationOnS1, check whether the address has been successfully configured, whether the interfaceis up, and whether the static route has been successfully added, and then run "ping62003::2" to check whether the ping operation is successful.

S1(config)#show running-config-interface vlan10

!<if-intf>

interface vlan10

ipv6 enable

ipv6 address 2005::1/64

$

!</if-intf>

S1(config)#show ipv6 interface brief vlan10

vlan10 [up/up]

fe80::2d0:d0ff:fe60:1000

2005::1/64

S1(config)#show running-config ipv6-static

!<ipv6-static-route>

ipv6 route 2003::/64 2005::2

!</ipv6-static-route>

S1(config)#ping6 2003::2

sending 5,100-byte ICMP echo(es) to 2003:0:0:0:0:0:0:2,timeout is 2 second(s).

5-5



!!!!!

Success rate is 100 percent(5/5),round-trip min/avg/max= 7/8/12 ms.

5-6


Chapter 6RIPng ConfigurationTable of Contents

RIPng Overview .........................................................................................................6-1Configuring the RIPng ................................................................................................6-3RIPng Maintenance and Diagnosis.............................................................................6-7RIPng Configuration Example ....................................................................................6-9

6.1 RIPng OverviewThe Routing Information Protocol (RIP) is widely applied as a mature routing standard onthe Internet, especially on some small-scale and medium-scale networks. Consideringthis situation and the compatibility between RIP and IPv6, the Internet Engineering TaskForce (IETF) altered the existing technology and set an RIP standard under IPv6, that is,RIP next generation (RIPng).

RIPng is a User Datagram Protocol (UDP)-based protocol using port 521 to transmit andreceive data packets. In general, RIPng packets are classified into two categories: routinginformation packets and request packets.

RIPng is not intended to create a completely new protocol but to make necessaryalternation to the RIP so as to enable it to adapt to the routing requirements under IPv6.Therefore, RIPng has the same working principles as the RIP, except for changes in theaddress and packet formats.

l Address Length

RIPv1 and RIPv2 are IPv4-based. The address field consists of only 32 bits. Incontrast, RIPng is IPv6-based and all its addresses comprise 128 bits.

l Subnet Mask and Prefix Length

RIPv1 is designed for use in subnet-free networks and thus does not involvethe subnet mask concept. For this reason, RIPv1 cannot be used to propagatevariable-length subnet addresses or CIDR classless addresses. The support forsubnet routing is added to RIPv2, so it can use subnet masks to distinguish betweennetwork routes and subnet routes.

IPv6 address prefixes have express meanings. Therefore, RIPng no longer involvesthe subnet mask concept but uses the prefix length instead. Similarly, due to the useof IPv6 addresses, it is unnecessary for RIPng to distinguish among network routes,subnet routes and host routes.

l Protocol Applicable Scope

6-1



The application scope of RIPv1 and RIPv2 is not limited to the Transfer ControlProtocol/Internet Protocol (TCP/IP) protocol suite but also includes other networkprotocol suites. Therefore, the routing entries of a packet include the networkprotocol suite field. However, it is seldom used for other non-IP networks in practice.Therefore, support for this function is removed from RIPng.

l Next Hop

There is no information about next hop in RIPv1. The router at the receiving end takesthe source address of a packet as the next hop for the route to the destination network.RIPv2 contains explicit information about the next hop, thus facilitating selection of theoptimum route and avoiding routing loops and slow convergence.

Different from RIPv1 and RIPv2, the next hop field in RIPng exists as a separate RTEto avoid overlong Routing table Entry (RTE) and to improve the efficiency of routinginformation transmission.

l Packet Length

In both RIPv1 and RIPv2, the packet length is limited and a packet can carry at most25 RTEs.

RIPng has no limit on the length of a packet and the number of RTEs. The length of apacket depends on the MTU of a medium. This packet length processing mechanismof RIPng has improved the transmission efficiency of routing information on thenetwork.

l Security Consideration

RIPv1 packets do not contain authentication information and thus RIPv1 is not secure.Any host sending packets via UDP port 520 may be regarded by neighboring hostsas a router and thus router spoofing may easily take place. RIPv2 is designed tocontain authentication packets to enhance security. Although routers that exchangeroutes with each other cannot receive route information from each other beforeauthentication, RIPv2 does not have adequate security.

IPv6 contains perfect security policies, so there is no need to design separate securityauthentication packets for RIPng any more but to use IPv6 security policies.

l Packet Transmission Mode

RIPv1 sends routing information through broadcast. In this way, both routers and allthe hosts within the same Local Area Network (LAN) can receive packets, which isunnecessary and insecure.

However, both RIPv2 and RIPng can send packets either through broadcast orthrough multicast. In this way, packets can be sent through multicast in networks thatsupport multicast, thus greatly reducing the volume of routing information transmittedin networks.

6-2


Chapter 6 RIPng Configuration

6.2 Configuring the RIPngRIPng configuration includes the enabling of RIPng and the configuration of RIPng protocolparameters.

Enabling RIPngTo enable RIPng, perform the following steps.


1 ZXR10(config)#ipv6 router rip Enters the RIPng configuration

mode.

2 ZXR10(config-ripng)#interface <interface-name> Enters the RIPng interface

configuration mode.

3 ZXR10(config-ripng-if)#ipv6 rip enable Enables RIPng on an interface.

Configuring RIPng Protocol ParametersTo configure RIPng protocol parameters, perform the following steps.

l Configure the timers of RIPng:


1 ZXR10(config)#ipv6 router rip Enters the RIPng

configuration mode.

2 ZXR10(config-ripng)#timers basic <update><timeout

><garbage>

Configures the timers of

RIPng.



<update> Specifies the periodic packet sending interval in the unit

of seconds. The value range is 5-65535 seconds. The


<timeout> Specifies the time for the route to become invalid in the

unit of seconds. The value range is 5-65535 seconds.


<garbage> Specifies the time period from the time when the route

becomes invalid to the time when the route is deleted in

the unit of seconds. The value range is 5-65535 seconds.


l Set the default metric of RIPng routes:

6-3





configuration mode.

2 ZXR10(config-ripng)#default-metric <metric> Sets the default metric of

routes in the range of 1-16.

l Configures the summarized routes of the RIPng:



configuration mode.

2 ZXR10(config-ripng)#summary-prefix

X:X::X:X/<0-128>

Configures the summarized

routes of the RIPng.



X:X::X:X/<0-128> Indicates the IPv6 route prefix and length of the

summarized routes.

l Configure the port for listening to RIPng multicast packets:



configuration mode.

2 ZXR10(config-ripng)#port <1-65535> Specifies the port for listening

to multicast packets. The

value range is 1-65535. The

default value is 521.

l Configure the offset list of the RIPng:



configuration mode.

2 ZXR10(config-ripng)#offset-list <access-list-name>{in

| out}<offset>

Configures the offset list of

the RIPng.



<access-list-name> Specifies the ACL number with 1-31 characters.

6-4




in | out Specifies route receiving or sending.

<offset> Specifies the metric of the offset in the range of 0-16.

l Configure the redistribution of protocol routes:



configuration mode.

2 ZXR10(config-ripng)#redistribute <protocol>[metric<metric-value>][route-map <map-tag>]

Configures the redistribution

of protocol routes.



<protocol> Specifies the name of the protocol whose routes are

redistributed.

<metric-value> Specifies the metric for the redistributed routes in the

range of 1-16.

<map-tag> Specifies the route map used for protocol route

redistribution.

l Delete the routes received by the RIPng:

Command Function

ZXR10#clear ipv6 rip route {X:X::X:X/<0-128>| all| vrf} Deletes the routes received by

the RIPng. You can delete all

the received routes or a certain

route only.



X:X::X:X/<0-128> Specifies the route prefix of the routes to be deleted.

all Indicates that all the received RIPng routes will be deleted.

vrf Specify parameters for a VPN.

l Configure interface commands:



configuration mode.

6-5




2 ZXR10(config-ripng)#interface <interface-name> Enters the RIPng interface

configuration mode.

ZXR10(config-ripng-if)#ipv6 rip split-horizon Enables split horizon on

the interface. By default,

split horizon is enabled. To

disable split horizon, use the

no form of the command.

ZXR10(config-ripng-if)#ipv6 rip poison-reverse Enables poison reverse on

the interface. By default, the

poison reverse function is

enabled.

ZXR10(config-ripng-if)#ipv6 rip interface active Configures the active

interface so that the interface

only sends packets but

does not receive packets.

To cancel the configuration

and restore normal packet

sending and receiving, use

the no form of the command.

ZXR10(config-ripng-if)#ipv6 rip interface passive Configures the passive

interface so that the interface

only receives packets but

does not send packets. To

cancel the configuration

and restore normal packet

sending and receiving, use

the no form of the command.

ZXR10(config-ripng-if)#ipv6 rip neighbor

<X:X::X:X>

Configures the neighbor

address of the RIPng so that

unicast packets will be sent

to this neighbor only.

3

ZXR10(config-ripng-if)#ipv6 rip originate-default-

route [only]

Originates the default route

of the RIPng on the interface.

To cancel the configuration,

use the no form of the

command.



<X:X::X:X> Specifies the link-local address of the neighbor.

6-6




[only] Indicates that only the default route will be sent on the

interface.

6.3 RIPng Maintenance and DiagnosisTo maintain and diagnose RIPng, use the following commands.

Command Function

ZXR10(config)#show ipv6 rip [vrf <vrf-name>] Shows the content of the RIPng

protocol.

ZXR10(config)#show ipv6 rip database [{X:X::X:X/<0-128>|<X:X::X:X>}][vrf <vrf-name>]

Shows the RIP route database

information.

ZXR10(config)#show ipv6 rip interface [vrf <vrf-name>]<interface-name>

Shows the interfaces on which

RIPng is enabled.

The command parameters are described as follows:


vrf <vrf-name> VRF name, with 1-32 characters

X:X::X:X Indicates the specific IPv6 route prefix.

X:X::X:X/<0-128> Indicates the IPv6 route prefix and prefix length.

<interface-name> Indicates the interface name.

The following example shows the outputs of the command show ipv6 rip:

ZXR10(config)#show ipv6 rip

RIPng protocol, port 521, multicast-group FF02::9

administrative distance is 120

default metric is 1

updates every 30 seconds, expire after 180 seconds

garbage collect after 120 seconds

the number of ripng routes:

connect ripng route 0

aggregate ripng route 0

ripng route 0

Redistribution:

The outputs of the command show ipv6 rip are described as follows:


port 521 Indicates that the RIPng uses UDP port 521.

6-7




multicast-group FF02::9 Indicates that the multicast address used by the RIPng is

FF02::9.

administrative distance is 120 Indicates that the administrative distance of RIPng routes

is 120.

default metric is 1 Indicates that the default metric of RIPng routes is 1.

updates every 30 seconds, expire

after 180 seconds


Indicates that the update timer currently set is 30s, the

timeout timer is 180s, and the garbage timer is 120s.

connect ripng route 0 Indicates that the number of connect RIPng routes is 0.

aggregate ripng route 0 Indicates that the number of aggregate RIPng routes is 0.

Redistribution Indicates that the protocol type of rouet redistribute.

The following example shows the outputs of the command show ipv6 rip database:

ZXR10(config)#show ipv6 rip database

2010::/64

nexthop: 2010::13, via: vlan10

metric: 1, tag: 0 time: 00:01

The outputs of the command show ipv6 rip database are described as follows:


2010::/64 Indicates the destination network segment.

nexthop: 2010::13 Indicates the next-hop address. In this example, there is no

next hop because the network segment is a direct connection

segment.

via: vlan10 Indicates the egress interface of the route.

metric: 1, tag: 0 Indicates that the metric of the route is 1 and the tag is 0.

time: 00:01 Indicates the time of the route exist.

The following example shows the outputs of the command show ipv6 rip interface [<interface-name>]:

ZXR10(config)#show ipv6 rip interface vlan10

vlan10: interface is up

RIPng is enabled

Split horizon enabled

Poison reverse enable

IPv6 interface address:

2010::13/64

The outputs of the command show ipv6 rip interface [<interface-name>] are described asfollows:

6-8




vlan10: interface is up Indicates that the vlan10 is up.

RIPng is enabled Indicates that PIPng is enabled on the interface vlan10.

Split horizon enabled Indicates that the split horizon is enabled.

Poison reverse enable Indicates that the poison reverse is enabled.

IPv6 interface address:

2010::13/64

Indicates that the address of the interface vlan10 is

2010::13/64.

6.4 RIPng Configuration ExampleGeneral DescriptionAs shown in Figure 6-1, the RIPng runs on routers S1 and S2 to advertise the RIPng routesof the two routers. Here, a loopback address is taken as an example and can redistributeother routes. The redistribution of direct routes is taken as an example.

Figure 6-1 RIPng Configuration Example

Method1. Enable the IPv6 protocol on the interfaces and configure IPv6 addresses.2. Configure the RIPng protocol.3. Enable the RIPng-related configurations on the interfaces.4. Configure the redistribution commands if it is necessary to redistribute other routes.5. Check the configuration results, and confirm that neighbors are correctly established

between the two routers and each router can learn the routes advertised by the peerrouter.



S1(config-if)#ipv6 enable

S1(config-if)#ipv6 address 3611::11/64

S1(config-if)#exit

6-9






S1(config)#interface loopback5



S1(config-if)#exit

S1(config)#ipv6 router rip

S1(config-ripng)#interface vlan1

S1(config-ripng-if)#ipv6 rip enable

S1(config-ripng-if)#exit

S1(config-ripng)#interface loopback5



S1(config-ripng)#redistribute connected

S1(config-ripng)#exit

S2 configuration:




S2(config-if)#exit







S2(config-if)#exit

S2(config)#ipv6 router rip

S2(config-ripng)#interface vlan1



S2(config-ripng)#interface loopback5



S2(config-ripng)#redistribute connected

S2(config-ripng)#exit

VerificationRun the command show running-config ripng on S1 and S2 to check the RIPngconfiguration information, and run the command show ipv6 forwarding route ripng tocheck the routing information.

6-10



Check the routing information on S1:

S1#show running-config

ripng

! <RIPNG>

ipv6 router rip

redistribute connected

interface vlan1

ipv6 rip enable

$

interface loopback5

ipv6 rip enable

$! </RIPNG>

S1#show ipv6 rip



default metric is 1



the number of ripng routes is 4

Redistribution:

Interfaces:

vlan1

loopback5

S1#show ipv6 rip database

2255::/64

nexthop: ::, via: unknown

metric: 16, tag: 0, time: 04:41

2355::/64

nexthop: fe80::2d0:d0ff:feaf:cc10, via: vlan1


2356::/64



2357::/64



2358::/64



2310::/64


6-11




3036::/64

nexthop: ::, via: vlan1

metric: 1, tag: 0

3550::/64



3555::/64

nexthop: ::, via: loopback5

metric: 1, tag: 0

3611::/64


metric: 1, tag: 0

S1#show ipv6 forwarding route ripng

IPv6 Routing Table:

Dest Owner Metric Interface Gw

2352::/64 ripng 2 vlan1 fe80:12::2d0:d0ff:feaf:cc10




S1#ping6 2352::52

sending 5,100-byte ICMP echoes to 2352::52,timeout is 2 seconds.

!!!!!


Check the routing information on S2:

S2#show running-config

ripng

! <RIPNG>

ipv6 router rip


interface vlan1

ipv6 rip enable

$

! </RIPNG>

S2#show ipv6 rip



default metric is 1


6-12




the number of ripng routes is 4

Redistribution:

Interfaces:

loopback5

vlan1

S2#show ipv6 rip database

2255::/64

nexthop: fe80::2d0:d0ff:fe78:99dd, via: vlan1


2355::/64


metric: 1, tag: 0

2356::/64


metric: 1, tag: 0

2310::/64



3036::/64



3550::/64

nexthop: ::, via: loopback5

metric: 1, tag: 0

3555::/64



3611::/64


metric: 1, tag: 0

S2#show ipv6 forwarding route ripng

IPv6 Routing Table:


2255::/16 ripng 2 vlan1 fe80:2e::2d0:d0ff:fe78:99dd




S2#ping6 2255::66


!!!!!


6-13




6-14


Chapter 7OSPFv3 ConfigurationTable of Contents

OSPFv3 Overview......................................................................................................7-1Configuring OSPFv3 ..................................................................................................7-5OSPFv3 Maintenance and Diagnosis .......................................................................7-11OSPFv3 Configuration Examples .............................................................................7-13

7.1 OSPFv3 OverviewIntroduction to OSPFv3Open Shortest Path First (OSPF) version 2 is a link-status-based interior gateway protocoldeveloped by IETF. Because it has a wide application scope, provides fast convergence,eliminates routing loops and facilitates hierarchical network design, it has been widelyapplied in IPv4 networks.

With the construction of IPv6 networks, dynamic routing protocols are also required toprovide accurate and valid routing information for IPv6 packet forwarding. For this reason,IETF revised OSPFv2 according to IPv6 networks and developed OSPFv3. OSPFv3 ismostly used in IPv6 networks to provide the routing function. It is a mainstream routingprotocol applied in IPv6 networks.

The IPv6 OSPF protocol is OSPFv3, and the IPv4 OSPF protocol is OSPFv2.

The IPv6 OSPF keeps the majority of IPv4 algorithms. The essential OSPF mechanismremains unchanged from IPv4 to IPv6.

Both OSPFv3 and OSPFv2 have a link status database. The Link Status Advertisement(LSA) is contained in the link status database, and the link status databases of all routersin the same area must be kept synchronous.

Database synchronization is implemented through the database exchange process, whichincludes exchanging database description packets, link state request packets and link stateupdate packets. The subsequent database synchronization is maintained through floodingwith link state update packets and link state acknowledgment packets.

In broadcast and Non-Broadcast Multicast Access (NBMA) networks, both OSPFv3 andOSPFv2 use the hello packet to discover and maintain adjacency and to elect DesignateRouter (DR) and Backup Designate Router (BDR).

OSPFv3 and OSPFv2 also keep consistent with each other in such aspects as neighbordetermination, basic concept of inter-area routes, redistribution of Autonomous System(AS) external routes and so on.

7-1



OSPFv3 PrincipleCompared with OSPFv2, OSPFv3 has almost the same working mechanism but has alsorevised OSPFv2 so as to support the IPv6 address format. The following sections describein detail the similarities and differences between OSPFv2 and OSPFv3. For details aboutthe OSPFv2 principles, please refer to "OSPF Configuration" in IPv4 Routing Volume.

Similarities Between OSPFv3 and OSPFv2

OSPFv3 has almost the same protocol design concept and working mechanism asOSPFv2.

l The same packet types: Hello, DD, Link State Packet (LSP), Link State Update (LSU),LSAck packets.

l The same area division.l The same LSA flooding and synchronization mechanisms: To guarantee the

correctness of Link-state Database (LSDB) information, the reliable flooding andsynchronization of LSAs must be guaranteed.

l The same route computation method: Both use the Shortest Path First (SPF)algorithm to compute routes.

l The same network types: Both support four network types, i.e. broadcast, NBMA,point-to-point, point-to-multipoint.

l The same neighbor discovery and neighbor establishment mechanisms: After anOSPF router is started, it sends a Hello packet via the OSPF interface to anotherOSPF router. Upon receipt of the Hello packet, the latter OSPF router checks theparameters defined in the packet. If the parameters in the received packet are thesame as those in its own packet, adjacency is established between the two routers.

Two routers in an adjacency relationship do not necessarily become neighbors. Thisdepends on the network type. The two routers become real neighbors only whenthey have successfully exchanged the DD packet and the LSA and their LSDBs aresynchronized with each other.

l The same DR election mechanism: The DR and BDR need to be elected in NBMAand broadcast networks.

Differences Between OSPFv3 and OSPFv2

There are differences between OSPFv3 and OSPFv2 because OSPFv3 is based on IPv6.

l The topology of OSPFv3 is link-based whereas that of OSPFv2 is subnet-based.

IPv6 uses the term "link" to describe the facilities or mediums used by nodes forcommunications over the link layer. Nodes are connected with links. Multiple IPsubnets can be attached to the same link. Two nodes in different IP subnets cancommunicate with each other directly over a single link.

l Address semanteme is deleted from OSPFv3.

The OSPFv3 packet contains no IPv6 address except for the LSA payload carried ina link state update packet. The router LSA and network LSA do not contain networkaddresses but only indicate topology information. The OSPF router ID and the LSAID are reserved as 32-bit IPv4 addresses and not assigned with any IPv6 address.

7-2


Chapter 7 OSPFv3 Configuration

l OSPFv3 extends the range of flooding

The LS field of the LSA reflects its flooding range. LSA features the following threeflooding ranges:

à Link Local Range: LSAs only flood in the local link range. This range is applicableto the link LSA.

à Area Range: LSAs only flood in a single OSPFv3 area. This range is applicableto the router LSA, network LSA, inter-area prefix LSA, inter-area router LSA andintra-area prefix LSA.

à AS Range: LSAs flood in the whole OSPFv3 routing domain. This is applicableto the AS external LSA. Each link supports multiple instances. OSPFv3 supportsthe running of multiple OSPF protocol instances over a single link.

l Usage of link local address.

The IPv6 link local addresses are used for neighbor discovery and automaticconfiguration over a single link. IPv6 routers do not forward the IPv6 packetscontaining link local source addresses. The IPv6 address range allocated to the linklocal unicast addresses is FE80/10.

Except for the virtual link, OSPFv3 link local addresses related to interfaces canserve as source addresses to send OSPF packets. In the virtual link, only the IPv6addresses in the global range or of a local site can serve as the source address.

The link local addresses occur in the OSPFv3 LSA but are not allowed to occur inother types of LSAs.

l Changes to the authentication mode

The authentication type and authentication field are removed from the OSPFv3header. The authentication-related fields do not occur in the OSPFv3 area datastructure and the interface data structure. The OSPFv3 employs the authenticationmechanism provided by the IPv6 itself to implement integrity and confidentiality inpacket exchanging.

l Changes to the protocol packet format

The OSPFv3 runs over the IPv6 directly. Address semanteme is not contained inthe OSPF header but in different LSA types. Therefore, OSPFv3 is independent ofnetwork protocols. The following are changes to the packet format:

à The version number changes from 2 to 3.

à Options fields of the Hello packet and the database description packet areexpanded to 24 bits.

à The authentication and authentication type fields are removed from the packetheader.

à The Hello packet does not contain the address semanteme but contains aninterface ID used by the router to identify the link. If the router becomes the DRon the link, the interface ID will be the link state ID of the network LSA.

7-3



à To process the router LSA during SPF computation, two flag bits R and V6 areadded to the options field. The OSPF header contains an Instance ID, thusallowing the running of multiple OSPF protocol instances over a single link.

LSA Types

An LSA is the unit to construct the OSPFv3 link state database. A router uses LSAs toform a complete network topology and further generate a routing table. OSPFv3 has thefollowing types of LSAs.

l Router LSA

Its link state type is 0x2001. It can generate one or multiple LSAs on each routerwithin an area.

l Network LSA

Its link state type is 0x2002. It can generate network LSAs for each broadcast andNBMA link within an area, which supports two or multiple routers. Network LSAs arecreated by DR on this link.

l Inter-Area Prefix LSA

Its link state type is 0x2003. It is equivalent to the Type-3 LSA in OSPFv2. Created byan area border router, the inter-area prefix router LSA describes IPv6 address prefixesin other areas. For stub areas, inter-area prefix LSA can also be used to describe thedefault route.

l Inter-Area Router LSA

Its link state type is 0x2004. It is equivalent to the Type-4 LSA in IPv4. Created by theABR, it describes the ASBR to other areas.

l AS External LSA

Its link state type is 0x4005. It is created by the ASBR and describes the ASBR toother areas.

l Link LSA

Its link state type is 0x0008. A router advertises a separate link LSA to each linkconnecting with it. These LSAs have a local link flooding range and will not be floodedout of the related link.

l Intra-Area Prefix LSA

Its link state type is 0x2009. A router uses the intra-area prefix LSA to advertiseone or multiple IPv6 address prefixes, which are associated with the router itself, theconnected stub network segment or the connected transit network segment.

Two types of LSAs are added to OSPFv3. They are the Link LSA and the Intra Area PrefixLSA.Table 7-1 describes the brief similarities and differences between OSPFv3 LSAs andOSPFv2 LSAs.

7-4



Table 7-1 Similarities and Differences Between OSPFv3 LSAs and OSPFv2 LSAs

OSPFv2 LSA OSPFv3 LSA Similarities with andDifferences from OSPFv2LSAs

Router LSA Router LSA

Network LSA Network LSA

The name is the same and the

function is similar, except that

the LSA no longer describes

address information but is used

only to describe the topology

structure of the routing area.

Network Summary LSA Inter Area Prefix LSA

ASBR Summary LSA Inter Area Router LSA

The function is similar but the

name is different.

AS External LSA AS External LSA Both the function and the name

are completely the same.

Link LSA The LSA is newly added.-

Intra Area Prefix LSA The LSA is newly added.

7.2 Configuring OSPFv3Enabling OSPFv3To enable OSPFv3, perform the following steps.


1 ZXR10(config)#ipv6 router ospf <process-id> Enables the OSPFv3 process.

2 ZXR10(config-ospfv3-process-id)#router-id

<router-id>

Specifies the Router ID for an

OSPFv3 process.

Configuring OSPFv3 Interface AttributesTo configure OSPFv3 interface attributes, perform the following steps.


1 ZXR10(config)#ipv6 router ospf<process-id> Enters the interface

configuration mode.

2 ZXR10(config-ospfv3-process-id)#interface

<interface-name>[area <area-id>] nstance <0-255>]Adds an interface to OSPFv3.

7-5




ZXR10(config-ospfv3-process-id-if-interface-

name)#hello-interval <interval>

Specifies the interval of

sending Hello packets on an

interface in the unit of seconds.

The value range is 1-65535.

The default value for

point-to-point and broadcast

interfaces is 10 seconds.


non-broadcast and

point-to-multipoint interfaces is

30 seconds.


name)#retransmit-interval <interval>

Specifies the time interval at

which an interface retransmits

an LSA in the unit of seconds.

The value range is 1-65535.



name)#transmit-delay <interval>

Specifies the delay after which

an interface transmits a link

state update packet in the unit

of seconds. The value range

is 1-65535. The default value

is 1 second.


name)#dead-interval <interval>

Specifies the aging time of

neighbors on an interface in

the unit of seconds. The value

range is 1-65535.


point-to-point and broadcast

interfaces is 40 seconds.


non-broadcast and

point-to-multipoint interfaces is

120 seconds.


name)#cost <cost-value>

Sets the interface cost value in



value of a loopback interface is

1, and that of other interfaces

is 10.

3

7-6





name)#priority <value>

Sets the interface priority in



value is 1.


name)#neighbor <X:X::X:X>[{[cost <cost-value>]|[poll-interval <interval>]|[priority <value>]}]

Configures the neighboring

routers in a non-broadcast or

point-to-multipoint network.


name)#network {broadcast | non-broadcast |

point-to-multipoint [non-broadcast]| point-to-point}

Sets the network type for an

interface.


name)#bfd <disable | enable>

Configures BFD attribute.


name)#ipv6-mtu-ignore

Configures to ignore MTU

check during DD packet

exchange


name)#linklsa-suppress <enable>

Suppresses an interface to

generate Type-8 link LSA.

Configuring OSPFv3 Protocol AttributesTo configure OSPFv3 protocol attributes, perform the following steps.


1 ZXR10(config)#ipv6 router ospf <process-id> Enables an OSPFv3 instance

and enters the OSPFv3

configuration mode.

2 ZXR10(config-process-id)#area <area-id> bfd <disable

| enable>

Configures BFD attribute of all

interface in an area.

3 ZXR10(config-ospfv3)#area <area-id> default-cost<cost-value>

Configures the default metric

value for an area, the value

range is 0-16777215.

4 ZXR10(config-ospfv3)#area <area-id> rangeX:X::X:X/<0-128>[advertise | not-advertise]

Configures the range of

summary addresses in an

area.

5 ZXR10(config-ospfv3)#area <area-id> stub [no-summary] Defines an area as the stub

area. no-summary implies

the ABR is forbidden to send

summary routes to this stub

area.

7-7




6 ZXR10(config-ospfv3)#area <area-id> virtual-link<router-id>[dead-interval <seconds>][hello-interval<seconds>][retransmit-interval <seconds>][transmit-delay<seconds>]

Defines an OSPF virtual link.

7 ZXR10(config-ospfv3)# bfd enable Enables BFD function on all

interfaces. Use the no format

of this command to restore the

default value.

8 ZXR10(config-ospfv3)#default-metric <metric-value> Sets the default metric value

for the OSPFv3 protocol.

This value is allocated to

redistributed routes. The value

range is 1-16777214. The

default value is 20.

9 ZXR10(config-ospfv3)#distribute-list {[access-list<access-list-name> in ]|[route-map <name of a route-map>

in]}

The distribute-list in command

filters routes of which the

owner is OSPF routes. The

distribute-list out command

controls the redistribution

of external routes to OSPF

areas after Type-5 LSAs

are generated. This is a

supplement of the redistribute

command.

10 ZXR10(config-ospfv3)#maximum-paths <number> Sets the maximum number

of routes for load sharing in

OSPF.

11 ZXR10(config-ospfv3)#passive-interface <interface-name> Prohibits OSPFv3-enabled

interfaces from sending

OSPFv3 packets.

12 ZXR10(config-ospfv3)#redistribute <protocol>[metric<metric-value>][metric-type <type>][route-map <name>]

Redistributes the routes of

protocols into the OSPFv3

protocol.

13 ZXR10(config-ospfv3)#summary-prefix <X:X::X:X/<0-

128>>

Summaries the routes of other

protocols that are redistributed

to OSPF.

14 ZXR10(config-ospfv3)#timers spf delay <delay>

hold-time <holdtime>Sets the interval at which the

OPSFv3 protocol computes

routes.


7-8




<area-id> Specifies the ID of the area as an IP address of the decimal

(0-4294967295) or dotted decimal format (A.B.C.D).

disable Disables BFD.

enable Enables BFD.





<cost-value> Specifies the default metric value. The value range is

0-16777215. The default value is 1.





X:X::X:X/< 0-128> Specifies the summary IPv6 route prefix and the prefix length.

advertise Enables the advertisement of summary 3-type LSAs.

not-advertise Prohibits the advertisement of summary 3-type LSAs.





no-summary Forbids ABR to send summary information to the stub area.





<router-id> Specifies the peer router ID of the virtual link in the format of

a dotted decimal IP address.

hello-interval <seconds> Specifies the interval at which Hello packets are sent on the

virtual link in the unit of seconds. The value range is 1-8192.


7-9




dead-interval <seconds> Specifies the dead interval of neighbors on the virtual link in

the unit of seconds. The value range is 1-8192. The default

value is 40 seconds.

retransmit-interval <seconds> Specifies the retransmission interval of packets on the virtual

link in the unit of seconds. The value range is 1-8192. The


transmit-delay <seconds> Specifies the delay after which a link state update packet

is transmitted on the virtual link in the unit of seconds. The

value range is 1-8192. The default value is 1 second.

The command parameter in step 8 is described as follows:


<metric-value> Default metric of external routes, in the range of 1-16777214.



<access-list-name> The first character can be a digit. Use an unused name.

<name of a route-map> Route-map template name

in In: The template specified is used to filter routes.



<number> Maximum number of routes for load sharing in OSPF, in the

range of 1-32, with the default value of 1.



<interface-name> Interface name



<protocol> Specifies the name of the redistributed protocol, such as

"connected", "static", "RIP", "BGP", "ISIS" or "OSPF".

<metric-value> Specifies the metric of the redistributed LSA. By default, the

default-metric of the instance is used. The value range is

0-16777214.

7-10




<type> Specifies the metric-type of the redistributed LSA. The value

is 1-2. The default value is 2.

route-map <map-name> Specifies the route map used for protocol route redistribution.



<X:X::X:X/128> Prefix and prefix length of the IPv6 routes summarized.



<delay> Specifies the delay of route re-computation that follows after

route updates are received in the unit of seconds. The value

range is 0-65535. The default value is 5 seconds.

<holdtime> Specifies the hold time in the unit of seconds. The value


7.3 OSPFv3 Maintenance and DiagnosisCompared with RIPng, OSPFv3 ismore complicated. There aremany fault reasons behinda fault symptom. Therefore, the maintenance and diagnosis of OSPFv3 is more difficult.To maintain and diagnose OSPFv3, use the following commands.

Command Function

ZXR10(config)#show ipv6 ospf <process id> Shows an OSPFv3 instance.

ZXR10(config)#show ipv6 ospf database Shows the database information

about an OSPFv3 instance.

ZXR10(config)#show ipv6 ospf interface [<interface-name>] Shows the interface information


ZXR10(config)#show ipv6 ospf neighbor Shows the neighbor information


ZXR10(config)#show ipv6 ospf virtual-links Shows the virtual link information


The following example shows the outputs of the command show ipv6 ospf:

ZXR10#show ipv6 ospf

Routing Process "ospfv3 1" with ID 1.1.1.8

SPF schedule delay 5 secs. Hold time between two SPFs 10 secs

Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs

7-11



Number of external LSA 1. Checksum Sum 0x00985A

The number of ospfv3 routes is 3

Default metric is 20

Number of areas in this router is 2. 2 normal 0 stub

Redistribution:

redistribute static

Area BACKBONE(0)

Number of interfaces in this area is 1

SPF algorithm executed 3 times

Number of LSA 5. Checksum Sum 0x02BC99

Number of Unknown LSA 0

Area 0.0.0.1

Number of interfaces in this area is 2

SPF algorithm executed 10 times

Number of LSA 9. Checksum Sum 0x045678

Number of Unknown LSA 0

The following example shows the outputs of the command show ipv6 ospf interface:

ZXR10#show ipv6 ospf interface

loopback1 is up, line protocol is up

Link Local Address fe80::2f0:e0ff:fe21:201, Interface ID 4

Area 0.0.0.0, Process ID 1, Instance ID 0, Router ID 1.1.1.8

Network Type LOOPBACK, Cost: 1

Loopback interface is treated as a stub Host

qinq1 is up, line protocol is up

Link Local Address fe80::2f0:e0ff:fe21:201, Interface ID 2

Area 0.0.0.1, Process ID 1, Instance ID 0, Router ID 1.1.1.8

Network Type BROADCAST, Cost: 10

Transmit Delay is 1 sec, State BDR, Priority 1

Designated Router(ID) 1.1.1.9, local address fe80::2f0:e0ff:fe21:203

Backup Designated router(ID) 1.1.1.8,local address fe80::2f0:e0ff:fe21:201

Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

Hello due in 00:00:08

Neighbor Count is 1, Adjacent neighbor count is 1

The following example shows the outputs of the command show ipv6 ospf database:

OSPFv3 Router with ID (2.2.2.2) (Process ID 1)

Router Link States (Area 0.0.0.0)

ADV Router Age Seq# Link count Bits

2.2.2.1 804 0x80000008 1 -|-|-|-

2.2.2.2 404 0x8000000a 0 -|-|-|B

Inter Area Prefix Link States (Area 0.0.0.0)

7-12



ADV Router Age Seq# Prefix

2.2.2.2 1035 0x80000001 500::/64

Intra Area Prefix Link States (Area 0.0.0.0)

ADV Router Age Seq# Link ID Ref-lstype Ref-LSID

2.2.2.2 403 0x80000001 5 0x2001 0

Link (Type-8) Link States (Area 0.0.0.0)

ADV Router Age Seq# Link ID Interface

2.2.2.1 810 0x80000004 1 vlan20

2.2.2.2 739 0x80000004 59 vlan20

Router Link States (Area 0.0.0.1)

ADV Router Age Seq# Link count Bits

1.1.1.1 1042 0x80000005 1 -|-|-|B

2.2.2.2 1045 0x80000005 1 -|-|-|B

Net Link States (Area 0.0.0.1)

ADV Router Age Seq# Link ID Rtr count

2.2.2.2 1046 0x80000001 60 2

Inter Area Prefix Link States (Area 0.0.0.1)

ADV Router Age Seq# Prefix

1.1.1.1 405 0x80000001 2000::/64

2.2.2.2 403 0x80000001 1000::/64

Intra Area Prefix Link States (Area 0.0.0.1)

ADV Router Age Seq# Link ID Ref-lstype Ref-LSID

2.2.2.2 1044 0x80000001 7 0x2002 60

Link (Type-8) Link States (Area 0.0.0.1)

ADV Router Age Seq# Link ID Interface

1.1.1.1 1911 0x80000001 1186 vlan500

2.2.2.2 101 0x80000002 60 vlan500

7.4 OSPFv3 Configuration Examples

7.4.1 OSPFv3 Configuration Example 1

Configuration DescriptionAs shown in Figure 7-1, S1 and S2 establish a link via direct connection interfaces toadvertise their respective loopback address route.

7-13



Figure 7-1 OSPFv3 Configuration Example

Configuration Thought1. Enable the IPv6 protocol on the direct connection interfaces of S1 and S2, configure

IPv6 addresses for the direct connection interfaces, configure loopback interfaces,enable IPv6 on the loopback interfaces, and configure IPv6 addresses for the loopbackinterfaces.

2. Configure OSPFv3.3. Add the interfaces to OSPF area 0.4. Check and verify the configuration results: Neighbors are correctly established

between the two routers, each router can learn the routes advertised by the peerrouter, and each router can ping the peer loopback interface.







S1(config-if-loopback5)#ipv6 enable

S1(config-if-loopback5)#ipv6 address 3555::52/64

S1(config-if-loopback5)#exit

S1(config)#ipv6 router ospf 1

S1(config-ospfv3-1)#router-id 11.11.11.11

S1(config-ospfv3-1)#interface vlan10 area 0

S1(config-ospfv3-1-if-vlan10)#exit

S1(config-ospfv3)#interface loopback5 area 0

S1(config-ospfv3-1-if-loopback5)#exit

S1(config-ospfv3-1)#exit

S2 configuration:








7-14








S2(config-ospfv3-1)#interface loopback5 area 0



Configuration VerificationAfter completing the above configuration, run the commands show ipv6 ospf neighbor andshow ipv6 forwarding route on each router to check the established neighbors and routes.Ping the peer loopback interface from each router. If both routers can ping the loopbackinterface of the peer router, the configuration is successful.

Check and verify the configuration results as follows on S1:

S1(config)#show ipv6 ospf neighbor

OSPFv3 Process 1

Neighbor ID Pri State Dead Time Interface ID Interface

10.10.10.10 1 FULL/BDR 00:00:35 46 vlan10

S1#show ipv6 forwarding route 3550::55

IPv6 Routing Table:

Dest Owner Metric Interface Pri Gw

3550::55/128 ospf6 10 vlan10 0 fe80:12::2d0:d0ff:feaf:cc10

S1#ping6 3550::55


!!!!!



S2(config)#show ipv6 ospf neighbor

OSPFv3 Process 1


11.11.11.11 1 FULL/DR 00:00:37 18 vlan10

S2#show ipv6 forwarding route 3555::55

IPv6 Routing Table:


3555::55/128 ospf6 0 vlan10 0 fe80:2e::2d0:d0ff:fe78:99dd

S2#ping6 3555::55


!!!!!


7-15



7.4.2 OSPFv3 Configuration Example 2

Configuration DescriptionAs shown in Figure 7-2, S1 and S2 establish a link with each other via the direct connectioninterfaces, S1 and S2 establish the link in area 0 whereas S2 and S3 establish a linkwith each other in area 10 to advertise their respective loopback address route, and S1redistributes the direct route.

Figure 7-2 OSPFv3 Configuration Example 2

Configuration Thought1. Enable the IPv6 protocol on the interfaces, configure IPv6 addresses for these

interfaces, configure loopback interfaces, enable IPv6 on the loopback interfaces,and configure IPv6 addresses for the loopback interfaces.

2. Configure OSPFv3.3. Add the interfaces to OSPFv3. S1 and S2 establish a link with each other in area 0,

S2 and S3 establish a link with each other in area 10, and S1 redistributes the directroute.

4. Check and verify the configuration results: Neighbors are correctly establishedbetween the routers, each router can learn the routes advertised by the other tworouters, and each router can ping the loopback interfaces of the other two routers.









7-16








S2(config-ospfv3-1)#interface loopback5 area 0


S1(config-ospfv3)#redistribute connected


!

S2 configuration:


















S2(config-ospfv3-if-loopback5)#exit

S2(config-ospfv3)#interface vlan20 area 10

S2(config-ospfv3-if-vlan20)#exit

S2(config-ospfv3)#exit

S3 configuration:











7-17






S3(config-ospfv3-if-loopback5)#exit

S3(config-ospfv3)#exit

Configuration VerificationAfter completing the above configuration, run the commands show ipv6 ospf neighbor andshow ipv6 forwarding route on each router to check the established neighbors and routes.Ping the loopback interfaces of the other two routers from each router. If each router canping the loopback interfaces of the other two routers, the configuration is successful.

Check and verify the configuration results as follows on R1:

S1(config)#show running-config ospfv3

!<ospfv3>

ipv6 router ospf 1

router-id 11.11.11.11


redistribute static

interface vlan100 area 0.0.0.0 instance 0

$

interface loopback5 area 0.0.0.0 instance 0

$

$

!</ospfv3>

R1#show ipv6 ospf neighbor

OSPFv3 Process 1


10.10.10.10 1 FULL/BDR 00:00:35 46 vlan10

R1#show ipv6 forwarding route 3550::55

IPv6 Routing Table:


2352::/64 ospf6 20 vlan10 0 fe80:12::2d0:d0ff:feaf:cc10



R1#ping6 3550::55


!!!!!



R2#show running-config ospfv3

! <OSPFV3>

ipv6 router ospf 1

7-18



router-id 10.10.10.10


$


$


$

!

! </OSPFV3>


OSPFv3 Process 1


1.1.1.5 1 FULL/BDR 00:00:33 54 vlan20

11.11.11.11 1 FULL/DR 00:00:37 18 vlan10

R2#show ipv6 forwarding route 3555::55

IPv6 Routing Table:


3555::55/128 ospf6 10 vlan10 0 fe80:2e::2d0:d0ff:fe78:99dd

3500::55/128 ospf6 10 vlan20 0 fe80:2d::1416:15ff:fe14:1212

R2#ping6 3555::55


!!!!!



R3#show running-config ospfv3

! <OSPFV3>

ipv6 router ospf 1

router-id 1.1.1.5


$


$

!

! </OSPFV3>


OSPFv3 Process 1


10.10.10.10 1 FULL/DR 00:00:31 45 vlan20

S3(config)#show ipv6 forwarding route ospf

7-19



IPv6 Routing Table:

Headers: Dest: Destination, Gw: Gateway, Pri: Priority;

Codes : K: kernel, I1: isis-l1, SFN: sf-nat64, R: ripng, AF: aftr, B: bgp,

D: direct, I2: isis-l2, SLN: sl-nat64, O: ospfv3, D6: dhcp, P: ppp,

S: static, N: nd, V: vrrp, A: address, M: multicast, UI: user-ipaddr;

Dest Owner Metric

Interface Pri Gw

3550::52/128 O 1

vlan101 110 fe80::2d0:d0ff:fe0a:b20

3555::52/128 O 2


3611::/64 O 2


R3#ping6 3555::55


!!!!!


7-20


Chapter 8IS-ISv6 ConfigurationTable of Contents

IS-ISv6 Overview .......................................................................................................8-1Configuring IS-ISv6 ....................................................................................................8-2Maintaining IS-ISv6 ..................................................................................................8-14IS-ISv6 Configuration Examples...............................................................................8-18

8.1 IS-ISv6 OverviewThe Intermediate System-to-Intermediate System (IS-IS) protocol is a routing protocoldeveloped by the International Organization for Standardization (ISO) for CLNS. It is anetwork layer protocol of the OSI protocol suite. It has been expanded to support IProuting and form an integrated IS-IS protocol. The IS-IS protocol currently mentionedrefers to the integrated IS-IS protocol.

The IS-IS protocol is used as an Interior Gateway Protocol (IGP) in plenty of networks.Its operating mechanism is similar to that of the OSPF protocol. It divides a network intomultiple areas. The routers in an area can manage only the routing information in the area.This saves router costs and thus makes it suitable for large- and medium-scale networks.

The IS-IS protocol also uses Dijkstra's SPF algorithm to compute routes. It uses the SPFalgorithm to obtain the optimal route according to the link status database and then addsthe route to the IP routing table.

IS-IS is a routing protocol with high expansibility, so it can support the expansion of theCLNS routing protocol to support IPv4 and support IPv6.

Uni-topology IS-IS can only run a single SPF algorithm. The topologies corresponding toIPv4 and IPv6 must be identical and with special restriction. While the multi-topology IS-IScan run multiple SPF algorithms. Then the topologies corresponding to IPv4 and IPv6 maybe different and with certain flexibility.

RFC 5308 (Routing IPv6 with IS-IS) defines how to use IS-IS to support IPv6. It definestwo new Tag, Length, Values (TLVs): IPv6 Reachability TLV and IPv6 Interface AddressTLV.

l The TLV type value of the IPv6 Reachability TLV is 236 (0xEC). Its TLV effects areequal to the two TLVs of IPv4: IP internally reachable and IP externally reachable.Up/down and external are defined in this TLV and are used to indicate that routes areredistributed mutually in the L2/L1 and to determine whether a route is an externalroute.

8-1



l The TLV type value of the IPv6 Interface Address TLV is 232 (0xE8). Its TLV effectsare equal to the TLV of IPv4: IP port address. The difference is that the original 32-bitaddress segment is superseded by the 128-bit address segment in the new TLV.

l The operating principles of IS-ISv6 are similar to those of IS-ISv4. For details, pleaserefer to "IS-IS Configuration" in IPv4 Routing Volume.

8.2 Configuring IS-ISv6Configuring Basic InformationIn this manual, it is assumed that the process-id is 0, and the VLAN100 interface is used.

To configure the basic information about IS-ISv6, perform the following steps:


1 ZXR10(config)#router isis[process-id][vrf <vrf-name>] Enables the IS-ISv6 routing

protocol process.

ZXR10(config-isis-0)#system-id <system-id>[range<range-number>]

Configures the system ID of a

route instance.

2

ZXR10(config-isis-0)#area <area-address> Designates the area address

of IS-ISv6.

3 ZXR10(config-isis-0)#interface <interface-name> Adds an interface to the

IS-ISv6 route entity.

4 ZXR10(config-isis-0-if-vlan100)#ipv6 router isis Runs the IS-ISv6 protocol on

an interface.



[process-id] IS-IS process ID, range: 0-65535.

<vrf-name> Specifies the VRF name, range: 1-32 characters.



<system-id> Specifies the System ID of the instance, which is a

hexadecimal string of 6 bytes in the form of xxxx.xxxx.xxxx.

range <range-number> Specifies the extensible range of the System ID. The

value range is 0-32. The default value is 0. The instance

will assume an ID ranging from System ID to System

ID+<range-number>.

<area-address> Specifies the area address, which is a hexadecimal string

of 1 to 13 bytes.

8-2


Chapter 8 IS-ISv6 Configuration

Configuring IS-ISv6 Global ParametersIf all the routers in the network are the ZXR10, the default parameters can be used duringIS-IS configuration. If other vendors' routers exist in the network and interconnect with theZXR10, however, the relevant interface parameters and timers may need to be changedso as to enable the IS-IS protocol to run more efficiently in the network.

IS-IS parameter configuration includes the configuration of global parameters and theconfiguration of interface parameters. The global parameters of IS-ISv6 need to beconfigured in IS-ISv6 routing mode (some parameters are configured under the IS-ISv6address suite).

To configure the global information about IS-ISv6, perform the following steps:


1 ZXR10(config)#router isis [process-id][vrf <vrf-name>] Enables the IS-ISv6 routing

protocol process.

2.1 ZXR10(config-isis-0)#area <area-address> Designates the area

address of IS-ISv6.

2.2 ZXR10(config-isis-0)#system-id <system-id>[range <range-number>]

Configures the system ID of

IS-ISv6.

2.3 ZXR10(config-isis-0)#authentication-type {md5 |

text}[level-1 | level-2]

Configures the

authentication mode of

the IS-ISv6 route entity.

2.4 ZXR10(config-isis-0)#ignore-lsp-errors[disable] Sets the IS-ISv6 to ignore

LSP checksum errors.

2.5 ZXR10(config-isis-0)#is-type {level-1 | level-2-only

| level-1-2}

Configures the routing level

for a router.

2.6 ZXR10(config-isis-0)#lsp-refresh-time <interval> Configures the LSP refresh

time.

2.7 ZXR10(config-isis-0)#max-lsp-lifetime <interval> Configures the maximum

LSP life time.

2.8 ZXR10(config-isis-0)#metric-style {narrow | wide} Configures the metric style

of the router.

2.9 ZXR10(config-isis-0)#spf-interval

<interval>[level-1 | level-2]

Configures the minimum

interval at which the

IS-ISv6 makes topology

computation.

2.10 ZXR10(config-isis-0)#authentication {key |

encrypt <key>}[level-1 | level-2]Configures the LSP/SNP

authentication of IS-ISv6.

ZXR10(config-isis-0)#disable-snp-authentication Disables SNP

authentication.

2.11

2

8-3




This command must

be run to disable SNP

authentication if only

LSP authentication is

required after LSP/SNP

authentication is set.

ZXR10(config-isis-0)#enable-snp-authentication Enables SNP

authentication.

ZXR10(config-isis-0)#disable Disables the IS-ISv6

protocol.

2.12

ZXR10(config-isis-0)#enable Disables the IS-ISv6

protocol.

2.13 ZXR10(config-isis-0)#maximum-paths <number> Configures the maximum

number of next-hop paths.

2.14 ZXR10(config-isis-0)#lsp-mtu <size> Configures the size of LSP

packets.

2.15 ZXR10(config-isis-0-if-vlan100)#passive-mode

[with-original-metric]

Configures an interface as

an IS-ISv6 passive interface.

2.16 ZXR10(config-isis-0)#hostname dynamic {disable

| enable}

Configures the dynamic

host name mapping function

of IS-ISv6.

2.17 ZXR10(config-isis-0)#hello padding [multi-point |

point-to-point]

Pads 0 to each hello packet

sent on the interface till the

packet size equals the MTU

value of the interface.

3 ZXR10(config-isis-0)#address-family ipv6 Enters the IPv6 family

configuration mode.

4.1 ZXR10(config-isis-0-af)#distance <1-255> Configures the

administrative distance

of IS-ISv6 routes.

4.2 ZXR10(config-isis-0-af)#multi-topology Enables the multi-topology

function.

4.3 ZXR10(config-isis-0-af)#redistribute

<protocol>[level-1 | level-1-2 | level-2][metric<metric-value>][route-map <map-tag>]

Configures the redistribution

of routes from other routing

protocols into IS-ISv6.

4.4 ZXR10(config-isis-0-af)#set-overload-bi Sets the overload-bit in the

LSP packets sent by IS-IS

itself.

4

8-4




4.5 ZXR10(config-isis-0-af)#summary-prefix

X:X::X:X/<0-128>[ level-1 | level-1-2 | level-2 ][metric<metric-value>]

Configures IS-ISv6 route

aggregation.

4.6 ZXR10(config-isis-0-af)#route-leak {level 1|level

2} into {level2|level1}[route map<map tag>]Configures the leakage from

level-2 to level-1 routes.

4.7 ZXR10(config-isis-0-af)#distribute-list route-map

<map-tag> in

Configures IS-ISv6 route

filter policy.



vrf <vrf-name> Specifies the VRF name, which is a string of 1 to 32

characters.

Enable the IS-ISv6 protocol instance if the instance is not yet enabled, and then enter theroute configuration mode of the IS-ISv6 instance. Enable the IS-ISv6 VPN instance if VRFis configured.

For a description of the parameters in Step 2.1, refer to the following table:


<area-address> Specifies the area address, which is a hexadecimal string

of 1 to 13 bytes.



<system-id> Specifies the System ID of the instance, which is a

hexadecimal string of 6 bytes in the form of xxxx.xxxx.xxxx.

range <range-number> Specifies the extensible range of the System ID. The

value range is 0-32. The default value is 0. The instance

will assume an ID ranging from System ID to System

ID+<range-number>.

The IS-ISv6 protocol cannot be enabled if the system-id is not set.



md5 | text Indicates that the authentication mode is MD5 or text

authentication.

level-1 | level-2 Indicates the level to which the authentication mode applies.

8-5





level-1 | level-2-only | level-1-2 Specifies the level of the configured router. By default, a

router is a level-1-2 router.

This is a basic parameter involved in IS-IS configuration. It is used to define the operationtype of the router according to the practical networking condition. By default, IS-IS-enabledrouter is identified as a level-1-2 router.



<interval> Specifies the periodic LSP refresh interval in the unit of

seconds. The value range is 1-65535. The default value is

900 seconds.

Set the LSP refresh interval of the IS-IS protocol so that the LSP packets locally generatedare periodically updated when the network is stable. By default, LSP packets are refreshedat an interval of 900 seconds.



<interval> Specifies the maximum LSP lifetime in the unit of seconds.

The value range is 1-65535. The default value is 1,200

seconds.

Set the maximum LSP lifetime of the local IS-IS, that is, the lifetime of LSP packets locallygenerated in the databases of all the reachable nodes. By default, the maximum lifetimeof LSP packets is 1,200 seconds.



narrow | wide Specifies the metric type (narrow or wide).

The narrow mode uses only 6 bits to carry the metric value,

whereas the wide mode uses 24 bits to carry it and supports

more TLVs to be carried.

The metric range in the narrow mode is smaller than that in the wide mode. In addition, thewide mode supports more TLV extensions. By default, the metric-style is set to "narrow".Topology creation may fail due to inconsistent settings of the metric-type between the tworouters to be interconnected.


8-6




<interval> Specifies the interval in the unit of seconds. The value range

is 1-120. The default value is 10 seconds.

level-1 | level-2 Specifies the level of the topology computation interval.



encrypt <key> Specifies the encrypted key, which is a string of 24 to 140

characters.

<key> Specifies the plaintext key, which is a string of 1 to 100

characters.

level-1 | level-2 Specifies the authentication range. The default value is

level-1-2.

After configuring this command, you also need to set the same authentication code forSNP packets. By default, application also applies to SNP packets. To clear SNP packetauthentication, run the command disable-snp-authentication.



<number> Specifies the number of parallel routes supported. The value

range is 1-32.

If the maximum-paths parameter is not specified, only one parallel route is supported bydefault.



<size> Specifies the size of LSP packets in the unit of bytes. The

value range is 512-7680.

By default, the size of LSP packets transmitted on a broadcast link is 1,497 bytes. Youcan run this command to specify the LSP packet size to a value between 512 and 7,680bytes. It is not recommended that users run this command unless really necessary.



with-original-metric Using original metric of the interface.

8-7



You can set interfaces as passive interfaces. When an interface is set as a passiveinterface, its address information will be carried only in local LSP packets but the interfacewill not send packets.



dynamic Indicates that the system name is dynamically obtained.



<1-255> Specifies the distance. The value range is 1-255. The default

value is 115.

The administrative distance of an IS-ISv5 route is used for IPv6 route computation. Thesmaller the value, the better the IS-ISv6 route is than the routes obtained by other routingmeans or other routing protocols.



<protocol> Specifies the route origin, which can be "connect", "static",

"rip", "ospf", or "bgp". This parameter is mandatory. To

redistribute IS-IS/OSPF routes, it is necessary to specify the

instance number.

level-1 | level-2 | level-1-2 Specifies the redistribution range. The default value is

"level-2".

metric <metric-value> Specifies the metric value of the redistributed route. The

value range is 0-4261412864. The default value is 10.

route-map <map-tag> Specifies the route map name for the current protocol

redistribution, which is a string of 1 to 31 characters.

If the metric-style is narrow, the value range of <metric-value> is 0-63. If the metric-style iswide, the value range of <metric-value> is 0-426142864.



X:X::X:X/<0-128> Specifies the IPv6 network segment prefix.

8-8




level-1 | level-1-2 | level-2 Specifies the route aggregation level, which is "level-1-2" by

default.

When a local LSP packet of the corresponding level carries

non-local interface address information that indicates a route

with this network segment prefix, the route is then aggregated

to the set level according to the aggregate address.

metric <metric-value> Specifies the metric value of the redistributed route. The


The IS-ISv6 protocol may aggregate certain routing table entries into an aggregate routeand advertise it to other routers instead of advertising the specific routes.



route-map <map-tag> Specifies the route map name for protocol route redistribution,

which is a string of 1 to 31 characters.

Configuring IS-ISv6 Interface ParametersThe interface parameters of IS-ISv6 need to be set in interface mode. To configure theinterface parameters of the IS-ISv6 protocol, perform the following steps:


1 ZXR10(config)#router isis [process-id][vrf <vrf-name>] Enables the IS-ISv6 routing

protocol process.

2 ZXR10(config-isis-0)#interface <interface-name> Configures the IS-ISv6

protocol on the specified

interface.

3.1 ZXR10(config-isis-0-if-vlan100)#circuit-type

{level-1 | level-1-2 | level-2-only}

Configures the circuit-type

on an interface.

3.2 ZXR10(config-isis-0-if-vlan100)#csnp-interval


Configures the interval at

which the IS-ISv6 protocol

sends CSNP packets on an

interface.

3.3 ZXR10(config-isis-0-if-vlan100)#hello-interval




sends two consecutive hello

packets on an interface.

3.4 ZXR10(config-isis-0-if-vlan100)#hello-multipl

ier <multiplier>[level-1 | level-2]

Configures the IS-ISv6 hello

multiplier on an interface.

3

8-9




3.5 ZXR10(config-isis-0-if-vlan100)#lsp-interval




sends two consecutive

LSP packets on an

interface in the unit of

milliseconds. The value

range is 33-4294967040.

The default value is 33

millisecond.

3.6 ZXR10(config-isis-0-if-vlan100)#psnp-interval




sends PSNP packets on an

interface.

3.7 ZXR10(config-isis-0-if-vlan100)#ipv6 metric

<value>[level-1 | level-2]

Configures the IS-ISv6

metric on an interface.

3.8 ZXR10(config-isis-0-if-vlan100)#authenticatio

n-type {md5 | text}[level-1 | level-2]

Configures the

authentication mode of

IS-ISv6 hello packets.

3.9 ZXR10(config-isis-0-if-vlan100)#authenticat

ion {key| encrypt <key>|clear<key>}[level-1 | level-2]Configures the

authentication of IS-ISv6

hello packets.

3.10 ZXR10(config-isis-0-if-vlan100)#priority

<priority>[level-1 | level-2]

Configures the IS-ISv6

password on the broadcast

network interface.

3.11 ZXR10(config-isis-0-if-vlan100)#retransmit-i

nterval <interval>[level-1 | level-2]



retransmits LSP packets on

an interface.

3.12 ZXR10(config-isis-0-if-vlan100)#ipv6 router

isis

Enables the IS-ISv6 protocol

on an interface.

3.13 ZXR10(config-isis-0-if-vlan100)#max-burst

<number>

Sets the maximum number

of LSP packets to be sent

on an interface. The value


value is 1.

3.14 ZXR10(config-isis-0-if-vlan100)#mesh-group

{<mesh group number>| blocked}

Sets the mesh-group

function on an certain

interface.

8-10




3.15 ZXR10(config-isis-0-if-vlan100)#network

point-to-point

Enables a LAN network

interface to simulate a

point-to-point interface.

3.16 ZXR10(config-isis-0-if-vlan100)#metric

<value>[level-1 | level-2]

Configures IS-ISv6 metric

on an interface.



level-1 | level-1-2 | level-2-only Specifies the circuit type of an interface. Either option must

be selected. By default, the circuit type of an interface is

level-1-2.

This is a basic parameter involved in IS-IS configuration to specify the operation type foran interface. The default value is level-1-2. The value needs to match the IS-IS globaloperation type. The settings of this parameter must also be matched between two routersestablishing adjacency.



<interval> Specifies the interval at which the IS-ISv6 protocol sends

CSNP packets in the unit of seconds. The value range is

1-65535. The default value is 10 seconds for a broadcast link

and 3,600 seconds for a point-to-point link.

level-1 | level-2 Specifies the applicable scope of the CSNP interval (level-1

CSNP or level-2 CSNP). By default, the interval takes effect

for both level-1 and level-2.

The above parameters specify the CSNP packet sending interval. When the optionalparameter is not carried in the command, the set interval takes effect for both level-1 CSNPand level-2 CSNP on the interface.



<interval> Specifies the interval at which the IS-ISv6 sends hello

packets on an interface in the unit of seconds. The value


level-1 | level-2 Specifies the applicable scope of the hello interval (level-1

hello or level-2 hello). By default, the interval takes effect


8-11



When the optional parameter is not carried in the command, the set interval takes effectfor both level-1 hello and level-2 hello on the interface.



<multiplier> Specifies the IS-ISv6 hello multiplier on an interface. The


level-1 | level-2 Specifies the applicable scope of the hello multiplier (level-1

or level-2). By default, the hello multiplier takes effect for both

level-1 and level-2.

When the optional parameter is not carried in the command, the set multiplier takes effectfor both level-1 and level-2.



<interval> Specifies the interval at which the IS-ISv6 sends PSNP

packets on an interface in the unit of seconds. The value


level-1 | level-2 Specifies the applicable scope of the PSNP interval (level-1

PSNP or level-2 PSNP). By default, the interval takes effect


In general, PSNP is used in point-to-point networks. When the optional parameter is notcarried in the command, the set interval takes effect for both level-1 PSNP and level-2PSNP on the interface.



<value> Specifies the metric value of an interface. The value range

is 1-16777215. The set metric value takes effect after the

multi-topology function is enabled. The default value is 10.

level-1 | level-2 Specifies the applicable scope of the metric value (level-1

or level-2).

The above parameters set the metric value for IS-ISv6 SPF computation on an interface.When the optional parameter is not carried in the command, the metric-value takes effectfor both level-1 metric and level-2 metric on the interface.


8-12




md5 | text Indicates that the authentication mode is MD5 or text

authentication. By default, the text authentication mode

applies to hello packet authentication and takes effect for

both level-1 hello and level-2 hello.

level-1 | level-2 Indicates the level to which the authentication mode applies.



<priority> Sets the port priority in the unit of seconds. The value range

is 0-127. The default value is 64.

level-1 Indicates that the router is in the level-1 area.

level-2 Indicates that the router is in the level-2 area.

The above parameter settings exist only for broadcast links. When the optional parameteris not carried, the priority takes effect for both level-1 priority and level-2 priority.



<interval> Specifies the retransmission interval in the unit of seconds.

The value range is 1-65535. The default value is 5 seconds.

level-1 | level-2 Specifies the applicable scope of the LSP retransmission

interval (level-1 or level-2). By default, the interval takes

effect for both level-1 and level-2.

The above parameter settings exist only for point-to-point links. When the optionalparameter is not carried, the set retransmission interval takes effect for both level-1retransmission interval and level-2 retransmission interval.



<mesh group number> Specifies the mesh-group to which the interface belongs. The

value range is 1-4294967295.

blocked Indicates that LSP packets are blocked on the interface.



<value> Metric on an interface, The narrow mode value range is 1-63.

The wide mode value range is 1-16777215. The default

value of 10.

8-13




level-1 | level-2 Configures the valid range (level-1 or level-2) of the metric

value.

The above parameters are used to configure the metric value when the interfaceparticipates in IS-ISv6 shortest path calculation. When no optional parameter isconfigured, the metric value is valid for both level-1 and level-2 on the interface.

8.3 Maintaining IS-ISv6To maintain IS-ISv6, run the following commands:

Command Function

ZXR10(config)#show isis adjacency [level-1{ process-id }| level-2{

process-id }| process-id | up_time {level-1{ process-id }| level-2{

process-id }}]

Shows IS-ISv6 neighbor

information.

ZXR10(config)#show isis database [process-id|detail{process-id<process-id>}]

Shows the current IS-ISv6

database.

ZXR10(config)#show isis circuits [process-id|detail{process-id}] Shows IS-ISv6 port information.

ZXR10(config)#show isis ipv6 route [process-id |summary {

process-id<process-id>}]Shows the current IS-ISv6 route

table

ZXR10(config)#show isis ipv6 topology [level-1{process-id<process-id>}| level-2{process-id<process-id>}|process-id<process-id>]

Shows IS-ISv6 topology

information.

ZXR10(config)#show isis hostname [process-id<process-id>] Shows current IS-ISv6 hostname

information.

ZXR10(config)#show isis mesh-groups{blocked |

group}[process-id<process-id>]Shows IS-ISv6 mesh-group

information.



process-id<process-id> IS-IS instance number, range: 0–65535.

level-1 Shows the neighbors in the level-1 area.

level-2 Shows the neighbors in the level-2 area.

up_time Shows the neighbor up-time.

vrf <vrf-name> Specifies the VRF name, which is a string of 1 to 32

characters.

verbose Shows the current verbose database information.

The following is a sample output from the show isis adjacency command:

8-14



ZXR10(config)#show isis adjacency

Process ID: 1

Interface System id State Lev Holds SNPA(802.2) Pri MT

vlan1 1111.1111.1111 UP/UP L1L2 27/27 00E0.D023.0203 64/64

ZXR10(config-isis-0-if-vlan100)#show isis adjacency process-id 1

Process ID: 1


vlan2 AAAA.AAAA.AAAA UP L1 21 00E0.D023.0203 64

ZXR10(config-isis-0-if-vlan100)#show isis adjacency up-time level-1 process-id 1

Process ID: 1

Interface System id State Lev Holds Pri MT Time

vlan1 1111.1111.1111 UP L1 22 64 000:00:01:1

ZXR10(config)#

For a description of the sample output from the show isis adjacency command, refer to thefollowing table:


Process-id IS-IS instance number, range: 0–65535

Interface Indicates the interface name.

System ID Indicates the system ID of the neighbor, displayed as the

mapped hostname.

State Indicates the status, which may be "UP" or "INIT".

Level Indicates the level, which may be "L1", "L2", or "L1L2".

Holds Indicates the hold time.

SNPA Indicates the port address of the neighbor in the format of

<snpa type> xx.xx.xx.xx.xx.xx.

Pri Indicates the priority of DIS election.

MT Indicates that the peer supports multi-topology.

The following is a sample output from the show isis database command:

ZXR10#show isis database

Process ID:0

IS-IS Level-1 Link State Database:

LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL

NULL.00-00* 0x4 0xe750 858 0/0/0

NULL.02-00* 0x1 0x624f 770 0/0/0

sr1.00-00 0xe 0x8ebc 652 0/0/0

IS-IS Level-2 Link State Database:

LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL

NULL.00-00* 0x4 0xe750 858 0/0/0

NULL.02-00* 0x1 0x624f 770 0/0/0

sr1.00-00 0xe 0x8ebc 652 0/0/0

8-15



For a description of the sample output from the show isis database command, refer to thefollowing table:


Process-id IS-IS instance number, range: 0–65535.

LSP ID Indicates the LSP ID in the form of xxxx.xxxx.xxxx.xx-xx.

LSP Seq Num Indicates the LSP sequence number in the form of

0xdddddddd.

LSP Checksum Indicates the LSP checksum in the form of 0xdddd.

LSP Holdtime Indicates the LSP lifetime in the form of a common number.

ATT/P/OL Indicates the ATT (Whether to connect with external areas)

flag bit/partitioning bit/overload bit.

IS neighbor Indicates the IS neighbor.

IP-Internal/IP-External Indicates the reachable IP address.

Area Address Indicates the area address.

NLPID Indicates the supported protocol.

Hostname Indicates the host name.

Ip Address Indicates the port IP address.

IPv6 Address Indicates the port IPv6 address.

Inter-Domain Info Indicates the inter-domain information (Tag).

The following is a sample output from the show isis circuit command:

ZXR10(config)#show isis circuits

Process ID: 0

Interface State Lev CirId Level1-DR Level2-DR Pri(L1/L2)

vlan1 Up L1L2 2 Dis is me Dis is me 64/64

ZXR10(config)#

For a description of the sample output from the show isis circuit command, refer to thefollowing table:



Interface Indicates the interface name.

State Indicates whether the IS-IS protocol is enabled on the

interface. "UP" indicates that the IS-IS protocol is enabled.

"DOWN" indicates that the protocol is disabled.

Lev Indicates the port level, which can be "L1", "L2", or "L1L2".

CirId Indicates the port ID.

8-16




Level1–DR Indicates the level-1 designated router on the port, which can

be "xxxx.xxxx.xxxx.xx", "No found", "Disabled", "Dis is me",

"Point to point" and so on.

Level2–DR Indicates the level-2 designated router on the port, which can

be "xxxx.xxxx.xxxx.xx", "No found", "Disabled", "Dis is me",

"Point to point" and so on.

Pri(L1/L2) Indicates the L1/L2 priority set on the port.

The following is a sample output from the show isis ipv6 route command:

ZXR10(config)#show isis ipv6 route process-id 1

IS-IS Local IPv6 Routing Table

Codes: I1 - ISIS L1, I2 - ISIS L2

Porcess ID: 1

I1 1001::/64 [115/20]

via fe80::200:0:0:0,vlan2

I2 1002::/64 [115/30]

via fe80::200:0:0:0,vlan2

There are totally 2 routes.

ZXR10(config-isis-0)#show isis ipv6 rib summary process-id 1

Porcess ID: 1

There are totally 2 routes.

For a description of the sample output from the show isis ipv6 route command, refer to thefollowing table:


I1 ISIS L1 route information

I2 ISIS L2 route information

The following is a sample output from the show isis topology command:

ZXR10(config)#show isis ipv6 topology process-id 1

Process ID: 1

IS-IS IPv6 paths to Level-1 routers

System id Metric Next-Hop Interface SNPA

1111.1111.1111 10 1111.1111.1111 vlan1 00E0.D023.0203

2222.2222.2222 --



1111.1111.1111 10 1111.1111.1111 vlan1 00E0.D023.0203

2222.2222.2222 --

For a description of the sample output from the show isis topology command, refer to thefollowing table:

8-17





System id Indicates the system ID of the neighbor in the format of

xxxx.xxxx.xxxx.

Metric Indicates the metric to the neighbor.

Next-Hop Indicates the system-id of the next-hop router.

Interface Indicates the egress interface.

SNPA Indicates the port address of the neighbor in the format of

<snpa type> xx.xx.xx.xx.xx.xx.

8.4 IS-ISv6 Configuration Examples

8.4.1 Single-Area IS-ISv6 Configuration Example

Configuration DescriptionThis example shows how to configure the IS-ISv6 protocol on a single-area network shownin Figure 8-1.

Figure 8-1 Single-Area IS-ISv6 Configuration Example

Configuration Thought1. Enable the IPv6 protocol on the direct connection interfaces of S1 and S2, configure

IPv6 addresses for the direct connection interfaces, configure loopback interfaces,enable IPv6 on the loopback interfaces, and configure IPv6 addresses for the loopbackinterfaces.

2. Configure the IS-ISv6 protocol and ensure that the system-ids of the two routers arenot the same. If the IPv4 IS-IS protocol has been configured on certain interfaces ofthe two routers, set both routers to the multi-topology mode. To set the multi-topologymode, first set the metric type of the IS-IS protocol to "wide". If the IPv4 IS-IS protocolis not configured on any interface of the two routers, adjacency can be establishedthrough the default single-topology settings on the two routers. If any interface of eitherrouter is configured with an IPv4 address and the IS-IS protocol, IS-ISv6 neighborscan be established through the single-topology function on the two routers. In thelatter case, the interface needs to be configured with both an IPv4 address and an

8-18



IPv6 address as well as the commands ip router isis and ipv6 router isis. Here, themulti-topology environment is taken as an example.

3. Enable the IS-ISv6 protocol on the interfaces.4. Check and verify the configuration results: Neighbors are correctly established

between the routers, and each router correctly computes the IPv6 topology and cansuccessfully ping the loopback interface of the peer router.










S1(config)#router isis

S1(config-isis-0)#area 47.0005

S1(config-isis-0)#system-id 0000.0000.0011

S1(config-isis-0)#metric-style wide

S1(config-isis-0)#interface vlan10

S1(config-isis-0-if-vlan10)#ipv6 router isis

S1(config-isis-0-if-vlan10)#exit

S1(config-isis-0)#interface loopback5

S1(config-isis-0-if-loopback5)#ipv6 router isis

S1(config-isis-0-if-loopback5)#exit

S1(config-isis-0)#address-family ipv6

S1(config-isis-0-af)#multi-topology

S1(config-isis-0-af)#end

S2 configuration:










S2(config-isis-0)#area 47.0005



8-19












Configuration VerificationAfter the configuration is completed, run the show command on each router to check theconfiguration information: Neighbors are correctly established between the routers, andeach router correctly computes the IPv6 topology and can successfully ping the loopbackinterface of the peer router.

First verify the configuration results on S1. Run the command show running-config isis tocheck the IS-IS configuration information as follows:

ZXR10_S1#show running-config isis

! <ISIS>

router isis

area 47.0005

system-id 0000.0000.0011

metric-style wide

address-family ipv6

multi-topology

$

interface vlan10

ipv6 router isis

$

interface loopback5

ipv6 router isis

$

! </ISIS>

Run the command show isis adjacency to check whether the neighbor status is normal, thatis, check whether the state field is UP. After the neighbor is established, the state fieldshould indicate "UP":

ZXR10_S1#show isis adjacency


vlan10 0000.0010.0022 UP/UP L1L2 7/6 00D0.D0AF.CC10 64/64 M

Run the command show isis ipv6 topology to check whether the topology is correctlycomputed (For the single-topology environment, run the command show isis topologyinstead to check it). If the topology has been successfully computed, the execution results

8-20



will indicate the following item. If the metric is "–", it indicates the local router. If the metricis "xx", it indicates that the destination is unreachable.

ZXR10_S1#show isis ipv6 topology



0000.0010.0022 10 0000.0010.0022 vlan10 00D0.D0AF.CC10

0000.1122.1155 --



0000.0010.0022 10 0000.0010.0022 vlan10 00D0.D0AF.CC10

0000.1122.1155 –

Run the command show isis circuits to check the interface information and Designate IS(DIS) election. If the interface status is "UP", the interface is normal. If the interface statusis "DOWN", the interface is abnormal. Then it is necessary to check the link status. TheLevel1-DR item shows the system-id of the DIS.

ZXR10_S1#show isis circuits

IS-IS interface database:


loopback5 Up L1L2 0 No found No found 64/64

vlan10 Up L1L2 6 0000.0000.0010-03 0000.0000.0010-03 64/64

Run the command show ipv6 forwarding route isis_l1 or show ipv6 forwarding route isis_l2to check route advertisement. If route advertisement is normal, the route advertised by theloopback interface of the peer router can be seen.

ZXR10_S1#show ipv6 forwarding route isis_l1

IPv6 Routing Table:


3550::/64 isis_l1 20 vlan10 fe80:12::2d0:d0ff:feaf:cc10

If neighbor establishment and route advertisement are normal, the loopback interface ofthe peer route can be pinged through:

ZXR10_S1#ping6 3550::55


!!!!!


Similarly, verify the configuration results on S2 as follows:


! <ISIS>

router isis

area 47.0005

system-id 0000.0000.0010

metric-style wide

address-family ipv6

multi-topology

8-21



$

interface vlan10

ipv6 router isis

$

interface loopback5

ipv6 router isis

$

! </ISIS>



vlan10 0000.1122.1155 UP/UP L1L2 25/25 00D0.D078.99DD 64/64 M




0000.0010.0022 --

0000.1122.1155 10 0000.1122.1155 vlan10 00D0.D078.99DD



0000.0010.0022 --

0000.1122.1155 10 0000.1122.1155 vlan10 00D0.D078.99DD




loopback5 Up L1L2 0 No found No found 64/64

vlan10 Up L1L2 3 Dis is me Dis is me 64/64


IPv6 Routing Table:


3555::/64 isis_l1 20 vlan10 fe80:2e::2d0:d0ff:fe78:99dd

ZXR10_S2#ping6 3555::55


!!!!!


8.4.2 Multi-Area IS-ISv6 Configuration Example

Configuration DescriptionFor a large-scale network, the use of multiple areas shall be considered in IS-IS. Set thenear routers to be in one area according to their positions and functions because area

8-22



division is helpful to decrease the demand for memory, and the routers in each area onlyneed to maintain a smaller link state database.

Figure 8-2 shows a multi-area IS-IS instance. S1 is in Area 1, S2 in Area 0, and S3 andS4 in Area 2. On S1, perform route aggregation for the network segments in Area 1. Thedirect routes are redistributed to the IS-IS on R4.

Figure 8-2 Multi-Area IS-ISv6 Configuration Example

Configuration Thought1. Enable the IPv6 protocol on the interfaces, configure IPv6 addresses for these

interfaces, configure loopback interfaces, enable IPv6 on the loopback interfaces,and configure IPv6 addresses for the loopback interfaces.

2. Configure the IS-ISv6 protocol and ensure that the system-ids of the routers are notthe same. Establish L2 neighbors between S2 and S1/S3, and establish L1 neighborsbetween S3 and S4. Here, the multi-topology environment is taken as an example.

3. Enable the IS-ISv6 protocol on the interfaces.4. Enable route aggregation on S1.5. Redistribute the direct route on S4.6. Check and verify the configuration results: The routers can correctly establish

neighbors and correctly compute the IPv6 topology, and the interface addresses ofthe routers can be successfully pinged from each other








S1(config-if-loopback1)#ipv6 address 2000:0:0:1::1/64


8-23












S1(config-isis-0)#area 01


S1(config-isis-0)#is-type level-1-2




S1(config-isis-0-if-vlan10)#circuit-type level-2




S1(config-isis-0-if-loopback1)#circuit-type level-2












S1(config-isis-0-af)#summary-prefix 2000::/48


S2 configuration:




S2(config-if)#exit




S2(config-if)#exit



8-24




S2(config-isis-0)#is-type level-2













S3 configuration:




S3(config-if)#exit




S3(config-if)#exit




S3(config-isis-0)#is-type level-1-2













S4 configuration:




8-25



S4(config-if)#exit




S4(config-if)#exit




S4(config-isis-0)#is-type level-1












S4(config-isis-0-af)#redistribute connected level-1 metric 10


Configuration VerificationAfter the configuration is completed, run the show command on each router to check theconfiguration information: Neighbors are correctly established, the topology is computed,and interfaces can be pinged.

First verify the configuration results on S1. Run the command show running-config isis tocheck the IS-IS configuration information as follows:


! <ISIS>

router isis

area 01

system-id 0000.0000.0011

is-type level-1-2

metric-style wide

address-family ipv6

multi-topology

summary-address 2000::/48

$

interface vlan30

ipv6 router isis

circuit-type level-2-only

$

8-26



interface loopback1

ipv6 router isis


$

interface loopback2

ipv6 router isis


$

interface loopback3

ipv6 router isis


$

! </ISIS>

Run the command show isis adjacency to check whether the neighbor status is normal, thatis, check whether the state field is UP. After the neighbor is established, the state fieldshould indicate "UP":



vlan10 0000.0000.0012 UP L2 7 00D0.D078.99D2 64 M

Run the command show isis ipv6 topology to check whether the topology is correctlycomputed (For the single-topology environment, run the command show isis topologyinstead to check it). If the topology has been successfully computed, the execution resultswill indicate the following item. If the metric is "–", it indicates the local router. If the metricis "xx", it indicates that the destination is unreachable.




0000.0000.0011 --



0000.0000.0012 10 0000.0000.0012 vlan10 00D0.D078.99D2

0000.0000.0013 20 0000.0000.0012 vlan10 00D0.D078.99D2

0000.0000.0011 –

Run the command show ipv6 forwarding route isis_l2 to check route advertisement. If routeadvertisement is normal, the route advertised by the loopback interface of the peer routercan be seen.


IPv6 Routing Table:


2001::/64 isis_l2 10 vlan10 fe80:2e::2d0:d0ff:fe78:99d2



8-27



If neighbor establishment and route advertisement are normal, the loopback interface ofR4 can be pinged through:

ZXR10_S1#ping6 2400::4


!!!!!

Success rate is 100 percent(5/5),round-trip min/avg/max=97/120/156 ms.

Similarly, verify the configuration results on S2 as follows:


! <ISIS>

router isis

area 00

system-id 0000.0000.0012

is-type level-2-only

metric-style wide

address-family ipv6

multi-topology

$

interface vlan10

ipv6 router isis


$

interface vlan20

ipv6 router isis


$

! </ISIS>



vlan10 0000.0000.0011 UP L2 25 00D0.D078.99DD 64 M

vlan20 0000.0000.0013 UP L2 25 00D0.D078.99D3 64 M




0000.0000.0012 --



0000.0000.0012 --

0000.0000.0011 10 0000.0000.0011 vlan10 00D0.D078.99DD

0000.0000.0013 10 0000.0000.0013 vlan20 00D0.D078.99D3



8-28




vlan10 Up L2 3 Disabled Dis is me 64/64

vlan20 Up L2 2 Disabled 0000.0000.0013-01 64/64


IPv6 Routing Table:


2000::/48 isis_l2 10 vlan10 fe80:2e::2d0:d0ff:fe78:99dd



Verify the configuration results on S3 as follows:


! <ISIS>

router isis

area 02

system-id 0000.0000.0013

is-type level-1-2

metric-style wide

address-family ipv6

multi-topology

$

interface vlan20

ipv6 router isis


$

interface vlan30

ipv6 router isis

circuit-type level-1

$

! </ISIS>



vlan30 0000.0000.0014 UP L1 25 00D0.D078.99D4 64 M

vlan20 0000.0000.0012 UP L2 25 00D0.D078.99D2 64 M




0000.0000.0013 --

0000.0000.0014 10 0000.0000.0014 vlan30 00D0.D078.99D4



8-29



0000.0000.0013 --

0000.0000.0011 10 0000.0000.0012 vlan20 00D0.D078.99D2

0000.0000.0012 20 0000.0000.0012 vlan20 00D0.D078.99D2

ZXR10_S3#show ipv6 forwarding route

IPv6 Routing Table:





Verify the configuration results on R4 as follows:


! <ISIS>

router isis

area 02

system-id 0000.0000.0014

is-type level-1

metric-style wide

address-family ipv6

multi-topology

redistribute connected level-1 metric 10

$

interface vlan20

ipv6 router isis


$

! </ISIS>



vlan30 0000.0000.0013 UP L1 25 00D0.D078.99D3 64 M




0000.0000.0014 --

0000.0000.0013 10 0000.0000.0013 vlan30 00D0.D078.99D3

ZXR10_S4#show ipv6 forwarding route

IPv6 Routing Table:



ZXR10_S4#ping6 2000:0:0:1::1

sending 5,100-byte ICMP echoes to 2000:0:0:1::1,timeout is 2 seconds.

8-30



!!!!!


8-31




8-32


Chapter 9BGP4+ ConfigurationTable of Contents

BGP4+ Overview........................................................................................................9-1Configuring BGP4+ ....................................................................................................9-1Maintaining BGP4+ ....................................................................................................9-2BGP4+ Configuration Examples .................................................................................9-8

9.1 BGP4+ OverviewThe Border Gateway Protocol (BGP) is a routing protocol applied between ASs toexchange network reachability information between the ASs. The information covers alist of ASs that a route passes. It is sufficient for establishing a diagram indicating theconnection status of the ASs. This makes possible AS-based routing policies and at thesame time solves the route loop issue.

BGP4+ is an extension of BGP. It assumes the basic message format of BGP4 as definedin RFC 1771 but added with the extended attributes defined in RFC 2858 to transmit IPv6routing information, and processes all IPv6 routes according to RFC 1771. BGP4+ alsosupports the extended functions such as BGP route reflection and BGP alliance as definedin RFC 1966 and RFC 1997. It has the following features:

l Supporting route aggregationl Employing TCP as the bottom-layer protocol and using TCP port 179 to guarantee

reliable runningl Transmitting route updates onlyl Periodically sending the keepalive signal to guarantee normal TCP connectionsl Possessing complete metricsl Boasting of abundant attributes and powerful control functionsl Suiting huge networks

The operating principles of BGP4+ are similar to those of BGP. For details, please referto the "BGP Configuration" chapter in ZXR10 M6000 (V1.00.30) Carrier-Class RouterConfiguration Guide (IPv4 Routing Volume).

9.2 Configuring BGP4+The commands for configuring BGP4+ are similar to those for configuring BGP in IPv4,except that the ZXR10 5900E supports IPv6 address configuration. For details, pleaserefer to the "BGP Configuration" chapter in ZXR10 5950-H Series All Gigabit IntelligentRouting Switch Configuration Guide (IPv4 Routing Volume).

9-1



9.3 Maintaining BGP4+Common Maintenance Commands for Viewing InformationCertain debugging commands can be used to locate and remove BGP route faults. Theshow command is most commonly used and can be run on a router to show the currentBGP neighbors and the BGP routes learned by the router.

To maintain BGP, run the following commands:

Command Function

ZXR10(config)#show ip bgp protocol Shows configuration information

about the BGP protocol module.

ZXR10(config)#show bgp ipv6 unicast neighbor Shows BGP adjacency and the

current neighbor status.

ZXR10(config)#show bgp ipv6 unicast Shows the entries in the BGP

routing table.

ZXR10(config)#show BGP ipv6 unicast summary Shows the states of all BGP

neighbors.

The following is a sample output from the show ip bgp protocol command:

E1#show ip bgp protocol

BGP router ID is 1.1.1.11, Local as is 100

Hold time is 180 seconds, KeepAlive time is 60 seconds

Default local preference is 100

Default export metric is 0

IPv4 IGP synchronization is disabled

IPv6 IGP synchronization is disabled

Default information advertise is disabled

Always compare med is disabled

Fast fallover is enabled

Client-to-client reflection is enabled

Enforce-first-as is enabled

IPv4 client-number: 1

IPv4 unicast is activated

BGP FRR is disabled

BGP IPv6 frr is disabled

Router target is filtered

Graceful restart is disabled

As-path ignore is disabled

Router-id ignore is disabled

BGP advertise-active-only is disabled

BGP VPNv4 advertise-active-only is disabled

BGP IPv4 rib-only is disabled

9-2


Chapter 9 BGP4+ Configuration

BGP IPv6 rib-only is disabled

Route dampening is disabled

Distance : external 20 internal 200

RT constraint filter is enabled

Number of all peer : 8

Number of enabled peer : 8

Number of disabled peer : 0

Number of establised peer : 1

Number of actived ipv4 peer : 2

Number of actived ipv6 peer : 5

Number of actived vpnv4 peer : 1

Number of actived ipv4_multi peer : 0

For a description of the sample output from the show ip bgp protocol command, refer tothe following table:


Hold time is 180 seconds, KeepAlive

time is 60 seconds

Indicates that the hold time is 90 seconds and the keepalive

time is 30 seconds.

Default local preference is 100 Indicates that the default local preference is 100.

IPv4 IGP synchronization is disabled BGP routing table is synchronized with IPv4 IGP routing table

(by default, they are not synchronized).

IPv6 IGP synchronization is disabled BGP routing table is not synchronized with IPv6 IGP routing

table (by default, they are not synchronized).

Default export metric is 0 Indicates the default export metric is 0.

Distance : external 20 internal 200 Indicates that the external administrative distance is 20 and

the internal administrative distance is 200.

The following is a sample output from the show bgp ipv6 unicast neighbor command:

ZXR10#show BGP ipv6 unicast neighbor

BGP neighbor is 2002:9::2, remote AS 300, external link

BGP version 4, remote router ID 218.231.0.1

BGP state = Established, up for 00:13:58

Last read update 00:13:58, hold time is 90 seconds, keepalive interval is 30

seconds

Neighbor capabilities:

Route refresh: advertised and received

New ASN Capability: advertised

Address family IPv4 Unicast: received

IPv4 MPLS Label capability: received

Address family IPv4 Multicast: received

Address family VPNv4 Unicast: received

Address family IPv6 Unicast: advertised and received

IPv6 MPLS Label capability: received

9-3



Address family VPNv6 Unicast: received

Address family IPv6 Multicast: received

All received 31 messages

1 updates, 0 errs

1 opens, 0 errs

29 keepalives

0 vpnv4 refreshes, 0 ipv4 refreshes, 0 ipv4 multicast refreshes, 0 ipv6

refreshes, 0 ipv6 multicast refreshes, 0 vpnv6 refreshes, 0 errs

0 notifications, 0 other errs

After last established received 29 messages

1 updates, 0 errs

0 opens, 0 errs

28 keepalives


refreshes, 0 ipv6 multicast refreshes, 0 ipv6 vpn refreshes, 0 errs

0 notifications, 0 other errs

All sent 33 messages

5 updates, 1 opens, 27 keepalives


refreshes, 0 ipv6 multicast refreshes, 0 vpnv6 refreshes,0 notifications

After last established sent 31 messages



refreshes, 0 ipv6 multicast refreshes, 0 vpnv6 refreshes, 0 notifications

For address family: IPv4 Unicast no activate

All received nlri 0, unnlri 0, 0 accepted prefixes

All sent nlri 0, unnlri 0, 0 advertised prefixes

Maximum limit 4294967295

Threshold for warning message 75%

Minimum time between advertisement runs is 30 seconds

Minimum time between origin runs is 15 seconds

For address family: IPv4 Multicast no activate





For address family: VPNv4 Unicast no activate





For address family: IPv6 Unicast

Med attribute sent to this neighbor



9-4





For address family: VPNv6 Unicast no activate

Private AS number not removed from updates to this neighbor





For address family: IPv6 multicast no activate





Connections established 1

Local host: 2002:9::1, Local port: 4331

Foreign host: 2002:9::2, Foreign port: 179

For a description of the sample output, refer to the following table:


BGP neighbor is 2002:9::2, remote

AS 300, external link

The IP address is the peer BGP address of the TCP

connection. The peer belongs to AS 300. It is an EBGP

connection.

BGP version 4, remote router ID

218.231.0.1

BGP-4 is used. The peer BGP router ID is 218.231.0.1.

BGP state = Established, up for

00:13:58

Neighbor relation state is Established. The session has been

established for 13 minutes 58 seconds.

hold time is 90 seconds, keepalive

interval is 30 s

The hold time is 90 seconds, and the Keepalive interval is

30 seconds.

Neighbor capabilities: The capability to describe the peer.

Route refresh: advertised and

received

The neighbor supports enhanced router soft-reset.

Address family IP64 Unicast:

advertised and received

The neighbor supports unicast NLRI.

All received 31 messages

1 updates, 0 errs

1 opens, 0 errs

29 keepalives

Totally 31 messages are received, among which there is

1 open message, 1 update message and 29 keepalive

messages. There is no VPNV4 route update , no IPV4 route

update, no Notification message and no error message.

After last established received 29

messages

1 updates, 0 errs

0 opens, 0 errs

28 keepalives

Totally 29 messages are received since the neighbor

relationship was established last time, among which there is

1 update message and 28 keepalive messages.

9-5




All sent 33 messages 5 updates, 1

opens, 27 keepalives

Totally 33 messages are sent, among which there are 5

update messages, 1 open message and 27 keepalive

message.

After last established sent 31

messages


Totally 31 messages are sent since the neighbor relationship

was established last time, among which there are 5 update

message, 0 open message and 26 keepalive messages.

For address family: IPv4 Unicast no

activate

Indicates that unicast IPv4 routes are described below. IPv4

unicast function is not activated.

All received nlri 0, unnlri 0, 0 accepted

prefixes

There is no NLRI message, no withdraw message and no

unicast prefix received.

All sent nlri 0, unnlri 0, 0 advertised

prefixes

here is no NLRI message, no withdraw message and no

unicast prefix sent.



The maximum limit is 4294967295s. The threshold to send

warning messages is 75%.

For address family: IPv6 Unicast Indicates that unicast IPv6 routes are described below.

Med attribute sent to this neighbor MED attribute is sent to local device.

All received nlri 5, unnlri 0, 5 accepted

prefixes

There are 5 NLRI messages, no withdraw message and 5

unicast prefixes received.

All sent nlri 7, unnlri 6, 1 advertised

prefixes

There are 7 NLRI messages, 6 withdraw message and 1

unicast prefix received.



The maximum limit is 4294967295s. The threshold to send

warning messages is 75%.

For address family: VPNv6 Unicast

no activate

Indicates that unicast IPv6 routes are described below. IPv6

unicast function is not activated.

For address family: IPv6 multicast no

activate

Indicates that multicast IPv6 routes are described below.

IPv6 multicast function is not activated.

Connections established 1 BGP neighbor relationship is established once with the peer.

Local host: 2002:9::1, Local port:

4331

Local IP host, including local IP address and TCP port

number

Foreign host: 2002:9::2, Foreign port:

179

Peer IP host, including peer IP address and TCP port number

The following is a sample output from the show bgp ipv6 unicast command:

ZXR10#show bgp ipv6 unicast

Status codes: *valid, >best, i-internal

Origin codes: i-IGP, e-EGP, ?-incomplete

Network Next Hop Metric LocPrf RtPrf Path

*> 1:1::/32 2002:9::2 100 300 i

9-6



*> 1:1:1::/64 2002:9::2 300 i

*> 1:1:1:1::/64 2002:9::2 300 i

*> 1:1:1:2::/64 2002:9::2 300 i

*> 1:1:1:3::/64 2002:9::2 300 i

*> 1:1:1:4::/64 2002:9::2 300 i

A symbol "*" before a route entry indicates that the route is valid. A route marked withthe symbol ">" indicates that it is the optimal route. A route marked with the symbol "i"indicates that it is an IGP route. A route marked with the symbol "e" indicates that it isan EGP route. A route marked with the symbol "?" indicates that the origin of the route isincomplete.



Network Indicates the destination address.

Next-hop Indicates the next hop of the BGP route. A route with an

all-0s next hop indicates that the route is generated by the

local router itself.

Metric Indicates the route metric.

LocPrf Indicates the local preference of the routes learned by BGP.

RtPrf Distance of the route. The default distance of the

EBGP-advertised route is 20, and the distance of the

IBGP-advertised route is 200.

Path Indicates the route origin, which can be one of "IGP", "EGP"

and "incomplete".

The following is a sample output from the show bgp ipv6 unicast summary command:

ZXR10# show bgp ipv6 unicast summary

Neighbor Ver As MsgRcvd MsgSend Up/Down State/Pfx

Rcd

2002:2::2 4 400 7 11 00:15:45 Connect

2002:8::2 4 500 0 0 00:00:00 0

2002:9::2 4 300 37 38 00:17:44 5



Neighbor Indicates the BGP neighbor.

Ver Indicates the BGP version.

As Indicates the AS number of the neighbor.

MsgRcvd Indicates the number of messages received by BGP.

MsgSend Indicates the number of messages sent by BGP.

9-7




Up/Down(s) Indicates the connection establishment time.

State/PfxRcd Indicates the status of adjacency establishment. If the adjacency

has been established, a number is displayed to show the number of

received route entries. Otherwise, a letter is displayed to show the

status.

Common Alarm InformationThe system will present major alarms in the form of alarms. This section lists somecommon BGP alarms.

Alarm Code Description

Neighbor down/up BGP interface is up/down. Neighbor relationship is

established/un-established.

A complete alarm information record covers the alarm type, the alarm code, and theadditional information about the alarm. The alarm code indicates the essence of thealarm and enables the alarm console to learn what the alarm is. An alarm may also carrysome additional information such as the alarm cause. For details about BGP alarms,refer to the relevant alarm reference manual.

9.4 BGP4+ Configuration Examples

9.4.1 BGP4+ Route Reflector Configuration Example

Configuration DescriptionIn a network as shown in Figure 9-1, routers S1, S2, and S3 are Interior Border GatewayProtocol (IBGP)-based but not fully meshed. To eliminate full meshing for IBGP, a routereflector can be configured so that S3 can forward the routes it receives from an IBGPneighbor to another IBGP neighbor. Considering that the routers with IBGP are not fullymeshed in AS 200, a route reflector can be configured to avoid full meshing.

9-8



Figure 9-1 BGP4+ Route Reflector Configuration Example

Configuration Thought1. Enable BGP.2. Specify neighbors.3. Configure a route reflector group ID. Set the neighbors as route reflector clients.


S1(config)#router bgp 200

S1(config-bgp)#neighbor 3fe6::1 remote-as 100

S1(config-bgp)#neighbor 2010::126 remote-as 200

S1(config-bgp)#address-family ipv6

S1(config-bgp-af-ipv6)#neighbor 3fe6::1 activate

S1(config-bgp-af-ipv6)#neighbor 2010::126 activate

S1(config-bgp-af-ipv6)#end

S2 configuration:


S2(config-bgp)#neighbor 6e22::1 remote-as 500



S2(config-bgp-af-ipv6)#neighbor 6e22::1 activate



S3 configuration:



9-9







S3(config-bgp-af-ipv6)#neighbor 2010::125 route-reflector-client

S3(config-bgp-af-ipv6)#neighbor 3331::101 route-reflector-client


9.4.2 BGP4+ General Configuration Example

Configuration DescriptionThis example describes how to configure BGP4+. It involves the practical use of BGP4+,such as IBGP/EBGP neighbor establishment, routing policy, route redistribution, andMessage Digest 5 Algorithm (MD5) encryption.

As shown in Figure 9-2, EBGP neighbors are established between S4 and S1, IBGPneighbors are established between S1 and S2, and multi-hop EBGP neighbors areestablished between S2 and S5. S2 and S5 establish an EBGP multi-hop relation throughS3. Before BGP is configured, it is necessary to ensure that the addresses used forneighbor establishment between the two routers can interwork with each other (via IGP;IGP configuration is omitted in this example).

Figure 9-2 BGP4+ General Configuration Example

Configuration Thought1. Create a BGP4 instance.2. Configure BGP4+ neighbors and routing policies.3. Configure the redistribution command and enable neighbors to advertise routes.

9-10








S4(config-bgp-af-ipv6)#redistribute static


S1 configuration:








S2 configuration:




S2(config-bgp)#neighbor 2007::5 ebgp-multihop

S2(config-bgp)#neighbor 2007::5 password hello





S5 configuration:

ZXR10_S5(config)#router bgp 3


S5(config-bgp)#neighbor 2005::2 ebgp-multihop

S5(config-bgp)#neighbor 2005::2 password hello




Configuration VerificationRun the command show bgp ipv6 unicast summary on S1 to check the adjacency, as shownbelow:

ZXR10_S1(config)#show bgp ipv6 unicast summary

Neighbor Ver As MsgRcvd MsgSend Up/Down State/PfxRcd

2003::2 4 1 12 12 00:25:34 0

9-11



2001::4 4 2 14 14 00:28:06 4

Run the command show bgp ipv6 unicast on S1 to check the routing table, as shown below:

ZXR10_S1(config)#show bgp ipv6 unicast




*> 2004:1::/64 2001::4/64 2 ?

*> 2004:2::/64 2001::4/64 2 ?

*> 2004:3::/64 2001::4/64 2 ?

*> 2004:4::/64 2001::4/64 2 ?

Run the command show bgp ipv6 unicast summary on S2 to check the adjacency, as shownbelow:



2003::1 4 1 12 12 00:25:34 4

2007::5 4 3 15 15 00:32:30 0






*> 2004:1::/64 2003::1/64 100 2 ?

*> 2004:2::/64 2003::1/64 100 2 ?

*> 2004:3::/64 2003::1/64 100 2 ?

*> 2004:4::/64 2003::1/64 100 2 ?

Run the command show bgp ipv6 unicast summary on S4 to check the adjacency, as shownbelow:



2001::1 4 1 14 14 00:28:06 0






*> 2004:1::/64 :: 2 ?

*> 2004:2::/64 :: 2 ?

*> 2004:3::/64 :: 2 ?

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

Run the command show ip bgp summary on S5 to check the adjacency, as shown below:


9-12




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






*> 2004:1::/64 2005::2/64 1 2 ?

*> 2004:2::/64 2005::2/64 1 2 ?

*> 2004:3::/64 2005::2/64 1 2 ?

*> 2004:4::/64 2005::2/64 1 2 ?

9-13




9-14


Chapter 10IPv6 QoS ConfigurationTable of Contents

IPv6 QoS Overview ..................................................................................................10-1Configuring IPv6 QoS...............................................................................................10-1IPv6 QoS Configuration Examples ...........................................................................10-1

10.1 IPv6 QoS OverviewIPv6 QoS is added with IPv6 support in addition to the functions of IPv4 QoS. For detailsabout QoS, refer to the section about the general description and principles of QoS in theQoS Volume.

10.2 Configuring IPv6 QoSThe commands for configuring IPv6 QoS are similar to those for configuring IPv4 QoS,except that IPv6 addresses are involved during the configuration. For details about theconfiguration commands, refer to the section about QoS configuration in the QoS Volume.

10.3 IPv6 QoS Configuration Examplesl Configuration Description

As shown in Figure 10-1, user1 accesses the system via the interface gei-0/1/1/1whereas user2 accesses the system via the interface gei-0/1/1/2. The DSCP valuesare 1 and 2 respectively. Packets are sent via the interface gei-0/1/1/3.

According to the requirements, the DSCP values of the packets of the two users sentvia the interface gei-0/1/1/3 should be 7, the guaranteed bandwidth should be 100 M,and the maximum bandwidth should be 150 M.

10-1



Figure 10-1 IPv6 CAR SET Configuration Example

l Configuration Thought

Configure two Committed Access Rates (CARs) in the downlink of the interfacegei-0/1/1/3, match them with DSCP values 1 and 2 respectively, and set the DSCPvalue of the permitted traffic to 7. Set the guaranteed bandwidth to 100 M, and setthe maximum bandwidth to 150 M.

l Configuration Commands1. Enter the QoS configuration mode:

ZXR10(config)#pm-qos

ZXR10(config-qos)#

2. Configure QoS commands:ZXR10(config-pm-qos)#conform-dscp 1700

ZXR10(config-pm-qos)#conform-dscp 2710

ZXR10(config-pm-qos)#trust-dscp gei-0/1/1/3 enable

ZXR10(config-pm-qos)#traffic-shape gei-0/1/1/3 queue 0 min-gua-datarate

100000 max-datarate-limit 150000

l Configuration Verification

Run the command show running-config pm-qos to check the CAR SET configured onthe interface:

ZXR10(config-pm-qos)#show running-config pm-qos

!

pm-qos

traffic-shape gei-0/1/1/3 queue 0 min-gua-datarate 100000

max-datarate-limit 150000

traffic-shape gei-0/1/1/3 queue 1 min-gua-datarate 100000

max-datarate-limit 150000

conform-dscp 1700

conform-dscp 2710

trust-dscp gei-0/1/1/3 enable

!

10-2


Chapter 11IPv6 Multicast ConfigurationTable of Contents

IPv6 Multicast Overview ...........................................................................................11-1Configuring Public IP Multicast .................................................................................11-3

11.1 IPv6 Multicast OverviewIntroduction to MulticastAs a replacement of IPv4, IPv6 uses 128–bit address structure to solve the problem of IPaddress shortage. Meanwhile, IPv6 optimizes some characteristics. IPv4 multicast solvesthe problem of single-point sending and multi-point receiving, and it realizes high-efficiencypoint-to-multipoint data transmission. It saves a lot of network bandwidths and reducesnetwork load. Therefore, multicast is applied and enhanced in IPv6.

The most obvious difference between IPv6 multicast and IPv4 multicast is that IPv6multicast address mechanism is improved. The group member management, multicastpacket forwarding and multicast path establishment of IPv6 are similar to those of IPv4.

Multicast AddressAn IPv6 address is of 128–bit long, divided by colons into eight bytes with four hex numbersin each byte, such as FEDC:BA98:7654:3210:FEDC:BA98:7654:3210. An IPv6 multicastaddress identifies a group of interfaces that belong to different nodes. A node can belongto 0 or several multicast groups. A packet sent to a multicast address is received by allinterfaces identified by the multicast address.

According to RFC 4291, some IPv6 multicast addresses have been allocated permanently,as described in Table 11-1.

Table 11-1 IPv6 Multicast Address Allocation

Name Address Description

Reserved multicast address FF0x:: Not allocated to any multicast

address

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

FF02::1 (link-local)

-

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

FF02::2 (link-local)

FF05::2 (site-local)

-

11-1



Name Address Description

Requested node multicast

addresses

FF02::1:FFxx:xxxx Consisting of the address

prefix FF02::1:FF00:/104 (in

front) and low 24 bits of a

unicast or anycast address of a

requested node. For example,

4307::01:800:200E:8C6C

is corresponding to

FF02::1:FF0E:8C6C.

RFC 3306 defines amode to allocate IPv6multicast addresses dynamically, that is, an IPv6multicast address on the basis of unicast prefix. A such IPv6multicast address includes theunicast address prefix of its multicast source network. Global-unique multicast addressescan be allocated in this way. The address structure is shown in Figure 11-1.

Figure 11-1 Structure of IPv6 Multicast Address on Basis of Unicast Prefix

IPv6 Multicast ProtocolsThe multicast protocols supported by IPv6 include Multicast Listener Discovery (MLD),MLD Snooping, IPv6 Protocol Independent Multicast (PIM) and IPv6 MBGP.

1. Multicast routing group management protocol

MLD originate from Internet GroupManagement Protocol (IGMP). MLDv1 correspondsto IGMPv2, and Multicast Listener Discovery Version 2 (MLDv2) corresponds toIGMPv3. Different from IGMP which uses message type of IP protocol number 2,MLD uses message type of ICMPv6 (the IP protocol number is 58), including MLDQuery message (type value is 130, MLDv1 Report message (type value is 131),MLDv1 Leaving message (type value is 132) and MLDv2 Report message (typevalue is 143). MLD acts completely the same as IGMP does excepts for the messagestructure.

MLD Snooping is similar to IGMP Snooping.

2. Multicast routing protocol

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

11-2


Chapter 11 IPv6 Multicast Configuration

When IPv6 PIM sends a protocol message (such as PIM Hello, Join-Prune, Assert,Bootstrap, Graft, Graft-Ack or State-refresh) of link-local range, the source IPv6address of the message is the link-local address on the interface that sendsthe message. When IPv6 PIM sends a protocol message (such as Register,Register-Stop or C-RP Advertisement), the source IPv6 address of the message isthe global unicast address on the interface that sends the message.

IPv6 multicast does not support Multicast Source Discovery Protocol (MSDP). Thereare two ways to receive multicast data from other IPv6 PIM domains.

a. One way is to obtain the multicast source addresses in other IPv6 PIM domainsdirectly through other modes (such as advertisement) and use IPv6 PIM-SSM toinitiate joins of specific source groups.

b. The other way is to use embedded Rendezvous Point (RP) mechanism. Thedevice can obtain the RP addresses in other IPv6 PIM domains through the IPv6multicast addresses with embedded RP addresses, and initiate joins to the RPsin other domains. To deliver inter-domain IPv6 multicast routing information, IPv6MBGP can be used, which is similar to IPv4 MBGP.

11.2 Configuring Public IP MulticastTo configure public IPv6 multicast on ZXR10 5900E, perform the following steps.


ZXR10(config)#ipv6 multicast-routing Enables IPv6 multicast

function.

1

ZXR10(config)#no ipv6 multicast-routing Deletes all IPv6 multicast

functions.

2 ZXR10(config-mcast-ipv6)#router pimsm Enters PIM-SM mode.

3 ZXR10(config-pimsm-ipv6)#exit Exits from PIM-SM mode.

4 ZXR10(config-mcast-ipv6)#show ipv6 mroute [group<group-address>][source <source-address>]

Shows information in the IPv6

multicast routing table.

5 ZXR10#show ipv6 rpf<source-address> Shows the Reverse Path

Forwarding (RPF) information.

The RPF information that PIM

is not concerned about will not

be displayed by this command.

6 ZXR10#clear ipv6 mroute[group-address <group-address>][source-address<source-address>]

Clears multicast routes.

7 ZXR10#show ipv6 mroute summary Shows the number of IPv6

multicast routing tables.

8 ZXR10#show ipv6 mroute brief Shows the brief information of

an IPv6 multicast routing table.

11-3



The command parameters in Step 4 are described as follows:


<source-address> Source address, in the X:X::X:X format

<group-address> Group address, in the X:X::X:X format

The command parameter in Step 6 is described as follows:


<group-address> Group address, in the X:X::X:X format

11-4


Chapter 12MLD ConfigurationTable of Contents

MLD Overview..........................................................................................................12-1Configuring MLD ......................................................................................................12-2Maintaining MLD ......................................................................................................12-6MLD Configuration Examples ...................................................................................12-8

12.1 MLD OverviewMLD originate from IGMP. MLDv1 corresponds to IGMPv2, and MLDv2 corresponds toIGMPv3. Different from IGMP which uses message type of IP protocol number 2, MLDuses message type of ICMPv6 (the IP protocol number is 58), including MLD Querymessage (type value is 130, MLDv1 Report message (type value is 131), MLDv1 Leavingmessage (type value is 132) and MLDv2 Report message (type value is 143). MLD actscompletely the same as IGMP does excepts for the message structure.

MLD provides the information that is needed in the last state to forward a multicast packetto the destination. The multicast router exchanges information with the host receiving themulticast data. The information is collected from the group members of hosts that connectto the multicast router directly.

MLD mainly uses two types of messages, group member query message and groupmember report message. The multicast router sends group member query messages toall hosts periodically to know the group members on the interconnected subnets. Eachhost replies with a member report message to report the multicast group which it belongsto. When a host joins a new group, it sends a join message immediately instead of waitingfor a query in case it is the first member of the group.

When a host begins to receive information as a member of a group, the multicast routerwill query the group periodically to check whether there is any member in the group. Aslong as there is one host, the multicast router continues forwarding data.

When a host leaves a group, the multicast router receives a leaving message, and then itqueries whether there is any other active member in the group immediately. If there is any,the multicast router continue forwarding data. Otherwise, it will not forward data any more.

At present, there are two versions of MLD. MLDv1 corresponds to IGMPv2, and it providesthe fast leaving mechanism of group members. MLDv2 corresponds to IGMPv3, and itprovides to receive or refuse to receive packets from designated multicast sources, thusto support SSM.

12-1



12.2 Configuring MLDTo configure MLD on the ZXR10 5900E, perform the following steps:


ZXR10(config-mcast-ipv6)#router mld1

ZXR10(config-mcast-ipv6)#no router mld

Enters MLD mode. This is

not related to whether MLD

is enabled. That whether

MLD is enabled id controlled

by IPv6 multicast-routing.

Use the no format of this

command to delete all MLD

configuration and restore the

default configuration.

ZXR10(config-mcast-mld-ipv6)#interface

<interface_name>

2

ZXR10(config-mcast-mld-ipv6)#no interface

<interface_name>

Enters MLD interface

configuration mode. This

is not related to whether MLD

is enabled on an interface.

That whether MLD is enabled

on an interface is controlled by

whether PIM is enabled on an

interface. Use the no format

of this command to delete

the interface configuration

and restore the default

configuration.

3 ZXR10(config-mcast-mld-ipv6)#ssm-map static

{<access-list-number>|default}<source-address>

Configures mapping from

groups in a specified range to

the source.

4 ZXR10(config-mcast-mld-ipv6)#require-alert-options Discards the MLD packets

without carrying the

Router_Alert_Options option in

IPv6 headers.

To restore the default setting,

run the no form of this

command.



<intf-name> Interface name


12-2


Chapter 12 MLD Configuration


<access-list-number> SSM group access list name, with 1-31 characters

<source-address> Source address, in the X:X::X:X format

The MLD function on ZXR10 5900E is on the basis of PIM interface. The MLD functionwill be enabled automatically after PIM is enabled on an interface.

Configuring MLD VersionAt present, there are MLDv1 andMLDv2. Version 2 is applied by default. Users can set theversion with the version <version> command according to demand. Considering security,it is required to use the same version on the network elements in the same segment. MLDversion configuration is on the basis of interface. Different versions can be configured ondifferent interfaces of the same device.

Configuring an MLD Group on an InterfaceTo configure an MLD group on the ZXR10 5900E, perform the following steps:


ZXR10(config-mcast-mld-if-interface-name)#access-

group <access-list-number>

Configures the range of groups

allowing MLD join.

1

ZXR10(config-mcast-mld-if-interface-name)#no

access-group

Deletes the join group.

ZXR10(config-mcast-mld-if-interface-

name)#static-group <group-address>[source

{<source-address>[{include|exclude}]|ssm-map}]

Binds a group address on an

interface statically.

2


static-group<group- address>[source {<source-address>|

ssp-map}]

Deletes the static group

member on an interface.

ZXR10(config-mcast-mld-if-interface-name)#immed

iate-leave {<access-list-name>|all}

Configure the range of

groups allowing MLD leaving

immediately.

3


immediate-leave

Deletes the function of allowing

MLD leaving immediately.

ZXR10(config-mcast-mld-ipv6)#querier-election disable Configures querier election

evading.

4

ZXR10(config-mcast-mld-ipv6)#no querier-election

disable

Deletes querier election

evading.

12-3




ZXR10(config-mcast-igmp-if-interface-name)#join-g

roup <group-address>

Configures members for the

static group on the IGMP

interface.

To delete all members from

the static group on the

interface, run the no form of

this command.

5

ZXR10(config-mcast-igmp-if-interface-name)#no

join-group <group-address>

Deletes the static group

member from the interface.



<access-list-number> Standard IP access list name, with 1-31 characters



<group-address> Static MLD join group address, in the X:X::X:X format

<source-address > Source address, in the X:X::X:X format



<access-list-number> Standard IP access list name, with 1-31 characters

By default, when a device receives an MLD leaving message, the group member will leavethe group if it does not receive any report message within (last member query interval *2 + 1) seconds. If no option is configured in the command, it takes effect in all multicastgroups.

Configuring MLD TimersAfter MLD is enabled on interfaces of multicast routers in a shared segment, an optimalinterface will be elected as the querier of the segment to obtain group member informationby sending query messages.

After sending a query message, the querier waits for a period to receive the reportmessages from member hosts. The period is the value of the maximum response timecontained in the query messages. By default, the period is 10 seconds.

After receiving the query message, a member host in the segment will subtract a randomvalue on the basis of the maximum response time. It uses the result as its response time.If the querier receives a report message from another member host during this period,the host cancels to send a report message. If the querier does not receive any report

12-4



message from any other member hosts when the period expires, the member host willsend a report message. Increasing the maximum response time also increases the waitchances of group members in the segment, and reduces the rate that several hosts sendreport messages in the segment.

Users can set the timers related to the querier according to demand.

To configure MLD timers on the ZXR10 5900E, perform the following steps:


ZXR10(config-mcast-mld-if-interface-name)#quer

y-interval <seconds>

Configures the MLD common

query interval.

1


query-interval


the MLD query-interval.

ZXR10(config-mcast-mld-if-interface-name)#query-

max-response-time <seconds>

Configures the maximum

response time contained in

query messages.

2


query-max-response-time

Restores the default maximum

response time.

ZXR10(config-mcast-mld-if-interface-name)#queri

er-timeout <seconds>

Configures the MLD querier

timeout time.

3


querier-timeout

Restores the default MLD

querier timeout time.

ZXR10(config-mcast-mld-if-interface-name)#last-me

mber-query-interval <seconds>

Configures MLD query-interval

of a specified group.

4


last-member-query-interval

Restores the default MLD

query-interval of a specified

group.

ZXR10(config-mcast-mld-if-interface-name)#robu

stness-count <times>

Configures the allowed packet

loss times. <times>: The

allowed packet loss times + 1.

Range: 2-7.

5


robustness-count


the robust variable.



<seconds> The interval for sending common query packets by the MLD,

in the range of 1-65535, in the unit of second, with the default

value of 125.


12-5




<seconds> Time value, in the range of 1-25, in the unit of second, with

the default value of 10.



<seconds> Querier timeout period, in the range of 60-300, in the unit of

second, with the default value of 255.



<seconds> Query interval, in the range of 1-25, in the unit of second, with

the default value of 1.



<times> Robust variable. Range: 2–7, default: 2.

12.3 Maintaining MLDTo maintain MLD, run the following commands:

Command Function

ZXR10#show ipv6 mld interface [<interface-name>] Shows MLD configuration on an

interface.

ZXR10#show ipv6 mld groups{[<interface-name >], [<group-address

>]}[detail ]

Shows MLD group join information

on an interface.

ZXR10#show ipv6 mld packet-count [<interface-name>] Shows statistics counts of MLD

protocol messages sent and

received.

ZXR10#clear ipv6 mld groups [<interface-name>] Clears multicast groups that are

joined dynamically.

ZXR10#clear ipv6 mld packet-count[<interface-name>] Clears statistics counts of MLD

protocol messages sent and

received.


12-6




<interface-name> Interface name.

<group-address > The address of the group that the static MLD joins in. Format:

X:X::X:X.

The following is a sample output from the show ipv6 mld interface command:

ZXR10#show ipv6 mld interface vlan10

Internet address is fe80::2e0:d0ff:fe21:203

MLD is enabled on interface

Current MLD version is 2

MLD query interval is 125 seconds

MLD last member query interval is 1 seconds

MLD query max response time is 10 seconds

MLD querier timeout period is 255 seconds

MLD robustness variable is 2

MLD querier is fe80::2e0:d0ff:fe21:203, never expire

Inbound MLD access group is not set

MLD immediate leave control is not set

The following is a sample output from the show ipv6 mld groups command:

ZXR10(config-pimsm-ipv6-if)#show ipv6 mld groups

Group addr Interface Present Expire Last Reporter

ff88::1 loopback1 00:00:16 never ::

ff88::2 loopback1 00:00:16 never ::



Group addr Group address.

Interface Interface.

Present The time when the group member is present.

Expire Remaining time to Expire the timer. The information "never"

indicates that there is a static group and the timer is not

enabled.

Last Reporter The address of the host that reports group member

information last time.

12-7



12.4 MLD Configuration Examples

12.4.1 MLDv2 Configuration Example

Configuration DescriptionAs shown in Figure 12-1, PIM-SM is enabled on S1 and S2. TheMLD version is v2. MLDv1elects a querier through common query messages. The MLDv2 router with the smallestIP address is elected as the querier.

Figure 12-1 MLDv1 Configuration Example

Configuration Thought1. Configure addresses on the interfaces of the routers in interface configuration mode.

The address of S1 should be smaller than that of S2.2. Enable multicast function by configuring ipv6 multicast-routing.3. Enter PIM route mode and then enter the interfaces.4. Enable PIM-SM in interface configuration mode.






S1(config)#ipv6 multicast-routing

S1(config-mcast-ipv6)#router pim

S1(config-mcast-ipv6-pim)#interface vlan1

S1(config-mcast-ipv6-pim-if-vlan1)#pimsm

S1(config-mcast-ipv6-pim-if-vlan1)#end

S2 configuration:








12-8





Configuration VerificationCheck and verify the configuration results as follows on S1:

S1#show ipv6 mld interface vlan1

vlan1

Internet address is 100::1








MLD querier is fe80::2d0:d0ff:fe06:606, never expire





vlan2












12.4.2 Static Group Configuration Example

Configuration DescriptionAs shown in Figure 12-2, PIM-SM is enabled on S1. The MLD version is v2 (default). Itis required to configure S1 to join a static group ffee::1, and configure it to join a dynamicgroup ffee::2 through a tester.

12-9



Figure 12-2 Static Group Configuration

Configuration Thought1. Configure addresses on the interfaces of the routers in interface configuration mode.2. Enable multicast function by configuring ipv6 multicast-routing.3. Enter PIM route mode and then enter the interfaces.4. Enable PIM-SM in interface configuration mode.5. Enter MLD route mode from multicast mode and then enter the interfaces.6. Configure static group join on vlan1 of S1.7. Send MLD group join messages to S1 on the PC.











S1#configure terminal


S1(config-mcast-ipv6)#router mld

S1(config-mcast-ipv6-mld)#interface vlan1

S1(config-mcast-ipv6-mld-if-vlan1)#static-group ffee::1 source 200::1

S1(config-mcas-ipv6-mld-if-vlan1)#end

Configuration VerificationView interface information on S1:


vlan1







12-10








View the detailed information of corresponding interface on S1:

S1#show ipv6 mld groups vlan1 detail

Flags: S - Static Group, SSM - SSM Group

Interface: vlan1

Group: ffee::

Flags: S

Uptime: 21:51:24

Group mode: INCLUDE

Last reporter: fe80::2d0:d0ff:fe06:606

Group source list is empty

Interface: vlan1

Group: ffee::1

Flags: S

Uptime: 21:51:20

Group mode: INCLUDE


Group source list: (R - Report, M - SSM Mapping, S - Static)

Source addr Present Expires Fwd Flag

200::1 00:03:50 Never Yes S

Interface: vlan1

Group: ffee::2

Flags: S

Uptime: 21:51:18

Group mode: INCLUDE



Interface: vlan1

Group: ffee::3

Flags: S

Uptime: 21:51:16

Group mode: INCLUDE



12-11




12-12


Chapter 13IPv6 PIM-SM ConfigurationTable of Contents

PIM-SM Overview ....................................................................................................13-1Configuring IPv6 PIM-SM .........................................................................................13-3IPv6 PIM-SM Maintenance and Diagnosis................................................................13-9IPv6 PIM-SM Configuration Example......................................................................13-16

13.1 PIM-SM OverviewIntroduction to PIM-SMPIM-SM is mainly used in the following situations:

l Group members locate sparsely in a relatively large scale.l The network bandwidth resource is limited.

PIM-SM does not depend on a specific unicast routing protocol. PIM-SM assumes thatall routers on a shared segment do not need to send multicast packets. The routers onlycan receive and send multicast packets after they request to join a multicast group ontheir own initiative. PIM-SM advertises the multicast information to all routers supportingPIM-SM through a RP. In PIM-SM, a router joins or leaves the multicast group explicitly.This reduces the number of packets and the bandwidth used by the control packets.

PIM-SM PrinciplePIM-SM sends multicast packets by using a shared tree. A shared tree has a center pointthat is responsible for sending packets to all the source-sending ends in the multicastgroup. Each source-sending end sends packets to the center point along the shortestpath, and then takes the center point as the root point to distribute the packets to variousreceiving ends of the group.

The group center point of the PIM-SM is called the RP. There may be several RPs in anetwork, but there is only one RP in a multicast group.

A switch can obtain the location of the RP in two ways.

1. Configure the RP manually and statically on the switches running PIM-SM.2. PIM-SMv2 obtains the location through the candidate RP advertisement. The

candidate RP with the lowest priority will become formal RPs.

In PIM-SM, some switches running PIM-SM are manually set to work as candidateBootstrap switch (BSR). The candidate BSR with the highest priority will be elected asthe formal BSR.

13-1



The BSR is responsible for collecting the candidate RP information on the multicastswitches in group to find out candidate RPs in the multicast domain. It notifies thecandidate RPs to all the PIM switches in the PIM domain in a unified way. Each PIMswitch, according to the similar Hash rules, elects the one with the highest priority as theformal RP from the same candidate RP set. Candidate RPs are configured manually.

The switches running PIM-SM discover each other and maintain the neighbor relationshipby exchanging Hello messages. In the multi-access network, the Hello messages alsocontain the priority information of switches. The DR is elected according to this parameter.

The multicast source or the first hop switch (the DR connecting to the source directly)encapsulates a packet in a Register message, and then sends it to the RP through a unicastswitch. When receiving the Register message, the RP de-encapsulates the messages totake out the packet, and then sends the packet to the receivers of the group along theshared multicast tree.

Each host acting as a receiver joins the multicast group through the IGMP member reportmessage. The last hop switch (or the DP in the multi-access network) sends the receivedJoin message to the RP level by level. After receiving the Join message, the intermediateswitch checks whether it has already had the routes of the group. If it has, the intermediateswitch adds the downstream request switch to the shared multicast tree as a branch. Ifnot, it continues to send the Join message to the RP.

When the RP or the multicast switch connects to a receiver directly, it can switch to theSPT from the shared tree. When the RP receives a Register message sent from a newmulticast source, the RP will return a Join message to the DR directly connecting to themulticast source. Thus, the SPT from the source to the RP is constructed.

After a DR or a switch directly connecting to multicast members receives the first multicastpacket from the multicast group, or the received packets reaches a threshold, it can switchto the SPT from the shared tree. Once the handover occurs, the switch will send a Prunemessage to the upstream neighbor and request to leave the shared tree.

In PIM-SM, there are the following types of messages.

l Hello message: The switch interfaces on which PIM-SM runs send Hello messagesperiodically to the neighbor interfaces in the same segment to establish neighborrelationship. Hello messages are also used for switches running MLD to elect theDR.

l Register message: When receiving a multicast packet sent by a host in the localnetwork, the DR will encapsulate the packet in a Register message and send it to theRP through unicast. The source address in the IP header of the Register message isthe address of the DR, and the destination address is the address of the RP.

l Register-Stop message: The RP unicasts a Register-Stop message to the sender ofthe Register message to inform it stop sending Register messages.

l Join/Prune message: This message is forwarded in the direction to the source orthe RP. A Join message is used to construct a source tree or a shard tree. When areceiver leaves a group, it sends a Prune message to prune the source tree or theshard tree. This message contains the joining information and pruning information

13-2


Chapter 13 IPv6 PIM-SM Configuration

of the multicast route entities. The Join message and the Prune message are in thesame packet. Either message can be null.

l Bootstrap message: A route needs to send Bootstrap messages on all interfacesexcept the interface on which the Bootstrap message is received. This message isgenerated on the BSR and forwarded by all switches.

l Assert message: When there are several switches on a multi-access network and amulticast group packet is received on an egress interface of a switch, it is necessaryto use the Assert message to designate a forwarder.

l Candidate-RP-Advertisement: A candidate RP unicastsCandidate-RP-Advertisement to the BSR periodically to advertise the set of groupaddresses served by the Candidate RP.

13.2 Configuring IPv6 PIM-SMTo configure IPv6 PIM-SM on ZXR10 5900E, perform the following steps.


ZXR10(config-mcast-ipv6)#router pim Enables IPv6 PIM-SM.1

ZXR10(config-mcast-ipv6)#no router pim Disables PIM-SM.

ZXR10(config-mcast-ipv6-pim)#static-rp<ip-address>[priority <priority>]

Configures a static RP.

ZXR10(config-mcast-ipv6-pim)#no static-rp<ip-address

>[priority<priority>]Deletes a static RP.

ZXR10(config-mcast-ipv6-pim)#rp-candidate

<ip-address>[priority <priority>]Configures a candidate BSR.

ZXR10(config-mcast-ipv6-pim)#rp-candidate

<ip-address>[priority <priority>]Configures a candidate RP.

ZXR10(config-mcast-ipv6-pim)#spt-threshold infinity Configures handover of the

SPT.

ZXR10(config-mcast-ipv6-pim)#accept-register<

access-list-name >

Filters the multicast packets

encapsulated in Register

messages.

ZXR10(config-mcast-ipv6-pim)#no accept-register Disables to filter the packets


messages.

ZXR10(config-mcast-ipv6-pim)#accept-rp

<access-list-name>

Filters the candidate RP

addresses advertised in the

Bootstrap messages.

ZXR10(config-mcast-ipv6-pim)#no accept-rp Disables to filter the candidate

RP addresses.

2

13-3




ZXR10(config-mcast-ipv6-pim)#anycast-rp-local <

ipv6-address >

Configures the Anycast-RP

local address.

ZXR10(config-mcast-ipv6-pim)#no anycast-rp-local Clears the Anycast-RP local

address.

ZXR10(config-mcast-ipv6-pim)#anycast-rp-peer <

ipv6-address >

Configures the Anycast-RP

peer address.

ZXR10(config-mcast-ipv6-pim)#no anycast-rp-peer <

ipv6-address >

Clears the Anycast-RP peer

address.

ZXR10(config-mcast-ipv6-pim)#embedded-rp disable Disables embedded RP

function.

ZXR10(config-mcast-ipv6-pim-if-vlan1)#pimsm Enables IPv6 PIM-SM on an

interface.

ZXR10(config-mcast-ipv6-pim-if-vlan1)#no pimsm Disables IPv6 PIM-SM on an

interface.

ZXR10(config-mcast-ipv6-pim-if-vlan1)#dr-priority

<priority>

ZXR10(config-mcast-ipv6-pim-if-vlan1)#no

dr-priority

Configures the DR priority on a

IPv6 PIM-SM interface.

ZXR10(config-mcast-ipv6-pim-if-vlan1)#bsr-border


bsr-border

Sets an interface to the border

of the IPv6 PIM-SM domain.

3

ZXR10(config-mcast-ipv6-pim-if-vlan1)#hello-inter

val <seconds>


hello-interval

Configures the interval to send

Hello messages.



<ip-address> Static RP address, in the X:X::X:X format

<hash-mask-length > Hash mask length, in the range of 0-128

<access-list-name> ACL name, with 1-32 characters



<seconds> The interval to send Hello messages on a IPv6 PIM-SM

switch. It is in the range of 1-65535, in the unit of second.


13-4



Configuring IPv6 PIM-SM Basic InformationTo configure IPv6 PIM-SM on ZXR10 5900E, perform the following steps.


1 ZXR10(config-mcast-ipv6)#router pim Enables IPv6 PIM-SM.

ZXR10(config-mcast-ipv6-pim)#interface

<interface-name>

2

ZXR10(config-mcast-ipv6-pim-if-vlan1)#pimsm

After IPv6 PIM-SM is enabled

on an interface, MLD is enabled

automatically on the interface.

By default, IPv6 PIM-SM is not

enabled on an interface.

3 ZXR10(config-mcast-ipv6-pim)#static-rp<ip-address>[priority <priority>]

Configures a static RP.

4 ZXR10(config-mcast-ipv6-pim)#bsr-candidate<interface

-name>[<hash-mask-length>][<priority>]

Configures a candidate BSR.

5 ZXR10(config-mcast-ipv6-pim)#rp-candidate<ipv6

address>[priority <priority>]Configures a candidate RP.

6 ZXR10(config-mcast-ipv6-pim)#anycast-rp-local <

ipv6-address >

Configures the anycast-rp local

address.

7 ZXR10(config-mcast-ipv6-pim)#anycast-rp-peer <

ipv6-address >

Configures the anycast-rp peer

address.



<ip-address> Static RP address, in the X:X::X:X format

<priority> Priority, in the range of 0-255, with the default value of 192

Note:

By default, no static RP is configured.

Usage descriptions of a static RP: After a static RP is configured, it participates in RP setselection, even the switch does not receive any RP information advertisement of BSR.

The following example shows how to configure a static RP 2001::1 for all multicast groups.

ZXR10(config-pimsm-ipv6)#static-rp 2001::1



< ipv6-address > BSR address, in the X:X::X:X format

13-5




<hash-mask-length> Hash mask length, in the range of 0-128

<priority> Priority, in the range of 0-255, with the default value of 0

If static RP mechanism is not used, it is necessary to configure a candidate BSR on oneor more multicast switches in each multicast domain and elect a BSR.

A BSR sends bootstrap messages periodically to advertise the RP information. Theswitches running PIM-SM update the RP state according to the latest advertisementmessages. The bootstrap messages sent by BSRs are also used to elect a formal BSRamong candidate BSRs.

The default priority of a candidate BSR is 0. The BSR with the highest priority will becomethe formal BSR. If several candidate BSR have the same highest priority, the one with thelargest IP address will become the formal BSR.



< ipv6-address > BSR address, in the X:X::X:X format

<priority> Candidate RP priority, in the range of 0-255, with the default

value of 192

In PIM-SM, a RP is the root of the RPT. It is responsible for sending multicast packets todownstream multicast receiving members along the RPT. There should be only one formalRP in each multicast group.

Usage descriptions of a candidate RP:

1. The default priority of a candidate RP is 192. The RP with the smallest priority valuewill become the RP. If some candidate RPs have the same smallest priority value, thehash values are compared. The candidate RP with the largest hash value will becomethe RP. If the hash values are the same, IP addresses are compared. The candidateRP with the largest IP addresses will become the RP.

2. It is recommended to configure a candidate RP on the loopback interface to reducethe network oscillation due to physical interface up/down.

Configuring IPv6 PIM-SM Global ParametersIn IPv6 PIM-SM, different parameters have different default values. Configuring theseparameters can optimize the network. To configure IPv6 PIM-SM global parameters onZXR10 5900E, perform the following steps.


1 ZXR10(config-mcast-ipv6-pim)#spt-threshold infinity Configures handover of the

SPT.

13-6




2 ZXR10(config-mcast-ipv6-pim-if-vlan1)#dr-priority

<priority>

Configures the DR priority on a

IPv6 PIM-SM interface.

3 ZXR10(config-mcast-ipv6-pim-if-vlan1)#bsr-border Sets an interface to the border

of the IPv6 PIM-SM domain.

4 ZXR10(config-mcast-ipv6-pim-if-vlan1)#hello-inter

val <seconds>

Configures the interval to send

Hello messages.



infinity Infinity, making all sources of designated groups use the RPT

Note:

By default, the threshold to hand the RPT over to the SPT is 0.

Only the last hop DR and RP can hand over to the SPT on their own initiative. By default,the handover begins when the RP receives the first Register message. For the last hopDR, the policy of SPT handover can be configured by using single multicast group as thecontrol granularity. If the handover threshold of a group is set to infinity, handover will notbe performed. By default, as long as there is traffic, handover is performed.



<priority> DR priority on a PIM interface, in the range of 0-4294967295,

with the default value of 1.

A DR must be elected in a shared (or multi-access) segment. The candidate DR withthe highest priority will become the DR. If several candidate DRs have the same highestpriority, the one with the largest IP address will become the DR.

In a shared segment connecting to the multicast source, only the DR can send Registermessages to RP. In a shared segment connecting to receivers, only the DR reply to theMLD Join messages and Leaving messages, and send PIM Join/Pruning messages toupstream devices. The switch priority is contained in the Hello messages exchanged withneighbors, with the default value of 1.

Configuration Example

The following example shows how to configure the DR priority on vlan1.

ZXR10(config)#ipv6 multicast-routing

ZXR10(config-mcast-ipv6)#router pim

13-7



ZXR10(config-mcast-ipv6-pim)#interface vlan1

ZXR10(config-mcast-ipv6-pim-if-vlan1)#dr-priority 20

ZXR10(config-mcast-ipv6-pim-if-vlan1)#exit

By default, an interface is not the border of the PIM domain. When the interface is set tothe border of the PIM domain, no BSR messages can pass the border in any direction.This function divides the network into different areas of BSR messages effectively. OtherPIM messages can pass the domain border.

The following example shows how to configure a PIM domain border on vlan1.



ZXR10(config-mcast-ipv6-pim-if-vlan1)#bsr-border


The intervals of sending Hello messages to PIM-SM neighbors can be set according todemand.

The following example shows how to configure the intervals of sending PIM Hellomessages on vlan1.



ZXR10(config-mcast-ipv6-pim-if-vlan1)#hello-interval 25


Configuring an IPv6 PIM-SM Control PolicyTo configure an IPv6 PIM-SM control policy on ZXR10 5900E, perform the following steps.


1 ZXR10(config-mcast-ipv6-pim)#accept-register <

access-list-name >

Filters the multicast packets


messages.

2 ZXR10(config-mcast-ipv6-pim)#accept-rp

<access-list-name>

Filters the candidate RP

addresses advertised in the

Bootstrap messages.



<access-list-name> Defines a group range in which the source addresses of the

multicast packets encapsulated in Register messages are

filtered.

The source addresses of the multicast packets encapsulated in Register messages will befiltered according to the rules defined in an ACL.


13-8




<access-list-name> Defines a group range in which the candidate RPs advertised

in BSR messages received are filtered.

13.3 IPv6 PIM-SM Maintenance and DiagnosisThe ZXR10 5900E provides the following commands to maintain IPv6 PIM-SM:

Command Function

ZXR10(config)#show ipv6 pim mroute [group<group-address>][source <source-address>]

Displays the IPv6 PIM-SM routing

table.

ZXR10(config)#show ipv6 mroute summary Displays the routing table

information of the IPv6 broadcast

PIM-SM.

ZXR10(config)#show ipv6 pim bsr Displays the information of the

BSR.

ZXR10(config)#show ipv6 pim rp mapping Displays the RP mapping

information advertised by the

BSR.

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

selected by a specific multicast

group.

ZXR10(config)#show ipv6 pim interface [<interface-name>] Displays the interface on which

IPv6 PIM-SM is configured.

ZXR10(config)#show ipv6 pim neighbor [<interface-name>] Displays the neighbor information

of a PIM-SM interface.

ZXR10(config)#show ipv6 pim nexthop Displays the PIM-SM next hop

information.

ZXR10#show ipv6 pim traffic [<interface-name>] Displays the IPv6 PIM-SM traffic

statistics information.

ZXR10#clear ipv6 pim traffic Clears the IPv6 PIM-SM traffic

statistics information.



group <group-address> Multicast group address, in the X:X::X:X format

source <source-address> Source address, in the X:X::X:X format

<interface-name> Interface name

13-9



The following example shows the outputs of the show ipv6 pim mroute command:

ZXR10(config-mcast-ipv6-pim)#show ipv6 pim mroute group ff88::1

IPv6 PIM-SM Multicast Routing Table

Flags: T- SPT-bit set,A- Foward,J- Join SPT,U- Upsend ,

Macro state: Ind- Pim Include Macro,Exd- Pim Exclude Macro,

Jns- Pim Joins Macro,LAst- Pim Lost_assert Macro,

Imo- Pim Immediate_olist Macro,Ino- Pim Inherited_olist Macro,

Lcd- Pim Local_receiver_include Macro

Timers:Uptime/Expires(Upstream State)

(*, ff88::1), 1d0h/00:00:00(JOINED), RP address: 2002::20,

Ind: 1/Jns: 0/LAst: 0/Imo: 1/Lcd: 1

Iif: NULL, RPF nbr: 0.0.0.0

Oif:

vlan2, LocalIn/ImoXG Ind: 1/Jns: 0/LAst: 0/Imo: 1/Lcd: 1

Iif: NULL, RPF nbr: 0.0.0.0

Oif:

vlan2, LocalIn/ImoXG

The outputs of the command show ipv6 pim mroute is as follows:


Ind PIM local join state

RPF nbr RPF neighbor

The following example shows the outputs of the show ipv6 pimmroute summary command:

ZXR10#show ipv6 pim mroute summary

IPv6 PIM-SM Multicast Routing Table Summary

(*, G):6 , (S, G):0, (S, G, rpt):0, Register:0

(*, ff88::1) (JOINED), RP: 2002::20

(*, ff88::2) (JOINED), RP: 2002::20

(*, ff88::3) (JOINED), RP: 2002::20

(*, ff88::4) (JOINED), RP: 2002::20

(*, ff88::5) (JOINED), RP: 2002::20

(*, ff88::6) (JOINED), RP: 2002::20

The following example shows the outputs of the show ipv6 pim bsr command:

ZXR10(config-mcast-ipv6-pim)#show ipv6 pim bsr

No IPv6 PIM-SM Bootstrap information !

This system is a candidate BSR!

candidate BSR address: 2002::20,

priority: 100,

hash mask length: 30

This system is a candidate RP!

candidate RP address: 2001::20,priority:192

13-10



The outputs of the show ipv6 pim bsr command are described as follows:


BSR address BSR IPv6 address

Uptime BSR uptime

BSR Priority BSR priority

Hash mask length BSR mask length

Expires Expiring time of the BSR or of the BSR message

candidate BSR address IPv6 address of the candidate BSR configured locally

Priority Priority of the candidate BSR configured locally

hash mask length Mask length of the candidate BSR configured locally

CRP IP address, interface number, priority and other information

of the RP configured locally

The following example shows the outputs of the show ipv6 pim rp mapping command:

ZXR10(config-mcast-ipv6-pim)#show ipv6 pim rp mapping

ff02::/16

RP : ::

Protocol : L-Local

RPF : ,

Info source: Default

Expires :

ff10::/15

RP : ::

Protocol : NOUSED

RPF : ,


Expires :

ff12::/16

RP : ::

Protocol : L-Local

RPF : ,


Expires :

ff00::/8

RP : 2001::20

Protocol : SM

RPF : Local,2001::20

Info source: BSR From: 2002::20, Priority: 188

Expires : 00:02:18

The outputs of the show ipv6 pim rp mapping command are described as follows:

13-11




Group The address and mask of the broadcast group that selects

the RP.

RP The address of the secondary RP advertised by the broadcast

group.

Protocol Protocol.

RPF RPF type and the interface address.

Info source RP information source.

Expires The time the secondary RP expires.

Group Address and the mask of the broadcast group that selects

the RP.

The following example shows the outputs of the show ipv6 pim rp hash command:

ZXR10(config-mcast-ipv6-pim)#show ipv6 pim rp hash ff88::2

rp address: 2001::20

The outputs of the show ipv6 pim rp hash command are described as follows:


rp address RP address selected by a specific multicast group

The following example shows the outputs of the show ipv6 pim interface command:

ZXR10#show ipv6 pim interface vlan1

Interface State Nbr Hello DR

Count Period Priority

vlan1 Up 1 30 1

Address: fe80::2e0:d0ff:fe21:203

DR : fe80::2e0:d0ff:fe21:205

The outputs of the show ipv6 pim interface command are described as follows:


Address Interface address

Interface Interface name

NbrCount Number of neighbors

State Interface state up/down

HelloPeriod Intervals of sending Hello messages

DR Priority DR priority of this interface

DR The DR of the interface

The following example shows the outputs of the show ipv6 pim neighbor command:

13-12



ZXR10#show ipv6 pim neighbor

Neighbor Address(es) Interface Uptime Expires DR Pri

fe80::2ee:ffff:fe10:2000 vlan2 05:57:01 00:01:39 1

The outputs of the show ipv6 pim neighbor command are described as follows:


Neighbor Address(es) IPv6 address of the neighbor

Interface Interface name

DR Priority DR priority of the neighbor

Uptime Uptime of the neighbor

Expires Expiring time of the neighbor

Address-list Hello option Address list of the neighbor.

The following example shows the outputs of the show ipv6 pim nexthop command:

ZXR10(config-mcast-ipv6-pim)#show ipv6 pim nexthop

IPv6 PIM-SM Nexthop Table

Nexthop state: R- Nexthop to RP,S- Nexthop to Source,

O- Related with Unicast,U- No Unicast Route,

L- Local Route,C- Connect to Dest,

Nexthop:2001::20 (00:03:26)

Type:.R. . . .L.

Metric:0

Preference:0

Nexthop address:::(is Local)

Nexthop port:vlan1

Nexthop:2002::20 (00:03:26)

Type:. . . . .L.

Metric:0

Preference:0

Nexthop address:::(is Local)

Nexthop port:vlan1

The outputs of the show ipv6 pim nexthop command are described as follows:


Next-hop Address IPv6 address of the next hop

Type Type of the next hop route

Metric Route metric of the next hop

Preference Route priority of the next hop

Next-hop port Egress interface of the unicast route.

The outputs of the show ipv6 pim traffic command are described as follows:

13-13



ZXR10#show ipv6 pim traffic

IPv6 PIM-SM packet receive:

Interface Hel Reg Reg-st J/P Bst Ast

C-RP-Ad

loopback1 0 0 0 0 0 0

0

vlan1 641 0 0 0 0 0

0

vlan2 0 0 0 0 0 0

0

IPv6 PIM-SM packet send:


C-RP-Ad

loopback1 661 0 0 0 0 0

0

vlan1 652 0 0 0 0 0

0

vlan2 651 0 0 0 0 0

0

Total traffic in current IPv6 PIM-SM instance:

Summary_pkt Hel Reg Reg-st J/P Bst Ast

C-RP-Ad

RCV_type 641 0 0 0 0 0

0

SEND_type 1964 0 0 0 0 0

0

pkt_rcv_all 1281

pkt_rcv_error 640 pkt_rcv_ok_notpim 0

xg_Prune_rcv 0 sg_Prune_rcv 0

igmp_xglev_rcv 0 igmp_sginlev_rcv 0

pkt_send_all 1964

data_rcv_all 0 wrong_data_rcv 0

data_send_all 0 wrong_data_send 0

The outputs of the show ipv6 pim traffic command are described as follows:


Interface Interface name.

Hel Number of Hello packets.

Reg Number of Registration packets.

Reg-st Number of Deregistration packets.

J/P Number of J/P packets.

Bst Number of BSM packets.

13-14




Ast Number of Assert packets.

C-RP-Ad Number of CRP packets.


Summary Summarize traffic information of all interfaces.

pkt_rcv_all Number of protocol packets received by the IPv6

PIM-SM instance.

pkt_rcv_error Number of incorrect packets received by the IPv6

PIM-SM instance.

pkt_rcv_ok_notpim Number of incorrect packets received by the

non-pim interface of the IPv6 PIM-SM instance.

xg_Prune_rcv Number of xg prune packets received by the IPv6

PIM-SM instance.

sg_Prune_rcv Number of sg prune packets received by the IPv6

PIM-SM instance.

igmp_xglev_rcv Number of igmp xg leave packets received by the

IPv6 PIM-SM instance.

igmp_sginlev_rcv Number of igmp sg include leave packets

received by the IPv6 PIM-SM instance.

pkt_send_all Number of protocol packets sent by the IPv6

PIM-SM instance.

data_rcv_all Number of data packets received by the IPv6

PIM-SM instance.

wrong_data_rcv Number of incorrect data packets received by the

IPv6 PIM-SM instance.

data_send_all Number of data packets that are sent successfully

by the IPv6 PIM-SM instance.

wrong_data_send Number of data packets that failed to be sent by

the IPv6 PIM-SM instance.

The following example shows the outputs of the clear ipv6 pim traffic command:

ZXR10#clear ipv6 pim traffic

ZXR10#show ipv6 pim traffic

IPv6 PIM-SM packet receive:


C-RP-Ad

loopback1 0 0 0 0 0 0

0

13-15



vlan1 0 0 0 0 0 0

0

vlan2 0 0 0 0 0 0

0

IPv6 PIM-SM packet send:


C-RP-Ad

loopback1 0 0 0 0 0 0

0

vlan1 0 0 0 0 0 0

0

vlan2 0 0 0 0 0 0

0

Total traffic in current IPv6 PIM-SM instance:

Summary_pkt Hel Reg Reg-st J/P Bst Ast

C-RP-Ad

RCV_type 0 0 0 0 0 0

0

SEND_type 0 0 0 0 0 0

0

pkt_rcv_all 0

pkt_rcv_error 0 pkt_rcv_ok_notpim 0

xg_Prune_rcv 0 sg_Prune_rcv 0

igmp_xglev_rcv 0 igmp_sginlev_rcv 0

pkt_send_all 0

data_rcv_all 0 wrong_data_rcv 0

data_send_all 0 wrong_data_send 0

13.4 IPv6 PIM-SM Configuration ExampleGeneral DescriptionAs shown in Figure 13-1, an MLD group connects to S2, and a multicast source connectsto S1. It is required to configure BSR neighbors and CRP.

13-16



Figure 13-1 PIM-SM Configuration Example

Method1. Configure related interfaces.2. Enter multicast configuration mode.3. Enter PIM-SM configuration mode.4. Set the loopback5 interface on S2 to CRP and BSR.5. Enable PIM-SM on interfaces.6. Configure a unicast route to the RP on S1. Configure a unicast route to the multicast

source on S2 (In this example, static route or IGP can be used).



S1(config-mcast-ipv6-pim)#router pim



S1(config-mcast-ipv6-pim-if-vlan1)#exit



S1(config-mcast-ipv6-pim-if-vlan2)#dr-priority 20

S1(config)#ipv6 route 100::1/128 199::2

S2 configuration:



S2(config-mcast-ipv6-pim)#rp-candidate loopback5

S2(config-mcast-ipv6-pim)#bsr-candidate loopback5






S2(config-mcast-ipv6-pim-if-vlan2)#dr-priority 20

13-17




S2#configure terminal

S2(config)#ipv6 route 198::/64 199::1

VerificationExecute the show ip pim interface command on S1 to check the interface state, as shownbelow.

S1(config)#show ipv6 pim interface

Interface State Nbr Hello DR

Count Period Priority

vlan9 Up 0 30 1

Address: fe80::2d0:d0ff:fe06:606

DR : fe80::2d0:d0ff:fe06:606

vlan7 Up 0 30 1

Address: fe80::2d0:d0ff:fe06:606

DR : fe80::2d0:d0ff:fe06:606

Execute the show ipv6 pim neighbor command on S1 to check the neighbor state, as shownbelow.

S1(config)#show ipv6 pim neighbor

Neighbor Address(es)

Interface Uptime Expires DR Pri

fe80::211:12ff:fe51:ea11 vlan1 01:05:20 00:01:25 1

fe80::211:12ff:fe51:ea12 vlan2 01:05:20 00:01:30 1

Execute the show ip pim rp mapping command on S1 to check the RP state, as shownbelow.

S1(config)#show ipv6 pim bsr

BSR address: 100::1

Uptime:00:00::40,BSR Priority :0,Hash mask length:30

Expires:00:01:30

No IPv6 PIM-SM candidate RP information !

13-18


Chapter 14IPv6 PIM-SSM ConfigurationTable of ContentsPIM-SSM Overview ..................................................................................................14-1Configuring IPv6 PIM-SSM.......................................................................................14-1IPv6 PIM-SSM Maintenance and Diagnosis .............................................................14-2IPv6 PIM-SSM Configuration Example .....................................................................14-3

14.1 PIM-SSM OverviewProtocol Independent Multicast-Source Specific Multicast (PIM-SSM) has all advantagesof PIM-SM. PIM-SSM does not construct a shared tree. Instead, it only constructs theSPT. When receiving the member relation report messages about a specific source and agroup, PIM-SSM will construct the SPT directly.

PIM-SSM is a subset of PIM-SM. PIM-SSM is suitable for the well known sources. It isboth intra-domain and inter-domain valid. PIM-SM uses MSDP for inter-domain multicastrouting. PIM-SSM does not need to use MSDP. The multicast group address allocatedfor PIM-SSM is FF3X::/32. The switches will not construct a shared tree for this groupaddress.

After a host sends a Join message from a specific source to a group, the last hop switchwill send a (S, G) Join message to the direction of the source to construct a SPT. The lasthop switch will not send a (*, G) Join message to the direction of RP. Once the SPT isconstructed, the first hop switch will forward packets along this tree.

14.2 Configuring IPv6 PIM-SSMTo configure IPv6 PIM-SSM on ZXR10 5900E, perform the following step.

Command Function

ZXR10(config-mcast-ipv6-pim)#ssm range default[group-list< access-list-name >]

Configures address range of IPv6

SSM groups or uses the default

group address range.

The command parameter is described as follows:


< access-list-name > ACL name, with 1-31 characters

When the group-list is not configured, the default group range is FF3X::/32.

14-1



14.3 IPv6 PIM-SSM Maintenance and DiagnosisUsers can view the (S, G) routes of group addresses set by the SSM range. Otheraddresses only generate (*, G) routes.

ZXR10 5900E provides the following command to maintain IPv6 PIM-SSM:

Command Function

ZXR10#show ipv6 pim mroute [group <group-address>][source<source-address>]

Shows IPv6 PIM-SM routing table.



group <group-address> Multicast group address, in the X:X::X:X format

source <source-address> Source address, in the X:X::X:X format

The following example shows the outputs of the show ipv6 pim mroute command:

ZXR10(config-mld-if)#static-group FF38::2 source 2009::8

ZXR10(config-mld-if)#exit

ZXR10(config-mld-ipv6)#exit

ZXR10(config-mcast-ipv6)#router pimsm

ZXR10(config-pimsm-ipv6)#inerface loopback1

ZXR10(config-pimsm-ipv6-if)#pimsm

ZXR10(config-pimsm-ipv6-if)#exit

ZXR10(config-pimsm-ipv6)#show ipv6 pimsm mroute

IPv6 PIM-SM Multicast Routing Table

Flags: T- SPT-bit set,A- Foward,J- Join SPT,U- Upsend ,

Macro state: Ind- Pim Include Macro,Exd- Pim Exclude Macro,

Jns- Pim Joins Macro,LAst- Pim Lost_assert Macro,

Imo- Pim Immediate_olist Macro,Ino- Pim Inherited_olist Macro,

Lcd- Pim Local_receiver_include Macro

Timers:Uptime/Expires(Upstream State)

(2009::8, ff38::2), 00:00:07/00:00:00(JOINED)/00:00:00,

Reg:NO INFO; RP:0::0; RT:NULL;

Ind:1/Exd:0/Jns:0/LAst:0/Imo:1/Ino:1

Iif:NULL; RPF nbr:0.0.0.0;

Oif:

loopback1, LocalInSG/InoSG

14-2


Chapter 14 IPv6 PIM-SSM Configuration

14.4 IPv6 PIM-SSM Configuration ExampleGeneral DescriptionAs shown in Figure 14-1, PIM-SM is enabled on S1, and SSM is configured. Configurethe SSM group range. MLD version is v2. The multicast source sends flows to multicastgroups of multiple specific sources. Only the traffic matching both the source address andthe multicast group address is allowed to pass through.

Figure 14-1 IPv6 PIM-SSM Configuration Example

Method1. In interface mode, configure the interface address for both vlan1 and vlan2.2. Enable the IP multicast function with the ipv6 multicast-routing command.3. Enter the PIM-SM route configuration mode to configure the address range of SSM

groups.4. Enter VLAN 1 and VLAN 2 to enable the PIM-SM protocol.5. Enter MLD route configuration mode and then enter the interfaces to enable MLDv2.6. Send dynamic group Join messages to specific receiving groups.










S1(config-mcast-ipv6-pim)#ssm range default

S1(config-mcast-ipv6-pim)#exit

S1(config-mcast-ipv6)#router mld

S1(config-mcast-ipv6-mld)#interface vlan2

S1(config-mcast-ipv6-mld-if-vlan2)#version 2

VerificationCheck the configuration information on S1, as shown below.

14-3



S1#show running-config multicast6

!

<MULTICAST6>

ipv6 multicast-routing

router pim

ssm range default

interface vlan2

pimsm

$

interface vlan1

pimsm

$

$

router mld

interface vlan2

version 2

$

$

!<MULTICAST6>

Check the result of routes on S1, as shown below.

S1#show ipv6 mroute

(100::2, ff3a::aaaa:1), RP: ::, TYPE: DYNAMIC, FLAGS: NS

Incoming interface: vlan1, flags: NS

Outgoing interface list : vlan2

14-4


Chapter 15IPv6 Static MulticastConfigurationTable of ContentsIPv6 Static Multicast Introduction..............................................................................15-1Configuring IPv6 Static Multicast ..............................................................................15-2Maintaining IPv6 Static Multicast ..............................................................................15-3IPv6 Static Multicast Configuration Example.............................................................15-3

15.1 IPv6 Static Multicast IntroductionStatic multicast routes are applied in the scenario where multicast packets are expectedto be forwarded along the specified path rather than the optimal path in unicast routing.

Static multicast routing provides ingress and egress interfaces for configuring the multicastrouting table, and creates the multicast forwarding table based on the user configuration. Ifstatic and dynamic multicast routes are available at the same time, static multicast routesare selected due to a higher priority. Static multicast routing can be considered as a specialmulticast routing protocol.

The applications of static multicast routing vary with the application scenario:l Changing RPF routes.

In general, the multicast networking structure is the same as the unicast networkingstructure, and the transport path for multicast packets is the same as that for unicastpackets. RPF routes can be changed through the static multicast route configuration,which creates a transport path for multicast packets. This path is different from thetransport path for unicast packets.

l Re-establishing RPF routes.

When unicast routes are blocked, packets (including multicast packets) cannot beforwarded due to no RPF routes. RPF routes are generated through the staticmulticast route configuration, and the multicast routing table is generated for theforwarding of multicast packets.

When the multicast routing table is created by using the multicast routing protocol, the RPFcheck mechanism is used to ensure the loop-free forwarding of multicast packets alongcorrect paths.

Three paths are separately selected from the unicast routing table, MBGP routing table,and static multicast routing table, and the optimal path to themulticast source is determinedbased on one of the following rules:

15-1



l If the longest matching rule is used, the longest matching path is selected from thethree paths.

l If the three paths have the same subnet mask, the highest-priority path is selected.l If the three paths have the same priority, the path is selected in the following order:

à Static multicast path

à MGGP path

à Unicast path

This optimal path is used as an RPF route. After an RPF route is determined,corresponding RPF interfaces and RPF neighbors are also determined.

15.2 Configuring IPv6 Static MulticastTo configure IPv6 static multicast routing, perform the following steps:


1 ZXR10(config-mcast-ipv6)#ipv6

multicast-static-start

Enables the MSTATIC protocol.


multicast-static-limit xg <xg-limit> sg<sg-limit>

Configures the maximum number of static

multicast routes.


multicast-static-route <source-address><grou

p-address>[{[iif <iif-name>],[oif <oif-index>]}]

Configures a static multicast routing entry.


multicast-static-interface index <index>

interface <interface-name>

Configures a static multicast egress

interface set.



<xg-limit> Maximum number of static multicast routes (*,

G), default: 0.

<sg-limit> Maximum number of static multicast routes (S,

G), default: 0.



<group-address> Multicast group address.

<source-address> Multicast source address.

15-2


Chapter 15 IPv6 Static Multicast Configuration


<iif-name> Name of the ingress interface for the multicast

route.

<oif-index> Sequence number of the egress interface for the

multicast route.



<index> Sequence number of the egress interface.

<interface-name> Name of the egress interface.

15.3 Maintaining IPv6 Static MulticastTo maintain IPv6 static multicast routing, run the following commands:

Command Function

ZXR10#show ipv6 multicast-static-interface[index<index>]

Displays valid interfaces in the egress interface

set.

ZXR10#show ipv6 multicast-static-route [group <g

roup-address>|[source <source-address>]]|[source<source-address>]

Displays the contents in the static multicast

routing table.

ZXR10##show ipv6 multicast-static-route summary Displays the statistics on the contents in the static

multicast routing table.

15.4 IPv6 Static Multicast Configuration Examplel Configuration Description

Figure 15-1 shows a sample networking topology. It is required to configure a staticmulticast route (source address: 1::, destination address: ff88::1) to forward multicastpackets.

Figure 15-1 Sample Networking Topology for the IPv6 Static MulticastConfiguration

l Configuration Flow

15-3



1. Configure the IP addresses of gei-0/1/1/1 and gei-0/1/1/2 interfaces.2. Enter the multicast mode.3. Enable static multicast routing.4. Configure the maximum number of static multicast routes (*, G) and (S, G).5. Configure a list of static multicast egress interfaces.6. Configure a static multicast route.

l Configuration Commands

Run the following commands on S1:S1(config)#ipv6 multicast-routing

S1(config-mcast-ipv6)#ipv6 multicast-static-start

S1(config-mcast-ipv6)#ipv6 multicast-static-limit xg 1024 sg 1024

S1(config-mcast-ipv6)#ipv6 multicast-static-interface index 2 interface gei-0/1/1/2

S1(config-mcast-ipv6)#ipv6 multicast-static-route 1::1 ff88::1 iif gei-0/1/1/1 oif 2

S1(config-mcast-ipv6)#end

l Configuration Verification

Run the show ipv6 multicast-static-interface command on S1 to display static multicastinformation about the interfaces:S1(config)#show ipv6 multicast-static-interface

STATIC-MULTICAST OUT PORT INDEX 2:

Outgoing Interface: gei-0/1/1/2

S1(config)#show ipv6 multicast-static-route

The Capability of Static Multicast6 Route

(*, g) 1024, (s, g) 1024

(1::1, ff88::1)

Incoming interface: gei-0/1/1/1 A

Outgoing interface list:

gei-0/1/1/2 N

15-4


Chapter 16ISATAP Tunnel ConfigurationTable of Contents

ISATAP Tunnel Overview .........................................................................................16-1Configuring an ISATAP Tunnel .................................................................................16-2ISATAP Configuration Example ................................................................................16-3

16.1 ISATAP Tunnel OverviewInstruction to ISATAP TunnelWith the wide applications of IPv6 technology, there are more and more IPv6 hostson current IPv4 network. Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)tunnel technology provides a good solution for such application. ISATAP can obtain thedestination of a tunnel automatically by embedding an IPv4 address in the destinationaddress of an IPv6 packet.

When an ISATAP tunnel is used, the destination address of an IPv6 packet and the IPv6address of a tunnel interface should use special ISATAP addresses. The format of anISATAP address is Prefix (64 bit):0:5EFE:ip-address. Thereinto, the 64–bit prefix is theprefix of a legal IPv6 unicast address, and the ip-address is a 32–bit IPv4 source address(in the a.b.c.d format or abcd:efgh format). Through this embedded IPv4 address, atunnel can be established automatically to transmit IPv6 packets. The ISATAP tunnel ismainly used to connect two IPv6 forwarding devices and connect an IPv6 host to an IPv6forwarding device on an IPv4 network.

ISATAP Tunnel PrincipleISATAP encapsulation principle and decapsulation principle are described below.

l Encapsulation principle: When an IPv6 is sent, the egress is an tunnel interface.The tunnel type is judged according to packet call-back on the interface. If it is anISATAP tunnel, IPv4 header encapsulation is performed. An ISATAP tunnel follows theencapsulation format of a 6in4 tunnel. The outer IPv4 destination address is the IPv4address embedded in the destination address of the IPv6 packet, and the outer IPv4source address is the source address of the ISATAP tunnel. After the encapsulation,the packet is handled according to the common IPv4 packet sending flow.

l Decapsulation principle: The decapsulation flow of an ISATAP tunnel is the same asthat of a 6in4 tunnel. When an IPv4 packet is received and the protocol number inthe IPv4 header is 41, the protocol number processing functions registered for IPv4are called and the 6in4 decapsulation function is used. The device searches for the

16-1



matched tunnel entity according to the source address and destination address ofthe packet. If the matched tunnel entity is found, the IPv4 header encapsulated isremoved, and the left IPv6 packet is handled according to the IPv6 packet receivingflow.

ISATAP tunnel principle is shown in Figure 16-1.

Figure 16-1 ISATAP Tunnel Principle

16.2 Configuring an ISATAP TunnelTo configure an ISATAP tunnel on ZXR10 5900E, perform the following steps:


1 ZXR10(config)#interface v6_tunnel1<tunnel_no> Creates an IPv6 tunnel

interface. Use the no format

of this command to delete a

tunnel interface.

2 ZXR10(config-if)#ipv6 enable Enables IPv6.

3 ZXR10(config-if)#ipv6 address <addrprefix / prefix-len>

eui-64

Configures an eui-64 address

on an interface for an ISATAP

tunnel.

4 ZXR10(config)#ipv6-tunnel-config Enters IPv6 tunnel

configuration mode.

5 ZXR10(config)#interface v6_tunnel1<tunnel_no> Enters IPv6 tunnel interface

configuration mode.


mode ipv6ip isatap

Sets the tunnel mode to isatap.

Use the no format of this

command to delete the current

tunnel mode.

16-2


Chapter 16 ISATAP Tunnel Configuration



source ipv4 <src-addr>

Configures the source address

of an tunnel. Use the no format

of this command to delete the

source address of the tunnel.

Parameter descriptions:


<tunnel_no> Tunnel number, indicating the number of tunnel interfaces

that can be created, in the range of 1-512

<src-addr> Source address on the egress of the tunnel

<addrprefix /prefix-len> IPv6 address prefix and prefix length

16.3 ISATAP Configuration ExampleGeneral DescriptionAs shown in Figure 16-2, assume that S1 and S2 are dual-stack switches, PC1 and PC2are IPv6 hosts. It is required to configure an ISATAP tunnel.

Figure 16-2 ISATAP Configuration Example

MethodTo configure an ISATAP tunnel, it is necessary to enable IPv6 and bind the IPv4 addressof the switch at the source end of the tunnel. It is unnecessary to configure the destinationaddress. The configuration steps are described below:

1. Create an ISATAP tunnel. Configure an IPv6 address and enable IPv6. The IPv6address on the ISATAP interface uses eui mode.

2. Enter tunnel configuration mode from global configuration mode, and then enter theISATAP tunnel interface to be configured.

3. Configure the tunnel mode and the source address.

16-3



4. Configure static routes or BGP4+ to advertise the tunnel route.



S1(config)#ip add 1.1.1.1 255.255.


S1(config-if-v6_tunnel2)#ipv6 add 82::/64 eui





S1(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip isatap




S2 configuration:


S2(config)#ip add 1.1.1.2 255.255.255.0


S2(config-if-v6_tunnel2)#ipv6 add 81::/64 eui





S2(config-ipv6-tunnel-if-v6_tunnel2)#tunnel mode ipv6ip isatap




VerificationCheck the ISATAP configuration on S1, as shown below:


!<INTERFACE>


interface trap-enable

ipv6 enable

ipv6 address 82::/64 eui-64

!

!</INTERFACE>

!<V6_TUNNEL>

ipv6-tunnel-config


16-4


Chapter 16 ISATAP Tunnel Configuration

tunnel mode ipv6ip isatap


!</V6_TUNNEL>

Execute the show ipv6 interface brief v6_tunnel2 command on S1 to view the tunnelinterface information, as shown below:

S1(config)#show ipv6 interface brief v6_tunnel2

v6_tunnel2 [up/up]

fe80::5efe:101:101

82::5efe:101:101/64 [EUI]

16-5




16-6


Chapter 17IPv6 Basic ConfigurationThis command is used to query the mtu value, including the IP address, the path mtu valuelearned by this device, the time when the path mtu becomes effective, and the remainingtime.

To query the learned PMTU on the ZXR10 5900E, perform the following step:

Command Function

ZXR10#show ipv6 pmtu Queries the PMTU.

ExampleThe following is a sample output from the ZXR10#show ipv6 pmtu command:

ZXR10#show ipv6 pmtu

MTU Since Timeout Dest Vrfname(Vpnid)

1300 19s 9m41s 3ffe:320e:1:211::2 zte

1400 27s 9m33s 3ffe:3000:1:211::2 zte

17-1




17-2


Chapter 18TCP6 ConfigurationTable of Contents

TCP6 Overview ........................................................................................................18-1Configuring the TCP6...............................................................................................18-1TCP6 Maintenance and Diagnosis ...........................................................................18-3

18.1 TCP6 OverviewTCP6 is a connection-oriented full duplex data transmission control protocol. It providesthe end-to-end transmission service. This protocol is used when the transmission qualityand transmission result are highlighted.

The TCP6 protocol uses a mechanism that is similar to virtual connection. Before datatransmission, ensure that both ends are ready to send or receive data. The acknowledgeand retransmission mode guarantees that data can be transmitted safely. Before oneend sends packets, the other end must acknowledge the packet sent before. Using thismethod, packets can be transmitted reliably.

The window mechanism can greatly improve the network throughput. Congestionmechanism and retransmission mechanism can solve the packet delay and retransmissionfaults. The state machine and timers are key to TCP6 data transmission.

18.2 Configuring the TCP6To configure the TCP6 on the ZXR10 5900E, perform the following steps:


1 ZXR10(config)#ipv6 tcp synwait-time <seconds> Sets the waiting time for

creating a TCP6 connection.

The time is effective is effective

for the TCP6 connections

created later. Range: 30-80

seconds. Use the no command

to restore the time to the

default 75 seconds.

18-1




2 ZXR10(config)#ipv6 tcp window-size <bytes> Sets the size of the TCP6

listening window. It is not

effective for the created

TCP6 connections. Range:

100-65535 bytes. Use the no

command to restore the value

to the default 32768 bytes.

3 ZXR10(config)#ipv6 tcp finwait-time <seconds> Sets the waiting time for

disconnecting a TCP6

connection. Range: 300-675

seconds. Use the no command

to restore the value to the

default 675 seconds.

4 ZXR10(config)#ipv6 tcp queuemax <packets> Maximum queue length.

Range: 5-50 packets. Use the

no command to restore the

value to the default 5 packets.

5 ZXR10#clear tcp6 connect {<local-ip-address>|vrf<vrf-name><local-ip-address>}<local-port><remote-ip-addre

ss><remote-port>

Clears a TCP6 connection.

6 ZXR10#clear tcp6 statistics Clears the TCP6 statistics

information.

7 ZXR10#clear tcp6 tcb <tcb-index> Clears the TCP6 control block

information.

The range of <tcb-index> is

1-4294967295



vrf <vrf-name> Name of the VRF to which the IP address

belongs. Range: 1-32 characters.

<local-host-address> Local IP address.

<local-port> Local port number. Range: 1-65535.

<remote-ip-address> Remote IP address.

<remote-port> Remote port number. Range: 1-65535.

18-2


Chapter 18 TCP6 Configuration

18.3 TCP6 Maintenance and DiagnosisTo view the operation status of the TCP6 on the ZXR10 5900E, run the followingcommands:

Command Function

ZXR10#show tcp6 brief Displays the brief information of all

TCP6 connections.

ZXR10#show tcp6 config Displays the TCP6 configuration

parameters.

ZXR10#show tcp6 statistics Displays the TCP6 statistics.

ZXR10#show tcp6 tcb <tcb-index> Displays the parameters of a

specific TCP connection.

The following is a sample output from the show tcp6 brief command:

ZXR10#show tcp brief

TCB Local Address Foreign Address State

11 2001::1:23 2001::10:3183 ESTAB

10 2001::1:23 2001::10:3182 ESTAB

7 2001::1:23 2001::6:1380 ESTAB

Parameter descriptions are as follows:


2001::1.23 2001::10.2382 ESTAB The index of the current control block is 10.

l Local Address: Local address and the port.

l Foreign Address: Remote address and the

port.

l State: State of the TCP connection.

The following is a sample output from the show tcp6 config command:

ZXR10#show tcp6 config

IPv6 TCP SYNWAIT: 75

IPv6 TCP FINWAIT: 675

IPv6 TCP QUEUEMAX: 5

IPv6 TCP WINDOWSIZE: 65535



TCP SYNWAIT: 75 TCP6 connection SYN packet timeout time. Unit:

second.

TCP FINWAIT: 675 TCP6 connection FIN packet timeout time. Unit:

second.

18-3




IPv6 TCP QUEUEMAX: 5 Maximum TCP6 connection queue length. Unit:

packet.

TCP WINDOWSIZE: 65535 Size of the TCP6 connection window that

receives data. Unit: byte.

The following is a sample output from the show tcp6 statistics command:

ZXR10#show tcp6 statistics

Rcvd:0 Total

0 checksum error, 0 bad offset, 0 too short

0 packets (0 bytes) in sequence

0 dup packets (0 bytes)

0 partially dup packets (0 bytes)

0 out-of-order packets (0 bytes)

0 packets (0 bytes) with data after window

0 packets after close

0 window probe packets, 0 window update packets

0 dup ack packets, 0 ack packets with unsend data

0 ack packets (0 bytes)

Sent: 0 Total

0 control packets (including 0 retransmitted)

0 data packets (0 bytes)

0 data packets (0 bytes) retransmitted

0 ack only packets (0 delayed)

0 window probe packets, 0 window update packets

0 Connections initiated, 0 connections accepted, 0 connections established

0 Connections closed (including 0 dropped, 0 embryonic dropped)

0 Total rxmt timeout, 0 connections dropped in rxmt timeout

0 Keepalive timeout, 0 keepalive probe, 0 connections dropped in keepalive



0 Total

0 checksum error, 0 bad offset,

0 too short

0 packets (0 bytes) in sequence

0 dup packets (0 bytes)

0 partially dup packets (0 bytes)

0 out-of-order packets (0 bytes)

0 packets (0 bytes) with data after window

0 packets after close

0 window probe packets,

0 window update packets

Number of all received packets, and the number

of packets of each type, including the incorrect

packet.

18-4


Chapter 18 TCP6 Configuration


0 dup ack packets,

0 ack packets with unsend data

0 ack packets (0 bytes)

The following is a sample output from the show tcp6 tcb <tcb-index> command:

ZXR10#show tcp6 tcb 3

Connection state is ESTAB

Local host: 2345:6:7:8:ffff:2:1:a, Local port: 23

Foreign host: 2345:6:7:8:fff:2:1:b, Foreign port: 39647

iss: 435911597 snduna: 435911882 sndnxt: 435911882 sndwnd: 3844

irs: 3391817218 rcvnxt: 3391817259 rcvwnd: 8192

SRTT: 8 ms, RTTO: 4 ms, RTV: 0 ms

minRTT: 2 ms, maxRTT: 0 ms, ACK hold: 200 ms



show tcp6 tcb 2 Displays the parameters of the connection that

corresponds to control block 2. For parameter

descriptions, refer to the show tcp command.

18-5




18-6


Chapter 19UDP6 ConfigurationThe UDP6 is a transmission layer protocol, and its transmission mechanism is not reliable.It forwards the data received from programs but it cannot guarantee that the data can reachthe destination. In addition, whether to retransmit data and correct the data is determinedby the superior applications.

The UDP6 uses the source port (source IP address) and the destination port (destination IPaddress) to establish a connection between two programs. It is a connectionless datagramtransmission mechanism. When you use the UDP protocol to transmit data, there is noreply. The sender does not guarantee that the data is sent to the destination, and thereceiver only arranges the datagram according to the sequence field. If a datagram failsto reach the destination, all data need to be retransmitted.

19-1




19-2


Chapter 20DHCPv6 ConfigurationTable of Contents

DHCPv6 Overview ...................................................................................................20-1Configuring DHCPv6 ................................................................................................20-3Maintaining DHCPv6 ................................................................................................20-9DHCPv6 Configuration Examples...........................................................................20-10

20.1 DHCPv6 OverviewIntroduction to DHCPv6DHCPv6 is an automatic address allocation protocol defined by IETF on IPv6 networks.Through DHCPv6, a network node can apply for IPv6 addresses and some otherconfiguration parameters from a DHCPv6 server. The network node also can obtain IPv6addresses through other methods and just obtain other network parameters from theDHCPv6 server.

On an IPv6 network, a DHCP client uses a reserved multicast address that is valid on alink to locate the DHCPv6 server. Therefore, it is required that the client and the servershould be on the same link. However, in some applications, considering management,economy and extension, it is required that a client can communicate with a server that isnot on the same link with the client. This function is accomplished by a DHCPv6 relay. ADHCPv6 relay can relay access requests from other clients or relays.

Figure 20-1 shows the relation among DHCPv6 clients, relays and a server.

Figure 20-1 Relation Among DHCPv6 Client, Relay and Server

20-1



DHCPv6 PrincipleEach DHCPv6 client or server has a unique identifier, that is, a DHCP Unique Identifier(DUID). There are several modes to generate DUIDs. The lengths of DUIDs are different.Not eachmessage needs to carry a DUID, so a DUID is contained in the option information.

Identity Association (IA) is an abstract concept used by DHCPv6 servers and clients toidentify, group and management multiple addresses. A network interface needs at lestone IA to manage the IPv6 address information obtained on this interface. An IA mustbe associated with a unique network interface. Different IAs are identified by IAIDs. TheIPv6 address information allocated by DHCPv6 is contained in IAs. An IA can carry theinformation of several addresses.

DHCPv6 uses UDP to transport the protocol packets. The detection port on clients isPort 546, and the detection port on servers and relays is Port 547. Clients always usemulticast packets to start interactions. DHCPv6 defines two multicast addresses. One isthe multicast address (FF05::1:3) of all local DHCP servers, and the other is the multicastaddress (FF02::1:2) of all servers and relay agents.

There are the following types of standard DHCPv6 messages.

l Solicit message (1): A client uses Solicit messages to locate the position of a server.l Advertise message (2): A server sends an Advertise message to reply a Solicit. An

Advertise message contains the allocated address and option information.l Request message (3): A client sends a Request message to a specified server to

request an address and configuration information.l Confirm message (4): A client sends Confirm messages to any reachable server to

check whether the current IPv6 address it obtained is suitable for the connected links.l Renew message (5): A client uses Renew messages to extend the address lease

term and update other configuration information.l Rebind message (6): If the renew message is not replied, a client will use a Rebind

message to extend the address lease term and update other configuration information.l Reply message (7): A server uses Reply message to respond Request, Renew,

Rebind, Release, Decline and Information-request messages. A Reply message cancarry an address and configuration information. In an exception, a Reply messagealso can carry the status code information of an error.

l Release message (8): When a client sends a Release message to a server thatallocates an address for this client, the client does not use the address (or addresses)any longer.

l Decline message (9): When a client sends a Decline message to a server, the address(or addresses) has (have) been used on a link (or links).

l Reconfigure message (10): A server can send a Reconfigure message to a client tohint the configuration information that the client can update.

l Information-request message (11): A client sends an Information-request message toa sever to request configuration information without requesting an IP address.

l Relay-forward message (12): A relay agent sends a Relay-forward message to aserver to replay information.

20-2


Chapter 20 DHCPv6 Configuration

l Relay-replay message (13): A server sends a Relay-replay message carrying theinformation that will be sent to a client to a rely agent.

Figure 20-2 shows the interaction procedure of DHCPv6 messages in a standard networkenvironment.

Figure 20-2 DHCPv6 Protocol Message Interaction

20.2 Configuring DHCPv6Configuring the DHCPv6 ServerTo configure the DHCPv6 server on the ZXR10 5900E, perform the following steps:


1 ZXR10(config)#dhcp ipv6 Enters DHCPv6 configuration

mode.

20-3




ZXR10(config-dhcpv6)#enable Enables the embedded

DHCPv6 function.

2

ZXR10(config-dhcpv6)#disable Disables the DHCPv6 process.

ZXR10(config-dhcpv6)#interface <interface-name> Enters DHCPv6 interface

configuration mode.

ZXR10(config-dhcpv6)#server max-user <1-48000> Configures the maximum

number of users on the

DHCPv6 server.

ZXR10(config-dhcpv6)#server single-user-quota {[address <max-address-number>],[prefix <max-prefix-number>]}

Configures the maximum

number of addresses that can

be assigned to a DHCP client

and the maximum number of

associated address prefixes.

ZXR10(config-dhcpv6)#server rapid-redial Enables the sending of a

notification to the DHCP server

after a DHCPv6 client is

re-connected to the server and

has an address assigned.

3

ZXR10(config-dhcpv6-if)#mode {server | relay} Enables DHCPv6 working

mode of an interface.

ZXR10(config)#ipv6 addr-pool <pool-name> Enters IPv6 address pool

configuration mode.

ZXR10(config-ipv6-addr-pool)#addr-range

<start-ipv6><end-ipv6>[vrf-instance <vrf-name>]Configures the range of the

IPv6 address pool.

ZXR10(config-ipv6-addr-pool)#exclude-range

<start-ipv6><end-ipv6>[vrf-instance <vrf-name>]Configures IPv6 reserved

addresses.

ZXR10(config-ipv6-addr-pool)#conflict-time <timeout> Configures the release time of

conflict addresses in the IPv6

address pool, the default value

is 30 minutes.

ZXR10(config-ipv6-addr-pool)#lock This locks the IPv6 address

pool. By default, the address

pool is not locked.

4

ZXR10(config-ipv6-addr-pool)#threshold <percent> Configures the alarm threshold

of the IPv6 address pool, the

default threshold is 100%.

20-4




ZXR10(config)#ipv6 prefix-pool <pool-name> Enters IPv6 prefix-pool

configuration mode.

ZXR10(config-ipv6-addr-pool)#lock This locks the IPv6 prefix-pool.

By default, the IPv6 prefix-pool

is not locked.

ZXR10(config-ipv6-addr-pool)#prefix-delegation <ipv6

prefix-delegation><prefix-length>[vrf-instance <vrf-name>]Configures an IPv6

prefix-delegation.

ZXR10(config-ipv6-addr-pool)#threshold <percent> Configures the alarm threshold

of the IPv6 prefix-pool. The

default threshold is 100%.

5

ZXR10(config-ipv6-prefix-pool)#exclude-prefix

<ipv6-prefix-delegation><prefix-length>[ vrf-instance<vrf-name>]

Configures an IPv6

exclude-prefix.

ZXR10(config-dhcpv6)#pool <pool-name> Enters DHCPv6 address

pool configuration mode form

DHCPv6 configuration mode.

ZXR10(config-dhcpv6-pool)#address-pool <pool-name> Binds a specified IPv6

address-pool to a DHCPv6

pool.

ZXR10(config-dhcpv6-pool)#address-lifetime

{<valid-lifetime>| infinite}{<preferred-lifetime>| infinite}

Specifies the life time of the

address-pool.

ZXR10(config-dhcpv6-pool)#prefix-pool <pool-name> Binds the specified prefix-pool

to the dhcpv6 pool.

ZXR10(config-dhcpv6-pool)#prefix-lifetime

{<valid-lifetime>| infinite}{<preferred-lifetime>| infinite}

Specifies the lifetime for the

prefix-pool.

ZXR10(config-dhcpv6-pool)#binding <c

lient-duid>{address <ipv6-address>| prefix<ipv6-prefix-delegation>}[vrf-instance <vrf-name>]

Configures a static binding

between a client-DUID, an

assigned IPv6 address, and an

assigned prefix.

ZXR10(config-dhcpv6-pool)#option <code>[description<WORD>]{fqdn <WORD>| ascii <WORD>| hex <WORD>|ipv6-address <IPv6-address>[<IPv6-address>|[<IPv6-address>|[<IPv6-address>|[<IPv6-address>|[<IPv6-address>|[<IPv6

-address>|[<IPv6-address>]]}

Configures DHCPv6 options.

ZXR10(config-dhcpv6-pool)#dns-server

<server-number><server-ipv6>

Configures the address of an

IPv6 DNS server.

ZXR10(config-dhcpv6-pool)#domain-name

<server-number><domain-name>

Configures the domain name

of an IPv6 DNS server.

6

20-5




ZXR10(config-dhcpv6-pool)#preference

<preference-value>

Configures the server

preference. The range of

the preference is 1-255.

ZXR10(config-dhcpv6-pool)#aftr address

<ipv6-address>[option-code-value <option_code>]Configures the aftr address.

Range: 1-65535

ZXR10(config-dhcpv6-pool)#aftr fqdn <Tunnel endpoint

name>[option-code-value < option_code >]Configures the aftr domain

name. Range: 1-65535.

ZXR10(config-dhcpv6-pool)#server-unicast-address

<ipv6-address>

Configures the unicast address

of the server.

ZXR10(config-dhcpv6)#policy <policy-name><priority> Enters DHCPv6 policy

configuration mode from

DHCPv6 configuration mode

and configures the priority of

the policy. The range of the

priority is 1-5.

ZXR10(config-dhcpv6-policy)#dhcpv6-pool

<pool-name>

This binds a DHCPv6 policy to

a DHCPv6 address pool.

7

ZXR10(config-dhcpv6-policy)#link-addrss

<ipv6-address>

Configures a DHCPv6 policy

link-address.


configuration mode.

ZXR10(config-dhcpv6-if)#server policy <policy-name> Configures a DHCPv6 server

policy on the interface.

ZXR10(config-dhcpv6-if)#enable server-unicast Enables unicast on a DHCPv6

interface.

8

ZXR10(config-dhcpv6-if)#dscp <0-63> Configures the IPv6 Traffic

Class option carried in the

message replied from the

DHCP server to DHCP relay.



<start-ipv6> The start IP address of the IPv6 address pool.

<end-ipv6> The end IP address of the IPv6 address pool.

vrf-instance <vrf-name> IPv6 address pool in the VRF instance.

<timeout> The time before releasing conflicted addresses for the IPv6

address pool. Range: 1-18000 minutes, default: 30 minutes.

20-6




<threshold> Alarm threshold of the IPv6 address pool. Range: 50-100,

default: 100.



<valid-lifetime> The valid life time of the address pool, in the unit of second,

in the range of 60-4294967295

<preferred-lifetime> The preferred life time of the address pool, in the unit of

second, in the range of 60-4294967295

<server-number> DNS server number, value 1 or 2

<Tunnel endpoint name> Domain name. Range: 1–32 characters.

Configuring a DHCPv6 RelayTo configure a DHCPv6 relay on the ZXR10 5900E, perform the following steps:


1 ZXR10(config)#dhcp ipv6 Enters DHCPv6 configuration

mode.

ZXR10(config-dhcpv6)#enable Enables the embedded

DHCPv6 function.

2

ZXR10(config-dhcpv6)#disable Disables the embedded

DHCPv6 function.

ZXR10(config-dhcpv6)#relay server group <number> Enters DHCPv6 relay server

group configuration mode from


ZXR10(config-dhcpv6)#relay max-user <1-48000> Configures the maximum

number of users on the DHCP

relay.

ZXR10(config-dhcpv6r-server-group)#algorithm

{normal | first | round-robin}

Configures the DHCPv6 relay

server to use a policy. The

default forwarding mode is

normal.

ZXR10(config-dhcpv6-server-group)#server <server-no

><server-ipv6>[interface <interface-name>][master][dscp<0-63>]


server to trust information.

ZXR10(config-dhcpv6r-server-group)#deadtime

<time>

Configures the unavailable

duration after the DHCPv6

relay server fails sending.

3

20-7




ZXR10(config-dhcpv6r-server-group)#description

<descript-string>

Configures the description of a

DHCP relay server.

ZXR10(config-dhcpv6r-server-group)#max-retry

<limit-value>

Configures the number of retry

attempts that the DHCPv6

relay server group applies

for address from an external

DHCPv6 server. The default

number is 10.

ZXR10(config-dhcpv6)#relay policy <policy-name> Enters DHCPv6 relay policy

configuration mode from


4

ZXR10(config-dhcpv6r-policy-group)#default

server-group <number>


server group bound to the

DHCPv6 relay policy group by

default.

ZXR10(config-dhcpv6)#relay intfid-format {china-tel |

dsl-forum | user-configuration}

Configures the interface-ID

format of the DHCPv6 relay.

5

ZXR10(config-dhcpv6)#relay remote-id <num><name> Configures the global

remote-ID of a relay. It is not

allowed to run this command.

By default, the value is not

configured.


configuration mode.

ZXR10(config-dhcpv6-if)#relay agent <ipv6-address> Configures IP address of an

DHCPv6 agent on an interface.

ZXR10(config-dhcpv6-if)#relay interface-id <word> Configures an interface-ID

of a DHCPv6 relay on an

interface. The ID is valid

when the interface-ID format is

user-configuration.

The interface-ID is a string with

1-16 characters. By default, the

primary Option82 is kept, that

is, transparent transmission.

6

ZXR10(config-dhcpv6-if)#relay policy <policy-name> Configures a DHCPv6 relay

policy of an interface.


20-8




{normal | first | round-robin} Normal mode is to forward to all servers. First mode is

master/slave mode. Round-robin is load sharing mode. The

default mode is normal.

<server-no> Server number, range: 1–5.

[master] Master server



china-tel | dsl-forum |

user-configuration

china-tel: China Telecommunication modedsl-forum: DSL forum mode

user-configuration: user configuration modeBy default, L3 interface index is used directly.

<num> Enterprise number, range: 0–4294967295.

<name> Remote-ID string, range: 1–32 characters.

20.3 Maintaining DHCPv6To maintain DHCPv6, run the following commands:

Command Function

ZXR10#show ipv6 dhcp server user [interface<interface-name>]|[summary]

Shows the client information on a DHCPv6

server.

ZXR10#show ipv6 dhcp relay user [interface<interface-name>]|[summary]

Shows the client information on a DHCPv6

relay.

ZXR10#show running-config dhcpv6 Displays the DHCPv6 information



summary Displays the number of statistics instead of the

detailed contents.

The following is a sample output from the show ipv6 dhcp server user command:

ZXR10#show ipv6 dhcp server user

Client DUID: 0001000113CB5B3A002127A242AA

IA NA: IA ID 2720473344, T1 500, T2 800

Address: 100::2

preferred lifetime 1000, valid lifetime 1000

expires at 16:28:51 07/16/2010 (918 seconds)

20-9





DUID Unique identifier of a client.

IA NA IA type. IA NA means a temporary address. IA PD means

allocated by a prefix.

IA ID IA identifier.

T1 Recommended Renew interval.

T2 Recommended Rebind interval.

20.4 DHCPv6 Configuration Examples

20.4.1 DHCPv6 Server Configuration Instance

Configuration DescriptionAs shown in Figure 20-3, ZXR10 acts as both DHCP server and the default gateway. ThePC obtains an IP address dynamically through DHCP.

Figure 20-3 DHCPv6 Server Configuration Instance

The configuration requirements of ZXR10 are described below.

l In global configuration mode, configure an IPv6 address, an IPv6 pool, a DHCPv6pool and a DHCPv6 policy. Enable DHCPv6 function.

l In interface configuration mode, configure an IP address and DHCP server mode.Bind the DHCPv6 policy.

Configuration Thought1. Enable IPv6 on the interface and configure an IPv6 address.2. Configure an IPv6 address pool and configure related parameters such as the range

of the address pool. The range of the addresses in the pool should be in the samenetwork segment.

3. Enable DHCPv6 globally.4. Configure DHCPv6 pool. The DHCPv6 pool needs to bind to an IP pool. Configures

DNS, lease time and other parameters.5. Configure DHCPv6 policy. The DHCPv6 policy is a policy option. Many priorities are

supported by a name for policy management.

20-10



6. Configure a DHCPv6 server. Configure server mode in DHCPv6 interfaceconfiguration mode. Bind the policy.

Configuration CommandsConfiguration on ZXR10:

ZXR10(config)#switchvlan-configuration

ZXR10(config-swvlan)#interface gei-0/1/1/1

ZXR10(config-swvlan-if-gei-0/1/1/1)#switchport access vlan 10

ZXR10(config-swvlan-if-gei-0/1/1/1)#exit

ZXR10(config-swvlan)#exit

ZXR10(config)#interface vlan10

ZXR10(config-if)#ipv6 enable

ZXR10(config-if)#ipv6 add 86::1:1/96

ZXR10(config-if)#exit

/*Configure an IPv6 address pool*/

ZXR10(config)#ipv6 addr-pool zte

ZXR10(config-ipv6-addr-pool)#addr-range 86::1:2 86::1:10

ZXR10(config-ipv6-addr-pool)#exit

/*Enable DHCPv6*/

ZXR10(config)#dhcp ipv6

ZXR10(config-dhcpv6)#enable

/*Bind the IPv6 address pool to the DHCPv6 pool*/

ZXR10(config-dhcpv6)#pool zte

ZXR10(config-dhcpv6-pool)#address-lifetime 1000 1000

ZXR10(config-dhcpv6-pool)#exit

/*Bind the DHCPv6 pool to the DHCPv6 policy*/

ZXR10(config-dhcpv6)#policy zte 1

ZXR10(config-dhcpv6-policy)#dhcpv6-pool zte

ZXR10(config-dhcpv6-policy)#exit

/*Configure server mode in interface configuration mode and bind the policy*/

ZXR10(config-dhcpv6)#inter vlan10

ZXR10(config-dhcpv6-if)#mode server

ZXR10(config-dhcpv6-if)#server policy zte

ZXR10(config-dhcpv6-if)#exit

Configuration VerificationCheck the configuration of the IPv6 address pool on ZXR10, as shown below.

ZXR10#show ipv6 addr-pool zte

20-11



PoolName Lock Begin End Vrf Used Free

zte no 86::1:2 86::1:10 0 15

RangeTotal:1

Check the DHCPv6 configuration on ZXR10, as shown below.

ZXR10#show running-config dhcpv6

! <DHCPV6>

dhcp ipv6

enable

policy zte 1

dhcpv6-pool zte

$

pool zte

address-lifetime 1000 1000

$

interface vlan10

mode server

server policy zte

$

! </DHCPV6>

After the PC user obtains an address through DHCPv6, check the user information onZXR10, as shown below.

ZXR10#show ipv6 dhcp server user

Client DUID: 000100014CFBF3DB001094000001

IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:2




IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:3




IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:4



20.4.2 DHCPv6 Relay Configuration Instance

Configuration DescriptionWhen a DHCP client and a server do not belong to the same network, it is necessary touse a router connected directly to the user to act as a DHCPv6 relay.

20-12



As shown in Figure 20-4, enable DHCPv6 relay function on S1. S2 provides DHCPv6server function. This method is usually used when there are many hosts needing DHCPv6service.

Figure 20-4 DHCPv6 Relay Configuration Instance

The configuration requirements are described below.

l Configure an IPv6 address, a DHCPv6 server address and DHCPv6 relay mode onthe interface of S1.

l Configure an IPv6 address and DHCPv6 server mode on the interface of S2. Bind aDHCPv6 policy on the interface of S2.

l In global configuration mode on S2, enable DHCPv6, configure an IPv6 address pool,a DHCPv6 pool and a DHCPv6 policy, and configure a routes pointing to interfacenetwork segment of S1.

Configuration Thought1. Configure an IPv6 address on the interface of the relay and enable DHCPv6.2. Configure a relay server group on the relay. Bind the group in the relay policy.3. Configure relay agent mode on the interface connected to the PC on the relay.4. The configuration on the server is similar to that on the server in the "DHCPv6 Server

Configuration Instance". It is necessary to specify the IPv6 address of the relayinterface in the DHCPv6 policy.

5. Configure a static route to the network segment of the relay interface on the server.

Configuration CommandsConfiguration on S1:

/*Configure an interface*/

S1(config)#switchvlan-configuration

S1(config-swvlan)#interface gei-0/1/1/1

S1(config-swvlan-if-gei-0/1/1/1)#switchport access vlan 10

S1(config-swvlan-if-gei-0/1/1/1)#exit

S1(config-swvlan)#exit







S1(config-if)#ipv6 address 86::1:1/96

S1(config-if)#exit

20-13





S1(config-if)#ipv6 add 87::1:1/96

S1(config-if)#exit

/*Enable DHCPv6 function*/

S1(config)#dhcp ipv6

S1(config-dhcpv6)#enable

/*Specify a server*/

S1(config-dhcpv6)#relay server group 1

S1(config-dhcpr-server-group)#server 1 87::1:2

S1(config-dhcpr-server-group)#exit

/*Configure a relay policy*/

S1(config-dhcpv6)#relay policy 1

S1(config-dhcpv6r-policy-group)#default server-group 1

S1(config-dhcpv6r-policy-group)#exit

/*Configure interface DHCP mode and other attributes*/

S1(config-dhcpv6)#interface vlan10

S1(config-dhcpv6-if)#mode relay

S1(config-dhcpv6-if)#relay agent 86::1:1

S1(config-dhcpv6-if)#relay policy 1

S1(config-dhcpv6-if)#exit

S1(config-dhcpv6)#exit

Configuration on S2:

/*Configure an interface*/







S2(config-if)#ipv6 address 87::1:2/96

S2(config-if)#exit

/*Configure an IPv6 address pool*/

S2(config)#ipv6 addr-pool zte1

S2(config-ipv6-addr-pool)#addr-range 86::1:10 86::1:50

S2(config-ipv6-addr-pool)#exit

/*Enable DHCPv6*/

S2(config)#dhcp ipv6

20-14



S2(config-dhcpv6)#enable

/*Bind the IPv6 address pool to the DHCPv6 pool*/

S2(config-dhcpv6)#pool zte1

S2(config-dhcpv6-pool)#address-lifetime 10000 10000

S2(config-dhcpv6-pool)#exit

/*Bind the DHCPv6 pool to the DHCPv6 policy*/

S2(config-dhcpv6)#policy zte1 1

S2(config-dhcpv6-policy)#dhcpv6-pool zte1

S2(config-dhcpv6-policy)#link-address 86::1:1

S2(config-dhcpv6-policy)#exit

S2(config)#dhcp

/*Configure DHCP mode of the interface*/

S2(config-dhcpv6)#interface vlan20

S2(config-dhcpv6-if)#mode server

S2(config-dhcpv6-if)#server policy zte1

S2(config-dhcpv6-if)#exit

/*Configure a static route*/

S2(config)#ipv6 route 86::/96 87::1:1

Configuration VerificationCheck the DHCPv6 configuration on S1, as shown below.

S1#show running-config dhcpv6

! <DHCPV6>

dhcp ipv6

enable

relay policy 1

default server-group 1

$

relay server group 1

server 1 87::1:2

$

interface vlan10

mode relay

relay agent 86::1:1

relay policy 1

$

! </DHCPV6>

Check the configuration of the IPv6 address pool on S2, as shown below.

S2#show ipv6 addr-pool zte1

20-15



PoolName Lock Begin End Vrf Used Free

zte1 no 86::1:10 86::1:50 0 65

RangeTotal:1

Check the DHCPv6 configuration on S2, as shown below.

S2#show running-config dhcpv6

! <DHCPV6>

dhcp ipv6

enable

policy zte1 1

dhcpv6-pool zte1

link-address 86::1:1

$

pool zte

address-lifetime 10000 10000

$

interface vlan20

mode server

server policy zte1

$

! </DHCPV6>

After the PC user obtains an address through DHCPv6, check the user information on S2,as shown below.

S2#show ipv6 dhcp server user


IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:10




IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:11




IA NA: IA ID 0, T1 50000, T2 80000

Address: 86::1:12



20-16


FiguresFigure 1-1 IPv4 Header Format................................................................................. 1-2

Figure 1-2 IPv6 Header Format................................................................................. 1-2

Figure 1-3 Structure of an IPv6 unicast address........................................................ 1-4

Figure 1-4 IPv6 Address Configuration Example..................................................... 1-15

Figure 3-1 Principles of the IPv6 over IPv4 Tunnel Mechanism ................................. 3-1

Figure 3-2 Principles of the IPv4 (or IPv6) over IPv4 Tunnel ..................................... 3-2

Figure 3-3 Principles of a 6in4 Tunnel ....................................................................... 3-2

Figure 3-4 Principles of a 6to4 Tunnel....................................................................... 3-3

Figure 3-5 6in4 Tunnel Configuration Example.......................................................... 3-6

Figure 3-6 6to4 Tunnel Configuration Example ......................................................... 3-8

Figure 4-1 IPv6 ACL Configuration Example........................................................... 4-10

Figure 5-1 IPv6 Static Route Configuration Example................................................. 5-4

Figure 6-1 RIPng Configuration Example .................................................................. 6-9

Figure 7-1 OSPFv3 Configuration Example ............................................................ 7-14

Figure 7-2 OSPFv3 Configuration Example 2.......................................................... 7-16

Figure 8-1 Single-Area IS-ISv6 Configuration Example ........................................... 8-18

Figure 8-2 Multi-Area IS-ISv6 Configuration Example ............................................. 8-23

Figure 9-1 BGP4+ Route Reflector Configuration Example ....................................... 9-9

Figure 9-2 BGP4+ General Configuration Example................................................. 9-10

Figure 10-1 IPv6 CAR SET Configuration Example................................................. 10-2

Figure 11-1 Structure of IPv6 Multicast Address on Basis of Unicast Prefix............ 11-2

Figure 12-1 MLDv1 Configuration Example............................................................. 12-8

Figure 12-2 Static Group Configuration................................................................. 12-10

Figure 13-1 PIM-SM Configuration Example ......................................................... 13-17

Figure 14-1 IPv6 PIM-SSM Configuration Example................................................. 14-3

Figure 15-1 Sample Networking Topology for the IPv6 Static MulticastConfiguration ........................................................................................ 15-3

Figure 16-1 ISATAP Tunnel Principle ...................................................................... 16-2

Figure 16-2 ISATAP Configuration Example............................................................ 16-3

Figure 20-1 Relation Among DHCPv6 Client, Relay and Server.............................. 20-1

Figure 20-2 DHCPv6 Protocol Message Interaction ................................................ 20-3

Figure 20-3 DHCPv6 Server Configuration Instance ............................................. 20-10

I



Figure 20-4 DHCPv6 Relay Configuration Instance............................................... 20-13

II


TablesTable 1-1 IPv6 Address Types .................................................................................. 1-3

Table 1-2 Aggregatable Global Unicast Address Fields ............................................. 1-4

Table 1-3 Structure of the IPv6 Address Embedded With IPv4 Address .................... 1-6

Table 1-4 Structures of Link-local Address and Site-local Address ............................ 1-7

Table 1-5 Multicast Address Format .......................................................................... 1-8

Table 1-6 Multicast Scope Value ............................................................................... 1-8

Table 1-7 IPv6 Address Compression ..................................................................... 1-10

Table 7-1 Similarities and Differences Between OSPFv3 LSAs and OSPFv2LSAs........................................................................................................ 7-5

Table 11-1 IPv6 Multicast Address Allocation .......................................................... 11-1

III


Tables


IV


Glossary6VPE- IPv6 VPN Provider Edge

ACL- Access Control List

ARP- Address Resolution Protocol

AS- Autonomous System

BDR- Backup Designate Router

BFD- Bidirectional Forwarding Detection

BGP- Border Gateway Protocol

BOOTP- Bootstrap Protocol

BSR- Bootstrap Router

CAR- Committed Access Rate

CE- Customer Edge

DHCP- Dynamic Host Configuration Protocol

DIS- Designate IS

DR- Designated Router

DSCP- Differentiated Services Code Point

DUID- DHCP Unique Identifier

IA- Identity Association

V



IBGP- Interior Border Gateway Protocol

ICMP- Internet Control Message Protocol

IETF- Internet Engineering Task Force

IGMP- Internet Group Management Protocol

IGP- Interior Gateway Protocol

IP- Internet Protocol

IPSec- IP Security Protocol

IPv4- Internet Protocol version 4

IPv6- Internet Protocol Version 6

IPX- Internetwork Packet Exchange protocol

ISATAP- Intra-Site Automatic Tunnel Addressing Protocol

IS-IS- Intermediate System-to-Intermediate System

ISO- International Organization for Standardization

ISP- Internet Service Provider

LAN- Local Area Network

LDP- Label Distribution Protocol

LSA- Link State Advertisement

LSDB- Link-state Database

LSP- Label Switched Path

VI


Glossary

LSP- Link State Packet

LSU- Link State Update

MBGP- Multiprotocol Border Gateway Protocol

MD5- Message Digest 5 Algorithm

MLD- Multicast Listener Discovery

MLDv2- Multicast Listener Discovery Version 2

MPLS- Multiprotocol Label Switching

MSDP- Multicast Source Discovery Protocol

MTU- Maximum Transfer Unit

NBMA- Non-Broadcast Multiple Access

NDP- Neighbor Discovery Protocol

NSAP- Network Service Access Point

OSI- Open System Interconnection

OSPF- Open Shortest Path First

PE- Provider Edge

PIM-SSM- Protocol Independent Multicast-Source Specific Multicast

QoS- Quality of Service

RD- Route Distinguisher

RFC- Request For Comments

VII



RIP- Routing Information Protocol

RIPng- Routing Information Protocol next generation

RP- Rendezvous Point

RPF- Reverse Path Forwarding

RSVP-TE- Resource Reservation Protocol - Traffic Engineering

RT- Route Target

SPF- Shortest Path First

SSM- Source Specific Multicast

TCP/IP- Transmission Control Protocol/Internet Protocol

TLV- Tag, Length, Value

TTL- Time To Live

UDP- User Datagram Protocol

URPF- Unicast Reverse Path Forwarding

VPN- Virtual Private Network

VRF- Virtual Route Forwarding

WRED- Weighted Random Early Detection

VIII


Documents

ZXR105900ESeries - nova-minsk.com · ZXR105900ESeries Easy-MaintenanceMPLSRoutingSwitch ConfigurationGuide (IPv6) Version: 3.00.11 ZTECORPORATION No.55,Hi-techRoadSouth,ShenZhen,P.R.China