NN47263-503 04.01 Configuration IPv6 Routing

Configuration IPv6 and Routing
Avaya Secure Router 2330/4134
10.3
NN47263-503, 04.01
October 2010
2010 Avaya Inc.
All Rights Reserved.

Notice
While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of this documentation unless
such modifications, additions, or deletions were performed by Avaya.
End User agree to indemnify and hold harmless Avaya, Avaya's agents,
servants and employees against all claims, lawsuits, demands and
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the
extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation(s) provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition,
Avayas standard warranty language, as well as information regarding
support for this product, while under warranty, is available to Avaya
customers and other parties through the Avaya Support Web site:
http://www.avaya.com/support. Please note that if you acquired the
product from an authorized Avaya reseller outside of the United States
and Canada, the warranty is provided to you by said Avaya reseller and
not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE
ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.
BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS YOU AND END USER),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (AVAYA).
protected by copyright and other intellectual property laws including the

sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software. Unauthorized reproduction, transmission, dissemination,
storage, and or use without the express written consent of Avaya can
be a criminal, as well as a civil, offense under the applicable law.
Third-party components
Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (Third
Party Components), which may contain terms that expand or limit
rights to use certain portions of the Product (Third Party Terms).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the Avaya Support
Web site: http://www.avaya.com/support/Copyright/.
Trademarks
The trademarks, logos and service marks (Marks) displayed in this
site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the documentation(s) and product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.
Avaya is a registered trademark of Avaya Inc.
All other trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support
Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems
or to ask questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Web site: http://www.avaya.com/
support
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation(s) and Product(s) provided
by Avaya. All content on this site, the documentation(s) and the
product(s) provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is
October 2010
Contents
Chapter 1: New in this release.................................................................................................9
Other changes...................................................................................................................................................9
Chapter 2: IPv6 routing fundamentals...................................................................................11

IPv6 routing fundamentals navigation.............................................................................................................11
The IPv6 header..............................................................................................................................................12
IPv6 addresses.......................................................................................................................................13
Anycast Address.....................................................................................................................................13
Multicast Address...................................................................................................................................13
IPv4-Compatible Address.......................................................................................................................14
Address formats.....................................................................................................................................14
IPv6 extension headers..........................................................................................................................15
Comparison of IPv4 and IPv6.................................................................................................................16
ICMPv6...........................................................................................................................................................17
Neighbor discovery.........................................................................................................................................17
ND messages.........................................................................................................................................18
ND cache................................................................................................................................................19
Router discovery.....................................................................................................................................21
Multicast..........................................................................................................................................................21
IPv6 and the Avaya Secure Router 2330/4134...............................................................................................22
Management access.......................................................................................................................................22
Tunneling.........................................................................................................................................................23
Static IPv4 Tunnel...................................................................................................................................23
Automatic IPv4 Tunnel............................................................................................................................25
IPv6 Tunnels...........................................................................................................................................26
Path MTU discovery........................................................................................................................................26
Routing............................................................................................................................................................27
Static routes............................................................................................................................................27
Open Shortest Path First (OSPF) protocol.............................................................................................30
OSPFv3...........................................................................................................................................................31
Flooding scope.......................................................................................................................................32
Multiple instances per link......................................................................................................................32
Link-local addresses...............................................................................................................................32
Authentication.........................................................................................................................................33
Packet format.........................................................................................................................................33
New LSAs...............................................................................................................................................33
Unknown LSA types...............................................................................................................................34
Stub area................................................................................................................................................34
Routing Information Protocol for IPv6 Networks (RIPng)................................................................................35
Avaya Secure Router 2330/4134 implementation of RIP.......................................................................35
Routing Information Protocol..................................................................................................................35
Border Gateway Protocol for IPv6 Networks (BGP4+)....................................................................................36
Hierarchical mechanisms.......................................................................................................................37
Policy-based routing...............................................................................................................................37
Route redistribution................................................................................................................................38
Security...................................................................................................................................................38
Route reflectors......................................................................................................................................38
Route flap dampening............................................................................................................................39
October 2010
Route refresh..........................................................................................................................................39
BGP planning considerations.................................................................................................................40
BGP multicast.................................................................................................................................................42
Protocol Independent Multicast-Sparse Mode................................................................................................42
PIM-SM concepts and terminology.........................................................................................................43
Shared trees and shortest-path trees.....................................................................................................47
Receiver joining group............................................................................................................................48
Receiver leaving group...........................................................................................................................49
Source sending packets to group...........................................................................................................49
Required elements for PIM-SM operation..............................................................................................50
PIM-SM simplified example....................................................................................................................50
PIM-SM static source groups.................................................................................................................51
Static source groups...............................................................................................................................52
PIM-SM Multipath............................................................................................................................................52
Anycast RP for PIM-SM..................................................................................................................................53
Static Multicast Routing Support.....................................................................................................................53
PIM-SSM.........................................................................................................................................................53
SSM features..........................................................................................................................................53
PIM-SSM architecture............................................................................................................................54
Avaya Secure Router 2330/4134 implementation of SSM and IGMP....................................................56
PIM-SSM static source groups...............................................................................................................59
Configuration limitations.........................................................................................................................59
Multicast link discovery...................................................................................................................................59
MLD versions 1 and 2.............................................................................................................................60
IPv6 Routing over VLAN.................................................................................................................................60
Chapter 3: IPv6 routing procedures......................................................................................61

Enabling unicast routing globally.....................................................................................................................61
Enabling multicast routing globally..................................................................................................................61
Enabling IPv6 on an Ethernet interface...........................................................................................................61
Enabling IPv6 on a bundle..............................................................................................................................62
Configuring the IPv6 address for an interface.................................................................................................62
Configuring Neighbor Discovery parameters..................................................................................................63
Configuring IPv6 redirects...............................................................................................................................64
Configuring an IPv6 general-prefix..................................................................................................................64
Configuring the IPv6 hop-limit.........................................................................................................................65
Configuring IPv6 icmp rate limit......................................................................................................................65
Configuring IPv6 load balancing.....................................................................................................................66
Configuring an IPv6 neighbor..........................................................................................................................66
Configuring IPv6 next-hop address.................................................................................................................67
Establishing static routes................................................................................................................................67
Configuring a multicast static route.................................................................................................................68
Configuring multicast lookup in MRIB only......................................................................................................69
Clearing multicast static routes.......................................................................................................................70
Creating an access list entry...........................................................................................................................70
Creating a prefix list........................................................................................................................................71
Configuring match address of a route.............................................................................................................71
Configuring prefix list match entries................................................................................................................72
Displaying IPv6 access lists............................................................................................................................72
Displaying general prefix information..............................................................................................................73
Displaying IPv6 interface information..............................................................................................................73
October 2010
Displaying the IPv6 multicast routing table.....................................................................................................73

Displaying learned pmtu information...............................................................................................................74
Displaying IPv6 multicast interface information...............................................................................................74
Displaying Neighbor Discovery cache information..........................................................................................74
Displaying IPv6 prefix list information.............................................................................................................75
Displaying the IPv6 routing table.....................................................................................................................75
Displaying IPv6 Router Advertisement information.........................................................................................76
Removing dynamically learned neighbor entries............................................................................................76
Clearing a prefix list.........................................................................................................................................76
Clearing multicast route table entries..............................................................................................................77
Chapter 4: RIPng configuration procedures.........................................................................79

Enabling RIPng...............................................................................................................................................79
Configuring the IPv6 RIP aggregate address..................................................................................................79
Configuring IPv6 default routes.......................................................................................................................80
Configuring IPv6 rip default metrics................................................................................................................80
Configuring IPv6 administrative distance........................................................................................................81
Configuring the IPv6 update filters..................................................................................................................81
Configuring an IPv6 RIP neighbor...................................................................................................................82
Configuring an IPv6 RIP offset-list..................................................................................................................83
Configuring an IPv6 RIP passive interface......................................................................................................83
Configuring an IPv6 RIP route-map................................................................................................................84
Configuring split-horizon.................................................................................................................................84
Configuring route redistribution.......................................................................................................................85
Configuring timers...........................................................................................................................................85
Removing RIPng routes..................................................................................................................................86
Displaying RIPng information..........................................................................................................................87
Displaying RIPng configuration.......................................................................................................................87
Displaying all configured RIPng interfaces......................................................................................................87
Displaying IPv6 RIP information......................................................................................................................87
Displaying the IPv6 RIP database...................................................................................................................88
Displaying IPv6 RIP interface information.......................................................................................................88
Clearing an IPv6 RIP route.............................................................................................................................88
Chapter 5: OSPFv3 procedures.............................................................................................91

Configuring OSPFv3 routing...........................................................................................................................91
Configuring OSPFv3 IPv6 address range.......................................................................................................91
Configuring a stub area...................................................................................................................................92
Configuring a virtual link..................................................................................................................................92
Configure the OSPF area default cost............................................................................................................92
Configuring default-metric values....................................................................................................................93
Configuring a passive interface.......................................................................................................................93
Configuring redistribution of routes into OSPF................................................................................................94
Configuring the IPv6 OSPF ABR type.............................................................................................................94
Configuring IPv6 OSPF cost for an interface..................................................................................................95
Configuring IPv6 OSPF administrative distance.............................................................................................95
Configuring logging of adjacency state changes.............................................................................................96
Configure OSPFv3 routing on an interface.....................................................................................................97
Configuring the dead interval..........................................................................................................................97
Configuring the hello interval...........................................................................................................................97
Configuring OSPF priority...............................................................................................................................98
Configuring IPv6 OSPF link cost.....................................................................................................................98
October 2010
Configuring IPv6 OSPF interface MTU...........................................................................................................99

Configuring the IPv6 OSPF mtu-ignore setting...............................................................................................99
Configuring the IPv6 OSPF network type.....................................................................................................100
Configuring the IPv6 OSPF retransmit interval.............................................................................................100
Configuring the IPv6 OSPF transmission delay............................................................................................101
Displaying OSPFv3 debugging information..................................................................................................102
Display global and area OSPFv3 information...............................................................................................102
Display OSPFv3 interface information..........................................................................................................102
Display OSPFv3 neighbor information..........................................................................................................102
Display OSPFv3 route information................................................................................................................103
Display OSPFv3 virtual link information........................................................................................................103
Displaying IPv6 OSPF border routers...........................................................................................................103
Displaying the IPv6 OSPF database.............................................................................................................103
Clearing IPv6 OSPF routing processes........................................................................................................104
Chapter 6: BGP4+ configuration procedures.....................................................................105

Enabling BGP................................................................................................................................................105
Specifying IPv6 address family.....................................................................................................................105
Configuring a passive session OPEN...........................................................................................................106
Advertising the local router ID as nexthop....................................................................................................106
Comparing the MED value of routes learned from eBGP peers...................................................................107
Removing private AS numbers from route advertisements...........................................................................107
Configuring a BGP Confederation.................................................................................................................108
Configuring a BGP Route Reflector cluster...................................................................................................109
Enabling an address family for a neighbor....................................................................................................109
Configuring interval for BGP route updates...................................................................................................110
Configuring interval for AS-origination updates.............................................................................................110
Advertising capability to a peer......................................................................................................................111
Configuring to originate a default route to neighbor......................................................................................112
Configuring a neighbor description................................................................................................................112
Configuring a distribution list.........................................................................................................................113
Disallowing capability negotiation..................................................................................................................114
Allowing EBGP neighbors from indirectly connected networks.....................................................................114
Configuring BGP filters..................................................................................................................................115
Enabling BGP on an interface.......................................................................................................................115
Configuring maximum number of prefixes.....................................................................................................116
Configuring a neighbor password..................................................................................................................117
Configuring peer-group members..................................................................................................................117
Configuring a prefix list..................................................................................................................................118
Configuring AS number of a remote BGP neighbor......................................................................................119
Configuring a route map to a neighbor..........................................................................................................119
Configuring a neighbor as route reflector client............................................................................................120
Configuring a neighbor as route server client...............................................................................................120
Sending a community attribute to a neighbor................................................................................................121
Shutting down a neighbor.............................................................................................................................122
Configuring BGP neighbor timers.................................................................................................................122
Configuring a routing update source.............................................................................................................123
Configuring weight for a BGP neighbor.........................................................................................................123
Modifying a default bestpath selection..........................................................................................................124
Configuring client-to-client route reflection....................................................................................................125
Configuring a route reflector cluster-id..........................................................................................................125
October 2010
Configuring AS confederation parameters....................................................................................................126

Enabling route flap dampening.....................................................................................................................127
Configuring BGP defaults..............................................................................................................................127
Enforcing first AS for EBGP routes...............................................................................................................128
Resetting a session when a peer goes down................................................................................................129
Logging neighbor changes............................................................................................................................129
Overriding current router-id...........................................................................................................................130
Configuring background scan interval...........................................................................................................130
Defining the administrative distance.............................................................................................................131
Configuring IGP synchronization...................................................................................................................132
Configuring routing timers.............................................................................................................................132
Redistributing information from another protocol..........................................................................................133
Configuring BGP aggregate entries..............................................................................................................134
Configuring EBGP-ECMP processing...........................................................................................................134
Activating the current address family for a neighbor.....................................................................................135
Configuring to accept an AS-path containing the current AS........................................................................135
Configuring to start storing updates..............................................................................................................136
Configuring to selectively unsuppress suppressed routes............................................................................136
Specifying a network to announce via BGP..................................................................................................137
Configuring aggregation on same next hop..................................................................................................137
Displaying BGP routes matching communities.............................................................................................138
Displaying all BGP4+ community information...............................................................................................138
Displaying detailed BGP4+ neighbor information..........................................................................................139
Displaying routes matching an AS path regular expression..........................................................................139
Displaying the BGP4+ scan status................................................................................................................139
Displaying BGP attribute information............................................................................................................140
Displaying BGP paths...................................................................................................................................140
Displaying BGP neighbor status summary....................................................................................................140
Displaying inconsistent AS paths..................................................................................................................140
Displaying detailed dampening information..................................................................................................141
Displaying routes matching route map..........................................................................................................141
Display routes matching a prefix list..............................................................................................................142
Display routes matching a filter list................................................................................................................142
Display routes matching a community list.....................................................................................................142
Display routes matching an AS path regular expression..............................................................................143
Initiating a BGP Route Refresh.....................................................................................................................143
Resetting all BGP peers in IPv6 family.........................................................................................................143
Resetting an IPv6 BGP connection...............................................................................................................144
Chapter 7: PIM configuration procedures...........................................................................145

Registering an accept filter............................................................................................................................145
Configuring candidate bootstrap router.........................................................................................................145
Setting the source address for PIM register..................................................................................................146
Configuring source-specific multicast............................................................................................................147
Configuring the PIM rendezvous point address............................................................................................147
Configuring a PIM rendezvous point candidate............................................................................................148
Configuring to not have source-tree switching threshold..............................................................................148
Enabling a BSR border router.......................................................................................................................149
Setting Hello message interval......................................................................................................................149
Enabling PIM sparse-mode operation...........................................................................................................150
Configuring PIM router DR priority................................................................................................................150
October 2010
Configuring to exclude Gen-id.......................................................................................................................151

Configuring a PIM peering filter.....................................................................................................................151
Configuring PIM neighbor change logging....................................................................................................152
Configuring an anycast member RP address...............................................................................................152
Configuring PIM multipath.............................................................................................................................153
Displaying PIM RPF......................................................................................................................................154
Clearing PIM statistics...................................................................................................................................154
Configuring embedded RP mapping.............................................................................................................155
Displaying PIM RP........................................................................................................................................155
Displaying group-to-RP mappings................................................................................................................156
Displaying PIM statistics...............................................................................................................................156
Displaying bootstrap router information........................................................................................................156
Displaying the PIM Tree Information Base....................................................................................................156
Displaying PIM interface information.............................................................................................................157
Displaying group-to-RP mapping information...............................................................................................157
Displaying PIM neighbor information............................................................................................................157
Displaying PIM Rendezvous Point information.............................................................................................158
Clearing PIM bootstrap router information....................................................................................................158
Chapter 8: MLD procedures.................................................................................................159

Configuring multicast group membership......................................................................................................159
Configuring leave latency..............................................................................................................................159
Configuring query intervals...........................................................................................................................160
Configuring query timeouts...........................................................................................................................160
Configuring the robustness variable..............................................................................................................161
Configuring the MLD version.........................................................................................................................161
Configuring MLD last-member query-count..................................................................................................161
Configuring group-specific query interval......................................................................................................162
Configuring the MLD query maximum response time...................................................................................162
Configuring global state limit.........................................................................................................................163
Configuring state limit on an interface...........................................................................................................164
Configuring the SSM mapping status............................................................................................................164
Configuring a static SSM map.......................................................................................................................165
Configuring a static group on an interface....................................................................................................165
Displaying MLD statistics..............................................................................................................................166
Clearing MLD statistics.................................................................................................................................167
Display MLD groups......................................................................................................................................167
Display MLD interface information................................................................................................................167
Clearing MLD group entries..........................................................................................................................168
Clearing MLD interface entries......................................................................................................................168
October 2010
Chapter 1: New in this release

There is no new content added to Avaya Secure Router 2330/4134 Configuration IPv6 and Routing
(NN47263-503) for Release 10.3.
Other changes
This document is rebranded to Avaya.
October 2010
New in this release
10
October 2010
Chapter 2: IPv6 routing fundamentals

The router-management features apply regardless of which routing protocols you use and include router
Internet Protocol version 6 (IPv6) configuration and IPv6 route table management.
IPv6 routing fundamentals navigation

The IPv6 header on page 12
ICMPv6 on page 17
Neighbor discovery on page 17
Multicast on page 21
IPv6 and the Avaya Secure Router 2330/4134 on page 22
Management access on page 22
Tunneling on page 23
Path MTU discovery on page 26
Routing on page 27
OSPFv3 on page 31
Routing Information Protocol for IPv6 Networks (RIPng) on page 35
Border Gateway Protocol for IPv6 Networks (BGP4+) on page 36
BGP multicast on page 42
Protocol Independent Multicast-Sparse Mode on page 42
PIM-SSM on page 53
Multicast link discovery on page 59
PIM-SM Multipath on page 52
Anycast RP for PIM-SM on page 53
Static Multicast Routing Support on page 53
IPv6 Routing over VLAN on page 60
October 2010
11
IPv6 routing fundamentals
The IPv6 header

The IPv6 header contains the following fields:
a 4-bit Internet Protocol version number, with a value of 6
an 8-bit traffic class field, similar to Type of Service in IPv4
a 20-bit flow label that identifies traffic flow for additional quality of service
a 16-bit unsigned integer, the length of the IPv6 payload
an 8-bit next header selector, that identifies the following header
an 8-bit hop limit unsigned integer that decrements by 1 each time a node forwards the
packet. Nodes discard packets with hop limit values of 0.
a 128-bit source address
a 128-bit destination address
Figure 1: IPv6 header on page 12 illustrates the IPv6 header.
Figure 1: IPv6 header
12
October 2010
The IPv6 header
IPv6 addresses
IPv6 addresses are 128 bits in length. The address identifies a single interface or multiple
interfaces. IPv4 addresses, in comparison, are 32 bits in length. The increased number of
possible addresses in IPv6 solves the inevitable IP Address exhaustion inherent to IPv4.
The IPv6 address contains two parts: an address prefix and an IPv6 interface ID. The first 3
bits indicate the type of address that follows. Figure 2: 128-Bit IPv6 address format on
page 13 shows the IPv6 address format.
Figure 2: 128-Bit IPv6 address format
An example of a unicast IPv6 address is 1080:0:0:0:8:8000:200C:417A
Interface ID
The interface ID is a unique number that identifies an IPv6 node (a host or a router). For
stateless autoconfiguration the ID is 64 bits in length.
In IPv6 stateless autoconfiguration, the interface ID is derived by a formula that uses the link
layer 48-bit MAC address. (In most cases, the interface ID is a 64-bit interface ID that contains
the 48-bit MAC address.) The IPv6 interface ID is as unique as the MAC address.
If you manually configure interface IDs or MAC addresses (or both), no relationship between
the MAC address and the interface ID is necessary. A manually configured interface ID can
be longer or shorter than 64 bits.
Anycast Address
An IPv6 anycast address is a unicast address identifying a group of IPv6 nodes that share a
common variable-length address prefix. A packet bearing an anycast address is delivered to
one node in the group. There is no visual way of distinguishing an anycast address from an
unicast address.
Multicast Address
An IPv6 multicast address identifies a group of nodes. A packet bearing a multicast address
is delivered to all members of the group. (The function of IPv4 broadcast addresses has been
superseded by IPv6 multicast addresses.)
October 2010
13
Figure 3: Multicast Address Format on page 14 shows the format of an IPv6 multicast
address.
Figure 3: Multicast Address Format
A value of FF (11111111) in the 8 high-order bits of an IPv6 address indicates that the address
specifies a multicast group. The 4-bit flags field indicates whether the group is permanent or
transient. The 4-bit scope field indicates the scope of the group specified in the 112-bit group
ID field. The scope options are:
1 - node local
2 - link-local
3 - subnet local
4 - admin local
5 - site-local
8 - organization-local
B - community-local
E - global
An example of a multicast address is: FF01:0:0:0:0:0:0:101
IPv4-Compatible Address
The IPv4-compatible address, which includes an IPv4 address in the low-order 32 bits, is
intended for IPv6 nodes that need to inter operate with IPv4 nodes. Figure 4: IPv4Compatible Unicast Address Format on page 14 shows the format of an IPv4-compatible
address.
Figure 4: IPv4-Compatible Unicast Address Format
Address formats
The format for representing an IPv6 address is
14
October 2010
The IPv6 header
n:n:n:n:n:n:n:n
n is the hexadecimal representation of 16 bits in the address. For example:
FF01:0:0:0:0:0:0:43
Each non zero field must contain at least one numeral. Within a given hexadecimal field
however, leading zeros are not required.
Certain classes of IPv6 addresses commonly include multiple contiguous fields containing
hexadecimal 0. The following sample address includes five contiguous fields containing 0
represents contiguous fields containing zeroes with a double colon (::):
FF01::43
You can use a double colon to compress the leading zero fields in a hexadecimal address. A
double colon can appear once in an address.
An IPv4-compatible address combines hexadecimal and decimal values as follows:
x:x:x:x:x:x:d.d.d.d
x:x:x:x:x:x is a hexadecimal representation of the six high-order 16-bit pieces of the address,
and d.d.d.d is a decimal representation of the four 8-bit pieces of the address. For example:
0:0:0:0:0:0:13.1.68.3
or
::13.1.68.3
IPv6 extension headers

IPv6 extension headers describe processing options. Each extension header contains a
separate category of options. A packet can include zero or more extension headers, see Figure
5: IPv6 Header and Extension Headers on page 15.
Figure 5: IPv6 Header and Extension Headers
IPv6 examines the destination address in the main header of each packet it receives: this
examination determines whether the router is the packet destination or an intermediate node
in the packet data path. If the router is the destination of the packet, IPv6 examines the header
extensions that contain options for destination processing. If the router is an intermediate node,
IPv6 examines the header extensions that contain forwarding options.
October 2010
15
By examining only the extension headers that apply to the operations it performs, IPv6 reduces
the amount of time and processing resources required to process a packet.
IPv6 defines the following extension headers:
The hop-by-hop extension header contains optional information that all intermediate IPv6
routers examine between the source and the destination.
The end-to-end extension header contains optional information for the destination node.
The source routing extension header contains a list of one or more intermediate nodes
that define a path for the packet to follow through the network, to its destination. The
packet source creates this list. This function is similar to the IPv4 source routing options.
The fragmentation extension header uses by an IPv6 source to send packets larger than
the size specified for the path MTU.
The authentication extension header and the security encapsulation extension header,
used singly or jointly, provide security services for IPv6 datagrams.
Comparison of IPv4 and IPv6

Table 1: IPv4 and IPv6 differences on page 16 compares key differences between IPv4 and
IPv6.
Table 1: IPv4 and IPv6 differences
Feature
16
IPv4
IPv6
Address length
32 bits
128 bits
IPSec support
Optional
Required
QoS support
Limited
Improved
Fragmentation
Hosts and routers
Hosts only
MTU Packet size
576 bytes
1280 bytes
Checksum in header
Yes
No
Options in header
Yes
No
Link-layer address
resolution
ARP (broadcast)
Multicast Neighbor
Discovery Messages
Multicast membership
IGMP
Multicast Listener Discovery

(MLD)
Router Discovery
Optional
Required
Uses broadcasts
Yes
No
Configuration
Manual, DHCP
Automatic, DHCP
October 2010
ICMPv6
ICMPv6
Internet Control Message Protocol (ICMP) version 6 maintains and improves upon features
from ICMP for IPv4. ICMPv6 reports the delivery of forwarding errors, such as Destination
Unreachable, Packet Too Big, Time Exceeded, and Parameter Problem. ICMPv6 also delivers
information messages such as echo request and echo reply.
Important:
ICMPv6 plays an important role in IPv6 features such as Neighbor Discovery, Multicast
Listener Discovery and Path MTU Discovery.
Neighbor discovery
Neighbor discovery (ND) allows IPv6 nodes (routers and hosts) on the same link to discover
link layer addresses and to obtain and advertise various network parameters and reachability
information. ND combines the services provided for IPv4 with the Address Resolution Protocol
(ARP) and router discovery. ND replaces ARP in IPv6.
Hosts use ND to discover the routers in the network that you can use as the default routers,
and to determine the link layer address of their neighbors attached on their local links. Routers
also use ND to discover their neighbors and their link layer information. ND also updates the
neighbor database with valid entries, invalid entries, and entries migrated to different locations.
ND protocol provides you with the following:
Address and prefix Discovery: hosts determine the set of addresses that are on-link for
the given link. Nodes determine which addresses or prefixes are locally reachable and
are remote with address and prefix discovery.
Router Discovery: hosts discover neighboring routers with router discovery. Hosts then
establish neighbors as default packet-forwarding routers.
Parameter Discovery: host and routers discover link parameters such as the link MTU or
the hop limit value placed in outgoing packets.
Duplicate address detection: hosts and nodes determine if an address is assigned to
another router or a host.
Address Resolution: hosts determine link layer addresses (MAC for Ethernet) of the local
neighbors (attached on the local net), provided the IP address is known.
Next-Hop determination: hosts determine how to forward local or remote traffic with nexthop determination. The next-hop can be a local or remote router.
October 2010
17
Neighbor unreachability detection: hosts determine if the neighbor is reachable, and

address resolution must be performed again to update the database. For neighbors you
use as routers, hosts attempt to forward traffic through alternate default routers.
Redirect: routers inform the host of more efficient routes with redirect messages.
Neighbor discovery is categorized into three components:
Host-Router discovery
Host-Host communication component
Redirect
See Figure 6: Neighbor Discovery components on page 18 for the ND components.
Figure 6: Neighbor Discovery components
ND messages
Table 2: IPv6 and IPv4 Neighbor comparison on page 18 shows new ICMPv6 message types.
Table 2: IPv6 and IPv4 Neighbor comparison
IPv4 Neighbor
Function
18
IPv6 Neighbor
Function
Description
ARP Request message Neighbor Solicitation

message
A node sends this message to

determine the link-layer address of a
neighbor or to verify that a neighbor is
still reachable through a cached linklayer address. You can also use
Neighbor Solicitations for Duplicate
Address Detection.
ARP Reply message
Neighbor
Advertisement
A node sends this message either in

response to a received Neighbor
Solicitation message or to
communicate a link-layer address
change.
ARP cache
Neighbor cache
The neighbor cache contains

information about neighbor types on
October 2010
Neighbor discovery
IPv4 Neighbor
Function
IPv6 Neighbor
Function
Description
the network. See ND cache on
page 19.
Gratuitous ARP
Duplicate address
detection
A host or node sends a request with its

own IP address to determine if another
router or host uses the given address.
The source receives a reply from the
duplicate device. Both hosts and
routers use this.
Router Solicitation
message (optional)
Router Solicitation
(required)
The host sends this message upon

detecting a change in a network
interface operational state. The
message requests that routers
generate Router Advertisement
immediately rather than at the
scheduled time.
Router Advertisement
message (optional)
Router Advertisement
(required)
Routers send this message to

advertise their presence together with
various links and Internet parameters
either periodically, or in response to a
Router Solicitation message. Router
Advertisements contain prefixes that
you use for on-link determination or
address configuration, and a
suggested hop limit value.
Redirect message
Redirect message
Routers send this message to inform

hosts of a better first hop for a
destination.
ND cache
The neighbor discovery cache lists information about neighbors in your network.
The neighbor discovery cache can contain the following types of neighbors:
Static: a configured neighbor
Local: a device on the local system
Dynamic: a discovered neighbor
Table 3: Neighbor cache states on page 20 describes neighbor cache states.
October 2010
19
Table 3: Neighbor cache states

State
Description
Incomplete
A node sends a neighbor solicitation message to a multicast

device. The multicast device sends no neighbor advertisement
message in response.
Reachable
You receive positive confirmation within the last ReachableTime

period.
Stale
A node receives no positive confirmation from the neighbor in

the last Reachable Time period.
Delay
A time period longer than the ReachableTime period passes

since the node received the last positive confirmation, and a
packet was sent within the last DELAY_FIRST_PROBE_TIME
period. If no reachability confirmation is received within
DELAY_FIRST_PROBE_TIME period of entering the DELAY
state, Neighbor Solicitation is sent and the state is changed to
PROBE.
Probe
Reachability confirmation is sought from the device every

RetransmitTimer period.
The following events affect the Neighbor cache. Processing the following events involves layer
2 and layer 3 interaction:
Important:
Administrative actions cause certain events. These events affect system stability.
Flushing the VLAN MAC.
Remove VLANr.
Performing an action on all VLANs.
Remove a port from a VLAN.
Performing an action that disables a VLAN, such as removing all ports from VLAN.
Disable a tagged port that is a member of multiple routable VLANs.
Table 4: IPv4 and IPv6 Neighbor Discovery comparison on page 20 shows a comparison of
IPv4 and IPv6 Neighbor Discovery.
Table 4: IPv4 and IPv6 Neighbor Discovery comparison
IPv4 Neighbor Functions
20
ARP Request message
Neighbor Solicitation message
ARP Reply message
Neighbor Advertisement message
ARP cache
Neighbor cache
October 2010
Multicast
Gratuitous ARP
Duplicate address detection
Router Solicitation message (optional)
Router Solicitation (required)
Router Advertisement message (optional)
Router Advertisement (required)
Redirect message
Redirect message
Router discovery
IPv6 nodes discover routers on the local link with router discovery. The IPv6 router discovery
process uses the following messages:
Router advertisement on page 21
Router solicitation on page 21
Router advertisement
Configured interfaces on an IPv6 router send out router-advertisement messages. Routeradvertisements are also sent in response to router-solicitation messages from IPv6 nodes on
the link.
Router solicitation
An IPv6 host without a configured unicast address sends router solicitation messages.
Multicast
Most of the IPv6 routing protocols use multicast addresses for sending some of the protocol
information, especially during the discovery phase. In order to receive these messages the
device has register the well-known multicast addresses when a particular protocol is enabled
and deregisters when the protocol is disabled.
As in IPv4, a multicast address is assigned to a set of interfaces belonging to different nodes. A
packet destined to a multicast address is routed to all interfaces identified by that address. The
IPv6 multicast address uses the FF00::/8 prefix which is equivalent to the Ethernet multicast
address of 33-33-.
There is multicast neighbor solicitation for address resolution, duplicate address detection and
multicast router solicitation and router advertisement
October 2010
21
IPv6 and the Avaya Secure Router 2330/4134

IPv6 routing provides an underlying mechanism for transmitting blocks of data from source to
destination. The source and destination are hosts, identified by fixed-length IPv6 addresses.
Transmission control protocol (TCP) and user datagram protocol (UDP) provide transport
facility for data transmission. TCP is a reliable mechanism. UDP is not as reliable as TCP.
Routing protocols 6 through 8 identify the shortest path from a given source to a destination.
Internet Protocol 1 defines a standard format primarily known as the IP header, required for
successful delivery of datagram. Transport and routing protocols are physical media agnostic.
The next hop path calculated by the routing protocol in path from source to destination can
result in the next hop being connected on an Ethernet interface. In such a case, the nexthop router must request a mapping of a next-hop IPv6 address to a 48 bit MAC address. IPv6
neighbor-discovery protocol, described in RFC 2461, defines a mechanism to identify existing/
upcoming neighbors in the network. This mechanism combines the ARP, router discovery, and
redirect information into one. Due to this combination of features, the mechanism supports the
auto configuration of host entities.
Management access
The Avaya Secure Router 2330/4134 contains an Ethernet port for both master and standby
CPU. These Ethernet ports are configured differently from the regular switch ports. In IPv4,
the protocol stack operating for these ports is different than the switch IP stack. The IPv6
functionality for the CPU Ethernet port is offered only when the switch operational state is up,
and is not offered from the boot monitor level.
The management port has three functions:
enabling IPv6 from the boot monitor and from the CLI.
configurating IPv6 after the system boots up in the CLI and device management through
the configured IPv6 address
configuring static routes reachable through the management route for connectivity
IPv6 supports multiple addresses on each interface. This is supported for multiple addresses to
management IP interface.
In addition to the management port, you can configure management routes to reach non local
destinations.
The Avaya Secure Router 2330/4134 advertises the management port and the management
route to the regular routing domain (OSPFv3), but does not include the prefix for the interface in
the router advertisement.
22
October 2010
Tunneling
Tunneling
Tunneling is a forwarding technique in which a packet is encapsulated inside another packet.
IPv6 supports two kinds of encapsulating tunnels: IPv4 tunnels and IPv6 tunnels.
In IPv4 tunneling, a router running both IPv6 and IPv4 encapsulates an IPv6 packet within an
IPv4 packet. This technique allows IPv6 nodes in noncontiguous IPv6 regions to forward
messages through an intervening region of IPv4 nodes.
In IPv6 tunneling, a router running IPv6 encapsulates an IPv6 packet in another IPv6 packet.
This section covers the following topics:
Static IPv4 Tunnel on page 23
Automatic IPv4 Tunnel on page 25
IPv6 Tunnels on page 26
Static IPv4 Tunnel

A static tunnel -- also called a configured tunnel -- is a mechanism for forwarding any IPv6
packet through an IPv4 region. Figure 7: Configured IPv4 Static Tunnel on page 24 shows
a static tunnel between an IPv4 interface on router C and an IPv4 interface on router D. (Note
that routers C and D are running both IPv4 and IPv6.)
October 2010
23
Figure 7: Configured IPv4 Static Tunnel
In Figure 7: Configured IPv4 Static Tunnel on page 24, for example, a user connected to router
B in Region 1 sends a packet addressed to a user on router F in Region 3. The following steps
occur:
1. Router C receives the IPv6 packet and determines that it must be forwarded out its
tunnel interface.
2. Router C encapsulates the IPv6 packet in an IPv4 header.
The source address in the IPv4 header is the IPv4 address of the local tunnel
interface on router C. The destination address is the IPv4 address of the remote
tunnel interface on router D.
3. Using the IPv4 header, intermediate IPv4 routers in Region 2 forward the
encapsulated packet through the IPv4 region to router D.
4. Router D decapsulates the packet (removing the IPv4 header) and forwards the
original IPv6 packet to router F.
After you have configured the IPv4 interfaces on the end point routers, the tunnel becomes a
permanent point-to-point link in the IPv6 topology.
24
October 2010
Tunneling
Automatic IPv4 Tunnel

An automatic tunnel is a mechanism for forwarding unicast IPv6 packets that use the IPv4compatible address format. All routers in IPv6 regions that use automatic tunneling must run
both IPv6 and IPv4.
IPv6 creates the tunnel dynamically as needed for the purpose of forwarding an IPv6 packet
through multiple IPv4 and IPv4/IPv6 routers.
In Figure 8: Automatic IPv4 Tunnel on page 25, for example, a user connected to router B
in Region 1 wants to send an IPv6 packet to a user on router J in Region 3.
Figure 8: Automatic IPv4 Tunnel
The following steps occur:

1. Router D receives the packet and determines that the next hop requires an
automatic tunnel.
2. Router D encapsulates the packet in an IPv4 header.
The source address in the IPv4 header is the IPv4 address of the local tunnel
interface on node D.
The destination address is the IPv4 address contained in the IPv4-compatible IPv6
address. This is the address of an IPv4 interface on router J.
October 2010
25
3. IPv4 routers in Region 2 forward the packet to Region 3.

4. IPv4/IPv6 routers in Region 3 forward the IPv4 packet to router J.
5. Router J decapsulates the packet.
Note that unlike a configured tunnel, which is a permanent point-to-point link in the IPv6
topology, an automatic tunnel is a dynamic mechanism, created by the encapsulating end point
for the purpose of forwarding an IPv6 packet. After the packet reaches its destination, the
automatic tunnel no longer exists.
IPv6 Tunnels
Tunneling provides a mechanism for transferring IPv6 traffic through an IPv4 network.
Manually configured tunnels

Manually configured tunnels are point-to-point. IPv6 reachability enables tunnel forwarding.
Manually configured tunnels provide communication between two isolated IPv6 domains over
an IPv4 network. Create a point-to-point connectivity between the two isolated IPv6 devices
by configuring the tunnel endpoints. Tunnel interfaces are logical point-to-point interfaces.
Enable a routing protocol, such as the open shortest path first (OSPF) protocol, on the
interfaces to allow dynamic routing.
You cannot configure the maximum transmission unit (MTU) for tunnels. The default MTU value
for tunnels is 1280. Tunnel operational status depends on the IPv4 reachability of the tunnel
endpoint. The Avaya Secure Router 2330/4134 attempts reachability through R modules and
updates IPv6 information with changes.
Configure IPv6 and IPv4 addresses at each end of the tunnel. The router or host at the source
and destination of the tunnel must support both IPv4 and IPv6 protocol stacks.
Important:
Classic modules cannot perform encapsulation or decapsulation. All IPv4 route reachability
requires R modules.
Path MTU discovery

IPv6 routers do not fragment packets. The source node sends a packet equal in size to the
maximum transmission unit (MTU) of the link layer. The packet travels through the network to
source. If the packet encounters a link to a smaller MTU, the router sends the source node an
ICMP error message containing the MTU size of the next link.
26
October 2010
Routing
The source IPv6 node then resends a packet equal to the size of the MTU included in the ICMP
message.
The default value for a regular interface is 1500.
Routing
A routing table is present on all nodes. The table stores information about IPv6 network prefixes
and how they are reached. IPv6 checks the destination neighbor cache first. If the destination is
not in the destination neighbor cache, the routing table determines:
the interface used for forwarding (the next-hop interface)
the next-hop address
Routing protocols to exchange IPv6 routing prefixes are required. IPv6 routes in a routing table
can be:
directly attached network routes using a 64-bit prefix
remote network routes using a 64-bit or lower prefix
host routes using a 128-bit prefix length
the default route using a prefix of ::/0
Route redistribution is limited to static routes and local device using the OSPFv3 protocol. The
dynamic protocols supported are OSPFv3, RIPng and BGP.
When routing on a VLAN, an IP address is assigned to the VLAN and is not associated with
any particular physical port. Brouter ports are VLANs that route IP packets and bridge
nonroutable traffic in a single-port VLAN.
This section has the following topics:
Static routes on page 27
Open Shortest Path First (OSPF) protocol on page 30
Static routes
Static routes provide an alternative method for establishing route reachability. This, with
dynamic routes, provides routing information from the forwarding database to the forwarding
plane. Only enabled static routes are submitted to the Route Table Manager (RTM), which
determines the best route based on reachability, route preference, and cost. The RTM
communicates all the updates to best routes to the forwarding plane.
You must provide the following options to configure a static route:
Route preference: you can specify the route preference for the static routes as follows:
- Global value for all static routes: either static or dynamic routes are preferred.
October 2010
27
- Preference per static-route-entry: if specified, this value over-rides the global value
for the entry. This provides flexibility to change the general behavior of a specific
static route.
Multiple static routes: specify alternative paths to the same destination. Multiple static
routes provide stability and load balancing.
To configure a default static route, supply a value of 0 for the prefix and the prefix length.
Events that affect static route operation include user-configured changes or other system
events, such as:
Deleting the Ipv6 addresses of a VLAN.
The static route with the corresponding local neighbors are permanently deleted from the
RTM, the forwarding database, and the configuration database.
Deleting a VLAN.
Static routes with a local next-hop option set are removed from the configuration
database. Static routes with a non local next-hop option become inactive (they are
removed from the forwarding database).
Disabling forwarding on a VLAN.
Static routes that are reachable through the locally attached network become inactive.
Disabling a VLAN, making the static routes inactive.
Disabling IPv6 forwarding globally.
A change in a dynamically learned neighbor.
When a neighbor becomes unreachable or is deleted, the static route with the neighbor
becomes inactive, and the configuration is not affected. The static route with the neighbor
becomes active in the configuration and is added to the RTM and forwarding database.
Enable a static route
Add the route to the RTM to change certain static routes to active.
Delete a static route.
Permanently delete a static route from the configuration.
Disable a static route.
Change a preference.
When the static route preference changes, the selection of best routes for the entries have
both static and dynamic paths.
Delete or disable a tunnel.
Deleting or disabling a tunnel removes the tunnel entry from the forwarding table.
Enable the tunnel.
Enabling a tunnel activates the tunnel static routes and adds an entry to the forwarding
table.
28
October 2010
Routing
The local-nexthop-flag is not required in IPv6. An Ipv4 device cannot learn a neighbor ARP
entry unless the device has a local route entry. In Ipv6, a host can learn a neighbor entry if the
device is physically connected to the neighbor (one hop).
The static route becomes active when the next-hop is reachable by a dynamic route neighbor
resolution. The static route takes the forwarding information from the dynamic route. If the
next-hop is reachable via local route, the neighbor resolution is required.
IP static route table

The static route table is separate from the system routing table that the router uses to make
forwarding decisions. The static route table allows you to change static routes directly. Although
the tables are separate, the Static Route Table Manager entries are automatically reflected in
the System Routing Table if the next hop address in the static route is reachable and if the
static route is enabled.
The static route table is indexed by four attributes:
Destination Network
Destination Mask
Next Hop
ifIndex
The maximum number of entries is 100. You can insert static routes using the Static Route
Table, and you can delete static routes by using either the Static Route Table or the System
Routing Table.
Important:
The System Routing Table displays only active static routes with the "best route" preference.
A static route is active only if the route is enabled and that the next hop address is reachable.
You can enter multiple routes (for example, multiple default routes) that have different costs
and the lowest-cost route that is reachable appears in the routing table. If you enter multiple
next hops for the same route with the same cost, the switch does not replace the existing route.
If you enter the same route with the same cost and a different next hop, the first route is used.
However, if that first route becomes unreachable, the second route (with a different next hop) is
activated with no loss of connectivity.
Static routes configured for the management port are applied with the natural mask of the
network. Because traffic that originates from the switch refers to these routes before checking
the IP routing table, the switch management traffic can be incorrectly forwarded from the
management port, even though a specific route exists in the routing table.
October 2010
29
Black hole static routes

While aggregating or injecting routes to other routers, a router may not have a route to the
aggregated destination, which causes a "black hole." To avoid routing loops, you can configure
a black hole static-route to the destination it is advertising.
A black hole route is a route with invalid next hop, so that the data packets destined to this
network will be dropped by the switch.
When you specify a route preference, be sure that you configure the preference value
appropriately so that when the black-hole route is used, it gets elected as the best route. Before
adding the black hole route a check is made to ensure that no other static route to that identical
destination in an enabled state exists. If such a route exists, then you are not allowed to add
the black hole route, and an error message is generated.
However, if there is an enabled black hole route, then you will not be allowed to add another
static route to that destination. You must first delete or disable the black hole route before you
can add a regular static route to that destination.
Open Shortest Path First (OSPF) protocol

Open Shortest Path First (OSPF) Protocol is an Interior Gateway Protocol (IGP) that distributes
routing information between routers belonging to a single autonomous system (AS). OSPF is a
link-state protocol intended for use in large networks.
This section includes the following topics:
Overview on page 30,
Benefits on page 31
Neighbors on page 31
Overview
In an OSPF network, each router maintains a link-state database that describes the topology of
the autonomous system (AS). The database contains the local state for each router in the AS,
including usable interfaces and reachable neighbors. If the router detects any changes, it
shares them by flooding link-state advertisements (LSAs) throughout the AS. Routers
synchronize topological databases based on the sharing of information from LSAs.
From the topological database, each router constructs a shortest-path tree, with itself as the
root. The shortest-path tree gives the optimal route to each destination in the AS. Routing
information from outside the AS appears on the tree as leaves.
OSPF routes IP traffic based solely on the destination IP address and the prefix contained in
the IP packet header.
30
October 2010
OSPFv3
OSPFv3 is supported in IPv6 routing. OSPFv3 runs on a per-link basis, rather than a persubnet basis. Multiple instances are possible on a single link. OSPFv3 does not support the
OSPFv2 authentication feature.
Benefits
In large networks, OSPF offers the following benefits:
Fast convergence: in the event of topological changes, OSPF recalculates routes quickly.
Minimal routing protocol traffic
Load sharing: OSPF provides support for equal-cost multipath routing. If several equalcost routes to a destination exist, traffic is distributed equally among them.
Type of Service: separate routes can be calculated for each IP Type of Service.
Neighbors
In an OSPF network, any two routers with an interface to the same network are neighbors.
Routers use the Hello Protocol to discover their neighbors and maintain neighbor relationships.
On a broadcast or point-to-point network, the Hello Protocol dynamically discovers neighbors.
On a non broadcast multiaccess network (NBMA), you must manually configure neighbors for
the network.
The Hello Protocol provides bi directional communication between neighbors. Periodically,
OSPF routers send out hello packets over all interfaces. These hello packets include the
following information:
the priority
the Hello Timer and Dead Timer values
a list of routers that sent hello packets on the interface
the choice between designated router (DR) and backup designated router (BDR)
Routers establish bidirectional communication when one router discovers itself listed in the
neighbor router hello packet.
OSPFv3
This section is an overview of the differences between Open Shortest Path First (OSPF)v3
protocol, developed for IPv6, and OSPFv2, used in IPv4. This information is compiled from
RFC 2740.
The IPV4 terms subnet and network are replaced in IPv6 by link. An IPv6 link is a
communication medium between nodes at the link layer. You can assign multiple IP subnets
October 2010
31
(prefixes) to a link. Two IPv6 nodes with common or different prefixes can communicate over
a single link.
OSPF for IPv6 operates on a per-link basis, rather than per-IP-subnet, as in IPv4. IPv6 makes
the following changes to how packets are received and to the contents of Network-LSAs and
hello packets:
The OSPF packet contains no IPv6 addresses. LSA payloads carried in Link State Update
packets contain IPv6 addresses.
The following IDs remain at 32-bits and are not assigned IPv6 addresses: Area IDs, LSA
Link State IDs, and OSPFRouter IDs.
Router IDs identify neighboring routers, identified by an IP address on broadcast and
NBMA networks in OSPFv2.
Flooding scope
LSA flooding scope is generalized in OSPFv3 and coded in the LS type field of the LSA. The
following three flooding scopes are available for LSAs:
Link-local scope: The LSA is not flooded beyond the local link.
Area scope: The LSA is flooded in a single OSPF area. Area scope is used in RouterLSAs, Network-LSAs, Inter-Area-Prefix-LSAs, Inter-Area-Router-LSAs, and Intra-AreaPrefix-LSAs.
AS scope: The LSA is flooded through the routing domain. AS scope is used for ASexternal-LSAs.
Multiple instances per link

OSPFv3 supports multiple OSPF protocol instances on a single link. For example, you can
configure a single link in two or more OSPF areas.
An Instance ID in the OSPF packet header and the OSPF interface structures allow multiple
protocol instances on a single link.
Link-local addresses
In IPv6, link-local addresses are used on a single link. Link-local addresses facilitate features
such as neighbor discovery and auto-configuration. Datagrams with link-local sources are not
forwarded. Instead, routers assign link-local unicast addresses from the IPv6 address range.
OSPF for IPv6 assigns link-local unicast addresses to physical segments attached to a router.
The source for all OSPF packets sent on OSPF physical interfaces is the associated link-
32
October 2010
OSPFv3
local unicast address. Routers learn link-local addresses for all other nodes on their links. The
learned addresses are included in next-hop information during packet forwarding.
For OSPF protocol packets, global scope or site-local IP addresses must be used as the source
for packets.
Link-LSA is the only OSPF LSA type that allows you to include link-local addresses. Linklocal addresses must not be advertised in other LSA types.
Authentication
OSPF for IPv6 requires the IP Authentication Header and the IP Encapsulating Security
Payload for authentication and security. OSPFv3 does not support the Authentication feature
from OSPFv2.
The IPv6 16-bit one's complement checksum protects against accidental data corruption.
Packet format
OSPFv3 runs directly over IPv6. All other addressing information is absent in OSPF packet
headers. OSPFv3 is essentially network-protocol-independent. LSA types now contain
addressing information.
OSPF packet changes:
Hello packets and database description packets operations fields are expanded to 24 bits.
Authentication and AuType fields are not included in the packet header.
The Interface ID replaces the address information in the Hello packet. The Interface ID
becomes the Network-LSA Link State ID if the router becomes the Designated Router on
the link.
R-bit and V6-bit in the options field process Router-LSAs during SPF calculation. R-bits
and V6-bits determine participation in topology distribution.
The packet header includes the Instance ID, which allows multiple OSPF protocol
instances on the same link.
New LSAs
OSPFv3 includes Link-LSAs and Intra-Area-Prefix.
October 2010
33
Link-LSA
Link-LSA has local-link flooding scope, not flooded beyond the associated link.
Link-LSAs have three purposes:
to provide the router's link-local address to all other nodes on the link
to provide the list of IPv6 prefixes associated with the link
to allow the router to associate options bits with the Network-LSA for the link
Intra-Area-Prefix-LSA
The Intra-Area-Prefix-LSA carries all IPv6 prefix information. In IPv4, this information is in
Router-LSAs and Network LSAs.
Unknown LSA types

In OSPFv3, unknown LSA types are either stored and flooded as though understood or given
local flooding scope. Specific behavior is coded in the LS type field of the header.
Stub area
OSPFv3 retains the concept of stub areas, which minimize link-state databases and routing
table sizes.
IPv6 stub areas carry only Router-LSAs, Network-LSAs, Inter-Area-Prefix-LSAs, Link-LSAs,
and Intra-Area-Prefix-LSAs.
Unlike IPv4, IPv6 allows LSAs with unrecognized LS types to be stored and flooded as though
understood. Rules applied to the stub area prevent the excessive growth of the link-state
database. An LSA with an unrecognized LS can be flooded only if the LSA has area or linklocal flooding scope, and the LSA U-bit is set to 0.
34
October 2010
Routing Information Protocol for IPv6 Networks (RIPng)
Routing Information Protocol for IPv6 Networks (RIPng)

Avaya Secure Router 2330/4134 implementation of RIP
RIP works well for small- to medium-sized networks, where the longest path is 15 hops. A node
connected directly to the router has a metric of zero; an unreachable node has a metric of 16.
When used as a provider edge (PE), the Avaya Secure Router 2330/4134 supports RIP on
access ports that interface with customer edge (CE) devices. To preserve the RIP hop count
across the core, the router adds one hop and then passes the hop count to the BGP multiexit discriminator (MED).
RIPv1 advertises addresses without subnet masking. RIPv2 advertises more explicitly, based
on the subnet mask. The Avaya Secure Router 2330/4134 supports RIPv2 with backwards
compatibility for RIPv1.
Routing Information Protocol

Routing Information Protocol for IPv6 Networks (RIPng) is built on the RIP foundation and
functions in the same capacity, with the key difference being support for IPv6 (128bit) prefixes.
In routed environments, routers communicate with one another to track available routes.
Routers can learn about available routes dynamically using the Routing Information Protocol
(RIP). The Avaya Secure Router 2330/4134 software implements standard RIP for exchanging
Transmission Control Protocol (TCP)/IP route information with other routers.
RIP uses broadcast User Datagram Protocol (UDP) data packets to exchange routing
information. By default, each router advertises routing information by sending a routing
information update every 30 seconds (one interval). If a router does not receive an update from
another router within 180 seconds (six intervals), it marks the routes served by the nonupdating
router as being unusable. If no update is received within an additonal 120 seconds (four
intervals), the router removes all routing table entries for the nonupdating router. All of these
intervals are user-configurable values.
RIP is known as a distance vector protocol. The vector is the network number and next hop,
and the distance is the cost associated with the network number. RIP identifies network
reachability based on cost, and cost is defined as hop count. One hop is considered to be the
distance from one router to the next. This cost or hop count is known as the metric (Figure 9:
Hop count or metric in RIP on page 36).
October 2010
35
Figure 9: Hop count or metric in RIP
RIP version 1 was distributed in the early years of the Internet and advertised default class
address without subnet masking. RIP version 2 advertises more explicitly, based on the subnet
mask.
The Avaya Secure Router 2330/4134 supports RIP version 2, which advertises routing table
updates using multicast instead of broadcasting. RIP version 2 supports variable length subnet
masks (VLSM) and triggered updates of routers. RIP version 2 sends mask information. If
information about a network is not received for 180 seconds, the metric associated with the
network rises to infinity (U)the metric resets to 16, which means the network becomes
unreachable. If information about a network is not received for an additional 120 seconds (four
update intervals), it is removed from the routing table. You can change the default timers by
using the 'timers basic' command at the 'router rip' command level.
A directly connected network has a metric of zero. An unreachable network has a metric of 16.
Therefore, the highest metric between any two networks can be 15 hops or 15 routers.
Border Gateway Protocol for IPv6 Networks (BGP4+)

Border Gateway Protocol for IPv6 Networks (BGP4+) is built on the BGP foundation and
functions in a very similar fashion, with the key difference being the support for IPv6 (128bit)
prefixes.
The Border Gateway Protocol (BGP) is routing protocol used for routing between Autonomous
Systems. The main purpose of the Border Gateway Protocol (BGP) is to exchange networklayer reachability information (NLRI) among IP routers in different autonomous systems, for
example, between ISPs. An autonomous system (AS) is a set of interconnected networks
36
October 2010
administered by a single authority, and with certain routing behaviors determined by common
routing policies.
Because BGP routes traffic between networks, it is also referred to as External BGP (EBGP)
as opposed to routing protocols like RIP and OSPF that route traffic within a network and are
referred to as Interior Gateway Protocols (IGP). BGP can also be used as an IGP (routing
within a single AS, and in this case is referred to as Interior BGP (IBGP).
The primary characteristics of BGP are its scalability and stability. For these reasons, BGP is
the routing protocol typically used by Internet Service Providers to route over the Internet.
A protocol that allows BGP to maximize the efficiency of routing tables is classless interdomain routing (CIDR). CIDR is used by BGP to reduce the size of the Internet routing tables.
CIDR allows BGP to manage blocks of IP address as single routing table entries.
BGP also maximizes routing efficiency by only exchanging full routing information when
connections are first established. Thereafter, only changes to routing tables are sent to
neighbors. Also BGP only advertises optimal routes.
Hierarchical mechanisms
A BGP network consists of BGP peers, peer groups, communities, and extended communities.
Multiple BGP neighbors can be assigned to a peer group. The peer group is internal if all of its
member peers reside within an AS. The peer group is external if all of its member peers reside
outside the AS. The peers within a peer group share the same configuration, including routing
policies. Any peer assigned to a peer group automatically inherits any configuration and
policies established for the peer group, but an administrator can override certain attributes of
this configuration at the individual peer level.
A BGP community is a collection of destinations larger than a BGP peer group. BGP identifies
members of a community by means of a community attribute inserted in the route to each
community destination. As with a BGP peer group, the BGP community can be an efficient
mechanism to identify a large number of routes to which an administrator can apply common
routing policies. The community attribute identifies the AS of origin and specific ID of the
community to which the route (or community destination) belongs.
BGP identifies members of an extended community by means of extended community
attributes. As with any BGP community, the BGP extended community is also an efficient
mechanism for identifying a set of routes to which an administrator can apply common routing
policies.
Policy-based routing
BGP uses import and export routing policies to control the types of routes advertised from the
routing table, or accepted into the routing table, respectively.
October 2010
37
Export policies allow BGP to advertise certain routes that match defined (default or configured)
criteria. Export policies also enable BGP to alter the properties of certain routes before
advertising them.
BGP import policies allow BGP to filter route updates received, and to assign properties to
accepted routes before installing them into the routing table. An administrator can create
routing policies to prefer, modify, or redistribute routes associated with a:
BGP peer
BGP peer group
BGP community
BGP extended community
Route redistribution
BGP can redistribute, to its domain, routes learned by other dynamic and static routing
protocols. BGP then advertises these routes to its external peers according to any export policy
configured. Note that connected routes and loopback addresses are not automatically
redistributed, but an administrator can use policies to export such routes.
BGP supports the redistribution of routing information from other routing protocols such as RIP,
OSPF, and static routes. BGP attributes of the routes can be altered by applying a routing
policy during redistribution.
Note that routes are redistributed only if they are in the forwarding table (that is, they are active
routes). The Avaya Secure Router 2330/4134 does not support extensions that allow BGP to
send out routes that are not active routes.
Security
BGP can authenticate peerings and routing protocol exchanges. Authentication guarantees
that BGP imports routing information from trusted peers only. An administrator can configure
a password for this purpose. By default, authentication security is disabled.
Route reflectors
Route Reflectors and Confederations are two different techniques used to solve the same
problem of full iBGP meshing.
BGP systems generally require full-mesh connectivity within an AS to facilitate redistribution
of external routes to all routers in the same AS. However, scaling issues can arise within an
AS that contains a significant number of BGP routers because they all exchange the same
information with each other, causing an unacceptable amount of BGP control traffic. To avoid
38
October 2010
this scenario, an administrator can configure Route Reflectors to decrease the BGP control
traffic inside the AS.
A Route Reflector is a cluster of BGP devices within an AS, with one system serving as a Route
Reflector server and other BGP systems serving as client peers. The server redistributes
intracluster routing information to its client peers. Outside the cluster, non-client peers receive
intercluster routing information from the server. Non-client peers may also be Route Reflectors.
Route flap dampening

A route is flapping when its state oscillates from available to unavailable to available
periodically. An available route resides in the router FIB, whereas an unavailable route has
been withdrawn from the router FIB. Every time a route flaps, BGP assigns to that route a
penalty that is cumulative. When the penalty reaches a certain limit (called the suppress limit),
BGP suppresses (stops advertising) the flapping route. However, as route availability
stabilizes, BGP also actively reduces the penalty value for that route by half, at a period defined
by a half-life attribute. Once the penalty value diminishes below a reuse threshold value, BGP
can resume advertising (reusing) the route.
When route flapping occurs, BGP systems generate too many route update messages, thereby
reducing the efficiency of peers in the network. By damping route flaps, BGP generates fewer
route updates, thereby helping to optimize BGP operation in peers and in the network.
Route refresh
When any import policies for the local BGP peer change, all of the routes advertised by a
remote peer must be re-evaluated against all existing (including new and modified) import
policies. One way to perform this operation is for the local peer, at great expense of available
resources, to:
Maintain a real-time database of all routes advertised by remote peers, at the expense of
local memory and CPU resources.
Reapply all import policies to the above routes.
Import into the BGP RIB-IN table only those routes accepted by the latest BGP import
policies on the local peer.
October 2010
39
Instead of the above approach, the route-refresh feature enables the local peer to:
Not maintain a real-time database of all routes advertised by remote peers, saving local
memory and CPU resources.
Request a remote peer to resend all of the routes currently in its RIB-OUT table. Upon
receiving the requested routes, the local peer can reapply all of its current import policies.
The RIB-OUT table contains the routes that the router announces to adjacent peers.
Import into the BGP RIB-IN table only those routes qualified by the latest local BGP import
policies on the local peer. The RIB-IN table contains the routes that the router learns from
adjacent peers.
A BGP speaker uses the BGP Capabilities Advertisement to advertise to peers at session
OPEN its ability to originate and correctly process route-refresh messages. By using the BGPCAP mechanism, the BGP speaker will send route-refresh messages only to peers that also
support the feature.
BGP planning considerations

An administrator can plan for the different stages of BGP configuration by obtaining certain
key information from the detailed network design plan. For the purpose of grouping related
configuration tasks, the stages of BGP configuration planning are:
BGP minimum configuration planning
BGP initial session customization planning
BGP update processing and advertisement configuration planning
BGP optimization planning
BGP minimum configuration planning

Before you begin BGP minimum configuration, determine the following from your network
design plan:
The AS number in which the local BGP peer resides.
The address families to be supported by the local BGP peer. (By default, BGP supports
the IPv4 address family, but can also support the IPv6 address family.)
The names of BGP groups you want to configure on this router.
For each BGP neighbor, its peer type (internal iBGP or external eBGP).
The number of any AS in which BGP peers reside.
The IP addresses of the local and remote BGP peers in each group. (By default, the
address of the local peer is its router-id.)
The names of any routing policies necessary to allow certain other BGP peers to connect
dynamically, or as needed, to the local peer.
40
October 2010
BGP initial session customization planning

Before customizing the behavior or sessions between the local and any remote BGP peers,
you should finish the minimum configuration of the Avaya Secure Router 2330/4134 local BGP
peer. The administrator should then additionally determine from the network design plan these
settings for each static or dynamic peer configured on the local BGP router:
BGP session OPEN type (active or passive)
BGP connection type (direct or multihop)
Authentication password
Session timer settings (default or customized)
BGP update processing and advertisement configuration planning

After BGP minimum configuration and initial session customization, you can customize how
the local peer must process received updates and outgoing advertisements. From the network
design plan, determine if the local BGP peer must:
Advertise the local router ID as nexthop (to all, group, or specific peers)
Advertise no aggregator ID in updates (to all, group, or specific peers)
Advertise MED values (to all, group, or specific peers)
Compare MED values in routes learned from eBGP peers
Remove a private AS number from routes
Replace the peer AS number with the local AS number in updates received from peers
Keep routes that contain the local AS number
Accept routes containing the local AS number n times
Allow default or set customized maximum routes and session teardown criteria for each
address family
BGP optimization planning

To help optimize BGP operations, determine from the network design plan if the local BGP
peer:
Is part of an AS confederation
Is part of a Route Reflector cluster
Is part of any specific communities or extended communities
Has requirements for customized import and export policies
October 2010
41
Should support damping for flapping routes

Should support the BGP Route Refresh capability
BGP multicast
With BGP Multicast (MBGP), BGP can connect multicast topologies within and outside an AS.
Routers implementing this feature carry two separate sets of routing information for unicast
and multicast routing. Multicast protocols such as PIM use this multicast routing information to
build multicast distribution trees.
Using MBGP, it is possible to direct all the multicast traffic to designated access points other
than normal unicast forwarding paths. Combined with the power of BGP policies, MBGP
provides more control over the way multicast traffic is carried inside as well as outside the AS.
MBGP supports most applicable unicast BGP CLI commands, with the exception that MBGP
routes are not redistributed to other protocols and BGP routes are not redistributed to MBGP.
To configure multicast BGP, specify the IPv6 multicast address family (using the addressfamily command) before configuring the desired BGP property (the default address family is
IPv4 unicast).
Protocol Independent Multicast-Sparse Mode

Protocol Independent Multicast-Sparse Mode (PIM-SM) supports multicast groups spread out
across large areas of a company or the Internet. Unlike dense mode protocols, such as
DVMRP, that initially flood multicast traffic to all routers over an entire internetwork, PIM-SM
sends multicast traffic only to routers that have specifically joined a multicast group. This
technique reduces traffic flow over WAN links and overhead costs for processing unwanted
multicast packets.
Dense-mode protocols use a flood-and-prune technique, which is efficient where receivers are
densely populated. However, for sparsely populated networks, PIM-SM is more efficient
because it sends multicast traffic only to those routers that belong to a specific multicast group
and that choose to receive the traffic.
PIM-SM is independent of any specific unicast routing protocol, but it does require the presence
of a unicast routing protocol, such as RIP or OSPF. PIM-SM uses the information from the
unicast routing table to create and maintain multicast trees that enable PIM-enabled routers
to communicate.
42
October 2010
PIM-SM concepts and terminology

Typically, a PIM-SM network consists of several multipoint data streams, each targeted to a
small number of LANs in the internetwork. For example, customers whose networks consist
of multiple hosts on different LANs can use PIM-SM to simultaneously access a video data
stream, such as a video teleconference, on a different subnet.
Important:
In some cases, PIM stream initialization can take several seconds.
Hosts
A host can be a source, a receiver, or both.
A source, also known as a sender, sends multicast data to a multicast group.
A receiver receives multicast data from one or several sources that sends data to a
multicast group.
PIM-SM domain
PIM-SM operates in a domain of contiguous routers that have PIM-SM enabled. All these
routers are configured to operate within a common boundary defined by PIM Multicast Border
Routers (PMBRs).
Each PIM-SM domain requires the following routers:
Designated router (DR)
Rendezvous-point (RP) router
Bootstrap router (BSR)
Although a PIM-SM domain can have only one active RP router and one active BSR, you can
configure additional routers as candidate RP routers and as candidate BSRs. Candidate
routers provide backup protection in case the primary RP or BSR router fails.
October 2010
43
Designated router
The designated router (DR) is the router with the highest IP address on a LAN designated to
perform the following tasks:
sends register messages to the rendezvous-point (RP) router on behalf of directly
connected sources
sends join/prune messages to the RP router on behalf of directly connected receivers
maintains information about the status of the active RP router for local sources in each
multicast group
Important:
The DR is not a required configuration, and switches act automatically as such for directly
attached sources and receivers.
Rendezvous-Point router
PIM-SM builds a shared multicast distribution tree within each domain, and the rendezvous
point (RP) router is at the root of this shared tree. Although the RP can be physically located
anywhere on the network, it must be as close to the source as possible. There is only one
active RP router for a multicast group.
At the RP router, receivers meet new sources. Sources use the RP to identify themselves to
other routers on the network; receivers use the RP to learn about new sources.
The RP performs the following tasks:
registers a source that wants to announce itself and send data to group members
joins a receiver that wants to receive data for the group
forwards data to group
Candidate rendezvous-point router

You can configure a set of routers as candidate rendezvous-point (C-RP) routers that serve
as backup to the RP router. If an RP fails, all the routers in the domain apply the same algorithm
to elect a new RP from the group of C-RPs. To make sure that the routers have a complete
list of C-RPs, the C-RP periodically sends unicast advertisement messages to the bootstrap
router (BSR). The most common implementation is to configure a PIM-SM router as both a
candidate RP and a candidate BSR.
Important:
Although you can configure a candidate RP on a DVMRP interface, no functionality is tied
to this configuration.
Static rendezvous point router

You can configure a static entry for a rendezvous point (RP) with static RP. This feature avoids
the process of selecting an active RP from the list of candidate RPs and dynamically learning
44
October 2010
about RPs through the BSR mechanism. Static RP-enabled switches cannot learn about RPs
through the BSR because the switch loses all dynamically-learned BSR information and
ignores BSR messages. When you configure static RP entries, the switch adds them to the
RP-set as if they were learned through the BSR.
Important:
In a PIM domain with both static and dynamic RP switches, the static RP switches cannot
have one of their (local) interfaces configured as RP.
While configuring a PIM static RP in a switch, consider that the next-hop of the unicast route
towards PIM static RP must be a PIM neighbor. The PIM protocol fails to work if due to a route
change the next-hop towards an already configured static RP becomes a non-PIM neighbor.
The configured RP does not activate until it can be reached through a PIM neighbor, and its
state remains invalid.
Static RP-enabled Avaya Secure Router 2330/4134 can communicate with switches from other
vendors that do not use the BSR mechanism. Some vendors use either early implementations
of PIM-SM v1 that do not support the BSR or proprietary mechanisms like the Cisco AutoRP. For a network to work properly with static RP, you must have all the switches in the network
(including switches from other vendors) map to the same RP or RPs, if several RPs are present
in the network.
To avoid a single point of failure, you can also configure redundant static RPs.
You use the static RP feature when dynamic learning mode is not needed, typically in small
networks or for security reasons, where RPs have to be forced to some devices in the network
so that they do not learn other RPs.
Static RP configuration considerations

Before you can configure a static RP, you must enable PIM in sparse mode (SM) and enable
Static RP.
After meeting these prerequisites, keep in mind the following configuration considerations:
A static RP-enabled switch cannot be configured as a BSR or as a C-RP.
All dynamically learned BSR information is lost. However, if you disable static RP, the
switch loses the static RP information and regains the BSR functionality.
Static RPs do not age, that is, they cannot time out.
Switches do not advertise static RPs, so, if a new PIM neighbor joins the network, it does
not know about the static RP unless it is configured with that static RP.
Configure all the switches in the network (including switches from other vendors) to map to
the same RP.
In a PIM domain with both static and dynamic RP switches, the static RP switches cannot
have one of their (local) interfaces configured as RP.
To avoid a single point of failure, you can configure redundant static RPs for the same
group prefix. If there is a mix of Avaya and other vendor's switches across the network,
you must ensure that all switches/routers use the same active RP because other vendors
can be using different algorithms to elect the active RP. Avaya Secure Router 2330/4134
October 2010
45
devices use the hash function defined in the PIM-SM standard to elect the active RP;
other vendors can use the lowest IP address to break the tie.
Important:
To reduce convergence times, Avaya recommends you create only one static RP per
group. The more static RPs you configure for redundancy, the more time PIM requires
to rebuild the mroute table and associate RPs.
Static RP configured on the switch is assumed to be alive as long as the switch has a
unicast route to the static RP's network. If the switch loses this route, the static RP is
invalidated and the hash algorithm is invoked to remap all affected groups. If the switch
regains this route, the static RP is validated and the hash algorithm is invoked to remap
the affected groups.
Bootstrap router
The BSR receives RP router advertisement messages from the candidate RPs. The BSR adds
the RP router with its group prefix to the RP set. Only one BSR exists for each PIM-SM domain.
The BSR periodically sends bootstrap messages containing the complete RP set to all routers
in the domain. The BSR ensures that all PIM-SM routers send join/prune and register packets.
Candidate bootstrap router
Within a PIM-SM domain, you can configure a small set of routers as candidate BSRs (CBSRs). The candidate BSR with the highest configured priority becomes the BSR for the
domain. If two candidate BSRs have equal priority, the candidate with the higher IP address
becomes the BSR. If you add a new candidate BSR with a higher priority to the domain, it
automatically becomes the new BSR.
Join/prune messages
The DR sends join/prune messages from a receiver toward a RP for the group to either join
the shared tree or remove (prune) a branch from it. A single message contains both a join
and a prune list. This list includes a set of source addresses indicating the shortest-path trees or
the shared trees that the host wants to join. The DR sends join and prune messages hop by
hop to each PIM router on the path to the source or the RP.
Register and register-stop messages

The DR sends register messages to the RP for a directly connected source. The register
message informs the RP of a new source, causing the RP to send join or prune messages
back toward the DR of the source which forwards the data down the RP tree after it gets the
data natively. When the receiver DR gets the first packet, it switches to the shortest-path tree
(SPT) and continues receiving data through the SPT path.
46
October 2010
The DR stops sending encapsulated packets to the RP after receiving a register-stop message.
This traffic stops without delay because the RP sends a register-stop message immediately
after receiving the first multicast data packet, and joins the shortest-path tree.
Shared trees and shortest-path trees

In a PIM-SM domain, shared trees and shortest-path trees are used to deliver data packets to
group members. This section describes both trees.
Shared trees
Group members in a PIM-SM domain receive the first packet of data from sources across a
shared tree. A shared tree consists of a set of paths that connect all members of a multicast
group to the RP. PIM creates a shared tree when sources and receivers send messages toward
the RP.
Shortest-path trees
After receiving a certain number of packets from the RP, the DR switches from a shared tree
to a shortest-path tree (SPT). Switching to a shortest-path tree creates a direct route between
the receiver and the source. The Avaya Secure Router 2330/4134 switches to the SPT when it
receives the first packet from the RP.
Figure 10: Shared tree and shortest-path tree on page 48 shows a shared tree and a shortestpath tree.
October 2010
47
Figure 10: Shared tree and shortest-path tree
Receiver joining group

The following steps describe how a receiver joins a multicast group:
1. A receiver multicasts an IGMP host membership message to the group that it wants
to join.
2. When the last-hop router (DR), normally the PIM router with the highest IP address
for that VLAN , receives the IGMP message for a new group join, the router looks
up the associated elected RP that is responsible for the group.
3. After it determines the RP router for the group, the last-hop router creates a (*,G)
route entry in the multicast forwarding table and sends a (*,G) Join message to the
RP. When the last-hop router receives data packets from the RP, if the multicast
packet arrival rate exceeds the DR threshold, the last-hop router switches to the
48
October 2010
SPT by sending an (S,G) Join message to the source. (S denotes the source unicast
IP address, and G denotes the multicast Group Address.)
4. If the switch to the SPT occurs:
All intermediate PIM routers along the path to the source create the (S,G) entry.
To trim the shared tree, the router sends an (S,G) Prune message to the RP.
Receiver leaving group

Before it leaves a multicast group, a receiver sends an IGMP leave message to the DR. If all
directly connected members of a multicast group leave or time out, and no downstream
members remain, the DR sends a prune message upstream and PIM-SM deletes the route
entry after that entry times out.
Source sending packets to group

The following steps describe how a source sends multicast packets to a group:
1. A source directly attached to a VLAN bridges the multicast data to the DR. The DR
for the VLAN (the router with the highest IP address) encapsulates each packet in
a register message and sends a unicast message directly to the RP router to
distribute to the multicast group.
2. If a downstream group member chooses to receive multicast traffic, the RP router
sends a join/prune message towards the source DR and forwards the data down
the RP tree after it gets the data natively.
3. When the receiver DR gets the first packet, it switches to the shortest-path tree
(SPT) and continues receiving data through the SPT path.
4. If no downstream members want to receive multicast traffic, the RP router sends a
register-stop message (for the source) to the DR.
The DR starts the register suppression timer when it receives the first registerstop message. During the register suppression timeout period (the default is 60
seconds), the following events occur:
The DR for the source sends a probe packet to the RP router before the register
suppression timer expires. The probe packet prompts the RP router to
determine whether any new downstream receivers have joined the group.
If no new receivers have joined the group, the RP router sends another
register-stop message to the DR for the source, and its register suppression
timer restarts.
When the RP router no longer responds with a register-stop message to the
source DR probe message, the register suppression timer expires and the DR
October 2010
49
sends encapsulated multicast packets to the RP router. The RP router uses

this method to tell the DR that new members have joined the group.
The RP sends a register-stop message to the DR immediately after receiving the first multicast
data packet.
Required elements for PIM-SM operation

For PIM-SM to operate, a number of elements must be present in the PIM-SM domain including
the following:
An underlying unicast routing protocol must be enabled for the switch to provide routing
table information to PIM-SM.
In a PIM-SM domain, an active BSR must be in place to send bootstrap messages to all
PIM-V2 configured switches and routers to enable them to learn group-to-RP mapping.
If several BSRs are configured in a network, an active BSR is elected based on priority
and IP address (if priority is equal, the BSR with the higher IP address is elected).
An RP must be in place in the PIM-SM domain to perform the following tasks:
- To manage one or several IP Multicast groups.
- To become the root for the shared tree to these groups.
- To accept join messages from receiver switches for groups that it manages.
- If more than one RP that have groups in common, the RPs elect an active RP based
on priority and IP address (if priority is equal, the RP with the higher IP address is
elected).
PIM-SM simplified example

Figure 11: PIM-SM simplified example on page 51 shows a simplified example of a PIMSM configuration.
50
October 2010
Figure 11: PIM-SM simplified example
In the sample configuration, the following events occur:

1. The BSR distributes RP information to all switches in the network.
2. R sends an IGMP membership report to S4.
3. Acting on this report, S4 sends a (*,G) join message to RP.
4. S sends data to G.
5. The DR (S1 in this example) encapsulates the data that it unicasts to RP (S2) in
register messages.
6. S2 decapsulates the data which it forwards to S4.
7. S4 forwards the data to R.
8. If the packet rate exceeds the DR threshold, S4 sends S1 an (S,G) Join message.
9. S1 forwards data to S4. When S4 receives data from S1, it prunes the stream from
the RP.
Important:
Figure 11: PIM-SM simplified example on page 51 is a simplified example and is
not the best design for a network if the source and receiver are placed as shown.
In general, RPs are placed as close as possible to sources.
PIM-SM static source groups

You can configure static source groups (or static mroutes) as static source-group entries in the
PIM-SM multicast routing table. PIM-SM cannot prune these entries from the distribution tree.
For more information about static source groups, see Static source groups on page 52.
October 2010
51
Static source groups

Static source groups (or static mroutes) enable you to configure static source-group entries in
the PIM-SM or PIM-SSM multicast routing table. PIM cannot prune these entries from the
distribution tree. In other words, even if there are no receivers for the group, the multicast
stream for a static source-group entry stays active. Static forwarding entries are never pruned.
When they are no longer needed, you manually delete them.
To configure static source groups, you must first globally enable PIM. If you disable PIM, the
switch saves all of the configured static source-group entries and deactivates them. When you
reenable PIM, the switch reactivates the static source groups.
Static source groups ensure that the multicast route (mroute) records remain in the distribution
tree. When receivers join the group, there is no delay in receiving multicast data because there
is no need to graft onto the group or start a join process in the case of PIM. This is essential
for applications where the multicast data must be sent to a receiver as soon as the receiver
joins the group, for example, when a switch delivers TV channels to receivers. When the
receiver turns the channel, which is equivalent to joining a group, the receiver is able to view
the channel immediately.
Static entries result in continuous traffic if the source is active, even when no receivers are
present. However, traffic is not forwarded by an Avaya Secure Router 2330/4134 with static
entry if there are no receivers, but is forwarded continuously to the switch where the entry is
programmed and crosses intermediate switches on the path.
Static source-group entries can be configured for a specific source or subnet. If several sources
on the same subnet send traffic to the same group, traffic for all these sources flows
continuously when using the subnet configuration.
PIM-SM Multipath
In IPv6 Multicast Multipath, the reverse-path forwarding (RPF) interface for each (*, G) or (S,
G) state is selected among the available equal cost paths depending on the RPF address to
which the state resolves. For an (S, G) state, this is the address S of the source. For a (*, G)
state, this is the address of the RP associated with the group G of the state. As a result,
multicast traffic for different states can be received across more than just one equal-cost
interface.
PIM-SM supports the multipath functionality. The multipath functionality comprises two
methods for selecting the nexthop if multiple ECMP routes exist:
Round - Robin
Hashing
52
October 2010
Anycast RP for PIM-SM
The first method selects the nexthop in round-robin manner, while the latter selects the nexthop
based on the key calculated using source address, group address and nexthop address.
Anycast RP for PIM-SM

Anycast RP is a method of allowing the mapping of a single group to multiple RPs. In Anycast
RP, you can configure two or more RPs with the same IPv6 address on loopback interfaces.
Configure the Anycast RP loopback address as a host address. Configure all the downstream
routers to "know" that the Anycast RP loopback address is the IPV6 address of their local RP.
IPV6 routing automatically selects the topologically closest RP for each source and receiver.
Static Multicast Routing Support

Multicast static routes are unicast routes which allow multicast and unicast topologies to be
incongruous. Multicast routing protocols use these routes to perform reverse-path forwarding
(RPF) checks.
PIM-SSM
Source Specific Multicast (SSM) optimizes PIM-SM by simplifying the many-to-many model.
Since most multicast applications distribute content to a group in one direction, SSM uses a
one-to-many model that only uses a subset of the PIM-SM features. This model is more efficient
and puts less of a load on multicast routing devices.
SSM only builds source-based shortest path trees. Whereas PIM-SM always joins a shared
tree first and then switches to the source tree, SSM eliminates the need for starting with a
shared tree by immediately joining a source through the shortest path tree. This method
enables SSM to avoid using a rendezvous point (RP) and RP-based shared trees, which can be
a potential bottleneck.
Members of a SSM group can only receive from a single source. This is ideal for applications
like TV channel distribution and other content-distribution businesses. Banking and trade
applications can also use SSM because it provides more control over the hosts receiving and
sending data over their networks.
SSM features
SSM only uses a subset of the PIM-SM features such as the shortest path tree, designated
router (DR), and some messages (Hello, Join/Prune, and Assert). However, there are also
October 2010
53
some features that are unique to SSM. These features, which are described in the following
sections, are extensions of the IGMP and PIM protocols.
PIM requires a unicast protocol in order to forward multicast traffic within the network when
performing the Reverse Path Forwarding (RFP) check. PIM-SM uses the information from the
unicast routing table to create and maintain the shared and shortest multicast tree that enables
PIM-enabled routers to communicate. The unicast routing table must contain a route to every
multicast source in the network as well as to routes to PIM entities like the RPs and BSR.
PIM-SSM architecture
Figure 12: PIM-SSM architecture on page 55 illustrates how the PIM-SSM architecture
requires routers to:
support IGMPv3 source-specific host membership reports and queries at the edge routers
initiate PIM-SSM (S,G) joins directly and immediately after receiving an IGMPv3 join
report from the designated router
restrict forwarding to shortest-path trees within the SSM address range by all PIM-SSM
routers
54
October 2010
PIM-SSM
Figure 12: PIM-SSM architecture
The following rules apply to layer 3 devices with SSM enabled:

Receive IGMPv3 membership join reports in the SSM range and, if there is no entry (S,G)
in the SSM channel table, creates one.
Receive IGMPv2 membership join reports, but only for groups that already have a static
(S,G) entry in the SSM channel table.
Send periodic join messages to maintain a steady SSM tree state.
Use standard PIM-SM SPT procedures for unicast routing changes, but ignore any rules
associated with the SPT-bit for the (S,G) route entry.
Receive prune messages and use standard PIM-SM procedures to remove interfaces
from the source tree.
Forward data packets to interfaces from the downstream neighbors that have sent an
SSM join, or to interfaces with locally attached SSM group members.
Drop data packets that do not have an exact-match lookup (S,G) in their forwarding
database for S and G.
October 2010
55
Avaya Secure Router 2330/4134 implementation of SSM and IGMP

The following sections describe how PIM-SSM and IGMP are implemented in the Avaya
Secure Router 2330/4134.
SSM range
The standard SSM range is 232/8, but you can extend the range to include any IP Multicast
address with the Avaya Secure Router 2330/4134 implementation of SSM. Although you can
configure the SSM range, configuring it for all multicast groups is not allowed.
You can extend the SSM range to configure existing applications without changing their group
configurations. This flexibility allows applications to take immediate advantage of SSM.
SSM channel table

The SSM channel table gives you the flexibility to manually configure S,G entries that map
existing groups to their sending source. These table entries apply to the whole switch, not per
interface, and both IGMPv2 and IGMPv3 hosts use the SSM channel table.
The following rules apply to a SSM channel table for an individual switch:
You can map one source to multiple groups.
You can map one group to one source only; that is, you cannot map the same group more
than once in a given table.
Important:
Different switches can have different mappings for groups to sources, for example, different
channels may be mapped differently even if they are on the same network.
56
October 2010
PIM-SSM
SSM and IGMPv2

SSM-configured switches can accept reports from IGMPv2 hosts on IGMPv2 interfaces if the
group has a SSM channel table entry. However, the IGMPv2 host groups must be in the SSM
range defined on the switch, which is 232/8 by default.
When the SSM switch receives an IGMPv2 report for a group that is in the SSM channel
table, it joins the specified source immediately.
When the SSM switch receives an IGMPv2 report for a group that has an enabled static
SSM channel table entry, it triggers PIM-SSM processing as if it had received an
equivalent IGMPv3 report.
When the SSM switch receives an IGMPv2 report for a group out of the SSM range, it
processes the report as if it is in PIM-SM mode.
SSM and IGMPv3

The Avaya Secure Router 2330/4134 supports IGMPv3 for SSM. IGMPv3 enables a host to
selectively request or filter traffic from sources within the multicast group. IGMPv3 is an
interface-level configuration.
Important:
IGMPv3 works only with PIM-SSM or SSM snoop enabled on the interface.
The following rules apply to IGMPv3-enabled interfaces:
Send only IGMPv3 (source-specific) reports for addresses in the SSM range.
Accept IGMPv3 reports.
Drop IGMPv2 reports.
Note that the IGMPv2 report mentioned in SSM and IGMPv2 on page 57 is processed
because it is an IGMPv2 report that is received on an IGMPv2 interface. If it is an IGMPv3
report received on an IGMPv2 interface, it is dropped even if PIM-SSM is enabled and
the entry is in the SSM channel table. The rule is that the IGMP version must match first.
Discard any IGMP packets with a group address out of the SSM range.
The Avaya Secure Router 2330/4134 implements IGMPv3 in one of two modes: dynamic and
static.
In dynamic mode, the switch learns about new (S,G) pairs from IGMPv3 reports and adds
them to the SSM channel table. If dynamic mode is not enabled and an IGMPv3enabled interface receives a report that includes a group not listed in the SSM channel
table, it ignores the report.
In static mode, you can statically configure (Source, Group) entries in the SSM channel
table. If an IGMPv3-enabled interface receives a report that includes a group not listed in
October 2010
57
the SSM channel table, it ignores the report. It also ignores the report if the group is in
the table, but the source/mask does not match what is in the table.
Important:
When IGMPv3 is enabled, changes to the query interval and robustness values on the
querier switch are propagated to other switches on the same VLAN through IGMP query.
Both IGMPv2 and IGMPv3 hosts use the SSM channel table:
An IGMPv2 host (with an IGMPv2 VLAN) must have an existing SSM channel entry if the
group is in SSM range.
An IGMPv3 host has dynamic learning that is enabled, the SSM channel automatically
learns the group. Otherwise, the SSM channel also needs a static entry.
Table 5: Summary of how PIM-SSM interacts with IGMPv2 and v3 on page 58 summarizes
how a switch in PIM-SSM mode works with IGMP. References to any matching static SSM
channel entry assumes that the entry is enabled. If an entry is disabled, it is treated the same as
if it is disallowed.
Table 5: Summary of how PIM-SSM interacts with IGMPv2 and v3
Host
58
VLAN
SSM Range
Action
IGMPv2 host
IGMPv3 VLAN
In or Out of
range
Drop report.
IGMPv3 host
IGMPv2 VLAN
In or Out of
range
Drop report.
IGMPv2 host
IGMPv2 VLAN
In SSM range
If the report matches an existing

static SSM channel entry, create
(S,G).
If the report does not match any
existing static SSM channel entry,
drop it.
IGMPv2 host
IGMPv2 VLAN
Out of SSM
range
Ignore the SSM channel table and

process the report as if it is in PIMSM mode.
IGMPv3 host
IGMPv3 VLAN
Out of SSM
range
Drop report.
IGMPv3 host
IGMPv3 VLAN
In SSM range
Dynamic enabled. Create (S,G).
IGMPv3 host
IGMPv3 VLAN
In SSM range
Dynamic disabled and matches an

existing SSM channel entry. Create
(S,G).
IGMPv3 host
IGMPv3 VLAN
In SSM range
Dynamic disabled and does not

match an existing SSM channel
entry. Drop it.
October 2010
Multicast link discovery
When an IGMPv3 group report enters the VLAN port and one or more of the groups in that
packet needs to be discarded after the IGMP access controls are applied, the entire packet is
dropped and is not forwarded on to any other ports of the VLAN.
When an IGMPv3 interface receives an IGMPv2 or v1 query, the interface backs down to
IGMPv2 or v1. As a result, all senders and receivers on this interface are flushed.
PIM-SSM static source groups

You can configure static source group entries in the PIM-SSM multicast routing table with static
source groups (or static mroutes). PIM-SSM cannot prune these entries from the distribution
tree. For more information about static source groups, see Static source groups on page 52.
Configuration limitations
Avaya recommends running PIM-SSM on either all the switches in the domain or only on the
edge routers. If there is a mix of PIM-SSM and PIM-SM switches in the domain, run PIMSSM on all the edge routers and PIM-SM on all the core routers.
Important:
A PIM domain with edge routers running PIM-SM and core routers running PIM-SSM does
not work properly.
Avaya does not support SSM interoperability with DVMRP. However, the MBR functionality
works properly for non-SSM groups because SSM-enabled interfaces use PIM-SM behavior
for groups outside the SSM range.
SSM switches running IGMPv3 drop any reports that they receive out of the SSM range. The
SSM switch does not forward them to a PIM-SM switch.
Static source groups cannot conflict with SSM channels and vice versa. When you configure
a static source group or a SSM channel, the switch performs a consistency check to make sure
there are no conflicts. You cannot map one group (G) to different sources for both a static
source group and a SSM channel.
Multicast link discovery

Multicast link discovery (MLD) allows IPv6 routers to discover:
the presence of multicast listeners on directly attached links
multicast addresses required by neighboring nodes.
MLD is an asymmetric protocol. It specifies separate behaviors for multicast address listeners
(that is, hosts or routers that listen to multicast packets) and multicast routers. Each multicast
October 2010
59
router learns, for each directly attached link, which multicast addresses and which sources
have listeners on that link. The information that MLD gathers is provided to the multicast routing
protocols that the router uses. This ensures that multicast packets are delivered to all links
where listeners require such packets.
A multicast router can itself be a listener of one or more multicast addresses. That is, perform
both the multicast router part and the multicast address listener part of the protocol. The router
collects the multicast listener information needed by its multicast routing protocol and informs
itself and other neighboring multicast routers of its listening state.
MLD versions 1 and 2

The purpose of the MLD protocol in the IPv6 multicast architecture is to allow an IPv6 router
to discover the presence of multicast listeners on directly attached links, and to discover which
multicast addresses are of interest to those neighboring nodes. MLD is the direct IPv6
replacement for the IGMP protocol used in IPv4. The MLD implementation described in this
document is based on the MLDv2 standard, which is a backward-compatible update to the
MLDv1 standard.
IPv6 Routing over VLAN

With Release 10.2 and later, you can enable IPv6 unicast and multicast routing on VLAN
interfaces.
60
October 2010
Chapter 3: IPv6 routing procedures

This section describes how to use the command line interface (CLI) to perform basic IPv6 connectivity
configuration.
Enabling unicast routing globally

This procedure describes the process used to enable IPv6 unicast forwarding. Use the no form
of this command to disable.
Procedure steps
1. Enter Configuration mode.
configure terminal
2. Enable IPv6 unicast forwarding.
[no] ipv6 unicast-routing
Enabling multicast routing globally

This procedure describes the process used to enable IPv6 multicast routing. Use the no form of
this command to disable.
Procedure steps
configure terminal
2. Enable IPv6 multicast routing.
[no] ipv6 multicast-routing
Enabling IPv6 on an Ethernet interface

The following procedure describes how to enable IPv6 on an Ethernet interface. Use the no
form of this command to disable.
October 2010
61
IPv6 routing procedures
Procedure steps
configure terminal
2. Enter Interface mode.
interface <interface>
3. Enable IPv6 on the interface.
[no] ipv6 enable
Enabling IPv6 on a bundle

The following procedure describes how to enable IPv6 on a bundle. Use the no form of this
command to disable.
Procedure steps
configure terminal
2. Create a bundle.
interface bundle <bundle>
3. Enable IPv6 on the bundle
[no] ipv6 enable
Configuring the IPv6 address for an interface

Use this command to configure the IPv6 address for an interface.
Procedure steps
configure terminal
3. Configure the IPv6 address.
ipv6 address {<X:X::X:X/M> [eui-64 | anycast] | <prefixname> [<X:X::X:X/M>] }
62
October 2010
Configuring Neighbor Discovery parameters
Table 6: Variable definitions

Variable
Value
<X:X::X:X/M>
IPv6 prefix address.
<prefix-name>
Prefix name to be referred to assign IPv6

address to this interface
[<X:X::X:X/M>]
Subnet prefix number to be ORed with NW

prefix referred by gen_prefix_name
Configuring Neighbor Discovery parameters

Use this command to configure Neighbor Discovery (ND) parameters.
Procedure steps
configure terminal
3. Configure Neighbor Discovery (ND) parameters.
[no] ipv6 nd { dad-attempts <dad-attempts> | managed-configflag | ns-interval <ns-interval> | other-config-flag | rainterval <ra-interval> | ra-interval-min <ra-interval-min> |
ra-lifetime <ra-lifetime> | reachable-time <nd-reachabletime>| suppress-ra }
Variable
Value
dad-attempts <dad-attempts>
Number of NS to be sent to validate DUP

status (0-600). Use 0 to disable DAD on this
interface. (default: 1)
managed-config-flag
Enable MANAGED bit on the RAs sent on

this interface.
ns-interval <ns-interval>
Configure the interval in milliseconds

between IPv6 NS retransmission on an
interface (1000 - 3600000). Default is 1000.
other-config-flag
Enable OTHER bit on the RAs sent on this

interface.
October 2010
63
ra-interval <ra-interval>
Configure maximum interval between router

advertisements in seconds (4 - 1800).
ra-interval-min <ra-interval-min>
Configure minimum interval between router

advertisements in seconds (1 - 600).
ra-lifetime <ra-lifetime>
Router lifetime value in seconds (0-9000).
reachable-time <nd-reachable-time>
NS Reachability time in milliseconds (0 3600000; default: 30000).
suppress-ra
Suppress the transmission of RA on this

interface. Use the no parameter to enable it
again.
Configuring IPv6 redirects

Use this command to allow the interface to send ICMP redirect messages when a better route
exists for a destination IP address.
Procedure steps
configure terminal
3. Configure redirects.
ipv6 redirects
Configuring an IPv6 general-prefix

Use this command to configure a general prefix name with an NW prefix.
Procedure steps
configure terminal
2. Configure the general prefix.
ipv6 general-prefix <prefix-name> <NW-name>
64
October 2010
Configuring the IPv6 hop-limit

Variable
Value
<prefix-name>
Prefix name
<NW-name>
NW prefix in the format: xxxx:yyyy::/

prefix_len
Configuring the IPv6 hop-limit

Use this command to configure the hop-limit for outgoing IPv6 packets.
Procedure steps
configure terminal
2. Configure the hop-limit.
ipv6 hop-limit <hop-limit>
Variable
<hop-limit>
Value
Hop limit on outgoing IPv6 packets, in the
range 1 - 255.
Configuring IPv6 icmp rate limit

Use this command to configure ICMPv6 rate limit.
Procedure steps
configure terminal
2. Configure the ICMP rate limit.
ipv6 icmp rate-limit <rate-limit>
October 2010
65

Variable
<rate-limit>
Value
Specifies the time interval for sending ICMP
messages in milliseconds (default : 500ms,
0 disables rate limit). Acceptable values are
in the range: 0 - 1000000
Configuring IPv6 load balancing

Use this command to specify load balancing policy for equal cost routes (default = per flow).
Procedure steps
configure terminal
2. Configure load balancing.
ipv6 load-balancing policy { per-flow | per-packet }
Variable
Value
per-flow
per IP destination load balancing
per-packet
round robin load balancing
Configuring an IPv6 neighbor

Use this command to configure a static entry in IPv6 ND Cache.
Procedure steps
configure terminal
2. Configure the neighbor.
ipv6 neighbor <neighbor-ip> <neighbor-mac> <interface_name>
66
October 2010
Configuring IPv6 next-hop address

Variable
Value
<neighbor-ip>
Neighbor's IPv6 address.
<neighbor-mac>
Neighbor's MAC address in

HH:HH:HH:HH:HH:HH format.
<interface_name>
Interface on which this neighbor entry has to

be added, for example: ethernet0/2. This
parameter is required for link-local
neighbors.
Configuring IPv6 next-hop address

Use this command to set a next hop-address. Use the no parameter with this command to
delete an entry.
Procedure steps
configure terminal
2. Configure the next-hop address.
[no] set ipv6 next-hop [local] <X:X::X:X>
Variable
Value
local
Specifies that the address is local. (If not

specified, the address is considered global.)
<X:X::X:X>
Specifies the IPv6 address if the next hop.
Establishing static routes

The following procedure describes how to establish a static route. Use the no form of this
command to delete the route.
Procedure steps
October 2010
67
configure terminal
2. Specify the IPv6 destination.
[no] ipv6 route <X:X::X:X/M> <gatewayip|interface>
[<distvalue>]
Table 14: Variable definition
Variable
Value
<distvalue>
The distance value for the prefix in the 1 to 255.
<gatewayip>
The IPv6 gateway address.
<interface>
The IPv6 gateway interface name.
<X:X::X:X/M>
The IP destination prefix.
Configuring a multicast static route

Use this procedure to configure a multicast static route. By default no multicast static routes
are configured.
Procedure steps
1. To enter the Configuration mode, enter:
configure terminal
2. To configure a multicast static route, enter:
[no] ipv6 mroute <source-address/mask> [<protocol>] [<RPFaddr>| <if-name>] [<distance>]
Variable
Value
[no]
Removes the configured multicast static

route.
<source-address/mask>
Specifies the multicast source IPv6 address

(X:X::X:X) and address mask length (0-128).
[<protocol>]
Specifies the unicast routing protocol:

bgp: BGP
isis: IS IS
ospf: OSPF
68
October 2010
Configuring multicast lookup in MRIB only
Variable
Value
rip: RIP
static
[<RPF-addr>]
Specifies the RPF address (X:X::X:X) for the

multicast route. The host IPV6 address can
be a directly connected system or a remote
system. When it is a remote system, a
recursive lookup is done from the unicast
routing table to find a directly connected
system; the recursive lookup is done up to
only one level.
<if-name>
Specifies the incoming interface name. You

can specify the interface for non-broadcast
interfaces only.
[<distance>]
Specifies a distance for the multicast route,

which determines whether a unicast route or
multicast static route is used for the RPF
lookup. Lower distances take precedence. If
the multicast static route has the same
distance as other RPF sources, the multicast
static route takes precedence. Default is 0.
Range is 0-255.
Configuring multicast lookup in MRIB only

Use this procedure to configure the router to perform IPv6 multicast lookups in the MRIB only. If
you do not enable this feature, the device does a multicast route lookup in the URIB as well
as in the MRIB. By default, this feature is disabled.
Procedure steps
1. To enter Configuration mode, enter:
configure terminal
2. To configure the multicast lookup in MRIB only feature, enter:
[no] ipv6 multicast-lookup-mrib-only
Variable
[no]
Value
Disables the multicast lookup in MRIB only
feature.
October 2010
69
Clearing multicast static routes

Use this procedure to clear configured IPv6 multicast static routes. When you perform this
procedure, the MRIB clears the multicast route entries in its IPv6 multicast route table, and
removes the entries from the multicast forwarder. The MRIB sends a clear message to the
multicast protocols. Each multicast protocol has its own clear multicast route command. The
protocol-specific clear command clears multicast routes from the protocol, and also clears the
routes from the MRIB.
Procedure steps
To clear multicast static routes, enter:
clear {all ipv6 mroutes | <group-addr> [<source-addr>]}
Variable
Value
all
Deletes routes for all multicast groups.
<group-addr>
Specifies the group IPv6 address of the

routes to clear.
[source-addr]
Specifies the source IPv6 address of the

routes to clear.
Creating an access list entry

The following procedure describes how to create an access list entry. Use the no form of this
command to delete the entry.
Procedure steps
configure terminal
2. Create the access list entry.
[no] ipv6 access-list <listname> <permit|deny|remark>
<prefixmatch>
Variable
<listname>
70
Value
The access list name.
October 2010
Creating a prefix list
Variable
<prefixmatch>
Value
The prefix list to match.
Creating a prefix list

The following procedure describes how to create a prefix list. Use the no form of this command
to delete the prefix list.
Procedure steps
configure terminal
2. Create the prefix list.
[no] ipv6 prefix-list <list> <seq|permit|deny|description>
<X:X::X:X/M|any>
Variable
Value
<any>
Match any prefix.
<list>
The prefix list name.
<X:X::X:X/M>
The IPv6 prefix.
Configuring match address of a route

The following procedure describes how to configure the match address of a route. Use the no
form of this command to remove the ipv6 address entry.
Procedure steps
1. Enter configuration mode:
configure terminal
2. Specify a route map:
route-map <route-map-name> [deny|permit] <1-65535>
3. To specify an address, enter:
[no] match ipv6 address <accesslistname>
October 2010
71

Variable
<accesslistname>
Value
The IPv6 access list name.
Configuring prefix list match entries

The following procedure describes how to match entries of prefix lists. Use the no form of this
command to disable this function.
Procedure steps
1. Enter configuration mode:
configure terminal
2. Specify a route map:
route-map <route-map-name> [deny|permit] <1-65535>
3. To specify a prefix list, enter:
[no] match ipv6 address prefix-list <listname>
Variable
<listname>
Value
The IP address prefix list name.
Displaying IPv6 access lists

The following procedure describes how to display IPv6 access lists.
Procedure steps
Display IPv6 access lists.
show ipv6 access-list <list>
Variable
<list>
72
Value
October 2010
Displaying general prefix information
Displaying general prefix information

The following procedure describes how to display general prefix information.
Procedure steps
Display general prefix information.
show ipv6 general-prefix
Displaying IPv6 interface information

The following procedure describes how to display IPv6 interface information.
Procedure steps
Display IPv6 interface information.
show ipv6 interfaces [interface <name>] [format <detail|brief>]
Variable
Value
<brief>
A brief display.
<detail>
A detailed display.
[format]
The display format.
[interface]
Display a specific interface.
<name>
The interface name.
Displaying the IPv6 multicast routing table

The following procedure describes how to display the IPv6 multicast routing table.
Procedure steps
Display the IPv6 multicast routing table.
October 2010
73
show ipv6 mroute <X:X::X:X|summary>

Variable
Value
<summary>
Display a summary of the table.
<X:X::X:X>
The group IP address.
Displaying learned pmtu information

The following procedure describes how to display learned pmtu information.
Procedure steps
Display learned pmtu information.
show ipv6 mtu
Displaying IPv6 multicast interface information

The following procedure describes how to display IPv6 multicast interface information.
Procedure steps
Display IPv6 multicast interface information.
show ipv6 mvif <interface>
Variable
<interface>
Value
The interface name.
Displaying Neighbor Discovery cache information

The following procedure describes how to display Neighbor Discovery cache information.
Procedure steps
Display Neighbor Discovery cache information.
74
October 2010
Displaying IPv6 prefix list information
show ipv6 neighbors
Displaying IPv6 prefix list information

The following procedure describes how to display IPv6 prefix list information.
Procedure steps
Display IPv6 prefix list information.
show ipv6 prefix-list <WORD|detail|summary>
Variable
Value
<detail>
Detail of prefix lists.
<summary>
Summary of prefix lists.
<WORD>
The name of a prefix list.
Displaying the IPv6 routing table

The following procedure describes how to display the IPv6 routing table.
Procedure steps
Display the IPv6 routing table.
show ipv6 route <X:X::X:X|X:X::X:X/M|database|bgp|connected|
ospf|rip|static|summary>
Variable
Value
<bgp>
Border Gateway Protocol information
<connected>
Connected route information.
<database>
The IPv6 routing table database.
<ospf>
OSPF information.
<rip>
RIP information.
<static>
Static route information.
<summary>
Summary of all routes.
October 2010
75
Variable
Value
<X:X::X:X>
The IPv6 address.
<X:X::X:X/M>
The IPv6 prefix.
Displaying IPv6 Router Advertisement information

The following procedure describes how to display IPv6 Router Advertisement information.
Procedure steps
Display IPv6 Router Advertisement information.
show ipv6 routers
Removing dynamically learned neighbor entries

The following procedure describes how to remove dynamically learned neighbor entries.
Procedure steps
Remove the neighbor entries.
clear ipv6 neighbors
Clearing a prefix list

The following procedure describes how to clear a prefix list.
Procedure steps
Clear the prefix list.
clear ipv6 prefix-list <list> <X:X::X:X/M>
Variable
76
Value
<list>
The prefix list name.
<X:X::X:X/M>
The IPv6 prefix.
October 2010
Clearing multicast route table entries
Clearing multicast route table entries

The following procedure describes how to clear multicast route table entries.
Procedure steps
Clear the prefix list.
clear ipv6 mroute <all|X:X::X:X>
Variable
Value
<all>
Clear all table entries.
<X:X::X:X/M>
Clear by group IPv6 address.
October 2010
77
78
October 2010
Chapter 4: RIPng configuration procedures

This section describes how to configure the Routing Information Protocol for IPv6 networks (RIPng) on
an Avaya Secure Router 2330/4134. Before you configure an interface, you must globally enable RIPng
for all interfaces. RIPng interfaces that you later create inherit these global configuration property settings.
However, to customize RIPng on an interface, you can override the global settings.
This section documents the configuration commands and some operational commands. For a complete
list of show, clear, and other operational commands, refer to Avaya Secure Router 2330/4134 Command
Line Reference (NN47263507).
Enabling RIPng
Enable RIPng to use the Avaya Secure Router 2330/4134 in a RIPng network.
Procedure steps
configure terminal
2. Enable RIPng.
router ipv6 rip
3. Enable RIPng on an interface.
interface <interface> ipv6 router rip
Variable
<interface>
Value
Interface name. Example: Ethernet 0/1
Configuring the IPv6 RIP aggregate address

Use this command to aggregate RIPng routes. Use the no parameter with this command to
disable this feature.
October 2010
79
RIPng configuration procedures
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the aggregate address.
[no] aggregate-address X:X::X:X/P
Configuring IPv6 default routes

Use this command to add default routes to the RIPng updates. Use the no form of this
command to disable this feature.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure default routes.
[no] default-information originate
Configuring IPv6 rip default metrics

Use this command to specify the metrics to be assigned to redistributed routers. Use the no
form of this command to disable this feature. The default metric value is 1.
Use this command with the redistribute command to make the routing protocol use the
specified metric value for all redistributed routes. Default metric is useful in redistributing routes
with incompatible metrics. Every protocol has different metrics and cannot be compared
directly. Default metric provides the standard to compare. All routes that are redistributed will
use the default metric
Procedure steps
80
October 2010
Configuring IPv6 administrative distance
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure default metrics.
[no] default-metric <1-16>
Configuring IPv6 administrative distance

Use this command to set the administrative distance.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the administrative distance.
distance <distancevalue>
Variable
<distancevalue>
Value
The administrative distance value.
Configuring the IPv6 update filters

Use this command to filter incoming or outgoing route updates using the access-list or the
prefix-list. Use the no form of this command to disable this feature. This command is disabled
by default.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure update filtering.
October 2010
81
distribute-list [<prefix>|<accesslist>] <direction>

<interface>
Variable
Value
<prefix>
Specifies the name of the IPv6 prefix-list to

use.
<accesslist>
Specifies the IPv6 access-list number or

name to use.
<direction>
Direction to filter routing updates, in or out.
<interface>
Specifies the name of the interface for which

distribute-list applies.
Configuring an IPv6 RIP neighbor

Use this command to configure a router neighbor. Use the no parameter with this command
to disable the specific router.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the neighbor router.
[no] neighbor <address> <interface>
Variable
82
Value
<address>
Specifies the link-local IPv6 address

(X:X::X:X) of a neighboring router with which
the routing information is exchanged.
<interface>
RIPng interface.
October 2010
Configuring an IPv6 RIP offset-list
Configuring an IPv6 RIP offset-list

Use this command to add an offset to in and out metrics to routes learned through RIPng. Use
the no parameter with this command to remove this function.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the offset list.
offset-list <name> <direction> <metricvalue> <interfacename>
Variable
Value
<name>
<direction>
Direction of updates. In or out.
<metricvalue>
The metric value to modify.
<interfacename>
The interface name.
Configuring an IPv6 RIP passive interface

Use this command to enable suppression of routing updates on an interface. Use the no
parameter with this command to disable this function.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the passive interface.
[no] passive-interface <interface>
October 2010
83

Variable
<interface>
Value
The interface for which you want to suppress
routing updates.
Configuring an IPv6 RIP route-map

Use this command to set a route map. Use the no form of this command to disable this function.
Procedure steps
configure terminal
2. Enable RIP.
router ipv6 rip
3. Configure the route map.
[no] route-map <route-map-name> {in|out} <if-name>
Variable
Value
<route-map-name>
Specifies the route map name.
<if-name>
Specifies the interface name.
Configuring split-horizon
Configure split horizon to prevent loops by not advertising erroneous routes from neighbors.
Use the no form of this command to disable this function.
Procedure steps
configure terminal
2. Enter interface mode.
3. Enable split-horizon with poison reverse.
84
October 2010
Configuring route redistribution
ipv6 rip split-horizon poison

Variable
<interface>
Value
Configuring route redistribution

To redistribute information from other routing protocols use the redistribute command. Use the
no form of this command to disable this function.
Procedure steps
configure terminal
2. Enable RIPng.
router ipv6 rip
3. Redistribute routes.
redistribute [<connected>|<static>|<ospf>|
<bgp>]<metric><routemap>
Variable
Value
<connected>
Redistribute from connected routes
<static>
Redistribute from static routes
<ospf>
Redistribute from Open Shortest Path First (OSPF)
<bgp>
Redistribute from Border Gateway Protocol (BGP)
<metric>
Metric <0-16> Specifies metric value to be used in

redistributing information
<routemap>
Specifies route-map to be used to redistributes information
Configuring timers
Use this command to adjust routing network timers. Use the no form of this command to return
to default setting.
October 2010
85
Procedure steps
configure terminal
2. Enable RIPng.
router ipv6 rip
3. Enable timers.
timers basic <update><timeout><garbage>
Variable
Value
<update>
<5-2147483647> Specifies the routing table update timer in

seconds. The default is 30 seconds.
<timeout>
<5-2147483647> Specifies the routing information timeout

timer in seconds. The default is 180 seconds. After this
interval has elapsed and no updates for a route are received,
the route is declared invalid.
<garbage>
<5-2147483647> Specifies the routing garbage collection

timer in seconds. The default is 120 seconds.
Removing RIPng routes

Remove RIPng routes learned from neighbors and keep the RIPng network intact.
Procedure steps
configure terminal
2. Enter interface mode.
3. Delete learned RIPng routes.
no ipv6 router rip
Variable
<interface>
86
Value
October 2010
Displaying RIPng information
Displaying RIPng information

Display RIPng information for interface
Procedure steps
Show RIPng information.
show ipv6 rip
Displaying RIPng configuration

Display current RIPng configuration.
Procedure steps
Show RIPng protocol information.
show ipv6 protocols rip
Displaying all configured RIPng interfaces

Display information about all configured RIPng interfaces.
Procedure steps
Show RIP interface information.
show ipv6 rip interface
Displaying IPv6 RIP information

Use this command to display RIPng process parameters and statistics.
Procedure steps
Display RIP information.
October 2010
87
show ipv6 protocols rip
Displaying the IPv6 RIP database

Use this command to display the IPv6 RIP database.
Procedure steps
Display the RIP database.
show ipv6 rip database
Displaying IPv6 RIP interface information

Use this command to display IPv6 RIP interface status and configuration.
Procedure steps
Display RIP interface information.
show ipv6 rip interface [<if-name>]
Clearing an IPv6 RIP route

Use this command to clear specific data from the RIPng routing table.
Procedure steps
Clear the routing table.
clear ipv6 rip route [X:X::X:X/M | static | connected | rip |
ospf | bgp |all]
Variable
88
Value
X:X::X:X/M
Removes entries which exactly match this

destination address from the RIPng routing
table.
static
Removes redistributed static entries from the

RIPng routing table.
October 2010
Clearing an IPv6 RIP route
Variable
Value
connected
Removes redistributed connected entries

from RIPng routing table.
rip
Removes RIPng routes from the RIPng

routing table.
ospf
Removes redistributed OSPFv3 routes from

the RIPng routing table.
bgp
Removes redistributed BGP4+ routes from

the RIPng routing table.
all
Clears the entire RIPng routing table.
October 2010
89
90
October 2010
Chapter 5: OSPFv3 procedures
Configuring OSPFv3 routing

The following procedure describes how to begin the OSPFv3 routing process. Use the no form
of this command to disable the process.
Procedure steps
1. Enter Configuration Mode.
configure terminal
2. Enable OSPFv3 routing.
[no] router ipv6 ospf <ospf>
Configuring OSPFv3 IPv6 address range

This procedure describes the steps used to configure the OSPFv3 IPv6 address range. Use
the no form of this command to remove the assigned range.
Procedure steps
configure terminal
2. Specify the OSPF process.
router ipv6 ospf <processid>
3. Set the address range.
[no] area <areaid> range X:X::X:X/M [advertise|not-advertise]
October 2010
91
OSPFv3 procedures
Configuring a stub area

This procedure describes the steps used to define an area as a stub area. Use the no form of
Procedure steps
configure terminal
3. Define an area as a stub area.
[no] area <areaid> stub [no-summary]
Configuring a virtual link

This procedure describes the steps used to configure a link between two backbone areas that
are physically separated through other non-backbone areas. Use the no form of this command
to break the link.
Procedure steps
configure terminal
3. Configure the link.
[no] area <areaid> virtual-link <X:X::X:X> [interval|instid]
Configure the OSPF area default cost

This procedure describes how to specify the summary-default cost of a stub area.
Procedure steps
92
October 2010
Configuring default-metric values
configure terminal
3. Configure the link.
[no] area <areaid> default-cost <cost>
Configuring default-metric values

This procedure describes the steps used to set default metric values for the OSPF routing
protocol. Use the no form of this command to return to defaults.
Procedure steps
configure terminal
3. Set the default metric value.
[no] default-metric <metricvalue>
Configuring a passive interface

This procedure describes the steps used to suppress Hello packets on the specified interface.
Procedure steps
configure terminal
3. Configure an interface as passive.
passive-interface <interfacename>
October 2010
93
OSPFv3 procedures
Configuring redistribution of routes into OSPF

This procedure describes the steps used to redistribute routes from other routing protocols,
static routes into an ospf routing table. Use the no form of this command to disable.
Procedure steps
configure terminal
3. Redistribute the route.
[no] redistribute <protocol> <metric|metric-type|route-map>
Configuring the IPv6 OSPF ABR type

Use this command to specify the OSPFv3 ABR type.
Procedure steps
configure terminal
3. Configure the ABR type.
abr-type <type>
Variable
<type>
94
Value
Type of implementation. Possible choices
are:
October 2010
Configuring IPv6 OSPF cost for an interface
Variable
Value
cisco - Alternative ABR, Cisco
implementation (RFC3509)
ibm - Alternative ABR, IBM
implementation (RFC3509)
standard - Standard behavior
(RFC2328)
Configuring IPv6 OSPF cost for an interface

Use this command to control how OSPF calculates the cost for the interface. Use the no
parameter with this command to assign cost based only on the interface type.
By default OSPF calculates the OSPF cost for an interface by dividing the reference bandwidth
by the interface bandwidth. The default value for the reference bandwidth is 100Mbps. The
auto-cost command is used to differentiate high bandwidth links. For multiple links with high
bandwidth, specify a larger reference bandwidth value to differentiate cost on those links.
Procedure steps
configure terminal
3. Configure the cost.
auto-cost reference-bandwidth <bandwidth>
Variable
<bandwidth>
Value
Reference bandwidth in terms of Mbits per
second, in the range 1 to 4294967.
Configuring IPv6 OSPF administrative distance

Use this command to define an administrative distance.
October 2010
95
OSPFv3 procedures
Procedure steps
configure terminal
3. Configure the administrative distance.
distance [ospf {external | inter-area | intra-area}]
<distance>
Variable
Value
[ospf {external | inter-area | intra-area}]
Specifies administrative distance for OSPF

external, inter-area, or intra-area routes.
<distance>
The OSPF administrative distance, in the

range 1 to 255.
Configuring logging of adjacency state changes

Use this command to enable logging of adjacency state changes.
Procedure steps
configure terminal
3. Configure logging.
log-adjacency-changes [detail]
Variable
[detail]
96
Value
Log all state changes.
October 2010
Configure OSPFv3 routing on an interface
Configure OSPFv3 routing on an interface

This procedure describes the steps used to OSPFv3 routing on an interface. Use the no form of
Procedure steps
configure terminal
2. Enter Interface Mode.
3. Configure OSPFv3 routing.
[no] ipv6 router ospf area <areaid> [instid|tag]
Configuring the dead interval

This procedure describes the steps used to set the interval during which no hello packets are
received and after which a neighbor is declared dead. Use the no form of this command to
reset to default.
Procedure steps
configure terminal
3. Set the dead interval.
[no] ipv6 ospf dead-interval <interval> [instid]
Configuring the hello interval

This procedure describes the steps used to specify the interval between hello packets. Use
the no form of this command to reset to default.
October 2010
97
OSPFv3 procedures
Procedure steps
configure terminal
3. Set the hello interval.
[no] ipv6 ospf hello-interval <interval> [instid]
Configuring OSPF priority

This procedure describes the steps used to set the router priority for determining the
designated router for the network. Use the no form of this command to reset to default.
Procedure steps
configure terminal
3. Set the priority.
[no] ipv6 ospf priority <priority> [instid]
Configuring IPv6 OSPF link cost

Use this command to specify the link-cost described in LSAs. Use the no parameter with this
command to reset the cost to default.
Procedure steps
configure terminal
3. Configure the link cost.
[no] ipv6 ospf cost <cost> [instance-id <1-255>]
98
October 2010
Configuring IPv6 OSPF interface MTU

Variable
Value
<cost>
Specifies the cost of the interface (1-65535).

The default value is 10.
[instance-id <1-255>]
Specifies the instance ID of the interface

(1-255). The default value is 0.
Configuring IPv6 OSPF interface MTU

Use this command to specify the OSPFv3 interface Maximum Transmission Units (MTU).
Procedure steps
configure terminal
3. Configure MTU.
ipv6 ospf mtu <576-65535>
Configuring the IPv6 OSPF mtu-ignore setting

Use this command to set OSPFv3 to ignore the MTU in DBD packets.
Procedure steps
configure terminal
3. Configure to ignore MTU in DBD packets.
ipv6 ospf mtu-ignore
October 2010
99
OSPFv3 procedures
Configuring the IPv6 OSPF network type

Use this command to configure the OSPF network type to a type different from the default for
the media. Use the no form of this command to return to the default value.
Procedure steps
configure terminal
3. Configure the network type.
[no] ipv6 ospf network {broadcast | point-to-point}
Variable
{broadcast | point-to-point}
Value
The OSPF network type. Possible values
are:
broadcast - broadcast multi-access
network
point-to-point - point to point
network

Configuring the IPv6 OSPF retransmit interval

Use this command to set the interval between retransmission of Link State Update packets for
adjacencies belonging to the interface. Use the no parameter with this command to reset the
interval to the default value.
Procedure steps
configure terminal
100
October 2010
Configuring the IPv6 OSPF transmission delay
3. Configure the retransmit interval.
[no] ipv6 ospf retransmit-interval <interval> [instance-id
<1-255>]
Variable
Value
<interval>
Specifies the interval in seconds (1-65535).

The default interval is 5 seconds.

Configuring the IPv6 OSPF transmission delay

Use this command to set the estimated time it takes to transmit a Link State Update packet
over the interface. Use the no parameter with this command to reset the delay to the default
value.
Procedure steps
configure terminal
3. Configure the transmission delay.
[no] ipv6 ospf transmit-delay <delay> [instance-id <1-255>]
Variable
Value
<delay>
Specifies the time, in seconds, to transmit a

link-state update (1-65535). The default
interval is 1 second.

October 2010
101
OSPFv3 procedures
Displaying OSPFv3 debugging information

This procedure describes the steps used to display the OSPFv3 debugging option.
Procedure steps
Display the OSPFv3 debugging option.
show debugging ipv6 ospf
Display global and area OSPFv3 information

This procedure describes the steps used to display global and area information about OSPFv3.
Procedure steps
Display global and area information about OSPFv3.
show ipv6 ospf [tag]
Display OSPFv3 interface information

This procedure describes the steps used to display OSPFv3 interface information.
Procedure steps
Display OSPFv3 interface information.
show ipv6 ospf interface [ifname]
Display OSPFv3 neighbor information

This procedure describes the steps used to display information about an OSPFv3 neighbor.
Procedure steps
Display information about an OSPFv3 neighbor.
102
October 2010
Display OSPFv3 route information
show ipv6 ospf [tag] neighbor [interface|A.B.C.D|detail]
Display OSPFv3 route information

This procedure describes the steps used to display the IPv6 routing table for OSPFv3.
Procedure steps
Display the IPv6 routing table for OSPFv3.
show ipv6 ospf [tag] route
Display OSPFv3 virtual link information

This procedure describes the steps used to display information about OSPFv3 virtual-links.
Procedure steps
Display information about OSPFv3 virtual-links.
show ipv6 ospf [tag] virtual-links
Displaying IPv6 OSPF border routers

Use this command to show border and boundary router information.
Procedure steps
Display border routers.
show ipv6 ospf border-routers
Displaying the IPv6 OSPF database

Use this command to show the OSPFv3 database summary.
Procedure steps
Display the OSPF database.
October 2010
103
OSPFv3 procedures
show ipv6 ospf database
Clearing IPv6 OSPF routing processes

Use this command to clear and restart the OSPFv3 routing process. You can specify the
Process ID to clear one particular OSPFv3 process. When no process ID is specified, this
command clears all running OSPFv3 processes.
Procedure steps
Clear IPv6 OSPF routing processes.
clear ipv6 ospf {<processid> | process}
Variable
<processid>
104
Value
The OSPFv3 process to clear.
October 2010
Chapter 6: BGP4+ configuration

procedures
Enabling BGP
Enable BGP to support the exchange of routes between autonomous systems. This procedure
enables BGP with mainly default configuration values. Any peer groups created under BGP
inherit these default values. You can choose to override (customize) many of these BGP global
values at the BGP group or individual peer level.
Procedure steps
Enable BGP.
router bgp <group-id>
Variable
<group-id>
Value
BGP group ID, in the range 1 to 65535.
Specifying IPv6 address family

Avaya Secure Router 2330/4134 BGP implementation supports IPv4 and IPv6 address
families. Specify the IPv6 address family.
Procedure steps
1. Enable BGP.
router bgp <1-65535>
2. Specify address family.
address-family ipv6 [unicast|multicast]
October 2010
105
BGP4+ configuration procedures
Configuring a passive session OPEN

Configure a passive session OPEN if you do not want BGP to send the active OPEN message
to another peer to establish a BGP session. Instead, the local peer waits for the remote peer
to initiate the BGP session and responds accordingly. (By default, BGP actively initiates
session OPEN with another peer.)
Use the no form of this command to revert.
Procedure steps
configure terminal
2. Enter router mode and specify the BGP AS number.
3. Specify IPv6 address family
address-family ipv6
4. Set the session to passive.
neighbor <X:X::X:X> passive
Advertising the local router ID as nexthop

Advertise the local router ID as the next hop to force iBGP peers and/or eBGP Confederation
Peers in the local AS to use that local node as the next hop for routing traffic to destinations
outside the AS.
Procedure steps
configure terminal
3. Specify the IPv6 address family (if unicast or multicast is not specified, unicast is
the default):
106
October 2010
Comparing the MED value of routes learned from eBGP peers

4. Advertise as next hop.
neighbor <X:X::X:X> next-hop-self
Comparing the MED value of routes learned from eBGP

peers
Compare the multi-exit discriminator (MED) value of routes learned from eBGP peers so that
the Avaya Secure Router 2330/4134 can select the route with the lowest advertised MED
value.
Procedure steps
configure terminal
3. Specify the IPv6 address family.
address-family ipv6
4. Configure to always compare MED values.
bgp always-compare-med
Removing private AS numbers from route advertisements

Remove private AS numbers from route advertisements to avoid propogating those routes to
other BGP peers. When an ISPs local eBGP peer receives a route update message from an
eBGP peer on a private AS, the ISPs peer must remove the private AS numbers.
Procedure steps
configure terminal
October 2010
107

the default):
4. Remove private AS numbers from route advertisements.
neighbor <X:X::X:X> remove-private-as
Configuring a BGP Confederation

Configure a BGP confederation to avoid the scaling issues that the full-mesh connectivity
requirement causes. A confederation splits a major AS into multiple sub-ASs. Although each
sub-AS contains a group of fully-meshed iBGP peers, the sub-AS BGP border router
communicates with other sub-AS BGP border routers using a smaller number of eBGP
sessions. Together, the sub-ASs and their respective peers form a confederation, which
appears to external ASs as a single AS.
Procedure steps
configure terminal
address-family ipv6
4. Configure a confederation.
bgp confederation <id>
Variable
<id>
108
Value
Identifier name.
October 2010
Configuring a BGP Route Reflector cluster
Configuring a BGP Route Reflector cluster

Configure a BGP Route Reflector cluster to achieve full iBGP meshing within a large AS. With
this configuration, an administrator subdivides an AS into peer clusters.
Procedure steps
configure terminal
address-family ipv6
4. Configure a cluster-id.
bgp cluster-id <cluster-id>
Variable
<cluster-id>
Value
Cluster identifier.
Enabling an address family for a neighbor

The following procedure describes how to activate the current address family for the supplied
neighbor.
Procedure steps
configure terminal
the default):
October 2010
109

4. To activate the address family, enter:
neighbor <X:X::X:X> activate
Configuring interval for BGP route updates

The following procedure describes how to configure the minimum interval between sending
BGP routing updates.
Procedure steps
configure terminal
address-family ipv6
4. To set the minimum advertisement interval, enter:
neighbor <X:X::X:X> advertisement-interval <interval>
Variable
<interval>
Value
The advertisement interval, in seconds, in the range 0 to 600.
Configuring interval for AS-origination updates

The following procedure describes how to set the minimum interval between sending ASorigination routing updates.
Procedure steps
110
October 2010
Advertising capability to a peer
configure terminal
address-family ipv6
4. To set the minimum interval, enter:
neighbor <X:X::X:X> as-origination-interval <interval>
Variable
<interval>
Value
The minimum interval, in seconds, in the range 1 to 600.
Advertising capability to a peer

The following procedure describes how to advertise capabilities to a neighbor.
Procedure steps
configure terminal
the default):
4. To advertise a capability, enter:
neighbor <X:X::X:X> capability <dynamic|orf|route-refresh>
Variable
Value
<dynamic>
Advertise dynamic capability to this neighbor.
<orf>
Advertise ORF capability to this neighbor.
<route-refresh>
Advertise route-refresh capability to this neighbor.
October 2010
111
Configuring to originate a default route to neighbor

The following procedure describes how to originate a default route to the specified neighbor.
Procedure steps
configure terminal
the default):
4. To configure a default route, enter:
neighbor <X:X::X:X> default-originate route-map <mapname>
Variable
<mapname>
Value
The route-map name.
Configuring a neighbor description

The following procedure describes how to configure a neighbor's specific description.
Procedure steps
configure terminal
112
October 2010
Configuring a distribution list
address-family ipv6
4. To configure the description, enter:
neighbor <X:X::X:X> description <description>
Variable
<description>
Value
A short description of this neighbor, up to 80 characters.
Configuring a distribution list

The following procedure describes how to filter updates to and from the specified neighbor.
Procedure steps
configure terminal
the default):
4. To filter updates, enter:
neighbor <X:X::X:X> distribute-list <identifier>
Variable
<identifier>
Value
The distribute list identifier. Possible values are:
IP access list number, in the range 1 to 199
Expanded range IP access list number, in the range 1300
to 2699
The IP access list name
October 2010
113
Disallowing capability negotiation

The following procedure describes how to disallow capability negotiation with the specified
neighbor.
Procedure steps
configure terminal
3. Specify the IPv6 address family:
address-family ipv6
4. To disallow capability negotiation, enter:
neighbor <X:X::X:X> dont-capability-negotiate
Allowing EBGP neighbors from indirectly connected

networks
The following procedure describes how to allow EBGP neighbors not on directly connected
networks.
Procedure steps
configure terminal
address-family ipv6
4. To allow EBGP neighbors, enter:
neighbor <X:X::X:X> ebgp-multihop <maxhop>
114
October 2010
Configuring BGP filters

Variable
<maxhop>
Value
The maximum hop count, in the range 1 to 255.
Configuring BGP filters

The following procedure describes how to establish BGP filters.
Procedure steps
configure terminal
the default):
4. Configure BGP filters.
neighbor <X:X::X:X> filter-list <listname> <in|out>
Variable
Value
<in>
Filter incoming routes.
<listname>
The AS path access list name.
<out>
Filter outgoing routes.
Enabling BGP on an interface

The following procedure describes how to enable BGP on an interface.
October 2010
115
Procedure steps
configure terminal
address-family ipv6
4. Enable BGP on the interface.
neighbor <X:X::X:X> interface <interface>
Variable
<interface>
Value
The interface for which you want to enable BGP.
Configuring maximum number of prefixes

The following procedure describes how to set the maximum number of prefixes accepted from
the specified peer.
Procedure steps
configure terminal
the default):
4. Configure the maximum number of prefixes.
neighbor <X:X::X:X> maximum-prefix <maxprefix>
116
October 2010
Configuring a neighbor password

Variable
<maxprefix>
Value
The maximum number of prefixes, in the range 1 to
4294967295.
Configuring a neighbor password

The following procedure describes how to set a password for the specified neighbor.
Procedure steps
configure terminal
address-family ipv6
4. Configure the neighbor password.
neighbor <X:X::X:X> password <password>
Variable
<password>
Value
The password for the specified neighbor.
Configuring peer-group members

The following procedure describes how to add the specified interface as a peer-group member.
Procedure steps
October 2010
117
configure terminal
the default):
4. Configure peer group members.
neighbor <X:X::X:X> peer-group <groupname>
Variable
<groupname>
Value
The name of the peer group to join.
Configuring a prefix list

The following procedure describes how to filter updates to and from the specified neighbor.
Procedure steps
configure terminal
the default):
4. Configure the prefix list.
neighbor <X:X::X:X> prefix-list <name> <in|out>
Variable
118
Value
<in>
Filter incoming updates.
<name>
The name given to the prefix list.
<out>
Filter outgoing updates.
October 2010
Configuring AS number of a remote BGP neighbor
Configuring AS number of a remote BGP neighbor

The following procedure describes how to set the AS number of a remote BGP neighbor.
Procedure steps
configure terminal
3. Specify the IPv6 address-family.
address-family ipv6
4. Configure the AS number.
neighbor <X:X::X:X> remote-as <asnumber>
Variable
<asnumber>
Value
The AS number of the specified remote BGP neighbor, in the
range 1 to 65535.
Configuring a route map to a neighbor

The following procedure describes how to apply a route map to the specified neighbor.
Procedure steps
configure terminal
the default):
October 2010
119

4. Configure the route map.
neighbor <X:X::X:X> route-map <mapname> <in|out>
Variable
Value
<in>
Apply route map to incoming routes.
<mapname>
The name of the route map.
<out>
Apply route map to outbound routes.
Configuring a neighbor as route reflector client

The following procedure describes how to configure the specified neighbor as a route reflector
client. Use the no form of this command to disable this function.
Procedure steps
configure terminal
the default):
4. Configure as route reflector client.
[no] neighbor <X:X::X:X> route-reflector-client
Configuring a neighbor as route server client

The following procedure describes how to configure the specified neighbor as a route server
client. Use the no form of this command to disable this function.
120
October 2010
Sending a community attribute to a neighbor
Procedure steps
configure terminal
the default):
4. Configure as route server client.
[no] neighbor <X:X::X:X> route-server-client
Sending a community attribute to a neighbor

The following procedure describes how to send a community attribute to the specified neighbor.
Procedure steps
configure terminal
the default):
4. Configure to send community attribute.
neighbor <X:X::X:X> send-community <both|extended|standard>
Variable
Value
<both>
Send Standard and Extended Community attributes.
<extended>
Send Extended Community attributes.
<standard>
Send Standard Community attributes.
October 2010
121
Shutting down a neighbor

The following procedure describes how to administratively shutdown the specified neighbor.
Procedure steps
configure terminal
3. Specify the IPv6 address-family:
address-family ipv6
4. Shutdown the neighbor.
neighbor <X:X::X:X> shutdown
Configuring BGP neighbor timers

The following procedure describes how to configure BGP per-neighbor timers.
Procedure steps
configure terminal
address-family ipv6
4. Configure a neighbor timer.
neighbor <X:X::X:X> timers <keepalive> [connect <interval>]
122
October 2010
Configuring a routing update source

Variable
Value
[connect]
Configure the neighbor connect timer.
<interval>
The connect timer interval, in the range 1 to 65535.
<keepalive>
The keepalive interval for the specified neighbor, in the range

0 to 65535.
Configuring a routing update source

The following procedure describes how to configure a source for the specified neighbor's
routing updates.
Procedure steps
configure terminal
address-family ipv6
4. Configure the routing update source.
neighbor <X:X::X:X> update-source <source>
Variable
<source>
Value
The interface name or address of the update source.
Configuring weight for a BGP neighbor

The following procedure describes how to configure the weight for the specified BGP neighbor.
October 2010
123
Procedure steps
configure terminal
address-family ipv6
4. Configure the weight.
neighbor <X:X::X:X> weight <weight>
Variable
<weight>
Value
The default weight, in the range 0 to 65535.
Modifying a default bestpath selection

The following procedure describes how to modify the default bestpath selection. Use the no
form of this command to revert to default.
Procedure steps
configure terminal
address-family ipv6
4. To modify the default selection, enter:
[no] bgp bestpath [as-path ignore] [compare-confed-aspath]
[compare-routerid] [med [confed [missing-as-worst]|[missingas-worst [confed]]]]
Variable
[as-path ignore]
124
Value
Ignore as-path length in selecting a route.
October 2010
Configuring client-to-client route reflection
Variable
Value
[compare-confed-aspath]
Allow comparing confederation AS path length.
[compare-routerid]
Compare router-id for identical EBGP paths.
[confed]
Compare MED among confederation paths.
[med]
Configure MED attribute.
[missing-as-worst]
Treat missed MED as the least preferred one.
Configuring client-to-client route reflection

The following procedure describes how to configure client-to-client route reflection.
Procedure steps
configure terminal
address-family ipv6
4. To configure route reflection, enter:
bgp client-to-client reflection
Configuring a route reflector cluster-id

The following procedure describes how to configure the route reflector cluster-id.
Procedure steps
configure terminal
October 2010
125

address-family ipv6
4. To configure the cluster-id, enter:
bgp cluster-id <id>
Variable
<id>
Value
The route reflector cluster-id. Can be configured as 32bit
quantity, in the range 1 to 4294967295 or in IP address
format.
Configuring AS confederation parameters

The following procedure describes how to configure confederation parameters.
Procedure steps
configure terminal
address-family ipv6
4. To configure confederation parameters, enter:
bgp confederation [identifer <asnumber>] [peers <peer>]
Variable
126
Value
[identifer <asnumber>]
Configure confederation by AS number, in the range 1 to

65535.
[peers <peer>]
Configure confederation by peer AS by listing each peer

number, in the range 1 to 65535, followed by a space, up to
a maximum of 255 entries.
October 2010
Enabling route flap dampening
Enabling route flap dampening

The following procedure describes how to enable and configure route flap dampening.
Procedure steps
configure terminal
the default):
4. To enable and configure flap dampening, enter:
bgp dampening [route-map <mapname>] [<hltime> <reuse>
<suppress> <duration> <uhltime>
Variable
Value
<duration>
Maximum duration to suppress a stable route.
<hltime>
Reachability half-life time for a penalty, in minutes.
<reuse>
Value to start reusing a route.
[route-map <mapname>]
Configure route-map criteria by map name.
<suppress>
Value to start suppressing a route.
<uhltime>
Unreachability half-life time for a penalty, in minutes.
Configuring BGP defaults

The following procedure describes how to configure BGP defaults.
October 2010
127
Procedure steps
configure terminal
address-family ipv6
4. To configure BGP defaults, enter:
bgp default [ipv4-unicast] [local-preference <value>]
Variable
Value
[ipv4-unicast]
Activate IPv4 unicast for a peer by default.
[local-preference <value>]
Configure the local preference value, in the range 0 to

4294967295. The higher the value, the more preferred.
Enforcing first AS for EBGP routes

The following procedure describes how to enforce the first AS for an EBGP route.
Procedure steps
configure terminal
address-family ipv6
4. To enforce the first AS, enter:
bgp enforce-first-as
128
October 2010
Resetting a session when a peer goes down
Resetting a session when a peer goes down

The following procedure describes how to immediately reset a session if a link to a directly
connected external peer goes down.
Procedure steps
configure terminal
address-family ipv6
4. To configure the session to reset, enter:
bgp fast-external-failover
Logging neighbor changes

The following procedure describes how to configure logging neighbor changes.
Procedure steps
configure terminal
address-family ipv6
4. To log neighbor changes, enter:
bgp log-neighbor-changes
October 2010
129
Overriding current router-id

The following procedure describes how to override the current router identifier and reset peers.
Procedure steps
configure terminal
address-family ipv6
4. To override the router id, enter:
bgp router-id <id>
Variable
<id>
Value
The manually configured router identifier, in IP address
format.
Configuring background scan interval

The following procedure describes how to configure the background scan interval, in seconds.
Procedure steps
configure terminal
the default):
130
October 2010
Defining the administrative distance

4. To set the scan interval, enter:
bgp scan-time <interval>
Variable
<interval>
Value
The scan interval, in seconds, in the range 10 to 60. Default is
60.
Defining the administrative distance

The following procedure describes how to configure the administrative distance.
Procedure steps
configure terminal
the default):
4. To configure the administrative distance, enter:
distance [<distance>] [bgp <ext> <int> <local>]
Variable
Value
[bgp]
Configure the BGP distance.
[<distance>]
Configure the administrative distance, in the range 1 to 255.
<ext>
Distance for routes external to the AS, in the range 1 to 255.
<int>
Distance for routes internal to the AS, in the range 1 to 255.
<local>
Distance for local routes, in the range 1 to 255.
October 2010
131
Configuring IGP synchronization

The following procedure describes how to configure IGP synchronization.
Procedure steps
configure terminal
the default):
4. To configure synchronization, enter:
synchronization
Configuring routing timers

The following procedure describes how to configure routing keepalive and holdtime timers.
Procedure steps
configure terminal
address-family ipv6
4. To configure timers, enter:
timers bgp <keepalive> <holdtime>
132
October 2010
Redistributing information from another protocol

Variable
Value
<holdtime>
The hold timer value, in the range 0 to 65535.
<keepalive>
The keepalive interval, in the range 0 to 65535.
Redistributing information from another protocol

The following procedure describes how to redistribute information from another protocol.
Procedure steps
configure terminal
the default):
4. To redistribute information, enter:
redistribute <protocol> route-map <mapname>
Variable
Value
<mapname>
The pointer to route-map entries.
<protocol>
The protocol you want to redistribute from. Possible choices

are:
connected - redistribute from connected routes.
ospf - redistribute from OSPF routes.
rip - redistribute from RIP routes.
static - redistribute from Static routes.
October 2010
133
Configuring BGP aggregate entries

Use this command to configure BGP aggregate entries.
Procedure steps
configure terminal
the default):
4. Configure aggregate entries.
aggregate-address <prefix> [as-set] [summary-only]
Variable
Value
[as-set]
Generate AS set path information.
[summary-only]
Filter more specific routes from updates.
Configuring EBGP-ECMP processing

Use this command to perform EBGP ECMP processing.
Procedure steps
configure terminal
the default):
4. Configure EBGP-ECMP processing.
134
October 2010
Activating the current address family for a neighbor
ebgp-ecmp
Activating the current address family for a neighbor

Use this command to activate the current address family for the supplied neighbor.
Procedure steps
configure terminal
the default):
4. Activate the address family.
neighbor {<X:X::X:X> | <tag>} activate
Configuring to accept an AS-path containing the current AS

Use this command to accept as-path with my AS present in it.
Procedure steps
configure terminal
the default):
4. Configure to accept the AS-path.
neighbor {<X:X::X:X> | <tag>} allowas-in [<1-10>]
October 2010
135

Variable
[<1-10>]
Value
Number of occurences of AS number.
Configuring to start storing updates

Use this command to configure the software to start storing updates. Use the no parameter
with this command to disable this function.
Procedure steps
configure terminal
the default):
4. Configure to start storing updates.
[no] neighbor {<X:X::X:X> | <tag>} soft-reconfiguration
inbound
Configuring to selectively unsuppress suppressed routes

Use this command to selectively unsuppress suppressed routes.
Procedure steps
configure terminal
the default):
136
October 2010
Specifying a network to announce via BGP

4. Configure to unsuppress routes
neighbor {<X:X::X:X> | <tag>} unsuppress-map <route-map>
Variable
<route-map>
Value
Name of the route map.
Specifying a network to announce via BGP

Use this command to specify a network to announce via BGP
Procedure steps
configure terminal
the default):
4. Specify the network to announce.
network [<X:X::X:X/M>] [synchronization]
Variable
Value
<X:X::X:X/M>
IPv6 prefix of the network.
[synchronization]
Perform IGP synchronization on network

routes.
Configuring aggregation on same next hop

The following procedure describes how to configure BGP to perform aggregation only when
the next hop is the same.
October 2010
137
Procedure steps
configure terminal
2. To configure aggregation, enter:
bgp aggregate-nexthop-check
Displaying BGP routes matching communities

Use this command to show routes matching the communities.
Procedure steps
Display routes matching communities.
show bgp ipv6 [unicast|multicast] community [<AA:NN>] [localas] [no-advertise] [no-export] [exact-match]
Variable
Value
[<AA:NN>]
Specifies a valid value for a community

number.
[local-AS]
Do not send outside local AS (well-known

community).
[no-advertise]
Do not advertise to any peer (well-known

community).
[no-export]
Do not export to next AS (well-known

community).
[exact-match]
Specifies that the router shows the exact

match of the communities.
Displaying all BGP4+ community information

Use this command to list all BGP4+ community information.
Procedure steps
Display community information.
138
October 2010
Displaying detailed BGP4+ neighbor information
show bgp ipv6 [unicast|multicast] community-info
Displaying detailed BGP4+ neighbor information

Use this command to display detailed information about BGP4+ neighbor connections.
Procedure steps
Display detailed neighbor information.
show bgp ipv6 [unicast|multicast] neighbors [<A.B.C.D> |
<X:X::X:X>] [advertised-routes | received | received-routes |
routes]
Variable
Value
[<A.B.C.D> | <X:X::X:X>]
Neighbor for which to display information.
advertised-routes
Display the routes advertised to a BGP

neighbor.
received
Display information received from a BGP

neighbor.
received-routes
Display the received routes from neighbor.
routes
Display routes learned from neighbor.
Displaying routes matching an AS path regular expression

Use this command to display routes matching the AS path regular expression (quoted string).
Procedure steps
Display routes.
show bgp ipv6 [unicast|multicast] quote-regexp <"quotedstring">
Displaying the BGP4+ scan status

Use this command to display the BGP4+ scan status.
October 2010
139
Procedure steps
Display the scan status.
show bgp ipv6 [unicast|multicast] scan
Displaying BGP attribute information

The following procedure describes how to display BGP attribute information.
Procedure steps
To display BGP attribute information, enter:
show bgp ipv6 [unicast|multicast] attribute-info
Displaying BGP paths

The following procedure describes how to display BGP path information.
Procedure steps
To display BGP path information, enter:
show bgp ipv6 [unicast|multicast] paths
Displaying BGP neighbor status summary

The following procedure describes how to display a BGP neighbor status summary.
Procedure steps
To display a neighbor status summary, enter:
show bgp ipv6 [unicast|multicast] summary
Displaying inconsistent AS paths

The following procedure describes how to display inconsistent AS paths.
140
October 2010
Displaying detailed dampening information
Procedure steps
To display inconsistent AS paths, enter:
show bgp ipv6 [unicast|multicast] inconsistent-as
Displaying detailed dampening information

The following procedure describes how to display detailed dampening information.
Procedure steps
To display detailed dampening information, enter:
show bgp ipv6 [unicast|multicast] dampening <type>
Variable
<type>
Value
The type of dampening information to display. Possible
choices are:
dampened-paths - Display paths suppressed due to
dampenin.
flap-statistics - Display flap statistics of routes.
parameters - Display details of configured dampening
parameters.
Displaying routes matching route map

The following procedure describes how to display routes that match a particular route map.
Procedure steps
To display routes, enter:
show bgp ipv6 [unicast|multicast] route-map <mapname>
Variable
<mapname>
Value
The route map to match against.
October 2010
141
Display routes matching a prefix list

The following procedure describes how to display routes that match a particular prefix list.
Procedure steps
show bgp ipv6 [unicast|multicast] prefix-list <listname>
Variable
<listname>
Value
The prefix list to match against.
Display routes matching a filter list

The following procedure describes how to display routes matching a particular filter list.
Procedure steps
show bgp ipv6 [unicast|multicast] filter-list <listname>
Variable
<listname>
Value
The filter list to match against.
Display routes matching a community list

The following procedure describes how to display routes matching a particular community list.
Procedure steps
142
October 2010
Display routes matching an AS path regular expression
show bgp ipv6 [unicast|multicast] community-list <listname>

Variable
<listname>
Value
The community list to match against.
Display routes matching an AS path regular expression

The following procedure describes how to
Procedure steps
show bgp ipv6 [unicast|multicast] regexp <expression>
Variable
<expression>
Value
A regular expression used to match the BGP AS paths.
Initiating a BGP Route Refresh

Initiate a BGP Route Refresh when you want to re-evaluate routes advertised by a remote peer
against all existing import policies.
Procedure steps
Clear BGP neighbors from the system.
clear bgp all
Resetting all BGP peers in IPv6 family

The following procedure describes how to reset all BGP peers in the IPv6 address family.
Procedure steps
To clear all IPv6 BGP peers, enter:
October 2010
143
clear bgp ipv6 {unicast|multicast}*
Resetting an IPv6 BGP connection

Use this command to reset an IPv6 BGP connection.
Procedure steps
Reset the connection.
clear bgp ipv6 {unicast|multicast}{* | v4 | v6 | <1-65535> |
<A.B.C.D> | <X:X::X:X>} [in|out|soft] [prefix-filter]
Variable
144
Value
Clears all peers.
v4
Clears all IPv4 peers
v6
Clears all IPv6 peers
<1-65535>
Clears peers with the specified AS number.
<A.B.C.D> | <X:X::X:X>
Specifies a BGP neighbor address to clear.
in
Indicates that incoming advertised routes are to be cleared.
out
Indicates that outgoing advertised routes are to be cleared.
soft
Indicates that both incoming and outgoing routes are to be

cleared
[prefix-filter]
Pushes out prefix-list ORF and does inbound soft

reconfiguration.
October 2010
Chapter 7: PIM configuration procedures
Registering an accept filter

This procedure details the steps necessary to configure the ability to filter out multicast sources
specified by the given access-list at the RP so that the RP will accept/refuse to perform Register
mechanism for the packets sent by the specified sources. Use the no form of this command
to revert to default (off).
Procedure steps
1. Enter configuration mode.
configure terminal
2. In configuration mode, enter the command to configure the accept filter.
[no] ipv6 pim accept-register list [<accesslist>|<word>]
Variable
Value
<accesslist>
The IP standard access list. Valid ranges are 1 to 99 for

simple range value and 1300 to 1999 for expanded range
value.
<word>
The IP named access-list.
Configuring candidate bootstrap router

This procedure details the steps necessary to enable BSR status using a specific interface
name. Use the no form of this command to disable the function.
Procedure steps
configure terminal
2. In configuration mode, enter the command to enable BSR status.
October 2010
145
PIM configuration procedures
ipv6 pim bsr-candidate <ifname> <hash> <priority>

Variable
Value
<ifname>
The name of the interface.
<hash>
The mask hash length for RP selection. Valid range is 0 to 32.
<priority>
The priority for a BSR candidate. Valid range is 0 to 255.
Setting the source address for PIM register

This procedure details the steps necessary to configure the source address of Register packets
sent by this DR, overriding the default source address, which is the address of the RPF
interface toward the source host. Use the no form of this command to revert to the default
source address.
Note:
The configured address must be reachable in order to be used by the RP to send
corresponding Register-Stop messages in response. It can be either the loop back interface
address or other physical addresses. This address must be advertised by unicast routing
protocols on the DR. The configured interface does not require being PIM-SM enabled.
Procedure steps
configure terminal
2. In configuration mode, enter the command to configure the source address.
[no] ipv6 pim register-source <sourceaddress> <ifname>
Variable
146
Value
<sourceaddress>
The IP address used as the source of register packets.
<ifname>
The interface name. The address of this interface is used as

the source of register packets.
October 2010
Configuring source-specific multicast
Configuring source-specific multicast

This procedure details the steps necessary to configure the source-specific multicast (SSM)
default value or access-list filter range. Use the no form of this command to disable sourcespecific multicast.
Procedure steps
configure terminal
2. In configuration mode, enter the command to configure SSM.
[no] ipv6 pim ssm [default] [range <word>]
Variable
Value
[default]
To use 232/8 group range for SSM (optional).
[range]
To configure a range using access list or word (optional).
<word>
The IP named standard IPv6 access list.
Configuring the PIM rendezvous point address

Use this command to configure the PIM Rendezvous Point address. Use the no form of this
command to revert to default.
Procedure steps
configure terminal
2. Configure the RP address.
[no] ipv6 pim rp-address <address>
Variable
<address>
Value
The address of the Rendezvous Point.
October 2010
147
Configuring a PIM rendezvous point candidate

Use this command to configure the Rendezvous Point candidate. Use the no form of this
command to revert to default behavior.
Procedure steps
configure terminal
2. Configure the RP candidate.
[no] ipv6 pim rp-candidate <X:X::X:X> [interval <1-16383>]
[priority <0-255>] [group-list <listname>]
Variable
Value
<X:X::X:X>
The IPv6 address of the RP candidate.
<interval>
The candidate RP advertisement interval.
<priority>
The candidate RP priority.
<group-list>
The group range for this candidate RP.
Configuring to not have source-tree switching threshold

Use this command to configure a group to have no source-tree switching threshold. Use the
no form of this command to revert to default behavior.
Procedure steps
configure terminal
2. Configure the group to not have a source-tree switching threshold.
[no] ipv6 pim spt-threshold-infinity [group-list
<accesslist>]
148
October 2010
Enabling a BSR border router

Variable
Value
<accesslist>
The IPv6 access list name you want to

remove the threshold from.
Enabling a BSR border router

This procedure details the steps necessary to enable a BSR border router. Use the no form of
Procedure steps
configure terminal
3. In Interface mode, enter the command to enable a border router.
[no] ipv6 pim bsr-border
Variable
<interface>
Value
The Interface name. Example: ethernet 0/1
Setting Hello message interval

This procedure details the steps necessary to configure a hello interval value. Use the no form
of this command to disable.
Procedure steps
configure terminal
3. In Interface mode, enter the command to configure the hello interval.
October 2010
149
[no] ipv6 pim hello-interval <interval>

Variable
Value
<interface>
<interval>
The hello interval value in seconds. Valid range is 10 to

65535 (default is 30).
Enabling PIM sparse-mode operation

This procedure details the steps necessary to enable PIM-SM on the active interface. Use the
no form of the command to disable PIM-SM on the interface.
Use the passive option to enable passive mode operation for local IGMP members on the
interface. Passive mode stops PIM-SM transactions on the interface, allowing only IGMP
mechanism to be active. Use the no form of this command to turn off passive mode.
Procedure steps
configure terminal
3. In Interface mode, enter the command to enable PIM-SM.
[no] ipv6 pim sparse-mode
4. To enable passive mode, enter the following command:
[no] ipv6 pim sparse-mode passive
Variable
<interface>
Value
Configuring PIM router DR priority

Use this command to configure PIM router DR priority. Use the no form of this command to
revert to default.
150
October 2010
Configuring to exclude Gen-id
Procedure steps
configure terminal
3. Configure the priority.
[no] ipv6 pim dr-priority <priority>
Variable
<priority>
Value
The PIM router DR priority, in the range 0 to
4294967294.
Configuring to exclude Gen-id

Use this command to configure PIM to exclude Gen-id option from PIM hello packets on the
specified interface. Use the no form of this command to revert to default behavior.
Procedure steps
configure terminal
3. Configure to exclude gen-id.
[no] ipv6 pim exclude-genid
Configuring a PIM peering filter

Use this command to configure a PIM peering filter. Use the no form of this command remove
the peer filter.
Procedure steps
October 2010
151
configure terminal
3. Configure the PIM peering filter.
[no] ipv6 pim neighbor-filter <accesslist>
Variable
<accesslist>
Value
The IPv6 access list name used in filtering.
Configuring PIM neighbor change logging

Use this procedure to enable logging of the PIM neighbor changes to the console. By default,
PIM neighbor change logging is enabled.
Procedure steps
1. To enter configuration mode, enter:
configure terminal
2. To configure PIM neighbor change logging to the console, enter:
[no] ipv6 pim log-neighbor-changes
Variable
[no]
Value
Disables PIM neighbor change logging.
Configuring an anycast member RP address

Use this procedure to configure an anycast member RP address. By default, no anycast
members are configured.
Prerequisites
To perform this procedure, configure the anycast RP address as a static RP address.
Procedure steps
1. To enter the configuration mode, enter:
152
October 2010
Configuring PIM multipath
configure terminal
2. To configure the anycast member RP address, enter:
[no] ipv6 pim anycast-rp <anycast-RP-address> <anycastmember-RP-address>
Variable
Value
[no]
Removes the configured anycast RP

member.
<anycast-RP-address>
Specifies the IPv6 address of the anycast RP

address.
<anycast-member-RP-address>
Specifies the IPv6 address of the anycast

member RP address.
Configuring PIM multipath

Configure PIM multipath to enable the selection of equal cost multipath (ECMP) next hops for a
given destination. By default, PIM multipath is disabled.
Procedure steps
configure terminal
2. To configure PIM mutipath , enter:
[no] ipv6 pim multipath [hashing]
Variable
Value
[no]
Disables PIM multipath.
[hashing]
Enables the next hop selection based on key,

which is calculated using source address,
group address and nexthop address. By
default, a round-robin mechanism is used to
select the next hop
October 2010
153
Displaying PIM RPF

Use this procedure to display RPF information based on source address and, optionally, group
address.
The router displays RPF information for all ECMP routes if:
- Multipath (round-robin / hashing) is enabled and group address is not specified
- Multipath (round-robin) is enabled and a matching (S,G) entry does not exist.
Procedure steps
To display the PIM RPF information, enter:
show ipv6 pim sparse-mode rpf <source-addr> [<group-addr>]
Variable
Value
<source-addr>
Specifies the IPv6 source address for which

to display PIM RPF information.
<group-addr>
Specifies the IPv6 group address for which

to display PIM RPF information.
Clearing PIM statistics

Use this procedure to clear PIM statistics. If no options are specified, the router clears the
interface and global statistics counters.
Procedure steps
To clear PIM statistics, enter:
clear ipv6 pim sparse-mode statistics [ interface [<ifname>] |
all]
Variable
[interface <ifname>]
154
Value
Clears statistics for the particular interface. If
the interface name is not specified, the router
clears statistics for all interfaces.
October 2010
Configuring embedded RP mapping
Variable
all
Value
Clears the interface and global statistics
counters and Tree Information Base (TIB)
information.
Configuring embedded RP mapping

Use this procedure to enable or disable embedded RP mapping.
Procedure steps
configure terminal
2. To configure embedded RP mapping, enter:
[no] ipv6 pim rp embedded
Variable
[no]
Value
Disables embedded RP mapping.
Displaying PIM RP
Use this procedure to display RP (rendezvous point) to be chosen based on group selected.
Procedure steps
To display the RP to be chosen based on group selected, enter:
show ipv6 pim sparse-mode rp-hash <group-addr>
Variable
<group-addr>
Value
Specifies the IPv6 group address for which
to display PIM RP information.
October 2010
155
Displaying group-to-RP mappings

Use this procedure to display group-to-RP mappings and the RP set.
Procedure steps
To display the group-to-RP mappings, enter:
show ipv6 pim sparse-mode rp mapping
Displaying PIM statistics

Use this procedure to display IPv6 PIM statistics.
Procedure steps
To display the group-to-RP mappings, enter:
show ipv6 pim sparse-mode statistics
Displaying bootstrap router information

This procedure details the steps necessary to show the bootstrap router address.
Procedure steps
Enter the command to show bootstrap router information.
show ipv6 pim sparse-mode bsr-router
Displaying the PIM Tree Information Base

This procedure details the steps necessary to show the PIM Tree Information Base. Use group,
source address (or both) to filter display between group, source, and group/source displays
respectively.
Procedure steps
Enter the command to show the PIM Tree Information Base.
156
October 2010
Displaying PIM interface information
show ipv6 pim sparse-mode database [<src-addr>|<grp-addr>]

Variable
Value
<src-addr>
Filter by source address (optional).
<grp-addr>
Filter by group address (optional).
Displaying PIM interface information

This procedure details the steps necessary to show PIM interface information.
Procedure steps
Enter the command to show PIM interface information.
show ipv6 pim sparse-mode interface <ifname> [detail]
Variable
Value
<ifname>
The interface name.
[detail]
Display detailed information (optional).
Displaying group-to-RP mapping information

Use this command to display group-to-RP mapping information.
Procedure steps
Display mapping information.
show ipv6 pim rp mapping
Displaying PIM neighbor information

This procedure details the steps necessary to show PIM neighbor information.
October 2010
157
Procedure steps
Enter the command to show neighbor information.
show ipv6 pim sparse-mode neighbor <ifname> [detail]
Variable
Value
<ifname>
The PIM-enabled interface name or number
[detail]
Show detailed PIM neighbor information (optional).
Displaying PIM Rendezvous Point information

This procedure details the steps necessary to display rendezvous-point (RP) information
based on group.
Procedure steps
Enter the command to show RP information.
show ipv6 pim rp-hash <group-address>
Variable
<group-address>
Value
The IPv6 group address.
Clearing PIM bootstrap router information

Use this command to clear all PIM bootstrap router information.
Procedure steps
Clear bootstrap router information.
clear ipv6 pim sparse-mode bsr rp-set all
158
October 2010
Chapter 8: MLD procedures
Configuring multicast group membership

This procedure details the steps necessary to control the multicast group membership on an
interface. Use the no form of this command to disable.
Procedure steps
configure terminal
3. Configure group membership.
[no] ipv6 mld access-group <word>
<word> is the named standard IPv6 access list.
Configuring leave latency

This procedure details the steps necessary to minimize the leave latency of MLD memberships.
This command is used when only one receiver node is connected to each interface. Use the
no form of this command to disable.
Procedure steps
configure terminal
3. Configure leave latency.
[no] ipv6 mld immediate-leave group-list <word>
<word> is the named standard IPv6 access list.
October 2010
159
MLD procedures
Configuring query intervals

This procedure details the steps necessary to configure the frequency at which MLD sends
MLD General query messages. Use the no form of this command to return to default frequency.
Procedure steps
configure terminal
3. Configure the query interval.
[no] ipv6 mld query-interval <interval>
Configuring query timeouts

This procedure details the steps necessary to configure the timeout period before the router
takes over as the querier for the interface after the previous querier has stopped querying. Use
the no form of this command to restore default values.
Procedure steps
configure terminal
3. Configure the query timeout.
[no] ipv6 mld querier-timeout <timeout>
Variable
<timeout>
160
Value
The timeout interval.
October 2010
Configuring the robustness variable
Configuring the robustness variable

This procedure details the steps necessary to set the robustness variable for MLD. Use the no
form of this command to restore default values.
Procedure steps
configure terminal
3. To configure the robustness variable, enter:
[no] ipv6 mld robustness-variable <robustnessvalue>
Configuring the MLD version

This procedure details the steps necessary to set the version of MLD. Use the no form of this
command to use the default version.
Procedure steps
configure terminal
3. To set the MLD version, enter:
[no] ipv6 mld version <version>
Configuring MLD last-member query-count

Use this command to set the last-member query-count value.
Procedure steps
October 2010
161
MLD procedures
configure terminal
3. Configure the query-count value.
ipv6 mld last-member-query-count <2-7>
Variable
<2-7>
Value
Specifies the last member query count value.
Configuring group-specific query interval

Use this command to configure the frequency at which the router sends MLD group-specific
query messages. To set this frequency to the default value, use the no parameter with this
command.
Procedure steps
configure terminal
3. Configure the query interval
[no] ipv6 mld last-member-query-interval <interval>
Variable
<interval>
Value
Specifies the frequency (in seconds) at
which IGMP group-specific host query
messages are sent. It ranges from 1 to 25.
The default is 1 second.
Configuring the MLD query maximum response time

Use this command to configure the maximum response time advertised in MLD queries.
162
October 2010
Configuring global state limit
Procedure steps
configure terminal
3. Configure the maximum response time.
ipv6 mld query-max-response-time <responsetime>
Variable
<responsetime>
Value
Specifies the maximum response time (in
seconds) advertised in MLD queries. It
ranges from 1 to 240. The default is 10
seconds.
Configuring global state limit

Use this procedure to configure a maximum global limit to the number of allowable states
(groups) on the router. By default, no state limit exists.
Procedure steps
configure terminal
2. To configure the state limit, enter:
[no] ipv6 mld limit <limit>
Variable
Value
[no]
Removes the configured state limit.
<limit>
Specifies the maximum allowable states on

the router. Values range from 1 to 2097152.
October 2010
163
MLD procedures
Configuring state limit on an interface

Use this procedure to configure a maximum limit to the number of allowable states (groups)
on an interface. By default, no state limit exists.
Procedure steps
configure terminal
2. To specify the VLAN to configure, enter:
interface vlan <vid>
3. To configure the group limit, enter:
[no] ipv6 mld limit <limit>
Important:
If the L2 VLAN is not created before you enter the interface vlan vlan<vid>
command, an error message is displayed.
Variable
Value
<vid>
Specifies the ID of the VLAN interface to

configure.
[no]
Removes the configured state limit.
<limit>
Specifies the maximum allowable states on

the router. Values range from 0 to 2097152.
Configuring the SSM mapping status

Use this procedure to enable static source specific multicast (SSM) mapping. By default, SSM
mapping is disabled.
Procedure steps
configure terminal
2. To configure the SSM mapping status, enter:
164
October 2010
Configuring a static SSM map
[no] ipv6 mld ssm-map enable

Variable
[no]
Value
Disables SSM mapping.
Configuring a static SSM map

Use this procedure to statically map a specified source address to an SSM group specified in
the access list. The router applies the mapping after it receives an MLDv2 report for the
specified group. By default, no static SSM maps are configured.
Procedure steps
configure terminal
2. To configure the static SSM map, enter:
[no] ipv6 mld ssm-map static [<access-list>>] <source-addr>
Variable
Value
[no]
Removes the static mapping.
<access-list>
Specifies an IP named access-list.
<sorce-addr>
Specifies an IPv6 multicast source address.
Configuring a static group on an interface

Use this procedure to add a static group on an interface. By default, no static groups are
configured.
Procedure steps
configure terminal
2. To access the VLAN database, enter:
vlan database
October 2010
165
MLD procedures
3. To specify the VALN to configure, enter

vlan <vid>
4. To configure a static group, enter:
[no] ipv6 mld static-group <group-addr> [source {<sourceaddr> |ssm-map}] {interface <if-name>}
Variable
Value
[no]
Removes the specified static mapping.
<vid>
Specifies the ID of the VLAN interface to

configure.
<group-addr>
Specifies the IPv6 multicast group address

to statically configure.
<source-addr>
Specifies the IPv6 multicast source address

to associate with this group.
ssm-map
Specifies to use Source Specific Multicast

(SSM) mapping to identify the source to
associate with this group.
<if-name>
Specifies the VLAN interface name to

associate with this group.
Displaying MLD statistics

Use this procedure to display MLD statistics.
Procedure steps
To display MLD statistics, enter:
show ipv6 mld statistics <if-name> [detail]
Variable
166
Value
<if-name>
Specifies the interface for which to display

the MLD statistics.
[detail]
Provides additional detail in the command

output.
October 2010
Clearing MLD statistics
Clearing MLD statistics

Clear MLD statistics to set all MLD statistics counters to zero. To clear interface-specific
counters, use the <if-name> parameter.
Procedure steps
To clear MLD statistics, enter:
clear ipv6 mld statistics <if-name>
Variable
<if-name>
Value
Specifies the interface for which to clear the
MLD statistics. If no interface is specified, all
statistics information is set to zero.
Display MLD groups

This procedure details the steps necessary to display the multicast groups with receivers
directly connected to the router and learned through MLD.
Procedure steps
Displays the groups.
show ipv6 mld groups [<groupaddress>|<ifname>] [detail]
Display MLD interface information

This procedure details the steps necessary to display multicast-related information about an
interface. Using show ipv6 mld interface command without parameters displays information
about all interfaces.
Procedure steps
Display interface information.
October 2010
167
MLD procedures
show ipv6 mld interface <ifname>

Variable
<ifname>
Value
The interface for which you want to display information.
Clearing MLD group entries

This procedure details the steps necessary to clear MLD group entries.
Procedure steps
Clear MLD group entries.
clear ipv6 mld group [all|<groupaddress>|<ifname>]
Variable
Value
[all]
Clear all MLD group entries.
<groupaddress>
Clear by group address.
<ifname>
Clear by interface name.
Clearing MLD interface entries

This procedure details the steps necessary to clear MLD interface entries.
Procedure steps
Clear MLD interface entries.
clear ipv6 mld interface <ifname>
Variable
<ifname>
168
Value
The interface for which you want to clear MLD interface
entries.
October 2010

NN47263-503 04.01 Configuration IPv6 Routing

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

NN47263-503 04.01 Configuration IPv6 Routing

Cargado por

Copyright:

Formatos disponibles

Configuration IPv6 and Routing

Avaya Secure Router 2330/4134

2010 Avaya Inc.

All Rights Reserved.

protected by copyright and other intellectual property laws including the

Configuration IPv6 and Routing

Chapter 2: IPv6 routing fundamentals...................................................................................11

Configuration IPv6 and Routing

Chapter 3: IPv6 routing procedures......................................................................................61

Configuration IPv6 and Routing

Displaying the IPv6 multicast routing table.....................................................................................................73

Chapter 4: RIPng configuration procedures.........................................................................79

Chapter 5: OSPFv3 procedures.............................................................................................91

Configuration IPv6 and Routing

Configuring IPv6 OSPF interface MTU...........................................................................................................99

Chapter 6: BGP4+ configuration procedures.....................................................................105

Configuration IPv6 and Routing

Configuring AS confederation parameters....................................................................................................126

Chapter 7: PIM configuration procedures...........................................................................145

Configuration IPv6 and Routing

Configuring to exclude Gen-id.......................................................................................................................151

Chapter 8: MLD procedures.................................................................................................159

Configuration IPv6 and Routing

Chapter 1: New in this release

Configuration IPv6 and Routing

New in this release

Configuration IPv6 and Routing

Chapter 2: IPv6 routing fundamentals

IPv6 routing fundamentals navigation

Configuration IPv6 and Routing

IPv6 routing fundamentals

The IPv6 header

Figure 1: IPv6 header

Configuration IPv6 and Routing

The IPv6 header

Figure 2: 128-Bit IPv6 address format

An example of a unicast IPv6 address is 1080:0:0:0:8:8000:200C:417A

Configuration IPv6 and Routing

IPv6 routing fundamentals

Figure 3: Multicast Address Format

Figure 4: IPv4-Compatible Unicast Address Format

Configuration IPv6 and Routing

The IPv6 header

IPv6 extension headers

Figure 5: IPv6 Header and Extension Headers

Configuration IPv6 and Routing

IPv6 routing fundamentals

Comparison of IPv4 and IPv6

Hosts and routers

MTU Packet size

Multicast Listener Discovery

Configuration IPv6 and Routing

Configuration IPv6 and Routing

IPv6 routing fundamentals

Neighbor unreachability detection: hosts determine if the neighbor is reachable, and

Figure 6: Neighbor Discovery components

ARP Request message Neighbor Solicitation

A node sends this message to

ARP Reply message

A node sends this message either in

The neighbor cache contains

Configuration IPv6 and Routing

A host or node sends a request with its

The host sends this message upon